On January 29, 2009 at 15:10, Outlanderman said...
OK, as promised. Based on the Velleman specs I built
the Pronto hex codes for the keys I needed, Vol+, Vol-,
and Mute. I then used Girder and my USB-UIRT to enter
the codes on my PC & transmit them to a learning remote
I have (you could use Irnhelper or other free software
I am sure). This worked fine, and I can indeed now control
my Velleman MK164 volume control using pretty much any
learning remote in the house.
Very impressive.
I wrote Makehex, so if I thought I understood those Velleman specs, I could trivially write a .irp file to cause MakeHex to generate all the Pronto Hex strings.
But I looked at those specs and saw several details for which there might be ambiguity in their meaning. That gets hard to deal with since I don't have the actual device to test. So I didn't try.
I haven't looked at the details of your working Pronto Hex strings, but those must resolve any ambiguity in the meaning of the spec (or they wouldn't work) so if there remains any reason to have the .irp file (rather than just the strings you posted), someone should ask and I'll write it.
Vol+: 0000 006E 0000 000C 001A 011E 001A 00c0 001A 00c0
001A 00c0 001A 00C0 001A 00C0 001A 00C0 001A 011E 001A
00C0 001A 011E 001A 00C0 0001 0B00
This worked well when learned by one of my remotes, not
as well on another. However, the "one-click" codes worked
on everything.
That's a strange choice for controlling the delay. I expect what you wanted was
0000 006E 0000 000C 001A 011E 001A 00c0 001A 00c0 001A 00c0 001A 00C0 001A 00C0 001A 00C0 001A 011E 001A 00C0 001A 011E 001A 00C0 001A 0B00
or maybe
0000 006E 0000 000B 001A 011E 001A 00c0 001A 00c0 001A 00c0 001A 00C0 001A 00C0 001A 00C0 001A 011E 001A 00C0 001A 011E 001A 0BC0
Could you check how those behave?
