Write a troubleshooting post people can answer
Turn an observation into a clear, reproducible support question.
Identify your setup
Choose your vehicle make, then enter model, year, device and software project. Include the branch and version in the post. A report for one fork may not describe upstream openpilot.
Describe one issue
State what you expected and what happened instead. Copy the exact error message. Mention recent software, mount, cable or vehicle changes. Distinguish things you measured from guesses about the cause.
Point to the relevant evidence
Use an existing observation or route segment. Include the relevant time and conditions; do not repeat hazardous behavior to produce a demonstration. Follow upstream feedback instructions if reporting directly to openpilot, or the fork maintainer’s process for a fork.
Review before sharing
Remove credentials, private locations and unnecessary camera footage. Check whether a route link exposes more than the segment you intended. Share large route data through the appropriate service rather than trying to upload a whole drive here.
Close the loop
Reply with the outcome and mark a helpful answer as accepted. If an upstream issue is opened, link it so later readers can follow progress.