Message Types

You may not see all the message types described here or you may use some message types that are not shown here.

Message types are vendor-specific. The full text of the message is provided where available.

Table 1. Description of Message Type Abbreviations Seen in MDT Center
Abbreviation Full Text Explanation
ACP Accepted The driver accepted a trip that was added to the manifest.
CD Driver Request Client Cancel at Door The driver indicated that the passenger canceled at the door.
CHF Fare Changed The fare was changed.
CNT Vehicle Connected/Vehicle Disconnected The vehicle is either connected or disconnected to the MDT Center.

Check the Comments field to determine its current state.
CTX CannedMsg The driver sent a canned message or the mobile software generated a message using the canned text message format.
DOFF Vehicle Logoff by Driver The driver manually logged off from the mobile computer system.
EMG Emergency The driver pressed the Emergency button on the mobile data computer.
FRF Driver Failed Download Fx The fixed route trip download failed.
FTX FreeText The driver typed a message or the mobile software generated a message using the free-form text message format.
LOFF VehLoggedOffByMdtSrv The driver was logged off by the MDT Server because the NAK threshold has been reached.

The mobile computer sent back so many NAK messages that the MDT Server automatically logged the vehicle off to save over-the-air traffic. As a dispatcher, contact the driver to determine the issue, and if appropriate, use the MDT Center to manually log the driver back into the system.
LOFF Veh logged off The driver was logged off by the MDT Server because the driver performed the pull-in event.

This functionality is controlled by an MDT Server property.
LOFF Veh Logged Off by MDT Server The driver was logged off by the MDT Server through its end of day routine.
LOFF Veh Logoff by Driver The driver performed the log-off function on the mobile data computer.
LON Veh Auto Logon The driver logged on the vehicle.
LONF Driver Download Trips Failed, Invalid Driver Info The log on credentials provided were invalid.
LONF Driver Download Trips Failed, Incorrect Run The run provided during the log on process was not correct.
LONF Driver Download Trips Failed, Driver Not Assigned to the Run The log on credentials/run combination were not valid.
LONF Driver Download Trips Failed, Driver not Qualify the Run's Requirement The driver does not have the required certifications to perform this run.
LONS Driver Download Trips Success, Wait Co-Driver Login This run requires a co-driver and is waiting for the co-driver to log on.
LONS Co-Driver Download Trips Success, Whole Login Success This run requires a co-driver and the co-driver has successfully logged in.
LONS Driver Download Trips Success The log on process has been successfully completed.
MFL ManifestFull The driver's manifest is at critical capacity (the mobile computer manifest is full).

The driver cannot receive additional trips or trip insertions because of the critical capacity limit. Once the driver performs his or her next event then he or she can receive trip insertions.
NAK VehInNakStatus: Veh in NAK Status (Too many NAKS) The gateway software has returned a NAK (Not Acknowledged) or the MDT Server has not received a response from the gateway software. This indicates that a pending message has not been delivered to the vehicle. The system will continue to attempt to deliver it until it reaches the threshold where the vehicle is logged off because of too many NAKs.
NS Driver Req Client No Show The driver has requested a no-show.
NTF Notification Notifications relating to the IVR notifications. Used only with IVR integration.
ORD Trip Execute Out of the Order The driver attempted to perform a trip which was not according to the order of events in the itinerary.
REF Refused The driver refused a trip that was added to the manifest.
SKIP Flex Node/Stop Was Skipped A driver missed a flex stop.
SYS System Message: The communication to SchSrv is broken! The MDT Server has lost communication with the Schedule Server.
SYS System Message: Connection to FTP Server is Not Available This message is currently only generated by the FTP interface.
TOT Send Trip Time Out The send trip action was timed out (due to established thresholds).
TrE TripTimeEarly/Late-Trip Early This message is generated based on the Expected Time of Arrival (ETA) and the trip early parameter specified in the MDT Server properties. It is not so much a schedule adherence message as an indication that the driver might have performed the trips out of sequence.
TrL TripTimeEarly/Late-Trip Late This message is generated based on the ETA and the trip early parameter specified in the MDT Server properties. When a TrL is received, the dispatcher should check the run for possible schedule adherence issues.
TrMM Drv Exec Trip but MdtSrv cannot retrieve from Manifest

A driver executed a trip that is no longer on his or her manifest. This is typically a timing issue.

TrMM messages happen when the following events occur in sequence:
  1. The event was sent to the mobile computer.
  2. The trip was moved or otherwise changed resulting in the MDT Server canceling or resending the event.
  3. Before the MDT Server could remove the old event from the mobile computer and replace it with the new, the driver performed the trip.

The event the driver performed is therefore no longer the same one and the TrMM message is sent.

If you have many same day changes, you are likely to have multiple TrMM messages.