Some STRANGE PROBLEM

udi

1. I have an ADB-CABLE 1090 and I didn’t found an IR file for this device I tried to do an IREdit file and I tried to teach hex command from the remote and using the discreet IR hex code, but
Only 3 buttons are working and all other button didn’t work and if I use the hex code with other device like pronto it is working OK. Does anyone know what could be the problem? Or maybe have an IR code for this device?

2. I have an media center and I made arrows on my iPad to control the media center, when I am sending an IR command by push the cursor button like cursor up it is working ok but if I push again on the on the same button it isn’t doing anything, if I push up -> down-> left-> up -> right it is working. But if I press up -> up -> up it only work in the first time. I don’t know what could be the problem.

Someone told me he ran into these two problems and he told me to try to increase the TIMOUT but I didn’t understand what he meant?

Related Files are added.
my problem is Refers to the YES and PCMEDIA include files


I hope someone could help me with this two problems.Thanks for any help

the8thst

Try controlling the cable box using "Diagnostics->Control a Device" to make sure you don't have an error in your code.

As for the media center you are running into IR codes that have a toggle-bit.
Check this out: http://www.cepro.com/whitepapers/details/the_ir_toggle_bit/

udi

the8thst wrote: »

Try controlling the cable box using "Diagnostics->Control a Device" to make sure you don't have an error in your code.
/QUOTE]

how could i know if i have an error in the code???
i used the acuate on the IREDIT to send a pulse commands and it sends the commands but only the 3 buttons are working and when I am sending others butoon the device dont get them but the led on the AMX device of the port is working? I dont know if it is the ir commands that don't good because i tried to use different hex code for the same butoon but it is still dont work.
could it be a problem in the code or in the ir file??? how can I know?

Jorde_V

udi wrote: »

the8thst wrote: »

Try controlling the cable box using "Diagnostics->Control a Device" to make sure you don't have an error in your code.

how could i know if i have an error in the code???
i used the acuate on the IREDIT to send a pulse commands and it sends the commands but only the 3 buttons are working and when I am sending others butoon the device dont get them but the led on the AMX device of the port is working? I dont know if it is the ir commands that don't good because i tried to use different hex code for the same butoon but it is still dont work.
could it be a problem in the code or in the ir file??? how can I know?

That's why he said you should try "Diagnostics-> Control a Device". You can then check all the channels of your IR file by controlling the device you mapped to it and pulsing the channels you want to check. That way you know whether it's the commands.

DHawthorne

I've made many posts about this, and at the risk of repeating myself to those who have heard it before, the IRIS box is flaky, and it is possible to capture IR incorrectly with it. It still boggles my mind that AMX has not updated the thing, and that cheap, throwaway devices can often do a better job.

Some guidelines:

1) Try to hit the button you are capturing solidly, and for no more than a half second ... but no less either. The IRIS especially has trouble with repeating IR codes.
2) As best as you can, hit the button on the verify pass exactly the same length of time as the initial press.
3) Remote buttons can be mushy, and difficult to press solidly with consistent timing. There are some remotes I've done better with by taking them apart and firing the IR code by directly shorting out the PC board where the button lands.
4) It's a bit of extra work, but often a difficult remote can be better captured by using something like a Pronto or RTI remote, that allows you to copy the IR hex,k then pasting that in IREdit. I've even captured something on a Universal remote, then captured the Universal to the IRIS. I haven't tried it yet, but I'm also betting the Global Cache capture would work too.

ericmedley

DHawthorne wrote: »

I've made many posts about this, and at the risk of repeating myself to those who have heard it before, the IRIS box is flaky, and it is possible to capture IR incorrectly with it. It still boggles my mind that AMX has not updated the thing, and that cheap, throwaway devices can often do a better job.

Some guidelines:

1) Try to hit the button you are capturing solidly, and for no more than a half second ... but no less either. The IRIS especially has trouble with repeating IR codes.
2) As best as you can, hit the button on the verify pass exactly the same length of time as the initial press.
3) Remote buttons can be mushy, and difficult to press solidly with consistent timing. There are some remotes I've done better with by taking them apart and firing the IR code by directly shorting out the PC board where the button lands.
4) It's a bit of extra work, but often a difficult remote can be better captured by using something like a Pronto or RTI remote, that allows you to copy the IR hex,k then pasting that in IREdit. I've even captured something on a Universal remote, then captured the Universal to the IRIS. I haven't tried it yet, but I'm also betting the Global Cache capture would work too.

Also, it is quite possible that the IRIS need recalibrating. I've had one do this and it was unable to capture any remote. After sending it in and having it recalibrated, it worked fine.

John Nagy

The remote problem relates to the debounce feature implemented in MCE.
They have alternating IR commands, the remote gives a different IR the second push, and the MCE won't take the same command twice for the same function in order to know you didn't hold the IR by mistake.

You need to tell the MCE to stop using alternating codes. There is a small registry hack that will fix it. Newer MCE might have a setting to do this from the UI, I don't know.

There is a Windows XP registry value called EnableDebounce, and you have to change it to 0, from its default value of 1.

The registry value is located:

For Media Center 2004:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\idIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da

For Media Center 2005:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da

I have not looked for these settings in newer OS/APP combinations.

If you are not familiar with making changes to the Windows System Registry, refer to this Microsoft support document:

http://support.microsoft.com/kb/322756