10-04-2007 04:31 PM
10-04-2007 09:08 PM
10-04-2007 09:16 PM
10-05-2007 09:42 AM
Yes, this is a RT project with fieldpoint etc. It takes RT signals from the FP (which takes it from the motor tach). The VI remains broken as it cannot find the above-mentioned file.
This has been developed by my predecessor and I am left to deal with it. I am still trying to figure out his code. He has used local variables in ABUNDANCE!!! I am trying to refactor everything so that I can get rid of L-variables instances.
10-05-2007 10:18 AM
10-05-2007 10:27 AM
I believe that VI is part of the Real-Time Communication Wizard, which has an LLB that installs in the [LabVIEW]\project folder...I can't remember the name of the LLB off-hand.
-D
10-05-2007 11:00 AM
Thanks for that guys. Please jog your memory for the location of that file. that is the only thing that is holding me from building the exe.
Also, another quick question. Although all my VI's are in 7.1, can I buiild using 8.2 and still be able to save the build as a 7.1?
BK
10-05-2007 11:11 AM
Are you using LabVIEW 8.2? I think the RT Communication Wizard switched from being located in the [LabVIEW]\project folder in LabVIEW 7.x to the [LabVIEW]\resource\Framework\Providers\lvrealtime\RTCommWizard folder in LabVIEW 8.x. Also, I wouldn't be surprised if some of the VIs were renamed or removed. Perhaps the old version of your code was written in 7.x, and by moving to 8.x, the VIs the code linked to are no longer there?
As a general rule, your application should only use VIs in vi.lib or in your own code repository. Using internal LabVIEW VIs (like those found in the project or resource folders) can cause problems, since there's no guarantee those VIs will remain the same (and have the same name) with LabVIEW upgrades.
-D
10-05-2007 02:38 PM
I dont have lvrealtime in the providers folder!
I checked it out as you said.
10-05-2007 02:44 PM
The RT Communication Wizard may be a separate install...at this point we're getting out of the realm of my knowledge. You may want to try cross-posting to the LabVIEW Real-Time forum to see if they have any suggestions.
Good luck,
-D