LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

driver dl1540

Solved!
Go to solution

Dear FonsB,

 

Dis removing the driver, repair of CVI and reinstalling the instrument driver have any result?

 

Best regards,

Martijn S
Applications Engineer
NI Netherlands
0 Kudos
Message 11 of 22
(1,239 Views)

Hi Martijn,

 

I did remove the driver and reinstalled it. Still no functional executable. What do you mean by repairing CVI?

 

BR FonzB

0 Kudos
Message 12 of 22
(1,235 Views)

Hi FonzB,

I meant Labwindows CVI; please try to repair it and install the driver again.

 

Best regards,

Martijn S
Applications Engineer
NI Netherlands
0 Kudos
Message 13 of 22
(1,224 Views)

Hi Martijn,

I understood that you meant LabWindowsCVI, but I don't understand what I should repair on it. LW 8.1 is working fine for me. For this program there are no compile errors, only link errors with the ykdl15xx driver so I cannot create a stand alone executable to run the program.

 

 1 Project link error
       Undefined symbol 'ykdl15xx_Initialize' referenced in "Test_yoko.c".

 

Are there some settings, environmental or build options to be set other than the ones I always use?

 

BR, FonzB

 


0 Kudos
Message 14 of 22
(1,221 Views)

Did you add the driver's .fp file to your project? If the project doesn't include it, and you didn't explicitly load the driver yourself, then the link error you're seeing makes sense.

 

Luis

0 Kudos
Message 15 of 22
(1,209 Views)

Hi Luis,

 

I added the .fp to the project like "Edit_ Add files to the project_Instrument(*.fp)_ykdl15xx.fp" The search path is then: C:\VXIPNP\WinNT\ykdl15xx.

I think because there is no sourcefile  (ykdl15cc.c) the reason of the Link error.

 

When I try an other driver like Tkdpo2k3k4.fp, which has also no C-source file, I get the same link error.

The Tkdpo2k.fp driver who has a C-source file gives no problem.

 

BR,

FonzB

0 Kudos
Message 16 of 22
(1,198 Views)

Not all drivers have .c files. But if they don't, they must have a .lib file which implements the functionality of the driver. Are you sure that there isn't some lib file for this driver in the C:\VXIPNP\WinNT\lib\msc folder?

 

Luis

0 Kudos
Message 17 of 22
(1,193 Views)

Hi Luis,

 

The ykdl15xx.lib is there in the C:\VXIPNP\WinNT\lib\msc folder.

 

Fonzb

0 Kudos
Message 18 of 22
(1,185 Views)

If you have the .lib file, then you shouldn't need to also have the .c file. Try this:

 

In CVI, select the Instrument>>Edit menu item, then highlight this instrument driver on the list and press the Show Info button. In the ensuing info box, the .lib file should appear as the program file of the driver. If it doesn't, then close the info box, press the Reattach Program button, and then check the program file again. Let me know what happens.

 

If the .lib file is already the program file for the instrument driver and you are still seeing link errors, then we'll have to look at the specific link errors, in the case the .lib file is somehow missing the implementation of some of the functions. Are you seeing a link error for every single function that you call from this instrument driver?

 

Luis

0 Kudos
Message 19 of 22
(1,175 Views)

Hi Luis,

In infobox the program file was not there, showing (none). When I close the the infobox and press the Reattach Program button, the message is: "No program file found for instrument Yokogawa DL1500 Series"

 

After reading this help:

 

"Reattach Program—LabWindows/CVI detaches the current instrument driver program file, if any, from the .fp file. LabWindows/CVI then reloads a program file using the rules outlined in Precedence Rules for Loading the Instrument Driver Program File."

 

I changed the Compatibility mode from Borland C/C++ to Visual C/C++, restarted my project and ran the program again. Now I have no more Link errors.

 

When I move the ykdl15xx.lib file to the Bc directory (I changed the Compatibility mode back to Borland C/C++ mode) and I Reattach the program,  the infobox shows the path to te -.lib file but the checkbox is not checked.

 

I see Link errors for every single function I call from the instrument.

 

 

0 Kudos
Message 20 of 22
(1,163 Views)