Ignition off message (but the ignition is on)
Have you checked the raw data to confirm if it's a device or server issue? That's probably the first thing you should do.
Yes, I have dozens of identical devices working perfectly. Only for that vehicle that sends notification with low engine speed.
Great, please provide a HEX sample with a breakdown as the proof and we'll try to help.
2023-03-20 16:14:27 INFO: [4973d2cb: gt06 < 187.119.225.54] HEX: 78781f12170314130e19c7025d1469051690d300585202d400058b001484038f83f00d0a
2023-03-20 16:14:27 INFO: [4973d2cb: gt06 > 187.119.225.54] HEX: 78780512038ff4330d0a
2023-03-20 16:14:27 INFO: [4973d2cb] id: 868003034, time: 2023-03-20 16:14:25, lat: -22.03028, lon: -47.42497, course: 82.0
2023-03-20 16:14:37 INFO: [4973d2cb: gt06 < 187.119.225.54] HEX: 78781f12170314130e23c7025d1460051690d400585202d400058b0014840390051f0d0a
2023-03-20 16:14:37 INFO: [4973d2cb: gt06 > 187.119.225.54] HEX: 7878051203901c450d0a
2023-03-20 16:14:37 INFO: [4973d2cb] id: 868003034, time: 2023-03-20 16:14:35, lat: -22.03028, lon: -47.42497, course: 82.0
2023-03-20 16:14:47 INFO: [4973d2cb: gt06 < 187.119.225.54] HEX: 78781f12170314130e2dc7025d1456051690d400585202d400058b001484039147ef0d0a
2023-03-20 16:14:47 INFO: [4973d2cb: gt06 > 187.119.225.54] HEX: 7878051203910dcc0d0a
2023-03-20 16:14:47 INFO: [4973d2cb] id: 868003034, time: 2023-03-20 16:14:45, lat: -22.03027, lon: -47.42497, course: 82.0
2023-03-20 16:14:57 INFO: [4973d2cb: gt06 < 187.119.225.54] HEX: 78781f12170314130e37c7025d144e051690d300585202d400058b0014840392a5a40d0a
2023-03-20 16:14:57 INFO: [4973d2cb: gt06 > 187.119.225.54] HEX: 7878051203923f570d0a
2023-03-20 16:14:58 INFO: [4973d2cb] id: 868003034, time: 2023-03-20 16:14:55, lat: -22.03027, lon: -47.42497, course: 82.0
2023-03-20 16:15:07 INFO: [4973d2cb: gt06 < 187.119.225.54] HEX: 78781f12170314130f05c7025d1449051690d400585202d400058b001484039312c30d0a
2023-03-20 16:15:07 INFO: [4973d2cb: gt06 > 187.119.225.54] HEX: 7878051203932ede0d0a
2023-03-20 16:15:07 INFO: [4973d2cb] id: 868003034, time: 2023-03-20 16:15:05, lat: -22.03026, lon: -47.42497, course: 82.0
2023-03-20 16:15:17 INFO: [4973d2cb: gt06 < 187.119.225.54] HEX: 78781f12170314130f0fc7025d1447051690d600585202d400058b001484039413180d0a
2023-03-20 16:15:17 INFO: [4973d2cb: gt06 > 187.119.225.54] HEX: 7878051203945a610d0a
2023-03-20 16:15:17 INFO: [4973d2cb] id: 868003034, time: 2023-03-20 16:15:15, lat: -22.03026, lon: -47.42497, course: 82.0
2023-03-20 16:15:27 INFO: [4973d2cb: gt06 < 187.119.225.54] HEX: 78781f12170314130f19c7025d1443051690d900585202d400058b001484039596470d0a
2023-03-20 16:15:27 INFO: [4973d2cb: gt06 > 187.119.225.54] HEX: 7878051203954be80d0a
2023-03-20 16:15:27 INFO: [4973d2cb] id: 868003034, time: 2023-03-20 16:15:25, lat: -22.03026, lon: -47.42497, course: 82.0
2023-03-20 16:15:37 INFO: [4973d2cb: gt06 < 187.119.225.54] HEX: 78781f12170314130f23c7025d1434051690dd00585202d400058b001484039665cb0d0a
2023-03-20 16:15:37 INFO: [4973d2cb: gt06 > 187.119.225.54] HEX: 78780512039679730d0a
2023-03-20 16:15:37 INFO: [4973d2cb] id: 868003034, time: 2023-03-20 16:15:35, lat: -22.03025, lon: -47.42498, course: 82.0
2023-03-20 16:15:47 INFO: [4973d2cb: gt06 < 187.119.225.54] HEX: 78781f12170314130f2dc7025d142f051690de00585202d400058b0014840397bd0d0d0a
2023-03-20 16:15:47 INFO: [4973d2cb: gt06 > 187.119.225.54] HEX: 78780512039768fa0d0a
2023-03-20 16:15:47 INFO: [4973d2cb] id: 868003034, time: 2023-03-20 16:15:45, lat: -22.03025, lon: -47.42498, course: 82.0
2023-03-20 16:15:57 INFO: [4973d2cb: gt06 < 187.119.225.54] HEX: 78781f12170314130f37c7025d142c051690e000585202d400058b00148403987f330d0a
2023-03-20 16:15:57 INFO: [4973d2cb: gt06 > 187.119.225.54] HEX: 787805120398900d0d0a
2023-03-20 16:15:57 INFO: [4973d2cb] id: 868003034, time: 2023-03-20 16:15:55, lat: -22.03025, lon: -47.42498, course: 82.0OK, just waiting for the breakdown now.
Sorry, I do not understand.
I asked if you checked the raw data and you said yes. How did you check it?
I noticed that the vehicle is moving at low speed (on corners and turnings) and the notifications of "ignition off" and then "ignition on" arrive on the platform. I believe it to be the battery voltage drop.
Ignição desligada 3 minutos
Ignição ligada 3 minutos
Ignição desligada 1 minutos
Ignição ligada 1 minutos
Ignição ligada 1 minutos
This with the vehicle in motion.
In short:
Low engine speed = "ignition off" notification
High engine speed = "ignition on" notification
It sounds to me like you haven't checked the raw data (aka HEX). If that's the case, we're back to my original comment. You have to check it against the documentation and figure out if the problem is on the device side or the server side.
Understood. I will check. thanks
Hello, I have the same problem with the power on and power off notifications.
When the vehicle is on, it sends the notification on, it continues to send the notification every 3 minutes when the vehicle is in motion.
When the vehicle is moving and stops at a traffic light, it sends the notification on off.
Your help please.
Your problem is very different. Ignition notifications are generated on the server side. Power notifications are coming directly from the device. So it's completely unrelated to this topic.
Thanks a lot my friend. I understood
Hello. I have a motorcycle that is old and when the engine rpm is low, it sends an ignition off message (but the ignition is on). Is there a way to resolve this?
PROTOCOL GT06
Thanks.