Sensaphone CELL682 - Manual (Page 68)

66
Cell682 User’s Manual
ChapTer 11: TesTIng The Cell682
It is extremely important that you test the system after installation to make sure
that it is working properly and that all programming is correct. In addition, it is
highly recommended that you test and/or verify proper operation on a weekly
basis to ensure that the system continues to function as required. (See Appendix
A.) The following items should be tested:
• Notification to all destinations to make sure that each one is programmed
correctly and that the messages are actually delivered.
• Input testing to make sure that the system is reading them correctly and that
when a fault occurs the system responds appropriately.
• Output testing to make sure they are wired correctly and that they switch on
and off when instructed.
• Control programming—Local control, Machine-to-machine, or Pump con-
trol—to make sure that the system is functioning properly, as required for
your application.
notification testing
Create an alarm and confirm that all destinations receive the alarm message.
This can be done by forcing an input into alarm, by temporarily adjusting an
alarm limit, or by changing the normality of a Dry Contact input. The Alarm
LED on the front of the unit will begin blinking when an alarm has occurred.
Be sure to disconnect from the serial port after creating the alarm, otherwise
the notifications will not be sent. After confirming that all notification messages
were delivered, correct the alarm condition and/or adjust your programming as
required.
inpUt testing
Check the current value of all of the programmed Dry Contact and Analog
Inputs. Make sure that the values being displayed are correct.
For Dry Contact inputs, momentarily reverse the input condition to verify that
the unit recognizes the change of state. For example, if you have a normally open
sensor connected to Dry Contact #1, force that sensor closed and verify that the
unit displays the value as closed.
For analog inputs, verify that the input reading matches the entity being mea-
sured. For example, for temperature inputs confirm that the unit is reporting the
correct temperature.