On July 25, 2007 at 21:29, fcc said...
I'll trouble you folks again,
If you don't want to ask for help with this part of the task, you can use the same program I use to answer these questions:
[Link: remotecentral.com][Link: john.fine.home.comcast.net] If I can
get the needed info for makehex
Aiwa.irp
DEvice=1.0
a long press of the info button (2 seconds)
is required. I've tried increasing the duration of the
info RF period, as well as capturing a "long press".
All to no effect.
I'm not sure why that didn't work for you.
MakeHex or a long press during learning will give you Pronto Hex representing a variable length press of the button. You posted that kind of learn for INFO.
If it is then used as the only action on a button the duration will be controlled by the button press duration when you use it (as you would want for a Vol+ button or similar).
If it is used in a macro in a model of Pronto that supports duration the requested duration should work.
If you learn with a short press of the original button (as you did with the other signals you posted) you will get Pronto Hex for a fixed length short press. Then you cannot extend it correctly either by making it the only action and pressing longer during use or by specifying a long duration for use in a macro.
It is possible to construct Pronto Hex for a fixed length long signal to use in a macro. We can try that if you don't find a cleaner solution. But various models of Pronto have various undocumented limits in the size of a signal that they will understand in Pronto Hex. So depending on model specific details, there is a big chance that the long signal done that way won't work.
Older Prontos can generate a long signal by doing parts of the signal as separate buttons strung together in a macro. But newer Prontos are too slow to allow that to work. I assume your model is too new.
