how to do you access the .lsb file an existing CIN uses

[futuramaar]

I have been trying to transfer VI's from Mac to PC. The subVI's they use contain CIN's. I can transfer the subVI's over to PC through the .llb file containing them however when I open them on PC they say the CIN has no code loaded. How do I find out what .lsb file the CINs origionally used so I can load it on PC? Or how can I at least access the code that was used to make the .lsb file so I can make another one?

[Dennis_Knutson]

If the C code was developed internally, you would have to track that down. With a CIN, you do not have to save the lsb file externally to the VI. After it's been compiled, you have the option to load the lsb and then it's part of the VI. The lsb file itself could be deleted. Even if you happen to find the lsb, you would almost certainly have to recompile it for windows.

What exactly is the function you are trying to transfer? Was this an internal custom VI, third-party VIs, VIs from NI? If you think they came from NI, then it must be a very old version. CINs have not been used in a long time, as far as I know.

[futuramaar]

The subVI's might be labview VI's they were from V5.1 I think. We are currently updating our control system.vi from 5.1 on mac to 7 on pc. The Subvi's are part of the AI Sample Channel.vi and AO Update Channel.vi The AI sample channel.vi has 6 subvi's containing CIN's (AI Buffer Config.vi, AI Clock Config.vi, AI Group Config.vi, AI Hardware Config, AI Parameter.vi, AI Single Scan.vi) The AO Update Channel has 4 subvi's containing CIN's (AO Buffer Config.vi, AO Group Config.vi, AO Hardware Config.vi, and AO Single Update.vi) If these are outdated Labview made subvi's is there a better way to use or access these subvi's in labview 7 as opposed to transfering them from V5.1?

[Dennis_Knutson]

These VIs do not require conversion. These VIs are part of the traditional DAQ driver and you need to have installed this driver fo your windows/LabVIEW 7. Only do a conversion of the VIs that are not part of the old LabVIEW distribution. Any of the VIs in the vi.lib folder are part of the distribution and should not be converted. If user VIs were save to vi.lib, then that was a major mistake by the person that originally wrote the code.

If these functions are included in an llb that you are trying to convert, that was also a major mistake made. No llb should include functions from vi.lib and you would have to remove them from the llb.