Serial coms On Girder Open causing crash kernel32.ddl error

[Ron]

I think Mark is out of town at the moment, so we'll have to have a little patience here.

[Ron]

Fixed:

http://www.girder.nl/temp/ieventc12.zip

[Mark F]

I got back yesterday. What a trip.

I'm currently using Girder 3.2.1, Win 98SE, Serial plugin 3.0.4 and (of course) don't see the problem. :( I have set up an event for On GirderOpen which sends data through one of the ports (NULL modem cable attached) and receives the same data on another port.

Does this occur if your .gml file has one command? If you disable other devices? I'm trying to figure out why the timing on your machine is so different from mine. Thanks.

[rickd]

Ron or Mark

Version 3.2a

I have narrowed this down to serial commands requesting data of the serial port by sending a command On Girder Open. It seems the crash occurs due to the devices not being ready yet ie still enabling the serial ports or input devices in my veiw.

If I load the GML file manually after all devices are enabled (ie disable autoload and load file manually) there is no problem....I have disabled the serial data request on open commands and the group loads and does not crash girder when set to autoload. These commands work fine with test command too.


Cheers Rick

[rickd]

Hi Mark I send data on two ports and this triggers receive data on both ports. These ports are on a serial port card com3 and 4.

These events are then processed by my on serial event group and parsed for the data they retrun.

They are basically to get the state of the devices on open.

I have them in separate on open commands might try putting them all in one multigroup and or turning one off at a time and see if it is related to one command.

Also since they generate other serial events perhaps their is a problem there but the new queuing events in girder should take care of that no?

Also I don't have 3.2.1 only 3.2.0

Cheers Rick

[rickd]

Ron this is actually being caused by a coomand using the ip client. It only seems to happen the first time. Once you reload and try again it's ok. It is part of a multigroup initated at start up. It sends a request to my other machine to send an ir command via the slinke.

Do I need to put something into the payload area?

I run ME on the client and XP pro on the Server and 3.2.1 on both machines cheers Rick

[rickd]

Yeap that nailed it :D

Thanks Rick