Used IRScrutinizer, but protocol not detected #466
-
Hi Bength Martensson, I am a happy user of you tool, the IR scrutinzer, v2.3.1. {38.0k,256,msb}<2,-3|2,-8>(9000u,-8,A:64,B:35){A=0x500518430305330,B=0x181818181} +9000 -2700 +550 -800 +550 -750 +550 -800 +550 -800 +550 -800 +550 -1950 +550 -800 +550 -2000 +500 -800 +550 -800 +550 -800 +550 -750 +600 -800 +500 -800 +550 -800 +550 -800 +550 -800 +550 -1950 +550 -800 +550 -1950 +550 -800 +550 -800 +550 -800 +550 -1950 +550 -2000 +550 -800 +550 -750 +550 -800 +550 -800 +550 -2000 +500 -800 +550 -800 +550 -800 +550 -800 +550 -1950 +550 -2000 +500 -800 +550 -800 +550 -800 +550 -800 +550 -800 +500 -800 +550 -2000 +550 -1950 +550 -800 +500 -850 +550 -800 +550 -800 +500 -800 +550 -2000 +550 -800 +500 -2000 +550 -800 +550 -800 +500 -2000 +550 -2000 +500 -800 +550 -800 +550 -2000 +500 -2000 +550 -800 +550 -800 +550 -800 +500 -800 +550 -800 +550 -800 +550 -1950 +550 -2000 +550 -800 +500 -800 +550 -800 +550 -800 +550 -800 +550 -800 +500 -2000 +550 -1950 +550 -800 +550 -800 +550 -800 +550 -800 +550 -750 +600 -750 +550 -2000 +550 -1950 +550 -800 +550 -800 +550 -800 +500 -800 +550 -800 +550 -800 +550 -1950 +550 -2000 +550 -800 +550 -800 +500 -800 +550 -800 +550 -800 +550 -800 +550 -1950 I have a decorative fireplace with a remote, of which I want to copy the commands to be able to controll it with an arduino. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 1 reply
-
Not all used IR signals correspond to previously known and documented protocols. It is quite possible, in particular for these kind of long signals, that it is something invented by the device manufacturer. Also, your captures are of fairly low quality (using a demodulating receiver probably). Consider getting better capturing hardware, using a non-demodulating sensor, like for example this. Then capture all the available commands, collect the results in a text file containing the command names and the captures. Try to find out if the keys are repeating or not. Then post the result here, and we'll see we what we can do. |
Beta Was this translation helpful? Give feedback.
-
Thanks for answering! |
Beta Was this translation helpful? Give feedback.
-
I edited the file to a format that we can analyze, found here. Running irptransmogrifier/analyze on that file gives:
So there are a few questions left. In particular, why are some signals a payload of 143 bits, while others are "broken up" after 99 bits? The former can be used as a protocol {562,msb}<1,-802u|1,-2009u>(16,-2009u,A:143,1,-30m), the rest with a similar protocol {562,msb}<1,-802u|1,-2009u>(16,-2009u,A:99,354u,-802u,B:43,1,-30m). But I have a bad feeling that your captures are too imprecise. Using a demodulating receiver like yours is not a good idea for analyzing IR signals, if possible get better equipment, like this. (I do not hold very much of "hobbyist IR boards" like the one you linked. It is in general a low-quality Chinese TR sensor (for example VS1838), with some non-essential resistors etc. Better to by for example a good-quality sensor from Vishay, they cost less than your hobbyist board, and comes with a data sheet. You can now go on trying to identify which bit makes what in the IRP representation. You will probably find IrpTransmogrifier usefule for this, a part of IrScrutinizer, and installed (as wrapper) together with the latter. |
Beta Was this translation helpful? Give feedback.
-
Hi, I was able to use the appropiate hardware, namely the TSMP58000. Just connected the bare minimum and I was able to use the .bat file to flash GirsLite on my nano (following this guide: http://www.harctoolbox.org/arduino_nano.html) |
Beta Was this translation helpful? Give feedback.
-
Now the captures all look much more similar; all signals seem to decode to I am not going to clean up your log file for you. If you want to pursue this issue further, you can capture the signals in raw mode in IrScrutinizer, using the Scrutinizer remote -> Raw remote pane. If you so desire, you can try to identify what the different of the 192 bits do. Strange is that subsequent captures of the "same" command seem to differ in as much as 9 bits: Sometimes there are toggles, they are in general one bit. Possibly there are time stamps, or battery status, air pressure/temperature/humidity or anything ... But this is probably beyond the original question. |
Beta Was this translation helpful? Give feedback.
I edited the file to a format that we can analyze, found here. Running irptransmogrifier/analyze on that file gives: