Command works in TEST but not normal mode

[windtrader]

I have a Girder command that works in TEST mode but will not work in normal mode. I am using the Girder plugin and a UIRT2.

I created a command using the UIRT2 driver plugin. In the settings I learned the IR command, applied it, then used the TEST button. The command works and the equiment responds properly.

I hit OK and return to the main panel where I Learn Event which adds the EventString. I try the command again and it does not work. The learned event code is right as the IR code on the bottom of the screen matches the learned event code. I select a different command on the left, press the remote key and Girder jumps to the command and sans IR Command Sent.

The equipment's LED lights when receiving IR code. In TEST mode the LED blinks but it does not in normal mode.

I've used Girder for months and never had this problem. I did try to vary a few of the other settings such as repeat and carrier but still no luck. I'm pretty stuck, anyone with ideas???

Thanks, Don

[jon_rhees]

Don,

While in Girder, if you right click on the new command and choose "Test Command" does that work?

-Jon

[windtrader]

Hi Jon,

Yes it does.

[jon_rhees]

Don,

if you can successfully send IR when using the 'Test Command' menu item, but have trouble when initiating the IR blast with an IR 'event', then I would guess you're suffering from IR 'collisions' -- ie., your remote control you're using to generate the event is colliding with the IR blast from the UIRT.

In the UIRT settings, there is an option for each command to 'Wait for n mS or IR inactivity'. Try this to see if it'll help.

Also, to prove whether this is indeed what is happening, try putting the command into a multigroup which is initiated by the event, with a 'Delay' before the Command, such that when you press the remote to initiate the event, Girder then waits several seconds before doing the UIRT command. If this works, you know it is IR collision.

-Jon

[windtrader]

HI Jon,

Just got back into town and tried your suggestion. BRAVO! Adding a delay fixed the problem. I tried it with 20ms, 50ms, and 100ms. At 20ms, the problem persisted, at 50 it worked intermittently, and at 100 I got reliable and stable results.

Since this worked, I did not try a multigroup with the "Delay before the command" parameter. Do you implement the "Delay" via a Windows-Wait command? I could not find any other delay command or option.

Just curious but what causes this condition? This is the only piece of equiment and command that causes this problem. Other commands on this equipment work fine. Is the problem the remote is still sending IR commands while Girder has already received the command and the plugin starts sending out the IR send command causing the collision? Does this mean I haved learned a string of duplicate commands or are long IR commands not that unusal?

FYI - it is the Lexicon sound processor's main power on and off command giving me the trouble.

Thanks again,
Don