Atrack ASCII protocol does not work with driver id field

Hey Anton,

Implementing iButtons with my AL11 and AK7s. I've assigned drivers and assigned them to the device, device is reporting the iButton, traccar is not parsing it. iButton field is marked with the *'s

@P,03F5,402,121,35696ddddd31165,1546810193,1546810194,1546810194,xxx,xxxxx,54,2,0,9,1,0,0,0,*1858AE010000*,2000,2000,,%CI%FL%ML%VN%PD%FC%EL%ET%AT%MF%MV%BV%DT%GN%GV%ME%RL%RP%SA%SM%TR%IA%MP,0,0,myvinhere,0,0,0,14,251,78,116,40,0,00A30016040500A30016040500A30016040500A30016040400A30016040400A30016040400A30016040600A30016040500A30017040500A300160406,007CFE7C03BC,35ddddd075931165,0,0,12,0,18,13,0

You would need to provide protocol documentation.

You have the whole atrack protocol in a pdf for both binary and ascii message formats. I provided it to you when I paid for you to add it to traccar.

Please provide original unmodified HEX sample.

40502c393439332c3430322c3134332c3335363936313037353933313136352c313534363833303135302c313534363833303135312c313534363833303135312c2d38383432393230392c34343237313135342c35342c31302c302c31302c312c302c302c302c3138353841453031303030302c323030302c323030302c1a2c25434925464c254d4c25564e25504425464325454c254554254154254d46254d5625425625445425474e254756254d4525524c25525025534125534d255452254941254d502c302c302c3254314b523332453238433730363138352c302c312c302c372c3235312c38392c3131382c34312c302c3030413530303141303430383030413530303141303430423030413530303141303430433030413530303141303430393030413430303143303430443030413530303139303430393030413630303139303430393030413430303142303430423030413530303141303430393030413730303141303430451a2c3030384346453743303343341a2c3335363936313037353933313136352c302c302c31322c302c31382c352c300d0a

It is three fields before the AT$FORM field. This driver id was 1858AE010000

Added support for driver id:

https://github.com/traccar/traccar/commit/90a88ff7584c9d4200f2a32800bf6eaf417955ac