With the shutdown of the 2g network here in Australia over the next 12-18 months, I am looking for a 3g compatible device to work with your software.
I have found the GT06E which is not listed on your compatible device list.
Will this work with the GT06 protocol?
I should work with one of the protocols. See following page:
@dtvea1 ,Please share about GT06E.
I will as soon as I have completed testing. The unit has just arrived.
Hi @dtvea1 ,
I between the decision to buy and looking to buy on eBay to test. I do not see the setup settings Common Command List to point GT06E to Server.
How Common Command List settings to point GT06E to Server?
What "Common Command List" are you talking about?
Hi @tananaev ,
“Common Command List” = “SMS command”
Edit SMS command to device setting.
See topic 7. Common Command List link below
Check out this document:
Hi @tananaev ,
Operating System : Linux 64 bit
Traccar : version 3.6
Device : GT06E
In state, Time Attibute(B) is incorrect not match Devices Last Update(A)
The impact is the result of date and time search that is not correct(C).
I try offset value with gt06.timezone (https://www.traccar.org/configuration-file/).
<entry key='gt06.port'>5023</entry> <entry key='gt06.timezone'>25200</entry>
Not working, Tracker server log display
2016-08-20 14:22:46 DEBUG: [952A5A21: 5023 < 184.108.40.206] HEX: 78780a1344060200020040d5c10d0a 2016-08-20 14:22:46 DEBUG: [952A5A21: 5023 > 220.127.116.11] HEX: 787805130040ba7c0d0a 2016-08-20 14:22:46 INFO: [952A5A21] id: xxxxxxxxxxxxxxx, time: 2016-08-20 21:01:23, lat: 13.87785, lon: 100.57455, speed: 1.1, course: 335.0
please guide me and Thank, For document is great.
Time in the Devices table is the server time when last message from device was received. In State and Report it's the time that device reported. They don't have to be the same.
What timezone is configured on your tracker? I would recommend to use UTC/GMT.