Ticket

Project	RCM Ultimate
Summary	Recovery by decoder -> do not reset lap memory
Sequence	1602
Classification	Change Request
Priority	High
Status	Done
Kickoff date	Oct 27, 2014
Maturity date	Oct 27, 2014
Responsible
Version	2.2.1
Expense	0
Description	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

Timestamp	Who	Modification
Oct 27, 2014 1:20:03 PM		Ticket created
Oct 27, 2014 1:20:19 PM	Felix Romer	Field: Status Old value: Opened New value : Running
Oct 27, 2014 5:29:42 PM	Felix Romer	Field: Status Old value: Running New value : Done