Girder 3.2 irMan plugin Bug?

[Ron]

Checking it out now.

Update: found bug; beta 13 released.

[Ron]

As far as I know the plugin sets all signals. Evation is working on the IRserver Girder 3.2 plugin. It would be great to find out what is wrong though.. what options did you try in the plugin ?

[stevech]

IRman plugged into COM1 of a Windows 98SE laptop.
After selecting the IRman plugin:
Each time I ENABLE INPUT device, I get this error pop-up from Win98SE:
Access violation at address 04F4041 in module GIRDER.EXE read address FFFFFFFF. When I dismiss this pop-up, Girder is still running.

When I first enable the irMan plugin, the Settings window says Plugin loaded but hardware initialization failed.

What I've tried:
- Ran irMan's server software on same COM port. Works properly.
- disabled plugin. exit and restarted Girder.
- Reinstalled Girder 3.2

- Removed 3.2. Installed 3.1. Now irMan plugin no longer causes the access voilation (as shown above), but irMan still fails to initialize. File/Enable yields Error Could not enable some of the input devices...

[stevech]

Fast fix! I'll try it.

I still have this problem: My irMan works on my Win XP desktop PC but on my Win98SE laptop, it works OK with irMan's "server" software but not with Girder 3.1 or 3.2. Girder gives an initialization error. I speculate this: irMan obtains its power from RS232 signals such as RTS and DTR. Could my problem be that the irMan server is setting ALL of these signal lines TRUE but the Girder plug-in is not doing so? Laptops often have weak RS232 signals. This could explain the symptoms. Or, I could be totally wrong!

[stevech]

All is working OK now.
Installing version 3.2 beta 13 cured the memory access error.
The access error was caused by a Girder bug arising upon a failure of the irMan hardware to initialize.

The irMan didn't initialize because of acute user stupidity. I had used Girder/irMan for quite some time on a desktop PC on COM2. I just started doing so on a laptop on COM1. I (stupidly) had never had to change the default serial port in the plug-in which is COM2, and for the laptop, I thought the plugin searched the COM ports for irMan automatically. Well, it doesn't - all I had to do is engage my brain and chose COM1.

Duh. That's it.