ERM custom message format
ERM trackers support many inputs and all does not need to be included in the messages sent to the server to save bandwidth. The default settings for the trackers does not include all inputs either.
Here is an example of the default Message Format for ZEE:
#EDT#,#EID#,#PDT#,#LAT#,#LONG#,#SPD#,#HEAD#,#ODO#,#IN1#,#IN2#,#IN3#,#IN4#,#OUT1#,#OUT2#,#OUT3#,#OUT4#,#LAC#,#CID#,#VIN#,#VBAT#,#DEST#
If you decide to change the Message Format for your trackers or part of your trackers, you also need to update the Message Format in GpsGate.
Follow those steps:
A. Update the Message Format for the Device Type in Site Admin (Legacy)
1. Login to Site Admin (Legacy)
2. Go to Devices (top menu)
3. Go to Types (left menu)
4. Select Device Type to edit.
5. Scroll down to "Message Format" and enter your new format.
6. Save.
TIPS! If you have many Message Formats you can create new Device Types, one for each Message Format.
B. Update the devices.
Connect your tracker(s) to a PC and set the Message Format.
Or send a Template Command with the new Message Format from GpsGate Server.
C. Select the correct Device Type in the applications.
Log in to the application(s), and make sure your tracker(s) has the correct Device Type set.
If you just edited an existing Device Type in step A. and did not create a new one, this step is not necessary.
NOTE!
- Inputs that are not part of the message format cannot be used in the Device Mapper (they will have empty values).
- Changing the Message Format in Site Admin (Legacy) will not automatically change the Message Format i the tracker. Those are two separate actions you need to take.