Sie sind auf Seite 1von 65

Supervisory Control & Data

Acquisition
Communication Technology
•Seriplex FAQ
•CAN FAQ Which Network Do I Use?
•Interbus S FAQ Modbus
•IBS club
•WorldFIP Interbus S
•LON works Modbus Plus
•Modbus
ASI Profibus
•Fieldbus compare
•Honeywell
•Control competition Echelon CAN

Ethernet Device Net

Seriplex SDS
What is a Network ?
A group of devices physically connected together for the
purpose of sharing information, resources and a common
transmission medium.
Why do you need a network?
 Control the flow of information
• security, accessibility, data control
 Centralize resources
• save cost on local work stations and peripherals
 Simplify data / software management
• Backups, IS maintenance
• Share information with multiple users
 Distribute tasks
• reduce local need CPU power
What makes a network work ?
Computers, printers …...
Network interface cards
Network adapter Software drivers
Network Cabling
Network protocols
The Basic Types of Networks

Master / Slave
(Similar to the teacher- student relationship)

Peer to Peer
(Similar to the workgroup concept)

Client / Server
(Similar to an automated teller transaction)
Master / Slave Network
Central Control and Administration
Central Processing of Information
Polling of Stations
Master

Slave Slave Slave


Peer To Peer Network
 Distributed Administration
 Independent Processing of Information
 Shared Transmission Medium
Client / Server Network
 Central Network Administrator
 Controlled Flow of Information
 Independent Processing of Information
 Shared Transmission Medium
How is a network put together ?
 The OSI model uses 7 layers to categorized the main
elements of a basic network

Application
Presentation Layers Designed
for Data Processing
Session

Transport
Network
Layers Designed
Datalink Layer for Communications

Physical Medium
OSI Model Layers
 A Model is used to ensure Compatibility
 Each station utilizes the same Protocol Stack

Application Application

Presentation Presentation

Session Session

Transport Transport

Network Network

Datalink Layer Datalink Layer

Physical Medium Physical Medium


OSI Model: Flow of Data
 Logical Structure
 Data Multiplexing

Application Application
Presentation Presentation

Session Session
Transport Transport
Network Network

Datalink Layer Datalink Layer

Physical Medium Physical Medium


Hardware / Software integration
 The upper five layers are implemented with software
 The lower two layers are implemented with hardware

Application
Presentation Software Layers

Session

Transport
Network

Datalink Layer Hardware Layers

Physical Medium
OSI Model vs. Ethernet -TCP/IP
 Ethernet does not incorporate all 7 layers because it’s
development predated the OSI model

Application

Presentation

Session Application
Transport Transmission Control
Network Internet Protocol

Datalink Layer CSMA - CD

Physical Medium Twisted Pair/ Fiber Optics

CDMA/CD – Carrier Sense Multiple Access with Collision Detection


OSI Model vs. Field Bus Model
 The typical field bus only utilizes 3 layers. The functions
of the other layers are either built into the ASIC chip or the
application layer

Application
Presentation

Session

Transport
Network Application
Datalink Layer ASIC Dependent
Physical Medium Multiple Mediums

ASIC - Application-Specific Integrated Circuit


What is common to all networks ?
 Application message - dependent on software package
• The message is created by the application package
 Media Access Control
• The procedure for sharing the physical medium
 Logical Topology
• The associations between the devices
 Physical Topology
• The layout of all the device connections
 Transmission Mediums
• The physical path used between the devices
Various Transmission Mediums

 Coaxial Cable Jacket of PVC or Teflon

Jacket made of PVC or Teflon

 Twisted Pair

 Optical Fiber

 Wireless
Basic Physical Topologies
 Bus Topology
 Star Topology
 Ring Topology
 Free Topology
 Hybrid Topology
Bus Architecture Topology
 Single Channel - Broadcast oriented
• More delicate to maintain signal integrity based on cable
selection, distance and drops/taps
Star Architecture Topology
 Central Hub
• multi-port repeater
– Loose star = lost network
• channel selecting switch
Ring Architecture Topology
 Each device is a repeater
• Loose node= broken ring

Token Ring
Free Topology
 Devices are wired in any combination of topologies
 Usually requires one terminator

Star
.
term
Loop
Bus
Hybrid Architecture Topology
 Non-rooted Tree Architecture (ex.- Internet)

X25
Phone System
Network Extenders
 Repeater and Hub Repeater and Hub

 Bridge
 Router
Bridge
 Gateway

Gateway Router
Physical Layer Network Extenders
 Repeater or Hub
• Active repeaters regenerate the signal (store and forward)
• Passive repeater amplifies the signal; adds no latency

Application Application
Presentation Presentation

Session Session

Transport Transport

Network Network

Datalink Layer Datalink Layer

Physical Medium Physical Medium


Physical Medium Physical Medium
Data Link Layer Network Extenders
 Bridge or Level 2 Switch

Application Application
Presentation Presentation

Session Session
Transport Transport
Network Network

Datalink Layer
Data Link Layer Datalink Layer
Data Link Layer
Physical Medium Physical Medium
Physical Medium Physical Medium
Network Layer Network Extenders
 Router or Level 3 Switch

Application Application
Presentation Presentation

Session Session

Transport Transport

Network
Network Network
Network
Datalink Layer Datalink Layer
Data Link Layer Data Link Layer
Physical Medium Physical Medium
Physical Medium Physical Medium
Application Layer Network Extenders
 Gateway

Application
Application Application
Application
Presentation Presentation

Session Session

Transport Transport

Network Network

Datalink Layer Datalink Layer

Physical Medium Physical Medium


Logical Terminology & Topologies
 Node Node

 Segment / Channel
 Subnet
Segment Segment
 Network
Bridge
 Domain
 System
Subnet Subnet
Router

Network A

Gateway Router

Network B
Domain A Domain B
A Node
 A collection of SW objects that communicate over a
network based upon a single hardware ID.
 A physical device may contain one or more nodes
• Example - a router

Node

Node ID
Parameters
Data
Segment / Channel
 One or more nodes electrically connected to a continuous
section of a transmission media
 May include the trunk line, drop line, multi-port taps and
other cable components.

Segment

Node Node Node Node Node Node


Subnetwork (Subnet)
 One or more nodes sharing a common protocol and a
media access arbitration method
 May contain multiple segments

Subnet
Segment

Segment
Segment
Network
 One or more subnets using a common network level
protocol where each hardware ID is unique on the network
 May contain multiple subnets

Network
Domain
 One or more networks where each network has a unique
ID within the domain
 May contain a variety of network types connected together
with gateways and routers

Network
Domain Network

Network Network
Gateway Router
System
 One or more Domains

Domain
System

Domain

Domain
Basic Media Access Control Methods
 Time Division Access
 Polled Access
 Token Access
 Carrier Sense Multiple Access

How will they share the common media ?

NODE #2 NODE #12 NODE #10 NODE #5


Token
Time Division Access
 Utilizes a master clock
 Each device is assigned a slice of time
Polled Access
 Utilizes one device as a master
 Other devices a considered slave devices
 The master requests information from each slave
 The slave responds to the request

Request Frame
Trailer Output Data Header

DP-Slave
immediate
Master

response

Slave
Header Input Data Trailer
Response Frame
Token Access
 Every device is considered equal
 A token is used to administer access rights
 The token is passed logically among the devices
 Requests are initialized when a device possess the token

Message Message Message Message


Token Token Token Token Token

Token Token
Message Message
NODE #2 NODE #12 NODE #10 NODE #5
Token Token
Carrier Sense Multiple Access
 No priority is assigned to the devices
 All the devices contend for access
 Messages are only sent if the shared media is not in use

Message Message Message


Message Message
Message Message

Message Message Message Message


NODE #2 NODE #12 NODE #10 NODE #5
Typical Automation Field Bus Model
 The typical field bus only utilizes 3 layers. The functions
of the other layers are either built into the ASIC chip or the
application layer
 The application layer will characterize the overall function
of the field bus or the network.

Application: message specifications

Various Media Access Methods: ASIC


Dependent

Multiple Mediums & Physical Topologies


Basic Types of Automation Networks
 Data Network
 Control Network
 Device Bus / Field Bus
 Sensor / Actuator Bus

Operations Level
Data Network
Management Level

System Level (Cell) Control Network

Process Level Device Bus / Field Bus


Sensor/Actuator Bus
Sensor / Actuator
Level
Network Levels - Typical Applications
 Level 2: Hosts
Host
• Recipe data downloads
• Production data uploads
• Application programming and
management Level 2

 Level 1: Control Level 1


• Peer to peer data
• HMI displays
Controller
 Level 0.5: I/O HMI
Peer
• I/O racks and blocks
• Intelligent devices
– Variable frequency drives Level 0.5
– Process valves
– Power meters Intelligent
– Complex Sensors Devices
 Level 0: Devices
• Pushbuttons / Simple sensors Level 0

Pusbutton Sensor
Network Levels - Transmission Characteristics
 Level 2: Hosts Host
• Data: blocks or files
• Frequency: seconds to minutes
• Distance: LAN / WAN / Internet Level 2
 Level 1: Control
Level 1
• Data: words or blocks
• Frequency: 50 to 500 Milliseconds
• Distance: 300m
Controller
HMI
 Level 0.5: I/O Peer
• Data: bytes or words
• Frequency: 20 to 100 Milliseconds
Level 0.5
• Distance: 300m
 Level 0: Devices Intelligent
• Data: bits Devices
• Frequency: 5 to 50 Milliseconds
• Distance: 30m Level 0

Pusbutton Sensor
Communication Network Levels

Level Network Name Information Type

Data Network Ethernet TCP/IP File Transfers


Information Level
Token ring
( Level 2 )

Modbus Plus
Control Network FIPWay Data Transfer
Word Level Program
( Level 1 ) Device Net
Ethernet TCP/IP

Remote I/O
Device / Field Bus Interbus ™ Discrete
Byte & Word Level Analog
( Level 0.5 ) Profibus DP ™ Set Points
DeviceNet ™ Words
Lonworks ™
Fip IO ™

Sensor/ Actuator Bus Lonworks ™ Discrete


Bit Level Seriplex ™ Limited Analog
( Level 0 ) ASi ™

* ™ is a trade mark
Automation & Control System Hierarchy
 Automation and control systems can incorporate them all
Sensor / Actuator Bus
 Sensor Actuator Buses are bit level oriented
Sensor / Actuator Bus

ASi Seriplex LONworks

Speed 5ms 0.7ms 16-100 ms


Nodes 31 nodes 64 nodes 64 nodes
31 510 32385
Distance 100m 1500m 500m
Message Size 4 bits 1 bit 228 bytes
Node Cost Low Low High
Installed Cost Low Low High
Physical Size Small Small Large
ASI Communication Network
 Master - Slave Network – polled media access method
 Utilizes a special 2 conductor cable for data and power
 Data size - 4 bits
 31 maximum slave devices on the bus

ASi power supply Controller


24 V DC
Network Interface Module

Distribution Module

Valves Pilot Actuators


Lights
I/O Module

Push
Buttons
Seriplex Communication Network
 Master - slave or peer to peer network type
 Time division media access control - 100kHz clock
 Special 4 conductor cable - clock, power, data, common
 Clock pulse number equals address

24 VDC power
supply Controller / Network Interface Module

Valves Push Pilot Actuators


Buttons Lights
Device / Field Bus
 Device Buses incorporate intelligent devices
Device / Field Bus

Interbus S Device Net Profibus-DP


(CAN)

Speed 4 ms 10-52 ms 10 ms
Nodes 256 nodes 64 nodes 32 nodes
Max nodes N/A 64 32
Distance 13km 250m 1200m
Message Size 8 bytes 246 bytes
Node Cost Medium Medium Medium
Installed Cost Low High High
Physical Size Medium Medium Large
Interbus Network
 Many third party suppliers  Loss of device or connection
 Large physical topology 12km disables complete system
 Price competitive

PC based Operator
Quantum Controller Control Station Compact 984
I/O Modules

BDEA 202
NOA 611 Interface
Interface

Third Party Products


T/C, RTD, Servo, Barcode, RF Tag
Terminal I/O Modules
 Strong points  Weak points
• High performance I/O • Low performance message
InterBus-S exchanges, deterministic handling
– Adapted to parameter
protocol setting only. 1 to 8 words
– Approx. 7 ms for 128 per device and per bus
devices with 32 I/O cycle
(2048 input bits, 2048 – No slave to slave
output bits) communication
– Built-in reflex functions
• No diffusion (variable or
message handling)
• Standardized profiles ,
interoperability, unique • One level of priority for cyclic
installation tool : CMD variables
tool, product catalogue
• No downgrade mode
• Different physical layers – The bus stops in the event
(loop sensor ) of a fault on the device
– When the bus restarts,
the following devices
• Activation / deactivation cannot be accessed
segment
• DIN standard
• Fault localization – Similar to Phoenix Contact
strategy (components,
policies, etc)
DeviceNet Communication Network
 Limited physical topology 500m

Controller / Network Interface

24 VDC power
supply

MODICON

Valves I/O Module Push I/O Module Actuators Drives


Buttons
ProfiBus DP Network
 Large physical topology 24km  Difficult to configure and
(fiber) maintain; needs multiple
software pieces

Controller / Network Computer / Network Controller / Network


Interface Module Interface Module Interface Module

up to 1200m distance

Direct connection
to third party products

Terminal I/O Modules


LONWorks Communication Network
 Free topology and highly  Slower cycle times
flexible
 Large number of nodes
32000/domain

Programmable Computer
Controller

MODICON MODICON

I/O Modules

Photo Sensor
Lighting Assemblies Switch
Control Networks
 Control Networks require critical performance
Control Networks

Modbus Plus FIPWAY


Speed 20k reg/sec 10-80 ms
Nodes 64 32
Distance 13km 1000m
Message Size 100 registers 128 bytes
Node Cost Medium Medium
Installed Cost Low High
Physical Size Medium Large
Modbus Plus Network

Operator Control
Station
Quantum Controller 984 Controller
Compact 984
Controller

ModConnect

Third Party
Products
Terminal I/O Modules
Modbus Plus excellent performance
 Predictable performance
 As fast as hardwired I/O
• Typical token rotation time
of 2 milliseconds per node Network Throughput
• Maximum network
Reg/Sec per Node
throughput of 20,000
registers/Sec 10000

8000

6000

4000

2000

0
2 4 10 20 30
Nodes
Data Networks
 Data Networks extend the information capabilities
Data Networks

Ethernet

Nodes 8 - 24 nodes/hub
Max Nodes Unlimited
Distance 100 m (node to hub)
Message Size Unlimited
Node Cost Low
Installed Cost Depends on Extent of Network
Physical Size World Wide
Ethernet Data Network

Laptop Hub
10Base-T
Offices
Ethernet Backbone

Hub
Plant
Floor
10Base-T
Quantum Quantum
Ethernet Ethernet
Important Application Information

Number of nodes (I/O points) required.


Distance between I/O points.
Overall network distance.
Data throughput required.
Preferred PLC Controllers being utilized
Bit level traffic quantity
Word level traffic quantity
Preferred Media (coax, fiber, twisted pair,…..)
Maintenance preferences
Greenfield installation
Installed base
Preferred vender list

Das könnte Ihnen auch gefallen