➤ CalAmp

Hello,

I have got access to puls wiki and I am going through the documentation.
I have a few doubts and it would be really helpful if you could guide me on the same. (PS  My hardware has been shipped and will be arriving soon. )

1)To set GPIO 1 as an output and GPIO 2 as an input you would use:
AT$APP PARAM 1024,39,1,1
AT$APP PARAM 1024,39,2,0
Or you could use the single command of
ATS157 = 1---------------------------this should be ATS159 as the ID is 39???? right????

2) Restoring values through a power cycle
The LMU is capable of storing some of its values to nonvolatile memory so that they can be restored after a power cycle. The following values may be stored:
The values of all 16 or 32 Accumulators (since 25d in LMU3000)---------------------what does 25d mean here?? is it 25 in decimal?? I find it difficul to understand this part.
The states of all 16 or 32 PEG Flags (since 25d in LMU32 family)

Also, Can you guys suggest me an easy way to start learning how to script..Like are there any short cuts to learn this stuff.. Any help would be appreciated.

hi..Thanks yavi..
I am also having trouble typing anything into my hyper- terminal.
Can I type inside the terminal only after i get the device connected. I know it makes no sense but I just want to see what kind of error i get if I try to communicate from an hyperterminal without the LMU.
But the problem is I am not able to enter anything!!

Hello

1.-
Use PEG actions instead,  for SET Output 0

AT$APP PEG ACTION 8 0

To RESET Ouput 0

AT$APP PEG ACTION 9 0

2.-
25d means firmware version (actually 2.5d)

gokulsreedhar91 you can set  logic of device, like an tracking, Ignition ON etc. with help of CalAmp LMU Manager. To understand how to work with LMU manager, please, read about it on CalAmp wiki (https://puls.calamp.com/wiki/LMU_Manager_User's_Guide_V8.3). We also can help you to set basic settings of device (APN,server,port etc), but for this, please, write to hw@gurtam.com. Thank you.  .

gokulsreedhar91  We have no any internal documents.
Calamp is very complicated but functional tracker. It is impossible to learn it very fast. Nobody can explain you in a few words all nuances. We can create the basic script for Wialon only. But it will be only small part of all functions,

Please ask Calamp support about details of configuration.

Hi,

We have a number of LMU-3030 OBDs in service with our customers and wondering if someone could shed some light on an issue we constantly have.

It seems that the device takes some time to lock on to signal and start taking data, example, it may take up to 5kms before it shows any tracking. It is noted when pulling reports and it doesn't send an Exit geofence because it exited well before the device was triggered. We only get Enter geofence when it returns to the office. I speak in this case one of our own vehicles - a BMW X5, all too often short trips (5km round trip) is not even recorded in tracking because it has not connected yet..

Our customers have a "basic" track and trace requirement so there are not complicated needs for diagnostics etc.

I have attached an image to show what I am speaking of.

Any assistance or insight would be very welcome, we are now trialing an alternative OBD device for us to use in place of the LMU-3030 for all future sales as we cannot seem to rely on this CalAmp device.

Thanks small_gprs, we have the CalAmp agents here in Australia configure for us when we purchase them.

We have been going back and forth with them and the latest config change has been to turn off the device filtering - they think it might be the issue and too aggressive.

We put it to a small test on Saturday to see if it made any difference and it is now tracking as it should be.

They also changed the ignition config so am not sure which change made the difference, although it is now seemingly working as we would expect, however will continue to monitor to confirm.

Cheers.

http://avl.hobby-site.org/blog/?p=82

Good day!

Could you please write to hw@gurtam.com. At letter please, indicate your question and device ID. Thank you.

Thanks small_gprs,

The main issue with these Calamps is that 30 or so parameters for LMU303 and other models.Is there somewhere that advises us of which parameter does what? Otherwise it is a lot of time trial and error with all this units in service with customers.

The CalAmp agent who applied the script gave us these event codes to help us set up sensors.

Alaiksandr from Gurtam has since helped use by building some sensors for us for the LMU2600 devices we have. Now we need to work out the other models.

We gave up using Calamp and have only around 40 left in service, we find them to complex for scripting, too expensive for purchasing and noncompetitive.

I can help in detailed events or parameters calamp sent, Duo Wialon+Calamp is best solution around, can be a little expensive due Calamp is built in USA real high quality , any way, good luck !