Network Streams between cRIO 2017 and Desktop 2019

[terickson]

I am working on system that has an HMI and cRIO application both developed in LabVIEW 2017.  Networks streams are used to communicate between the two.  I need to update the HMI but in LabVIEW 2019.  However, the network streams do not appear to work between the cRIO application in LabVIEW 2017 and the HMI application in LabVIEW 2019.

The originally built HMI EXE built in LabVIEW 2017 works.

Any thoughts?

[Bob_Schor]

If you were doing "pure TCP/IP", I could imagine that Host code running with LabVIEW 2019 that just sends TCP/IP packets to a Target running deployed LabVIEW 2017 code, with the only interaction between the two being via TCP/IP, should be OK (but I wouldn't be too surprised if it failed).  But if you are using Network Streams, that's an "internal" NI Protocol that might have slightly different "rules" and "procedures" that make connecting a Host 2019 Reader (or Writer) to a Target 2017 Writer (or Reader).  Your best (= most likely to succeed) bet would be to rebuild the Target code using LabVIEW 2019, or see if you can do what you need with TCP or UDP.

Bob Schor

[terickson]

I was able to confirm that both applications using network streams must be the same LabVIEW version.  I compiled the host application in LabVIEW 2017 and everything worked fine.