DotNet Examples (Windows UD)
Print page
Export all
C# and VB .Net examples for the LabJackUD driver. Refer to the text file in the zip for more information.
File attachment:
LabJack
Measurement & Automation Simplified
The team at LabJack is driven to make measurement and automation simple and affordable. Located in Lakewood, Colorado, LabJack Corporation builds great hardware and software for industry, government, and education.
LabJack writes drivers for Windows, Linux, and Mac OS X, plus example code in dozens of languages.
Have a question or problem? LabJack engages in active customer support. You can find answers in the support area and FAQ, or contact us so we can help.
Comments
#1
Hi
I have a LJU3-HV which has been installed successfuly on a Windows Vista 64 machine (The test Control Panel utility can read and write to all inputs) but I'm having trouble with the .Net examples as neither the example VB nor the C versions will run in VS2010.
The error generated is: "Unable to load DLL labjackud.dll. The specified module could not be found". I ran a Windows search for "labjackud.dll" and it confirmed that the file doesn't exist on my system.
Any ideas? Please help!
Simon
#2
If the LJControlPanel works then LabJackUD.dll should be on the system. It would either be in C:\windows\system32 or C:\windows\SysWOW64.
Most likely with this error, the issue is building for the wrong version of the .dll. Since LJControlPanel works, that means that the 32-bit version of the .dll is likely in the SysWOW64 folder. 32-bit programs can then run and use this version of the .dll. Since the program is not finding it, it's likely that the program is a 64-bit program and looking for the 64-bit version in the System32 directory.
There are two fixes to this. The first (most common and easiest) is to change the build options for the project, and set the target architecture to x86, which will force a 32-bit application. This is often set to "any architecture" which will compile as 64-bit on 64-bit machines and 32-bit on 32-bit machines. That change should fix the problem.
The other fix is to place a copy of the 64-bit version of the .dll into the system32 directory. You can find information on doing that here.
#3
Hi Paul
Thank you so much for the reponse - "fix 1" sorted out the problem immediately - I can now get down to some serious fun!
Thanks again!
Simon
#4
AIN resolution in U6 C# examples updated December 27, 2010
I2C C# examples updated December 28, 2010
Minor revisions December 29, 2010