Beruflich Dokumente
Kultur Dokumente
FPA-5000 Level 2
Release 2.0
Course instructor
Josef Angstenberger
Table of Contents
2. NETWORKING ...............................................................................................................................7
Legend
Hint: Here are some useful facts you will not read in the
documentation but may be very helpful for you and
your customers
This version is needed for the configuration of the FPA-5000 Rel. 2.0. Older ver-
sions can not be used.
This version can also be used for the configuration of the FPA-5000 Rel. 1.3 and
earlier
When opening old configurations with RPS version, they can’t be opened anymore
with previous versions
Ø
With this drop down list one can
filter the elements that shall be
shown in the selection
Ease of use
5. Summary of LSN-Elements
• Overview about quantity and type of LSN Elements at one loop can be received
1.3.1 Layout
n o
n Operations
Features previously placed under communication have been moved
With the older version various options
were offered in the drop down list under
“Communication”.
These options have been moved to the
single nodes
o Options
Consistency Check has been removed
Feature “Setting” has been expanded.
1.3.2 Rules
Activation with time de- Not possible before. Extended configuration possibilities.
lay
Was only offered at
Event triggered rules
Timed activation (activa- Not possible before. Extended configuration possibilities.
tion for a defined time)
Was only offered at
Event triggered rules
Block organization of Not offered before More precise configuration is possi-
rules ble.
Before: When several stated de-
pendent rules had been added to
an element, it was not possible to
individually define the else condition
for every single rule. Now for every
single rule an else condition can be
added.
Feature Comment
Configuration of remote states is Not possible with Event Triggered rule due to
possible security reasons.
Sequence of activation when pro- The rule will be activated whose conditions have
gramming several rules to one been triggered the last (time rule). The assort-
element ment of the rules in RPS is of now relevance.
2. Networking
Connection Drawings
MPC-xxxx-B_Leaflet_A3.pdf (installation manual)
FMR-5000-xx_Leaflet_A3.pdf (installation manual)
PI (Product Information) – available E04/2008
Very important.
If this is not done properly the network setting might not be done
correctly, like
address and dip switch setting
wrong assignment of CAN wires between the node
If this is done well, the user will save time at all stages to follow.
Things to do / define:
Loop or bus topology?
Will group scope be used? If yes, how many groups?
Network scope used? If yes, which nodes?
Draw down the nodes and assign the single address to the single node (same
group address for all nodes in the same group, only different sub-address)
Draw down the cables connecting the different nodes and assign a number to
every wire
Printer etc.: is it used for all nodes or only for specific?
2.2 Set physically the rotary and dip switches on every node
For more examples in more detail about the setting of the rotary switches at different
topologies see in documents recommended above.
Below you find an excerpt of the most important topologies.
2.2.1 On FPA-5000
Rotary Switches
Dip Switches
Loop setting
Bus setting
Use the drawing of the network layout as recommended to do under paragraph 4.1.
It shows
the single nodes
their type (panel or remote keypad)
their address and
the CAN wires connecting the different notes
Example:
Addr. 1.1
Line 4
Addr. 1.4
Line 1
Addr. 1.2
Addr. 1.3
Line 2
Line 3
The configuration of the panel and the remote keypad differs partly.
Below the configuration of the panel is shown. Afterwards the configuration of the re-
mote keypad will be shown.
‒ The OPC server can also be inserted. For the panel networking only the panel and
remote keypad is of relevance. This is why the OPC server shall not be mentioned
in this respect.
‒ Panel and remote keypad have to be inserted separately
‒ Some differences exist at the configuration of the panel and the remote keypad.
Be aware of them.
‒ Here you assign
o the logical node address
o The rotary switches (have to match with the physical setting!)
o the scope (group or network)
‒ Here you define the cables the CAN interfaces are connected to.
‒ The default setting of the cables can not be adopted. You need to assign the ca-
bles.
‒ This can be done automatically or manually.
Node
1.1.
n
o
p
q
r
n Node address
Assign address of the Group and Node (sub
address).
o Rotary Switches
Has to be similar to the physical Rotary Switch
setting of this device (MPC or Remote Key-
pad).
Attention: This number must be unique, may
only be used once.
p Scope
Here you assign if the device shall be a group
or network device
r Label
Assign a clear description to this device. This
helps to keep the overview.
s IP Setting
Only needed to assign when using an TCP/IP
connection
III Assigning the CAN cables that connect the nodes
With this setting you tell RPS how the single CAN1 and/or CAN2 interfaces are
connected to the other CAN1 and/or CAN2 interfaces. This is done by assigning
the exact cables that connect the various CAN interfaces.
Process:
Define for every CAN interface the cable it is physically connected to.
Do this for every node and every CAN connection of the nodes.
For every cable two interface connections have to be defined.
Use the drawing you have created before.
Attention: Be very careful and make sure this setting matches exactly to the set-
ting of the physical cables.
n o
n Interface number
Can’t be changed. This is the number of the
CAN Interface of that you double clicked on
above. Here: CAN1 of Node 1.1
o Connect to Line
Here you assign the cable that is (physically)
connected to the CAN interface (here interface
Number CAN1).
Has to be the same line as shown in above
drawing connected to CAN 1 of Node 1.1.
p Bit Rate
Speed can be changed depending on the max.
cable length of cable 1.
Here only these points will be mentioned that are specific for the remote keypad, thus
differ from the configuration of the panel FPA-5000.
I Inserting new nodes
o Automatic connection
The remote keypad will connect automatically
to the panel assigned. It will also display auto-
to matically the messages from this panel.
Only possible to connect to a panel of the
same group.
III Assigning the CAN cables that connect the nodes
The addresses and lines assigned to the single CAN interfaces have to match com-
pletely. Make sure to do this final control after having programmed the addresses and
CAN interfaces.
n
Addr. 1.1
q
Line 4
n
Addr. 1.4
Addr. 1.2
Line 1
o
Addr. 1.3
Line 2
p
Line 3
o p
n, o, p, q = Cable 1-4
It is possible to have above created report changed with RPS. Simply change the setting
to the desired topology (loop, bus, bus with redundancy etc.).
Attention: The cable setting in RPS will not be done automatically when creating or chang-
ing the topology report. The cable setting still has to be done manually.
The configuration has to be downloaded into every node (OPC server not included) of
the panel network.
When changing the configuration of one panel, the changed configuration has to be
downloaded into every single panel again. It is not sufficient to download it only in the
panel that has been changed.
n Press “Operation”
Select “communication”
o p Select “Connect”
or
Press button “Connect”
o
n
I Panel topology
II Auto configuration
Window appears.
Configuration can be seen, when open-
ing the paths (here path of FPA5000)
o
n
p
n Shows the network configuration.
Faulty (yellow) or missing (red) elements are marked in colors.
Click on these market elements and the differences will be shown between the
configuration that will be entered and the existing.
o Shows the differences between the configuration that will be loaded and the
existing configuration (configuration that shall be integrated).
Configuration is integrated.
Even new setting of state dependent rules
(“Blocks of state dependent rule) has been
transformed / adopted
It is possible to use triggers of one panel to activate e.g. output of another panel.
‒ Some differences exist at the configuration of the panel and the remote keypad.
‒ Here you define the cables the CAN interfaces are connected to.
3.5.2 Export
3.5.3 Import
The items that have been exported are marked as shown below
Possible scopes:
When time control is configured, this can be synchronized with selected nodes or with
all.
The setting in one panel can be synchronized with all panels of the scope (group) or
to any panel.