Professional Documents
Culture Documents
Open Interfaces: User's Manual
Open Interfaces: User's Manual
Open Interfaces: User's Manual
Manual
Open Interfaces
IM 32S05B10-21E
IM 32S05B10-21E
3rd Edition
Introduction
This is the reference manual on engineering and maintenance for connecting ProSafe-RS with
other systems except CENTUM VP and CS 3000.
The manual consists of the following parts:
Part A
SOE OPC Interface
This part mainly explains specifications of the SOE OPC Interface of ProSafe-RS and
compatibility with the OPC specifications.
Part B
Modbus Slave Interface
This part explains the engineering and maintenance for connecting ProSafe-RS with other
systems via Modbus Slave Interfaces.
Part C
Common Items Regarding Subsystem Communication Interfaces
This part explains the engineering and maintenance for connecting ProSafe-RS with other
systems via Subsystem Communication Interfaces.
IM 32S05B10-21E
ii
Engineering
Guide
IM 32S01S10-21E
IM 32S01C10-21E
Software
Safety Control Station
Reference
IM 32S03B10-21E
Integration with
CENTUM VP/CS 3000
Open Interfaces
IM 32S01E10-21E
IM 32S05B10-21E
Engineering
Reference
Utilities and
Maintenance
Reference
IM 32S04B20-21E
Messages
IM 32S02B10-21E
Integration with
FAST/TOOLS
IM 32S04B10-21E
ProSafe-RS
System Test
Reference
IM 32S04B30-21E
IM 32S56H20-21E
Hardware
Vnet/IP
Safety Control
Stations
(Hardware)
IM 32S06C10-21E
Communication
Devices
ProSafe-RS
Vnet/IP
IM 32S06H10-21E
IM 32S56H10-21E
Installation
Installation
Manual
Software Help
IM 32S01C50-21E
Read Me First
IM 32S05B10-21E
iii
Safety Precautions
n Safety, Protection, and Modification of the Product
In order to protect system controlled by this product, the product itself and ensure safe
operation, observe the safety precautions described in this users manual. We assume no
liability for safety if users fail to observe these instructions when operating the product.
You must use this product according to the instructions described in user manuals. If not,
protective functions of this product may not work as expected.
If any protection or safety circuit is required for system controlled by the product or for the
product itself, prepare it separately.
Be sure to use the parts approved by Yokogawa Electric Corporation (hereafter simply
referred to as YOKOGAWA) when replacing parts or consumables.
Modification of the product is strictly prohibited.
The following symbols are used on the product and in this user manual to indicate that
safety precautions are required:
Indicates that user must take caution. The symbol on the equipment refers the user to the
relevant manual to avoid potentially hazardous situations that may result in injury or death.
The symbol appears next to the cautionary information in user manuals required to avoid
harm to personnel and to the equipment.
Indicates a protective grounding terminal. Before using the product, ground the terminal.
Indicates a functional grounding terminal. Before using the product, ground the terminal.
Indicates an AC supply.
Indicates a DC supply.
IM 32S05B10-21E
iv
n Notes on Handling User Manuals
Please hand over user manuals to your end users so that they can have them on hand for
convenient reference.
Please read the user manuals thoroughly before using the product.
The purpose of these user manuals is not to warrant that the product is well suited to any
particular purpose but rather to describe the functional details of the product.
YOKOGAWA reserves the right to make improvements in the user manuals and product at
any time, without notice or obligation.
If you have any questions, or you find mistakes or omissions in the user manuals, please
contact our sales representative or your local distributor.
n Notes on Software
YOKOGAWA makes no warranties, either expressed or implied, with respect to the
softwares merchantability or suitability for any particular purpose, except as specified in the
terms of warranty.
This software may be used on one machine only. If you need to use the software on another
machine, you must purchase another copy of the software.
It is strictly prohibited to reproduce the product except for the purpose of backup.
Store the CD-ROM (the original medium) in a safe place.
It is strictly prohibited to perform any reverse-engineering operation, such as reverse
compilation or reverse assembling on the product.
No part of the product may be transferred, converted or sublet for use by any third party,
without prior written consent from YOKOGAWA.
IM 32S05B10-21E
Documentation Conventions
n Typographical Conventions
The following typographical conventions are used throughout the user manuals:
FIC100.SV=50.0
Mark:
Indicates a space between character strings that must be entered.
Example: Calling the tuning view with the tag name of S0001 on HIS (Human Interface Station of
the integrated CENTUM).
S0001TUN
IM 32S05B10-21E
vi
n Symbol Marks
Throughout this user manual, you will find that several types of symbols are used to identify
different sections of text. This section describes these icons.
CAUTION:
Indicates instructions that must be observed in order to prevent physical injury and death of
operator.
WARNING :
Indicates instructions that must be observed in order to prevent software or hardware from
being damaged or system from becoming faulty.
IMPORTANT :
TIP:
SEE :
ALSO
Clicking a reference displayed in green can call up its source, while clicking a reference
displayed in black cannot.
n Drawing Conventions
Some drawings in the user manual may be partially emphasized, simplified, or omitted, for the
convenience of description.
Note that screen images in user manuals may be slightly different from the actual ones (for
example, display positions and case differences), and some show only example images.
SEE
ALSO
For information about the functions and usage of CENTUM VP components, see CENTUM VP Users
Manuals (IM) and related Technical Information (TI) and General Specifications (GS).
For information about the functions and usage of CENTUM CS 3000 components, see CENTUM CS 3000
Users Manuals (IM) and related Technical Information (TI) and General Specifications (GS).
IM 32S05B10-21E
vii
n About Explanation of System Behavior
In this manual, system behavior is explained assuming the use of the latest software and
hardware that Yokogawa provides at the publication of the manual. Wherever a topic needs
explanation of earlier revisions of software or hardware, a link to the required explanation is
provided so that you can read them according to your system.
SCSP1-S :
SCSP2-S :
To explain the functions of these different types of SCS, the following generic terms or
abbreviations may be used in this manual.
SCS
SCSV
SCSP
SCSV1
SCSP1
SCSP2
IM 32S05B10-21E
viii
n Trademark Acknowledgments
CENTUM, ProSafe, Vnet/IP and STARDOM are registered trademarks of YOKOGAWA.
Microsoft, Windows, Windows Vista, Visual Basic, Visual C++ and Visual Studio are either
registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries.
Adobe, Acrobat and Acrobat Reader are either registered trademarks or trademarks of
Adobe Systems Incorporated in the United States and/or other countries.
Ethernet is a registered trademark of XEROX Corporation.
Modicon and Modbus are registered trademarks of Schneider Electric SA.
PLC is a registered trademark of Rockwell Automation, Inc.
HART is a registered trademark of the HART Communication Foundation.
All other company and product names mentioned in this users manual are trademarks or
registered trademarks of their respective companies.
We do not use TM or mark to indicate those trademarks or registered trademarks used in
this users manual.
IM 32S05B10-21E
TocA-1
ProSafe-RS
Open Interfaces
IM 32S05B10-21E 3rd Edition
CONTENTS
PART A
A1.
A1.2
A1.3
IM 32S05B10-21E
TocB-1
ProSafe-RS
Open Interfaces
IM 32S05B10-21E 3rd Edition
CONTENTS
PART B
B1.
B2.
B3.
B1.2
B1.3
Engineering..............................................................................................B2-1
B2.1
B2.2
B2.3
B2.4
Messages Communication....................................................................B3-1
IM 32S05B10-21E
TocC-1
ProSafe-RS
Open Interfaces
IM 32S05B10-21E 3rd Edition
CONTENTS
PART C
C1.
C1.2
C1.3
C1.4
C1.4.2
C1.6
C1.6.2
C3.
C1.4.1
C1.5
C1.7
C2.
C3.2
C3.3
C3.4
C3.5
C3.5.2
C3.5.3
C3.6
C3.7
C3.8
C3.9
IM 32S05B10-21E
A1-1
TIP
OPC (OLE for Process Control) is an OLE (Object Linking and Embedding) specification, i.e., a method of
standard communication between applications in Windows environments, which is specifically applicable
to process control. OPC allows sending/receiving process data among multiple general-purpose Windowscompatible applications.
IM 32S05B10-21E
A1-2
Ethernet
General-purpose
PC (OPC server)
SENG
HIS
Control bus
IM 32S05B10-21E
A1-3
OPC server
(A&E server)
Cache Data
SOE cassette
Control bus
SCS
Legend
SOE
Events log
Diagnostic
Information log
OPC interface
Events
A010101E.ai
IM 32S05B10-21E
A1-4
l OPC Interface
The following OPC compliant interface is provided:
Alarms and Events (A&E)
This interface notifies event messages, which are generated asynchronously by SCS, to
the host computer. The SOE cassette reads the event log on SCS at regular intervals (the
default is 10 seconds) and notifies changes (e.g., that new event messages are generated)
to the client.
The A&E server provides OPC A&E custom interfaces and OPC A&E automation interfaces.
l Application Capacity
The table below shows the application capacity limits.
Table
Application Capacity
Item
Capacity
100 clients
1000/OPC server
100/registeration object
Value
Event type
Description
System alarms
101
Simple(=1)
Diagnostic Information
Sequence of events
110
Simple(=1)
Event Information
IM 32S05B10-21E
A1-5
Severity level
Name
System alarms
Sequence of events
Description
900
500
300
200
500
Event Information
l Message
All SCS-generated event messages displayed in the SOE Viewer as the character string are
stored, including all system alarm messages generated in the SOE cassette.
Attribute Name
OPC ID
VARIANT type
Remark
SOETimestamp
301
VT_DATE
TimestampM
302
VT_12
Resource
303
Type
304
ID
305
VT_BSTR
Quality
306
Node
308
VT_I2
Node position, or 0
Slot
309
VT_I2
Slot position, or 0
Time_Diff
318
VT_BSTR
*1:
Resource (computer name), Type (fixed to BSYS), ID/Quality (blank) SOETimestamp, TimestampM and Time_Diff (PCTime) are
stored in the case of alarms generated in the SOE cassette.
Table
Attribute Name
OPC ID
VARIANT type
Remark
SOETimestamp
301
VT_DATE
TimestampM
302
VT_12
Resource
303
Type
304
ID
305
VT_BSTR
Quality
306
IM 32S05B10-21E
A1-6
Table
Attribute Name
OPC ID
VARIANT type
Remark
Node
308
VT_I2
Slot
309
VT_I2
Channel
310
VT_I2
TripMark
313
VT_I2
Time_Diff
318
VT_BSTR
Event Type:
1 (Simple)
Source:
Yokogawa.ExaopcAESCSSOE
Time:
(PC time)
Severity:
900
Message:
(Computer name)
BSYS
ID (Event Attribute):
(Blank)
(Blank)
SEE
ALSO
For information about the CPU Load Distribution, see the following:
2.17, Connection with Host System Computer via OPC Server of the Engineerign Guide (IM 32S01C1021E)
IM 32S05B10-21E
A1-7
l Available Interfaces
The following tables shows the custom interfaces available to clients of the A&E server.
Table
Object
IOPCCommon
Method
Description
Support
SetLocaleID
Locale ID setting
GetLocaleID
Locale ID acquisition
QueryAvailableLocaleIDs
GetErrorString
SetClientName
GetStatus
CreateEventSubscription
QueryAvailableFilters
QueryEventCategories
QueryConditionNames
OPCEventServer
IOPCEventServer
IConnectionPoint
Container
x:
:
QuerySourceConditions
QueryEventAttributes
TranslateToItemIDs
Item ID translation/acquisition
GetConditionState
EnableConditionByArea
EnableConditionBySource
DisableConditionByArea
DisableConditionBySource
AckCondition
Notification of condition
acknowledgment
CreateAreaBrowser
IOPCSecurityNT
IOPCSecurityPrivate
EnumConnectionPoints
FindConnectionPoint
Supported
Not supported
IM 32S05B10-21E
A1-8
Table
Object
Method
IOPCSecurity
Private
OPCEventArea
Browser
(Option)
IOPCEventArea
Browser
IOPCEvent
SubscriptionMgt
OPCEvent
Subscription
IConnectionPoint
Container
IConnectionPoint
Support
Advise
Unadvise
IsAvailableNT
x
(*1)
QueryMinImpersonationLevel
ChangeUser
IsAvailablePriv
Logon
Logoff
ChangeBrowsePosition
BrowseOPCAreas
GetQualifiedAreaName
GetQualifiedSourceName
SetFilter
GetFilter
SelectReturnedAttributes
GetReturnedAttributes
Refresh
CancelRefresh
GetState
SetState
EnumConnectionPoints
FindConnectionPoint
IConnectionPoint
OPCEventServer IOPCSecurityNT
Description
Advise
Unadvise
x
(*2)
x
x
OPCEventSink
IOPCEventSink
OnEvent
Event notification
OPCShutdown
IOPCShutdown
ShutdownRequest
x:
:
*1:
*2:
Supported
Not supported
The IsAvailableNT method of the IOPCSecurityNT interface always returns FALSE.
The IsAvailablePriv method of the IOPCSecurityPrivate interface always returns FALSE.
IM 32S05B10-21E
A1-9
l Filters
It is possible to specify the following filtering conditions.
Table
Filtering Conditions
Mask
Description
OPC_FILTER_BY_EVENT
OPC_FILTER_BY_CATEGORY
OPC_FILTER_BY_SEVERITY
OPC_FILTER_BY_SOURCE
n Error Codes
The following tables show error codes handled by the SOE cassette. Each error code is set as a
return value of a function of the SOE cassette interface or a data error value of each data.
Description
E_FAIL
E_INVALIDARG
Invalid parameter
E_NOTIMPL
Unsupported function
E_OUTOFMEMORY
Insufficient memory
Table
Description
OPC_E_BADRIGHTS
No access right
OPC_E_BADTYPE
OPC_E_INVALIDITEMID
Invalid item ID
OPC_E_INVALID_PID
Invalid parameter ID
OPC_E_UNKNOWNITEMID
IM 32S05B10-21E
A1-10
Code
(xxxx-x999)
Symbol
(ZOT_XL_E_XXXX)
Description
0xC0042329
ZOC_AE_E_MAXSERVER
0xC004232A
ZOC_AE_E_MAXSUBSCRIPTION
For Microsoft
0200 to 7999
9000 to 9999
1 0 9 8 7 6 5 to 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
Sev C R
Facility
Code
IM 32S05B10-21E
A1-11
The SOE OPC interface functions include a tool for setting operation parameters of the
SOE cassette. This section explains the functions of the operation parameter setting tool.
Maintenance
Online Manual
Message Cache Tool
SCS Status Overview
SOE OPC Parameter Setting
SOE Viewer
Software Configuration Viewer
Version Control Tool
Workbench
Project Attribute Tool
Test Project Creating Tool
Shut Down
Start
A010201E.ai
IM 32S05B10-21E
A1-12
When the operation parameter setting tool is launched, it displays the SOE OPC Interface Setting
dialog box.
SOE OPC Interface Setting
A&E
Use Database
SCS0101
SCS Name
9:00:00 AM
10
(sec)
120
(sec)
40
(msec)
HDA
Use HDA
10000
OK
Cancel
A010202E.ai
Specify operation parameters for the A&E server and the HDA(Historical Data Access) server as
necessary. Click the [OK] button when you have completed the settings; the dialog box closes.
IM 32S05B10-21E
A1-13
IMPORTANT
Determine the maximum number of saving events based on the disk capacity and the search
speed of the HDA server. One event uses approximately 500 bytes of storage space, which
means that 10000 events use approximately 5 MB. Note that the larger the file, the longer it takes
to search; do not set too large a value even if disk capacity is sufficient.
TIP
The same information will not be sent again if the SOE OPC interface is restarted with the same date/time
previously specified. To resend the past events, check the [Specify Start Date/Time of Events] box and specify
the date and time again.
IM 32S05B10-21E
A1-14
DCOM Settings
Server machine
Client machine
Authentication level
Connect
None
Impersonation level
Impersonate
Access permissions
None
Launch permissions
N/A
IM 32S05B10-21E
A1-15
n Starting
The OPC server is automatically launched as a Windows service. That means the A&E server
and SOE cassette become available automatically simply by turning the power supply to the PC
on (no logon operation is necessary).
n Closing
The OPC server closes when Windows is shut down. At this time, the OPC server receives a
shutdown event and notifies it to the OPC client.
IM 32S05B10-21E
B1-1
Use the Modbus interface to connect between the ProSafe-RS and other systems.
By accessing SCS data via the Modbus interface, operator interfaces can also be
configured in other systems.
SEE
ALSO
For more information about Modbus Slave Connection, see the following:
2.16, Connection with Other Systems via Serial Communication of the Engineering Guide (IM 32S01C1021E)
IM 32S05B10-21E
B1-2
Downloading definition
information
Error information
SCS CPU
Definition information
Reference
SCS data
Data access
The relationship of each component with the Modbus master is explained below.
SENG
The engineering functions of the SENG download the definition information of the serial
communication module and the definition of correspondence between Modbus device
addresses and SCS data, etc. to SCS.
SCS Maintenance Support Tool
The SCS status display function of SCS Maintenance Support Tool receives error
information and notifies the error status if there is any error in the serial communication
module and communication content.
Modbus Master
The Modbus master references and sets SCS data via the serial communication module.
SCS
The Modbus slave function of SCS accesses data in response to a request from the
Modbus master and returns the result to the Modbus master via the serial communication
module.
IM 32S05B10-21E
B1-3
n Modbus Protocol
The Modbus protocol defines communication procedures and message formats between one
master and multiple slaves when performing serial communication.
The Modbus protocol has the following features:
Only the master can initiate communication via the Modbus protocol. The master requests
data reference or setting, and the slave responds to the request.
The signal transmission between the master and slaves can be performed in either the RTU
(Remote Terminal Unit) mode or the ASCII mode. SCS supports the RTU mode only.
Modbus Devices
Data
Write (set)
Coil
Possible
Possible (*1)
Input relay
Possible
Impossible
Input register
Possible
Impossible
Holding register
Possible
Possible (*1)
*1:
The Modbus master can only set data on SCS (Modbus slave) if virtual Modbus devices are assigned to external communication
function blocks.
The correspondence between the addresses of the Modbus devices and variables of the
application logic is defined using SCS Manager.
SEE
ALSO
For more information about how to associate Modbus device addresses with application logic variables, see the
following:
B2.2, Definitions in Modbus Address Builder
IM 32S05B10-21E
B1-4
Modbus communication
processing
1 second
B010103E.ai
Monitoring operation
System alarm
IM 32S05B10-21E
B1-5
SCS operates as a Modbus slave to perform Modbus communication. The Modbus slave
communication functions include the Modbus communication function and the data
access function.
l Word Reversal
To reference SCS data, the order of 32-bit data can be changed.
The direct order is in the order of the upper word first and the lower word. The reverse order is in
the order of the lower word first and the upper word if this option is specified.
32-bit data
Upper word
Lower word
Direct
40001
40002
Reverse
40002
40001
B010201E.ai
IM 32S05B10-21E
B1-6
l Communication Test
When testing for referencing a variable of SCS, change a value of the variable by using the
forcing function and confirm the value by the Modbus master. When testing for setting an external
communication function block of SCS, connect a variable with the external function block and
confirm the value of the variable by the Modbus master reading back.
SEE
ALSO
For more information about the forcing function, see the following:
2, Forcing Function of the Utilities and Maintenance Reference (IM 32S04B20-21E)
IM 32S05B10-21E
B1-7
n Transmission Specifications
The transmission specifications of SCS operating as a Modbus slave device are summarized in
the table below.
Table
Description
RS-232C
Interface
RS-422/RS-485 (4-wire
system)
Builder
specification
x
Remarks
ALR111
ALR121
Synchronization method
Start-stop
synchronization
Baud rate
Start bits
Fixed to 1
Data bits
7, [8]
Stop bits
[1], 2
Parity
RS control
Yes, [No]
DR check
[Yes], No
CD check
Yes, [No]
Transmission
enable monitoring
time
0 to 99990 (ms)
[1000 ms]
Specify in units of 10 ms
Control line
Time monitoring
Text frame
0 to 99999 (ms)
Reception character
[10 ms]
interval timer
Specify in units of 1 ms
Character internal
monitoring timeout
Reception start
character
1 character, [None]
EOT character
1 character, 2
characters, [None]
Maximum number of
Up to 512 bytes
transmit characters
Maximum number of
Up to 512 bytes
receive characters
Station number
1 to 247
Option 1 to 4
Fixed to 0
MODBUS RTU/ASCII
RTU(*1)
IM 32S05B10-21E
B1-8
This section describes the connection configuration between the Modbus master and
SCS, including the configuration of serial communication modules and cable connection.
n Connection Configuration
A connection configuration using STARDOM autonomous controller FCN (Field Control Node) as
the Modbus master is shown below.
Modbus master
(STARDOM FCN)
Serial
communication
module (NFLR111)
RS-232C
Modbus Slave
(SCS)
MODEM
MODEM
RS-232C
Serial communication
module
(ALR111)
Modbus Slave
(SCS)
MODEM
Serial communication
module
(ALR111)
B010301E.ai
Figure Example of Connection between the Modbus Master and SCS (Using a STARDOM FCN as the
Modbus Master)
SCS communicate with the STARDOM FCN, which is the Modbus master, via a serial
communication module (NFLR111 and ALR111 in the example above).
TIP
The STARDOM autonomous controller FCN and the serial communication module (NFLR111) are products of
Yokogawa Electric Corporation.
IM 32S05B10-21E
B1-9
PSM
PSM
CPU
CPU
IOM
IOM
ALR111
IOM
IOM
IOM
IOM
IOM
Two ports
SCS
RS-232C
Modbus master
ALR111: Serial communication module (RS-232C)
ALR121: Serial communication module (RS-422/RS-485)
B010302E.ai
l Status Display
The operation status can be checked by observing the LED displays on the serial communication
module as well as the HIS System Status Overview window. The table below lists the LED
displays of the serial communication module and their meanings when they are illuminated.
Table
LED indication
SEE
ALSO
Meaning
STATUS
Hardware ready
ACT
Operating normally
DX
Duplex display
SND1, SND2
RCV1, RCV2
Receiving at port 1 or 2
Remarks
Always OFF
For more information about Restrictions on Mounting and about Serial Communication Redundancy, see the
following:
2.16, Connection with Other Systems via Serial Communication of the Engineering Guide (IM 32S01C1021E)
IM 32S05B10-21E
B1-10
l Connector Specification
Use an RS-232C D-sub 9-pin connector for connecting with ALR111.
1
2
3
4
5
6
7
8
9
B010304E.ai
Pin number
Signal name
Name
Processing on ALR111
Send when CD is OFF (only if CD check is
specified). Receive when CD is ON.
CD
Carrier Detect
RD
Receive Data
SD
Send Data
ER
SG
Signal Ground
DR
RS
Request to Send
CS
Clear to Send
Not used
IM 32S05B10-21E
B1-11
l Modem Connection
The following figure shows a cable connection when ALR111 and the Modbus master are
connected via modems.
ALR111
SD 3
2 SD
RD 2
3 RD
RS 7
4 RS
CS 8
5 CS
CD 1
8 CD
DR 6
6 DR
ER 4
20 ER
SG 5
7 SG
Modem
1 FG
Sheathed cable
Figure Cable Connection of ALR111 (9-pin) and the Modbus Master (25-pin) via Modems
ALR111
SD 3
2 SD
RD 2
3 RD
RS 7
4 RS
CS 8
5 CS
CD 1
8 CD
DR 6
6 DR
ER 4
20 ER
SG 5
7 SG
DTE
1 FG
Sheathed cable
Figure Cable Connection for Directly Connecting ALR111 (9-pin) and the Modbus Master (25-pin)
IM 32S05B10-21E
B1-12
ALR111
SD 3
3 SD
RD 2
2 RD
RS 7
7 RS
CS 8
8 CS
CD 1
1 CD
DR 6
6 DR
ER 4
4 ER
SG 5
5 SG
DTE
1 FG
Sheathed cable
Protective grounding
(equivalent to JIS Class D: 100 or less)
B010307E.ai
Figure Cable Connection for Directly Connecting ALR111 (9-pin) and the Modbus Master (9-pin)
n Precautions at Wiring
Precautions on wiring the ALR111 signal lines are described as follows.
l CD Signal Line
When the CD signal is ON, data is being transmitted to the receiver. Wire a signal line that turns
ON when the connection destination sends data to the CD signal. In general, wire the RS signal
of the connection destination to the CD signal.
If a signal line that turns ON when the connection destination sends data is not available, wire a
signal that is always ON, for example the ER signal line of the ALR111 itself, to the CD signal pin.
When the CD check function is enabled, transmission is not allowed when the CD signal is ON
(because data is being transmitted from the other end of the line).
Turn OFF the CD check if the CD signal cable is always in the ON status. The check is turned
OFF by default.
IM 32S05B10-21E
B1-13
IM 32S05B10-21E
B2-1
<B2. Engineering>
B2. Engineering
The following settings are required for the Modbus master to access variables of the
application logic on SCS via Modbus communication.
Definitions of serial communication modules
Define the serial communication module (ALR111/ALR121) to perform Modbus
communication using I/O Wiring View and I/O Parameter Builder.
Definition of addresses of Modbus devices
Define virtual Modbus devices on SCS and assign them to variables, using Modbus
Address Builder.
Data setting using external communication function blocks
SEE
ALSO
For more information about module parameter settings, see the following:
Common Setting Items for Input/Output Modules in A4.3, Common Setting Items for Process Data
Inputs and Outputs of the Safety Control Station Reference (IM 32S03B10-21E)
For more information about parameter settings for each port, see the following:
[Port 1], [Port 2] Tab in B2.1, Definitions in I/O Parameter Builder
Open I/O Wiring View and select a module (ALR111 or ALR121). The number of channels
should be set to 0.
2.
Select parameters for the module and specify the node number and the slot number. The
node number and the slot number must not overlap with those of other input/output modules
and serial communication modules.
SEE
ALSO
For more information about I/O Wiring View and I/O Parameter Builder, see the following:
4, Definitions of Inputs/Outputs of the Engineering Reference (IM 32S04B10-21E)
IM 32S05B10-21E
<B2. Engineering>
B2-2
IM 32S05B10-21E
B2-3
SEE
ALSO
For more information about how to open I/O Parameter Builder and the window configuration, see the
following:
4.4, I/O Parameter Builder of the Engineering Reference (IM 32S04B10-21E)
For more information about the common setting items of serial communication modules, see the following:
Common Setting Items for Input/Output Modules in A4.3, Common Setting Items for Process Data
Inputs and Outputs of the Safety Control Station Reference (IM 32S03B10-21E)
Description
Baud Rate
Stop Bits
Parity
Control Line
Remark
RS Control
DR Check
CD Check
Station Number
Option 1 to 4
Fixed to 0
IM 32S05B10-21E
B2-4
l Baud Rate
Specify the baud rate, selecting either 1200, 2400, 4800, 9600, 19200. The default baud rate is
19200 bps.
l Stop Bits
Specify the length of stop bits for the communication, selecting either 1 bit or 2 bits. The default
value is 1 bit.
l Parity
Specify the parity, selecting None, Odd or Even. The default value is Even.
l RS Control
Specify whether or not to perform RS control during ALR111 transmission. The setting is only
valid for the ALR111. The default is not to perform the RS control function.
Without RS control
Always set the RS signal cable to ON regardless of the data transmission from the ALR111.
With RS control
Turn the RS signal cable ON when data is transmitted from the ALR111 and OFF at the
completion of transmission.
l DR Check
Specify whether or not to perform DR signal line check during ALR111 transmission. The setting
is only valid for the ALR111. The default is to perform the DR check function.
Without DR check
ALR111 transmission data regardless of the status of the DR signal cable.
With DR check
ALR111 transmission data only if the DR signal cable is ON. A no-response error occurs if
the DR signal does not turn ON after the transmission enable monitoring time has elapsed
(the response data is discarded).
The DR signal is used to connect to the ER (data terminal ready) signal line to communicate with
and to determine whether or not the ER signal line at the connection destination is able to receive
character data (normal operation). If the ER signal line cannot be used, set without DR check or
wire the line in such a way that the DR signal line is switched ON at all times (*1).
*1:
For example, connect the RS signal line to the DR signal pin of its own.
l CD Check
Specify whether or not to perform CD signal check during ALR111 transmission. The default is
not to perform the CD check function.
Without CD check
ALR111 transmission data regardless of the status of the CD signal cable.
With CD check
ALR111 transmission data if the CD signal is OFF. A no-response error occurs if the CD
signal does not turn OFF after the transmission enable monitoring time has elapsed.
IM 32S05B10-21E
B2-5
10 ms
IMPORTANT
If multiple slave devices are connected on the same line, set the time so that it corresponds to
the transmission of approximately 20 characters in the RS communication (20 ms for 9600 bps,
10 ms for 19200 bps). If the value is set larger than the communication time with other slave
devices, the communication is not performed properly and a non-response error occurs.
l Station Number
Specify the slave address of the Modbus slave.
Default:
l Options 1 to 4
Always set 0 for these options.
Default:
0 (for all)
IM 32S05B10-21E
B2-6
Use Modbus Address Builder to associate the variables of the application logic with the
addresses of Modbus devices.
SEE
ALSO
Remark
BOOL
Input relay
REAL
Input register
DINT
Input register
Input register
Input relay
Coil
Holding registers
IM 32S05B10-21E
B2-7
l Variable Names
A variable name can be up to 69 characters long. Both global and local variables can be
accessed regardless of the scope. Describe a scope name after @ to access local variables.
To access internal variables in a user-defined function block, it is necessary to use Dictionary
View of SCS Manager to name instances of the user-defined function block itself. A variable
name is specified using the format instance name:internal variable name. Up to two nesting
levels can be specified for an instance name.
Table
Variable name
SEE
ALSO
Scope
Description
VAR1
Global
A global variable
VAR2@PROG1
PROG1
FB01.VAR3
Global
FB01.VAR3@PROG1
PROG1
FB01.FB2.VAR3
Global
For more information about Dictionary View of SCS Manager, see Workbench of the Workbench Users Guide.
IM 32S05B10-21E
B2-8
Edit
Debug
Tools
Options
Window
0
1
N
A
Z
Help
Z
A
All variables
Variables
Main (Config1)
BoundVariable
BindingError
Any Group
All variables
Global varia
Addition (*si
Main (*simpl
Binding Test
ComplexTes
Test (Config1)
CPC001-09889-03.00109889
Name
Alias
BindingErrorTxt
BindingErrorTxt [0]
BindingErrorTxt [1]
BindingErrorTxt [2]
BindingErrorTxt [3]
BindingErrorTxt [4]
OK2
IN01
val4
VASystemKVB
UserAcknowledge
InitBindText
Type
[]
BindErrText
STRING
STRING
STRING
STRING
STRING
BOOL
REAL
BOOL
BOOL
BOOL
BOOL
200
200
200
200
200
200
Edit
Variable
AI03
AI04
D02@P1
D03@P1
D04
FB1A.R1
FB1A.R2
FB2A.R1
FB2B.R2
R01
R02
R04
IN01
View Tools
IOM
Coil
Window
Input relay
Reference
Input registers
Variable name
Type
30001
R03
REAL
30003
IN01
30005
D01@P1
Holding regis
Wiring po
DINT
30007
30009
30011
AI01
IO_REAL
%IU0.1
30013
AI02
IO_REAL
%IU0.2
30015
Message
Ready
Position: Line
1 Column 3
B020201E.ai
IM 32S05B10-21E
B2-9
IMPORTANT
Changing a name and type of a variable in Dictionary View will not change the corresponding
definition in Modbus Address Builder. Make the corresponding modifications in Modbus Address
Builder according to changes.
If a variable is added
Use Modbus Address Builder and assign a reference number to the variable as necessary.
If a variable name is changed
Change the corresponding variable name in Modbus Address Builder as well.
If a variable is deleted
Delete the corresponding variable in Modbus Address Builder.
IM 32S05B10-21E
B2-10
This section describes the window configuration and menus of Modbus Address Builder.
Edit
Variable
AI03
AI04
D02@P1
D03@P1
D04
FB1A.R1
FB1A.R2
FB2A.R1
FB2B.R2
R01
R02
R04
IN01
View Tools
IOM
Coil
Window
Help
Input relay
Reference
30001
Input registers
Variable name
Type
R03
REAL
D01@P1
DINT
Holding regist
Wiring Po
30003
30005
30007
30009
30011
AI01
IO_REAL
%IU0.1
30013
AI02
IO_REAL
%IU0.2
30015
Message
Ready
Position: Line
1 Column 3
Work Space
B020301E.ai
SEE
ALSO
For more information about the configuration components common with other builders, see the following:
2.2, Relationship between ProSafe-RS Projects and CENTUM Project of the Engineering Reference
(IM32S04B10-21E)
IM 32S05B10-21E
B2-11
l [Variable] Tab
The [Variable] tab displays a list of variables that can be defined. The variable names displayed
change depending on the type of Modbus devices displayed in the work space.
Variables that have been defined already at the time a variable was set or deleted are deleted
from the list and not displayed.
Variable
IOM
AI03
AI04
D02@P1
D03@P1
D04
FB1A.R1
FB1A.R2
FB2A.R1
FB2B.R2
R01
R02
R04
IN01
B020302E.ai
l [IOM] Tab
When the [input relay] tab or the [input register] tab is displayed, in the workspace the [IOM] tab
becomes available. For an Input Relay, a discrete input module will be displayed; while for an
Input Register, an analog input module will be displayed.
Variable
IOM
Node1
1-1
1-2
1-3
1-4
1-5
1-6
B020303E.ai
IM 32S05B10-21E
B2-12
Output devices of 1 bit per channel (allows both input and output)
Each register is assigned to a 32-bit data, i.e. 2 words compose one data.
Output registers of 16 bits per channel (allows both input and output)
Each register is assigned to a 32-bit data, i.e. 2 words compose one data.
IM 32S05B10-21E
B2-13
IM 32S05B10-21E
B2-14
The SCS Modbus slave connection function allows setting data on SCS from the Modbus
master. Use external communication function blocks to set SCS data from the Modbus
master. Data setting via external communication function blocks does not interfere with
the safety loop (interference-free). Make sure to read back and confirm the data set by
external communication function blocks, when using the data for safety application.
SEE
ALSO
For more information about Modbus Address Builder, see the following:
B2.2, Definitions in Modbus Address Builder
For more information about external communication function blocks, see the following:
D5, Data Setting Using External Communication Function Blocks of the Safety Control Station Reference
(IM 32S03B10-21E)
To set BOOL-type data, assign an ECW_B instance name to the reference number of a coil.
To set DINT-type data, assign an ECW_I instance name to the reference number of a
holding register.
To set REAL-type data, assign an ECW_R instance name to the reference number of a
holding register.
As a result, data set from the Modbus master are output from the output parameter OUT of the
associated external communication function blocks.
Modbus master
Application
Modbus
Modbus slave
connection
function
Application logic
Internal
variable
ECW_B
OUT
Internal
variable
ECW_I
OUT
Internal
variable
ECW_R
OUT
<BOOL-type data>
<DINT-type data>
<REAL-type data>
SCS
B020401E.ai
Figure Data Setting Using the Modbus Slave Connection Function and External Communication
Function Blocks
IM 32S05B10-21E
B2-15
The user uses Modbus Address Builder to assign reference number of these Modbus devices to
external communication function blocks and read-back variables.
Table
BOOL
Coil
Input relay
DINT
Holding register
Input register
REAL
Holding register
Input register
*1:
*2:
*3:
2.
Assign an input relay reference number to a read-back variable using Modbus Address
Builder.
3.
The Modbus master writes data to a coil reference number. In the figure below, the data is
written to reference number 00032.
4.
The Modbus master reads back data with an input relay reference number. In the figure
below, data is read back with reference number 10032.
00032
(reference number)
Modbus slave
connection function
Application logic
Internal
variable
OUT
ECW_B
10032
(reference number)
Modbus Master
READBACK
Normal
BOOL-type
variable
SCS
Modbus
B020402E.ai
IM 32S05B10-21E
B2-16
IMPORTANT
Periodical data setting will result in a writing error.
Do not set data periodically from the Modbus master.
IM 32S05B10-21E
B3-1
l Slave Address
This is the setting value (1 to 247) of Station Number.
All the Modbus slaves receive a request message of the Modbus master. The only SCS, whose
slave address is the same as the slave address in the request message, responds the request.
l Function Code
SCS supports the following function codes of request messages of the Modbus master.
Table
Function code
(hexadecimal)
Description
Maximum size
01
512 bits
02
512 bits
03
04
05
1 bit
08
0F
32 bits
10
Remark
512 bits = 32 words
IM 32S05B10-21E
B3-2
SEE
ALSO
IM 32S05B10-21E
B3-3
Error Codes
Meaning of error
01
02
03
04
07
10
11
12
IM 32S05B10-21E
B3-4
l Response Time
The response time refers to the time from the point SCS receiving a request message to
starting to transmit the response message. The RS transmission (data transmission on the
communication line) time is not included.
Response time = (Message receiving and sending processing time) +
(Modbus message reading and writing processing time)
= 20 ms + (0 to scan period of application logic)
Message receiving and sending processing time
: Set to 20 ms
Modbus message reading and writing processing time : Scan period of application logic
The Modbus message reading and writing processing is performed after the completion of
processing of the application logic. This generates a delay of up to the application logic scan
period from receiving a request message to completing it.
IMPORTANT
The longest time it takes for data to be read by the Modbus master is as follows:
If a writing request from the CENTUM integration function coincides with those from a Modbus
master on another RS port, notification of the writing request to the application logic will be
delayed for the number of writing requests. Therefore, the longest time it takes for the Modbus
master to notify a write to the SCS application logic is as follows:
RS transmission time +
scan period of the application logic x
number of writing requests from the external connection
function
IM 32S05B10-21E
B3-5
SEE
ALSO
For more information about diagnostic Information Message, see the following:
3.1, Safety Control Station Error Occurrence and Recovery Messages of the Messages (IM 32S02B1021E)
TIP
The serial communication modules (ALR111/ALR121) can be used on SCS and CENTUM FCS. The Modbus
communication driver needs to be down loaded into the serial communication module. The driver down loaded is
referred to as Serial Communication Driver. When a serial communication module is replaced, it is necessary to
perform IOM Load to the new module.
SEE
ALSO
For more information about system alarm messages at downloading serial communication driver, see the
following:
3.2, Safety Control Station Status Change Related Messages of the Messages (IM 32S02B10-21E)
SEE
ALSO
For more information about diagnostic Information Message, see the following:
3.1, Safety Control Station Error Occurrence and Recovery Messages of the Messages
(IM 32S02B10-21E)
IM 32S05B10-21E
B3-6
IM 32S05B10-21E
C1-1
This section describes the structure of subsystem communication functions within the
SCS and gives an overview of communication between the subsystem and the SCS.
IM 32S05B10-21E
C1-2
Output enable
IOM download
- Multi-Language
Editor
- Dictionary
Communication I/O
Lock Window
Operating status
IOM status
Diagnostic information
Forcing
CENTUM
Referencing of logics
Referencing of
communication data
Referencing of
communication data
as tag names
SCS
Application logic
execution
System FBs
Communication
I/O data
management
Subsystem
communication module
management
Integration
with CENTUM
Communication
I/O data area
Communication I/O
images
Module status
IOM download
Subsystem communication module
Images inside the module
Subsystem
communication program
(communication driver)
Subsystem
Interpretation of communication
protocols
Subsystem
C010101E.ai
IM 32S05B10-21E
C1-3
AI
DI
Subsystem
communication
module
Sequencer
DO
SCS
POU
Logical data
50.0
Physical data
50.0
50.0
Wiring
Comm. definition
DI
DO
1
1
1
Comm. definition
1
Comm
1
1
. defin
ition
1
Subsystem
communication
input FB
1
1
Subsystem
communication
input FB
Subsystem
communication
output FB
C010102E.ai
IM 32S05B10-21E
C1-4
CPU
IM 32S05B10-21E
C1-5
Application logic
execution
Communication I/O
data area (input)
Subsystem
communication
period
0 to SCSs
application logic
scan period
Communication I/O
data area (output)
5. Flush the
communication I/O
data area (output)
Images inside
the module
Images inside
the module
Subsystem
input
4. Subsystem
communication
output FB
(write)
6. Subsystem
communication
(write)
Subsystem
output
Subsystem
communication
period
C010104E.ai
SEE
ALSO
1.
2.
3.
4.
5.
6.
IM 32S05B10-21E
C1-6
RSP
Read
communication
definition 1
for port 1
CMD
RSP
Write
communication
definition n
for port 1
(if changed)
CMD
RSP
Read
communication
definition n
for port 1
CMD
CMD
RSP
Read
communication
definition 1
for port 1
Serial
communication
module
CMD: Command
RSP: Response
Subsystem
Communication period
C010105E.ai
SEE
ALSO
For assurance of simultaneity of communication data when the Modbus Communication Package (for ALR111,
ALR121) is used, see the following:
n Simultaneity of Communication Data in C3.1, Communication Specifications
IM 32S05B10-21E
C1-7
Remark
Bit (DI/DO)
BOOL (bit)
32-bit floating
In order to handle the subsystem communication data on SCS, the Communication I/O Builder is
used for wiring the subsystem data and the SCS data according to the data types of subsystem.
All the wired data are referred to as communication data. A communication datum consists of
data value and data status.
n IOM Download
An IOM download downloads the subsystem communication package to the subsystem
communication module and restarts the communication module. No output enable operation is
required.
IM 32S05B10-21E
C1-8
Subsystem
communication
output FBs
Output
Subsystem
communication
module
(standby side)
Input
Output
Input
Output
Input
Input
Output
Output
Subsystem communication
module (control side)
Images inside the module
Reading of
input data
Readback of
output data
Reading of
input data
Writing of
modified data
Subsystem
C010201E.ai
IM 32S05B10-21E
C1-9
SEE
ALSO
TIP
When you have online-changed the configuration of the subsystem communication module from a single to dualredundant configuration, the modules start the dual-redundant operation immediately after the module is added.
This does not affect the operating mode of the SCS because the output of the SCS stays enabled.
IM 32S05B10-21E
C1-10
This section describes the error handling actions after a restart of the subsystem
communication module, initial cold start of the SCS, occurrence of a communication
error, and so on.
Condition
Upon occurrence
Input data: Value of Input Processing at
Fault
Input status: BAD
Output status: BAD
After recovery
Input data: Value from the subsystem
Input status: GOOD
Output status: GOOD
During on-line change download
Input data: 0 or FALSE
Input status: BAD
Output status: BAD
*1:
*2:
*3:
*4:
*5:
*6:
Subsystem communication
Only inputs are communicated and
data is not output until the output
enable operation is performed.
Output starts following the output
enable operation (for subsystem
communication). (*1)
Upon occurrence: Communication
is not possible. (*2)
After recovery: I/O is resumed.
Values from the application logic are
output. (*3) (*4)
No impact. Communication
continues.
The output enable operation using SCS Maintenance Support Tool enables both safety output and subsystem communication
output. Dedicated system function blocks are provided for enabling safety output and subsystem communication output,
respectively.
The SCSs operating mode is not affected by communication errors or subsystem communication module errors.
If errors need to be latched, application logics that reference data status needs to be created.
If the subsystem communication module is locked and in the case of outputs with readback, the output values are read back from
the subsystem immediately after the recovery of subsystem communication and are output.
Even when a subsystem communication I/O FB instance is deleted and then a new instance is recreated, it is recognized as
addition of a new subsystem communication I/O FB.
The operating mode of the SCS is not affected because the output of the SCS stays enabled.
IM 32S05B10-21E
C1-11
Communication
input
Logical data
Physical
data
Logical data
Communication
output
Physical
data
Output to subsystem
After recovery
Data value: Value immediately before
locking
Data status: Value immediately before
locking
Data value: Value from the subsystem
Data status: GOOD
Data value: Value from the application
logic
Data status: Value immediately before
locking
Data value: Output value from the
subsystem immediately after
recovery of communication
Data status: GOOD
Input:
Resumed.
Output:
Output value from the
subsystem immediately after
recovery of communication
C1-12
Communication
I/O Builder
CENTUM
Definition of
communication data
SCS
Application logic
execution
Tag name definitions
Wiring
Communication
I/O data management
Communication definitions
Device definitions
Integration
with CENTUM
Subsystem
communication
module
management
Subsystem
communication
module
Transmission definitions
Subsystem
C010401E.ai
IM 32S05B10-21E
C1-13
2.
3.
Set parameters for the subsystem communication module using the I/O Parameter Builder.
4.
Define communication I/O assignments in the Comm. I/O Definition tab of the
Communication I/O Builder. Assign subsystem communication data to element numbers.
This assigns the subsystem communication data to the communication I/O data area.
5.
Associate the element numbers and subsystem communication I/O FBs in the Comm. I/O
Wiring tab of the Communication I/O Builder.
Associate (wire) the subsystem communication I/O FBs defined in step 1 with the
element numbers defined in step 4. Associate one subsystem communication I/O FB
with one element number. This links the subsystem communication data assigned to the
communication I/O data area with the subsystem communication I/O FBs.
Dictionary View
1. Definition of subsystem
communication I/O FBs
using Dictionary View
2. Definition of subsystem
communication module
3. Definition of subsystem
communication module
parameters
4. Assignment of
communication I/Os
5. Assignment of element
numbers and subsystem
communication I/O FBs
C010402E.ai
IM 32S05B10-21E
C1-14
%WB200301
Mapping of
subsystem
communication
data and
communication
I/O data area
%WB210101
Program
(application logic)
Subsystem communication
I/O FB
Mapping of
element
numbers and
subsystem
communication
I/O FBs
Subsystem communication
I/O FB
Subsystem communication
I/O FB
%WB210301
Subsystem
communication
module
C010403E.ai
The types of subsystem communication I/O FBs vary depending on the type of communication
I/O data to be assigned.
Table Types of Subsystem Communication I/O FBs and Types of Data that can be Wired
Data type
SCI_I
SCI_R
SCO_I
SCO_R
Discrete input
SCI_B
Discrete output
SCO_B
IM 32S05B10-21E
C1-15
C1.4.1
SEE
ALSO
For the recommended settings and items to note when the Modbus Communication Package (for ALR111,
ALR121) is used, see the following:
C3.5.2, Items Set in the I/O Parameter Builder
l Module Tab
The items set in the Module tab are shown below.
Pjt:SCS1020 File:IOMDEFSB.edf
I/O
Module
Port 1
Port 2
Node1
1-1 SDV144(
1-3 SAI143([
1-5 SAI143([
Node Number
Slot Number
1-7 ALR111M
Device
ALR111M
1-8 ALR121(
Dual-Redundant
No
Device Number
Connection Device
4
S_MODBUS
Comment
C010404E.ai
l Node Number
The node number corresponding to the mounting position of the module is displayed. The node
number is defined in the I/O Wiring View of SCS Manager.
The Node Number field is read only.
l Slot Number
The slot number corresponding to the mounting position of the module is displayed. The slot
number is defined in the I/O Wiring View of SCS Manager.
The Slot Number field is read only.
IM 32S05B10-21E
C1-16
l Device
The type of module is displayed. The device (module type) is defined in the I/O Wiring View of
SCS Manager.
The Device field is read only.
l Dual-Redundant
Whether the module is used in a single or dual-redundant configuration is displayed. The dualredundant specification is defined in the I/O Wiring View of SCS Manager.
The Dual-Redundant field is read only.
l Device Number
The device number assigned to the module. The device number is defined in the I/O Wiring View
of SCS Manager.
The Device Number field is read only.
l Connection Device
Set the type of connection device (subsystem). This field is displayed only when the module type
is subsystem communication module.
Select the subsystem communication package that has been installed.
l Comment
A comment regarding the module. A desired comment can be entered using up to 24 single-byte
characters or 12 double-byte characters.
IM 32S05B10-21E
C1-17
Module
Port 1
Port 2
Node1
1-1 SDV144(
Baud Rate
19200
Stop Bits
1bit
1-7 ALR111M
Parity
Even
1-8 ALR121(
Data Bits
8bit
No
Yes
No
1-3 SAI143([
1-5 SAI143([
10 ms
Communication Retry
30 s
4-Wire
Option 1
Option 2
Option 3
Option 4
C010405E.ai
IM 32S05B10-21E
Table
Setting Items Available in Port 1 and Port 2 Tabs (Example where S_MODBUS is Set as
Connection Device)
Title
Description
Baud Rate
Stop Bits
Parity
Data Bits
Control
Line
C1-18
Remark
RS Control
DR Check
CD Check
Response Timeout
Communication Retry
Interval of Connection
Retries
2-Wire/4-Wire
Options 1 to 4
l Baud Rate
Specify the baud rate of communication. Select from 1200, 2400, 4800, 9600, 19200 and 38400
bps. The default is 19200 bps.
l Stop Bits
Specify the stop bits of communication. Select 1 bit or 2 bits. The default is 1 bit.
l Parity
Specify the parity. Select None, Odd or Even. The default is Even.
l Data Bits
Specify the data bit length of subsystem data to be transmitted. Select 7 bits or 8 bits. The default
is 8 bits.
l RS Control
Specify whether or not to use RS control when sending data from the ALR111M. This setting is
valid only when the ALR111M is used. The default is [No].
No (without RS control)
The RS signal line is always turned ON regardless of whether or not data is sent from the
ALR111M.
Yes (with RS control)
The RS signal line is turned ON when data is sent from the ALR111M, and turned OFF after
the sending is completed.
IM 32S05B10-21E
C1-19
l DR Check
Specify whether or not to use DR signal line check when sending data from the ALR111M. This
setting is valid only when the ALR111M is used. The default is [Yes].
No (without DR check)
Text data is sent from the ALR111M regardless of the DR status.
Yes (with DR check)
Text data is sent from the ALR111M only when the DR is ON. If the DR signal line does not
turn ON after elapse of the send-enable monitor time, a Line Not Ready (A393) error will
occur.
The DR signal is normally connected to the ER (Data Terminal Ready) signal line of the
subsystem and used to determine if the subsystem can receive data (normal operation). If the
signal line of the subsystem cannot be used, set [No] in this field or change the wiring so that the
DR signal line turns ON (*1).
*1:
For example, the RS signal line of the applicable module can be looped back to the DR signal line.
l CD Check
Specify whether or not to use CD signal line check when sending data from the ALR111M. The
default is [No].
No (without CD check)
Text data is sent from the ALR111M regardless of the CD status.
Yes (with CD check)
Text data is sent from the ALR111M only when the CD is OFF. If the CD signal line does
not turn OFF after elapse of the transmission monitoring time, a Communication line busy
(A392) error will occur.
10 ms
l Response Timeout
Set the timeout period to wait for subsystem response, in seconds.
Default:
4 sec.
IM 32S05B10-21E
C1-20
l Communication Retry
Set the number of retries to be attempted after a communication error occurs.
Default:
Setting range: 0 to 99
30 sec.
l 2-Wire/4-Wire
Specify the 2-wire or 4-wire connection method used by the ALR121M. This setting is valid only
when the ALR121M is used.
l Options 1 to 4
Specify the different optional communication parameters provided by each subsystem
communication package.
IM 32S05B10-21E
C1-21
C1.4.2
The Communication I/O Builder is used to define communication I/O data assignments
and wire communication I/O variables.
SEE
ALSO
For the recommended settings and items to note when the Modbus communication package (ALR111, ALR121)
is used, see the following:
C3.5.3, Items Set in the Communication I/O Builder
Title bar
Toolbar
Tool
Window
Help
Buffer
Program Name
Port
Size
2
Station
%WW2001
6 1-7S_MODBUS
%WW2002
* *
%WW2003
* *
%WW2004
* *
%WW2005
* *
%WW2006
* *
1
*
*
%WW2007
%WW2008
%WW2009
%WW2010
Message
Ready
Status bar
Workspace
C010406E.ai
IM 32S05B10-21E
C1-22
Buffer
Program Name
1-7S_MODBUS
%WW2001
Port
Size
4
Station
2 1
%WW2002
* *
* *
%WW2003
* *
* *
%WW2004
* *
* *
%WW2005
%WW2006
%WW2007
%WW2008
%WW2009
%WW2010
%WW2011
%WW2012
%WW2013
C010407E.ai
The items set in the Comm. I/O Definition tab are as follows:
Element: Read only
Buffer
Program Name
Size
Port
Station
Device Address
Data Type
Reverse
Input Processing at Fault
Input Value at Fault
l Element
The buffer address within the communication I/O data area is displayed.
The Element field is read only.
Display format: %WWnnnn
%WW: Fixed
IM 32S05B10-21E
C1-23
l Buffer
Specify the size of communication I/O data area to be used by the program (subsystem
communication package) in units of words (16 bits). The Buffer field can be entered only when
the Element field is an odd number address.
Input unit:
2 (even number)
Input range:
2 to 1000
Size limitation:
After a size has been specified to allocate the buffer, moving to the next setting item will display
asterisks (*) in the subsequent Buffer and Program Name fields corresponding to the buffer
size that has been allocated, where there is no error in the defined items. These asterisks
indicate that the applicable communication I/O data area has been allocated. The Buffer and
Program Name fields showing asterisks do not accept new settings. Deleting a Program
Name for which a buffer is allocated will not delete the asterisks in the corresponding Program
Name field.
If a Buffer is deleted, the items defined in the allocated buffer area (Program name, Size, Port,
Station, Device address, Data type, Reverse, Input Processing at Fault, Input Value at Fault) as
well as asterisks in the applicable fields will be deleted, and these fields can now accept new
settings.
If a Buffer is changed, the asterisks will also be changed. The Buffer field can not be changed
to a value smaller than the value in the Size field. Moreover, the designated value of Buffer
should not conflict with the reserved area. If the error value is entered, it would be cancelled so as
to revert to the previous value.
Example:
Table
Buffer
Program Name
%WW2001
2 (*1)
1-3S_MODBUS
%WW2002
%WW2003
1-5S_MODBUS
%WW2004
%WW2005
%WW2006
*1:
Size
An attempt to change 2 to 4 will generate an error, since specifying 4 overlaps with the area already allocated for
%WW2003.
l Program Name
Specify the program name using a combination of the node number and slot number for the
subsystem communication module defined in the I/O Wiring View, and a fixed character string.
The program name can be entered using up to 12 single-byte alphanumeric characters and
symbols (+,-, _).
The Program Name field cannot be selected if the corresponding Buffer field is not specified
or no module is defined in the I/O Wiring View.
In the case of a dual-redundant module configuration, specify the odd slot number.
Program Name: n-s Fixed character string
n: Node number
s: Slot number
Fixed character string: Enter the character string determined for the subsystem
([Connection Device] specified in the I/O Parameter Builder).
Specify S_MODBUS for the Modbus communication package.
IM 32S05B10-21E
C1-24
l Size
Set the assigned size (data length) from the beginning address of the area allocated in the
Buffer field. The Size field can be entered only when the Element field is an odd number
address.
Input range: 1 to 1000
If an odd number is specified as the size, the odd number will be displayed, but the actual size to
be allocated will correspond to an even number being the sum of the specified odd number and
1.
An error will occur in the following conditions:
The specified size exceeds the range allocated in the Buffer field.
The total sum of sizes assigned to all discrete inputs/outputs, when the Data Type is
discrete input or output, exceeded 256 words.
An odd value is specified when the Data Type is 32-bit analog input or output.
After a size has been specified, moving to the next setting item will display asterisks (*) in the
subsequent Size, Port, Station Number, Device Address, Data Type and Reverse fields
corresponding to the specified size, where there is no error in the defined items. These asterisks
indicate that data of the specified size has been assigned. The fields showing asterisks do
not accept new settings. Deleting a Port, Station Number, Device Address, Data Type or
Reverse entry indicated by asterisks will not delete the asterisks in the field.
If a Size is deleted, the items defined in the data of the assigned size (Port, Station, Device
address, Data type, Reverse, Input Processing at Fault, Input Value at Fault) as well as asterisks
in the applicable fields will be deleted, and these fields can now accept new settings.
If a Size is changed, the asterisks will also be changed. If the Size is changed to a smaller
value, the items that have been set in the data corresponding to the size decremented will be
deleted.
Table
Element
Buffer
Program Name
Size
Port
Device
Address
Station
Data Type
Reverse
%WW2001
1-3S_MODBUS 2
A10012
Input (Discrete) No
%WW2002
%WW2003
%WW2004
%WW2005
l Port
Specify the port of the subsystem communication module to be used. Select 1 or 2. The default is
1.
l Station
Specify the station number for the subsystem. Select a value between 0 and 255. The specifiable
values vary depending on the subsystem. The default is 1. Specify a value between 1 and 255 for
the Modbus communication package.
IM 32S05B10-21E
C1-25
l Device Address
Specify the content of data to be acquired from the other device, using a combination of the
communication method used by the subsystem and the beginning data address.
l Data Type
Specify the type of subsystem data. A list of selectable data types is given below:
1: Input (16-Bit Signed) (Analog input (16-bit signed integer))
2: Input (32-Bit Signed) (Analog input (32-bit signed integer))
3: Input (16-Bit Unsigned) (Analog input (16-bit unsigned integer))
4: Input (32-Bit Floating) (Analog input (32-bit floating))
5: Output (16-Bit Signed) (Analog output (16-bit signed integer))
6: Output (32-Bit Signed) (Analog output (32-bit signed integer))
7: Output (16-Bit Unsigned) (Analog output (16-bit unsigned integer))
8: Output (32-Bit Floating) (Analog output (32-bit floating))
9: Input (Discrete) (Discrete input)
10: Output (Discrete) (Discrete output)
If discrete input or output is selected, whether or not the total sum of Sizes assigned to all
discrete inputs/outputs is 256 words or less is checked. If the total size exceeds 256 words, an
error will occur. If 32-bit analog input or output is selected, whether or not the corresponding
Size field contains an even number is checked. If an odd number is entered, an error will occur.
l Reverse
Specify whether or not to store subsystem data in the SCS after reversing the order of bits/words
comprising the data.
The selectable items vary depending on the data type specified in the Data Type field.
The combinations of reverse specifications that can be selected for different data types are
shown below:
32-bit analog input or output:
Fixed to 2: No.
IM 32S05B10-21E
C1-26
Description
Hold
Table
Description
Hold
Fixed Value
Input range:
IM 32S05B10-21E
C1-27
SCI_R SCI_B S
ALARM001_CLS1@SYSiFBD
ALARM001_CLS2@SYSiFBD
ALARM001_CLS3@SYSiFBD
ALARM001_SUM@SYSiFBD
ALARM002_CLS1@SYSiFBD
ALARM002_CLS2@SYSiFBD
ALARM002_CLS3@SYSiFBD
ALARM002_SUM@SYSiFBD
ALARM003_CLS1@SYSiFBD
ALARM003_CLS2@SYSiFBD
ALARM003_CLS3@SYSiFBD
ALARM003_SUM@SYSiFBD
ANLGI001_HHH@HISIFFBD
ANLGI001_HTRP@HISIFFBD
ANLGI001_LLL@HISIFFBD
ANLGI001_LTRP@HISIFFBD
ANLGI001_SOER@HISIFFBD
ANLGI002_HHH@HISIFFBD
ANLGI002_HTRP@HISIFFBD
ANLGI002_LLL@HISIFFBD
ANLGI002_LTRP@HISIFFBD
ANLGI002_SOER@HISIFFBD
ANLGI003_HHH@HISIFFBD
ANLGI003_HTRP@HISIFFBD
ANLGI003_HTRP@HISIFFBD
Element
Data Type
Variable Name
Type
C010408E.ai
The items set in the Comm. I/O Wiring tab are as follows:
Element:
Read only
Data Type:
Read only
Variable Name
Type:
Read only
Comment:
Read only
l Element
An element or elements (%WB) is/are assigned automatically in accordance with the element
number (%WW) for which Buffer and Size have been set in the Comm. I/O Definition tab as
well as the applicable Data Type field.
Example:
If the selected element is %WW2001, Size is 4 words, and Data Type is [Input (16-Bit
Signed)], the following elements will be assigned automatically.
l Data Type
The data type specified in the Comm. I/O Definition tab is displayed.
The Data Type field is read only.
IM 32S05B10-21E
C1-28
l Variable Name
You can perform any of the following alternative steps to set an instance name of Subsystem
Communication FB (SCI_B, SCI_I, SCI_R, SCO_B, SCO_I, SCO_R) for each variable.
Enter the variable name directly.
Double-click on a variable name displayed in the Variable Name tab in the left pane.
Drag a variable name from Dictionary View and drop it into the Variable Name text box.
Table
Scope
Description
SCIB1
Global
Global variable
SCIB2@PROG1
PROG1
FB01.SCIB3
Global
FB01.SCIB3@
PROG1
PROG1
FB01.FB2.SCIB3
Global
The table below lists the combinations of variable types and data types specified in the Comm.
I/O Definition tab. The types of the variable are the Subsystem communication FBs.
Table Data Types and Specifiable Variable Types
Data type
Variable type
SCI_I
SCI_R
SCO_I
SCO_R
Discrete input
SCI_B
Discrete output
SCO_B
l Type
The selected variable type is displayed. The type of the variable is the Subsystem communication
FB.
The Type field is read only.
l Comment
A comment for the selected variable is displayed.
The Comment field is read only.
IM 32S05B10-21E
C1-29
n Overview
Forcing of subsystem communication data is performed in the Communication I/O Lock
window. Forcing operation cannot be performed in the Dictionary View or Multi Language
Editor.
Forcing can be performed when the SCSs security level is 1 or below.
Communication with subsystems will continue even after subsystem communication data is
locked.
It is not possible to lock a given set of communication data. All data of a module or all input
data or output data of a module will be locked simultaneously.
Data status values are changed for each communication definition. Data values are
changed for each communication data item.
In the SCS, forcing of subsystem communication data is processed using a completely
different mechanism from one used for forcing of I/O variables. Forcing of subsystem
communication applies only to the communication I/O data area via the communication I/O
data management function.
Forcing
(communication input data)
Referencing of communication
I/O data
Forcing
(communication output data)
Logic
Subsystem
communication
output FBs
Mapping elements
(%WB)
Subsystem
C010501E.ai
C1-30
Scope
Subsystem communication
Subsystem communication
inputs
Subsystem communication
outputs
IM 32S05B10-21E
C1-31
TIP
Communication data correspond to the wired subsystem communication I/O FBs. Just like I/O variables,
subsystem communication I/O FBs consist of data values and statuses. Unlike I/O variables, however, data
statuses of subsystem communication I/O FBs indicate the statuses of communication with subsystems.
Communication definition is a unit of communication between the subsystem communication module and a
subsystem. A communication definition is a block of data of the same data type specified by the Size, among
the data included in the Buffer assigned to each communication module specified by the Program Name in the
Communication I/O Builder.
Table
Subsystem communication
Communication is not affected.
IM 32S05B10-21E
C1-32
SCS Manager
Launch
Launch
Engineering
Maintenance
Builders
Analyzers
Inter-SCS Communication
Lock Window
Launch
Controller
Save
Operation
Marks
Download
Operation
Marks
Tools
SCS Maintenance
Support Tool
Communication I/O
Lock Window
C010601E.ai
IM 32S05B10-21E
C1-33
Locking/
setting of values
Locking/
setting of values
SCS
Application logic
execution function
Subsystem
communication
I/O FBs
Subsystem
communication function
I/O variables
Process data I/O function
Communication I/O
data management
Input/output
Send/receive
Subsystem
Detecting element,
final control element
C010602E.ai
l Setting of Values
Values can be set when subsystem communication input or output data is locked.
Logical data and physical data are displayed for each value.
A data value can be set for each communication data item. A data status can be set for each
communication definition.
When the SCS project target name is SCS_SIMULATOR, it is possible to set values to multiple
communication data together.
IM 32S05B10-21E
C1-34
Check if the SCS security level is 0 or 1 using the SCS security level operation function.
2.
3.
4.
Select [Communication I/O Lock Window] from the Maintenance Launcher menu.
The Communication I/O Lock window appears.
IMPORTANT
The Communication I/O Lock window cannot be started while Build or Download is running
in SCS Manager.
Multiple Communication I/O Lock windows cannot be launched simultaneously regardless
of whether or not the windows are for the same SCS project or different SCS projects.
The Communication I/O Lock window will be forcibly closed when SCS Manager is closed
or a different SCS project is opened.
OK
C010603E.ai
To unlock the applicable communication module, start the Communication I/O Lock window
again and perform the necessary operation.
IMPORTANT
If you commenced an on-line change download when the Communication I/O Lock window
is open, close the Communication I/O Lock window after the on-line change download is
completed.
If the Communication I/O Lock window remains open after completion of an on-line change
download in which a subsystem communication database was changed, a database discrepancy
error may occur when the displayed data is refreshed subsequently. When this error occurs, a
message prompting you to re-launch the Communication I/O Lock window will be displayed.
IM 32S05B10-21E
C1-35
C1.6.1
This section describes the window structure and components of the Communication I/O
Lock window.
The structure of the Communication I/O Lock window is shown below.
Title bar
Menu bar
MODULE LIST
L D
Module
3-1 ALR111
3-1 ALR111
3-3 ALR111
3-3 ALR111
*****SCS_TARGET*****
Inputs/Outputs
I/O
I
O
I
O
Toolbar
Comment
Comment
Comment
Comment
Comment
All Data
Definition
%WB L D Instance Logical Value Physical Value Co
3-1S_MODBUS:001200101
DI0000.V TRUE
TRUE
Port1:DI
DI0000.STS GOOD
GOOD
200102
DI0001.V TRUE
DI0001.STS GOOD
TRUE
GOOD
TRUE
GOOD
TRUE
GOOD
200105
DI0004.V TRUE
DI0004.STS GOOD
TRUE
GOOD
TRUE
GOOD
TRUE
GOOD
TRUE
GOOD
3-1S_MODBUS:002200301
Port1:I32 Input
I32000.V
1
I32000.STS GOOD
1
GOOD
200501 I32001.V
2
I32001.STS GOOD
0
GOOD
200701
I32002.V
Status bar
IM 32S05B10-21E
C1-36
The components of the Communication I/O Lock window are described below.
n Title Bar
On the title bar, besides window name and project name, the SCS status is also displayed.
SCS_TARGET:
For logic simulation test, SIMULATION will be displayed in the position of SCS status.
n Menu Bar
The following menus are provided on the menu bar:
[File] menu
[Edit] menu
[Lock] menu
[Option] menu
The menu items provided on each menu are explained below.
Table
[File] Menu
Menu item
Description
Imports the values for setting all together to communication data from a file.
Exports the values for setting all together to communication data to a file.
Exit
*1:
Table
[Edit] Menu
Menu item
Description
Cut (*1)
Deletes the selected character string and copies it onto the clipboard
Copy (*1)
Paste (*1)
Delete (*1)
Select All
Selects all displayed modules (same action as pressing the [Ctrl] key and [A] key
together).
*1:
Table
[Lock] Menu
Menu item
Description
Lock Modules
Unlock Modules
*1:
IM 32S05B10-21E
C1-37
Table
[Option] Menu
Menu item
INT
Numerical Display
REAL
Description
Decimal
Hexadecimal
1.234E+12
Exponential notation
12.34567
123.4567
1234.567
12345.67
123456.7
All Modules
Selected Modules
n Toolbar
The following buttons are provided on the toolbar.
Table
Toolbar Buttons
Button
Description
(*1)
Imports the values for setting all together to communication data from a file.
Same as choosing [Import Values] from [File] menu.
(*1)
Exports the values for setting all together to communication data to a file.
Same as choosing [Export Values] from [File] menu.
Locks all modules selected.
Same as choosing [Lock Modules] from [Lock] menu.
Unlocks all modules selected.
Same as choosing [Unlock Modules] from [Lock] menu.
(*1)
(All Modules)
(Selected Modules)
*1:
IM 32S05B10-21E
C1-38
Description
Module
Subsystem communication module name (with node number (n) and slot number (s))
I/O
Signal direction of the subsystem communication module ([I]: input, [O]: output)
Comment
Meaning
(No symbol)
(red)
? (black)
IM 32S05B10-21E
C1-39
Meaning
(No symbol)
(yellow)
(red)
? (black)
l Filtering
Subsystem communication modules can be filtered based on input/output classification by using
the drop-down list box.
Table
Menu item
Operation
Inputs/Outputs
Both the input and output lines of communication definitions are displayed.
Inputs
Outputs
l Pop-up Menu
Click the right mouse button on the Communication Module List View to display the pop-up
menu.
The menu items in the pop-up menu are shown below.
Table
Menu item
Select All
Description
Selects all displayed modules.
Same as choosing [Select All] from [Edit] menu and same action as pressing
the [Ctrl] key and [A] key together.
IM 32S05B10-21E
C1-40
Description
Definition
Communication definition
%WB
Instance
Logical Value
Physical Value
Comment
*1:
Displayed and editable only when the SCS project target name is SCS_SIMULATOR.
l Communication Definition
A communication definition (for Modbus communication package) is shown in the following
format:
n-sS_MODBUS:c
Portp:DataType
n:
Node number
s:
Slot number
c:
p:
Port number
DataType:
Data type
- DI:
Discrete input
- DO:
Discrete output
- I16 Input:
- I32 Input:
- U16 Input:
- R32 Input:
- I16 Output:
- I32 Output:
- U16 Output:
- R32 Output:
TIP
C1-41
Communication definition numbers specify communication definitions defined in one subsystem communication
module. A communication definition is a block of data of the same data type specified by the Size, among
the data included in the Buffer assigned to each communication module specified by the Program Name in
the Communication I/O Builder. Communication definition numbers are sequential numbers (starting from 1)
assigned for each subsystem communication module.
Meaning
(No symbol)
(red)
? (black)
Meaning
(No symbol)
(red)
? (black)
l Instance Name
The instance name (data value (V) and data status (STS)) of the subsystem communication I/O
FB wired to the %WB is displayed.
IM 32S05B10-21E
C1-42
l Filtering
The communication data to be displayed can be filtered using the drop-down list box.
Table
Operation
All Data
Locked Data
Unlocked Data
l Pop-up Menu
Click the right mouse button on the Communication Data List View to display a pop-up menu.
However, this is available only when the SCS project target name is SCS_SIMULATOR.
The items on the pop-up menu are as follows:
Table
Description
Cut
Copy
Paste
Delete
Select All
Set .V=TRUE
Set .V=FALSE
Clear .V
Set .STS=GOOD
Set .STS=BAD
Clear .STS
IM 32S05B10-21E
C1-43
n Status Bar
The status bar shows the following information relating to the subsystem communication
modules shown in the Communication Module List View.
Input Selected: Number of selected input lines/number of all input lines
Output Selected: Number of selected output lines/number of all output lines
IM 32S05B10-21E
C1-44
C1.6.2
The following operations can be performed in the Communication I/O Lock window:
Lock all input data and/or all output data for each subsystem communication module
Unlock all input data and/or all output data for each subsystem communication
module
Set data values and data status for locked data
Set all input data and/or all output data for each subsystem communication module
(only in SCS Simulation Test).
Performing an all lock or all unlock operation by selecting input and output of a given
module will lock or unlock all subsystem communication data of the module.
You can also specify locked data and set values individually. A data value (V) is set
for each communication data item, while a data status value (STS) is set for each
communication definition.
In SCS Simulation Test, you can set values all together to the communication data for the
communication modules.
IMPORTANT
All of the above operations cannot be executed while Build or Download is running.
IM 32S05B10-21E
C1-45
In the Communication Module List View, select the subsystem communication module you
want to perform all lock for.
2.
In the Communication Data List View, check for discrepancy between the logical data and
physical data of each data value and status of the selected subsystem communication
module to confirm that locking will not cause any problem.
3.
Select [Lock Modules] from the [Lock] menu, or click the [Lock] button in the toolbar.
4.
When the confirmation dialog box appears, click [OK] to perform the lock. All selected input
and/or output data will be locked. To cancel the operation, click [Cancel].
lock Modules
Are you sure to lock modules?
OK
Cancel
C010605E.ai
In the Communication Module List View, select the subsystem communication module you
want to perform all unlock for.
2.
In the Communication Data List View, check for discrepancy between the logical data and
physical data of each data value and status of the selected subsystem communication
module to confirm that unlocking will not cause any problem.
3.
Select [Unlock Modules] from the [Lock] menu, or click the [Unlock] button in the toolbar.
The confirmation dialog box appears.
Unlock Modules
Are you sure to unlock modules?
OK
Cancel
C010606E.ai
4.
Click [OK] to perform the unlock. Click [Cancel] to cancel the operation.
5.
If [OK] is clicked in step 4, the reconfirmation dialog box will appear if there is a discrepancy
between logical data and physical data for any one of the communication data items
corresponding to the communication definitions of the subsystem communication module to
be unlocked.
Unlock Modules
Logical Value(s) and Physical Value(s) are not equal.
Are you sure to unlock modules?
OK
Cancel
C010607E.ai
6.
Click [OK] to perform the unlock. Click [Cancel] to cancel the operation.
IM 32S05B10-21E
C1-46
IMPORTANT
Setting values to communication data cannot be executed while Build or Download is running.
Double-clicking any field between %WB and Physical Value for locked data in the
Communication Data List View will display the dialog box in which you can set the data value or
status of the communication data in the clicked line.
If the upper part of the line showing a data value is double-clicked, the Write data value dialog
box appears. If the lower part of the line showing a data status is double-clicked, the Write data
status dialog box appears.
Set values in these dialog boxes. A data value is set for each communication data item, while a
data status is set for each communication definition. Once a data status value is set, the value
will be reflected in all data statuses within the same communication definition.
Write data value
DI0000.V
0
TRUE
FALSE
1
Cancel
C010608E.ai
256
Write
Cancel
C010609E.ai
BAD
GOOD
1
Cancel
C010610E.ai
IM 32S05B10-21E
C1-47
When the Write data value dialog box or Write data status dialog box opens for a discrete input or
output, the button corresponding to the current value is already selected.
With an analog input or output, the current value is displayed when the Write data value dialog
box opens. Whether logical data or physical data is displayed is determined based on which of
the two values can be set at the time. Logical data is displayed if the logical data can be set, and
physical data is displayed if the physical data can be set. The initial displays of the Write data
value dialog box are summarized below.
Table
Data
Locked
Not locked
Logical data
Logical data
Logical data
Logical data
Data value
Physical data
Logical data
Logical data
Logical data
Data value
IM 32S05B10-21E
C1-48
IMPORTANT
Setting values to communication data cannot be executed while Build or Download is running.
On Communication Module List View, choose a communication module that you want to set
the values for.
2.
Choose [Set Values] from [Lock] menu or click Set Values button on the toolbar so as to
display Set Values dialog box.
3.
Click [OK] for setting values. All the values entered in the Set Value items will be set to the
communication data. If no values are entered, the communication data will not be changed.
You can cancel the setting by clicking [Cancel].
Choose [Export Values] from [File] menu, or click the Save (Export Values) button on the
toolbar so as to display a dialog box for selecting files.
2.
Specify the CSV file for saving the setting values and then click [Save]. The communication
data values and data statuses for all the communication modules on the Communication
Module List View will be exported to the file.
IMPORTANT
Do not edit the exported file if you want to import the file later.
IM 32S05B10-21E
C1-49
IMPORTANT
Do not import any file other than the file exported from Communication I/O Lock window.
Choose [Import Values] from [File] menu, or click the Open (Import Values) button on the
toolbar so as to display a dialog box for selecting files.
2.
Choose the CSV file that contains the setting values and then click [Open]. The
communication data values and data statuses of all the communication modules on the
Communication Module List View will be displayed with the data values and data statuses
imported from the file.
If the values of data statuses differ among communication data in the same communication
definition in the CSV file, a warning message is displayed and the data status value
of the first communication data in the same communication definition is set to all the
communication data within the same communication definition.
IM 32S05B10-21E
C1-50
Lock
Not required.
If a setting is changed while an error occurs, input values will change. Subsystem communication outputs are not affected.
Change the application logic in SCS Manager, and build the application logic.
2.
3.
4.
5.
Lock the inputs/outputs of subsystem communication data in accordance with what you
want to change.
6.
7.
8.
SEE
ALSO
IM 32S05B10-21E
C1-51
ALSO
For details on whether addition, deletion and other operations relating to subsystem communication modules can
be performed, see the following:
5.2, List of Applicable Items for On-line Change in the Engineering Guide (IM 32S01C10-21E)
IM 32S05B10-21E
C1-52
l Changing a Wiring
Before performing an on-line change download, the subsystem communication data of
the target subsystem communication module needs to be locked. To change the wiring
of a subsystem communication I/O FB between two subsystem communication modules,
subsystem communication data needs to be locked for the subsystem communication module
that contains the wired communication data before the change, as well as the subsystem
communication module that will contain the wired communication data after the change. If the
data of both modules is not locked, subsystem communication data will be immediately input
to the application logic after the on-line change download is completed, and outputs from the
application logic will also be output to subsystems immediately after the download.
Each subsystem communication module will restart after the on-line change download is
completed. Once the subsystem communication module has been restarted, unlock the
subsystem communication data of the module.
IM 32S05B10-21E
C2-1
This section describes the communication specifications of the ALR111 RS-232C serial
communication module and ALR121 RS-422/RS-485 serial communication module.
Description
STATUS
Hardware ready
ACT
Operating normally
DX
Dual-redundant configuration
SND1, SND2
RCV1, RCV2
Signal
Name
CD
Carrier Detect
RD
Receive Data
SD
Send Data
ER
SG
Signal Ground
DR
RS
Request to Send
CS
Clear to Send
Output ON if normal.
Not used
IM 32S05B10-21E
C2-2
Description
STATUS
Hardware ready
ACT
Operating normally
DX
Dual-redundant configuration
SND1, SND2
RCV1, RCV2
Name
TX+
TX-
RX+
RX-
SG
Signal Ground
IM 32S05B10-21E
C2-3
l RS-232C Cable
This cable is used to connect an ALR111 with a subsystem.
AKB163: RS-232C cable (for ALR111 to FA500 connection)
l RS-422/RS-485 Cable
This cable is used to connect an ALR121 with a subsystem.
AKB164: RS-422/RS-485 cable (for ALR121 to FA-M3 connection)
IM 32S05B10-21E
C3-1
Application logic
execution function
Modbus PLC
C030001E.ai
TIP
Mounting a communication module which is downloaded the Modbus communication package of CENTUM FCS
in an SCS will not enable Modbus communication. You need to perform the IOM download for downloading the
Modbus communication package of SCS.
IM 32S05B10-21E
C3-2
n Communication Capacity
The table below summarizes the Modbus-specific communication capacity applicable to
communication between a Modbus PLC and an SCS.
Table
Maximum capacity
Remark
1,000 words
(1 word = 16 bits)
125 words
TIP
Modbus PLCs process data in units of 16 bits. Simultaneity of 32-bit data depends on the application software
used on the Modbus PLC side. To assure simultaneity of communication data in units of 32 bits, the application
software on the Modbus PLC side needs to set 32-bit data within the same control period.
IM 32S05B10-21E
C3-3
n Transmission Specification
The transmission specifications for subsystem communication with a Modbus PLC are
summarized below.
Table
Transmission Specification
Item
Interface
Description
Remarks
ALR111
ALR121 (*1)
Transmission method
Half-duplex
Synchronization method
Start-stop synchronization
Baud rate
Transmission protocol
Transmission code
Binary
Data type
Control line
Time monitoring
Text frame
Start bit
Fixed to 1.
Data bit
Parity bit
Stop bit
RS control
Yes, [No]
DR check
[Yes], No
CD check
Yes, [No]
1000 ms
(*1)
(*1)
None
End character
None
XON/XOFF control
None
Response timeout
0 to 99 sec [4 sec]
Communication retry
0 to 99 [1]
1 sec
Option 1
0 to 5
Specification of recovery
communication method
Option 2
0, [1]
(*2)
Option 3
Option 4
0
Note: The recommended settings are shown in [ ].
*1:
With Modbus, the reception inter-character timer is used to detect completion of reception. Thus, setting a longer time for
the reception inter-character timer will delay the time to reception completion. This timer should be set to around 10 ms
(corresponding to the time required for sending 10 characters) at 9600 bps.
*2:
Wind-up specification without readback.
0: Valid
1: Invalid
IMPORTANT
When performing subsystem communication with a Modbus PLC, always specify 8 as the data
bit length, and specify 1 as the stop bit length. If any other value is specified, a communication
error will occur.
IM 32S05B10-21E
C3-4
Description
Remarks
A3B0
No response
A3B1
(*1)
A3B2
(*1)
A3B3
(*1)
A3B4
(*1)
A3B5
(*1)
A3B6
(*1)
A3B8
(*1)
A3B9
(*1)
A3BA
(*1)
A3C0
CRC-16 error
(*1)
A3C1
(*2)
A3C2
(*2)
A3C3
(*2)
A3C4
(*2)
A3C5
(*2)
A3C6
(*2)
A3D1
(*2)
A3D2
(*2)
A3D3
(*2)
A3D4
(*2)
A3D5
(*2)
A3D6
(*2)
A3D7
(*2)
A3D8
(*2)
A3D9
(*2)
A3DA
(*2)
A3DB
(*2)
A3DC
(*2)
A3DD
(*2)
A3DE
(*2)
A3DF
(*2)
*1:
*2:
Definition error for ALR111/ALR121. If this error occurs, no communication can be performed to the Modbus PLC.
This is an error when an error message was received from the Modbus PLC.
IM 32S05B10-21E
Table
C3-5
Description
Remarks
A3E0
(*2)
A3E1
(*2)
A3E2
(*2)
A3E3
(*2)
A3E4
(*2)
A3E5
(*2)
A3E6
(*2)
A3E7
(*2)
A3E8
(*2)
*2:
This is an error when an error message was received from the Modbus PLC.
IM 32S05B10-21E
C3-6
This section describes how to connect a serial communication module with a Modbus
PLC using a cable.
IMPORTANT
The length of the RC-232C cable connecting the ALR111 to the modem, and one connecting the
modem to the Modbus PLC, shall not exceed 15 m.
l Modem Connection
An example of cable connection where an ALR111 is connected to a Modbus PLC via a modem
is shown below.
ALR111
SD 3
2 SD
RD 2
3 RD
RS 7
4 RS
CS 8
5 CS
CD 1
8 CD
DR 6
6 DR
ER 4
20 ER
SG 5
7 SG
Modem
1 FG
Shielded cable
Protective ground
(100 ohm or less)
C030201E.ai
Figure Cable Connection of ALR111 and Modbus PLC via Modem (RS-232C D-sub, 25-pin)
IM 32S05B10-21E
C3-7
ALR111
SD 3
2 SD
RD 2
3 RD
RS 7
4 RS
CS 8
5 CS
CD 1
8 CD
DR 6
6 DR
ER 4
20 ER
SG 5
7 SG
Modbus
PLC
1 FG
Shielded cable
Protective ground
(100 ohm or less)
C030202E.ai
Figure Direct Cable Connection of ALR111 and Modbus PLC (RS-232C D-sub, 25-pin)
ALR111
SD 3
3 SD
RD 2
2 RD
RS 7
7 RS
CS 8
8 CS
CD 1
1 CD
DR 6
6 DR
ER 4
4 ER
SG 5
5 SG
Modbus
PLC
Connected to
connector shell
Shielded cable
Protective ground
(100 ohm or less)
C030203E.ai
Figure Direct Cable Connection of ALR111 and Modbus PLC (RS-232C D-sub, 9-pin)
SEE
ALSO
For the specific connection between an ALR111 (RS-232C) and each Modbus PLC model, see the users manual
for the applicable Modbus PLC.
IM 32S05B10-21E
C3-8
SEE
ALSO
For the specific connection between an ALR121 (RS-422/RS-485) and each Modbus PLC model, see the users
manual for the applicable Modbus PLC.
IM 32S05B10-21E
C3-9
This section describes the Modbus PLC devices that can be accessed from SCSs.
Internal data of a Modbus PLC are called devices. Devices include bit devices and word
devices, as specified below.
Bit device
Data in which each bit has a meaning. An input relay is a bit device.
Word device
Data in which each word (1 word = 16 bits) has a meaning. A holding register is a
word device.
Modbus PLCs also have devices called special coil and communication status.
n Accessible Devices
To access Modbus PLC devices, set [Device Address] and [Size] in the Communication I/O
Builder.
With Modbus PLCs, [Device Address] is set in the following format:
<Function code> + <Device type> + <Address within device>
To specify input relays 10012 to 10015 in the Communication I/O Builder, for example, set
A10012 in [Device Address] and 1 in [Size]. A of A10012 indicates a function code, 1 indicates
a device type, and 0012 indicates an address within device.
The table below lists the Modbus PLC devices accessible from SCSs, as well as the
corresponding addresses and Modbus protocol function codes.
Table
Bit Devices
Modbus protocol function
code (hexadecimal)
Address
Device
Function
code
A
B
Coil
01
0
XXXX
-
Y
Input relay
XXXX
A
Link relay (*1)
B
X
*1:
02
12
XXXX
-
Y
Step status (*1)
Read
XXXX
17
Write
0F
05
0F
05
1D
19
1D
19
-
These are Memocon-SC GL60S devices and not available on other models.
IM 32S05B10-21E
Table
Word Devices
Modbus protocol function
code (hexadecimal)
Address
Device
Function
code
Input register
XXXX
Read
Write
04
10
03
B
C
Holding register
10
-
Z
A
C
X
1E
13
C
1E
-
Z
A
XXXX
14
15
R
1F
-
1B
1F
20
B
C
X
16
A
20
-
Z
A
1C
20
XXXX
Y
4-byte register
1B
1F
XXXX
Extended register
(*1)
1F
B
C
1A
1E
1A
1E
XXXX
Y
Elapsed step time
(*1)
06
10
B
Constant register
(*1)
06
10
XXXX
*1:
C3-10
1C
20
XXXX
04
These are Memocon-SC GL60S devices and not available on other models.
Table
Other Devices
Modbus protocol function
code (hexadecimal)
Address
Device
Special coil
Communication
status
Function
code
Read
Write
SP001
07
STSXXX
IM 32S05B10-21E
C3-11
Function code
Device
Word device
All data for one communication All data for one communication
Yes
definition
definition
Bit device
Yes
Word device
Yes
Word device
Yes
Bit device
Word device -
Bit device
SEE
ALSO
Readback
All data for one communication All data for one communication
Yes
definition
definition
Write
Bit device
A
Read
In units of 1 bit
No
Word device -
In units of 16 bits
No
Word device -
In units of 32 bits
No
SEE
ALSO
The supported function codes, accessible devices, sizes and other details will vary depending on the Modbus
PLC model. For details, see the users manual for the applicable Modbus PLC.
IM 32S05B10-21E
C3-12
IMPORTANT
With a dual-redundant configuration based on ALR111/ALR121s, it is always necessary to
perform readback when data is written to the Modbus PLC. Writing of data without readback is
not supported in a dual-redundant configuration.
IM 32S05B10-21E
C3-13
This section describes the formats in which Modbus PLC data that has been read is
stored in the applicable SCS.
The storage formats for different Modbus PLC devices, such as bit devices, word devices,
special coils and communication statuses, are explained.
n Bit Devices
When 16 x m (m = 1, 2, ...) numbers of bit devices are read from address n in the Modbus PLC,
the applicable Modbus PLC data will be stored in the SCS as follows.
In the Communication I/O Builder, specify m in [Size]. You can also reverse the order of bits in
units of 16 bits.
16 bits
n n n n n n
+ + + + + +
15 14 13 12 11 10
n
+
9
n
+
8
n
+
7
n
+
6
n
+
31
n+16(m-1)+15
n
+
5
n
+
4
n
+
3
n
+
2
n
+
1
m=1
n
+
16
m=2
n+16(m-1)
C030401E.ai
IM 32S05B10-21E
C3-14
n Word Devices
l 16-bit Data
If m numbers of word devices are read from address n, the applicable word registers (16 bits) in
the Modbus PLC will be stored in the SCS as follows.
16 bits
Content of register n
Content of register n+1
l 32-bit Data
Word registers (16 bits) in the Modbus PLC are stored in the SCS in the order of registers, as
shown below. If 32-bit data is defined as the data type, however, two word registers are combined
and regarded as 32-bit data.
If word reversing is not specified in the SCS (default), the first register is recognized as the upper
word, while the next register is regarded as the lower word.
16 bits
Content of register n
IM 32S05B10-21E
C3-15
If 32-bit data is stored in word registers in the Modbus PLC, depending on the model of the
Modbus PLC the data may be stored in pairs of two 16-bit word registers in the order of lower
word and upper word, as shown below. This word order (16 bits) is opposite from the order in the
SCS.
16 bits
Content of register n
Figure Order of 32-bit Data in Modbus PLC (Opposite Order from SCS)
If the above Modbus PLC data is to be stored in the SCS, the data order can be reversed in units
of words (16 bits) by specifying [Reverse] in the Communication I/O Builder.
n Special Coils
Special coils in Modbus PLCs have a data length of 1 word (16 bits). Special coils are stored in
the SCS as follows.
By specifying [Reverse] in the Communication I/O Builder, you can reverse the order of bits.
(a) When bit reversing is not specified
15
n
+
7
n
+ n
1
15
n
n +
1
n
+
7
IM 32S05B10-21E
C3-16
n Communication Status
Modbus PLC communication status STSnnn indicates the status of communication with each
station corresponding to a station number of nnn to nnn+15.
The communication status is specified as follows:
Of the stations defined in the Communication I/O Builder, those communicating normally are
indicated as 0.
Of the stations defined in the Communication I/O Builder, those experiencing an error are
indicated as 1.
Stations not physically performing communication (not defined in the Communication I/O
Builder) are indicated as 0.
With communication status, the station number specification in the Communication I/O Builder
has no specific meaning. It is only relevant in that the number corresponding to the youngest
station among the stations physically performing communication should be set. Specify the
address as follows.
Table
Communication Status
Description
Address
STS001
STS017
00
Bit order
Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn.
No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No.
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16
Structure of STS017
15
00
Bit order
Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn. Stn.
No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No.
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
C030404E.ai
IM 32S05B10-21E
C3-17
C3.5.1
The items set in the I/O Wiring View are explained below.
C3.5.2
The items set in the I/O Parameter Builder for the ALR111M/ALR121M are explained below.
n Connection Device
Select S_MODBUS as the name of connection device.
n Transmission Specifications
Set the transmission specifications for each port.
SEE
ALSO
n Options 1 and 2
In Option 1, specify the method of recovery communication. In Option 2, specify the wind-up
action for communication without readback.
SEE
ALSO
For the procedure to specify the recovery communication action in Option 1, see the following:
C3.7, Recovery Communication
For the procedure to specify the wind-up action in Option 2, see the following:
n Operation in Communication without Readback in C3.6, Readback Communication
IM 32S05B10-21E
C3-18
C3.5.3
This section describes the items set in the Communication I/O Builder.
The following items are explained by assuming the use of a Modbus PLC.
Element
Buffer
Program Name
Size
Port
Station
Device Address
Data Type
Reverse
Input Processing at Fault
Input Value at Fault
n Element
Element numbers are displayed to specify the buffer addresses in the communication I/O data
area. The Element field is read only and cannot be set.
n Buffer
Specify the buffer size to be used by the program (Modbus communication package).
The Buffer is a required setting item in the Communication I/O Builder and always needs to be
set.
n Program Name
Set the program name consisting of the node number, slot number and S_MODBUS, as
specified below.
Program name: n-s Fixed character string
n:
Node number
s:
Slot number
n Size
Set the assigned size (data length) from the beginning address set in Device Address.
The Size is a required setting item in the Communication I/O Builder and always needs to be
set.
Specify the size in units of words (16 bits). The setting range is 1 to 125 words.
IM 32S05B10-21E
C3-19
n Port
Set the port of the ALR111/ALR121 to be used.
Port 1 or 2 can be set.
n Station
Set the station number for the Modbus PLC.
The setting range is 1 to 255.
n Device Address
Set the content of data to be acquired from other device as a combination of the communication
method used by the Modbus PLC and the beginning address of data.
The address can be set using 3 to 7 alphanumeric characters as specified below.
Coil:
Input relay:
A1xxxx
Link relay:
Step status:
ASxxxx
Input register:
A3xxxx
Holding register:
Constant register:
A5xxxx
Link register:
Extended register:
4-byte register:
AWxxxx
Special coil:
SP001
Communication status:
STSxxx
SEE
ALSO
IM 32S05B10-21E
C3-20
TIP
If a function code without readback is specified in a dual-redundant configuration, the following problems will
occur:
Outputs that occurred while switching the dual-redundant modules may not be output, or the same outputs
may be output again after switching.
With readback, data is read from the subsystem, compared with the data in the CPU, and then the CPU
data is written to the subsystem if the two data are different.
Without readback, the data in the CPU is compared with the data in the serial communication module
on the control side, without reading data from the subsystem, after which the CPU data is written to the
subsystem and the data in the module is refreshed only when there is a difference between the two data. If
the serial communication module on the control side is normal, the data in the serial communication module
on the standby side is not refreshed, which means that the serial communication module on the standby
side will contain old data when the control switches from the module on the control side to the module on
the standby side. Since the module in this condition cannot accurately compare the data in the CPU with
the data in the module, data cannot be written in this mode without readback.
In Modbus communication, whether or not readback is used is determined by an address function code
specified in the Communication I/O Builder.
If an address without readback is specified, the control will not be switched to the applicable serial
communication module in the dual-redundant configuration for 70 seconds after recovery of the module
from an error.
SEE
ALSO
If the serial communication module on the standby side is reset following a restart, the serial communication
status will not be considered normal for 70 seconds. If a serial communication error occurs during this
period in the serial communication module on the control side, the control will not switch to the module on
the control side.
n Data Type
Set the type of subsystem data.
If 32-bit data is used, simultaneity of communication data needs to be considered.
n Reverse
Set whether or not to reverse the order of bits/words in the SCS from the order of bits/words in
the subsystem.
SEE
ALSO
For details on how subsystem data is stored in the SCS, see the following:
C3.4, Storage Formats of Subsystem Data
IM 32S05B10-21E
C3-21
IM 32S05B10-21E
C3-22
In subsystem communication, output data from subsystems are always read (read back)
even when their data type is output, and each read-back data is compared with the data
to be written. If a difference is found as a result of comparison, the data will be written.
This method is indicated by the phrase with readback. Readback forms the basis of
subsystem communication.
On the other hand, there is another method of subsystem communication in which
subsystem outputs are not read back and data is written only when the previously written
data is different from the data to be written. This method is indicated by the phrase
without readback. This method is used to support one-shot outputs from Modbus PLCs.
Subsystem
communication
period
Output value
on subsystem side
(1)
Read values from the subsystem.
If different from the value to be
written, the new data is written.
(2)
(3)
(4)
(5)
In a dual-redundant configuration, the serial communication module on the standby side reads
back output values to confirm integrity of communication paths and prevent omission of outputs
when the control right is switched.
In the following conditions if readback is enabled, values of subsystems are output from the serial
communication module.
While output from the communication module is disabled following an initial cold start of the
SCS
While the subsystem communication output data is locked.
By locking the communication outputs before an on-line change, the outputs statuses on the
subsystem side can be retained even after restarting the communication module.
IM 32S05B10-21E
C3-23
Output data
(Physical data value
output from subsystem
communication/output
value of the serial
communication module)
Readback
fails.
Output value
on subsystem side
(1)
(2)
(3)
(4)
(5)
C030602E.ai
Figure Operation in Communication with Readback after Recovery from Serial Communication Module
Error
IM 32S05B10-21E
C3-24
Subsystem
communication
period
Communication
to write data
is not
performed.
(2)
(3)
(4)
(5)
IM 32S05B10-21E
C3-25
SEE
ALSO
For the function codes that can be set in [Device Address], see the following:
C3.3, Modbus PLC Devices Accessible from SCSs
Output data
(Physical data value
output from subsystem
communication/output
value of the serial
communication module)
Output value on
subsystem side
(1)
Subsystem
communication
period
(2)
(3)
(4)
(5)
C030604E.ai
Figure Operation in Communication without Readback after Recovery from Serial Communication
Module Error
With readback, output values are read back, so the differences between read-back values and
values to be written are detected and the new data are written even when the output values
have not been written to subsystems. Without readback, however, data will not be written unless
output values on the SCS side are changed. For this reason, the statuses of output values on
the SCS side may remain different from those on the Modbus PLC side after output values have
been changed on the Modbus PLC or the serial communication module has been reset.
IM 32S05B10-21E
C3-26
When Communication Data that Defined without Readback Becomes BAD upon Serial
Communication Error
1
2
3
Perform recovery
communication using a 08
command (loopback check
command)
Perform recovery
communication using a READ
command
Reset the error condition when
recovery communication is
performed
Perform recovery
communication using a WRITE
command of 0 write size
Perform recovery
communication using a WRITE
command based on the data
written immediately before the
error
Do not recognize an error nor
perform recovery communication
*1:
TIP
All communication
definitions for one station
are without readback
Always normal
Applicable only to the recovery communication methods without readback. With readback, recovery communication is performed
using a READ command.
In addition to the above conditions, the status will also change to BAD in the following cases:
Occurrence of a serial communication module error or error in the path from the CPU to the serial
communication module
Occurrence of a range error of station number setting, range error of address setting or other definition error
IM 32S05B10-21E
C3-27
SEE
ALSO
The 08 command may not be usable with certain Modbus PLC models. For details, see the users manual for the
applicable Modbus PLC.
IM 32S05B10-21E
C3-28
IMPORTANT
When Option 1 is set to 4, recovery communication is performed using the data written
immediately before the error. Exercise caution since duplicate operation commands may
occur if the data written immediately before the error contained an operation command to
the Modbus PLC.
On some Modbus PLC models, reading with a READ command may reset the flag. If you
dont want to cause the discrepancy, specify a function code without readback in [Device
Address] of the communication definitions on Communication I/O Builder.
IM 32S05B10-21E
C3-29
This section describes the communication text used in the Modbus protocol.
The communication text contains frames for each command in the Modbus protocol and
a response to the command. The structures of communication text frames are shown
below.
01 Command
01
Response
01
02 Command
02
Response
02
03 Command
03
Response
03
04 Command
04
Response
04
05 Command
05
n-1
Pattern
CRC
Response
05
n-1
Pattern
CRC
06 Command
06
n-1
DATA
CRC
Response
06
n-1
DATA
CRC
07 Command
07
CRC
Response
07
08 Command
08
code
DATA
CRC
Response
08
code
DATA
CRC
0F Command
0F
n-1
m16
Response
0F
n-1
m16
10 Command
10
n-1
Response
10
n-1
CRC
11 Command
11
n-1
CRC
Response
11
CRC
12 Command
12
n-1
Response
12
n-1
m2
m16
DATA 1
n-1
m2
m2
DATA m
m
CRC
CRC
DATA 1
DATA m
m
CRC
CRC
DATA 1
DT
CRC
CRC
DATA 1
n-1
m2
DATA m
m16
n-1
m2
CRC
DATA m
CRC
CRC
m2
DATA m
CRC
CRC
m2
m16
DATA 1
DATA 1
DATA m
CRC
CRC
DATA 1
DATA m
CRC
C030801E.ai
s:
Station number
n:
Relative value from the beginning of the address within device
With holding register 40050, for example, n becomes 49 (40050 - 40001 = 49).
m:
Assigned size set in the Communication I/O Builder (in words)
Pattern: 0xFF00 if ON, or 0x0000 if OFF
IM 32S05B10-21E
C3-30
13 Command
13
Response
13
14 Command
14
Response
14
15 Command
15
Response
15
16 Command
16
Response
16
17 Command
17
Response
17
19 Command
19
n-1
Pattern
CRC
Response
19
n-1
Pattern
CRC
1A Command
1A
n-1
DATA
CRC
Response
1A
n-1
DATA
CRC
1B Command
1B
n-1
DATA
CRC
Response
1B
n-1
DATA
CRC
1C Command
1C
n-1
DATA
CRC
Response
1C
n-1
DATA
CRC
1D Command
1D
n-1
m16
Response
1D
n-1
m16
1E Command
1E
n-1
Response
1E
n-1
1F Command
1F
n-1
Response
1F
n-1
20 Command
20
n-1
Response
20
n-1
n-1
m2
m
DATA 1
n-1
m2
n-1
m2
DATA m
m
DATA m
CRC
CRC
DATA 1
DATA m
m16
CRC
CRC
DATA 1
m
CRC
CRC
DATA 1
n-1
m2
DATA m
m
n-1
m2
CRC
CRC
CRC
DATA 1
DATA m
m2
DATA 1
CRC
DATA m
CRC
DATA m
CRC
DATA m
CRC
DATA m
CRC
CRC
m2
DATA 1
CRC
m2
DATA 1
CRC
m2
DATA 1
CRC
C030802E.ai
s:
Station number
n:
Relative value from the beginning of the address within device
With holding register 40050, for example, n becomes 49 (40050 - 40001 = 49).
m:
Assigned size set in the Communication I/O Builder (in words)
Pattern: 0xFF00 if ON, or 0x0000 if OFF
IM 32S05B10-21E
C3-31
This section explains the time of communication between a serial communication module
and a Modbus PLC.
n Communication Time
The time of communication between a serial communication module and a Modbus PLC is
calculated as the total sum of T1 through T7 shown below.
Start of data
acquisition
Data can
be read
Interpretation of
received message,
storage of data
Creation of
send message
ALR111/ALR121
ALR111/ALR112
modem
Modbus PLC
modem
Interpretation/
execution of
message, creation of
response message
Modbus PLC
Time
T1
T2
T3
T4
T5
T6
T7
C030901E.ai
T1:
T2:
T3:
T4:
T5:
T6:
T7:
Figure Timing Chart for Serial Communication Module and Modbus PLC Communication
TIP
Since each port performs communication independently, the sum of times required for all communication
definitions set for each port becomes the data refresh time of the port. For example, if definitions 1 and 2 are
set for port 1, the communication period of port 1 is calculated as (Communication time for definition 1) +
(Communication time for definition 2).
IM 32S05B10-21E
C3-32
Fixed to 1 bit.
Data bits:
Parity bit:
Stop bit:
Fixed to 1 bit.
Baud rate:
Table
Device
Read
Send
Write
Response
Send
Response
Coil
Fixed to 8.
Fixed to 8.
Input relay
Fixed to 8.
Holding register
Fixed to 8.
5 + 2 x Number of registers
9 + 2 x Number of registers
Fixed to 8.
Input register
Fixed to 8.
5 + 2 x Number of registers
*1:
IM 32S05B10-21E
Rev-1
Revision Information
Title
: Open Interfaces
Manual No. : IM 32S05B10-21E
Dec. 2009/3rd Edition/R2.03 or later*
B1.1
B2.2
B3
C1.2
C1.3
C1.6
*: Denotes the release number of the software corresponding to the contents of this users manual. The
revised contents are valid until the next edition is issued.
Added the description of operation when a serial communication module is added online.
Deleted the TIP on variable names (error correction).
Changed the description of response time.
Added the diagnostic messages generated when a serial communication module is added online.
Added the description about the case when the subsystem communication module is changed from
single to dual-redundant configuration.
Added the description of operation when a subsystem communication module is added/removed
online.
Changed Figure: Positioning of Communication I/O Lock Window in SENG.
IM 32S05B10-21E