Reach It
- Method:
POST - Path:
/api/curve/rpm - Base URL:
http://openhaldex.local(or controller IP) - Response format:
JSON ok/debugCaptureActive/disableController.
API Endpoint
Stores RPM curve points.
POST/api/curve/rpmhttp://openhaldex.local (or controller IP)JSON ok/debugCaptureActive/disableController.None
JSON points[1..12], x 0..10000, 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/rpm" -H "Content-Type: application/json" -d '{...}'
This section is intentionally unique for POST /api/curve/rpm. Focus area:
engine-speed curve updates for pull consistency through shifts. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated
workflow step rather than a generic HTTP action.
Operational scenario: Write RPM points and validate full pull logs to ensure transitions across shifts remain controlled.
Domain vocabulary: rpm-knee, shift-recovery, powerband, rev-mapping, upper-band, midrange-load, gear-handoff, rev-ceiling, accel-band, rpm-sculpting.
POST /api/curve/rpm and capture status code + raw response./api/status) to verify runtime convergence.await fetch('/api/curve/rpm',{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.