Product Info

COMPANY CONFIDENTIAL: CalAmp reserves all rights to these documents and any information contained therein. Page
Reproduction use or disclosure to third parties without express permission is strictly prohibited. ©2020 CalAmp 13 of 35
LMU-1300 Training Guide
Revision & Date
0.8–09/22/2020
o Configuration Parameters - same format as existing Config Param file (File Type 1)
o PEG2 Script - ASCII Text Lines delimited with <CR><LF>
o End-Of-File marker
o CRC - Usual 2-byte CRC is appended to the file by PULS or file generation tool
• Configuration Parameter section (if present) is merged with configuration parameters on target
device
• Script section (if present) overwrites script on target device.
• New File Type: 22
• File Extension: 'PG2'
The sections 5.1.1 through 5.1.4 below describe the content of each file section. Tags are used
to identify the start of each section.
Header
TAG Definition
Example
!TD: UTC Date and Time the file was generated or
uploaded to the maintenance server (PULS)
!SIG:
File Signature is a MD-5 Hash generated
from the file contents (anything after the
signature). This is generated by LMU Manager and
PULS during upload.
!ID:
User defined identification field. Up to 60
characters allowed. This field is displayed on
PULS.
!TD:10:47:38 12-27-2018
!SIG:2a944f7d34857d99e4b39ce50069dcf0
!ID:v10.41_12_27_18_FAEPilot
Configuration Parameters
TAG Definition
Example
!CP: Following this tag, this is where all the Config
Parameters start until the PEG2 script section
starts or the EOF is detected.
Important Notes:
• Config Parameters use the same format
as in a PEG1 file
• Config Parameters are still a union of the
file contents and what already resides on
the target device
!CP:
256,0,00
256,1,01
256,2,00
256,3,00
257,0,15D4
259,3,00
260,0,00
260,1,00
....