Hello,
I have some LabVIEW code that I am trying to integrate into VEE, and for the most part, I've been succesful after mimicing the procedure in the relevant example. However, I am running into major problems when I try to pass a value into a LabVIEW cluster. The cluster in question contains a string and a number, and so I tried to pass a record with the same structure. However, when I do so, I get a generic error pop up window "Agilent VEE has encountered a problem." When I pass this cluster in as an output instead of an input, I've found that VEE handles it properly and creates a record that has the same structure as the one I built earlier.
Does anybody have any insight as to why I can't pass a record into a LabVIEW cluster input?
Thanks for any and all help!
I have some LabVIEW code that I am trying to integrate into VEE, and for the most part, I've been succesful after mimicing the procedure in the relevant example. However, I am running into major problems when I try to pass a value into a LabVIEW cluster. The cluster in question contains a string and a number, and so I tried to pass a record with the same structure. However, when I do so, I get a generic error pop up window "Agilent VEE has encountered a problem." When I pass this cluster in as an output instead of an input, I've found that VEE handles it properly and creates a record that has the same structure as the one I built earlier.
Does anybody have any insight as to why I can't pass a record into a LabVIEW cluster input?
Thanks for any and all help!
Anyway, I don't think that will work directly as it is extremely likely that compound structures like records, waveforms and the like are going to be implemented differently in each language ( that doesn't just go for these two either - pick any other two languages like C++ and Visual Basic ). In that case you'll need to make some sort of adapter in both languages that converts whatever structure into 'native' elements ( real, text, integer ) to pass them across and then re-construct them on the other side. If you have one place passing data between the two you can integrate the converter into that code.
It could be a little tricky making it generic ( in VEE you may need to check for the data type before reconstructing a record, for example ).