https://doku.siwenoid.com/ 2026-05-12T07:01:42+00:00 https://doku.siwenoid.com/ https://doku.siwenoid.com/lib/exe/fetch.php?media=wiki:logo.png text/html 2026-03-17T14:35:58+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:backup&rev=1773758158&do=diff Backup This page describes how to create a backup of the SIWENOID v2 installation using the built-in Safety Backup function. Regular backups are essential for every SIWENOID v2 installation. A current backup allows the system to be fully restored after a hardware failure, software corruption, accidental misconfiguration, or a server migration. text/html 2026-04-15T08:46:00+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:bosch_configuration&rev=1776242760&do=diff Bosch FPA5000 configuration Configuring Bosch FPA5000 control unit Bosch FPA5000 uses ethernet port to communicate with Siwenoid. In FSP5000 create an FSI server node under nodes. ---------- (The default Net Node, Group and RSN must be ok) Edit FSI server node's ip properties, this IP Address will be the remote PC's IP. Multicast Address is also neccessary for siwenoid so as Port Number. text/html 2026-03-24T22:17:11+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:cerberuspro_configuration_new&rev=1774390631&do=diff CerberusPro configuration (standalone) CerberusPro (SIEMENS) uses the BACnet protocol to communicate with Siwenoid. Communication settings are made in the FXS72xx editor of the CerberusPro control unit. To enable Siwenoid to communicate with the CerberusPro panel, BACnet communication must be enabled on the panel. On the text/html 2026-04-15T08:50:17+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:cerberuspro_safedlink_configuration&rev=1776243017&do=diff CerberusPro configuration (SAFEDLINK) CerberusPro (SIEMENS) uses the BACnet protocol to communicate with Siwenoid. Communication settings are made in the FXS72xx editor of the CerberusPro control unit. To enable communication, BACnet must be enabled on the panel. On the text/html 2026-03-17T14:16:07+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:creating_categories&rev=1773756967&do=diff Creating Categories This page describes how to create and configure event categories in SIWENOID v2, and how to set their display priority. What Is a Category? A category in SIWENOID v2 is a classification label assigned to every event and treatment (status) in the system. Categories are the primary way SIWENOID v2 organises, colours, and prioritises events across the entire operator interface. Every signal log entry, every datapoint status, every map icon highlight, and every count in the ca… text/html 2026-03-17T14:11:01+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:creating_forced_actions&rev=1773756661&do=diff Creating Forced Actions This page describes how to configure Forced Actions in SIWENOID v2. A Forced Action is a mandatory operator intervention that must be completed before an event in a specific category can be acknowledged. It enforces a structured, documented response to security events. text/html 2026-03-17T14:18:06+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:creating_module&rev=1773757086&do=diff Creating Module This page describes how to configure communication modules in SIWENOID v2. Modules are the components that enable SIWENOID v2 to send outgoing notifications — such as SMS messages and emails — in response to events. Modules are created once and then referenced by Tasks (see the text/html 2026-03-17T14:08:41+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:creating_tasks&rev=1773756521&do=diff Creating Tasks This page describes how to create and configure Tasks in SIWENOID v2. Tasks are automated actions that SIWENOID v2 executes automatically when a defined event occurs in the system. They allow the system to respond to security events without requiring manual operator intervention. text/html 2026-03-17T14:22:32+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:everyday_operation_of_siwenoid_v2&rev=1773757352&do=diff Everyday Operation of SIWENOID v2 This page describes the daily operational use of SIWENOID v2 from the operator's perspective. It covers the event categories bar, the signal log and all its controls, how to handle alarms step by step, how to use the event log for searching and filtering, and how to export event data. text/html 2026-03-17T14:30:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:license_upgrade&rev=1773757846&do=diff License Upgrade This page describes how to request and apply a license upgrade for SIWENOID v2. A license upgrade is required when the current license limits need to be increased — for example, when expanding an installation with more datapoints, adding additional client workstations, or adding additional server nodes. text/html 2026-03-19T15:35:41+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:logical_containers&rev=1773934541&do=diff Logical Containers This page explains what physical and logical containers are, how datapoints are imported into SIWENOID, and how logical containers allow engineers to reorganise the imported datapoint structure for daily operation. Physical Containers — Connecting to a Control Panel text/html 2026-03-19T16:35:19+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:obejcts_permissionsv2&rev=1773938119&do=diff Object Permissions V2 This page describes the Object Permissions (Object Restrictions) system in SIWENOID v2. Object permissions control which datapoints, treatments (statuses), and commands specific users or user groups can access. They form the second layer of access control in SIWENOID v2, operating alongside user-level permissions. text/html 2026-03-17T14:35:10+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:restore&rev=1773758110&do=diff Restore This page describes how to restore a SIWENOID v2 installation from a backup file. A restore operation is used when recovering from a hardware failure, software corruption, accidental misconfiguration, or when migrating the system to a new server machine. text/html 2026-04-15T10:38:08+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_-operation_manual_de&rev=1776249488&do=diff Siwenoid v2 Betriebshandbuch Anmeldung Wenn der SIWENOID v2 Client gestartet wird, verbindet er sich automatisch mit dem Server. Sobald die Verbindung hergestellt ist, erscheint der Anmeldedialog. Geben Sie Ihren Benutzernamen und Ihr Passwort ein und klicken Sie dann auf text/html 2026-03-19T16:59:22+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_-operation_manual&rev=1773939562&do=diff Siwenoid v2 Operation Manual Logging In When SIWENOID v2 Client is launched, it connects to the server automatically. Once the connection is established, the login dialog appears. Enter your username and password, then click Login. The bottom of the dialog shows the name of the server you are connected to. text/html 2024-07-25T07:45:18+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_android_client_manual&rev=1721893518&do=diff Siwenoid v2 Android client manual Siwenoid android client description 1. Server access address To enter the server access address, press the framed icon on the left image, then on the screen that appears, enter the access address in the text input box according to the pattern on the right, and then press the save button. text/html 2024-07-25T07:43:04+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_aritech_configuraion&rev=1721893384&do=diff Siwenoid v2 Aritech configuration Setting up the Atc 1000 for an Aritech control panel [Converter] For communication we will need an Atc-1000 Ethernet converter with the following settings. The default IP address for the ATC-1000 is 192.168.2.1 Connect to a computer via Ethernet, then enter the above IP address into your browser. text/html 2024-07-25T07:44:42+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_cctv_configuration&rev=1721893482&do=diff Siwenoid v2 CCTV configuration Siwenoid configuration files [Configuration files] CCTV service: In order to enable the Server or Client CCTV service, a CCTV node needs to be present in the Services section of the given configuration file as shown in the picture above. text/html 2026-03-17T13:42:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_first_run_after_installation&rev=1773754977&do=diff SIWENOID v2 — First Run After Installation This page describes what to do immediately after the SIWENOID v2 installation is complete. The goal of the first run is to verify that all server services have started correctly, then connect the Client application to the Server and log in for the first time. text/html 2024-07-25T07:41:25+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_galaxy_dimension_configuration&rev=1721893285&do=diff Siwenoid v2 Galaxy Dimension configuration Configuring Galaxy control unit Galaxy Dimension uses internal RS232 port to communicate with Siwenoid. Use GD editor tool to set some parameters. In Group Mode set Enable Groups (program step:63-Options 1-1-1). text/html 2024-07-25T07:44:26+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_inim_previdiamax_modbus_configuration&rev=1721893466&do=diff Siwenoid v2 INIM PrevidiaMax Modbus configuration Siwenoid container parameters [Parameters] Parameters: Host IP: The IP address or hostname where the INIM PrevidiaMax panel can be found on the network. Port: In the case of direct ethernet connection the port number is text/html 2026-03-17T14:03:31+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_intrusion_detection_system&rev=1773756211&do=diff SIWENOID v2 — Intrusion Detection System This page describes how SIWENOID v2 represents and manages intrusion detection subsystems. It covers the datapoint hierarchy structure for intrusion panels, how to verify a device connection, how to use zone commands and treatments, and how to use the Group & Zone States view for a comprehensive overview of the entire intrusion installation. text/html 2026-04-30T10:13:29+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_map&rev=1777544009&do=diff SIWENOID v2 — Map This page describes the map function in SIWENOID v2. Maps provide a graphical representation of a physical location — floor plans, building layouts, or site diagrams — with live datapoint status icons overlaid on the image. Operators can use maps to monitor the status of sensors, zones, and other datapoints based on their physical position at a glance, instead of navigating through the datapoint hierarchy tree. text/html 2024-07-25T07:43:41+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_minimax_configuration&rev=1721893421&do=diff Siwenoid v2 Minimax configuration Connecting Mobus RS422 and ATC-1000 [Connecting MObus] Modbus RS422 jumpering [RS422] MxSyscon configuration (Modbus configuration, Minimax fire alarm programming interface) [Add and manage modules] XML file MXGUARD requires an XML file to be imported. This can be extracted from MxSyscon: text/html 2024-07-25T07:43:25+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_modbus_configuration&rev=1721893405&do=diff Siwenoid v2 Modbus configuration Modbus description We need to ask the PLC programmer for a table containing the addresses of the control panels and the device addresses belonging to the control panel, as well as the treatments and which bits are associated with them text/html 2024-07-25T07:41:54+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_paradow_api_configuration&rev=1721893314&do=diff Siwenoid v2 Paradox API configuration Siwenoid container parameters [Parameters] Parameters: Host IP: The IP address or hostname where the IP150 communicator can be found on the network. Port: The TCP port of the IP150 communicator used for the communication. The default is port 10000 text/html 2024-07-25T07:41:43+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_paradox_configuration&rev=1721893303&do=diff Siwenoid v2 Paradox configuration Configuring Paradox EVO192 Paradox EVO192 can connect to Siwenoid through a Paradox PRT3 interface modul. It ensures an RS-232 connection to Paradox panel. Most of newer computers haven't got any serial (RS-232) connection. That's why we need a TCP-IP to RS-232 converter. In this configuration tutorial, we will use an ATC-1000 converter. text/html 2024-07-25T07:44:09+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_relaydroid_configuration&rev=1721893449&do=diff Siwenoid v2 Relaydroid configuration Siwenoid-Relaydroid communication setup For the setup we need the relaydroid's connection IP address, through which the device can be accessed, and a valid web admin user account/password for the device. The default IP: text/html 2024-07-25T07:42:04+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_sintony_configuration&rev=1721893324&do=diff Siwenoid v2 Sintony configuration Sintony configuration with Sylcom To be able to connect to the control panel with Sylcom, we will need a SAQ11 programming cable, which we need to connect to port J7 on the SI410 motherboard, the other end to the pc! text/html 2026-04-15T08:50:50+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:siwenoid_v2_spc6xxx_configuration&rev=1776243050&do=diff Siwenoid v2 SPC6xxx configuration Setting up Internet Explorer The SPC system can only be configured from Internet Explorer. Before connecting to the SPC make sure that SSL3 encryption is enabled in the browser! In the menu select Tools → Internet Options → Advanced tab. text/html 2026-03-17T13:41:04+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:swnd_v2_inst&rev=1773754864&do=diff SIWENOID v2 Installation This page describes the installation procedure for SIWENOID v2 on a Windows-based server or workstation. The installation is performed by a commissioning engineer. The installer package contains all required components: the Client application, the Server application, and the License Service. text/html 2026-03-19T16:54:55+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:system_prefeernces_and_engineering_options&rev=1773939295&do=diff System Preferences and Engineering Options This page provides an overview of all configuration sections available in the SIWENOID v2 Settings menu. Every system setting is accessible from File → Settings. Menu items and their submenus are visible only to users with the appropriate permissions. text/html 2026-03-17T13:49:15+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:the_starting_screen_of_siwenoid_v2&rev=1773755355&do=diff The Starting Screen of SIWENOID v2 This page describes the main user interface of SIWENOID v2 as it appears after a successful login. It explains the purpose and function of each screen area, the workspace layout system, the datapoint hierarchy panel, and the event log. Understanding this screen is essential before proceeding with system configuration, as all engineering and operator functions are accessed from here. text/html 2026-03-19T15:57:53+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:treatment_editing&rev=1773935873&do=diff Treatment Editing This page describes how to view and edit Treatment definitions in SIWENOID v2. Treatments are one of the most fundamental configuration elements in the system — they define how SIWENOID v2 interprets and categorises every signal received from every connected subsystem. text/html 2026-03-19T16:23:49+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:usage_of_datapoint_hierarchy_screen&rev=1773937429&do=diff Usage of the Datapoint Hierarchy Screen This page explains the Datapoint Hierarchy screen in detail — how the tree is structured, what information is shown for each datapoint, how to read and use the status and command panels, and how to interpret the per-datapoint event history. The Datapoint Hierarchy screen is the primary tool for engineers to inspect, diagnose, and control individual points in the connected security subsystems. text/html 2026-03-17T13:44:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://doku.siwenoid.com/doku.php?id=swnd2:user_permissions_v2&rev=1773755084&do=diff User Permissions V2 This page describes how to create user accounts and configure their permissions in SIWENOID v2. User management is permission-based — every function in the system can be individually granted or denied per user. Only users with administrative access can create or modify accounts.