Save for pervious

[ALSPI]

I have a Vi.Lib that was created in 6.0.2, given to customer. We upgraded to 6.1 I made changes to vi and saved for 6.0, I had a warnings file come up. I selected OK. When I open the vi in 6.0 I have several vi's that does not work. Can you help me with this?

[Zvezdana S.]

The warnings you are getting mean that you cannot save VIs from the vi.lib for the previous version of LabVIEW. This is to prevent possible corrupting of the vi.lib VIs (VIs that show up on your palette) each time you use Save With Options.
Each VI you develop with VIs from the palette, will link to those VIs in the vi.lib. When you save the VI for previous version, it will try to link to the same VIs in the vi.lib of that other installation/version of LabVIEW. If the VIs do not exist in that version, or have different connector pane, the VI will not work.
Not all of the VIs in the warning list will be different in LabVIEW 6.0. You should check which VI doesn't work when you open your VI in LabVIEW 6.0, and try to make necessary changes. If the vi.lib used does
not exist in LabVIEW 6.0, you will have to use some other VI on the block diagram.

Zvezdana S.
National Instruments

[ALSPI]

Thank you, this makes sense. My problems seem to be with the serial port, the Bytes at Serial Port vi is passing a 0 not the serial number so it just keeps repeating waiting on data. I deleted this vi and replaced it with the one in the 6.0.2 palette but it didn't help.

[Zvezdana S.]

This now seems like a problem with the serial communication. The problem appears to be with the Bytes at Serial Port VI, but it is probably caused by failed initialization or response from the instrument.
You may now want to post this question on the GPIB/Serial developer exchange forum to troubleshoot why reading from the serial port failed.

Zvezdana S.