Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

NI-PCI 8431

Solved!
Go to solution

Thanks

0 Kudos
Message 11 of 19
(3,513 Views)

Hi,

Can  help me  a Synchronous VISA Function ?

What do you  think?

Thanks.

0 Kudos
Message 12 of 19
(3,501 Views)
No, that has nothing at all to do with your issue.

What sort of testing are you doing that the time between writes is so critical?
0 Kudos
Message 13 of 19
(3,495 Views)

My application must response to every command (16 bytes frame) with frequency 200Hz without  skipping of command streem.

0 Kudos
Message 14 of 19
(3,490 Views)

If you have that tight of a timing requirement, then you really should go to an RT system and/or FPGA.  Even then, it will be pretty close, even with 115.2kbaud (10 bits/byte*16bytes/155200 = 1.4ms, 200Hz = 5ms).



There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 15 of 19
(3,487 Views)
Your application that is receiving the data must respond in a deterministic manner? Then your LabVIEW code should be the same.
0 Kudos
Message 16 of 19
(3,484 Views)

What do u mean "the same"?

I have to check my application for stream of command with freq. 200Hz(the freq. have to be constant, no gaps) and I have to response to each 200 Hz command.

I really must use RT system...

0 Kudos
Message 17 of 19
(3,469 Views)

I think Dennis_Knutson's point is that if your application has tight timing requirements, your software must be deterministic, and therefore requires a RT operating system.  The inherent jitter introduced by a non-RTOS such as Windows will not allow you to achieve the strict timing requirements your application seems to have.

 

If you must receive and respond to commands at 200 Hz without jitter, you really should use an RT system.

Cody A.
Message 18 of 19
(3,451 Views)
Whatever sort of widget you have connected to the serial port would appear to be designed for a non-windows environment with the custom baud rate and tight timing requirements. If you don't think that requires an rtos at the other end, you have completely misunderstood or misrepresented the widget.

There have been enough comments on the need for an rtos and the thread has been marked as solved.
Message 19 of 19
(3,446 Views)