Problem loading .lsb into CIN

[Raymond Mouthaan]

Hello,

Now I'm able to create a .lsb file with CIN custom step.vi from
http://www.jyestudio.com/lview.shtml, I tried to load the .lsb into CIN.
This didn't work.

I loaded the file, but LW still comes with an error that the code (from lsb)
is not loaded.
Strangs thing is that the dll file which I used for creating the .lsb works
correctly with Labview's "Call Library Function Node. For this test I just
took a example from Labview and used the .c file to create the .dll, then I
created the .lsb with CIN custom step.vi.

So the .dll works, but the .lsb does not.

I someone tell me why?

Some example code with .c, .dll and .lsb files is welcome.

Regards,

Ray

[David Duffey]

Do you have two versions of LabVIEW on your system, is it possible that the third party VI you are using is calling the incorrect version?

I've used the "How to build a .lsb" tutorial several times and had success, it can be found at:
http://zone.ni.com/devzone/conceptd.nsf/webmain/31DAB548C369B2C6862567C8006D8FC9?opendocument&node=DZ52045_US

Since you have a working dll, you could run the lvsbutil by hand to create the .lsb yourself.

Here is the command line form:

lvsbutil -d

You can reduce the introduction of typing errors and mis-quoting by following these steps:
Go to the start button -> click run -> type cmd

Browse to the directory that has lvsbutil.exe (in the cintools directo
ry under labview), drag the lvsbutil.exe onto the cmd window. This will correctly quote the executable

Browse to the folder that holds your dll, this is usually in "Debug" of your project's directory, verify that a dll has been created there

In the cmd window, type a space, and then "projectname" and then type a space -d space

Drag the folder that contains the dll onto the cmd window, and hit enter

You should see LabVIEW resource file, type 'CIN ', name 'sharedcin.lsb', created properly.

The lsb file will be built in the same directory as the DLL.

[Marco Tedaldi]

Raymond Mouthaan wrote:

> I loaded the file, but LW still comes with an error that the code (from lsb)
> is not loaded.

I've got the really same Problem her. But not with self-compiled .lsbs.
I've got some third-party vis that should allow access to an Axon
Digidata 1200 Card. The Problem is, that if I want to load the Vi's, i
recieve a lot of errors. All about the same thing. That a CIN has no
code loaded.
I've got the source-code of the functions, so I could try to recompile
them. Isn't it possible to use lsbs, that are created for LabView 5, in
LabView 6i? Or is there another Problem?

Thanx David Duffey for your Answer to Raymonds questin. Just letting
lvsbutil.exe run "over" the Files i have, resultet in a new .lsb-file,
which had the exact same s
ize as the old one, und didn't wored either .-(

Would recompile help?
What other reasons are possible, that the CINs can't "hold" the code?
Why isn't there any error-message, when i choose the file?

bye

Marco

[TROUBLESHOOTING]

Hi

I gone through all steps creating manual .lsb file and all replies listed in this discussion forum

still I am not getting it done.

Can I get any help for what exactly I must do to make it run?

I think In Visual C++ project settings something is wrong as for me its creating erroe as

Linking...
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
'"D:\cin\add\.\Debug"' is not recognized as an internal or external command,
operable program or batch file.
Error executing c:\windows\system32\cmd.exe.

add.dll - 1 error(s), 0 warning(s)
 but if I didnt give path in custom build tab in command line it causes 0 errors and .lsb created cant be loaded in labview

so

I guess problem is in project setting

please help me coming out of this Error I want to see my code running properly with CIN