User's Manual

Octopus ATM Defense System
Installation and Operation Guide
Page 21 of 25
Final ALERT event check.
After 90 minutes of ALERT mode, the system looks to make sure that all ALERT events that are inactive have
been held for 60 minutes minimum, and any active ALERT event has been in affect for 90 minutes. Any active
ALERT event at this time is disabled, the system will return to the ARMED mode until either a STANDBY event
or another ALERT event occurs.
Logging all events.
All alert conditions are logged to a LIFO register in non-volatile random access memory (NVRAM). The purpose
of the log file is to generate the trail of events leading to activation. Currently the only way to retrieve the
NVRAM information is to export the unit back to the factory for investigation. Using specialized software a
report can be generated of the events.
Keep in mind that the events are only those which cause the unit to go to ALERT and FIRE mode, no real time
clock is installed to allow event tracking to a specific time.
FIRE mode operation
Fire mode in the last stage of an ATM attack. Any unit elevated to this level will stain the currency. This state is
irrevocable. The unit sends a message to the CSU to degrade the currency, then the MCU warns of the event be
beeping. Further any optional device atached to the MCU (siren or smoke) is also activated.
Setting the output relays.
Two outputs on RJ11 jacks are provided for customer and internal monitoring of system status. The are called
FAULT and ALERT. When an error condition or fault in the system occurs, the FAULT relay is closed. When an
ALERT event occurs, the ALERT RELAY is closed. When a fire EVENT is processed both the FAULT and
ALERT relays are closed. The reasoning is that if both a system fault and an ALERT condition exist, the ATM
need service or police intervention. And, when the system fires the system will require maintenace.
FIRE event.
The Octopus ATM Defense system communicates wirelessly to the CSUs to cause staining. Further, any optional
device attached to the MCU is activated. A charge pump is used to generate sufficient energy density to fire the
pyrotechnic actuators. This pump take > 2 seconds to accomplish this task. Further the charge is pumped and
applied a minimum of 3 times to the pyrotechnic device to insure proper activation.
Logging all events.
All fire conditions are logged to a LIFO register in non-volatile random access memory (NVRAM). The purpose
of the log file is to generate the trail of events leading to activation. Currently the only way to retrieve the
NVRAM information is to export the unit back to the factory for investigation. Using specialized software a
report can be generated of the events.
Keep in mind that the events are only those which cause the unit to go to ALERT and FIRE mode, no real time
clock is installed to allow event tracking to a specific time.
After system activation:
After system activation all units wait for their POST buttons to be pressed before continuing operation. This is the
safe condition to prevent degradation of the NVRAM data with after FIRE event tasks.
End of Detailed Operation.
27
28
29
30
31
32