Chapter 7: Service and troubleshooting
208 EST3X Technical Reference Manual
Modules
When a module is replaced with another module of the same type, automatic
remapping assigns the replacement module the personality code of the module
originally installed at that map location.
If a module is replaced with a module of a different type one of three things can
happen.
1. If a single address module, such as the SIGA-CT1 or SIGA-CC1, is replaced
with a different type of single input module, the loop remaps all devices.
However, the new module type will not operate because of incompatible
personality codes. A map fault generates because the actual device differs
from the expected device. The new device type must be defined in the 3-SDU
and the database downloaded into the panel. The map fault will then clear.
2. If a single address module is replaced with a dual address module, the panel
unsuccessfully attempts to remap all devices. A map fault generates because
the actual device differs from the expected device, and the dual address
module does not operate. To clear the map fault, define the new module
using the 3-SDU, and then download the database into the panel.
3. If a dual address module is replaced with a single address module, the panel
never automatically attempts to remap all devices because the panel does not
see enough devices (one address less) on the loop. A manual remap will also
be unsuccessful. A map trouble shows on the control panel LCD screen as
the panel remains in map pending mode. To clear the trouble, define the new
module using the 3-SDU, and then download the database into the panel.
Notes
• Do not replace factory-programmed devices such as pull stations and MM1
modules with a SIGA-CT1.
• For mapping purposes, give all manual pull stations the device type Pull,
regardless of their model numbers.
Device type replacement
If a different Signature device model is substituted for a suspect device, when the
device count is correct the Signature controller module automatically remaps the
loop. A trouble occurs at the address of the suspect device as the result of a map
fault, because the known good device’s parameters differ from those of the
suspect device that was removed from the loop. To clear the map fault, accept
the parameters of the known good device. You can change the parameters later.
To Next Page
Loading...
