Closed MoreTore closed 1 year ago
This is probably similar to #25398 except the unfinished query (the one with the invalid consecutive frame index) is stalled at a different layer of the UDS/FP stack.
Can you identify which query is failing at that stage? Run fw_versions.py --debug
with openpilot shutdown to watch the process. Is it critical to the Mazda fingerprint? I think there were some ISO-TP/UDS timing compliance fixes (mainly for HKG) that might be of value for your multipart response issue, I can't recall if those fixes are part of 0.9.0.
Firstly this is a fork, and this car is unsupported in master currently. But it looks like your car is fuzzy matching, not exact matching with its FW.
We sort the brands to query FW versions by likelihood (based on present ECUs) and we break out of the loop whenever we get an exact match. If the car only fuzzy matches, it will run through everything for the chance that the second likeliest brand is the correct brand, and we get an exact match there.
Your fwdCamera ECU is missing on your recent routes, I'd check why that is.
Going to re-open until I check the timeouts to make sure they're working properly. @MoreTore Can you also connect your device to WiFi to upload logs? https://github.com/commaai/openpilot/pull/25897 may be related
So the can gateway is not on the camera, its on the BCM. Not sure if that matters since its using the OBD port. But anyways 164080f7933651c4|2023-02-16--08-52-15 should be uploaded.
@sshane can we close this?
yea this is my fault
Describe the bug
Finger printing has been slow when using 9.0 for months. I thought it was just my car but it seems to work fine on my C2 with 0.8.13. I have been putting off reporting this issue. This issue only happens after clearing the cached fingerprint.
Here is the cleaned up tmux output.
Provide a route where the issue occurs
164080f7933651c4|2023-02-16--08-52-15--0
openpilot version
0.9.0.x
Additional info
No response