Installation guide

LMU Users Guide
V1.0.6 December 10 2009
Copyright ©CalAmp DataCom Inc 2009
- 117 - CalAmp Proprietary & Confidential
For the MDT we will need the following messages:
• Cab Available (Driver –> Dispatch)
• Request Pickup, includes address (Dispatch -> Driver)
• Cab in use (Driver -> Dispatch)
• Cancel Pickup (Dispatch -> Driver)
• At pickup (Driver -> Dispatch)
For the driver messages, each will be assigned to a particular button on the MDT. The
incoming messages will be shown on the four line display.
On the credit card processing side we would like the card reader to encrypt the credit card
data before sending it to through LMU. The LMU, in turn sends the message to the back
end (again using an unacknowledged service). The back end will decrypt the data and
forward it to the credit card processing agent. Once an authorization has been received,
notification is sent back to the LMU and credit card reader to allow the transaction and print
a receipt.
14.3.2.3 Remote Application Requirements
The remote application will need to support the following high level features to meet the
customer’s needs:
• Send and Receive Messages to/from the MDT.
• Display all MDT messages to the Dispatch application.
• Display all vehicle locations in the dispatch application including availability status
• Display only available cabs in the website application
• Display ETA to pickup data for ‘reserved’ cabs in website application
• Receive and decrypt credit card data
• Process credit card data with an appropriate clearing house
• Send a response to the MDT based on credit card authorization
• Return authorization notification to the credit card reader connected to the LMU
14.3.3 LMU Programming – Planning
In the setup of the LMU, we really have four main areas of concern.
• Set up of the Host Port to work with the MDT
• Set up of the Aux Port to work with the credit card reader
• Set up of the LMU to report to the appropriate server
• Security between the LMU and the Data Center
For our Mobile Data Terminal, we have settled on the somewhat standard Net-955 from
Micronet. We have built a messaging application into this device to be able to handle the
requirements laid out in the Local Application section above.