Reset OSSD output

Open in ClaudeOpen in ChatGPT
Manually clear latched OSSD trips and faults by cycling the OSSD generator enable. The request must echo the current `reset_id` from the OSSD status endpoint; Keeper rotates the token on success so the request cannot be replayed. Returns the post-reset status, including the new `reset_id`. A trip source that is still asserted, or a persistent hardware fault, re-latches immediately.

Request

This endpoint expects an object.
reset_iduintRequired0-4294967295

The current reset_id from the OSSD status endpoint. Rejected if it does not match the live token.

Response

OSSD status after reset
configuredboolean

True when OSSD dual-channel output is configured on the MIO pins

statusenum

Live OSSD generator status.

  • DISABLED - OSSD generator is not running.
  • ENABLED - OSSD generator is enabled.
  • ACTIVE - OSSD outputs are asserted and diagnostics are clean.
  • TRIPPED - outputs are deasserted because the trip source asserted (for example a Zone Monitor infringement). Not a hardware failure.
  • FAULT - OSSD diagnostics detected a defect such as a short, open load, or failed startup qualification.
Allowed values:
sourceenum
Selected OSSD trip source
Allowed values:
errorslist of strings

Human-readable latched OSSD trip and fault messages

reset_iduint0-4294967295

Single-use token that must be echoed by a reset request. Rotated on each successful reset so a stale or replayed request cannot re-clear a latched fault.

Errors

400
Bad Request Error
500
Internal Server Error