I don't know which thread you mean. But in such situations, I decode the signal. That would give me the set of 256 signal to try, just as I already gave you in this case. I also would do a scan of my large library of downloaded IR files (CCF, JP1, etc.) for matching signals (as I did to find that JP1 file I mentioned) and then I check those files to see if the people who posted those files included discretes. In this case they didn't. Usually there is no more I can do than that.


Nope.


A few brands have consistent rules for discrete codes. Most don't. Samsung certainly doesn't.


I don't know a good way to experiment. But there is another approach, with a decent chance of creating discrete On and/or Off for a device with none designed in. Since there is no systematic approach to finding it, most people don't waste the time, but I'll mention it.

The device ignores most commands when off, and it probably ignores all commands during a short moment while executing certain commands. The first "ignore" above may be fast enough to allow a work around for discrete On:

Issue some command instantly followed by a minimum length power toggle command. If the device is off, it will ignore the first, maybe fast enough to execute the second. If on, it would obey the first and fail to see the second.

For other devices (probably not a set to box) there is a very low power mode used for "off" which is not as good at understanding IR as full power mode. For those devices, one might find an imperfect power toggle signal that can only be understood when the device was on.

Usually the macro capability of the remote isn't fast enough to control timing that well, so instead, one combines the commands on the form line of the .irp file to put a mini macro into one Pronto Hex string.