T2 Configuration Parameters
This page provides a partial list of T2 configuration parameters that are stored in the host's database. (There are additional parameters that are only visible/settable at the NMC.)
The columns in this table are:
- Parameter Code - unique ID of each parameter
- Description - a short description of the parameter
- Value Length - length of the parameter value
- Value Format - describes the format of the character-based parameter value and/or the valid values
- Host Settable - indicates if host is able set this parameter
Parameter Code
|
DescriptionValue
|
LengthValue Format
|
Description
|
Host Settable
|
---|---|---|---|---|
01003 |
TerminalPowerState |
3 |
Reports the current power state of the unit. Possible values are: |
|
01009 |
|
|
The material control number of the terminal. Example: 20-J1208-1 A/B |
|
|
|
|
The material control number of the main circuit card assembly of the terminal. |
|
|
|
|
The version number associated with the terminal's boot code. |
|
|
|
|
The version of the firmware residing in the onboard primary programmable integrated circuit (PIC) |
|
|
|
|
The version information of the terminal's firmware Format: [program].[major].[minor].[build] Example: TE.00.01.00042. |
|
|
|
|
The version information of the firmware residing within the phone module. |
|
|
|
|
The version information of the firmware on the GPS device. |
|
|
|
|
The version information of the firmware residing within the analog modem. |
|
|
|
|
Shows the registration status of the terminal. Possible values are: |
|
|
|
|
The ID of the equipment as specified by the owning company |
|
|
|
|
The first 4 bytes must contain the length of the installation notes. The remaining bytes contain the installation notes themselves. |
|
|
|
|
Reason for a configuration tool session. Possible values are: |
|
|
|
|
The interval (in relative time format) between status reports generated by the terminal. This parameter may be set in multiples or fractions of 24 hours only. Possible values are: |
|
|
|
|
A description of the door sensor connected to input 3. |
|
|
|
|
A description of the auxiliary sensor connected to input 4. |
|
|
|
|
The interval (in relative time format) between checks for forward messages. Possible values are: |
|
|
|
|
The interval (in relative time format) between GPS position checks during sleep. Possible values are: |
|
|
|
|
Upon entering an active geofence area, the terminal's response is based on this value. Possible values are: |
|
|
|
|
Upon exiting an active geofence area, the terminal's response is based on this value. Possible values are: |
|
|
|
|
The position of the center of the geofence, represented as latitude followed by longitude. Possible value: |
|
|
|
|
The east/west length of the geofence rectangle in meters. Possible values are: |
|
|
|
|
The north/south dimension of the geofence rectangle in meters. Possible values are: |
|
|
|
|
The time (in GMT seconds) when the defined geofence becomes active. Possible value: |
|
|
|
|
The time (in GMT seconds) when the defined geofence becomes inactive. Possible values are: |
|
|
|
|
The state indicating whether a terminal is currently located within an active geofence. Possible values are: |
|
|
|
|
Defines whether the geofence center is known, or should be set to the terminal's position (self-centered). Possible values are: |
|
|
|
|
The version of the loader firmware residing in the onboard primary programmable integrated circuit (PIC) |
|
|
|
|
The standard Carrier Alpha Code of the equipment. The fifth character must be blank; the value must be a valid SCAC as defined by the NMFTA. |
|
|
|
|
The interval (in relative time format) of how often to take cargo readings. Possible values are: |
|
|
|
|
The interval (in relative time format) of how long to wait between cargo state change validation readings. Possible values are: |
|
|
|
|
How many times a cargo reading must return the new state in order to confirm a cargo state change. Possible values are: |
|
|
|
|
Length of time (in relative time format) that the door sensor must be open before an open event is declared. Possible values are: |
|
|
|
|
Length of time (in relative time format) that the door sensor must be closed before an open event is declared. Possible values are: |
|
|
|
|
Length of time (in relative time format) that the auxiliary sensor must be open before an open event is declared. Possible values are: |
|
|
|
|
Length of time (in relative time format) that the auxiliary sensor must be closed before an open event is declared. Possible values are: |
|
|
|
|
Indicates the action to be taken when a door sensor open event occurs. Possible values are: |
|
|
|
|
Indicates the action to be taken when a door sensor close event occurs. Possible values are: |
|
|
|
|
Indicates the action to be taken when an auxiliary sensor open event occurs. Possible values are: |
|
|
|
|
Indicates the action to be taken when an auxiliary sensor close event occurs. Possible values are: |
|
|
|
|
Indicates the action to be taken when a cargo empty event occurs. Possible values are: |
|
|
|
|
Indicates the action to be taken when a cargo not empty event occurs. Possible values are: |
|
|
|
|
Indicates whether the terminal should send its Terminal ID over the power bus for connect / disconnect detection by a connected mobile unit. Possible values are: |
|
|
|
|
Indicates whether status reports should be sent when connected to external power. Possible values are: |
|
|
|
|
Length of time (in relative time format) that the terminal should stay in the "engine off" state after a "stay awake" event action occurs. Possible values are: |
|
|
|
|
Indicates whether door sensor is installed. Will be automatically set to 'Installed' when the sensor closes and may be set to 'Installed' or 'Not Installed' by user input. Possible values are: |
|
|
|
|
Indicates whether auxiliary sensor is installed. Will be automatically set to 'Installed' when the sensor closes and may be set to 'Installed' or 'Not Installed' by user input. Possible values are: |
|
|
|
|
The validated state of the door sensor. Possible values are: |
|
|
|
|
The validated state of the auxiliary sensor. Possible values are: |
|
|
|
|
Indicates whether the cargo sensor is installed. Automatically detected by the terminal. Sent on change. Possible values are: |
|
|
|
|
The validated cargo state as determined by the cargo sensor. Possible values are: |
|
|
|
|
The time (in GMT seconds) at which the cargo state was last known to be true. |
|
|
|
|
The time (in GMT seconds) when the battery was last replaced. Sent on change. |
|
|
|
|
The type of auxiliary battery connected to the terminal. Automatically detected by the terminal. Sent on change. Possible values are: |
|
|
|
|
The interval (in relative time format) between queued scheduled status reports generated by the terminal. This parameter may be set in multiples or fractions of 24 hours only. Possible values are: |
|
|
|
|
The version number of the Cargo Sensor. Not applicable unless a cargo sensor is present. |
|
|
|
|
This parameter indicates the minimum distance, in miles or kilometers depending on company preference, the terminal can move to be considered a beginning of trip movement. The specified value will then be used to update both the 1257 (beginning of trip distance threshold in meters) and the H0152 (beginning of trip distance threshold in miles) monitoring plan default parameters. Valid values are specified in appendix B of the TT/iWeb 2.0 Technical Reference. |
|
|
|
|
This parameter indicates the time interval, in seconds, that a terminal must remain motionless be considered an end of trip movement. The specified value will then be used to update the 1261 (end of trip time threshold) monitoring plan default parameter. Valid values are specified in appendix B of the TT/iWeb 2.0 Technical Reference. |
|
|
|
|
This parameter indicates the time interval, in seconds, that a terminal must remain motionless after an end of trip movement to be considered an extended end of trip movement. The specified value will then be used to update the 1262 (end of trip time threshold) monitoring plan default parameter. Valid values are specified in appendix B of the TT/iWeb 2.0 Technical Reference. |
|
|
|
|
This parameter indicates the Event Code Action that will result from a beginning of trip movement. The specified value will then be used to update the 1263 (beginning of trip event action) monitoring plan default parameter. Valid values are specified in appendix B of the TT/iWeb 2.0 Technical Reference. |
|
|
|
|
This parameter indicates the Event Code Action that will result from an end of trip movement. The specified value will then be used to update the 1264 (beginning of trip event action) monitoring plan default parameter. Valid values are specified in appendix B of the TT/iWeb 2.0 Technical Reference. |
|
|
|
|
This parameter indicates the Event Code Action that will result from an extended end of trip movement. The specified value will then be used to update the 1265 (beginning of trip event action) monitoring plan default parameter. Valid values are specified in appendix B of the TT/iWeb 2.0 Technical Reference. |
|
|
|
|
The maximum distance in meters that the terminal can move while suppressing messages. Possible values are: |
|
|
|
|
The maximum interval (in relative time format) that can elapse while the terminal is suppressing messages. This parameter may be set in days only. Possible values are: |
|
|
|
|
This parameter indicates the time interval, in seconds, that a terminal. The specified value will then be used to update the 1270 (power-on validation time) monitoring plan default parameter. Valid values are specified in appendix B of the TT/iWeb 2.0 Technical Reference. |
|
|
|
|
This parameter indicates the time interval, in seconds, that a terminal. The specified value will then be used to update the 1271 (power-on validation time) monitoring plan default parameter. Valid values are specified in appendix B of the TT/iWeb 2.0 Technical Reference. |
|
|
|
|
This parameter indicates the Event Code Action that will result from a power-on time occurrence. The specified value will then be used to update the 1272 (power-on event action) monitoring plan default parameter. Valid values are specified in appendix B of the TT/iWeb 2.0 Technical Reference. |
|
|
|
|
This parameter indicates the Event Code Action that will result from a power-off time occurrence. The specified value will then be used to update the 1273 (power-off event action) monitoring plan default parameter. Valid values are specified in appendix B of the TT/iWeb 2.0 Technical Reference. |
|
|
|
|
This parameter indicates the time interval, in seconds, that a terminal will submit reports while it is considered to be in and In-Trip status. The specified value will then be used to update the 1280 (in-trip status reporting) monitoring plan default parameter. Valid values are specified in appendix B of the TT/iWeb 2.0 Technical Reference. |
|
|
|
|
This parameter indicates whether trip reporting is enabled or not. |
|
|
|
|
This parameter indicates the Status Reporting Mode for the terminal. The specified value will then be used to update the 1317 (customer status report mode) monitoring plan default parameter. Valid values are as follows: |
|
|
|
|
This parameter indicates the Window Status Hours for windowed status reporting on the terminal. The specified values will then be used in junction with the Window Length input to update the 1318 (customer status report times) monitoring plan default parameter.Up to 4 scheduled reporting hours may be set. There must be a minimum of 2 hours between each start hour. The parameter layout will be 'HhHhHhHh', where up to 4 hour values can be entered. If less than the maximum of 4, enter the hour(s) value(s) and the remaining portion of the field shall contain blanks. As an explanation of the internal processing of Scheduled Status Reporting, if the Preferred Status Reporting Mode parameter is '0' (use Elapsed Status Reporting, the a decimal value of 0 will fill the 1318 parameter. Otherwise, the value of this parameter combined with the value of the WR Window Length parameter will be converted to a decimal representation value which aligns to the rightmost 24 bit values expected by the mobile unit. The following are the rightmost 24 bit values associated with the scheduled reporting hour(s) that will be used to create the decimal value that gets sent to the unit: |
|
|
|
|
This parameter indicates the Reefer Temp Sensor Selection Default. The specified value will then be used to update the 1405 (reefer temp sensor selection default) monitoring plan default parameter. Valid values are specified in the T2 Parameter Reference. |
|
|
|
|
This parameter indicates the Reefer Temp Tolerance Default. The specified value will then be used to update the 1406 (reefer temp tolerance default) monitoring plan default parameter. Valid values are specified in the T2 Parameter Reference. |
|
|
|
|
This parameter indicates the Reefer Out of Range Temp Validation Time Default. The specified value will then be used to update the 1407 (reefer out of range temp validation time default) monitoring plan default parameter. Valid values are specified in the T2 Parameter Reference. |
|
|
|
|
This parameter indicates the Send Reefer Out-of-Range Temp Alert Default. The specified value will then be used to update the 1408 (send reefer out-of-range temp alert default) monitoring plan default parameter. Valid values are specified in the T2 Parameter Reference. |
|
|
|
|
This parameter indicates the Reefer Normal Temp Validation Time. The specified value will then be used to update the 1409 (reefer normal temp validation time) monitoring plan default parameter. Valid values are specified in the T2 Parameter Reference. |
|
|
|
|
This parameter indicates the Send Reefer Normal Temp9 Alert. The specified value will then be used to update the 1410 (send reefer normal temp alert) monitoring plan default parameter. Valid values are specified in the T2 Parameter Reference. |
|
|
|
|
This parameter indicates the Reefer Over Temp Alert Disable Time. The specified value will then be used to update the 1411 (reefer over temp alert disable time) monitoring plan default parameter. Valid values are specified in the T2 Parameter Reference. |
|
|
|
|
This parameter controls whether trailer specs are transmitted on the vehicle's powerbus. Note, to enable this parameter, Omni Connects must also be enabled. |
|
|
|
|
The time (in GMT seconds) of the last UTT transaction received. |
|
|
|
|
The last known battery condition. Possible values are: |
|
|
|
|
The time (in GMT seconds) when the last battery condition event was received. |
|
|
|
|
The label to display on the UI when a Door Sensor Open state is received. |
|
|
|
|
The label to display on the UI when a Door Sensor Close state is received. |
|
|
|
|
The label to display on the UI when an Auxiliary Sensor Open state is received. |
|
|
|
|
The label to display on the UI when an Auxiliary Sensor Close state is received. |
|
|
|
|
The time (in GMT seconds) the door state last changed. |
|
|
|
|
The time (in GMT seconds) the auxiliary state last changed. |
|
|
|
|
The description of the geofence displayed on the UI. |
|
|
|
|
The east/west length of the geofence rectangle in miles. Includes 2 decimal positions. Possible values are: |
|
|
|
|
The north/south dimension of the geofence rectangle in miles. Includes 2 decimal positions. Possible values are: |
|
|
|
|
Indicates the type of geofence. Possible values are: |
|
|
|
|
The message suppression radius in miles. Includes 2 decimal positions. Possible values are: |
|
|
|
|
This parameter indicates the minimum distance, in miles or kilometers depending on company preference, the terminal can move to be considered a beginning of trip movement. The specified value will then be used to update both the 1257 (beginning of trip distance threshold in meters) and the H0152 (beginning of trip distance threshold in miles) monitoring plan default parameters. Valid values are specified in appendix B of the TT/iWeb 2.0 Technical Reference. |