Startek protocol - driverUniqueId after event Swiping Card

Theerayuttu14 days ago

Startek protocol, refer server log data when event swiping card (event code 53) it continue sending driverUniqueId data every position message (in end of message) even if it is not event code 53 until Ignition is off or swiping card again then to stop send. but in report data not capture driverUniqueId every message. can we modify to capture driverUniqueId in every position message?

log data :

2024-12-09 13:32:17  INFO: [Tc62axxxxx: startek < xxxxxxxx] 26264b3139392c3836383832353036343238323034302c3030302c35332c33313030202031202036313030303534312020313038303020203f2c3234313230393036333231372c412c31332e3830393635362c3130302e3535383235352c31342c302e392c302c302c36372c313536302c3532307c347c413431387c30303841414333462c33312c30303030303042442c30322c30302c303444427c303137317c303030307c303030302c3133312c2c2c2c33313030202031202036313030303534312020313038303020203f31300d0a
2024-12-09 13:33:02  INFO: [Tc62axxxxx: startek < xxxxxxxx] 26264c3137312c3836383832353036343238323034302c3030302c302c2c3234313230393036333330322c412c31332e3830393635362c3130302e3535383235352c31342c302e392c302c302c36372c313536302c3532307c347c413431387c30303841414333462c33312c30303030303042442c30322c30302c303445337c303137317c303030307c303030302c3133312c2c2c2c33313030202031202036313030303534312020313038303020203f46450d0a
2024-12-09 13:34:02  INFO: [Tc62axxxxx: startek < xxxxxxxx] 26264d3137312c3836383832353036343238323034302c3030302c302c2c3234313230393036333430332c412c31332e3830393635362c3130302e3535383235352c31342c302e392c302c302c36372c313536302c3532307c347c413431387c30303841414333462c33312c30303030303042442c30322c30302c303445417c303137307c303030307c303030302c3133312c2c2c2c33313030202031202036313030303534312020313038303020203f30450d0a

driverUniqueId data not in event swiping card:

Screenshot 2024-12-09 140755.png

Report not capture continue driverUniqueId:

Screenshot 2024-12-09 141112.png

Anton Tananaev14 days ago

Probably need some code changes.