NI-VISA Error 0xBFFF00A7 From Real-Time Target

Issue Details

• I am using NI-VISA to establish serial communication on a cRIO. My cRIO periodically hangs or crashes into an unrecoverable state. When this happens, NI Measurement & Automation Explorer (MAX) reports error 0xBFFF00A7 and my LabVIEW code reports error -1073807193. How can I fix this?
• I received the following error from my real-time target in LabVIEW or  NI MAX: 

 

Solution

• The remote machine name may be incorrectly specified (either the name was misspelled or the wrong IP address was typed in).
• The remote machine may not be turned on.
• The VISA server has not been started on the remote machine.
• The VISA server was started but is either suspended or is no longer running on the remote machine.
• Either the local machine or the remote machine is not connected to the network.
• There is a network configuration problem, such as an improperly assigned IP address, an incorrectly configured routing table, or a firewall between the local and remote machine.

• Ensure that you have all the correct drivers installed.
• Using the Real-Time Software Wizard, remove and reinstall the NI-VISA driver on the controller.
• Reset the Controller's IP address.
• Check if you have multiple network cards on your computer. If you do, make sure that the correct ethernet adapter is being used for your controller as detailed in How do I Connect to Ethernet Targets with Multiple Network Cards in the Host?
• If NI-VISA is used to open and close communication ports from LabVIEW, ensure that:
  • The port is opened and closed as few times as possible.
  • Resource handles are passed around loops with a Shift Register, and open/close the port(s) outside of the loop.
• If this error occurs with a CompactRIO (cRIO) controller:
  • Verify that the cRIO has enough storage space on it. This can be checked from the System Settings tab of NI MAX as described in Monitoring CPU and Memory Usage on Real-Time Embedded Targets.
  • Ensure that the cRIO's CPU usage does not exceed 75%. If the CPU usage is greater than this, refer to Recommended CPU Usage for Real-Time Targets for mitigation steps.