Micodus MV710G voltage
Do you have the protocol documentation for your device?
Not yet. Have just requested the manufacturer, hope they'd respond.
Hi Anton! I've got the documentation for Micodus devices: https://drive.google.com/file/d/1QliuWpScGtZedV9DBuFGNox0kFsPECY9/view?usp=sharing
It would be nice to have voltage and alarms status decoded by Traccar. Also I see my devices seem to go offline sometimes. May heartbeat processing help solving this?
You need to investigate why it's happening.
Yeah, would look into it. But does Traccar server process hearbeat messages or just ignores them?
Actually it's not a huge problem in my case as I'm getting device updates continuously. But some times I also get Device offline alerts and Device online right after that. That's a bit annoying but does not affect me much.
Depends on the protocol. If heartbeat includes some valuable data, it will be decoded.
Hi Anton!
Just to remind on my query: is there any chance for voltage and alarm to be implemented in Traccar as per protocol documentation?
Here is the doc: https://drive.google.com/file/d/1QliuWpScGtZedV9DBuFGNox0kFsPECY9/view?usp=sharing
There are two possible options:
- You submit a feature request through GitHub and wait. The backlog is long, so most likely it will only get prioritized if multiple people request the same thing.
- Use out professional services offering.
Got it, thanks! Just submitted a feature request.
Were you able to customize your protocol alerts? And does the MV710G lock and unlock work?
Anton just to report to some attribute to use for Huabao locking and unlocking to work?
I will share some log packages after the block exit!
2024-05-28 01:35:31 INFO: [f0d53113: huabao > 62.151.183.54] HEX: 7e8001000501917586542000010fc6020000597e
2024-05-28 01:35:31 INFO: [f0d53113] id: 019175865420, time: 2024-05-28 01:35:31, lat: -20.13966, lon: -40.28807, course: 338.0
2024-05-28 01:35:36 INFO: [f0d53113] id: 019175865420, command type: engineStop sent
2024-05-28 01:35:36 INFO: [f0d53113: huabao > 62.151.183.54] HEX: 7e810500010191758654200001f0637e
2024-05-28 01:35:42 INFO: [f0d53113: huabao < 62.151.183.54] HEX: 7e020000360191758654200fc7000000000000000f01334e8b0266bf46002d0000015224052809354201040000000030011931011257080000000000000000820200792e7e
2024-05-28 01:35:42 INFO: [f0d53113: huabao > 62.151.183.54] HEX: 7e8001000501917586542000010fc7020000587e
2024-05-28 01:35:42 INFO: [f0d53113] id: 019175865420, time: 2024-05-28 01:35:42, lat: -20.13966, lon: -40.28807, course: 338.0
2024-05-28 01:35:45 INFO: [f0d53113: huabao < 62.151.183.54] HEX: 7e000200000191758654200fc8d27e
2024-05-28 01:35:45 INFO: [f0d53113: huabao > 62.151.183.54] HEX: 7e8001000501917586542000010fc8000200577e
2024-05-28 01:35:54 INFO: [f0d53113: huabao < 62.151.183.54] HEX: 7e020000360191758654200fc9000000000000000f01334e8b0266bf46002d000001522405280935530104000000003001193101115708000000000000000082020079327e
2024-05-28 01:35:54 INFO: [f0d53113: huabao > 62.151.183.54] HEX: 7e8001000501917586542000010fc9020000567e
2024-05-28 01:35:54 INFO: [f0d53113] id: 019175865420, time: 2024-05-28 01:35:53, lat: -20.13966, lon: -40.28807, course: 338.0
2024-05-28 01:36:05 INFO: [f0d53113: huabao < 62.151.183.54] HEX: 7e020000360191758654200fca000000000000000f01334e8b0266bf46002d000001522405280936030104000000003001193101115708000000000000000082020079627e
Hello, I've the same "request" for Micodus MV710G and MV930G. Do you have the link to your github request ?
hi, also have the same request for micodus MV710g,MVG810g and MV610g
Hi there. I'm having several Micodus MV710G, working with Huabao protocol (port 5015). Micodus app, among other parameters, shows car voltage. Is there any possibility for the voltage to be decoded and displayed in Traccar?