Ticket

Projekt	RCM Ultimate
Zusammenfassung	Recovery by decoder -> do not reset lap memory
Sequenz	1602
Klassifikation	Change Request
Priorität	High
Status	Done
Startdatum	27.10.2014
Fälligkeitsdatum	27.10.2014
Verantwortlich
Version	2.2.1
Aufwand	0
Beschreibung	Main decoder missed some laps for a driver. I checked the export from a third decoder not connected to any system and found some more laps there. And another not connected decoder also had laps. I wanted to diff these to the main decoder but the main decoder only had the most recent laps. Thus I was unable to match this data. I went to the heat and printed the laps for the driver in question and had to manually check the laps instead of running scripts/tools. Is it really needed to reset the lap memory stored on the decoder with every start of a heat? The protocol supports resending of intervals of the stored laps, and ive seen that you store the id's of each lap. So maybe just request the laps adjacent to the id that you know.

Change history

Zeitstempel	Wer	Änderung
27.10.2014 13:20:03		Ticket erstellt
27.10.2014 13:20:19	Felix Romer	Feld: Status Alter Wert: Opened Neuer Wert: Running
27.10.2014 17:29:42	Felix Romer	Feld: Status Alter Wert: Running Neuer Wert: Done