Module going wonky

travis

I'm wondering if anyone has seen something like this. I have a module that has been working great, until recently. In this installation there are two of the same type of device, so I load the module twice from the same main code.

Now, after a power cycle, one of the devices is not being controlled. It still pings and can be controlled by sending the strings from a computer. It's a UDP device. The other device is working like normal.

This module is installed on like 30 different masters and this is the 2nd time this has happened. Last time I resent the programming and it started working again.

jjames

Is this a custom module? Did you write it? Did AMX write it? Duet? NetLinx?

Would probably be helpful if we had more specifics.

Auser

travis wrote: »

This module is installed on like 30 different masters and this is the 2nd time this has happened. Last time I resent the programming and it started working again.

Global variables are non volatile by default. There's a good chance that one which should have been declared as volatile, or be reinitialised at run time, hasn't been and the value it has acquired during operation is causing the module code to become confused when the system is rebooted.

Edit: I'm referring to global variables in the module here, not in the main code.

travis

jjames wrote: »

Is this a custom module? Did you write it? Did AMX write it? Duet? NetLinx?

Would probably be helpful if we had more specifics.

It's a NetLinx module that I wrote.

Auser wrote: »

Global variables are non volatile by default. There's a good chance that one which should have been declared as volatile, or be reinitialised at run time, hasn't been and the value it has acquired during operation is causing the module code to become confused when the system is rebooted.

Edit: I'm referring to global variables in the module here, not in the main code.

I will take a look at that.