Diagnose » Historie » Version 2
Maximilian Seesslen, 10.01.2024 15:40
| 1 | 1 | Maximilian Seesslen | h1. Diagnose |
|---|---|---|---|
| 2 | |||
| 3 | * RTC drift |
||
| 4 | |||
| 5 | The drift of intern RTC is enormous. On CANRec its running way to fast (LSE not even enabled? and not used by RTC?). |
||
| 6 | The calibration is capable to adjust several seconds per month, not per day. |
||
| 7 | Not sure if an per-device config is even necessary or if it is an per type thing. |
||
| 8 | |||
| 9 | CANRec can request time values periodically from all devices. It can only compare it to the own clock, so this is not usefull. |
||
| 10 | Cordyceps can analyse this. It has a "real" working RTC form the computer. |
||
| 11 | 2 | Maximilian Seesslen | |
| 12 | h2. Events |
||
| 13 | |||
| 14 | There is no logging available from devices that are only connected via CAN. The heartbeat "Warning" is nice. But useless as long as |
||
| 15 | the user does not know whats going on. |
||
| 16 | An event has to be send via CAN so at least Cordyceps can show the reason of warning. |
||
| 17 | |||
| 18 | Each warning needs to handle an Event-code additionally. Having it in the logging would be nice and clean for the using code. |