Actions
Bug #176
closedWrong transponder detected on MRC lapcounter
Status:
Closed
Priority:
Normal
Assignee:
Category:
Lap counter
Target version:
Start date:
03/11/2023
Due date:
% Done:
0%
Estimated time:
Description
It's not reproducible (same conditions won't reproduce the issue) but it's proved sometimes a lap message containing a transponder code fires a detection with partial data of a previous transponder and adding some digit (0/1..)
Example
0,045938EA8D1090,11739776#0A
00:01:06.520 Mini Race Challenge register Car: 040; 0 ms; 0 (MRC)ms
00:01:06.526 DETECCION. Coche (tx=040) fuera de carrera
It should decode 045938EA8D1090
Updated by Jesús M. Broceño about 1 year ago
- Status changed from New to Feedback
Additional log added to the protocol decoder. It has been refactored to prevent object re-usage.
Updated by Jesús M. Broceño about 1 year ago
- Status changed from Feedback to Closed
Updated by Jesús M. Broceño about 1 year ago
- Related to Bug #181: Ghost laps generated on some lapcounters added
Actions