08-21-2013 04:27 PM
I have an intermittent problem where a network-published shared variables fails to send a command from the host GUI to the PXI Real-time target. For example, a valve control suddenly became on-responsive during testing although all other controls and indicators were functioning correctly. Communication to open and close the valve is controlled by network-published shared variables. Then when I stopped the host computer, the target did not stop as usual. The shared variable named "StopAll" should as stopped the target when the host was stopped. I have a number of other examples like this where a particular shared variabe was functioning and then became non-responsive. Occassionally I see error -1950679035. This is a potentially serious situation when testing rocket engines if a valve does not open of close when commanded.
I wish to ask if any could offer some troubleshooting suggestions for me to investigate this internittent problem?
Hardware Overview:
PXI-1050 Chassis:
PXI-8110 Controller
6221 – Accelerometers
6280 – Pressure / Voltage
6224 – Controls / Indicators
6220 – Thermocouples
6221 – IEPE (Not Wired)
SCXI-1520 – 8 Load Cells
SCXI -1520 – 8 Load Cells
SCXI-1520 – 8 Load Cells
SCXI-1104 – 32 Multiplexer
PXI-1052 Chassis:
SCXI-1000 Chassis:
SCXI-1102 – 32 TC1
SCXI-1102 – 32 TC2
SCXI-1102 – 32 TC3
SCXI-1530 – 4 IEPE (Accel)
PXI-1052 Chassis:
SCXI-1001 Chassis:
SCXI-1143 Filter 1 – 8 PT,V
SCXI-1143 Filter 2 – 8 PT,V
SCXI-1143 Filter 3 – 8 PT,V
SCXI-1143 Filter 4 – 8 PT,V
SCXI-1143 Filter 5 – 8 PT,V
SCXI-1143 Filter 6 – 8 PT,V
SCXI-1143 Filter 7 – 8 PT,V
SCXI-1143 Filter 8 – 8 PT,V
Thanks, Bill
08-21-2013 11:08 PM
...Which is another reason why I don't use shared variables. IMHO they have way too much hidden "under the hood". It's a good idea, but there are more robust (and debugable!) ways of accomplishing the same thing.
You could establish TCP/IP connections.
You could used VI Server.
There are potentially lots of options.
Mike...