Macro Field Types
The following table describes the type and length of the types of macro fields.
Type | Length | Description |
---|---|---|
Free-form | 1-38 | Letters, numbers, and special characters in any format. The following characters cannot be used in macros: \ { } [ ] ^ ¢ _ |
Alphabetic | 1-38 | Alphabetic characters (A–Z and a-z) only. There can be embedded spaces, and spaces before and after the letters. |
Unsigned Integer | 1-10 | Whole numbers only; plus (+) and minus (–) signs cannot be used. |
Full Field Integer | 1-10 | Whole numbers only; plus (+) and minus (–) signs cannot be used. The number must fill the entire field. |
Signed Integer | 1-10 | Whole numbers with plus (+) and minus (–) signs. There can be spaces before and after the numbers, but not between them. |
Alphanumeric | 1-38 | Letters and numbers. There can be spaces before, after, and between the characters. |
Real Number | 1-12 | Numbers with plus (+) and minus (–) signs and decimal points. There can be spaces before and after the numbers, but not between them. |
Monetary | 5-12 | Dollar and cent amounts only. The field size includes a dollar sign and decimal point, so a 5 digit field is shown in the macro as $_ . _ _ |
Standard Date | 8 | Valid month, day, and year, shown in the macro as _ _ /_ _ /_ _ . |
Brief Date | 5 | Valid month and day, shown in the macro as _ _ / _ _ . |
12-Hour Time | 6 | Valid times in the format hh:mmA (for AM) or hh:mmP (for PM). Shown in the macro as _ _ : _ _ _ |
24-Hour Time | 5 | Valid 24-hour (military) times in the format hh:mm. Shown in the macro as _ _ : _ _ |
7-Digit Phone Number | 8 | Phone numbers without an area code. Shown in the macro as _ _ _ - _ _ _ _ |
12-Digit Phone Number | 12 | Phone numbers with an area code. Shown in the macro as _ _ _ _ _ _ - _ _ _ _ |
Zip Code | 5 | The 5-digit zip code, shown in the macro as _ _ _ _ _ |
Extended Zip Code | 10 | The 9-digit zip code, shown in the macro as _ _ _ _ _ - _ _ _ _ |
Yes/No | 1 | Y or N response |
Weekday | 3 | Days of the week abbreviations (MON, TUE, WED, THU, FRI, SAT, SUN). |
Month | 3 | Month abbreviations (JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC). |
State | 2 | State abbreviations (AL, AK, …WY). |
DTTS Code | 1 | Valid DTTS codes |
Item List | 1-38 | Accepts an alphanumeric value from a list of
specified values. The values appear in the macro after the field, for example:
(value1, value2, value3...). After selecting this field type, you are prompted
to enter the list values. Type any number of valid alphanumeric items following
these rules:
|
Integer Range | 1-10 | Accepts a whole number within a specified range. The range appears in the macro after the field, for example: (1:10) After selecting this field, you are prompted for a length and a lower and upper limit. When the dispatcher or driver creates a macro with an integer range field, the entry is validated. |
Social Security Number | 11 | A social security number, shown in the macro as _ _ _ - _ _ - _ _ _ _ |
Password | 1-15 | Accepts a password. The field appears in the macro definition as asterisks between brackets, such as [*****]. The sender replaces the asterisks with the password, but the password is hidden to the recipient. The recipient replaces the asterisks with the password to see the information that follows the password field. |
Time Stamp | 24 | The date, in the form of mm/dd/yyyy; the time and the time zone in which the transmission was created in the form of hh:mm:ss:tmzn. This is an autofill field. |
Odometer (Performance Monitoring) | 11 | The vehicle’s odometer
reading when the transmission is created, shown in the macro as _ _ _ _ _ _._
_MI (or KM).
Tip: You can’t add the Odometer field to a macro that
contains the LTD Distance field. You must remove the LTD Distance field before
adding the Odometer field if you prefer to use Odometer.
|
Total Fuel Used | 12 | The amount of fuel used by the engine, shown in the macro as _ _ _ _ _ _._ GAL or LTR. |
Idle Fuel Used | 12 | The amount of fuel used while the engine is running but the speed is zero, shown in the macro as _ _ _ _ _ _._ GAL or LTR. |
PTO Fuel Used | 12 | The amount of fuel used while idling in PTO (power take off) mode, shown in the macro as _ _ _ _ _ _._ GAL or LTR. |
Parked Idle Fuel | 12 | The amount of fuel used while the engine is idling and the parking brake is on, shown in the macro as _ _ _ _ _ _._ GAL or LTR. |
Reefer Temperature (Trailer Tracks) | 26 |
The temperature and trailer ID data from the attached Trailer Tracks-equipped trailer. The dispatcher sees the following:_ _ _ . _°_ _ _ . _°_ _ _._°_ _ _ _ _ _ _ _ . The first temperature is for set point, the second is for supply
air, the third is for return air, and the fourth field is the trailer ID or
serial number. Include, as part of the macro definition, some text to remind
the dispatcher what the various parts of the temperature field are. The
characteristics of this field include:
This field can only be used in return macros. |
Arrival Date & Time | 22 | The arrival date, time, and QTRACS system time zone. This is an autofill field used primarily by LTL carriers. The information is initially stored in the mobile unit’s memory if the mobile unit is enabled for message combining and the driver brought up the arrival screen on the display unit upon arriving at a stop. Depending on the Macro Field Date format (*MDY or *DMY), this field has one of the following formats: mm/dd/yy hh:mm:ss zzzz, or dd/mm/yy hh:mm:ss zzzz. It shows in the macro as follows: _ _/_ _ /_ _ _ _:_ _ :_ _ _ _ _ _ |
Arrival GPS Position | 25 | The arrival position (lat/long in degrees, minutes, seconds plus direction) and age of the GPS position in minutes. This is an autofill field used primarily by less than truckload carriers. This field has the following format: dd° mm' ss'' x ddd° mm' ss'' x mm. It shows in the macro as follows: _ _°_ _ '_ _''_ _ _ _ _° _ _'_ _''_ _ _ |
Message Send Date & Time | 22 | The message send date, time, and QTRACS system time zone. This is an autofill field used primarily by LTL carriers. Depending on the Macro Field Date format (*MDY or *DMY), this field has one of the following formats: mm/dd/yy hh:mm:ss zzzz, or dd/mm/yy hh:mm:ss zzzz. It shows in the macro as follows: _ _/_ _ /_ _ _ _:_ _ :_ _ _ _ _ _ |
Message Send GPS Position | 25 | The message send position (lat/long in degrees, minutes, seconds plus direction and age of the GPS position in minutes. This is an autofill field used primarily by LTL carriers. This field has the following format: dd° mm' ss'' x ddd° mm' ss'' x mm It shows in the macro as follows: _ _°_ _ '_ _''_ _ _ _ _° _ _'_ _''_ _ _ |
Life-to-Date Distance | 12 | The vehicle’s odometer
reading when the transmission is created, shown in the macro as _ _ _ _ _ _ _._
_MI (or KM). This is similar to the Odometer field, except it rolls over at
9,999,999.9 miles (or km), instead of at 999,999.9 miles (or km).
Tip: You can’t add the Odometer field to a macro
containing the LTD Distance field.
|
©2018 Omnitracs, LLC