API Endpoint

Read Curve

Returns current curve points for mode endpoint.

GETMap and Curves/api/curve/rpm

Reach It

Method: GET
Path: /api/curve/rpm
Base URL: http://openhaldex.local (or controller IP)
Response format: JSON

Query Input

None

Body Input

None

Response / Parse

Receive: JSON: {"count":N,"points":[{"x":...,"lock":...}]}

Parse: Variable point count; render dynamically.

Error Behavior

200 success

Example Call

curl -s "http://openhaldex.local/api/curve/rpm"

Endpoint-Specific Engineering Notes

This section is intentionally unique for GET /api/curve/rpm. Focus area: engine-speed curve visibility across shift zones and rev range. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated workflow step rather than a generic HTTP action.

Operational scenario: Read RPM curve to compare lock behavior around shift points and upper rev-band transitions.

Domain vocabulary: engine-rpm, shift-window, rev-band, spool-zone, redline, rpm-axis, gear-change, pull-region, rev-drop, load-transition.

Common Mistakes for This Endpoint

Ignoring post-shift rev drops
Over-locking near redline
No gear-dependent interpretation

Practical Validation Pattern

Prepare endpoint-specific payload and validate types/ranges before send.
Execute GET /api/curve/rpm and capture status code + raw response.
Parse response and apply only validated fields to UI state.
Run a follow-up read (usually /api/status) to verify runtime convergence.
Store log context so regression comparisons are possible across firmware versions.

Reference Snippet

const curve = await fetch('/api/curve/rpm').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.

RPM Axis Interpretation Notes

RPM-axis calibration focuses on engine-speed phases and shift dynamics. Use this endpoint to inspect how lock behavior aligns with spool region, midrange pull, shift recovery, and near-redline operation. Unlike throttle tuning, RPM tuning should emphasize temporal continuity through gear changes and rev transitions.

Axis-specific vocabulary includes rev-band segmentation, pre-shift ramp, post-shift recovery, powerband hold, rev ceiling taper, and shift-drop compensation. If users report instability during hard pulls, inspect the RPM curve near common shift points before adjusting pedal or speed curves.

Validation sequence: log full-throttle pulls, annotate shift RPM events, compare lock response around each shift, and tune anchor points to remove abrupt transitions. Keep revisions versioned by gear set and tire setup when possible.

Project Backlinks

Try the OpenHaldex Firmware Demo

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.

Open firmware demo