Aplicom D-protocol and CAN messages in Traccar
Please provide message samples and protocol documentation.
Hi Anton,
The protocol is here https://dl.dropboxusercontent.com/s/nxn0fsxu1zweg7r/S100300_Aplicom_D_protocol.pdf.
Since it's a binary protocol it's difficult to parse by humans.
Greetings,
I have debug logs enabled and looking at the logs coming in. Is there any way to know or see if the data coming in after it has been parsed?
Hi any help would be appreciated! Thanks!
I'm still waiting for HEX samples.
Binary data
434946010A0100075253F85F0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000FEEA0000FEE90000F0030000F0040000FEF10000FEF20000FEF50000FEFC0000FEC10000FEE500
Sorrym this didn't paste too well. I can't attach a PDF of JPEG here that preserves the formating
Looks like C message type is not supported at the moment. Send an email to support address to discuss implementation, if you are interested in sponsoring the work.
By the way, document you provided doesn't have the information for this message format, as far as I can see. So you would need to get documentation as well.
Hi Anton,
This is still the D-protocol. Is that what you meant?
Thanks,
Alp
No, it's not, as far as I can see.
Greetings,
We're using Aplicom A9 IPEX for sending data to the traccar server we setup. Everything is working fine with the standard data coming in. Though we are also sending CAN messages that being watched on the CANbus. It's unclear whether Traccar can compute/parse these other attributes that are being sent.
Appreciate the support.