FSM 5000 OPC Operation Manual enUS 9007208643043467
FSM 5000 OPC Operation Manual enUS 9007208643043467
FSM-5000-OPC
en User Guide
FPA-5000 OPC-Server Table of Contents | en 3
Table of contents
1 Purpose 4
2 Preconditions 6
3 Installation 7
3.1 Installation of FSM-5000-OPC Software 7
3.2 Remote Access to the FSM-5000-OPC Server from the Building Integration System (BIS) 7
3.3 Backward Compatibility 9
3.3.1 Package: BIS600StateConversion.msi 9
3.3.2 Package: LanguageDependentCommand.msi 9
4 Step-by-Step Configuration 11
4.1 FSP-5000-RPS 11
4.2 Panel Controller MPC-xxxx-B or MPC-xxxx-C 12
4.3 PC/Server 12
5 Troubleshooting 13
6 Technical data 14
7 Appendices 16
7.1 Appendix A.1 - State Table 1 16
7.2 Appendix A.2 - State Table 2 18
1 Purpose
This document contains information on accessing and controlling FPA-5000 networks via OPC
using the FSM-5000-OPC server. It is designed to aid in successfully configuring the FPA-5000
network and the corresponding FSM-5000-OPC server to enable communication between the
two via a single or redundant Ethernet connection. In completing these steps successfully a
functional interface is provided for a subsequent connection to BIS 2.x which functions as
OPC client.
Notice!
Setting up and configuring an FPA-5000 network controlled by an OPC server requires basic
IT knowledge.
The information refers to FSM-5000-OPC Version 1.1.11 and later and supported FPA-5000
software.
192.168.1.2
255.255.255.0
Cat. 5 Cat. 5
Ethernet
FPA_OPC
RSN 004
CAN
RSN 001
RSN 002
RSN 003
RSN 003
Figure 1.1: FPA-5000 network controlled by an OPC server with single Ethernet connection
192.168.1.2
255.255.255.0
Cat. 5 Cat. 5
Ethernet
FPA_OPC
RSN 004
switch
CAN
RSN 001
RSN 002
RSN 001
RSN 003
RSN 003
Figure 1.2: FPA-5000 network controlled by an OPC server with redundant panel
2 Preconditions
The following must be available to set up an OPC server in an FPA-5000 network:
– FPA-5000 network with MPC-xxxx-B or MPC-xxxx-C
– ADC-5000-OPC license card
– Latest FSP-5000-RPS installation CD
– The correct FSM-5000-OPC Server version for the respective FPA-5000 release (available
on FSP-5000-RPS installation CD or download from Extranet). Look up the compatible
version in the readme file of the FSM-5000-OPC software.
– Existing Ethernet network with Cat. 5e cable
– PC to install FSM-5000-OPC on
3 Installation
Notice!
If the prerequisite software is not present install it from the PreRequisites folder of the
FSP-5000-RPS installation CD or download it from http://www.microsoft.com/downloads/en/
default.aspx
Notice!
The installation of FSM-5000-OPC is only released for the Windows operating systems listed
in Technical data, page 14. For other operating systems the installation may succeed but
was not tested and is therefore on your own risk.
Server side PC
Notice!
Consider the naming conventions for users, groups and passwords (“MgtS-Service”
“BISUsers“) given in this description. The Building Integration System (BIS) internally makes
use of these conventions. As BIS internally always assumes the same user and password by
convention it is not necessary to logon as a distinct user or enter the password. If you
remotely access the FSM-5000-OPC server with another client, you are free to choose names
and a password on the server side, as long as you specify the matching logon when your
client connects to the OPC server.
All of the following settings refer to the PC running the OPC server.
Notice!
The following steps are based on the Windows XP operating system. For all other operating
systems the paths to the respective dialogs might be slightly different.
Notice!
The user name and password must be identical with the user of the login server.
6. Add the new group “BISUsers” by using Access Permissions – Edit Defaults – allow
Local and Remote Access.
7. Add the new group “BISUsers” by using Launch and Activation Permissions – Edit
Defaults – allow Local and Remote Launch and allow Local and Remote Activation.
8. Add the new group “BISUsers” by using Launch and Activation Permissions – Edit Limits
– allow Local and Remote Launch and allow Local and Remote Activation.
9. Reboot the PC.
Set Local Security Policy
Perform the following procedure to set the Local Security Policy.
For operating systems Windows XP / Windows Server 2003 / Windows 7 / Windows Server
2008:
1. Go to Start - Control Panel - Administrative Tools, and select Local Security Policy.
2. Open the tree on the left side: Security Settings - Local Policies- Security Options.
3. Select on the right side: Network access: Sharing and security model for local accounts.
4. Right click on this selection to open Properties and choose Classic– local users
authenticate as themselves.
5. Close all windows and restart the PC.
6. Open dcomcnfg and go to services (Local).
7. Select FPA5000OPCServer - Properties and open the Log-On tab
8. Choose radio button This Account – User: MgtS-Service and the password.
9. You are requested to restart the service in order to activate the changes. Select Stop and
Start (or Restart).
Client side PC
On the PC running the FSM-5000-OPC client software connect to the server with the same
logon you used to start the service. This also applies if you install both on the same PC. The
OPC server installation routine installs the service for the local system account by default.
Change the service to “MgtS-Service” when you use the OPC server with BIS.
Notice!
Only use these packages if you require compatibility with solutions designed for versions
prior to version 1.1 of FSM-5000-OPC server.
4 Step-by-Step Configuration
4.1 FSP-5000-RPS
1. Open the FSP-5000-RPS programming software.
2. In an existing 2.x configuration select “Nodes” in the tree view and choose “Create
FPA-5000 OPC- Server” in the context menu.
A new node with name FPA-5000 OPC-Server is created and a dialog box for configuration
is opened.
3. Configure the OPC server node.
Enter the virtual RSN and logical node.
4. Choose IP Settings... to enter the IP settings dialog.
5. Edit the fields accordingly. IP Address and Subnet Mask are mandatory fields, Gateway
is optional.
Notice!
The settings must match the network adapter/card settings of the computer the FSM-5000-
OPC Server will be installed on!
The values of Net Group and Node Address, the RSN and the IP address are required to
configure the OPC server.
Notice!
It is mandatory that this FPA-5000 node is then assigned to the OPC server!
13. Choose the country and the language from the list
Notice!
Take care about the country and language settings. BIS 2.x will display commands and
detector names in the selected language.
4.3 PC/Server
1. Connect the Cat.-5 cable to the PC Ethernet port. Afterwards open the DOS command
window and successfully “ping” the panel controller.
2. Right click on the OPC icon in the taskbar notification area and open the Connection
dialog. A list with all identified panels and their respective connection status is displayed.
If the configuration was successful, all panels which are assigned to the OPC server
should have the status “connected”.
You can also find these information in a log file, located on C:\Program Files\Bosch
\FPA5000 OPC-Server\Log (for Windows XP, might be slightly different for other
operating systems).
5 Troubleshooting
If the configuration of the FSM-5000-OPC server doesn’t work with the FPA-5000 network try
the following:
– Confirm on the panel controller that the IP address is assigned and “ping” the OPC
server.
– If the Ping request is answered but the configuration still doesn’t work please check
– all settings on the panel,
– all settings in the FSM-5000-OPC Configuration Editor,
– the Ethernet adapter settings in the Window’s System Configuration.
– De-activate firewall
– Follow these steps:
– Stop OPC (see “Service” tab in Configuration Editor)
– Delete bin file(s) under C:\MPOPCServer\Repository
– Start OPC → A new file per node will be created.
– If no elements are shown, check whether the Repository folder exists and whether it
contains a bin file for each node. The files are located under C:\MPOPCServer\Repository.
– On the MPC panel controller go to Diagnostics – Network – Routing table.
A table with routing information is displayed. All networked nodes that can be reached via
the panel and that are recognized within the system network are displayed under Node.
Aside the respective interfaces via which the connected network nodes are connected to
the panel are displayed. If the OPC server configuration is correct there must be an entry
under Node with the RSN of the OPC server node and the interface “UDP tunnel”.
– Make sure that the panel controller does not show any troubles which could concern the
OPC server node or the network communication in general.
– Verify that OPC card is detected by panel:
Choose in the start menu of the panel controller: Diagnostics - Hardware - Address cards
6 Technical data
Supported OPC standards:
– DA 2.0
– AE 1.01
Other Standards
– “BIS Common Requirements” (Bosch standard).
Supported operating systems:
– Windows 2008 Server (32-bit and 64-bit)
– Windows 2008 Server R2 64-bit
– Windows 7 (32-bit and 64-bit)
– Windows 8.1 (32-bit and 64-bit)
– Windows 10 (64 bit)
Limits
For each panel approximately 2000 OPC items can be created in maximum configuration.
Memory
For configuration data caching a file with approximately 200kb is stored for each panel in the
repository folder.
Licensing
Each OPC Server requires an OPC license card (ADC-5000-OPC) in one of the assigned
FPA-5000 panels.
Additional Information
LAN Technology Specifications:
For example: 100BASE-TX indicates a Fast Ethernet connection (100 Mbps) that uses a
twisted pair cable capable of full-duplex transmissions.
Cable Grade Capabilities
7 Appendices
7.1 Appendix A.1 - State Table 1
OPC Item Value Internal Panel Description
Compound State
600 Invalid
601 Normal
602 Fault
603 Fire
606 Heat
608 Smoke
609 Activate
611 Tamper
617 On
618 Off
619 Pollution
621 Monitor
622 Water
628 Not enough address Address card changed and now there are less
space addresses licensed than points configured
629 Address card tamper The countdown after address card removal is
finished, addresses are to be switched off
630 Fire internal Internal fire, results from a usage type “FIRE_INT”
645 Walktest On
0 Missing Zone FG
2 Fade-out/Skip ABL
5 Stand-by/Control off GE
7 Control On STE
8 Malfunction ground ES
9 Criterion -4 K4
10 Criterion -3 K3
11 Criterion -2 K2
12 Malfunction generic G0
13 Emergency alarm H1
14 Int-Fire F3
15 Pre-Fire F2
16 Ext-Fire (TU) F1
17 Trigger disarmed A6
18 Intern-Alarm A5
19 Int-Sabotage A4
20 Ext-Sabotage (TU) A3
21 Ext-Intrusion (TU) A2
23 Ext-Malfunction.(TU)/Ext-Fire. (TU) A0
24 Stand-by/Off PE
25 On P2
26 Acknowledgement P3
27 Malfunction P4
29 Switch Off P6
39 Maint.-Control On R-STE
41 Maint.-Criterion-4 R-K4
42 Maint.-Criterion -3 R-K3
43 Maint.-Criterion -2 R-K2
44 Maint.-Malfunction R-G0
46 Maint.-Int-Fire R-F3
47 Maint.-Pre-Fire R-F2
48 Maint.-Ext-Fire R-F1
49 Maint.-Triggering R-A6
55 Maint.-Malfunction-Ext R-A0
68 Light Pollution V2
69 Heavy Pollution V1
87
89 Periph. Control On P8
90 Light Malfunction G1
91 Line Malfunction G2
92 End of Paper PA
93 Triggering Disarmed A7
94 Mains Fault
95 Battery Fault
Table 7.2: Appendix A.2 - State Table 2