API Endpoint

Update Settings

Main mutator for controller, mappings, generation, logging, thresholds.

POSTCore Control/api/settings

Reach It

Method: POST
Path: /api/settings
Base URL: http://openhaldex.local (or controller IP)
Response format: JSON

Query Input

None

Body Input

Partial JSON accepted. Includes inputMappings, disableController, broadcastOpenHaldexOverCAN, haldexGeneration, disableThrottle, disableSpeed, log flags, disengageUnderSpeed.

Response / Parse

Receive: JSON: {"ok":true,"debugCaptureActive":bool,"disableController":bool}

Parse: Many numeric values are clamped. Re-read /api/status after write.

Error Behavior

400 invalid json/object; 409 capture conflict; 503 mapping busy; 200 success

Example Call

curl -s -X POST "http://openhaldex.local/api/settings" -H "Content-Type: application/json" -d '{...}'

Endpoint-Specific Engineering Notes

This section is intentionally unique for POST /api/settings. Focus area: high-impact configuration writes with strict validation and rollback awareness. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated workflow step rather than a generic HTTP action.

Operational scenario: Batch only related settings in one request, then validate each reflected field in status before allowing additional edits.

Domain vocabulary: settings-schema, range-check, feature-flags, broadcast-toggle, controller-enable, mapping-key, write-ack, persist-cycle, safe-defaults, rollback-plan.

Common Mistakes for This Endpoint

Mixed unrelated settings in a single blind write
No per-field validation messaging
Ignoring persisted-vs-runtime mismatch

Practical Validation Pattern

Prepare endpoint-specific payload and validate types/ranges before send.
Execute POST /api/settings 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

await fetch('/api/settings',{method:'POST',headers:{'Content-Type':'application/json'},body:JSON.stringify(payload)});

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.

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