Schneider Electric Communication Services and Architectures Reference manual
Advertisement
Advertisement
Communication Services and Architectures
35010500 12/2018
Communication Services and Architectures
Reference Manual
(Original Document)
12/2018 www.schneider-electric.com
2
The information provided in this documentation contains general descriptions and/or technical characteristics of the performance of the products contained herein. This documentation is not intended as a substitute for and is not to be used for determining suitability or reliability of these products for specific user applications. It is the duty of any such user or integrator to perform the appropriate and complete risk analysis, evaluation and testing of the products with respect to the relevant specific application or use thereof. Neither Schneider Electric nor any of its affiliates or subsidiaries shall be responsible or liable for misuse of the information contained herein. If you have any suggestions for improvements or amendments or have found errors in this publication, please notify us.
You agree not to reproduce, other than for your own personal, noncommercial use, all or part of this document on any medium whatsoever without permission of Schneider Electric, given in writing. You also agree not to establish any hypertext links to this document or its content.
Schneider Electric does not grant any right or license for the personal and noncommercial use of the document or its content, except for a non-exclusive license to consult it on an "as is" basis, at your own risk. All other rights are reserved.
All pertinent state, regional, and local safety regulations must be observed when installing and using this product. For reasons of safety and to help ensure compliance with documented system data, only the manufacturer should perform repairs to components.
When devices are used for applications with technical safety requirements, the relevant instructions must be followed.
Failure to use Schneider Electric software or approved software with our hardware products may result in injury, harm, or improper operating results.
Failure to observe this information can result in injury or equipment damage.
© 2018 Schneider Electric. All rights reserved.
35010500 12/2018
Table of Contents
Safety Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Part I Introduction to the Communication Application. . . . .
Chapter 1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to the Communication Application . . . . . . . . . . . . . . . . . .
Summary of Communication Solutions . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2 Services Available on Networks and Buses . . . . . . . . . .
2.1 Global Data Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Global Data Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 IO Scanning Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IO Scanning Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Peer Cop Service on Modbus Plus . . . . . . . . . . . . . . . . . . . . . . . . . . .
Peer Cop Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Common Words and Shared Tables Services on Fipway . . . . . . . . . .
Fipway Common Words and Shared Tables. . . . . . . . . . . . . . . . . . . .
2.5 Messaging Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Messaging Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Characteristics of the Messaging Service Communication Functions.
Chapter 3 Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Modbus Function Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4 Communication Architectures. . . . . . . . . . . . . . . . . . . . .
Global Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fieldbus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5 X-Way Message Routing . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Main Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-Module Station Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Part II Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 6 General Points Concerning Addressing . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
59
61
63
63
53
54
55
57
43
44
48
52
31
32
39
39
26
29
29
30
22
24
24
26
18
20
21
22
7
11
15
17
35010500 12/2018
3
4
Chapter 7 IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Note on IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 8 Modbus Plus Addressing . . . . . . . . . . . . . . . . . . . . . . . . .
Addressing for a Modbus Plus Communication Entity . . . . . . . . . . . . .
Chapter 9 X-Way Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Addressing for a Communication Entity . . . . . . . . . . . . . . . . . . . . . . . .
Types of Communication Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processor Communication Channel Addressing . . . . . . . . . . . . . . . . .
Addressing for a TSX SCY 21601 Communication Module. . . . . . . . .
Examples of Intra-Station Addressing: Uni-Telway Addressing. . . . . .
Examples of Intra-Station Addressing: Fipio Addressing . . . . . . . . . . .
Examples of Intra-Station Addressing . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 10 Modicon M340 PLCs Addressing . . . . . . . . . . . . . . . . . . .
Modicon M340 Types of Communication Entities . . . . . . . . . . . . . . . .
Modicon M340 Addressing for a Communication Entity . . . . . . . . . . .
Processor Communication Channels Addressing . . . . . . . . . . . . . . . .
Example of Modicon M340 Ethernet Addressing . . . . . . . . . . . . . . . . .
Example of Modicon M340 CANopen Addressing. . . . . . . . . . . . . . . .
Examples of Modicon M340 Modbus and Character Mode Addressing
Examples of Modicon M340 Communication EFs Addressing . . . . . .
87
88
89
92
80
81
83
84
94
95
96
98
73
74
76
78
65
65
69
69
Chapter 11 General points concerning bridging . . . . . . . . . . . . . . . . .
101
Bridging Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bridging Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
102
104
Part III Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . .
107
Chapter 12 Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .
109
Network Configuration Principle Using Control Expert . . . . . . . . . . . .
Creating a Logic Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110
111
Configuring a Logic Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Associating a Logic Network with Network Hardware . . . . . . . . . . . . .
113
114
Chapter 13 Bus Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
117
Creating and Accessing RIO\DIO Field Buses. . . . . . . . . . . . . . . . . . .
Accessing Bus Configurations on PCMCIA and SCY 21601 Cards . .
118
124
Chapter 14 Configuration of X-Way Routing Premium Stations . . . . .
127
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration of Multi-Network Services . . . . . . . . . . . . . . . . . . . . . . .
Configuring an X-Way Router Module . . . . . . . . . . . . . . . . . . . . . . . . .
Examples of X-Way Routing Stations . . . . . . . . . . . . . . . . . . . . . . . . .
Examples of Partial Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
128
129
131
135
139
35010500 12/2018
Chapter 15 Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description of the Communication Debug Screens. . . . . . . . . . . . . . .
Chapter 16 Communication Function Programming and Entry Help.
Communication Function Entry Help . . . . . . . . . . . . . . . . . . . . . . . . . .
Access a specific instruction of the function, function block or DFB type
Address Entry Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141
141
145
146
147
149
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
151
35010500 12/2018
5
6
35010500 12/2018
Safety Information
Important Information
NOTICE
Read these instructions carefully, and look at the equipment to become familiar with the device before trying to install, operate, service, or maintain it. The following special messages may appear throughout this documentation or on the equipment to warn of potential hazards or to call attention to information that clarifies or simplifies a procedure.
35010500 12/2018
7
PLEASE NOTE
Electrical equipment should be installed, operated, serviced, and maintained only by qualified personnel. No responsibility is assumed by Schneider Electric for any consequences arising out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction and operation of electrical equipment and its installation, and has received safety training to recognize and avoid the hazards involved.
8
BEFORE YOU BEGIN
Do not use this product on machinery lacking effective point-of-operation guarding. Lack of effective point-of-operation guarding on a machine can result in serious injury to the operator of that machine.
WARNING
UNGUARDED EQUIPMENT
Do not use this software and related automation equipment on equipment which does not have point-of-operation protection.
Do not reach into machinery during operation.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
This automation equipment and related software is used to control a variety of industrial processes.
The type or model of automation equipment suitable for each application will vary depending on factors such as the control function required, degree of protection required, production methods, unusual conditions, government regulations, etc. In some applications, more than one processor may be required, as when backup redundancy is needed.
Only you, the user, machine builder or system integrator can be aware of all the conditions and factors present during setup, operation, and maintenance of the machine and, therefore, can determine the automation equipment and the related safeties and interlocks which can be properly used. When selecting automation and control equipment and related software for a particular application, you should refer to the applicable local and national standards and regulations. The
National Safety Council's Accident Prevention Manual (nationally recognized in the United States of America) also provides much useful information.
In some applications, such as packaging machinery, additional operator protection such as pointof-operation guarding must be provided. This is necessary if the operator's hands and other parts of the body are free to enter the pinch points or other hazardous areas and serious injury can occur.
Software products alone cannot protect an operator from injury. For this reason the software cannot be substituted for or take the place of point-of-operation protection.
Ensure that appropriate safeties and mechanical/electrical interlocks related to point-of-operation protection have been installed and are operational before placing the equipment into service. All interlocks and safeties related to point-of-operation protection must be coordinated with the related automation equipment and software programming.
35010500 12/2018
NOTE: Coordination of safeties and mechanical/electrical interlocks for point-of-operation protection is outside the scope of the Function Block Library, System User Guide, or other implementation referenced in this documentation.
START-UP AND TEST
Before using electrical control and automation equipment for regular operation after installation, the system should be given a start-up test by qualified personnel to verify correct operation of the equipment. It is important that arrangements for such a check be made and that enough time is allowed to perform complete and satisfactory testing.
WARNING
EQUIPMENT OPERATION HAZARD
Verify that all installation and set up procedures have been completed.
Before operational tests are performed, remove all blocks or other temporary holding means used for shipment from all component devices.
Remove tools, meters, and debris from equipment.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Follow all start-up tests recommended in the equipment documentation. Store all equipment documentation for future references.
Software testing must be done in both simulated and real environments.
Verify that the completed system is free from all short circuits and temporary grounds that are not installed according to local regulations (according to the National Electrical Code in the U.S.A, for instance). If high-potential voltage testing is necessary, follow recommendations in equipment documentation to prevent accidental equipment damage.
Before energizing equipment:
Remove tools, meters, and debris from equipment.
Close the equipment enclosure door.
Remove all temporary grounds from incoming power lines.
Perform all start-up tests recommended by the manufacturer.
35010500 12/2018
9
OPERATION AND ADJUSTMENTS
The following precautions are from the NEMA Standards Publication ICS 7.1-1995 (English version prevails):
Regardless of the care exercised in the design and manufacture of equipment or in the selection and ratings of components, there are hazards that can be encountered if such equipment is
improperly operated.
It is sometimes possible to misadjust the equipment and thus produce unsatisfactory or unsafe operation. Always use the manufacturer’s instructions as a guide for functional adjustments.
Personnel who have access to these adjustments should be familiar with the equipment manufacturer’s instructions and the machinery used with the electrical equipment.
Only those operational adjustments actually required by the operator should be accessible to the operator. Access to other controls should be restricted to prevent unauthorized changes in operating characteristics.
10
35010500 12/2018
About the Book
At a Glance
Document Scope
This manual gives an overview of the communication services and architectures using
EcoStruxure™ Control Expert software.
More details on communication services and architectures in Modicon M580 and Modicon
Quantum platforms are provided in the following topics:
Modicon M580 Communication (see Modicon M580, BMENOC0301/0311 Ethernet
Communications Module, Installation and Configuration Guide)
Modicon M580 Ethernet I/O (see Modicon M580 Standalone, System Planning Guide for,
Frequently Used Architectures)
Quantum Communication (see Quantum using EcoStruxure™ Control Expert, Experts and
Communication, Reference Manual)
Quantum Ethernet I/O (see Quantum EIO, System Planning Guide)
Validity Note
This documentation is valid for EcoStruxure™ Control Expert 14.0 or later.
The technical characteristics of the devices described in the present document also appear online.
To access the information online:
Step
1
2
3
4
5
6
Action
Go to the Schneider Electric home page www.schneider-electric.com
.
In the Search box type the reference of a product or the name of a product range.
Do not include blank spaces in the reference or product range.
To get information on grouping similar modules, use asterisks ( * ).
If you entered a reference, go to the Product Datasheets search results and click on the reference that interests you.
If you entered the name of a product range, go to the Product Ranges search results and click on the product range that interests you.
If more than one reference appears in the Products search results, click on the reference that interests you.
Depending on the size of your screen, you may need to scroll down to see the data sheet.
To save or print a data sheet as a .pdf file, click Download XXX product datasheet.
35010500 12/2018
11
The characteristics that are presented in the present document should be the same as those characteristics that appear online. In line with our policy of constant improvement, we may revise content over time to improve clarity and accuracy. If you see a difference between the document and online information, use the online information as your reference.
Related Documents
Title of documentation
Modicon M340 for Ethernet, Communications
Modules and Processors, User Manual
EcoStruxure™ Control Expert, Program Languages and Structure, Reference Manual
Premium and Atrium using EcoStruxure™ Control
Expert, Asynchronous Serial Link, User Manual
Premium and Atrium using EcoStruxure™ Control
Expert, Fipway Network, User Manual
Premium and Atrium using EcoStruxure™ Control
Expert, Ethernet Network Modules, User Manual
Premium and Atrium using EcoStruxure™ Control
Expert, Modbus Plus Network, User Manual
Reference number
31007131 (English),
31007132 (French),
31007133 (German),
31007494 (Italian),
31007134 (Spanish),
31007493 (Chinese)
35006144 (English),
35006145 (French),
35006146 (German),
35013361 (Italian),
35006147 (Spanish),
35013362 (Chinese)
35006178 (English),
35006179 (French),
35006180 (German),
35013959 (Italian),
35006181 (Spanish),
35013960 (Chinese)
35006183 (English),
35006185 (French),
35006186 (German),
35013955 (Italian),
35006187 (Spanish),
35013956 (Chinese)
35006192 (English),
35006193 (French),
35006194 (German),
31007214 (Italian),
35006195 (Spanish),
31007102 (Chinese)
35006188 (English),
35006189 (French),
35006190 (German),
35013962 (Italian),
35006191 (Spanish),
35013963 (Chinese)
12
35010500 12/2018
Title of documentation
Quantum EIO, System Planning Guide
Modicon M580 BMENOC0301/11, Ethernet
Communication Module, Installation and
Configuration Guide
Modicon M580 Standalone, System Planning Guide for Frequently Used Architectures
Reference number
S1A48959 (English),
S1A48961 (French),
S1A48962 (German),
S1A48964 (Italian),
S1A48965 (Spanish),
S1A48966 (Chinese)
HRB62665 (English),
HRB65311 (French),
HRB65313 (German),
HRB65314 (Italian),
HRB65315 (Spanish),
HRB65316 (Chinese)
HRB62666 (English),
HRB65318 (French),
HRB65319 (German),
HRB65320 (Italian),
HRB65321 (Spanish),
HRB65322 (Chinese)
Modicon M580, Hardware, Reference Manual
EcoStruxure™ Control Expert, Communication, Block
Library
EIO0000001578 (English),
EIO0000001579 (French),
EIO0000001580 (German),
EIO0000001582 (Italian),
EIO0000001581 (Spanish),
EIO0000001583 (Chinese)
33002527 (English),
33002528 (French),
33002529 (German),
33003682 (Italian),
33002530 (Spanish),
33003683 (Chinese)
EcoStruxure™ Control Expert, I/O Management,
Block Library
33002531 (English),
33002532 (French),
33002533 (German),
33003684 (Italian),
33002534 (Spanish),
33003685 (Chinese)
EcoStruxure™ Control Expert, System, Block Library 33002539 (English),
33002540 (French),
33002541 (German),
33003688 (Italian),
33002542 (Spanish),
33003689 (Chinese)
35010500 12/2018
13
Title of documentation
Quantum using EcoStruxure™ Control Expert,
Experts and Communication, Reference Manual
Reference number
35010574 (English),
35010575 (French),
35010576 (German),
35014012 (Italian),
35010577 (Spanish),
35012187 (Chinese)
You can download these technical publications and other technical information from our website at
www.schneider-electric.com/en/download
.
14
35010500 12/2018
Communication Services and Architectures
Introduction
35010500 12/2018
Introduction to the Communication Application
Part I
Introduction to the Communication Application
Subject of this Part
This part gives an overview of the communication application: the types of networks and buses, services and architectures available.
What Is in This Part?
This part contains the following chapters:
Chapter
1
2
3
4
5
Chapter Name
General
Services Available on Networks and Buses
Interoperability
Communication Architectures
X-Way Message Routing
Page
35010500 12/2018
15
Introduction
16
35010500 12/2018
Communication Services and Architectures
General
35010500 12/2018
General
Chapter 1
General
Subject of this Chapter
This chapter gives an overview of the different characteristics of the communication application.
What Is in This Chapter?
This chapter contains the following topics:
Topic
Introduction to the Communication Application
Summary of Communication Solutions
Page
35010500 12/2018
17
General
Introduction to the Communication Application
At a Glance
The communication application makes it possible to exchange data between different devices connected to a bus or a network.
This function applies to :
processors with an Ethernet, Modbus, built-in Fipio or CANopen link, specific rack-mounted communication modules, the terminal port of a processor,
PCMCIA cards of a rack-mounted processor or module.
Communication Types
The different communication types are:
TCP/IP or Ethway Ethernet Network
Fipway Network
Modbus Plus Network
Fipio bus (manager and agent)
Uni-Telway bus
Modbus/JBus bus
Character mode serial link
CANopen field bus
Interbus field bus
Profibus field bus
The USB-standard fast terminal port
18
35010500 12/2018
General
Available Services
The available services can be classified into three categories:
Explicit messaging
see page 30
Modbus messaging
UNI-TE messaging telegrams
Implicit database access services:
see page 22
common words
see page 29 see page 29
Implicit Input/Output management services:
I/O scanning
peer cop
see page 24
see page 26
WARNING
UNEXPECTED APPLICATION BEHAVIOR - DATA EXCHANGE COMPATIBILITY
Data structure alignments are not the same for Premium/Quantum and M340 PLCs so verify that the data exchanged are compatible.
See the page DDT: Mapping rules (see EcoStruxure™ Control Expert, Program Languages and
Structure, Reference Manual) for more information.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Characteristics of the Different Service Types
The following table gives an overview of the main characteristics of the types of services mentioned above:
Type of service
Messaging services
Implicit database access services
Implicit I/O management services
These services make it possible ... They are used ...
for a device (Client) to send a message to another device
(Server) and obtain a response without having to program anything into the server device. to access data from time to time.
to share data which is refreshed automatically and on a regular basis.
to transparently and automatically manage remote I/Os on a network.
to synchronize applications or to transparently obtain realtime images of a system on several remote PLCs to monitor a set of distributed systems across a network.
35010500 12/2018
19
General
Summary of Communication Solutions
At a Glance
The services presented earlier in this chapter are available for certain types of communication.
For example, for messaging services, certain communication functions apply to networks, others to buses and others to serial links in character mode
see page 35
Summary
The following table gives an overview of the different services available according to the types of communication:
Function Fipway Fipio Uni-
Telway
Character mode
Modbus/
Jbus
Modbus
Plus
Ethway TCP/IP CANopen USB
Messaging services
Communi-cation functions
The communication functions that can be used depend closely on the type of communication for which they are applied
.
Implicit database access services
Global Data -
Common words
Shared tables
Periodic data exchanges
X
X
X
-
-
Implicit I/O management services
I/O Scanning -
Peer cop
Other
-
-
-
X
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
X
X
-
-
-
-
-
-
-
X
-
-
X
X
-
-
-
-
X
-
-
-
X
-
-
-
-
-
-
-
-
-
-
-
-
Legend:
X Yes
No
20
35010500 12/2018
Communication Services and Architectures
Services
35010500 12/2018
Services Available on Networks and Buses
Chapter 2
Services Available on Networks and Buses
Subject of this Chapter
This chapter describes the different services available on the communication buses and networks.
What Is in This Chapter?
This chapter contains the following sections:
Section
2.1
2.2
2.3
2.4
2.5
Topic
Global Data Service
IO Scanning Service
Peer Cop Service on Modbus Plus
Common Words and Shared Tables Services on Fipway
Messaging Service
Page
35010500 12/2018
21
Services
Global Data Service
Section 2.1
Global Data Service
Global Data Service
At a Glance
The aim of the Global Data service, which is supported by Ethernet modules, is to provide an automatic data exchange for the coordination of PLC applications. Data is shared according to an inter-device publication/subscription method.
How it Works
The communication modules are grouped into a Distribution group.
Each communication module publishes a local application variable for the other communication modules in the distribution group.
Each communication module can also subscribe to the application variables published by all other modules belonging to the distribution group.
The Global Data service should be configured to determine the location and the number of application variables of each communication module. Once the modules have been configured, exchanges between communication modules belonging to the same group are automatically carried out when the PLC is in RUN mode.
22
35010500 12/2018
Services
Illustration:
A Distribution group is a group of communication modules identified by the same multicast IP address. Exchanges in "multicasting" are used to distribute Global Data. Several independent distribution groups can co-exist on the same subnetwork with their own multicast address.
A Publication/Subscription protocol on UDP/IP is used for data distribution.
Limitations
There is no theoretical limit to the number of stations that may belong to a distribution group.
The main limitation is the number of variables exchanged in a group (64 variables).
Replacing a 140 NOE 771 x0 module by a new 140 NOE 771 x1 module, the Global Data
Service must not be configured by web pages. Otherwise, the Global Data Utility will start even if Global Data has not been configured in the application.
35010500 12/2018
23
Services
IO Scanning Service
Section 2.2
IO Scanning Service
IO Scanning Service
At a Glance
The IO scanner makes it possible to periodically read or write to/from remote inputs/ouputs on the
Ethernet network, without requiring any specific programming.
This service comprises the following essential elements:
a read field containing all the values of the remote inputs, a write field containing all the values of the remote outputs, scanning periods independent of the PLC cycle and dedicated to checking each remote device.
How it Works
The scan will only be performed if the PLC is in Run mode.
This service works with all devices supporting Modbus communication on the TCP/IP profile in server mode.
The exchange mechanism, which is transparent for users, involves:
read requests, write requests, read and write requests.
24
35010500 12/2018
The following diagram shows how scanning of remote inputs/outputs works.
Services
1. As soon as the PLC goes into Run mode, the module opens one connection per scanned device.
2. The module then periodically reads the input words and periodically writes the output words of each device.
3. If the PLC goes into Stop mode, the connections with each device are closed.
Summary of Functions
The functions of the IO scanning service are to:
manage the connection with each remote device (one connection per scanned device), scan the inputs/outputs of the device by using the Modbus read/write requests on the TCP/IP profile, update the read/write fields in the application memory, refresh the status bits of each remote device.
NOTE: The status bits indicate whether the input/output words of the module have been refreshed.
35010500 12/2018
25
Services
Peer Cop Service on Modbus Plus
Section 2.3
Peer Cop Service on Modbus Plus
Peer Cop Service
At a Glance
The Peer Cop service is a mechanism for automatic exchange between stations connected on the same Modbus Plus segment.
This service makes it possible to control remote inputs / outputs on a continuous basis by implicit exchanges.
Premium and Quantum PLCs are capable of managing this service on a Modbus Plus network
Premium PLCs support two types of Peer Cop transfer:
specific inputs, specific outputs.
Specific Inputs and Outputs
Specific inputs and outputs are point-to-point services using the multicast (multi-station) protocol.
Each message contains one or more destination addresses for data transmission. This mode of operation makes it possible to exchange data with several stations without them having to be repeated.
Report
Three types of report are associated with specific inputs and outputs:
An activity bit provides information on the availability and validity of the status bits.
Status bits (one bit per station):
ensure consistency between the number of specific inputs configured and the number of specific inputs received, indicate if the specific inputs have been received before the Timeout.
Presence bits (one bit per station) indicate if the specific inputs have been refreshed.
NOTE: The presence bits are only valid for the specific inputs.
26
35010500 12/2018
Services
Example for the Inputs
The data blocks are copied in their entirety from the PCMCIA communication card to the internal word space, reserved at the time of configuration.
In the following example, the address of the first internal word is %MW10:
35010500 12/2018
27
Services
Example for the Outputs
The data blocks are copied in their entirety from the internal word space, reserved at the time of configuration, to the PCMCIA communication card. The reports are copied from the PCMCIA communication card to the language objects.
In the following example, the address of the first internal word is %MW10:
28
35010500 12/2018
Common Words and Shared Tables Services on Fipway
Section 2.4
Common Words and Shared Tables Services on Fipway
Services
Fipway Common Words and Shared Tables
At a Glance
The Fipway network provides two data sharing services:
common words, shared table.
The main objective of these two services is to synchronize automation applications.
Common Words
The common words service consists of a set of dedicated %NW words. Each station on the network can, depending on its software configuration, access the database in read or write mode.
Updates are performed implicitly at the start of the cycle for read operations and at the end of the cycle for write operations. The function of the application program is simply to read or write these words.
The addressing of the words is as follows: %NWn.s.k
The following table states the address parameters of the common words: s k
Parameter n
Description
Network number
Station number
Word number
NOTE: The network number makes it possible to select the network on which the common words are exchanged in a multi-network configuration.
Shared Table
This service makes it possible to exchange a table of %MW internal words divided up into as many fields as there are stations on the Fipway network. The principle is based on each PLC broadcasting a word memory field to the other stations on the network.
Updates are performed implicitly and independently of the application program's execution cycle.
The function of the program is simply to write or read the %MW words.
NOTE: When configuring and assigning fields, be careful to avoid creating memory conflicts between stations.
35010500 12/2018
29
Services
Messaging Service
Section 2.5
Messaging Service
Subject of This Section
This section gives an overview of the messaging service available on Schneider Electric PLCs.
What Is in This Section?
This section contains the following topics:
Topic
Messaging Service
Characteristics of the Messaging Service Communication Functions
Page
30
35010500 12/2018
Services
Messaging Service
At a Glance
The messaging service makes it possible to perform inter-PLC data exchanges using communication functions.
Two types of messaging are used:
Private: UNI-TE on Modicon Premium and Telemecanique installed base,
Standard: Modbus on Modicon Quantum, Modicon Premium, Modicon M340, Modicon M580, and Modicon Momentum installed base.
The destination entities of an exchange can either be located in a local station or in a remote station on a communication channel or directly in the CPU.
The communication functions provide an interface that is independent of the location of the destination entity. Furthermore, they mask the coding of the communication requests from the user. They thus provide compatibility of communication between Premium, Micro, Quantum,
TSX 40, TSX 17, 1000 series and Modicon M340 PLCs.
NOTE: Processing of communication functions is asynchronous in relation to the processing of the application task which allowed them to be activated. The send/receive telegram and stop operation functions are the only exceptions as their execution is synchronous with the execution of the activation task.
Synchronous/Asynchronous Communication
A communication function is said to be synchronous when it is wholly executed during the PLC task that activated it.
A communication function is said to be asynchronous when it is executed during one or more PLC tasks after the task that activated it.
35010500 12/2018
31
Services
Characteristics of the Messaging Service Communication Functions
At a Glance
These functions (see EcoStruxure™ Control Expert, Communication, Block Library) of communication channel. Others may be specific to one communication function.
enable communication between one device and another. Certain functions are common to several types
NOTE: Processing of communication functions is asynchronous in relation to the processing of the application task, which allowed them to be activated. The send/receive telegram and stop operation functions are the only exceptions as their execution is synchronous with the execution of the activation task.
NOTE: It is recommended that asynchronous functions be triggered on edge and not on state to avoid sending several identical requests in quick succession, thus saturating the communication buffers.
Messaging Service Communication Functions on Modicon M340 Platform
The following table gives an overview of Modicon M340 platform messaging service functions:
Function
DATA_EXCH
ETH_PORT_CTRL
INPUT_BYTE
INPUT_CHAR
PRINT_CHAR
READ_VAR
SEND_EMAIL
WRITE_VAR
Role
Transmit or receive data.
Activate or deactivate a protocol.
Receive an array of bytes on a character mode link of a BMX NOM module in a local rack or linked to a CPU embedded communication channel.
Receive a character string on a character mode link of a BMX NOM module in a local rack or linked to a CPU embedded communication channel.
Send a character string on a character mode link of a BMX NOM module in a local rack or linked to a CPU embedded communication channel.
Read the value of one or more language objects via a communication module in a local rack or linked to a CPU embedded communication channel.
Send an email over an Ethernet port of a communication module plugged in a local rack.
Write the value of one or more language objects via a communication module in a local rack or linked to a CPU embedded communication channel.
32
35010500 12/2018
Services
Messaging Service Communication Functions on Modicon M580 Platform
The following table gives an overview of the Modicon M580 platform messaging service functions:
Function
DATA_EXCH
GET_TS_EVT_M
INPUT_BYTE
INPUT_CHAR
PRINT_CHAR
READ_PARAM_MX
READ_STS_MX
READ_VAR
RESTORE_PARAM_MX
SAVE_PARAM_MX
SEND_EMAIL
WRITE_CMD_MX
WRITE_PARAM_MX
WRITE_VAR
Role
End any requests (Modbus, Umas …) to any Modbus slave via a communication module plugged in a local rack or in an EIO drop.
Get the time stamped data in a Modicon BMX ERT 1604T or BMX CRA ••••• module plugged in a local rack or in an EIO drop.
Receive an array of bytes on a character mode link of a BMX NOM module plugged in a local rack or in an EIO drop.
Receive a character string on a character mode link of a BMX NOM module plugged in a local rack or in an EIO drop.
Send a character string on a character mode link of a BMX NOM module plugged in a local rack or in an EIO drop.
Read the parameter words of an X80 I/O module plugged in a local rack by performing an explicit exchange.
Read the status words of an X80 I/O module plugged in a local rack or in an EIO drop by performing an explicit exchange.
Read the value of one or more language objects via a communication module plugged in a local rack or in an EIO drop.
Restore the parameter words of an X80 I/O module plugged in a local rack by performing an explicit exchange.
Save the parameter words of an X80 I/O module plugged in a local rack by performing an explicit exchange.
Send an email over an Ethernet port of a communication module plugged in a local rack (Ethernet modules cannot be plugged in an EIO drop).
Send a command to an X80 I/O module plugged in a local rack or in an EIO drop by performing an explicit exchange.
Write the parameter words of an X80 I/O module plugged in a local rack by performing an explicit exchange.
Write the value of one or more language objects via a communication module plugged in a local rack or in an EIO drop.
35010500 12/2018
33
Services
Messaging Service Communication Functions on Modicon Quantum Platform
The following table gives an overview of Modicon Quantum platform messaging service functions:
Function
CREAD_REG
CWRITE_REG
EXCH_QX
INPUT_CHAR_QX
MBP_MSTR
PRINT_CHAR_QX
READ_REG
READ_REG_QX
READ_STS_QX
WRITE_CMD_QX
WRITE_REG
WRITE_REG_QX
XXMIT
Role
Continuously read a register area from a slave addressed via Modbus Plus,
TCP/IP-Ethernet or SY/MAX-Ethernet
Continuously write a register area to a slave addressed via Modbus Plus,
TCP/IP-Ethernet or SY/MAX-Ethernet
Perform data transfers through an EIO bus to and from Modbus slaves connected to a Modicon M340 rack
Receive a character string from a Modicon M340 serial communication module through an EIO bus
Perform various network communication operations on Modbus Plus, TCP/IP-
Ethernet or SY/MAX-Ethernet
Send a character string of 1000 bytes maximum from a Modicon M340 Modbus master through an EIO bus
Read a register area from a slave addressed via Modbus Plus, TCP/IP-Ethernet or SY/MAX-Ethernet
Read registers in a Modbus slave connected to a Modicon M340 Modbus master through an EIO bus
Read the status words of a Modicon M340 Ethernet I/O module by performing an explicit exchange with the processor memory
Send a command to a Modicon M340 Ethernet I/O module with a command word by performing an explicit exchange
Write a register area to a slave addressed via Modbus Plus, TCP/IP-Ethernet or
SY/MAX-Ethernet
Write registers in a Modbus slave connected to a Modicon M340 Modbus master through an EIO bus
Modbus messages from master PLC and ASCII input/output strings.
Messaging Service Communication Functions on Modicon Momentum Platform
The following table gives an overview of Modicon Momentum platform messaging service functions:
Function
MBP_MSTR
XMIT
XXMIT
Role
Perform various network communication operations on Modbus Plus, TCP/IP-
Ethernet or SY/MAX-Ethernet.
Modbus messages from master PLC and ASCII input/output strings.
Modbus messages from master PLC and ASCII input/output strings.
34
35010500 12/2018
Services
Messaging Service Communication Functions on Modicon Premium Platform
The following table gives an overview of Modicon Premium platform messaging service functions:
Function
DATA_EXCH
INPUT_BYTE
INPUT_CHAR
OUT_IN_CHAR
OUT_IN_MBUS
PRINT_CHAR
RCV_TLG
READ_ASYN
READ_GDATA
READ_VAR
SEND_REQ
SEND_TLG
UNITE_SERVER
WRITE_ASYN
WRITE_GDATA
WRITE_VAR
Role
Send/request receipt of data.
Read an array of bytes.
Read a character string.
Send a character string and wait for a response.
Emulate a Modbus master communication from a serial link configured in character mode.
Write a character string.
Receive a telegram.
Read 1 Kbyte of messaging.
Read common Modbus Plus data.
Read standard language objects: internal words and bits, system words and bits, timers, monostables, drums, registers, counters.
Send UNI-TE requests.
Send a telegram.
Process immediately READ_VAR and WRITE_VAR requests on Modbus
(Immediate server).
Write 1 Kbytes of messaging.
Write common Modbus Plus data.
Write standard language objects: internal words and bits, system words and bits.
Availability of Functions According to Protocols
Protocols supported by the messaging service functions in a Modicon M340 platform:
Function
DATA_EXCH
ETH_PORT_CTRL
INPUT_BYTE
INPUT_CHAR
PRINT_CHAR
READ_VAR
X Yes
– No
TCP/IP ETHWAY CANopen Modbus serial
X
X
–
–
X
–
X
–
–
X
–
–
–
–
–
–
–
–
–
X
–
–
–
X
Modbus
Plus
–
–
–
–
–
–
Fipway Uni-
Telway
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Fipio Character mode
–
–
X
–
X
X
X
–
35010500 12/2018
35
Services
Function
SEND_EMAIL
WRITE_VAR
X Yes
– No
TCP/IP ETHWAY CANopen Modbus serial
–
X
–
–
–
X
–
X
Modbus
Plus
–
–
Fipway Uni-
Telway
–
–
–
–
Fipio Character mode
–
–
X
–
Protocols supported by the messaging service functions in a Modicon M580 platform:
Function
DATA_EXCH
GET_TS_EVENT_M
INPUT_BYTE
INPUT_CHAR
PRINT_CHAR
READ_PARAM_MX
READ_STS_MX
READ_VAR
RESTORE_PARAM_
MX
SAVE_PARAM_MX
SEND_EMAIL
WRITE_CMD_MX
WRITE_PARAM_MX
WRITE_VAR
X Yes
– No
TCP/IP ETHWAY CANopen Modbus serial
X
X
–
–
–
–
X
–
–
X
–
–
–
–
–
–
–
–
–
–
–
–
–
–
X
X
X
–
–
–
–
–
–
–
X
–
Modbus
Plus
–
–
–
–
–
–
–
–
–
Fipway Uni-
Telway
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
X
X
X
X
X
–
–
–
–
–
–
–
–
–
–
–
–
–
–
X
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Fipio Character mode
–
–
–
–
X
X
X
–
–
–
–
–
–
–
–
–
–
–
–
Protocols supported by the messaging service functions in a Modicon Quantum platform:
Function
CREAD_REG
CWRITE_REG
EXCH_QX
INPUT_CHAR_QX
X Yes
– No
TCP/IP ETHWAY CANopen Modbus serial
X
X
–
–
–
–
–
–
X
–
–
–
–
–
X
–
Modbus
Plus
X
X
–
–
Fipway Uni-
Telway
–
–
–
–
–
–
–
–
Fipio Character mode
–
–
–
–
–
–
–
X
36
35010500 12/2018
35010500 12/2018
Services
Function
MBP_MSTR
PRINT_CHAR_QX
READ_REG
READ_REG_QX
READ_STS_QX
WRITE_CMD_QX
WRITE_REG
WRITE_REG_QX
XXMIT
X Yes
– No
TCP/IP ETHWAY CANopen Modbus serial
X
–
–
–
–
–
–
–
X
X
X
–
–
–
–
–
–
–
–
–
–
X
–
–
X
–
–
–
–
–
–
–
–
–
X
X
Modbus
Plus
X
–
–
–
X
–
X
–
–
Fipway Uni-
Telway
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Fipio Character mode
–
–
–
X
–
–
–
–
–
–
–
–
–
X
Function
Protocols supported by the messaging service functions in a Modicon Momentum platform:
MBP_MSTR
XMIT
XXMIT
X Yes
– No
TCP/IP ETHWAY CANopen Modbus serial
X
–
–
–
–
–
–
–
–
–
X
X
Modbus
Plus
X
–
–
Fipway Uni-
Telway
–
–
–
–
–
–
Fipio Character mode
–
–
–
–
X
X
Protocols supported by the messaging service functions in a Modicon Premium platform:
Function
DATA_EXCH
INPUT_BYTE
INPUT_CHAR
OUT_IN_CHAR
OUT_IN_MBUS
PRINT_CHAR
TCP/IP ETHWAY CANopen Modbus serial
(1)
–
X
–
–
–
–
–
–
X
X
X
X
X
–
X
–
–
–
–
–
–
X
–
Modbus
Plus
–
–
–
–
–
–
Fipway Uni-
X
–
X
X
–
X
Telway
X
–
–
–
–
–
Fipio Character
–
–
–
–
–
– mode
–
X
X
X
–
X
RCV_TLG – – – – – X – – –
X Yes
– No
(1) Exchanges between applications and UNI-TE requests are available but Modbus requests coding is not available with an ETY Premium module.
37
Services
Function
READ_ASYN
READ_GDATA
READ_VAR
SEND_REQ
SEND_TLG
UNITE_SERVER
TCP/IP ETHWAY CANopen Modbus serial
X
–
–
–
–
–
–
–
–
–
X
X
X
X
–
–
–
X
–
–
X
X
–
X
Modbus
Plus
–
X
X
X
–
–
Fipway Uni-
–
–
X
–
X
X
Telway
–
–
X
X
–
–
Fipio Character mode
–
–
X
X
–
–
–
–
–
–
–
–
WRITE_ASYN
WRITE_GDATA
X
–
–
–
–
–
–
–
–
X
–
–
–
–
–
–
–
–
WRITE_VAR X X – X X X X X –
X Yes
– No
(1) Exchanges between applications and UNI-TE requests are available but Modbus requests coding is not available with an ETY Premium module.
38
35010500 12/2018
Communication Services and Architectures
Interoperability
35010500 12/2018
Interoperability
Chapter 3
Interoperability
List of Modbus Function Codes
At a Glance
Quantum, Premium and M340 PLCs have communication server kernels that accept the common
Modbus function codes. These are listed in the table on this page.
As servers, Quantum, Premium and M340 PLCs recognize all Class 0 and Class 1 Modbus function codes, as stipulated in the Modbus specifications available at http://www.Modbus.org
. Their server kernel also includes the function code 23 for reading/writing of consecutive variables.
For the list of Modbus function codes recognized by Quantum PLCs, please refer to the specific
Quantum documentation.
For the list of function codes recognized by Premium PLCs, please refer to the specific Premium
(see Premium and Atrium using EcoStruxure™ Control Expert, Asynchronous Serial Link, User
Manual) documentation. In addition to this, Premium PLCs recognize certain UNI-TE
(see EcoStruxure™ Control Expert, Communication, Block Library) requests.
List of Modbus Requests Recognized When Connected as a Server
The following table lists the function codes and the address of the Modbus function codes, recognized by Premium, Quantum and M340 platforms.
Meaning
2
3
Function code
1
Quantum memory address
16#0XXX
16#1XXX
16#4XXX
M340 and Premium memory address
%M
%M
%MW
4
5
6
15
1
16#3XXX
16#0XXX
16#4XXX
16#0XXX
%MW
%M
%MW
%M
Read output bits, refer to note below.
Read input bits
Read consecutive integer values (until 125 registers for Premium/Atrium PLCs)
Read consecutive input integer values (until 124 registers for Premium/Atrium PLCs)
Write single output bit
Write single integer value
Write n output bits
35010500 12/2018
39
Interoperability
Function code
16
1
23
2
Quantum memory address
16#4XXX
16#4XXX
M340 and Premium memory address
%MW
%MW
Meaning
Write consecutive integer values
Read/write consecutive integer values 3
1 When using the SEND_REQ communication function to send these codes, the maximum size that can be used is 121 words (1936 bits).
2 This function is neither supported nor transmitted by Premium TSX SCP 111, TSX SCP 114 and
TSX SCP 1114 communication cards nor by TSX SCY 116 01 and TSX SCY 21601 communication modules.
3 On the Premium platform, the Read is done before the Write.
NOTE:
The READ_VAR communication function can read, on any remote devices, up to:
1008 consecutive bits for Premium CPUs.
2000 consecutive bits for M340 CPUs.
To be able to read more than these limitations, the SEND_REQ communication function must be used.
Use of Modbus Function Codes as a Client on Premium and M340
The table below lists the Modbus function codes and their use as a client on Premium, Quantum and M340 PLCs.
1
2
3
Function code
4
15
16
-
-
Quantum memory address
16#0XXX
16#4XXX
M340 and
Premium memory address
%M
%I
%MW
16#0XXX
16#4XXX
%IW
%M
%MW
Modbus request Communication function
Read output bits
Read input bits, see 1)
Read consecutive integer values
(until 125 registers for
Premium/Atrium PLCs)
READ_VAR
READ_VAR
READ_VAR
Read consecutive input integer values (until 124 registers for
Premium/Atrium PLCs), see 1)
READ_VAR
SEND_RER for
Premium/Atrium
PLCs
Write n output bits WRITE_VAR
Write consecutive integer values WRITE_VAR
1) The addresses %I and %IW cannot be used when creating a communication function of type
READ_VAR with the function input assistant.
40
35010500 12/2018
Interoperability
The way in which to use function codes with communication functions is described in the Modbus manual (see Premium and Atrium using EcoStruxure™ Control Expert, Asynchronous Serial Link,
User Manual) .
NOTE: Interoperability with Windows applications is provided by access to the PLC variables using
OFS software.
WARNING
UNEXPECTED APPLICATION BEHAVIOR - DATA EXCHANGE COMPATIBILITY
Data structure alignments are not the same for Premium/Quantum and M340 PLCs so verify that the data exchanged are compatible.
See the page DDT: Mapping rules (see EcoStruxure™ Control Expert, Program Languages and
Structure, Reference Manual) for more information.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
35010500 12/2018
41
Interoperability
42
35010500 12/2018
Communication Services and Architectures
Communication Architectures
35010500 12/2018
Communication Architectures
Chapter 4
Communication Architectures
Subject of this Chapter
This chapter gives an overview of the different communication architectures.
What Is in This Chapter?
This chapter contains the following topics:
Topic
Global Architecture
Network Architectures
Fieldbus
Page
35010500 12/2018
43
Communication Architectures
Global Architecture
At a Glance
Schneider has a communications strategy based on open standards (core of the range) such as:
Ethernet Modbus TCP/IP
CANopen
AS-Interface
Modbus Link Series
This has not always been the case and there are a significant number of installed bases on networks or proprietary buses such as Modbus Plus, Fipway, Ethway, X-Way on TCP/IP, Fipio,
Symax and Uni-telway.
Schneider offers a connectivity range for the main standards available on the market through its
Profibus, Interbus and TCPopen ranges.
The possible and recommended communication architectures are presented in the following pages, according to the type of PLC used:
At level 2: Inter-PLC network
see page 48
see page 52
.
The communication solutions for existing installations, from the Telemecanique or Modicon ranges, are then presented.
44
35010500 12/2018
Communication Architectures
Global Architecture
The following diagram shows a global communication architecture with an AS-i bus:
35010500 12/2018
45
Communication Architectures
The following diagram shows a global communication architecture with a Modbus and Uni-Telway bus:
46
35010500 12/2018
Communication Architectures
The following diagram shows a global communication architecture with a Modbus and Fipio bus:
NOTE: Depending on the type of network used, the interconnection is made either directly via a
PLC which routes the information (Ethernet/Uni-Telway), or via an additional device such as a bridge (Ethernet/Modbus) or switch (Ethernet/Ethernet).
NOTE: Technically, sophisticated solutions using Ethernet, Modbus Plus, Fipway, Fipio, Modbus,
Uni-Telway etc. in a single architecture are possible. However, to facilitate maintenance, user training and to reduce operating costs, it is recommended that you aim for maximum homogeneity between the types of networks and buses used. In the following architecture examples, we give an overview of the most suitable solutions depending on the devices connected.
35010500 12/2018
47
Communication Architectures
Network Architectures
At a Glance
Various network architectures are available. The Schneider product range enables you to create standard Ethernet mono-networks as well as transparent multi-network architectures
(Ethernet/Fipway/Modbus Plus). The following examples of network architectures show the various optimal solutions provided by Schneider products.
NOTE: The selection of an architecture with the Modbus Plus network or Fipway network is strongly linked to the use of Quantum or Premium devices:
Modbus Plus for Quantum and Premium PLCs,
Fipway for Premium PLCs.
NOTE: In the following illustrations, the arrows show the different communication possibilities.
An attempt has been made to show all the available scenarios.
The types of communication shown in the homogeneous Ethernet networks are also possible when these networks are extended using Modbus Plus or Fipway segments.
Mono-Network Ethernet Architecture
The diagram below shows an Ethernet mono-network:
48
NOTE: All inter-device exchanges are possible.
35010500 12/2018
Multi-Network Ethernet Architecture
The diagram below shows an Ethernet multi-network:
Communication Architectures
NOTE: All inter-device exchanges are possible.
35010500 12/2018
49
Communication Architectures
Multi-Network Ethernet/Modbus Architecture
The diagram below shows an Ethernet/Modbus multi-network:
50
NOTE: Access is possible from devices on the Modbus Plus network across Ethernet/Modbus Plus bridges. In contrast, the devices on the second Modbus Plus network cannot be accessed by an
Ethernet device via the Bridge Plus.
35010500 12/2018
Multi-Network Ethernet/Fipway Architecture
The diagram below shows an Ethernet/Fipway multi-network:
Communication Architectures
NOTE: All inter-device exchanges are possible.
35010500 12/2018
51
Communication Architectures
Fieldbus
At a Glance
The CPU uses many types of fieldbus: Ethernet, CANopen, Modbus, Modbus Plus, AS-i, Fipway,
Uni-Telway, Fipio, INTERBUS, and PROFIBUS.
Field buses addressed by each platform:
Fieldbus
Ethernet
CANopen
Modbus
Modbus Plus
AS-i
Fipway
Uni-Telway
Fipio
INTERBUS
PROFIBUS
Platform
M340
X*, O
X*
X, O
O*
O
–
–
–
–
O*
M580
X, O
–
O
O*
O
–
–
–
–
O*
Quantum
X*, O
–
X
X
O
–
–
–
O
O, O*
Momentum
X*
O
X
O
–
–
–
O
O
O
Premium
X*, O
O
O
O
O
O
X, O
X*
O
O, O*
X Embedded in the CPU.
X* Embedded is some CPUs.
O Available through extension modules (inserted in the CPU or added in a rack).
O* Communication is performed using a gateway connected to the Ethernet distributed network addressed by the CPU or by an Ethernet module.
– Not available.
52
35010500 12/2018
Communication Services and Architectures
X-Way Routing
35010500 12/2018
X-Way Message Routing
Chapter 5
X-Way Message Routing
Subject of this Chapter
This chapter describes the principles of X-Way message routing on X-Way multi-network architectures.
What Is in This Chapter?
This chapter contains the following topics:
Topic
General
Features
Main Address
Multi-Module Station Addresses
Messaging
Page
35010500 12/2018
53
X-Way Routing
General
Introduction
A multi-network architecture consists of several networks. Two levels of architecture are distinguished:
Multi-module architectures, in which there are several networks but no communication between these different segments is provided by the communication system.
Multi-network architectures, composed of several network segments interconnected by bridge stations. Communication transparency is then provided in the equipment group present in this type of architecture.
This chapter describes how to set up the bridge function in a Premium PLC station, as well as the use of communication services in a multi-network architecture. The multi-network architecture complies with X-Way communication standards.
To set up stations on different networks, refer to the documentation corresponding to the module used.
NOTE: X-Way communication is not available for Modicon M340 PLCs.
54
35010500 12/2018
X-Way Routing
Features
At a Glance
An X-Way PLC architecture is comprised of various network levels that interconnect via intermediate stations.
In a multi-network architecture, a single logic link must exist between two terminal stations.
Example
Terminal Stations
A terminal station is addressed by the {network address . station address} pairing.
Terminal stations receive the messages intended for their network address, as well as the general broadcast messages, and send to their network connection all the messages intended for a remote station.
Intermediate Stations
An intermediate station has as many network addresses as it has connection points to different networks. One of its addresses is considered to be the main address and has the role of guaranteeing access to all the communication entities of a routing station.
Intermediate stations are classified in two categories:
Multicoupler stations
Bridge stations
Multicoupler Stations
These provide management of various network couplers and guarantee all the mono-network services on the various network segments (common words, telegrams, messaging). They do not offer routing between the various network connections.
35010500 12/2018
55
X-Way Routing
Bridge Stations
These provide the same functions as the multi-coupler stations and also guarantee transparency of communication between the various network connections.
56
35010500 12/2018
X-Way Routing
Main Address
Introduction
A station configured in bridge mode has as many addresses as it does network connection points.
The network address that corresponds to the network module with the lowest module address
(module the farthest to the left in the station rack) is regarded as the main address of the station.
Using the main address of a station guarantees access to a bridge station.
Rule
A bridge station must always be accessed by its main address.
Addressing Example
The example shows the communication between stations connected on the Fipway networks.
For a communication from station A to station R2, the main address of station R2 is {11.3}.
For a communication from station A to station R1, the main address of station R1 is {12.7}.
For a communication from station A to station R3, the main address of station R3 is {13.5}.
For a communication from station A to station C, the address of station C is {12.7}5.0.56.
35010500 12/2018
57
X-Way Routing
Multi-Module Station Addresses
Introduction
A station configured in multi-module mode has as many addresses as it does network connection points.
There is no main address for the station. It will be addressed according to the network that communicates with it.
Rule
A multi-module station must always be accessed via the network address that corresponds to the network module enabling entry to the station.
Example
In the following example, station R1 does not have the bridge function between its modules 2, 4 and 5.
58
For a communication from station A to station R1, the address is {13.5}SYS.
For a communication from station B to station R1, the address is {12.7}SYS.
35010500 12/2018
X-Way Routing
Messaging
With Multi-Coupler Stations
Messages intended for a network are sent to the coupler connected to the destination network. The configuration phase allows the destination coupler to be determined.
Specific case
Messages intended for a network with an unknown address are sent to the network with the main address of the station, along with messages whose network number is 0.
Example:
All messages intended for network 3 are sent to the coupler with module address 4, and those whose destination network is 1 to the network link integrated into the processor.
All messages whose network number address is different from 1 or 3 are sent to the processor that manages the main network.
In a multi-coupler architecture, communication is limited to a single network level.
With Bridge Stations
Messages intended for a network are sent to the coupler that has access to this network. The configuration phase allows determination of the accessible networks for each coupler of the station.
Specific case
Messages whose network number is 0 are sent to the network with the main address of the station.
35010500 12/2018
59
X-Way Routing
60
35010500 12/2018
Communication Services and Architectures
Addressing
35010500 12/2018
Addressing
Part II
Addressing
Subject of this Part
This part describes the different addressing solutions for devices on a communication bus or network.
What Is in This Part?
This part contains the following chapters:
Chapter
6
7
8
9
10
11
Chapter Name
General Points Concerning Addressing
IP Addressing
Modbus Plus Addressing
X-Way Addressing
Modicon M340 PLCs Addressing
General points concerning bridging
Page
35010500 12/2018
61
Addressing
62
35010500 12/2018
Communication Services and Architectures
Introduction to Addressing
35010500 12/2018
General Points Concerning Addressing
Chapter 6
General Points Concerning Addressing
General
At a Glance
Within a communication architecture, each device must be identified by an address. This address is specific to each device, and enables the device initiating communication to determine the destination precisely. Similarly, for the configuration of services such as Global Data on Ethernet, the Peer Cop service on Modbus Plus or common words and shared tables on Fipway, these addresses make it possible to identify the stations that own different shared information.
Schneider products support 4 types of addressing depending on the type of device, network or bus used:
IP addressing
see page 65
Modbus Plus addressing
,
see page 69
see page 73
Modicon M340 PLCs addressing
,
see page 87
35010500 12/2018
63
Introduction to Addressing
64
35010500 12/2018
Communication Services and Architectures
IP Addressing
35010500 12/2018
IP Addressing
Chapter 7
IP Addressing
Note on IP Addressing
IP Address
On a TCP/IP Ethernet network, each device must have a unique IP address.This address is made up of two identifiers, one of which identifies the network, while the other identifies the connected machine.
The uniqueness of the addresses is managed as follows:
When the network environment is of open type, the uniqueness of the address is guaranteed by the attribution of a network identifier by the relevant authority in the country where the network is located,
If the type of environment is closed, the uniqueness of the address is managed by the company's network manager.
An IP address is defined as 32 bits. It consists of 4 numbers, one for each byte of the address.
NOTE: Standardized and made common largely thanks to the Internet, IP addressing is described in detail in RFCs (Request For Comment) 1340 and 791 which stipulate the Internet standards as well as in computing manuals describing networks. You can refer to these sources for further information.
Example
Depending on the size of the network, three classes of address can be used:
35010500 12/2018
65
IP Addressing
Spaces reserved for the different classes of IP addresses:
B
C
Class
A
Range
0.0.0.0 to 127.255.255.255
128.0.0.0 to 191.255.255.255
192.0.0.0 to 223.255.255.255
Class A addresses are intended for large-scale networks which have a large number of connected sites.
Class B addresses are intended for medium-scale networks which have fewer connected sites.
Class C addresses are intended for small-scale networks which have a small number of connected sites.
Sub-Addressing and Sub-Network Mask
An IP address is composed of two identifiers, one of which identifies the network while the other identifies the connected machine. In reality, the machine identifier can also hold a sub-network identifier.
In an open environment, having received a network identifier from the relevant authority, the local system administrator has the possibility of managing many networks. This means that local networks can be installed without having any effect on the external world, which still sees just one network designated by the network identifier.
The sub-network mask makes it possible to see the number of bits attributed respectively to the network identifier and to the sub-network identifier (bits at 1), and then to the machine identifier
(bits at 0).
66
35010500 12/2018
IP Addressing
Example
Example: 140.186.90.3
The segmentation allows for 254 possible sub-networks with 254 sub-network machines.
The value of the sub-network mask should be chosen so that it is consistent with the IP address class.
The sub-network mask will have the following value:
for a class A address: 255.xxx.xxx.xxx, for a class B address: 255.255.xxx.xxx, for a class C address: 255.255.255.xxx, xxx is an arbitrary value which can be chosen by the user.
Gateway
The term Gateway is used in this manual in the sense of "router". If the target machine is not connected to the local network, the message will be sent to the "default gateway" connected to the local network, which will guarantee routing to another gateway or towards its final destination.
35010500 12/2018
67
IP Addressing
68
35010500 12/2018
Communication Services and Architectures
Modbus Plus Addressing
35010500 12/2018
Modbus Plus Addressing
Chapter 8
Modbus Plus Addressing
Addressing for a Modbus Plus Communication Entity
At a Glance
Modbus Plus addressing makes it possible to identify a device on a Modbus Plus network.
The Modbus Plus addressing system is based on the access path that needs to be followed to reach the destination device. This path is determined by the Modbus Plus routers, also referred to as Bridges Plus. So when a device has to communicate with another device, it is necessary to determine the path taken by the data to be communicated.
Principle
A Modbus Plus network segment may have up to 64 addressable devices. Each device has a unique address between 1 and 64.
Several segments may be linked by Bridges Plus.
The routing path is determined by the 5 bytes that indicate in succession the addresses of the devices that need to be crossed before arriving at the destination.
The routing system makes it possible to cross a maximum of 3 segments, in other words to allow communication between stations belonging to 5 consecutive segments.
NOTE: When not all of the 5 bytes are necessary (only one Bridge Plus crossed for example), the remaining bytes are set to 0.
35010500 12/2018
69
Modbus Plus Addressing
Illustration
The following illustration shows a multi-segment Modbus Plus structure. Three characteristic examples are used to explain Modbus Plus addressing:
Example 1
The routing path to access the Quantum station is:
61, 30, 22, 62, 0.
NOTE: The final 0 is added so that the address path consists of 5 bytes.
Example 2
The routing path to access slave A is as follows:
61, 25, 1, 0, 0.
NOTE: As slave A is the only slave on port 1, it is sufficient to indicate the port number and complete the path with the zeros to obtain the 5 bytes for the address path.
70
35010500 12/2018
Modbus Plus Addressing
Example 3
The routing path to access slave 113 is as follows:
61, 25, 4, 113, 0.
NOTE: When several slaves are connected to the same port, it is necessary to indicate the slave number after the port number. Do not forget to complete the address with zeros to obtain 5 bytes.
35010500 12/2018
71
Modbus Plus Addressing
72
35010500 12/2018
Communication Services and Architectures
X-Way Addressing
35010500 12/2018
X-Way Addressing
Chapter 9
X-Way Addressing
Subject of this Chapter
This chapter describes X-Way addressing and indicates its fields of application.
What Is in This Chapter?
This chapter contains the following topics:
Topic
Addressing for a Communication Entity
Types of Communication Entities
Processor Communication Channel Addressing
Addressing for a TSX SCY 21601 Communication Module
Examples of Intra-Station Addressing: Uni-Telway Addressing
Examples of Intra-Station Addressing: Fipio Addressing
Examples of Intra-Station Addressing
Page
35010500 12/2018
73
X-Way Addressing
Addressing for a Communication Entity
At a Glance
X-Way addressing makes it possible to identify a communication entity on a network or a bus, or on a station’s bus on a network. Each station is identified by a unique address, which consists of a network number and a station number. The addresses then differ according to the bus:
Uni-Telway or Modbus bus
Fipio bus
Within a station, each communication entity is characterized by a topological address (access path) and a type
see page 76
.
NOTE: An address is expressed in the form of a character string. However, it can only be used in conjunction with the function ADDR() , which is why the following notation will be used to describe an address: ADDR('address string') ;
Addressing a Station on a Network
The address of a station on a network takes the form: ADDR('{n.s}SYS') where: n: network number (network) s: station number (station
SYS: keyword used to stipulate the station server system (
see page 76
Addressing a Device on a Uni-Telway or Modbus Bus
The address of a device on a Uni-Telway or Modbus bus depends on the station managing the bus:
stand-alone station: ADDR('r.m.c.e') station belonging to a network: ADDR('{n.s}r.m.c.e') where: n: network number (network) s: station number (station) r: rack number (rack) m: module number (module) c: channel number (channel) e: number of device or slave (equipment)
74
35010500 12/2018
X-Way Addressing
Addressing of a Device on a Fipio Bus
The address of a device on a Fipio bus depends on the station managing the bus:
stand-alone station: ADDR('\b.e\SYS') station belonging to a network: ADDR('{n.s}\b.e\SYS') where: n: network number (network) s: station number (station) b: bus number (bus), for Fipio the bus number is always 2 e: device number (equipment)
SYS: keyword used to stipulate the station server system (
see page 76
Example
The figure below describes the address of the station located in the gray rectangle. The example here shows slave 2 on channel 1 of the module in rack 0 (base rack), slot 1, on network 20, station
3:
35010500 12/2018
75
X-Way Addressing
Types of Communication Entities
At a Glance
There are different types of communication entities. To characterize them, the following keywords have been created: SYS , APP , and APP.num
. Another keyword, ALL , makes it possible to send general broadcast messages.
These exchanges are performed by the communication functions described in the Communication
EF library.
It is possible to class addresses into three types:
local addresses remote addresses broadcast addresses
Keywords
The keywords are as follows:
SYS gives access to the Uni-te server of a processor, channel, communication module, etc.
APP gives access to a station’s PL7 or Control Expert application.
ALL is defined to describe a broadcast. For a TSX SCY 11601 module, the keyword is 0 . It may replace one of the elements of a topological address. The broadcast level is determined according to the location of the keywords ALL or 0 in the address:
when alongside the network number, the broadcast is sent to all stations on the selected network (e.g.: the address ADDR('{2.ALL}') represents all stations on network 2), when alongside the station number, the broadcast is sent to all the entities connected to the intra-station communication channels (e.g.: the address ADDR('{2.4}ALL') represents all the communication entities of station 4 on network 2).
NOTE: For the sender application to communicate with the text function block of a TSX series 7
PLC’s PL7-2 or PL7-3 application, the keyword must be APP.num
, where num corresponds to the destination text function block number for the exchange.
76
35010500 12/2018
X-Way Addressing
Local Addresses
Local addresses contain topological addresses and the addresses of slaves on a bus.
Destination
Micro/Premium Uni-TE server
PL7 or Control Expert application
PL7-3 application
Uni-Telway slave
Modbus slave
Link in character mode
Module server
Sub-module or channel server
Fipio device server
Local address
SYS
APP
APP.text block number module.channel.slave number module.channel.slave number module.channel.SYS
module.SYS
module.channel.SYS
\bus number.connection point\SYS
Remote Addresses
Remote addresses correspond to the addresses of devices connected to a network.
Destination
Destination on remote network
Destination on local network
Remote address
{network.station}local address
{station}local address
Broadcast Addresses
Broadcast addresses depend on the destination devices.
Destination
Broadcast to all stations
Broadcast to all local addresses
Broadcast to all modules
Broadcast to all Uni-Telway or Modbus slaves
Broadcast to all Modbus slaves with a
TSX SCY 11601 module
Broadcast address
{network.ALL}local address
{network.station}ALL
ALL.SYS
module.channel.ALL
module.channel.0
NOTE: For Modbus equipments the report code of Broadcast function for a correct operation is 1.
35010500 12/2018
77
X-Way Addressing
Processor Communication Channel Addressing
At a Glance
Following are examples of the different types of addressing for a processor’s communication channels.
The examples are based on a Premium type processor.
The modules have a topological address that is a function of the module’s position in the rack.
Depending on the desired configuration, there may be either a single or double power supply, which occupies 1 or 2 slots in the rack respectively. As a result, the first slot the processor uses is either 0 or 1.
With a Single Power Supply
The power supply occupies one slot. The processor’s communication channels can then have the following addresses:
78
35010500 12/2018
X-Way Addressing
With a Double Power Supply
The power supply occupies two slots. The processor’s communication channels can then have the following addresses:
35010500 12/2018
79
X-Way Addressing
Addressing for a TSX SCY 21601 Communication Module
At a Glance
Following are examples of the different types of addressing for TSX SCY 21601 communication modules.
The examples are based on a Premium type processor.
NOTE: These types of communication module are limited according to processor. Please refer to the installation manual to determine the number of expert communication channels.
Examples
The module’s communication channels can have the following addresses:
80
35010500 12/2018
X-Way Addressing
Examples of Intra-Station Addressing: Uni-Telway Addressing
At a Glance
With this type of addressing, a master station can access different slaves connected to a bus.
In the following examples, the slaves are connected to the master station (with a Premium processor) via a Uni-Telway bus.
Addressing Rules
In this configuration, the addressing values are as follows:
For the rack address:
0 to 7
For the module address:
0 to 14
For the channel address:
0 if connected via the terminal port
0 if connected via a built-in link of a TSX SCY 21601 module
1 if connected via a PCMCIA card
For the slave:
1 to 98 if the slave is connected to a PCMCIA card or the built-in link of the TSX SCY 21601
module. In this case, the master station can scan up to 98 slaves.
1 to 8 if the slave is connected to the terminal port. In this case the master station can scan up to 8 slaves.
CAUTION
UNEXPECTED BEHAVIOR OF APPLICATION
Do not use wrong address parameters. For instance:
Do not set an address parameter that does not correspond to the targeted equipment.
Do not use value greater than 98 in ADDR function (field "e" for the equipment address) when using a TSXSCY21601 or higher than 8 when using a CPU embedded serial port.
Failure to follow these instructions can result in injury or equipment damage.
35010500 12/2018
81
X-Way Addressing
Connection via Terminal Port
A device with the address Ad0=8 is connected to the terminal port of a Premium.
Address settings of slave 8: ADDR('0.0.0.8')
Connection via TSX SCY 21601 Module
A device with the address Ad0=1 is connected to the built-in link of a TSX SCY 21601 at position
2 in the base rack.
Address settings of slave 1: ADDR('0.2.0.1')
82
35010500 12/2018
X-Way Addressing
Examples of Intra-Station Addressing: Fipio Addressing
At a Glance
Exchanges with the bus manager are of variable exchange or message exchange type.
The addressing syntax to access the Unite messaging server is as follows:
\ bus number . connection point \ SYS
Addressing Rules
For Fipio communication, the addressing values are as follows:
For the bus address: always 2 for a Fipio bus,
For the connection point: 1 to 127 as it is possible to connect up to 127 devices on the bus.
Examples
In the following example, the bus manager addresses the Premium at connection point 4, or the
Magelis at connection point 8.
Address settings of device 4: ADDR('\2.4\SYS')
Address settings of device 8: ADDR('\2.8\SYS')
35010500 12/2018
83
X-Way Addressing
Examples of Intra-Station Addressing
At a Glance
For an intra-station exchange to take place (i.e. an exchange between two stations on the same network or on different networks), the address must also show the destination entity’s network number and station number.
Example 1
The multi-network configuration is as follows:
84
In the first case, station B addresses station A's system:
ADDR('{21.1}SYS')
In the second case, station B addresses station C:
ADDR('{1.2}0.5.0.56')
35010500 12/2018
X-Way Addressing
Example 2
The example below shows how to access a Magelis system connected to a Fipio bus (connection point 6) and communicate with text block TXT 8 on a model 40 programmable PLC connected to network 2.
The address of the TXT 8 text block on the TSX 7 PLC station 4 is:
ADDR('{2.4}APP.8')
The address of the Magelis system is:
ADDR('{2.4}\2.6\SYS')
35010500 12/2018
85
X-Way Addressing
86
35010500 12/2018
Communication Services and Architectures
Modicon M340 PLCs Addressing
35010500 12/2018
Modicon M340 PLCs Addressing
Chapter 10
Modicon M340 PLCs Addressing
Purpose of this Chapter
This chapter describes Modicon M340 PLCs addressing and indicates its fields of application.
What Is in This Chapter?
This chapter contains the following topics:
Topic
Modicon M340 Types of Communication Entities
Modicon M340 Addressing for a Communication Entity
Processor Communication Channels Addressing
Example of Modicon M340 Ethernet Addressing
Example of Modicon M340 CANopen Addressing
Examples of Modicon M340 Modbus and Character Mode Addressing
Examples of Modicon M340 Communication EFs Addressing
Page
35010500 12/2018
87
Modicon M340 PLCs Addressing
Modicon M340 Types of Communication Entities
At a Glance
There are different types of communication entities.
These exchanges are performed by the communication functions described in the Communication
EF library.
It is possible to class addresses into 3 types:
local addresses, identified by r.m.c.SYS
, or more simply, r.m.c
, remote addresses, to address a device (Modbus, CANopen or Ethernet) directly connected to the channel, broadcast addresses, depend on the network. For Modbus communication, broadcast address is obtained with the slave number set to 0. Note that a broadcast address can be used for all networks but requires that the communication channel supports broadcasting. This is not always the case.
SYS Keyword
SYS gives access to a local module or a channel server. SYS is used for character mode and can be ommitted.
Broadcast Addresses
Broadcast addresses depend on the destination devices:
Destination
Broadcast to all Modbus slaves (the slave number equals 0)
Broadcast address rack.module.channel.0
88
35010500 12/2018
Modicon M340 PLCs Addressing
Modicon M340 Addressing for a Communication Entity
At a Glance
With Modicon M340 PLCs, it is possible to address any Modicon M340 PLC communication channel and any device directly connected to a Modicon M340 PLC communication channel.
Each device is identified by a unique address, which consists of a device number or an IP address.
The addresses then differ according to the protocol:
Ethernet TCP/IP
Modbus or CANopen
Character Mode
Within a station, each communication entity is characterized by a topological address (access path) and a target entity.
NOTE: An address is expressed in the form of a character string. However, it can only be used in conjunction with the function ADDM , which is why the following notation will be used to describe an address: ADDM('address string') .
Modicon M340 addressing uses 3 concepts:
The target entity depends on the communication EF and is chosen implicitly:
MBS for addressing a Modbus server,
TCP.MBS
for addressing a TCP Modbus server,
SYS for addressing a channel server on Character mode. SYS can be ommitted.
The communication channel is explicit (processor’s or module’s position and communication channel number) or symbolized with the Netlink name for Ethernet communication.
The node address depends on the communication protocol:
IP address with Ethernet,
node address with CANopen, slave address with Modbus.
Addressing a Station on a Ethernet
The address of a station on Ethernet takes the form:
ADDM('Netlink{hostAddr}')
ADDM('Netlink{hostAddr}TCP.MBS')
ADDM('Netlink{hostAddr}node')
ADDM('r.m.c{hostAddr}')
ADDM('r.m.c{hostAddr}TCP.MBS')
ADDM('r.m.c{hostAddr}node')
ADDM('{hostAddr}')
ADDM('{hostAddr}TCP.MBS')
ADDM('{hostAddr}node')
35010500 12/2018
89
Modicon M340 PLCs Addressing
Where:
Netlink: network name set in the Net Link field of Ethernet channel hostAddr: IP address of device r: rack number (rack) c: channel number (channel) node: Modbus or CANopen node behind a gateway (gateway identified with hostAddr)
NOTE: If the netlink name is ommitted the system takes the default netlink connection which is the closest link to the processor (usually the processor Ethernet channel).
Addressing of a Device on a CANopen Bus
The address of a device on a CANopen bus takes the form ADDM('r.m.c.e') , where:
r: rack number (rack) m: rack module position c: channel number (channel) of CANopen port (2) e: CANopen slave node (equipment) (range 1 to 127)
Addressing a Device on a Modbus
The address of a device on a Modbus bus takes the form ADDM('r.m.c.e.MBS') , where:
r: rack number (rack) m: rack module position c: channel number (channel) of Modbus port (0) e: Modbus slave number (equipment) (range 1 to 247)
Addressing a Device on Character mode
To send or receive a character string, you can use ADDM('r.m.c') or ADDM('r.m.c.SYS') , where:
r: rack number (rack) m: rack module position c: channel number (channel) of Character mode port (0)
SYS: keyword used to stipulate the station server system (
see page 88
SYS can be ommitted.
90
35010500 12/2018
Modicon M340 PLCs Addressing
Example
The figure below describes the address of the servodrive. The example here shows slave 14 on channel 2 (CANopen) of the module in rack 0, slot 0:
35010500 12/2018
91
Modicon M340 PLCs Addressing
Processor Communication Channels Addressing
At a Glance
Following are examples of the different types of addressing for a processor’s communication channels.
The examples are based on a Modicon M340 type processor.
The modules have a topological address that is a function of the module’s position in the rack.
The first two slots of the rack (marked PS and 00) are reserved for the rack’s power supply module
(BMX CPS ••••) and the processor (BMX P34 •••••) respectively.
Available communication channels
The available communication channels vary depending on the processor:
Processor
BMX P34 1000
BMX P34 2000
BMX P34 2010/20102
BMX P34 2020
BMX P34 2030/20302
Key
X Available
- Not available
-
X
X
X
X
Integrated Modbus
Connection
-
X
X
-
-
Integrated
CANopen Master
Connection
-
X
X
-
-
Integrated
Ethernet
Connection
92
35010500 12/2018
Modicon M340 PLCs Addressing
Processor Communication Channels Addressing
The diagram below shows an example of Modicon M340 configuration including a BMX P34 2010 processor and the addresses of the processor communication channels:
The diagram below shows an example of Modicon M340 configuration including a BMX P34 2030 processor and the addresses of the processor communication channels:
35010500 12/2018
93
Modicon M340 PLCs Addressing
Example of Modicon M340 Ethernet Addressing
At a Glance
With this type of addressing, a station can access different station connected to logical network.
Connection via CPU Ethernet port
A device with the IP address 139.180.204.2 is connected to the Ethernet network. It is the processor Ethernet port configured with Netlink name Ethernet_1 .
Address settings station 1: ADDM('0.0.3{139.180.204.2}') or Address settings station 1: ADDM('Ethernet_1{139.180.204.2}')
94
35010500 12/2018
Modicon M340 PLCs Addressing
Example of Modicon M340 CANopen Addressing
At a Glance
With this type of addressing, a master station can access different slaves connected to CANopen bus.
Addressing Rules
The syntax of CANopen addressing is ADDM ('r.m.c.node') . The meaning of the string parameter is as follows:
r: rack address. The processor’s rack address is always 0.
m: module address. The Modicon M340 processor’s slot number in the rack is always 0.
c: channel address. The Modicon M340 CANopen port is always channel 2.
node: slave number to which the request is being sent. The range for configured slave numbers is from 1 to 127.
Example
In the following example, the Modicon M340 processor’s bus manager addresses the Lexium 05 device at connection point 28:
Address settings of slave 28: ADDM('0.0.2.28') .
NOTE: In addition to the address defined by ADDM , the READ_VAR and WRITE_VAR functions use another parameter NUM , which must be defined to address the SDO to be read or written.
35010500 12/2018
95
Modicon M340 PLCs Addressing
Examples of Modicon M340 Modbus and Character Mode Addressing
At a Glance
The following examples deal with:
Modbus addressing
Character mode addressing.
Modbus Addressing Rules
The syntax of Modbus addressing is ADDM ('r.m.c.node') . The meaning of the string parameter is as follows:
r: rack address. The processor’s rack address is always 0.
m: module address. The Modicon M340 processor’s slot number in the rack is always 0.
c: channel address. The Modicon M340 processor’s serial port is always channel 0.
node: slave number to which the request is being sent. The range for configured slave numbers is from 1 to 247.
NOTE: In a Modbus Slave configuration, an additional address, number 248, is used for a pointto-point serial communication.
Serial Link Using Modbus Protocol
The diagram below shows two Modicon M340 processors connected via a serial link and using
Modbus protocol:
96
The address settings of the slave processor number 8 are ADDM('0.0.0.8') .
35010500 12/2018
Modicon M340 PLCs Addressing
Character Mode Addressing Rules
The syntax of Character mode addressing is ADDM ('r.m.c') or ADDM ('r.m.c.SYS') ( SYS can be omitted). The meaning of the string parameter is as follows:
r: rack address of the connected device.
m: module address of the connected device.
c: channel address of the connected device.
SYS: keyword used to stipulate the station server system. SYS can be omitted.
Serial Link Using Character Mode Protocol
The diagram below shows a Modicon M340 processor linked to a data entry/display terminal
TM8501:
The address settings of the TM8501 terminal are ADDM('0.0.0') or ADDM('0.0.0.SYS') .
35010500 12/2018
97
Modicon M340 PLCs Addressing
Examples of Modicon M340 Communication EFs Addressing
At a Glance
The multi-network addressing available on Modicon M340 PLCs is described below.
Example 1
The first example is a multi-network configuration as follows:
98
In the diagram above there are the following configurations:
Three Modicon M340 configurations called A, B and D
One Premium configuration called C
All the configurations can communicate because of the following statements:
A and B: communication between two Modicon M340 PLCs on an Ethernet network is possible.
A and C: communication between a Modicon M340 PLC and a Premium PLC is possible on an
Ethernet network.
A or C, and D: communication between two Modicon M340 PLCs or between a Modicon M340
PLC and a Premium PLC on Ethernet multi-network is possible. An IP router is required.
35010500 12/2018
Example 2
The second example is a multi-network configuration as follows:
Modicon M340 PLCs Addressing
In the diagram above there are two Modicon M340 configurations which are called A and B. The configuration B is directly connected to the Modbus device 1 via Modbus communication channel.
Communication between the two Modicon M340 PLCs is possible because the configurations are linked to the same Ethernet network.
Communication between the configuration A and the Modbus device 2 is possible only if you use an Ethernet/Modbus gateway. In case of it is a CANopen device, an Ethernet/CANopen gateway is required.
NOTE: To address the CANopen device or the Modbus device 2 on the configuration A you must use the following syntax : ADDM('Netlink{hostAddr}node') , the gateway being identified with hostAddr field. For example, if the Netlink is set to Ethernet_1 , the gateway address is 139.160.234.64
and the slave number of the device is set to 247, the syntax of the ADDM function is as follows: ADDM('Ethernet_1{139.160.230.64}247')
35010500 12/2018
99
Modicon M340 PLCs Addressing
100
35010500 12/2018
Communication Services and Architectures
Introduction to bridging
35010500 12/2018
General points concerning bridging
Chapter 11
General points concerning bridging
Subject of this Chapter
This chapter gives an overview of the different bridging solutions for devices in a communication architecture.
What Is in This Chapter?
This chapter contains the following topics:
Topic
Bridging Description
Bridging Example
Page
35010500 12/2018
101
Introduction to bridging
Bridging Description
At a Glance
There are two available connection modes:
Direct PLC access: Control Expert connects directly to the PLC.
Transparent PLC access or bridging: Control Expert connects to a PLC via a Modicon M340
PLC.
Set Address
The direct PLC access and transparent PLC access features are available via the Set Address screen. In this screen, you must enter the PLC address.
To access the Set Address screen, use the Set Address command on the PLC menu.
The Set Address screen is as follows:
Direct PLC Access Syntax
The available syntaxes for a direct PLC access are described below:
Connection used
USB
Ethernet
Modbus
Address
SYS or empty
IP address: 139.169.3.4
Slave number
102
35010500 12/2018
Introduction to bridging
Transparent PLC Access Syntax
The bridging address string consists of two parts:
First part: The "via address" (optional).
Second part: The "remote PLC address".
The address parameter syntax is:
via address\\remote PLC address
The syntax for the "remote PLC address" depends on the network link type:
Network link
Modbus slave
Ethernet
Ethernet device
Remote PLC address
Link_address.Modbus Slave Number
Link_address {IP address}
Link_address.UnitID
"Link_address" is a r.m.c-type topological address where:
r: rack address.
m: module address.
c: channel address.
The "via address" is a classical address depending on the media:
Media
Modbus slave
USB
Ethernet
Via address
Slave_nbr
SYS or empty
IP address
Online Service Limitations of Transparent PLC Access
The transparent PLC access or bridging offers:
full online services if the remote PLC is a Modicon M340 or a Quantum PLC.
restricted online services if the remote PLC is a Premium PLC (not all option module screens work).
no online services for the modules ETY 4103, ETY 5103, WMY 100 and ETY PORT (except embedded Ethernet ports of Premium PLCs P57 4634, P57 5634 and P57 6634).
35010500 12/2018
103
Introduction to bridging
Bridging Example
At a glance
The following pages present an example of PLC configurations bridging and its transparent PLC adresses.
Bridging Example
The following example consists of the following PLC configurations:
Configuration 3: this Modicon M340 configuration consists of the following communication modules:
An Ethernet-Modbus processor with IP address 139.160.235.34 and Modbus Master. The processor is in slot 0 of the configuration so that the topological address of this processor’s
Ethernet channel is 0.0.3 and the topological address of this processor’s Modbus channel is
0.0.0.
An Ethernet module BMX NOE 0100 with IP address 118.159.35.2. The Ethernet module is in slot 5 of the configuration so that the topological address of this Ethernet module’s channel is 0.5.0.
Configuration 1: this configuration consists of a remote PLC linked to processor’s Ethernet channel of the configuration 3. The IP address of this remote PLC is 139.160.235.16.
Configuration 2: this configuration consists of a remote PLC linked to Ethernet module’s channel of the configuration 3. The IP address of this remote PLC is 118.159.35.45.
Configuration 4: this configuration consists of a remote PLC linked to processor’s Modbus channel of the configuration 3. The Modbus slave address of this remote PLC is 66.
104
35010500 12/2018
This diagram presents the bridging example:
Introduction to bridging
The transparent PLC addresses are as follows:
Bridging configuration Transparent PLC address
(1) USB connection to remote PLC, which is linked to an Ethernet module SYS\\0.5.0{118.159.35.45}
139.160.235.34\\0.5.0{118.159.35.45} (2) processor’s Ethernet channel to remote PLC, which is linked to an
Ethernet module
(3) processor’s Modbus channel to remote PLC linked, which is linked to an Ethernet module
5\\0.5.0{118.159.35.45}
SYS\\0.0.0.66
(4) USB connection to remote PLC, which is linked to processor’s Modbus channel
(5) Ethernet module connection to remote PLC, which is linked to processor’s Modbus channel
(6) Ethernet module connection to remote PLC, which is linked to processor’s Ethernet channel
118.159.35.2\\0.0.0.66
118.159.35.2\\0.0.3{139.160.235.16}
35010500 12/2018
105
Introduction to bridging
106
35010500 12/2018
Communication Services and Architectures
Operating Modes
35010500 12/2018
Operating Modes
Part III
Operating Modes
Subject of this Part
This part describes the operating modes associated with expert communication.
What Is in This Part?
This part contains the following chapters:
Chapter
12
13
14
15
16
Chapter Name
Network Configuration
Bus Configuration
Configuration of X-Way Routing Premium Stations
Debugging
Communication Function Programming and Entry Help
Page
35010500 12/2018
107
Operating Modes
108
35010500 12/2018
Communication Services and Architectures
Network Configuration
35010500 12/2018
Network Configuration
Chapter 12
Network Configuration
Subject of this Chapter
This chapter presents the tools for configuring a network at the global level and at the station level.
What Is in This Chapter?
This chapter contains the following topics:
Topic
Network Configuration Principle Using Control Expert
Creating a Logic Network
Configuring a Logic Network
Associating a Logic Network with Network Hardware
Page
35010500 12/2018
109
Network Configuration
Network Configuration Principle Using Control Expert
At a Glance
With Control Expert, the installation of a network takes place from the application browser and from the hardware configuration editor.
The method involves the following four steps:
creation of a logic network, configuration of the logic network, declaration of the module or of the PCMCIA card (for Premium), association of the card or of the module with the logic network.
These four methods are presented further on in this documentation.
NOTE: The advantage of this method is that from the second step onwards, you can design your communication application (you do not need the hardware to start working) and use the simulator for functional testing of it.
NOTE: The first two steps are carried out in the project browser and the following two in the hardware configuration editor.
This manual introduces the method. For details of the various network configurations, please refer to the following documentation:
Ethernet configuration for Premium (see Premium and Atrium Using EcoStruxure™ Control
Expert, Ethernet Network Modules, User Manual) , Ethernet configuration for M340
(see Modicon M340 for Ethernet, Communications Modules and Processors, User Manual) , and Ethernet configuration for Modicon M580,
Modbus Plus configuration (see Premium and Atrium Using EcoStruxure™ Control Expert,
Modbus Plus Network, User Manual) ,
Fipway configuration (see Premium and Atrium using EcoStruxure™ Control Expert, Fipway
Network, User Manual) .
110
35010500 12/2018
Network Configuration
Creating a Logic Network
At a Glance
The first step in implementing a communication network is to create a logic network.
Creating a Logic Network
The following table describes how to create a network using the project browser.
Step
1
Action
Expand the
Result::
Communication directory in the project browser.
2 Right-click in the
Result::
Networks sub-directory and select the New network option.
35010500 12/2018
111
Network Configuration
Step
3
Action
Select the network that you want to create from the list of available networks and give it a meaningful name.
Result: Example of an Ethernet network:
4
Note: You can also add a comment, if you so desire, by clicking on the
Comment tab.
Click OK and a new logic network is created.
Result: We have just created the Ethernet network that appears in the project browser
Note: As you can see, a small icon indicates that the logic network is not associated with any PLC hardware. Furthermore, the small blue "v" sign indicates that the project needs to be rebuilt before it can be used in the PLC.
112
35010500 12/2018
Network Configuration
Configuring a Logic Network
At a Glance
The second step in implementing a communication network is to configure a logic network.
This manual introduces the access to network configuration. For information on how to configure the various networks, please refer to the following documentation:
Ethernet configuration for Premium (see Premium and Atrium Using EcoStruxure™ Control
Expert, Ethernet Network Modules, User Manual) , Ethernet configuration for M340
(see Modicon M340 for Ethernet, Communications Modules and Processors, User Manual) , and Ethernet configuration for Modicon M580 (see Modicon M580, Hardware, Reference
Manual) ,
Modbus Plus configuration (see Premium and Atrium Using EcoStruxure™ Control Expert,
Modbus Plus Network, User Manual) ,
Fipway configuration (see Premium and Atrium using EcoStruxure™ Control Expert, Fipway
Network, User Manual) .
Configuring a Logic Network
The table below describes how to access the configuration of a network from the project browser.
Step
1
Action
In the project browser, expand the directory tree under the Networks sub-tab located in the Communication tab of the tree directory to display all the project networks.
Example::
35010500 12/2018
2 Double-click the network you want to configure to obtain the network configuration window.
Note: The windows differ according to the network family selected. However, for all networks, from this window it is possible to configure the Global Data, IPO scanning, Peer Cop utilities, common words, etc.
Note: For Ethernet networks, an intermediate step is necessary, which involves selecting the family of the module that will be used in the hardware configuration.
113
Network Configuration
Associating a Logic Network with Network Hardware
At a Glance
The final step in implementing a communication network is to associate a logic network with a network module, Modbus Plus card or Fipway card. Although the screens differ, the procedure is the same for each network device.
How to Associate a Logic Network
The following table describes how to associate a logic network to a network device declared in the hardware configuration editor.
Step
1
2
3
Action
Open the hardware configuration editor.
Right-click the device (Ethernet module, Fipway PCMCIA card or Modbus Plus
PCMCIA card) that you wish to associate with a logical network.
Select the channel and function.
Result: For a TSX ETY 4103 module:
114
35010500 12/2018
Step
4
Network Configuration
Action
In the Network link field, select the network to be associated with the card.
Result:
5 Confirm your choice and close the window.
Result: The logic network is associated with the device. The icon associated with this logic network changes and indicates the existence of a link with a PLC.
Furthermore, the rack, module and channel numbers are updated in the logic network configuration screen. In our example we obtain the following project browser:
35010500 12/2018
115
Network Configuration
116
35010500 12/2018
Communication Services and Architectures
Bus Configuration
35010500 12/2018
Bus Configuration
Chapter 13
Bus Configuration
Subject of this Chapter
This chapter describes how to access bus configuration tools.
What Is in This Chapter?
This chapter contains the following topics:
Topic
Creating and Accessing RIO\DIO Field Buses
Accessing Bus Configurations on PCMCIA and SCY 21601 Cards
Page
35010500 12/2018
117
Bus Configuration
Creating and Accessing RIO\DIO Field Buses
Introduction
Quantum PLCs offer a decentralized input/output architecture solution:
RIO field bus networks are based on the S908 input/output decentralization network technology.
Up to 31 decentralized stations may be configured, with each station capable of supporting up to 128 input/output words.
DIO field bus networks are based on Modbus Plus technology. 32 subscribers may be configured over 500 meters/1640 feet (receiving 64 subscribers over 2000 meters/6560 feet).
Creating a RIO Bus
The following table describes the procedure for creating a RIO bus from a communication module:
Step
1
2
3
Action
In the bus editor, select the slot where you wish to insert the communication module.
Select New Device in the contextual menu.
Result: The New Device window appears.
Expand the Communication directory.
Result: The following window appears:
118
35010500 12/2018
Step
4
Action
To create a RIO bus, select a 140 CRP 93x 00 module.
Result: The bus appears in the project browser:
Bus Configuration
Creating a DIO Bus
The following table describes the procedure for creating a DIO bus from a communication module:
Step
1
2
Action
In the bus editor, select the slot where you wish to insert the communication module.
Select New Device in the contextual menu.
Result: The New Device window appears.
35010500 12/2018
119
Bus Configuration
Step
3
Action
Expand the Communication directory.
Result: The following window appears:
4
5
6
7
To create a bus, select a 140 NOM 2XX 00 module.
Result: The module appears in the rack.
Double-click the 140 NOM 2XX 00 module’s Modbus Plus port.
Result: The bus configuration window appears.
Check the box marked DIO Bus.
Confirm the configuration.
Result: The DIO bus appears in the project browser.
120
35010500 12/2018
Bus Configuration
Creating a DIO Bus from the Processor
The following table describes the procedure for creating a DIO bus from the processor:
2
3
Step
1
Action
In the bus editor, double-click the processor’s Modbus Plus port.
Check the box marked DIO Bus.
Confirm the configuration.
Result: The DIO bus appears in the project browser:
35010500 12/2018
121
Bus Configuration
Accessing a RIO or DIO Bus
To access a bus, carry out the following actions:
Step
1
Action
In the project browser, open the
Example:
Configuration directory.
122
35010500 12/2018
Step
2
Action
Select the RIO bus or DIO bus subdirectory depending on the type of bus you want to open. Next, select the Open command in the popup menu.
Result: The following window is displayed for the RIO bus:
Bus Configuration
Result: The following window is displayed for the DIO bus:
35010500 12/2018
123
Bus Configuration
Accessing Bus Configurations on PCMCIA and SCY 21601 Cards
Introduction
For all communication buses other than those described before, configuration access is done via the hardware configuration of the module (TSX SCY 21601) or PCMCIA card concerned. The following pages describe how to create a new bus by declaring a PCMCIA card, and then how to access the bus configuration.
How to Create a New Communication Bus
The table below describes the actions to be taken to create a communication bus.
Step
1
Action
Double-click the slot of the PCMCIA card that is to manage the desired communication bus (in a
TSX SCY 21601 module or in a processor).
Result:
124
2 Select the type of bus management card desired.
Result: The communication bus is created. It must now be configured - to do so, follow the procedure described in the following paragraph.
35010500 12/2018
Bus Configuration
How to Configure a Communication Bus
The table below describes the actions to be taken to configure a communication bus:
Step
1
Action
Double-click the slot of the PCMCIA card that is to manage the desired communication bus.
Result: A window that resembles the following is displayed:.
35010500 12/2018
125
Bus Configuration
Step
2
Action
Select the channel and the desired function (for example, Modbus).
Result: A window that resembles the following is displayed. The bus must now be configured according to the project parameters:.
126
35010500 12/2018
Communication Services and Architectures
Configuration of X-Way Routing
35010500 12/2018
Configuration of X-Way Routing Premium Stations
Chapter 14
Configuration of X-Way Routing Premium Stations
Subject of this Chapter
This chapter presents the operating modes required for configuring X-Way routing Premium stations.
What Is in This Chapter?
This chapter contains the following topics:
Topic
Configuration
Configuration of Multi-Network Services
Configuring an X-Way Router Module
Examples of X-Way Routing Stations
Examples of Partial Routing
Page
35010500 12/2018
127
Configuration of X-Way Routing
Configuration
At a Glance
In an intermediate station, the management of several network couplers requires a configuration phase in order to distribute the functional characteristics to the various network entities.
128
NOTE: Multi-network routing information is constructed at the station level at the time of configuration of each bridge. No consistency check is done on routing data for the same network architecture.
35010500 12/2018
Configuration of X-Way Routing
Configuration of Multi-Network Services
At a Glance
In a station that supports various network modules, each network connection point is considered as an address for the station. When configuring each module, it is necessary to define the list of network numbers that are accessible for each connection point.
Depending on the processor selected during hardware configuration, a bridge station can only manage 3 or 4 network modules. The table will therefore have a maximum of 4 elements.
Illustration
A specific screen allows entry of routing data for all the network modules of a station.
35010500 12/2018
129
Configuration of X-Way Routing
Elements and Functions
The following table describes the various zones in the configuration screen:
2
3
Label
1
4
Field
Logical network
Network type
Accessible networks
Available networks
Function
Used to display the logical network name.
Used to display the network type.
Used:
for the unshaded Logical Network zone, to enter the list of
networks accessible by this module, for the shaded Logical Network zones, to display the list of networks accessible by these modules.
Used to select the networks accessible by a module configured as a bridge.
A list of numbers from 1 to 127 shows the networks available for a connection point. Each network number selected as being accessible is removed from the list of available networks in order to avoid configuration errors.
130
35010500 12/2018
Configuration of X-Way Routing
Configuring an X-Way Router Module
At a Glance
Before configuring the module as an X-Way router, the station’s logical networks must be created.
Procedure
The following procedure is used to access, and then configure the station’s module as an X-Way router.
Step
1
Action
Open the Communication tab in your project browser and in the Routing table tab, click the X-Way table tab.
Result: The following window appears.
35010500 12/2018
If the list of accessible module networks is empty, the window appears automatically (without double-clicking).
131
Configuration of X-Way Routing
Step
2
Action
Double-click the highlighted field in order to configure the first network.
Result: The Selection of accessible networks window appears.
3
4
5
6
Double-click the number of the required network from the Available networks scroll list.
Result: The network number is assigned in the Access networks scroll list.
Perform operation 3 as many times as necessary to define all the networks accessible by the module.
Once finished, proceed to step 5.
Confirm the selection by clicking OK.
Confirm the configuration of the X-Way router by closing the window or clicking the Enable button in the toolbar.
132
35010500 12/2018
Removing the Bridge Function
It is possible to remove the bridge function from the module.
Step
1
Action
Access the following X-Way window.
Configuration of X-Way Routing
2
3
Click Delete network list.
Confirm the configuration
35010500 12/2018
133
Configuration of X-Way Routing
Removing Access to a Network
It is possible to remove access to a single network.
Step
1
Action
Access the following X-Way window of the accessible networks.
134
2
3
4
Double-click the numbers of the accessible networks to be removed (left column).
Result: The network number is reassigned in the Available networks scroll list.
Confirm the selection by clicking OK.
Confirm the router configuration.
35010500 12/2018
Configuration of X-Way Routing
Examples of X-Way Routing Stations
At a Glance
Each station must be configured in order to define the list of accessible networks.
35010500 12/2018
135
Configuration of X-Way Routing
Configuration of Station R1
The module at slot 2 can only access network 12.
The module at slot 4 can only access network 1 and 11.
The module at slot 5 can access networks 13 and 21.
The bridge configuration of the station is therefore as follows:
Configuration of Station R2
The module at slot 0 can only access network 11.
The module at slot 5 can access networks 1, 12, 13 and 21.
The bridge configuration of the station is therefore as follows:
136
35010500 12/2018
Configuration of Station R3
The module at slot 0 can access networks 13, 12, 1 and 11.
The module at slot 5 can only access network 21.
The bridge configuration of the station is therefore as follows:
Configuration of X-Way Routing
Messaging
To use the communication function (see EcoStruxure™ Control Expert, Communication, Block
Library) such as Read_VAR for ethernet exchange between stations, configure the TCP/IP
Messaging in the Ethernet network configuration (see Premium and Atrium Using EcoStruxure™
Control Expert, Ethernet Network Modules, User Manual) screen. In the Messaging tab, for each exchange set the IP address and target XWay address.
For example if station R3 needs to communicate with station B, in R1Messaging tab:
set the R2 IP address (139.255.255.4) in the field IP address, and set the B XWay address (11.4) in the field XWay address.
The following illustration shows the R1 Messaging tab:
For another example if station B needs to communicate with station A, in R2, Messaging tab:
set the R1 IP address (139.255.255.5) in the field IP address, and set the A XWay address (21.7) in the field XWay address.
35010500 12/2018
137
Configuration of X-Way Routing
The following illustration shows the R2 Messaging tab:
138
35010500 12/2018
Configuration of X-Way Routing
Examples of Partial Routing
At a Glance
When configuring a module as a bridge, it is possible to assign to it only a part of the available networks, instead of all of them. This selection is used to define a partial routing.
Illustration
Each station must be configured in order to define the list of accessible networks.
Configuration of Station R1
The module at slot 2 is not involved in the routing of data.
The module at slot 4 can access networks #1 and #11.
The module at slot 5 can access networks #13 and #21.
35010500 12/2018
139
Configuration of X-Way Routing
The bridge configuration of the station is therefore as follows:
Configuration of Station R2
The module at slot 0 can only access network #11.
The module at slot 5 can access networks #1, #13 and #21. Network #12 is inaccessible.
The bridge configuration of the station is therefore as follows:
Configuration of Station R3
The module at slot 0 can access networks #13, #1 and #11. Network #12 is no longer accessible.
The module at slot 5 can only access network #21.
The bridge configuration of the station is therefore as follows:
140
35010500 12/2018
Communication Services and Architectures
Debugging
35010500 12/2018
Debugging
Chapter 15
Debugging
Description of the Communication Debug Screens
At a Glance
The debug screen dedicated to the application-specific communication function is accessible via the Debug tab. It has two distinct sections:
The top left section, which is in all types of debug screens, is dedicated to module and communication channel information.
The bottom right section is dedicated to debugging data and parameters. This area, which is specific to the type of communication chosen, is detailed in the documentation relating to the various types of communication.
Accessing the Screen
It is only possible to access debug mode in online mode.
Step
1
2
Action
Access the configuration screen
Select Debug mode by clicking the corresponding tab.
35010500 12/2018
141
Debugging
Illustration
This area is used to access diagnostics for a communication channel.
142
35010500 12/2018
Description
The table below shows the different elements of the debug screen and their functions.
Label
1
2
3
4
5
Element
Tabs
Function
The tab in the foreground indicates the mode in progress (Debug for this example). You can select each mode by clicking the corresponding tab. The modes available are:
Debug (accessible only in online mode),
Diagnostic (accessible only in online mode),
Configuration,
Settings.
Module area This area displays the abbreviated module indicator.
There are three indicators that provide the module’s status in online mode:
RUN indicates the module’s operating status,
ERR indicates an internal fault in the module,
I/O indicates a fault from outside the module, or an application fault.
Channel area
General parameters area
Mode parameters area
This area is used to select the channel to be debugged:
Channel: module channel number. To the left of the symbol there is a copy of the CHx channel LED.
This area shows the communication channel parameters:
Function: shows the configured communication function. This
information cannot be modified.
Task: shows the task (configured MAST). This information cannot be modified.
This area contains the parameters of the mode selected by the tab.
NOTE: All unavailable LEDs and commands appear in gray.
Debugging
35010500 12/2018
143
Debugging
144
35010500 12/2018
Communication Services and Architectures
Entry Help
35010500 12/2018
Communication Function Programming and Entry Help
Chapter 16
Communication Function Programming and Entry Help
Subject of this Chapter
This chapter presents the various entry help tools.
What Is in This Chapter?
This chapter contains the following topics:
Topic
Communication Function Entry Help
Access a specific instruction of the function, function block or DFB type
Address Entry Help
Page
35010500 12/2018
145
Entry Help
Communication Function Entry Help
At a Glance
During programming you can access an entry help screen allowing you to find out all the parameters of a communication function.
This help can be obtained from the Control Expert library functions.
Illustration
The following illustration shows the entry help screen for the communication function READ_VAR .
NOTE: The number and type of fields vary according to the communication function selected.
Availability
This screen is available for the following communication functions:
DATA_EXCH
INPUT_CHAR
OUT_IN_CHAR
PRINT_CHAR
READ_VAR
SEND_REQ
SEND_TLG
WRITE_VAR
146
35010500 12/2018
Entry Help
Access a specific instruction of the function, function block or DFB type
At a Glance
The application-specific function may be accessed:
by direct entry of the instruction and its parameters in an operate block via the entry help function accessible in the program editors (FBD, LD, IL, ST).
Calling a Function
The following table describes how to call a function.
Step
1
2
Action
Access the required editor.
Depending on the editor, select one of the following methods to open the function library:
Select the function to enter with the data editor. Once in the editor, right-click on the function (LD, FBD
editors).
Right-click in the program editor and select the option FFB Input Assistant.
Note: The function input assistant window appears:
3
4
35010500 12/2018
Select the type of FFB required (if it is not already entered).
Then select the name of the instance (where necessary and if available).
147
Entry Help
Step
5
6
7
Action
Many instructions have a customized entry help screen. You can access this screen by clicking the
Special Assistant button.
Enter each parameter of the instruction (each instruction is explained in the relevant application-specific documentation):
in the customized detailed data entry screen, or in the Prototype area of the Entry field.
Confirm by clicking Ok.
148
35010500 12/2018
Entry Help
Address Entry Help
At a Glance
To assist in entering the address, a help screen is available.
With this screen, a description of the architecture in which the communication function is integrated and generated can be added. By completing the fields of this description, the address is automatically generated.
Accessing the Help
When entering the parameters of the communication function, you can access the address entry help with the following button:
Illustration
The following illustration shows the address input help screen for a communication function.
Mode
The first parameter to select is the Mode. With it you can select one of the following communication modes:
local (communication by bus) remote (communication by network)
35010500 12/2018
149
Entry Help
Network Level
For remote communications only, the network level is used to:
enter the network number, enter the station number, select the station type.
Station Level
Depending on the communication function, with this parameter the type of exchange can be selected:
The Application box selects an exchange with a PL7 application (corresponds to APP addressing).
The System box selects the PLC system of the station designated by the network level
(corresponds to SYS addressing).
The Module box means that the destination device is connected to the station via a link (Uni-
Telway, Modbus, Modbus Plus or Fipio). This case requires you to specify:
the position of the module supporting this link, the type of this module.
Protocol
The Protocol field defines the exchange protocol used between the station on the network and the exchange’s destination device.
Device Level
This parameter is used to specify:
the type of destination device, the address of this device.
Limitations
In the address entry help screen, communications from a Uni-Telway slave require coding of the destination address in the transmission buffer (see EcoStruxure™ Control Expert,
Communication, Block Library) .
The help window allows full entry of the section corresponding to ADDR() advising the user that the additional buffer must be coded.
Remote station address coding is only supported by the following devices: TSX 17, TSX 37,
TSX 47-107, TSX 57.
For third-party devices, only entry of the port number is proposed. In other cases the address must be entered manually.
150
35010500 12/2018
Communication Services and Architectures
Index
35010500 12/2018
Index
A
addressing,
ALL,
APP,
IP,
Premium,
Modbus Plus,
Modicon M340,
B
broadcast
Modicon M340,
Premium,
C
Communication
Entry help,
configuring field buses, configuring networks,
D
Debug screen,
E
Entry help,
G
35010500 12/2018
I
IO Scanning,
M
messaging,
P
Peer Cop,
S
SYS,
T
X
X-Way message routing,
151
Index
152
35010500 12/2018
Download
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement
