AGG Software Forums

Hello
I use the last week your app "GPS Tracker Data Logger" and I am excited.

I use the following command in SQL Database Professional plugin to record the id of the device to send records to the database.

UPDATE car_location INNER JOIN car ON car_location.IMEI_number = car.IMEI_number SET car_location.car_id = car.car_id

This I do to find in the database the car_id based the  IMEI number .
This works but takes much processing power because it searches for the IMEI of all recordings.
My question is if I can use the above command one a VALUES like (:IMEI) for compare only the IMEI of the device and not from the database.

Thank You
George

You can try to add the WHERE expression:

UPDATE car_location INNER JOIN car ON car_location.IMEI_number = car.IMEI_number SET car_location.car_id = car.car_id
WHERE car_location.IMEI_number = :IMEI

and then assign the IMEI SQL parameter with the corresponding parser item. Please, note that not all device send their IMEI to the server.

Thank you for your prompt reply
It works very well.
But I have a new problem.
We use the device Teltonika FM42xxx and if I change the settings in the I/O
do not get the IMEI number.
This is the problem of device or in format of the parse data ?
Could I have modified the module for devices teltonika ?

Thank you
George

Hello, George.

Could you describe your actions step-by-step? I'll verify it.

I will first query the company Teltonika to learn more information because I think it might be the problem.
When I configure the device to have events for change profiles , sends the IMEI only on first connection to the server.
Also how I could add the following additional features of the device FM4200 ?
We must build communication from scratch or you can add to the existing?

AI1                     double          Yes    NULL       
AI2                     double          Yes    NULL       
AI3                     double          Yes    NULL       
AI4                     double          Yes    NULL       
EVENTID           int(11)          Yes    NULL       
V1                      double          Yes    NULL       
V2                      double          Yes    NULL       
TRACK              double          Yes    NULL       
DI1          bit(1)          Yes    NULL       
DI2          bit(1)          Yes    NULL       
DI3          bit(1)          Yes    NULL       
DI4          bit(1)          Yes    NULL       
DI5          bit(1)          Yes    NULL       
DI6          bit(1)          Yes    NULL       
DI7          bit(1)          Yes    NULL       
DI8          bit(1)          Yes    NULL       
DO1          bit(1)          Yes    NULL       
DO2          bit(1)          Yes    NULL       
DO3          bit(1)          Yes    NULL       
DO4          bit(1)          Yes    NULL       
DO5          bit(1)          Yes    NULL       
DO6          bit(1)          Yes    NULL       
DO7          bit(1)          Yes    NULL       
DO8          bit(1)          Yes    NULL       
FLAG1          varchar(16)    latin1_swedish_ci       
FLAG2          varchar(16)    latin1_swedish_ci       
FLAG3          varchar(16)    latin1_swedish_ci       
FLAG4          varchar(16)    latin1_swedish_ci    

Thank you for all
George   

1. Our software stores the IMEI after the connection and adds it to each database record.
2. Please, note that the table is universal and your tracker may not provide all info that the table can store.

I solved the problem with the script execute.
Now the device tracker continuously sends the IMEI.
Thank you for your interest.
But now how I can add extra data to parse module of Teltonika ?

Our parser extracts all data that described in the data exchange protocol for this device.
Please, read about IOX_Y parser items here:

http://www.aggsoft.com/gps-tracker-data-logger/gps-tracker-teltonika.htm

Do you mean that the plugin can read CAN BUS data from device?
If not how can I do ?

I only mean that if the tracker sends some special data, then our software parses it to IOX_Y parser items. For example, the device that we've tested before returns:

IO1_1 - digital counter #1
IO1_2 - digital counter #2
IO1_3 - digital counter #3
IO1_4 - digital counter #4
IO2_66 = 13413 external power (13.4 V)
IO2_67=10023 internal power (10.0 V)
IO4_70=346  internal temperature (34 C)

IO2_9 = 13484 - analog input #1 (13.4 V)
IO2_10 - analog input #2
IO2_11  - analog input #3
IO2_19  - analog input #4

But in your case it may be different.