U12 Setup V1.21
This is the legacy software installation for the LabJack U12. The directory and file structure has been changed since V1.17, so LabJack U12 software V1.17 or lower should be uninstalled first. If you are not sure what version you currently have installed, run LJtest and see if it reports driver version 1.17 or lower. LabJackUD does not support the U12, so this U12 specific driver should still be used. This install includes drivers, documentation, LabVIEW examples only, and sample applications.
Supports Windows 98SE/ME/2000/XP/Vista/7. This installer will work on 32-bit or 64-bit Windows. It contains the drivers for 32-bit applications run on either 32-bit or 64-bit Windows. If you are using 64-bit applications on 64-bit Windows, then after using the installer above you need to get the new 64-bit U12 drivers (unzip and copy to \windows\system32).
Also provided is an updated version (1.03) of the LJSHTmulti program that supports data logging. This version is newer than the LJSHTmulti (version 1.01) installed with U12 Setup V 1.21.
Also provided for OEMs and developers is a zip archive with just the DLL and OCX files.
Also provided is V1.13 of LJlogger. This just fixes screen alignment issues on Vista and Windows 7 and is only recommended for those operating systems. Note that FTP/HTTP/Email features had to be removed from this version. The attached archive is simply the exe file. You must replace the current V1.12 exe with this new exe.
All Support Guides
Search
Shopping Cart
Testimonials
-
I don't know of many other companies that provide such excellent service. I wouldn't hesitate to recommend your product to anyone.
—Richard, Milwaukee School of Engineering

Comments
#1
For many years we have been using U12’s and more recently U3’s and U6’s attached to a PC running XP. We have an application ( https://www.unc.edu/~ogmonbur/ms/ms-docs/ms-infoP0.html ) using three U12’s; two of which are under VB.NET control and the other under LabView. It works very well and we want to thank LabJack for this.We are now trying to make the system work under WINDOWS 7 but with very little success (if any). The problem seems to be related to finding the hardware (both U12 and U3 - have not tried U6 as yet).Using LabJack Legacy LJlogger with two U12’s connected (https://www.unc.edu/~ogmonbur/zzTemp/Select_a_U12.png ) presents no problem under XP: https://www.unc.edu/~ogmonbur/zzTemp/29546U12.png and https://www.unc.edu/~ogmonbur/zzTemp/56245U12.pngBut under WINDOWS 7 no matter which one we select to test, the software always runs the first U12. We are hoping that this problem is related to ours and that fixing it may fix the other.
#2
So when you run LJlogger with your 2 U12s connected, no matter which one you select it always uses the same one? I looks like both have LocalID=7, so have you tried giving them different LocalIDs using LJconfig? I suggest continuing this discussion by posting on our forum or sending email to support@labjack.com.
#3
Re-configuring worked, thanks. I did not realize the local ID was kept in the U12. That explains why they came up with the same local ID on both computers, but it does not explain why the XP did not have any problem differentiating between the two U12's while the WINDOWS 7 computer did. No problem though. Thanks again.
#4
Hello,
I'm having an issue with labview. The error message says that the "serial port is not configured." Since my instruments are connected to Labjack, does that mean I need to download the labjack drivers, or is there some other issue here? The reason I ask this is because my computer crashed along with my previous information. Thanks.
#5
Where are you getting that error, as our devices do not use the serial port? If it is coming from one of our examples, what is the errorcode number?
See the general information about using the U12 in LabVIEW.
#6
There is an error code number, from LabVIEW: Error-1073807343, and it gives as a possible reason this error: "VISA: Insufficient location info or the device or resource is not present in the system."
#7
That is a LabVIEW errorcode not a LabJack errorcode. I would assume it is coming from an NI VI not a LabJack VI? Perhaps you have a VISA VI that is talking to some serial device?
Is this coming from one of our examples? Did you look at the general information about using the U12 in LabVIEW?
#8
Greetings,
Just downloaded the evaluation (30 days) version of Labview 2010 SP1 and tried http://labjack.com/sites/default/files/software/2009/08/U12SetupV121.exe (the above link).
Basic Eanalogin, eanalogOut, edi, edo works, did not test the other VIs.
Will be giving this version of Labview with labjack U12 a good test this autumn semester (A2011) .
Running Windows 7 (32 bits).
Cheers.
#9
On Windows 7 the windows of the legacy software have some formatting problems resulting in sometimes poorly usable software.
On the good side - the connection via the device server (TCP/IP) works!
#10
We are looking into rebuilding the VIs.
#11
any news in rebuilding? It is risky to use the legacy logger software, because of the formatting problems, having erroneously aligned rows...
#12
Try V1.13 now posted above, although the FTP/HTTP/Email features had to be removed if you were using those.
#13
Lack of a straight down load of labjackuw.dll ?
No I have had to download the complete setup.exe file and do a test install to make sure Labveiw is not installed on my machine.
#14
The installer just installs a LabVIEW run-time engine, not actually LabVIEW. It also installs some example applications.
I have posted a zip above with just the DLL and OCX.