
QM range App Note, document number 260283, rev 15
Page 46 of 48
Read word transaction type. The fan speed is returned in LINEAR11 format. The value is in units of RPM. If
no fan is fitted this will return 0.
Read Fan speed 2
– Command 91h
Read word transaction type. The fan speed is returned in LINEAR11 format. The value is in units of RPM. If
one or no fans are fitted this will return 0.
Manufacturer ID
– Command 99h
Read Block transaction type. The value is returned as an ACSII string, and is always equal to “TDK_LAMBDA”.
Model ID
– Command 9Ah
Read Block transaction type. The
value is returned as an ACSII string, and is always equal to “QM”.
Manufacture Date
– Command 9Dh
Read Block transaction type. The value is returned in 3 bytes as follows:
Byte 1 = Day of Month (1-31)
Byte 2 = Month of Year (1-12 representing January to December)
Byte 3 = Year (16-99 representing 2016
– 2099)
Serial Number
– Command 9Eh
Read Block transaction type. The value is returned as a 10 character ACSII string.
Runtime
– Command C4h
Read Block transaction type. The data is returned as a 32-bit unsigned value as follows:
Byte 1 = Least Significant Byte
Byte 2 = 2
nd
Least Significant Byte
Byte 3 = 2
nd
Most Significant Byte
Byte 4 = Most Significant Byte
Note that he value represents the time the unit has been powered up, which may not equal the time that module
outputs have been enabled. The value is in units of ¼ hours e.g. a value of 13 represents 3.25 hours.
Power Cycle Count
– Command C5h
Read Block transaction type. The data is returned as a 32-bit unsigned value as follows:
Byte 1 = Least Significant Byte
Byte 2 = 2
nd
Least Significant Byte
Byte 3 = 2
nd
Most Significant Byte
Byte 4 = Most Significant Byte
Note that he value represents the number of times that power has been cycled to the unit.
S/W Version Number
– Command C6h
Read Word transaction type. The version number is expressed as a major and minor pair as follows:
Byte 1 = Major version number (unsigned value 0-255)
Byte 2 = Minor version number (unsigned value 0-255)
The version number is
usually expressed as “<major>.<minor>”.
Miscellaneous Commands
Capability
– Command 19h