API Endpoint

Read Curve

Returns current curve points for mode endpoint.

GETMap and Curves/api/curve/throttle

Reach It

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

Endpoint-Specific Engineering Notes

This section is intentionally unique for GET /api/curve/throttle. Focus area: pedal-axis curve visibility for tip-in and load response calibration. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated workflow step rather than a generic HTTP action.

Operational scenario: Inspect throttle curve to understand how lock demand responds from light cruise to aggressive pedal input.

Domain vocabulary: pedal-percent, tip-in, mid-pedal, kickdown, load-request, throttle-axis, driver-demand, transient-input, pedal-ramp, response-shape.

Common Mistakes for This Endpoint

Overly aggressive low-pedal response
Flat mid-pedal region causing dull behavior
No separation between street and launch tuning

Practical Validation Pattern

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

Throttle Axis Interpretation Notes

Throttle-axis calibration is about driver intent mapping. This OpenHaldex endpoint should be reviewed using pedal zones: feathered input, gentle cruise correction, progressive tip-in, brisk mid-load demand, and full-load launch. The goal is to shape torque request behavior so response feels deliberate instead of abrupt or lazy.

Distinct vocabulary for this axis includes tip-in transient, tip-out unwind, part-throttle modulation, kickdown request, pedal-rate sensitivity, launch pedal threshold, and driver feedback linearity. If the vehicle feels nervous in stop-and-go traffic, inspect early pedal points before changing speed bins.

Validation sequence: observe pedal telemetry, compare curve anchors against real pedal percentages, run light-throttle urban tests, then perform controlled full-throttle pulls. Capture logs so pedal intent and resulting lock request can be correlated over time.

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