Dear John,

Reading the threads in this forum for some months, I noticed, that you must be one of the real RC-Cracks in here. So I allow myself to ask you for a solution for my "little" remote control problem, which is the following:

To reduce the number of all the remote controls of my little home theater equipment, I bought some time ago a Philips Pronto Professional TSU 9400. Very cool device. I made it to learn all the infrared codes from the original rc's and now I can control all my devices very well from the TSU 9400. There is only one nerving exception: The tv-cable receiver I got (Brand name: ItGate [www.itgate.co.kr] / Device model: TGM220) can only be controlled with the original rc by a toggle button command "power on / power off". All my tries (also in this forum) for researching the discrete code commands "power on" an "power off" were without success. So I ask you, if there is some way to find out this discrete code commands "power on" and "power off" for this device experimentally by modifying the learned IR code for the toggle button command from the original remote control, which is (in the Pronto Hex format) the following:

0000 006D 0022 0002 0155 00AC 0015 0016 0015 0040 0015 0016 0015 0016 0015 0016 0015 0040 0015 0016 0015 0016 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0016 0015 0040 0015 0040 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0040 0015 0016 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0016 0015 0040 0015 0016 0015 05C8 0155 0058 0017 0E52


Thanks al lot for your answer, which will be highly esteemed!

Greetings an my best regards, Pasquino


P.S: All the other RC cracks are also allowed to reply! ;-)

There is no generic way to turn a power toggle into a discrete.

You can decode the toggle (IrTool and DecodeIr) then use MakeHex to generate the full set of 256 signals and test them to find a discrete code if it exists and you just don't know about it. But you can't create it that way if it doesn't exist.

It's possible that the device uses different rules for checking the validity of a power toggle when the it is off than when it is on. So you might find a fixed duration signal is long enough for one but not the other, or maybe unrelated garbage IR just before or after the signal will stop one from seeing the power toggle, but not the other. Or maybe a legitimate other command immediately before a power toggle (in the same pronto hex string, not a macro) would cause the device to be too busy to see the power toggle if already on, but it would ignore the other command and then not be too busy if off.

With a good understanding of Pronto Hex and lots of nearly blind experimentation you might be able to invent a power discrete where none existed.

Dear John,

Thank you very much for your instant reply. I will try the way you have proposed. But I have another problem. I'm a little bit a dummy concerning deeper knowledges about "computering" (perhaps a question of age). I just downloaded the recommended program files and tried, but it didn't work. Can you just give me a little crash course how to manage the right way? (Please try to understand, it's not my intention to let do the work from other people, but english is not my mother-tongue, and so technical explainings in english in the readme-files are sometimes difficult to understand, sorry).

Again thanks a lot, Pasquino