Reach It
- Method:
POST - Path:
/api/curve/speed - Base URL:
http://openhaldex.local(or controller IP) - Response format:
JSON ok/debugCaptureActive/disableController.
API Endpoint
Stores SPEED curve points.
POST/api/curve/speedhttp://openhaldex.local (or controller IP)JSON ok/debugCaptureActive/disableController.None
JSON points[1..12], each {x,lock}; x 0..300, lock 0..100, x strictly ascending.
Receive: JSON ok/debugCaptureActive/disableController.
Parse: Sort x and avoid duplicates.
400 invalid points/range/order; 200 success
curl -s -X POST "http://openhaldex.local/api/curve/speed" -H "Content-Type: application/json" -d '{...}'
This section is intentionally unique for POST /api/curve/speed. Focus area:
speed-axis curve updates with attention to parking and cruise transitions. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated
workflow step rather than a generic HTTP action.
Operational scenario: Write revised speed points, then road-test low-speed turns and mid-speed exits with logs enabled.
Domain vocabulary: launch-rollout, velocity-slope, speed-anchor, coasting-transition, ramp-entry, taper-point, progressive-falloff, bind-avoidance, turn-in, exit-speed.
POST /api/curve/speed and capture status code + raw response./api/status) to verify runtime convergence.await fetch('/api/curve/speed',{method:'POST',headers:{'Content-Type':'application/json'},body:JSON.stringify({points})});
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.