How to select the target when migration to LabVIEW

[waldemar.hersacher]

I'm migrating from VBAI 3.0.1 to LabVIEW 8.5. The script will read an image file instead of grabbing from a camera. The migrated LabVIEW VI will get part of a larger LV application which will run on a WinXP OS.

The inspection in VBAI is working fine and is loading the image from the right location.

After migration to LabVIEW the image is not found. I can see that the path is correct in the "Inspect Setup-Cleanup.vi" as parameter for the "Simulate Acquisition" step. Debugging into the code I found that the file will be read by a VI named "IVB Simul IMAQ Setup (for RT).vi". This VI checks the path for location on a C: drive. In my case the image is located on the 😧 drive and the VI is changing the path to an not existing folder.

How can I tell during migration that my target is not a RT system but a Windows system?

I expected to find a VI named "IVB Simul IMAQ Setup (for Win).vi" in the VBAI\LV\subVIs folder but it seems it does not exist.

Changing the check from C: to 😧 and running the migrated inspection it works fine.

Message Edited by waldemar.hersacher on 03-05-2008 04:34 PM

[Ken_Tobler]

Hello!

The problem is coming from the VI IVB Simul IMAQ Setup.vi which doesn't recognize the images coming from other places as C:
In VBAI 3.5 the problem is resolved.

As workaround you should change a constant in the IVB Simul IMAQ Setup so that it can manage images from other places as C.
As attachement the changement which has to be done.

Best regards
Ken

[waldemar.hersacher]

Dear Ken,

I have found the same location by myself and changed the "C" to "D" in the other case.

My problem is that I have to do this each time I migrate the inspection. Even when I document this with the project in the case one of my colleagues has to work on the project he may forget it.

Changing to 3.5 would only be a solution if the update is for free. The license will be shifted to our customer and I don't think he will buy the update.