Best way to move date between LabVIEW 7.1 and 2010

[paris1_]

We have a large LabVIEW based control and data acquisition system that for reasons beyond the scope of this post is at and needs to stay at LabVIEW version 7.1 for the forseeable future...  We are soon to add a camera diagnostic to this system that, again for reasons beyond the scope of this post, needs to be written in LabVIEW 2010...  The 2010 piece of code will run and need to receive some information such as shot number, when to trigger, etc. from the 7.1 side of the system...  Then after a shot has occurred and a camera image has been acquired, the 2010 code will do some on the fly processing of this image and within a few seconds will need to send back some results data to the 7.1 side... 

The 7.1 code uses a tag engine approach to sharing data among different codes running on different machines...  I think now that more modern versions of LabVIEW use a shared variable approach...  But I need to communicate as I've described above between the two versions, 7.1 and 2010 (or it could be 2011 if that would offer some advantage)... 

I'm new at this moving of data between versions like this so if something could offer some advice, especially if there is some tutorial information on this topic, that would be much appreciated...  Thanks in advance for any help that you might be able to offer...  thanks...  bob...

[GuenterMueller]

A low-level approach would be using TCP to communicate between your LabVIEW applications. This will definitely fullfil your demands but will introduce a couple of work that needs to be done.

The best starter would be having a look at the TCP examples that ship with LabVIEW.

[rolfk]

It really depends if your tag engine like communication approach is a home brown solution or something like the LabVIEW DSC engine. If homebrown and well written you should be able to reuse the client library part of it in newer LabVIEW versions without to many hassles. If it is LabVIEW DSC it may be a bit more complicated since the only means to share DSC tags in version 7.1 was as far as I can remember their proprietary TCP/IP tag interface, which was replaced in newer versions with he shared variable engine.