« Close

Datasheets and User Guides

App Notes

Software & Driver

 

3.7 - LJtest

LJtest runs a sequence of tests on the LabJack itself. Users will generally leave “Factory Test Fixture Installed” unselected and execute the tests with nothing connected to the LabJack (except the USB of course).

Note that the U12 is not the “Test Fixture” for the purposes of this program. Rather, the U12 is the device under test (DUT) and might connect to a test fixture which tests the U12.

The “Continuous” option causes the test program to keep running over-and-over.

LJtest is installed as part of the normal U12 software package. It can typically be run by doing Start => Programs => LabJack U12 Legacy => Legacy U12 Samples => LJtest.


Figure 3.8-1. LJtest

If all tests fail except “OS Version” and “Driver Version”, it generally indicates LJtest does not detect a LabJack U12 at all. Check for proper blinking of status LED upon power-up, and if using Windows 98 SE check out the related file (Win98sehid.zip) from the downloads page at labjack.com.

If “Find LabJack” is the only failure, it is often because more than 1 LabJack U12 is connected.

“Check USB” performs some basic tests to detect any obvious problems with the Universal Serial Bus. Proper LabJack U12 communication is required for this test.

“Local ID” will show a yellow warning if the Local ID has been changed from the factory default of 0.

Failures from “Test RAM” or any of the “AI …” tests could indicate damage to the unit. Make sure there are no connections to the LabJack U12 (except for the USB cable), and contact LabJack support if the failures continue. Yellow warnings on any of the “AI …” tests (make sure nothing is connected to the AI channels) could indicate that a self-calibration needs to be performed (see below).

A yellow warning from the “Cal Constants” test is usually because the constants have all been set to zero. Most often this is due to selecting “Test Fixture Installed” and running LJtest without the proper connections. Follow the below procedure to correct this issue.

To write new calibration data, a self-calibration should be performed using LJtest and 12 small (1.5” will work) jumper wires:

  1. Make the following initial connections:
    • AI0 <=> AI2 <=> AI4 <=> AI6 <=> +5V
    • AI1 <=> AI3 <=> AI5 <=> AI7 <=> +5V
    • IO0 <=> IO1
    • IO2 <=> AO0
    • IO3 <=> AO1
    • CNT <=> STB
  2. Start LJtest and select “Factory Test Fixture Installed” and “Prompt During Cal”, and then click on the “Run” button.
  3. LJtest will step through various tests and then prompt to connect GND to all 8 AI channels (AI6<=>GND and AI7<=>GND), then to connect CAL to the even channels (AI6<=>CAL), then to connect CAL to all 8 AI channels (AI7<=>CAL), and finally to connect GND to the even channels (AI6<=>GND).
  4. When finished, remove all wires and unplug the USB cable. Reconnect the USB cable and the new calibration constants will be loaded at power-up. Run LJtest again with “Test Fixture Installed” unselected, to make sure the unit passes the normal self-test.

3 comments

I'm getting a failed Find LabJack test when all other computers are not having this issue. There is only one LabJack connected to the computer and I have tried uninstalling all LabJack software and re-installing it. Above it says "If “Find LabJack” is the only failure, it is often because more than 1 LabJack U12 is connected." Have you encountered any other times when it failed?

Is the LED behavior different than what you see on working computers?  What operating system is it?  See the U12 Hardware Troubleshooting page.

Make sure not other software is running that might be talking to the U12.  Perhaps reboot your PC to make sure.

See if the entries in Windows Device Manager look correct.  Under Human Interface Devices you should see 2 entries appear/disappear when you connect/disconnect.  One entry for USB Input Device and one entry for HID-compliant device.  In the HID entry you can look at Details => Hardware Ids and see VID_0CD5 and PID_0001.

What do you normally use for software?  Do you use or have available any programming languages to run our examples?