Chinese Clone: Receiving data but not getting processed by traccar

Here:

https://www.traccar.org/donate/

Thanks

Seems it is still not working unfortunatly:

DEBUG: [C8C8DF66: 5013 < 62.140.137.117] HEX: 2a48512c3335333530353232313236343530372c56322c3130303232302c302c353233382e32363235392c4e2c30303530372e33333938332c452c302e32352c302c3238303931372c46464646464646462c63632c32382c202064622c6437356223200d0a

Not getting a valid log entry..

Have you made a build from latest code?

No did not build, only downloaded latest binaries. I will find someone to build the latest from source. thanks

Hi, Apologies for barging in an existing thread; however i find the issue to be related hence the response. I have a Chinese clone; similar issue with h02 protocol; the device identifier also seems to be incorrect, hex dump of the device as follows
Would appreciate inputs / advice / suggestions on the same please.

Thanks in advance

HEX: 533136382338363131313830313031303433373523303030382330303762234c4f43413a4c3b43454c4c3a322c3139342c35632c3536372c313435312c32322c3536372c313435322c643b47444154413a562c302c3137303932393036333935382c302e3030303030302c302e3030303030302c302c302c303b414c4552543a303030303b5354415455533a3130302c3130303b574946493a3024

This protocol doesn't seem to be supported yet. Do you have protocol documentation?

decoded output

S168#861118010104375#0008#007b#LOCA:L;CELL:2,194,5c,567,1451,22,567,1452,d;GDATA:V,0,170929063958,0.000000,0.000000,0,0,0;ALERT:0000;STATUS:100,100;WIFI:0$

have tried v680, tlt2h, meitrack, and disha protocls, seems i am doing something wrong here, would appreciate your views and inputs

Hi,

Thanks for the quick revert; i have tried to get this from the vendor; will keep you posted on the same.

Hi Anton

Unfortunately we are not able to compile from source. Is there a idea when it will be in the next release?

No.

ok we are getting this 403 error, and this in the logs. Not sure if it is the cause.

traccar_1  | INFO 9/28/17 2:33 PM: liquibase: ./schema/changelog-master.xml: changelog-3.8::changelog-3.8-dropuniquetoken::author: Change set changelog-3.8::changelog-3.8-dropuniquetoken::author failed, but failOnError was false.  Error: Constraint "UK_USER_TOKEN" not found; SQL statement:
traccar_1  | ALTER TABLE PUBLIC.users DROP CONSTRAINT uk_user_token [90057-196] [Failed SQL: ALTER TABLE PUBLIC.users DROP CONSTRAINT uk_user_token]
traccar_1  | INFO 9/28/17 2:33 PM: liquibase: Successfully released change log lock

That's not an issue. You can safely ignore it.