CalAmp LMU3030
It doesn't look like the standard format for CalAmp. Do you have the protocol documentation?
I got 2 of these devices hoping they'd be compatible "out of the box" as I saw them listed as supported in the device documentation. Maybe they are older firmware, a different model, or are misconfigured somehow. I'll factory reset and reconfigure, check for firmware updates, and also try the second one that I have here.
I'm somewhat shooting in the dark with the SMS programming, though. I'm kind of combining two sources...
https://support.hologram.io/hc/en-us/articles/360035696993-CalAmp-LMU-3030
and
https://www.traccar.org/forums/topic/calamp-lmu-2630-setup-problems/
I am using the first method because I have hologram SIM cards and it seems to be working to do some of the basic programming. But the additional commands in the second method... I'm not sure how they translate to the first method. The "!RP" in the commands I am sending using the first method line up with the "AT$APP PARAM" prefix from the second method. But I'm not sure how to translate some of the other commands... so any help here would be awesome.
I'll dig some more to see if I can find protocol information or other info to debug this and report back.
As an aside, I have the traccar client working for Android and iPhone working flawlessly with some tweaks to the standard app settings and the xml config on the server. So that is exciting!
So the second device has the same issues... The initial call from the device into traccar server results in an unknown device message...
2023-11-10 10:39:09 INFO: [U544bf687: calamp < 195.226.133.53] 830545720351110101010200045d5575325d54a54d13c072b5ba18d09800001ab70000000000000c240000000080080e080acb570000000000131f8fff0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000e2200000000000000000000000000000000000000000000000000000000
2023-11-10 10:39:09 WARN: Unknown device - 4572035111 (195.226.133.53)
So I add the device thru the traccar webui and subsequent log entries are shown below...
2023-11-11 07:15:56 INFO: [U544bf687: calamp < 195.226.133.55] c305457203511101010102113555584352364330374c39423133383335010200045d5575325d54a54d13c072b5ba18d09800001ab70000000000000c240000000080080e080acb570000000000131f8fff0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000e2200000000000000000000000000000000000000000000000000000000
2023-11-11 07:15:57 INFO: [U544bf687: calamp > 195.226.133.55] 02011135020000000000
2023-11-11 07:15:57 INFO: [U544bf687] error - Latitude out of range - IllegalArgumentException (Position:236 < CalAmpProtocolDecoder:80 < *:210 < ExtendedObjectDecoder:75 < ...)
2023-11-11 07:16:16 INFO: [U544bf687: calamp < 195.226.133.55] c305457203511101010102113555584352364330374c39423133383335010200045d5575325d54a54d13c072b5ba18d09800001ab70000000000000c240000000080080e080acb570000000000131f8fff0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000e2200000000000000000000000000000000000000000000000000000000
2023-11-11 07:16:16 INFO: [U544bf687: calamp > 195.226.133.55] 02011135020000000000
2023-11-11 07:16:16 INFO: [U544bf687] error - Latitude out of range - IllegalArgumentException (Position:236 < CalAmpProtocolDecoder:80 < *:210 < ExtendedObjectDecoder:75 < ...)
2023-11-11 07:17:16 INFO: [U544bf687: calamp < 195.226.133.55] c305457203511101010102113555584352364330374c39423133383335010200045d5575325d54a54d13c072b5ba18d09800001ab70000000000000c240000000080080e080acb570000000000131f8fff0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000e2200000000000000000000000000000000000000000000000000000000
2023-11-11 07:17:16 INFO: [U544bf687: calamp > 195.226.133.55] 02011135020000000000
2023-11-11 07:17:16 INFO: [U544bf687] error - Latitude out of range - IllegalArgumentException (Position:236 < CalAmpProtocolDecoder:80 < *:210 < ExtendedObjectDecoder:75 < ...)I have been unable to find any information about the specific formats of the different message types. All of the subsequent messages have a prefix of c305 followed by what traccar pulls out as the device ID (4572035111). Beyond that I am not sure what the rest of the data is.
CalAmp seems to be fairly proprietary with regard to their devices and platform. Worth contacting them to see if I can get this decoded, or should I move on and try to find different devices? Any feedback would be appreciated...
And again, my goal is low cost, reliable ODB devices for mileage tracking. My client has about 200 devices currently and we have a "hands free" system that imports the trips for each employee and lines it up with their payroll punches to determine if the mileage for the trip can be reimbursed to the employee. Problem is the current cost and recent issues with reliability with the current vendor.
If you bought the devices legitimately, I don't see why they wouldn't provide you the documentation.
I'll give it a go with calling CalAmp. I bought the devices on eBay and suspect they are older and maybe not supported, but I'll report back.
Just had a little break through... Within this article is a CalAmp executable file for decoding the hex string...
https://github.com/traccar/traccar/issues/1430
And as you'd expect, the log entries above decode with all kinds of garbage data and dates after the MobileID is decoded properly. The mobileID detected does match up to the device ESN. This is the partial output from their decoding tool...
OptionsByte MobileID,MobileIDType C3
MobileIDLength 5 bytes 05
MobileID 4572035111 4572035111
MobileIDLen 1 byte 01
MobileIDType ESN 01
Service Type Ack'd Request 01
Message Type 02: Event 02
Sequence# 4405 1135
UpdateTime 5/17/2015 7:29:22 AM 55584352
TimeOfFix 11/6/1998 5:21:59 PM 36433037
Latitude 127.8820913 4C394231
Longitude 85.9321141 33383335
Altitude 16908292 01020004
Speed 35035192.6 mph 5D557532
Heading 5D54
Satellites 165 A5
For what it's worth, by sending an !R4 command over SMS to the device I got this back via SMS...
!E4572035111FFFFFF010000654FBC1F654FBC1F171273FEB7C4B40E000002F000F80A000104FFBBAF091300FFFF0400003570000002D20000000000001064
Which is decoded perfectly with all valid information from the CalAmp LMDecoder.exe program.
MobileID 4572035111FFFFFF
MobileIDType ESN
Sequence# 0
UpdateTime 11/11/2023 5:38:39 PM
TimeOfFix 11/11/2023 5:38:39 PM
Latitude 38.708531
Longitude -121.1845618
Speed 16.8 mph
Heading Southwest ( 248 degrees)
Satellites 10
FixStatus Good
Carrier 260
RSSI Very Good (-69)
CommState Avail,Network,Data,Connected,Roaming
HDOP Ideal (.9)
Inputs IgnitionOn,Input1,Input4
UnitStatus Good
EventIndex Realtime PEG request
EventCode Realtime PEG request
Accum Count 4
Spare B7
Accum 0 00003570
Accum 1 000002D2
Accum 2 00000000
Accum 3 00001064
So, I'm unsure why the SMS format seems legit, but the report to traccar seems garbled.
@Ken, do you know another source for the LMDecoder app? The server of the source you mentioned above seems to be down.
Cheers,
Simon
@Ken Loveless
can you share the LMDecoder File for us please.
The Link is broken.
Just got this device connected and it's kicking this error in the logs...
Anybody have any ideas on how to rectify?
These are the commands I've used to program the device over SMS...