Hello to all you brilliant people on the forums.
I am working on a project that involves a cRIO which will eventually be installed into a test cell with a PLC and a PC. The cRIO uses a TCPModbus Slave to allow single points of data to be communicated between itself and the PLC and/or PC. I also included a Network Stream to pass waveforms to a diagnostics application that will run on the PC. All of this works very well, so if it's not broke it needs more features, right?
I decided to also include Ethernet/IP communication to the cRIO. This would simply be another option for the PLC to pass data to/from the cRIO using explicit messaging. I created the modules and ran them on a test VI and all was well. After adding the Ethernet/IP modules to the main RT application the PLC returned a connection error. The Modbus communication was still working. After some head scratching I found that if I removed (not just diagram disable) the VI that included the Network Stream, the Ethernet/IP communication would work.
My question is, should Ethernet/IP and Network Streams coexist on the same target without issue, or was the issue I'm seeing expected? I would love to get your thoughts and thank you for your time.
LabVIEW 2018 (Software Platform Bundle)
NI-Industrial Communications for EtherNet/IP 18.0
NI-9068 cRIO
TCPModbus API is part of the DSC Module
Kind regards,
Josh