communicating cRIO with PC

[carsale]

I have a comlpex control system. one of the subsystem is cRIO 9014 and another is NI6071E DAQ card. while the cRIO run a standalone programme to control some devices some information of the cRIO needs to be continuousely read by the NI6071E application programme. which mehtod (RS232 or ethernet)  is it better for this purpose?  how fast of the speed? are there some examples of both methods available? many thanks!

Carl

[StevenA]

I would recommend using ethernet.  Take a look at the simple TCP messaging component, or use shared variables.  You can so event based communication with the TCP messaging component and it is very efficient.  Shared variables are very easy and for many apps work very well.  Not quite as efficient as TCP but you can't beat the simplicity.

[carsale]

Thanks so much! Steve, I will try.

Carl

[StevenA]

Carl,

Here is another link that you might find useful.  This is a very powerful method of communication with your RT.  It is an example of an command base architecture based on the STM tool.

[carsale]

really appreciate your help!

[rex1030]

I recommend shared variables over ethernet. They are fast and easy to use.

[carsale]

Thanks, rex1030 and SteveA!

I am not sure if I use ethernet or shared variables the speed is high enough? I mean, I need to read data frequently (around 15 times / second) from cRIO. Do you think which is better, ethernet or shared variables? by the way, are there some examples for shared variables? Many thanks! 

[StevenA]

---

carsale wrote:

Thanks, rex1030 and SteveA!

I am not sure if I use ethernet or shared variables the speed is high enough? I mean, I need to read data frequently (around 15 times / second) from cRIO. Do you think which is better, ethernet or shared variables? by the way, are there some examples for shared variables? Many thanks! 

---

shared variables would be plenty fast for that rate.  Ethernet (using the STM component) will take less resources however.

Here is a link on shared variables

[carsale]

Thanks, SteveA!