openpilotcommunity
Log inJoin the community
TROUBLESHOOTING · PUBLISHED

Understand routes and share less private data

Find the useful part of a log without publishing an entire journey.

Original author / contributors: Community editorial synthesis; linked comma.ai / openpilot referencesOriginal source ↗

Identify the observation

Record the relevant time, software version and symptom before searching through data. The official logs reference explains route and segment terminology.

Use the appropriate viewer

Open your own routes in comma connect or the tools documented by your software project. Find the smallest relevant portion. Keep your original data intact and prepare a separate, minimal example for public discussion.

Review what a link reveals

A route or video can reveal destinations, number plates, voices, occupants and the inside of your vehicle. Check the sharing controls and actual content before posting. Never include an access token, private SSH key or login credential in a forum message.

Add context beside the evidence

Describe the timestamp, expected behavior, observed behavior and setup. Screenshots help with error messages; a screenshot alone may not explain a driving issue. Use the project’s official reporting channel if maintainers need private logs.

Keep uploads small

This forum accepts scanned photos and limited diagnostic text/CSV/JSON files according to category policy. Full route archives and installers belong with their maintained services, not a renamed forum attachment.

END OF GUIDE Back to the library