I just forked the GitHub project and checked in an improved broadlink_cli, supporting two new options, --durations and --convert. With the --durations option, instead send options are the durations in microseconds we are aware of, and --learn (and --learnfile) delivers the results as durations in micro seconds (with the signs common in this forum). The --convert option converts Broadlink data to durations.
This is the changed file.
How is this device as an alternative to an IR widget for going the other way 'round?
It obviously uses a demodulating receiver, with the properties we know of: no frequency measurement available, probably very limited possibilities to "learn" signals outside of 38kHz +- 2kHz. The captures appear pretty "dirty"; a lot of random errors. Im conjunction with a signal cleaner/repeat finder/decoder, it can certainly be used to "learn" at least standard signals. With some more work (2-3 days?), it should be possible to support it directly in, say, IrScrutinizer.
Quote:
Here is an example of what a 'learn' looks like:
Code:
2600 5800 0001 2894 1015 1015 103a 1014 1015 1015 1015 1015 1039 1139 1015 103a 1039 1139 103a 103a 1014 103a 1015 1015 1015 1015 1014 1015 103a 1015 1039 1139 103a 103a 1039 103a 1000 0529 0001 2949 1100 0c5a 0001 284a 1000 0d05
The just described program converts this to
Code: Select all
+9732 -4860 +529 -684 +529 -684 +529 -1891 +529 -684 +529 -684 +529 -684 +529 -684 +529 -684 +529 -1891 +529 -1891 +529 -684 +529 -1891 +529 -1891 +529 -1891 +529 -1891 +529 -1891 +529 -684 +529 -1891 +529 -684 +529 -684 +529 -684 +529 -684 +529 -684 +529 -684 +529 -1891 +529 -684 +529 -1891 +529 -1891 +529 -1891 +529 -1891 +529 -1891 +529 -1891 +529 -43382
+9732 -2414 +529 -106648
which is protocol = NEC1, device = 4, obc = 2.