New 4G OBD2 GPS device with DTC support C005, cant connect with Huabao on 5015
Do you have logs?
I do, but I dont see anything trying to connect. So I'm confused. Even if it had a different protocol, it should still show messages in the log? (I have several other devices, but I remember there was an error message before for either not having the device ID or not using the right protocol port). If it had the wrong port it should show in there correct?
The odd thing is that all I have to do is change the IP/port to their server and it works. So it must be sending some messages, I just dont see anything in the log.
Have you followed the troubleshooting guide?
Thanks that looks helpful. I have other devices using port 5015, I believe, because it says huabao in the logs. Yes, the Sinotrack 902Ls use it.
I tried the port checking with the traccar page and it says closed (probably because of my firewall), but I tried it with nc -v x.x.x.x 5015 from my machine and it says "succeeded".
I think step 4 says contact device vendor if port is open, but has no messages. They sent me the docs linked above for their device.
How are your devices sending data if the port is blocked by firewall?
They only allow connections from certain IPs on that port. I tested it with allowing all IPs the other day. I will try again.
It says "open" from the Traccar tool now. I'll check the logs again in another couple of minutes.
OK, if you are sure that firewall is not a problem, then it simply means that your device is not sending anything to the server. Device issue.
So somehow, by setting the IP to their server en.aika168.com, it starts sending messages? That seems odd, but the only explanation. I dont know why the vendor would instruct me to set the protocol and give me the docs then.
2022-02-14 18:43
Also, I cant get it to communicate with my own server to test the trouble codes with it.
Hi John. Have you integrated our communication protocol with your server?
Which protocol is it?
it is the JT808 communication protocol,
you need to integrate your server with it and then point the device to your server ip and port.
OBD data example_Feifan GPS 20210310.docx
JT T808-2013 OBD2 PROTOCOL.docxWould this be it?
2022-02-17 15:38:10 INFO: [62647566] disconnected
2022-02-17 15:38:10 WARN: [62647566] error - Connection reset by peer - IOException (...)I'll try switching it back to their server, to exclude if its an intermittent data connection issue.
Would this be it?
You need to see some actual HEX data. This could be anything, including your port test.
It is connecting by SMS, so I dont know why data would be a problem, but checking..
I have a ton of HEX data for my other devices, but nothing that looks like its missing an id. I think there is an error message when it finds data without an id.
For example:
2022-02-17 15:59:41 INFO: [d7719204: huabao > x.x.x.x] HEX: 7e80010005019171951153000107ce010200797eI have tried with the id set and unset in the GUI. And also grepped for the last 4 digits of the id.
The example you provide is data from server to device. See the arrow direction.
That is true: here is an example going the other way
2022-02-17 16:04:10 INFO: [f26dc244: huabao < x.x.x.x] HEX: 7e0002000001917195115307d5e67eLots of log data. Would send if I could scrub it.
The APN is locked. I cant change it, but it works with TMobile at least.. I wonder if the IP or Port are locked too. I will ask the vendor. Their server and port uses 27.aika168.com:8185.
No they wouldnt change in the SMS response if they were locked.
Okay, its not connecting to their server right away. So Im going for a drive in case the SMS reception is different than the GPRS data.
Hello, I'm running several Coban 306A OBD2 devices, along with some Sinotrack 906W and 902L-4G OBD2 devices. Unfortunately, the latter doesnt have DTC engine code alerts, and the ODB2 devices are 3G and that service will by sunsetted at some point by US telcoms. So I am testing a new 4G device called COO5, Alibaba link below. It looks very similar to the 902L, except I cant get it to connect. I did connect to their server en.aika168.com, so I know the SIM data is fine.
I asked the seller what protocol it uses and he said JT808 and sent the two docs linked below. The search on this forum said it should be Huabao on 5015, but that doesnt work. I've tried 5013, 5023, and others. I tried comparing to the Huabao protocol docs from this site, but one says its for JT702/JT70, and couldnt see if they are different.
Could someone look if JT808 from the C005 seller can work with Huabao? Thank you
JT T808-2013 OBD2 PROTOCOL.docx:
https://clouddisk.alibaba.com/file/downloadFile.htm?spm=a2706.im-chat.0.0.4f711f8d1qz0ki&appkey=OneChat&id=746248530&parentId=652542651&secOperateAliId=MC1IDX1nJHw40IJswS8gLvBsTITocVyDs_trJNt10n49-aAOk0yi5sF1fCD6gUZZYU_j2ZO
OBD data example_Feifan GPS 20210310.docx:
https://clouddisk.alibaba.com/file/downloadFile.htm?appkey=OneChat&id=747682791&parentId=652542651&secOperateAliId=MC1IDX1GIm1LH8dxg8NL19yCXL3uA7aVx2nbupXPJuoUmoai8cRxBMhk4E7h2Iii7_0ly_h