Frequently asked questions

FAT2002: FATProgWin version 3.1.13.0

FAT3000 / ADP-N3x standard applications: FATProgWin version 3.2.15.1 and higher

FAT3000 / ADP-N3x special applications (controller redundancy, long identifiers, FAT-ICP2 network...): FATProgWin version 3.2.23.0 or higher

ADP4000 / FAT4000 / FBF4000 / IMT4000CPU / GMT4000 / ABT4000: Prog4000

IMT4CPU: IMTProgWIN

ADP-ESPA / ADP-ESPA-U / FS20-ESPA-Interface: ESPA-ProgWIN (matching the respective FACP)

ADP-UPC: UPC-Config (suitable for the respective BMZ)!

FAT2002 settings:

• In the Configuration - ESPA menu, tick the box for ESPA active
• In the Configuration - Code Table menu, select the ESPA “incoming” or “incoming + outgoing” column for the events to be transmitted
• In the Configuration - Texts menu

o Code: general, group=0, detector=0,

o Enter call address (tel. no./ESPA ID) in line 1 part 2. At least 4 entries (lines) must be made in the text dialog (if necessary, use empty entries with group=0, detector 1...3), otherwise the text dialog will be ignored.

FAT3000 settings:

• DIL switch S2-4=ON, other DIL switches according to the respective application
• Jumper J1 + J2 set to 2-3 (upwards) for output via plug-in terminals
• Jumper J8 set to 1-2 (upwards)
• Select “incoming” or “incoming + outgoing” for the events to be transmitted in the Configuration - Code Table menu, ESPA column
• In the Configuration - Texts menu

o Code: general, Type = Group, Sys.-Adr.=0, Group=0, Melder=0, AE=0

o Enter call address (tel. no./ESPA ID) in line 1 part 2.

ADP-N3E settings (ADP is used for ESPA output to SIO1 and SIO2):

• DIL switch 4=ON, other DIL switches according to the respective application
• In the Configuration - Code Table menu, select “incoming” or “incoming + outgoing” for the events to be transmitted in the ESPA column
• In the Configuration - Texts menu

o Code: general, type = group, system addr.=0, group=0, detector=0, AE=0

o Enter call address (tel. no./ESPA-ID) in line 1 part 2.

In the event of an alarm, the message code with the group/detector information and the text in line 2 is transmitted to the address from line 1 part 2 (call address)!

To return to normal operation, the USB cable must be disconnected!

A PC test software program called “ESPA Tool” can be obtained from the homepage. To use it, start the “ESPA-Tool.exe” file from the PC without installing it. The PC simulates the remote station. The connection is made via RS232 using the null modem cable.

At least one COM port must be active on the computer. This can be checked in the device manager. In addition, the USB-serial converter must be connected.

Press the “Ebene” and “Back” buttons at the same time for at least 5 seconds to deactivate the FAT internal buzzer. The message “Maintenance mode - buzzer switched off” appears on the FAT display. Pressing the two buttons “Ebene” and “Back” again will immediately reactivate the buzzer. The buzzer is automatically switched back on 12 hours after maintenance mode is activated.

With the programming software FATProgWin, the messages displayed on the FAT can be edited in the menu: \Configuration\Code Table. Mark the lines for “Fault” or “Shutdown” in the “Meaning” column and then press the “Reset” button.

1.) The supplied null modem cable was not used. Check your null modem cable. Pin 4 of one socket must be wired through to pin 6 of the other socket. Info: Control lines are used for switching to programming mode.

2.) In FATProgWin in menu: PC settings check if the correct COM port for data transfer to the FAT has been selected.

3.) If you are using the ESPA function on the FAT. If the ESPA function has been activated on the FAT, then the automatic switchover to programming mode is deactivated. Proceed as follows: If the following message appears in the PC dialog window: “If the FAT has switched to programming mode, click OK”, then click the reset button on the FAT. Then click the “OK” button on the PC.

1.) In FATProgWin in the menu: \Transfer\PC settings, check whether the correct COM interface for data transfer to the FAT has been selected and the baud rate is set to 57600, no parity.

2) If a USB-serial converter was used, then this is obviously not compatible for data transfer to the FAT. Note: A compatible USB-serial converter can be found in our product range.

Update firmware version and configuration file. The current firmware and associated configuration file were adapted to the new firmware versions of the BMZ Expert.

You have used a non-redundant version of a FAT configuration file or changed the settings in the file for this. Use a configuration file from the CD included with the FAT and labeled xxx_redundant.

Remedy is possible through configuration with FATProgWin. The FAT is connected via TTY to an ESSER BMZ. No year is transferred in the ESSER TTY protocol. In the FATProgWin menu: Configuration\System config, press the key combination “ALT” + “E”. Then set the value “128” under the parameter “lkgdisp” and confirm with “OK”. Program the configuration back into the FAT. The date is thereby displayed identically on the FAT to the display of the fire alarm control panel without the year.

Check the DIP switches on the FAT3000. Set DIP switches 1

Check the firmware versions on the FAT and on the redundancy adapter. The firmware versions of the two devices should be identical. Different firmware versions on the FAT and ADP can lead to incompatibility.

If the FAT3000 is connected redundantly, the fault relay on the FAT is not operational. The fault relay of the ADP-N3x must be used!

The SIO lines from the ADP-N3x to the FAT are reversed. Make sure to connect SIO1 of one device to SIO2 of the other device!

The power supply of the IMT4CPU must not be realized via the “OUT UB” terminal of the FAT. The IMT4CPU must be supplied with power separately!

The system address entered in the respective text line must match the system address entered in the Configuration - System3000 menu. Either change it manually in the text dialog or set a checkmark in the System3000 dialog next to “This resulting system address of the fire alarm system should be adopted for all additional texts”.

Check the FAT configuration file in FATProgWin. In the “System3000” dialog under the “SIO” tab, the protocol “PCTAB” or “PCTAB/IMT4CPU” must be set.

Note the different DIL switch settings on the FAT. FBF2003 serial: DIL switches 1+3 of DIL switch block S1 to on; FBF3000: DIL switches 1+2 of DIL switch block S1 to on.

The cause of this lies in the limited protocol buffer of the ESSER fire alarm control panel. The control panel limits and sorts its messages before transmission to the FAT. If there are a large number of messages (e.g. many shutdowns during commissioning), messages may only be displayed on the FAT late or not at all.

Check the configuration files for the FAT and the redundancy adapter. In the FATProgWin, the “3 lines per message” option must be checked for both devices in the “System Config” dialog.

With the FSD closed and the fire brigade key deposited in it, check:

1.) Is a measurement of approx. 2.2 kOhm possible between pin 1 (white) and pin 2 (brown) of the FSD? If a measurement of 2.2 kOhm is not possible, please check the cabling, 2.2 kOhm resistor, door contact, anti-drilling protection and key-operated switch contact in the FSD.

2.) No current should be measurable between pin 7 (blue) and pin 8 (red) of the FSD (high resistance). If a short circuit is measured, check the switching function of the feedback contact at the FSD lock.

Check the door lock's feedback contact on the FSD. When the FSD is closed, no current should flow between pin 7 (blue) and pin 8 (red) (high resistance). If a short circuit is measured, then check the switching function of the feedback contact on the FSD lock.

Expert mode -> System configuration -> System data and LED settings

BMZ ---> IMT4CPU ---> IMT4LED:

• GMA-Adr = xx (0 or ABF address for BMZ)
• Network addr = 0
• IC-Kask1: 1...4 Number of IMT4LED(K) modules
• IC-Kask2: 1...8 Number of IMT4LED24 / IMT4LED32 modules according to the connection

BMZ ---> IMT4CPU ---> IMT4PROC ---> IMT4LED:

• GMA-Adr = xx (0 or ABF address for BMZ)
• Network addr = 1...max. (highest IMT4PROC address to be controlled + 1)
• IC-Kask1 = IC-Kask2 = 0 (both are set to 0!)

BMZ ---> FAT ---> IMT4CPU ---> IMT4LED:

• GMA-Adr = 0
• Network address = 1...31 Slave address
• IC-Kask1: 1...4 Number of IMT4LED(K) modules
• IC-Kask2: 1...8 Number of IMT4LED24 / IMT4LED32 modules according to connection

BMZ ---> FAT ---> IMT4CPU ---> IMT4PROC ---> IMT4LED:

• GMA-Adr = 1...31, FAT net address
• Network addr = 101...131 (IMT4PROC addresses + 100)
• IC-Kask1 = IC-Kask2 = “0” (both are set to 0!)

1. The power supply could be defective:
--> Please check the connection of the IRAS hazard detection system to the 230V mains supply and measure the voltage if necessary.

Replace the cable if necessary. Remove the cable and operate the IRAS hazard detection system on battery power.

Note: If the voltage at the PC is below 21V, the system is deactivated as a precaution.

2.The battery could be defective:
Plug in the power cable and operate the IRAS hazard detection system with 230V.

1. Battery voltage too low
--> The battery voltage is too low due to a defect in the battery or a deep discharge.

--> Check the batteries or charge them using an external charger.

2. Consumer current too high
The PC is defective. Please contact the IFAM GmbH Erfurt service department.

--> Basically, ports 80 for incoming and port 443 for incoming and outgoing connections are required. If you have configured a printer or e-mail, these customer-specific ports must also be released for outgoing connections. These ports can be obtained from your e-mail provider and may vary.

--> There is no general answer to this question. Depending on the type of control center, the manufacturer and the interface (protocol) used, different hardware is required. If operations are possible via the protocol, this can be carried out by the ADP4000 in conjunction with IRAS. If this form of operation is not possible, only one operation can be carried out with the ADP4000-FBF. This is limited to the FBF functionalities.

--> In principle, this connection must be made by the customer. Ask your system administrator about the different options. Here are some examples of how to implement this (this depends on devices from other manufacturers!

--> Possible variants are:

- port forwarding through the router (dynDNS or static IP required)

- VPN connection via Mdex, IRAS-Plus-Connect

- Mobile connection with fixed IP address.

--> Check your internet connection and that of your box. Save the project again in the app. Test the connection by clicking on “Open project in browser” in the app. If your browser displays the access page, your connection is technically okay.

--> If the IRAS hazard detection system is configured with active SSL, the “Secure connection (HTTPS)” option must be set in the app.

--> There could be a certificate problem. Test the “Test” button behind the “Secure connection (HTTPS)” setting in the app.

--> Incorrect IP address.

--> Use an IP scanner to determine the correct IP address of the IRAS hazard detection system. You may need to adjust the IP addresses so that your PC and the IRAS hazard detection system are in the same subnet.

--> IP address has changed

--> Only the preinstalled admin account has a hijacking protection measure. To do this, the IP address is stored at the time of login. As soon as this changes during administration, the connection is disconnected

--> Network change of the mobile device

--> The IRAS hazard detection system has different addresses in the WLAN than in the mobile network. Many mobile devices switch networks depending on the available speed or signal quality.

--> The boxes do not offer any alternative access method. If you have lost your password, contact support. There is the option of resetting the password via the USB port. To do this, a USB emergency pin must already have been assigned (default: 12345).

1. Username/password entered incorrectly three times
--> Wait at least 5 minutes and then try again. Make sure you enter the correct password and username.

2. Browser cache
The browser has stored an old cookie or has a cache that contains data that is no longer valid. Close the browser or delete the cache. Alternatively, the keyboard shortcut CTRL+F5 can be used.

3. Update error
Interrupting the power supply during an update can cause a serious error. Contact the IFAM GmbH Erfurt service team.

For the systems IRAS-Basic, IRAS-Printer, Fire Brigade Print System (old), NORA, ERA, a jpg is required as a preview image for the import. For the systems IRAS-Maintenance Box, IRAS-Plus/-Mobile, NORA-Plus/-Mobile, Fire Brigade Print System-Plus, a missing preview image is automatically generated from the first page of the PDF. This may take some time the first time the preview image is accessed.

--> My call signs have been uploaded correctly, but are not displayed in the firefall. What can I do?

--> Check whether the call signs have been created with a BMZ number and that this is also sent by your BMZ (or the ADP). If neither match, then delete all call signs and upload them again without a BMZ number.

1. Push filter for the group is not set correctly.
--> Check the filter settings for notifications of the respective user under Setup->System->User.

2. Failure of the notification service
--> Like some other functions, the IRAS hazard detection system relies on mobile operating system functions to receive notifications. If this service fails or short-term maintenance is being carried out on it, there may be disruptions or delays in notification.

3. Push server not accessible
--> Run the self-diagnosis under Setup->System->Diagnosis. If the server is not accessible, check that port 443 is enabled and that the URL is iras.ifam.com.

1. Provider hat die Sicherheit angepasst
--> Bitte prüfen sie ob „unsichere Anwendungen“ zugriff auf ihren E-Mail-Dienst haben. Nehmen Sie Kontakt mit Ihrem Anbieter auf um eine Klärung zu erreichen. Nutzen Sie App-Passwörter. Diese ermöglichen einen Zugriff mit speziellen Zugangsdaten (google).
2. E-Mail-Einstellungen nicht korrekt
--> Prüfen Sie ihre E-Mail-Einstellungen unter Setup->System->E-Mail. Nutzen Sie die Test-E-Mail um Ihre Einstellungen zu prüfen.
3. E-Mail-Server nicht erreichbar
--> Prüfen Sie das der unter Setup->System->E-Mail eingestellte Port für das IRAS-Gefahrenmeldesystem erreichbar ist. Ebenfalls muss ein gültiger DNS eingetragen sein (DHCP) und die URL darf nicht blockiert werden. Nutzen Sie die Test-E-Mail um Ihre Einstellungen zu prüfen.
4. Spam Filter
--> Prüfen Sie Ihren Spam Filter. Nutzen Sie die Test-E-Mail um Ihre Einstellungen zu prüfen.
--> Die E-Mail wird für konfigurierte Meldungen gesendet, jedoch ohne Anhang.
5. Laufkarte nicht vorhanden
--> Das IRAS-Gefahrenmeldesystem kann zu der Meldung nicht die entsprechende Laufkarte finden. Prüfen Sie unter Setup->Laufkarte ihre Konfiguration. Prüfen Sie ob die Laufkarten-Dateien vorhanden sind und die Namensvereinbarung einhalten.
--> Schauen Sie ob bei einer anstehenden Meldung die Laufkarte in der App oder auf der Webseite angezeigt wird.
6. Spam Filter
--> Der Anhang wird von Ihren E-Mail-Filtern gelöscht. Nutzen Sie die Test-E-Mail um Ihre Einstellungen zu prüfen
7. Benachrichtigungsfilter prüfen
--> Prüfen Sie die Einstellungen des E-Mail-Filter und ob der Versand von JPG/PDF aktiviert ist.
--> Ich möchte während der Wartung keine Push-Berichtigungen erhalten.
--> Sie können für eine Benutzergruppe die Push-Benachrichtigungen, während einer Wartung, auf der Webseite der Box deaktivieren. Wird dann eine Wartung über die App gestartet, kommen keine Meldungen Push-Benachrichtigungen zu dieser Gruppe.

1. Messages for this level are not assigned.
--> Check the assignment of messages to the fire level under Setup-> Code table.

2. The app is not correctly connected to the correct IRAS hazard detection system.
--> Enter the correct address, username and password in the app and save this configuration. This will automatically register this mobile device with the IRAS hazard detection system for push messages.

3. Sound muted on mobile device.
Activate the sounds on your device.

4. Push notifications disabled in the app.
Activate push notifications in the app settings.

5. Incorrect sound configured.
Check the sound configuration in the app.

1. From 31.03.2021, the push method using certificates will no longer be supported.

You can update your IRAS-Basic with an update. You can find it here: http://ifam-erfurt.de/support-82/supportangebote/downloadbereich/category/38-iras-app.

The end devices (Windows 10) do not have an MS account and do not have access to the store. 1. From 31.03.2021, the push procedure using certificates will no longer be supported.

--> If you want to use the IRAS-Basic app on Windows 10, access to the store is necessary. This guarantees the highest possible security for your Windows installation. An MS account is currently not required to access the Windows store.

The end devices (Windows 10) do not have an MS account and do not have access to the store. 1. From 31.03.2021, the push procedure using certificates will no longer be supported.

--> If you want to use the IRAS-Basic app on Windows 10, access to the store is necessary. This guarantees the highest possible security for your Windows installation. An MS account is currently not required to access the Windows store.

1. Communication with the update server is not possible, the self-test displays the following output:

--> No updates have been installed on your system for some time. This may cause certificates to expire for technical reasons. The following link provides the latest updates for the certificates, including the necessary instructions (system update).