Modicon M340 Using Unity

Pro S
Architectures and Communication
Services
Reference Manual
07/2008 eng
35013341.02

www.schneider-electric.com
2
 Table of Contents

Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Part I Introduction to the Communication Application. . . . . . . 9

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Introduction to the Application-Specific Communication Function . . . . . . . . . . . 12
Summary of Communication Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2 Services Available on Networks and Buses . . . . . . . . . . . . . . 15

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1 Global Data Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Global Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2 IO Scanning Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Description of the IO Scanning Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.3 Messaging Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Messaging Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Characteristics of the Messaging Service Communication Functions. . . . . . . . . 25

Chapter 3 Communication Architectures . . . . . . . . . . . . . . . . . . . . . . . . . 27

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Global Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Preferred Network Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Communication with the Installed Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 4 Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
List of Modbus Function Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Part II Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

35013341.02 07/2008 3
 Chapter 5 General Points Concerning Addressing . . . . . . . . . . . . . . . . . 37
At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Chapter 6 IP Addressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Reminder about IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 7 Modicon M340 PLCs Addressing . . . . . . . . . . . . . . . . . . . . . . . 43

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Modicon M340 Types of Communication Entities . . . . . . . . . . . . . . . . . . . . . . . . 44
Modicon M340 Addressing for a Communication Entity . . . . . . . . . . . . . . . . . . . 45
Processor Communication Channels Addressing . . . . . . . . . . . . . . . . . . . . . . . . 48
Example of Modicon M340 Ethernet Addressing. . . . . . . . . . . . . . . . . . . . . . . . . 50
Example of Modicon M340 CANopen Addressing. . . . . . . . . . . . . . . . . . . . . . . . 51
Examples of Modicon M340 Modbus and Character Mode Addressing . . . . . . . 52
Examples of Modicon M340 Communication EFs Addressing . . . . . . . . . . . . . . 55

Chapter 8 General points concerning bridging . . . . . . . . . . . . . . . . . . . . 57

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Bridging Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Bridging Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Part III Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 9 Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

At a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Network Configuration Principle Using Unity Pro . . . . . . . . . . . . . . . . . . . . . . . . 66
Creating a Logic Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Configuring a Logic Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Associating a Logic Network with Network Hardware . . . . . . . . . . . . . . . . . . . . . 70

Chapter 10 Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Description of the Communication Debug Screens . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 11 Communication Function Programming and Entry Help . . . . 75

How to Access a Function, Function Block or DFB-Type Specific Instruction . . . 75

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

4 35013341.02 07/2008
 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, 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.

The addition of this symbol to a Danger or Warning safety label indicates

that an electrical hazard exists, which will result in personal injury if the
instructions are not followed.

This is the safety alert symbol. It is used to alert you to potential personal
injury hazards. Obey all safety messages that follow this symbol to avoid
possible injury or death.

DANGER
DANGER indicates an imminently hazardous situation, which, if not avoided, will
result in death or serious injury.

WARNING
WARNING indicates a potentially hazardous situation, which, if not avoided, can result
in death, serious injury, or equipment damage.

CAUTION
CAUTION indicates a potentially hazardous situation, which, if not avoided, can result
in injury or equipment damage.

35013341.02 07/2008 5
Safety Information

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.
© 2008 Schneider Electric. All Rights Reserved.

6 35013341.02 07/2008
 About the Book

At a Glance

Document Scope This manual presents the architectures and communication services associated
with Schneider PLCs programmed using Unity Pro S.

Validity Note The data and illustrations found in this documentation are not binding. We reserve
the right to modify our products in line with our policy of continuous product
development.
The information in this document is subject to change without notice and should not
be construed as a commitment by Schneider Electric.

Product Related Schneider Electric assumes no responsibility for any errors that may appear in this
Warnings document. If you have any suggestions for improvements or amendments or have
found errors in this publication, please notify us.
No part of this document may be reproduced in any form or by any means, electronic
or mechanical, including photocopying, without express written permission of
Schneider Electric.
All pertinent state, regional, and local safety regulations must be observed when
installing and using this product.
For reasons of safety and to ensure compliance with documented system data, only
the manufacturer should perform repairs to components.
When controllers are used for applications with technical safety requirements,
please follow the relevant instructions.
Failure to observe this product related warning can result in injury or equipment
damage.

User Comments We welcome your comments about this document. You can reach us by e-mail at
techpub@schneider-electric.com

35013341.02 07/2008 7
About the Book

8 35013341.02 07/2008
 Introduction to the
Communication Application
I
At a Glance

Subject of this This part gives an overview of the communication application: the types of networks
Part and buses, services and architectures available.

What's in this This part contains the following chapters:

Part?
Chapter Chapter Name Page
1 General 11
2 Services Available on Networks and Buses 15
3 Communication Architectures 27
4 Interoperability 33

35013341.02 07/2008 9
Introduction

10 35013341.02 07/2008
 General

1
At a Glance

Subject of this This chapter gives an overview of the different characteristics of the communication
Chapter application.

What's in this This chapter contains the following topics:

Chapter?
Topic Page
Introduction to the Application-Specific Communication Function 12
Summary of Communication Solutions 14

35013341.02 07/2008 11
General

Introduction to the Application-Specific Communication Function

At a Glance The application-specific communication function makes it possible to exchange data

between different devices connected to a bus or a network.
This function applies to:
z Processors with an Ethernet, a built-in Fipio or a CANopen link,
z Specific rack-mounted communication modules,
z The terminal port of a processor,
z PCMCIA cards of a rack-mounted processor or module.

Communication The different types of communication are:

Types z Ethernet TCP/IP or Ethway Network
z Fipway Network
z Modbus Plus Network
z Fipio bus (manager and agent)
z Uni-Telway bus
z Modbus/JBus bus
z Character mode serial link
z CANopen field bus
z Interbus field bus
z Profibus field bus
z USB-standard fast terminal port

12 35013341.02 07/2008
 General

Available The available services can be classified into three categories:

Services z Explicit messaging (see Messaging Service, p. 23) services:
z Modbus messaging
z UNI-TE messaging
z Telegrams
z Implicit database access services:
z Global data (See Modicon M340, Premium, Atrium and Quantum Using Unity
Pro, Communication Services and Architectures, Global Data Service),
z Common words (See Modicon M340, Premium, Atrium and Quantum Using
Unity Pro, Communication Services and Architectures, Fipway Common
Words and Shared Tables),
z Shared tables (See Modicon M340, Premium, Atrium and Quantum Using
Unity Pro, Communication Services and Architectures, Fipway Common
Words and Shared Tables).
z Implicit Input/Output management services:
z I/O scanning (See Modicon M340, Premium, Atrium and Quantum Using Unity
Pro, Communication Services and Architectures, IO Scanning Service),
z Peer cop (See Modicon M340, Premium, Atrium and Quantum Using Unity
Pro, Communication Services and Architectures, Peer Cop Service).

Characteristics The following table gives an overview of the main characteristics of the types of
of the Different services mentioned above:
Service Types
Type of service These services make it They are used...
possible...
Messaging services for a device (Client) to send a to access data from time to
message to another device time.
(Server) and obtain a
response without having to
program anything into the
server device.
Implicit database access to share data which is to synchronize applications or
services refreshed automatically and on to transparently obtain real
a regular basis. time images of a system on
several remote PLCs.
Implicit I/O management to transparently and to monitor a set of distributed
services automatically manage remote systems across a network.
I/Os on a network.

35013341.02 07/2008 13
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 Modicon
M340, Premium, Atrium and Quantum Using Unity Pro, Communication Services
and Architectures, Characteristics of the Messaging Service Communication
Functions).

Summary The following table gives an overview of the different services available according to
the types of communication:
Function Fipway Fipio Uni- Character Modbus Modbus Ethway TCP/IP CANopen USB
Telway mode /JBus Plus
Messaging services
Communication The communication functions that can be used depend closely on the type of communication for
functions which they are applied (See Modicon M340, Premium, Atrium and Quantum Using Unity Pro,
Communication Services and Architectures, Characteristics of the Messaging Service
Communication Functions).
Implicit database access services
Global Data - - - - - - - X - -
Common words X - - - - - X - - -
Shared tables X - - - - - X - - -
Implicit I/O management services
I/O Scanning - - - - - - - X - -
Peer cop - - - - - X - - - -
Other - X - - - X - - X -

Legend:
X Yes
- No

14 35013341.02 07/2008
 Services Available on Networks
and Buses
2
At a Glance

Subject of this This section describes the main services available on the communication buses and
Section networks.

What's in this This chapter contains the following sections:

Chapter?
Section Topic Page
2.1 Global Data Service 16
2.2 IO Scanning Service 19
2.3 Messaging Service 23

35013341.02 07/2008 15
Services

2.1 Global Data Service

Global Data

Introduction Global Data, which is supported by the BMX NOE 0100 module, provides an
automatic data exchange for the coordination of PLC applications.

Note: Global Data is not supported by the Ethernet port of BMX P34 20•• CPUs.

Global Data Key features of Global Data:

z Data exchanges are based on a standard producer/consumer protocol, giving
optimal performance while maintaining a minimum network load.
z The Global Data service provides real-time exchanges between stations in the
same distribution group, which share variables used for PLC coordination.
z Global Data can synchronize remote applications or share a common database
among several distributed applications.
z A maximum of 64 stations can participate in Global Data within the same
distribution group.

Operation An application variable is a group of contiguous words from a PLC. Communication

module stations can publish or subscribe to application variables:
z publish: Communication modules can publish one 1024-byte local application
variable for other communication modules in the time-based distribution group.
The publication period can be configured from 10 ms to 15000 ms (in 10 ms
increments).
z subscribe: A communication module can subscribe to between 1 and 64
application variables that are published by other modules in their distribution
group, regardless of their location. The validity for each variable is controlled by
health status bits, linked to a refresh timeout configurable between 50 ms and
15 s (15000 ms). Access to a variable element is not possible. The maximum size
of the subscribed variables is 4 Kbytes.
Through Global Data configuration you can define:
z the number of valid published and subscribed variables
z the group with which these variables are associated for the communications
module

16 35013341.02 07/2008
 Services

Once the module is configured, exchanges between the communication modules

sharing the same Distribution Group are automatically carried out when the PLC is
in RUN mode.
Distribution Group
IP multicast: 239 255 255 251
Data distribution

Intranet control

2...n stations

Data distribution

Distribution Group
IP multicast: 239 255 255 250
A distribution group is a group of communication modules identified by the same
multicast IP address. Multicast exchanges (see Modicon M340 for Ethernet,
Communications Modules and Processors: Multicasting Considerations) distribute
Global Data. Several independent distribution groups can co-exist on the same
subnetwork with different multicast addresses.
Important points:
z A publish/subscribe protocol on UDP/IP is used for data distribution.
z The content of the publication variable is synchronized during the out section of
the MAST task.
z The content of the subscribed variables are copied to the PLC application
memory during the in section of the MAST task.
z The PLC memory zones that receive the various subscription variables should
not overlap. Do not use these variables for any other purpose.

Health Bits A health bit (status bit) is associated with each application variable.
This bit indicates the validity of each subscription variable. It is 1 if the variable has
been published and the subscriber has received it in the configured validity time.
Otherwise, it is 0.

Multicast Global Data uses multicast addressing. In accordance with the nature of broadcast
Filtering messages, the multicast frames transmitted by a module are repeated on all switch
ports, generating network congestion.

35013341.02 07/2008 17
Services

When the switches possess this function, multicast filtering allows multicast frame
spreading to be limited to only the ports that require it.
The GMRP protocol establishes the list of ports involved in data traffic.

Operating Modes The operating modes are as follows:

z Stopping the PLC stops Global Data exchanges.
z The use of the I/O forcing system bits (%S9, %SW8, %SW9) does not stop Global
Data exchanges.

Limits There are no theoretical limits for the number of stations that share a distribution
group. There is a limit on the number of variables (64) that can be exchanged within
the distribution group.

Note: We recommend that you use fewer than 200 modules in any single
distribution group.

18 35013341.02 07/2008
 Services

2.2 IO Scanning Service

Description of the IO Scanning Service

At a Glance The I/O Scanner is used to periodically:

z reads remote inputs
z writes remote outputs
z reads/writes remote outputs

The I/O Scanner is used to periodically read or write remote inputs and outputs on
the Ethernet network without specific programming.
Configure the I/O Scanner with Unity Pro (see Modicon M340 for Ethernet,
Communications Modules and Processors: I/O Scanner Configuration Parameters).

Note: I/O scanning is not supported by the Ethernet port of BMX P34 20•• CPUs.

Characteristics This service comprises the following essential elements:

z read zone: the values of remote inputs
z write zone: the values of remote outputs
z scanning periods: independent of the PLC cycle and specific to each remote
device
During operation, the module:
z manages the TCP/IP connections with each remote device
z scans inputs and copies their values into the configured %MW word zone
z scans outputs and copies their values from the configured %MW word zone
z reports status words so that correct operation of the service can be monitored by
the PLC application
z applies the preconfigured fallback values (in the event of a communication
problem)
z enables or disables each entry in the I/O scanner table in accordance with its
application

35013341.02 07/2008 19
Services

Recommended Scanning is performed only when the PLC is in Run mode.

Use This service operates with all devices that support Modbus TCP/IP server mode.
The exchange mechanism, which is transparent to the user, is executed with these
request types (as long as the remote devices support them):
z read
z write
z read and write

20 35013341.02 07/2008
 Services

I/O Scanner This figure illustrates the scanning of remote inputs and outputs:
Operation Application Memory

Read zone

Write zone

Device
input
words

Device
output
words
1 As soon as the PLC switches to Run mode, the module successfully opens a connection
for each scanned device. (One connection is made for each line entered in the table of
scanned devices.)
2 Then the module periodically reads input words and reads/writes output words for each
device.
3 If the PLC switches to Stop mode, the connections to all devices are closed.

35013341.02 07/2008 21
Services

Summary of The I/O scanning service:

Functionality z manages the connection with each remote device (one connection per remote
device)
z scans the inputs/outputs of the device using Modbus read/write requests on the
TCP/IP server mode.
z updates the read and write zones in the application memory
z refreshes the status bits for each remote device
Each I/O Scanner device can be enabled/disabled (see Modicon M340 for Ethernet,
Communications Modules and Processors: I/O Scanner: Device Control Block).

Note: These status bits show whether the module's input/output words have been
refreshed.

22 35013341.02 07/2008
 Services

2.3 Messaging Service

At a Glance

Subject of this This section gives an overview of the messaging service available on Schneider
Section PLCs.

What's in this This section contains the following topics:

Section?
Topic Page
Messaging Service 24
Characteristics of the Messaging Service Communication Functions 25

35013341.02 07/2008 23
Services

Messaging Service

At a Glance The messaging service makes it possible to perform inter-PLC data exchanges
using communication functions.
The standard type of messaging is used on Modicon M340 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 guarantee compatibility of communication
between Modicon M340 PLCs and the other platforms.

Synchronous/ A communication function is said to be synchronous when it is wholly executed

Asynchronous during the PLC task which activated it.
Communication A communication function is said to be asynchronous when it is executed during one
or more PLC tasks after the one which activated it.

24 35013341.02 07/2008
 Services

Characteristics of the Messaging Service Communication Functions

At a Glance These functions (see Unity Pro 3.1, Communication: Extended) enable
communication between one device and another. Certain functions are common to
several types of communication channel. Others may be specific to one
communication function.

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 totally synchronous with the execution of the activation task.

Note: It is recommended that asynchronous functions be triggered on edge and

not on state so as to avoid sending several identical requests in quick succession,
thus saturating the communication buffers.

Communication The following table gives an overview of Modicon M340 communication functions:
Functions on
Function Its role is...
Modicon M340
ADDM To convert a character string into an address that can be used
directly by the communication functions READ_VAR,
WRITE_VAR, INPUT_CHAR and PRINT_CHAR.
INPUT_BYTE To send an array of read request bytes.
READ_VAR To read standard language objects: words and bits using UNI-
TE or Modbus.
WRITE_VAR To write standard language objects: words and bits using UNI-
TE or Modbus.
PRINT_CHAR To write a character string.
INPUT_CHAR To read a character string.

35013341.02 07/2008 25
Services

Availability of The following table lists the protocols that support the communication functions:
Functions
Function Uni-Telway Character Modbus Ethernet CANopen
According to
mode TCP/IP
Protocols
Modicon M340
READ_VAR X X X X X
WRITE_VAR X X X X X
ADDM X X X X X
INPUT_BYTE - X - - -
PRINT_CHAR - X - - -
INPUT_CHAR - X - - -
Legend:
X Yes
- No

26 35013341.02 07/2008
 Communication Architectures

3
At a Glance

Subject of this This chapter gives an overview of the different communication architectures.
Chapter

What's in this This chapter contains the following topics:

Chapter?
Topic Page
Global Architecture 28
Preferred Network Architecture 30
Communication with the Installed Base 31

35013341.02 07/2008 27
Communication Architectures

Global Architecture

At a Glance Schneider has a communications strategy based on open standards (core of the
range) such as:
z Ethernet Modbus TCP/IP
z CANOpen
z Modbus Link series
The possible and recommended communication architectures are presented in the
following pages, according to the type of PLC used:
z At level 2: Inter-PLC network,
z At level 1: Field Bus.
The communication solutions for existing installations, from the Télémécanique or
Modicon ranges, are then presented.

Network The network architectures available for Modicon M340 PLCs are summarized
Architecture below:

Ethernet TCP/IP
Modicon M340

28 35013341.02 07/2008
 Communication Architectures

Field Bus The field bus architectures available for Modicon M340, Premium and Quantum
Architecture PLCs are summarized below:

Modicon M340

Ethernet
I/O Scanning

CANopen

Modbus

Legend:

Core of the range

(recommended)

35013341.02 07/2008 29
Communication Architectures

Preferred Network Architecture

At a Glance The Ethernet network architecture presented below is Schneider’s so-called

preferred solution.
A B C

Modbus TCP 0 0

Ethernet
Modbus TCP / Global Data

Web access

Modicon M340

Main services:
z Global Data: inter-PLC synchronization.
z Modbus TCP/IP: client/server device for accessing automation variables.
z Web Access: access to the variables and diagnostics from a standard
workstation.
Depending on the type of device, other services may also operate simultaneously:
z SMTP: e-mail
z MTP: time distribution
z SNMP: network management
z FDR: faulty device replacement

IP Routers As PLCs do not have IP routers, standard routers must be used to connect two
Ethernet TCP/IP networks. The following diagram shows the communication
between two Ethernet networks:

Ethernet TCP/IP 1

Modbus TCP Router

Ethernet TCP/IP 2

30 35013341.02 07/2008
 Communication Architectures

Communication with the Installed Base

Télémécanique The Ethway, Xip, Fipway, Uni-telway and Fipio installed bases use the
Architecture Télémécanique Uni-te private messaging protocol on a network layer called X-way.
This layer guarantees transparent routing of Uni-te messages between each of
these networks. Only Premium and Micro PLCs support this protocol.
In the architecture below, transparency may be achieved by configuring the
Premium 2 PLC as a Bridge, and provided the Premium 1 PLC or the Unity terminal
uses the Xip protocol (X-way on TCP/IP).

Premium 1
Modbus TCP
Ethernet TCP/IP

X-way TCP

ETZ
Premium 2 ETG Micro

X-way TCP Ethway or Xip

Premium Series 7 S1000

Fipway

Premium Micro

35013341.02 07/2008 31
Communication Architectures

Modicon The Modicon installed base uses the standard Modbus protocol on serial link or
Architecture token bus.
It is not possible to perform routing using this protocol.
This is, however, possible using gateways or bridges.

Premium Quantum Modicon M340

Ethernet TCP/IP

Modbus TCP

Momentum Ethernet/Modbus Bridge Ethernet/Modbus plus

M1E 174 CEV 300 10

Modbus TCP

Modbus Plus

Quantum 984 Compact

Modbus

984

32 35013341.02 07/2008
 Interoperability

4
List of Modbus Function Codes

At a Glance M340 PLCs have communication server kernels that accept the common Modbus
function codes. These are listed in the table on this page.
As servers, 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.

List of Modbus The following table lists the function codes and the address of the Modbus function
Requests codes, recognized by M340 platform:
Recognized
Function M340 memory Meaning
When Connected
code address
as a Server
1 %M Read output bits
2 %M Read input bits
3 %MW Read consecutive integer values
4 %MW Read consecutive input integer values
5 %M Write single output bit
6 %MW Write single integer value
15 %M Write n output bits
16 %MW Write consecutive integer values
23 %MW Read/write consecutive integer values

35013341.02 07/2008 33
Interoperability

Use of Modbus The table below lists the Modbus function codes and their use as a client on M340
Function Codes PLCs:
as a Client on
Function M340 Modbus request Communication
M340
code memory function
address
1 %M Read output bits READ_VAR
2 %I Read input bits READ_VAR
3 %MW Read consecutive integer values READ_VAR
4 %IW Read consecutive input integer values READ_VAR
15 %M Write n output bits WRITE_VAR
16 %MW Write consecutive integer values WRITE_VAR

The way in which to use function codes with communication functions is described
in the Modbus manual.

Note: Interoperability with Windows applications is provided in 2 ways:

z Access to the PLC variables can be easily achieved with OFS software.
z The application download function, import/export source format function and
access to operating modes (RUN/STOP/INIT) functions can be performed using
the UDE (Unity Development Edition) range.

WARNING
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 for more information.
Failure to follow this instruction can result in death, serious injury, or
equipment damage.

34 35013341.02 07/2008
 Addressing

II
At a Glance

Subject of this This part describes the different addressing solutions for devices on a
Part communication bus or network.

What's in this This part contains the following chapters:

Part?
Chapter Chapter Name Page
5 General Points Concerning Addressing 37
6 IP Addressing 39
7 Modicon M340 PLCs Addressing 43
8 General points concerning bridging 57

35013341.02 07/2008 35
Addressing

36 35013341.02 07/2008
 General Points Concerning
Addressing
5
At a Glance

Subject of this This chapter gives an overview of the different addressing solutions for devices in a
Chapter communication architecture.

What's in this This chapter contains the following sections:

Chapter?
Section Topic Page
5.1 General 38

35013341.02 07/2008 37
Introduction to Addressing

5.1 General

Description

At a Glance In 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.

Modicon M340 PLCs support 2 types of addressing depending on the type of

device, network or bus used:
z IP addressing (see IP Addressing, p. 39)
z Modicon M340 PLCs addressing (see Modicon M340 PLCs Addressing, p. 43)

38 35013341.02 07/2008
 IP Addressing

6
Reminder about 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:
z If the type of network environment is open, 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.
z 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.

35013341.02 07/2008 39
IP Addressing

Example Depending on the size of the network, three classes of address can be used:

7 bits 24 bits

Class A 0 Network ID Machine ID

14 bits 16 bits

Class B 1 0 Network ID Machine ID

21 bits 8 bits

Class C 1 1 0 Network ID Machine ID

Spaces reserved for the different classes of IP address:

Class Range
A 0.0.0.0 to 127.255.255.255
B 128.0.0.0 to 191.255.255.255
C 192.0.0.0 to 223.255.255.255

z Class A addresses are intended for large-scale networks which have a large
number of connected sites.
z Class B addresses are intended for medium-scale networks which have fewer
connected sites.
z Class C addresses are intended for small-scale networks which have a small
number of connected sites.

Sub-Addressing An IP address is composed of two identifiers, one identifies the network while the
and Subnet Mask other identifies the connected machine. In reality, the machine identifier can also
hold a subnet 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 outside world which still sees only one network, the one designated by the
network identifier.
The subnet mask makes it possible to see the number of bits attributed respectively
to the network identifier and to the subnet identifier (bits at 1), and then to the
machine identifier (bits at 0).

40 35013341.02 07/2008
 IP Addressing

Example Example: 140.186.90.3

16 bits 8 bits 8 bits

Class B Network identifier = 140.186 Sub-network Machine

identifier = 90 identifier = 3

Subnet mask
24 bits at 1 8 bits at 0

The segmentation allows for 254 possible sub-networks, each with 254 sub-network
machines.

The value of the subnet mask should be chosen so that it is consistent with the IP
address class.
The subnet mask will have the following value:
z For a class A address: 255.xxx.xxx.xxx
z For a class B address: 255.255.xxx.xxx
z For a class C address: 255.255.255.xxx
Where 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 manage the routing to
another gateway or towards its final destination.

35013341.02 07/2008 41
IP Addressing

42 35013341.02 07/2008
 Modicon M340 PLCs Addressing

7
At a Glance

Purpose of this This chapter describes Modicon M340 PLCs addressing and indicates its fields of
Chapter application.

What's in this This chapter contains the following topics:

Chapter?
Topic Page
Modicon M340 Types of Communication Entities 44
Modicon M340 Addressing for a Communication Entity 45
Processor Communication Channels Addressing 48
Example of Modicon M340 Ethernet Addressing 50
Example of Modicon M340 CANopen Addressing 51
Examples of Modicon M340 Modbus and Character Mode Addressing 52
Examples of Modicon M340 Communication EFs Addressing 55

35013341.02 07/2008 43
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:
z local addresses, identified by r.m.c.SYS, or more simply, r.m.c,
z remote addresses, to address a device (Modbus, CANopen or Ethernet) directly
connected to the channel,
z 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 Broadcast addresses depend on the destination devices:

Addresses
Destination Broadcast address
Broadcast to all Modbus slaves (the slave rack.module.channel.0
number equals 0)

44 35013341.02 07/2008
 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:
z Ethernet TCP/IP
z Modbus or CANopen
z 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:

z The target entity depends on the communication EF and is chosen implicitly:
z MBS for addressing a Modbus server,
z TCP.MBS for addressing a TCP Modbus server,
z SYS for addressing a channel server on Character mode. SYS can be
ommitted.
z The communication channel is explicit (processor’s or module’s position and
communication channel number) or symbolized with the Netlink name for
Ethernet communication.
z The node address depends on the communication protocol:
z IP address with Ethernet,
z node address with CANopen,
z slave address with Modbus.

35013341.02 07/2008 45
Modicon M340 PLCs Addressing

Addressing a The address of a station on Ethernet takes the form:

Station on a z ADDM(‘Netlink{hostAddr}’)
Ethernet z ADDM(‘Netlink{hostAddr}TCP.MBS’)
z ADDM(‘Netlink{hostAddr}node’)
z ADDM(‘r.m.c{hostAddr}’)
z ADDM(‘r.m.c{hostAddr}TCP.MBS’)
z ADDM(‘r.m.c{hostAddr}node’)
z ADDM(‘{hostAddr}’)
z ADDM(‘{hostAddr}TCP.MBS’)
z ADDM(‘{hostAddr}node’)
Where:
z Netlink: network name set in the Net Link field of Ethernet channel
z hostAddr: IP address of device
z r: rack number (rack)
z c: channel number (channel)
z 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 The address of a device on a CANopen bus takes the form ADDM(‘r.m.c.e’),
Device on a where:
CANopen Bus z r: rack number (rack)
z m: rack module position
z c: channel number (channel) of CANopen port (2)
z e: CANopen slave node (equipment) (range 1 to 127)

Addressing a The address of a device on a Modbus bus takes the form ADDM(‘r.m.c.e.MBS’),
Device on a where:
Modbus z r: rack number (rack)
z m: rack module position
z c: channel number (channel) of Modbus port (0)
z e: Modbus slave number (equipment) (range 1 to 247)

46 35013341.02 07/2008
 Modicon M340 PLCs Addressing

Addressing a To send or receive a character string, you can use ADDM(‘r.m.c’) or

Device on ADDM(‘r.m.c.SYS’), where:
Character mode z r: rack number (rack)
z m: rack module position
z c: channel number (channel) of Character mode port (0)
z SYS: keyword used to stipulate the station server system (see Modicon M340
Types of Communication Entities, p. 44). SYS can be ommitted.

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:
Network 20

Station 2 Station 3

Ad0 = 14

LEXIUM05

ADDM(‘0.0.2.14’)

35013341.02 07/2008 47
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 The available communication channels vary depending on the processor:

communication
Processor Integrated Integrated Integrated
channels
Modbus CANopen Master Ethernet
Connection Connection Connection
BMX P34 1000 X - -
BMX P34 2000 X - -
BMX P34 2010 X X -
BMX P34 2020 X - X
BMX P34 2030 - X X
Key
X Available
- Not available

48 35013341.02 07/2008
 Modicon M340 PLCs Addressing

Processor The diagram below shows an example of Modicon M340 configuration including a
Communication BMX P34 2010 processor and the addresses of the processor communication
Channels channels:
Addressing
PS 00 01 02 03 04 05 06 07

Rack 0. Module 0. Channel 0: Serial port

(available on BMX P34 1000/2000/2010/2020 processors)
Rack 0. Module 0. Channel 2: CANopen port
(available on BMX P34 2010/2030 processors)

The diagram below shows an example of Modicon M340 configuration including a

BMX P34 2030 processor and the addresses of the processor communication
channels:
PS 00 01 02 03 04 05 06 07

Rack 0. Module 0. Channel 3: Ethernet port

(available on BMX P34 2020/2030 processors)

Rack 0. Module 0. Channel 2: CANopen port

(available on BMX P34 2010/2030 processors)

35013341.02 07/2008 49
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 A device with the IP address 139.180.204.2 is connected to the Ethernet network. It
CPU Ethernet is the processor Ethernet port configured with Netlink name Ethernet_1.
port

hostAddr: 139.180.204.1
Ethernet
Netlink: Ethernet_1

hostAddr: 139.180.204.2
Station 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}’)

50 35013341.02 07/2008
 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 The syntax of CANopen addressing is ADDM (‘r.m.c.node’) . The meaning of

Rules the string parameter is as follows:
z r: rack address. The processor’s rack address is always 0.
z m: module address. The Modicon M340 processor’s slot number in the rack is
always 0.
z c: channel address. The Modicon M340 CANopen port is always channel 2.
z 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:

Master

CANopen

Slave address: 28

LEXIUM05

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.

35013341.02 07/2008 51
Modicon M340 PLCs Addressing

Examples of Modicon M340 Modbus and Character Mode Addressing

At a Glance The following examples deal with:

z Modbus addressing
z Character mode addressing.

Modbus The syntax of Modbus addressing is ADDM (’r.m.c.node’) . The meaning of the
Addressing string parameter is as follows:
Rules z r: rack address. The processor’s rack address is always 0.
z m: module address. The Modicon M340 processor’s slot number in the rack is
always 0.
z c: channel address. The Modicon M340 processor’s serial port is always
channel 0.
z 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 point-to-point serial communication.

52 35013341.02 07/2008
 Modicon M340 PLCs Addressing

Serial Link Using The diagram below shows two Modicon M340 processors connected via a serial link
Modbus Protocol and using Modbus protocol:

Modbus Master
BMX P34 2010 Processor

Modbus Slave
BMX P34 2010 Processor

The address settings of the slave processor number 8 are ADDM(’0.0.0.8’).

Character Mode The syntax of Character mode addressing is ADDM (’r.m.c’) or ADDM
Addressing (’r.m.c.SYS’) (SYS can be omitted). The meaning of the string parameter is as
Rules follows:
z r: rack address of the connected device.
z m: module address of the connected device.
z c: channel address of the connected device.
z SYS: keyword used to stipulate the station server system. SYS can be omitted.

35013341.02 07/2008 53
Modicon M340 PLCs Addressing

Serial Link Using The diagram below shows a Modicon M340 processor linked to a data entry/display
Character Mode terminal TM8501:
Protocol BMX P34 2010 Processor

TM8501 Terminal

The address settings of the TM8501 terminal are ADDM(’0.0.0’) or

ADDM(’0.0.0.SYS’).

54 35013341.02 07/2008
 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:

A Modicon M340
Configuration

Ethernet Network 1

IP router
Modicon M340
B Configuration

Premium
C
Configuration

Ethernet Network 2

Modicon M340 D
Configuration

In the diagram above there are the following configurations:

z Three Modicon M340 configurations called A, B and D
z One Premium configuration called C
All the configurations can communicate because of the following statements:
z A and B: communication between two Modicon M340 PLCs on an Ethernet
network is possible.
z A and C: communication between a Modicon M340 PLC and a Premium PLC is
possible on an Ethernet network.
z 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.

35013341.02 07/2008 55
Modicon M340 PLCs Addressing

Example 2 The second example is a multi-network configuration as follows:

A Modicon M340
Configuration

Ethernet Network 1

Gateway Gateway
Modicon M340
B Configuration
Modbus serial CANopen

Modbus serial
Modbus CANopen
device 2 device
Modbus
device 1

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’)

56 35013341.02 07/2008
 General points concerning
bridging
8
At a Glance

Subject of this This chapter gives an overview of the different bridging solutions for devices in a
Chapter communication architecture.

What's in this This chapter contains the following topics:

Chapter?
Topic Page
Bridging Description 58
Bridging Example 60

35013341.02 07/2008 57
Introduction to bridging

Bridging Description

At a Glance There are two available connection modes:

z Direct PLC access: Unity Pro connects directly to the PLC.
z Transparent PLC access or bridging: Unity Pro 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:
Set Address ?
PLC Simulator
Bandwidth...
Address Address
Test Connection
SYS 127.0.0.1
Media Media
USB TCPIP OK

Cancel
Communication Parameters Communication Parameters
Help

Direct PLC The available syntaxes for a direct PLC access are described below:
Access Syntax
Connection used Address
USB SYS or empty
Ethernet IP address: 139.169.3.4
Modbus Slave number

58 35013341.02 07/2008
 Introduction to bridging

Transparent PLC The bridging address string consists of two parts:

Access Syntax z First part: The "via address" (optional).
z 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 Remote PLC address
Modbus slave Link_address.Modbus Slave Number
Ethernet Link_address {IP address}
Ethernet device Link_address.UnitID

"Link_address" is a r.m.c-type topological address where:

z r: rack address.
z m: module address.
z c: channel address.
The "via address" is a classical address depending on the media:
Media Via address
Modbus slave Slave_nbr
USB SYS or empty
Ethernet IP address

Online Service The transparent PLC access or bridging offers:

Limitations of z full online services if the remote PLC is a Modicon M340 or a Quantum PLC.
Transparent PLC z restricted online services if the remote PLC is a Unity Premium PLC (not all
Access option module screens work).
z 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).

35013341.02 07/2008 59
Introduction to bridging

Bridging Example

At a glance The following pages present an example of PLC configurations bridging and its
transparent PLC adresses.

Bridging The following example consists of the following PLC configurations:

Example z Configuration 3: this Modicon M340 configuration consists of the following
communication modules:
z An Ethernet-Modbus processor with IP address 139.160.235.34 and Modbus
slave address 5. 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.
z 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.
z 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.
z 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.
z 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.

60 35013341.02 07/2008
 Introduction to bridging

This diagram presents the bridging example:

Configuration 1 Configuration 2

@IP 139.160.235.16
@IP 118.159.35.45

(2) (6)

Unity Pro Unity Pro

(5)
ETHERNET ETHERNET

@IP 139.160.235.34 @IP 118.159.35.2

(1)
USB (3)
Modbus CPU Configuration 3
slave number : 5
MODBUS
Unity Pro
(4)

Unity Pro

Configuration 4

Modbus CPU
slave number : 66

35013341.02 07/2008 61
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}
(2) processor’s Ethernet channel to remote PLC, which is linked to an 139.160.235.34\\0.5.0{118.159.35.45}
Ethernet module
(3) processor’s Modbus channel to remote PLC linked, which is linked to 5\\0.5.0{118.159.35.45}
an Ethernet module
(4) USB connection to remote PLC, which is linked to processor’s SYS\\0.0.0.66
Modbus channel
(5) Ethernet module connection to remote PLC, which is linked to 118.159.35.2\\0.0.0.66
processor’s Modbus channel
(6) Ethernet module connection to remote PLC, which is linked to 118.159.35.2\\0.0.3{139.160.235.16}
processor’s Ethernet channel

62 35013341.02 07/2008
 Operating Modes

III
At a Glance

Subject of this This part describes the operating modes associated with expert communication.
Part

What's in this This part contains the following chapters:

Part?
Chapter Chapter Name Page
9 Network Configuration 65
10 Debugging 73
11 Communication Function Programming and Entry Help 75

35013341.02 07/2008 63
Operating Modes

64 35013341.02 07/2008
 Network Configuration

9
At a Glance

Subject of this This chapter presents the tools for configuring a network at the global level and at
Chapter the station level.

What's in this This chapter contains the following topics:

Chapter?
Topic Page
Network Configuration Principle Using Unity Pro 66
Creating a Logic Network 67
Configuring a Logic Network 69
Associating a Logic Network with Network Hardware 70

35013341.02 07/2008 65
Network Configuration

Network Configuration Principle Using Unity Pro

At a Glance With Unity Pro, the installation of a network takes place using the project browser
and the hardware configuration editor.
The method involves the following four steps:
z Creation of a logic network,
z Configuration of the logic network,
z Declaration of the module,
z Association of the module with the logic network.
These four steps 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 to have the hardware to
start work) and use the simulator to test its operation.

Note: The first two steps are performed using the project browser and the next two
using the hardware configuration editor.

This manual introduces the method. For detailed information on how to configure the
various networks, please refer to the specific documentation:
z Ethernet configuration (see Modicon M340 for Ethernet, Communications
Modules and Processors: Ethernet Configuration with Unity Pro)

66 35013341.02 07/2008
 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 The following table describes how to create a network using the project browser.
Network
Step Action
1 Expand the Communication directory in the project browser.
Result:

Communication
Networks

2 Right-click in the Networks sub-directory and select the New network option.
Result:
Add network

Network Comment

List of available networks:

None selected

Change name:

OK Cancel Help

35013341.02 07/2008 67
Network Configuration

Step Action
3 Select the network that you wish to create from the list of available networks
and give it a meaningful name.
Result: Example of an Ethernet network.
Add network

Network Comment

List of available networks:

Ethernet

Change name:
Ethernet factory

OK Cancel Help

Note: You can also add a comment, if you so wish, by clicking on the
Comment tab.
4 Click OK and a new logic network is created.
Result: We have just created the Ethernet network that appears in the project
browser.

Communication
Networks
Ethernet factory

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.

68 35013341.02 07/2008
 Network Configuration

Configuring a Logic Network

At a Glance The second step in implementing a communication network consists of configuring

a logic network.
This manual introduces the access to network configuration. For further information
on configuring the various networks please refer to the specific documentation:
z Ethernet configuration (see Modicon M340 for Ethernet, Communications
Modules and Processors: Ethernet Configuration with Unity Pro)

Configuring a The table below describes how to access the configuration of a network using the
Logic Network project browser.
Step Action
1 In the project browser, expand the Networks sub-tab located in the
Communication tab of the tree directory to display all the networks of the
project.
Example:
Communication
Networks
Ethernet packaging
Ethernet factory

2 Double-click the network you wish to configure to obtain the network’s

configuration window.
Note: The windows differ according to the network family selected. However,
for all networks it is from this window that you can configure the Global Data,
IO scanning 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.

35013341.02 07/2008 69
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. Although the screens differ, the procedure is the
same for each network device.

How to Associate The following table describes how to associate a logic network to a network device
a Logic Network declared in the hardware configuration editor.
Step Action
1 Open the hardware configuration editor.
2 Right-click the device (Ethernet module) that you wish to associate with a
logical network.
3 Select the channel and function.
Result: For a BMX NOE 0100 module:
0.2: BMX NOE 0100

ETHERNET 1 Port 10/100 RJ45

BMX NOE 0100 Config

Channel 0

Function:
ETH TCP IP

Task:
MAST

Network link:
No link

70 35013341.02 07/2008
 Network Configuration

Step Action
4 In the Network link field, select the network to be associated with the module.
Result:
0.2: BMX NOE 0100

ETHERNET 1 Port 10/100 RJ45

BMX NOE 0100 Config

Channel 0

Function:
ETH TCP IP

Task:
MAST

Network link:
Ethernet_factory

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:
Communication
Networks
Ethernet_factory

35013341.02 07/2008 71
Network Configuration

72 35013341.02 07/2008
 Debugging

10
Description of the Communication Debug Screens

At a Glance The debug screen dedicated to the application-specific communication function may
be accessed via the Debug tab. It is broken down into two distinct sections:
z The top and left-hand part of the screen, common to all types of debug screen, is
dedicated to module and communication channel information.
z The right-hand part of the screen is dedicated to debugging data and parameters.
This area, specific to the type of communication selected, is detailed in the
documentation relating to the various types of communication.

How to Access The debug mode may only be accessed in online mode.
the Screen
Step Action
1 Access the configuration screen.
2 Select the Debug mode by clicking on the corresponding tab.

35013341.02 07/2008 73
Debugging

Illustration This area is used to access diagnostics for a communication channel.

Ethernet 1 Port 10/100 RJ45 Version: 1.0 1
Run Err. ADR

Config Debug Fault

BMX NOE 0100
Channel 0
Address information
2 Fom a MAC Address 00.00.00.00.00.00
server
IP Address 0 . 0 . 0 . 0
Subnetwork mask 0 . 0 . 0 . 0 4
Gateway Address 0 . 0 . 0 . 0

Messages
Open connections 0 Reset counters
Non-authorized 0
Messages refused 0 Ping
Messages received 0 IO Scanning
Bandwidth Not configured 16 1
Messages sent 0 Scanned 32 17
IO Scanning Unscanned 48 33
enabled Faulty or absent 64 49
Message traffic (msg./min)
2000 msg/sec
3 Global data
Function:
ETH TCP IP Not configured 16 1
SUB variable 32 17
Task: Global Data
MAST Default SUB 48 33
enabled PUB variable 64 49
Network link: Min. 0 Avg. 0 Max. 0 Reset
noe

Description The table below shows the various elements of the debug screen and their
functions.
Zone Function
1: Module module description zone
2: Channel channel selection zone
3: parameters general parameters zone
4: Debug tab Address z displays TCP/IP utility configuration
information z tests communication of the TCP/IP profile

Messages displays of the number of unacknowledged or refused messages

Message traffic displays the number of messages processed by the module per minute
IO Scanning display of the status for each remote input/output module
Global Data displays the status of Global Data variables

74 35013341.02 07/2008
 Communication Function
Programming and Entry Help
11
How to Access a Function, Function Block or DFB-Type Specific Instruction

At a Glance The application-specific function may be accessed:

z by direct entry of the instruction and its parameters in an operate block
z via the entry help function that may be accessed in the program editors
(FBD, LD, IL, ST).

35013341.02 07/2008 75
Entry Help

How to Call a
Function
Step Action
1 Access the required editor.
2 Depending on the editor, select one of the following methods to open the function library:
z Select the function to enter with the data editor. Once in the editor, right-click on the function (LD, FBD
editors).
z Right-click in the program editor and select the option FFB Input Assistant.

Note: The function entry help window appears.

Function Input Assistant

FFB Type: ...

Instance: ...

Prototype

Name Type No. Comment Entry field

Add pin Remove pin(s) Help on Type

Special Assistant OK Cancel Help

3 Select the type of FFB required (if it is not already entered).

4 Then select the name of the instance (where necessary and if available).
5 Enter each parameter of the instruction (each instruction is expanded upon in the relevant application-
specific documentation):
z In the Entry field field, in the Prototype area.

6 Validate with Ok.

76 35013341.02 07/2008
 Index
B
AC
A M
addressing messaging, 15
assistant, 75
IP, 39
Modicon M340, 43 T
architectures, 27 topologies, 27

B
brigde, 57
broadcast
Modicon M340, 44

C
configuring networks, 65

F
function codes
Modbus, 33

G
Global Data, 15

I
IO Scanning, 15

35013341.02 07/2008 77
Index

78 35013341.02 07/2008