Fire

The table below shows the current FSM, FSI and MPC versions compatibility:  

Do you want to move the license activated on existing computer/server to another computer/server (FSM - Fire Monitoring System)?

Is always recommended to backup the database before running the default process. Find out in this article the steps to restore default FSM (Fire Monitoring System) configuration

With FSM 5.6  the database.xml structure was slightly changed and FSM 5.6 is supporting only the new database.xml structure. This is leading after upgrade to a loss of the configured symbols (only the symbols, not the content of the devices configured on the floor plans). Therefore after upgrading from older FSM version (e.g. 5.2) to 5.6, the already configured symbols of sensors on maps are not shown correctly, they are shown are dots/circles.   Please note: If before executing the file provided below the application was opened and the sensor properties were edited by approving > at that step the symbols changed to the default symbol and the previously configured symbol cannot be recovered.

If FSM needs to be connected to a new panel (network), then proceed as it is described in this article:

The license key is not stored in plain text therefore is not possible to view, but the associated order number can be identified.

This article indicates where you can find the log files for FSM client and for FSM server

Check out this article and find out where are the FSM Alarm and Events logs stored and what is the size limit

Check this article and find out what's new in FSM version 5.6.1

Follow this step-by-step guide from this article and find out how to stop and restart the FSM Server service

Any related HW change in the FSM server will lead to license not being valid and will need to be transferred.

Library is offering 3 different sizes of detectors and can be customized. See this article and find out how you can customize Symbols (icons) - FSM

To check Directx and graphics card capability you can use the dxdiag tool provided with Windows OS.

The cause of the error is combination of group address and the text length of the group label as defined in RPS as shown in this article

Have a look at this article and see how you can setup the FMS - OSD Logo

This article explains if possible to install Fire monitoring system (FSM) in a virtual environment

In FSM client select the "About" button in the upper right hand side, the About window opens and license info is displayed as shown in this article

Follow the steps from this article to see the labels from the sensors in FSM which are configured in RPS

This article contains the FSM - Anomalies symbols and their description

Follow this article and learn about the option which allows you to configure the color for each state & sensor in FSM