Problems with IR Profile Editor (learning) and USBUIRT!!

[Invent]

As a precursor, I'm new to Girder 5 and am evaluating the unlicensed version for purchase. (Just in case there is something limiting about that version - not sure)

I'm using this on a new machine, with a fresh install of XP (fully updated), USBUIRT (v1.4 drivers), and the latest Girder 5 (5.0.8 build 542)

I'm able to use Girder5 and the USBUIRT to learn remote codes (pressing LEARN in the Event Mapping Editor works fine), Girder reacts fine to these learned IR events, logs them, etc. Also if I use Profile Editor and add an existing Manufacturer / Device Type, I can transmit IR codes fine. Seems like everything is great - until....

When I hit LEARN in the Profile Editor, the TEST button grays out permanently. Girder stops seeing any events from the USBUIRT. It does not LEARN from within the profile editor. The USBUIRT led stops responding to any IR remotes. Logging of any USBUIRT events ceases.

To get Girder working again, I have to kill the task from the task manager. It is responsive in its UI, but will not exit when requested. Once killed and restarted, things are fine again (USBUIRT working for events etc) - until hitting LEARN in the Profile Editor - blammo, off into the weeds. Once again, note LEARN works fine in the Event Mapping Editor...

So it looks like the USBUIRT gets 'locked up' by Girder when pressing LEARN in the Profile Editor, but not in the Event Mapping Edtor. What gives??

help! Am I doing something wrong? Or is this a bug...

[Invent]

An update - made sure I flashed the USBUIRT with the latest firmware.

Also built another new XP machine - installed nothing but XP, the USBUIRT driver and Girder. Same behavior... won't learn in Profile Editor. Kill Girder and the USBUIRT comes back fine.

New question - if my USBUIRT is 'old' (probably over 4 years old or so) - even taking the updated firmware - do I need a newer one or something? This is the only commonality between the two systems I've attempted this on.

Otherwise, if I can't use Girder to learn remote IR events - it will be pretty useless!

:( help

[Ron]

To test, instead of using the Profile Editor can you:



enable the USB-UIRT plugin
Add a new USB-UIRT action
Learn from there.


Let me know if that works or not.

[Invent]

Hi Ron,

OK, I tried that. Pressing the Learn button in the USB-UIRT Action dialog box pops up a child box, "Learn IR Code". As soon as this box pops up, the LED on the USBUIRT no longer flashes when transmitting a IR event to the PC. The log stops capturing any IR events, known or not.

The Signal bar stays blank. The learning bar stays blank. Clicking the "Force UIRT-RAW mode format" has no effect. "Accept Burst" is greyed out.

The one notable difference is, upon hitting "Cancel", the machine returns to normal operation. No longer is killing / restarting Girder required.

So, still stuck I guess :(

Thanks for your quick reply; we were off the grid up here for a while due to ice storms.

[Ron]

That is strange. What is the version of the usb-uirt PLUGIN? You can see this in the configuration screen.

[Invent]

It is Version 3.2.0, USBUIRT.dll, API:3, Device number 75.

This is weird enough that I've purchased a second USBUIRT from the Sage store - I'm going to write this off as h/w for right now, and try again when the new one arrives.

I'll update this thread when that happens... Thanks again for your prompt replies!

[Ron]

3.2.0 should be fine. Let us know what happens.

[rpalmer68]

I'm getting exactly the same problem.

USBUIRT works fine until I go into the USBUIRT Action and try to learn a code, then the USBUIRT just stops receiving anything (no light etc).

As soon as I close the dialog the USBUIRT starts working again.

I'm currently on Girder 5.0.6 (build 540), v1.4 USBUIRT driver, 3.2.0 Plugin version.

HELP!!! :)

Richard

[Ron]

Nothing has changed in the USB-UIRT driver in months,.. probably over a year. When did this stop working?

[Invent]

After purchasing a new USBUIRT (which did work better)- I did figure out what the issue was with the old one.

Try placing the remote that you are trying to learn codes from directly (and I mean less than 1/4 inch from the front of the USBUIRT) in front of it, and then try to learn.

Watch the LED - vertical/horizontal and angle are important.

My old one works now so long as I do that. Sometimes the CCFs it learns are not that great, and I have to try a couple of times. The newer USBUIRT works great.

The big suprise out of all of this was that when in one mode in Girder, you can learn from 6 feed away. In the other mode, you need to be on top of the USBUIRT. Not sure why, but everything works now :)

[rpalmer68]

Nothing has changed in the USB-UIRT driver in months,.. probably over a year. When did this stop working?


I've never tried to learn in the USBUIRT action until today.

As Invent says, learning an event action is fine, but learning an IR code gives the problems.

My USBUIRT is probably 5 years old and I don't need a new one so that's not an option for me.

Richard

[Ron]

I'm afraid there is not much I can do about that, it's Jon's code and Jon's hardware. You could try asking him over at usbuirt.com to see if he has any ideas.

[rpalmer68]

Well the USBUIRT firmware notes has the answer (as Invent discovered) ....


The new USB-UIRT firmware (v5.4 or later) in conjunction
with the new Girder plugin completely overhauls the learning
process. In previous firmware, learning takes place using the
same IR detector as normal reception. This is a long-range
detector which is designed to work across a room, and is not ideal
for learning. The new firmware uses a 'wideband' IR detector which
is built inside the USB-UIRT. This detector is solely for learning
and has a *very* short range. In fact, it is range sensitive and
for it to work your remote will need to be only a few inches from
the USB-UIRT. The wideband detector is located just to the left of
the indicator LED. When learning, you'll need to point your remote
directly at the USB-UIRT and on a level plane. If you're too close
or too far away, the LED on the USB-UIRT will not light up. When
learning, you may want to try learning a few times and
experimenting with the range that works best.
The wideband detector gives very precise information about
the IR signal -- *including* frequency. When learning, you will
see a frequency appear on the learn dialog if you are at a good
range. Also, a signal quality meter helps identify if you're not
aimed properly or at a poor range.


Richard