« Close

Datasheets and User Guides

App Notes

Software & Driver

 

4.0 Hardware Overview

Following is a listing of of various registers that return general information about the device.

General Device Information Registers
Name Start Address Type Access
PRODUCT_ID 60000 FLOAT32 R
HARDWARE_VERSION 60002 FLOAT32 R
FIRMWARE_VERSION 60004 FLOAT32 R
BOOTLOADER_VERSION 60006 FLOAT32 R
WIFI_VERSION 60008 FLOAT32 R
HARDWARE_INSTALLED 60010 UINT32 R
ETHERNET_MAC 60020 UINT64 R
WIFI_MAC 60024 UINT64 R
SERIAL_NUMBER 60028 UINT32 R
DEVICE_NAME_DEFAULT 60500 STRING R/W
PRODUCT_ID
- Address: 60000
The numeric identifier of the device. Such as 7 for a T7 / T7-Pro.
  • Data type: FLOAT32  (type index = 3)
  • Read-only
HARDWARE_VERSION
- Address: 60002
The hardware version of the device.
  • Data type: FLOAT32  (type index = 3)
  • Read-only
FIRMWARE_VERSION
- Address: 60004
The current firmware version installed on the main processor.
  • Data type: FLOAT32  (type index = 3)
  • Read-only
BOOTLOADER_VERSION
- Address: 60006
The bootloader version installed on the main processor.
  • Data type: FLOAT32  (type index = 3)
  • Read-only
WIFI_VERSION
- Address: 60008
The current firmware version of the WiFi module, if available.
  • Data type: FLOAT32  (type index = 3)
  • Read-only
HARDWARE_INSTALLED
- Address: 60010
Bitmask indicating installed hardware options. bit0: High Resolution ADC, bit1: WiFi, bit2: RTC, bit3: microSD.
  • Data type: UINT32  (type index = 1)
  • Read-only
  • Default value: 0
ETHERNET_MAC
- Address: 60020
The MAC address of the wired Ethernet module.
  • Data type: UINT64  (type index = N/A)
  • Read-only
WIFI_MAC
- Address: 60024
The MAC address of the WiFi module.
  • Data type: UINT64  (type index = N/A)
  • Read-only
SERIAL_NUMBER
- Address: 60028
The serial number of the device.
  • Data type: UINT32  (type index = 1)
  • Read-only
DEVICE_NAME_DEFAULT
- Address: 60500
Reads return the current device name. Writes update the default and current device name. A reboot is necessary to update the name reported by NBNS. Up to 49 characters, cannot contain periods.
  • Data type: STRING  (type index = 98)
  • Readable and writable

 
There are several other useful device control registers listed below.  These registers have device-wide impact.

Miscellaneous Device Registers
Name Start Address Type Access
CORE_TIMER 61520 UINT32 R
SYSTEM_REBOOT 61998 UINT32 W
WAIT_US_BLOCKING 61590 UINT32 R/W
CORE_TIMER
- Address: 61520
Internal 32-bit system timer running at 1/2 core speed, thus normally 80M/2 => 40 MHz.
  • Data type: UINT32  (type index = 1)
  • Read-only
  • This register may be streamed
  • Minimum firmware version: 1.0071
SYSTEM_REBOOT
- Address: 61998
Issues a device reboot. Must write 0x4C4Axxxx, where xxxx is number of 50ms ticks to wait before reboot. To reboot immediately write 0x4C4A0000 (d1279918080).
  • Data type: UINT32  (type index = 1)
  • Write-only
  • Minimum firmware version: 0.9419
WAIT_US_BLOCKING
- Address: 61590
Delays for x microseconds. Range is 0-100000.
  • Data type: UINT32  (type index = 1)
  • Readable and writable
  • Minimum firmware version: 1.0026

 

5 comments

Is any way to find some exact information about every single analog&digtial I/O ? I mean like a table , minimalist, for example : FIO1 can perform reading,MIO2 can control speed and so on and so for ?  Eventually also the address port ? I've went to all the document and is kind of confusing for a beginner....

 

This is a good suggestion.  There is currently no table with information about every single I/O on the device.  Do you have any specific application questions?  In general, FIO, EIO, CIO and MIO can all perform digital input or digital output.  There are bullet lists at the top of each section in the datasheet which contain most of the basic information related to the section.

I think there is too much to fit in 1 table, but I did add a listing above for all connections that has a brief summary and link to further details.

michael.egan's picture

Does the T7 have any kind of self test or self diagnostic that could be run before installing the unit in a system?  I am trying to verify that the data logger in fully operational before I install it in the system and start running tests on the system.

LabJack Support's picture

To do complete testing you need some sort of connections from outputs to inputs so you can see if they are all working as expected.  You could connect jumpers from outputs to inputs and then check whichever ones you want with the Dashboard in Kipling.  Some people buy an extra CB15 and CB37 and leave them wired up with jumpers from channel to channel so they can plug in those terminal boards and check every channel.

Damage to particular channels, without damaging an entire system, is quite rare, so just opening Dashboard and seeing readings bouncing around is a good sign that the device is working properly.