01-04-2008 12:25 PM - edited 01-04-2008 12:26 PM
01-05-2008 11:20 AM
Hi richjoh,
I noticed there is now a Device Status shared variable. Has that provided any insight as to why you may be receiving a device error? A good first step when receiving error -1950679038 is to check your hardware configuration.
I'm not sure about the Commfails. Do you have any waits in the loop you are running? Also, do you have multiple network cards on your computer? If so, it may help to disable any that are not being used.
01-07-2008 06:51 PM
01-08-2008 02:53 PM
OK, SV on the block must be wired or errors occur.
I can read registers and write, my problem is when I make a value change on a control, the SV green (triangle binding indicator) goes red! At this point I see the SV engine is running but SV manager reports "device failure". I can only read my value back after I toggle the SV engine process off and back on. What going on here...anyone???
01-15-2008 10:26 AM
OK, just to clear this issue up a little, I confirmed the following.
LV version 8.2 DSC modbus is not functional after a write. All shared variables show device error in the manager after a write. Only a toggle of the process will bring the SV back.
LV version 8.5 DSC modbus is functional after a write. My Watlow controller is capable of update at 100msec. LV version 8.5 Modbus default update rate is 1 second. Writes require a few seconds to read back in LV 8.5 modbus. During the time between writes and read an error is reported in the error cluster (block diagaram SV) or you get the red icon (front panel SV).
Thus issues still exist with Modbus SV engine LV 8.5
richjoh