Why XNET Stop Is Not Stopping the Sending of LIN Scheduler

Updated Mar 28, 2025

Reported In

Software

  • LabVIEW

Driver

  • NI-XNET

Issue Details

I place the XNET Stop.vi for interface mode in my program before XNET Read.vi or XNET Write.vi. However I notice the LIN scheduler still started and sent in the bus when the program execute, why?

 

Solution

There is property called AutoStart? in both XNET Write and XNET Read. When these API first time call, it will auto start the session even there is XNET Stop in front. If you are using XNET Write, you may turn off the AutoStart? property to achieve the stop behavior. However, take note that the same property is not allow to turn off if using in XNET Read. It is expected behavior is you are using XNET Read after the XNET Stop.

Taking below code as an example, you can turn off the AutoStart? property so that the XNET Write will not auto start when first time executing to avoid sending the scheduler.