Real-Time Measurement and Control

cancel
Showing results for 
Search instead for 
Did you mean: 

Faster than 2000Hz / TCP takes too long

1. How can we get faster than 500µs (2000Hz) on an PXI RT-8145 System? 502µs,501µs works fine, but 500 or lower the System doesnt respond. We loose connection to the RT System, also the RT-System Manager doesn´t respond. It doesn´t make any difference which VI we use. With 501µs we have an CPU usage about 91%.

2. If our program start´s, it takes always 1.24min to connect over TCP/IP. We tried all timing an loop-rates, but it´s always the same time.

Message Edited by prol on 04-11-2005 07:58 AM

0 Kudos
Message 1 of 3
(3,291 Views)
Could you describe in a bit more detail your application, including the code running in your host aplication and the code running in LV RT on the 8145 controller.

What type of I/O operations are your performing?

I assume you want to communicate between the host and LV RT application at 2000 Hz or faster? Why do you need these fast loop rates in your communication? What is the overall purpose of the application? In general TCP/IP is not well suited for fast loop rates, i.e. sending small packets back and forth at high rates. it is more designed for streaming data, sedning larger packets at high data rates in one direction. It sounds like you may be trying to setup a closed loop controller across Ethernet which will have a maximum looop rate around the rates you are describing.

On your second question, please describe what you mean by 'program starts'. What is the sequence of operation on the host and RT system? Do you reboot or start either of these two systems at this time? How is you Ethernet configured? Specifically how are IP addresses assigned to the two systems? Do you have a DHCP server on the network or are the IP addresses statically assigned? If neither is true, Windows will take about a minute to a minute and half to assign its own IP addresses.
authored by
Christian L, CLA
Systems Engineering Manager - Automotive and Transportation
NI - Austin, TX


  
0 Kudos
Message 2 of 3
(3,268 Views)
Sorry for my bad formulation.

1. We have a TCL (with analog/digital DAQ) and used the RT-Comm.Wizard sending the analog values over TCP. The TCL runs about 500µs and the NPL/Host at 50ms.
But this problem is not only with this one TCL.
We have tried a single TCL with no function inside and no TCP communication. With 501µs the RT-System manager shows 16% CPU usage, with 500µs the PXI system doesnt respond.

2. When we download and start the NPL and TCL on the PXI-System, is takes 1.24min until the Host receives data.
We use static IP-adresses (192.168.0.1/2 and the same
subnet). A switch is between the two systems.
0 Kudos
Message 3 of 3
(3,262 Views)