Product Info

Table Of Contents
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 5 of 35
LMU-1300 Training Guide
Revision & Date
0.8–09/22/2020
1. Scope
This document provides an overview of CalAmp’s Telematics EdgeCore platform, referred as EdgeCore
hereafter, the associated products, its highlights and major features. It also serves as a training manual
on ‘how-to’ get started with an EdgeCore device (e.g. LMU-1300). Lastly, this document serves to
describe the major differences between EdgeCore and the LMU32 predecessor platforms.
Platform Introduction
CalAmp’s next-generation EdgeCore platform features a new embedded architecture and revamped
hardware featuring significant advanced capability, reliability, and security. EdgeCore is agnostic to
operating system (OS) and Hardware underneath. This section highlights the major features and
benefits of the new platform.
Highlights and Features
A new embedded architecture & framework designed to be adapted on new technologies,
hardware chipsets, and operating systems
Support of Next-Generation PEG2 scripting environment
Power Management down to sub-milliamp levels during sleep
BLE Asset Tag scanner and aggregator
3 axis - Accelerometer (MEMS) and 3 axis Gyroscope
Extensive RAM/Flash memory space to avoid code space constraints.
Delta file upgrade capability
Embedded Software Architecture
The new software architecture deployed on the EdgeCore platform moves the CalAmp LMU
application functionality into a multi-threaded/multi-tasking environment. While the initial
deployment for this architecture is in a Linux environment, the architecture is specifically designed
to be portable across many other multi-tasking environments.
The fundamental goal of this architecture is to not only achieve a powerful and extensible software
platform, but also a platform that easily supports for scalability across other hardware designs in
order to meet different market segments. This is achieved by re-using common code built on a
common framework that can be ported onto different operating systems and hardware chipsets by
leveraging the use of abstraction layers.
The design and architecture of this software platform achieve the intended benefits by following
these principles:
1. Modularity and compactness of system. One module envelops one concept and/or
task.
2. Commonality across modules to allow more efficient methods to understand code
across different platforms and developers.
3. Adaptability to allow for easier changes within the product or platform, with the goal
that one module is applicable to other modules.