Sending Dashcam Logs for Analysis

한국어

Automatic Dashcam mode after a suspected impact

While onroad, two consecutive fresh accelerometer samples with a calibrated longitudinal/lateral magnitude of 1.5g (about 14.7 m/s²) trigger an Impact suspected notice, a ten-second countdown, and the existing notification sound. Gravity and mounting orientation are compensated; vertical acceleration alone does not trigger it. Valid sensor, pose, and calibration data are required. Wheel-speed-derived aEgo is recorded only as supporting information.

• Touch anywhere on the screen within ten seconds to cancel. That touch does not activate the controls underneath.
• Without a touch, the device saves Enable openpilot OFF and reboots. Control, including Always Lateral, stops; after reboot, Dashcam mode records without allowing engagement.
• OFF persists through subsequent ignition cycles. To restore control, park safely, enable openpilot in the device settings, and perform the requested restart.
• Recording pauses during reboot. This does not separately lock/save incident footage or upload it automatically.
• A full-screen emergency alert or an unresponsive display that prevents continued notice presentation cancels automatic switching. After cancellation, valid horizontal acceleration must remain below 10 m/s² for one second before another impact can trigger a new notice.

1.5g is an experimental threshold, not confirmation of a collision. Rough roads, mount impacts, and device drops can cause false triggers; sensor limits and short impulses can cause missed impacts. Vehicle detection rates, false triggers, display, sound, and physical reboot remain unvalidated. The notification respects existing volume and mute settings.

When you ask a Carrot support specialist to analyze abnormal behavior, use Logs > Dashcam in Carrot Web to find and upload the affected time range. A dashcam upload can provide vehicle-state and control-decision data in addition to the visible road video.

WARNING

Operate Carrot Web only after parking safely. While driving, do not search for or select logs; remember the occurrence time and symptom instead.

Record these details first

Note as much of the following as possible:

• Date and time, preferably accurate to the minute
• Observed symptom, such as unexpected deceleration, failure to start, lane departure, or an alert sound
• Conditions, including road type, approximate speed, lead vehicle, curve, merge, congestion, or signal state
• Whether it repeated and any driver intervention with the brake, accelerator, steering wheel, or buttons
• Vehicle, current branch, and commit, available from Tools > Info

“At about 14:32, the vehicle unexpectedly decelerated from about 80 km/h as a car merged from the right, and I disengaged with the brake” is much more useful than “It behaved strangely.”

Fastest method: send a symptom that just occurred

1. Park safely and wait for the drive to finish.
2. Open http://device-IP:7000 in a browser.
3. Open Logs > Dashcam.
4. From the top-right Logs menu, select Upload recent 5 logs.
5. Review the file count and upload size, then confirm.
6. When it finishes, verify that the successful count equals the total and select Copy.
7. Send the copied result with the symptom details to the designated support specialist.

Recent-log upload selects the newest completed segments regardless of the visible sort order. Recent 5 is recommended for a typical one-time event because it usually includes useful context before and after it.

Selection	Appropriate use
Recent 2	The time is certain and upload size must be minimized
Recent 5	A recent one-time symptom or normal analysis request
Recent 10	The exact segment is uncertain or the symptom repeated over a longer period

Find and send an exact range

Dashcam logs are shown as drive cards containing segments of about one minute each.

1. Expand the drive card containing the occurrence date and time.
2. Use the displayed segment times to locate the event.
3. Select a segment to play its video, or use Replay from its menu to inspect it with recorded driving data.
4. Check the affected segment.
5. When possible, also select the segment immediately before and after it. Analysis often depends on what happened around the symptom.
6. Use Upload selected, Select all, or range selection for multiple segments. Range input accepts forms such as 1, 1-3, or 1, 3-5.
7. In the confirmation dialog, review the file count, total size, and mobile-data warning.
8. Start the upload and keep the device online until it completes. You can cancel from the progress dialog if necessary.

A segment that is still recording or has not been finalized cannot be uploaded. If a newly completed segment is not visible, wait briefly. While the Logs page is active, it silently checks for updates about every 10 seconds.

Verify the result and request analysis

If the completion screen shows the same uploaded/total number, all selected files were uploaded. If an entry shows FAILED or the successful count is lower, retry the failed segment.

The result generated by Copy can include device, branch, commit, and per-segment upload information. Each successful segment is shown as a public Synology viewer link. Opening it provides web playback, public files, and ready-to-copy Cabana, PlotJuggler, and JotPluggler commands. Consecutively numbered segments from the same route also receive one combined link that opens the full range.

When the upload job finishes, the device sends the same result report directly to the configured Discord webhook. A Discord notification failure does not undo an already completed log upload; if no notification appears, post the completion screen's Copy result to the channel manually.

Public viewer links do not require a login. Anyone who receives a link can open or forward it. Confirm the selected segments and the Discord channel where the report will be posted, then add the following details when requesting analysis:

Vehicle:
Occurrence date/time:
Symptom:
Speed and road conditions:
Lead or surrounding vehicle conditions:
Driver intervention:
Number of reproductions:
Upload result: (paste the text copied from Carrot Web)
Screen recording: yes / no

Only one upload job can run at a time. If the browser is briefly closed and reopened while the same device-side job is still running, Carrot Web may restore its progress or result. A job ID saved by the browser is verified against the device before it is used, so an already-finished or missing job does not block a new upload by itself. A device-side upload with no activity for 30 minutes is marked failed and released so that it cannot block later uploads.

Include a screen recording when useful

A Carrot Web screen recording helps explain what the driver saw, including HUD, alerts, and visible UI changes.

1. Before driving, select Record on the Drive page.
2. Confirm that the REC indicator appears.
3. After parking safely, select Record again to stop.
4. Open Logs > Screen Record, play the file to confirm the symptom is visible, and download it separately if the specialist requests it.

A screen recording alone may not contain enough data to determine the control cause. For abnormal driving behavior, upload the dashcam logs from the same time first.

Troubleshooting

Symptom	What to check
The latest drive is missing	Confirm that the drive has completely ended, wait briefly, and check the list again.
Recording or incomplete-segment error	Wait for that segment to be finalized, then select it again.
Another upload is already running	Carrot Web rechecks the existing device-side job and restores its progress. If it is genuinely running, wait for it to finish or cancel it. A job with no activity for 30 minutes is released automatically.
Upload stalls or fails	Check the device's internet connection and retry only the failed segment.
Only some files succeeded	Read the completion result and resend the segment containing the failed item.
The required log is gone	Check whether Tools > delete all logs or storage cleanup was used. Deleted logs cannot be restored or uploaded from Carrot Web.

Use the segment menu's qcamera, rlog, or qlog download only when a specialist asks for a particular original file. For a normal analysis request, use Upload Logs or Upload selected.

Privacy and sharing

Uploaded data may include road video, location and vehicle-state logs, device identifiers, vehicle name, branch, and commit information. Recheck the selected time and segments before uploading because a public viewer link remains available to anyone while the files remain on the server. Driver-facing dcamera files are excluded from the public viewer and analysis API.

Related guides

• Carrot Web User Guide
• Understanding Settings

---

Source reference

Reference checked 2026-10-30 · carrot-wip · 10bf0a56.

docs/user/ko/dashcam-log-sharing.md · docs/user/ko/carrot-web.md

The development branch continues to change. Check your device’s branch, commit and current settings together.