Sending Commands to Atrack Device
What commands have you tried? Have you checked the documentation to see if it's correct format for GPRS?
I have tried the following, all are known to respond
AT$GPRS=?
AT$INFO=?
AT$TRAC=?
I worked with ATrack devices for a time and we only ever formatted commands in this manner.
Even over serial we would send commands like this.
Unless I have missed a required obvious Line in the
Config xml
The devices should reply $OK or reply with the configuration information attached
for example
$TRAC=141,20,100,15,0,0,2,0,0,0
It is possible it’s a device fault or shitty firmware. However i have no other Atrack devices to test my theory on currently
For an example
My Teltonika FTC921s replied flawlessly on FW0.4.0 when upgraded to FW2.1.4 they stopped responding/listening. this was resolved with FW3.0.8 they work rock solid on Traccar again now.
Thank you for your Time
It's very possible that command format is different between SMS and GPRS.
Thanks Anton,
I will try to get another ATrack device to verify against.
I note this in the docs after a re-read
I have been too buried in the actual contents of the command.
• For the serial port and GPRS communications, it is mandatory to terminate a command
line using <CR><LF>.
• For the SMS communication, the <CR><LF> is not needed. The commands are followed
by a response that includes <CR><LF>.
Traccar automatically adds <CR><LF>, so I hope you're not adding those.
Nope not at all
So a little further digging,
The Device is definitely receiving and replying but something (way above my pay grade) is stopping it from showing in the UI?
2026-02-01 22:46:27 INFO: [T6392c09d] id: 8677300*REDACTED*, command type: custom sent
2026-02-01 22:46:27 INFO: [T6392c09d: atrack > *REDACTED*] AT$INFO=?\r\n
2026-02-01 22:46:27 INFO: [T6392c09d: atrack < *REDACTED*] 40502c313834302c3134332c3135372c3836373733303035333837313734392c313736393933393138362c313736393933393138362c313736393933393138362c3137343639323533302c2d33363830353734302c34352c322c32333139352c362c312c302c302c302c2c323030302c323030302c1a2c34302c3133352c31302c31352c392c254256254d562547512553412547532543490d0a
2026-02-01 22:46:27 INFO: [T6392c09d: atrack > *REDACTED*] fe02000000000000008f009d
2026-02-01 22:46:29 INFO: [T6392c09d: atrack < *REDACTED*] $INFO=8677300*REDACTED*,AK7V,Rev.1.00 Build.253900,8677300*REDACTED*,530011117526597,8964012304035265975F,135,40,15,1,10,1,0,BG95M3LAR02A03_01.005.01.005,**REDACTED**\r\n
2026-02-01 22:46:29 WARN: [T6392c09d] error - For input string: "AK7V" - NumberFormatException (... < AtrackFrameDecoder:57 < BaseFrameDecoder:29 < ... < WrapperInboundHandler:56 < ... < StandardLoggingHandler:62 < ...)
2026-02-01 22:46:29 INFO: [T6392c09d] disconnected
2026-02-01 22:46:29 INFO: Event id: 8677300*REDACTED*, time: 2026-02-01 22:46:29, type: deviceOffline, notifications: 0
2026-02-01 22:46:29 WARN: [T6392c09d] error - For input string: "AK7V" - NumberFormatException (... < AtrackFrameDecoder:57 < BaseFrameDecoder:29 < ... < WrapperInboundHandler:50 < ... < OpenChannelHandler:38 < ...)
2026-02-01 22:46:30 INFO: [T6392c09d] id: 8677300*REDACTED*, time: 2026-02-01 22:46:26, REDACTED LAT AND LONG, course: 45.0
2026-02-01 22:46:34 INFO: [T93777d3a] connected
2026-02-01 22:46:34 INFO: [T93777d3a: atrack < *REDACTED*] fe0200031532259f3885009e
2026-02-01 22:46:34 INFO: [T93777d3a: atrack > *REDACTED*] fe0200031532259f3885009e
2026-02-01 22:46:35 INFO: [Tb0cf2b95: teltonika < REDACTED IP] ff
2026-02-01 22:46:47 INFO: [T93777d3a: atrack < *REDACTED*] 40502c334231382c3134332c3135392c3836373733303035333837313734392c313736393933393230362c313736393933393230362c313736393933393230362c3137343639323533302c2d33363830353734302c34352c322c32333139352c362c312c302c302c302c2c323030302c323030302c1a2c34302c3133352c31302c31352c392c254256254d562547512553412547532543490d0a
2026-02-01 22:46:47 INFO: [T93777d3a: atrack > *REDACTED*] fe02000000000000008f009f
2026-02-01 22:46:47 INFO: Event id: 8677300*REDACTED*, time: 2026-02-01 22:46:47, type: deviceOnline, notifications: 0
2026-02-01 22:46:50 INFO: [T93777d3a] id: 8677300*REDACTED*, time: 2026-02-01 22:46:46, REDACTED LAT AND LONG, course: 45.0
2026-02-01 22:47:07 INFO: [T93777d3a: atrack < *REDACTED*] 40502c444633322c3134332c3136302c3836373733303035333837313734392c313736393933393232362c313736393933393232362c313736393933393232362c3137343639323533302c2d33363830353734302c34352c322c32333139352c362c312c302c302c302c2c323030302c323030302c1a2c34302c3133352c31302c31352c392c254256254d562547512553412547532543490d0a
2026-02-01 22:47:07 INFO: [T93777d3a: atrack > *REDACTED*] fe02000000000000008f00a0
2026-02-01 22:47:10 INFO: [T93777d3a] id: 8677300*REDACTED*, time: 2026-02-01 22:47:06, REDACTED LAT AND LONG, course: 45.0
2026-02-01 22:47:17 INFO: [T93777d3a] id: 8677300*REDACTED*, command type: custom sent
2026-02-01 22:47:17 INFO: [T93777d3a: atrack > *REDACTED*] AT$TRAC=?\r\n
2026-02-01 22:47:20 INFO: [T93777d3a: atrack < *REDACTED*] $TRAC=141,20,100,15,0,0,2,0,0,0\r\n
2026-02-01 22:47:23 WARN: Position handler failed - Cannot invoke "java.util.Date.getTime()" because "time" is null - NullPointerException (TimeHandler:65 < *:60 < *:53 < BasePositionHandler:34 < ProcessingHandler:169 < *:178 < OutdatedHandler:56 < ...)
2026-02-01 22:47:23 WARN: Position handler failed - Cannot invoke "java.util.Date.getTime()" because the return value of "org.traccar.model.Position.getFixTime()" is null - NullPointerException (FilterHandler:126 < *:212 < *:279 < BasePositionHandler:34 < ProcessingHandler:169 < *:178 < DistanceHandler:74 < ...)
That looks like invalid format. Do you have the protocol documentation?
yes, I had emailed you some the other week freshly updated documentation from Atrack.
the device(s) are definitely reply in a manner I am familiar with
ie the “$TRAC=Current config numbers”
is pretty normal for their replies
Atrack devices tend to reply without any fluff just a “$OK”
When did you email?
30/12/2025
not for this reason, but it was the latest official protocol documents if you wished to share on the traccar website
Are you sure you're using the latest official release without any modifications? I just tested the latest code and I don't get any errors.
I'll spin up another fresh install to test, but currently running 6.11.1
Thanks for the assistance thus far!
Try the preview.
Hey there,
This may well be a silly question, however I am currently having issues sending GPRS commands to a Atrack AK7V-ME. (I wish to adjust some of the configuration over the wire without having to do SMS commands and responses, especially as it's not cheap to send SMS messages here.
All my Teltonika units Receive and Reply to commands, however the single Atrack device does not, at all. it does however reply to SMS messages.
I accept this may just be a fault with this singular device, but would welcome any advice or direction if I am perhaps missing something crazy obvious.
For all intents and purposes the Atrack device seems to work.