On February 23, 2020 at 11:06, Barf said...
It appears that there is a misunderstanding somewhere. Most ("most") IR signals are not NEC, just as most vehicles are not airplanes. If a signal is not NEC, say it is RC5, there is no way to convert it to NEC, just as you cannot convert an automobile into an airplane.
IrScrutinizer will recognize NEC signals as such, if it is recognized as something else (say RC5), it is clearly not NEC. If it is not recognized at all, it is likely somehow fawlty read. In rare cases, it may be a protocol that IrScrutinizer does not know yet.
As long as I have the pronto hex code, for example:
"0000 006e 0022 0002 0154 00aa 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 06a2 0154 0055 0015 0e3d"
and I try to transmit it via comsumerIR of an android app for example, should I care if the pronto hex is in RC5 protocol or NE protocol for example or I can just transmit it as is?
is the type of the protocol is relevant only when I want to convert a hex code into a pronto hex code?
thank you for the explnations
