Ticket
Projekt | RCM Ultimate |
---|---|
Zusammenfassung | Multiloop setup: GPS Lock flag and UTC timestamp on passing records: |
Sequenz | 1603 |
Klassifikation | Bug |
Priorität | Medium |
Status | Done |
Startdatum | 27.10.2014 |
Fälligkeitsdatum | 27.10.2014 |
Verantwortlich | |
Version | 2.2.1 |
Aufwand | 0 |
Beschreibung | 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
Zeitstempel | Wer | Änderung |
---|---|---|
27.10.2014 13:23:08 | Ticket erstellt | |
27.10.2014 13:24:21 | Felix Romer | Feld: SpecificationAlter Wert: 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 Neuer Wert: 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 |
27.10.2014 13:24:26 | Felix Romer | Feld: StatusAlter Wert: Opened Neuer Wert: Running |
27.10.2014 17:29:55 | Felix Romer | Feld: StatusAlter Wert: Running Neuer Wert: Done |