Driver RFID
There are many different versions of Meiligao protocol. I guess RFID is not supported for this particular one. Do you have protocol documentation?
Anton emailed you TOPTEN GPRS Communication Protocol V5.0_20170518 (2).pdf
Thanks
I found the problem in your message. Odometer is supposed to be 9 digits, but it your case it looks like it's only 6. I would recommend contacting device vendor about this issue.
Thanks Anton, I will follow up. Not expecting much help from manufacture but you never know.
Then there were 7 instead of 6 or 9, with no RFID reading. A different device but same manufacturer.
Response so far:
"I talked with engineer. He says it's ok if it's only 6 characters, as long as the odometer is correct. Is the value of odometer correct?"
Original Hex:
242400726578902405844099553036303331372e3937382c412c343632332e313332312c4e2c30373932342e323437322c572c303030302c3030302c3230313231372c2c2a31437c31312e357c3139347c303030307c333939302c303030307c313136323030307c30303030303007e00d0aDecoded Hex:
$$rex$@U060317.978,A,4623.1321,N,07924.2472,W,0000,000,201217,,*1C|11.5|194|0000|3990,0000|1162000|000000àI have implemented a workaround.
Thank you Anton,
Latest Traccar 3.15, TopTen TK228, MeiligaoProtocol
So according to MeiligaoProtocolDecoder.java RFID is supported, I can see in the logs the RFID ID, but I do not see it in the database:traccar:positions.
Orginal Hex:
Decoded Hex:
003148is the id, but if you inquiry the fob there is 2 extra zeroes:00003148, I have entered it as driver unique id as003148as that is what the log sees.I guess I should add that this is an OBDII, setup on bench not sending OBDII information in case that affects positioning of bytes.