USB-UIRT Sending Delayed Signals To Zones 1 and 2!

[shalamigri]

This problem I'm sure is error on my part because I just started using Girder. I have Girder set up so that when I send certain commands to the USB-UIRT from my universal remote, device commands are sent to 2 external cable boxes on zone 1 and 2. It seems that when I press a button on the remote, Girder or something is sending 2 or 3 presses to my boxes. I set the repeat value to 1. Now, if I hold a button on my remote, nothing happens until I release the button and my box sees only one key press. So a tap on the remote sends multiple commands and a long press issues one command. This seems backwards to me. It seems like something maybe in the Girder software which I don't know how to adjust. Has anyone else seen this?

[shalamigri]

I now believe it's somethig to do with the receiver on the USB-UIRT or my remote. When I run the test in Girder, the command is sent to zone 1 and 2 immedately and the box does the proper funtion. When I aim my ir remote at the USB-UIRT, the light on my emitters for zone 1 and 2 come right on, but it appears that my box has a hard time determining the ir signal. I have to keep pressing the button before my cable box can see the signal. I tried the same setup with my firefly remote to see if there would be a delay; there wasn't. The firefly is able to send the command almost immediately to my zones.

[shalamigri]

I think I figured it out. The USB-UIRT handles(receives) certain IR codes better than others. I played around with various codes on my universal remote and got all kinds of results. I think I will purchase a Harmony Remote now.

[jrhees]

shalamigri,

You are experiencing issues with IR 'collisions'. Because the USB-UIRT is receiving IR from your remote, it must wait until your remote 'shuts up' before it can send out the IR code (from your Girder script) to your cable box. Different remote protocols will have different 'gaps' between repeats of a code, which is likely affecting your results.

In addition, not only must the USB-UIRT wait until IR reception is finished before it can transmit, but if your cable box sees IR from your remote at the same time (or too closely spaced) as IR from the USB-UIRT, it will not recognize the IR.

To verify, try this:

1. Modify your script in Girder and add a Girder Delay/Sleep of 1 second at the beginning of the multigroup triggered by your remote.
2. Tap the button on your remote for a very short duration to trigger the Girder multigroup. The delay before Girder transmits IR will ensure that the IR from your remote has terminated before Girder tries to transmit.

See what behavior this exhibits.
-Jon

[Guest]

shalamigri,

You are experiencing issues with IR 'collisions'. Because the USB-UIRT is receiving IR from your remote, it must wait until your remote 'shuts up' before it can send out the IR code (from your Girder script) to your cable box. Different remote protocols will have different 'gaps' between repeats of a code, which is likely affecting your results.

In addition, not only must the USB-UIRT wait until IR reception is finished before it can transmit, but if your cable box sees IR from your remote at the same time (or too closely spaced) as IR from the USB-UIRT, it will not recognize the IR.

To verify, try this:

1. Modify your script in Girder and add a Girder Delay/Sleep of 1 second at the beginning of the multigroup triggered by your remote.
2. Tap the button on your remote for a very short duration to trigger the Girder multigroup. The delay before Girder transmits IR will ensure that the IR from your remote has terminated before Girder tries to transmit.

See what behavior this exhibits.
-Jon

I have no idea how to achieve this. I looked around for delay/sleep options, but did not see any. I did see something about scripts. I'll try Girder's website to see if I can find a script there.