Recevier improvements - setReceiveUsingProtocolTiming() and setReceiveUnknownProtocol() #418
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This library is using initial synchronisation pulse to determine base delay value used for decoding data. Some cheap transmitters use slightly shorter synchronisation pulse and, as a result, system is unable to recognize the data sent.
Setting setReceiveUsingProtocolTiming(true) tells library to use standard delay for protocol (e.g. 350 microseconds for protocol 1) to decode input.
This makes receiver more robust - able to receive data that otherwise was ignored.
This is used as debugging aid only.
When system is unable to recognize any valid protocol it produces no output. It is difficult to tell is system didn't receive any data or was unable to decode it.
With setReceiveUnknownProtocol(true) you can see the dump of timers even if no valid protocol was recognized. The
ReceiveDemo_Advanced
example was updated to use it.