Reach It
- Method:
POST - Path:
/api/canview/capture - Base URL:
http://openhaldex.local(or controller IP) - Response format:
JSON
API Endpoint
Enable safe capture state or restore previous state.
POST/api/canview/capturehttp://openhaldex.local (or controller IP)JSONNone
JSON: {"active":true|false}
Receive: JSON: ok,active,disableController,broadcastOpenHaldexOverCAN
Parse: Enable forces STOCK/controller-off safe profile.
400 invalid json; 200 success
curl -s -X POST "http://openhaldex.local/api/canview/capture" -H "Content-Type: application/json" -d '{...}'
This section is intentionally unique for POST /api/canview/capture. Focus area:
toggling capture session state with safety-aware control behavior. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated
workflow step rather than a generic HTTP action.
Operational scenario: Enable capture for diagnostics, then restore normal control and verify state rollback after session end.
Domain vocabulary: capture-toggle, session-start, session-stop, controller-bypass, broadcast-force, safe-observe, trace-session, capture-control, analyzer-transition, revert-state.
POST /api/canview/capture and capture status code + raw response./api/status) to verify runtime convergence.await fetch('/api/canview/capture',{method:'POST',headers:{'Content-Type':'application/json'},body:JSON.stringify({active:true})});
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.