user's manual open interfaces - yokogawa electric · user's manuals (im), technical...

User's Manual Open Interfaces

IM 32Q05B10-31E

IM 32Q05B10-31E4th Edition

IntroductionThis manual describes the details of engineering and maintenance for connecting ProSafe-RS with other systems except CENTUM VP/CS 3000. You can read it for your necessary in-formation.This manual consists of the following parts:• Part A SOE OPC Interface

This part mainly describes specifications of the SOE OPC Interface of ProSafe-RS andcompatibility with the OPC specifications. It also describes the setup procedures requiredto connect to OPC clients using the SOE OPC Interface.

• Part B Subsystem communicationSubsystem communication is used for connections between the ProSafe-RS and othersystems. This part describes the subsystem communication functions and setting itemsrequired for connections with other systems.

• Part C Modbus slave communicationModbus slave communication is used for connections between the ProSafe-RS and othersystems. This part describes the definition of communication modules, definition of ad-dresses of Modbus devices, and data setting using Modbus slave communication, whichare required for connections.

• Part D DNP3 slave functionDNP3 communication is used for connections between the ProSafe-RS and other sys-tems. This section describes the DNP3 slave function, engineering and maintenance onthe SENG, and DNP3 communication function blocks.

• AppendixThis section describes the DNP3 Field Device Profile.

i

Media No. IM 32Q05B10-31E (CD) 4th Edition : Jan. 2015 (YK)All Rights Reserved Copyright © 2011, Yokogawa Electric Corporation

IM 32Q05B10-31E 4th Edition : Jan.30,2015-00

Safety Precautions for Usen Safety, Protection, and Modification of the Product

• To protect the system controlled by the Product and the Product itself and to ensure safeoperation, please observe the safety precautions described in this Manual. YokogawaElectric Corporation ("YOKOGAWA") assumes no liability for safety if users fail to observethe safety precautions and instructions when operating the Product.

• If the Product is used in a manner not specified in the User's Manuals, the protection pro-vided by the Product may be impaired.

• If any protection or safety circuit is required for the system controlled by the Product or forthe Product itself, please install it externally.

• Use only spare parts that are approved by YOKOGAWA when replacing parts or consum-ables of the Product.

• Do not use the Product and its accessories such as power cords on devices that are notapproved by YOKOGAWA. Do not use the Product and its accessories for any purposeother than those intended by YOKOGAWA.

• Modification of the Product is strictly prohibited.

• The following symbols are used in the Product and User's Manuals to indicate the accom-panying safety precautions:

Indicates that caution is required for operation. This symbol is labeled on the Prod-uct to refer the user to the User's Manuals for necessary actions or behaviors inorder to protect the operator and the equipment against dangers such as electricshock. In the User's Manuals, you will find the precautions necessary to preventphysical injury or death, which may be caused by accidents, such as electricshock resulting from operational mistakes.Identifies a protective conductor terminal. Before using the Product, you mustground the protective conductor terminal to avoid electric shock.Identifies a functional grounding terminal. A terminal marked "FG" also has thesame function. This terminal is used for grounding other than protective grounding.Before using the Product, you must ground this terminal.Indicates an AC supply.

Indicates a DC supply.Indicates the ON position of a power on/off switch.

Indicates the OFF position of a power on/off switch.

n Notes on Handling User's Manuals• Hand over the User's Manuals to your end users so that they can keep the User's Man-

uals on hand for convenient reference.

• Thoroughly read and understand the information in the User's Manuals before using theProduct.

• For the avoidance of doubt, the purpose of the User's Manuals is not to warrant that theProduct is suitable for any particular purpose but to describe the functional details of theProduct.

• Contents of the User's Manuals are subject to change without notice.

ii


• Every effort has been made to ensure the accuracy of contents in the User's Manuals.However, should you have any questions or find any errors, contact us or your local dis-tributor. The User's Manuals with unordered or missing pages will be replaced.

n Warning and Disclaimer• Except as specified in the warranty terms, YOKOGAWA shall not provide any warranty for

the Product.

• YOKOGAWA shall not be liable for any indirect or consequential loss incurred by eitherusing or not being able to use the Product.

n Notes on Software• YOKOGAWA makes no warranties, either expressed or implied, with respect to the Soft-

ware Product's merchantability or suitability for any particular purpose, except as speci-fied in the warranty terms.

• Purchase the appropriate number of licenses of the Software Product according to thenumber of computers to be used.

• No copy of the Software Product may be made for any purpose other than backup; other-wise, it is deemed as an infringement of YOKOGAWA's Intellectual Property rights.

• Keep the software medium of the Software Product in a safe place.

• No reverse engineering, reverse compiling, reverse assembling, or converting the Soft-ware Product to human-readable format may be performed for the Software Product.

• No part of the Software Product may be transferred, converted, or sublet for use by anythird-party, without prior written consent from YOKOGAWA.

iii


Documentation Conventionsn Symbols

The following symbols are used in the User's Manuals.

Identifies instructions that must be observed to avoid physicalinjury, electric shock, or death.

Identifies instructions that must be observed to prevent damageto the software or hardware, or system failures of the Product.

Identifies important information required to understand opera-tions or functions.

Identifies additional information.

Identifies referenced content.In online manuals, you can view the referenced content by click-ing the links that are in green text. However, this action does notapply to the links that are in black text.

n Typographical ConventionsThe following typographical conventions are used throughout the User's Manuals.

l Commonly Used Conventions throughout the User's Manuals• Δ Mark

Indicates that a space must be entered between character strings.Example:

.ALΔPIC010Δ-SC• Character string enclosed by braces { }

Indicates character strings that may be omitted.Example:

.PRΔTAG{Δ.sheet name}

l Conventions Used to Show Key or Button Operations• Characters enclosed by brackets [ ]

When characters are enclosed by brackets in the description of a key or button operation,it indicates a key on the keyboard, a button name in a window, or an item in a list boxdisplayed in a window.Example:

To alter the function, press the [ESC] key.

l Conventions of a User-defined Folder• User-defined folder name enclosed by parenthesis ( )

User definable path is written in a pair of parentheses.Example:

(RS Project Folder)\SCS0101

iv


If the RS Project Folder is C:\MYRSPJT, the above path becomes C:\MYRSPJTSCS0101.

n Drawing ConventionsDrawings used in the User's Manuals may be partially emphasized, simplified, or omitted forthe convenience of description.Drawings of windows may be slightly different from the actual screenshots with different set-tings or fonts. The difference does not hamper the understanding of basic functionalities andoperation and monitoring tasks.

n Integration with CENTUMThe Product can be integrated with CENTUM VP or CENTUM CS 3000. In the User's Man-uals, the integration with CENTUM VP or CENTUM CS 3000 is referred to as "Integration withCENTUM."In the User's Manuals, the explanations for integrating the Product with CENTUM VP orCENTUM CS 3000, the glossary for various features of CENTUM VP is used instead of theglossary for CENTUM CS 3000. For example, the term "CENTUM VP System Alarm View" isused instead of "CENTUM CS 3000 System Alarm window." Nevertheless, if the features forintegrating the Product with CENTUM VP and CENTUM CS 3000 are different, both featureswill be explained separately.

SEEALSO For more information about the functions and usage of CENTUM VP components for integrating the Product

with CENTUM VP, refer to:

User's Manuals (IM), Technical Information (TI), and General Specifications (GS) of CENTUM VP

For more information about the features and usage of CENTUM CS 3000 components for integrating theProduct with CENTUM CS 3000, refer to:

User's Manuals (IM), Technical Information (TI), and General Specifications (GS) of CENTUM CS 3000

n Explanation of Hardware and Software Behaviors in the User'sManuals

In the User's Manuals, system behaviors are explained assuming that the latest versions ofYOKOGAWA software and hardware at the time of publication of the User's Manuals are in-stalled.If additional precise information about the safety of legacy versions of software or hardware isrequired, a link to the corresponding explanation is provided. Please refer to the informationaccording to your system.

n Station TypesA safety control station (hereafter referred to as SCS) is named according to the type of thesafety control unit used in it.

Table Info-1 Names of SCS and Safety Control Unit UsedName of SCS Model of the safety control unit

SCSV1-S SSC10S/SSC10D

SCSP1-S SSC50S/SSC50D

SCSP2-S SSC60S/SSC60D

SCSU1-S SSC57S/SSC57D

In the User's Manuals, the following abbreviations may be used to describe functions of theseSCS as a whole.

v


• SCSV1: Abbreviation of SCSV1-S

• SCSP1: Abbreviation of SCSP1-S

• SCSP2: Abbreviation of SCSP2-S

• SCSU1: Abbreviation of SCSU1-S

vi


Copyright and Trademark Noticesn All Rights Reserved

The copyright of the programs and online manuals contained in the software medium of theSoftware Product shall remain with YOKOGAWA.You are allowed to print the required pages of the online manuals for the purposes of using oroperating the Product; however, reprinting or reproducing the entire document is strictly pro-hibited by the Copyright Law.Except as stated above, no part of the online manuals may be reproduced, transferred, sold,or distributed to a third party in any manner (either in electronic or written form including, with-out limitation, in the forms of paper documents, electronic media, and transmission via thenetwork). Nor it may be registered or recorded in the media such as films without permission.

n Trademark Acknowledgments• CENTUM, ProSafe, Vnet/IP, and STARDOM are registered trademarks of YOKOGAWA.

• Microsoft, Windows, Windows Vista, Windows Server, Visual Basic, Visual C++, and Vis-ual Studio are either registered trademarks or trademarks of Microsoft Corporation in theUnited States and other countries.

• Adobe, Acrobat, and Adobe Reader are registered trademarks of Adobe Systems Incor-porated.

• Ethernet is a registered trademark of Xerox Corporation.

• HART is a registered trademark of the HART Communication Foundation.

• Modicon and Modbus are registered trademarks of Schneider Electric SA.

• All other company and product names mentioned in the User's Manuals are trademarksor registered trademarks of their respective companies.

• TM or ® mark are not used to indicate trademarks or registered trademarks in the User'sManuals.

• Logos and logo marks are not used in the User's Manuals.

vii


Open Interfaces

IM 32Q05B10-31E 4th Edition

CONTENTSPART-A SOE OPC Interface.......................................... A-1

A1. Overview of SOE OPC Interface....................................................... A1-1A2. Setup for using the OPC server........................................................A2-1

A2.1 Settings of the SOE OPC Interface...........................................................A2-2A2.2 Overview of product security settings.....................................................A2-5A2.3 Operations after operation parameters are configured..........................A2-9

A3. Setup for using the OPC client......................................................... A3-1A3.1 Settings using the setup tool and Windows account settings.............. A3-2

A3.1.1 Preparations on the OPC server..................................................A3-3

A3.1.2 Operation procedure for the OPC client.......................................A3-4

A3.2 Settings of the OPC client.........................................................................A3-5

TocA-1


Open Interfaces


CONTENTSPART-B Subsystem communication............................B-1

B1. Common items regarding subsystem communication functions......................................................................................................................B1-1B1.1 Overview of subsystem communication................................................. B1-2B1.2 Dual-redundant communication...............................................................B1-9B1.3 Error handling actions.............................................................................B1-11B1.4 Setting items relating to subsystem communication...........................B1-14

B1.4.1 Settings using the I/O Parameter Builder...................................B1-17

B1.4.2 Settings using the Communication I/O Builder.......................... B1-22

B1.5 Forcing of subsystem communication data..........................................B1-30B1.6 Communication I/O Lock window...........................................................B1-33

B1.6.1 Structure of the Communication I/O Lock window..................... B1-36

B1.6.2 Operations in the Communication I/O Lock window.................. B1-44

B1.7 Online change.......................................................................................... B1-50

B2. Subsystem communication modules.............................................. B2-1B2.1 Communication specifications.................................................................B2-2

B3. Modbus communication (ALR111, ALR121)....................................B3-1B3.1 Communication specifications.................................................................B3-2B3.2 Connection of serial communication module and Modbus PLC...........B3-6B3.3 Modbus PLC devices accessible from SCSs.......................................... B3-8B3.4 Storage formats of subsystem data.......................................................B3-12B3.5 Builder setting items specific to Modbus PLCs....................................B3-15

B3.5.1 Settings in the I/O Wiring View...................................................B3-16

B3.5.2 Items set in the I/O Parameter Builder.......................................B3-17

B3.5.3 Items set in the Communication I/O Builder...............................B3-18

B3.6 Readback communication.......................................................................B3-21B3.7 Recovery communication....................................................................... B3-26B3.8 Communication text.................................................................................B3-28B3.9 Communication time between serial communication module and Modbus

PLC............................................................................................................B3-30

B4. ProSafe-SLS communication (for ALR121)..................................... B4-1B4.1 Operating Environment............................................................................. B4-2B4.2 System configuration................................................................................ B4-4

TocB-1


B4.2.1 Connection configuration of SCS and ProSafe-SLS....................B4-5

B4.2.2 System overview of ProSafe-SLS................................................B4-6

B4.3 Data access................................................................................................ B4-7B4.4 Event acquisition....................................................................................... B4-9B4.5 Time synchronization.............................................................................. B4-11B4.6 Alarm notification.....................................................................................B4-14B4.7 Communication specifications...............................................................B4-15B4.8 ProSafe-SLS device accessible by the SCS..........................................B4-17B4.9 Communication time between communication module and CO-920............

................................................................................................................... B4-20B4.10 Data types handled by the ProSafe-SLS communication function...............

................................................................................................................... B4-22B4.11 Message specifications...........................................................................B4-23B4.12 Builders to be set and engineering flow................................................B4-25

TocB-2


Open Interfaces


CONTENTSPART-C Modbus slave communication....................... C-1

C1. Common items regarding the Modbus slave communicationfunction...............................................................................................C1-1C1.1 Overview of Modbus slave communication............................................ C1-2C1.2 Data access using the Modbus communication functions....................C1-5C1.3 Setting items relating to Modbus slave communication........................C1-7C1.4 Definition of communication modules.....................................................C1-8

C1.4.1 Definitions in I/O Wiring View.......................................................C1-9

C1.4.2 Definitions in I/O Parameter Builder.......................................... C1-10

C1.5 Definition of addresses of Modbus devices.......................................... C1-11C1.5.1 Definitions in Modbus Address Builder...................................... C1-12

C1.5.2 Window configuration of Modbus Address Builder.................... C1-17

C1.6 Data setting using Modbus slave communication................................C1-20C1.7 Messages communication...................................................................... C1-23C1.8 Troubleshooting.......................................................................................C1-31

C2. Serial communication modules........................................................C2-1C2.1 Connection between the Modbus master and SCS................................ C2-2C2.2 Definitions in I/O Parameter Builder.........................................................C2-6

C3. Ethernet communication modules...................................................C3-1C3.1 Connection between the Modbus master and SCS................................ C3-2C3.2 Definitions in the I/O Parameter Builder.................................................. C3-4

TocC-1


Open Interfaces


CONTENTSPART-D DNP3 slave function........................................D-1

D1. Overview of DNP3 slave function.....................................................D1-1D1.1 DNP3 communication system configuration and components.............D1-2D1.2 Operating Environment............................................................................. D1-4

D2. DNP3 slave function of SCS............................................................. D2-1D2.1 Data access using the DNP3 slave function............................................D2-2

D2.1.1 Referencing DNP3 data...............................................................D2-4

D2.1.2 Setting DNP3 data....................................................................... D2-5

D2.1.3 Freeze command, Freeze & Clear command..............................D2-8

D2.1.4 Response time...........................................................................D2-10

D2.2 Event buffering.........................................................................................D2-11D2.2.1 Event generation........................................................................D2-12

D2.2.2 Event response..........................................................................D2-13

D2.2.3 Event deletion............................................................................ D2-14

D2.3 DNP3 function support for each data type............................................ D2-15D2.4 Time synchronization.............................................................................. D2-16

D3. Engineering and maintenance with SENG...................................... D3-1D3.1 Enabled DNP3 slave function................................................................... D3-2D3.2 Definition of communication input/output modules...............................D3-3

D3.2.1 Definitions in I/O Wiring View.......................................................D3-4

D3.2.2 Definitions in I/O Parameter Builder............................................ D3-5

D3.3 DNP3 slave setting.....................................................................................D3-8D3.4 Definition of instances for DNP3 communication FBs.........................D3-11D3.5 Definition of DNP3 data........................................................................... D3-12

D3.5.1 Window configuration of the DNP3 Communication Builder......D3-13

D3.5.2 Definition in the DNP3 Communication Builder......................... D3-15

D3.6 Creating an application logic..................................................................D3-18D3.7 Troubleshooting.......................................................................................D3-19

D4. DNP3 communication FBs................................................................D4-1D4.1 DNP3_BI......................................................................................................D4-2D4.2 DNP3_BO.................................................................................................... D4-3D4.3 DNP3_CT_16...............................................................................................D4-4

TocD-1


D4.4 DNP3_CT_32...............................................................................................D4-6D4.5 DNP3_AI_16................................................................................................D4-8D4.6 DNP3_AI_32................................................................................................D4-9D4.7 DNP3_AI_SF............................................................................................. D4-10D4.8 DNP3_AO_16............................................................................................ D4-11D4.9 DNP3_AO_32............................................................................................ D4-13D4.10 DNP3_AO_SF............................................................................................D4-14

TocD-2


Open Interfaces


CONTENTSAppendix

Appendix 1. DNP3 Field Device Profile.............................................. App.1-1Appendix 1.1 Device Properties........................................................................App.1-2Appendix 1.2 Capabilities for Device Database.............................................. App.1-9Appendix 1.3 Implementation Table............................................................... App.1-13

TocApp.-1


A. SOE OPC InterfaceThe SOE OPC Interface provides the functions of the OPC (OLE for Process Control) serverthat handles event information and diagnostic information that are acquired through the se-quence of event recorder (SOER) function of SCSs. OPC clients can access this informationby using the OPC Interface.

<A. SOE OPC Interface > A-1


A1. Overview of SOE OPC InterfaceBy using the SOE OPC Interface (server) provided by ProSafe-RS, it is possible to accessevent information and diagnostic information of SCS from OPC applications (clients) on thehost computer.This section explains the specifications of ProSafe-RS SOE OPC Interface and compatibilitywith the OPC specifications. The OPC specifications can be obtained from the web site of theOPC Foundation.

TIP OPC (OLE for Process Control) is an OLE (Object Linking and Embedding) specification, i.e., a method ofstandard communication between applications in Windows environments, which is specifically applicable toprocess control. OPC allows sending/receiving process data among multiple general-purpose Windows-com-patible applications.

n What is the SOE OPC Interface?The SOE OPC Interface provided by ProSafe-RS consists of the OPC server and SOE cas-sette dedicated to ProSafe-RS.• OPC server

The OPC server notifies event information and diagnostic information that is acquiredfrom SCSs to OPC clients. The OPC server consists of the Alarms & Events server (here-inafter referred to as A&E server), which accesses various data, and Historical Data Ac-cess server (hereinafter referred to as HDA server), which stores historical data.

• ProSafe-RS SOE cassetteThe SOE cassette dedicated to ProSafe-RS is incorporated in the cassette provided bythe OPC Interface as communication interface.

• Function of the SOE cassetteThe SOE cassette provides communication functions for notifying SOE events and diag-nostic information of SCS to the OPC server. By connecting to the OPC server equippedwith this cassette, OPC clients can receive event messages (SOE events and diagnosticinformation) of SCS.

n System configuration using the SOE OPC InterfaceThe SOE OPC Interface runs on a computer and reports SCS event information and diagnos-tic information to the host computer through the OPC Interface.

<A1. Overview of SOE OPC Interface> A1-1


SENG

Ethernet

Control bus

Host computer(OPC client)

Computer (OPC server)

HIS

Data flow of the OPC interface

Data flow of the SOE function SCS

Figure A1-1 Example of system configuration using the SOE OPC Interface

n Software configuration of the SOE OPC InterfaceThe SOE OPC Interface is comprised of the OPC server and the ProSafe-RS SOE cassette(hereinafter referred to as SOE cassette). The OPC server sends data to the OPC client. TheSOE cassette is an interface used by the OPC server to acquire data from SCS. The followingfigure shows the software configuration for the SOE OPC Interface.



Control bus

SCS

OPC client (Exaquantum, etc.)

SOEEvents log

DiagnosticInformation log

Ethernet

OPC interfaceEvents

Legend

A&E server

SOE cassette

Cache Data

HDA serverHistorical Data

Figure A1-2 Software configuration and data flow

n Details of the SOE OPC InterfaceParticular items of the SOE OPC Interface are explained below, including parameters andcontrol method required when constructing the system with the SOE OPC Interface.

l OPC interfaceThe following OPC-compliant interface is provided:• Alarms and Events (A&E)

This interface notifies event messages, which are generated asynchronously by SCS, tothe host computer. The SOE cassette reads the event log on SCS at regular intervals (thedefault is 10 seconds) and notifies changes (e.g., that new event messages are gener-ated) to the client.The A&E server provides OPC A&E custom interfaces and OPC A&E automation interfa-ces.

• Historical Data Access (HDA)This interface stores event messages, which are generated asynchronously by SCS, inthe historical database. This operation enables OPC clients to receive missed event mes-sages.

l Application capacityThe following table shows the application capacity limits.



Table A1-1 Application capacityItem Capacity

Maximum number of connected clients 100 clients

Maximum number of event registration objects 1000/OPC server

Maximum number of registered event generationsources

100/registration object

l Server name (ProgID), type library nameThe server name and type library name for the A&E server are as follows: The server name isused for custom interfaces. The type library name is used by the automation interfaces in ap-plications such as Visual Basic and Excel.• The custom interfaces

Server name: Yokogawa.ExaopcAESCSSOE

• The automation interfacesType library name: Yokogawa ProSafe-RS SCS Alarms & Events Automation Server

The server name and type library name for the HDA server are as follows:• The custom interfaces

Server name: Yokogawa.ExaopcHDASCSSOE

• The automation interfacesType library name: Yokogawa ProSafe-RS SCS HDA Server

l Event categories and event typesThe following table shows support for event categories and event types for SOE cassettes.The event category of system alarms generated in the SOE cassette is "System alarms(101)."

Table A1-2 Event category and event typeEvent category

Event type DescriptionName Value

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 systemalarms generated in the SOE cassette, the ProgID value (Yokogawa.Exaopc AESCSSOE) isstored in this item.

l Time (event generation time)This item contains the same time stamp (SCS time) as displayed in SOE Viewer. The timestamp is stored using UTC (Universal Time Coordinated).The time stamp based on the computer time is stored using UTC in the case of system alarmsgenerated 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. 900is stored in the case of system alarms generated in the SOE cassette.



Table A1-3 Event category and severityEvent category

Severity level DescriptionName

System alarms 900 Diagnostic Information (class 1)

500 Diagnostic Information (class 2)



Sequence of events 500 Event Information

l MessageAll SCS-generated event messages displayed in the SOE Viewer as the character string arestored, including all system alarm messages generated in the SOE cassette.

l Event description and attributesThe following table summarizes SOE event attributes for events reported by the OPC inter-face.

Table A1-4 Event attributes of diagnostic informationAttribute name OPC ID VARIANT type Remark

SOETimestamp 301 VT_DATE Event Occurrence Date (Local)

TimestampM 302 VT_I2 Event Occurrence Time (Millisecond)

Resource 303

VT_BSTR The same as the corresponding information dis-played in SOE Viewer (*1)

Type 304

ID 305

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 (computertime) are stored in the case of alarms generated in the SOE cassette.

Table A1-5 Event attributes of event informationAttribute name OPC ID VARIANT type Remark

SOETimestamp 301 VT_DATE Event Occurrence Date (Local)

TimestampM 302 VT_I2 Event Occurrence Time (Millisecond)

Resource 303

VT_BSTR The same as the corresponding information dis-played in SOE Viewer

Type 304

ID 305

Quality 306

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 cassetteThe SOE cassette generates a system alarm when access to SCS event logs fails. The sys-tem alarm is notified to the OPC client. The following example shows the message format forthis system alarm.

• Event Category: 101 (System alarms)• Event Type: 1 (Simple)• Source: Yokogawa.ExaopcAESCSSOE• Time: (Computer time)• Severity: 900• Message: Database Connection Error ERR=0x80004005

Database Connection Recover• SOETimestamp (Event Attribute): (Computer time) Event Occurrence Date (Local)• TimestampM (Event Attribute): (Computer time) Event Occurrence Date (Millisecond)• Resource (Event Attribute): (Computer name)• Type (Event Attribute): BSYS• ID (Event Attribute): (Blank)• Quality (Event Attribute): (Blank)• Node (Event Attribute): 0• Slot (Event Attribute): 0• Time_Diff (Event Attribute): (Computer time) Time zone (-08:00, +00:00,

+09:00, ...)

SEEALSO For more information about CPU load balancing for the SOE cassette, refer to:

2.18, “Connection with Host System Computer via an OPC Server” in Engineering Guide (IM32Q01C10-31E)

n Event notification interfacesThe SOE cassette notifies event information and diagnostic information of SCS to the A&Eserver. It also provides a function for filtering each event.

l Available interfacesThe following tables show the custom interfaces available to A&E server clients, based on thefunctions that are installed on the SOE cassette.



Table A1-6 Custom interfacesObject Interface Method Description Sup-

port(*1)OPCEventServer IOPCCommon SetLocaleID Locale ID setting Yes

GetLocaleID Locale ID acquisition Yes

QueryAvailableLocaleIDs Inquiry about supported localeIDs Yes

GetErrorString Error character string acquisi-tion Yes

SetClientName Client name setting Yes

IOPCEventServ-er

GetStatus Server status acquisition Yes

CreateEventSubscription Generation of Event Subscrip-tion object Yes

QueryAvailableFilters Inquiry about items that can befiltered Yes

QueryEventCategories Inquiry about event categories Yes

QueryConditionNames Inquiry about condition names Yes

QuerySubConditionNames Inquiry about sub-conditionnames Yes

QuerySourceConditions Inquiry about condition namescorresponding to a sourcename

Yes

QueryEventAttributes Inquiry about event attributes Yes

TranslateToItemIDs Item ID translation/acquisition Yes

GetConditionState Acquisition of condition status Yes

EnableConditionByArea Condition Enable for a speci-fied area No

EnableConditionBySource Condition Enable for a speci-fied source Yes

DisableConditionByArea Condition Disable for a speci-fied area No

DisableConditionBySource Condition Disable for a speci-fied source Yes

AckCondition Notification of condition ac-knowledgment No

CreateAreaBrowser Generation of Event AreaBrowser object No

IOPCSecurityNT Access control interface thatuses NT credit information Yes

IOPCSecurityPrivate Access control interface thatuses private-defined username/password

Yes

IConnection-PointContainer

EnumConnectionPoints Creation of enumerator thatscans connection points Yes

FindConnectionPoint Acquisition of interface pointersto connection points Yes

IConnectionPoint Advise Connection between connec-tion point and sink Yes

Unadvise Disconnection between con-nection point and sink Yes

Continues on the next page



Table A1-6 Custom interfaces (Table continued)Object Interface Method Description Sup-

port(*1)OPCEventServer IOPCSecurityNT IsAvailableNT Inquiry about availability of

OPC security function by NTcredit information

Yes (*2)

QueryMinImpersonation-Level

Inquiry about impersonationlevel

No

ChangeUser Notification of user credit infor-mation changes

No

IOPCSecurityPri-vate

IsAvailablePriv Inquiry about availability ofOPC security function by pri-vate credit information

Yes

Logon Logon request by client user Yes

Logoff Logoff request by client user Yes

OPCEventAr-eaBrowser (op-tion)

IOPCEventAr-eaBrowser

ChangeBrowsePosition Change of browser position No

BrowseOPCAreas Acquisition of area list No

GetQualifiedAreaName Acquisition of Area name No

GetQualifiedSourceName Acquisition of Source name No

OPCEventSub-scription

IOPCEventSub-scriptionMgt

SetFilter Event filter setting Yes

GetFilter Acquisition of event filter Yes

SelectReturnedAttributes Selection of event attribute Yes

GetReturnedAttributes Acquisition of selected eventattribute Yes

Refresh Event refresh request Yes

CancelRefresh Cancellation of refresh request Yes

GetState Acquisition of the status ofEvent Subscription object Yes

SetState Set the status of Event Sub-scription object Yes

IConnection-PointContainer

EnumConnectionPoints Creation of enumerator thatscans connection points Yes

FindConnectionPoint Acquisition of interface pointersto connection points Yes

IConnectionPoint Advise Connection between connec-tion point and sink Yes

Unadvise Disconnection between con-nection point and sink Yes

OPCEventSink IOPCEventSink OnEvent Event notification Yes

OPCShutdown IOPCShutdown ShutdownRequest Server shutdown notification Yes

*1: Yes: supportedNo: Not supported

*2: The IsAvailableNT method of the IOPCSecurityNT interface always returns FALSE.

l FiltersYou can specify the following filtering conditions:

Table A1-7 Filtering conditionsMask Description

OPC_FILTER_BY_EVENT Filtering by Event type




Table A1-7 Filtering conditions (Table continued)Mask Description

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 interfacesThe OPC Foundation released a draft version of the OPC A&E automation interfaces. YOKO-GAWA provides the OPC A&E automation interfaces that comply with the draft specifications.

n Error codesThe following tables show error codes handled by the SOE cassette. Each error code is setas a return value of a function of the SOE cassette interface or a data error value of each da-ta.

l OPC error codesThe following OPC error codes are used by the SOE cassette:

Table A1-8 COM error codesCOM 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 A1-9 OPC error codesOPC 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

l SOE cassette definition error codesThe following cassette definition error codes are used in the SOE cassette:

Table A1-10 SOE cassette definition error codesCode

(xxxx-x999)Symbol

(ZOT_XL_E_XXXX) Description

0xC0042329 ZOC_AE_E_MAXSERVER Excessive number of clients connected to theA&E server

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

l Error code bit assignmentThe bit assignment in the error codes is as follows:Code:



0000 to 0200: For Microsoft0200 to 7999: For OPC definition errors9000 to 9999: For the A&E server

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

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

Figure A1-3 Bit assignment in error codes



A2. Setup for using the OPC serverSetup is required to connect the SOE OPC Interface server (hereinafter referred to as SOEOPC server) and OPC client products. This section describes the setting items of the SOEOPC Interface required to use the OPC server, setting procedures, and operations after thesettings are completed.

<A2. Setup for using the OPC server> A2-1


A2.1 Settings of the SOE OPC InterfaceYou can configure operation parameters of the SOE cassette by using the operation parame-ter setting tool that is included in the SOE OPC interface. This section describes how to usethis tool to configure the settings for connecting the SOE OPC server and OPC client prod-ucts.

n Settings of operation parametersUse the operation parameter setting tool to configure the operation parameters for the A&Eserver and HDA server.1. From the Windows Start menu, select [All Programs] > [YOKOGAWA ProSafe] > [SOE

OPC Parameter Setting].

Figure A2.1-1 Launching the operation parameter setting tool

When the operation parameter setting tool is launched, it displays the SOE OPC InterfaceSettings dialog box.

<A2.1 Settings of the SOE OPC Interface > A2-2


Figure A2.1-2 SOE OPC Interface Settings dialog box

2. In the SOE OPC Interface Settings dialog box, specify operation parameters for the A&Eserver and HDA (Historical Data Access) server.

SEEALSO For more information about Items set for the HDA server, refer to:

“l Items set for the HDA server” on page A2-4

l Items set for the A&E serverThis section describes the setting items in the SOE OPC Interface Settings dialog box thatrelate to 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 NameThis field becomes enabled only if you select the [Use Database] check box. List thenames of SCSs to be referenced (separated by space, comma or period).Example:

SCS0101, SCS0102The event logs of the SCSs selected here become the target of notification.

• Specify Start Date/Time of EventsSelect this check box to change the date/time of the first event to be acquired. If this boxis selected, all events after the specified date/time are sent to the client. If the box is notselected, events after the computer time when restarting the SOE cassette are sent to theclient.The check box is not selected by default.

• Date/Time SpecificationThese fields become enabled only if you select 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 de-fault.

• Database Reference PeriodSpecify the period in units of seconds if you want to change the database reference peri-od.A value in the range from 1 to 600 seconds can be specified. 10 seconds is set by de-fault.

• Database Connection Retry PeriodSpecify the time interval in seconds to retry reconnection to the database in case the con-nection 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 de-fault.

• Delay Time Per Transmission EventThis is the delay time for a single transmission event. Specify the time in units of millisec-onds 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.Specify an appropriate value according to the load on the computer.• If you make the "Delay Time Per Transmission Event" longer, it takes more time to

send events and the CPU load is reduced.

• If you make the "Delay Time Per Transmission Event" shorter, it takes less time tosend events and the CPU load is increased.

l Items set for the HDA serverThis section describes the setting items in the SOE OPC Interface Settings dialog box thatrelate to the HDA server.• Use HDA

Select this check box when the HDA functions should be used.

• Max No. of Saving EventsThis field becomes enabled only if you selected the [Use HDA] check box. Specify themaximum number of events that the HDA server should maintain. If more events than themaximum number of events saved are generated, events are overwritten starting fromthe oldest event. A value in the range from 1000 to 1000000 can be specified. 10000 isset by default.

IMPORTANTDetermine the maximum number of saving events based on the disk capacity and the searchspeed of the HDA server. An event uses approximately 500 bytes of disk space, which meansthat 10000 events use approximately 5 MB. When there are many events, file searches takeslonger.



A2.2 Overview of product security settingsProduct security settings are required to connect the SOE OPC server and OPC client prod-ucts. This section describes the settings required on the SOE OPC server side.You can configure the OPC product security and DCOM connection settings using the opera-tion parameter setting tool that is included in the SOE OPC Interface.

n Product security setting procedureFollow these steps to configure the product security settings on the SOE OPC server:1. Log on as a user with administrative rights. If the standard model of security settings are

applied, log on as a user who belongs to the PSF_ENGINEER or PSF_ENGINEER_LCLgroup.

2. From the Windows Start menu, select [All Programs] > [YOKOGAWA ProSafe] > [SOEOPC Parameter Setting].The operation parameter setting tool starts, and the SOE OPC Interface settings dialogbox appears.

3. Click the [Edit] button next to [OPC Security Settings].A dialog box to select the logon type for the OPC server appears.

Figure A2.2-1 Select Logon Type dialog box

4. Configure the logon type settings for the OPC server according to the security level. Thefollowing table shows the setting items in the dialog box and precautions for setting theitems.

Table A2.2-1 Setting items and precautionsItem Description Precautions

Logon transaction is requiredfor connecting OPC server.

Select this option if you needto log on when connecting tothe OPC server

Calls of Logon and SetUser methods on theOPC client are required to select this op-tion.Do not select this option if the OPC clientdoes not support the calls of Logon and Se-tUser methods.

Automatically logon the des-ignated user for connectingOPC server.

Select this option to enable au-tomatic logon when connectingto the OPC server

After the automatic logon is enabled, selectone of the following logon methods.• Designated user• Default user of R2.03 and earlier ver-

sions


<A2.2 Overview of product security settings> A2-5


Table A2.2-1 Setting items and precautions (Table continued)Item Description Precautions

Designated user Select this option to designatea user for automatic logon

Specify the user name and password that isused for automatic logon.If periodic password change is required,you must respecify this password accord-ingly. This applies to the case of domainmanagement in Windows authenticationmode. Make sure to note the password ex-piration date.

Default user of R2.03 andearlier versions

Select this option to ensurecompatibility with ProSafe-RSR2.03 or earlier.

This option is selected by default when au-tomatic logon is enabled for connecting tothe OPC server.Note that this setting may result in a re-duced level of security.

TIP To connect a computer that is installed with the SOE OPC interface package for ProSafe-RS R3.01 or later toExaquantum or Exaquantum/SER as an OPC client, you need to set the items for product security in ad-vance. When using Exaquantum, you must select [Default user of R2.03 and earlier versions].

SEEALSO For more information about security settings required when using Exaquantum as an OPC client, refer to:

D1.3.1, “ProSafe-RS SOE OPC Interface Package and Exaquantum PIMS Server” in Installation (IM32Q01C50-31E)

n DCOM settingsIn ProSafe-RS R3.02 or later, the IT security of the SOE OPC server is strengthened. Thus,depending on the OPC client used, the connection to the server may fail after R3.02 or later isinstalled. If the connection fails, configure the DCOM settings on the OPC server. You mustrestart the computer after you finish configuring the settings.This section describes the DCOM setting procedures for different combinations of securitymodels and user management methods.

l DCOM setting procedure for legacy modelIf the SOE OPC server security model is the legacy model, DCOM settings are configured bythe IT security setting tool. No manual configuration is required.

l DCOM setting procedure for the standard model under standalonemanagement

This section describes the DCOM setting procedure when the SOE OPC server security mod-el is the standard model and the user management method is standalone management. Withthis procedure, you change the default authentication level of the SOE OPC server. If you failto establish connection with OPC clients after ProSafe-RS R3.02 or later is installed, config-ure the following settings.This section describes the setting procedure for the Windows 7 operating system as an exam-ple.1. From the Windows Start menu, select [Control Panel] > [Administrative Tools] > [Compo-

nent Services].The Component Services window appears.

2. In the hierarchy tree, expand [Component Services] > [Computers] > [My Computer] >[DCOM Config].



Figure A2.2-2 DCOM Config

3. Select Yokogawa ProSafe-RS SCS Alarms & Events Automation Server, and select[Properties] from the right-click menu.The Properties dialog box appears.

Figure A2.2-3 Yokogawa ProSafe-RS SCS Alarms & Events Automation Server Properties dialog box

4. Click the General tab, set the Authentication Level to [None], and click [OK].

5. Specify Yokogawa ProSafe-RS SCS HDA Server in Application Name, and select [Prop-erties] from the right-click menu.The Properties dialog box appears.



Figure A2.2-4 Yokogawa ProSafe-RS SCS HDA Server Properties dialog box

6. Click the General tab, set the Authentication Level to [None], and click [OK].

7. Restart the computer.

l DCOM setting procedure for standard model under domain managementThe DCOM setting procedure when the SOE OPC server security model is the standard mod-el and the user management method is domain management is the same as when the securi-ty model is the standard model and the user management method is standalone manage-ment.

SEEALSO For more information about DCOM setting procedure for the standard model under standalone management,

refer to:

“l DCOM setting procedure for the standard model under standalone management” on page A2-6

l DCOM setting procedure for standard model under combinationmanagement

The DCOM setting procedure when the SOE OPC server security model is the standard mod-el and the user management method is combination management is the same as when thesecurity model is the standard model and the user management method is standalone man-agement.


refer to:

“l DCOM setting procedure for the standard model under standalone management” on page A2-6



A2.3 Operations after operation parameters areconfigured

This section describes how the SOE OPC Interface operates after the operation parametersare configured.

n Operations when the operation parameter setting tool is launchedWhen the operation parameter setting tool is launched for the first time, all the items are set totheir default values. When you launch the tool the next time, the tool displays all items accord-ing to the settings the user made last time.The [Specify Start Date/Time of Events] check box is deselected when the SOE cassettestarts to send events.

n Operations when changing parametersWhen using the operation parameter setting tool to change operation parameters for the SOEcassette, the SOE OPC interface restarts when you click the [OK] button in the operation pa-rameter setting tool.Events generated while the SOE OPC interface is restarting are not sent to the client. If youwant to send events generated during the SOE OPC interface restart processing (approxi-mately 1 to 2 minutes) to the client, specify the [Specify Start Date/Time of Events] settingitem for the A&E server. The current time can be set by selecting/deselecting the [Specifica-tion 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 aspreviously specified.To resend the past events, check the [Specify Start Date/Time of Events] box and specify the date and timeagain.

<A2.3 Operations after operation parameters are configured > A2-9


A3. Setup for using the OPC clientSetup of the OPC server and OPC client is required to connect to the SOE OPC server.This section describes the settings using the setup tool, Windows account settings required touse the OPC client, and settings required on the OPC client.

<A3. Setup for using the OPC client > A3-1


A3.1 Settings using the setup tool andWindows account settings

You can configure the OPC client using required information which is collected from the OPCserver using the setup tool.After that, you can configure Windows accounts and settings required for the connection onthe OPC server and client.

<A3.1 Settings using the setup tool and Windows account settings > A3-2


A3.1.1 Preparations on the OPC serverOn the computer where the SOE OPC Interface is installed, you must get the information thatis required to set up the OPC client and save it in a removable storage device. After savingthe information, you must create the user account to be used to run the application on theOPC client.

TIP To run a program file or SETUP.exe in Windows Vista or later, right-click the file, and then select [Run as Ad-ministrator].

1. Connect a formatted removable storage medium (such as USB memory stick) to the com-puter where the SOE OPC server is running.

2. In Windows Explorer, start the following program:(ProSafe-RS installation drive):\(ProSafe-RS installation folder)\ProSafe-RS\YOKOGAWA\program\RHHCopyOPC.exeThe RHHCopyOPC dialog box appears.

Figure A3.1.1-1 RHHCopyOPC dialog box

3. Select the connected removable storage medium and click [OK].The setup information that is required for the OPC client is saved on the removable stor-age medium.

4. On the OPC server, set up the user who will run the application on the OPC client.

• For the SOE OPC server where the standard model of security settings are appliedAdd the user to the PSF_OPC group.



A3.1.2 Operation procedure for the OPC clientOn the computer where the OPC client runs, you must configure the setup information by us-ing the setup tool and set up the user who will run the application on the OPC server.

TIP To run a program file or SETUP.exe in Windows Vista or later, right-click the file and select [Run as Adminis-trator].

1. Connect the removable storage medium that stores the setup information to the computerin which the OPC client is running.

2. Log on to the OPC client as an administrative user.

3. Insert the ProSafe-RS software medium into the drive, and run the following programcontained in the medium.(Drive):\ProSafe-RS\vcredist_x86\vcredist_x86.exe

4. Run the SETUP.exe in the removable storage medium.The command prompt appears and the setting up of OPC client is performed.

5. Specify the user who will run the application on the SOE OPC server.If the SOE OPC server security model is the standard modela. Insert the ProSafe-RS software medium into the drive, start the command prompt

window, and move to the following folder.(Drive):\ProSafe-RS\SECURITY

b. Run the following program.ProSafe.Security.CreateProSafeProcess.exeThe "PSF_PROCESS" user is created on the client computer.

c. Configure the security settings designated by the client application.

TIP If the client application is Exaquantum, add the "PSF_PROCESS" user to the QTM_OPC user group as des-ignated by Exaquantum.

If the SOE OPC server security model is the legacy modela. Create the following user on the client computer.

Account name: EXAUSER (all in upper case)Password: EXAUSER (all in upper case)

b. Configure the security settings designated by the client application.



A3.2 Settings of the OPC clientSetup of the computer in which the OPC client is running is required to connect the SOE OPCserver and OPC client products. On the OPC client, you can configure firewall settings, Win-dows account settings, DCOM settings, and local security settings according to the securitymodel and user management method used on the SOE OPC server. If the client applicationcoexists with the SOE OPC server, the configuration is not required.You must configure the OPC client with administrator privileges.

n Settings for the legacy modelIf the SOE OPC server security model is the legacy model, the following settings are required.You must restart the computer after you finish configuring the settings.• Firewall settings

• Windows account settings

• DCOM settings

• Local security settings

This section describes the setting procedure for Windows Vista as an example.

l Firewall setting procedureDisable the Windows Firewall.1. From the Windows start menu, select [Control Panel] > [Security Center].

The Windows Security Center window appears.

Figure A3.2-1 Windows Security Center window

2. Click [Windows Firewall].The Windows Firewall Settings dialog box appears.

<A3.2 Settings of the OPC client> A3-5


Figure A3.2-2 Windows Firewall Settings dialog box

3. Click the General tab, select [Off (not recommended)], and click [OK].An alert balloon appears when the firewall function is disabled.

4. To stop the alert balloon from appearing, open the Windows Security Center windowagain.

5. On the left side of the Windows Security Center window, click [Change the way SecurityCenter alerts me].Do you want to be notified of security issues? dialog box appears.

Figure A3.2-3 Do you want to be notified of security issues? dialog box

6. Select [Don't notify me and don't display the icon (not recommended)].The display of the alert balloon stops.



l Windows account setting procedureSet up the user who will run the client application and the user who will access the SOE OPCserver.1. From the Windows start menu, select [Control Panel] > [Administrative Tools] > [Comput-

er Management].The Computer Management window appears.

2. Select [System Tools] > [Local Users and Groups] > [Users], create the following user ac-count, which is used to run the SOE OPC server.User name: EXAUSERPassword: EXAUSERTo clear the check box, click [User must change password at next logon].Select [Password never expires].

l DCOM setting procedureFor DCOM, add the Everyone user and configure "Access Permissions" and "Launch and Ac-tivation Permissions" for the Everyone user and default user. After that, change the defaultauthentication level.1. Edit the Access Permissions settings for the Everyone user.

a. From the Windows start menu, enter dcomcnfg in [Start search], and run the dcomcnfg.exe that is displayed.The Component Services window appears.

Figure A3.2-4 Component Services window

b. Right-click [Component Services] > [Computers] > [My Computer] and select [Proper-ties].The My Computer Properties dialog box appears.



Figure A3.2-5 COM Security tab of the My Computer Properties dialog box

c. Click the COM Security tab and click [Edit Default] for Access Permissions.The Access Permission dialog box appears.

Figure A3.2-6 Default Security tab of the Access Permission dialog box

d. Click [Add].The Select Users or Groups dialog box appears.



Figure A3.2-7 Select Users or Groups dialog box

e. Enter Everyone for the object name to select and click [OK].The [Everyone] user is added to the Access Permission dialog box.

f. Select [Everyone], select the "Allow" check boxes for "Local Access" and "RemoteAccess," and click [OK].

2. Edit the default values of Launch and Activation Permissions.

a. In the My Computer Properties dialog box, click the COM Security tab and click [EditDefault] for Launch and Activation Permissions.The Launch and Activation Permission dialog box appears.

Figure A3.2-8 Default Security tab of the Launch and Activation Permission dialog box

b. Click [Add].The Select Users or Groups dialog box appears.

c. Enter Everyone for the object name to select and click [OK].The [Everyone] user is added to the Launch and Activation Permission dialog box.

d. Select [Everyone], select the "Allow" check boxes for "Local Launch," "RemoteLaunch," "Local Activation," and "Remote Activation," and click [OK].



3. Edit limits for Access Permissions.

a. In the My Computer Properties dialog box, click the COM Security tab and click [EditLimits] for Access Permissions.The Access Permission dialog box appears.

Figure A3.2-9 Security Limits tab of the Access Permission dialog box

b. Select [ANONYMOUS LOGON] in the Group or user names list, select the "Allow"check boxes for "Local Access" and "Remote Access," and click [OK].

4. Edit limits for Launch and Activation Permissions.

a. In the My Computer Properties dialog box, click the COM Security tab and click [EditLimits] for Launch and Activation Permissions.The Launch and Activation Permission dialog box appears.

Figure A3.2-10 Security Limits tab of the Launch and Activation Permission dialog box



b. Select [Everyone] in the Group or user name list, select the "Allow" check boxes for"Local Launch," "Remote Launch," "Local Activation," and "Remote Activation," andclick [OK].

5. Edit the default properties.

a. In the My Computer Properties dialog box, click the Default Properties tab and select[None] for the Authentication Level, and click [OK].

Figure A3.2-11 Default Properties tab of the My Computer Properties dialog box

l Local security policy setting procedureSet the local security policy.1. Select [Control Panel] > [Administrative Tools] > [Local Security Policy].

The Local Security Policy window appears.



Figure A3.2-12 Local Security Policy window

2. Open [Security Settings] > [Local Policies] > [Security Options].

3. In the Policy column, double-click [Network access: Let Everyone permissions apply toanonymous users].The Network access dialog box appears.



Figure A3.2-13 Network access dialog box

4. Select [Enabled] and click [OK].In the Security Options folder, check if "Enabled" is selected in the "Security Setting" fieldfor [Network access: Let Everyone permissions apply to anonymous users].


n Settings for standard model under standalone managementIf the security model on the SOE OPC server is the standard model and the user manage-ment method is standalone management, you need to configure the following settings. Besure to restart the computer after you finish the configuration.• Firewall settings


• DCOM settings

This section describes the setting procedure for the Windows 7 operating system as an exam-ple.

l Firewall setting procedureConfigure firewall settings for the [File and Printer Sharing] service and the client application.1. From the Windows start menu, select [Control Panel] > [Windows Firewall].

The Windows Firewall window appears.



Figure A3.2-14 Windows Firewall window

2. Click [Allow a program or feature through Windows Firewall].The Allowed Programs window appears.

Figure A3.2-15 Allowed Programs window

3. Click [Change settings].



4. In the Name column, select the check box for [File and Printer Sharing].Check if all profiles (Domain, Home/Work(Private), and Public) are selected.

5. Click [Allow another program].The Add a Program dialog box appears.

6. Select the client application from the Programs list and click [Add].Check if the selected client application is added to the Allowed Programs window andthat its check boxes in the Name and Public columns are selected.

l Windows account setting procedureSet up the user who will run the client application and the user who will access the SOE OPCserver.1. Insert the ProSafe-RS software medium into the drive, start the command prompt win-

dow, and move to the following folder.(Drive):\ProSafe-RS\SECURITY

2. Run the following program.ProSafe.Security.CreateProSafeProcess.exeThe "PSF_PROCESS" user is created on the client computer.

3. From the Windows start menu, select [Control Panel] > [Administrative Tools] > [Comput-er Management].The Computer Management window appears.

Figure A3.2-16 Computer Management window

4. Select [System Tools] > [Local Users and Groups] > [Users], and add the user who willrun the client application.The user added on the client side must have permissions of the PSF_OPC group on theSOE OPC server side. In addition, the user name and password must be the same as thecorresponding user on the SOE OPC server.

l DCOM setting procedureFor DCOM, add the PSF_PROCESS user and configure "Access Permissions" and "Launchand Activation Permissions." After that, change the default authentication level.1. Edit the Access Permissions settings for the Everyone user.

a. From the Windows start menu, select [Control Panel] > [Administrative Tools] >[Component Services].



The Component Services window appears.

Figure A3.2-17 Component Services window

b. Right-click [Component Services] > [Computers] > [My Computer] and select [Proper-ties].The My Computer Properties dialog box appears.

Figure A3.2-18 COM Security tab of the My Computer Properties dialog box

c. Click the COM Security tab and click [Edit Default] for Access Permissions.The Access Permission dialog box appears.



Figure A3.2-19 Default Security tab of the Access Permission dialog box

d. Click [Add].The Select Users or Groups dialog box appears.

Figure A3.2-20 Select Users or Groups dialog box

e. Enter PSF_PROCESS for the user to select and click [OK].The PSF_PROCESS user is used to access the SOE OPC server and must be createdin advance.The [PSF_PROCESS] user is added to the Access Permission dialog box.

f. Select [PSF_PROCESS], select the "Allow" check boxes for "Local Access" and "Re-mote Access," and click [OK].

2. Edit limits for Access Permissions

a. In the My Computer Properties dialog box, click the COM Security tab and click [EditLimits] for Access Permissions.The Access Permission dialog box appears.



Figure A3.2-21 Security Limits tab of the Access Permission dialog box

b. Select [ANONYMOUS LOGON] in the Group or user names list, select the Allowcheck boxes for "Local Access" and "Remote Access," and click [OK].

3. Edit the default values of Launch and Activation Permissions

a. In the My Computer Properties dialog box, click the COM Security tab and click [EditDefault] for Launch and Activation Permissions.The Launch and Activation Permission dialog box appears.

Figure A3.2-22 Default Security tab of the Launch and Activation Permission dialog box




c. Enter PSF_PROCESS for the user to select and click [OK].The [PSF_PROCESS] user is added to the Launch and Activation Permission dialogbox.

d. Select [PSF_PROCESS], select the Allow check boxes for "Local Launch," "RemoteLaunch," "Local Activation," and "Remote Activation," and click [OK].

4. Edit limits for Launch and Activation Permissions.

a. In the My Computer Properties dialog box, click the COM Security tab and click [EditLimits] for Launch and Activation Permissions.The Launch and Activation Permission dialog box appears.

Figure A3.2-23 Security Limits tab of the Launch and Activation Permission dialog box


c. Enter PSF_PROCESS for the user to select and click [OK].The [PSF_PROCESS] user is added to the Launch and Activation Permission dialogbox.

d. Select [PSF_PROCESS], select the Allow check boxes for "Local Launch," "RemoteLaunch," "Local Activation," and "Remote Activation," and click [OK].

5. Change the default authentication level of the SOE OPC server.

a. In the hierarchy tree, expand [Component Services] > [Computers] > [My Computer]> [DCOM Config].



Figure A3.2-24 DCOM Config

b. Select Yokogawa ProSafe-RS SCS Alarms & Events Automation Server and select[Properties] from the right-click menu.The Properties dialog box appears.

Figure A3.2-25 Yokogawa ProSafe-RS SCS Alarms & Events Automation Server Properties dialog box

c. In the Yokogawa ProSafe-RS SCS Alarms & Events Automation Server Propertiesdialog box, click the General tab and select [None] for the Authentication Level, andclick [OK].

d. From the hierarchy tree, open the DCOM Config window, select Yokogawa ProSafe-RS SCS HDA Server, and select [Properties] from the right-click menu.



The Properties dialog box appears.

Figure A3.2-26 Yokogawa ProSafe-RS SCS HDA Server Properties dialog box

e. In the Yokogawa ProSafe-RS SCS HDA Server Properties dialog box, click the Gen-eral tab and select [None] for the Authentication Level, and click [OK].


n Settings for standard model under domain managementIf the SOE OPC server security model is the standard model and the user management meth-od is domain management, you can change the following settings. You must restart the com-puter after you finish changing the settings.• Firewall settings


• DCOM settings

The setting procedure is the same as when the security model is the standard model and theuser management method is standalone management.For Windows account settings, you need to configure only for the PSF_PROCESS user.


refer to:

“l DCOM setting procedure” on page A3-15

n Settings for standard model under combination managementIf the SOE OPC server security model is the standard model and the user management meth-od is combination management, change the following settings. Always restart the computerafter you finish changing the settings.• Firewall settings




• DCOM settings

The setting procedure is the same as when the security model is the standard model and theuser management method is standalone management.


refer to:

“l DCOM setting procedure” on page A3-15



B. Subsystem communicationThe subsystem communication function is one of the Modbus communication functions thatare provided by ProSafe-RS. This function enables a safety control station (SCS) to act as theModbus master and communicate with subsystems.

<B. Subsystem communication > B-1


B1. Common items regardingsubsystem communicationfunctions

The subsystem communication function enables communication, such as reading and writingsubsystem data between SCSs and PLCs (Programmable Logic Controllers), or other subsys-tems connected to the SCS's communication module.This section describes common subsystem communication functions that are not dependenton subsystem types.

<B1. Common items regarding subsystem communication functions> B1-1


B1.1 Overview of subsystem communicationThis section describes the structure of subsystem communication functions within the SCSand gives an overview of communication between the subsystem and the SCS.

n Type of subsystem communication functionThe following subsystem communication function is available in an SCS: The communicationmodule in the SCS becomes the communication master.• MODBUS communication

• ProSafe-SLS communication

n Structure of subsystem communication functionsThe following section provides an overview of subsystem communication.• Functional structure and data flow

• Relationship of subsystems and the application logic

<B1.1 Overview of subsystem communication > B1-2


l Functional structure and data flow

Operating status IOM status Diagnostic informationOutput enable

IOM download Forcing Referencing of logicsReferencing of

communication data

System FBs

Referencing of communication data as tag names

SENG

SCS

IOM download

Module status

Interpretation of communication protocols

- SCS State Management Window- IOM Report- Diagnostic Information Window

Communication I/O Lock Window

- Multi-Language Editor - Dictionary

CENTUM

Integrationwith CENTUM

Application logic execution

Communication I/O data area

Subsystem communication module

management

Communication I/O images

Subsystem


Subsystem

Subsystem communication program (communication driver)

Images inside the module

Communication I/O data management

Figure B1.1-1 Functional structure and data flow

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 com-munication I/O data management function.



• The subsystem communication program interprets communication protocols (such as theModbus protocol).

• The communication I/O data management function is a general-purpose data manage-ment function not dependent on communication protocols. The communication I/O datamanagement function manages the communication I/O data area consisting of 1000words in which subsystem register images are mapped.

• The subsystem communication input FBs and subsystem communication output FBs areused to access the communication I/O data management function from the applicationlogic.

Subsystem

AI DI

DO

AI

DI

DO

Sequencer SCS

Registers

Communication I/O data management POU

Physical data Logical data 50.0 50.0 50.0

Subsystem communication input FB

Subsystem communication output FB

Comm. definition

Comm. definition

Comm. definition

Wiring

1

1 1

1

1 1

1 1

• • • • • • • • • •

1 1

1 1


Subsystem communication input FB

Figure B1.1-2 Relationship of communication I/Os and registers

n Communication with subsystemsThe subsystem communication module communicates with each subsystem in accordancewith the transmission specifications and communication definitions set with subsystem com-munication builders to refresh the images inside the module.The subsystem communication module interprets subsystem communication protocols andperforms communication based on the protocols. Thus, the CPU only exchanges data withthe subsystem communication module and does not perform any processing specific to eachsubsystem communication type.



Subsystem

Subsystem communication program(interpretation of protocols, conversion to data)


CPU


Communication definitions

Transmission definitions

Subsystem communication I/O refresh function


Figure B1.1-3 Communication between SCS and subsystem

n Data flow and refresh timeThe data refresh time varies depending on the subsystem type, amount of acquired data andtransmission specifications. The following describes the flow of data not dependent on sub-system types.

l Data refresh time (input through output)


Communication I/O data area (input)

Communication I/O data area (output)



Subsystem input

Subsystem output

Subsystem communication

period


period

0 to SCS’s application logic

scan period

Run time = Dependent on the application logic scan period and CPU load

1. Subsystem communication (read)

2. Refresh the communication I/O data area (input)

5. Flush the communication I/O data area (output)

3. Subsystem communication input FB (read)

4. Subsystem communication output FB (write)

6. Subsystem communication (write)

Figure B1.1-4 Data refresh time (input through output)

l Data flow and timings1. Subsystem communication (read)

The data acquisition period varies depending on the subsystem type and transmissionspecifications.

2. Refresh the communication I/O data area (input)The data is read from the subsystem communication module to the communication I/Odata area at the beginning of the SCS scan period.

3. Subsystem communication input FB (read)The data is read from the communication I/O data area (input) when the subsystem com-munication 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 thesubsystem communication output FB.

5. Flush the communication I/O data area (output)At the end of the SCS scan period, the communication I/O data area is flushed and thedata is written to the subsystem communication module.

6. Subsystem communication (write)The data acquisition period of each subsystem from the subsystem communication mod-ule varies depending on the subsystem type and transmission specifications.

SEEALSO For more information about transmission specifications, refer to:

“n Transmission specification” on page B3-2

n Period of subsystem communication and communication timeThe following section describes the period of subsystem communication and communicationtime using a serial communication module.

l Period of serial communicationSubsystem communication is performed asynchronously with the scan period of the applica-tion logic execution function. Data is written only when written by the CPU.

Read communication

definition 1 for port 1

Read communication

definition 1 for port 1

Read communication

definition n for port 1

Write communication

definition n for port 1

(if changed)

Communication period

Serial communication module

Subsystem

• • • CMD: Command RSP: Response

CM

D R

SP C

MD

RSP

CM

D R

SP C

MD

RSP

Figure B1.1-5 Subsystem communication (example numbers of communication definitions for port 1is "n")

In serial communication, each port of the serial communication module communicates at a dif-ferent period. The communication period of each port represents the sum of times required tocommunicate all communication definitions set for the port.Example:

Communication definition 1: Port 1Communication definition 2: Port 1Communication definition 3: Port 2Communication definition 4: Port 2Communication period of port 1 = (Communication time for communication definition1) + (Communication time for communication definition 2)Communication period of port 2 = (Communication time for communication definition3) + (Communication time for communication definition 4)



n Assurance of simultaneity of communication dataIn the SCS (between the subsystem communication module and the communication I/O datamanagement function), simultaneity of data is assured in units of 32 bits.Between the subsystem communication module and each subsystem, the unit of data inwhich simultaneity is assured varies, depending on the subsystem communication programand the subsystem.

SEEALSO For more information about assurance of simultaneity of communication data for Modbus communication pro-

grams, refer to:

“n Simultaneity of communication data” on page B3-2

n Handling of subsystem dataThe following table shows how subsystem data types are handled in the SCS.

Table B1.1-1 Types of subsystem data handledSubsystem 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 DINT (32-bit signed integer)

32-bit signed integer DINT (32-bit signed integer) With/without word reversing

SLS event type N/A (*1) Without bit reversing, without wordreversing

*1: SLS event type represents the ProSafe-SLS data type that is used exclusively for acquiring events. This data type is usedinternally by the SCS. It cannot be used in application logics.

In order to handle the subsystem communication data on SCS, the Communication I/O Build-er is used for wiring the subsystem data and the SCS data according to the data types of sub-system. All the wired data are referred to as "communication data." A communication datumconsists 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 tosubsystems will start following the output enable operation for subsystem communication.Note, however, that output will start immediately after the subsystem communicationmodule is started following a recovery from an error, no output enable operation is re-quired in such a case. Readback of output will start as soon as the subsystem communi-cation module is started.

• Output from the subsystem communication module is disabled only after an initial coldstart of the SCS.

• Regardless of the status of the subsystem communication module, output enable opera-tion for the safety output modules can be performed at any time.

• Output enable operation can be performed even when a subsystem communication erroris present. In this case, output will start only for those outputs that can be communicated.



n IOM downloadWhen an IOM download is performed, the subsystem communication program is downloadedto the subsystem communication module and the communication module is restarted. No out-put enable operation is required.

n Status monitoring from SENG or HIS• The status of the subsystem communication module can be monitored in the status dis-

play window of the SENG or HIS.

• From a SENG, communication program names and error information can be referencedusing SCS Maintenance Support Tool's IOM Report.

• The forcing status of subsystem communication data and errors in the subsystem com-munication module are notified as diagnostic information messages.



B1.2 Dual-redundant communicationIf the ALR111 or ALR121 is used, dual-redundant communication can be implemented byconnecting two serial communication modules side by side. Note, however, that dual-redun-dant communication cannot be implemented without readback.ALR121M redundancy is not supported by the ProSafe-SLS communication function.

n Data flow in a dual-redundant configuration of subsystemcommunication modules

The following figure illustrates the flow of data when the subsystem communication modulehas a dual-redundant configuration and readback is performed.


module (standby side)

Communication I/O images (odd-number slots)

Input

Subsystem communication module (control side)

Communication I/O images (even-number slots)



Input Output

Output

Input Output Input Output

Input Output

Application logic (POU) Subsystem communication

input FBs

Writing of modified data

Readback of output data

Reading of input data


output FBs

SCS(CPU)

Reading of input data

Subsystem

Figure B1.2-1 Data flow in dual-redundant configuration of subsystem communication modules

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

<B1.2 Dual-redundant communication > B1-9


l Flow of output dataData is written to subsystems only from the subsystem communication module on the controlside. Details of the flow of output data 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 thedata output from each subsystem (readback).

• The subsystem communication module on the control side compares the value read backfrom the subsystem and the write data from the CPU, and writes the output data to thesubsystem only when the two values are different. If the two values are the same, thesubsystem communication module on the control side reflects the value read back fromthe subsystem in the image (area for output) inside the module.

• The subsystem communication module on the standby side does not write data, so datais not refreshed by the CPU. The image (area for output) inside the subsystem communi-cation module on the standby side is refreshed via readback of the output subsystem da-ta that have been changed via writing from the subsystem communication module on thecontrol side. This operation equalizes the output data of both the subsystem communica-tion modules on the control and standby sides.

TIP When you have online-changed the configuration of the subsystem communication module from a single todual-redundant configuration, the modules start the dual-redundant operation immediately after the module isadded. This does not affect the operating mode of the SCS because the output of the SCS stays enabled.

SEEALSO For more information about readback communication, refer to:

B3.6, “Readback communication” on page B3-21

<B1.2 Dual-redundant communication > B1-10


B1.3 Error handling actionsThis section describes the error handling actions after a restart of the subsystem communica-tion module, initial cold start of the SCS, occurrence of a communication error, and so on.

n Error conditions and error handling actionsThe following table summarizes the conditions in which error handling actions occur, as wellas the specific actions.

Table B1.3-1 Conditions in which error handling actions occur and specific actions

Condition Impact on application logic (Sub-system communication I/O FBs) Subsystem communication

Initial cold start of the SCS (theSCS operating mode is shiftingfrom Waiting Mode to RunningMode)

Input data: Value from the subsys-temInput status: GOODOutput status after output enableoperation: GOOD

Only inputs are communicated anddata is not output until the outputenable operation is performed.Output starts after the completionof output enable operation (forsubsystem communication) (*1)

• Communication error (subsys-tem communication error, com-munication definition error)

• Faulty subsystem communica-tion module

• Restart of the subsystem com-munication module due to on-line change download

• Path error between the CPUand subsystem communicationmodule

Upon occurrenceInput data: Value of "Input Pro-cessing at Fault"Input status: BADOutput status: BADAfter recoveryInput data: Value from the subsys-temInput status: GOODOutput status: GOOD

At occurrence: communication notpossible (*2)After recovery: I/O is resumed.Values are output from the appli-cation logic (*3) (*4)

Adding a new subsystem commu-nication I/O FB (online changedownload) (*5)

During online change downloadInput data: 0 or FALSEInput status: BADOutput status: BADAfter online change downloadInput data: Value from the subsys-temInput status: GOODOutput status: GOOD

No impact. Communication contin-ues.

Adding a subsystem communica-tion module online (*6)

Until the module starts upInput data: 0Input status: BADOutput status: BADAfter the module started upInput data: Value from the subsys-temInput/output status: Status of com-munication with the subsystem

Until the module starts up:Communication is not possible.After the module started up:Communication starts.In the case of outputs with read-back, the output values are readback from the subsystem immedi-ately after the recovery of subsys-tem communication and are out-put. After that, values from the ap-plication logic are output.

*1: The output enable operation using SCS Maintenance Support Tool enables both safety output and subsystem communicationoutput. Dedicated system function blocks are provided for enabling safety output and subsystem communication output, re-spectively.

*2: The SCS operating mode is not affected by communication errors or subsystem communication module errors.*3: If errors need to be latched, application logics that reference data status needs to be created.*4: 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.*5: 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.*6: The operating mode of the SCS is not affected because the output of the SCS stays enabled.

<B1.3 Error handling actions > B1-11


n Restart of the subsystem communication module when subsystemcommunication data is locked

If you perform the following types of operations that require a subsystem communication mod-ule restart, it is recommended that you lock the subsystem communication data first.• Before performing an online change download requiring a restart of the subsystem com-

munication module

• Before replacing the failed subsystem communication module. Perform an IOM downloadafter the replacement.

The following table lists the values and statuses of locked communication I/O data before andafter the recovery of the subsystem communication module to a normal state.

Table B1.3-2 Statuses of locked communication I/O dataBefore recovery After recovery

Communi-cation input

Logical da-ta

Data value: Value immediately beforelockingData status: Value immediately beforelocking

Data value: Value immediately beforelockingData status: Value immediately beforelocking

Physicaldata

Data value: Value immediately beforeoccurrence of an errorData status: BAD

Data value: Value from the subsystemData status: GOOD

Communi-cation out-put

Logical da-ta

Data value: Value from the applicationlogicData status: Value immediately beforelocking

Data value: Value from the applicationlogicData status: Value immediately beforelocking

Physicaldata

Data value: Value immediately beforelockingData status: BAD

Data value: Output value from the sub-system immediately after recovery ofcommunicationData status: GOOD

Output to subsystem Communication is not possible.Input: Resumed. Output: Output valuefrom the subsystem immediately afterrecovery of communication

n Notification of error conditions• Error conditions such as errors in the subsystem communication module and those relat-

ing 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 commu-nication.

• With the use of system FBs for subsystem communication, an application logic that de-tects unlocked subsystem communication data and overflow of lock limit can be created.If any subsystem communication data remains unlocked or the number of locks exceedsthe maximum value, a diagnostic information message will be notified to the SENG orHIS.

n Diagnostic information messagesIf the subsystem communication module status or communication status with any subsystemhas changed, a diagnostic information message is generated to notify the change. Diagnosticinformation 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.

• When a subsystem communication module is added or deleted online



B1.4 Setting items relating to subsystemcommunication

The following describes the setting items relating to subsystem communication. Subsystemcommunication builders can be used to set items relating to communication modules andthose relating to communication I/O data.

n Builders for subsystem communication

I/O Wiring View I/O Parameter Builder

Communication I/O Builder Tag Name Builder

SENG

CENTUM

Integration with CENTUM

SCS


module

Definition of communication data


module management

Subsystem



Wiring

Tag name definitions

Communication definitions

Device definitions

Transmission definitions

Figure B1.4-1 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 thesubsystem communication module. The setting items vary depending on the type of sub-system communication module.

• 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 subsystemcommunication I/O FBs.

<B1.4 Setting items relating to subsystem communication > B1-14


l Settings related to integration with CENTUM• Tag name definitions provide settings for assigning tag names to subsystem communica-

tion I/O FBs.

n Engineering procedure using related buildersThe I/O Wiring View, I/O Parameter Builder, Communication I/O Builder and Dictionary Vieware used to create communication definitions. The procedure and builders used in each stepare as follows: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 Build-er.

4. Define communication I/O assignments in the Comm. I/O Definition tab of the Communi-cation I/O Builder. Assign subsystem communication data to element numbers. This as-signs 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/OWiring tab of the Communication I/O Builder.Associate (wire) the subsystem communication I/O FBs defined in step 1 with the elementnumbers defined in step 4. Associate one subsystem communication I/O FB with one ele-ment number. This links the subsystem communication data assigned to the communica-tion 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

2. Definition of subsystem communication module

3. Definition of subsystem communication module parameters

4. Assignment of communication I/Os

1. Definition of subsystem communication I/O FBs using Dictionary View

5. Assignment of element numbers and subsystem communication I/O FBs

Figure B1.4-2 Engineering procedure using related builders



Define using I/O Wiring View

Define using Dictionary View

Define using Communication I/O Builder


module


module


Mapping of subsystem

communication data and

communication I/O data area

Mapping of element

numbers and subsystem

communication I/O FBs

Program (application logic)

Subsystem communication I/O FB



%WB200101 %WB200301

%WB210301 %WB210101

Figure B1.4-3 Wiring of subsystem communication I/O FBs and element numbers

The types of subsystem communication I/O FBs vary depending on the type of communica-tion I/O data to be assigned.

Table B1.4-1 Types of subsystem communication I/O FBs and types of data that can be wiredData type Type of wirable subsystem communication I/O FBs

Analog input (16-bit signed integer)

SCI_IAnalog input (32-bit signed integer) (*1)

Analog input (16-bit unsigned integer)

Analog input (32-bit floating decimal) (*1) SCI_R

Analog output (16-bit signed integer)

SCO_IAnalog output (32-bit signed integer) (*1)

Analog output (16-bit unsigned integer)

Analog output (32-bit floating point) (*1) SCO_R

Discrete input SCI_B

Discrete output SCO_B

*1: Cannot be used in connection with the ProSafe-SLS communication function.



B1.4.1 Settings using the I/O Parameter BuilderThe I/O Parameter Builder is used to specify settings relating to subsystem communicationmodules.

SEEALSO For more information about recommended settings and items for consideration when using Modbus commu-

nication programs, refer to:

B3.5.2, “Items set in the I/O Parameter Builder” on page B3-17

n Subsystem communication module settingsSubsystem communication module settings are specified in the Module tab where commoncommunication module parameters are set, and in the Port tabs where port parameters areset.The Port tabs include the Port 1 and Port 2 tabs. Together with the Module tab, thus, a total ofthree tabs are available.

l Module tabThe following items are set in the Module tab:

Pjt:SCS1020 File:IOMDEFSB.edf

1-7 ALR111M

I/O

Node1

1-8 ALR121(

1-5 SAI143([ 1-3 SAI143([

1-1 SDV144(

S_MODBUS

Module Port 1 Port 2

Node Number

Slot Number

Device

Dual-Redundant

Device Number

Connection Device

Comment

1

7

ALR111M

No

4

Figure B1.4.1-1 Module tab (serial communication module for subsystem communication)

l Node NumberThe node number corresponding to the mounting position of the module is displayed. Thenode number is defined in the I/O Wiring View of SCS Manager.• The "Node Number" field is read only.

l Slot NumberThe slot number corresponding to the mounting position of the module is displayed. The slotnumber is defined in the I/O Wiring View of SCS Manager.• The "Slot Number" field is read only.

l DeviceThe type of module is displayed. The device (module type) is defined in the I/O Wiring View ofSCS Manager.• The "Device" field is read only.



l Dual-RedundantWhether the module is used in a single or dual-redundant configuration is displayed. The du-al-redundant specification is defined in the I/O Wiring View of SCS Manager.• The "Dual-Redundant" field is read only.

l Device NumberThe device number assigned to the module. The device number is defined in the I/O WiringView of SCS Manager.• The "Device Number" field is read only.

l Connection DeviceSet the type of connection device (subsystem). This field is displayed only when the moduletype is a subsystem communication module.Select the subsystem communication program to be used.

l CommentA comment regarding the module. A desired comment can be entered using up to 24 single-byte characters or 12 double-byte characters.

l Port 1 and Port 2 tabsThe setting items in the Port 1 and Port 2 tabs change in accordance with the module typeand the "Connection Device" setting in the Module tab. The setting items are the same be-tween the Port 1 and Port 2 tabs.

Pjt:SCS1020 File:IOMDEFSB.edf

1-7 ALR111M

I/O

Node1

1-8 ALR121(

1-5 SAI143([ 1-3 SAI143([

1-1 SDV144(

Module Port 1 Port 2

Baud Rate

Stop Bits

Parity

Data Bits

Control Line (RS Control)

Control Line (DR Check)

Control Line (CD Check)

Reception Inter-Character Timer

Response Timeout

Communication Retry

Interval of Connection Retries

2-Wire/4-Wire

Option 1

Option 2

Option 3

Option 4

19200

1bit

Even

8bit

No

Yes

No

10 ms

4 s

1

30 s

4-Wire

0

0

0

0

Figure B1.4.1-2 Port 1 tab (example where S_MODBUS is set as Connection Device)



Table B1.4.1-1 Setting items available in Port 1 and Port 2 tabsTitle Description Remark

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 subsystemdata to be transmitted. -

Control Line

RS Control Specify whether or not to use RS controlwhen sending data from the ALR111M.

Valid only when theALR111M is used.

DR CheckSpecify whether or not to use DR signalline check when sending data from theALR111M.


CD CheckSpecify whether or not to use CD signalline check when sending data from theALR111M.


Reception Inter-Character TimerSpecify the period to monitor inter-charac-ter time when data is received by theALR111M/ALR121M.

-

Response Timeout Set the timeout period to wait for subsys-tem response. -

Communication Retry Set the number of retries to be attemptedafter a communication error occurs. -

Interval of Connection Retries

Set the interval of communication with astation that generated a communicationerror to check for recovery of communica-tion (recovery communication).

-

2-Wire/4-Wire Specify the 2-wire or 4-wire connectionmethod.


Options 1 to 4 Not used -

l Baud RateSpecify the baud rate of communication. Select from 1200, 2400, 4800, 9600, 19200 and38400 bps. The default is 19200 bps.

l Stop BitsSpecify the stop bits of communication. Select 1 bit or 2 bits. The default is 1 bit.

l ParitySpecify the parity. Select None, Odd or Even. The default is Even.

l Data BitsSpecify the data bit length of subsystem data to be transmitted. Select 7 bits or 8 bits. Thedefault is 8 bits.

l RS ControlSpecify whether or not to use RS control when sending data from the ALR111M. This settingis valid only when the ALR111M is used. The default is No (without RS control).• No (without RS control)

The RS signal line is always turned ON regardless of whether or not data is sent from theALR111M.

• Yes (with RS control)



The RS signal line is turned ON when data is sent from the ALR111M, and turned OFFafter the sending is completed.

l DR CheckSpecify 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 (with DR check).• 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 doesnot turn ON after elapse of the transmission enable monitoring 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 sub-system and used to determine if the subsystem can receive data (normal operation). If thesignal line of the subsystem cannot be used, set No (without DR check) in this field orchange 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 CheckSpecify whether or not to use a CD signal line check when sending data from the ALR111M.The default is No (without CD check).• 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 doesnot turn OFF after elapse of the transmission monitoring time, a "Communication linebusy (A392)" error will occur.

l Reception Inter-Character TimerThe reception inter-character timer (reception inter-character timeout setting) is a function formonitoring the time between adjacent characters received (interval after one character is re-ceived until the next character is received) by the ALR111M/ALR121M. In the Modbus com-munication program, the receive operation is considered complete if no characters are re-ceived within the set time.If communication is performed via a modem or other device that provides data buffering func-tion, this value needs to be set in consideration of the communication delay (inter-characterdelay) caused by the buffering at the modem. Note, however, that increasing the reception in-ter-character time will affect the RS communication time, since completion of reception is de-termined based on elapse of this time.

Default: 10 msSetting range: 0 to 99999 ms

l Response TimeoutSet the timeout period to wait for subsystem response. The unit is second.Default: 4 secSetting range: 0 to 99 sec

l Communication RetrySet the number of retries to be attempted after a communication error occurs.Default: 1 time



Setting range: 0 to 99 times

l Interval of Connection RetriesSet the interval of communication with a station that generated a communication error tocheck for recovery of communication (recovery communication). The unit is second.Default: 30 secSetting range: 1 to 999 sec

l 2-Wire/4-WireSpecify the 2-wire or 4-wire connection method used by the ALR121M. This setting is validonly when the ALR121M is used.

l Option 1 to 4Specify the different communication parameter options for each subsystem communicationprogram.



B1.4.2 Settings using the Communication I/O BuilderThe Communication I/O Builder is used to define communication I/O data assignments andwire communication I/O variables.

SEEALSO For more information about recommended settings and items for consideration when using Modbus commu-

nication programs, refer to:

B3.5.3, “Items set in the Communication I/O Builder” on page B3-18

n Communication I/O settingsThe 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 thesubsystems

• Wire %WB elements and communication I/O variables

The structure of the Communication I/O Builder window is as follows:

Communication I/O Builder-[Pjt:SCS0101 File:CommIO.edf]

%WW2001

%WW2002

%WW2010

%WW2003

%WW2004

%WW2005

%WW2006

%WW2007

%WW2008

File Edit View Tool Window Help

Comm. I/O Definition Comm. I/O Wiring

Element

%WW2009

Buffer Program Name Size Port Station

Message

Ready

2 6 1-7S_MODBUS 1

1 1

* *

* *

* *

* *

* *

* *

*

*

* *

Position : Line 1 Column 4

Data menu area Workspace

Title bar Menu bar Toolbar

Message display area Status bar

Figure B1.4.2-1 Structure of Communication I/O Builder window



n Comm. I/O Definition tabCommunication I/O Builder-[Pjt:SCS0101 File:CommIO.edf]

%WW2001

%WW2002

%WW2013

%WW2003

%WW2004

%WW2005

%WW2006

%WW2007

%WW2008


Element

%WW2009

%WW2010

%WW2011

%WW2012

Buffer Program Name Size Port Station

2 1-7S_MODBUS

* *

* *

* *

* * *

* *

*

*

* *

Buffer

4 4 1

Figure B1.4.2-2 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 ElementThe buffer address within the communication I/O data area is displayed.

Display format: %WWnnnn%WW:nnnn:

Fixed2001 to 3000

l BufferSpecify the size of the communication I/O data area to be used by the subsystem communi-cation program, in units of words (16 bits). This can only be entered when the "Element num-ber" field is an odd number.• 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 dis-play asterisks (*) in the subsequent "Buffer" and "Program Name" fields corresponding to thebuffer size that has been allocated, where there is no error in the defined items. These aster-isks 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 "Pro-gram 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 atFault) as well as asterisks in the applicable fields will be deleted, and these fields can nowaccept new settings.If a "Buffer" is changed, the asterisks will also be changed. The "Buffer" field cannot bechanged to a value smaller than the value in the "Size" field. Moreover, the designated valueof Buffer should not conflict with the reserved area. If the error value is entered, it would becancelled so as to revert to the previous value.Example:

When changing the buffer for %WW2001 to "4"

Table B1.4.2-1 Example of definitions before changeElement Buffer Program Name Size • • •

%WW2001 2 (*1) 1-3S_MODBUS

%WW2002 * *

%WW2003 4 1-5S_MODBUS

%WW2004 * *

%WW2005 * *

%WW2006 * *

*1: An attempt to change "2" to "4" will generate an error, since specifying "4" overlaps with the area already allocated for%WW2003.

l Program nameSpecify the program name using a combination of the node number and slot number for thesubsystem communication module defined in the I/O Wiring View, and a fixed characterstring. The program name can be entered using up to 12 single-byte alphanumeric charactersand symbols (+, -, _).The "Program Name" field cannot be selected if the corresponding "Buffer" field is not speci-fied 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 inthe I/O Parameter Builder).

If the program name is changed, a confirmation dialog box appears with a message asking ifyou want to delete the communication data and wirings. The following shows the content ofcommunication data.• Size

• Port



• Station number

• Device Address

• Data type

• Comment

• Reverse

Clicking [OK] deletes the communication data and wirings.Clicking [Cancel] restores the original program name without deleting the communication dataand wirings.

l SizeSet 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 numberaddress.• Input range: 1 to 1000

If an odd number is specified as the size, the odd number will be displayed, but the actualsize to be allocated will correspond to an even number being the sum of the specified oddnumber and 1.If the data type is SLSEVENT, set "24."An error will occur in the following situations:• 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" isdiscrete input or output, exceeded 256 words.

• An odd value is specified when the "Data Type" is 32-bit analog input or output.

• An attempt is made to change the assigned size to other than 24 when the "Data Type" isSLSEVENT.

After a size has been specified, moving to the next setting item will display asterisks (*) in thesubsequent "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. Theseasterisks indicate that data of the specified size has been assigned. The fields showing aster-isks do not accept new settings. Deleting a "Port," "Station Number, "Device Address," "DataType" 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, Deviceaddress, Data type, Reverse, Input Processing at Fault, Input Value at Fault) as well as aster-isks 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 smallervalue, the items that have been set in the data corresponding to the size decremented will bedeleted.

Table B1.4.2-2 Example of completed item settings

Element Buffer Program Name Size Port Station DeviceAddress Data Type Reverse

%WW2001 4 1-3S_MODBUS 2 1 1 A10012 Input (Discrete) No

%WW2002 * * * * * * * *

%WW2003 * *

%WW2004 * *

%WW2005



l PortSpecify the port of the subsystem communication module to be used. Select 1 or 2. The de-fault is 1.

l StationSpecify the station number for the subsystem. Select a value between 0 and 255. The specifi-able values vary depending on the subsystem. The default is 1.

l Device addressSpecify the content of data to be acquired from the other device, using a combination of thecommunication method used by the subsystem and the beginning data address.To use the data type SLSEVENT, enter "SLSEVENT."After the data type SLSEVENT is specified, this item is automatically set to "SLSEVENT."

l Data typeSpecify the type of subsystem data. The following list shows the data types that can be selec-ted.• 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)

• 11: SLSEVENT

If discrete input or output is selected, whether or not the total sum of "Sizes" assigned to alldiscrete 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 con-tains an even number is checked. If an odd number is entered, an error will occur.When the ProSafe-SLS communication function is used, the data types 2, 4, 6 and 8 cannotbe specified. Also note that the data type 11 can be specified only when the ProSafe-SLScommunication function is used.If the data type SLSEVENT is selected, using any combination other than the following willgenerate an error.

Table B1.4.2-3 Items to be set for acquisition of ProSafe-SLS eventsProgram Name Size Device Address Data type

Setting value n-sS_SLSMOD 24 SLSEVENT SLSEVENT

SLSEVENT represents a communication definition unique to each combination of stationnumber and port, so defining multiple SLSEVENTs for the same combination of port and sta-tion number will generate a build error.



l ReverseSpecify 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. Thefollowing combinations of reverse specifications can be selected for each data type:

• 32-bit analog input/output: "2: No," "3: Words (word reversing)"• Discrete input/output: "1: Bits (bit reversing)," "2: No"• 16-bit analog input/output: Fixed to "2: No"• SLSEVENT: Fixed to "2: No"

l Input processing at faultSpecify the value to be input to the application logic, instead of the input value received fromthe subsystem, upon detection of an error. This field can be specified only when "discrete in-put" 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 theCPU to the communication module, errors in the communication module, and communicationerrors between subsystems and the communication module. Errors in subsystems are not ap-plicable.

Table B1.4.2-4 Input processing at fault (discrete input)Selection Description

0 0 Set the input value to 0 upon error detection.

1 1 Set the input value to 1 upon error detection.

2 Hold Retain the value before detection of an error (default).

Table B1.4.2-5 Input processing at fault (analog input)Selection Description

2 Hold Retain the value before detection of an error (default).

3 Fixed Value Use the input value specified in "Input Value at Fault" upon errordetection.

l Input value at faultIf "Fixed Value" is specified in "Input Processing at Fault," specify the input value to be usedinstead of the input value received from the subsystem.

• Default: 0• Input range: A value of up to 11 digits and containing a negative sign and/or a decimal

point

n Comm. I/O Wiring tabThe Comm. I/O Wiring tab shows a list of elements corresponding to the areas assigned inthe Comm. I/O Definition tab.



Communication I/O Builder-[Pjt:SCS0101 File:CommIO.edf]

%WB200101

%WB200201

%WB200301

%WB200401


Element Data Type Variable Name

ALARM001_CLS1@SYSiFBD ALARM001_CLS2@SYSiFBD ALARM001_CLS3@SYSiFBD ALARM001_SUM@SYSiFBD ALARM002_CLS1@SYSiFBD ALARM002_CLS2@SYSiFBD ALARM002_CLS3@SYSiFBD ALARM002_SUM@SYSiFBD ALARM003_CLS1@SYSiFBD ALARM003_CLS2@SYSiFBD ALARM003_CLS3@SYSiFBD ALARM003_SUM@SYSiFBD ANLGI001_HHH@HISIFFBD ANLGI001_HTRP@HISIFFBD ANLGI001_LLL@HISIFFBD ANLGI001_LTRP@HISIFFBD ANLGI001_SOER@HISIFFBD ANLGI002_HHH@HISIFFBD ANLGI002_HTRP@HISIFFBD ANLGI002_LLL@HISIFFBD ANLGI002_LTRP@HISIFFBD ANLGI002_SOER@HISIFFBD ANLGI003_HHH@HISIFFBD ANLGI003_HTRP@HISIFFBD ANLGI003_HTRP@HISIFFBD

Input (16-Bit Signed)




SCI_I SCI_R SCI_B S

Type

Figure B1.4.2-3 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 ElementAn element or elements (%WB) is/are assigned automatically in accordance with the elementnumber (%WW) for which "Buffer" and "Size" have been set in the Comm. I/O Definition tabas 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

Any area to which the data type SLSEVENT is assigned on the Communication I/O Definitiontab will not be displayed on the Communication I/O Wiring tab. The data type SLSEVENTcannot be wired.

l Data typeThe data type specified in the Comm. I/O Definition tab is displayed.• The "Data Type" field is read only.

l Variable nameYou can use any of the following methods to set the instance name for a Subsystem Commu-nication FB (SCI_B, SCI_I, SCI_R, SCO_B, SCO_I, SCO_R) in each variable name.• 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 B1.4.2-6 Examples of variable specificationVariable name(*1)

(*2) 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 de-

fined locally in PROG1 function

FB01.FB2.SCIB3 GlobalInternal variable SCIB3 of user-defined function block instance FB2, whichis used in user-defined function block instance FB01 (maximum limit offunction block nesting)

*1: Also note the following:• 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 User-

defined 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 per-

mitted in each variable.*2: A variable name can be up to 67 characters long.

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.• If a variable name has 3 or more nests, an error will result. In the above table, "FB01.SCIB3" and "FB01.SCIB3@PROG1"

have one nest, while "FB01.FB2.SCIB3" has two nests.

The following table lists the combinations of variable types and data types specified in theComm. I/O Definition tab. The types of the variable are the Subsystem communication FBs.

Table B1.4.2-7 Data types and specifiable variable typesData type Variable type

Analog input (16-bit signed integer)

SCI_IAnalog input (32-bit signed integer)

Analog input (16-bit unsigned integer)

Analog input (32-bit floating) SCI_R

Analog output (16-bit signed integer)

SCO_IAnalog output (32-bit signed integer)

Analog output (16-bit unsigned integer)

Analog output (32-bit floating) SCO_R

Discrete input SCI_B

Discrete output SCO_B

l TypeThe selected variable type is displayed. The type of the variable is the Subsystem communi-cation FB.• The "Type" field is read only.

l CommentA comment for the selected variable is displayed.• The "Comment" field is read only.



B1.5 Forcing of subsystem communication dataThis 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 LanguageEditor.

• Forcing can be performed when the SCS security level is 1 or below.

• Communication with subsystems will continue even after subsystem communication datais locked.

• It is not possible to lock a given set of communication data. All data of a module or allinput data or output data of a module will be locked simultaneously.

• Data status values are changed for each communication definition. Data values arechanged for each communication data item.

• In the SCS, forcing of subsystem communication data is processed using a completelydifferent mechanism from one used for forcing of I/O variables. Forcing of subsystemcommunication applies only to the communication I/O data area via the communicationI/O data management function.

• Communication data of SLSEVENT data type can be defined for communication modulesthat are used in connection with the ProSafe-SLS communication function, but such com-munication data constitute special data that is used for acquiring events and are not wiredto the subsystem communication function blocks. Accordingly, communication data ofSLSEVENT data type are not displayed in the communication data list view and thus notlocked or allow values to be set.

• If the communication I/O module (model: ALR121) used in connection with the ProSafe-SLS communication function is locked, events will be the only information to remain un-locked. All data other than events will be locked.

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 manage-ment function cuts off the flow of logical data and physical data. If communication inputdata is locked, inputs from subsystems will not reach the application logic. If communica-tion 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.

<B1.5 Forcing of subsystem communication data > B1-30


SCS Application logic execution


input FBs

Forcing (communication input data)

Forcing (communication output data)

Referencing of communication I/O data


Communication I/O data area (logical data)

Communication I/O data area (physical data)

Subsystem

Mapping elements (%WB)

In accordance with locking


output FBs Logic

Figure B1.5-1 Communication I/O data management and forcing

n Locking subsystem communication dataSubsystem communication data can be locked or unlocked based on the following units: Allsubsystem communication data in each scope will be locked or unlocked.

Table B1.5-1 Subsystem communication data locking unit and rangeLocking 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 appli-cation logic and outputs from the application logic will stop and the previous values will beretained.

• Locking and unlocking will both generate a diagnostic information message.

• All outputs of a module can be locked, even for a subsystem communication module forwhich no output communications have been defined. As long as subsystem communica-tion outputs are locked before an online change download, output data will be lockedeven when output communication definitions are added, via the online change, to themodule with no output communication definitions. The same applies to inputs.

l SCS operations while subsystem communication data is lockedThe following table shows how the SCS operates when subsystem communication data islocked.



Table B1.5-2 SCS operations while subsystem communication data is lockedWhat is locked Subsystem communication I/O FBs Subsystem communication

Subsystem communica-tion inputs

The values immediately before lockingare retained for data values and datastatuses.

Communication is not affected.

Subsystem communica-tion outputs

The values immediately before lockingare retained for data statuses.

The values immediately before lockingare used as the output values to sub-systems.

n Setting subsystem communication data values• 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 oc-cur.

• 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 willaffect all communication data in the same communication definition, so check the poten-tial impact thoroughly before changing a data status.

• When a value is set, a diagnostic information message will be notified.

TIP Communication data corresponds 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, datastatuses 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 asubsystem. 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 "ProgramName" in the Communication I/O Builder.

Table B1.5-3 Setting subsystem communication data valuesSetting target Subsystem communication I/O FBs Subsystem communication

Subsystem communica-tion inputs

The values set in the CommunicationI/O Lock window are reflected in datavalues and statuses.

Communication is not affected.

Subsystem communica-tion outputs

The data statuses set in the Communi-cation I/O Lock window are output fromsubsystem communication output FBs.

The data values set in the Communica-tion I/O Lock window are used as theoutput value to subsystems.

n Management of subsystem communication data lock status• By using the SYS_FORCE_SC function block, the lock status of subsystem communica-

tion data can be handled in the application logic.

• The SYS_FORCE_SC function block detects a lock timeout of subsystem communicationdata and forcibly unlocks subsystem communication data.

• Locking of subsystem communication data does not affect the lock management of I/Ovariables 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 oflocks is not counted.



B1.6 Communication I/O Lock windowThis 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 out-puts 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 to-gether.The Communication I/O Lock window is used to perform the following tasks:• Perform forcing during debugging of an application logic that uses subsystem communi-

cation

• Disconnect inputs/outputs during maintenance of a subsystem communication module

• Fix communication inputs/outputs from/to a subsystem during online change download

n Positioning of the Communication I/O Lock windowThe Communication I/O Lock window is one of the windows used mainly for maintenance pur-poses. The Communication I/O Lock window is launched from SCS Manager.The positioning of the Communication I/O Lock window is as follows:

SENG

SCS Manager

SCS MaintenanceSupport Tool

Launch LaunchLaunch

Engineering Maintenance Controller

Builders

Analyzers

Tools

I/O Lock Window

Communication I/OLock Window

Inter-SCS Communication Lock Window

SCS Link TransmissionLock Window

SaveOperation

Marks

DownloadOperation

Marks

• •

•

Figure B1.6-1 Positioning of Communication I/O Lock window in SENG

In the Communication I/O Lock window, communication inputs/outputs can be locked orforced via the communication I/O data management function included in the SCS's subsystemcommunication functions.

<B1.6 Communication I/O Lock window > B1-33


SENG

SCS

Communication I/O Lock window I/O Lock window

Locking/ setting of values

Locking/ setting of values

Application logic execution function


I/O FBs I/O variables

Subsystem communication function


AIO/DIO data I/O function

Send/receive Input/output

Subsystem Detecting element,

final control element

Figure B1.6-2 Relationship with SCS and subsystem

n Functions of the Communication I/O Lock window

l Locking and unlockingIn the Communication I/O Lock window, subsystem communication data inputs and outputscan be locked or unlocked. The lock status is also displayed for locked data.Locking and unlocking of data can be performed based on 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 valuesValues can be set when subsystem communication input or output data is locked. Logical da-ta 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 eachcommunication definition.When the SCS project target name is SCS_SIMULATOR, it is possible to set values to multi-ple communication data together.

n Start the Communication I/O Lock window1. 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] buttonon 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 run-

ning in SCS Manager.

• Multiple Communication I/O Lock windows cannot be launched simultaneously regardlessof 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 closedor a different SCS project is opened.

n Exit the Communication I/O Lock windowTo exit the Communication I/O Lock window, on the [File] menu, select [Exit].If any communication module is locked when exiting the Communication I/O Lock window, theconfirmation dialog box appears. Click [OK] to close the Communication I/O Lock window.

Communication I/O Lock Window

OK

Communication I/O module is locked.

Figure B1.6-3 Confirmation dialog box

To unlock the applicable communication module, start the Communication I/O Lock windowagain and perform the necessary operation.

IMPORTANTIf you commenced an online change download when the Communication I/O Lock window isopen, close the Communication I/O Lock window after the online change download is comple-ted.If the Communication I/O Lock window remains open after completion of an online changedownload in which a subsystem communication database was changed, a database discrep-ancy error may occur when the displayed data is refreshed subsequently. When this error oc-curs, a message prompting you to re-launch the Communication I/O Lock window will be dis-played.



B1.6.1 Structure of the Communication I/O Lock windowThis section describes the window structure and components of the Communication I/O Lockwindow.The structure of the Communication I/O Lock window is as follows:

3-1S_MODBUS:002 Port1:I32 Input

File Lock OptionEditCommunication I/O Lock Window [Pjt:SCS0101] *****SCS_TARGET*****

MODULE LIST Inputs/Outputs

L D Module I/O CommentCommentCommentCommentComment

3-1 ALR1113-1 ALR1113-3 ALR1113-3 ALR111

I

IO

O

COMMUNICATION DATA LIST All Data

Definition %WB L D Instance Logical Value Physical Value Co3-1S_MODBUS:001 Port1:DI

200102

200103

200104

200105

200106

200107

200108

200501

200701

●

●

●

● ●

●

●

●

●

●

●

●

●

●

●

●

●

DI0000.V DI0000.STS DI0001.V DI0001.STS DI0002.V DI0002.STS DI0003.V DI0003.STS DI0004.V DI0004.STS DI0005.V DI0005.STS DI0006.V DI0006.STS DI0007.V DI0007.STS I32000.V I32000.STS I32001.V I32001.STS I32002.V

TRUE GOOD

TRUE GOOD

TRUE GOOD FALSE GOOD FALSE GOOD

FALSE GOOD FALSE GOOD FALSE GOOD 1 GOOD

1 GOOD 0 GOOD

2 GOOD

TRUE GOOD

TRUE GOOD

TRUE GOOD

TRUE GOOD

TRUE GOOD

TRUE GOOD TRUE GOOD TRUE GOOD

0 0

Input Modules Selected: 1/2 Output Modules Selected 1/2

200101

200301

Status barMessage display area

Communication Module List View

Communication Data List View

Title bar Toolbar Menu bar Drop-down list box

Figure B1.6.1-1 Communication I/O Lock window

The following section explains the elements that make up the window.

n Title barOn the title bar, besides window name and project name, the SCS status is also displayed.

SCS_TARGET:SCS_SIMULATOR:(No display):

Indicates communication with the SCS.Indicates communication with the SCS Simulator.Indicates the SCS is not running.

For logic simulation test, "SIMULATION" will be displayed in the position of SCS status.

n Menu barThe following menus are provided on the menu bar:



• [File] menu

• [Edit] menu

• [Lock] menu

• [Option] menu

The following menu items are provided on each menu:

Table B1.6.1-1 [File] menuMenu 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 B1.6.1-2 [Edit] menuMenu item Description

Cut(*1) Cut

Copy(*1) Copy

Paste(*1) Paste

Delete(*1) Delete

Select All Select All (the same as pressing the [Ctrl] key + the [A] key on the keyboard)


Table B1.6.1-3 [Lock] menuMenu item Description

Lock Modules Locks all modules selected.

Unlock Modules Unlocks all modules selected.

Set Values(*1) Sets all values of communication data.


Table B1.6.1-4 [Option] menuMenu item Description

Numerical Display

INTDecimal Displays in hexadecimal number format.(*1)

Hexadecimal Displays in hexadecimal number format.

REAL

1.234E+12 Exponential notation

12.34567 Displays 5 decimal places.





Data Acquiring ModeAll Modules Changes data acquiring mode to "All Modules"

mode

Selected Modules Changes data acquiring mode to "SelectedModules" mode

*1: A negative sign is added if the value of a signed integer is negative.



n ToolbarThe following buttons are provided on the toolbar:

Table B1.6.1-5 Toolbar buttonsButton Description

(*1)Imports the values for setting all together to communication data from afile. Same as choosing [Import Values] from [File] menu.

(*1)Exports the values for setting all together to communication data to afile. 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)Sets all values of communication data. Same as choosing [Set Values]from [Lock] menu.

(All Modules)

(Selected Modules)

Switch data acquisition modes (same as the [Data Acquiring] on the[Option] menu. Switches between [All Modules] and [Selected Mod-ules])


n Data acquisition modeThe 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 subsystemcommunication modules defined in the applicable SCS project will be acquired sequen-tially.

• "Selected modules" modeCommunication data corresponding to the communication definitions of the subsystemcommunication modules selected in the Communication Module List View will be ac-quired sequentially.While data is acquired, "Updating Selected Modules" is displayed in the CommunicationModule List View and Communication Data List View.

n Communication Module List ViewThe Communication Module List View shows a list of subsystem communication modules de-fined in the current SCS project.Two lines, one for subsystem communication inputs and the other for subsystem communica-tion outputs, are displayed for each subsystem communication module. Even when input/output communications are not defined for the module, or subsystem communication I/O FBsare not wired to the module's communication definitions, this view always shows two lines foreach subsystem communication module.With the subsystem communication modules used in a dual-redundant configuration, informa-tion of the module in the odd-number slot is displayed regardless of which module is currentlyoperating. Note, however, that the L and D fields show the corresponding statuses of themodule on the control side.The following items are displayed in the Communication module list view:



Table B1.6.1-6 Items displayed in Communication Module List ViewItem Description

L Lock status of communication data for the subsystem communication module

D Consistency/discrepancy of logical data and physical data of communication data for thesubsystem 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 communicationmodules

Table B1.6.1-7 Lock status display (L field)LED Meaning

(No symbol) None of the communication data is locked.

(red) All communication data are locked.

? (black) Communication with the SCS is disabled.

l Consistency/discrepancy of logical data and physical data ofcommunication data for subsystem communication modules

Discrete inputs and outputs are deemed to have "discrepancy" if the logical data and physicaldata of the data value or data status are different.Analog inputs and outputs are deemed to have "discrepancy" if the logical data and physicaldata of the data status are different.

Table B1.6.1-8 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.


The consistency/discrepancy display of communication data for each subsystem communica-tion 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 applicableSCS 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 Communi-cation Module List View will be refreshed and displayed sequentially. A "?" symbol will beshown in the D field for subsystem communication modules that are not selected.

l FilteringSubsystem communication modules can be filtered based on input/output classification by us-ing the drop-down list box.



Table B1.6.1-9 Drop-down list box in Communication Module List ViewMenu 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 menuClick the right mouse button on the Communication Module List View to display the pop-upmenu.The following menu items are displayed in the pop-up menu:

Table B1.6.1-10 Pop-up menu in Communication Module List ViewMenu item Description

Select All Selects all displayed modules. Same as choosing [Select All] from [Edit] menuand same action as pressing the [Ctrl] key and [A] key together.

n Communication Data List ViewThe Communication Data List View shows information regarding the communication datawired to subsystem communication I/O FBs, for the subsystem communication modules se-lected in the Communication Module List View.When the subsystem communication input line of a communication module is selected in theCommunication Module List View, information of the communication data corresponding tothe applicable input communication definition will be displayed.When the subsystem communication output line of a communication module is selected in theCommunication Module List View, information of the communication data corresponding tothe applicable output communication definition will be displayed.Communication data of SLSEVENT data type can be defined for S_SLSMOD subsystemcommunication that is used in connection with the ProSafe-SLS communication function, butsuch communication data constitute special data that is used for acquiring events and are notwired to the subsystem communication function blocks. Accordingly, communication data ofSLSEVENT data type are not displayed in the Communication Data List View and thus notlocked or allow values to be set.

Table B1.6.1-11 Items displayed in Communication Data List ViewItem Description

Definition Communication definition

%WB %WB element number %WBnnnnbb (nnnn: 2001 to 3000, bb: 01 to 16)

L Lock status of communication data

D 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 definitionCommunication definition (for Modbus communication program) is displayed in the followingformat:



n-sConnectionDevice :cPortp:DataType

• n: Node number• s: Slot number• c: Communication definition number• ConnectionDevice: Communication program name• p: Port number• DataType:

• DI:

• DO:

• I16 Input:

• I32 Input:

• U16 Input:

• R32 Input:

• I16 Output:

• I32 Output:

• U16 Output:

• R32 Output:

Data typeDiscrete inputDiscrete outputAnalog input (16-bit signed integer)Analog input (32-bit signed integer)Analog input (16-bit unsigned integer)Analog input (32-bit floating)Analog output (16-bit signed integer)Analog output (32-bit signed integer)Analog output (16-bit unsigned integer)Analog output (32-bit floating)

TIP Communication definition numbers specify communication definitions defined in one subsystem communica-tion 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 "ProgramName" in the Communication I/O Builder. Communication definition numbers are sequential numbers (startingfrom 1) assigned for each subsystem communication module.

l %WB element numberThe %WB element number included in the communication definition is displayed.

l Lock status of communication data

Table B1.6.1-12 Lock status display (L field)LED Meaning

(No symbol) Communication data is not locked.

(red) Communication data is locked.


l Consistency/discrepancy of communication dataDiscrete inputs and outputs are deemed to have "discrepancy" if the logical data and physicaldata of the data value or data status are different.Analog inputs and outputs are deemed to have "discrepancy" if the logical data and physicaldata of the data status are different.



Table B1.6.1-13 Communication data consistency/discrepancy display (of D field)Display Meaning

(No symbol) Communication data is consistent.

(red) Communication data has discrepancy.


l Instance nameThe instance name (data value (V) and data status (STS)) of the subsystem communicationI/O FB wired to the %WB is displayed.

l Logical data and physical dataFor BOOL-type data, "TRUE" or "FALSE" is displayed. DINT-type data and REAL-type dataare shown in the display format specified in the [Option] menu. The data status is displayedas either "GOOD" or "BAD". If communication with the SCS is disabled, "******" is shown.

l Refreshing of communication data consistency/discrepancy, logical dataand physical data display

How the consistency or discrepancy of each communication data is displayed, and how datavalues and statuses of logical data and physical data is refreshed, depend on the data acquis-ition mode.• When the data acquisition mode is "All Modules"

Data will be acquired sequentially from the communication definitions of all subsystemcommunication modules defined in the applicable SCS project. The display of the Com-munication 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 subsystemcommunication modules selected in the Communication Module List View. If only subsys-tem communication module inputs are selected, data will be acquired only from the inputcommunication definitions. If only subsystem communication module outputs are selec-ted, data will be acquired only from the output communication definitions. The display ofthe Communication Data List View will be refreshed once communication data is ac-quired.

l FilteringThe communication data to be displayed can be filtered using the drop-down list box.

Table B1.6.1-14 Drop-down list box of Communication Data List ViewItem 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 menuClick 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 following menu items are displayed in the pop-up menu:

Table B1.6.1-15 Items on pop-up menu in the Communication Data List ViewMenu item Description

Cut Same as [Cut] command on [Edit] menu.




Table B1.6.1-15 Items on pop-up menu in the Communication Data List View (Table continued)Menu item Description

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.

l Selecting communication dataIf the SCS project target name is SCS_SIMULATOR, you can select any communication datain the Communication Data List View.• Clicking a communication data while pressing the [Shift] key on the keyboard, the com-

munication data of the continuous lines can be selected.

• Clicking a communication data while pressing the [Ctrl] key on the keyboard, the commu-nication data of the separated lines can be selected.

• Choosing [Select All] from pop-up menu, all communication data can be selected.

n Message display areaThe results of all lock, all unlock and forcing operations are displayed as messages. The dis-played messages are cleared every time a new operation is performed.

n Status barThe status bar shows the following information relating to the subsystem communication mod-ules 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



B1.6.2 Operations in the Communication I/O Lock windowThe 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 (onlyin SCS Simulation Test).

Performing an all lock or all unlock operation by selecting input and output of a given modulewill 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 eachcommunication data item, while a data status value (STS) is set for each communication defi-nition.In SCS Simulation Test, you can set values all together to the communication data for thecommunication modules.

IMPORTANTNone of the previously mentioned operations can be executed during a build or download.

n Selection of subsystem communication modulesA desired subsystem communication module can be selected in the Communication ModuleList 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 allinputs.

• Selecting [Outputs] in the drop-down list box will display communication definitions for alloutputs.

When the following operations are performed, communication data is displayed in the Com-munication data list view.• Clicking an input line or output line of a subsystem communication module without press-

ing the [Shift] key or [Ctrl] key on the keyboard will display communication data for thecommunication definitions of the subsystem communication module specified in theclicked line.

• Clicking an input line or output line of subsystem communication modules while holdingdown the [Shift] key on the keyboard will display communication data for the communica-tion definitions of the subsystem communication modules specified in the lines betweenthe previously clicked (without [Shift] key) line through the line clicked this time.

• Clicking an input line or output line of subsystem communication modules while holdingdown the [Ctrl] key on the keyboard will display communication data for the communica-tion definitions of the subsystem communication modules specified in the clicked line, inaddition to the communication data currently shown.

• Selecting [Select All] in the pop-up menu on the Communication List View will displaycommunication data for the communication definitions of all subsystem communicationmodules currently shown in the Communication Module List View.



n All lock of subsystem communication modulesAll input data or output data of a selected subsystem communication module or all subsystemcommunication 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 andphysical data of each data value and status of the selected subsystem communicationmodule 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 in-put and/or output data will be locked.To cancel the operation, click [Cancel].

lock Modules

Are you sure to lock modules?

OK Cancel

Figure B1.6.2-1 Lock confirmation dialog box

n All unlock of subsystem communication modulesAll input data or output data of a selected subsystem communication module or all subsystemcommunication 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 andphysical data of each data value and status of the selected subsystem communicationmodule 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

Figure B1.6.2-2 Unlock confirmation dialog box

4. Click [OK] to perform the unlock. To cancel the operation, click [Cancel].

5. If [OK] is clicked in step 4, the reconfirmation dialog box will appear if there is a discrep-ancy between logical data and physical data for any one of the communication data itemscorresponding to the communication definitions of the subsystem communication moduleto be unlocked.



OK

Unlock Modules

Are you sure to unlock modules? Logical Value(s) and Physical Value(s) are not equal.

Cancel

Figure B1.6.2-3 Unlock reconfirmation dialog box

6. Click [OK] to perform the unlock. Click [Cancel] to cancel the operation.

n Set value to each communication dataFor each communication data, the value of data and data status can be set.

IMPORTANTSetting 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 Commu-nication Data List View will display the dialog box in which you can set the data value or sta-tus 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 dialogbox appears. If the lower part of the line showing a data status is double-clicked, the Writedata status dialog box appears.Set values in these dialog boxes. A data value is set for each communication data item, whilea data status is set for each communication definition. Once a data status value is set, thevalue will be reflected in all data statuses within the same communication definition.

Write data value

DI0000.V

FALSE TRUE 0 1

Cancel

Figure B1.6.2-4 Write data value dialog box (discrete input/output)

Write data value

I320000.V

Cancel Write

256 Enter new value:

Figure B1.6.2-5 Write data value dialog box (analog input/output)

Write data status

Definition 1

0 1

Cancel

BAD GOOD

Figure B1.6.2-6 Write data status dialog box

When the Write data value dialog box or Write data status dialog box opens for a discrete in-put 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 dia-log box opens.Whether logical data or physical data is displayed is determined based on which of the twovalues can be set at the time. Logical data is displayed if the logical data can be set, andphysical data is displayed if the physical data can be set. The following table shows the de-fault display for the dialog box.

Table B1.6.2-1 Initial displays of Write data value dialog box

DataInitial display

Locked Not lockedInput communication data: Data value 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

n Set values to multiple items of communication data togetherUsing the SCS Simulator, you can set values to multiple communication data items together.The following batch operations can be performed for the communication data from the com-munication module selected in 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. Ifmore data values are set at a time, some of the system alarm messages informing the datasetting or data status setting may not be transmitted.

l Enter the values to be set to communication dataThe values can be entered to the "Set Value" items on Communication data list view.The value can be entered using any of the following operations. After entering the values, youneed 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 communica-tion 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 click switches between TRUE, FALSE, and empty (nothingspecified).For DINT or REAL type data, values can be entered directly from the keyboard.

• Edit multiple data valuesFrom [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.

• Entering values using [Input Values][Input values] on the 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 "SetValue" 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.



l Set values to multiple communication dataFor the selected communication modules, the values of "Set Value" items on the Communica-tion Data List View can be set together to the communication data.

IMPORTANTSetting 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 toolbarso 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 novalues are entered, the communication data will not be changed.Click [Cancel] to cancel the operation.

l Export the setting values to a fileThe values for "Set Value" items of the communication data can be exported to a file.The procedure is as follows:1. Choose [Export Values] from [File] menu, or click the [Save (Export Values)] button on the

toolbarso 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 onthe Communication Module List View will be exported to the file.

IMPORTANTDo not edit the exported file if you want to import the file later.

l Import the setting values from a fileThe values for "Set Value" items of the communication data can be imported from a file.

IMPORTANTDo not import any file other than the file exported from Communication I/O Lock window.

The procedure is as follows:1. Choose [Import Values] from [File] menu, click the [Open (Import Values)] button on the

toolbarso 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 onthe Communication Module List View will be displayed with the data values and data sta-tuses imported from the file.If the values of data statuses differ among communication data in the same communica-tion definition in the CSV file, a warning message is displayed and the data status valueof the first communication data in the same communication definition is set to all the com-munication data within the same communication definition.



B1.7 Online changeThis section describes online changes such as the addition/deletion/dual-redundancy specifi-cation of subsystem communication modules, changes to settings relating to communicationinputs and outputs, the addition/deletion of subsystem communication I/O FBs, and changesto wiring for subsystem communication I/O FBs.

n Locking of subsystem communication dataBy locking subsystem communication data, you can reduce the impact of online changes onthe application logic or prevent erroneous outputs to subsystems resulting from applicationlogic correction errors.Subsystem communication data cannot be locked once an online change download is started.Lock subsystem communication data before starting an online 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 online change is completed, displaythe Communication I/O Lock window again, if necessary.

Table B1.7-1 Relationship of online changes and locking of communication modulesContent of change Lock

Change a transmission definition

Required (inputs/outputs need to be locked).

Add, change or delete a communication definition

Add a subsystem communication I/O FB

Change the wiring of a subsystem communicationI/O FB

Change an error handling action(*1)

Delete a subsystem communication I/O FB Not required.

*1: If a setting is changed while an error occurs, input values will change. Subsystem communication outputs are not affected.

n Online change procedureThe procedure for making an online change is as follows: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 SCS's security level to Level 1.

5. Lock the inputs/outputs of subsystem communication data in accordance with what youwant to change.

6. Close the Communication I/O Lock window.

7. Perform an online 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 SCS's security level to Level 2.

12. Save the SCS project using Version Control Tool.

<B1.7 Online change > B1-50


SEEALSO For more information about procedures for changing application options, refer to:

5.1, “Entire Procedure of Online Change of Application” in Engineering Guide (IM 32Q01C10-31E)

n Addition, deletion, and dual-redundant specifications of subsystemcommunication modules

SEEALSO For more information about availability of operations such as adding and deleting subsystem communication

modules, refer to:

5.2, “List of Applicable Items for Online Change” in Engineering Guide (IM 32Q01C10-31E)

n Online changes relating to communication inputs/outputsWhen changing a communication input/output setting in the Communication I/O Builder, alsochange the wiring of the subsystem communication I/O FB affected by the change.

l Online change downloadIf an online change download is to be performed after a communication input/output data orsubsystem communication module setting has been changed, the subsystem communicationdata of the target subsystem communication module needs to be locked before commencingthe online change download. If the subsystem communication data of the target module is notlocked, the application logic will be affected by a restart of the subsystem communicationmodule.The subsystem communication module will restart after the online change download is com-pleted. After the subsystem communication module has been restarted, unlock the subsystemcommunication data of the module.

n Online changes relating to subsystem communication I/O FBs

l Adding a subsystem communication I/O FBIf a subsystem communication I/O FB is added, the FB also needs to be wired. If the FB is notwired, a build error will occur.Before performing an online change download to add a subsystem communication I/O FB, thecommunication I/O data of the target subsystem communication module needs to be locked.An online change download to add a subsystem communication I/O FB is performed as a ser-ies of multiple scans. Specifically, the subsystem communication I/O FB is added first, andthen the wiring is changed. As a result, the added FB is not wired while the online changedownload is in progress. The subsystem communication I/O FB temporarily assumes the fol-lowing status 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 isFALSE.

The subsystem communication module will restart after the online change download is com-pleted. Once the subsystem communication module has been restarted, unlock the subsys-tem communication data of the module.

l Deleting a subsystem communication I/O FBWhen deleting a subsystem communication I/O FB, also delete the wiring of the FB.



l Changing a wiringBefore performing an online change download, the subsystem communication data of the tar-get subsystem communication module needs to be locked. To change the wiring of a subsys-tem communication I/O FB between two subsystem communication modules, subsystemcommunication data needs to be locked for the subsystem communication module that con-tains the wired communication data before the change, as well as the subsystem communica-tion module that will contain the wired communication data after the change. If the data ofboth modules is not locked, subsystem communication data will be immediately input to theapplication logic after the online change download is completed, and outputs from the applica-tion logic will also be output to subsystems immediately after the download.Each subsystem communication module will restart after the online change download is com-pleted. Once the subsystem communication module has been restarted, unlock the subsys-tem communication data of the module.

n Changes relating to POUsTo change a POU containing a subsystem communication output FB, the communication out-put data of the subsystem communication module wired to the applicable subsystem commu-nication output FB needs to be locked.



B2. Subsystem communicationmodules

This section describes the subsystem communication modules used for connecting subsys-tems. Subsystem communication modules are classified into the following two types:• ALR111 RS-232C serial communication module

• ALR121 RS-422/RS-485 serial communication module

<B2. Subsystem communication modules > B2-1


B2.1 Communication specificationsThis section describes the communication specifications for the ALR111 RS-232C serial com-munication module and ALR121 RS-422/RS-485 serial communication module.

n ALR111 RS-232C serial communication moduleThis section describes the LED indications, connector pin layout and cable connection of theALR111 RS-232C serial communication module.

l LED indications in the ALR111 RS-232C serial communication module

Table B2.1-1 ALR111 LED indicationsLED 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 for the ALR111 RS-232C serial communicationmodule

Table B2.1-2 RS-232C D-sub 9-pin connector specificationPin No. Signal Name Processing on ALR111 side

1 CD Carrier DetectSend data if the CD is OFF (only whenCD check is performed).Receive data if the CD is ON.

2 RD Receive Data

3 SD Send Data

4 ER Data Terminal Ready Output "ON" if normal.

5 SG Signal Ground

6 DR Data Set Ready Send data if the DR is ON(only when DR check is performed).

7 RS Request to Send

This signal is always ON if RS controlis not performed.If RS control is performed, the ALR111outputs "ON" when sending data.

8 CS Clear to Send Send data if the CS is ON.

9 - Not used

n ALR121 RS-422/RS-485 serial communication moduleThe following describes the LED indications, connector pin layout and cable connection forthe ALR121 RS-422/RS-485 serial communication module.

<B2.1 Communication specifications > B2-2


l LED indications in the ALR121 RS-422/RS-485 serial communicationmodule

Table B2.1-3 ALR121 LED indicationsLED 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 communicationmodule

Table B2.1-4 ALR121 connector specificationsTerminal 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

n Cables provided by Yokogawa Electric CorporationYokogawa Electric Corporation provides the following four types of cables for connecting a se-rial communication module to a subsystem.

l RS-232C modem cablesThese 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 cablesThese 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 connec-tion)

• 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 con-nection)



l RS-232C cableThis cable is used to connect an ALR111 with a subsystem.• RS-232C cable (for ALR111 to FA500 connection)

l RS-422/RS-485 cableThis cable is used to connect an ALR121 with a subsystem.• AKB164: RS-422/RS-485 cable (for ALR121 to FA-M3 connection)



B3. Modbus communication (ALR111,ALR121)

This section explains Modbus communication. The Modbus communication function enablessubsystem communication between an SCS and a Modbus PLC, such as the reading andwriting of subsystem data, by connecting the Modbus PLC to an ALR111 RS-232C serial com-munication module or an ALR121 RS-422/RS-485 serial communication module.

n Overview of Modbus connectionThe subsystem communication function implements communication with PLCs and other sub-systems via a subsystem communication module. The Modbus communication program isdownloaded to the subsystem communication modules and runs on them.Reading of data from subsystems or writing of data to subsystems is performed by the appli-cation logic execution function via the communication I/O data area and subsystem communi-cation I/O FBs.The following figure illustrates the flow of data in subsystem communication.

Application logic execution function

Communication I/O data area/subsystem

communication I/O FBs

SCS

Communication module

(ALR111/ALR121)

Modbus PLC

Figure B3-1 Data flow of subsystem communication function

TIP If you install in the SCS a communication module to which the CENTUM FCS Modbus communication pro-gram was downloaded, the module does not function. You need to perform an IOM download to download theModbus communication program for SCS to the module.

<B3. Modbus communication (ALR111, ALR121) > B3-1


B3.1 Communication specificationsThis section describes the specifications for communication between an SCS and a ModbusPLC.

n Communication capacityThe following table summarizes the Modbus-specific communication capacity applicable tocommunication between a Modbus PLC and an SCS.

Table B3.1-1 Capacity of communication between SCS and Modbus PLCItem Maximum capacity Remark

Amount of data that can becommunicated per serial com-munication module

1000 words(1 word = 16 bits)

Limitations of the SCS:Communication I/O data area: 1,000 words perSCSNumber of communication data items: 500 da-ta items per SCS

Number of subsystem stationsthat can be communicatedwith

30 stations per port

If is recommended that the number of stationsbe limited to a maximum of four or so, in orderto minimize the impact on communications withother normal stations when an error occurs in acommunication with a given station.

Size of communication dataper communication definition 125 words

One communication definition corresponds toone communication. This limitation applies toone communication using the Modbus protocol.

Number of usable ports 2 Communications are performed independently(in parallel) using two ports.

n Simultaneity of communication dataModbus PLCs assure simultaneity of communication data in units of 16 bits. Accordingly, si-multaneity of communication data between a serial communication module and a ModbusPLC 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 softwareused on the Modbus PLC side. To assure simultaneity of communication data in units of 32 bits, the applica-tion software on the Modbus PLC side needs to set 32-bit data within the same control period.

n Transmission specificationThe transmission specifications for subsystem communication with a Modbus PLC are as fol-lows:

Table B3.1-2 Transmission specificationItem Description(*1) Remark

InterfaceRS-232C (D-sub, 9-pin) ALR111

RS-422/RS-485 (2-wire, [4-wire]) ALR121(*2)

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




Table B3.1-2 Transmission specification (Table continued)Item Description(*1) Remark

Data type

Start bit Fixed to 1

Data bit 8

Parity bit None, [Even], Odd

Stop bit 1

Control line

RS control Yes, [No] Valid only for ALR111

DR check [Yes], No Valid only for ALR111

CD check Yes, [No] Valid only for ALR111

Time monitoring

Transmission enable moni-toring time 1000 ms

Reception inter-charactertimer 0 to 99999 ms [10 ms] (*2)

Inter-character monitortimeout Errors are latched. (*2)

Text frameReception start character None

EOT 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 5Specification of recov-ery communicationmethod

Option 2 0 to 1 (*3)

Option 3 0

Option 4 0

*1: The recommended settings are shown in [ ].*2: 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 (corre-sponding to the time required for sending 10 characters) at 9600 bps.

*3: Wind-up specification without readback.0: Valid1: Invalid

IMPORTANTWhen performing subsystem communication with a Modbus PLC, always specify 8 for the da-ta bit length. In addition, always specify 1 for the stop bit length. If any other value is specified,a communication error will occur.

n Communication error codeModbus PLC-specific error codes resulting from address and communication errors are as fol-lows:



Table B3.1-3 Communication error code - ModbusError code (hexa-

decimal) Description Remarks

A3B0 No response

A3B1 Inappropriate station number (When the station number is otherthan 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 (*2)

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)









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)

A3E0 Error code $10 received (*2)










Table B3.1-3 Communication error code - Modbus (Table continued)Error code (hexa-

decimal) Description Remarks



*1: Definition error for ALR111/ALR121. If this error occurs, no communication can be performed to the Modbus PLC.*2: This is an error when an error message was received from the Modbus PLC.



B3.2 Connection of serial communicationmodule and Modbus PLC

This section describes how to connect a serial communication module with a Modbus PLCusing a cable.

n Connecting an ALR111 RS-232C serial communication module witha Modbus PLC

The ALR111 uses a RS-232C D-sub, 9-pin connector, but the computer link unit of the con-nected Modbus PLC may be equipped with a RS-232C D-sub, 25-pin connector or a 9-pinconnector. 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 ALR111and Modbus PLC are sharing the same grounding system, the two can be connected directlyusing a RS-232C cable of a length not exceeding 15 m.

IMPORTANTThe length of the RC-232C cable connecting the ALR111 to the modem, and one connectingthe modem to the Modbus PLC, shall not exceed 15 m.

l Modem connectionThe following figure shows a cable connection when an ALR111 and a Modbus PLC are con-nected via a modem.

Modem

Protective grounding systemShielded cable

ALR111

2 SD

3 RD

4 RS

5 CS

6 DR

20 ER

1 FG

7 SG

8 CD

SD 3

RD 2

RS 7

CS 8

DR 6

ER 4 SG 5

CD 1

Figure B3.2-1 Cable connection of ALR111 and Modbus PLC via modem (RS-232C D-sub, 25-pin)

l Connecting a RS-232C D-sub, 25-pin connector to a Modbus PLC (directconnection)

The following example shows a cable connection where an ALR111 is connected directly to aModbus PLC equipped with an RS-232C D-sub 25-pin connector. In this connection, a cablewith an RS-232C D-sub, 25-pin connector needs to be used.

<B3.2 Connection of serial communication module and Modbus PLC > B3-6


Modbus PLC


ALR111

2 SD

3 RD

4 RS

5 CS

6 DR

20 ER

1 FG

7 SG

8 CD

SD 3

RD 2

RS 7

CS 8

DR 6

ER 4 SG 5

CD 1

Figure B3.2-2 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 (directconnection)

The following example shows a cable connection where an ALR111 is connected directly to aModbus PLC equipped with an RS-232C D-sub 9-pin connector. In this connection, a cablewith an RS-232C D-sub, 9-pin connector needs to be used.

Modbus PLC


ALR111

3 SD

2 RD

7 RS

8 CS

6 DR

4 ER

Connected to connector shell

5 SG

1 CD

SD 3

RD 2

RS 7

CS 8

DR 6

ER 4 SG 5

CD 1

Figure B3.2-3 Direct cable connection of ALR111 and Modbus PLC (RS-232C D-sub, 9-pin)

SEEALSO For more information about connecting the ALR111 (RS-232C) to each Modbus PLC model, refer to:

Modbus PLC user manuals

n Connecting an ALR121 RS-422/RS-485 serial communicationmodule with a Modbus PLC

The specific connection varies depending on the Modbus PLC model.

SEEALSO For more information about connecting the ALR121 (RS-422/RS-485) to each Modbus PLC model, refer to:


<B3.2 Connection of serial communication module and Modbus PLC > B3-7


B3.3 Modbus PLC devices accessible fromSCSs

This section describes the Modbus PLC devices that can be accessed from SCSs.Internal data of a Modbus PLC are called devices. Devices can be bit devices or word devi-ces, as described in the following explanation.• Bit devices

Data in which each bit has a meaning. An input relay is a bit device.

• Word devicesData in which each word (1 word = 16 bits) has a meaning. A holding register is a worddevice.

Modbus PLCs also have devices called "special coil" and "communication status."

n Accessible devicesTo access Modbus PLC devices, set [Device Address] and [Size] in the Communication I/OBuilder.With Modbus PLCs, "Device Address" is set using the following format:

<Function code> + <Device type> + <Address within device>

To specify input relays 100012 to 100015 in the Communication I/O Builder, for example, setA100012 in "Device Address" and 1 in "Size." "A" of A100012 indicates a function code, "1"indicates a device type, and "00012" indicates an address within device.The table below lists the Modbus PLC devices accessible from SCSs, as well as the corre-sponding addresses and Modbus protocol function codes.

Table B3.3-1 Bit devices

Device

Address Modbus protocol function code(hexadecimal)

Functioncode

Modbus PLC de-vice type

Address in theModbus PLC de-

viceRead Write

Coil

A

0 XXXX

010F

B 05

X-

0F

Y 05

Input relay A 1 XXXX 02 -

Link relay:(*1)

A

D XXXX

121D

B 19

X-

1D

Y 19

Step status:(*1) A S XXXX 17 -

*1: These are Memocon-SC GL60S devices and not available on other models.

<B3.3 Modbus PLC devices accessible from SCSs > B3-8


Table B3.3-2 Word devices

Device


Functioncode



viceRead Write

Input register A 3 XXXX 04 -

Holding register

A

4 XXXX

03

10

B 06

C 10

X

-

10

Y 06

Z 10

Constant register:(*1)

A

C XXXX

13

1E

B 1A

C 1E

X

-

1E

Y 1A

Z 1E

Elapsed steptime:(*1) A 5 XXXX 14 -

Link register:(*1)

A

R XXXX

15

1F

B 1B

C 1F

X

-

1F

Y 1B

Z 1F

Extended register:(*1)

A

A XXXX

16

20

B 1C

C 20

X

-

20

Y 1C

Z 20

4-byte register A W XXXX 04 -

*1: These are Memocon-SC GL60S devices and not available on other models.

Table B3.3-3 Other devices

Device


Functioncode



viceRead Write

Special coil SP001 07 -

Communicationstatus STSXXX - -

The meaning of each function code is as follows:



• ARead 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 read-back.

• BRead data for the size specified at Size field in the Communication I/O Builder.Write data individually to each modified device in units of 1 bit for a bit device, or in unitsof 16 bits for a word device. With readback.

• CRead data for the size specified at Size field in the Communication I/O Builder.Write data individually to each modified device in units of 32 bits. With readback.

• XWrite data for the size specified at Size field in the Communication I/O Builder when achange occurs. Without readback.

• YWrite data individually only to each modified device for the size of each device when achange occurs. Without readback.

• ZWrite data individually only to each modified device in units of 32 bits when a change oc-curs. Without readback.

Table B3.3-4 List of function codesFunction code Device Read Write Readback

A

Bit deviceAll data for onecommunication defi-nition

All data for onecommunication defi-nition

Yes

Word deviceAll data for onecommunication defi-nition


Yes

B

Bit deviceAll data for onecommunication defi-nition

In units of 1 bit Yes

Word deviceAll data for onecommunication defi-nition

In units of 16 bits Yes

C Word deviceAll data for onecommunication defi-nition


X

Bit device -All data for onecommunication defi-nition

No

Word device -All data for onecommunication defi-nition

No

YBit device - In units of 1 bit No

Word device - In units of 16 bits No

Z Word device - In units of 32 bits No



IMPORTANTWith a dual-redundant configuration based on ALR111/ALR121s, it is always necessary toperform readback when data is written to the Modbus PLC. Writing of data without readbackis not supported in a dual-redundant configuration.

Supported function codes, accessible devices, and sizes vary depending on the Modbus PLCmodel.

SEEALSO For more information about supported function codes, accessible devices, sizes, and so on , refer to:

The user manual for your Modbus PLC

For more information about readback communication, refer to:




B3.4 Storage formats of subsystem dataThis section describes the formats in which Modbus PLC data that has been read is stored inthe 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 devicesWhen 16 x m (m = 1, 2, ...) numbers of bit devices are read from address n in the ModbusPLC, the Modbus PLC data is stored in the SCS as follows:In the Communication I/O Builder, specify "m" in "Size". You can also reverse the order of bitsin units of 16 bits.

n + 15

n + 14

n + 13

n + 12

n + 11

n + 10

n + 9

n + 8

n + 7

n + 6

n + 5

n + 4

n + 3

n + 2

n + 1

n

n + 31

n + 16

n+16×(m-1)+15

16 bits

n+16×(m-1)

m=1

m=2

Figure B3.4-1 Storage image of bit devices

n Word devices

l 16-bit dataIf 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

Figure B3.4-2 Storage image of word devices

l 32-bit dataWord registers (16 bits) in the Modbus PLC are stored in the SCS in the order of registers, asshown in the following. However, if 32-bit data is defined as the data type, two word registersare combined and treated as 32-bit data.

<B3.4 Storage formats of subsystem data > B3-12


If word reversing is not specified in the SCS (default), the first register is recognized as theupper word, while the next register is regarded as the lower word.

16 bits


Content of register n+1

Upper word of 32-bit data

Lower word of 32-bit data


Figure B3.4-3 Order of 32-bit data in SCS (without word reversing)

If 32-bit data is stored in word registers in the Modbus PLC, some Modbus PLC models maystore the data in pairs of two 16-bit word registers in the order of low-order word and high-order word, as follows: This word order (16 bits) is opposite to the order in the SCS.

16 bits


Content of register n+1 Upper word of 32-bit data

Lower word of 32-bit data


Figure B3.4-4 Order of 32-bit data in Modbus PLC (opposite order from SCS)

If the previously mentioned Modbus PLC data is to be stored in the SCS, the data order canbe switched to units of words (16 bits) by specifying "Reverse" in the Communication I/OBuilder.

n Special coilsSpecial coils in Modbus PLCs have a data length of 1 word (16 bits). Special coils are storedin the SCS as follows.By specifying "Reverse" in the Communication I/O Builder, you can reverse the order of bits.

n + 1

n

n + 7

0

15 7 0

The status of special coil is stored. The value of n varies depending onthe model of the Modbus PLC to be connected.

n + 1

n

n + 7

0

15 8 0

(a) When bit reversing is not specified (b) When bit reversing is specified

Figure B3.4-5 Storage image of special coil data



n Communication statusModbus PLC communication status STSnnn indicates the status of communication with eachstation 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 areindicated as "1."

• Stations not physically performing communication (not defined in the Communication I/OBuilder) are indicated as "0".

With communication status, the station number specification in the Communication I/O Builderhas no specific meaning. It is only relevant in that the number corresponding to the youngeststation among the stations physically performing communication should be set. Specify theaddress as follows:

Table B3.4-1 Communication statusDescription 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 as follows:

Structure of STS001 15 Bit order

Stn. No. 01

Stn. No. 02

Stn. No. 03

Stn. No. 04

Stn. No. 05

Stn. No. 06

Stn. No. 07

Stn. No. 08

Stn. No. 09

Stn. No. 10

Stn. No. 11

Stn. No. 12

Stn. No. 13

Stn. No. 14

Stn. No. 15

Stn. No. 16

Structure of STS017

00

15

Stn. No. 17

Stn. No. 18

Stn. No. 19

Stn. No. 20

Stn. No. 21

Stn. No. 22

Stn. No. 23

Stn. No. 24

Stn. No. 25

Stn. No. 26

Stn. No. 27

Stn. No. 28

Stn. No. 29

Stn. No. 30

Stn. No. 31

Stn. No. 32

00 Bit order

Figure B3.4-6 Correspondence of communication status bits and station numbers



B3.5 Builder setting items specific to ModbusPLCs

This section describes the builder setting items specific to Modbus PLCs.

<B3.5 Builder setting items specific to Modbus PLCs > B3-15


B3.5.1 Settings in the I/O Wiring ViewThe following items are set in the I/O Wiring View:

n Subsystem communication module definitionIf an ALR111/ALR121 is used for subsystem communication, select ALR111M/ALR121M asthe module type. Specify the mounting position (node, slot number) of the module, as well aswhether or not to use a dual-redundant configuration.

n Dual redundancy of serial communication modulesTo use serial communication modules in a dual-redundant configuration, set "IsRedundant" to"TRUE."



B3.5.2 Items set in the I/O Parameter BuilderThe following items are set in the I/O Parameter Builder for the ALR111M/ALR121M:

n Connection DeviceFor the name of the connected device, select [S_MODBUS].

n Transmission SpecificationsSet the transmission specifications for each port.

SEEALSO For more information about settings information, refer to:

“n Transmission specification” on page B3-2

n Options 1 and 2In Option 1, specify the method of recovery communication. In Option 2, specify the wind-upaction for communication without readback.

SEEALSO For more information about procedure for specifying recovery communication operations in Option 1, refer to:

B3.7, “Recovery communication” on page B3-26

For more information about procedure for specifying wind-up operations in Option 2, refer to:

“n Operation in communication without readback” on page B3-22



B3.5.3 Items set in the Communication I/O BuilderThis section describes the items set in the Communication I/O Builder.This section describes the following items when a Modbus PLC is used.• Element

• Buffer

• Program Name

• Size

• Port

• Station

• Device Address

• Data Type

• Reverse

• Input Processing at Fault

• Input Value at Fault

n ElementElement numbers are displayed to specify the buffer addresses in the communication I/O dataarea. The "Element" field is read only and cannot be set.

n BufferSpecify the size of the storage area to be used by the Modbus communication program.The "Buffer" is a required setting item in the Communication I/O Builder and always needs tobe set.

n Program nameSet the program name using the node number, slot number and S_MODBUS, as follows:Program Name : n-s Fixed character string

• n: Node number

• s: Slot number

• Fixed character string: S_MODBUS

n SizeSet 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 beset.Specify the size in units of words (16 bits). The setting range is 1 to 125 words.

n PortSet the port of the ALR111/ALR121 to be used.Port 1 or 2 can be set.



n StationSet the station number for the Modbus PLC.The setting range is 1 to 255.

n Device addressSet the content of data to be acquired from the other device as a combination of the commu-nication method used by the Modbus PLC and the beginning address of the data.The address can be set using 3 to 7 alphanumeric characters as follows:

• Coil:

• Input relay:

• Link relay:

• Step status:

• Input register:

• Holding register:

• Constant register:

• Elapsed step time:

• Link register:

• Extended register:

• 4-byte register:

• Special coil:

• Communication status:

A0xxxx, B0xxxx, X0xxxx, Y0xxxxA1xxxxADxxxx, BDxxxx, XDxxxx, YDxxxxASxxxxA3xxxxA4xxxx, B4xxxx, C4xxxx, X4xxxx, Y4xxxx, Z4xxxxACxxxx, BCxxxx, CCxxxx, XCxxxx, YCxxxx, ZCxxxxA5xxxxARxxxx, BRxxxx, CRxxxx, XRxxxx, YRxxxx, ZRxxxxAAxxxx, BAxxxx, CAxxxx, XAxxxx, YAxxxx, ZAxxxxAWxxxxSP001STSxxx

The "Device Address" field is blank by default."xxxx" indicates an address within Modbus PLC device, and is set as a decimal or hexadeci-mal value between 1 and 65535 (1H and FFFFH). If a hexadecimal value is used, add "H" atthe 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.

SEEALSO For more information about specifying addresses , refer to:

B3.3, “Modbus PLC devices accessible from SCSs” on page B3-8

l Limitations on dual-redundant serial communication modulesIf 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 ina dual-redundant configuration. Dual redundancy is not supported if readback is not used. Toprovide a dual-redundant configuration using two serial communication modules, specify onlyfunction 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 willoccur:

• Outputs that occurred while switching the dual-redundant modules may not be output, or the same out-puts may be output again after switching.With readback, data is read from the subsystem, compared with the data in the CPU, and then the CPUdata 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 onthe control side, without reading data from the subsystem, after which the CPU data is written to the sub-system and the data in the module is refreshed only when there is a difference between the data. If theserial communication module on the control side is normal, the data in the serial communication moduleon the standby side is not refreshed. This means that the serial communication module on the standbyside will still contain old data when the control switches from the module on the control side to the mod-ule on the standby side. Since the module in this condition cannot accurately compare the data in theCPU 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 codespecified in the Communication I/O Builder.

• If an address without readback is specified, the control will not be switched to the applicable serial com-munication module in the dual-redundant configuration for 70 seconds after recovery of the module froman error.If the serial communication module on the standby side is reset following a restart, the serial communi-cation status will not be considered normal for 70 seconds. If a serial communication error occurs duringthis period in the serial communication module on the control side, the control will not switch to the mod-ule on the control side.

SEEALSO For more information about readback, refer to:


n Data typeSet the type of subsystem data.If 32-bit data is used, simultaneity of communication data needs to be considered.

n ReverseSet whether or not to reverse the order of bits/words in the SCS from the order of bits/wordsin the subsystem.

SEEALSO For more information about storing subsystem data on an SCS, refer to:

B3.4, “Storage formats of subsystem data” on page B3-12

n Input processing at faultSpecify 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 faultSpecify the input value to be used, instead of the process value, when "Fixed Value" is speci-fied in "Input Processing at Fault."



B3.6 Readback communicationIn subsystem communication, output data from subsystems are always read (read back) evenwhen their data type is output, and each read-back data is compared with the data to be writ-ten. If a difference is found as a result of comparison, the data will be written. This method isindicated by the phrase "with readback." Readback forms the basis of subsystem communica-tion.On the other hand, there is another method of subsystem communication in which subsystemoutputs are not read back and data is written only when the previously written data is differentfrom the data to be written. This method is indicated by the phrase "without readback." Thismethod is used to support one-shot outputs from Modbus PLCs.

n Operation in communication with readbackValues output from subsystems are read at the subsystem communication period. The read-back data is compared with the data to be written. If there are no differences, write communi-cation is not sent ((1) and (3) in the following figure).If an output value is changed in the CPU and a difference occurs between the read-back dataand the data to be written, communication is established with the applicable subsystem towrite the new data ((2) in the following figure).If an output value in a subsystem is changed while communication is normal, a difference oc-curs between the read-back data and the data to be written, in which case communication isestablished with the subsystem to write the new data ((4) in the following figure).

The output value is changed.


period

Output data (Physical data value output from subsystem communication/output value of the serial communication module)

Read values from the subsystem. If different from the value to be written, the new data is written.

Output value on subsystem side

(1) (2) (3) (4) (5)

The output value is changed on the subsystem side.

Figure B3.6-1 Output communication with readback

In a dual-redundant configuration, the serial communication module on the standby sidereads back output values to confirm integrity of communication paths and prevent omission ofoutputs when the control right is switched.In the following conditions, if read-back is enabled, values from subsystems are output fromthe 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 online change, the outputs statuses onthe subsystem side can be retained even after restarting the communication module.

<B3.6 Readback communication > B3-21


l Recovery from a serial communication module errorIf the serial communication module has recovered from an error in a communication withreadback, the output values on the subsystem side are tracked. The following figure illustratesthe operations when communication output is locked.If the serial communication module has generated an error, data from subsystems cannot beread back. Thus, the SCS retains the previous output values and does not output data ((1)and (2) in the following figure).Once the serial communication module recovers and communication is enabled for the firsttime, data from subsystems are read back and subsystem output values are tracked ((3) inthe following figure).Following this, if an output value on the SCS side is changed, a difference occurs between thereadback data and the data to be written. In this case, communication is established with theapplicable subsystem to write the new data ((5) in the following figure).

(1) (2) (3) (4) (5)




First successful readback after recovery from the serial communication module error. → The value on the subsystem side is tracked.

Readback fails.

Figure B3.6-2 Operation in communication with readback after recovery from serial communicationmodule error

n Operation in communication without readbackCommunication 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 ascommands 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 ac-cepts the command and resets the corresponding output value (OFF → ON → OFF). At thistime if readback is enabled, the output value will be read back from the Modbus PLC, in whichcase the Modbus PLC's value will be compared with the value to be written. If a difference isdetected, communication will be established to write the new data again. If it is necessary toperform one-shot 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 subsys-tem communication period, and does not perform communication to write data if the previousoutput values have not changed ((1), (3), (4) and (5) in the following figure).Data is written only when a change is detected in any output value on the CPU side ((2) in thefollowing figure ).Since readback communication is not performed, communication to write data is not per-formed, even after an output value has been changed on the Modbus PLC side ((4) in the fol-lowing figure).





Output value on Modbus PLC side


period

The output value is changed on the Modbus PLC side.

The output value is checked at the subsystem communication period. Data is written if a change in the output value is detected.

(1) (2) (3) (4) (5)

Communication to write data is not performed.

Figure B3.6-3 Output communication without readback

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 anoutput value has been changed on the master side. Thus, the wind-up function disables allchanges to output values for 70 seconds following a reset of the serial communication mod-ule, in order to prevent unnecessary write accesses after the reset. Enable/disable this func-tion 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 writtento the Modbus PLC for 70 seconds following the reset. Changes to output values will bewritten to the Modbus PLC only after elapse of 70 seconds following the reset.

• When Option 2 is set to 1The wind-up function is disabled. (Wind-up disable)

SEEALSO For more information about function codes specified in [Device Address], refer to:

B3.3, “Modbus PLC devices accessible from SCSs” on page B3-8

l Recovery from a serial communication module error (wind-up functionenabled)

After the serial communication module recovers from an error, output values will be initializedat 0 ((1) in the following figure).In the I/O Parameter Builder, if 0 is set in "Option 2" in the Port tab, changes to output valueswill not be written to the Modbus PLC for 70 seconds following the recovery ((3) in the follow-ing figure). Thus, discrepancies will occur between the output values on the SCS side andthose on the subsystem side immediately after the reset of the serial communication module,until the output values are changed on the subsystem side.



The output value is changed. Output data

(Physical data value output from subsystem communication/output value of the serial communication module)



period (1) (2) (3) (4) (5)

The change in output value is output after

elapse of 70 seconds.

Recovery from the IOM error The default is 0. 70 seconds (No output)

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.

Figure B3.6-4 Operation in communication without readback after recovery from serial communica-tion module error

With readback, output values are read back, so the differences between read-back valuesand values to be written are detected and the new data are written even when the output val-ues have not been written to subsystems. Without readback, however, data will not be writtenunless output values on the SCS side are changed. For this reason, the statuses of outputvalues on the SCS side may remain different from those on the Modbus PLC side after outputvalues have been changed on the Modbus PLC or the serial communication module has beenreset.

l Error handling actions in communication without readbackThe error handling actions in communication without readback are as follows:• Initial cold start of the CPU (Output disabled)

When output is disabled, the defaults of physical communication output data are 0. Out-put is not performed until any output value is changed on the CPU side. Once output isenabled, output will be performed when any output value is changed to a value other than0 on the CPU side. The output timing varies depending on the setting of the wind-up func-tion.

• Occurrence of a serial communication module error while subsystem communication datais lockedWhen an error of serial communication module occurs or online change that may resetthe serial communication module is performed, if any output value is changed to a valueother than 0, output acts just like after an initial cold start of the CPU. The output timingvaries depending on the setting of the wind-up function.

l Status in communication without readbackWithout readback, whether the status of communication data becomes BAD upon a serialcommunication error is determined by the following conditions:• Whether there is any data to read from the station to communicate with

• The recovery communication specification that is set as "Option 1" on the Port tab of theI/O Parameter Builder



Table B3.6-1 When communication data that defined without readback becomes BAD upon serialcommunication error

Option 1 setting(*1)If there is no readback for all

the communication defini-tions for one station

If at least one communication defi-nition for the station has readback

0Perform recovery communica-tion using a 08 command (loop-back check command)

The status will change to BADif a communication error occursduring a communication towrite data. (If "Option 1" is setto 2, the status will automatical-ly return to normal when recov-ery communication is per-formed.)

The status will change to BAD if acommunication error occurs duringa communication to write data.The status will also change to BADif a communication error occurs inwhich abnormal line communicationis recognized (no response, lineNRDY, etc.) during a communicationbased on a definition with readback(input definition, or output definitionwith readback).

1 Perform recovery communica-tion using a READ command

2Reset the error condition whenrecovery communication is per-formed

3Perform recovery communica-tion using a WRITE commandof 0 write size

4

Perform recovery communica-tion using a WRITE commandbased on the data written im-mediately before the error

5Do not recognize an error norperform recovery communica-tion

Always normal

*1: Applicable only to the recovery communication methods without readback. With readback, recovery communication is per-formed using a READ command.

TIP In addition to the previously listed 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 com-munication module

• Occurrence of a range error of station number setting, range error of address setting or other definitionerror

• With readback, if a serial communication error occurs, the status of communication data becomes BADat readback that is performed at every subsystem communication period.



B3.7 Recovery communicationIf no response is received or a CRC-16 code error occurs during communication with a Mod-bus PLC, communication with the applicable station is temporarily suspended. Thereafter,communication is performed at the interval of connection retries set in the I/O ParameterBuilder to check if the Modbus PLC that generated an error has recovered to normal state.This communication is called "recovery communication."This section explains recovery communication.

n Types and details of recovery communicationThe recovery communication method is determined by the Option settings, which are set inthe Port 1 and Port 2 tabs of the I/O Parameter Builder.

l Option 1 (Recovery communication specification)Recovery communication can be performed using the following five methods:• When Option 1 is set to 0

With readback, recovery communication is performed using a READ command.Without readback, recovery communication is performed using a 08 command. The 08command is a loopback check command used to check presence of the subsystem.

• When Option 1 is set to 1Recovery communication is performed using a READ command regardless of the read-back setting.

• When Option 1 is set to 2With readback, recovery communication is performed using a READ command.Without readback, the error condition will be reset when recovery communication is per-formed. If the same station generates an error again during recovery communication, asystem alarm will generate every time recovery communication is performed.

• When Option 1 is set to 3With readback, recovery communication is performed using a READ command.Without readback, recovery communication is performed using a WRITE command of 0write size.

• When Option 1 is set to 4With readback, recovery communication is performed using a READ command.Without readback, recovery communication is performed using a WRITE command basedon the data written immediately before the error.

• When Option 1 is set to 5With readback, recovery communication is performed using a READ command.Without readback, any station that generated an error is not recognized as an error sta-tion. When Option 1 is set to 5, communication with the non-responding Modbus PLC willstop for the period corresponding to "No response time x (1 + Number of retries)" aftereach interval of connection retries set in the communication module definition.

<B3.7 Recovery communication > B3-26


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 mayoccur if the data written immediately before the error contained an operation command tothe Modbus PLC.

• On some Modbus PLC models, reading with a READ command may reset the flag. If youdon't want to cause the discrepancy, specify a function code without readback in "DeviceAddress" of the communication definitions on Communication I/O Builder.

The 08 command cannot be used for some types of Modbus PLC models.

SEEALSO For more information about Modbus PLC, refer to:


<B3.7 Recovery communication > B3-27


B3.8 Communication textThis section describes the communication text used in the Modbus protocol.The communication text contains frames for each command in the Modbus protocol and a re-sponse to the command. The structures of communication text frames are as follows:

01 Command

Response

s

s

02 Command

Response

s

s

04 Command

Response

s

s

05 Command

Response

s

s

06 Command

Response

s

s

07 Command

Response

s

s

11 Command

Response

s

s

12 Command

Response

s

s

10 Command

Response

s

s

0F Command

Response

s

s

m

m

08 Command

Response

s

s

03 Command

Response

s

s

01

01

02

02

03

03

04

04

05

05

06

06

07

07

08

08

0F

0F

10

10

11

11

12

12

m×2

n-1

n-1 m×16

DATA

DATA

DATA 1

DATA 1 DATA m

DT

m×2

n-1 m×16

m×16

m×16

m×16

DATA 1 DATA m

m×2

m×2

m×2

n-1 m

DATA 1 DATA m

m×2

m×2

n-1 m

DATA 1 DATA m

DATA m

Pattern

n-1 Pattern

n-1

DATA 1 DATA m

DATA m DATA 1

m

n-1

n-1

n-1

n-1

n-1

n-1

n-1

DATA

DATA

code

code

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

s: Station numbern: 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 B3.8-1 Communication text frame structures (1/2)

<B3.8 Communication text > B3-28


14 Command

Response

s

s

15 Command

Response

s

s

17 Command

Response

s

s

19 Command

Response

s

s

1A Command

Response

s

s

1B Command

Response

s

s

1F Command

Response

s

s

20 Command

Response

s

s

1E Command

Response

s

s

1D Command

Response

s

s

1C Command

Response

s

s

16 Command

Response

s

s

14

14

15

15

16

16

17

17

19

19

1A

1A

1B

1B

1C

1C

1D

1D

1E

1E

1F

1F

20

20

m×2

n-1

n-1 m

DATA

DATA

DATA 1

DATA 1 DATA m

13 Command

Response

s

s

13

13 m×2

n-1 m

DATA 1 DATA m

m×2

n-1 m

m×16

m×16

DATA 1 DATA m

m×2

m×2

m×2

n-1 m

DATA 1 DATA m

m×2

m×2

n-1 m×16

DATA 1 DATA m

DATA m

Pattern

n-1 Pattern

n-1

DATA 1 DATA m

n-1

DATA

DATA

n-1

n-1

n-1

n-1

n-1

n-1

m×2 DATA 1 DATA m

DATA 1 DATA m

n-1

n-1

n-1

n-1

DATA

DATA

n-1

n-1

m

m

m

m

m

m

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

CRC

s: Station numbern: 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 B3.8-2 Communication text frame structures (2/2)

<B3.8 Communication text > B3-29


B3.9 Communication time between serialcommunication module and Modbus PLC

This section explains the communication time between a serial communication module and aModbus PLC.

n Communication timeThe communication time between a serial communication module and a Modbus PLC is cal-culated as the total sum of T1 through T7 as follows:

T4

Interpretation/execution of

message, creation ofresponse message

T7

Interpretation ofreceived message,

storage of data

Start of dataacquisition

T1

Creation ofsend message

ALR111/ALR121

Modbus PLC

Modbus PLCmodem

Time

ALR111/ALR121modem

T5 T6T2 T3

Data canbe read

T1: Time for creating a send message: Approx. 10 msT2: Delay time of the ALR111/ALR121 modem: Approx. 5 msT3: Time for transmitting the send message.T4: 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.T5: Delay time of the Modbus PLC modem: Approx. 5 msT6: Time for transmitting the response message.T7: Time for interpreting the response message: Approx. 15 ms

Figure B3.9-1 Timing chart for communication between a serial communication module and a ModbusPLC

TIP Since each port performs communication independently, the sum of times required for all communication defi-nitions set for each port becomes the data refresh time of the port. For example, if definitions 1 and 2 are setfor port 1,the communication period of port 1 is calculated as "(Communication time for definition 1) + (Communicationtime for definition 2)."

l How to calculate communication timeThe transmission time for sending (T3) and receiving (T6) can be calculated by using the fol-lowing formulas:

<B3.9 Communication time between serial communication module and Modbus PLC > B3-30


1000 x Number of characters x Number of bits per one characterBaud rate

(ms)

Number of bits per one character = Number of start bits (1) + Number of data bits (8) + Number of parity bits (1) + Number of stop bits (1)

T3 or T6 =

Start bit: Fixed at 1 bitData bits: Fixed at 8 bits (7 bits cannot be specified)Parity bit: Set 1 if parity is even or odd, set 0 if parity is noneStop bit: Fixed at 1 bitBaud rate: 1200, 2400, 4800, 9600, 19200, 38400 bps

The following table shows the length of each frame that can be transmitted by a Modbus com-pliant device.

Table B3.9-1 Number of characters transmitted

DeviceRead Write

Send Response Send Response

Coil Fixed to 8. 5 + Number of coils/8(*1)

9 + Number of coils/4(*1) Fixed to 8.

Holding register Fixed to 8. 5 + +2 x Number of reg-isters

9 + +2 x Number of reg-isters Fixed to 8.

Input relay Fixed to 8. 5 + Number of relays/8(*1) - -

Input register Fixed to 8. 5 + +2 x Number of reg-isters - -

*1: Fraction below the decimal point is rounded up.

<B3.9 Communication time between serial communication module and Modbus PLC > B3-31


B4. ProSafe-SLS communication (forALR121)

The ProSafe-RS can acquire events of the ProSafe-SLS and data using subsystem communi-cation. Acquired events and data can be handled on the SCS in the same way existing eventsand data are handled. If the ProSafe-RS is integrated with a CENTUM system, the eventsand data of ProSafe-SLS can be comprehensively managed using the HIS.The following list shows functions that are needed for the SCS to acquire events and datafrom the communication module of the ProSafe-SLS by using the communication I/O module(model: ALR121) and how ProSafe-SLS alarms are notified.• Data access

The ProSafe-RS can access the input/output data of ProSafe-SLS using the subsystemcommunication function.

• Event acquisitionThe ProSafe-RS can acquire the events generated by ProSafe-SLS.To integrate events of the ProSafe-SLS with the ProSafe-RS, synchronize the time of theProSafe-SLS with that of the SCS to align the time stamps of these events to events ofthe ProSafe-RS.

• Alarm notificationTo notify the CENTUM HIS of error conditions as alarms when the error conditions aredetected based on diagnostic information of the ProSafe-SLS, it is necessary to performengineering and configure an application on both the ProSafe-SLS side and ProSafe-RSside.

SEEALSO For more information about event notified in the case of a ProSafe-SLS error, refer to:

ProSafe-SLS TI

<B4. ProSafe-SLS communication (for ALR121)> B4-1


B4.1 Operating EnvironmentThe ProSafe-SLS is the only subsystem supported by the ProSafe-SLS communication func-tion. If the ProSafe-SLS and other subsystem are connected to the same communicationpath, proper operation of the ProSafe-SLS communication function cannot be guaranteed. Touse the ProSafe-SLS communication function, check the conditions applicable to connectiondevices, subsystem communication program and other aspects of operating environment ex-plained herein, and then make the necessary preparations.

n Connection devices, type and versionsThe following table shows the connection devices covered by the ProSafe-SLS communica-tion function.

Table B4.1-1 Connection deviceItem Description

Subsystem to be connected ProSafe-SLS

ProSafe-COM interface module Type CO-920-00 for Modbus protocol (RTU mode)(*1)

Firmware revision of communication module (model:CO-920-00)

Version 1.0 or later

DI module to be connected (for time synchronization) DI-511-05

*1: One ProSafe-SLS is connected to one CO-920-00.

n SCS operating environmentThe following table shows the operating environment of the SCS that is needed to use theProSafe-SLS communication function.

Table B4.1-2 SCS operating environmentItem Specification

Station (CPU node) SSC50S/SSC50D, SSC57S/SSC57D, SSC60S/SSC60D

I/O node SNB10D

CPU SCP451, SCP461

SCS system program release number R3.02.20 or later

n SENG operating environmentTo use the ProSafe-SLS communication function, the operating environment of the SENGmust support R3.02.20 or later.

n Available input/output modulesThe following table shows the input/output modules that can be used in connection with theProSafe-SLS communication function.

Table B4.1-3 Input/output modules that can be used in connection with the ProSafe-SLS communica-tion function

Model Type PurposeALR121 Serial communication module (RS-422/RS-485 interface) For Modbus protocol (RTU

mode)


<B4.1 Operating Environment> B4-2


Table B4.1-3 Input/output modules that can be used in connection with the ProSafe-SLS communica-tion function (Table continued)

Model Type PurposeSDV531 Digital output module (8 channels, 24 V DC, module isola-

tion)For time synchronization

SDV531-L Digital output module (8 channels, 24 V DC, module isola-tion, for long distance)

SDV541 Digital output module (16 channels, 24 V DC, module iso-lation)

n Available subsystem communication programUse S_SLSMOD as the subsystem communication program for ProSafe-SLS communicationfunction.S_SLSMOD is applicable only to the ALR121. The S_SLSMOD-compatible hardware revi-sions of the ALR121 conform to the conditions under which S_MODBUS can be applied.

n CENTUM version and software revisionThe following table shows the CENTUM versions and revisions that are needed when theProSafe-RS is integrated with a CENTUM system to monitor ProSafe-SLS events using theHIS.

Table B4.1-4 CENTUMs supporting the ProSafe-SLS communication functionVersion Revision

CENTUM CS 3000 R3.07 or later

CENTUM VP R4.01 or later

n Configuration of communication modulesWhen the subsystem communication program S_SLSMOD is applied for the communicationI/O module (model: ALR121), the ALR121 can be used only in a single configuration.

<B4.1 Operating Environment> B4-3


B4.2 System configurationThe following figure shows an overall system configuration based on the ProSafe-RS andProSafe-SLS connected to it.

CENTUM VP ProSafe-RS

ProSafe-COM

COM-SET

ProSafe-SLS

HIS/ENG

Vnet/IP

SENG

FCS SCS

RS-485

RS-232CDigital signal

CO-920-00Y-net

Field devices

Figure B4.2-1 Example of overall system configuration

The following table explains the terms that are used in the figure.

Table B4.2-1 Description of termsTerm Description

ProSafe-SLS A SIL4-certified safety instrumented system. It can be connected to other system throughthe ProSafe-COM.

ProSafe-COM One component of a safety instrumented system. It provides the communication functionto connect the ProSafe-SLS and other system.

CO-920-00 A communication module and one of ProSafe-COM products. This module is hereinafterreferred to as "CO-920."

COM-SET Software package. This package is used for engineering and maintenance of the CO-920.It also provides the function to display SOE events of the CO-920. SET stands for "Sys-tem Engineering Tool."

Y-net A local network connecting each ProSafe-SLS module and the ProSafe-COM. RS-485serial communication is used.

<B4.2 System configuration> B4-4


B4.2.1 Connection configuration of SCS and ProSafe-SLSThe following figure shows the connection configuration of ProSafe-RS SCS and ProSafe-SLS.

Vnet/IP or Vnet/IP-Upstream

Modbus protocol (RTU mode)

Digi

tal s

igna

l for

tim

e sy

nchr

oniza

tion

COM 2 or COM 3

COM 1COM 1

COM 2 or COM 3

COM-SET

ProSafe-RS

SENG

SCS

DO module ALR121

RS-485

RS-485

RS-232C

Y-netY-net

ProSafe-COM

CO-920 CO-920

ProSafe-SLS

ProSafe-SLS

DigitalInputs Digital

OutputsAnalogInputs

DigitalStorage

DI-511 MC-576MC-562MC-573

Figure B4.2.1-1 Connection configuration of ProSafe-RS SCS and ProSafe-SLS

"Vnet/IP or Vnet/IP-Upstream" in the figure is hereinafter abbreviated as "Vnet/IP."To display the events of the ProSafe-SLS in the SOE viewer as with the event data of theSENG, the time of the ProSafe-SLS must be synchronized with that of the ProSafe-RS. Theevent time stamps given by the ProSafe-SLS are used directly by the ProSafe-RS. Connectthe DO module of the SCS and DI module of the ProSafe-SLS to synchronize the time.



B4.2.2 System overview of ProSafe-SLSThe ProSafe-SLS is a safety system that can be applied to installations requiring the SIL4safety level.The ProSafe-COM is one component of a safety system.The CO-920 is a communication module and one of ProSafe-COM products, which can bedirectly installed on a standard 19" cassette connector for ProSafe-SLS. To connect the Pro-Safe-SLS to the ProSafe-RS, connect the CO-920 to the ProSafe-RS as a communication in-terface with the ProSafe-SLS.For more information about the ProSafe-SLS system, refer to each IM for ProSafe-SLS.

n Communication interface of ProSafe-SLSUse Y-net as a communication interface between the ProSafe-SLS and external devices. Y-net is a local ProSafe-SLS network. Use the CO-920 as an interface between the Modbusand Y-net networks. The external interface of the CO-920 consists of one RS-232C port (portname: COM1) and two RS-485 ports (port names: COM2 and COM3).The CO-920 acquires the events of ProSafe-SLS modules, time-stamps the acquired eventsbased on its internal clock and sorts them chronologically, and then stores the sorted eventsin the event buffer. The resolution of time stamp is 1 ms. Events are stored in the event bufferaccording to the FIFO method.Various engineering tasks on the CO-920 are performed from the application software COM-SET by using RS-232 communication.

n Communication interface of ALR121 and CO-920The COM port of the ALR121 of the SCS is connected to the COM port of the CO-920 by us-ing RS-485 communication, and the two ports communicate with each other according to theModbus protocol (RTU mode).The ALR121 (Modbus master) can access the I/O data of each ProSafe-SLS module that isconnected to the Y-net by using standard Modbus commands. It can also acquire ProSafe-SLS events from the CO-920 by using expansion Modbus commands.You need to download the subsystem communication program S_SLSMOD into the ARL121.S_SLSMOD, which is a ProSafe-SLS communication program, can be used only by theALR121.

n Setting the ProSafe-SLS time using an external clockThe ProSafe-SLS time can be set by using an external clock. When a change event involvinga DI module associated with ProSafe-SLS time synchronization occurs, the CO-920 time isset to a fixed time.



B4.3 Data accessThe ProSafe-RS can access input/output data of ProSafe-SLS by using the subsystem com-munication function. The Modbus protocol (RTU mode) is used for the communication proto-col.If the ProSafe-RS is integrated with a CENTUM system, the accessed data can be monitoredusing the HIS.

n Handling of ProSafe-SLS communication dataThe data that is collected by the ProSafe-RS by accessing the ProSafe-SLS can be handledby the communication input FBs and communication output FBs.The subsystem communication FBs that can be used in connection with the ProSafe-SLScommunication function are interference-free function blocks and cannot be used for input ofsafety loops.A POU containing any subsystem communication FB that can be used under the ProSafe-SLS communication function must be approved by using the Integrity analyzer.The following subsystem communication input FBs can be used in connection with the Pro-Safe-SLS communication function.• SCI_B

• SCI_I

The following subsystem communication output FBs can be used in connection with the Pro-Safe-SLS communication function.• SCO_B

• SCO_I

SEEALSO For more information about SCI_B, refer to:

C8.1, “SCI_B (BOOL-type subsystem communication input)” in Safety Control Station Reference (IM32Q03B10-31E)

For more information about SCI_I , refer to:

C8.2, “SCI_I (INTEGER-type subsystem communication input)” in Safety Control Station Reference (IM32Q03B10-31E)

For more information about SCO_B, refer to:

C8.4, “SCO_B (BOOL-type subsystem communication output)” in Safety Control Station Reference (IM32Q03B10-31E)

For more information about SCO_I, refer to:

C8.5, “SCO_I (INTEGER-type subsystem communication output)” in Safety Control Station Reference(IM 32Q03B10-31E)

n Connection interface of ProSafe-RS and ProSafe-SLSConnect the ALR121 and CO-920 as a communication path for I/O data, events and ProSafe-SLS diagnostic information. Connect the two using 2-wire type or 4-wire type connection ofRS-485 to a 1:n multi-drop configuration.The following figure shows the 4-wire type connection of RS-485.

<B4.3 Data access> B4-7


ALR121

TX-A

TX-B

RX-A

RX-B

GND

TX-A

TX-B

RX-A

RX-B

GND

TX-

TX-

RX+

RX-

SG

R1

TX-A

TX-B

RX-A

RX-B

GND

R2

R2

CO-920CO-920 CO-920

R1: Termination resistance of 120 ohmR2: Termination resistance built in CO-920

Figure B4.3-1 1:n connection in 4-wire type of RS-485

The following figure shows the 2-wire type connection of RS-485.

ALR121

TX-A

TX-B

RX-A

RX-B

GND

TX-A

TX-B

RX-A

RX-B

GND

TX+

TX-

RX+

RX-

SG

R1

TX-A

TX-B

RX-A

RX-B

GND

R2

CO-920CO-920 CO-920

R1: Termination resistance of 120 ohmR2: Termination resistance built in CO-920

Figure B4.3-2 1:n connection in 2-wire type of RS-485

SEEALSO For more information about connection method on the CO-920 side, refer to:

CO-920 instructions

<B4.3 Data access> B4-8


B4.4 Event acquisitionThe SCS acquires events from the communication module of the ProSafe-SLS (model:CO-920) through the communication I/O module (model: ALR121). Acquired events are stor-ed in the SOER event information storage area inside the SCS memory and integrated withexisting SOE events. If a CENTUM system is integrated, acquired events can be viewed inthe SOE Viewer of the HIS.You can not specify the events acquired from the ProSafe-SLS as the trip signal of ProSafe-RS.Events are not included in the target of forcing. If the communication I/O module (model:ALR121) is locked, events will be the only information to remain unlocked. The SCS contin-ues to store events that are acquired from the CO-920 into the SOE buffer.

SEEALSO For more information about SOE event message acquired from the ProSafe-SLS, refer to:

“n Event information displayed on SOE Viewer” on page B4-23

n Basic event acquisition operation and time stampThe subsystem communication program S_SLSMOD acquires events from the CO-920 of thespecified station number based on the event acquisition communication definitions.S_SLSMOD acquires events from the CO-920 periodically. If the subsystem communicationperiod consists of one communication session for all communication definitions set for oneALR121 port, one event is acquired in one communication period.Events are acquired into the SCS in the order stored in the CO-920. The time stamps ofevents occurring near the time setting of the CO-920 or near the time its time synchronizationwas performed with that of the SCS may not be precise.

n SCS operation to acquire stored eventsIn the following situations, the SCS continuously acquires multiple events already stored inthe CO-920, instead of the cycle being repeated whereby the CO-920 stores events internallyand then SCS acquires the events.• The SCS is connected to the CO-920 for the first time.

• The SCS changes the COM port to which the CO-920 is connected.

• The SCS, which was down for a long time but is finally recovered, is reconnected to theCO-920.

• The SCS is reconnected to the CO-920 after the communication was cut off for a longperiod of time because the faulty ALR121 was replaced, etc.

• Multiple events occur at the same time because the ProSafe-SLS generated an error orshut down.

The SCS acquires events from the CO-920 according to the communication definitions. Ac-quisition starts from the event immediately after the last acquired event from the CO-920. Asin the case of normal communication, one event is acquired from the CO-920 in one subsys-tem communication period.

n Cautions when starting event acquisitionWhen the SCS continuously acquires multiple events that are already stored in the CO-920, itmay take several hours for all events to be acquired, after the start of event acquisition, ifmany events are stored in the CO-920. In this case, a time lag of several hours may occur toacquire the latest event because the latest event of the CO-920 is acquired after the acquisi-tion of all stored events is completed.

<B4.4 Event acquisition> B4-9


If events that are already stored in the ProSafe-SLS and not yet acquired by the ProSafe-RSare not needed, connect the COM-SET to the maintenance port of the CO-920 (port name:COM1) and acquire the stored events from the CO-920, and then clear all events of theCO-920, so as to prevent these events from being acquired over a long period of time.Events acquired by the COM-SET cannot be integrated with the SOE events of the ProSafe-RS.

n Causes of event acquisition communication errorThe following shows the causes of why the ALR121 notifies a communication error code tothe CPU.• The CO-920 is no longer responding.

The CO-920 may stop responding temporarily after being engineered from the COM-SETwhile operating.

• An error occurred along the communication path between the ALR121 and CO-920.

• A format error of the response from the CO-920 occurred.

IMPORTANTAssume that the ALR121 is disconnected from the SCS and then inserted again. An event ac-quired from the ProSafe-SLS immediately before the ALR121 is disconnected may be passedto the CPU module of the SCS redundantly after the ALR121 is inserted into the SCS.

SEEALSO For more information about communication error code system, refer to:

“n Communication error code” on page B3-3

n Event time for SOETime information effective when an event occurs on the ProSafe-SLS and is recorded, pro-vides the SOE event time. No new time information generates on the SCS side.The SCS converts the event time of the ProSafe-SLS to the ProSafe-RS time format, andthen stores the converted time as a SOE event in the SOER event information storage memo-ry.

<B4.4 Event acquisition> B4-10


B4.5 Time synchronizationAll references to time in the explanation of time synchronization are described with universaltime coordinated.To integrate events of the ProSafe-SLS with the SOE of the ProSafe-RS, it is necessary tosynchronize the time of the ProSafe-SLS with that of the SCS to align the time stamps ofthese events to those of the ProSafe-RS.The times can be synchronized by connecting the DO module of the SCS and DI module ofthe ProSafe-SLS.

n Configuration for time synchronizationThe following figure shows an example of configuration for time synchronization using the DOmodule (model: SDV531).

SD

V531

ALR

121

Vnet/IP

SCS

DO

Module

Trigger

Modbus protocol (RTU mode)

DI-511

DI M

odule

MC

-573D

igital Data

Storage M

odule

Event

Time adjustment

Initial time

ProSafe-SLS CO-920

CPU

COM-SET

Time synchronization

DO

: Cable

Puls

Legend

Figure B4.5-1 Configuration example for time synchronization of SCS and ProSafe-SLS

Connect the DO module of the SCS and DI module of the ProSafe-SLS.To synchronize the time of the SCS with that of the ProSafe-SLS, time synchronization pa-rameters of the CO-920 must be set from the COM-SET. To set these parameters, connectthe COM-SET to the maintenance port of the CO-920.After the time synchronization parameters are set, cause a time synchronization event to gen-erate periodically, for the ProSafe-SLS, through the DO module and DI module, to allow fortime synchronization.

<B4.5 Time synchronization> B4-11


It should be noted that, if multiple CO-920s are connected to the SCS, set the time synchroni-zation parameters and also perform time synchronization through the DO module and DImodule, for each CO-920.

n Connection between ProSafe-RS DO module and ProSafe-SLS DImodule

Connect the DO module of SCS (model: SDV531 or SDV541) and DI module of ProSafe-SLS(model: DI-511) to synchronize the time of the SCS with that of the ProSafe-SLS. Bleeder re-sistors should be connected with the DI module in parallel to meet the minimum load current35 mA of the DO module.You have to prepare bleeder resistors of 730 ohm or less to do this.A bleeder resistor of 680 ohm or less (5 W or 2 W) is recommended. When the 2-watt ratedpower resistor is used, the pulse width of the DO output must be set to one second or less.Before any resistor other than the recommended one is used, please contact us.

SEEALSO For more information about maximum length of the DI/DO cable connecting the SDV531/SDV541 and DI-511,

refer to:

"ProSafe-RS Outline of I/O Modules" (GS 32Q06K20-31E)

n Time synchronization settingFor the purpose of time synchronization, build an application logic, for the SCS, to output atime setting pulse once a day.The following list explains how to set the ProSafe-SLS for time synchronization.• Building a wired logic

Build a wired logic so that a time setting event is notified to the CO-920 from the DI mod-ule of the ProSafe-SLS.

• Reflecting the COM-SET settings in the CO-920The COM-SET should be set as follows:• Selection of time setting method

• Initial setting of date and timeSet in the COM-SET the initial time to adjust the CO-920 to when a time setting eventoccurs. Because the initial date and time are set for the purpose of time synchroniza-tion, they need not be set accurately.

• Tag information settingSet in the COM-SET the tag information at the time event source.

n Mechanism of time synchronizationThis section describes the mechanism of what happens after an application logic of the SCSis executed until the ProSafe-SLS is time-synchronized with the ProSafe-RS.The following list shows an example where the time of the ProSafe-SLS is adjusted to that ofthe ProSafe-RS when the SCS's CPU time reaches time A.1. When the SCS's CPU time reaches time A, a pulse is output from the application logic to

the DO module.

2. The pulse output from the DO module (model: SDV531 or SDV541) of the SCS is input tothe DI module (model: DI-511) of the ProSafe-SLS.

3. The DI-511 outputs an event, that is then input to the Digital Data Storage Module (model:MC-573).



4. The MC-573 notifies the time event to the CO-920. The CO-920 detects from the tagname of the event that the event is a time event, and sets its own clock to time A.

SEEALSO For more information about engineering for time synchronization, refer to:

10.3.3, “Engineering to Configure Applications on ProSafe-RS” in Engineering Guide (IM32Q01C10-31E)

n Time synchronization accuracy and calculation exampleThe accuracy of time synchronization of the CO-920 with respect to the SCS depends on theoutput timing of the DO module of the SCS.If the difference between the logic execution time and DO module output response time is afactor of error, time synchronization is always delayed by this time. If other factor of error is atplay, time synchronization is slightly delayed or passes by slightly fast.The following list shows a calculation example.• Calculation example of time error between the SCS and CO-920

(SCS scan period) + (output response time of DO module) + (CO-920 scan period)

• Calculation example of time error between the CO-920s connected to the same SCS(CO-920 scan period)

• Calculation example of time error between the CO-920s connected to different SCSs(SCS scan period) + (CO-920 scan period)



B4.6 Alarm notificationThe diagnostic information and events of the ProSafe-SLS are not notified to the CENTUMsystem operator or ProSafe-RS as alarms or events. To notify them as alarms to theCENTUM HIS, build an application that makes judgment on the diagnostic information anddata read from the CO-920 and uses the annunciator FB to notify alarms as necessary. Tonotify them as events to the CENTUM HIS, build an application that notifies events using theSOE FB.The SCS can acquire from CO-920 the self-diagnostic information of the Y-net and each mod-ule in the ProSafe-SLS, the available space in the event buffer of the CO-920 and other diag-nostic information. The diagnostic information of the CO-920 indicates the current statusesand values, and these statuses and values are retained while an error is present.Alarms relating to the subsystem communication between the SCS and ProSafe-SLS are no-tified to the HIS as subsystem communication system alarms, and to the SENG, as diagnosticinformation messages.To acquire diagnostic information from the CO-920, perform engineering on the CO-920 fromthe COM-SET.Examine for each system configuration how an error should be determined by using the diag-nostic information of the CO-920 and how the judgment result should be used, and performengineering so that error alarms and recovery alarms will be notified to the operator.

SEEALSO For more information about Communication error code system, refer to:

“n Communication error code” on page B3-3

For more information about engineering for CO-920, refer to:

ProSafe-SLS TI

For more information about application configuration procedure, refer to:

10., “Engineering for ProSafe-SLS Communication Function” in Engineering Guide (IM 32Q01C10-31E)

<B4.6 Alarm notification> B4-14


B4.7 Communication specificationsThe following describes the requirements for application capacity and transmission specifica-tions that must be met to build a system that uses the ProSafe-SLS communication function.

n Application capacityWhen the ProSafe-SLS communication function is used, determine I/O data, diagnostic infor-mation and events of ProSafe-SLS that you want to apply the comprehensive management inProSafe-RS. Examine ways to keep the application capacity to or less than the applicablemaximum capacity shown in the following table.

Table B4.7-1 Application capacityApplication element Maximum capacity Description

Number of ALR121 to install 4 per one SCS Total number includingALR111 (*1)

Number of communicationdata units per SCS

500 data units This specifies the num-ber of data items thatcan be wired to subsys-tem communication FBinstances.Maximum 256 words(4096 bits) are allowedfor the total assignmentsize of discrete input/output.

Size of communication I/Oper SCS

1000 words A word holds two bytes.

Allowable number of commu-nication attempts perALR121

1000 words -

Number of ports per ALR121 2 ports -

Allowable number of subsys-tem stations to communicateper port

30 stations One CO-920 is consid-ered as a station.

Number of communicationdefinitions per ALR121

Number of definitions in the range that can be cal-culated by using the following formula(Number of SLSEVENT type communication defi-nitions) x 2 + (Number of non-SLSEVENT typecommunication definitions) ≤ 128

-

Number of data sets forevent acquisition per Pro-Safe-SLS

24 words To acquire the eventsfrom ProSafe-SLS, as-sign 24 words of com-munication definition forevent acquisition perProSafe-SLS.

*1: Available number of ALR111 and ALR121 to be installed to an SCS is determined according to the total number of ALR111and ALR121 that are installed in the same SCS. Ensure the total number of ALR111/ALR121 does not exceed the applicablevalue shown in the table. Communication modules for the Modbus slave communication are not included in the count.

n Transmission specificationsThe following table shows the transmission specifications for RS-485 communication thatmust be met in order to implement the ProSafe-SLS communication function.

<B4.7 Communication specifications> B4-15


Table B4.7-2 Transmission specificationsSetting items Recommen-

ded settingRequiredsetting

Selection

Interface - RS-485 RS-422, RS-485

RS-422/RS-485 2-wire/4-wire 4-wire - 2-wire, 4-wire

Transmission method - - Half-duplex

Synchronization method - - Start-stop synchronization

Baud rate (bps) (*1) 19200 - 1200, 2400, 4800, 9600, 19200, 38400

Transmission protocol - - Modbus protocol (RTU mode)

Transmission code - - Binary

Data type Start bit - - Fixed to 1.

Data bit - 8 7, 8

Parity Even (*2) - None, even, odd

Stop bit - - Fixed to 1.

Control line RS control - - Not used

DR check - - Not used

CD check - - Not used

Time monitor-ing

Transmission ena-ble monitoringtime

- - 1000 ms

Reception inter-character timer(ms)

10 (*3) - 10 to 99999

Generate an errorupon detection ofan inter-charactermonitoring time-out.

Do not gen-erate an er-ror (*3)

- Do not generate an error

Text frame Reception startcharacter

- - None

EOT character - - None

XON/XOFF control - - None

Response timeout (sec) 4 - 0 to 99

Communication retry 1 time - 0 to 99 times

Interval of connection retries (sec) 30 - 0 to 999

Transmission wait time - - 1 sec

Option 1 - - Not used




*1: The baud rate of the CO-920 is initially set to a value not included in the options. Ensure the baud rate set for the CO-920 isthe same as this baud rate setting.

*2: The initial setting of CO-920 parity is "None." It is recommended to set a parity to improve reliability. Ensure the parity settingof the CO-920 matches this parity setting.

*3: Completion of reception is detected as an inter-character timeout. Setting a longer time for the inter-character timer will delaythe time to reception completion. As a guide, the timer is set to approx. 10 ms at 9600 bps. 10 ms corresponds to the timerequired for sending 10 characters when the baud rate is 9600 bps.

<B4.7 Communication specifications> B4-16


B4.8 ProSafe-SLS device accessible by the SCSInternal data used by the Modbus slave function of the CO-920 is called a "Device." The fol-lowing shows types of devices.• Bit devices

Every bit of this data has a meaning.

• Word devicesEvery word of this data has a meaning. One word consists of 16 bits.

• Extended deviceExtended devices are specific to Modbus equipment. On the CO-920, extended devicesare those devices whose event data is stored as historical records.

Communication module of the ProSafe-SLS (model: CO-920) can be accessed from an exter-nal system according to the Modbus protocol (RTU mode).Use standard Modbus commands to access the analog input module and digital I/O module ofthe ProSafe-SLS from the ProSafe-RS.To access the devices, set "Device Address" and "Size" in the Communication I/O Builder.The following formula shows an address format.

<Function code> + <Device type> + <Address within device>

To specify input relays 100012 to 100015 in the Communication I/O Builder, for example, setA100012 in "Device Address" and 1 in "Size." "A" of A100012 indicates a function code, "1"indicates a device type, and "00012" indicates an address within device.The following table shows the devices that can be used in connection with the ProSafe-SLScommunication function, address, and the Modbus protocol function code.

Table B4.8-1 Bit devices listDevice Address Modbus protocol function code

(hexadecimal)Function code Device types of

CO-920Internal ad-

dress of CO-920device (to the

extent specifia-ble)

Read Write

Coil A 0 00001-65536 01 0F

B 05

X - 0F

Y 05

Input relay A 1 00001-65536 02 -

Table B4.8-2 Word devices listDevice Address Modbus protocol function code


CO-920Internal ad-



Read Write

Input register A 3 00001-65536 04 -


<B4.8 ProSafe-SLS device accessible by the SCS> B4-17


Table B4.8-2 Word devices list (Table continued)Device Address Modbus protocol function code


CO-920Internal ad-



Read Write

Holding register A 4 00001-65536 03 10

B 06

C 10

X - 10

Y 06

Z 10

n Meaning of function codeThe meaning of each function code is as follows:• 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 read-back.

• BRead data for the size specified at Size field in the Communication I/O Builder.Write data individually to each modified device in units of 1 bit for a bit device, or in unitsof 16 bits for a word device. With readback.

• CRead data for the size specified at Size field in the Communication I/O Builder.Write data individually to each modified device in units of 32 bits. With readback.

• XWrite data for the size specified at Size field in the Communication I/O Builder when achange occurs. Without readback.

• YWrite data individually only to each modified device for the size of each device when achange occurs. Without readback.

• ZWrite data individually only to each modified device in units of 32 bits when a change oc-curs. Without readback.

n List of function codesThe meaning of each function code is shown in the following table:



Table B4.8-3 List of function codesFunction code Device Read Write Readback

A Bit devices All data for onecommunication defi-nition


Yes

Word devices All data for onecommunication defi-nition


Yes

B Bit devices All data for onecommunication defi-nition

In units of 1 bit Yes

Word devices All data for onecommunication defi-nition


C Word devices All data for onecommunication defi-nition


X Bit devices - All data for onecommunication defi-nition

No

Word devices - All data for onecommunication defi-nition

No

Y Bit devices - In units of 1 bit No

Word devices - In units of 16 bits No

Z Word devices - In units of 32 bits No

Data is read from the ProSafe-SLS if readback is enabled, and the read data is written to theSCS if the data type specified in the Communication I/O Definition Builder is "Input Specifica-tion." The read data is compared against the SCS data if the data type is "Output Specifica-tion," or sent to the ProSafe-SLS if data is different.If readback is disabled, the SCS data is compared against the ALR121 data, and the data willbe sent to the ProSafe-SLS only if a discrepancy is found.

SEEALSO For more information about readback, refer to:

• B3.6, “Readback communication” on page B3-21

• “■ About Readback Communication Operations” in 2.17.1, “Subsystem Communication Function” inEngineering Guide (IM 32Q01C10-31E)



B4.9 Communication time betweencommunication module and CO-920

The communication time between the communication module of the ProSafe-RS (model:ALR121) and CO-920 is the total sum of times T1 to T7 as shown in the following figure.

T4

Interpretation/execution of

message, creation ofresponse message

T7

Interpretation ofreceived message,

storage of data

Start of dataacquisition

T1

Creation ofsend message

ALR121

CO-920

CO-920 modem

Time

ALR121 modem

T5 T6T2 T3

Data canbe read

T1: Time for creating a send message: Approx. 10 msT2: Delay time of the ALR121 modem: Approx. 5 msT3: Time for transmitting the send message.T4: 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.T5: Delay time of the Modbus PLC modem (T4 + T5 ): Approx. 3 msT6: Time for transmitting the response message.T7: Time for interpreting the response message: Approx. 15 ms

Figure B4.9-1 Communication processing time in connection with the ProSafe-SLS communicationfunction

The following shows how to calculate the communication time.The transmission time for sending (T3) and receiving (T6) can be calculated by using the fol-lowing formulas:

<B4.9 Communication time between communication module and CO-920> B4-20


1000 x Number of characters x Number of bits per one characterBaud rate

(ms)

Number of bits per one character = Number of start bits (1) + Number of data bits (8) + Number of parity bits (1) + Number of stop bits (1)

T3 or T6 =

Start bit: Fixed at 1 bitData bits: Fixed at 8 bits (7 bits cannot be specified)Parity bit: Set 1 if parity is even or odd, set 0 if parity is noneStop bit: Fixed at 1 bitBaud rate: 1200, 2400, 4800, 9600, 19200, 38400 bps

The following table shows the length of each frame that is transmitted by a Modbus compliantdevice.

Table B4.9-1 Number of characters transmitted

DeviceRead Write

Send 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 ofrelays/8(*1) - -

Input register Fixed to 8. 5 + 2 x Number of regis-ters - -

Holding register Fixed to 8. 5 + 2 x Number of regis-ters

9 + 2 x Number of regis-ters Fixed to 8.

Event Fixed to 4. 5 + event (maximum 86) - -

*1: Fraction below the decimal point is rounded up.

<B4.9 Communication time between communication module and CO-920> B4-21


B4.10 Data types handled by the ProSafe-SLScommunication function

The following table shows the data types of subsystem communication that can be handledby the ProSafe-SLS communication function.

Table B4.10-1 Relationship between the data types of subsystem communication, and data types ofthe SO-920 and those of the SCSSubsystem communication data

typeCO-920 data type SCS data type (subsystem com-

munication FBs)Discrete input BOOL (bit) SCI_B

Discrete output BOOL (bit) SCO_B

Analog input (16-bit unsigned inte-ger)

16-bit unsigned integer SCI_I

Analog output (16-bit unsigned in-teger)

16-bit unsigned integer SCO_I

SLS event type ASCII character string N/A (*1)

*1: The SLS event type represents a data type used exclusively for acquiring ProSafe-SLS events. The SCS uses the SLS eventtype internally.SLS events cannot be used in application logics.

<B4.10 Data types handled by the ProSafe-SLS communication function> B4-22


B4.11 Message specificationsThe SCS interprets the event acquired from the ProSafe-SLS and stores them as SOEevents. The stored events can be comprehensively managed with existing SCS events usingthe SOE Viewer of SENG or SOE Viewer of CENTUM HIS.The following table shows the event information issued by the ProSafe-SLS.

Table B4.11-1 Event information issued by ProSafe-SLSEvent Information ASCII format Description

Event generation time Set this information according to one of the fol-lowing formats:• dd/mm/yyyy hh:mm:ss.msc• dd/mm/yy hh:mm:ss.mscThe setting ranges for each element are as fol-lows:dd: 01 to 31mm: 01 to 12yy: 00 to 99yyyy: 0000 to 9999hh: 00 to 23mm: 00 to 59ss: 00 to 59msc: 000 to 999

Year, month, day, hours, minutes,seconds and milliseconds indicat-ing when the event occurred.The description format of year var-ies depending on the format set forevent character strings.

Tag name of ProSafe-SLS

ASCII character string with 25 charactersAny empty digit in the 25-character tag nameis filled by the ASCII character code 0x20 (SP).

ProSafe-SLS tag names associ-ated with data at the source. Thefirst 22 characters of the tag nameof ProSafe-SLS are imported intothe SOE of ProSafe-RS.

Description ASCII character string with 25 charactersAny empty digit in the 25-character descriptionis filled by the ASCII character code 0x20 (SP).

Supplemental information regard-ing the tag name of ProSafe-SLS.This information is not imported in-to the SOE of ProSafe-RS.

Status 1 character type: 0 to 110 character type: 0 to 65535The end of the 10-character status is filled bytwo space characters.Also, any non-character part at the beginningor end is filled by the ASCII character code0x20 (SP).

Data value upon event generation.The range of values is as follows.10 character type: 0 to 655351 character type: 0 or 1. (*1)When performing engineering onthe CO-920, determine whether touse the 10 character type or 1character type.

*1: Any 10-character value between 1 and 65535 is expressed as 1 based on the 1 character type.

n Event information displayed on SOE ViewerThe SCS acquires ProSafe-SLS event information and displays it in the SOE Viewer. The fol-lowing table shows the event information displayed in the SOE Viewer.

<B4.11 Message specifications> B4-23


Table B4.11-2 SOE Viewer event informationItem Description Acquisition source of event information

CO-920 SCS Subsystemcommunica-tion function

Time Stamp Date and time the event occurredSet the date format in the SOE ViewerProperties dialog box.The following format displays time:hh:mm:ss:tttThe meaning of each element is as fol-lows:hh: Time (24 hours)mm: Minutess: Secondttt: Millisecond

Event generationtime

- -

Quality Empty - - -

Type SOER (fixed) - - -

ID EVT_TRUE (fixed) - - -

Resource Station name (SCSddss) - Station name -

Reference (*1) Node number (1 to 9, a to e, 1 hexa-decimal character)

- Node number -

Slot number (1 to 8, 1 character) - Slot number -

Port number (1 to 2, 1 character) - - Port number

Station number (01 to ff, 2 hexadeci-mal characters)

- - Station num-ber

Tag name of ProSafe-SLS (maximum22 characters)

Tag name of Pro-Safe-SLS (first 22of 25 characters)

- -

Message Data value (DINT type) Status - -

*1: Display format: "SLS [Node number] [Slot number] [Port number] - [Station number]:[ProSafe-SLS tag name]"

n Event display example of SOE Viewer and COM-SETAssume that the ALR121 installed in slot 3 of SCS0101 node 10 acquired an event from theProSafe-SLS of station number 24 connected to port 1 at 18 hours 30 minutes 15 seconds123 milliseconds on February 24, 2015. Examples of how this is displayed in the SOE Viewerand on the COM-SET are given.In the table, an empty field indicates that nothing is displayed in the applicable item field.The tag name and value of the ProSafe-SLS event are DI511_1 and 1, respectively.

Table B4.11-3 Display example of SOE ViewerTimestamp Quality Type ID Resource Reference Message

02/24/201518:30:15.123

SOER EVT_TRUE

SCS0101 SLSa31-18:DI-511_1(*1)

1

*1: "a" in hexadecimal notation indicates that the node number is 10. "18" in hexadecimal notation indicates that the station num-ber is 24.

Table B4.11-4 Display example of COM-SETDate/Time (*1) Tag Name Tag Description Status

24/02/2015 18:30:15.123 DI-511_1 TAG1 1

*1: The specific value varies depending on the set format of event character string.

<B4.11 Message specifications> B4-24


B4.12 Builders to be set and engineering flowThe following table shows the builders that must be set to use the ProSafe-SLS communica-tion function.

Table B4.12-1 Related builders and windowPurpose Name and builders and window Role

Engineering I/O Wiring View Definition of communication device

I/O Parameter Builder Selection of communication program

Setting of transmission definitions foreach port

Comm. I/O Definition tab of the Communi-cation I/O Builder

Definition of communication definition

Comm. I/O Wiring tab of the Communica-tion I/O Builder

Assignment of communication I/O FB tocommunication data

Maintenance Communication I/O Lock Window Referencing of logical and physical datavalues of I/O variables, and forcing

The following figure shows the engineering flow to be followed in order to implement the Pro-Safe-SLS communication function.

<B4.12 Builders to be set and engineering flow> B4-25


ProSafe-SLSCENTUM

ProSafe-RS

Applicationengineering• Tag name access• Operating status display

Start

End

Engineering toconfigure application• Time synchronization• Monitoring I/O data• Alarm notification• Tag name access

SystemEngineering• I/O wiring• I/O parameter definition• Communication I/O definition

Design study on I/O module or alarm to be consolidated and determine specifications of time synchronization

Upgrading SENG revision (*1)

Off-line loadingof SCS (*2)

Networkconnection check

Engineering for CO-920• Communication settings• Tag name settings• I/O data and diagnostic information assigned to Modbus register

Process and setting that conform to the design information• Processing CO-920 events• Initial setting of time

for engineering?

*1: You do not need to upgrade the revision for a new project. If you intend to upgrade the revision of existing project to use ProSafe-SLS functions, you must perform offline download.

*2: If you have performed offline download of the project database in R3.02.20 or later, you can perform online download.

Figure B4.12-1 Engineering flow for ProSafe-SLS communication function



SEEALSO For more information about engineering regarding ProSafe-SLS, refer to:

10., “Engineering for ProSafe-SLS Communication Function” in Engineering Guide (IM 32Q01C10-31E)

For more information about I/O Parameter Builder setting, refer to:

B1.4.1, “Settings using the I/O Parameter Builder” on page B1-17

For more information about Communication I/O Builder setting, refer to:

B1.4.2, “Settings using the Communication I/O Builder” on page B1-22

For more information about Communication I/O Lock Window, refer to:

B1.6, “Communication I/O Lock window” on page B1-33



C. Modbus slave communicationThe Modbus slave communication function is one of the Modbus communication functionsthat are provided by ProSafe-RS. This function allows a safety control station (SCS) to act asa Modbus slave and communicate with other systems.

<C. Modbus slave communication> C-1


C1. Common items regarding theModbus slave communicationfunction

You can use the Modbus slave communication function to connect the ProSafe-RS SCS toother systems. The Modbus master (an external device) can reference or set data in SCS byusing the communication function of the communication module. By accessing SCS data us-ing the Modbus slave communication function, you can configure operator interfaces also inother systems.This section provides an overview and details of the Modbus slave communication functionand describes the settings that are related to Modbus slave communication.

<C1. Common items regarding the Modbus slave communication function> C1-1


C1.1 Overview of Modbus slave communicationWhen the Modbus master (external device) sends data, the Modbus slave communicationfunction of SCS receives the data through the communication function of the communicationmodule. The SCS Modbus slave communication function sends a response message to theModbus master (external device) in response to the request for data.

SEEALSO For more information about overview of Modbus slave communication, refer to:

2.17, “Connection with Other Systems via Communication Modules” in Engineering Guide (IM32Q01C10-31E)

n Relationship between SCS, SENG, and Modbus masterThe following figure shows the relationship between the SCS, SENG, and Modbus master(external device).

Modbus master (e.g., DCS)

Error information

Communication data

SENG

SCS CPU

Request/response

Data access Reference

Communication module

Downloading definition information

SCS Status display function of SCS Maintenance Support Tool

Definition information SCS data

Engineering functions

Communication functions

Modbus slave communication function

Figure C1.1-1 Relationship with an external device

The following describes the relationship between the SCS, SENG, and Modbus master (exter-nal device).• SENG

The engineering functions of the SENG download the definition information of the com-munication module and the definition of correspondence between Modbus device ad-dresses and SCS data, etc. to SCS.

• SCS Maintenance Support ToolThe SCS status display function of SCS Maintenance Support Tool receives error infor-mation and notifies the error status if there is any error in the communication module andcommunication content.

<C1.1 Overview of Modbus slave communication> C1-2


• Modbus masterThe Modbus master references and sets SCS data through the communication module.

• SCSThe Modbus slave communication function of SCS accesses data in response to a re-quest from the Modbus master and returns the result to the Modbus master through thecommunication module.

n Interface with the Modbus masterSCS operates as a Modbus slave. An external device operates as the Modbus master and itcan reference and set SCS data.The external device and SCS are connected with a serial communication module or Ethernetcommunication module that is installed in the SCS node. Neither of these modules supportdual-redundant configuration. These modules are interference-free modules that do not inter-fere 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, 1200 bps to 115.2 kbps)

• Ethernet communication module (10BASE-T, 1-port)

n Data access by device speciationThe Modbus master requests data access to the SCS (Modbus slave) using the Modbus devi-ces names in the following table as the interface.SCS does not have actual Modbus devices. SCS assigns virtual Modbus device addresses tovariables of the application logic and sends them responses accordingly.

Table C1.1-1 Modbus devices

Virtual Modbus device DataAccess from master to slave (*1)Read (reference) Write (set)

Coil Output device with 1 bit/channel Yes Yes (*2)

Input relay Input device with 1 bit/channel Yes No

Input register Input register with 16 bit/channel Yes No

Holding register Output register with 16 bit/channel Yes Yes (*2)

*1: Yes: allowedNo: not allowed

*2: The Modbus master can only set data on SCS (Modbus slave) if virtual Modbus devices are assigned to external communica-tion function blocks.

The correspondence between the addresses of the Modbus devices and variables of the ap-plication logic is defined using SCS Manager.

SEEALSO For more information about procedure for supporting addresses and application logic variables for Modbus

devices, refer to:

C1.5.1, “Definitions in Modbus Address Builder” on page C1-12

n Data settings from the Modbus masterData can be set to variables of the application logic from the Modbus master through Modbusslave communication using external communication function blocks.



n Modbus slave communication execution timingAs a Modbus slave, SCS performs Modbus slave communication at the idle time of each scanfor the application logic. SCS checks whether any request has been sent from the Modbusmaster through the communication module. If SCS finds any request, SCS will respond to therequest only when the scan has idle time.SCS only responds to the request in this communication processing and will set the data tothe variables of application logic in the scan by the safety functions after responding to therequest.

Scan by an external device connection functions 1 second

Scan by the safety functions

Modbus communication processing

Figure C1.1-2 Modbus slave communication execution timing

n Monitoring from HIS or SCS Maintenance Support ToolThe communication module status can be monitored from HIS or SCS Maintenance SupportTool.

Table C1.1-2 Monitoring of communication modules from HIS or SCS Maintenance Support ToolWindow Monitoring operation

SCS State Management Displays whether the communication module is normal or faulty.No communication errors are displayed.

System alarm Errors in the communication module are notified by systemalarms.

n Operation when the communication module is added onlineIt is possible to make changes online to applications that involve addition or removal of serialcommunication modules. If you install an additional communication module in the SCS andexecute an online change download, the communication 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 remains the same. You do not need to per-form the Output enable operation or any other special operation.



C1.2 Data access using the Modbuscommunication functions

When the Modbus master sends a request for data access, SCS receives the data throughthe ALR111/ALR121 serial communication module or ALE111 Ethernet communication mod-ule. The SCS reads/writes data within itself using the Modbus communication commands andnotifies the result to the Modbus master.By using the Modbus communication functions, the SCS references or sets SCS data in re-sponse to requests from the Modbus master. To process the requests, it references the data-base that defines the correspondence between Modbus device addresses and applicationlogic variables.

n Referencing/setting SCS dataThis 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 (ModbusWord Order), variables data of external communication function blocks.

n Word reversalTo 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 isin the order of the lower word first and the upper word if this option is specified.

40001 Direct 40002

40002 40001 Reverse

Lower word

32-bit data

Upper word

Figure C1.2-1 Execution example of word reversal

n One shot writeWhen setting SCS data, a one shot write operation is performed on data that does not inter-fere with the safety loop. An error is returned if it is requested to set data that interfere withthe safety loop.

n 16-bit Modbus master support modeYou can use 16-bit Modbus master support mode when connecting SCS to a Modbus masterthat handles only 16-bit data. If the Modbus master does not read or write data of SCS in 16-bit units, leave 16-bit Modbus master support mode disabled (default setting), and access da-ta in 32-bit units. When this mode is enabled, the Modbus master can read and write data in-cluding 16-bit integer data, 32-bit signed integer data, and 32-bit floating point data. However,this requires very complicated ProSafe-RS application.If the following types of data access is required, enable 16-bit Modbus master support modeby using SCS Constants Builder.

<C1.2 Data access using the Modbus communication functions> C1-5


Table C1.2-1 Data accesses available in 16-bit Modbus master support modeAccess from the Modbus master to SCS Data type Function code (decimal)

Read one word from a holding register withan odd or even reference number

Signed integer dataFloating-point data

Read Holding Registers (03)

Read one word from an input register with anodd or even reference number

Signed integer dataFloating-point data

Read Input Registers (04)

Write one word to a holding register with anodd or even reference number

Signed integer data Use the following function codewhichever is available with the Mod-bus master:Preset Single Register (06) or PresetMultiple Registers (16)

SEEALSO For more information about function codes supported on an SCS, refer to:

• “l Function code” on page C1-23

• “l Cautionary notes on function codes” on page C1-24

n Communication testWhen testing for referencing a variable of SCS, change a value of the variable by using theforcing function and confirm the value by the Modbus master. When testing for setting an ex-ternal communication function block of SCS, connect a variable with the external functionblock and confirm the value of the variable by the Modbus master reading back.

SEEALSO For more information about forcing function, refer to:

2., “Forcing Function” in Utilities and Maintenance Reference (IM 32Q04B20-31E)

<C1.2 Data access using the Modbus communication functions> C1-6


C1.3 Setting items relating to Modbus slavecommunication

The following settings are required for the Modbus master to access application logic varia-bles on an SCS through Modbus slave communication.• Definition of communication modules

You can define the serial communication module (ALR111/ALR121) or Ethernet communi-cation module (ALE111) to perform Modbus slave communication using I/O Wiring Viewand I/O Parameter Builder.

• Definition of addresses of Modbus devicesYou can define virtual Modbus devices on SCS and assign them to variables, using theModbus Address Builder.

• Data setting using Modbus slave communicationYou can assign external communication function blocks to set SCS data from the Modbusmaster (external device).

<C1.3 Setting items relating to Modbus slave communication> C1-7


C1.4 Definition of communication modulesYou can define the communication module for SCS so that SCS can preform Modbus commu-nication.You can define the serial communication module or Ethernet communication module by usingthe I/O Wiring View of SCS Manager first, and then you can set parameters for each port ofthe module by using the I/O Parameter Builder.

SEEALSO For more information about I/O Wiring View and I/O Parameter Builder, refer to:

4., “Definitions of Inputs/Outputs” in Engineering Reference (IM 32Q04B10-31E)

For more information about parameter settings for communication modules, refer to:

“■ Common setting items for input/output modules” in A4.3, “Common input/output setting items” in Safe-ty Control Station Reference (IM 32Q03B10-31E)

<C1.4 Definition of communication modules> C1-8


C1.4.1 Definitions in I/O Wiring ViewTo define the serial communication module (ALR111/ALR121) or Ethernet communicationmodule (ALE111), use the I/O Wiring View in SCS Manager and follow these steps:1. Open I/O Wiring View and select ALR111, ALR121, or ALE111. The number of channels

should be set to 0.

2. Select parameters for the module and specify the node number and the slot number. Thenode number and the slot number must not overlap with those of other input/output mod-ules and communication modules.



C1.4.2 Definitions in I/O Parameter BuilderYou can specify parameters for the communication module using I/O Parameter Builder. Theparameters to specify differ depending on the type of the communication module.Because a serial communication module (ALR111/ALR121) has two ports, two sets of param-eters are required. You can specify the parameters in the Port1 and Port2 tabs of I/O Parame-ter Builder.For an Ethernet communication module, you can specify the parameters in the Ethernet com-munication module parameters tab of I/O Parameter Builder.

SEEALSO For more information about parameter settings for serial communication modules, refer to:

“n Port 1, Port 2 tab” on page C2-6

For more information about parameter settings for Ethernet communication modules, refer to:

“n Module tab of Ethernet communication module” on page C3-4



C1.5 Definition of addresses of Modbus devicesTo access variables of the application logic on SCS from the Modbus master through Modbusslave communication, it is necessary to define the correspondence between the variables andthe addresses of Modbus devices. Define Modbus device addresses for the variables usingModbus Address Builder.Modbus device addresses can be assigned to input/output variables and internal variables.

<C1.5 Definition of addresses of Modbus devices > C1-11


C1.5.1 Definitions in Modbus Address BuilderUse Modbus Address Builder to associate the variables of the application logic with the ad-dresses of Modbus devices.

n Assigning variables in Modbus Address BuilderModbus devices can belong to the following four types: coils, input relays, input registers andholding registers. A reference number is assigned to each Modbus device type. The variablename to be accessed is assigned to a reference number in Modbus Address Builder. The typeof variable to be assigned is selected according to the reference number. For example, a vari-able of BOOL type or IO_BOOL type can be assigned to an input relay.

SEEALSO For more information about reference numbers, refer to:

“n Modbus device tabs” on page C1-18

l Types of Modbus devices and variablesThe type of variables that can be assigned to each reference number of Modbus devices is asfollows:

Table C1.5.1-1 Variables to which Modbus device addresses can be assignedModbus device type Variable type Remark

Coil

ECW_B Instance of external communication function block (BOOLtype)

BOOL Read-only. Writing data to the SCS results in an error whenthe SCS runs.

IO_BOOL Read-only. Writing data to the SCS results in an error whenthe SCS runs.

ECWR_B Available only with SCSU1, which is dedicated to integrationwith FAST/TOOLS

Input relayBOOL -

IO_BOOL Only the data value is included, and the data status is not in-cluded.

Input register

REAL Requires two addresses per data.

DINT Requires two addresses per data.

IO_REALOnly the data value is included, and the data status is not in-cluded.Requires two addresses per data.




Table C1.5.1-1 Variables to which Modbus device addresses can be assigned (Table continued)Modbus device type Variable type Remark

Holding register

ECW_RInstance of external communication function block (REALtype)Requires two addresses per data

ECW_IInstance of external communication function block (DINTtype)Requires two addresses per data

REAL Read-only. Writing data to the SCS results in an error whenthe SCS runs

DINT Read-only. Writing data to the SCS results in an error whenthe SCS runs

IO_REAL Read-only. Writing data to the SCS results in an error whenthe SCS runs

ECWR_R Available only with SCSU1, which is dedicated to integrationwith FAST/TOOLS

ECWR_I Available only with SCSU1, which is dedicated to integrationwith FAST/TOOLS

The BOOL, IO_BOOL, DINT, REAL, and IO_REAL-type variables are read-only. You can as-sign these variables to input relays and input registers. In Modbus Address Builder, variablesof these types are not displayed in the data menu area for coils and holding registers. To as-sign these variables to coils or holding registers, you need to enter the variable names direct-ly.When the Modbus device is a coil or holding register, you can set data from the Modbus mas-ter only for the types that have correspondence with external communication function blockssuch as ECW_B, ECW_R, and ECW_I types.

l Variable namesA variable name can be up to 69 characters long. Both global and local variables can be ac-cessed regardless of the scope. Describe a scope name after "@" to access local variables.To access internal variables in a user-defined function block, you can use the SCS ManagerDictionary View to name instances of the user-defined function block itself. Specify the varia-ble name in the following format. Up to two nesting levels can be specified for an instancename.

Instance name.internal variable name

Table C1.5.1-2 Example of variable namesVariable name Scope Description

VAR1 Global Global variable

VAR2@PROG1 PROG1 A local variable of a function in PROG1

FB01.VAR3 Global The internal variable VAR3 of an instance of theuser-defined function block FB01

FB01.VAR3@PROG1 PROG1The internal variable VAR3 of an instance of theuser-defined function block FB01, which is locally de-fined in a function of PROG1

FB01.FB2.VAR3 Global

The internal variable VAR3 of an instance of theuser-defined function block FB2 used inside an in-stance of the user-defined function block FB01 (Thelimit of nesting of a function block is two)



SEEALSO For more information about SCS Manager Dictionary View, refer to:

Workbench User's Guide

n How to define variable namesVariable names can be specified in the Variable name columns in the tabs for the four differ-ent 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 keyboardEnter a variable name in the Variable name column directly from the keyboard.

l Double-clicking a variable name in the data menu areaThe 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 namecolumn.Double-click a node number or a slot number in the IOM tab to set variables wired for eachInput/Output Module at once.

l Drag and drop from Dictionary ViewDrag and drop a variable name from Dictionary View to a variable name field of Modbus Ad-dress Builder to register the variable name in Modbus Address Builder. If you drag and dropmultiple variable names, they are registered in order starting from the top of the Variablename column where they are dropped. If variable names have already been registered in theVariable name field, they are overwritten.



File Edit View Tools Window Modbus Address Builder -[Pjt:SCS0101 File:Modbus.edf]

Variable IOM Holding regis

Reference

30003

30005

Variable name Type

30001 REAL

IO_REAL

IO_REAL

%IU0.2

%IU0.1

DINT

R03

IN01

AI02

AI01

D01@P1

30007

30009

30011

30013

30015

Wiring po

Coil

AI03 AI04 D02@P1 D03@P1 D04 FB1A.R1 FB1A.R2 FB2A.R1 FB2B.R2 R01 R02 R04 IN01

Message

Ready Position: Line 1 Column 3

Input relay Input registers

File Edit Debug Tools Options Window Help ProSafe-RS - [Project2 (*Binding error management*) - Dictionary - 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 Resource 1: Config1\Main(*send info to R2*)

All variables

Name Alias

BindErrText STRING STRING STRING STRING STRING BOOL REAL BOOL BOOL BOOL

BindingErrorTxt BindingErrorTxt [0] BindingErrorTxt [1] BindingErrorTxt [2] BindingErrorTxt [3] BindingErrorTxt [4]

OK2 IN01 val4 VASystemKVB UserAcknowledge InitBindText

Type

200 200 200 200 200 200

[ ]

BOOL

0 1 N

A Z

Z A

Figure C1.5.1-1 Drag and drop from Dictionary View



IMPORTANTChanging a name and type of a variable in Dictionary View will not change the correspondingdefinition in Modbus Address Builder. Make the corresponding modifications in Modbus Ad-dress Builder according to changes.• If a variable is added

Use Modbus Address Builder and assign a reference number to the variable as necessa-ry.

• If a variable name is changedChange the corresponding variable name in Modbus Address Builder as well.

• If a variable is deletedDelete the corresponding variable in Modbus Address Builder.



C1.5.2 Window configuration of Modbus Address Builder

File Edit View Tools Window Help Modbus Address Builder -[Pjt:SCS0101 File:Modbus.edf]

Holding regist

Reference

30003

30005

Type

30001 REAL

IO_REAL

IO_REAL

%IU0.2

%IU0.1

DINT

30007

30009

30011

30013

30015

Wiring Po

Coil


Message

Ready Position: Line 1 Column 3

Input relay Input registers

Data menu area Work Space

Variable IOM

Variable name

R03

AI02

AI01

D01@P1

Figure C1.5.2-1 Window configuration of Modbus Address Builder

The Modbus Address Builder window mainly consists of the data menu area and work space.

SEEALSO For more information about components that are the same in other builders, refer to:

2.2, “Relationship Between ProSafe-RS Projects and CENTUM Projects” in Engineering Reference (IM32Q04B10-31E)

n Data menu areaThe data menu area of Modbus Address Builder contains two tabs, the Variable tab and theIOM tab. Modbus Address Builder allows setting variable names only.

l Variable tabThe Variable tab displays a list of variables that can be defined. The variable names displayedchange 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 deletedfrom the list and not displayed.




Variable IOM

Figure C1.5.2-2 Data menu area - Variable tab

l IOM tabWhen the input relay tab or the input register tab is displayed, in the workspace the IOM tabbecomes available.For an Input Relay, a discrete input module will be displayed; while for an Input Register, ananalog input module will be displayed.

Node1 1-1 1-2 1-3 1-4 1-5 1-6

Variable IOM

Figure C1.5.2-3 Data menu area - IOM tab

n Modbus device tabsThe following tabs are provided in the Modbus Address Builder workspace:• Coil tab

• Input relay tab

• Input registers tab

• Holding registers tab

l Reference numbers in tabsEach tab displays the reference numbers.• Coil tab

Range of reference numbers: 00001 to 01000Example:

00001, 00002, 00003, ...... , 01000Output devices of 1 bit per channel (allows both input and output)



• Input relay tabRange of reference numbers: 10001 to 14000Example:

10001, 10002, 10003, ...... , 14000Input devices of 1 bit per channel (allows input only)

• Input registers tabRange of reference numbers: Odd numbers between 30001 and 34000Example:

30001, 30003, 30005, ...... , 33999Input 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 tabRange of reference numbers: Odd numbers between 40001 and 41000Example:

40001, 40003, 40005, ...... , 40999Output 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.

l Items displayed in tabsEach 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 NameVariable names to be assigned.This item is commonly displayed for all the tabs.

• TypeTypes of variables. These are displayed once variable names are determined.This item is commonly displayed for all the tabs.

• CommentComments attached to variables. These are displayed once variable names are deter-mined.This item is commonly displayed for all the tabs.

• Wiring PositionInstallation positions of channels corresponding to variables. This item is displayed onlyfor the Input relay and Input registers tabs. The wiring positions are displayed when varia-bles are determined if the variable type is IO_BOOL in the case of the Input relay tab andIO_REAL in the case of the Input registers tab. The display format is %IUm.n or %QUm.nin both cases,for example %IU0.0.



C1.6 Data setting using Modbus slavecommunication

The SCS Modbus slave communication function allows setting data on SCS from the Modbusmaster. Use external communication function blocks to set SCS data from the Modbus mas-ter. Data setting through external communication function blocks does not interfere with thesafety loop (interference-free). Make sure to read back and confirm the data set by externalcommunication function blocks, when using the data for safety application.

n Data setting using external communication function blocksIt is possible to read and write data of SCS from the Modbus master using the SCS Modbusslave communication function. The Modbus master device sends a data access request toSCS, using Modbus device address as interfaces. Although SCS is not equipped with any ac-tual Modbus devices, it acts as if it has them and responds to the data access requests fromthe Modbus master.Data can be set from the Modbus master to the SCS by combining the Modbus slave commu-nication function and external communication function blocks. The Modbus device types thatcan be used for data setting are coil and holding register. Assign instance names of externalcommunication function blocks to coils and holding registers using Modbus Address Builder.• 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 aholding register.

• To set REAL-type data, assign an ECW_R instance name to the reference number of aholding register.

As a result, data set from the Modbus master are output from the output parameter OUT ofthe associated external communication function blocks.

Modbus Modbus slave communication

function

Application logic

SCS

Modbus master

Application

OUT Internal variableECW_B

Internal variableECW_I

OUT

Internal variableECW_R

OUT

<BOOL-type data>

<DINT-type data>

<REAL-type data>

Modbus interface (coil)

Modbus interface (holding register)

Modbus interface (holding register)

Figure C1.6-1 Data setting using the Modbus slave communication function and external communica-tion function blocks

The user uses Modbus Address Builder to assign reference numbers of these Modbus devi-ces to external communication function blocks and read-back variables.

<C1.6 Data setting using Modbus slave communication> C1-20


Table C1.6-1 Modbus devices used for setting and read-backData type (*1) Write register (*2) Read register (*3)

BOOL Coil Input relay

DINT Holding register Input register

REAL Holding register Input register

*1: Assignation in Modbus Address Builder*2: Assign registers to external communication function blocks*3: Assign to readback variables (the READBACK variables in the following figure, "Figure Readback application")

BOOL-type data is set using the following procedure.1. Use Modbus Address Builder to assign a reference number of a coil to ECW_B (BOOL-

type external communication function block).

2. In Modbus Address Builder, assign a reference number of an input relay to a read-backvariable.

3. The Modbus master (an external device) sets an address in a request message based onthe reference number of the coil and writes data.

4. The Modbus master (an external device) sets an address in a request message based onthe reference number of the input relay and reads back data.

Modbus

Application logic

SCSModbus Master

UserApplication

OUT

Address

Address

00032 (reference number)

10032 (reference number)

Internal variable

READBACK

Normal BOOL-type variable

ECW_B

Modbus slave communication

function

Figure C1.6-2 Readback application

SEEALSO For more information about external communication function blocks, refer to:

D5., “Data setting using external communication function blocks” in Safety Control Station Reference (IM32Q03B10-31E)

For more information about Modbus Address Builder, refer to:

C1.5.1, “Definitions in Modbus Address Builder” on page C1-12

For more information about reference numbers, refer to:

“l Data” on page C1-25

l Restrictions on the number of data setting communication operationsusing Modbus slave communication

On receiving a data setting request from the Modbus master, SCS returns a response and re-tains 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 across all Modbus slave communication at the sametime.

• SCS will process the retained data setting requests from the Modbus master four re-quests per second at maximum when the scan period of the application logic is shorterthan 250 ms. When the scan period is 250 ms or longer, SCS will process one request inone scan period. If SCS also retains any request from FCS and/or HIS for data setting viatag name interface in addition to requests from the Modbus master, the SCS will processonly one request in one scan period in the order of acceptance.

• SCS responds with an error if the number of retained requests is four when SCS receivesa request from the Modbus master.

IMPORTANTPeriodical data setting will result in a writing error. Do not set data periodically from the Mod-bus master.

l Confirming data set using Modbus slave communicationWhen setting data from the Modbus master using Modbus slave communication, it is neces-sary to perform readback for checking the data. When performing a readback, the applicationlogic should be designed as shown in the previously listed "Figure Readback application." Da-ta is set to an external communication function block and the data is read back from a varia-ble connected to an OUT (READBACK variable in the previous figure).



C1.7 Messages communicationIn data communication between the Modbus master and SCS, SCS sends a response mes-sage in response to a request message from the Modbus master. When SCS detects an errorrelevant to the communication module, the SCS sends the diagnostic information messagethrough the control bus.

n Request message from the Modbus masterThe request message from the Modbus master is composed of the following information ac-cording to the communication module used.• For serial communication modules

• Slave address

• Function code

• Data

• Error check code

• For Ethernet communication modules

• Transaction identifier

• Protocol identifier

• Field length

• Unit identifier

• Function code

• Data

l Slave address (specific to serial communication modules)A slave address is a station number (1 to 247) that is set for a Modbus slave.The Modbus master communicates only with the SCS with a matching slave address. A re-quest message from the Modbus master is received by all the Modbus slaves. Of these, onlythe SCS whose slave address matches the one in the request message processes the re-quest according to the received message.

l Function codeThe function codes supported on an SCS for request messages are as follows:

Table C1.7-1 Function codes supported on an SCSFunction code

(decimal) Description Maximum size Remark

01 Read Coil Status 512 bits 512 bits = 32 words

02 Read Input Status 512 bits -

03 Read Holding Regis-ters 124 words (62 or 124 data units)

When 16-bit Modbus mastersupport mode is disabled, up to62 data units (32 bits per unit)can be read.When enabled, up to 124 dataunits (16 bits per unit) can beread.


<C1.7 Messages communication > C1-23


Table C1.7-1 Function codes supported on an SCS (Table continued)Function code

(decimal) Description Maximum size Remark

04 Read Input Registers 124 words (62 or 124 data units)

When 16-bit Modbus mastersupport mode is disabled, up to62 data units (32 bits per unit)can be read.When enabled, up to 124 dataunits (16 bits per unit) can beread.

05 Force Single Coil 1 bit Restriction from protocol

06 Preset Single Regis-ter 1 word (16 bits)

Can be used when 16-bit Mod-bus master support mode is ena-bled in SCS Constants Builder.Cannot be used by default.

08 Loopback DiagnosticTest - Can only be used for serial com-

munication modules.

15 Force Multiple Coils 32 bits -

16 Preset Multiple Reg-isters

64 words (*1) (32 or 64 dataunits)

When 16-bit Modbus mastersupport mode is disabled, up to32 data units (32 bits per unit)can be set.When enabled, up to 64 dataunits (16 bits per unit) can beset.

*1: If an even number is specified for the reference number, the maximum size becomes 63 words (63 data units).

l Cautionary notes on function codesNormally, analog data used in SCS are 32-bit signed integer or 32-bit floating point data. Be-cause an input register or holding register is assigned to 32-bit data, one data unit consists oftwo words. Note the following points when using these data:

IMPORTANT• When the Modbus master writes 32-bit floating point data to SCS, writing a NaN (not a

number) or an infinite value (+INF or -INF) by using Preset Multiple Registers (16) doesnot result in an error but the data is not written to the SCS.

• When 16-bit Modbus master support mode is disabled (default setting), specify an oddreference number for Read Holding Registers (03), Read Input Registers (04), or PresetMultiple Registers (16). For the number of registers, specify an even number.

IMPORTANT• When 16-bit Modbus master support mode is enabled, the Modbus master can read and

write data including 16-bit integer data, 32-bit signed integer data, and 32-bit floatingpoint data. However, this requires very complicated ProSafe-RS application.

• You must note that simultaneity of the upper and lower words of 32-bit data is not assuredif you read or write the upper word and the lower word separately in 16-bit Modbus mas-ter support mode.

• When 16-bit Modbus master support mode is enabled, you can specify an odd number oreven number for the reference number and the number of registers for Read Holding



Registers (03), Read Input Registers (04), and Preset Multiple Registers (16). Therefore,error codes 10 and 11 (hexadecimal) do not occur in this mode.

• When 16-bit Modbus master support mode is enabled, the following operations will resultin an error (error code 02).

• Writing only to the upper or lower word of 32-bit floating point data by using PresetSingle Register (06).

• Writing only to the upper or lower word of 32-bit floating point data by using PresetMultiple Registers (16) specifying an odd number for the number of registers.

• Writing only to the upper or lower word of 32-bit floating point data by using PresetMultiple Registers (16) specifying an even number for the reference number.

l DataThis contains the detailed information for SCS to execute the requested function. The addressinformation of Modbus devices (coil, input relay, input register and holding register) is the rela-tive number from the first reference number of each device. Reference numbers of ProSafe-RS start from one. The following table shows the relationship between reference numbersand relative numbers.

Table C1.7-2 Relationship between reference numbers and relative numbersDevice Reference number Relative number

Coil 0xxxx 0xxxx - 1

Input relay 1xxxx 1xxxx - 10001

Input register 3xxxx 3xxxx - 30001

Holding register 4xxxx 4xxxx - 40001

TIP The following table shows an example of the "Device & Address" setting that is specified in the Communica-tion I/O Builder of CENTUM when communicating with CENTUM.

Table C1.7-3 Reference numbers and relative numbers when specifying a holding register fromCENTUM

Communication module Address specified byCENTUM

Relative number Reference number

Serial communication mod-ule

A40001 0000 40001

Ethernet communicationmodule

A40000 0000 40001

SEEALSO For more information about reference numbers, refer to:

“n Modbus device tabs” on page C1-18

l Error check code (specific to serial communication modules)Error check information is used to detect errors in messages occurring during a signal trans-mission (bit errors). A request message sent to SCS contains CRC (Cyclic RedundancyCheck) information. SCS verifies the CRC in a request message and discards the message ifan error is detected.

l Transaction identifier (specific to Ethernet communication modules)The Modbus master assigns a unique identifier to each request message. SCS copies thisvalue to the transaction identifier field of the response message.



l Protocol identifier (specific to Ethernet communication modules)The Modbus master sets this field to the fixed value of 0. SCS copies this value to the proto-col identifier field of the response message.

l Field length (specific to Ethernet communication modules)Byte length of the fields (unit identifier + function code + data).

l Unit identifier (specific to Ethernet communication modules)This field identifies the Modbus slave and is set to the same value as the slave address that isused in the Modbus communication protocol (RTU mode). SCS copies this value to the unitidentifier field of the response message.

SEEALSO For more information about Modbus protocol (RTU mode), refer to:

“n Supported Modbus protocol” on page C2-2

n Response message from SCSSCS sends a response message when it receives a request message from the Modbus mas-ter. The response message that SCS sends differs depending on whether the request mes-sage is sent normally or abnormally. In some cases, SCS does not send a response messagein response to a request message.

l Response message under abnormal conditionsWhen errors other than transmission errors are detected in a request message, or when theSCS is processing the request message, the SCS sends the response message with the fol-lowing information. The format of the response message differs depending on the communi-cation module used.• For serial communication modules

• Slave address

• Function code: The function code in a request message plus 0x80

• Error code

• Error check code

• For Ethernet communication modules

• Transaction identifier

• Protocol identifier

• Field length

• Unit identifier

• Function code: The function code in a request message plus 0x80

• Error code

Details of error codes to indicate abnormal conditions are as follows.

Table C1.7-4 Error codesError code (hexadecimal) Meaning of error

01 Function code error (non-existing function code)

02 Coil, input relay, register number error (out of range)




Table C1.7-4 Error codes (Table continued)Error code (hexadecimal) Meaning of error

03 Error of the number of coils, input relays, or registers (out of range)

04 CPU not started.

05 Another request message with the same transaction identifier is receivedwhile a request is being processed.(*1)

06 Another request message with a different transaction identifier is receivedwhile a request is being processed.(*1)

07 Unsupported diagnostic loop-back code(*2)

10 Even number specified as the register reference number.(*3)

11 Odd number specified as the number of registers (*3)

12

Data setting error• The number of simultaneously writing exceeds four.• Writing size exceeds limit.• Writing to an undefined variable or write-inhibited variable attempted.

13Access error during online change downloadDuring online change download, it is not possible to read from/write to func-tion block instances or variables whose types have been changed.

*1: Specific to Ethernet communication modules*2: Specific to Modicon serial communication modules*3: This error does not occur when 16-bit Modbus master support mode is enabled.

l Response message in normal conditionsWhen the request message is sent normally, the following response message is sent. The re-sponse message differs depending on the content of the request message and the communi-cation module used.

Table C1.7-5 Response messages depending on the content of the request message and the commu-nication module used

Content of request message Communicationmodule

Response message

For functions of single coil statuschange, writing to a single hold-ing register, or loop back

Serial communica-tion module

The same message as the request message

Ethernet communi-cation module

The same message as the request message

For functions of multiple coil sta-tus changes or writing to multipleholding registers

Serial communica-tion module

Slave addressFunction codeError check codeStart numberNumber of coils or holding registers


Transaction identifierProtocol identifierField lengthUnit identifierFunction codeStart numberNumber of coils or holding registers

In the case of read function Serial communica-tion module

Slave addressFunction codeError check codeRead data


Transaction identifierProtocol identifierField lengthUnit identifierFunction codeRead data



l Cases where no response is madeSCS 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 does not correspond to the slave address set onthe communication module

• The time interval between receiving one character and the next character is longer thanthe setting value of the reception inter-character timer

• A protocol related error occurs (for example, a transmission is performed just when beingresponding to a request)

• Definitions of the serial communication module are being online change downloaded

• Definitions of Modbus communication are being changed

l Response timeThe response time refers to the time from when SCS receives a request message to when itstarts to transmit the response message. The transmission time is not included.

Response time = ( Message receiving and sending processing time) + (Modbus message reading and writing processing time)

Set the message receiving and sending processing time to 20 ms.The time taken by Modbus message reading and writing processing varies as shown in thefollowing table, according to the scan period of application logic and the number of communi-cation ports. The Modbus message reading and writing are processed during the idle time af-ter the processing of application logic is completed.

Table C1.7-6 Modbus message processing time and the combination of scan period of application log-ic and the number of communication ports

Scan period Number of communicationports per SCS

Processing time of Modbus message reading andwriting

200 ms or lon-ger

- 0 to the scan period of application logic

Shorter than200 ms

2 ports or less 0 to the scan period of application logic

3 ports or more 0 to (The scan period of application logic x 2)

TIP • For the Ethernet communication module, take the number of ports that appear in the above descriptionfor the number of connections.

• If you install two serial communication modules or Ethernet communication modules or mix of both in anSCS and use two ports per module, the number of communication ports per SCS is regarded as three ormore.



IMPORTANT• The longest time it takes for data to be read by the Modbus master is as follows:

Maximum data update time = transmission time + scan period of external connection function

• If a writing request from the CENTUM integration function coincides with those from aModbus master on another port, notification of the writing request to the application logicwill be delayed for the number of writing requests. Therefore, the longest time it takes fornotification of a write operation from the Modbus master to reach the SCS application log-ic is as follows:

Maximum data update time = transmission time + scan period of the application logic x

number of writing requests from the external connection function

n Diagnostic information messagesIf a communication module is faulty, the SCS send a diagnostic Information message toSENG and/or HIS through the control bus. This section describes the SCS diagnostic Infor-mation messages.

l Error occurrence/recovery to normal state on communication moduleWhen an error occurs in the communication module, or when the module recovers from anerror, an IOM Fail diagnostic information message, or an IOM Recover diagnostic informationmessage, respectively, is sent through the control bus.The configuration error occurs if the communication driver cannot operate due to configura-tion mismatch. For example, this error occurs if the communication driver has not been down-loaded to the communication module or if an application program different from the definedcommunication driver has been downloaded.

TIP Communication modules ALR111, ALR121, and ALE111 must be loaded with a driver for Modbus communi-cation.After you replace these communication modules, perform IOM download to the new modules.

However, if the communication driver of SCS is already downloaded to the replaced module, the modulestarts normally. In this case, you do not need to perform IOM download.

SEEALSO For more information about diagnostic information messages for communication module error occurrence and

recovery to normal state, refer to:

3.1, “Safety Control Station Error Occurrence and Recovery Messages (Message Numbers 0001through 0094)” in Messages (IM 32Q02B10-31E)

l When a communication error occursWhen a communication error occurs, no system alarm message is sent because the Modbusmaster is assumed to handle the error.

l When downloading the communication driverWhen downloading the communication driver to the communication module, system alarmmessages indicating the start of the download, and the completion or abnormal termination ofthe download, are sent through the control bus.



SEEALSO For more information about system alarm messages for communication driver downloads, refer to:

3.2, “Safety Control Station Status Change Related Messages (Message Numbers 0450 through 0480)”in Messages (IM 32Q02B10-31E)

l When a communication module is added onlineCommunication modules can be added or removed online. When a communication module isadded, diagnostic information messages (IOM Fail, and then IOM Recover) are sent throughthe control bus.

SEEALSO For more information about diagnostic information messages for communication module error occurrence and

recovery to normal state, refer to:

3.1, “Safety Control Station Error Occurrence and Recovery Messages (Message Numbers 0001through 0094)” in Messages (IM 32Q02B10-31E)



C1.8 TroubleshootingIf a communication module error occurs, you can use the SCS Maintenance Support Tool toacquire information on the communication module and communication error information. Thissection describes typical troubleshooting cases.

n The status display window shows the status of ALR111/121 orALE111 in red

If the status of the communication module appears in red in the status display window of theSCS Maintenance Support Tool, check the error code that is related to the input/output mod-ule in the diagnostic information message.

n There is no response and communication fails• Check if the transmission specifications are consistent with those of the master.

• Check if the cable wiring complies with the specifications.

• Analyze the communication log for the cause of the communication error by using theSCS Maintenance Support Tool.

• Check if there is enough CPU time available. Response may be delayed when the CPUload is high.

n A response message under abnormal conditions is received• Check if the function code that is included in the message is correct.

• Check if the Modbus master sent another request message to the SCS before receiving aresponse message through a given connection. (Specific to Modbus TCP)

n Connection cannot be established and communication fails(specific to Modbus TCP)

• Check if the destination IP address and port number are correct.

• If the Modbus master fails without a notification of the communication termination (socketclose) to the Modbus slave while they are communicating through an Ethernet communi-cation module, the slave becomes ready for reconnection in up to 34 seconds.

<C1.8 Troubleshooting > C1-31


C2. Serial communication modulesSCS uses a serial communication module to send and receive data to and from the Modbusmaster (external device).

<C2. Serial communication modules> C2-1


C2.1 Connection between the Modbus masterand SCS

This section describes the connection configuration between the Modbus master and SCS, in-cluding the configuration of serial communication modules and cable connection.

n Connection configuration of the serial communication moduleThe following is an example of connection using YOKOGAWA STARDOM autonomous con-troller FCN (Field Control Node) as the Modbus master.

RS-232C

RS-232C

MODEM

MODEM MODEM

Modbus master (STARDOM FCN)

Serial communication

module (NFLR111)


(ALR111)


(ALR111)

Modbus Slave (SCS)

Modbus Slave (SCS)

Figure C2.1-1 Example of connection between the Modbus master and SCS (ALR111) (using a STAR-DOM FCN as the Modbus master)

An SCS communicates with the STARDOM FCN, the Modbus master, via a serial communi-cation module (NFLR111 and ALR111 in the previous example).

n Supported Modbus protocolThe Modbus protocol defines communication procedures and message formats between onemaster and multiple slaves when performing serial communication.The Modbus protocol for the SCS Modbus slave communication has the following features:• Only the master can initiate communication via the Modbus protocol. The master re-

quests data reference or setting, and the slave responds to the request.

• The signal transmission between the master and slaves can be performed in either theRTU (Remote Terminal Unit) mode or the ASCII mode. SCS supports the RTU mode only.

n Transmission specifications of serial communication modulesThe SCS transmission specifications when using a serial communication module are as fol-lows:

<C2.1 Connection between the Modbus master and SCS > C2-2


Table C2.1-1 Transmission specifications when using a serial communication module

Item Description(*1)Builder

specifica-tion(*2)

Remark

InterfaceRS-232C

YesALR111

RS-422/RS-485 (4-wiresystem) ALR121

Synchronization method Start-stop synchronization -

Baud rate 1200, 2400, 4800, 9600,[19200], 38400 bps Yes

Start bits Fixed to 1 -

Data bits 7 to [8] - Fixed to 8 in Modbus RTUmode

Stop bits [1], 2 Yes

Parity None, Odd, [Even] Yes

Control Line

RS control Yes, [No] Yes Valid only for ALR111

DR check [Yes], No Yes Valid only for ALR111

CD check Yes, [No] Yes Valid only for ALR111

Time monitoring

Transmission ena-ble monitoringtime

0 to 99990 (ms)[1000]Specify in units of 10 ms

- Fixed to 1000 ms for Mod-bus

Reception charac-ter interval timer

0 to 99999 (ms)[10]Specify in units of 1 ms

Yes

Character internalmonitoring timeout [Do not set], Set -

Fixed to Do not set forerrors in the RTU mode ofModbus

Text frame

Reception startcharacter 1 character, [None] - Fixed to None for Modbus

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

Maximum numberof transmit charac-ters

Up to 512 bytes -

Maximum numberof receive charac-ters

Up to 512 bytes -

Station number 1 to 247 Yes

Option 1 to 4 Fixed to 0 -

MODBUS RTU/ASCII RTU(*3) -

*1: [ ] indicates a default value (recommended value).*2: Yes: Can be specified.

-: Cannot be specified.*3: Only the RTU mode is supported. The ASCII mode is not supported.

n Mounting of a serial communication moduleSCS uses ALR111/ALR121, as a serial communication module. ALR111/ALR121 is used bymounting 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-485cable.



• ALR111: Serial communication module (RS-232C) • ALR121: Serial communication module (RS-422/RS-485)

IOM

IO

M

ALR

111 IO

M

IOM

IO

M

IOM

IO

M

Two ports RS-232C

SCS

I/O modules

Modbus master

PS

M

PS

M

CP

UC

PU

Figure C2.1-2 Example of mounting a serial communication module to SCS

l Status displayThe operation status of serial communication modules can be checked by observing the sta-tus display LEDs on the module or a system status display view on HIS.

SEEALSO For more information about the types and functions of status display LEDs of communication modules, refer

to:

“■ Inspection of LEDs” in 7.1.1, “Inspection by Status Display LEDs” in Safety Control Stations (Hard-ware) (IM 32Q06C10-31E)

n Cable connection when using ALR111You can connect the Modbus master and ALR111 by using a modem.

SEEALSO For more information about connections and connectors of ALR111, refer to:

“■ ALR111: RS-232C Interface” in 5.5.1, “Connection of RS-232C Communication Module” in SafetyControl Stations (Hardware) (IM 32Q06C10-31E)

For more information about modem connection, refer to:

“■ Modbus Connection” in 5.5.1, “Connection of RS-232C Communication Module” in Safety ControlStations (Hardware) (IM 32Q06C10-31E)

n Precautions when wiring signal linesThis section describes the precautions when wiring the ALR111 signal lines.

SEEALSO For more information about ALR111 connector signals, refer to:

“■ ALR111: RS-232C Interface” in 5.5.1, “Connection of RS-232C Communication Module” in SafetyControl Stations (Hardware) (IM 32Q06C10-31E)

l CD signal lineWhen the CD signal is ON, data is being transmitted to the receiver. Wire a signal line thatturns ON when the connection destination sends data to the CD signal. In general, wire theRS 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, wirea signal that is always ON, for example the ER signal line of the ALR111 itself, to the CD sig-nal pin.When the CD check is enabled, transmission is not allowed when the CD signal is ON (be-cause data is being transmitted from the other end of the line). Turn OFF the CD check if theCD signal line is always in the ON status. The check is turned OFF by default.



l ER (DTR) signal lineThe ER signal turns ON after the serial communication module has completed the startupprocessing and is ready to receive and send data. Use this signal to judge whether or not theserial communication module can receive data at the connection destination.

l DR (DSR) signal lineThe DR signal line is used to judge whether the device to which the ALR 111 is wired can re-ceive data.When the DR check is enabled, data can be sent while the DR signal is ON. Wire a signal linethat turns ON when the connected device can receive data to the DR signal pin.To disable this check, specify [No] for the DR check, or wire a signal line that is always ON tothe DR signal pin.

l RS (RTS)/CS (CTS) signal linesFor RS signal setting, either [No] (always ON) or [Yes] (ON at transmission) can be specifiedfor the RS control. If the RS signal connected to the device should be ON while transmittingand stay OFF otherwise, specify [Yes] for the RS control.Data is transmitted when the CS signal is ON. Wire the line in such a way that the CS signalline turns ON at transmission.



C2.2 Definitions in I/O Parameter BuilderThis section explains the settings of communication modules to perform Modbus slave com-munication. Settings for the serial communication modules can be configured in the Port 1 taband Port 2 tab of I/O Parameter Builder.

SEEALSO For more information about display method and window configuration for the I/O Parameter Builder, refer to:

4.4, “I/O Parameter Builder” in Engineering Reference (IM 32Q04B10-31E)

For more information about parameter tabs in the serial communication module, refer to:


n Port 1, Port 2 tabThe 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 willrestart after download.

Table C2.2-1 Port 1, Port 2 tabTitle Description Remark

Baud Rate Set the baud rate -

Stop Bits Set the stop bit -

Parity Specify the type of parity -

Control Line RS Control Specify whether or not to performRS control during ALR111 trans-mission

Valid only for ALR111

DR Check Specify whether or not to performDR signal check during ALR111transmission


CD Check Specify whether or not to performCD signal check during ALR111transmission


Reception Inter-Charactertimer

Specify the monitoring time of re-ception character interval during re-ception by the ALR111/ALR121

-

Station Number Specify the slave address of theModbus slave

-

Option 1 to 4 Option items Fixed to 0.

l Baud RateSpecify the baud rate of communication. Select from 1200, 2400, 4800, 9600, 19200 and38400 bps. The default is 19200 bps.

l Stop BitsSpecify the stop bits of communication. Select 1 bit or 2 bits. The default is 1 bit.

l ParitySpecify the parity. Select None, Odd or Even. The default is Even.

<C2.2 Definitions in I/O Parameter Builder > C2-6


l RS ControlSpecify whether or not to perform RS control during ALR111 transmission. The setting is onlyvalid 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 theALR111.

• With RS controlTurn the RS signal cable ON when data is transmitted from the ALR111 and OFF at thecompletion of transmission.

l DR CheckSpecify whether or not to perform DR signal line check during ALR111 transmission. The set-ting 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 checkALR111 transmission data only if the DR signal cable is ON. A no-response error occurs ifthe DR signal does not turn ON after the transmission enable monitoring time haselapsed (the response data is discarded).

The DR signal is used to connect to the ER (data terminal ready) signal line to communicatewith and to determine whether or not the ER signal line at the connection destination is ableto receive character data (normal operation). If the ER signal line cannot be used, set "with-out DR check" or wire the line in such a way that the DR signal line is switched ON at alltimes (*1) .

*1: For example, connect the RS signal line to the DR signal pin of its own.

l CD CheckSpecify whether or not to perform CD signal check during ALR111 transmission. The default isnot to perform the CD check function.• Without CD check

ALR111 transmission data regardless of the status of the CD signal cable.

• With CD checkALR111 transmission data if the CD signal is OFF. A no-response error occurs if the CDsignal does not turn OFF after the transmission enable monitoring time has elapsed.

l Reception Inter-Character timerThe reception Inter-Character timer (reception Inter-Character timeout setting value) is a func-tion that monitors the time between characters are received when the ALR111/ALR121 mod-ule receives data. In the Modbus (RTU mode) binary communication, the communication isregarded as completed if this duration of time or longer elapses between two character recep-tions.If the communication is performed through a modem with data buffering or similar functionali-ty, specify this value taking into account the communication delay (inter-character delay) dueto buffering by the modem. This also affects the communication time. However, this affectsthe communication time because the communication is regarded as completed based on thistime.

Default: 10 msSetting range: 0 to 99999 ms



IMPORTANTIf multiple slave devices are connected on the same line, set the time so that it corresponds tothe transmission of approximately 20 characters in the serial communication (20 ms for 9600bps, 10 ms for 19200 bps). If there is any slave device with a Reception Inter-Character Timervalue larger than those of other slave devices, reception is not performed properly on that de-vice and a non-response error occurs.

l Station NumberSpecify the slave address of the Modbus slave.Default: 1Setting range: 1 to 247

l Option 1 to 4Always set 0 for these options.Default: 0 (for all)



C3. Ethernet communication modulesSCS uses an Ethernet communication module to send and receive data to and from the Mod-bus master (external device).

<C3. Ethernet communication modules> C3-1


C3.1 Connection between the Modbus masterand SCS

This section describes the connection configuration between the Modbus master and SCS, in-cluding the configuration of Ethernet communication modules and cable connection.

n Connection configuration of the Ethernet communication moduleThe following figure shows an example of a connection using the YOKOGAWA STARDOMautonomous controller FCN (Field Control Node) as the Modbus master.

Ethernet

Modbus master(STARDOM FCN)

HUB

Ethernet communication module

(ALE111)

Ethernet communication module

(ALE111)

Modbus Slave(SCS)

Modbus Slave(SCS)

Figure C3.1-1 Example of a connection between the Modbus master and SCS (ALE111) (using a STAR-DOM FCN as the Modbus master)

An SCS communicates with the STARDOM FCN, the Modbus master, through an Ethernetcommunication module (ALE111 in the previous example).

n Supported Modbus protocolThe Modbus protocol that is supported on Ethernet communication modules is the ModbusTCP protocol. The Modbus TCP protocol uses TCP/IP (Ethernet) for Modbus slave communi-cation.• The Modbus TCP protocol can be used to communicate with multiple Modbus slaves at

almost the same time.

• The Modbus master can send a request message to multiple Modbus slaves at the sametime and wait for response messages.

n Transmission specifications of Ethernet communication modulesThe SCS transmission specifications when using an Ethernet communication module are asfollows:

Table C3.1-1 Transmission specifications when using an Ethernet communication module

Item DescriptionBuilder

specifica-tion(*1)

Remark

InterfaceEthernet (IEEE802.3) - -

10BASE-T - -

Baud rate 10 Mbps - Fixed to 10 Mbps(*2)


<C3.1 Connection between the Modbus master and SCS> C3-2


Table C3.1-1 Transmission specifications when using an Ethernet communication module (Table con-tinued)

Item DescriptionBuilder

specifica-tion(*1)

Remark

Transmission method Half-duplex - Fixed to half-duplex

Port number 502 YesModbus TCP port num-ber. The default value is502. (*3)

Number of connections 2 - -

Number of transactions per connection(*4) 1 -

When two connectionsare used, the number oftransactions per SCS is 2.

Data format Binary - Fixed to binary

Option 1 to 40 to 0xFFFFFFFF or-2147483648 to2147483647

Yes Reserved for extensions

*1: Yes: Specification required-: Specification not required

*2: Network auto-negotiation cannot be specified in hub settings.*3: The default value is recommended.*4: This is the number of request messages that SCS can process per connection. The Modbus master should not send more

request messages to an SCS than this value, regardless of the transaction identifier of the request message. If sent, the SCSsends a response message with an error code set.

n Mounting of an Ethernet communication moduleSCS uses the ALE111 as an Ethernet communication module. Install the ALE111 in the SCSand connect it to the Modbus master by using an Ethernet cable.

• ALE111: Ethernet communication module

IOM

IOM

ALE

111IO

MIO

MIO

MIO

MIO

MOne port

SCS

I/O modules

Modbus master

PS

M

PS

M

CP

UC

PU

Figure C3.1-2 Example of mounting an Ethernet communication module to SCS

IMPORTANTWhen using ALE111, use the style S1 module with unit revision U:2 or later. The unit revisionis indicated on the top of the module. However, the unit revision is not indicated if it is U:0.

l Status displayThe operation status of Ethernet communication modules can be checked by observing thestatus display LEDs on the module or a system status display view on HIS.

SEEALSO For more information about types and functions of status display LEDs of communication modules, refer to:

“■ Inspection of LEDs” in 7.1.1, “Inspection by Status Display LEDs” in Safety Control Stations (Hard-ware) (IM 32Q06C10-31E)

<C3.1 Connection between the Modbus master and SCS> C3-3


C3.2 Definitions in the I/O Parameter BuilderThis section explains the settings of Ethernet communication modules to perform Modbuscommunication. Settings for the Ethernet communication modules can be configured in theModule tab of I/O Parameter Builder.



n Module tab of Ethernet communication moduleThe following items can be set in the Module tab of the Ethernet communication module.The settings of each item can be changed by using online change download, but the corre-sponding module restarts after online change download.

Table C3.2-1 Display items of Module tab of Ethernet communication moduleTitle Description Remarks

Node Number The node number of the node in which themodule is mounted

Defined in I/O WiringView

Slot Number The slot number of the slot in which themodule is mounted


Device The model name of the module Defined in I/O WiringView

Dual-Redundant Whether the module is used in a single ordual-redundant configuration

The module cannot bedual-redundant

Device Number The device number that is assigned to themodule


Table C3.2-2 Setting items of Module tab of Ethernet communication moduleTitle Description Remarks

Connection Device Types of connection devices -

Comment A comment regarding the module -

IP Address The IP address of the module -

Subnet Mask The subnet mask of the module -

Default Gateway The default gateway address of the module -

Port Number The TCP/IP port number -


l Connection DeviceSet the type of connection device.Select SCSMDTCP when the Modbus slave communication function should be used.

Default value: SCSMDTCPSCSMDTCP: Modbus TCP masterSCSDPTCP: DNP3 master (Selectable only when the version of SCSU1 is R3.02.20 or lat-

er.)

<C3.2 Definitions in the I/O Parameter Builder> C3-4


TIP If an attempt is made to change the connection device and the selected port number is not the default, thefollowing dialog box appears:

Figure C3.2-1 Connection Device dialog box

Yes: The connection device is changed and the port number is changed to the default.

No: The connection device is changed but the port number is not changed.

Cancel: Neither the connection device nor port number is changed.

l CommentA comment regarding the Ethernet communication module can be entered. This comment canbe entered using up to 24 single-byte characters or 12 double-byte characters.

l IP AddressSet the IP address of the Ethernet communication module. Enter a desired IP address.

Default: This field is empty by default; be sure to enter an IP address. If no value isentered, an error occurs when you try to save the settings in the builder.

Format: nnn.nnn.nnn.nnnSetting range: 1.0.0.1 to 223.255.255.254

However, do not set the following IP addresses:• Host address digits are all zeros or all ones in binary form.

(Examples: 192.168.1.0 and 192.168.1.255 when the subnet mask is255.255.255.0)

• Any of the numbers delimited with a period has leading zeros.(Examples: 192.168.08.09 and 192.168.008.009)

l Subnet MaskSet the subnet mask of the Ethernet communication module. Enter a desired subnet mask.

Default: This field is empty by default; be sure to enter a subnet mask. If no value isentered, an error occurs when you try to save the settings in the builder.


However, do not set the following subnet masks:• Values less than 255.0.0.0 for a class A IP address

(Example: 128.0.0.0)

• Values less than 255.255.0.0 for a class B IP address(Example: 255.128.0.0)

• Values less than 255.255.255.0 for a class C IP address(Example: 255.255.128.0)



l Default GatewaySet the gateway address of the Ethernet communication module. Enter a desired gateway ad-dress.

Default: BlankFormat: nnn.nnn.nnn.nnnSetting range: 1.0.0.1 to 223.255.255.254

However, do not set the following gateway addresses:• Host address digits are all zeros or all ones in binary form.

(Examples: 192.168.1.0 and 192.168.1.255 when subnet mask is255.255.255.0)

• Network address digits do not match the IP address.(IP address is 192.168.1.1 and default gateway address is 192.168.2.2when the subnet mask is 255.255.255.0.)

• Any of the numbers delimited with a period has leading zeros.(Examples: 192.168.08.09 and 192.168.008.009)

l Port numberSet the port number for Modbus TCP.

Default: 502Setting range: 0 to 65535

l Option 1 to 4You must set 0 for these options.Default: 0 (for all)



D. DNP3 slave functionThe DNP3 slave function uses DNP3, which is an open protocol, to let the SCS operate asthe DNP3 slave and communicate with the DNP3 master such as the SCADA.This section describes an overview of the DNP3 slave function and explanation of this func-tion, engineering and maintenance on the SENG, and DNP3 communication function block(hereinafter referred to as DNP3 communication FB).The DNP3 slave function is supported only by SCSU1 of R3.02.20 or later.

SEEALSO For more information about DNP3 Field Device Profile of the SCS, refer to:

Appendix 1., “DNP3 Field Device Profile” on page App.1-1

<D. DNP3 slave function > D-1


D1. Overview of DNP3 slave functionThe DNP3 slave function of the SCS allows the DNP3 master to refer data from the SCS orset data to the SCS through DNP3 communication. The DNP3 slave function of an SCS doesnot affect the safety functions of it.To perform DNP3 communication with the DNP3 master, install the Ethernet communicationmodule (model: ALE111) on an SCS node.To use the DNP3 slave function, use DNP3 communication FBs. By assigning instances ofDNP3 communication FBs to DNP3 data, SCS data can be referred or set from the DNP3master.The SCS generates and buffers an event that includes a time stamp and data the moment avariable of the application logic changes. This prevents missing data when a communicationfailure occurs, because the DNP3 master can read the relevant event from the SCS's eventbuffer following the recovery.

n Precautions for using the DNP3 slave functionThe following shows precautions when using the DNP3 slave function.• The DNP3 slave function is supported only by SCSU1 of R3.02.20 or later.

• To use the DNP3 slave function, you need the FAST/TOOLS Integration EngineeringPackage.

• The DNP3 event buffering function cannot be used simultaneously with the data bufferingfunction in Integration with FAST/TOOLS.

<D1. Overview of DNP3 slave function > D1-1


D1.1 DNP3 communication systemconfiguration and components

The DNP3 communication system is configured in such a way that the DNP3 master is con-nected to the DNP3 slave, such as the SCS or any third-party controller, through Ethernet.The SENG and SCS are connected through the Vnet/IP-Upstream network.The following figure shows an example of configuration of a DNP3 communication systemwhere the SENG and SCS are connected through the Vnet/IP-Upstream network.

SENGDNP3Master

Ethernet

Controller from other companies

SNTPServer

Wide area network(FO, Wireless, and so on.)

Vnet/IP-Upstream

SCS(SSC57)

(ALE111)

SNTPServer

SCS(SSC57)

(ALE111)



Figure D1.1-1 Example of configuration of a DNP3 communication system where the SENG and SCSare connected through the Vnet/IP-Upstream network

The following figure shows an example of configuration of a DNP3 communication systemwhere the SENG is connected to the SCS only when required for engineering purposes.

<D1.1 DNP3 communication system configuration and components > D1-2


SENG

DNP3Master

Ethernet



SCS(SSC57)

(ALE111)

SCS(SSC57)

(ALE111)


SENG is connected locally only when engineering is done.

Vnet/IP-Upstream

Figure D1.1-2 Example of configuration of a DNP3 communication system where the SENG is connec-ted to the SCS only when required for engineering purposes

Any system used in DNP3 communication requires the following components:• DNP3 master

It uses the DNP3 protocol to communicate with the DNP3 slave, such as the SCS or anythird-party controller.

• SCSIt uses the DNP3 protocol to communicate with the DNP3 master. One SCS can be con-nected to one DNP3 master.The SCS performs DNP3 communication through the Ethernet communication module(model: ALE111). One ALE111 per SCS can be used for DNP3 communication.

• SENGFor the SCS to be able to use the DNP3 slave function, engineering must be performedon the SENG. The SENG supports remote engineering in the Central Control Room, orengineering based on local connection to the SCS. The SENG and SCS are connectedthrough the Vnet/IP-Upstream network.

• Controller from other companiesIt uses the DNP3 protocol to communicate with the DNP3 master.

• SNTP serverIn an environment where SNTP servers can be installed, use SNTP servers to synchron-ize the time of the DNP3 master and that of the SCS. Connect UTC-synchronized SNTPservers to the Ethernet network to which the DNP3 master is connected, and also to theVnet/IP-Upstream network to which the SCS is connected, to synchronize the time of theDNP3 master and that of the SCS.

<D1.1 DNP3 communication system configuration and components > D1-3


D1.2 Operating EnvironmentThis section describes the SCS and SENG operating environments that are needed to usethe DNP3 slave function.

n SCS operating environmentThe following table shows the SCS operating environment needed to use the DNP3 slavefunction.

Table D1.2-1 SCS operating environmentItem Description

Station SCSU1

CPU SCP451: Vnet/IP firmware revision R19 or later

System program R3.02.20 or later

Communication interface module ALE111

SEEALSO For more information about Transmission specifications of Ethernet communication modules, refer to:

“■ Transmission Specifications of Ethernet Communication Modules” in 2.17.3, “DNP3 Slave Function”in Engineering Guide (IM 32Q01C10-31E)

n SENG operating environmentThe following table shows the SENG operating environment that is needed to use the DNP3slave function.

Table D1.2-2 SENG operating environmentItem Description

Computer According to the ProSafe-RS operating environment

ProSafe-RS R3.02.20 or later

Package Safety System Generation and Maintenance Function Package(CHS5100)FAST/TOOLS Integration Engineering Package (CHS5700-V11)

Control bus card VI702: Vnet/IP firmware revision R19 or later

IMPORTANTTo use the DNP3 slave function, the FAST/TOOLS Integration Engineering Package is re-quired.

<D1.2 Operating Environment > D1-4


D2. DNP3 slave function of SCSThe DNP3 slave function of the SCS comprises the following:• Referencing and setting data

• Event buffering

• Time synchronization

The DNP3 slave function accesses data during idle time when no safety function is active, soit does not affect any of the safety functions.

<D2. DNP3 slave function of SCS > D2-1


D2.1 Data access using the DNP3 slavefunction

To reference and set any variable of application logic of the SCS from the DNP3 masterthrough DNP3 communication, assign an instance of DNP3 communication FB connected tothe variable of the application logic, to DNP3 data.DNP3 data is the virtual data of SCS consisting of the data type and Index.The following six different data types are available:• Binary Input

• Binary Output

• Binary Counter

• Frozen Counter

• Analog Input

• Analog Output

For the Index, a sequential value of 0 to 499 is appended for each data type.Once an instance of DNP3 communication FB is assigned to the Index for each data type, theDNP3 master can access the variable of the application logic as DNP3 data. An instance ofDNP3 communication FB can be assigned to any Index. Note, however, that the total numberof assignable instances of DNP3 communication FBs is limited to 1,000 for all data typescombined. For the Frozen Counter, it is not necessary to assign an instance to the Index, be-cause there is one Frozen Counter corresponding to one Binary Counter.The following figure shows the correspondence of DNP3 data and DNP3 communication FBs.

543210

10

43210

43210

3210

BinaryInput

56

BinaryOutput

BinaryCounter

AnalogInput

AnalogOutput

Application Logic

Correspondence

DNP3 Data

DNP3 Communication Function

DNP3 Slave (SCS)

DNP3 Master (SCADA)

Data access by Index in each data type

Request

Response

Figure D2.1-1 Correspondence of DNP3 data and DNP3 communication FBs

The DNP3 communication function executes processes relating to the DNP3 slave, such asreferencing, setting and freezing DNP3 data, and responding to and deleting events.

<D2.1 Data access using the DNP3 slave function > D2-2


n Data referencing and setting from DNP3 masterUse DNP3 communication FBs to reference data from or set data to the SCS from the DNP3master. The following table shows the relationship between the DNP3 communication FBsand DNP3 data that can be referenced and set from the DNP3 master.

Table D2.1-1 Relationship between the DNP3 communication FBs and DNP3 data that can be refer-enced and set from the DNP3 master

DNP3 communication FB DNP3 data Referencing and setting fromDNP3 master

DNP3_BI Binary Input Referencing

DNP3_BO Binary Output Referencing, setting

DNP3_CT_16, DNP3_CT_32 Binary Counter, Frozen Counter Referencing (*1)

DNP3_AI_16, DNP3_AI_32,DNP3_AI_SF

Analog Input Referencing

DNP3_AO_16, DNP3_AO_32,DNP3_AO_SF

Analog Output Referencing, setting

*1: Binary Counter can only be referenced, whereas the Frozen Counter can be referenced and cleared.

SEEALSO For more information about Engineering method of DNP3 data, refer to:

D3.5, “Definition of DNP3 data” on page D3-12



D2.1.1 Referencing DNP3 dataThe following describes how to reference the DNP3 data of the SCS from the DNP3 master.• Index specification

The DNP3 master obtains from the SCS the DNP3 data of the specified Index or Indexrange. If the specified Index has no instance of DNP3 communication FB assigned to it,or an out-of-range Index (other than 0 to 499) is specified, the SCS returns the followingerror:

IIN2.2 PARAMETER_ERRORMoreover, when there is a reference request for Analog Input, Analog Output and BinaryCounter, if a data type different from the data types (16 bit, 32 bit, float) is specified in theSCS, the SCS returns the following error:

IIN2.2 PARAMETER_ERROR• Batch specification (Class 0 specification)

The DNP3 master obtains from the SCS all DNP3 data to whose Index an instance ofDNP3 communication FB is assigned.Whether to include or not include the Frozen Counter in the response in the case of batchspecification can be set.

SEEALSO For more information about Precautions when assigning DNP3 data, refer to:

“■ Precautions When Assigning DNP3 Data” in 2.17.3, “DNP3 Slave Function” in Engineering Guide (IM32Q01C10-31E)

For more information about specifying whether or not to include the Frozen Counter in the response for batchspecifications, refer to:

D3.3, “DNP3 slave setting” on page D3-8

n Referencing DNP3 dataDNP3 data is referenced by the DNP3 communication function of the SCS. The DNP3 com-munication function is processed during the idle time after the processing of application logicis completed. Accordingly, DNP3 data is referenced with a delay up to the scan period of ap-plication logic. When a variable of the application logic are updated, it takes time up to thescan period of the external connection function before the value can be referenced.The following figure shows the execution timing of the DNP3 communication function.

Processing of application logic

DNP3 Communication Function

Scan period of application logic

Time

Figure D2.1.1-1 Execution timing of DNP3 communication function



D2.1.2 Setting DNP3 dataThe following describes how to set DNP3 data to the SCS from the DNP3 master.• Direct Operate - With Acknowledgment

DNP3 data is set to the SCS according to the Operate command from the DNP3 master.The SCS returns the setting result (Success/Error) to the DNP3 master as an Acknowl-edgment.

• Direct Operate - No AcknowledgmentDNP3 data is set to the SCS according to the Operate command from the DNP3 master.The SCS does not return the setting result (Success/Error) to the DNP3 master. Use theDNP3 master to acknowledge the setting result based on a change event or readback.

• Select Before OperateDNP3 data is set by using the Operate command after the Select command with OperateParameter has been notified to the SCS from the DNP3 master. The SCS accepts onlythe Operate command for the request reserved by the Select command. If no Operatecommand is received within a specified period, or the received Operate command is notfor the reserved request, the SCS cancels the Select command and will no longer exe-cute the Operate process for any subsequently received Operate command.Only one Select command can be accepted. If multiple Select commands are received,the last Select command will be accepted.

IMPORTANT• When setting data from the DNP3 master, use the Direct Operate - With Acknowledgment

command unless there is a specific reason.

• If the specified Index has no instance of DNP3 communication FB assigned to it, or anout-of-range Index (other than 0 to 499) is specified, the SCS returns the following error:

IIN2.2 PARAMETER_ERROR

The following figure shows the sequence for each DNP3 data setting method.

DNP3 Master SCS

Operate

Acknowledgement

Operate Select

Acknowledgement

Operate

Acknowledgement

Direct Operate-No AcknowledgementDirect Operate Select Before Operate

DNP3 Master SCS DNP3 Master SCS

Figure D2.1.2-1 Sequence for each DNP3 data setting method

SEEALSO For more information about Precautions when setting data from the DNP3 master, refer to:

“■ Data Settings from the DNP3 Master” in 2.17.3, “DNP3 Slave Function” in Engineering Guide (IM32Q01C10-31E)



n Setting DNP3 dataDNP3 data is set by the DNP3 communication function.The following figure shows how a DNP3 data setting request is processed.

DNP3 Master DNP3Communication Function

Data setting request

Success

Data setting processing

Application Logic

Acknowledgement is returned before variable of application logic is set

SCS

Figure D2.1.2-2 How a DNP3 data setting request is processed

When the DNP3 master accepts a data setting request for the SCS, the SCS's DNP3 commu-nication function issues a data setting request to the application logics of the SCS. The SCS'sDNP3 communication function returns an acknowledgment to the DNP3 master before thedata is set by the application logics of the SCS.The time that is taken for the variable of the application logic to be updated after the DNP3communication function receives the setting request, depends on the number of data settingrequests from the Modbus and other external connection functions.

SEEALSO For more information about Maximum time before the set value can be referenced, refer to:

“● Maximum Time Before the Set Value Can Be Referenced” in “■ Data Settings from the DNP3 Master”in 2.17.3, “DNP3 Slave Function” in Engineering Guide (IM 32Q01C10-31E)

For more information about Execution timing of DNP3 communication function, refer to:

“n Referencing DNP3 data” on page D2-4

n Precautions when setting DNP3 dataThis section describes the precautions when setting DNP3 data.

l Limitations on data setting using DNP3 communicationOn receiving a data setting request from the DNP3 master, SCS returns a response and re-tains the request it accepted.• Up to four data setting requests using DNP3 communication can be retained. A Freeze &

Clear request is also considered a data setting request.

• SCS will process the retained data setting requests from the DNP3 master four requestsper second at maximum when the scan period of the application logic is less than 250ms. If the scan period exceeds 250 ms, SCS will process one request in one scan period.



• If SCS also retains any request from the Modbus master or other external connection de-vice for data setting, the SCS will process only one data setting request from either fromthe external connection device or from the DNP3 master in the order of acceptance.

• SCS responds with a following status code if the number of retained requests is fourwhen SCS receives a request from the DNP3 master:

PROCESSING_LIMITEDSCS destroys any data setting request without acknowledgment.

SEEALSO For more information about Freeze & Clear request, refer to:

“n Freeze & Clear command” on page D2-8

l Binary Output limitThe SCS's Binary Output supports latch output type operation only. Pulse output operationcannot be used.



D2.1.3 Freeze command, Freeze & Clear commandThe SCS supports the DNP3 Freeze command and Freeze & Clear command.

n Freeze commandThe Freeze command is used to save the current value of the Binary Counter. After acceptinga Freeze request from the DNP3 master, the SCS copies the current values of all BinaryCounters to the Frozen Counter. The Frozen Counter will store the values of all Binary Coun-ters effective when the Freeze command was executed.The following figure shows how the SCS operates upon accepting a Freeze command fromthe DNP3 master.

SCS

Copy current values of all Binary Counter to Frozen Counter

DNP3 data reference function

BinaryCounter

FrozenCounter

DNP3 Master

Freeze request

Figure D2.1.3-1 How the SCS operates upon accepting a Freeze command

n Freeze & Clear commandIf no more than 32 Binary Counters are defined, the Freeze & Clear command can be used.The Freeze & Clear command is used to save the current value of the Binary Counter in theFrozen Counter and then clear the value of the Binary Counter to 0. After accepting a Freeze& Clear command from the DNP3 master, the SCS copies the current values of all BinaryCounters to the Frozen Counter and then clears the values of all Binary Counters to 0.The following figure shows how the SCS operates upon accepting a Freeze & Clear com-mand from the DNP3 master.



SCS

(1) Copy current values of all Binary Counter to Frozen Counter.

DNP3 data reference function

BinaryCounter

FrozenCounter

DNP3 Master

Freeze & Clear request

(2) Clear all Binary Counter values

Figure D2.1.3-2 How the SCS operates upon accepting a Freeze & Clear command

The DNP3 master can calculate the rate of change in Binary Counter values by periodicallyexecuting a Freeze & Clear command.

IMPORTANT• If a Freeze & Clear request is received when 33 or more Binary Counters are defined, the

following error is returned:

IIN2.0 NO_FUNC_CODE_SUPPORT• SCS responds with a following error if the number of retained requests is four when SCS

receives a Freeze & Clear request from the DNP3 master:

IIN2.0 NO_FUNC_CODE_SUPPORT• If SCS returns an error in response to the Freeze & Clear request, no Freeze process is

executed.



D2.1.4 Response timeThe response time it takes for the SCS to response to the request for data referencing anddata setting from the DNP3 master refers to the time from when SCS receives a request mes-sage to when it starts to transmit the response message. The Ethernet transmission time isnot included.

Response time = (Message receiving processing time and message sending processing time) + (Data referencing processing time or data setting processing time)The message receiving processing time and message sending processing time should bewithin 20 ms.The data referencing processing time or data setting processing time may be as long as thescan period of the application logic.



D2.2 Event bufferingThe SCS generates an event the moment a variable of the application logic assigned toDNP3 data changes. This event contains the applicable DNP3 data and a time stamp indicat-ing when the DNP3 data changes. The SCS can retain events while a communication failureis present, by buffering the generated events. Once communication is restored, the DNP3master reads the buffered events to prevent missing data.

Events of BO

Event BufferEvents of AI

Events of BC

SCS

Application Logic

•••

Create an event when conditions for event generation are met,and store it in event buffer.

Figure D2.2-1 Event buffering operation

IMPORTANTThe DNP3 event buffering function cannot be used simultaneously with the data bufferingfunction in Integration with FAST/TOOLS.

<D2.2 Event buffering > D2-11


D2.2.1 Event generationTo generate events at the SCS, set an event class for each DNP3 data and event buffer sizefor each DNP3 data type.

n Event classFor events, set an event class of 0, 1, 2, or 3 for each DNP3 data. Event classes are used toorganize generated events into groups. The DNP3 master can specify an event class to ob-tain events set under the event class.No event is generated for DNP3 data of event class 0. Set event class 0 for those data notrequiring an event.Set event classes using input parameters of DNP3 communication FBs. They cannot be setby using DNP3 communication commands from the DNP3 master.

n Event buffer sizeSet the number of events that can be stored in the event buffer, for each DNP3 data type. Anevent buffer size can be set separately for each DNP3 data type. The total of all event buffersizes must be no greater than 135000.Set event buffer sizes by using the DNP3 Communication Builder of the SENG.

n Event generation conditionThe SCS generates an event when the following conditions are met:• Event class 1, 2, or 3 is set to each DNP3 data.

• A value other than 0 is set for the event buffer size.

• The value of DNP3 data is changed.

Determine whether or not the value of DNP3 data is changed, as follows:• In the case of Analog Input, the value changes when the absolute difference between the

previous change event value and this value exceeds the set Deadband.

• In the case of DNP3 data other than Analog Input, the value changes when there is a dif-ference between the previous value and this value.

The Deadband is a threshold that is used to generate an event. Set the Deadband by usingan input parameter of a DNP3 communication FB.

IMPORTANT• No event is generated for DNP3 data whose event class is set to 0.

• No event is generated for DNP3-type data whose event buffer size is set to 0.

n Event time stampAn event has a time stamp indicating the time the application logic scan was started. Allevents generating during the same scan period has an identical time stamp. However, theseevents are stored in the event buffer in the order generated.



D2.2.2 Event responseUpon receiving an event acquisition request from the DNP3 master, the SCS responds withthe specified event, if available.The following methods are used to acquire SCS event data from the DNP3 master:• Data type specification: Acquire events of the specified data type.

• Class specification: Acquire events of the specified class.

IMPORTANTEvent response by the SCS supports the Pulled Report by Exception type only. The Unsolici-ted Response type is not supported.



D2.2.3 Event deletionThe SCS deletes an event after receiving a confirmation from the DNP3 master.The SCS responds with the event corresponding to the event acquisition request, and thensets the event response mode flag. Once a confirmation of completed event acquisition is re-ceived from the DNP3 master, the SCS deletes the event for which the flag is set.If no confirmation is received from the DNP3 master 10 seconds after the event responsefrom the SCS, the SCS cancels the response mode flag and retains the event.The following figure shows the event deletion sequence.

DNP3 Master SCS

Event acquisition request

Event responseResponding flag is set to the event to be responded

When confirmation was not received for 10 seconds, the event is continuously stored and the responding flag is removed

ConfirmationEvent in which responding flag is set is removed from buffer

Figure D2.2.3-1 Event deletion sequence



D2.3 DNP3 function support for each data typeThe following table shows DNP3 data type, Index range and DNP3 function supported by theSCS.

Table D2.3-1 SCS support Data type for DNP3 functionData type IEC

datatype

Indexrange

DNP3 function (*1)ReadStatic

ReadEvent

Write Selectand

Oper-ate

DirectOper-

ate

Freeze AssignClass

SetAna-log

Dead-band

Binary Input BOOL 0 to499(*2)

Yes Yes - - - - Yes(*3)

-

Binary Output BOOL 0 to499(*2)

Yes Yes - Yes(*4)

Yes(*4)

- Yes(*3)

-

16-Bit Binary Counter DINT(*5)

0 to499(*2)

Yes Yes - - - Yes Yes(*3)

-

32-Bit Binary Counter DINT(*5)

Yes Yes - - - Yes Yes(*3)

-

16-Bit Frozen Counter DINT(*5)

Yes Yes - - - - Yes(*3)

-

32-Bit Frozen Counter DINT(*5)

Yes Yes - - - - Yes(*3)

-

16-Bit Analog Input DINT(*5)

0 to499(*2)

Yes Yes - - - No Yes(*3)

Yes(*3)

32-Bit Analog Input DINT Yes Yes - - - No Yes(*3)

Yes(*3)

Single-Precision Float-ing Point Analog Input

REAL Yes Yes - - - No Yes(*3)

Yes(*3)

16-Bit Analog Output DINT(*5)

0 to499(*2)

Yes Yes - Yes Yes - Yes(*3)

No

32-Bit Analog Output DINT Yes Yes - Yes Yes - Yes(*3)

No

Single-Precision Float-ing Point Analog Out-put

REAL Yes Yes - Yes Yes - Yes(*3)

No

*1: Yes: Supported, No: Not supported, -: Function not available under DNP3*2: The total number of data is 1000 for all data types combined.*3: Set by a DNP3 communication FB. Command setting from the DNP3 master is not supported.*4: Only latch type output operation is supported. Pulse type output operation is not supported.*5: The UNIT, UDINT and INT data types under DNP3 are handled as DINT on the SCS.

SEEALSO For more information about Definition of DNP3 data, refer to:


For more information about DNP3 communication FB, refer to:

D4., “DNP3 communication FBs” on page D4-1

<D2.3 DNP3 function support for each data type > D2-15


D2.4 Time synchronizationMethods to synchronize the time of the DNP3 master and that of the SCS include time syn-chronization by using SNTP servers and time synchronization by using DNP3 communication.However, the accuracy of time synchronization using DNP3 communication is no more than 1second plus the scan period of the application logic.In an environment where SNTP servers can be connected to the Ethernet network to whichthe DNP3 master is connected, and also to the Vnet/IP-Upstream network to which the SCSis connected, use time synchronization using SNTP servers for greater time synchronizationaccuracy.

n Time synchronization using SNTP serversConnect time-synchronized SNTP servers to the Ethernet and Vnet/IP-Upstream, respective-ly. Synchronize the DNP3 master with the time of the SNTP server on the Ethernet, and syn-chronize the SCS with the time of the SNTP server on the Vnet-/IP-Upstream. As a result, thetime of the DNP3 master will synchronize with the time of the SCS.The following figure shows the time synchronization by using SNTP servers.

DNP3Master

Vnet/IP-Upstream

SCS SCSSCS

SNTPServer SENG

Ethernet

SNTPServer

DNP3 master stations are synchronized with time of SNTP server on Ethernet

SENG and SCSs are synchronized with time of SNTP server on Vnet/IP-Upstream

Figure D2.4-1 Time synchronization using SNTP servers

IMPORTANTIf a time setting using DNP3 communication is requested while the SCS is connected to aSNTP server, the following error is returned:

IIN2.0 NO_FUNC_CODE_SUPPORTAlso, the following information is not notified while the SCS is connected to a SNTP server:

IIN1.4 NEED_TIME

TIP IIN1.4 NEED_TIME is information in the DNP3 response frame. 30 minutes after the time is set using DNP3communication, the SCS notifies the DNP3 master with the response frame containing IIN1.4 NEED_TIME.

n Time synchronization using DNP3 communication (The SCS is notconnected to the Vnet/IP-Upstream network)

If the SCS is not connected to the Vnet/IP-Upstream network, set the times of all SCSs fromthe DNP3 master by using DNP3 communication.

<D2.4 Time synchronization > D2-16


The following figure shows time synchronization by using DNP3 communication when theSCS is not connected to the Vnet/IP-Upstream network.

DNP3Master

SCS SCSSCS

Time is set for all SCSs via DNP3 communication

Ethernet

Figure D2.4-2 Time synchronization by using DNP3 communication when the SCS is not connected tothe Vnet/IP-Upstream network

n Time synchronization using DNP3 communication (The SCS isconnected to the Vnet/IP-Upstream network)

If the SCS is connected to the Vnet/IP-Upstream network, set the time of one SCS from theDNP3 master by using DNP3 communication.The times of other SCSs connected to the Vnet/IP-Upstream network will be synchronized bythe time synchronization function of the Vnet/IP-Upstream.The following figure shows time synchronization by using DNP3 communication when theSCS is connected to the Vnet/IP-Upstream network.

DNP3Master

By time synchronization of Vnet/IP-Upstream, time of SCSs are synchronized with the time of a SCS that is set by DNP3 communication.

SCS SCSSCS

Time is set for any one of SCSs via DNP3 communication

Vnet/IP-Upstream

Ethernet

Figure D2.4-3 Time synchronization by using DNP3 communication when the SCS is connected to theVnet/IP-Upstream network

TIP • Even when the Vnet/IP-Upstream network consists of multiple domains, setting the time of any one SCSsynchronizes the times of all SCSs.

• If some SCSs are connected to the Vnet/IP-Upstream network and others are not, set the time of oneSCS that is connected to the Vnet/IP-Upstream network and the times of all SCSs that are not connec-ted to the Vnet/IP-Upstream network.



SEEALSO For more information about Precautions when setting the time through DNP3 communication, refer to:

“■ Precautions When Setting the Time Through DNP3 Communication” in 2.17.3, “DNP3 Slave Func-tion” in Engineering Guide (IM 32Q01C10-31E)



D3. Engineering and maintenance withSENG

The following settings are required for the DNP3 master to access application logic variablesof the SCS by using the DNP3 communication function.• Enabled DNP3 slave function

• Definition of communication input/output modules

• DNP3 slave setting

• Definition of instances for DNP3 communication FBs

• Definition of DNP3 data

• Creating an application logic

n Engineering flowUse the following flow to set the DNP3 slave function engineering on the SENG.

Enabling DNP3 Slave Function

Define communication I/O module

Settings for DNP3 slaves

Define DNP3 data

Define instance of FB for DNP3 communication

Start

End

• SCS Constants Builder

• I/O Wiring View: Select ALE111• I/O Parameter Builder: Setings for TCP/IP

• DNP3 Communication Builder

• DNP3 Communication Builder

• Dictionary View

Create application logic • Multi Language Editor

Figure D3-1 Engineering flow of DNP3 slave function

<D3. Engineering and maintenance with SENG > D3-1


D3.1 Enabled DNP3 slave functionUse the SCS Constants Builder to enable the DNP3 slave function so that the SCS can per-form DNP3 communication. Enable the DNP3 slave function on the Communication tab of theSCS Constants Builder.

IMPORTANT• The DNP3 slave function cannot be enabled online. Changing this setting requires offline

download to the SCS.

• Once the DNP3 slave function is enabled, the data buffering function in Integration withFAST/TOOLS can no longer be used. The event buffer function of the DNP3 slave func-tion can be used.

SEEALSO For more information about SCS Constants Builder, refer to:

3.1.3, “SCS Constants Builder” in Engineering Reference (IM 32Q04B10-31E)

<D3.1 Enabled DNP3 slave function > D3-2


D3.2 Definition of communication input/outputmodules

Define the Ethernet communication module to a communication input/output module so thatthe SCS can perform DNP3 communication.Use the I/O Wiring View of SCS Manager to define the Ethernet communication module, andthen use the I/O Parameter Builder to set the parameters of the Ethernet communicationmodule.

SEEALSO For more information about I/O Wiring View and I/O Parameter Builder, refer to:

4., “Definitions of Inputs/Outputs” in Engineering Reference (IM 32Q04B10-31E)

For more information about parameter settings for communication modules, refer to:


<D3.2 Definition of communication input/output modules > D3-3


D3.2.1 Definitions in I/O Wiring ViewTo define the Ethernet communication module (model: ALE111), use the I/O Wiring View inSCS Manager and follow these steps:1. Open I/O Wiring View and select ALE111.

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/outputmodules and communication modules.

SEEALSO For more information about Display method and window configuration for the I/O Wiring View, refer to:

4.3, “I/O Wiring View” in Engineering Reference (IM 32Q04B10-31E)



D3.2.2 Definitions in I/O Parameter BuilderYou can specify parameters for the communication module by using I/O Parameter Builder.For an Ethernet communication module, you can specify the parameters in the Module tab ofI/O Parameter Builder.



n Module tab of Ethernet communication moduleThe following items can be set in the Module tab of the Ethernet communication module.The settings of each item can be changed by using online change download, but the corre-sponding module restarts after online change download.

Table D3.2.2-1 Display items of Module tab of Ethernet communication moduleTitle Description Remarks

Node Number The node number of the node in which themodule is mounted


Slot Number The slot number of the slot in which themodule is mounted


Device The model name of the module Defined in I/O WiringView

Dual-Redundant Whether the module is used in a single ordual-redundant configuration

The module cannot bedual-redundant

Device Number The device number that is assigned to themodule


Table D3.2.2-2 Setting items of Module tab of Ethernet communication moduleTitle Description Remarks

Connection Device Types of connection devices -

Comment A comment regarding the module -

IP Address The IP address of the module -

Subnet Mask The subnet mask of the module -

Default Gateway The default gateway address of the module -

Port Number The TCP/IP port number -


l Connection DeviceSet the type of connection device.Select SCSDPTCP when the DNP3 slave function should be used.

Default value: SCSMDTCPSCSMDTCP: Modbus TCP masterSCSDPTCP: DNP3 master (Selectable only when the version of SCSU1 is R3.02.20 or lat-

er.)



TIP If an attempt is made to change the connection device and the selected port number is not the default, thefollowing dialog box appears:

Figure D3.2.2-1 Connection Device dialog box

Yes: The connection device is changed and the port number is changed to the default.

No: The connection device is changed but the port number is not changed.

Cancel: Neither the connection device nor port number is changed.

l CommentA comment regarding the Ethernet communication module can be entered. This comment canbe entered using up to 24 single-byte characters or 12 double-byte characters.

l IP AddressSet the IP address of the Ethernet communication module. Enter any IP address that youwant.

Default: This field is empty by default; be sure to enter an IP address. If no value isentered, an error occurs when you try to save the settings in the builder.


However, do not set the following IP addresses:• Host address digits are all zeros or all ones in binary form.

(Example: When subnet mask is 255.255.255.0, 192.168.1.0,192.168.1.255, etc.)

• Any of the numbers delimited with a period has leading zeros.(Example: 192.168.08.09, 192.168.008.009, etc.)

l Subnet MaskSet the subnet mask of the Ethernet communication module. Enter a subnet mask that youwant.

Default: This field is empty by default; be sure to enter a subnet mask. If no value isentered, an error occurs when you try to save the settings in the builder.


However, do not set the following subnet masks:• Values less than 255.0.0.0 for a class A IP address

(Example: 128.0.0.0)

• Values less than 255.255.0.0 for a class B IP address(Example: 255.128.0.0)

• Values less than 255.255.255.0 for a class C IP address



(Example: 255.255.128.0)

l Default GatewaySet the gateway address of the Ethernet communication module. Enter a desired gateway ad-dress.

Default: BlankFormat: nnn.nnn.nnn.nnnSetting range: 1.0.0.1 to 223.255.255.254

However, do not set the following gateway addresses:• Host address digits are all zeros or all ones in binary form.

(Example: When subnet mask is 255.255.255.0, 192.168.1.0,192.168.1.255, etc.)

• Network address digits do not match the IP address.(IP address is 192.168.1.1 and default gateway address is 192.168.2.2when the subnet mask is 255.255.255.0.)

• Any of the numbers delimited with a period has leading zeros.(Example: 192.168.08.09, 192.168.008.009, etc.)

l Port NumberSet the port number for DNP3 communication.Default: 20000Setting range: 0 to 65535

l Option 1 to 4Always set 0 for these options.Default: 0 (for all)



D3.3 DNP3 slave settingUse the DNP3 Communication Builder of SENG to set the following parameters so as tomake the SCS operate as the DNP3 slave:Set it as the DNP3 slave on the Parameters tab of the DNP3 Communication Builder.• DNP3 slave station address

• DNP3 master station address

• Timeout value for Select Before Operate

• Binary Input event buffer size

• Binary Output event buffer size

• Binary Counter event buffer size

• Frozen Counter event buffer size

• Analog Input event buffer size

• Event to be removed when event buffer overflows

• Generate an event when Freeze and Clear command changes data values

• Include Frozen Counters in Class 0 response

• Type of response message fragmentation

IMPORTANT• All DNP3 slave settings, except for the event buffer size, can be changed online without

stopping the SCS.

• If the DNP3 slave station address or DNP3 master station address is changed, theTCP/IP connection will be cut off.

• If either station address has been changed, connect again from the DNP3 master.

• Changing any DNP3 slave setting does not affect the events already buffered.

• Changing the event buffer size requires offline download to the SCS.

SEEALSO For more information about display method and window configuration for the DNP3 Communication Builder,

refer to:


n DNP3 slave station addressSet the station address of the SCS.

Setting range: 0 to 65519Default: 0

n DNP3 master station addressSet the station address of the DNP3 master.

Setting range: 0 to 65519

<D3.3 DNP3 slave setting > D3-8


Default: 1

n Timeout value for Select Before OperateSet the timeout value in seconds for the Select Before Operate function.


n Binary Input event buffer sizeSet the number of events that can be stored in the Binary Input event buffer.


n Binary Output event buffer sizeSet the number of events that can be stored in the Binary Output event buffer.


n Binary Counter event buffer sizeSet the number of events that can be stored in the Binary Counter event buffer.


n Frozen Counter event buffer sizeSet the number of events that can be stored in the Frozen Counter event buffer.


n Analog Input event buffer sizeSet the number of events that can be stored in the Analog Input event buffer.


n Analog Output event buffer sizeSet the number of events that can be stored in the Analog Output event buffer.




n Event to be removed when event buffer overflowsSet how events will be stored when the event buffer overflows.

Oldest: The oldest event stored in the event buffer is deleted and a new event is stored.Newest: The newest event stored in the event buffer is deleted and a new event is stored.Default: Oldest

n Generate an event when Freeze and Clear command changes datavalues

Set whether or not to send an event notification when values are cleared to 0 by the Freeze &Clear command.

No: Do not send an event notification.Yes: Send an event notification.Default: No

n Include Frozen Counters in Class 0 responseSet whether or not to include the Frozen Counter in the Class 0 response.

Yes: Including Frozen CounterNo: Not including Frozen CounterDefault: Yes

n Type of response message fragmentationSet how a response is sent to one acquisition request when the size of the response DNP3frame exceeds the maximum frame size that SCS can handle.

Single: Single fragmentThe DNP3 frame is divided into frames with maximum frame size and only oneframe is sent for one acquisition request.

Multi: Multi fragmentsThe DNP3 frame is divided into frames with maximum frame size and multipleframes are sent consecutively for one acquisition request.

Default: Single

To acquire events from the SCS that receives data setting requests, change the event re-sponse method of the SCS to "Single fragment."

SEEALSO For more information about Precautions on event acquisition methods, refer to:

“■ Method of Response Upon Event Acquisition” in 2.17.3, “DNP3 Slave Function” in Engineering Guide(IM 32Q01C10-31E)



D3.4 Definition of instances for DNP3communication FBs

Use the Dictionary View to define an instance of DNP3 communication FB.

SEEALSO For more information about How to define variables using the Dictionary View, refer to:

"Dictionary View" of the Workbench User's Guide

<D3.4 Definition of instances for DNP3 communication FBs > D3-11


D3.5 Definition of DNP3 dataTo access any variable of the application logic of the SCS from the DNP3 master throughDNP3 communication, associate an instance of DNP3 communication FB, to DNP3 data. Usethe DNP3 Communication Builder to define an instance of DNP3 communication FB to DNP3data.

n Launching DNP3 Communication Builder1. Select [Engineering] from the [Tools] menu of SCS Manager.

The Engineering Launcher menu appears.

2. Select [DNP3 Communication Builder].The DNP3 Communication Builder appears.

<D3.5 Definition of DNP3 data > D3-12


D3.5.1 Window configuration of the DNP3 CommunicationBuilder

The window of the DNP3 Communication Builder is primarily composed of the data menuarea and work space.

Data Menu Area Workspace

DNP3 Data Tab Sheet

Figure D3.5.1-1 Window configuration of the DNP3 Communication Builder

The data menu area of the DNP3 Communication Builder is composed of the Instance tab.The work space of the DNP3 Communication Builder is composed of the Parameters tab andDNP3 data tab.

SEEALSO For more information about components that are the same in other builders, refer to:

2.2, “Relationship Between ProSafe-RS Projects and CENTUM Projects” in Engineering Reference (IM32Q04B10-31E)

n Instance tab of the Data Menu AreaA list of settable instances is displayed on the Instance tab. The displayed names of instancesvary depending on the type of DNP3 data displayed in the work space.The following figure shows an example of the Instance tab for Binary Input.

Figure D3.5.1-2 Example of Instance tab in Binary Input

Instances that are already set or deleted are removed from this list and not displayed.



n Parameters tab of the work spaceThe Parameters tab is used to define the parameters of the DNP3 slave function.

SEEALSO For more information about Parameter defined by the DNP3 slave function, refer to:

D3.3, “DNP3 slave setting” on page D3-8

n DNP3 data tab in the work spaceThe DNP3 data tabs include the following tabs that are used to define a DNP3 communicationFB for each DNP3 data type.• Binary Input

• Binary Output

• Binary Counter

• Analog Input

• Analog Output

l Items displayed in tabsThe following items are displayed on each DNP3 data tab: A desired instance name can beset.• Index

Index number of the DNP3 data. These are displayed in advance in numerical order. 0 to499.

• Instance nameInstance name of the FB to be assigned to the DNP3 data. This can be changed online.

• Type nameType name of the FB to be assigned to the DNP3 data.

• CommentComment string representing the instance name of the FB to be assigned to the DNP3data.



D3.5.2 Definition in the DNP3 Communication BuilderUse the DNP3 Communication Builder to assign an instance of DNP3 communication FB to aDNP3 Index.

n Assigning an instance name in the DNP3 Communication BuilderThe DNP3 data types that can be set in the DNP3 Communication Builder include Binary In-put, Binary Output, Binary Counter, Analog Input and Analog Output, and an Index is as-signed to DNP3 data of each DNP3 data type. The DNP3 Communication Builder assigns aninstance name for the DNP3 communication FB to be accessed, to one of Indexes 0 to 499.An instance name for the DNP3 communication FB to be assigned is selected according tothe Index.If the DNP3 data type is Binary Input, for example, an instance name for DNP3 communica-tion FB of DNP3_BI type can be assigned. If the DNP3 data type is Binary Counter, an in-stance name for DNP3 communication FB of DNP3_CT_16 type or DNP3_CT_32 type canbe assigned.

l DNP3 data types and assignable FBsThe following table shows the DNP3 data types and type names of FBs that can be assignedto these data types in the DNP3 Communication Builder.

Table D3.5.2-1 DNP3 data types and type names of FBs that can be assigned in the DNP3 Communica-tion Builder

DNP3 data type Type name of DNP3communication FB

Description of FB

Binary Input DNP3_BI FB corresponding to the DNP3 data of the DNP3 data type Bi-nary Input

Binary Output DNP3_BO FB corresponding to the DNP3 data of the DNP3 data type Bi-nary Output

Binary Counter DNP3_CT_16 FB corresponding to the DNP3 data of the DNP3 data type 16-bit Binary Counter

DNP3_CT_32 FB corresponding to the DNP3 data of the DNP3 data type 32-bit Binary Counter

Analog Input DNP3_AI_16 FB corresponding to the DNP3 data of the DNP3 data type 16-bit Analog Input

DNP3_AI_32 FB corresponding to the DNP3 data of the DNP3 data type 32-bit Analog Input

DNP3_AI_SF FB corresponding to the DNP3 data of the DNP3 data type Sin-gle-Precision Floating Point Analog Input

Analog Output DNP3_AO_16 FB corresponding to the DNP3 data of the DNP3 data type 16-bit Analog Output

DNP3_AO_32 FB corresponding to the DNP3 data of the DNP3 data type 32-bit Analog Output

DNP3_AO_SF FB corresponding to the DNP3 data of the DNP3 data type Sin-gle-Precision Floating Point Analog Output

l Instance nameSet an instance name of DNP3 communication FB to be assigned to the DNP3 data.An instance name of DNP3 communication FB consists of up to 69 single-byte characters. Interms of accessibility to instance names, both global instances and local instances can be setregardless of the scope. In the case of a local instance, Scope name must be added after"@."



To access an instance of internal parameter in a user-defined function block, you can use theSCS Manager Dictionary View to name instances of the user-defined function block itself.Specify an instance name of DNP3 communication FB in the following format. Up to two nest-ing levels can be specified for an instance name.

instance name.internal parameter name

Table D3.5.2-2 Example of instance nameInstance name Scope Description

VAR1 Global Global instance

VAR2@PROG1 PROG1 Local instance of PROG1 function

FB01.VAR3 Global The internal parameter VAR3 of an instance of theuser-defined function block FB01

FB01.VAR3@PROG1 PROG1 The internal parameter VAR3 of an instance of theuser-defined function block FB01, which is locally de-fined in a function of PROG1

FB01.FB2.VAR3 Global The internal parameter VAR3 of an instance of theuser-defined function block FB2 used inside an in-stance of the user-defined function block FB01 (Thelimit of nesting of a function block is two)

SEEALSO For more information about SCS Manager Dictionary View, refer to:

"Dictionary View" of the Workbench User's Guide

n Definition method of instance nameAn instance name can be set in the Instance Name field of the tab corresponding to one offive DNP3 data types.

l Direct entry from the keyboardEnter an instance name in the Instance name field directly from the keyboard.

l Double-clicking an instance name in the data menu areaDouble-click an instance that is set in the Instance Name field on the Instance tab in the datamenu area, and you can set an instance name in the Instance Name field of the line selectedin the work space.

l Drag and drop an instance name from Dictionary ViewDrag and drop an instance name from Dictionary View to an Instance Name field of DNP3Communication Builder to register the instance name in DNP3 Communication Builder. If youdrag and drop multiple instance names, they are registered in order starting from the top ofthe Instance Name field where they are dropped. If instance names are already registered inthe Instance Name field, they are overwritten.

SEEALSO For more information about Screen image of drag & drop, refer to:

“l Drag and drop from Dictionary View” on page C1-14

n Precaution when setting definitions in the DNP3 CommunicationBuilder

Take note of the following when setting definitions in the DNP3 Communication Builder.



• An instance of DNP3 connection FB is assigned to one of Indexes 0 to 499 of a givenDNP3 data type.

• The total number of assignable instances of DNP3 communication FBs is limited to 1,000for all data types combined.

• The Frozen Counter need not have any instance assigned, because there is one FrozenCounter corresponding to one Binary Counter.

• DNP3 data assignments can be changed online without stopping the SCS. When onlinechange is executed, changing the definitions of the DNP3 master is also required.

The actions of SCS during online change are as follows:• Assume that the type name of a function block instance is being changed. If a data refer-

encing request or setting request for the function block instance of the new type name isreceived before the change is completed, the SCS returns the following error:

IIN2.1 OBJECT_UNKNOWN• When a response message by batch specification (Class 0 is specified) is divided into

several messages, if online change is executed before the SCS finishes returning all re-sponse messages, the SCS stops sending the response messages and returns the fol-lowing error:

IIN2.1 OBJECT_UNKNOWN• Any event of the data for which online change is performed is not created during online

change.

• If the data types (16 bit, 32 bit, float) of Analog Input, Analog Output, Binary Counter, andFrozen Counter are changed, the event data before the change may be incorrect.

• If a request is received for an Index whose definition was lost after the assignmentchange, the SCS returns the following error: The same applies to the Frozen Counter.

IIN2.2 PARAMETER_ERROR• When Binary Counter is changed online, all values of all Frozen Counters are cleared to

0. However, the events of Frozen Counter which are cleared to 0 due to online change ofBinary Counter are not created.

SEEALSO For more information about Precautions when assigning DNP3 data, refer to:

“■ Precautions When Assigning DNP3 Data” in 2.17.3, “DNP3 Slave Function” in Engineering Guide (IM32Q01C10-31E)



D3.6 Creating an application logicUse the Multi-language Editor to create an application logic.

SEEALSO For more information about How to create application logics using the Multi-Language Editor, refer to:

"Multi-Language Editor" in the "Language Editors" of the Workbench User's Guide

<D3.6 Creating an application logic > D3-18


D3.7 TroubleshootingIf a communication module error occurs, you can use the SCS Maintenance Support Tool toacquire information on the communication module and communication error information. Thissection describes typical troubleshooting cases.

n There is no response and communication failsIf there is no response and communication fails, check the following procedures.• Check if the TCP/IP settings of the Communication Input/Output Module match those on

the master side.

• Use the SCS Maintenance Support Tool to check the status of the communication mod-ule.

• Use Network Monitor or other tool to analyze the protocol governing the send/receiveframes.

• Check if there is enough CPU time available. Response may be delayed when the CPUload is high.

n Connection cannot be established and communication failsIf connection cannot be established and communication fails, check the following.• Check if the destination IP address and port number are correct.

• If the DNP3 protocol communication between the DNP3 master and SCS is cut off with-out the DNP3 master notifying the end of communication to the SCS, connection to theSCS becomes possible again after up to 34 seconds.

n The SCS time is not synchronized with the DNP3 master timeIf the SCS time is not synchronized with the DNP3 master time, check the following proce-dures.

l SNTP servers are used• Check if the time of the SNTP server on Ethernet side is synchronized with that of the

SNTP server on Vnet/IP-Upstream side.

• Check if the DNP3 master and SCS are synchronized with their respective SNTP servers.

l SNTP servers are not usedCheck if an application that issues time setting requests to the SCS exists on the DNP3 mas-ter.

<D3.7 Troubleshooting > D3-19


D4. DNP3 communication FBsDNP3 communication FBs are an interference-free function block unique to ProSafe-RS.DNP3 communication FBs can be used in the SCSU1 database created by a SENG ofR3.02.20 or later.The following list shows DNP3 communication FBs.• DNP3_BI (Binary Input type DNP3 communication FB)

• DNP3_BO (Binary Output type DNP3 communication FBs)

• DNP3_CT_16 (16-Bit Binary Counter type DNP3 communication FB)

• DNP3_CT_32 (32-Bit Binary Counter type DNP3 communication FB)

• DNP3_AI_16 (16-Bit Analog Input type DNP3 communication FB)

• DNP3_AI_32 (32-Bit Analog Input type DNP3 communication FB)

• DNP3_AI_SF (Single-Precision Floating Point Analog Input type DNP3 communicationFB)

• DNP3_AO_16 (16-Bit Analog Output type DNP3 communication FB)

• DNP3_AO_32 (32-Bit Analog Output type DNP3 communication FB)

• DNP3_AO_SF (Single-Precision Floating Point Analog Output type DNP3 communicationFB)

<D4. DNP3 communication FBs> D4-1


D4.1 DNP3_BIFB corresponding to the DNP3 data of the DNP3 data type Binary Input. This FB retainsBOOL-type data referenced by using DNP3 communication.

DNP3_BI

IN

CLS

Figure D4.1-1 DNP3_BI

n Arguments

Table D4.1-1 Arguments of DNP3_BIIN/OUT Arguments Data type Description

IN IN BOOL Input value

CLS DINT Event classSpecify 0, 1, 2 or 3 for CLS. (If a value smaller than 0 or great-er than 3 is specified for CLS, the FB operates based on CLS= 0. No event generates for CLS = 0.)

n Description• This FB acquires and retains an input value of BOOL-type data.

• If the event generation conditions are satisfied, it generates an event and stores it in theevent buffer.

n Remarks• The DNP3_BI is an interference-free function block. Do not use it for input to safety loops.

• The DNP3_BI can be used in SCSU1 database created by SENG of R3.02.20 or later.

n Specification difference between simulators on PC and actual SCS

l Operations of SCS simulation testsIn the DNP3_BI, SCS simulator cannot be used.

l Operations of Logic simulation testsThe event buffering function is disabled. Events are not stored in the event buffer.

<D4.1 DNP3_BI> D4-2


D4.2 DNP3_BOFB corresponding to the DNP3 data of the DNP3 data type Binary Output. This FB receivesBOOL type data written by using DNP3 communication and outputs the received value.

DNP3_BO

INI

CLSOUT

Figure D4.2-1 DNP3_BO

n Arguments

Table D4.2-1 Arguments of DNP3_BOIN/OUT Arguments Data type Description

IN CLS DINT Event classSpecify 0, 1, 2 or 3 for CLS. (If a value smaller than 0 or great-er than 3 is specified for CLS, the FB operates based on CLS= 0. No event generates for CLS = 0.)

INI BOOL Initial valueSpecify TRUE or FALSE for INI.

OUT OUT BOOL Output value

n Description• This FB receives BOOL type data that is written by using DNP3 communication and out-

puts the received value. Following an offline download or after adding an instance by us-ing online change download, the initial value is output until data is written by using DNP3communication.


n Remarks• The DNP3_BO is an interference-free function block. Do not use it for input to safety

loops.

• The DNP3_BO can be used in SCSU1 database created by SENG of R3.02.20 or later.


l Operations of SCS simulation testsIn the DNP3_BO, SCS simulator cannot be used.

l Operations of Logic simulation tests• The event buffering function is disabled. Events are not stored in the event buffer.

• Connection cannot be established with the DNP3 master. Test the logic by forcing an in-termediate variable.

<D4.2 DNP3_BO> D4-3


D4.3 DNP3_CT_16FB corresponding to the DNP3 data of the DNP3 data type 16-bit Binary Counter. This FB re-tains DINT-type data referenced by using DNP3 communication.

DNP3_CT_16

CLS

CLSF

OUT

IN

Figure D4.3-1 DNP3_CT_16

n Arguments

Table D4.3-1 Arguments of DNP3_CT_16IN/OUT Arguments Data type Description

IN IN DINT Input value


CLSF DINT Event class of frozen dataSpecify 0, 1, 2 or 3 for CLSF. (If a value smaller than 0 orgreater than 3 is specified for CLSF, the FB operates based onCLSF = 0. No event generates for CLSF = 0.)

OUT OUT DINT Output value

n Description• This FB acquires an input value of DINT-type data and retains the data in a range of 0 to

65535. It retains 0 when the input value is less than 0, and 65535 when the input valuesis greater than 65535.


• The retained value is output.

• If the DNP3_CT_16 receives a clear request and scan is performed, the retained value iscleared to 0. If scan is performed without a clear request being received, the input valueis output directly.

• To use this FB as a counter, create an application that uses the output value of theDNP3_CT_16 from the previous scan to perform calculations and links the calculation re-sult to the input of the DNP3_CT_16.

n Remarks• The DNP3_CT_16 is an interference-free function block. Do not use it for input to safety

loops.

• The DNP3_CT_16 can be used in SCSU1 database created by SENG of R3.02.20 or lat-er.

<D4.3 DNP3_CT_16> D4-4



l Operations of SCS simulation testsIn the DNP3_CT_16, SCS simulator cannot be used.


SEEALSO For more information about Engineering method of DNP3 counter, refer to:

“■ Engineering for DNP3_CT_16/DNP3_CT_32” in 2.17.3, “DNP3 Slave Function” in Engineering Guide(IM 32Q01C10-31E)

<D4.3 DNP3_CT_16> D4-5


D4.4 DNP3_CT_32FB corresponding to the DNP3 data of the DNP3 data type 32-bit Binary Counter. This FB re-tains DINT-type data referenced by using DNP3 communication.

DNP3_CT_32

CLS

CLSF

OUT

IN

Figure D4.4-1 DNP3_CT_32

n Arguments

Table D4.4-1 Arguments of DNP3_CT_32IN/OUT Arguments Data type Description



CLSF DINT Event class of frozen dataSpecify 0, 1, 2 or 3 for CLSF. (If a value smaller than 0 orgreater than 3 is specified for CLSF, the FB operates based onCLSF = 0. No event generates for CLSF = 0.)


n Description• This FB acquires an input value of DINT-type data and retains the data in a range of 0 to

2,147,483,647. It retains 0 when the input value is smaller than 0, and 2,147,483,647when the input values is greater than 2,147,483,647.


• The retained value is output.

• If the DNP3_CT_32 receives a clear request and scan is performed, the retained value iscleared to 0. If scan is performed without a clear request being received, the input valueis output directly.

• To use this FB as a counter, create an application that will use the output value of theDNP3_CT_32 from the previous scan to perform calculations and link the calculation re-sult to the input of the DNP3_CT_32.

n Remarks• The DNP3_CT_32 is an interference-free function block. Do not use it for input to safety

loops.

• The DNP3_CT_32 can be used in SCSU1 database created by SENG of R3.02.20 or lat-er.

<D4.4 DNP3_CT_32> D4-6



l Operations of SCS simulation testsIn the DNP3_CT_32, SCS simulator cannot be used.


SEEALSO For more information about Engineering method of DNP3 counter, refer to:

“■ Engineering for DNP3_CT_16/DNP3_CT_32” in 2.17.3, “DNP3 Slave Function” in Engineering Guide(IM 32Q01C10-31E)

<D4.4 DNP3_CT_32> D4-7


D4.5 DNP3_AI_16FB corresponding to the DNP3 data of the DNP3 data type 16-bit Analog Input. This FB re-tains DINT-type data referenced by using DNP3 communication.

DNP3_AI_16

CLS

DEL

IN

Figure D4.5-1 DNP3_AI_16

n Arguments

Table D4.5-1 Arguments of DNP3_AI_16IN/OUT Arguments Data type Description



DEL DINT DeadbandSpecify a value between 0 and 32,767 for DEL. (The FB oper-ates based on DEL = 0 if a value smaller than 0 is specified forDEL, or based on DEL = 32,767 if a value greater than 32,767is specified.)

n Description• This FB acquires an input value of DINT-type data and retains the data in a range of

-32,768 to 32,767. It retains -32,768 when the input value is smaller than -32,768, and32,767 when the input values is greater than 32,767.


n Remarks• The DNP3_AI_16 is an interference-free function block. Do not use it for input to safety

loops.

• The DNP3_AI_16 can be used in SCSU1 database created by SENG of R3.02.20 or lat-er.


l Operations of SCS simulation testsIn the DNP3_AI_16, SCS simulator cannot be used.


<D4.5 DNP3_AI_16> D4-8


D4.6 DNP3_AI_32FB corresponding to the DNP3 data of the DNP3 data type 32-bit Analog Input. This FB re-tains DINT-type data referenced by using DNP3 communication.

DNP3_AI_32

CLS

DEL

IN

Figure D4.6-1 DNP3_AI_32

n Arguments

Table D4.6-1 Arguments of DNP3_AI_32IN/OUT Arguments Data type Description



DEL DINT DeadbandSpecify a value between 0 and 2,147,483,647 for DEL. (TheFB operates based on DEL = 0 if a value smaller than 0 isspecified for DEL.)

n Description• This FB acquires and retains an input value of DINT-type data.


n Remarks• The DNP3_AI_32 is an interference-free function block. Do not use it for input to safety

loops.

• The DNP3_AI_32 can be used in SCSU1 database created by SENG of R3.02.20 or lat-er.


l Operations of SCS simulation testsIn the DNP3_AI_32, SCS simulator cannot be used.


<D4.6 DNP3_AI_32> D4-9


D4.7 DNP3_AI_SFFB corresponding to the DNP3 data of the DNP3 data type Single-Precision Floating PointAnalog Input. This FB retains REAL-type data referenced by using DNP3 communication.

DNP3_AI_SF

CLS

DEL

IN

Figure D4.7-1 DNP3_AI_SF

n Arguments

Table D4.7-1 Arguments of DNP3_AI_SFIN/OUT Arguments Data type Description

IN IN REAL Input value


DEL REAL DeadbandSpecify a value between 0.0 and 3.40282E38 for DEL. (TheFB operates based on DEL = 0.0 if a value smaller than 0.0 isspecified for DEL.)

n Description• This FB acquires and retains an input value of REAL-type data.


n Remarks• The DNP3_AI_SF is an interference-free function block. Do not use it for input to safety

loops.

• The DNP3_AI_SF can be used in SCSU1 database created by SENG of R3.02.20 or lat-er.


l Operations of SCS simulation testsIn the DNP3_AI_SF, SCS simulator cannot be used.


<D4.7 DNP3_AI_SF> D4-10


D4.8 DNP3_AO_16FB corresponding to the DNP3 data of the DNP3 data type 16-bit Analog Output. This FB re-ceives DINT-type data written by using DNP3 communication and outputs the received value.

DNP3_AO_16

INI

CLSOUT

Figure D4.8-1 DNP3_AO_16

n Arguments

Table D4.8-1 Arguments of DNP3_AO_16IN/OUT Arguments Data type Description


INI DINT Initial valueSpecify a value between -32,768 and 32,767 for INI. (The FBoperates based on INI = -32,768 if a value smaller than-32,768 is specified for INI, or based on INI = 32,767 if a valuegreater than 32,767 is specified.)


n Description• This FB receives DINT-type data written by using DNP3 communication and outputs the

received value in a range of -32,768 to 32,767. It outputs -32,768 if the input value issmaller than -32,768, and 32,767 if the input value is greater than 32,767. Following anoffline download or after adding an instance by using online change download, the initialvalue is output until data is written using DNP3 communication.


n Remarks• The DNP3_AO_16 is an interference-free function block. Do not use it for input to safety

loops.

• The DNP3_AO_16 can be used in SCSU1 database created by SENG of R3.02.20 or lat-er.


l Operations of SCS simulation testsIn the DNP3_AO_16, SCS simulator cannot be used.


<D4.8 DNP3_AO_16> D4-11



<D4.8 DNP3_AO_16> D4-12


D4.9 DNP3_AO_32FB corresponding to the DNP3 data of the DNP3 data type 32-bit Analog Output. This FB re-ceives DINT-type data written by using DNP3 communication and outputs the received value.

DNP3_AO_32

INI

CLSOUT

Figure D4.9-1 DNP3_AO_32

n Arguments

Table D4.9-1 Arguments of DNP3_AO_32IN/OUT Arguments Data type Description


INI DINT Initial valueSpecify a value between -2,147,483,648 and 2,147,483,647for INI.


n Description• This FB receives DINT-type data written by using DNP3 communication and outputs the

received value. Following an offline download or after adding an instance by using onlinechange download, the initial value is output until data is written by using DNP3 communi-cation.


n Remarks• The DNP3_AO_32 is an interference-free function block. Do not use it for input to safety

loops.

• The DNP3_AO_32 can be used in SCSU1 database created by SENG of R3.02.20 or lat-er.


l Operations of SCS simulation testsIn the DNP3_AO_32, SCS simulator cannot be used.



<D4.9 DNP3_AO_32> D4-13


D4.10 DNP3_AO_SFFB corresponding to the DNP3 data of the DNP3 data type Single-Precision Floating PointAnalog Output. This FB receives REAL-type data written by using DNP3 communication andoutputs the received value.

DNP3_AO_SF

INI

CLSOUT

Figure D4.10-1 DNP3_AO_SF

n Arguments

Table D4.10-1 Arguments of DNP3_AO_SFIN/OUT Arguments Data type Description


INI REAL Initial valueSpecify a value between -3.40282E38 and 3.40282E38 for INI.

OUT OUT REAL Output value

n Description• This FB receives REAL-type data that is written by using DNP3 communication and out-

puts the received value. Following an offline download or after adding an instance by us-ing online change download, the initial value is output until data is written by using DNP3communication.


n Remarks• The DNP3_AO_SF is an interference-free function block. Do not use it for input to safety

loops.

• The DNP3_AO_SF can be used in SCSU1 database created by SENG of R3.02.20 or lat-er.


l Operations of SCS simulation testsIn the DNP3_AO_SF, SCS simulator cannot be used.



<D4.10 DNP3_AO_SF> D4-14


Appendix 1. DNP3 Field Device ProfileThis section describes the DNP3 specifications of the SCS. Confirm that slave devices meet-ing these specifications can connect to the DNP3 master that communicates with the SCS.

<Appendix 1. DNP3 Field Device Profile> App.1-1


Appendix 1.1 Device PropertiesTable Appendix 1.1-1 Device Properties

DEVICE IDENTIFICATION

Device Function: [ ] Master[v] Outstation

Vendor Name: Yokogawa Electric Corporation

Device Name: ProSafe-RS SCS

Device manufacturer's hardware versionstring:

Device manufacturer's software versionstring:

Device Profile Document Version Num-ber:

2013

DNP Levels Supported for: Outstations OnlyRequests and Responses[v] None - partially supported[v] Level 1 - except Unsolicited Response;[v] Level 2 - except Device Attributes;[v] Level 3 - except Device Attributes[v] Level 4 - partially supported

Supported Function Blocks: [ ] Self-Address Support[ ] Data Sets[ ] File Transfer[ ] Virtual Terminal[ ] Mapping to IEC 61850 Object Models defined in a DNP3 XMLfile.[ ] Function code 31, activate configuration[ ] Authentication

Methods to set Configurable Parame-ters:

[ ] XML - Loaded via DNP3 File Transfer[ ] XML - Loaded via other transport mechanism[ ] Terminal - ASCII Terminal Command Line[v] Software - Vender software named "Multi Language Editor","I/O Parameter Builder" and "DNP3 Communication Builder"[ ] Proprietary file loaded via DNP3 File Transfer[ ] Proprietary file loaded via other transport mechanism[ ] Direct - Keypad on device front panel[ ] Factory - Specified when device is ordered[ ] Protocol - Set via DNP3 (e.g. assign class, write deadband)[ ] Other - explain:

DNP3 XML files available On-line: Rd Wr[ ] dnpDP.xml - Complete Device Profile[ ] dnpDPcap.xml - Device Profile Capabilities[ ] dnpDPcfg.xml - Device Profile config. values[ ] [ ] *.xml

External DNP3 XML files available Off-line:

Rd Wr[ ] [ ] dnpDP.xml - Complete Device Profile[ ] [ ] dnpDPcap.xml - Device Profile Capabilities[ ] [ ] dnpDPcfg.xml - Device Profile config. values[ ] [ ] *.xml

Connections Supported: [ ] Serial (complete section "SERIAL CONNECTIONS")[v] IP Networking (complete section "IP NETWORKING")[ ] Other, explain

Conformance Testing [v] Self-tested[ ] Independently tested, versionTest organization name

IP NETWORKING


<Appendix 1.1 Device Properties> App.1-2


Table Appendix 1.1-1 Device Properties (Table continued)

Port Name:

Type of End Point: [ ] TCP Initiating (Master Only)[v] TCP Listening (Outstation Only)[ ] TCP Dual (required for Master)[ ] UDP Datagram (required)

IP Address of this Device:

Subnet Mask:

Gateway IP Address:

Accepts TCP Connections or UDP Data-grams from:

[v] Allows all[ ] Limits based on IP address[ ] Limits based on list of IP address[ ] Limits based on a wildcard IP address[ ] Limits based on list of wildcard IP address[ ] Other, explain:

IP Address(es) from which TCP Con-nections or UDP Datagrams are accep-ted.

TCP Listen Port Number: [ ] Not Applicable (Master w/o dual end point)[ ] Fixed at 20000[v] Configurable, range 0 to 65535- by I/O Parameter Builder- default = 20000- The number must NOT be duplicated with other TCP Listen PortNumbers on the controller.[ ] Configurable, selectable from[ ] Configurable, other, describe:

TCP Listen Port Number of remote de-vice:

[v] Not Applicable (Outstation w/o dual end point)[ ] Fixed at 20000[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:

TCP Keep-alive timer: [v] Fixed at 30000 ms[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:

Local UDP Port: [ ] Fixed at 20000[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:

Destination UDP port for initial unsolici-ted null responses:

[ ] None[ ] Fixed at 20000[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:

Destination UDP port for responses: [ ] None[ ] Fixed at 20000[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:[ ] Use source port number

Multiple Master Connections: [ ] Supports multiple masters (Outstations only)If supported, the following methods may be used:[ ] Method 1 (based on IP address)[ ] Method 2 (based on IP port number)[ ] Method 3 (browsing for static data)





Time Synchronization Support: [v] DNP3 LAN procedure (function code 24)[v] DNP3 Write Time (not recommended over LAN)[ ] Other, explain[ ] Not Supported

LINK LAYER

Data Link Address:(DNP3 Outstation Address)

[ ] Fixed at[v] Configurable, range 0 to 0xffff- Configurable by DNP3 Communication Builder[ ] Configurable, selectable from[ ] Configurable, other, describe:

DNP3 Source Address Validation: [ ] Never[v] Always, one address allowed[ ] Always any one of multiple addresses allowed[ ] Sometimes, explain:

DNP3 Source Address(es) expectedwhen Validation is Enables:(DNP3 Master Address)

[v] Configurable to any 16 bit DNP Data Link Address value- Configurable by DNP3 Communication Builder[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:

Self Address Support using address0xFFFC:

[ ] Yes (only allowed if configurable)[v] No

Sends Confirmed User Data Frames: [v] Never[ ] Sometimes, explain:[ ] Always

Data Link Layer Confirmation Timeout: [v] None[ ] Fixed at[ ] Configurable, range to ms[ ] Configurable, selectable from ms[ ] Configurable, other, describe:[ ] Variable, explain:

Maximum Data Link Retries: [v] Never Retries[ ] Fixed at[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:

Maximum number of octets Transmittedin a Data Link Frame:

[v] Fixed at 292[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:

Maximum number of octets Received ina Data Link Frame:


APPLICATION LAYER

Maximum number of octets Transmittedin an Application Layer Fragment otherthan File Transfer:


Maximum number of octets Transmittedin an Application Layer Fragment con-taining File Transfer:

[ ] Fixed at[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:

Maximum number of octets that can beReceived in an Application Layer Frag-ment :






Timeout waiting for Complete Applica-tion Layer Fragment:

[ ] None[v] Fixed at 15 seconds[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:[ ] Variable, explain:

Maximum number of objects allowed ina single control request for CROB(group 12):

[v] Fixed at 1[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:[ ] Variable, explain:

Maximum number of objects allowed ina single control request for Analog Out-puts (group 41):

[v] Fixed at 1[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:[ ] Variable, explain:

Maximum number of objects allowed ina single control request for Data Sets(groups 85, 86, 87):

[ ] Fixed at[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:[ ] Variable, explain:

Supports mixing object groups (AOBs,CROBs and Data Sets) in the samecontrol request:

[ ] Not applicable - controls are not supported[ ] Yes[v] No

Control Status Codes Supported [v] 1 - Timeout[v] 2 - NO_SELECT[v] 3 - FORMAT_ERROR[v] 4 - NOT_SUPPORTED[v] 5 - ALREADY_ACTIVE[ ] 6 - HARDWARE_ERROR[ ] 7 - LOCAL[v] 8 - TOO_MANY_OBJS[ ] 9 – NOT_AUTHORIZED[ ] 10 – AUTOMATION_INHIBIT[v] 11 – PROCESSING_LIMITED[ ] 12 – OUT_OF_RANGE[ ] 13 – DOWNSTREAM_LOCAL[ ] 14 – ALREADY_COMPLETE[ ] 15 – BLOCKED[ ] 16 – CANCELLED[ ] 17 – BLOOCKED_OTHER_MASTER[ ] 18 – DOWNSTREAM_FAIL[ ] 126 – RESERVED[ ] 127 - UNDEFINED

ITEMS FOR OUTSTATIONS

Timeout waiting for Application Confirmof solicited response message:

[ ] None[v] Fixed at 10000 ms[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other, describe:[ ] Variable, explain:

How often is time synchronization re-quired from the master:

[v] Never needs time[ ] Within seconds after IIN1.4 is set[v] Periodically, fixed at 1800 seconds- IIN1.4 will be set at startup and every 30 minutes (1800 sec-onds) after the last "Time Synchronization"[ ] Periodically, between and seconds

Device Trouble Bit IIN1.6: [v] Never used[ ] Reason for setting:





File Handle Timeout: [v] Not Applicable, Files Not Supported[ ] Fixed at ms[ ] Configurable, range to ms[ ] Configurable, selectable from ms[ ] Configurable, other, describe:[ ] Variable, explain:

Event Buffer Overflow Behavior: [v] Discard the oldest event[v] Discard the newest event- Configurable by DNP3 Communication Builder[ ] Other, explain

Event Buffer Organization: [v] Per Object Group[ ] Per ClassClass 1:[ ] Fixed at______[ ] Configurable, range _______ to _______[ ] Configurable, selectable from ___,___,___[ ] Configurable, other, describe_____________Class 2:[ ] Fixed at______[ ] Configurable, range _______ to _______[ ] Configurable, selectable from ___,___,___[ ] Configurable, other, describe_____________Class 3:[ ] Fixed at______[ ] Configurable, range _______ to _______[ ] Configurable, selectable from ___,___,___[ ] Configurable, other, describe_____________[ ] Single Buffer[ ] Fixed at______[ ] Configurable, range _______ to _______[ ] Configurable, selectable from ___,___,___[ ] Configurable, other, describe_____________[ ] Other, describe ___________

Sends Multi-Fragment Responses: [v] Yes[v] No- Configurable by DNP3 Communication Builder

Last Fragment Confirmation: [v] Always[ ] Sometimes, explain[ ] Never

DNP Command Settings preservedthrough a device reset:

[ ] Assign Class[ ] Analog Deadbands[ ] Data Set Prototypes[ ] Data Set Descriptors.[ ] Function Code 31 Activate Configuration.

Supports configuration signature [ ] Configuration signature supportedIf configuration signature is supported, then the following algo-rithm(s) are available for calculating the signature:Algorithm Name:

Requests Application Confirmation For event response[v]Yes[ ]No[ ]ConfigurableFor non-final fragments[v]Yes[ ] No[ ] Configurable

OUTSTATION UNSOLICITED RESPONSE SUPPORT

Supports Unsolicited Reporting: [v] Not Supported[ ] Configurable, selectable from On or Off

INDIVIDUAL FIELD OUTSTATION PARAMETERS





Analog Input Deadbands: [ ] Configurable - Per Point - by Master[v] Configurable - Per Point - by Outstation- Configurable by Multi Language Editor

Class Assign: [ ] Configurable - Per Point - by Master[v] Configurable - Per Point - by Outstation- Configurable by Multi Language Editor

Time Value for all DNP3 protocol timestamps reported and time synchroniza-tion messages:

[v] Fixed at UTC[ ] Configurable, selectable from "Local Time" or "UTC"

File Handling: [v] Not Supported

Control Relay Output Block (CROB)Latch Operation:

[v] Yes- "CROB Operation" is available for Binary Outputs.- Output Block Operation (CROB and AOB) cannot run more thanfour times a second.

Control Relay Output Block (CROB)Pulse, Trip and Close Operation:

[v] Not Supported

Analog Output Block (AOB) Operation: [v] Yes- Output Block Operation (CROB and AOB) cannot run more thanfour times a second.

Freeze & Clear Operation Freeze & Clear Operation is available only when the number ofBinary Counter is defined as 32 or less.

Time Synchronization Accuracy If you use DNP3 network method, time synchronization accuracybetween DNP3 master and SCS is up to the scan cycle of appli-cation logic plus 1000 ms.

Delay of data setting There is delay after SCS receives the setting request of DNP3data until the actual data is updated. This delay is dependent onthe scanning cycle and the number of requests from external con-nection devices.

Support Data Types DNP3 Data type IEC data type treated by SCS

Binary Input BOOL

Binary Output BOOL

16-Bit Binary Counter DINT

32-Bit Binary Counter DINT

16-Bit Frozen Counter DINT

32-Bit Frozen Counter DINT

16-Bit Analog Input DINT

32-Bit Analog Input DINT

Single-Precision Floating PointAnalog Input

REAL

16-Bit Analog Output DINT

32-Bit Analog Output DINT

Single-Precision Floating PointAnalog Output

REAL





Online maintenance DNP3 data can be modified by using online change without stop-ping SCS. The following list shows how SCS behaves when on-line change is performed:- If the SCS receives a write request or a read request while thedata in the SCS is being updated by the online change, the SCSreturns the error IIN2.1 OBJECT_UNKNOWN.- If the Class 0 response is divided into multiple messages, run-ning the online change before the SCS finishes sending responsemessages causes the SCS to stop sending messages and returnthe error IIN2.1 OBJECT_UNKNOWN.- While the online change is running, events for the data in theSCS are not generated.- If you change the detailed data type of Analog Input, AnalogOutput, Binary Counter, or Frozen Counter, the event data beforethe change may be converted into an invalid data.- If a write request or a read request to the data that has been de-leted by the online change is received, the SCS returns the errorIIN2.2 PARAMETER_ERROR.- If you perform online change on Binary Counter, the SCS clearsall Frozen Counters to 0.

This Device Properties is referred to "DNP3 SPECIFICATION, Version 2013, Novem-ber-2013".



Appendix 1.2 Capabilities for Device DatabaseTable Appendix 1.2-1 Capabilities for Device Database

SINGLE-BIT BINARY INPUT POINTSStatic (Steady-State) Object Number: 1Event Object Number: 2

Static Variation reported when variation 0requested or in response to Class polls :

[ ] Variation 1 - packed format[v] Variation 2 - with flag[ ] Based on point index

Event Variation reported when variation 0requested or in response to Class polls:

[ ] Variation 1 - without time[v] Variation 2 - with absolute time[ ] Variation 3 - with relative time[ ] Based on point index

Event reporting mode: [ ] Only most recent[v] All events

Binary Inputs included in Class 0 re-sponse:

[v] Always[ ] Never[ ] Only if the point is assigned to a class[ ] Based on point index

Binary Inputs Event Buffer Organization [ ] Fixed at[v] Configurable, range 0 to 135000- Configurable by DNP3 Communication Builder[ ] Configurable, selectable from , ,[ ] Configurable, other, describe

BINARY OUTPUT STATUS AND CONTROL RELAY OUTPUT BLOCKBinary Output Status Object Number: 10Binary Output Event Object Number 11CROB Object Number 12

Binary Output Status included in Class 0response:

[v] Always[ ] Never[ ] Only if point is assigned to a class[ ] Based on point index

Static Variation reported when variation 0requested or in response to Class polls:

[ ] Variation 1 - packed format[v] Variation 2 – output status with flag[ ] Based on point index

Event Variation reported when variation 0requested or in response to Class polls:

[ ] Variation 1 – status without time[v] Variation 2 – status with time[ ] Based on point index


Maximum Time between Select and Oper-ate:

[ ] Not Applicable[ ] Fixed at seconds[v] Configurable, range from 1 to 600 seconds- by DNP3 Communication Builder ; (default=5)[ ] Configurable, selectable from seconds[ ] Configurable, other, describe:[ ] Variable, explain:[ ] Based on point index

Binary Outputs Event Buffer Organization [ ] Fixed at ___________[v] Configurable, range 0 to 135000- Configurable by DNP3 Communication Builder[ ] Configurable, selectable from ____,____,____[ ] Configurable, other, describe_______________

COUNTERS/FROZEN COUNTERSStatic Counter Object Number: 20Static Frozen Counter Object Number: 21Counter Event Object Number: 22Frozen Counter Event Object Number: 23


<Appendix 1.2 Capabilities for Device Database> App.1-9


Table Appendix 1.2-1 Capabilities for Device Database (Table continued)

Static Counter Variation reported whenvariation 0 requested or in response toClass 0 polls:

[ ] Variation 1 - 32-bit with flag[ ] Variation 2 - 16-bit with flag[ ] Variation 5 - 32-bit without flag[ ] Variation 6 - 16-bit without flag[v] Based on point index (Variation 1 or 2)

Counter Event Variation reported whenvariation 0 requested or in response toClass 0 polls:

[ ] Variation 1 - 32-bit with flag[ ] Variation 2 - 16-bit with flag[ ] Variation 5 - 32-bit with flag and time[ ] Variation 6 - 16-bit with flag and time[v] Based on point index (Variation 5 or 6)

Counter included in Class 0 response: [v] Always[ ] Never[ ] Only if point is assigned to a class[ ] Based on point index

Counter Event reporting mode: [ ] A: Only most recent (value at time of event)[ ] B: Only most recent (value at time of response)[v] C: All events[ ] Based on point index

Static Frozen Counter Variation reportedwhen variation 0 requested or in responseto Class polls:

[ ] Variation 1 - 32-bit with flag[ ] Variation 2 - 16-bit with flag[ ] Variation 5 - 32-bit with flag and time[ ] Variation 6 - 16-bit with flag and tie[ ] Variation 9 – 32-bit without flag[ ] Variation 10 – 16-bit without flag[v] Based on point index (Variation 1 or 2)

Frozen Counter Event Variation reportedwhen variation 0 requested or in responseto Class polls:

[ ] Variation 1 - 32-bit with flag[ ] Variation 2 - 16-bit with flag[ ] Variation 5 - 32-bit with flag and time[ ] Variation 6 - 16-bit with flag and time[v] Based on point index (Variation 1 or 2)

Frozen Counters included in Class 0 re-sponse:

[v] Always (default)[v] Never (can be selected by DNP3 Communication Builder)[ ] Only if point is assigned to a class[ ] Based on point index

Frozen Counter Event reporting mode: [ ] A: Only most recent frozen value[v] B: All frozen values[ ] Based on point index

Counter Roll Over at: [ ] 16 Bits (65,535)[ ] 32 Bits (4,294,967,295)[ ] Other Fixed Value[ ] Configurable, range to[ ] Configurable, selectable from[ ] Configurable, other describe:[v] Based on point index (16 Bits (65,535) or 32 Bits(2,147,483,647))

Counter frozen by means of: [v] Master Request[ ] Freezes itself without concern for time of day[ ] Freezes itself and requires time of day[ ] Other, explain:

Counters Event Buffer Organization [ ] Fixed at ___________[v] Configurable, range 0 to 135000- Configurable by DNP3 Communication Builder[ ] Configurable, selectable from ____,____,____[ ] Configurable, other, describe_______________

Frozen Counters Event Buffer Organiza-tion

[ ] Fixed at ___________[v] Configurable, range 0 to 135000- Configurable by DNP3 Communication Builder[ ] Configurable, selectable from ____,____,____[ ] Configurable, other, describe_______________





ANALOG INPUT POINTSStatic (Steady-State) Object Number: 30Event Object Number: 32Analog Input Deadband Object Number: 34

Static Variation reported when variation 0requested or in response to Class 0 polls:

[ ] Variation 1 - 32-bit with flag[ ] Variation 2 - 16-bit with flag[ ] Variation 3 - 32-bit without flag[ ] Variation 4 - 16-bit without flag[ ] Variation 5 - single-precision floating point with flag[ ] Variation 6 - double-precision floating point with flag[v] Based on point index (variation 1, 2 or 5)

Event Variation reported when variation 0requested or in response to Class 0 polls:

[ ] Variation 1 - 32-bit without time[ ] Variation 2 - 16-bit without time[ ] Variation 3 - 32-bit with time[ ] Variation 4 - 16-bit with time[ ] Variation 5 - single-precision floating point w/o time[ ] Variation 6 - double-precision floating point w/o time[ ] Variation 7 - single-precision floating point with time[v] Variation 8 - double-precision floating point with time[v] Based on point index (Variation 2, 4 or 7)

Event reporting mode: [ ] A: Only most recent (value at time of event)[ ] B: Only most recent (value at time of response)[v] C: All events[ ] Based on point index

Analog Inputs included in Class 0 re-sponse:


How Deadbands are set: [ ] A. Global Fixed[ ] B. Configurable through DNP[v] C. Configurable via other means- by Multi Language Editor[ ] D. Other, explain[ ] Based on point index

Analog Input Deadband Algorithm: [v] Simple[ ] Integrating[ ] Other, explain[ ] Based on point index

Analog Inputs Event Buffer Organization: [ ] Fixed at ___________[v] Configurable, range 0 to 135000- Configurable by DNP3 Communication Builder[ ] Configurable, selectable from ____,____,____[ ] Configurable, other, describe_______________

ANALOG OUTPUT STATUS AND ANALOG OUTPUT CONTROL BLOCKAnalog Output Status Object Number: 40Analog Output Control Block Object Number 41Analog Output Event Object Number 42

Static Analog Output Status Variation re-ported when variation 0 requested or inresponse to Class 0 polls

[ ] Variation 1 - 32-bit with flag[ ] Variation 2 - 16-bit with flag[ ] Variation 3 - single-precision floating point with flag[ ] Variation 4 - double-precision floating point with flag[v] Based on point index (Variation 1, 2 or 3)

Analog Output Status included in Class 0response:






Event Variation reported when variation 0requested or in response to Class 0 polls:

[ ] Variation 1 - 32-bit without time[ ] Variation 2 - 16-bit without time[ ] Variation 3 - 32-bit with time[ ] Variation 4 - 16-bit with time[ ] Variation 5 - single-precision floating point w/o time[ ] Variation 6 - double-precision floating point w/o time[ ] Variation 7 - single-precision floating point with time[ ] Variation 8 - double-precision floating point with time[v] Based on point index (Variation 3, 4 or 7)


Maximum Time between Select and Oper-ate:

[ ] Not Applicable[ ] Fixed at seconds[v] Configurable, range from 1 to 600 seconds- by DNP3 Communication Builder (default=5)[ ] Configurable, range to seconds[ ] Configurable, selectable from seconds[ ] Configurable, other, describe:[ ] Variable, explain:[ ] Based on point index

Analog Outputs Event Buffer Organiza-tion:

[ ] Fixed at ___________[v] Configurable, range 0 to 135000- Configurable by DNP3 Communication Builder[ ] Configurable, selectable from ____,____,____[ ] Configurable, other, describe_______________

This Device Properties is referred to "DNP3 SPECIFICATION, Version 2013, Novem-ber-2013".



Appendix 1.3 Implementation TableTable Appendix 1.3-1 Implementation Table

DNP OBJECT GROUP & VARIATION REQUEST (SCS will parse) RESPONSE (SCS will re-spond)

ObjectGroup

Number

VariationNumber

Description FunctionCodes(dec)

Qualifier Codes(hex)

FunctionCodes(dec)


1 0 Binary Input - Anyvariation(Variation 0 is used torequest default varia-tion)

1 (read) 00, 01 (start-stop),06 (all),07, 08 (limitedqty),17, 28 (index)

- -

1 1 Binary Input - Packedformat


129 (re-sponse)

00, 01 (start-stop),17, 28 (index)

1 2 Binary Input - Withflags


129 (re-sponse)


2 0 Binary Input ChangeEvent - Any variation(Variation 0 is used torequest default varia-tion)

1 (read) 06 (all),07, 08 (limited qty)

- -

2 1 Binary Input ChangeEvent - Without time


129 (re-sponse)

17, 28 (index)

2 2 Binary Input ChangeEvent - With absolutetime


129 (re-sponse)

17, 28 (index)

10 0 Binary Output Status -Any variation(Variation 0 is used torequest default varia-tion)


- -

10 1 Binary Output Status -Packed format


129 (re-sponse)


10 2 Binary Output Status -Output status withflags


129 (re-sponse)


11 0 Binary Output Event -Any variation(Variation 0 is used torequest default varia-tion)

1 (read) 00, 01 (start-stop),06 (all)

- -

11 1 Binary Output Event -Status without time


129 (re-sponse)

17, 28 (index)

11 2 Binary Output Event -Status with time


129 (re-sponse)

17, 28 (index)


<Appendix 1.3 Implementation Table > App.1-13


Table Appendix 1.3-1 Implementation Table (Table continued)DNP OBJECT GROUP & VARIATION REQUEST (SCS will parse) RESPONSE (SCS will re-

spond)ObjectGroup

Number

VariationNumber



FunctionCodes(dec)


12 1 Binary Output Com-mand - Control relayoutput block (CROB)

03 (se-lect),04 (oper-ate),05 (directoperate),06 (directop, noack)

17, 28 (index) 129 (re-sponse)

17, 28 (index)

20 0 Counter - Any varia-tion(Variation 0 is used torequest default varia-tion)


- -

7 (freeze),8 (freezeno ack),9 (freeze& clear),10 (frz &clr, noack)

00, 01 (start-stop),06 (all)

- -

20 1 Counter - 32-bit withflag


129 (re-sponse)


20 2 Counter - 16-bit withflag


129 (re-sponse)


20 5 Counter - 32-bit with-out flag


129 (re-sponse)


20 6 Counter - 16-bit with-out flag


129 (re-sponse)


21 0 Frozen Counter -Anyvariation(Variation 0 is used torequest default varia-tion)


- -

21 1 Frozen Counter - 32-bit with flag


129 (re-sponse)






spond)ObjectGroup

Number

VariationNumber



FunctionCodes(dec)


21 2 Frozen Counter - 16-bit with flag


129 (re-sponse)


21 5 Frozen Counter - 32-bit with flag and time


129 (re-sponse)


21 6 Frozen Counter - 16-bit with flag and time


129 (re-sponse)


21 9 Frozen Counter - 32-bit without flag


129 (re-sponse)


21 10 Frozen Counter -16-bit without flag


129 (re-sponse)


22 0 Counter ChangeEvent - Any variation(Variation 0 is used torequest default varia-tion)


- -

22 1 Counter ChangeEvent - 32-bit with flag


129 (re-sponse)

17, 28 (index)

22 2 Counter ChangeEvent - 16-bit with flag


129 (re-sponse)

17, 28 (index)

22 5 Counter ChangeEvent -32-bit with flagand time


129 (re-sponse)

17, 28 (index)

22 6 Counter ChangeEvent -16-bit with flagand time


129 (re-sponse)

17, 28 (index)

23 0 Frozen CounterChange Event - Anyvariation(Variation 0 is used torequest default varia-tion)


- -

23 1 Frozen CounterChange Event - 32-bitwith flag


129 (re-sponse)

17, 28 (index)

23 2 Frozen CounterChange Event - 16-bitwith flag


129 (re-sponse)

17, 28 (index)





spond)ObjectGroup

Number

VariationNumber



FunctionCodes(dec)


23 5 Frozen CounterChange Event - 32-bitwith flag and time


129 (re-sponse)

17, 28 (index)

23 6 Frozen CounterChange Event - 16-bitwith flag and time


129 (re-sponse)

17, 28 (index)

30 0 Analog Input - Anyvariation(Variation 0 is used torequest default varia-tion)


- -

30 1 Analog Input - 32-bitwith flag


129 (re-sponse)


30 2 Analog Input - 16-bitwith flag


129 (re-sponse)


30 3 Analog Input - 32-bitwithout flag


129 (re-sponse)


30 4 Analog Input - 16-bitwithout flag


129 (re-sponse)


30 5 Analog Input - Single-precision, floating-point with flag


129 (re-sponse)


32 0 Analog Input ChangeEvent - Any variation(Variation 0 is used torequest default varia-tion)


- -

32 1 Analog Input ChangeEvent - 32-bit withouttime


129 (re-sponse)

17, 28 (index)

32 2 Analog Input ChangeEvent - 16-bit withouttime


129 (re-sponse)

17, 28 (index)

32 3 Analog Input ChangeEvent - 32-bit withtime


129 (re-sponse)

17, 28 (index)

32 4 Analog Input ChangeEvent - 16-bit withtime


129 (re-sponse)

17, 28 (index)





spond)ObjectGroup

Number

VariationNumber



FunctionCodes(dec)


32 5 Analog Input ChangeEvent - Single-preci-sion, floating-pointwithout time


129 (re-sponse)

17, 28 (index)

32 7 Analog Input ChangeEvent - Single-preci-sion, floating-pointwith time


129 (re-sponse)

17, 28 (index)

34 0 Analog Input Dead-band - Any variation(Variation 0 is used torequest default varia-tion)


- -

34 1 Analog Input Dead-band - 16-bit


129 (re-sponse)


34 2 Analog Input Dead-band - 32-bit


129 (re-sponse)


34 3 Analog Input Dead-band - Single-preci-sion, floating-point


129 (re-sponse)


40 0 Analog Output Status- Any variation (Varia-tion 0 is used to re-quest default varia-tion)


- -

40 1 Analog Output Status- 32-bit with flag


129 (re-sponse)


40 2 Analog Output Status- 16-bit with flag


129 (re-sponse)


40 3 Analog Output Status- Single-precision,floating-point with flag


129 (re-sponse)






spond)ObjectGroup

Number

VariationNumber



FunctionCodes(dec)


41 1 Analog Output Com-mand - 32-bit



17, 28 (index)

41 2 Analog Output Com-mand - 16-bit



17, 28 (index)

41 3 Analog Output Com-mand - Single-preci-sion, floating-point



17, 28 (index)

42 0 Analog OutputChange Event - Anyvariation(Variation 0 is used torequest default varia-tion)


- -

42 1 Analog OutputChange Event - 32-bitwithout time


129 (re-sponse)

17, 28 (index)

42 2 Analog OutputChange Event - 16-bitwithout time


129 (re-sponse)

17, 28 (index)

42 3 Analog OutputChange Event - 32-bitwith time


129 (re-sponse)

17, 28 (index)

42 4 Analog OutputChange Event - 16-bitwith time


129 (re-sponse)

17, 28 (index)

42 5 Analog OutputChange Event - Sin-gle-precision, floating-point without time


129 (re-sponse)

17, 28 (index)

42 7 Analog OutputChange Event - Sin-gle-precision, floating-point with time


129 (re-sponse)

17, 28 (index)





spond)ObjectGroup

Number

VariationNumber



FunctionCodes(dec)


50 1 Time and Date - Ab-solute time

1 (read) 07 (quantity = 1) 129 (re-sponse)

07 (quantity = 1)

2 (write) 07 (quantity = 1) - -

50 3 Time and Date - Ab-solute time at last re-corded time

2 (write) 07 (quantity = 1) - -

60 1 Class 0 Data 1 (read) 06 (all) - -

60 2 Class 1 Data 1 (read) 06 (all),07, 08 (limited qty)

- -


- -


- -

80 1 Internal Indications -Packed format

1 (read) 00, 01 (start-stop) - -

2 (write) 00 index=7 (start-stop)

- -

This Implementation Table is referred to "DNP3 SPECIFICATION, Volume 6 Part2, Objects,DNP3 OBJECT LIBRARY Version 2.04, 15-March-2009".



Revision informationTitle : Open Interface

Manual No. : IM 32Q05B10-31E

Jan. 2015/4th Edition/R3.02.20 or later*

*: Denotes the release number of the Software Product corresponding to the contents of this Man-ual. The revised contents are valid until the next edition is issued.

Introduction ProSafe-RS Document Map has been deleted, and a description of Safety,Protection, and Modification of the Product has been changed.

Part B, Part C Reordered the Parts.

B1.1, B1.4, B1.5, B1.6 Changes have been made to support the ProSafe-SLS communicationfunction.

B4 "ProSafe-SLS communication (for ALR121)" has been created.

C3.2 "Connection Device" has been added and a description of "Port Number"has been changed.

Part D "DNP3 slave function" has been created.

Appendix 1 "DNP3 Field Device Profile" has been created.

Oct. 2013/3rd Edition/R3.02.10 or later

Introduction Description of station types has been changed.

B1.2 Feature name "Writing to a single holding register" has been changed to"16-bit Modbus master support mode" and descriptions have beenchanged.

B1.5.1 Variables to which a Modbus device address can be assigned have beenadded.

B1.7 Descriptions of function codes have been changed. An error code andnotes on individual function codes have been added.

Dec. 2012/2nd Edition/R3.02 or later

A2, A3, and Part B Entire contents have been revised.

Aug. 2011/1st Edition/R3.01 or laterNewly published

n

For Questions and More InformationOnline Query: A query form is available on the following URL for online query.http://www.yokogawa.com/iss

n Written by Yokogawa Electric Corporationn Published by Yokogawa Electric Corporation

2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN

Rev-1


user's manual open interfaces - yokogawa electric · user's manuals (im), technical...

Documents