Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Subaru Fingerprinting Issues
See original GitHub issueDescribe the bug
I’ve noticed that my car that previously FP’d as SUBARU IMPREZA 2017 is now being recognised as mock or SUBARU FORESTER 2019.
Here’s a dump of my carFw: They’re in slightly different orders, but all addresses are accounted for and the fw versions match between all three
SUBARU IMPREZA 2017 Route (Actual car): dc30ef2ad294a732|2022-04-04–13-04-36 SUBARU FORESTER 2019 Route: dc30ef2ad294a732|2022-04-05–09-45-30 mock: dc30ef2ad294a732|2022-04-05–08-31-18
What hardware does this issue affect?
comma three
Which car does this affect?
Subaru Impreza 2017
Provide a route where the issue occurs
dc30ef2ad294a732|2022-04-05–09-45-30
openpilot version
b2b6205e252b5291a953dd94c5524715b1f8f444
Additional info
No response
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@sshane Worked a treat mate, even with the CAN fingerprints removed.
Also looks like we’ll have to delete the remaining CAN fingerprints #24195. Fortunately, not too many users are still fingerprinting with CAN.