Configure a LabJack device

Connect a LabJack T4 or T7 to the Driver and configure it for tasks.

The Driver connects to LabJack T4 and T7 devices over USB, Ethernet, or Wi-Fi. It finds them with the LabJack LJM library. Before a task can use a device, you configure it. The T8 is not supported yet.

Prerequisites

Supported

WindowsmacOS

Not supported

LinuxNI Linux RTDocker

• Install the LJM library on the computer that runs the Driver, then restart the Driver.
• Connect the device to that computer by USB, or to the same network.

How the Driver finds devices

The Driver looks for LabJack devices every few seconds. A USB device shows in the devices toolbar within a few seconds. A device on the network can take about a minute.

• Name -> the model and the last four digits of the serial number, such as LJM_dtT7-8422.
• Location -> the connection, such as LJM_ctUSB or LJM_ctETHERNET.

The Console also shows the notification “New LJM_dtT7 connected”, with a Configure button.

Configure a device

for dev in client.devices.retrieve(makes=["LabJack"]):
    print(dev.key, dev.name, dev.model, dev.location)

for (const dev of await client.devices.retrieve({ makes: ["LabJack"] }))
  console.log(dev.key, dev.name, dev.model, dev.location);

Do not create LabJack devices in code. The Driver opens a device by its serial number, so only a device that the Driver found works in a task.

Troubleshooting

• The device does not show in the devices toolbar.

  Cause

  The Driver cannot load the LJM library, or it runs on Linux.

  Fix

  • LJM is not installed -> install the LJM library and restart the Driver.
  • The Driver runs on Linux -> LabJack devices do not work on Linux. Run the Driver on Windows or macOS.

  For more causes, see Troubleshoot hardware.

• A device matching the requested device parameters could not be found

  Cause

  Another program holds the device. A USB device works with one program at a time.

  Fix

  1. Close Kipling and other LabJack software.
  2. Start the task again.

• The device is temporarily unreachable. The Driver will keep trying to reach it.

  Cause

  The Driver lost the connection to the device. The task shows “Failed to read data” or “Failed to write commands”, with this text in the description.

  Fix

  Check the USB cable or the network. The task continues when the device comes back.

For other problems, see Troubleshoot hardware.