Ticket

back to ticket overview

Project RCM Ultimate
Summary Multiloop setup: GPS Lock flag and UTC timestamp on passing records:
Sequence 1603
Classification Bug
Priority Medium
Status Done
Kickoff date Oct 27, 2014
Maturity date Oct 27, 2014
Responsible
Version 2.2.1
Expense 0
Description Question:
What is your recommened way for handling this situation? Should RCM check before starting the heat if the "GPS locked" flag is set and based on this either use the RTC or UTC time during the complete heat independent of the "GPS locked" which is set within the passing records during the heat?

Answer:
We determine at the start of a run according the flag which time to use and keep that selection until the finish of that run. When GPS lock is set we always use UTC even when lock disappears the UTC time is there only referenced according the internal precision clock.

Change history

Timestamp Who Modification
Oct 27, 2014 1:23:08 PM Ticket created
Oct 27, 2014 1:24:21 PM Felix Romer Field: Specification
Old value: Question:

Answer:
We determine at the start of a run according the flag which time to use and keep that selection until the finish of that run. When GPS lock is set we always use UTC even when lock disappears the UTC time is there only referenced acco

New value : Question:
What is your recommened way for handling this situation? Should RCM check before starting the heat if the "GPS locked" flag is set and based on this either use the RTC or UTC time during the complete heat independent of the "GPS locked" which i
Oct 27, 2014 1:24:26 PM Felix Romer Field: Status
Old value: Opened
New value : Running
Oct 27, 2014 5:29:55 PM Felix Romer Field: Status
Old value: Running
New value : Done