Open Interfaces: User's Manual

Users
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.
Media No. IM 32S05B10-21E (CD)

3rd Edition : Dec. 2009 (YK)
All Rights Reserved Copyright 2008, Yokogawa Electric Corporation
IM 32S05B10-21E
3rd Edition : Dec.22,2009-00
ii
ProSafe-RS Document Map

Safety System
Safety Manual
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
Workbench Users Guide
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
2nd Edition : Dec.15,2008-00
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.
Indicates that main switch is ON.
Indicates that main switch is OFF.
IM 32S05B10-21E
1st Edition : May 30,2008-00
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 Warning and Disclaimer

The product is provided on an as is basis. YOKOGAWA shall have neither liability nor
responsibility to any person or entity with respect to any direct or indirect loss or damage arising
from using the product or any defect of the product that YOKOGAWA can not predict in advance.
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:
l Commonly used Conventions throughout User manuals:

Character strings in the following font and style:
Indicate that user must enter them in the relevant field or text box in the context.
Example:

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
Character string enclosed by brackets ({ }):

Indicates an option that can be omitted.
Example: Parameters for calling the tuning view on HIS

Tagname TUN {-Window size} {=Display position}
l Conventions used to show Key or Button Operations:

Characters enclosed by square brackets ([ ]):
Characters enclosed by square brackets within any description of a key or button operation,
indicate either a key on the keyboard, a button name on a window, or an item displayed on a
window.
Example:

Click the [OK] button.
l Conventions of User Defined Folder

User-Defined Folder Name
If the path of a folder can be defined by users, it is written within parentheses.
Example: (RS Project Folder) \SCS0101
If the RS Project Folder is C: \MYRSPJT, the above path becomes: C: \MYRSPJT\SCS0101
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 :

Indicates important information required to understand operations or functions.
TIP:

Indicates additional information.
SEE :
ALSO

Indicates a source to be referred to.
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.
n Integration with CENTUM

ProSafe-RS can be used by integrating with CENTUM VP or CENTUM CS 3000. In the Users
Manuals of ProSafe-RS, the integration with CENTUM VP or CENTUM CS 3000 is referred to as
Integration with CENTUM.
For the same features of CENTUM VP and CENTUM CS 3000 that have different feature names,
the name used in CENTUM VP will be referred to in the explanations. (For example, CENTUM
CS 3000 System Alarm Window and CENTUM VP System Alarm View have the same functions,
but only System Alarm View will be referred to when explaining this feature.) Nevertheless,
if there is any difference in functionality according to whether ProSafe-RS is integrated with
CENTUM VP or CENTUM CS 3000, the feature will be explained separately for both cases.
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.
n About Station Types

Safety control stations (SCS) are named as follows according to the CPU node (SSCx0S/
SSCx0D) and CPU module (SCP4x1) mounted in them.
SCSV1-S :
SCS that uses SSC10S/SSC10D (SCP401 is installed)
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
Generic term that denotes all types of SCS
SCSV
SCS connected on V net (this denotes SCSV1-S)
SCSP
SCS connected on Vnet/IP (this denotes SCSP1-S and SCSP2-S)
SCSV1
Abbreviation for SCSV1-S
SCSP1
Abbreviation for SCSP1-S
SCSP2
Abbreviation for SCSP2-S
IM 32S05B10-21E
viii
Copyright and Trademark Notices

n All Rights Reserved
The copyright of the programs and online manuals contained in the DVD-ROM or CD-ROM shall
remain in Yokogawa.
You are allowed to print out the required pages of the online manuals for using the product,
however, you are not allowed to print out the entire document.
Except as stated above, no part of the online manual may be reproduced, either in electronic
or written form, registered, recorded, transferred, sold or distributed (in any manner including
without limitation, in the forms of paper documents, electronic media, films or transmission via the
network).
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.
SOE OPC Interfaces
SOE OPC Interface..................................................................................A1-1

A1.1
Configuration of the SOE OPC Interface...................................................... A1-3
A1.2
Settings of the SOE OPC Interface..............................................................A1-11
A1.3
Starting and Closing the OPC Server......................................................... A1-15
IM 32S05B10-21E
TocB-1
ProSafe-RS
Open Interfaces
CONTENTS
PART B
B1.
B2.
B3.
Modbus Slave Interfaces
Modbus Slave Connection.....................................................................B1-1

B1.1
Overview of Modbus Slave Connection....................................................... B1-1
B1.2
Modbus Slave Communication Functions................................................... B1-5
B1.3
Connection between the Modbus Master and SCS.................................... B1-8
Engineering..............................................................................................B2-1
B2.1
Definitions in I/O Parameter Builder............................................................. B2-3
B2.2
Definitions in Modbus Address Builder....................................................... B2-6
B2.3
Window Configuration of Modbus Address Builder................................. B2-10
B2.4
Data Setting via Modbus Interfaces............................................................ B2-14
Messages Communication....................................................................B3-1
IM 32S05B10-21E
TocC-1
ProSafe-RS
Open Interfaces
CONTENTS
PART C
C1.
Common Items Regarding Subsystem Communication

Interfaces..................................................................................................C1-1
C1.1
Overview of Subsystem Communication ................................................... C1-1
C1.2
Dual-redundant Communication ................................................................. C1-8
C1.3
Error Handling Actions . .............................................................................. C1-10
C1.4
Setting Items Relating to Subsystem Communication ........................... C1-12

Settings Using the I/O Parameter Builder . ................................... C1-15
C1.4.2
Settings Using the Communication I/O Builder ............................ C1-21
Forcing of Subsystem Communication Data ........................................... C1-29
C1.6
Communication I/O Lock Window ............................................................. C1-32

C1.6.1
Structure of the Communication I/O Lock Window........................ C1-35
C1.6.2
Operations in the Communication I/O Lock Window . .................. C1-44
On-line Change ............................................................................................ C1-50
Subsystem Communication Modules .................................................C2-1

C2.1
C3.
C1.4.1
C1.5
C1.7
C2.
Subsystem Communication Interfaces
Communication Specifications .................................................................... C2-1
Modbus Communication (ALR111, ALR121)........................................C3-1

C3.1
Communication Specifications .................................................................... C3-2
C3.2
Connection of Serial Communication Module and Modbus PLC............. C3-6
C3.3
Modbus PLC Devices Accessible from SCSs ............................................ C3-9
C3.4
Storage Formats of Subsystem Data ........................................................ C3-13
C3.5
Builder Setting Items Specific to Modbus PLCs ...................................... C3-17

C3.5.1
Items Set in the I/O Wiring View ................................................... C3-17
C3.5.2
Items Set in the I/O Parameter Builder ......................................... C3-17
C3.5.3
Items Set in the Communication I/O Builder.................................. C3-18
C3.6
Readback Communication ......................................................................... C3-22
C3.7
Recovery Communication .......................................................................... C3-27
C3.8
Communication Text ................................................................................... C3-29
C3.9
Communication Time between Serial Communication Module

and Modbus PLC . ........................................................................................ C3-31
IM 32S05B10-21E
<A1. SOE OPC Interface>
A1-1
A1. SOE OPC Interface

By using the SOE OPC Interface (server) provided by ProSafe-RS, it is possible to access
event information and diagnostic information of SCS from OPC applications (clients) on
the host computer.
This chapter explains specifications of the SOE OPC Interface and compatibility with the
OPC specifications. The OPC specifications can be obtained from the web site of the OPC
Foundation.
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.
n What is the SOE OPC Interface?

The SOE OPC Interface provided by ProSafe-RS consists of the OPC server and SOE cassette
dedicated to ProSafe-RS.
OPC server
This server allows the host computer to access various data acquired from SCS. It has the
functions of Alarms & Events server (hereinafter referred to as A&E server).
ProSafe-RS SOE Cassette
The SOE cassette dedicated to ProSafe-RS is incorporated in the cassette provided by the
OPC Interface as communication interface.
Function of the SOE Cassette
The SOE cassette provides communication functions for notifying SOE Events and
diagnostic Information of SCS to the OPC server. By connecting to the OPC server
equipped with this cassette, OPC clients can receive event messages (SOE events and
diagnostic Information) of SCS.
IM 32S05B10-21E
A1-2
<A1. SOE OPC Interface>
n System Configuration Using the SOE OPC Interface

The SOE OPC Interface runs on a general-purpose PC and notifies event information and
diagnostic information of SCS to the host computer via the OPC interface.
Host computer
(OPC client)
Ethernet
General-purpose
PC (OPC server)
SENG
HIS
Control bus
Data flow of the OPC interface

Data flow of the SOE function
SCS
A010001E.ai
Figure Example of System Configuration Using the SOE OPC Interface
IM 32S05B10-21E
A1-3
<A1.1 Configuration of the SOE OPC Interface>
A1.1 Configuration of the SOE OPC Interface

This section explains the software configuration of the SOE OPC Interface.
n Software Configuration of the SOE OPC Interface

The SOE OPC Interface is composed of the OPC server and the SOE cassette dedicated to
ProSafe-RS (hereinafter referred to as SOE cassette). The OPC server sends data to the OPC
client. The SOE cassette is an interface used by the OPC server to acquire data from SCS. The
software configuration of the SOE OPC Interface is shown below.
OPC client (Exaquantum, etc.)
Ethernet
OPC server
(A&E server)
Cache Data
SOE cassette
Control bus
SCS
Legend
SOE
Events log
Diagnostic
Information log
OPC interface
Events
A010101E.ai
Figure Software Configuration and Data Flow
IM 32S05B10-21E
A1-4
n Detailed Items of the SOE OPC Interface

Particular items of the SOE OPC Interface are explained below, including parameters and control
method required when constructing the system with the SOE OPC Interface.
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
Maximum number of connected clients
100 clients
Maximum number of event registration objects
1000/OPC server
Maximum number of registered event generation sources
100/registeration object
l Server Name (ProgID), Type Library Name

The server name and type library name of the A&E server are defined as follows. The server
name is used for the custom interfaces. The type library name is used by the automation
interfaces in application such as Visual Basic and Excel.
The custom interfaces
Server name: Yokogawa.ExaopcAESCSSOE
The automation interfaces
Type library name: Yokogawa ProSafe-RS SCS Alarms & Events Automation Server
l Event Category and Event Type

The following table shows event categories and event types. The event category of system
alarms generated in the SOE cassette is System alarms (101).
Table
Event Category and Event Type

Event Category
Name
Value
Event type
Description
System alarms
101
Simple(=1)
Diagnostic Information
Sequence of events
110
Simple(=1)
Event Information
l Source (Event Generation Sources)

This item contains the same reference as displayed in SOE Viewer. In the case of system alarms
generated in the SOE cassette, the ProgID value (Yokogawa.Exaopc AESCSSOE) is stored in
this item.
IM 32S05B10-21E
A1-5
l Time (Event Generation Time)

This item contains the same time stamp (SCS time) as displayed in SOE Viewer. The time stamp
is stored using UTC (Universal Time Coordinated). The time stamp based on the PC time is
stored using UTC in the case of system alarms generated in the SOE cassette.
l Severity (Event Priority)

This item contains a value from 200 to 900 to indicate the severity of the alarm or event. 900 is
stored in the case of system alarms generated in the SOE cassette.
Table
Event Category and Severity

Event Category
Severity level
Name
System alarms
Sequence of events
Description
900
Diagnostic Information (class 1)
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.
l Event Description and Attributes

The table below summarizes SOE event attributes notified by the OPC interface.
Table
Event Attributes of Diagnostic Information
Attribute Name
OPC ID
VARIANT type
Remark
SOETimestamp
301
VT_DATE
Event Occurrence Date (Local)
TimestampM
302
VT_12
Event Occurrence Time (Millisecond)
Resource
303
Type
304
ID
305
VT_BSTR
The same as the corresponding information

displayed in SOE Viewer (*1)
Quality
306
Node
308
VT_I2
Node position, or 0
Slot
309
VT_I2
Slot position, or 0
Time_Diff
318
VT_BSTR
Time zone (-08:00, +00:00, +09:00, ...)
*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
Event Attributes of Event Information (1/2)
Attribute Name
OPC ID
VARIANT type
Remark
SOETimestamp
301
VT_DATE
Event Occurrence Date (Local)
TimestampM
302
VT_12
Event Occurrence Time (Millisecond)
Resource
303
Type
304
ID
305
VT_BSTR
The same as the corresponding information

displayed in SOE Viewer
Quality
306
IM 32S05B10-21E
A1-6
Table
Event Attributes of Event Information (2/2)
Attribute Name
OPC ID
VARIANT type
Remark
Node
308
VT_I2
Node position (DI/DO event only), or 0
Slot
309
VT_I2
Slot position (DI/DO event only), or 0
Channel
310
VT_I2
Channel position (DI/DO event only), or 0
TripMark
313
VT_I2
True/false of tripping signal (1/0)
Time_Diff
318
VT_BSTR
Time zone (-08:00, +00:00, +09:00, ...)
l Formats for System Alarms Generated in the SOE Cassette

The SOE cassette generates a system alarm when access to SCS event logs fails. The system
alarm is notified to the OPC client. The following shows a message format of the system alarm:
Event Category:
101 (System alarms)
Event Type:
1 (Simple)
Source:
Yokogawa.ExaopcAESCSSOE
Time:
(PC time)
Severity:
900
Message:

Database Connection Error [ERR=0x80004005]

Database Connection Recover
SOETimestamp (Event Attribute): (PC time) Event Occurrence Date (Local)

TimestampM (Event Attribute):
(PC time) Event Occurrence Time (Millisecond)
Resource (Event Attribute):
(Computer name)
Type (Event Attribute):
BSYS
ID (Event Attribute):
(Blank)
Quality (Event Attribute):
(Blank)
Node (Event Attribute):
Slot (Event Attribute):
Time_Diff (Event Attribute):
(PC time) Time zone (-08:00, +00:00, +09:00, ...)
The default values can be changed according to the performance of PC.

If the delay time per transmission event is set to a larger value, the event transmission
becomes slower and the CPU load becomes lower.
If the delay time per transmission event is set to a smaller value, the event transmission
becomes faster and the CPU load becomes higher.
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
n Event Notification Interfaces

The SOE cassette notifies event information and diagnostic information of SCS to the A&E
server. It also provides a function for filtering each event.
l Available Interfaces
The following tables shows the custom interfaces available to clients of the A&E server.
Table
Object
Custom Interfaces (1/2)

Interface
IOPCCommon
Method
Description
Support
SetLocaleID
Locale ID setting
GetLocaleID
Locale ID acquisition
QueryAvailableLocaleIDs
Inquiry about supported locale IDs
GetErrorString
Error character string acquisition
SetClientName
Client name setting
GetStatus
Server status acquisition
CreateEventSubscription
Generation of Event Subscription object
QueryAvailableFilters
Inquiry about items that can be filtered
QueryEventCategories
Inquiry about event categories
QueryConditionNames
Inquiry about condition names
QuerySubConditionNames Inquiry about sub-condition names
OPCEventServer
IOPCEventServer
IConnectionPoint
Container
x:
:
QuerySourceConditions
Inquiry about condition names

corresponding to a source name
QueryEventAttributes
Inquiry about event attributes
TranslateToItemIDs
Item ID translation/acquisition
GetConditionState
Acquisition of condition status
EnableConditionByArea
Condition Enable for a specified area
EnableConditionBySource
Condition Enable for a specified source
DisableConditionByArea
Condition Disable for a specified area
DisableConditionBySource
Condition Disable for a specified source
AckCondition
Notification of condition
acknowledgment
CreateAreaBrowser
Generation of Event Area Browser

object
IOPCSecurityNT
Access control interface that uses NT

credit information
IOPCSecurityPrivate
Access control interface that uses

private-defined user name/password
EnumConnectionPoints
Creation of emulator that scans

connection points
FindConnectionPoint
Acquisition of interface pointers to

connection points
Supported
Not supported
IM 32S05B10-21E
A1-8
Table
Object
Custom Interfaces (2/2)

Interface
Method
IOPCSecurity
Private
OPCEventArea
Browser
(Option)
IOPCEventArea
Browser
IOPCEvent
SubscriptionMgt
OPCEvent
Subscription
IConnectionPoint
Container
IConnectionPoint
Support
Advise
Connection between connection point

and sink
Unadvise
Disconnection between connection point

and sink
IsAvailableNT
Inquiry about availability of OPC security

function by NT credit information
x
(*1)
QueryMinImpersonationLevel
Inquiry about impersonation level
ChangeUser
Notification of user credit information

changes
IsAvailablePriv
Inquiry about availability of OPC security

function by private credit information
Logon
Logon request by client user
Logoff
Logoff request by client user
ChangeBrowsePosition
Change of browser position
BrowseOPCAreas
Acquisition of area list
GetQualifiedAreaName
Acquisition of Area name
GetQualifiedSourceName
Acquisition of Source name
SetFilter
Event filter setting
GetFilter
Acquisition of event filter
SelectReturnedAttributes
Selection of event attribute
GetReturnedAttributes
Acquisition of selected event attribute
Refresh
Event refresh request
CancelRefresh
Cancellation of refresh request
GetState
Acquisition of the status of Event

Subscription object
SetState
Set the status of Event Subscription

object
EnumConnectionPoints
Creation of enumerator that scans

connection points
FindConnectionPoint
Acquisition of interface pointers to

connection points
IConnectionPoint
OPCEventServer IOPCSecurityNT
Description
Advise
Unadvise
Connection between connection point

and sink
Disconnection between connection point
and sink
x
(*2)
x
x
OPCEventSink
IOPCEventSink
OnEvent
Event notification
OPCShutdown
IOPCShutdown
ShutdownRequest
Server shutdown notification
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
Filtering by Event type
OPC_FILTER_BY_CATEGORY
Filtering by Event category
OPC_FILTER_BY_SEVERITY
Filtering by Alarm severity
OPC_FILTER_BY_SOURCE
Filtering by Source name
l OPC A&E Automation Interfaces

Not supported. Currently, the OPC Foundation is creating the specifications of the OPC A&E
automation interfaces. Yokogawa Electric Corporation plans to provide the OPC A&E automation
interfaces in conformity with for the OPC A&E custom interfaces.
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.
l OPC Error Codes

The OPC error codes used by the SOE cassette are summarized below.
Table
COM Error Codes
COM error codes used by OPC server
Description
E_FAIL
General errors (without specific codes)
E_INVALIDARG
Invalid parameter
E_NOTIMPL
Unsupported function
E_OUTOFMEMORY
Insufficient memory
Table
OPC Error Codes

OPC error code
Description
OPC_E_BADRIGHTS
No access right
OPC_E_BADTYPE
Invalid request type
OPC_E_INVALIDITEMID
Invalid item ID
OPC_E_INVALID_PID
Invalid parameter ID
OPC_E_UNKNOWNITEMID
Undefined item ID specified
IM 32S05B10-21E
A1-10
l SOE Cassette Definition Error Codes

The cassette definition error codes used in the SOE cassette are shown below.
Table
SOE Cassette Definition Error Codes
Code
(xxxx-x999)
Symbol
(ZOT_XL_E_XXXX)
Description
0xC0042329
ZOC_AE_E_MAXSERVER
Excessive number of clients connected to

the A&E server
0xC004232A
ZOC_AE_E_MAXSUBSCRIPTION
Excessive number of event registration

objects of the A&E server
l Error Code Bit Assignment

The bit assignment in the error codes is shown below.
Code:
0000 to 0200
For Microsoft
0200 to 7999
For OPC definition errors
9000 to 9999
For the A&E server
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
Sev - is the severity code

00 - Success
01 - Informational
10 - Warning
11 - Error
C- is the Customer code flag
R- is a reserved bit
Facility- is the facility code (=FACILITY_ITF)
Code- is the facility's status code
A010102E.ai
Figure Bit Assignment in Error Codes
IM 32S05B10-21E
<A1.2 Settings of the SOE OPC Interface>
A1-11
A1.2 Settings of the SOE OPC Interface
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.
n Settings of Operation Parameters

The operation parameter setting tool can be launched by selecting [All Programs], [YOKOGAWA
ProSafe] and then [SOE OPC Parameter Setting] from the [Start] menu of Windows.
Java Web Start
PrintMe Internet Printing
Paint
Startup
Trend Micro Internet Security
Workbench
YOKOGAWA CENTUM
YOKOGAWA ProSafe
System View
Adobe Reader 6.0
Internet Explorer
All SCS Status Overview
MSN Explorer
Window
Outlook Express
Windows Media Player
PowerDVD
Remote Assistance
Set Program Access
Solution Center
Defaults
Windows Media Player
All Programs
Windows Messenger
Log Off
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
Figure SOE OPC Interface Setting Menu
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
Specify Start Date/Time of Events

1/1/2005
9:00:00 AM
10
(sec)
Database Connection Retry Period
120
(sec)
Delay Time per Transmittion Event
40
Database Reference Period
(msec)
HDA
Use HDA
10000
Max No. of Saving Events
OK
Cancel
A010202E.ai
Figure SOE OPC Interface Setting Dialog Box
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.
l Items Set for the A&E Server

Use Database
Always select this check box because the SOE OPC server is an A&E server.
The check box is selected by default.
SCS Name
This field becomes enabled only if you selected the [Use Database] check box. List the
names of SCSs to be referenced (separated by space, comma or period).
Example: SCS0101, SCS0102
The event logs of the SCSs selected here become the target of notification.
Specify Start Date/Time of Events
Select this check box to change the date/time of the first event to be acquired. If this box
is selected, all events after the specified date/time are sent to the client. If the box is not
selected, events after the PC time when restarting the SOE cassette are sent to the client.
The check box is not selected by default.
Date/Time Specification
These fields become enabled only if you selected the [Specify Start Date/Time of Events]
check box. Specify the date and time of the first event. The time when you select the
[Specify Start Date/Time of Events] check box is set by default.
Database Reference Period
Specify the period in units of seconds if you want to change the database reference period.
A value in the range from 1 to 600 seconds can be specified. 10 seconds is set by default.
IM 32S05B10-21E
A1-13
Database Connection Retry Period

Specify the time interval (seconds) to retry reconnection to the database in case the
connection to the database fails or the connection to the database is disconnected.
A value in the range from 1 to 1800 seconds can be specified. 120 seconds is set by default.
Delay Time Per Transmission Event
Specify the time in units of milliseconds if you want to change the setting.
A value in the range from 0 to 1000 milliseconds can be specified. 40 ms is set by default.
l Items Set for the HDA Server

It is possible to specify to use HDA if Exaquantum is used for the OPC client.
Use HDA
Select this check box when the HDA functions should be used.
Max No. of Saving Events
This field becomes enabled only if you selected the [Use HDA] check box. Specify the
maximum number of events that the HDA server should maintain. If more events than the
maximum number of events saved are generated, events are overwritten starting from the
oldest event. A value in the range from 1000 to 1000000 can be specified. 10000 is set by
default.
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.
n Operations when the SOE OPC Interface is Launched

When the operation parameter setting tool is launched for the first time, all the items are set to
their default values. When you launch the tool the next time, the tool displays all items according
to the settings the user made last time.
The [Specify Start Date/Time of Events] check box is deselected when the SOE cassette starts to
send events.
n Operations when Changing Parameters

If operation parameters of the SOE cassette are changed by the operation parameter setting tool,
the SOE OPC interface restarts when you click the [OK] button of the operation parameter setting
tool.
Events generated while the SOE OPC interface is restarting are not sent to the client. If you want
to send events generated during the SOE OPC interface restart processing (approximately 1 to
2 minutes) to the client, specify the [Specify Start Date/Time of Events] setting item for the A&E
server. The current time can be set by selecting/deselecting the [Specification of Head Event
Date/Time] check box.
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
n OPC Security Interface

In addition to the Security interface of the custom interfaces of the A&E server, security settings
for DCOM are provided.
The following table shows the security settings for DCOM:
Table
DCOM Settings
DCOM setting item
Server machine
Client machine
Authentication level
Connect
None
Impersonation level
COM selects the impersonation level set by the client.
Impersonate
Access permissions
Defines the user list using DCOMCNFG
None
Launch permissions
Defines the user list using DCOMCNFG
N/A
IM 32S05B10-21E
A1-15
<A1.3 Starting and Closing the OPC Server>
A1.3 Starting and Closing the OPC Server

This section explains how to start and close the OPC server.
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
<B1.1 Overview of Modbus Slave Connection>
B1. Modbus Slave Connection

ProSafe-RS Safety Control Station (SCS) has the Modbus slave function. The Modbus
master (external device) can reference and set SCS data.
B1.1 Overview of Modbus Slave Connection
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
n Relationship with the Modbus Master

An SCS has the following relationship with the Modbus master.
SENG
Engineering functions
SCS Status Overview of

SCS Maintenance Support Tool
Downloading definition
information
Error information
SCS CPU
Definition information
Reference
SCS data
Data access
Modbus slave communication function

Request/response
Serial communication
module
Serial communication functions
Serial communication data
Modbus master (e.g., DCS)

B010102E.ai
Figure Relationship with an External Device
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.
n Interface with the Modbus Master

SCS operates as a Modbus slave. An external device operates as the Modbus master and it can
reference and set SCS data.
The external device and SCS are connected with one of the following communication interface
modules installed to SCS. Neither of the modules supports dual-redundant configuration. These
modules are interference-free modules that do not interfere with the safety loop.
Serial communication module (RS-232C, 2-port, 1200 bps to 115.2 kbps)
Serial communication module (RS-422/RS-485, 2-port to 115.2 kbps)
n Data Access by Device Speciation

The Modbus master requests data access to SCS (Modbus slave) using the Modbus devices
addresses shown in the table below.
SCS does not have actual Modbus devices. SCS assigns virtual Modbus device addresses to
variables of the application logic and sends them responses accordingly.
Table
Modbus Devices
Virtual Modbus device
Data
Access from master to slave

Read
(reference)
Write (set)
Coil
Output device with 1 bit/channel
Possible
Possible (*1)
Input relay
Input device with 1 bit/channel
Possible
Impossible
Input register
Input register with 16 bit/channel
Possible
Impossible
Holding register
Output register with 16 bit/channel
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
n Data Settings from the Modbus Master

Data can be set to variables of the application logic from the Modbus master via the Modbus
slave connection using external communication function blocks.
n Modbus Communication Execution Timing

As a Modbus slave, SCS performs Modbus connection at the idle time of each scan for the
application logic. SCS checks whether any request has been sent from the Modbus master
through the serial communication module. If SCS finds any request, SCS will respond to the
request only when the scan has idle time.
SCS only responds to the request in this communication processing and will set the data to the
variables of application logic in the scan by the safety functions after responding to the request.
Scan by the
safety functions
Modbus communication
processing
Scan by an external device connection functions
1 second
B010103E.ai
Figure Execution Timing of Modbus Slave Connection Functions
n Monitoring from HIS and SCS Maintenance Support Tool

The serial communication module status can be monitored from HIS or SCS Maintenance
Support Tool.
Table
Serial Communication Monitoring from HIS or SCS Maintenance Support Tool

Window
Monitoring operation
SCS State Management
Displays whether the serial communication module is

normal or faulty. No communication errors are displayed.
System alarm
Errors in the serial communication module are notified by

system alarms.
n Operation when Serial Communication Module is Added Online

It is possible to make changes online to the application that involve addition or removal of serial
communication modules. If you mount an additional communication module in the SCS and
execute an online change download, the module starts to run immediately. During downloading,
the diagnostic information messages (IOM Fail, and then IOM Recover) are generated, but the
operating mode of the SCS remain the same. You do not need to perform the Output Enable
Operation or any other special operation.
IM 32S05B10-21E
<B1.2 Modbus Slave Communication Functions>
B1-5
B1.2 Modbus Slave Communication Functions
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.
n Modbus Communication Function

SCS receives data requests from the Modbus master via serial communication module, such as
ALR111 or ALR121.
The SCS reads/writes data within itself using the Modbus communication commands and notifies
the result to the Modbus master.
n Data Access Function

This function references/sets SCS data in response to requests of the Modbus master. To
process the requests, it references the database that defines the correspondence between
Modbus device addresses and application logic variables.
l Referencing/Setting SCS Data

This function allows the Modbus master to reference internal variables (BOOL, DINT, REAL) or
input/output variables of DI, DO and AI. It also allows the Modbus master to set (Modbus Word
Order), variables data of external communication function blocks.
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
Figure Execution Example of Word Reversal
IM 32S05B10-21E
B1-6
l One Shot Write Function

When setting SCS data, a one shot write operation is performed on data that does not interfere
with the safety loop. An error is returned if it is requested to set data that interfere with the safety
loop.
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
SCS Transmission Specifications

Item
Description
RS-232C
Interface
RS-422/RS-485 (4-wire
system)
Builder
specification
x
Remarks
ALR111
ALR121
Synchronization method
Start-stop
synchronization
Baud rate
1200, 2400, 4800, 9600,

[19200], 38400
Start bits
Fixed to 1
Data bits
7, [8]
Stop bits
[1], 2
Parity
None, Odd, [Even]
RS control
Yes, [No]
Valid only for ALR111
DR check
[Yes], No
CD check
Yes, [No]
Transmission
enable monitoring
time
0 to 99990 (ms)
[1000 ms]
Specify in units of 10 ms
Fixed to 1000 ms for

Modbus
Control line
Time monitoring
Text frame
Fixed to 8 for Modbus

(RTU)
0 to 99999 (ms)
Reception character
[10 ms]
interval timer
Specify in units of 1 ms
Character internal
monitoring timeout
[Do not set], Set
Fixed to [Do not set] for

errors in the RTU mode
of Modbus
Reception start
character
1 character, [None]
Fixed to [None] for

Modbus
EOT character
1 character, 2
characters, [None]
Fixed to [None] for

Modbus
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)
Note: [ ] indicates a default value (recommended value).

*1:
Only the RTU mode is supported. The ASCII mode is not supported.
IM 32S05B10-21E
B1-8
<B1.3 Connection between the Modbus Master and SCS>
B1.3 Connection between the Modbus Master

and SCS
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
module
(ALR111)
Modbus Slave
(SCS)
MODEM
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
n Serial Communication Modules

SCS uses ALR111/ALR121, as a serial communication module. ALR111/ALR121 is used by
mounting in SCS and connecting a serial communication cable.
If ALR111 is mounted, use an RS-232C cable. If ALR121 is mounted, use an RS-422/RS-485
cable.
I/O modules
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
Figure Example of Mounting a Serial Communication Module to SCS
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 Displays and Meanings When Illuminated
LED indication
SEE
ALSO
Meaning
STATUS
Hardware ready
ACT
Operating normally
DX
Duplex display
SND1, SND2
Sending from port 1 or 2
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
n Cable Connection when using ALR111

Connect the Modbus master and ALR111 via a modem. Note that the RS-232C cable lengths
between ALR111 and the modem, and between the modem and the Modbus master should both
be 15 m or less.
If the total cable length of the RS-232C connection is 15 m or less and the Modbus master and
ALR111 use the same grounding, the Modbus master and ALR111 can be connected directly.
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
Figure Pin Assignment of the RS-232C D-sub 9-pin Connector

Table
RS-232C D-sub 9-pin Connector Specification
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
Data Terminal Ready
SG
Signal Ground
DR
Data Set Ready
Send when DR is ON (only if DR check is specified)
RS
Request to Send
Always ON in case RS control is not used. ON is

output during transmission if RS control is used
CS
Clear to Send
Send only when CS is ON
Not used
Output ON during normal operation
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
Protective grounding (100 or less)

B010305E.ai
Figure Cable Connection of ALR111 (9-pin) and the Modbus Master (25-pin) via Modems
l Connection between an RS-232C D-sub 25-pin Connector and the Modbus

Master (Direct Connection)
The following figure shows a cable connection when directly connecting ALR111 and the Modbus
master that has an RS-232C D-sub 25-pin connector.
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
Protective grounding (100 or less)

B010306E.ai
Figure Cable Connection for Directly Connecting ALR111 (9-pin) and the Modbus Master (25-pin)
IM 32S05B10-21E
B1-12
l Connection between an RS-232C D-sub 9-pin Connector and the Modbus

Master (Direct Connection)
The following figure shows a cable connection when directly connecting ALR111 and the Modbus
master that has an RS-232C D-sub 9-pin connector.
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.
l ER (DTR) Signal Line

The ER signal turns ON after the serial communication module has completed the startup
processing and is ready to receive and send data. Use this signal to judge whether or not the
serial communication module can receive data at the connection destination.
l DR (DSR) Signal Line

The DR signal cable is used to judge whether or not the device to which the ALR 111 is wired can
receive data.
Data can be sent when the DR signal check is ON. Wire a signal line that turns ON when the
connection destination can receive data to the DR signal line.
To disable this check, specify [No] for the DR check, or wire a signal line that is always ON to the
DR signal pin.
IM 32S05B10-21E
B1-13
l RS (RTS)/CS (CTS) Signal Lines

For the RS signal either [No] (always ON) or [Yes] (ON at transmission) can be specified for the
RS control.
Wire the RS signal line to the end of the other line and set [Yes] for RS control to turn ON/OFF the
signal line when transmitting.
Data is transmitted when the CS signal is ON. Wire the line in such a way that it turns ON at
transmission.
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
Definitions of Serial Communication Modules

In order for SCS to perform Modbus communication, the serial communication modules must be
defined for SCS. The serial communication modules can be classified into two types depending
on the communication interface (RS-232C or RS-422/RS-485).
Define the serial communication modules using I/O Wiring View of SCS Manager first, and then
set parameters for each port of the modules using I/O Parameter Builder.
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
l Definitions of Serial Communication Module

Define serial communication modules using I/O Wiring View of SCS Manager according to the
following procedure:
1.
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.
l Parameter Setting of Serial Communication Modules

Specify parameters for each port of the serial communication modules using I/O Parameter
Builder. Since ALR111/ALR121 has two ports, two pairs of parameters are required.
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
Definition of Addresses of Modbus Devices

To access variables of the application logic on SCS from the Modbus master via Modbus
communication, it is necessary to define the correspondence between the variables and the
addresses of Modbus devices. Define Modbus device addresses for the variables using Modbus
Address Builder.
Modbus device addresses can be assigned to input/output variables and internal variables.
IM 32S05B10-21E
B2-3
<B2.1 Definitions in I/O Parameter Builder>
B2.1 Definitions in I/O Parameter Builder
This section explains how to define communication input/output modules to perform

Modbus communication. Serial communication modules can be defined in the [Port 1] tab
and [Port 2] tab of I/O Parameter Builder.
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)
[Port 1], [Port 2] Tab

The following items can be set in the [Port 1], [Port 2] tab.
The settings of each item can be changed online download, but the corresponding module will
restart after download.
Table
[Port 1], [Port 2] Tab

Title
Description
Baud Rate
Set the baud rate
Stop Bits
Set the stop bit
Parity
Set the method for checking the parity
Control Line
Remark
RS Control
Specify whether or not to perform RS control

during ALR111 transmission
DR Check
Specify whether or not to perform DR signal

check during ALR111 transmission
CD Check
Specify whether or not to perform CD signal

check during ALR111 transmission
Reception InterCharacter Timer
Specify the monitoring time of reception

character interval during reception by the
ALR111/ALR121
Station Number
Specify the slave address of the Modbus

slave
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
l Reception Inter-Character Timer

The reception Inter-Character timer (reception Inter-Character timeout setting value) is a function
that monitors the time between characters are received when the ALR111/ALR121 module
receives data. In the Modbus (RTU mode) binary communication, the communication is regarded
as completed if this duration of time or longer elapses between two character receptions.
If the communication is performed via a modem with data buffering or similar functionality,
it is necessary to specify this value taking account of the communication delay (elapsed
time between character receptions) due to buffering by the modem. This also affects the RS
communication time, however, because this interval of time is used to determine communication
completion.
Default:
10 ms
Setting range: 0 to 99999 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:
Setting range: 1 to 247
l Options 1 to 4
Always set 0 for these options.
Default:
0 (for all)
IM 32S05B10-21E
B2-6
<B2.2 Definitions in Modbus Address Builder>
B2.2 Definitions in Modbus Address Builder
Use Modbus Address Builder to associate the variables of the application logic with the
addresses of Modbus devices.
Assigning Variables in Modbus Address Builder

Modbus devices can belong to the following four types: coils, input relays, input registers and
holding registers. A reference number is assigned to each Modbus device type. The variable
name to be accessed is assigned to a reference number in Modbus Address Builder. The type of
variable to be assigned is selected according to the reference number. For example, a variable of
BOOL type or IO_BOOL type can be assigned to an input relay.
SEE
ALSO
For more information about reference numbers, see the following:

Modbus Device Tabs in B2.3, Window Configuration of Modbus Address Builder
l Types of Modbus Devices and Variables

The type of variables that can be assigned to each reference number of Modbus devices is as
follows:
Table
Variables to which Modbus Device Addresses can be Assigned

Variable type
Modbus device type
Remark
BOOL
Input relay
REAL
Input register
Requires two addresses per one data
DINT
Input register
Analog input variable (IO_REAL)
Input register
Only the data value is included, and the

data status is not included.
Discrete input/output variable

(IO_BOOL)
Input relay
Only the data value is included, and the

data status is not included.
Instance of external communication

function block (BOOL type)
Coil
Instance of external communication

function block (DINT and REAL types)
Holding registers
Requires two addresses per data value
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
Example of Variable Names
Variable name
SEE
ALSO
Scope
Description
VAR1
Global
A global variable
VAR2@PROG1
PROG1
A local variable of a function in PROG1
FB01.VAR3
Global
The internal variable VAR3 of an instance of the user-defined function

block FB01
FB01.VAR3@PROG1
PROG1

block FB01, which is locally defined in a function of PROG1
FB01.FB2.VAR3
Global

block FB2 used inside an instance of the user-defined function block
FB01 (The limit of nesting of a function block is two)
For more information about Dictionary View of SCS Manager, see Workbench of the Workbench Users Guide.
How to Define Variable Names

Variable names can be specified in the [Variable name] columns in the tabs for the four different
types of Modbus devices. A variable can be defined in one of the following ways.
Direct entry from the keyboard
Double-clicking a variable name in the data menu area
Drag and drop a variable from Dictionary View
l Direct Entry from the Keyboard

Enter a variable name in the [Variable name] column directly from the keyboard.
l Double-clicking a Variable Name in the Data Menu Area

The data menu area of Modbus Address Builder contains the [Variable] tab and the [IOM] tab.
Double-click a variable name in the [Variable] tab to set the variable name in the [Variable name]
column.
Double-click a node number or a slot number in the [IOM] tab to set variables wired for each
Input/Output Module at once.
IM 32S05B10-21E
B2-8
l Drag and Drop from Dictionary View

Drag and drop a variable name from Dictionary View to a [Variable name] field of Modbus
Address Builder to register the variable name in Modbus Address Builder. If you drag and drop
multiple variable names, they are registered in the order starting from the top of the [Variable
name] column of the dropping destination. If variable names have already been registered in the
[Variable name] field, they are overwritten.
ProSafe-RS - [Project2 (*Binding error management*) - Dictionary - Variables]
File
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
Resource 1: Config1\Main(*send info to R2*)
Modbus Address Builder -[Pjt:SCS0101 File:Modbus.edf]

File
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
Figure Drag and Drop from Dictionary View
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.3 Window Configuration of Modbus Address Builder>
B2-10
B2.3 Window Configuration of Modbus Address

Builder
This section describes the window configuration and menus of Modbus Address Builder.
Window Configuration of Modbus Address Builder

Modbus Address Builder -[Pjt:SCS0101 File:Modbus.edf]
File
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
Data menu area
1 Column 3
Work Space
B020301E.ai
Figure Window Configuration of Modbus Address Builder
This section describes each configuration component of the window.
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
Data Menu Area

The data menu area of Modbus Address Builder contains two tabs, the [Variable] tab and the
[IOM] tab. Modbus Address Builder allows setting variable names only.
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
Figure Data Menu Area - [Variable] Tab
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
Figure Data Menu Area - [IOM] Tab
IM 32S05B10-21E
B2-12
Modbus Device Tabs

The following tabs are provided in the work space of Modbus Address Builder:
[Coil] tab
[Input relay] tab
[Input registers] tab
[Holding registers] tab
l Reference Numbers in Tabs

Each tab displays the reference numbers.
[Coil] tab

Range of reference numbers: 00001 to 01000
Example: 00001, 00002, 00003, ..., 01000

Output devices of 1 bit per channel (allows both input and output)
[Input relay] tab

Range of reference numbers: 10001 to 14000
Example: 10001, 10002, 10003, ..., 14000

Input devices of 1 bit per channel (allows input only)
[Input registers] tab

Range of reference numbers: Odd numbers between 30001 and 34000
Example: 30001, 30003, 30005, ..., 33999

Input registers of 16 bits per channel (allows input only)
Each register is assigned to a 32-bit data, i.e. 2 words compose one data.
[Holding registers] tab

Range of reference numbers: Odd numbers between 40001 and 41000
Example: 40001, 40003, 40005, ..., 40999

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
l Items Displayed in Tabs

Each tab displays the following items. Some items are not displayed depending on the tab. The
user can set values only in the [Variable name] column.
Reference
Addresses of Modbus devices. These are displayed in advance in numerical order.
This item is commonly displayed for all the tabs.
Variable Name
Variable names to be assigned.
Type
Types of variables. These are displayed once variable names are determined.
Comment
Comments attached to variables. These are displayed once variable names are determined.
Wiring Position
Installation positions of channels corresponding to variables. This item is displayed only for
the [Input relay] and [Input registers] tabs.
The wiring positions are displayed when variables are determined if the variable type is
IO_BOOL in the case of the [Input relay] tab and IO_REAL in the case of the [Input registers]
tab. The display format is %IUm.n or %QUm.n in both cases, for example %IU0.0.
IM 32S05B10-21E
B2-14
<B2.4 Data Setting via Modbus Interfaces>
B2.4 Data Setting via Modbus Interfaces
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.
Data Setting Using External Communication Function Blocks

It is possible to read and write data of SCS from the Modbus master using the SCS Modbus
slave connection function. The Modbus master device sends a data access request to SCS,
using Modbus device address as interfaces. Although SCS is not equipped with any actual
Modbus devices, it acts as if it has them and responds to the data access requests from the
Modbus master.
Data can be set from the Modbus master to the SCS by combining the Modbus slave connection
function and external communication function blocks. The Modbus device types that can be used
for data settings are coil and holding register. Assign instance names of external communication
function blocks to coils and holding registers using Modbus Address Builder.
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
Modbus interface (coil)
Internal
variable
ECW_B
OUT
Modbus interface (holding register)
Internal
variable
ECW_I
OUT
Modbus interface (holding register)
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
Modbus Devices Used for Setting and Read-back
Data type (*1)
Register for writing (*2)
Register for read-back (*3)
BOOL
Coil
Input relay
DINT
Holding register
Input register
REAL
Holding register
Input register
*1:
*2:
*3:
Assignation in Modbus Address Builder

Assign registers to external communication function blocks
Assign to read-back variables (corresponding to the READBACK variables in the Read-back Application figure below)
BOOL-type data can be set according to the following sequence.

1.
Assign a coil reference number to ECW_B (BOOL-type external communication function

block) in Modbus Address Builder.
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
Data write by Cail reference address

User
Application
Application logic
Internal
variable
OUT
ECW_B
10032
(reference number)
Data read by Input Relay reference address
Modbus Master
READBACK
Normal
BOOL-type
variable
SCS
Modbus
B020402E.ai
Figure Read-back Application
IM 32S05B10-21E
B2-16
l Restrictions on the Number of Data Setting Communication Operations by

Modbus Interfaces
On receiving a data setting request from the Modbus master, SCS returns a response and retains
the request it accepted.
A data setting request message from the Modbus master is referred to as a request here.
Up to 32 data values can be specified in a request.
Up to four requests can be retained with all Modbus slave interfaces (serial communication
modules) at the same time.
SCS will process the retained data setting requests from the Modbus master four requests
per second at maximum when the scan period of the application logic is shorter than 250
ms. When the scan period is 250 ms or longer, SCS will process one request in one scan
period.
If SCS also retains any request from FCS and/or HIS for data setting via tag name interface
in addition to requests from the Modbus master, the SCS will process only one request in
one scan period in the order of acceptance.
SCS responds with error if the number of retained requests is four when SCS receives a
request from the Modbus master.
IMPORTANT
Periodical data setting will result in a writing error.
Do not set data periodically from the Modbus master.
l Confirming Data Set by Modbus Interfaces

When setting data from the Modbus master, it is necessary to perform read-back for checking the
data. The application logic should be designed as shown in the previous Read-back Application
figure.
Data is set to an external communication function block and the data is read back from a variable
connected to an OUT (READBACK variable in the previous figure).
IM 32S05B10-21E
B3-1
<B3. Messages Communication>
B3. Messages Communication

In the data communication between the Modbus master and SCS, SCS sends the
response message to the Modbus master in response to its request message. When
SCS detects an error relevant to the serial communication module, the SCS sends the
diagnostic information message via the control bus.
Message Communication Protocol from the Modbus Master

The request message of the Modbus master is composed of the following information:
Slave address
Function code
Modbus device information
Error check code
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 Codes supported by SCS
Function code
(hexadecimal)
Description
Maximum size
01
Read Coil Status
512 bits
02
Read Input Status
512 bits
03
Read Holding Registers
124 words (62 data items)
04
Read Input Registers
05
Force Single Coil
1 bit
08
Loopback Diagnostic Test -
0F
Force Multiple Coils
32 bits
10
Preset Multiple Registers
Remark
512 bits = 32 words
Restriction from protocol
IM 32S05B10-21E
B3-2
l Modbus Device Information

This contains the detailed information for SCS to execute the requested function.
The address information of Modbus devices (coil, input relay, input register and holding register)
is the relative number from the first reference number of each device.
SEE
ALSO
For more information about reference numbers, see the following:

Modbus Device Tabs of B2.3, Window Configuration of Modbus Address Builder
l Error Check Codes

Error check information is used to detect errors in messages occurring during a signal
transmission (bit errors). Whenever a request is sent to an SCS, CRC (Cyclic Redundancy
Check) information is stored.
Message Communication Protocol from an SCS

SCS verifies the CRC in a request message from the Modbus master, and discard the message
if detects an error.
l Response Message under Normal Conditions

In the case of functions of single coil status change, writing to a single holding register or
loop back:
The same message as the request message
In the case of functions of multiple coil status changes and writing to multiple holding
registers:
A part of the request message (slave address, function code, start number, number of coils
or number of holding registers)
In the case of read function:
The same slave address and same function code of the request message, and the read
data
IM 32S05B10-21E
B3-3
l Responses under Abnormal Conditions

When errors other than transmission errors is detected in a request message, SCS sends the
response message with the following information:
Slave address
Function code: The function code in a request message plus 0x80
Error code
Error check
The error codes to indicate abnormal conditions are as follows:
Table
Error Codes
Error code (hexadecimal)
Meaning of error
01
Function code error (non-existing function code)
02
Coil, input relay, register number error (out of range)
03
Error of the number of coils, input relays, or registers (out of range)
04
CPU not started
07
Unsupported diagnostic loop-back code
10
Use even numbered register
11
Use odd size register
12
Data setting error

The number of simultaneously writing exceeds four.
Writing size exceeds limit
Writing undefined variable or write inhibit variable
l Cases where no Response is Made

SCS does not respond to a request in the following cases:
A transmission error of a request message is detected (overrun, framing error, parity error or
CRC error)
Transmission specification setting values are invalid
The slave address in a request message is not the slave address set on the communication
module
The time interval between receiving one character and the next character is longer than the
setting value of the reception character interval timer
A protocol related error occurs (for example, a transmission is performed just when being
responding to a request)
Definitions of the serial communication module are being on-line change downloaded
Definitions of Modbus communication are being changed
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:

Maximum data update time = RS transmission time +

scan period of external connection function
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:

Maximum data update time =

RS transmission time +
scan period of the application logic x
number of writing requests from the external connection
function
IM 32S05B10-21E
B3-5
Diagnostic Information Messages

If a serial communication module is faulty, the SCS send a diagnostic Information message to
SENG and/or HIS via the control bus. This section describes the SCS diagnostic Information
messages.
l At IOM Error Occurrence/Recovery to Normal State

The diagnostic Information messages are sent via the control bus when an error occurs in the
serial communication module or the module recovers from an error.
The configuration error occurs if the serial communication driver cannot operate due to
configuration mismatch. For example, this error occurs if the serial communication driver has not
been downloaded to the serial communication module or if an application program different from
the defined serial communication driver has been downloaded.
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.
l At Serial Communication Error Occurrence

When an serial communication error occurs, no system alarm message is sent because the
Modbus master is assumed to handle the error.
l When Downloading Serial Communication Driver

When downloading a serial communication driver for the serial communication module, the
system alarm messages are sent via the control bus.
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)
l When Serial Communication Module is Added Online

Serial communication modules can be added or removed online. When a serial communication
module is added, diagnostic information messages (IOM Fail, and then IOM Recover) are sent
via the control bus.
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
l At Serial Communication Error Occurrence

When a serial communication error occurs, no system alarm message is sent because the
Modbus master is assumed to handle the error.
l When Downloading Serial Communication Driver

When downloading a serial communication driver for the serial communication module, the
following system alarm messages are sent via the control bus.
When starting download:
SCS0101 IOM Load Start FIO01 NODE01 SLOT01
At normal completion of download:
SCS0101 IOM Load Complete FIO01 NODE01 SLOT01
At abnormal completion of download:
SCS0101 IOM Load Error FIO01 NODE01 SLOT01 Error=A33D
IM 32S05B10-21E
C1-1
<C1.1 Overview of Subsystem Communication>
C1. Common Items Regarding

Subsystem Communication
Interfaces
The subsystem communication package enables communication, such as reading and
writing of subsystem data between SCSs and PLCs (Programmable Logic Controller) or
other subsystems connected to the SCSs communication module.
This chapter describes common subsystem communication functions that are not
dependent on subsystem types.
C1.1 Overview of Subsystem Communication
This section describes the structure of subsystem communication functions within the
SCS and gives an overview of communication between the subsystem and the SCS.
n Type of Subsystem Communication Package

The following subsystem communication package is available for SCSs. The communication
module in the SCS becomes the communication master.
Modbus Communication Package (for ALR111, ALR121)
IM 32S05B10-21E
C1-2
n Structure of Subsystem Communication Functions

An overview of subsystem communication is explained below:
Functional structure and data flow
Relationship of subsystems and the application logic
l Functional Structure and Data Flow

SENG
- SCS State Management
Window
- IOM Report
- Diagnostic Information
Window
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
Figure Functional Structure and Data Flow
IM 32S05B10-21E
C1-3
l Relationship of Subsystems and the Application Logic

Input data from subsystems are input to the application logic via the communication I/O data
management function.
Output values calculated by the application logic are output to subsystems via the
communication I/O data management function.
The subsystem communication program interprets communication protocols (such as the
Modbus protocol).
The communication I/O data management function is a general-purpose data management
function not dependent on communication protocols. The communication I/O data
management function manages the communication I/O data area consisting of 1000 words
in which subsystem register images are mapped.
The subsystem communication input FBs and subsystem communication output FBs are
used to access the communication I/O data management function from the application logic.
Subsystem
AI
DI
Subsystem
communication
module
Sequencer
DO
SCS
POU
Communication I/O data management

Registers
AI
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
Figure Relationship of Communication I/Os and Registers
IM 32S05B10-21E
C1-4
n Communication with Subsystems

The subsystem communication module communicates with each subsystem in accordance
with the transmission specifications and communication definitions set with subsystem
communication builders to refresh the images inside the module. The subsystem communication
module interprets subsystem communication protocols and performs communication based on
the protocols. Thus, the CPU only exchanges data with the subsystem communication module
and does not perform any processing specific to each subsystem communication type.
Communication I/O data area
Subsystem communication I/O refresh function
CPU

Communication
definitions
Transmission
definitions
Subsystem communication package

(interpretation of protocols, conversion to data)
Subsystem communication module
Subsystem
C010103E.ai
Figure Communication between SCS and Subsystem
IM 32S05B10-21E
C1-5
n Data Flow and Refresh Time

The data refresh time varies depending on the subsystem type, amount of acquired data
and transmission specifications. The following describes the flow of data not dependent on
subsystem types.
l Data Refresh Time (Input through Output)

3. Subsystem
communication
input FB
(read)
2. Refresh the
communication
I/O data area
(input)
1. Subsystem
communication
(read)
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
Run time = Dependent on the application logic

scan period and CPU load
Subsystem
communication
period
C010104E.ai
Figure Data Refresh Time (Input through Output)
l Data Flow and Timings
SEE
ALSO
1.
Subsystem communication (read)

The data acquisition period varies depending on the subsystem type and transmission
specifications.
2.
Refresh the communication I/O data area (input)

The data is read from the subsystem communication module to the communication I/O data
area at the beginning of the SCSs scan period.
3.
Subsystem communication input FB (read)

The data is read from the communication I/O data area (input) when the subsystem
communication input FB is executed.
4.
Subsystem communication output FB (write)

The data is written to the communication I/O data area (output) when output from the
subsystem communication output FB.
5.
Flush the communication I/O data area (output)

At the end of the SCSs scan period, the communication I/O data area is flushed and the
data is written to the subsystem communication module.
6.
Subsystem communication (write)

The data acquisition period of each subsystem from the subsystem communication module
varies depending on the subsystem type and transmission specifications.
For the transmission specifications, see the following:

n Transmission Specification in C3.1, Communication Specifications
IM 32S05B10-21E
C1-6
n Period of Subsystem Communication and Communication Time

The following describes the period of subsystem communication and communication time based
on a serial communication module.
l Period of Serial Communication

Subsystem communication is performed asynchronously with the scan period of the application
logic execution function. Data is written only when written by the CPU.
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
Figure Subsystem Communication (Example Numbers of Communication Definitions for Port 1 is n)
In serial communication, each port of the serial communication module communicates at a

different period. The communication period of each port represents the sum of times required to
communicate all communication definitions set for the port.
Example)

Communication definition 1: Port 1
Communication period of port 1 = (Communication time for communication definition 1) +

(Communication time for communication definition 2)

Communication period of port 2 = (Communication time for communication definition 3) +

(Communication time for communication definition 4)
n Assurance of Simultaneity of Communication Data

In the SCS (between the subsystem communication module and the communication I/O data
management function), simultaneity of data is assured in units of 32 bits.
Between the subsystem communication module and each subsystem, data units in which
simultaneity is assured varies depending on the subsystem communication package and the
subsystem.
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
n Handling of Subsystem Data

The table below summarizes the handling of subsystem data in the SCS by data type.
Table
Types of Subsystem Data Handled
Subsystem data type
Data type in SCS
Remark
Bit (DI/DO)
BOOL (bit)
With/without bit reversing
32-bit floating
REAL (32-bit floating)
With/without word reversing
16-bit signed integer
DINT (32-bit signed integer)
16-bit unsigned integer
32-bit signed integer
With/without word reversing
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 Output Enable Operation

Following an initial cold start of the SCS, input communications from subsystems will start
as soon as the subsystem communication module is started. Output communications to
subsystems will start following the output enable operation for subsystem communication.
Note, however, that output will start immediately after the subsystem communication
module is started following a recovery from an error, no output enable operation is required
in such a case. Readback of output will start as soon as the subsystem communication
module is started.
Output from the subsystem communication module is disabled only after an initial cold start
of the SCS.
Regardless of the status of the subsystem communication module, output enable operation
for the safety output modules can be performed at any time.
Output enable operation can be performed even when a subsystem communication error is
present. In this case, output will start only for those outputs that can be communicated.
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.
n Status Monitoring from SENG or HIS

The status of the subsystem communication module can be monitored in the status display
window of the SENG or HIS.
From a SENG, communication program names and error information can be referenced
using SCS Maintenance Support Tools IOM Report.
The forcing status of subsystem communication data and errors in the subsystem
communication module are notified as diagnostic information messages.
IM 32S05B10-21E
C1-8
<C1.2 Dual-redundant Communication>
C1.2 Dual-redundant Communication

This section gives an overview of dual-redundant communication.
To implement dual-redundant communication, the dual-redundant option of the

subsystem communication package is required.
n Data Flow in a Dual-redundant Configuration of Subsystem

Communication Modules
If the ALR111 or ALR121 is used, dual-redundant communication can be implemented by
connecting two serial communication modules side by side. Note, however, that dual-redundant
communication cannot be implemented without readback.
The figure below illustrates how data flows in a communication with readback in a dual-redundant
configuration of subsystem communication modules.
SCS(CPU)
Subsystem
communication
input FBs
Application logic (POU)
Subsystem
communication
output FBs

Input
Output
Communication I/O images

(even-number slots)
Communication I/O images

(odd-number slots)
Subsystem
communication
module
(standby side)
Input
Output
Input
Output
Input
Input
Output
Output
Subsystem communication
module (control side)
Reading of
input data
Readback of
output data
Reading of
input data
Writing of
modified data
Subsystem
C010201E.ai
Figure Data Flow in Dual-redundant Configuration of Subsystem Communication Modules
IM 32S05B10-21E
<C1.2 Dual-redundant Communication>
C1-9
l Flow of Input Data

The two dual-redundant subsystem communication modules both communicate with subsystems
periodically and refresh the images inside the subsystem communication modules.
The SCS references the image (area for input) inside the subsystem communication module on
the control side. The image (area for input) inside the module is copied to the communication I/O
image in odd-number slot and set in the communication I/O data area.
l Flow of Output Data

Data is written to subsystems only from the subsystem communication module on the control
side. The details of output data flow are as follows:
The CPU of the SCS refreshes only the data for the subsystem communication module on
the control side.
Both the subsystem communication modules on the control and standby sides read the data
output from each subsystem (readback).
The subsystem communication module on the control side compares the value read back
from the subsystem and the write data from the CPU, and writes the output data to the
subsystem only when the two values are different. If the two values are the same, the
subsystem communication module on the control side reflects the value read back from the
subsystem in the image (area for output) inside the module.
The subsystem communication module on the standby side does not write data, so data is
not refreshed by the CPU. The image (area for output) inside the subsystem communication
module on the standby side is refreshed via readback of the output subsystem data that
have been changed via writing from the subsystem communication module on the control
side. This operation equalizes the output data of both the subsystem communication
modules on the control and standby sides.
SEE
ALSO
For details on readback communication, see the following:

C3.6, Readback Communication
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.
n Support of Dual Redundancy

To provide dual redundancy of subsystem communication modules, the dual-redundant option of
the subsystem communication package is required.
IM 32S05B10-21E
<C1.3 Error Handling Actions>
C1-10
C1.3 Error Handling Actions
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.
n Error Conditions and Error Handling Actions

The table below summarizes the conditions in which error handling actions occur, as well as
specific actions.
Table
Conditions in Which Error Handling Actions Occur and Specific Actions
Condition
Impact on application logic (Subsystem

communication I/O FBs)
Input data: Value from the subsystem

Initial cold start of the SCS (the SCSs
Input status: GOOD
operating mode is shifting from Waiting
Output status after output enable
Mode to Running Mode)
operation: GOOD
Communication error
(subsystem communication error,
communication definition error)
Faulty subsystem communication
module
Restart of the subsystem
communication module due to online change download
Path error between the CPU and
subsystem communication module
Upon occurrence
Input data: Value of Input Processing at
Fault
Input status: BAD
Output status: BAD
After recovery
Input status: GOOD
Output status: GOOD
During on-line change download
Input data: 0 or FALSE
Input status: BAD
Output status: BAD
Addition of new subsystem

communication I/O FB (on-line change
download) (*5)
After on-line change download
Input status: GOOD
Output status: GOOD
On-line addition of subsystem

communication module (*6)
*1:
*2:
*3:
*4:
*5:
*6:
Until the module starts up

Input data: 0
Input status: BAD
Output status: BAD
After the module started up
Input/output status: Status of
communication with the subsystem
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.
Until the module starts up:

Communication is not possible.
After the module started up:
Communication starts.
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. After that, values from the
application logic are output.
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
<C1.3 Error Handling Actions>
n Restart of the Subsystem Communication Module When Subsystem

Communication Data Is Locked
When the following operations to be performed and the operations may cause the subsystem
communication module restart, it is recommended to lock the subsystem communication data
beforehand:
Before performing an on-line change download requiring a restart of the subsystem
Before replacing the failed subsystem communication module. Perform an IOM download
after the replacement.
The table below lists the locked communication I/O data before and after recovery of the
subsystem communication module to a normal state.
Table
Statuses of Locked Communication I/O Data

Before recovery
Communication
input
Logical data
Physical
data
Logical data
Communication
output
Physical
data
Output to subsystem
Data value: Value immediately before

locking
Data status: Value immediately before
locking
occurrence of an error
Data status: BAD
Data value: Value from the application
logic
locking
locking
Data status: BAD
Communication is not possible.
After recovery
locking
locking
Data value: Value from the subsystem
Data status: GOOD
Data value: Value from the application
logic
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
n Notification of Error Conditions

Error conditions such as errors in the subsystem communication module and those relating
to subsystem communication are notified to the application logic, SENG and HIS.
To handle error conditions in the application logic, use system FBs for subsystem
communication.
With the use of system FBs for subsystem communication, an application logic that detects
unlocked subsystem communication data and overflow of lock limit can be created. If any
subsystem communication data remains unlocked or the number of locks exceeds the
maximum value, a diagnostic information message will be notified to the SENG or HIS.
n Diagnostic Information Messages

If the subsystem communication module status or communication status with any subsystem
has changed, a diagnostic information message is generated to notify the change. Diagnostic
information messages are generated in the following conditions:
The subsystem communication module has started or shut down.
A subsystem communication error has occurred or has been reset.
A subsystem communication output enable operation has been performed.
IM 32S05B10-21E
C1-12
<C1.4 Setting Items Relating to Subsystem Communication>
C1.4 Setting Items Relating to Subsystem

Communication
The following describes the setting items relating to subsystem communication.

Subsystem communication builders can be used to set items relating to communication
modules and those relating to communication I/O data.
n Builders for Subsystem Communication

SENG
I/O Wiring View
I/O Parameter Builder
Communication
I/O Builder
Tag Name 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
Figure Subsystem Communication Builders
l Subsystem Communication Settings

Device definitions provide settings relating to the mounting position and redundancy of the
subsystem communication module.
Transmission definitions provide settings relating to the transmission specifications of
the subsystem communication module. The setting items vary depending on the type of
Communication definitions provide settings relating to data accesses to/from subsystems.
The setting items vary depending on the communication protocol.
Wirings provide settings for assigning the communication I/O data area to subsystem
communication I/O FBs.
IM 32S05B10-21E
C1-13
l Settings Related to Integration with CENTUM

Tag name definitions provide settings for assigning tag names to subsystem communication
I/O FBs.
n Engineering Procedure Using Related Builders

The I/O Wiring View, I/O Parameter Builder, Communication I/O Builder and Dictionary View are
used to create communication definitions. The procedure and builders used in each step are
explained below.
1.
Define subsystem communication I/O FBs using the Dictionary View.
2.
Define a subsystem communication module using the I/O Wiring View.

Add a subsystem communication module, and set its mounting position (node number, slot
number) and specify whether to use a dual-redundant or single configuration.
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.
I/O Wiring View
I/O Parameter Builder
Communication I/O Builder
Dictionary View
1. Definition of subsystem
communication I/O FBs
using Dictionary View
parameters
4. Assignment of
communication I/Os
5. Assignment of element
numbers and subsystem
C010402E.ai
Figure Engineering Procedure Using Related Builders
IM 32S05B10-21E
C1-14

Define using
Communication I/O Builder
Define using I/O Wiring View

%WB200101
Subsystem
communication
module
Define using Dictionary View
%WB200301
Mapping of
subsystem
communication
data and
communication
I/O data area
%WB210101
Program
(application logic)
I/O FB
Mapping of
element
numbers and
subsystem
communication
I/O FBs
I/O FB
I/O FB
%WB210301
Subsystem
communication
module
C010403E.ai
Figure Wiring of Subsystem Communication I/O FBs and Element Numbers
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
Type of wirable subsystem communication I/O FBs
Analog input (16-bit signed integer)

SCI_I
Analog input (16-bit unsigned integer)

Analog input (32-bit floating)
SCI_R
Analog output (16-bit signed integer)

SCO_I
Analog output (16-bit unsigned integer)

Analog output (32-bit floating)
SCO_R
Discrete input
SCI_B
Discrete output
SCO_B
IM 32S05B10-21E
C1-15
C1.4.1
Settings Using the I/O Parameter Builder
The I/O Parameter Builder is used to specify settings relating to subsystem

communication modules.
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
n Subsystem Communication Module Settings

Subsystem communication module settings are specified in the Module tab where common
communication module parameters are set, and in the Port tabs where port parameters are set.
The Port tabs include the Port 1 and Port 2 tabs. Together with the Module tab, thus, a total of
three tabs are available.
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
Figure Module Tab (Serial Communication Module for Subsystem Communication)
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
l Port 1 and Port 2 Tabs

The setting items in the Port 1 and Port 2 tabs change in accordance with the module type and
the Connection Device setting in the Module tab. The setting items are the same between the
Port 1 and Port 2 tabs.
Pjt:SCS1020 File:IOMDEFSB.edf
I/O
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
Control Line (RS Control)
No
Control Line (DR Check)
Yes
Control Line (CD Check)
No
1-3 SAI143([
1-5 SAI143([
10 ms
Reception Inter-Character Timer

Response Timeout
Communication Retry
30 s
Interval of Connection Retries

2-Wire/4-Wire
4-Wire
Option 1
Option 2
Option 3
Option 4
C010405E.ai
Figure Port 1 Tab (Example where S_MODBUS is Set as Connection Device)
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
Specify the baud rate.
Stop Bits
Specify the stop bits.
Parity
Specify the type of parity.
Data Bits
Specify the data bit length of subsystem data to be

transmitted.
Control
Line
C1-18
Remark
RS Control
Specify whether or not to use RS control when sending

data from the ALR111M.
Valid only when the ALR111M is used.
DR Check
Specify whether or not to use DR signal line check

when sending data from the ALR111M.
CD Check
Specify whether or not to use CD signal line check

when sending data from the ALR111M.
Reception InterCharacter Timer
Specify the period to monitor inter-character time when

data is received by the ALR111M/ALR121M.
Response Timeout
Set the timeout period to wait for subsystem response.
Communication Retry
Set the number of retries to be attempted after a

communication error occurs.
Interval of Connection
Retries
Set the interval of communication with a station that

generated a communication error to check for recovery
of communication (recovery communication).
2-Wire/4-Wire
Specify the 2-wire or 4-wire connection method.
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.
l Reception Inter-Character Timer

The reception inter-character timer (reception inter-character timeout setting) is a function
for monitoring the time between adjacent characters received (interval after one character
is received until the next character is received) by the ALR111M/ALR121M. In the Modbus
communication package, reception is deemed complete if a time corresponding to the reception
inter-character time has elapsed.
If communication is performed via a modem or other device that provides data buffering function,
this value needs to be set in consideration of the communication delay (inter-character delay)
caused by the buffering at the modem. Note, however, that increasing the reception intercharacter time will affect the RS communication time, since completion of reception is determined
based on elapse of this time.
Default:
10 ms
Setting range: 0 to 99999 ms
l Response Timeout
Set the timeout period to wait for subsystem response, in seconds.
Default:
4 sec.
Setting range: 0 to 99 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
l Interval of Connection Retries

Set the interval of communication with a station that generated a communication error to check
for recovery of communication (recovery communication).
Default:
30 sec.
Setting range: 1 to 999 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
Settings Using the Communication I/O Builder
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
n Communication I/O Settings

The Communication I/O Builder is used to perform the following tasks:
Assign subsystem communication data to the communication I/O data area (%WW)
Define communication details in the communication I/O data area in accordance with the
subsystems
Wire %WB elements and communication I/O variables
The structure of the Communication I/O Builder window is shown below.
Menu bar
Title bar
Toolbar
Communication I/O Builder-[Pjt:SCS0101 File:CommIO.edf]

File Edit View
Tool
Window
Help
Comm. I/O Definition

Element
Comm. I/O Wiring
Buffer
Program Name
Port
Size
2
Station
%WW2001
6 1-7S_MODBUS
%WW2002
* *
%WW2003
* *
%WW2004
* *
%WW2005
* *
%WW2006
* *
1
*
*
%WW2007
%WW2008
%WW2009
%WW2010
Message
Ready
Data menu area
Position : Line 1 Column 4
Message display area
Status bar
Workspace
C010406E.ai
Figure Structure of Communication I/O Builder Window
IM 32S05B10-21E
C1-22
n Comm. I/O Definition Tab

Buffer

Element
Comm. I/O Wiring
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
Figure Comm. I/O Definition Tab
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
nnnn: 2001 to 3000
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:
The total size shall not exceed 1000.
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
When changing the buffer for %WW2001 to 4
Example of Definitions Before Change

Element
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
Example of Completed Item Settings
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:
2: No, 3: Words (word reversing)
Discrete input or output:
1: Bits (bit reversing), 2: No
16-bit analog input or output:
Fixed to 2: No.
IM 32S05B10-21E
C1-26
l Input Processing at Fault

Specify the value to be input to the application logic, instead of the input value received from the
subsystem, upon detection of an error. This field can be specified only when discrete input or
analog input is selected in the Data Type field.
The errors that trigger this setting include errors occurring on both sides of the path from the CPU
to the communication module, errors in the communication module, and communication errors
between subsystems and the communication module. Errors in subsystems are not applicable.
Table
Input Processing at Fault (Discrete Input)

Selection
Description
Set the input value to 0 upon error detection.
Set the input value to 1 upon error detection.
Hold
Table
Retain the value before detection of an error (default).
Input Processing at Fault (Analog Input)

Selection
2
3
Description
Hold
Fixed Value
Retain the value before detection of an error (default).

Use the input value specified in Input Value at Fault upon error detection.
l Input Value at Fault

If Fixed Value is specified in Input Processing at Fault, specify the input value to be used
instead of the input value received from the subsystem.
Default:
Input range:
Value consisting of up to 11 digits including a negative sign and/or a decimal

point
IM 32S05B10-21E
C1-27
n Comm. I/O Wiring Tab

The Comm. I/O Wiring tab shows a list of elements corresponding to the areas assigned in the
Comm. I/O Definition tab.
SCI_I
SCI_R SCI_B S
ALARM001_CLS1@SYSiFBD
ALARM001_SUM@SYSiFBD
ANLGI001_HHH@HISIFFBD
ANLGI001_HTRP@HISIFFBD
ANLGI001_LLL@HISIFFBD
ANLGI001_LTRP@HISIFFBD
ANLGI001_SOER@HISIFFBD
ANLGI002_LLL@HISIFFBD
ANLGI002_LTRP@HISIFFBD
ANLGI002_SOER@HISIFFBD
Element
Comm. I/O Wiring
Data Type
Variable Name
Type
%WB200101 Input (16-Bit Signed)

C010408E.ai
Figure Comm. I/O Wiring Tab
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.
%WB200101, %WB200201, %WB200301, %WB200401
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
Examples of Variable Specification

Variable
Scope
Description
SCIB1
Global
Global variable
SCIB2@PROG1
PROG1
Local variable of PROG1 function
FB01.SCIB3
Global
Internal variable SCIB3 of user-defined function block instance FB01
FB01.SCIB3@
PROG1
PROG1
Internal variable SCIB3 of user-defined function block instance FB01 defined

locally in PROG1 function
FB01.FB2.SCIB3
Global
Internal variable SCIB3 of user-defined function block instance FB2, which is

used in user-defined function block instance FB01 (maximum limit of function
block nesting)
Note 1: There are following notices:

If an instance is a local variable, Scope name must be added after @.

If an instance is defined as an internal variable for a User-defined Function Block, assign an instance name to the Userdefined Function Block from Dictionary View in Workbench.

The variable name is specified in the format of [Instance Name].[Internal Variable Name], and up to two nests are permitted
in each variable.
Note 2: The variable name can contain up to 67 single-byte characters. Communication I/O Builder also checks the following items:

The variable name consists only of alphanumeric characters and @, . or _. If any other character is used, an error will
occur.

The variable name begins with an alphabetic character or _; otherwise, an error will occur.

In the above table, FB01.SCIB3 and FB01.SCIB3@PROG1 have one nest, while FB01.FB2.SCIB3 has two nests.
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
<C1.5 Forcing of Subsystem Communication Data>
C1.5 Forcing of Subsystem Communication Data

This section describes forcing of subsystem communication data.
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.
n Flow of Forced Data

Communication I/O data include logical data and physical data, just like I/O variables. Both
logical data and physical data can be referenced from an SENG.
When subsystem communication data is locked, the communication I/O data management
function cuts off the flow of logical data and physical data. If communication input data is
locked, inputs from subsystems will not reach the application logic. If communication output
data is locked, outputs from the application logic will not reach subsystems.
The values set to communication input data via forcing are input to the application logic, and
the values set to communication output data via forcing are output to subsystems.
SCS
Application logic execution
Subsystem
communication
input FBs
Forcing
(communication input data)
Referencing of communication
I/O data
Forcing
(communication output data)
Logic
Subsystem
communication
output FBs
Communication I/O data

management
(logical data)
Mapping elements
(%WB)
In accordance with locking

(physical data)
Subsystem
C010501E.ai
Figure Communication I/O Data Management and Forcing

IM 32S05B10-21E
C1-30
n Locking Subsystem Communication Data

Subsystem communication data can be locked or unlocked in the units specified below. All
subsystem communication data in each scope will be locked or unlocked.
Locking unit
Scope
All subsystem communication module inputs/outputs
All I/O data of a specified module
All subsystem communication module inputs
All input data of a specified module
All subsystem communication module outputs
All output data of a specified module
Lock operation is performed in the Communication I/O Lock window.

When the subsystem communication module is locked, refreshing of inputs to the
application logic and outputs from the application logic will stop and the previous values will
be retained.
Locking and unlocking will both generate a diagnostic information message.
All outputs of a module can be locked, even for a subsystem communication module for
which no output communications have been defined. As long as subsystem communication
outputs are locked before an on-line change download, output data will be locked even
when output communication definitions are added, via the on-line change, to the module
with no output communication definitions. The same applies to inputs.
l SCS Operations While Subsystem Communication Data is Locked

The table below indicates how the SCS operates when subsystem communication data is
locked.
Table
SCS Operations While Subsystem Communication Data is Locked

What is locked
Subsystem communication I/O FBs
inputs
The values immediately before locking

are retained for data values and data
Communication is not affected.
statuses.
outputs

are used as the output values to
are retained for data statuses.
subsystems.
IM 32S05B10-21E
C1-31
n Setting of Values to Subsystem Communication Data

Set data values and status after subsystem communication data is locked. If subsystem
communication data is not locked when data values and status are set, an error will occur.
A data value can be set for each communication data item.
A data status can be set for each communication definition. Changing a data status will
affect all communication data in the same communication definition, so check the potential
impact thoroughly before changing a data status.
When a value is set, a diagnostic information message will be notified.
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
Setting of Values to Subsystem Communication Data

Setting target
Subsystem communication I/O FBs
The values set in the Communication

I/O Lock window are reflected in data
inputs
values and statuses.
Communication is not affected.
The data statuses set in the

The data values set in the
Subsystem communication Communication I/O Lock window are
Communication I/O Lock window are
outputs
output from subsystem communication
used as the output value to subsystems.
output FBs.
n Management of Subsystem Communication Data Lock Status

By using the SYS_FORCE_SC function block, the lock status of subsystem communication
data can be handled in the application logic.
The SYS_FORCE_SC function block detects a lock timeout of subsystem communication
data and forcibly unlocks subsystem communication data.
Locking of subsystem communication data does not affect the lock management of I/O
variables and internal variables. It does not affect the SYS_FORCE function block.
Only whether or not subsystem communication data is locked is detected. The number of
locks is not counted.
IM 32S05B10-21E
C1-32
<C1.6 Communication I/O Lock Window>
C1.6 Communication I/O Lock Window
This section gives an overview of the Communication I/O Lock window.

The Communication I/O Lock window is used to lock or force inputs from subsystems or
outputs to subsystems in the subsystem communication function.
In SCS Simulation test, it is possible to set values to multiple communication data
together. Therefore, the initial values of communication data and testing patterns can be
defined all together.
The Communication I/O Lock window is used to perform the following tasks.
Perform forcing during debugging of an application logic that uses subsystem
communication
Disconnect inputs/outputs during maintenance of a subsystem communication
module
Fix communication inputs/outputs from/to a subsystem during on-line change
download
n Positioning of the Communication I/O Lock Window

The Communication I/O Lock window is one of the windows used mainly for maintenance
purposes. The Communication I/O Lock window is launched from SCS Manager.
The positioning of the Communication I/O Lock window is shown below.
SENG
SCS Manager
Launch
Launch
Engineering
Maintenance
Builders
I/O Lock Window

SCS Link Transmission
Lock Window
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
Figure Positioning of Communication I/O Lock Window in SENG
IM 32S05B10-21E
C1-33
In the Communication I/O Lock window, communication inputs/outputs can be locked or

forced via the communication I/O data management function included in the SCSs subsystem
communication functions.
SENG
Communication I/O
Lock window
I/O Lock window
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
Figure Relationship with SCS and Subsystem
n Functions of the Communication I/O Lock Window

l Locking and Unlocking
In the Communication I/O Lock window, subsystem communication data inputs and outputs can
be locked or unlocked. The lock status is also displayed for locked data.
Locking and unlocking of data can be performed in the following units:
Lock or unlock all input data in a communication module
Lock or unlock all output data in a communication module
Lock or unlock all input/output data in a communication module
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
n Start the Communication I/O Lock Window

1.
Check if the SCS security level is 0 or 1 using the SCS security level operation function.
2.
Put the SCS Manager into Debug mode or Editing mode.

To change to Debug mode, choose [Debug] from [Debug] menu or click Debug button on
the toolbar.
3.
Select [Maintenance] from the [Tools] menu of SCS Manager.

The Maintenance Launcher menu appears.
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.
n Exit the Communication I/O Lock Window

To exit the Communication I/O Lock window, choose [Exit] from [File] menu.
If any communication module is locked when exiting the Communication I/O Lock window, the
confirmation dialog box appears. Click [OK] to close the Communication I/O Lock window.
Communication I/O Lock Window
Communication I/O module is locked.
OK
C010603E.ai
Figure Confirmation Dialog Box
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
Structure of the Communication I/O Lock Window
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
Communication I/O Lock Window [Pjt:SCS0101]

File Edit Lock Option
MODULE LIST
L D
Module
3-1 ALR111
3-1 ALR111
3-3 ALR111
3-3 ALR111
Drop-down list box
*****SCS_TARGET*****
Inputs/Outputs
I/O
I
O
I
O
Toolbar
Comment
Comment
Comment
Comment
Comment
COMMUNICATION DATA LIST
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
200103 DI0002.V FALSE

DI0002.STS GOOD
TRUE
GOOD
200104 DI0003.V FALSE

DI0003.STS GOOD
TRUE
GOOD
200105
DI0004.V TRUE
DI0004.STS GOOD
TRUE
GOOD
200106 DI0005.V FALSE

DI0005.STS GOOD
TRUE
GOOD
200107 DI0006.V FALSE

DI0006.STS GOOD
TRUE
GOOD
200108 DI0007.V FALSE

DI0007.STS 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
Input Modules Selected: 1/2 Output Modules Selected 1/2
Message display area
Status bar
Communication Data List View

Communication Module List View
C010604E.ai
Figure Communication I/O Lock Window
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:
Indicates communication with the SCS.
SCS_SIMULATOR: Indicates communication with the SCS Simulator.

<Non>:
Indicates the SCS is not running.
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
Import Values (*1)
Imports the values for setting all together to communication data from a file.
Export Values (*1)
Exports the values for setting all together to communication data to a file.
Exit
Exits from the Communication I/O Lock window.
*1:
Displayed only when the SCS project target name is SCS_SIMULATOR.
Table
[Edit] Menu
Menu item
Description
Cut (*1)
Deletes the selected character string and copies it onto the clipboard
Copy (*1)
Copies the selected character string onto the clipboard
Paste (*1)
Inserts the character string stored in the clipboard
Delete (*1)
Deletes the selected character string
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
Locks all modules selected.
Unlock Modules
Unlocks all modules selected.
Set Values (*1)
Sets all values of communication data.
*1:
IM 32S05B10-21E
C1-37
Table
[Option] Menu
Menu item
INT
Numerical Display
REAL
Data Acquiring Mode

*1:
Description
Decimal
Displays in decimal number format. (*1)
Hexadecimal
Displays in hexadecimal number format.
1.234E+12
Exponential notation
12.34567
Displays 5 decimal places.
123.4567
1234.567
12345.67
123456.7
All Modules
Changes data acquiring mode to All Modules mode
Selected Modules
Changes data acquiring mode to Selected Modules

mode
A negative sign is added if the value of a signed integer is negative.
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:
Sets all values of communication data.

Same as choosing [Set Values] from [Lock] menu.
Changes data acquisition mode. Same as choosing the [Data Acquiring Mode] from
[Option] menu. Toggles between All Modules mode and Selected Modules mode.
n Data Acquisition Mode

The data acquisition mode is used when acquiring data values and statuses from an SCS.
All Modules mode
Communication data corresponding to the communication definitions of all subsystem
communication modules defined in the applicable SCS project will be acquired sequentially.
Selected Modules mode
Communication data corresponding to the communication definitions of the subsystem
communication modules selected in the Communication Module List View will be acquired
sequentially.
While data is acquired, Updating Selected Modules is displayed in the Communication
Module List View and Communication Data List View.
IM 32S05B10-21E
C1-38
n Communication Module List View

The Communication Module List View shows a list of subsystem communication modules
defined in the current SCS project.
Two lines, one for subsystem communication inputs and the other for subsystem communication
outputs, are displayed for each subsystem communication module. Even when input/output
communications are not defined for the module, or subsystem communication I/O FBs are not
wired to the modules communication definitions, this view always shows two lines for each
With the subsystem communication modules used in a dual-redundant configuration, information
of the module in the odd-number slot is displayed regardless of which module is currently
operating. Note, however, that the L and D fields show the corresponding statuses of the module
on the control side.
The items displayed in the Communication Module List View are shown below.
Table
Items Displayed in Communication Module List View

Item
Description
Lock status of communication data for the subsystem communication module
Consistency/discrepancy of logical data and physical data of communication data for

the subsystem communication module
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
Comment for the subsystem communication module
l Lock Status of Communication Data for Subsystem Communication Modules

Table
Lock Status Display (L Field)

Display
Meaning
(No symbol)
None of the communication data is locked.
(red)
All communication data are locked.
? (black)
Communication with the SCS is disabled.
IM 32S05B10-21E
C1-39
l Consistency/Discrepancy of Logical Data and Physical Data of

Communication Data for Subsystem Communication Modules
Discrete inputs and outputs are deemed to have discrepancy if the logical data and physical
data of the data value or data status are different.
Analog inputs and outputs are deemed to have discrepancy if the logical data and physical data
of the data status are different.
Table
Data Consistency/Discrepancy Display (D Field)

Display
Meaning
(No symbol)
All communication data are consistent.
(yellow)
Some communication data have discrepancy.
(red)
All communication data have discrepancy.
? (black)
The consistency/discrepancy display of communication data for each subsystem communication

module varies depending on the data acquisition mode.
When the data acquisition mode is All Modules
Data corresponding to all subsystem communication modules defined in the applicable SCS
project will be refreshed and displayed sequentially.
When the data acquisition mode is Selected Modules
Data corresponding to the subsystem communication modules selected in the
Communication Module List View will be refreshed and displayed sequentially. A ? symbol
will be shown in the D field for subsystem communication modules that are not selected.
l Filtering
Subsystem communication modules can be filtered based on input/output classification by using
the drop-down list box.
Table
Drop-down List Box in Communication Module List View
Menu item
Operation
Inputs/Outputs
Both the input and output lines of communication definitions are displayed.
Inputs
Only the input lines of communication definitions are displayed.
Outputs
Only the output lines of communication definitions are displayed.
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
Pop-up Menu in Communication Module List View
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
n Communication Data List View

The Communication Data List View shows information regarding the communication data wired
to subsystem communication I/O FBs, for the subsystem communication modules selected in the
Communication Module List View.
When the subsystem communication input line of a communication module is selected in the
Communication Module List View, information of the communication data corresponding to the
applicable input communication definition will be displayed.
When the subsystem communication output line of a communication module is selected in the
Communication Module List View, information of the communication data corresponding to the
applicable output communication definition will be displayed.
Table
Items Displayed in Communication Data List View

Item
Description
Definition
Communication definition
%WB
%WB element number %WBnnnnbb (nnnn: 2001 to 3000, bb: 01 to 16)
Lock status of communication data
Consistency/discrepancy of communication data
Instance
Instance name of the wired subsystem communication I/O FB
Logical Value
Logical data of data value and data status
Physical Value
Physical data of data value and data status
Set value (*1)
Set value of data value and data status, respectively
Comment
Comment for the subsystem communication I/O FB
*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:
Communication definition number
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:

IM 32S05B10-21E
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.
l %WB Element Number

The %WB element number included in the communication definition is displayed.
l Lock Status of Communication Data

Table
Lock Status Display (L Field)

Display
Meaning
(No symbol)
Communication data is not locked.
(red)
Communication data is locked.
? (black)
l Consistency/Discrepancy of Communication Data

Discrete inputs and outputs are deemed to have discrepancy if the logical data and physical
data of the data value or data status are different.
Analog inputs and outputs are deemed to have discrepancy if the logical data and physical data
of the data status are different.
Table
Communication Data Consistency/Discrepancy Display (of D Field)

Display
Meaning
(No symbol)
Communication data is consistent.
(red)
Communication data has discrepancy.
? (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.
l Logical Data and Physical Data

For BOOL-type data, [TRUE] or [FALSE] is displayed. DINT-type data and REAL-type data are
shown in the display format specified in the [Option] menu. The data status is displayed as either
[GOOD] or [BAD]. If communication with the SCS is disabled, [******] is shown.
IM 32S05B10-21E
C1-42
l Refreshing of Communication Data Consistency/Discrepancy, Logical Data

and Physical Data Display
How the consistency or discrepancy of each communication data is displayed, and how data
values and statuses of logical data and physical data is refreshed, depend on the data acquisition
mode.
When the data acquisition mode is [All Modules]
Data will be acquired sequentially from the communication definitions of all subsystem
communication modules defined in the applicable SCS project. The display of the
Communication Data List View will be refreshed once communication data is acquired.
When the data acquisition mode is [Selected Modules]
Data will be acquired sequentially from the communication definitions of the subsystem
communication modules selected in the Communication Module List View. If only
subsystem communication module inputs are selected, data will be acquired only from
the input communication definitions. If only subsystem communication module outputs
are selected, data will be acquired only from the output communication definitions. The
display of the Communication Data List View will be refreshed once communication data is
acquired.
l Filtering
The communication data to be displayed can be filtered using the drop-down list box.
Table
Drop-down List Box of Communication Data List View

Item
Operation
All Data
Information of all communication data is displayed.
Locked Data
Only information of locked communication data is displayed.
Unlocked Data
Only information of unlocked communication data is displayed.
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
Items on Pop-up Menu in the Communication Data List View

Items
Description
Cut
Same as [Cut] command on [Edit] menu.
Copy
Same as [Copy] command on [Edit] menu.
Paste
Same as [Paste] command on [Edit] menu.
Delete
Same as [Delete] command on [Edit] menu.
Select All
Same as [Select All] command on [Edit] menu.
Input Values >
Set .V=TRUE
Sets the data of Set Value to TRUE (only for DI/DO).
Set .V=FALSE
Sets the data of Set Value to FALSE (only for DI/DO).
Clear .V
Clears the data of Set Value.
Set .STS=GOOD
Sets the data status of Set Value to GOOD.
Set .STS=BAD
Sets the data status of Set Value to BAD.
Clear .STS
Clears the data status of Set Value.
IM 32S05B10-21E
C1-43
l Selecting Communication Data

Only when the SCS project target name is SCS_SIMULATOR, the communication data can be
selected on Communication Data List View as below.
Clicking a communication data while pressing the [Shift] key on the keyboard, the
communication data of the continuous lines can be selected.
Clicking a communication data while pressing the [Ctrl] key on the keyboard, the
communication data of the separated lines can be selected.
Choosing [Select All] from pop-up menu, all communication data can be selected.
n Message Display Area

The results of all lock, all unlock and forcing operations are displayed as messages. The
displayed messages are cleared every time a new operation is performed.
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
Operations in the Communication I/O Lock Window
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.
n Selection of Subsystem Communication Modules

A desired subsystem communication module can be selected in the Communication Module List
View.
Selecting [Inputs/Outputs] in the drop-down list box will display communication definitions
for all inputs and outputs.
Selecting [Inputs] in the drop-down list box will display communication definitions for all
inputs.
Selecting [Outputs] in the drop-down list box will display communication definitions for all
outputs.
The following operations will display communication data in the Communication Data List View:
Clicking an input line or output line of a subsystem communication module without
pressing the [Shift] key or [Ctrl] key on the keyboard will display communication data for the
communication definitions of the subsystem communication module specified in the clicked
line.
Clicking an input line or output line of subsystem communication modules while holding
down the [Shift] key on the keyboard will display communication data for the communication
definitions of the subsystem communication modules specified in the lines between the
previously clicked (without [Shift] key) line through the line clicked this time.
Clicking an input line or output line of subsystem communication modules while holding
down the [Ctrl] key on the keyboard will display communication data for the communication
definitions of the subsystem communication modules specified in the clicked line, in addition
to the communication data currently shown.
Selecting [Select All] in the pop-up menu on the Communication List View will display
communication data for the communication definitions of all subsystem communication
modules currently shown in the Communication Module List View.
IM 32S05B10-21E
C1-45
n All Lock of Subsystem Communication Modules

All input data or output data of a selected subsystem communication module or all subsystem
communication data of the entire module can be locked.
1.
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
Figure Lock Confirmation Dialog Box
n All Unlock of Subsystem Communication Modules

All input data or output data of a selected subsystem communication module or all subsystem
communication data of the entire module can be unlocked.
1.
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
Figure Unlock Confirmation Dialog Box
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
Figure Unlock Reconfirmation Dialog Box
6.
Click [OK] to perform the unlock. Click [Cancel] to cancel the operation.
IM 32S05B10-21E
C1-46
n Set Value to Each Communication Data

For each communication data, the value of data and data status can be set.
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
Figure Write Data Value Dialog Box (Discrete Input/Output)

Write data value
I320000.V
Enter new value:
256
Write
Cancel
C010609E.ai
Figure Write Data Value Dialog Box (Analog Input/Output)

Write data status
Definition 1
0
BAD
GOOD
1
Cancel
C010610E.ai
Figure Write Data Status Dialog Box
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
Initial Displays of Write Data Value Dialog Box

Initial display
Data
Locked
Not locked
Logical data
Logical data
Input communication definition: Data status
Logical data
Logical data
Output communication data:
Data value
Physical data
Logical data
Output communication definition: Data status
Logical data
Logical data
Input communication data:
Data value
n Set Values to Multiple Items of Communication Data Together

Using the SCS Simulator, you can set values to multiple communication data items together.
The following operations can be performed on the communication data of the communication
module selected on the Communication Module List View.
Set values to the communication data.
Save the set values for the communication data in a file.
Read values form a file and set them to the communication data.
Note that the number of communication data values set at a time should be 700 or less. If more
data values are set at a time, some of the system alarm messages informing the data setting or
data status setting may not be transmitted.
l Enter the Values to be Set to Communication Data

The values can be entered to the Set Value items on Communication Data List View.
The value can be entered by any of the following operations. After entering the values, you need
to set all the values to the communication data.
Enter a Value Directly
On Communication Data List View, click Set Value items on the line of the communication
data that you want to enter the value for. By clicking the data value or data status, they can
be entered directly.
For BOOL type data, each one click will move among TRUE, FALSE and a space (none
specified) for selections.
For DINT or REAL type data, values can be entered directly from the keyboard.
Edit Multiple Data Values
From [Edit] menu or from the pop-up menu after a right clicking, you can use [Cut], [Copy],
[Paste] and [Del] commands to edit the values of multiple Set Value items.
Input Values Item on Pop-up Menu
Right clicking on the Communication Data List View, a pop-up menu will be displayed. Using
[Input Values] item on the pop-up menu, the data values and data status for Set Value
items can be defined.
For example, if you want to set all communication data to FALSE, you can use [Select All]
command on the pop-up menu to select all Set Value items, and then you can choose [Set
.V=FALSE] of the [Input Values] from the pop-up menu.
IM 32S05B10-21E
C1-48
l Set Values to Multiple Communication Data

For the selected communication modules, the values of Set Value items on the Communication
Data List View can be set together to the communication data.
IMPORTANT
Setting values to communication data cannot be executed while Build or Download is running.
The procedure is as follows:

1.
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].
l Export the Setting Values to a File

The values for Set Value items of the communication data can be exported to a file.
1.
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
l Import the Setting Values from a File

The values for Set Value items of the communication data can be imported from a file.
IMPORTANT
Do not import any file other than the file exported from Communication I/O Lock window.

1.
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
<C1.7 On-line Change>
C1.7 On-line Change
This section describes on-line changes, such as addition/deletion/dual-redundant

specification of subsystem communication modules, change of settings relating to
communication inputs and outputs, addition/deletion of subsystem communication I/O
FBs, and change of wirings relating to subsystem communication I/O FBs.
n Locking of Subsystem Communication Data

By locking subsystem communication data, you can reduce the impact of on-line changes on
the application logic or prevent erroneous outputs to subsystems resulting from application logic
correction errors.
Subsystem communication data cannot be locked once an on-line change download is started.
Lock subsystem communication data before starting an on-line change download.
To change a communication input/output definition from any SCS Manager window or builder,
close the Communication I/O Lock window first. After the on-line change is completed, display
the Communication I/O Lock window again, if necessary.
Table
Relationship of On-line Changes and Locking of Communication Modules

Content of change
Lock
Change a transmission definition

Add, change or delete a communication definition
Add a subsystem communication I/O FB
Required (inputs/outputs need to be locked).
Change the wiring of a subsystem communication I/O FB

Change an error handling action (*1)
Delete a subsystem communication I/O FB
*1:
Not required.
If a setting is changed while an error occurs, input values will change. Subsystem communication outputs are not affected.
n On-line Change Procedure

The procedure to perform an on-line change is specified below.
1.
Change the application logic in SCS Manager, and build the application logic.
2.
Check the application logic for consistency using Integrity Analyzer.
3.
Check the range to be tested using Cross Reference Analyzer.
4.
Change the SCSs security level to Level 1.
5.
Lock the inputs/outputs of subsystem communication data in accordance with what you
want to change.
6.
Close the Communication I/O Lock window.
7.
Perform an on-line change download.
8.
Open the Communication I/O Lock window.
9. Test the modified application logic.

10. Unlock the inputs/outputs of subsystem communication data.
11. Reset the SCSs security level to Level 2.
12. Save the SCS project using Version Control Tool.
SEE
ALSO
For the procedure to change applications online, see the following:

5.1, Entire Procedure of On-line Change of Application in the Engineering Guide (IM 32S01C10-21E)
IM 32S05B10-21E
C1-51
n Addition, Deletion and Dual-redundant Specification of Subsystem

Communication Modules
SEE
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)
n On-line Changes Relating to Communication Inputs/Outputs

When changing a communication input/output setting in the Communication I/O Builder, also
change the wiring of the subsystem communication I/O FB affected by the change.
l On-line Change Download

If an on-line change download is to be performed after a communication input/output data or
subsystem communication module setting has been changed, the subsystem communication
data of the target subsystem communication module needs to be locked before commencing
the on-line change download. If the subsystem communication data of the target module is not
locked, the application logic will be affected by a restart of the subsystem communication module.
The subsystem communication module will restart after the on-line change download is
completed. After the subsystem communication module has been restarted, unlock the
subsystem communication data of the module.
n On-line Changes Relating to Subsystem Communication I/O FBs

l Adding a Subsystem Communication I/O FB
If a subsystem communication I/O FB is added, the FB also needs to be wired. If the FB is not
wired, a build error will occur.
Before performing an on-line change download to add a subsystem communication I/O FB, the
communication I/O data of the target subsystem communication module needs to be locked.
An on-line change download to add a subsystem communication I/O FB is performed as a series
of multiple scans. Specifically, the subsystem communication I/O FB is added first, and then the
wiring is changed. As a result, the added FB is not wired while the on-line change download is in
progress. The subsystem communication I/O FB assumes the following status temporarily during
the download:
Subsystem communication input FB: The data value is 0. The data status is FALSE.
Subsystem communication output FB: The data value is ignored. The data status is FALSE.
The subsystem communication module will restart after the on-line change download is
completed. Once the subsystem communication module has been restarted, unlock the
l Deleting a Subsystem Communication I/O FB

When deleting a subsystem communication I/O FB, also delete the wiring of the FB.
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
n Changes Relating to POUs

To change a POU containing a subsystem communication output FB, the communication output
data of the subsystem communication module wired to the applicable subsystem communication
output FB needs to be locked.
IM 32S05B10-21E
C2-1
<C2.1 Communication Specifications>
C2. Subsystem Communication Modules

This chapter describes the subsystem communication modules used for connecting
subsystems. Subsystem communication modules are classified into the following two
types:
ALR111 RS-232C serial communication module
ALR121 RS-422/RS-485 serial communication module
C2.1 Communication Specifications
This section describes the communication specifications of the ALR111 RS-232C serial
communication module and ALR121 RS-422/RS-485 serial communication module.
n ALR111 RS-232C Serial Communication Module

The following describes the LED indications, connector pin layout and cable connection of the
ALR111 RS-232C serial communication module.
l LED Indications of the ALR111 RS-232C Serial Communication Module

Table
ALR111 LED Indications

LED
Description
STATUS
Hardware ready
ACT
Operating normally
DX
Dual-redundant configuration
SND1, SND2
Sending data from RS port 1 or 2
RCV1, RCV2
Receiving data by RS port 1 or 2
l Terminal Assignments of the ALR111 RS-232C Serial Communication Module

Table RS-232C D-sub, 9-pin Connector Specifications
Pin No.
Signal
Name
Processing on ALR111 side
CD
Carrier Detect
RD
Receive Data
SD
Send Data
ER
Data Terminal Ready
SG
Signal Ground
DR
Data Set Ready
Send data if the DR is ON (only when DR check is performed).
RS
Request to Send
This signal is always ON if RS control is not performed. If RS

control is performed, the ALR111 outputs ON when sending
data.
CS
Clear to Send
Send data if the CS is ON.
Send data if the CD is OFF (only when CD check is performed).

Receive data if the CD is ON.
Output ON if normal.
Not used
IM 32S05B10-21E
C2-2
n ALR121 RS-422/RS-485 Serial Communication Module

The following describes the LED indications, connector pin layout and cable connection of the
ALR121 RS-422/RS-485 serial communication module.
l LED Indications of the ALR121 RS-422/RS-485 Serial Communication Module

Table
ALR121 LED Indications

LED
Description
STATUS
Hardware ready
ACT
Operating normally
DX
Dual-redundant configuration
SND1, SND2
Sending data from RS port 1 or 2
RCV1, RCV2
Receiving data by RS port 1 or 2
l Terminal Assignments of the ALR121 RS-422/RS-485 Serial Communication

Module
Table ALR121 Connector Specifications
Terminal
Name
TX+
Send Data (Positive phase signal)
TX-
Send Data (Negative phase signal)
RX+
Receive Data (Positive phase signal)
RX-
Receive Data (Negative phase signal)
SG
Signal Ground
IM 32S05B10-21E
C2-3
n Cables Provided by Yokogawa Electric Corporation

Yokogawa Electric Corporation provides the following four types of cables for connecting a serial
communication module with a subsystem.
l RS-232C Modem Cables

These cables are used to connect an ALR111 with a modem.
AKB131: RS-232C modem cable (9-25 pins) for RS circuit isolated device (for ALR111 to
modem connection)
AKB135: RS-232C modem cable (9-25 pins) (for ALR111 to modem connection)
l RS-232C Null Modem Cables

These cables are used to connect an ALR111 with a subsystem.
AKB132: RS-232C null modem cable (9-25 pins) for RS circuit isolated device (for ALR111
to RS-232C device connection)
AKB133: RS-232C null modem cable (9-9 pins, male) (for ALR111 to FA-M3 connection)
AKB134: RS-232C null modem cable (9-9 pins, female) (for ALR111 to RS-232C device
connection)
AKB136: RS-232C null modem cable (9-25 pins) (for ALR111 to RS-232C device
connection)
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
<C3. Modbus Communication (ALR111, ALR121)>
C3. Modbus Communication (ALR111,

ALR121)
This chapter describes the Modbus communication package. The Modbus
communication package enables subsystem communication, such as reading and writing
of subsystem data, between an SCS and a Modbus PLC by connecting the Modbus PLC
to an ALR111 RS-232C serial communication module or ALR121 RS-422/RS-485 serial
communication module.
n Overview of Modbus Connection

The subsystem communication function implements communication with PLCs and other
subsystems via a subsystem communication module. The Modbus communication package is
downloaded to each subsystem communication module in which it will operate.
Reading of data from subsystems or writing of data to subsystems is performed by the
application logic execution function via the communication I/O data area and subsystem
communication I/O FBs.
The figure below illustrates how data flows in subsystem communication.
SCS
Communication
module
(ALR111/ALR121)
Communication I/O data

area/subsystem
Application logic
execution function
Modbus PLC
C030001E.ai
Figure Data Flow of Subsystem Communication Function
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
C3.1 Communication Specifications
This section describes the specifications of communication between an SCS and a

Modbus PLC.
n Communication Capacity
The table below summarizes the Modbus-specific communication capacity applicable to
communication between a Modbus PLC and an SCS.
Table
Capacity of Communication between SCS and Modbus PLC

Item
Maximum capacity
Remark
Amount of data that can be

communicated per serial
1,000 words
(1 word = 16 bits)
Limitations of the SCS: Communication I/O data area:

1,000 words per SCS Number of communication data
items: 500 data items per SCS
Number of subsystem stations

that can be communicated with
30 stations per port
If is recommended that the number of stations be limited to

a maximum of four or so, in order to minimize the impact on
communications with other normal stations when an error
occurs in a communication with a given station.
Size of communication data per

communication definition
125 words
One communication definition corresponds to

one communication. This limitation applies to one
communication using the Modbus protocol.
Number of usable ports
Communications are performed independently (in parallel)

using two ports.
n Simultaneity of Communication Data

Modbus PLCs assure simultaneity of communication data in units of 16 bits. Accordingly,
simultaneity of communication data between a serial communication module and a Modbus PLC
is also assured in units of 16 bits.
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
RS-232C (D-sub, 9-pin)
ALR111
RS-422/RS-485 (2-wire, [4-wire])
ALR121 (*1)
Transmission method
Half-duplex
Synchronization method
Start-stop synchronization
Baud rate
1200, 2400, 4800, 9600, [19200],

38400 bps
Transmission protocol
Modbus protocol (RTU mode)
Transmission code
Binary
Data type
Control line
Time monitoring
Text frame
Start bit
Fixed to 1.
Data bit
Parity bit
None, [Even], Odd
Stop bit
RS control
Yes, [No]
Valid only when the ALR111

is used.
DR check
[Yes], No

is used.
CD check
Yes, [No]

is used.
Send-enable monitor time
1000 ms
Reception inter-character timer
0 to 99999 ms [10 ms]
(*1)
Inter-character monitor timeout
Errors are latched.
(*1)
Reception start character
None
End character
None
XON/XOFF control
None
Response timeout
0 to 99 sec [4 sec]
Communication retry
0 to 99 [1]
Interval of connection retries
0 to 999 sec [30 sec]
Transmission wait time
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
n Communication Error Code

The specific error codes of Modbus PLC corresponding to address errors and communication
errors are as follows.
Table
Communication Error Code - Modbus (1/2)
Error Code (hexadecimal)
Description
Remarks
A3B0
No response
A3B1
Inappropriate station number (When the station number is other

than the range between 1 and 255)
(*1)
A3B2
Station number 0 cannot be set
(*1)
A3B3
Inappropriate address name
(*1)
A3B4
Inappropriate address number
(*1)
A3B5
Too many communication processing points
(*1)
A3B6
Write to a read-only device occurred
(*1)
A3B8
Odd number is used for the size of 4-byte register
(*1)
A3B9
Option 1 setting is out of range
(*1)
A3BA
Cannot create communication frame
(*1)
A3C0
CRC-16 error
(*1)
A3C1
Response message error (Station error)
(*2)
A3C2
Response message error (Address error)
(*2)
A3C3
Response message error (Function code error)
(*2)
A3C4
Response message error (Data error)
(*2)
A3C5
Response message error (Received data size error)
(*2)
A3C6
Response message error (Received data length error)
(*2)
A3D1
Error code $01 received
(*2)
A3D2
(*2)
A3D3
(*2)
A3D4
(*2)
A3D5
(*2)
A3D6
(*2)
A3D7
(*2)
A3D8
(*2)
A3D9
(*2)
A3DA
Error code $0A received
(*2)
A3DB
Error code $0B received
(*2)
A3DC
Error code $0C received
(*2)
A3DD
Error code $0D received
(*2)
A3DE
Error code $0E received
(*2)
A3DF
Error code $0F received
(*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
Communication Error Code - Modbus (2/2)
Error Code (hexadecimal)
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
<C3.2 Connection of Serial Communication Module and Modbus PLC>
C3.2 Connection of Serial Communication

Module and Modbus PLC
This section describes how to connect a serial communication module with a Modbus
PLC using a cable.
n Connecting an ALR111 RS-232C Serial Communication Module with a

Modbus PLC
The ALR111 uses a RS-232C D-sub, 9-pin connector, but the computer link unit of the connected
Modbus PLC may be equipped with a RS-232C D-sub, 25-pin connector or a 9-pin connector.
Select a connection cable appropriate for the subsystem to be connected.
A modem is required for connecting an ALR111 with a Modbus PLC. As long as the ALR111 and
Modbus PLC are sharing the same grounding system, the two can be connected directly using a
RS-232C cable of a length not exceeding 15 m.
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
l Connecting a RS-232C D-sub, 25-pin Connector to a Modbus PLC (Direct

Connection)
An example of cable connection where an ALR111 is connected directly to a Modbus PLC
equipped with a RS-232C D-sub, 25-pin connector is shown below. In this connection, a cable
with a RS-232C D-sub, 25-pin connector needs to be used.
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)
l Connecting a RS-232C D-sub, 9-pin Connector to a Modbus PLC (Direct

Connection)
An example of cable connection where an ALR111 is connected directly to a Modbus PLC
equipped with a RS-232C D-sub, 9-pin connector is shown below. In this connection, a cable with
a RS-232C D-sub, 9-pin connector needs to be used.
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
n Connecting an ALR121 RS-422/RS-485 Serial Communication Module

with a Modbus PLC
The specific connection varies depending on the Modbus PLC model.
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
<C3.3 Modbus PLC Devices Accessible from SCSs>
C3.3 Modbus PLC Devices Accessible from

SCSs
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
Modbus PLC Address within Modbus

device type
PLC device
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
code (hexadecimal)
Address
Device
Function
code
Input register

device type
PLC device
3
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
Link register (*1)
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
code (hexadecimal)
Address
Device
Special coil
Communication
status
Function
code

device type
PLC device
Read
Write
SP001
07
STSXXX
IM 32S05B10-21E
C3-11
The meaning of each function code is explained below.

A
Read data for the size specified at [Size] field in the Communication I/O Builder.
Write data for the size specified at [Size] field in the Communication I/O Builder. With
readback.
B
Write data individually to each modified device in units of 1 bit for a bit device, or in units of
16 bits for a word device. With readback.
C
Write data individually to each modified device in units of 32 bits. With readback.
X
Write data for the size specified at [Size] field in the Communication I/O Builder when a
change occurs. Without readback.
Y
Write data individually only to each modified device for the size of each device when a
change occurs. Without readback.
Z
Write data individually only to each modified device in units of 32 bits when a change
occurs. Without readback.
Table
List of Function Codes
Function code
Device
Word device
All data for one communication All data for one communication
Yes
definition
definition
Bit device
All data for one communication

In units of 1 bit
definition
Yes
Word device

In units of 16 bits
definition
Yes
Word device

In units of 32 bits
definition
Yes
Bit device

No
definition
Word device -

No
definition
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
For readback communication, see the following:

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
<C3.4 Storage Formats of Subsystem Data>
C3.4 Storage Formats of Subsystem Data
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
Figure Storage Image of Bit Devices
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
Content of register n+m-1

C030402E.ai
Figure Storage Image of Word Devices
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
Upper word of 32-bit data
Lower word of 32-bit data

C030406E.ai
Figure Order of 32-bit Data in SCS (Without Word Reversing)
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
Lower word of 32-bit data
Upper word of 32-bit data

C030405E.ai
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
(b) When bit reversing is specified
n
+
7
n
+ n
1
15
n
n +
1
n
+
7
The status of special coil is stored.

The value of n varies depending on
the model of the Modbus PLC to be connected.
C030403E.ai
Figure Storage Image of Special Coil Data
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
Communication status of stations 1 to 16
STS001
Communication status of stations 17 to 32
STS017
The correspondence of bits and station numbers is shown below.

Structure of STS001
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.
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
Figure Correspondence of Communication Status Bits and Station Numbers
IM 32S05B10-21E
C3-17
<C3.5 Builder Setting Items Specific to Modbus PLCs>
C3.5 Builder Setting Items Specific to Modbus

PLCs
This section describes the builder setting items specific to Modbus PLCs.
C3.5.1
Items Set in the I/O Wiring View
The items set in the I/O Wiring View are explained below.
n Subsystem Communication Module Definition

If an ALR111/ALR121 is used for subsystem communication, select ALR111M/ALR121M as
the module type. Specify the mounting position (node, slot number) of the module, as well as
whether or not to use a dual-redundant configuration.
n Dual Redundancy of Serial Communication Modules

To use serial communication modules in a dual-redundant configuration, set [IsRedundant] to
TRUE. You also need the dual-redundant option in the package.
C3.5.2
Items Set in the I/O Parameter Builder
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
For the setting items, see the following:

n Transmission Specification in C3.1, Communication Specifications
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
Items Set in the Communication I/O Builder
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
Fixed character string: S_MODBUS
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:
A0xxxx, B0xxxx, X0xxxx, Y0xxxx
Input relay:
A1xxxx
Link relay:
ADxxxx, BDxxxx, XDxxxx, YDxxxx
Step status:
ASxxxx
Input register:
A3xxxx
Holding register:
A4xxxx, B4xxxx, C4xxxx, X4xxxx, Y4xxxx, Z4xxxx
Constant register:
ACxxxx, BCxxxx, CCxxxx, XCxxxx, YCxxxx, ZCxxxx
Elapsed step time:
A5xxxx
Link register:
ARxxxx, BRxxxx, CRxxxx, XRxxxx, YRxxxx, ZRxxxx
Extended register:
AAxxxx, BAxxxx, CAxxxx, XAxxxx, YAxxxx, ZAxxxx
4-byte register:
AWxxxx
Special coil:
SP001
Communication status:
STSxxx
The Device Address field is blank by default.

xxxx indicates an address within Modbus PLC device, and is set as a decimal or hexadecimal
value between 1 and 65535 (1H and FFFFH). If a hexadecimal value is used, add H at the end.
The 0 or 0s at the beginning of xxxx can be omitted. For example, coil addresses of A023,
A0023 and A00023 all represent the same address.
SEE
ALSO
For details on address specification, see the following:

C3.3, Modbus PLC Devices Accessible from SCSs
IM 32S05B10-21E
C3-20
l Limitations on Dual-redundant Serial Communication Modules

If even one function code without readback (X, Y or Z) is specified in the [Device Address] fields
of the Communication I/O Builder, that serial communication module cannot be used in a dualredundant configuration. Dual redundancy is not supported if readback is not used. To provide
a dual-redundant configuration using two serial communication modules, specify only function
codes with readback (A, B and C) for the modules.
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.
For details on readback, see the following:

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
n Input Processing at Fault

Specify the value to be input to the application logic, instead of the input from the subsystem,
upon detection of a communication error.
n Input Value at Fault

Specify the input value to be used, instead of the process value, when Fixed Value is specified
in Input Processing at Fault.
IM 32S05B10-21E
<C3.6 Readback Communication>
C3-22
C3.6 Readback Communication
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.
n Operation in Communication with Readback

Values output from subsystems are read at the subsystem communication period. Each readback data is compared with the data to be written, and communication to write data is not
performed if the two data are the same ((1) and (3) in the figure below).
If an output value is changed in the CPU and a difference occurs between the read-back data
and the data to be written, communication is established with the applicable subsystem to write
the new data ((2) in the figure below).
If an output value in a subsystem is changed while communication is normal, a difference
occurs between the read-back data and the data to be written, in which case communication is
established with the subsystem to write the new data ((4) in the figure below).
Output data
The output value
(Physical data value
is changed.
output from subsystem
communication/output
value of the serial
communication module)
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)
The output value is changed

on the subsystem side.
C030601E.ai
Figure Output Communication with Readback
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
l Recovery from a Serial Communication Module Error

If the serial communication module has recovered from an error in a communication with
readback, the output values on the subsystem side are tracked. The figure below illustrates the
operation when communication outputs are locked.
If the serial communication module has generated an error, data from subsystems cannot be
read back. Thus, the SCS retains the previous output values and does not output data ((1) and
(2) in the figure below).
Once the serial communication module recovers and communication is enabled for the first time,
data from subsystems are read back to track the output values of the subsystems ((3) in the
figure below).
If an output value on the SCS side is changed thereafter, a difference occurs between the
readback data and the data to be written. In this case, communication is established with the
applicable subsystem to write the new data ((5) in the figure below).
First successful readback
after recovery from the serial
communication module error.
The value on the subsystem
side is tracked.
Output data
value of the serial
The output value

is changed.
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
n Operation in Communication without Readback

Communication without readback is used to perform one-shot write to the Modbus PLC.
If the Modbus PLC is to accept outputs to the coils (discrete outputs) on the master side as
commands to subsystems, it is necessary to perform one-shot write.
If the output to a coil is changed from OFF to ON on the master side, the Modbus PLC accepts
the command and resets the corresponding output value (OFF ON OFF). At this time if
readback is enabled, the output value will be read back from the Modbus PLC, in which case the
Modbus PLCs value will be compared with the value to be written. If a difference is detected,
communication will be established to write the new data again. If it is necessary to perform oneshot write, disable readback.
Without readback, output values are not read back.
The serial communication module checks the output values on the CPU side at the subsystem
communication period, and does not perform communication to write data if the previous output
values have not changed ((1), (3), (4) and (5) in the figure below).
Data is written only when a change is detected in any output value on the CPU side ((2) in the
figure below).
Since readback communication is not performed, communication to write data is not performed
even after an output value has been changed on the Modbus PLC side ((4) in the figure below).
Output data
value of the serial
The output value

is changed.
Subsystem
communication
period
Communication
to write data
is not
performed.
The output value is

checked at the subsystem
communication period.
Data is written if a change
in the output value is detected.
Output value on
Modbus PLC side
(1)
(2)
(3)
(4)
(5)
The output value is changed

on the Modbus PLC side.
C030603E.ai
Figure Output Communication without Readback
IM 32S05B10-21E
C3-25
l Settings of Option 2 (Wind-up Function)

The wind-up function is enabled only when a function code without readback is specified in
[Device Address] in the Communication I/O Builder. Without readback, output starts when an
output value has been changed on the master side. Thus, the wind-up function disables all
changes to output values for 70 seconds following a reset of the serial communication module,
in order to prevent unnecessary write accesses after the reset. Enable/disable this function using
Option 2 available in the Port 1 or Port 2 tab of the I/O Parameter Builder.
When Option 2 is set to 0
The wind-up function is enabled.
If the serial communication module is reset, changes to output values will not be written to
the Modbus PLC for 70 seconds following the reset. Changes to output values will be written
to the Modbus PLC only after elapse of 70 seconds following the reset.
The wind-up function is disabled.
SEE
ALSO
For the function codes that can be set in [Device Address], see the following:
C3.3, Modbus PLC Devices Accessible from SCSs
l Recovery from a Serial Communication Module Error (Wind-up Function

Enabled)
After the serial communication module recovers from an error, output values will be initialized to 0
((1) in the figure below).
If 0 is set in [Option 2] in the I/O Parameter Builders Port tab, changes to output values will not
be written to the Modbus PLC for 70 seconds following the reset ((3) in the figure below). Thus,
discrepancies will occur between the output values on the SCS side and those on the subsystem
side immediately after the reset of the serial communication module, until the output values are
changed on the subsystem side.
Recovery from the IOM error
The default is 0.
70 seconds (No output)
Output data
value of the serial
The output value

is changed.
The change in output

value is output after
elapse of 70 seconds.
Output value on
subsystem side
A discrepancy occurs between the outputs on the CPU side and

Modbus PLC side until the output value is changed on the CPU
side after 70 seconds elapse since the serial communication
module is restarted.
(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
l Error Handling Actions in Communication without Readback

The error handling actions in communication without readback are explained below:
Initial cold start of the CPU (Output disabled)
When output is disabled, the defaults of physical communication output data are 0. Output
is not performed until any output value is changed on the CPU side. Once output is enabled,
output will be performed when any output value is changed to a value other than 0 on the
CPU side. The output timing varies depending on the setting of the wind-up function.
Occurrence of a serial communication module error while subsystem communication data is
locked
When an error of serial communication module occurs or on-line change that may reset the
serial communication module is performed, if any output value is changed to a value other
than 0, output acts just like after an initial cold start of the CPU. The output timing varies
depending on the setting of the wind-up function.
l Status in Communication without Readback

With readback, values are read back at the subsystem communication period, so the status of
affected communication data will change to BAD if a serial communication error occurs. Whether
or not the status of affected communication data will change to BAD in this case without readback
is determined by the following conditions:
Whether or not a communication data exists that performs read command to the station
communicating based on a communication definition without readback
Specification of recovery communication in [Option 1] of the I/O Parameter Builders Port
tab
Table
When Communication Data that Defined without Readback Becomes BAD upon Serial
Communication Error
Option 1 setting (*1)
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
The status will change to

BAD if a communication
error occurs during a
communication to write data.
(If [Option 1] is set to 2, the
status will automatically
return to normal when
recovery communication is
performed.)
At least one communication definition with

readback exists for one station
The status will change to BAD if a

communication error occurs during a
communication to write data.
The status will also change to BAD if a
communication error occurs in which abnormal
line communication is recognized (no response,
line NRDY, etc.) during a communication based
on a definition with readback (input definition, or
output definition with 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
Occurrence of a range error of station number setting, range error of address setting or other definition error
IM 32S05B10-21E
<C3.7 Recovery Communication>
C3-27
C3.7 Recovery Communication
If no response is received or a CRC-16 code error occurs during communication with

a Modbus PLC, communication with the applicable station is temporarily suspended.
Thereafter, communication is performed at the interval of connection retries set in the I/O
Parameter Builder to check if the Modbus PLC that generated an error has recovered to
normal state. This communication is called recovery communication.
This section describes recovery communication.
n Types and Details of Recovery Communication

The recovery communication method is determined by the Option settings, which are set in the
Port 1 and Port 2 tabs of the I/O Parameter Builder.
l Option 1 (Recovery Communication Specification)

Recovery communication can be performed in the following five methods:
With readback, recovery communication is performed using a READ command.
Without readback, recovery communication is performed using a 08 command. The 08
command is a loopback check command used to check presence of the subsystem.
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.

Recovery communication is performed using a READ command regardless of the readback
setting.
Without readback, the error condition will be reset when recovery communication is
performed. If the same station generates an error again during recovery communication, a
system alarm will generate every time recovery communication is performed.
Without readback, recovery communication is performed using a WRITE command of 0
write size.
Without readback, recovery communication is performed using a WRITE command based
on the data written immediately before the error.
IM 32S05B10-21E
<C3.7 Recovery Communication>
C3-28

Without readback, any station that generated an error is not recognized as an error station.
When Option 1 is set to 5, communication with the non-responding Modbus PLC will stop for
the period corresponding to No response time x (1 + Number of retries) after each interval
of connection retries set in the communication module definition.
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
<C3.8 Communication Text>
C3.8 Communication Text
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
Figure Communication Text Frame Structures (1/2)
IM 32S05B10-21E
C3-30
<C3.8 Communication Text>
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
Figure Communication Text Frame Structures (2/2)
IM 32S05B10-21E
C3-31
<C3.9 Communication Time between Serial Communication Module >
C3.9 Communication Time between Serial

Communication Module and Modbus PLC
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:
Time for creating a send message: Approx. 10 ms

Delay time of the ALR111/ALR121 modem: Approx. 5 ms
Time for transmitting the send message.
Processing time in the Modbus PLC. Time for interpreting/executing the received message and creating a response message.
Determined by the number of communication data items and number of scans performed by the Modbus PLC.
Delay time of the Modbus PLC modem: Approx. 5 ms
Time for transmitting the response message.
Time for interpreting the response message: Approx. 15 ms
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
<C3.9 Communication Time between Serial Communication Module >
l How to Calculate Communication Time

The time for transmitting each send message (T3) and time for transmitting each response
message (T6) can be calculated by the formulas specified below:
Start bit:
Fixed to 1 bit.
Data bits:
Fixed to 8 bits. (7 bits cannot be specified.)
Parity bit:
None, even, odd
Stop bit:
Fixed to 1 bit.
Baud rate:
1200, 2400, 4800, 9600, 19200, 38400 bps
Table
Number of Characters Sent
Device
Read
Send
Write
Response
Send
Response
Coil
Fixed to 8.
5 + Number of coils / 8 (*1)
9 + Number of coils / 4 (*1)
Fixed to 8.
Input relay
Fixed to 8.
5 + Number of relays / 8 (*1)
Holding register
Fixed to 8.
5 + 2 x Number of registers
Fixed to 8.
Input register
Fixed to 8.
*1:
Fraction below the decimal point is rounded up.
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.
Dec. 2008/2nd Edition/R2.02 or later

Overall CS 3000 was changed to CENTUM, which refers to both CENTUM VP and CS 3000.
Overall Changed according to the specifications of CENTUM VP.
B2.4 Description of data setting communication was modified.
C1.6 Description was added regarding collective data setting.
May. 2008/1st Edition/R2.01 or later
Newly published.
n For Questions and More Information

Online Query: A query form is available on the following URL for online query.
http://www.yokogawa.com/iss/
If you want more information about Yokogawa products, you can visit
Yokogawas homepage at the following web site.
Homepage: http://www.yokogawa.com/
n Written by
Process Automation Product Marketing Dept.

Industrial Automation Systems Business Div.

Yokogawa Electric Corporation
n Published by Yokogawa Electric Corporation

2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN
IM 32S05B10-21E

Open Interfaces: User's Manual

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Open Interfaces: User's Manual

Hochgeladen von

Copyright:

Verfügbare Formate

Users

Media No. IM 32S05B10-21E (CD)

3rd Edition : Dec.22,2009-00

ProSafe-RS Document Map

Workbench Users Guide

2nd Edition : Dec.15,2008-00

Indicates that main switch is ON.

Indicates that main switch is OFF.

1st Edition : May 30,2008-00

n Warning and Disclaimer

1st Edition : May 30,2008-00

l Commonly used Conventions throughout User manuals:

Character string enclosed by brackets ({ }):

Tagname TUN {-Window size} {=Display position}

l Conventions used to show Key or Button Operations:

Click the [OK] button.

l Conventions of User Defined Folder

2nd Edition : Dec.15,2008-00

Indicates important information required to understand operations or functions.

Indicates additional information.

Indicates a source to be referred to.

n Integration with CENTUM

2nd Edition : Dec.15,2008-00

n About Station Types

SCS that uses SSC10S/SSC10D (SCP401 is installed)

SCS that uses SSC50S/SSC50D (SCP451 is installed)

SCS that uses SSC60S/SSC60D (SCP461 is installed)

Generic term that denotes all types of SCS

SCS connected on V net (this denotes SCSV1-S)

SCS connected on Vnet/IP (this denotes SCSP1-S and SCSP2-S)

Abbreviation for SCSV1-S

Abbreviation for SCSP1-S

Abbreviation for SCSP2-S

3rd Edition : Dec.22,2009-00

Copyright and Trademark Notices

3rd Edition : Dec.22,2009-00

SOE OPC Interfaces

SOE OPC Interface..................................................................................A1-1

Configuration of the SOE OPC Interface...................................................... A1-3

Settings of the SOE OPC Interface..............................................................A1-11

Starting and Closing the OPC Server......................................................... A1-15

3rd Edition : Dec.22,2009-00

Modbus Slave Interfaces

Modbus Slave Connection.....................................................................B1-1

Overview of Modbus Slave Connection....................................................... B1-1

Modbus Slave Communication Functions................................................... B1-5

Connection between the Modbus Master and SCS.................................... B1-8

Definitions in I/O Parameter Builder............................................................. B2-3

Definitions in Modbus Address Builder....................................................... B2-6

Window Configuration of Modbus Address Builder................................. B2-10

Data Setting via Modbus Interfaces............................................................ B2-14

3rd Edition : Dec.22,2009-00

Common Items Regarding Subsystem Communication

Overview of Subsystem Communication ................................................... C1-1

Dual-redundant Communication ................................................................. C1-8

Error Handling Actions . .............................................................................. C1-10

Setting Items Relating to Subsystem Communication ........................... C1-12

Settings Using the Communication I/O Builder ............................ C1-21

Forcing of Subsystem Communication Data ........................................... C1-29

Communication I/O Lock Window ............................................................. C1-32

Structure of the Communication I/O Lock Window........................ C1-35

Operations in the Communication I/O Lock Window . .................. C1-44

On-line Change ............................................................................................ C1-50