Experion PKS/PMD
Opreating system and
networking
Local area networks and FTE
Network
HMI PMD HMI DM • The PMD automation
Web Server Web
system consists of
– a PMD server (PDS)
– HMI user interfaces
SystemNet (TCP/IP,FTE)
– a Design Module (DM)
– the System Net local area
network
FC FC
Profibus Profibus
– Field Controllers.
IOLINE IOLINE
IOC
IOC
IOC
IOC
Network protocols
PROTOCOLS AND NETWORK STANDARDS
• The System Net is based on the Ethernet standard:
– Physical layer = cabling and devices
– Ethernet = electrical signals at a rate of 10 or 100 Mbit/s are used
between the devices and 100 Mbit/s or 1 Gbit/s can be used between the
network switches.
– FTE = selecting the healthy route from the redundant bus
– UDP = connectionless protocol between the devices (messages that are
intended for general distribution for all network devices)
– TCP = connection-oriented protocol between devices (the message is
sent to a certain device and the sender waits for the acknowledgement of the
message)
Network applications
– Upper layers = inter-application data
Network applications TCP or UDP
TCP or UDP IP
IP FTE
Ethernet Ethernet
Physical layer Physical layer
Physical layer
Physical layer = cabling and devices
Network applications
• Typically CAT5 cabling system allow to use 100/10Mbit/s
Network applications TCP or UDP
transfer speed (speed selection or automatic choice by
system) TCP or UDP IP
• Network cards, connectors, cables, switches and possible IP FTE
routers are the physical components of Experion PKS
network Ethernet Ethernet
• Now a days most common is to use Twisted Pair shielded or Physical layer Physical layer
not shielded cables in short distances (<100m)
• Optical Fibre is useful in magnetic field areas (near motors
etc.) and long distance transmission
• For diagnostic measurements you need cable tester and in
projects all cables should be tested and documented.
Ethernet layer
Ethernet layer = hardware address and frame type in transmission
• Ethernet layer means that 802.2 type frame is Network applications
used in transmission
• This layer is using the hardware MAC addressies Network applications TCP or UDP
to send and receive packets in the network
TCP or UDP IP
• MAC address example: 00-04-75-9A-C3-A1
• This address you can get by command: IP FTE
ipconfig/all from your PC or by DAXMON from
FC: RUN IPCONF Ethernet Ethernet
• this MAC address is used to transmit packet
inside one sub network area (= ROUTER area) Physical layer Physical layer
from sender’s network card to receiver’s network
card
Sending MAC Receiving MAC IP frame/FTE Frame
FTE (1)
Network applications
FTE layer = Fault Tolerant Ethernet (=FTE node)
Network applications TCP or UDP
• FTE stands for Fault Tolerant Ethernet and
actually mean that the system net cabling TCP or UDP IP
and switches are duplicated thus enabling
IP FTE
redundant and reliable communication
between PMD system units – FCs and PDS. Ethernet Ethernet
• FTE is like a switch, which use two MAC
addressies to select the port in use to Physical layer Physical layer
transmission
• Computers and FC needs two network Upper levels
connections to be able to run FTE protocol
• FTE node number is defined in DHCP and
System Builder/Local area Networks IP level
FTE Node
First MAC address= Second MAC address=
First network card Second network card
Ethernet cable
FTE operation (2)
Applications FTE User Tool FTE
OSI Stack Node
Layer 5, 6, 7 Comm API
User Mode
Kernel Mode
Transport/
Layer 3, 4
network
protocols
Fault-Tolerant
NIC Switch FT Manager Ethernet
Software
Layer 2
Driver A Driver B
Control flow
NIC A NIC B Data flow
Layer 1
Dual LAN or Single LAN
FTE (3)
4 possible routes Node
k
A B
LAN A LAN B
A B
Node
i
FTE (4)
• Configuration parameters:
– Node numbers
• Each department’s FTE devices are numbered with node number witch is
defined for each device in the System Builder (it is not allowed to have
two devices provided with the same node number)
– MsgLossAllowed
• Parameter indicates, how many successive diagnostic messages the FTE
fault detection protocol is allowed to lose. The default value is normally
between 0 – 2
– PulseInterval
• Determines the transmission rate of the diagnostic messages. Diagnostic
messages are sent less frequently when the value is higher and then also
the fault recovery is slower.
– DisjoinInterval
• Determines the time that the FTE allows other FTE nodes not to send
diagnostic messages. If the time is exceeded, the device is declared to have
left the FTE network = defines the interval when a silent node is
”dead”
IP
IP level = packet frame with sender IP – receiver IP Network applications
• IP protocol is not checking transmission or order the Network applications TCP or UDP
packets are received
TCP or UDP IP
• Inside IP frame are ARP, ICMP and IGMP protocols:
• ARP make thé link between IP and MAC IP FTE
• ICMP is transmission status and error checking
and for example PING command is using ICPM Ethernet Ethernet
protocol
• IGMP is multicast protocol for multicast routers Physical layer Physical layer
etc.
• IP address is typically in eighter official NIC address
used in INTERNET connections or in public area not
connected to INTERNET network.
•Our System Net is using normally public addressies
and is not connected to MILL NETWORK or
INTERNET
•IP address is 32 bit’s and all network equipments
using TCP/IP protocol must have unic IP address
inside ROUTER/FIREWALL sub network
•IPCONFIG tell the IP address of your computer or
RUN IPCONF in FC/DAXMON
•PING command to your own IP address tell is your
network card working
TCP and UDP
TCP = Transmission Control Protocol and UDP = User Datagram Protocol
• TCP is connection- and error checking protocol to transmit data in
Ethernet network
• TCP confirm data transfer and check also errors in packets
• TCP packets are also arranged in sending order by receiver
• TCP is using sockets (=service<->port) in communication
(c:\Winnt\system32\drivers\etc\services)
• UDP protocol is not checking the transmission and higher level
application must check the data transmitted by UDP
Network applications
• UDP is used normally only for small transfer amounts.
Network applications TCP or UDP
TCP or UDP IP
IP FTE
Ethernet Ethernet
Physical layer Physical layer
Device naming (1)
• Department switches (DS)
– xxxDSyyy, where xxx is the department number. If the automation system
has several departments, each of them gets a number successively,
beginning from 001.
– yyy is number 001 for the department switch of Side A.
– The department switch of Side B gets number 002.
– For example, if the department number is 001, the names of the
department switches are 001DS001 (Side A) and 001DS002 (Side B).
• Edge switches (ES)
– xxxESyyy, where xxx is the department number. If there are several
departments, each of them gets a number successively, beginning from
001.
– yyy is number 001 for the edge switch of Side A. The edge switch of Side B
gets number 002. If the department has several edge switches, Side A edge
switches get odd numbers successively (001,003,005,…). The Side A edge
switch number 001 is backed up by Side B edge switch number 002. The
edge switch number 003 is backed up by edge switch number 004 and so
on. The following figure clarifies the situation.
Device naming (2)
Device naming (3)
• Routers
– Departments are connected together with a single router, the
router name is PMDRA.
– Departments are connected together with two routers (redundant
routing), the router names are PMDRA and PMDRB.
• PMD server
– Max. 8 characters. The name is xxxPMDA, where xxx is the
department number. PMDA stands for the PMD server. For
example, if the department number is 001, the name of the server
is 001PMDA.
• Remote HMI server (RHS)
– Max. 8 characters. The name is xxxRHS1, where xxx is the
department number.RHS stands for Remote HMI Server. 1 is the
number of the server.
Device naming (4)
• HMIWeb user interfaces
– Max. 8 characters. The name is xxxHMyyy, where xxx is the department
number. yyy is the number of the HMI. E.g. department number is 001, the
name of the HMI is 001HM001.
• Desing Module
– Max. 8 characters. The name is xxxDMyyy, where xxx is the department
number. yyy is the number of the DM. E.g. department number is 001, the
name of the first DM is 001DM001.
• PMD controllers
– Max. 8 characters. PMD Controllers’ names are defined in System Builder
(Definition menu/Modules function). Note that these names are used also
in the System Net configuration. E.g. FC01.
• Printers
– xxxPRyyy, where xxx is the department number. PR stands for the printer.
yyy is the number of the printer. The alarm printer gets number 001. The
other printers are numbered successively, starting from 002.
IP addressing (1)
• Private networking idea:
– Addresses can be freely used in private networks but IP packets
with these addresses must not be forwarded to the public Internet.
• IP addressing
example:
IP addressing (2)
• IP addressing example (continued):
FTE number
IP addressing (3)
• IP addressing example (continued):
FTE number
IP addressing example
IP addressies in System Net ( example)
001PMDA (FTE)
001DM001 (no FTE)
10.1.1.71 001HM001 (no FTE)
10.1.1.35
10.1.1.36 10.1.1.191
(10.1.0.11)
001DS001
FC1 (FTE)
001DS002 10.1.1.101
(10.1.0.12)
001HM003
10.1.1.193
001HM004 (no FTE)
(10.1.0.13) (10.1.0.15) 10.1.1.192
001ES001 001ES003
001ES002 001ES004
(10.1.0.14) (10.1.0.16)
001HM002
10.1.1.194
FC3 (FTE)
FC2 (FTE) 10.1.1.103
10.1.1.102
Testing (1)
Using the IP addressies in testing
• To test your network you can use the PING command :
Ping 10.1.1.51
to your own computer (yoy are using DM)
Ping 10.1.1.101 connection from DM to FC1
Ping 10.1.1.11 connection from DM to PDS server
• To test the connection from FC to PDS and HMI:
Open the DAXMON in DM
Connect to DEPT FC1
Give the DAXMON command:
.RUN PING 10.1.1.11 ( connection to PDS)
.RUN PING 10.1.1.201 (connection to HMI)
• If the test don’t give Reply under 100ms you must check the network cable,
connectors and Ethernet connection card’s.
FTE Status monitoring
• Select:
Start => Programs
=> Honeywell TPS
=> FTE Status
Display
• Leave the
computer name as
localhost and
press the OK
button.
FTE Status monitoring (2)
• FC6 Channel A disconnected - FTE status shows us that
channel B of FC6 is alive and keeping the connection.
FTE Status monitoring (3)
• FC6 Channel B also disconnected - complete contact is lost
to the FC6.
FTE Status monitoring (4)
• FC6 Channel A connected, B disconnected - channel A of
FC6 is alive and keeping the connection.
FTE Status monitoring (5)
• PMD server channel A disconnected - FTE status shows us
that the second network card of server is alive and keeping
the connection.
www.honeywell.com
