Skip to Navigation

Kipling

Summary

The latest software for the T7/T7-Pro is called Kipling. It is a cross-platform program designed to make using LJM hardware straightforward and convenient. It provides basic test, configuration, and firmware upgrade functionality in a graphical interface. This program also aims to make using the T7's advanced features more straight forward and easier to understand.

Installation

Windows details
Windows Installer 79.09 MB 2015-03-10 21:25
Latest Version
3.0.9
Kipling Notes

Newer updates to Kipling can be installed through the program, if these updates don't work re-install Kipling through this main installer link.
Kipling itself can be downloaded separately as a .zip file however this isn't recommended for most users. Windows (Kipling Only)

Windows Installer Notes

This is the installation package for Windows for the U3, U6, UE9, T7 and Digit. It supports both 32-bit and 64-bit versions of Windows XP, Windows Vista, Windows 7 and Windows 8. All high-level functions within the LJM library will be available through this installation.
This installation includes the driver, libraries, documentation, and utility applications listed below

Utility Applications
  • LJControlPanel 2.32 - Simple configuration and testing utility for the U3/U6/UE9
  • LJSelfUpgrade 1.30 - Updates firmware on the U3/U6/UE9
  • LJLogUD 1.18 - Logging program up to 10 Hz for the U3/U6/UE9
  • LJStreamUD 1.18 - Logging program up to 80,000 Hz for the U3/U6/UE9
  • LJLogM 1.03 - Logging program up to 10 Hz for the T7
  • LJStreamM 1.04 - Logging program up to 80,000 Hz for the T7
  • Kipling 3.0.6 - Basic configuration and testing application for the T7
  • Otero 1.53 - Configuration and downloader for the Digit series loggers
Code Libraries
  • LJM Library 1.0800 - Library of high-level code functions for the T7/Digit
  • LJM Constants 2015.02.26.A - JSON constants file for the LJM library
  • UD Library 3.45 - Library of high-level code functions for the U3/U6/UE9
Low-level Driver
  • LabJackWinUSB Driver X.XX - Driver for Windows USB communication to and from all LabJack devices

Tip: Uninstall previous versions before installing new versions. If a LabJack is connected during installation, unconnect and reconnect when done.

The normal ways of uninstalling previous versions of the package are:

  1. Do Start => Programs => LabJack => Uninstall.
  2. Go to Windows Control Panel (not LJControlPanel), then go to Add/Remove Programs, then find "LabJack" or "LabJackUD".

Here are the alternative manual steps:

  • Go to Start => Programs, find the LabJack group, right-click on it, and delete from the start menu.
  • On your hard drive delete the LabJack folder which is usually in "C:\Program Files\" or "C:\Program Files (x86)\"
  • Find and delete delete labjackud.dll in your system directory (i.e. "C:\windows\system32\" or "C:\windows\SysWOW64\").
Mac OS X details
Mac OS X (Kipling Only) 42 MB
3.0.9

Kipling is available for download/installation through a standalone .zip file that must be manually extracted and installed. Currently, Kipling only supports the T7. However, it will eventually support the Digit as well. This program supports both 32-bit and 64-bit versions of Mac OS X 10.7+. Mac OS X 10.6 is not officially supported. However, it currently runs on 10.6.8.

Notes:
  • Make sure you download and install the latest version of the LJM library.
  • Currently only available as a .zip file. Isn't integrated into our standard Mac OS X installer yet.
  • Currently Kipling3 is distributed for Mac OS X as a .zip file that should be copied into the applications directory. It contains one app and one folder that should reside in the same directory. Make a folder in the applications directory called Kipling and copy all contents into it.
  • When downloading with Google Chrome, you may get a "malicious file" warning. Ex: "kipling_win.exe is not commonly downloaded and could be dangerous" with a large Discard button. You must click the drop-down arrow and "Keep" to prevent the file from being discarded. Currently the files are hosted by s3.amazon.com, although this will be changed in the future.
Linux details
Linux 32-bit (Kipling Only) 43 MB
3.0.2
Linux details
Linux 64-bit (Kipling Only) 46 MB
3.0.0

Kipling is available for download/installation through a standalone .zip file that must be manually extracted and installed. Currently, Kipling only supports the T7. However, it will eventually support the Digit as well. This program supports both 32-bit and 64-bit versions of Linux.

Requirements

Kipling uses the pre-built binaries of Node Webkit / NW.js. Because of this, slow-moving distributions may not be compatible with Kipling. Some incompatible distributions include Debian (Weezy) and Red Hat 6.5 / CentOS 6.5. Generally, your distribution needs gtk 2.18, glibc 2.15, and other libraries.

Note that you can build NW.js and build Kipling yourself. If you do, feel free to let us know how it went so that we can add support for your distribution.

Notes:
  • Make sure you download and install the latest version of the LJM library.
  • Currently only available as a .zip file. Isn't integrated into any standard installer.
  • When downloading with Google Chrome, you may get a "malicious file" warning. Ex: "kipling_win.exe is not commonly downloaded and could be dangerous" with a large Discard button. You must click the drop-down arrow and "Keep" to prevent the file from being discarded. Currently the files are hosted by s3.amazon.com, although this will be changed in the future.

Release Notes

Currently the version of Kipling for Linux 64-bit (Ubuntu) computers isn't working. We are working on setting up a new build computer to release a new version of Kipling for that platform and architecture.

Kipling for all platforms is being updated to 3.0.9 and we noticed some upgrading issues on windows 8 machines. If a window comes up saying "node webkit" in ascii-art your upgrade failed and you will need to manually download the stand-alone .zip and replace the files in your program directory to finish the kipling upgrade. A new version of the main installer with kipling 3.0.9 will be released soon so this step won't be necessary.

Program Highlights

Device Selection

Kipling features a simple device selection process that makes it easy to see a device's connectivity options and provides users immediate information about each found device. The information provided is particularly useful for users trying to connect to devices using a local area network.

Program Usability

Multifunction DAQ devices, especially the T7 and T7-Pro have a lot of built-in features. Kipling combats this by being fast and organized. Kipling keeps a tabbed based interface but formats all information so that it is both easy to understand and easy to find.

Analog Input Functionality

The T7 and T7-Pro are highly capable devices with a multitude of different analog based features. Kipling makes them easy to learn about, configure, and use. Explore the device's extended features through a GUI interface before trying to program them with only command line based tools and a datasheet for debugging.

Device Scripting

Explore the T7/T7-Pro's most unique feature, Lua Scripting. Write, run, and debug Lua scripts that get executed locally on the device to explore the device's capabilities and allow the T7 to function independently from a computer. Lua script examples are built into the program!

Device Updating

The employees at LabJack are dedicated to making the T7 a quality data acquisition and control device that fits many people's needs. In order to do this we release device updates with new features, bug fixes, and more. Kipling makes this easy by automatically downloading and installing firmware files that used to be only available on the firmware page.

Screen Shots

Comments

#1

I've got no success using Kipling 3 on Ubuntu 12.04 64-bit. I updated my LJM library and unpacked Kipling. It starts just fine, but the top third of the screen is covered with a big orange error message:

Critical Error Encountered Loading Module: device_selector.html
Error: TypeError
When Loading File: device_selector.js
Full Path To File: /tmp/.org.chromium.Chromium.A6wN0x/static/js/device_selector.js
Error Contents: TypeError: Cannot read property '0' of undefined
Check console.log for more info.
Consider using www.jshint.com to debug file

I can select the device though, and a flurry of activity happens on the console when I do so (it seems it dumps the whole ljm_constants file), but when I click on »Continue«, the orange box stays, there's a message »devices connected. / Select Devices« in the lower-left corner, but other than that, there's nothing on the screen.

#2

We'll be releasing a new 64-bit Linux version of Kipling to address this as soon as possible. Thanks for the error report!

#3

Any idea on when this fix will be released?

#4

We are currently trying to re-work the lower level parts so that we can upgrade to the latest version of node-webkit and fix some of our distribution issues.  Unfortunately the project depends on a library that doesn't support the version of node that the newer node-webkit provides so it has taken a substantial amount of effort.  This issue will hopefully get resolved upon completion of the aforementioned task which will hopefully get finished at the end of the month.

#5

I just tried the current version (3.0.0) of Kipling for Linux 64bit on my Linux Mint 17 (equiv. to Ubuntu 14.04). I got as far as starting Kipling. It recognized my new T7 but froze with the following output shown in console:

[10941:1210/235259:INFO:CONSOLE(143)] ""Critical Error:" "TypeError"", source: file:///tmp/.org.chromium.Chromium.XzcDUh/presenter.js (143)

[10941:1210/235259:INFO:CONSOLE(144)] ""When Loading File:" "device_selector.js"", source: file:///tmp/.org.chromium.Chromium.XzcDUh/presenter.js (144)

[10941:1210/235259:INFO:CONSOLE(145)] ""Error Contents:" {}", source: file:///tmp/.org.chromium.Chromium.XzcDUh/presenter.js (145)

 

#6

We'll be releasing a new 64-bit Linux version of Kipling to address this as soon as possible. Thanks for the error report!

#7

I just bought a T7 LabJack and I was wondering how to manually configure a FIO to analog. For example, using a U3-HV you will do something like "lj.configAnalog(u3.FIO1)". 

Note: I'm using python

#8

The FIO/EIO cannot be used as analog inputs on the T7.  Only the U3 has the ability to use FIO/EIO as low-voltage analog inputs, and in fact on the U3-HV there is no FIO1 as that terminal is a fixed high-voltage analog input AIN1.

#9

I tried yesterday to install the windows standalone version on a windows 7 ultimate computer as administrator and was unable to install the program. And endless list of subprograms that violated the security regulations. Today I installed the kipling with the windows installer and no problems. The new version is much better than the old version that is in the windows installer package of 49,9 MB. Especially when you have a screen where you have enlarged the font size.   

 

#10

I was able to reproduce this issue with the files that get downloaded in the .zip file.  I assume you ran the "Kipling.exe"?  It hopefully came up with a windows security message and then popped up with many more?  If you run the "nw.exe" first and tell windows to remember that it is allowed to be executed, the problem should go away.  Kipling.exe loads a splash screen and starts the nw.exe program.  I believe it was recursively calling and trying to start the nw.exe program.  We are in the middle of fixing a few issues like these.  Thanks for the feedback and let us know if you have any suggestions, especially while Kipling is in its beta phase.

#11

Hi,

The source code of splash screen is also open source? If is, where can I find it?

I'm trying implement the same behavior for my nw test project, but I can't measure the progress of unpacking the nw files.

Best,

#12

We can publish the source code for the splash screen if you want, it is just not published anywhere.  Unfortunately, it doesn't measure the progress of unpacking the nw files.  The currently implemented splash screen simply checks for the number of running nw.exe processes and exits when this number reaches two.  We haven't found a way to measure the absolute progress of unpacking the nw files but would really like to be able to do that in our splash screen.

#13

Yes, I would like to check your code for splash screen.

I was following this discussion but seems that there is no a solution for measure the startup progress, until now.

If I found a good solution I will back and share with you.

Thank you.