XNET Start.vi delay

[ypi]

Hello,

I have a frame in Queued session which reads the interface and stops indefinedly for a specific trigger frame. When this frame arrives I start another session (Single point-frame) with some configured cyclic frames. The system works but there is a delay between the arrival of the frame and the start of the cyclic frames. (0001 is the trigger)

I tried to just stop the session and starting it again 18.5ms later but the delay is not consisten so somtimes the frames are sent the next trigger frame arrives which is not acceptable.

I tried also using a Output Stream Frame session but the delay is there and also way more inconsistent...

 

Is there any way to make this delay go away? or at least make it consistent so I can programmatically eliminate it? How long does it takes the XNET driver to start writing after I call the Start.vi? There is no more traffic in the bus at that moment so it is not a arbitration problem.

The snippet is just an example, the real code is running in a Custom device on a 8840e PXIe with PXIe-8510 QC with VeriStand.

Thanks!

Andrés

[ypi]

For anyone facing a similar problem:

I kinda got this under control by messuring how much time it took my interfaces to start sending the cyclic frames after y called the Start.vi. The messurmet was made with help of a Session input with Echo? == True

I calcularted how much time it took, then I calculated how earlier I needed to call the Start.vi.

Cheers!