User's Manual

545C Operations Manual

02/10/2012 Prerelease DCN 00001789-A

setbaud,1,9600

generic

save

5.6 Event Programming

The MCC-545C supports customer-programmed event logic. Discrete and

analog inputs can be monitored by the event program to detect “events”

which then perform a defined “action.” Actions may include the

controlling of discrete output signals, incrementing counters, setting

timers, transmission of canned messages, and issuance of various reports.

This means that customers are somewhat independent of factory

reprogramming from MCC and that MCC-545C behavior can be readily

modified in the field. It also means that operators now have limited power

to make the MCC-545C react to various field-programmable conditions.

The operator sets up the event program when installing the MCC-545C or

during maintenance and operation. Because the event program is

implemented via operator commands, it can be entered not only at a local

maintenance console, but also via the remote command capability. The

event programs are stored within a non-volatile table in the MCC-545C

battery-backed-up RAM. They are not lost due to external power failure.

When the external power is restored, they will be enabled to respond to

events again.

Refer to Figure 16 for a block diagram of event programming inputs and

outputs. Programming is usually done by creating a “script file” of the

required event commands, and loading these into the MCC-545C using

XTermW or any other terminal emulator software.

Several input/output lines are available directly from the processor card of

the MCC-545C modems. These differ between the A, B, and C variations of

the MCC-545. In addition, an optional I/O expander card (XIO) uses 3 lines

to implement a high-speed serial link for accessing the signals of the

expander card.