Error -1950679023 Occurs Occasionally for an Application Using CompactRIO

Updated Apr 12, 2019

Reported In

Hardware

  • CompactRIO Chassis

Software

  • LabVIEW

Issue Details

I have a cRIO application in the field that had been running continuously for months without any problems. However, last week I got the error -1950679023, causing the application to stop. Afterwards the application started again without any problem. This happens from time to time and the error message usually disappears after 35-40 seconds.  

Here you can see an image of the error and its explanation


And here, the error in text:
Error -1950679023 occurred at an unidentified location

Possible reason(s):

LabVIEW: (Hex 0x8BBB0011) The process specified in the binding URL does not exist. Ensure that all shared variables are deployed and the variable identifier URL is correct.

 

Solution

The error -1950679023 is due to the system that is hosting your shared variable being unable to find the shared variables. This could be caused by:
 

1. A bad connection between the PC and the cRIO device or a dip in the power supply of the installation
 
This sort of behaviour can be characterised by network instability or the cRIO device disconnecting periodically from the host device. Errors in the network can often be analysed using third party tools like Wireshark.
 
 
2. The Shared Variable Engine (SVE) is crashing momentarily
 
If you are using a LabVIEW Real-Time target such as CompactRIO or Compact FieldPoint, you should consider hosting the shared variable library on the real-time target. These devices have watchdog capabilities and typically contain hardware components controlling the critical pieces of an application, whereas most Windows or PC-based targets do not have these fail-safes. 
 
For more on watchdogs, look at the information outlined in Using Watchdog Hardware to Recover from Embedded Software Failures (Real-Time Module). 
 
You can host the shared variable library on the real-time target by following the steps detailed in the document How to Host Shared Variable Library on Real Time Target. This approach does not address the underlying issue but will function as a workaround as crashes in the SVE are often difficult to diagnose.

WAS THIS ARTICLE HELPFUL?

Not Helpful