AutoPulse 4100-3113AR Installationsanleitung Handbuch - Seite 9

Blättern Sie online oder laden Sie pdf Installationsanleitung Handbuch für Kontrolleinheit AutoPulse 4100-3113AR herunter. AutoPulse 4100-3113AR 10 Seiten. Idnet 2 sprinkler card and idnet loop card

Seite drucken

4100-3113AR IDNet 2 Sprinkler Card, and 4100-3111 IDNet Loop Card Installation Instructions

Double-click the 4100-3113AR IDNet 2 Sprinkler card in the Hardware Configuration area to open the Card Properties, Point Editing

and Loop Editing tabs. See

Configuring the Card Properties tab

Double-click the 4100-3113AR IDNet 2 Sprinkler card in the Hardware Configuration area to open the Card Properties tab.

Enter the appropriate information in the following fields:

• Card Address.*

• Card Description.

• Card Default label.

• Card Custom Label: Use this field to describe the card function, location, or other descriptive information.

• Card Alternate Custom Label: Use this field to enter an alternative description of the card.

• Annunciator: This field indicates which annunciator the card is associated with.

• Unit, Bay, and Box.*

• Location.*

• 24 V Alarm and Standby current (Amps).

* You can modify the default data manually. To avoid an error, ensure that the information you enter matches the data programmed in the sprinkler

control panel.

Configuring the Point Editing tab

Use the Point Editing tab to manage and edit the point types that correspond to the devices on the IDNet loop. Configure the Sprinkler Heat Sensors

at the desired addresses by selecting the SPRNKLR device type. The point type defaults to SUPV and cannot be changed.

Configuring the Loop Editing tab

When you add the sprinkler card to the sprinkler control panel, the Autopulse Panel Programmer programmer automatically reserves four addresses

for the four potential loops:

• Loop 1: Point 251

• Loop 2: Point 252

• Loop 3: Point 253

• Loop 4: Point 254

The device type for both Loop 1 and Loop 2 is set to ISO, you cannot edit this.

The device type for Loop 3 and Loop 4 is set to UNUSED by default. You must set this to ISO to activated these loops.

When the device is determined, complete the entries for the Custom Label, Alternate Custom Label, Primary Action Message, and Trouble

Action Message fields.

Troubleshooting

See the following tables for a list of error messages that can appear on the sprinkler control panel display when using the sprinkler card:

Trouble message

Extra Device

Wrong Device

Earth Fault Search

Channel Fail

No Answer

Bad Answer

Output Abnormal

See the panel diagnostics for additional troubleshooting information about duplicate devices, weak answers, and other problems.

page 9

Configuring the Card Properties tab

Table 3: Trouble messages

This message appears when one or more extra devices, or devices that have not been configured for the IDNet

channel, are found on the system. This message also appears when a device is at the incorrect address.

Note: An extra device on address 253 or 254 indicates that a loop module has been detected but not programmed.

Only one trouble message appears, regardless of the number of extra devices in the system. View the trouble log to

see the extra device address. LEDs on devices illuminate steady to indicate the trouble, as long as there are no alarms

in the system.

This message appears when the device detected at the address does not match the device type that is programmed in

the system.

This message appears when the sprinkler card is searching for earth faults on the IDNet channel. When this message

displays, the IDNet 2 Sprinkler Card cannot show any alarms or other statuses.

This message appears when the devices are configured, but none of the devices are communicating on the channel.

This message does not appear if there are no configured devices on the IDNet channel.

This message appears when a device is missing, damaged, or improperly configured, or when duplicate devices are

present.

Note: A No Answer trouble on address 253 or 254 indicates that a loop module has been programmed but not

detected.

This message appears when there is a faulty device, a noisy communications channel, or duplicate devices present.

This message appears during any of the following conditions:

• When 24 V is not present on IDNet devices, MBZAM and MAZAM devices for example.

• When TrueAlarm sensor bases with relay driver outputs are not supervised.

• When isolator devices are in isolation mode.

for more information.

Possible cause

579-1214AR Rev. B