Ensure checksums and counters match between carState and safety
Open
car safety
- Dominant language
- Python
- Stars
- 3.4k
- Forks
- 2.3k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 38
Description
A counter or checksum can be defined in just the DBC (and checked or set in the CANPacker/CANParser) but not in the respective safety mode. Or vice-versa.
Let's setup a test to ensure they match (including the full range) and fix any mismatches.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the carState definitions, DBC entries, CANPacker/CANParser handling, and the corresponding safety modes. Compare which counters and checksums each side defines or checks across their full ranges, then run the new consistency test. Done means the test passes and any reported mismatches are corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100