NI-XNET Application Crashing if “Shared Clone Reentrant” Mode Is Enabled in LabVIEW

Updated Aug 31, 2023

Reported In

Hardware

  • NI-9860
  • cDAQ-9189

Issue Details

A LabVIEW application using NI-XNET hardware is crashing after a random period of execution, once the crash takes place, the hardware shows up in NI-MAX as disconnected or not available. A reboot of the chassis is required in order to re-establish communication with the affected hardware. 

Solution

If the XNET Read VI is called in a VI or SubVI with execution mode set to Shared clone reentrant execution the application might crash.

The current workaround is to change the execution mode of any VI or SubVI calling the XNET Read VI to Preallocated clone reentrant execution or Non-reentrant execution. 

Contact Technical Support if the application crashes after implementing these changes.

Related Links

Reentrancy: Allowing Simultaneous Calls to the Same SubVI

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.