API Endpoint

Read Curve

Returns current curve points for mode endpoint.

GETMap and Curves/api/curve/speed

Reach It

Method: GET
Path: /api/curve/speed
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/speed"

Endpoint-Specific Engineering Notes

This section is intentionally unique for GET /api/curve/speed. Focus area: speed-axis curve visibility for coast and high-speed behavior tuning. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated workflow step rather than a generic HTTP action.

Operational scenario: Inspect curve points before tuning low-speed disengage and high-speed taper behavior.

Domain vocabulary: kmh, mph, coastdown, highway-ramp, parking-lot, wheel-bind, velocity-axis, speed-knee, decel-zone, cruise-window.

Common Mistakes for This Endpoint

Confusing units between UI and firmware
Ignoring low-speed bind symptoms
Flattening high-speed taper unintentionally

Practical Validation Pattern

Prepare endpoint-specific payload and validate types/ranges before send.
Execute GET /api/curve/speed 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/speed').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.

Speed Axis Interpretation Notes

Speed-axis calibration is primarily about vehicle kinematics and driveline comfort. For OpenHaldex users, this page should be interpreted through scenarios like parking-lot steering lock, rolling u-turns, off-throttle coastdown, and steady-state highway cruise. In those situations, the curve determines how quickly lock demand rises or falls as speed changes through low, mid, and upper ranges.

Use this endpoint to verify velocity breakpoints before editing any table. Helpful vocabulary for this axis includes standstill creep, launch rollout, corner-entry speed, apex velocity, exit acceleration, motorway merge, and overrun deceleration. If users report wheel bind in tight turns, review the first few speed points before touching throttle or RPM logic.

Validation sequence: confirm units (km/h or mph display layer), compare first two speed anchors, run low-speed turn tests, then review medium-speed lane-change behavior. Keep notes tied to exact speed values so future revisions can be compared objectively.

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