James Kuszmaul | 9f2f53c | 2023-02-19 14:08:18 -0800 | [diff] [blame] | 1 | namespace frc971.controls; |
| 2 | |
| 3 | // Counters to track how many times different errors have occurred. |
| 4 | table ImuFailures { |
| 5 | // Count of total number of checksum mismatches between the IMU and the |
| 6 | // pico itself. |
| 7 | imu_to_pico_checksum_mismatch:uint (id: 0); |
| 8 | // Count of total number of checksum mismatches between the pico board |
| 9 | // and the raspberry pi. |
| 10 | pico_to_pi_checksum_mismatch:uint (id: 1); |
| 11 | // Total number of dropped/missed messages. |
| 12 | missed_messages:uint (id: 2); |
| 13 | // Total number of messages dropped for any other conditions that can fault |
| 14 | // the zeroer (e.g., diagnostic failures in the IMU). |
| 15 | other_zeroing_faults:uint (id: 3); |
James Kuszmaul | 723e66e | 2023-04-05 21:22:57 -0700 | [diff] [blame] | 16 | // These are the counts for the number of times that we think the pico and imu |
| 17 | // have reset. Note that when the pico resets both of these should increment. |
| 18 | probable_pico_reset_count:uint (id: 4); |
| 19 | probable_imu_reset_count:uint (id: 5); |
| 20 | // This counter is used for things that look like resets (i.e., a large gap in |
| 21 | // IMU readings) but where the IMU data counter and pico timestamp offsets |
| 22 | // still look correct. |
| 23 | unassignable_reset_count:uint (id: 6); |
James Kuszmaul | 9f2f53c | 2023-02-19 14:08:18 -0800 | [diff] [blame] | 24 | } |