07-09-2010 10:57 AM
I upgraded a VI from Labview 7.1 to 8.6 which includes Publish Data VI on a new computer
I run the VI, no errors, since I want to read this point from the host computer using data socket I went to MAX to add the data point that it is published, MAX does not find any data points
So I tried to test the publish VI in a simple test VI which includes only the publish VI but I am getting error code -34117.
I am using fieldpoint CFP-2220 and Labview 8.6
Any suggestions why the publish data vi is not working even though it is not returning any errors why I am getting error -34117?.
is there any difference on how the publish data vi and data socket works in labview 8.6 vs. labview 7.1
Thanks.
Solved! Go to Solution.
07-09-2010 02:40 PM
I was missing the DataSocket for LabView Real-time software on the fieldpoint, so I installed it, I am not getting any errors now, but I still can not read or write to the data point.
and it still does not show up in MAX after I run the publish data vi the first time.
any suggestion to what I am still missing?
Thanks.
07-15-2010 05:15 PM
Hi j_sd,
Are you following the instructions laid out in the Publish Data VI Help article?
You must run any VI that contains the Publish Data VI at least once before adding the data items from the VI to Measurement & Automation Explorer (MAX).
To add a data item from the Publish Data VI to MAX, complete the following steps.
The data published by this VI can be read or written to over a network by subscribing to the block and item names, using the DataSocket Read or DataSocket Write VIs. The value of an item may also be read or changed on the local machine where it was created by using this VI and passing in the same block and item name.
Aaron P
National Instruments
Applications Engineer
07-19-2010 09:44 AM
Thanks for the reply, I was following the instructions but it did not work.
now I got it resolved.
It was a software version mismatch or some software was corrupted. what I did was uninstalling all the softwares on the field point and reinstalling them, which fixed the problem.