3.11 Central
3.11.7 Configuring the Control Module - Control M 4.3
3.11.7.1 About Control M 4.3
The Control M 4.3 is the control and/or display unit in the fire detection system.
Figure 34. Control M 4.3 editor box
Description of the fields in the Control M 4.3 editor box:
Address: Enter an address for the Control M 4.3. Each module in a fire alarm central should have a unique address between 1-125. Default address depends on module type. Please refer to list of modules in sectionAdding Modules, page 24.
Text: A free text field (max 37 characters) describing the Control M 4.3. This text will be shown in the fault list if a fault is reported from the Control M 4.3.
3.11.7.2 Logging Tab
Figure 35. The Logging tab in the Control M 4.3 editor box
Description of the fields in the Logging tab:
Select events to print: Select which events that will be sent to the printer connected to this Control M 4.3.
Hint!
Printers are defined in the Serial tab.
3.11.7.3 Serial Tab
The Control M 4.3 is equipped with four serial communication ports, where the first two ports are dedicated to the backbone and the other two ports are
configurable, as shown in the figure below.
Figure 36. The Serial tab in the Control M 4.3 editor box
Description of the columns in the Serial tab:
No: Fixed number for the serial communication ports.
Type: This column describes the type of serial communication port and is not editable. The type is always one or a combination of RS232, RS422 and/or RS485.
Protocol: Select the applicable serial protocol for the communication ports by clicking in the Protocol column, as shown in the figure below.
Figure 37. A list of the available serial protocols
Protocol alternatives:
• Not used: The port is not used.
• Extension bus: Internal communication between the modules on the extension bus connected to this control module.
• System bus: Communication between centrals. For further information of serial channel 3 and 4, seeSystem Bus Settings Window, page 18
• Printer: Communication to the printer.
• MiniPrinter: Communication to the Miniprinter.
• NMEA: NMEA protocol. The protocol is described in a separate document.
• ESPA444: ESPA444 protocol for paging systems. The protocol is described in a separate document.
• MiniRepeater (MN400): The channel will be used for MN400 modules connected to this control module.
• Modbus RTU: Protocol for supervision and control of the system. The protocol is described in a separate document.
• CSProt6: A Consilium specific protocol. The protocol is described in a separate document.
• EMU350/EMU798/ChangPing/Sardinia/Dalian: Train-specific protocols used on trains. The protocols are described in separate documents.
• Aquasys: Aquasys system sensor protocol.
• Clocksync (UTC)/Clocksync (Local): Protocols to activate Ship Clock Synchronisation.
Baud: Choose the applicable baud rate for the communication port by clicking in the baud column, as shown in the figure below.
Figure 38. A list of the available baud rates
Setup: Choose the applicable setup for the communication port by clicking in the setup column, as shown in the figure below.
Figure 39. The setup list
Text 1: A free text field (max 37 characters) describing the communication port.
This text will be shown in the fault list in case of a fault on the communication port.
Text 2: Additional text field (max 37 characters) describing the communication port. Shown in the same way as Text 1.
3.11.7.4 Outputs Tab
The Control M 4.3 is equipped with two outputs. They are configured from the outputs tab in the Control M 4.3 editor box, as shown in the figure below.
Figure 40. The Outputs tab in the Control M 4.3 editor box
Description of the columns in the Output tab:
No.: A fixed number for the outputs on the Control M 4.3.
Type: Select an appropriate category for each defined output by clicking in the category column, as shown in the figure below. The categorization allows the system operator to disconnect whole categories of outputs with one single command.
NOTE!
If you choose category “Firm output”, select “Not used” in the Active column.
Figure 41. The list showing output categories
Active: Choose one of the three alternatives by clicking in the Active column, as shown in the figure below.
Figure 42. The list for selecting activation method
Active alternatives:
• Not used: The fire detection system will not use this output.
• Active high: The output is normally inactive and will be activated upon activation.
• Active low: The output is normally active and will be inactivated upon activation, e.g., used with failure outputs. If the system goes down the output will be triggered.
Setup: Choose the applicable setup for the communication port by clicking in the setup column, as shown in the figure below.
Figure 43. The setup list
Text 1: A free text field (max 37 characters) describing the output. This text will be shown in the fault list in case of a fault on the output.
Text 2: Additional text field (max 37 characters) describing the output. Shown in the same way as Text 1.
3.11.7.5 Custom Keys Tab
The Control M 4.3 is equipped with three programmable custom shortcuts, F1-F3.
They are configured from the custom keys tab in the Control M 4.3 editor box, as shown in the figure below. The configuration of the LED indications on the custom shortcuts is performed in the Salwico Language sheet.
Use the command: CU x.y LED z, to define LEDs for shortcuts. Each custom key is reflected in a SYSTEM VIO which you then can use as input conditions to control the LEDs with the command: CU x.y LED z.
Figure 44. The Custom keys tab in the Control M 4.3 editor box
Key: Choose which custom shortcut F1, F2 or F3 to configure. All three shortcuts can be configured independently of each other.
Function: Select how the three customer-defined buttons on the Control M 4.3 should perform.
Function alternatives:
• Not used: The custom shortcut will not have any function.
• Set: The custom shortcut will activate the programmed action associated with this custom shortcut. The action will only be performed once. The configuration of the user buttons is performed in the Salwico Language module.
• Maintained: When the custom shortcut is pressed, the pre-programmed action associated with this user button will be performed and will stay active until the user button is pressed again.
• Menu: When the custom shortcut is pressed, a customer-specific menu is shown in the text display. The customer-specific menu is configured in the User Menu field displayed when Menu is selected.
Menu Text: This text is shown in the customer-specific menu defined for the selected custom shortcut.
Access level: Select which access level the user must have in order to use the custom shortcuts. Individually programmable for each custom shortcut.
Copy setup from: Choose a module to copy the setup from.
3.11.7.6 Configuring the User Menu
Configure the menu, which will be shown in the text display if the custom shortcut is pressed. The User Menu field, as shown in the figure below, is only displayed if the Function is set to Menu.
Figure 45. The User Menu
Each row marked as Used in the User Menu will be associated with a SYSTEM VIO x statement in the Salwico language. It is possible to have up to 1000 VIOs in one fire detection system. For example, if VIO is set to 2 and the Used checkbox is enabled, the VIO 2 statement in the Salwico language will be associated with this User Menu row. Further, the menu text to be shown in the custom menu is specified by the Text – VIO inactive and Text – VIO active columns. The action that should be triggered when the User Menu row is selected from the custom menu is configured in the Salwico Language module described previously in this chapter.
Description of the columns in the User Menu:
Menu row: The row number.
Used: Indicates if the menu row should be displayed if the custom shortcut is pressed.
VIO: Selects which SYSTEM VIO to use.
Text – VIO inactive (default): Defines the texts to be shown in the menu when the SYSTEM VIO is cleared.
Text – VIO active: Defines the texts to be shown in the menu when the SYSTEM VIO is set.
Indication only: Tick the checkbox to de-activate the buttons. It is then not possible to change status from the menu.
3.11.7.7 I/O Tab
Figure 46. The I/O tab in the Control M 4.3 editor box
Description of fields and columns in the I/O tab:
Output Voltage: Set the voltage on the two outputs.
Max Current for each Terminal: Set the maximum current on the outputs in order to protect external equipment.
No: A fixed number for the two loops on Control M 4.3.
Type: Select the type of input or output by clicking in the type column.
Figure 47. The list showing Type categories
There are several input/output categories, as shown in the figure above. Select an appropriate category for each input/output you define. The categorization allows the system operator to disconnect whole categories of input/outputs with a single command.
• Not used: The loop is not used.
• Zone: Normal operation with fire alarms.
• General Input: The loop is used as a digital input and can be programmed from the Cause/Effect module.
• Fault input: The loop is used as a digital input. A fault appears when the loop is activated.
• General output: The loop is used as a digital output and can be programmed from the Cause/Effect window.
• Door output
• Bell output
• Fire output
• Fault output: The loop is used as a digital output. A fault appears when the loop is activated.
• Ventilation output
• Indication output
• Alarm Trans. output: A supervised output for signalling that a fire has occurred.
• Firm output
Zone: Select which zone the input shall belong to. This value is only used if Type is set to “Zone”. The zone number specified appears in the Zones window, where texts describing the zones can be added.
The zone numbers should be in the interval of 1-65534. The zone number will be displayed at the control panel if a fire or fault is reported from the loop. The zone number must be unique.
Alarm 1: Enter the lower level for the Alarm 1 interval (in mA), as shown in the figure below. When the current passes this value, the input status changes from inactive to active.
Alarm 2: Enter the lower level for the Alarm 2 interval (in mA), as shown in the figure below. This is also the upper level for the Alarm 1 interval. Note: Alarm 2 is only active if Type is set to “Zone”.
Break Level: Set the current level under which a cable break fault will be generated. To avoid cable break fault messages, set the value to 0. For 1 or 2 mA the suitable resistance level is 10 kOhm.
Short level: A limit for short circuit error. The current output from the zone will be limited to the value specified in the Max Current for each Terminal field. If many alarms are triggered, causing the current to reach the Max Current for each Terminal value, the voltage on the input will decrease. Based on this voltage decrease, the system calculates a fictive current value, which is compared with the Short level value. A fault signal is sent if the fictive value exceeds the Short level value.
This is also the upper level for the Alarm 2 interval, if Type is set to “Zone”, as shown in the figure below. For “Zone” the Short level can be adjusted (default value 50 ohm).
Figure 48. Schematic diagram over conventional loop current (default values) when Type is set to
“Zone”.
If Type is set to “General Input” or “Fault Input” there is no Alarm 2, as shown in the figure below. The Short level for “General Input” and “Fault Input” is 50 ohm.
If you want to avoid short circuit error at closed input, set the Short Circuit Current to 70 mA.
Figure 49. Schematic diagram over conventional loop current (default values) when Type is not set to
“Zone”.
Additional Settings: For each input/output there are six additional options, where more than one option can be selected, as shown in the figure below.
Figure 50. The list for additional settings
Setup options:
• Anti-phase: The output will be in anti-phase in relation to the synchronization pulse, if such a pulse is available.
• Synchronized: The output will follow the synchronization pulse, if such a pulse is available.
• Break Supervised: Activates the cable break supervision. Signals a fault in case of a break.
• Short Supervised: Activates the short circuit supervision. Signals a fault in case of short circuit.
• GA-morse: If activated, this output will be active when the ’General
Announcement’ signal is activated. The latter is a hardware signal activated via Charger M.
• X-fire: If activated, this output will be active when the ‘X-Fire” signal is activated. The latter is a hardware signal used as a last resort if a module detects an alarm condition and is unable to communicate with any other modules.
Text 1: A free text field (max 37 characters) describing the location of the loop unit. This text will be shown in the fault list if a fault is reported from the loop unit.
If Type is set to “Zone”, this text must be entered in the Zones window, at the corresponding zone number. Otherwise, it can be entered directly in the Text 1 field.
Text 2: An additional free text field (max 37 characters) describing the location of the loop unit. Shown in the same way as Text 1. If Type is set to “Zone”, this text must be entered in the Zones window, at the corresponding zone number.
Otherwise, it can be entered directly in the Text 2 field.
3.11.7.8 Network Tab
Figure 51. The Network tab in the editor box
Interface information field
Name: Choose from the available interface names.
Type: Choose the type of interface.
Interface settings field
Adress: Set the IP-network address.
Netmask: Set the netmask.
Gateway: Set the gateway.
NOTE!
All three address fields must be set in order to activate the static IP.
VNC field
Enable Remote Access: Enable the ability to remotely log in to the module using VNC. A server is started on the control module that allows connections from remote clients.
Debug IP field
Enable Debug IP: Check the box to enable Debug IP.
CAUTION!
For advanced users only and should normally be activated. The debug IP address is derived from the module's hardware address.
Modbus TCP/IP field
Enable Modbus TCP/IP: Check the box to enable Modbus TCP/IP (as described inModbus TCP/IP Window, page 20).
3.11.7.9 Supervision Tab
Figure 52. The Supervision tab in the editor box
Description of the fields in the Supervision tab:
Secondary backbone channel (B): Disable or enable fault generation from the secondary backbone channel (B). Disable the fault generation if only the primary backbone channel (A) is connected to this module.
3.11.7.10 kProt Tab
There are some prerequisites on the Fire detection system for kProt (Kongsberg Protocol) to work:
• kProt is only supported in single-central Fire detection system.
• kProt is only supported by the Control panel M 4.3, Control panel M 2.2 and Control M X modules. (Note that control modules in the Fire detection system always act as kProt slaves and that equipment connected to the Fire detection system always acts as kProt masters.)
• A kProt slave can communicate with a maximum of five kProt masters.
NOTE!
No more than 3 Loop M X modules can be used in the same system if the kProt protocol itself shall support SIL-2 according to IEC61508 with regard to communication.
The kProt communication protocol is described in a separate document.
Figure 53. The kProt tab in the editor box
Enabling kProt
Select the box called ‘Enable’ in order to activate the protocol.
The kProt configuration requires a slave port and at least one master.
Configuring a kProt Slave Port
The Slave Port defines the port the kProt slave uses for incoming messages and shall be used by all masters in order to communicate with the slave. Valid port numbers are within the range 1024-65536. (28101 is the default kProt Slave Port.) Configuring a kProt master
To add a master to the configuration, click the first row of the list and fill data in the following order. (Press Enter after each line.)
Slave ID: The ID that the slave will use when communicating with the master.
Master ID: The ID that the master will use when communicating with the slave.
Master IP Address: The column must contain the IP-address of the kProt master.
This address is used by the kProt slave when it responds to queries from the master.
Dynamic IP addresses are not supported; each master must be assigned a static IP-address.
Master Port: The column must contain the port of the kProt master.
Each master must have a unique ID while the Slave ID can be unique or the same for all masters. It is possible to add masters with the same IP address but if in that case different port numbers must be used in order to assure that the master address is unique.
CAUTION!
The kProt slave follows the configuration strictly, messages will be dropped by the slave if other IDs than the ones specified are used and messages will be sent to the wrong destination if incorrect IP-addresses or ports are filled in.
An additional IP-address
It is also possible to configure the Control Module with an additional IP-address.
To set an additional IP-address:
1. Select tab Network for the control module.
2. Fill in the static IP-address, subnet mask and default gateway.