On January 28, 2010 at 15:55, cpmd said...
According to Logitech-Holland, the code I got from this forum was a bit short ?!?!
Can they give a slightly better explanation of what they mean by that?
The code you posted is broken into three lines with a real line break character at the end of each line. If the code you gave Logitech was the same, that might be a problem.
Pronto hex strings posted in forums usually look like they are multiple lines long with a line break at the end of each line. But actually a correct Pronto Hex string is one long line. The forum software displays one long line as it it were multiple lines. But with correct browser software settings when you copy/paste a Pronto Hex string from a correct forum post, it should be just one long line.
If the displayed line breaks became real line breaks, you might need to paste into wordpad or similar editor and replace the line breaks with spaces before recopying to whatever program or web page needs the correct Pronto Hex string.
But also this Pronto hex string is unusually short. That is because the signal it represents is unusually simple. Maybe whoever at Logitech that told you the Pronto Hex was "short" just didn't understand that it was supposed to be that short.
After all that, I don't know how to distinguish between the two likely causes of the problem:
1) Logitech didn't import the Pronto Hex string correctly, so you don't yet have use of the correct IR signal represented by that Pronto Hex string
2) The signal represented by that Pronto Hex string doesn't work for your model of TV.
Last edited by johnsfine on January 29, 2010 11:53.