John:
Thanks for your post. Interestingly, the two approaches (MakeHex and the excel spreadsheet) give different encodings:
From MakeHex:
Device Code: 07.07 Function: 1B
0000 006D 0000 0022 00AC 00AC 0015 0040 0015 0040 0015 0040 0015 0015 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 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0689
From the excel spreadsheet:
0000 006D 0000 0022 00AC 00AC 0015 0040 0015 0040 0015 0040 0015 0015 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 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0680
Unfortunately, neither code worked (code 1b; TV (ant) input) on my TSU3000 tring to control my HLP4663.
Btw, the contents of my makehex control file (NecX2.irp) is:
Device=7.7
Function=0..255
Protocol=NECx2
Frequency=38000
Time Base=564
One=1,-3
Zero=1,-1
Prefix=8,-8
Suffix=1,-78
Default S=D
Form=;*,D:8,S:8,F:8,~F:8,_
John, in earlier posts, I've seen people use device code 7; your post recommended device 7.7. What are these codes and how does one go about figuring out the correct one to use (other that sending posts to bboards like this, of course!!)
Thanks for your help. I would still love to find a discrete code for TV input; using the DVI
TV/Vid sequence can work, but I don't like the 5 second delay I've had to introduce into my Pronto config....
Thanks,
-- Dave
On 11/08/04 18:31 ET, johnsfine said...
You use one of several tools for generating Pronto
Hex, such as "bmontini's Excel spreadsheet" mentioned
earlier in this thread (and linked to in some
recent thread here) or my MakeHex program.
For MakeHex, you'd need to know that the protocol
is NECx2 and the device is 7.7
You ought to use MakeHex from command prompt with
the -h switch, rather than via the drag/drop method,
ecause that will give you function numbers in
hex rather than decimal, so you won't need to
convert in order to use the list in this thread.
These numbers need a translation before they can
be used with the OFA remote. If you want them
for the OFA remote, I'll explain that translation.
But if you want them for a Pronto, MakeHex is
easier and better.
