cRIO Communications

[KMitch81]

We currently have several cRIO controllers working with LabView on workstations.  I would like to make data from the cRIO available to another controller via OPC, Modbus or Ethernet IP.  The new controller would be from a different vendor and would only require read access.  Is this possible or does it need to go through the LabView workstation?

[nanocyte]

CRIOs can (and probably should) run completely independent from the LabVIEW workstation. You just have to build an executable and mark it for startup. https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9mySAC&l=en-US

[KMitch81]

Thanks. Can the cRIO communicate simultaneously with LabView and Ethernet IP to a second destination?

[nanocyte]

The short answer is yes. I'm a little curious what you mean by Ethernet IP. Do you mean TCP/IP or would you be open to network streams and the like?

[KMitch81]

Ethernet IP network. Primarily to get data to other places, not for the cRIO to use. 

[pipipi0405]

There's Industrial Communications for Ethernet/IP driver for LabVIEW, but it was primarily developed to interact with Ackermann PLCs and only has limited features. It can be used with cRIOs but you should be careful and try with the Trial version before purchasing this driver.

[KMitch81]

Yes. That answered my questions. That you very much. Sorry for the slow response.