opened
quade1664
username_0
I've noticed an issue with devices that have an imei starting with zero
ones without a leading zero in the IMEI work fine

here is the logs
019-06-07 12:28:50  INFO: [3b1fd56f] connected
2019-06-07 12:28:56  INFO: [3b1fd56f: 9181 < 194.54.172.13] HEX: 504124383633303833303330363032313234243230244150
2019-06-07 12:28:56  INFO: [3b1fd56f: 9181 > 194.54.172.13] HEX: 504124383633303833303330363032313234243230244150
2019-06-07 12:30:43  INFO: [1556ded3] connected
2019-06-07 12:30:43  INFO: [1556ded3: 9181 < 194.54.172.13] HEX: 504124303132323037303036313435303436243230244150
2019-06-07 12:30:43  INFO: [1556ded3: 9181 > 194.54.172.13] HEX: 504124303132323037303036313435303436243230244150
2019-06-07 12:30:48  INFO: [1556ded3: 9181 < 194.54.172.13] HEX: 504124303132323037303036313435303436243230244150
2019-06-07 12:30:48  INFO: [1556ded3: 9181 > 194.54.172.13] HEX: 504124303132323037303036313435303436243230244150
2019-06-07 12:30:50  INFO: [1556ded3: 9181 < 194.54.172.13] HEX: 504124303132323037303036313435303436243232244150
2019-06-07 12:30:50  INFO: [1556ded3: 9181 > 194.54.172.13] HEX: 504124303132323037303036313435303436243232244150
2019-06-07 12:30:55  INFO: [1556ded3: 9181 < 194.54.172.13] HEX: 5041243031323230373030363134353034362444233139303630372331323331353723312333372e393437303837233032332e373638363639233030302e3030233331342e362330303030302e302334313034233030302338244150
2019-06-07 12:31:54  INFO: [1556ded3: 9181 < 194.54.172.13] HEX: 5041243031323230373030363134353034362444233139303630372331323332353323312333372e393437303733233032332e373638363339233030302e3030233331342e362330303030302e302334313034233030302338244150
2019-06-07 12:33:05  INFO: [1556ded3: 9181 < 194.54.172.13] HEX: 504124303132323037303036313435303436243232244150
2019-06-07 12:33:05  INFO: [1556ded3: 9181 > 194.54.172.13] HEX: 504124303132323037303036313435303436243232244150
2019-06-07 12:33:08  INFO: [1556ded3: 9181 < 194.54.172.13] HEX: 5041243031323230373030363134353034362444233139303630372331323334303923312333372e393437323333233032332e373638373934233030302e3030233331342e362330303030302e302334303636233030302338244150
2019-06-07 12:34:03  INFO: [1556ded3: 9181 < 194.54.172.13] HEX: 5041243031323230373030363134353034362444233139303630372331323335303423312333372e393437313333233032332e373638373337233030302e3030233331342e362330303030302e302334313034233030302338244150


Im not 100% sure if its an issue with the leading zero, but it the only thing thats different.
c2stek protocol issue
issue
created
conde000011100
username_1
What protocols?
comment
created
Arismane
username_2
I seem to have the same problem with one MT20 unit form C2Stek, that serial doesn't start with zero. I cannot read data sent on web platform although traccar gets my data if I check track-server.log. Is there any trick for adding the serial inside platform? Thanx
comment