Reach It
- Method:
POST - Path:
/api/curve/throttle - Base URL:
http://openhaldex.local(or controller IP) - Response format:
JSON ok/debugCaptureActive/disableController.
API Endpoint
Stores THROTTLE curve points.
POST/api/curve/throttlehttp://openhaldex.local (or controller IP)JSON ok/debugCaptureActive/disableController.None
JSON points[1..12], x 0..100, 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/throttle" -H "Content-Type: application/json" -d '{...}'
This section is intentionally unique for POST /api/curve/throttle. Focus area:
pedal-axis curve updates for smooth drivability and launch behavior. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated
workflow step rather than a generic HTTP action.
Operational scenario: Update throttle points and validate in three states: light cruise, mid-throttle pull, and full-throttle launch.
Domain vocabulary: pedal-threshold, tipout, part-throttle, full-load, torque-request, pedal-smoothing, response-granularity, driver-feedback, launch-pedal, street-calibration.
POST /api/curve/throttle and capture status code + raw response./api/status) to verify runtime convergence.await fetch('/api/curve/throttle',{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.