Account Readiness
Choosing Your CTC Server Instance (US/EU)
CalAmp provides two instances of CTC. One instance is hosted in the US and a second is hosted in Europe. The EU instance exists to help customers comply with key privacy and data-protection requirements of the General Data Protection Regulation (GDPR), which is a requirement for any devices that are operating in Europe.
Once you determine the service instance of your devices:
- Ensure your account is set up in the correct CTC server instance by contacting our team.
- If you purchased a custom part:
- Update the maintenance URL (parameter 2320) in your PEG script to point to dm.calamp.com (US) or dm.calamp.co.uk (EU).
- Update the CRAF with the modified PEG script.
- If you purchased the G1000, order a G10US or G10EU part number.
Updating CRAFs and POs
New Devices
For new device shipments and orders on backlog, be certain to update your CRAFs and purchase orders (POs) with your designated contact. All new devices that are shipped will be managed and configured via the CTC device-management web application.
Performing Required Firmware Updates
You will need to upgrade the devices you manage to the minimum compatible firmware prior to migrating to the CTC device-management platform. Review the tables below and upgrade your devices to the minimum compatible firmware version so that they're ready to migrate. While the minimum compatible firmware version is required for migration, CalAmp will only investigate potential bugs and issues on devices running the most recently released firmware.
Group existing devices into three categories:
- Active devices: Queue any firmware updates prior to migration.
- Devices in inventory (but not powered on): Queue any firmware updates prior to migration. Our migration process will apply that update before moving the device over to the CTC device-management platform. Note that these devices will migrate over when they are powered on, even after the initial bulk migration of active devices.
- Old devices that are no longer in use: Move the ESNs into a PULS group labeled "Deactivated Devices."
Note
These lists are periodically updated. (Last updated 5/4/23)
EdgeCore
App IDs | Devices | Minimum Compatible Firmware Version |
---|---|---|
1001 | LMU-3040 | 2.4.2.15 |
1002 | LMU-3040 | 2.4.2.15 |
1011 | LMU-3240 | 2.4.2.15 |
1021 | LMU-1300 | 3.10.0.10 |
1025 | ATU-1300 | 3.10.0.10 |
1032 | LMU-3040M | 3.10.0.10 |
32 Bit
App IDs | Devices | Minimum Compatible Firmware Version |
---|---|---|
39 | LMU-4x30 | 6.0b |
44, 46 | LMU-2L30 | 6.0b |
47 | LMU-2L30 | 6.2a |
79 | LMU-2L30 | 6.2b |
48 | LMU-2L30 | 6.0a |
49 | LMU-2L30 | 8.6b |
89, 90 | Qtanium-400 | 6.0b |
164, 166 | LMU-5530, LMU-5541 | 4.1i |
170 | LMU-2x20 | 8.5c |
171 | LMU-2x20 | 6.0c |
172 | LMU-2x20 | 6.0b |
178, 179, 180 | Qube-5/Qube-300 | 6.1c |
194, 195, 196, 197, 198, 200 | LMU-3030 | 6.0b |
203 | LMU-2030 | 7.2b |
205, 207 | TTU-2830 | 6.0b |
206 | TTU-2830 | 6.2e |
220 | LMU-2640 | 6.2b |
224 | LMU-2630M | 8.5g |
227, 228 | LMU-2630M | 8.6b |
239 | LMU-3030 | 6.0b |
240 | LMU-3030 | 6.2a |
241, 434 | LMU-3030 | 8.6b |
254 | LMU-4532 | 6.2a |
302 | TTU-2840 | 6.2k |
304 | TTU-2840, TTU-2830 | 8.6b |
310, 313, 314 | LMU-4x32 | 6.2h |
311 | LMU-4x32 | 6.0b |
315 | LMU-4x32 | 8.6b |
316 | LMU-4x32 | 8.2a |
317, 417 | LMU-4x32, LMU/HMU-3640 | 8.3b |
330, 422 | TTU-4x32/TTU-4532z | 7.4c |
348 | LMU-3640 | 8.6b |
354, 355, 356 | LMU-3035 | 6.0b |
375, 378 | LMU-3640 | 8.6b |
376, 377 | LMU-3640 | 6.2a |
391 | LMU-3035 | 7.6c |
392 | Qube-5/Qube-300 | 6.2h |
403 | TTU-2840, TTU-2830 | 6.2h |
404 | TTU/LMU-3640 | 7.1a |
405 | Qube-5/Qube-300 | 8.6b |
406 | Qube-5, Qube-300 | 7.2e |
414 | LMU-3030 | 7.2c |
416 | LMU/HMU-3640 | 7.3c |
418 | LMU/HMU-3640 | 7.5a |
436 | LMU-3035 | 8.6b |
438 | VLU-11 | 8.1b |
444 | LMU-2630M | 8.5f |
445, 454, 455, 463 | TTU-2830, TTU-2900MB, LMU-2630M, TN3640M | 8.5d |
446 | LMU-3640M | 8.5f |
447 | LMU-2630EZ | 8.5d |
448 | LMU-2630M | 8.5b |
449 | LMU-3030 | 8.6b |
450 | HMU-3640-LE | 6.0b |
451 | HMU-3640-LA | 6.0b |
453 | TTU-2900 | 8.6b |
459 | LMU-2630M | 8.6b |
460 | LMU-3640M | 8.5f |
461 | TTU-2900MB | 8.6b |
462 | TN3640L | 8.5f |
464 | TN3640M | 8.6g |
465 | HMU-3640 | 8.6f |
466 | HMU-3640 | 8.6f |
467 | TTU-2830M | 8.6e |
8 Bit
App IDs | Devices | Minimum Compatible Firmware Version |
---|---|---|
5 | LMU-200 | 2.6u |
16, 17 | LMU-330 | 2.8f |
33 | LMU-200 | 2.6w |
34 | LMU-200 | 2.6v |
58 | LMU-1x30 | 2.6q |
66 | TTU-1x30, TTU-1230X | 2.6r |
67 | TTU-1x30, TTU-1230X | 2.8f |
69 | LMU-1x30 | 2.6r |
103 | LMU-1175 | 2.9a |
108 | LMU-32x | 2.8e |
131 | TTU-700 | 2.6a |
132, 134 | TTU-720, ATU-620 | 2.8c |
133 | TTU-720, ATU-620 | 2.8e |
135 | TTU-1200 | 2.8e |
136 | TTU-1220 | 2.8e |
137 | TTU-1200 | 2.6s |
140 | LMU-800 | 2.6q |
147 | LMU-1x20, LMU-720, LMU-820 | 2.6t |
148 | LMU-1x20/TTU-720 | 2.4e |
393 | LMU-330 | 2.8f |
419 | TTU-1230 | 2.9a |
420 | TTU-1x30, TTU-1230x | 2.9c |
429 | LMU-1x30 | 2.8f |
431 | LMU-1x30 | 2.8d |
432 | TTU-720, TTU-730 | 2.9a |
433 | TTU-720, TTU-730 | 2.9c |
437 | TTU-720, ATU-620 | 2.7c |
443 | LMU-1x30 | 2.8c |
Non-migratable/TBD
Note
Devices that are considered "TBD" have not been tested for migration, but may be able to migrate on a case-by-case basis.
32 Bit
App IDs | Devices | Status |
---|---|---|
9, 43 | LMU-4x30 | Non-migratable |
35 | LMU-2H30 | Non-migratable |
40, 41, 211 | LMU-4x30 | Non-migratable |
45 | LMU-2L30 | Non-migratable |
51, 52, 53, 61, 62, 63, 72 | Non-migratable | |
81, 82, 83, 84 | LMU-4100 | Non-migratable |
86 | LMU-1000 | Non-migratable |
111, 112, 114, 115 | LMU-4200 | Non-migratable |
125, 126 | LMU-2610 | Non-migratable |
129 | LMU-2610 | Non-migratable |
152 | LMU-3000 | Non-migratable |
160 | LMU-5000 | Non-migratable |
193 | LMU-2010 | Non-migratable |
222, 415 | LMU-2640 | Non-migratable |
321 | TTU-2940 | Non-migratable |
345 | LMU-3640 | Non-migratable |
364, 365 | LMU-3037 | Non-migratable |
367 | LMU-3640 | Non-migratable |
452 | HMU-3640-MB | Non-migratable |
116 | LMU-4200 | TBD |
117 | LMU-4200 | TBD |
118 | LMU-4200 | TBD |
121 | LMU-2500 | TBD |
127, 128 | LMU-2610 | TBD |
150, 153, 154 | LMU-3000 | TBD |
155, 156, 157, 158 | LMU-2000 | TBD |
161 | LMU-5000 | TBD |
173 | LMU-2x20 | TBD |
174, 175, 184, 191 | LMU-4x20 | TBD |
176 | LMU-4x20 | TBD |
177 | LMU-4x20 | TBD |
185, 186, 187 | TTU-2820 | TBD |
188, 189 | LMU-4x20 | TBD |
199 | LMU-2030 | TBD |
216, 218 | LMU-4x20 | TBD |
217 | LMU-4x20 | TBD |
208 | LMU-2030 | TBD |
209, 213 | LMU-4x30 | TBD |
210 | LMU-4x30 | TBD |
212 | LMU-4x30 | TBD |
8 Bit
App IDs | Devices | Status |
---|---|---|
19 | LMU-200 | Non-migratable |
28 | LMU-400 | Non-migratable |
29 | LMU-720 | Non-migratable |
97 | LMU-700 | Non-migratable |
101 | LMU-1100 | Non-migratable |
144 | LMU-710 | Non-migratable |
408 | LMU-1x30 | Non-migratable |
30 | TTU-330 | TBD |
68 | TTU-1x30, TTU-1230X | TBD |
94 | LMU-700u | TBD |
95 | LMU-700c | TBD |
96 | LMU-900 | TBD |
98 | LMU-700 | TBD |
99 | LMU-700 | TBD |
102 | LMU-1150 | TBD |
104 | LMU-1175 | TBD |
106 | LMU-1200 | TBD |
107 | LMU-1200V2 | TBD |
109 | LMU-32x | TBD |
130 | TTU-700 | TBD |
141 | LMU-800 | TBD |
142 | TTU-710 | TBD |
143 | LMU-800 | TBD |
145 | LMU-62x | TBD |
146 | LMU-1x20, LMU-720, LMU-820 | TBD |
Prepare List Of All Devices To Be Migrated
Prepare a list of all the ESNs that will need to be migrated. This list will be provided to our team when you're ready to execute migration.
Prepare List Of All Files To Be Migrated
The PULS migration tool can copy customer generated files in your PULS account to your CTC account. Prepare a list of the following to be sent to our team:
- PEG Script: maintenance URL will be updated to the CTC server (US or EU) automatically.
- PEG2 Script: maintenance URL will be updated to the CTC server (US or EU) automatically.
- EdgeApp/HostedApp: migrated with no changes.
- JPod2 Config: migrated with no changes.
- APN lists: migrated with no changes.
- Linux OPKG: migrated with no changes.
Updated over 1 year ago