Machine status monitor: discrete-input alarm annunciator

01

Order the input board together with the window hardware

Omniflex’s C1480B-5 Omni16C variant lists 16 ribbon-header inputs referenced to 0 V and individually selectable normally-open/normally-closed operation. The product is supplied without LED boards or lamps, which must be ordered separately. Confirm the suffix and supplied hardware instead of treating every Omni16C unit as a complete illuminated panel. [1]

List each fault signal, its healthy and alarm states, signal source and isolation requirement. Put the input-board reference, connection diagram, window legends and indication hardware into the order schedule.

Ronan’s X110 uses a different architecture: process-contact status is multiplexed and transferred over a serial link to controllers serving the windows. It accepts serial ASCII alarm/normal messages. A serial-only display needs the corresponding host or multiplexer interface; it is not a substitute for a local input board without that equipment. [3]

02

Write the alarm arrival, acknowledge and return-to-normal behaviour

The cited Omniflex variant offers 27 standard alarm sequences. Its optional integral Test, Silence, Acknowledge and Reset buttons occupy an alarm-window position; externally wired buttons are an alternative. Select the sequence and button arrangement before finalising the legends and channel allocation. [1]

Agree on flashing and steady indications, horn operation, a fault that clears before acknowledgement, a fault that remains active after acknowledgement and the reset conditions. If first-out identification is required, request the exact sequence and demonstrate it with a defined group of test inputs.

Omniflex also describes an inhibit input that can disable all alarm inputs during startup or maintenance. Record how inhibition is applied, indicated and removed in the machine procedure. [1]

03

Specify event timing separately from the alarm display

Ronan’s X11CB event-recording annunciator lists event timestamps at 1 ms resolution with date/time correlation when an external IRIG-B source is provided. The published entry describes timestamp resolution with a timing-source condition; it does not establish a universal input-to-lamp response time or absolute time accuracy. [2]

Its interface module supports local event storage up to 1,000 events and networked monitoring. Define the event retention, download route, clock source and behaviour after loss of communication or time reference for the selected installation. [2]

In acceptance testing, inject identified fault inputs, verify their window labels and alarm sequence, and compare the saved event records with the applied test sequence. Keep alarm acknowledgement separate from any machine reset or restart command in the agreed interface description.

04

Submit the fault list and annunciation sequence

Paste it into your enquiry below or into an email to a maker, then replace every bracket.

Inputs: [fault name; healthy/alarm state; source; board and isolation]
Windows: [legend; colour; LED/lamp hardware; panel cut-out]
Sequence: [arrival; acknowledge; clears-before-ack; reset; first-out group]
Buttons: [integral or external; occupied window; wiring]
History: [clock source; retention; export; communication-loss behaviour]
Trial: [injected inputs; audible/visual states; matching event record]

See manufacturer records Send an enquiry through CNFX