10-20-2010 03:12 PM
Hi -- I am attempting to run a Labview package provided by a hardware vendor for control of an RS232 device. I am running Windows 7 64bit / Labview 9 Full Dev. System. The code was developed for Labview ~7. When I attempt to run the code, I obtain the following error message:
"Error1 occurred at Config Data Registry.vi [get section]: invalid object 817889286
Possible reasons:
Labview: An input parameter is invalid.
or
NI488: Command requires GPIB Controller to be Controller in Charge."
I can't find this exact error on the forums, although I did find posts talking about Config Data Registry.vi (here and here, for example). I tracked down the error to the fact that the shift registers in Config Data Registry.vi always seem to be empty (vi attached), and the programs that call this vi are always running the "get section" frame of the device that fails unless the shift register was initialized in a previous runs. This seems like it might be a bug in the vendor's software, but it works for them in Labview 7 -- which certainly makes it seem like a legacy-compatibility issue.
Any help is appreciated, but I was particularly curious:
1) Is it clear why running this in labview 9 (rather than 7) would have broken the code? if so, can anyone suggest a fix?
2) Is this vi a core component of labview? It is included in the vi library the company provided, but the two links I posted above gave me conflicting ideas about this. I can't find any other versions of it on my computer, though, which made me think that it is either not a part of labview 9, or it is buried in a library that windows can't search.
Many thanks! Apologies if this is too application specific. I am trying to track down a copy of labview 7 to see if the program works in that environment, but until then I thought I'd ask the forum.
10-21-2010 11:17 AM
Hi mw13,
I opened the attached VI but I am missing a number of ctl files in order to be able to run it. Could you upload those as well?
Also, you mentioned that you only run the "get section" case in the VI. It appears that the VI would need other cases to be run first in order to set the reference, data, etc.
Would you be able to post the calling VI, or explain the goal of calling VI?
Also, have you been able to run the VI in LabVIEW 7 yet?
Thanks!
10-22-2010 09:06 AM
Hi Tanya -- thank you for the quick reply. I am not in the lab today, but I should be able to track down a copy of labview 7 over the weekend to determine for sure whether it is a compatibility issue. I will also upload the entire vi library on Monday. Many thanks for your attention!
09-13-2011 01:56 PM
Hello,
I recived this error while using stellarview spectrometer, It was solved by updating the sw.ini file.