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 IDsDevicesMinimum Compatible Firmware Version
1001LMU-30402.4.2.15
1002LMU-30402.4.2.15
1011LMU-32402.4.2.15
1021LMU-13003.10.0.10
1025ATU-13003.10.0.10
1032LMU-3040M3.10.0.10

32 Bit

App IDsDevicesMinimum Compatible Firmware Version
39LMU-4x306.0b
44, 46LMU-2L306.0b
47LMU-2L306.2a
79LMU-2L306.2b
48LMU-2L306.0a
49LMU-2L308.6b
89, 90Qtanium-4006.0b
164, 166LMU-5530, LMU-55414.1i
170LMU-2x208.5c
171LMU-2x206.0c
172LMU-2x206.0b
178, 179, 180Qube-5/Qube-3006.1c
194, 195, 196, 197, 198, 200LMU-30306.0b
203LMU-20307.2b
205, 207TTU-28306.0b
206TTU-28306.2e
220LMU-26406.2b
224LMU-2630M8.5g
227, 228LMU-2630M8.6b
239LMU-30306.0b
240LMU-30306.2a
241, 434LMU-30308.6b
254LMU-45326.2a
302TTU-28406.2k
304TTU-2840, TTU-28308.6b
310, 313, 314LMU-4x326.2h
311LMU-4x326.0b
315LMU-4x328.6b
316LMU-4x328.2a
317, 417LMU-4x32, LMU/HMU-36408.3b
330, 422TTU-4x32/TTU-4532z7.4c
348LMU-36408.6b
354, 355, 356LMU-30356.0b
375, 378LMU-36408.6b
376, 377LMU-36406.2a
391LMU-30357.6c
392Qube-5/Qube-3006.2h
403TTU-2840, TTU-28306.2h
404TTU/LMU-36407.1a
405Qube-5/Qube-3008.6b
406Qube-5, Qube-3007.2e
414LMU-30307.2c
416LMU/HMU-36407.3c
418LMU/HMU-36407.5a
436LMU-30358.6b
438VLU-118.1b
444LMU-2630M8.5f
445, 454, 455, 463TTU-2830, TTU-2900MB, LMU-2630M, TN3640M8.5d
446LMU-3640M8.5f
447LMU-2630EZ8.5d
448LMU-2630M8.5b
449LMU-30308.6b
450HMU-3640-LE6.0b
451HMU-3640-LA6.0b
453TTU-29008.6b
459LMU-2630M8.6b
460LMU-3640M8.5f
461TTU-2900MB8.6b
462TN3640L8.5f
464TN3640M8.6g
465HMU-36408.6f
466HMU-36408.6f
467TTU-2830M8.6e

8 Bit

App IDsDevicesMinimum Compatible Firmware Version
5LMU-2002.6u
16, 17LMU-3302.8f
33LMU-2002.6w
34LMU-2002.6v
58LMU-1x302.6q
66TTU-1x30, TTU-1230X2.6r
67TTU-1x30, TTU-1230X2.8f
69LMU-1x302.6r
103LMU-11752.9a
108LMU-32x2.8e
131TTU-7002.6a
132, 134TTU-720, ATU-6202.8c
133TTU-720, ATU-6202.8e
135TTU-12002.8e
136TTU-12202.8e
137TTU-12002.6s
140LMU-8002.6q
147LMU-1x20, LMU-720, LMU-8202.6t
148LMU-1x20/TTU-7202.4e
393LMU-3302.8f
419TTU-12302.9a
420TTU-1x30, TTU-1230x2.9c
429LMU-1x302.8f
431LMU-1x302.8d
432TTU-720, TTU-7302.9a
433TTU-720, TTU-7302.9c
437TTU-720, ATU-6202.7c
443LMU-1x302.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 IDsDevicesStatus
9, 43LMU-4x30Non-migratable
35LMU-2H30Non-migratable
40, 41, 211LMU-4x30Non-migratable
45LMU-2L30Non-migratable
51, 52, 53, 61, 62, 63, 72Non-migratable
81, 82, 83, 84LMU-4100Non-migratable
86LMU-1000Non-migratable
111, 112, 114, 115LMU-4200Non-migratable
125, 126LMU-2610Non-migratable
129LMU-2610Non-migratable
152LMU-3000Non-migratable
160LMU-5000Non-migratable
193LMU-2010Non-migratable
222, 415LMU-2640Non-migratable
321TTU-2940Non-migratable
345LMU-3640Non-migratable
364, 365LMU-3037Non-migratable
367LMU-3640Non-migratable
452HMU-3640-MBNon-migratable
116LMU-4200TBD
117LMU-4200TBD
118LMU-4200TBD
121LMU-2500TBD
127, 128LMU-2610TBD
150, 153, 154LMU-3000TBD
155, 156, 157, 158LMU-2000TBD
161LMU-5000TBD
173LMU-2x20TBD
174, 175, 184, 191LMU-4x20TBD
176LMU-4x20TBD
177LMU-4x20TBD
185, 186, 187TTU-2820TBD
188, 189LMU-4x20TBD
199LMU-2030TBD
216, 218LMU-4x20TBD
217LMU-4x20TBD
208LMU-2030TBD
209, 213LMU-4x30TBD
210LMU-4x30TBD
212LMU-4x30TBD

8 Bit

App IDsDevicesStatus
19LMU-200Non-migratable
28LMU-400Non-migratable
29LMU-720Non-migratable
97LMU-700Non-migratable
101LMU-1100Non-migratable
144LMU-710Non-migratable
408LMU-1x30Non-migratable
30TTU-330TBD
68TTU-1x30, TTU-1230XTBD
94LMU-700uTBD
95LMU-700cTBD
96LMU-900TBD
98LMU-700TBD
99LMU-700TBD
102LMU-1150TBD
104LMU-1175TBD
106LMU-1200TBD
107LMU-1200V2TBD
109LMU-32xTBD
130TTU-700TBD
141LMU-800TBD
142TTU-710TBD
143LMU-800TBD
145LMU-62xTBD
146LMU-1x20, LMU-720, LMU-820TBD

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.

What’s Next