CIN

[ep00]

Hi,

I have the LabVIEW 8.2.1 full version.

I am trying to control CCDs with that LabVIEW.

I have the LabVIEW driver with CIN(Code interface node) for taking a color picture with CCD.

When I tried to run this vi, they show the error like the following:

LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.

VI "ColorPicture.vi" was stopped at Code Interface Node "tnt.lsb" at a call to "ColorPicture.vi"

I stored all .lsb file and vi files in the same folder under the C: driver.

I cannot understand what this error happened.

I think that VI should be not depend on the path.

I'd like to know the solution.

[ClintM]

Hello,

Was this code previously written in an earlier version of LabVIEW and you are upgrading it or is it new code?  Have you tried following the CIN Code Resource Tutorial?  Do you get an error code when that error is generated?

If you aren't doing this in a project, you might consider adding all of these files to a project and running it from there.

Regards,

Clint M
National Instruments

[rolfk]

---

ep00 wrote:

Hi,

I have the LabVIEW 8.2.1 full version.

I am trying to control CCDs with that LabVIEW.

I have the LabVIEW driver with CIN(Code interface node) for taking a color picture with CCD.

When I tried to run this vi, they show the error like the following:

LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.

VI "ColorPicture.vi" was stopped at Code Interface Node "tnt.lsb" at a call to "ColorPicture.vi"

I stored all .lsb file and vi files in the same folder under the C: driver.

I cannot understand what this error happened.

I think that VI should be not depend on the path.

I'd like to know the solution.

---

Please let us know the answers to the questions Clint posed. Basically if the CIN was created with a much earlier version of LabVIEW than 8.2 the .lsb file could be two different types of files. There are .lsb files that are the actual CINs and they won't do anything helpful on disc as LabVIEW is not going to search for them in any way on its own. They need to be imported into the CIN node through the right click popup menu on that node.

Then there are external subroutines which are not supported to be created on LabVIEW 7 and higher. They will still run if created in earlier version but you can't create them with the LabVIEW cintools of more recent LabVIEW versions. Those subroutines have to reside on disc as external files and will be loaded by LabVIEW dynamically whenever needed.

But there is another story to this. LSB files (both CINs and subroutines) are compiled resources and as such created for a specific platform (Windows ix86, Linux ix86, Mac Classic 68K, Mac Classic PPC, Mac OSX PPC and MacOSX ix86). If you happen to have a CIN compiled for Linux ix86 you can try to load it into a CIN on a Windows machine 500 times and LabVIEW will continue to complain that it can't find the necessary code resource.

If that is your problem the only two solutions are either to run the VI on the original platform for which the CIN was created or using a supported C compiler and the C source code for the CIN, create a CIN resource for the platform you are trying to run it.

And BTW: I know you have this code and all already so it is not a good advice in this particular case but CIN's are old legacy technology and should be avoided for new developments. You can read more of history and details behind CIN's in my posts at My CIN articles on expressionflow.com

Rolf Kalbermatter

Message Edited by rolfk on 09-19-2007 09:42 AM

[ep00]

It's is written in an earlier version of LabVIEW.

Maybe it would be version 6.

I didn't get any error code, but error message was popped up.

Actually I didn't make this code myself.

It's provided from CCD company.

I asked the company to give me the original C source code, but they didn't.

I really appreciate all your help.

I think to recompile the C source code for the platform I am trying to run it is the besr way to solve the problem.

Unfortunately it's not possible.

I should find another way not by using CIN.

Anyway thank you very much!