API Endpoint

Download CAN Dump

Returns tab-delimited dump text as attachment.

GETDiagnostics and Logs/api/canview/dump

Reach It

Query Input

seconds default 30 clamped 1..120; bus=all|chassis|haldex.

Body Input

None

Response / Parse

Receive: text/plain attachment filename openhaldex-can-dump.txt

Parse: Useful for support bundles/offline parsing.

Error Behavior

200 success

Example Call

curl -s "http://openhaldex.local/api/canview/dump"

Endpoint-Specific Engineering Notes

This section is intentionally unique for GET /api/canview/dump. Focus area: exporting snapshot diagnostics for offline analysis. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated workflow step rather than a generic HTTP action.

Operational scenario: Generate downloadable dump during reproducible issue windows and store with timestamped notes.

Domain vocabulary: text-dump, attachment-download, snapshot-capture, offline-review, tab-delimited, export-window, capture-archive, trace-file, diagnostic-export, analysis-pipeline.

Common Mistakes for This Endpoint

Practical Validation Pattern

  1. Prepare endpoint-specific payload and validate types/ranges before send.
  2. Execute GET /api/canview/dump and capture status code + raw response.
  3. Parse response and apply only validated fields to UI state.
  4. Run a follow-up read (usually /api/status) to verify runtime convergence.
  5. Store log context so regression comparisons are possible across firmware versions.

Reference Snippet

window.location='/api/canview/dump';

Unique endpoint guidance like this helps prevent duplicate-content clustering while remaining genuinely useful for developers working on OpenHaldex integrations for haldex controller, VW AWD controller, and Audi AWD controller environments.

Project Backlinks

Try the OpenHaldex Firmware Demo

Preview the real OpenHaldex firmware UI in your browser with simulated live CAN traffic and interactive pages for tuning, diagnostics, logs, setup, and OTA workflows.

Open firmware demo