ni.com is currently experiencing issues.

Support teams are actively working on the resolution.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

XNET Driver Issue

I am using XNET driver 1.4.

 

My program loads the DBC file and reads all frames/signals out of DBC file. At the end of read dbc it closes the Xnet database close. 

 

In a sequence It starts the required frames and it changes required signal. It works fine for the first time using teststand.

 

But it never works for the second run until I close LabVIEW.

 

At the end of test, I normally close all sessions and stop all frames. Please let me know why?

0 Kudos
Message 1 of 2
(2,047 Views)

It sounds like there might be a reference handling problem, hence why the next test only runs once you have closed LabVIEW (this releases all references from memory).

 

Is it possible that you could post the code for me to take a look at? Without actually seeing the code, it could be difficult to put a finger on what is causing the problem.

 

-Nick-

Nick C | Software Project Manager - LabVIEW Real-Time | National Instruments
0 Kudos
Message 2 of 2
(2,031 Views)