USB-UIRT Forum

That's the error message I'm getting when I start NetRemote IR Server. The driver I'm using was downloaded from usbuirt.com within the past few days. Windows Device Manager says it's working properly, but the error comes up every time I try to start NRIRSrvr.

I've tried a different USB port as well as connecting it to a different computer and installing NRIR there. Still get the same errmsg.

I bought this USB-UIRT almost 3 years ago; I don't recall ever updating the firmware. Is it possible that the unit I have is so old that the firmware isn't compatible with the latest driver?

Anything else I should try? Or should I assume that this one is simply D.O.A.? Thanks in advance for the help.

Donny,

It really depends on *what* the error message says. That will give a clue as to where the problem is.

I would suggest contacting support@usbuirt.com and getting the lrnHelper test app. This will allow you to verify proper operation of the USB-UIRT first.

-Jon

Jon-

I got your response to my e-mail, but I've somehow lost it. I'll download the latest firmware update and apply it and retest, but can you please resend the test app? Thanks!

Umm... I can't find the firmware update.
I downloaded latestgirderplugin.zip - wasn't there. Tried downloading "brokenlink.zip" - wasn't there either.

OK. I found the firmware update by Googling for it. Not sure if it's the latest or not, but IR passthrough via NetRemote is working now.

Looks like I spoke too soon, Jon. It's not working very well at all. I press a button, see the LED on the front flash - nothing happens. If I press the button 2 or 3 more times, the LED stays on (and the process on the computer seems to hang. I have to end the process to get the LED to turn off.) Hopefully this sounds familiar and gives you some ideas. Also, I can't be sure it was the most recent version of the firmware, so let me know when you have a link on the website to that and I'll download it. Does your test app reveal the firmware version. Please resend the test app - looks like I'm going to need it. Thanks!

Donny,

Please use this firmware:

www.usbuirt.com/latestFirmware.zip

As far as Netremote and remote codes 'sticking on', I believe there is newer Netremote NRIRServer/Plugin code which remedies this. I originally write the first NRIR_USBUIR USB-UIRT plugin for NRIRServer, but then turned it over to Ben S. at Promixis (before Netremote was bought by Promixis) and he has maintained it and changed it as he change NRIRServer's protocols. Part of the changes made to NRIRServer were to handle holding buttons down more reliably, etc.

-Jon

Thanks, Jon. I'm actually using the latest version of NRIRSrv. I think the problem may be malformed IR codes. I'm going to try using lrnhelper and see what I get. One last question - what's the differenc ebetween lrnhelper-1 and lrnhelper-3. I'm guessing maybe one supports 56K and the other doesn't? (I have the 56K version.)

Jon-

I've now upgraded to the latest firmware. I've also confirmed the validity of the IR codes in my NetRemote CCF file by setting it for direct IR and controlling the components via the IR emitter on the Pocket PC - that works. But controlling via IR passthrough thru the USB-UIRT does not.

I'm continuing to experience the problem in which the red LED on the front of the UIRT stays on solid until I kill the NRIRSrv process.

Is it possible that there's some sort of driver issue due to the fact that I installed the hardware and driver when the firmware was quite old? Should I remove the hardware and driver and reinstall? Is there some test I should run with the lrnhelper app? If so, I need to know which one to use (-1 or -3) and what you need me to do.

Please help me with this, Jon.

Thanks,

~DB~

I don't think this is a driver/firmware issue, but instead some sort of issue with Netremote/NRIRServ.

One easy test you can do is to paste these Pronto codes into lrnHelper and transmit them with LrnHelper to verify a) they work correctly, and b) you don't see the USB-UIRT 'stick on'.

Another thing you can try is to go into NRIRServ's settings where there is an option to 'Disable Hold-down Button Repeats' which you can turn ON and see if that affects the 'stick-on' issue.

-Jon