Reach It
- Method:
GET - Path:
/api/canview - Base URL:
http://openhaldex.local(or controller IP) - Response format:
JSON
API Endpoint
Returns decoded/raw CAN rows with optional limits and bus filter.
GET/api/canviewhttp://openhaldex.local (or controller IP)JSONdecoded (default 200), raw (default 20), bus=all|chassis|haldex.
None
Receive: JSON: {decoded:[...], raw:[...]} with fields bus,dir,id,...
Parse: decoded[].value may be number or string.
200 success
curl -s "http://openhaldex.local/api/canview"
This section is intentionally unique for GET /api/canview. Focus area:
interactive CAN table retrieval for filtered diagnostics. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated
workflow step rather than a generic HTTP action.
Operational scenario: Read filtered CAN rows for targeted diagnosis instead of full unbounded stream rendering.
Domain vocabulary: frame-table, bus-filter, token-filter, decoded-row, raw-bytes, refresh-window, signal-context, can-inspection, row-limit, viewer-poll.
GET /api/canview and capture status code + raw response./api/status) to verify runtime convergence.const rows = await fetch('/api/canview?limit=200').then(r=>r.json());
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.
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.