Calamp LMU-2630 setup problems

Sheikha month ago

Yes I’m running it at home on proxmox. It worked well until I changed my internet provider. I use subdomain for phone app and for TTU2830LA GPS I was using my IP address and port. I have setup cloudflare proxy with subdomain for all my other services like home assistant etc but I’m stuck on TTU2830LA.

Dibbsa month ago

Most dynamic DNS providers will give you 1 host for free - that's one sub domain on one of their many domains. Your router would need to update the dynamic DNS provider each time the address changes & have a port forward for the port to your server on proxmox.

This is assuming the 2830 will take a (sub)domain instead of an IP address for the config.

Fairly standard dynamic DNS stuff.

Sheikha month ago

Getting a domain is not an issue. As you said if 2830 will take a subdomain. Last time when I tried using, I was not able to set a subdomain name using AT$APP PARAM 768,0,A_NUMBER_HERE - command.
But setting ip address worked just fine.
Is there any other command that’s for subdomains?

Dibbsa month ago

You could try the following:

AT$APP PARAM 769,0,5082 -- set the port to communicate with the server, whatever port you are using on the server.

Reset the IP to zero

AT$APP PARAM 768,0,0

And set the URL instead relying on DNS to do the lookup:

AT$APP PARAM 2319,0,"some.url.com" Change inbound URL

Can't guarantee it will work, but I think it will.

Sheikha month ago

Thanks Dibbs
I’ll try it in this week, I still need to remove it from my car. As soon as I’m done I’ll report back if it works.

Florian Sachs20 days ago

@Dibbs

that really helps some people a lot.
In Germany, a telematic service based on calamp devices has discontinued its service and a few people are trying to continue using the devices sensibly

Florian Sachs20 days ago

@Dibbs

A few things for my understanding:
Firstly, my device is a Calamp LMU-3030, but as far as I can tell, the commands should be the same as for the Calamp LMU-2630.
I also use programming via SMS. However, this seems to be derived from the AT commands.

I have found a PEG guide that is for the model LMU-1000 and LMU-4100
It describes the syntax as follows:
512,Event#,Trigger,Trigger Modifier,Condition One,Condition One Modifier,Condition Two,Condition Two Modifier,Action,Action Modifier
(AT$APP PARAM 512,Event#,Trigger,Trigger Modifier,Condition One,Condition One Modifier,Condition Two,Condition Two Modifier,Action,Action Modifier)

It seems to me that your commands follow the syntax
512,Event#,Trigger,Trigger Modifier,Condition One,Condition One Modifier,Action,Action Modifier,Unknown,Unknown
(AT$APP PARAM 512,Event#,Trigger,Trigger Modifier,Condition One,Condition One Modifier,Action,Action Modifier,Unknown,Unknown)
Does the syntax for LMU-2630 (and presumably LMU-3030) look like this?

Dibbs20 days ago

@Florian,

I checked the 512 commands I posted on Page 1 of this thread, e.g.

AT$APP PARAM 512,5,3,0,2,0,13,0,0,0

And it follows the format:

Trigger:
Trigger Modifier:
Condition One:
Condition One Modifier:
Condition Two:
Condition Two Modifier:
Action:
Action Modifier:

But as you've pointed out, there are 2 extra on the end. Having had a fresh look, the extra on the end are AND\OR operators. How they work, I don't know. You could just leave them as zero or miss them out - you'll need to see if both options get the same result.

HIH

Dibs

Florian Sachs20 days ago

@Dibbs:
The original programming read out was as follows (SMS format):

512,0,48,0,0,0,110,0,0,0 OK
512,1,1,0,30,0,1,34,0,0 OK
512,2,1,0,30,0,92,0,0,0 OK
512,3,1,0,0,0,49,0,0,0 OK
512,4,1,0,0,0,49,129,0,0 OK
512,5,1,0,0,0,31,3,0,0 OK
512,6,0,0,0,0,0,0,0,0 OK
512,7,3,0,167,5,7,0,0,0 OK
512,8,3,0,0,0,99,7,0,0 OK
512,9,0,0,0,0,0,0,0,0 OK
512,10,0,0,0,0,0,0,0,0 OK
512,11,0,0,0,0,0,0,0,0 OK
512,12,3,0,9,2,26,29,0,0 OK
512,13,3,0,0,0,19,31,0,0 OK
512,14,3,0,0,0,32,0,0,0 OK
512,15,0,0,0,0,0,0,0,0 OK
512,16,0,0,0,0,0,0,0,0 OK
512,17,0,0,0,0,0,0,0,0 OK
512,18,0,0,0,0,0,0,0,0 OK

As a result, 31 acc's were transmitted to Traccar, from which we were able to assign the following values:
acc04: fuel level (btw: LMU-3030 is a OBD-Device)
acc21: meters (current Trip)
acc22: seconds (current Trip)
acc27: Battery voltage * 1000 (Car)
acc30: Battery voltage * 1000 (build in battery device)

I´ve done the setup you describe.
Now Traccar gets only 15 acc`s.
I´ve were able to assign;
acc04: fuel level
Maybe acc09: Battery voltage * 1000 (Car)

I have just tried to restore:
512,12,3,0,9,2,26,29,0,0 OK
512,13,3,0,0,0,19,31,0,0 OK
512,14,3,0,0,0,32,0,0,0 OK

Still just 15 acc´s.

Any idea how to restore the original acc's...... or generally how to configure the acc output?

Florian Sachs20 days ago

@Dibbs

I checked the 512 commands I posted on Page 1 of this thread, e.g.

AT$APP PARAM 512,5,3,0,2,0,13,0,0,0

And it follows the format:

Trigger:
Trigger Modifier:
Condition One:
Condition One Modifier:
Condition Two:
Condition Two Modifier:
Action:
Action Modifier:

But as you've pointed out, there are 2 extra on the end. Having had a fresh look, the extra on the end are AND\OR operators. How they work, I don't know. You could just leave them as zero or miss them out - you'll need to see if both options get the same result.

I have not quite understood it yet

In your example
AT$APP PARAM 512,5,3,0,2,0,13,0,0,0
512=PEG
5=Rule Index
3=Trigger:
0=Trigger Modifier:
2=Condition One:
0=Condition One Modifier:
13=Condition Two:
0=Condition Two Modifier:
0=Action:
0=Action Modifier:

So two conditions defined and no action called?

Dibbs20 days ago

@Florian

I have not quite understood it yet

In your example
AT$APP PARAM 512,5,3,0,2,0,13,0,0,0
512=PEG
5=Rule Index
3=Trigger:
0=Trigger Modifier:
2=Condition One:
0=Condition One Modifier:
13=Condition Two:
0=Condition Two Modifier:
0=Action:
0=Action Modifier:

So two conditions defined and no action called?

Here's 2 sample 512 rows:

AT$APP PARAM 512,101,48,0,65,0,27,2,68,0
Event 101:
Start Idle Timer
Trigger: 48 (Any Trigger)
Trigger Modifier: 0
Condition One: Ignition On
Condition One Modifier: 0
Condition Two: Not Moving
Condition Two Modifier: 0
Action: Start Time Accumulator
Action Modifier: 2
Condition Operation: AND

AT$APP PARAM 512,5,3,0,2,0,13,0,0,0
Event: 5
Trigger: 3 (Power Up or Wake Up)
Trigger Modifier: 0
Condition One: 2 (Ignition Off)
Condition One Modifier: 0
Condition Two: None
Condition Two Modifier: 0
Action: 13 (Start/Restart Timer)
Action Modifier: 0

It would appear Condition 1 & 2 are being "combined" somehow into 1 field & their modifiers - I haven't found out how yet.

I do know

Ignition On = 1
Moving = 4

How these "combine" to 65, I don't know yet.