Toc J-1

CS 1000/CS 3000
Reference
Subsystem Communication (Using RIO)
IM 33S01B30-01E 16th Edition

CONTENTS
PART-J
J1.

Subsystem Communication (Using RIO)

General Information Regarding to Subsystem Communication ........ J1-1
J1.1

How to Connect the Subsystem ................................................................... J1-4

J1.2

Subsystem Data Identification ..................................................................... J1-7

J1.3

Accessing Subsystem Data from a Function Block .................................. J1-10

J1.4

Subsystem Data Type ................................................................................. J1-24

J1.5

Overview of Setting Items Related to the Subsystem ............................... J1-26

J1.6

J2.

J1.5.1

Overview of Setting Items on System View .................................... J1-27

J1.5.2

Overview of Settings on Communication I/O Builder ..................... J1-38

On-Line Maintenance .................................................................................. J1-45

Communication I/O Module .................................................................. J2-1

J2.1

Communication Module (ACM11, ACM12) ................................................... J2-2

J2.1.1

J2.2

J3.

Communication Specifications ACM11 and ACM12 ...................... J2-3

Communication Module (ACM21, ACM22, ACM71) ..................................... J2-4

J2.2.1

Communication Specifications ACM21 and ACM22 ...................... J2-5

J2.2.2

Communication Specifications ACM71 ......................................... J2-6

J2.3

System Alarm Messages Specific to the Communication Module ............ J2-7

J2.4

System Alarm Messages Specific to Ethernet Communication ............... J2-12

FA-M3 Communication (ACM11, ACM12)............................................. J3-1

J3.1

Communication Specifications FA-M3 ...................................................... J3-2

J3.2

Connecting FCS and FA-M3 ......................................................................... J3-5

J3.3

Accessible Devices FA-M3 ...................................................................... J3-12

J3.4

Subsystem Data Storing Format FA-M3.................................................. J3-14

J3.5

Setting Items on System View FA-M3 ...................................................... J3-16

J3.6

Setting Items on Communication I/O Builder FA-M3 .............................. J3-19

J3.7

System Alarm Messages Specific to FA-M3 .............................................. J3-25

J3.8

Settings on Subsystem FA-M3 ................................................................ J3-31

J3.9

Transmission Time between Communication Module and FA-M3 ........... J3-35

IM 33S01B30-01E 16th Edition : Dec.10,2007-00

Toc J-2
J4.

J5.

J6.

J7.

FA-M3 Communication (ACM71) .......................................................... J4-1

J4.1

Communication Specifications FA-M3 ..................................................... J4-2

J4.2

Connecting FCS and FA-M3 ......................................................................... J4-3

J4.3

Accessible Devices FA-M3 ........................................................................ J4-6

J4.4

Subsystem Data Storing Format FA-M3 ................................................... J4-7

J4.5

Setting Items on System View FA-M3 ....................................................... J4-8

J4.6

Setting Items on Communication I/O Builder FA-M3 ............................. J4-10

J4.7

Settings on Subsystem FA-M3 ................................................................ J4-15

J4.8

System Alarm Messages Specific to FA-M3 .............................................. J4-17

J4.9

Transmission Time between Communication Card and FA-M3 ............... J4-18

DARWIN Communication ..................................................................... J5-1

J5.1

Communication Specifications DARWIN ................................................. J5-2

J5.2

Connecting FCS and DARWIN ..................................................................... J5-4

J5.3

Accessible Data DARWIN .......................................................................... J5-8

J5.4

Subsystem Data Storing Format DARWIN ................................................ J5-9

J5.5

Setting Items on System View DARWIN ................................................. J5-10

J5.6

Setting Items on Communication I/O Builder DARWIN .......................... J5-13

J5.7

Communication Packet DARWIN ............................................................ J5-17

J5.8

System Alarm Messages Specific to DARWIN .......................................... J5-19

J5.9

Error Handling when a Communication Error Occurs .............................. J5-24

J5.10

Transmission Time between Communication Module and DARWIN ....... J5-29

Gas Chromatography Communication................................................ J6-1

J6.1

Communication Specifications Gas Chromatography ............................ J6-2

J6.2

Connecting FCS and Gas Chromatography ................................................ J6-4

J6.3

Reading Gas Chromatography Data ............................................................ J6-6

J6.4

Writing Data to Gas Chromatography ........................................................ J6-11

J6.5

Setting Items on System View Gas Chromatography ............................ J6-14

J6.6

Setting Items on Communication I/O Builder Gas Chromatography .... J6-18

J6.7

System Alarm Messages Specific to Gas Chromatography ..................... J6-22

J6.8

Precautionary Notes for Gas Chromatography Communication ............. J6-24

YS Instrument Communication ............................................................ J7-1

J7.1

Communication Specifications YS Instrument ........................................ J7-2

J7.2

Connecting FCS and YS Instrument ............................................................ J7-3

J7.3

Accessible Data YS Instrument ................................................................. J7-6

J7.4

Setting Items on System View YS Instrument .......................................... J7-7

J7.5

Setting Items on Communication I/O Builder YS Instrument ................ J7-10

J7.6

System Alarm Messages Specific to YS Instruments ............................... J7-16

J7.7

Transmission Time for YS Instrument ....................................................... J7-19

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

Toc J-3
J8.

J9.

MELSEC-A Communication (ACM11, ACM12) ..................................... J8-1

J8.1

Communication Specifications MELSEC-A ............................................. J8-3

J8.2

Connecting FCS and MELSEC-A ................................................................. J8-6

J8.3

Accessible Devices MELSEC-A .............................................................. J8-14

J8.4

Subsystem Data Storing Format MELSEC-A .......................................... J8-17

J8.5

Setting Items on System View MELSEC-A ............................................. J8-19

J8.6

Setting Items on Communication I/O Builder MELSEC-A ...................... J8-23

J8.7

Settings on Subsystem MELSEC-A ........................................................ J8-29

J8.8

System Alarm Messages Specific to MELSEC-A ...................................... J8-40

J8.9

Transmission Time between Communication Module and MELSEC ....... J8-44

MELSEC-A Communication (ACM71) .................................................. J9-1

J9.1

Communication Specifications MELSEC-A ............................................. J9-4

J9.2

Connecting FCS and MELSEC-A ................................................................. J9-5

J9.3

Accessible Devices MELSEC-A ................................................................ J9-7

J9.4

Subsystem Data Storing Format MELSEC-A ............................................ J9-9

J9.5

Setting Items on System View MELSEC-A ............................................. J9-10

J9.6

Setting Items on Communication I/O Builder MELSEC-A ...................... J9-12

J9.7

MELSEC-A Communication Transactions ................................................. J9-17

J9.8

Settings on Subsystem MELSEC-A ........................................................ J9-20

J9.8.1

Setting Switches of Ethernet Interface Units .................................. J9-21

J9.8.2

Communication Program on the MELSEC-A ................................. J9-24

J9.9

System Alarm Messages Specific to MELSEC-A ...................................... J9-31

J9.10

Transmission Time between Communication Card and MELSEC-A ....... J9-32

J9.11

Troubleshooting .......................................................................................... J9-35

J10. Modbus Communication (ACM11, ACM12) ....................................... J10-1

J10.1

Communication Specifications Modbus ................................................ J10-2

J10.2

Connecting FCS and Modbus PLC ............................................................ J10-5

J10.3

Accessible Devices Modbus ................................................................. J10-13

J10.4

Subsystem Data Storing Format Modbus ............................................ J10-17

J10.5

Setting Items on System View Modbus ................................................ J10-19

J10.6

Setting Items on Communication I/O Builder Modbus ......................... J10-22

J10.7

Recovery Communication Modbus ...................................................... J10-27

J10.8

Communication Packet Modbus ........................................................... J10-29

J10.9

Dual-Redundant Communication Modbus ........................................... J10-31

J10.10 System Alarm Messages Specific to Modbus PLC ................................. J10-39

J10.11

Transmission Time between Communication Module and Modbus

PLC ............................................................................................................ J10-43

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

Toc J-4
J11. A-B Communication ............................................................................ J11-1
J11.1

Communication Specifications PLC-5 ..................................................... J11-2

J11.2

Connecting FCS and PLC-5 ......................................................................... J11-4

J11.3

Accessible Files PLC-5 ........................................................................... J11-10

J11.4

Subsystem Data Storing Format PLC-5 ................................................. J11-12

J11.5

Setting Items on System View PLC-5 ..................................................... J11-13

J11.6

Setting Items on Communication I/O Builder PLC-5 ............................. J11-16

J11.7

Communication Packet PLC-5 ............................................................... J11-21

J11.8

System Alarm Messages Specific to PLC-5 ............................................. J11-24

J11.9

Transmission Time between Communication Module and PLC-5 .......... J11-28

J12. SYSMAC Communication .................................................................. J12-1

J12.1

Communication Specifications SYSMAC ............................................... J12-2

J12.2

Connecting FCS and SYSMAC ................................................................... J12-4

J12.3

Accessible Devices SYSMAC .................................................................. J12-9

J12.4

Subsystem Data Storing Format SYSMAC ........................................... J12-10

J12.5

Setting Items on System View SYSMAC ................................................ J12-11

J12.6

Setting Items on Communication I/O Builder SYSMAC ....................... J12-14

J12.7

Communication Text SYSMAC .............................................................. J12-19

J12.8

System Alarm Messages Specific to SYSMAC ....................................... J12-25

J12.9

Transmission Time between Communication Module and SYSMAC .... J12-30

J13. Siemens Communication ................................................................... J13-1

J13.1

Communication Specifications SIMATIC S5 ........................................... J13-2

J13.2

Connecting FCS and SIMATIC S5 .............................................................. J13-6

J13.3

Accessible Devices SIMATIC S5 ............................................................ J13-11

J13.4

Subsystem Data Storing Format SIMATIC S5 ....................................... J13-12

J13.5

Setting Items on System View SIMATIC S5 .......................................... J13-15

J13.6

Setting Items on Communication I/O Builder SIMATIC S5 ................... J13-19

J13.7

Communication Packet SIMATIC S5 ..................................................... J13-23

J13.8

System Alarm Messages Specific to SIMATIC S5 ................................... J13-24

J13.9

Transmission Time between Communication Module and SIMATIC S5 .... J13-29

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

Toc J-5
J14. DARWIN/DAQSTATION Communication (ACM71) ............................ J14-1
J14.1

Communication Specifications DARWIN/DAQSTATION ........................ J14-3

J14.2

Connecting FCS and DARWIN/DAQSTATION ........................................... J14-4

J14.3

Accessible Data DARWIN/DAQSTATION ................................................ J14-6

J14.4

Subsystem Data Storing Format DARWIN/DAQSTATION ...................... J14-7

J14.5

Setting Items on System View DARWIN/DAQSTATION .......................... J14-9

J14.6

Setting Items on Communication I/O Builder

DARWIN/DAQSTATION ........................................................................... J14-11

J14.7

Settings on Subsystem DARWIN/DAQSTATION .................................. J14-18

J14.8

Communication Packet DARWIN/DAQSTATION .................................. J14-19

J14.9

J14.8.1

Communication Packet Used for Communicating with DARWIN .. J14-20

J14.8.2

Communication Packet Used for Communicating with

DAQSTATION ............................................................................. J14-22

Data Acquired from DARWIN/DAQSTATION ............................................ J14-26

J14.10 System Alarm Messages Specific to DARWIN/DAQSTATION ................ J14-35

J14.11

Error Handling when Communication Error Occurs

DARWIN/DAQSTATION .......................................................................... J14-37
J14.11.1 Communication Errors when Communicating with DARWIN ........ J14-38
J14.11.2 Communication Errors when Communicating with
DAQSTATION ............................................................................. J14-41

J14.12 Transmission Time between Communication Card

and DARWIN/DAQSTATION ...................................................................... J14-46

J15. SLC 500 Communication (ACM11) ..................................................... J15-1

J15.1

Communication Specifications SLC 500 ................................................ J15-2

J15.2

Connecting FCS and SLC 500 .................................................................... J15-4

J15.3

Accessible Files SLC 500 ........................................................................ J15-8

J15.4

Subsystem Data Storing Format SLC 500 .............................................. J15-9

J15.5

Setting Items on System View SLC 500 ................................................ J15-10

J15.6

Setting Items on Communication I/O Builder SLC 500 ........................ J15-13

J15.7

System Alarm Messages Specific to SLC 500 ......................................... J15-17

J15.8

Transmission Time between Communication Module and SLC 500 ...... J15-21

J16. PLC-5/SLC 500 Communication (ACM71) ......................................... J16-1

J16.1

Communication Specifications PLC-5/SLC 500 ..................................... J16-2

J16.2

Connecting FCS and PLC-5/SLC 500 ......................................................... J16-3

J16.3

Accessible Files PLC-5/SLC 500 ............................................................. J16-5

J16.4

Subsystem Data Storing Format PLC-5/SLC 500 ................................... J16-7

J16.5

Setting Items on System View PLC-5/SLC 500 ....................................... J16-8

J16.6

Setting Items on Communication I/O Builder PLC-5/SLC 500 ............. J16-10

J16.7

Setting on Subsystem PLC-5/SLC 500 .................................................. J16-16

J16.8

System Alarm Messages Specific to PLC-5/SLC 500 .............................. J16-17

J16.9

Transmission Time between Communication Card

and PLC-5/SLC 500 ................................................................................... J16-18

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

Toc J-6
J17. Modbus Communication (ACM71) ..................................................... J17-1
J17.1

Communication Specifications Modbus ................................................ J17-3

J17.2

Connecting FCS and Modbus/TCP PLC .................................................... J17-5

J17.3

Accessible Devices Modbus ................................................................... J17-7

J17.4

Subsystem Data Storing Format Modbus ............................................. J17-11

J17.5

Setting Items on System View Modbus ................................................ J17-14

J17.6

Setting Items on Communication I/O Builder Modbus ........................ J17-16

J17.7

Settings on Subsystem Modbus ........................................................... J17-21

J17.8

Dual-Redundant Communication Modbus ........................................... J17-22

J17.9

System Alarm Messages Specific to Modbus/TCP PLC ......................... J17-25

J17.10 Transmission Time between Communication Card

and Modbus/TCP PLC ............................................................................... J17-27

IM 33S01B30-01E 14th Edition : Dec.26,2006-00

J1-1

<J1. General Information Regarding to Subsystem Communication>

J1. General Information Regarding to

Subsystem Communication
The subsystem communication package is used to perform communication between
the FCS and PLC (Programmable Logic Controller) using communication I/O.
This chapter explains those subsystem communication package functions that do
not depend on the subsystem machine manufacturer nor the machine type.
How to connect the FCS with subsystem
Subsystem data identification
Accessing subsystem data from a function block
Subsystem data type
Overview of setting items related to the subsystem
On-line maintenance

Overview of Subsystem Communications

In subsystem communication, communication with subsystem can be performed using the
following two methods:
Perform communication by downloading the subsystem communication package,
which is offered as an option package, to the communication module (ACM11 or
ACM12) (*1) or communication card.
Perform FCS-C (*2) communication task by downloading a program written in C Language to the communication module (ACM21, ACM22 or ACM71) (*3).
*1: ACM11
RS-232C communication module
ACM12
RS-422/RS485 communication module
*2: FCS-C is an option package, when implementing this package, please contact to Yokogawa Electric
Corporation.
*3: ACM21
RS-232C communication card
ACM22
RS-422/RS485 communication card
ACM71
Ethernet communication module

FCS
Control
function
Communication module
(ACM11, ACM12)

Subsystem
communication
package

Subsystem

Communication module
I/O image area
Communication card
(ACM21, ACM22,
ACM71)

FCS-C

Subsystem
J010001E.EPS

Figure Overview of Subsystem Communication

This section explains only the communication method using the subsystem communication
package.
Hereinafter, Communication modules and Communication cards are all referred to as
communication modules.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1. General Information Regarding to Subsystem Communication>

J1-2

Available Subsystem Communication Packages

Subsystem communication packages are available for following models:
FA-M3 communication package (ACM11, ACM12) (for use with Yokogawa Electrics
FA-M3)
FA-M3 communication package (ACM71) (for use with Yokogawa Electrics FA-M3)
DARWIN communication package (ACM11) (for use with Yokogawa Electrics DARWIN series data acquisition unit DA100, hybrid recorder DR231, DR232, DR241 and
DR242)
Gas chromatography communication package (ACM21) (for use with Yokogawa
Electrics GC1000/GC8)
YS communication package (ACM12) (for use with Yokogawas YEWSERIES 80/
YS100 series/YS1000 series devices)
MELSEC-A communication package (ACM11, ACM12) (for use with Mitsubishi
Electrics PLC, MELSEC-A)
MELSEC-A communication package (ACM71) (for use with Mitsubishi Electrics PLC
MELSEC-A)
Modbus communication package (ACM11, ACM12) (for use with Schneider Electrics
Modicon, and Yaskawa Electrics Memocon-SC)
A-B communication package (ACM11, ACM12) (for use with Rockwell Automations
PLC-5 family)
SYSMAC communication package (ACM11, ACM12) (for use with Omrons SYSMAC
C series)
Siemens communication package (ACM11, ACM12) (for use with Siemens SIEMENS
PLS SIMATIC S5)
DARWIN/DAQSTATION communication package (ACM71) (for use with Yokogawa
Electrics DARWIN series Data Acquisition Unit DA100, Data Collector DC100, Hybrid
Recorder DR231, DR232, DR241 and DR242, and DAQSTATION DX series products)
SLC500 communication package (ACM11) (for use with Rockwell Automations SLC
500 family products)
PLC-5/SLC500 communication package (ACM71) (for use with Rockwell Automations
PLC-5/SLC 500 family products)
Modbus communication package (ACM71) (for use with Schneider Electrics Modicon
Quantum and Premium)

IM 33S01B30-01E

15th Edition : Jun.27,2007-00

<J1. General Information Regarding to Subsystem Communication>

J1-3

SEE ALSO
For the subsystem communication package to be used for details on the functions of each communication
package, see the followings:
J3, FA-M3 Communication (ACM11, ACM12)
J4, FA-M3 Communication (ACM71)
J5, DARWIN Communication
J6, Gas Chromatography Communication
J7, YS Instrument Communication
J8, MELSEC-A Communication (ACM11, ACM12)
J9, MELSEC-A Communication (ACM71)
J10, Modbus Communication (ACM11, ACM12)
J11, A-B Communication
J12, SYSMAC Communication
J13, Siemens Communication
J14, DARWIN/DAQSTATION Communication (ACM71)
J15, SLC 500 Communication (ACM11)
J16, PLC-5/SLC 500 Communication (ACM71)
J17, Modbus Communication (ACM71)

IMPORTANT
The communication package in the communication module is the protocol for Master.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.1 How to Connect the Subsystem>

J1-4

J1.1 How to Connect the Subsystem

In order to communicate with subsystem, the communication module must be
installed to the FCS and connected to the subsystem.
This section outlines how to connect the CS 1000/CS 3000 with subsystem.
SEE ALSO
For details on how to connect the CS 1000/CS 3000 to different manufacturers subsystems, see the
explanation of the communication package for each subsystem:
J3.2, Connecting FCS and FA-M3
J4.2, Connecting FCS and FA-M3
J5.2, Connecting FCS and DARWIN
J6.2, Connecting FCS and Gas Chromatography
J7.2, Connecting FCS and YS Instrument
J8.2, Connecting FCS and MELSEC-A
J9.2, Connecting FCS and MELSEC-A
J10.2, Connecting FCS and Modbus PLC
J11.2, Connecting FCS and PLC-5
J12.2, Connecting FCS and SYSMAC
J13.2, Connecting FCS and SIMATIC S5
J14.2, Connecting FCS and DARWIN/DAQSTATION
J15.2, Connecting FCS and SLC 500
J16.2, Connecting FCS and PLC-5/SLC 500
J17.2, Connecting FCS and Modbus/TCP PLC

The Communication Modules Used

The following communication modules are used to connect the CS 1000/CS 3000 with
subsystem.
ACM11:

RS-232C communication module

ACM12:

RS-422/RS-485 communication module

ACM21:

RS-232C communication card (*1) (*2)

ACM22:

RS-422/RS-485 communication card (*1) (*2)

ACM71:

Ethernet communication module (*3) (*4)

*1:
*2:
*3:
*4:

ACM21/ACM22 communication cards can be applied in enhanced type PFCS.

ACM21/ACM22 communication cards can be applied in SFCS.
ACM71 communication module can only be applied for enhanced type PFCS.
ACM71 communication module can only be applied for SFCS.

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J1.1 How to Connect the Subsystem>

J1-5

Installing the Communication I/O Module

The communication I/O modules are installed in the dedicated communication module
nest.
The installation position for the communication I/O modules are shown below:

IMPORTANT
A non communication I/O module such as AMM or ADM cannot be used with a communication I/O module in the same communication I/O module nest.
SEE ALSO
For details on how to install the communication I/O module, see the following:
A3, Input & Output Modules in Input & Output Modules (IM 33Y06K01-01E)

ACM11 and ACM12

The table below shows the position where the ACM11 and ACM12 communication modules are installed.
Table Installation Position of the Communication Module ACM11 and ACM12
Communication module

Communication module nest (AMN33)

Slot No. 1

Slot No. 2

ACM11
(RS-232C communication module)

Can be installed

Can be installed

ACM12
(RS-422/RS-485 communication module)

Can be installed

Can be installed

Remarks

J010101E.EPS

Two communication modules can be installed in one AMN33. The ACM11 and ACM12 can
be installed together in the slots of the same nest.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

J1-6

<J1.1 How to Connect the Subsystem>

ACM21 and ACM22 : Enhanced Type PFCS/SFCS

The table below shows the position where the ACM21, ACM22 and ACM71 communication
modules are installed.
Table Installation Position of the Communication Module ACM21 and ACM22 : Enhanced Type
PFCS/SFCS
Communication module

Communication card nest (AMN51)

Slot No. 1

Slot No. 2

ACM21
(RS-232C communication card)

Can be installed

Can be installed

ACM22
(RS-422/RS-485 communication card)

Can be installed

Can be installed

Remarks

J010102E.EPS

Two communication modules can be installed in the slots of the same AMN51. The ACM21
and ACM22 can be installed together in the slots of the same nest.
AMN51 communication module nest can be only installed on the number 2 nest position on
FCS (*1) (*2).
*1:
*2:

AMN51 communication card nest can be applied on enhanced type PFCS.

AMN51 communication card nest can be applied on SFCS.

ACM71: Enhanced Type PFCS/SFCS

The installable positions for ACM71 are shown in the following table.
Table Installation Position of the Communication Module ACM71 : Enhanced Type PFCS/SFCS
Communication module
ACM71
(Ethernet communication module)

Communication card nest (AMN51)

Slot No. 1

Slot No. 2

Can be installed

Can be installed

Remarks

J010103E.EPS

In one AMN51 Nest, two communication modules can be installed. ACM71 and ACM21 or
ACM22 can be installed in the same nest.
The AMN51 nest can only be installed on the Nest Position 2 in an FCS (*1) (*2).
*1:
*2:

AMN51 nest for communication modules can only be installed in enhanced type PFCS.
AMN51 nest for communication modules can only be installed in SFCS.

Yokogawa Connecting Cable

Yokogawa Electric Co. provides the following two types of RS-232C cables for connecting
the Communication module and subsystem.
RS-232C modem cable
This is for connecting the communication I/O module (ACM11 and ACM21) to a
modem.
RS-232C null modem cable
This is for connecting the communication I/O module (ACM11 and ACM21) to subsystem.
SEE ALSO
For details on the cables for the connection between communication modules and subsystem, see the
following:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J1.2 Subsystem Data Identification>

J1-7

J1.2 Subsystem Data Identification

In subsystem communication, subsystem data are identified by the element numbers.
This section explains the identification method of the analog data and discrete
I/O data that are assigned to the regulatory control block, sequence control block
and other blocks.

Element Numbers for Data Handled by Subsystem

Element

Data handled by subsystem are identified by their element numbers.

There are the following two types of element numbers.
Table Element Numbers for Subsystem Data
Access method Element number

Explanation

Word data

%WWnnnn

nnnn is a number within the area. The head is 0001.

Bit data

%WBnnnnbb

nnnn is a number within the area. The head is 0001.

bb is a bit number (1 to 16) within the word. The most significant bit is 1.
J010201E.EPS

The same data may be accessed both in word units and bit units. For example, each bit in
the 16-bit data %WW0020 can be accessed respectively as %WB002001 to
%WB002016.
16 bit

Word unit
%WW0020

Bit unit
%WB002003

16

J010202E.EPS

Figure Identifying Data in Word Units and Bit Units

The following figure illustrates an example of connecting with word data.

IN

FIC1001

OUT

PID

%WW0001

%WW0003
J010203E.EPS

Figure Subsystem Data (Word Data) Link Example

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.2 Subsystem Data Identification>

J1-8

Designating Communication Input Conversion

When subsystem data is linked to the IN terminal or feedback (FB) terminal of a function
block: it may require to define communication input conversion. The items for communication input conversion are listed below:
Data conversion gain
Data conversion bias
Input high limit detection setpoint (IOP+)
Input low limit detection setpoint (IOP-)
SEE ALSO
For details on communication input conversion, see the following:
J1.3, Accessing Subsystem Data from a Function Block

Designating Communication Output Conversion

When subsystem data is linked to the OUT terminal of a function block, it may require to
designate communication output conversion. The items for communication output conversion are listed below:
Data conversion gain
Data conversion bias
SEE ALSO
For details on communication output conversion, see the following:
J1.3, Accessing Subsystem Data from a Function Block

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

J1-9

<J1.2 Subsystem Data Identification>

Data Items for Handling Subsystem Data

Table Data Items for Handling Subsystem Data
Identifier
%WWnnnn

%WBnnnnbb

Data item

Description

PV

For word data access. The data format depends on the communication
protocol.

PV

For bit data access. Returns 1 or 0 for designated bit ON/OFF state.

PV16

For accessing a 16-bit datum starts from the designated bit towards
LSB (Lease Significant Bit).

PVI16 (*1)

For accessing 16-bit signed integer data.

PVU16 (*1)

For accessing 16-bit unsigned integer data.

PVI32 (*1)

For accessing 32-bit signed long integer data.

PVU32 (*1)

For accessing 32-bit unsigned long integer data.

PVF32 (*1)

For accessing 32-bit single-precision floating-point data.

PVF64 (*1)

For accessing 64-bit double-precision floating-point data.

OPMK

Returns the operation mark assignment of the designated bit.

J010204E.EPS

*1:

The data type exists for %WB but can not be accessed (reference/set) from function blocks.

When data buffered in %WB are accessed using PV16, the 16-bit data are accessed
starting at the bit designated by %WBnnnnbb as the most significant bit, towards the least
significant bit (when reaching the word boundary, it continues to the next word).
However, an error will occur if the same bit is defined to be accessed by more than one
%WB element.
When using %WB to access the word data, it subjects to the following restrictions.
Starting bit number (bb) should be 01, otherwise, error will occur.
An error will occur when the same bit is defined to be accessed by more than one
%WB element.
When write a datum to a %WB(nnnn), and the datum has different format from that
specified in the Data Item for that %WB, an error will occur. If that %WB has not been
specified with a data format, the datum will be forced into that %WB with its own
format.
When reading the data of PVF32 or PVF64 type, if the data are (+/-) infinite or NaN
(Non-numeric), errors will occur.

Data Statuses Handled for Subsystem

Table Data Statuses Handled for Subsystem
Data status

Meaning

BAD

Invalid Data Value.

NRDY

Can not properly access data during power breakage recovery or similar situation.

LPFL

Malfunction of the communication module or communication error with the connected device.

NR (*1)

Data are properly communicated.

J010205E.EPS

*1:

In reality, there is no such status as NR; it indicates a state that none of BAD, NRDY or LPFL is present.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.3 Accessing Subsystem Data from a Function Block>

J1-10

J1.3 Accessing Subsystem Data from a Function

Block
Subsystem data can be acquired from the regulatory control block, sequence control block, SFC block and other function blocks using the subsystem communication
package. Also, data can be set into the subsystem from function blocks by using the
subsystem communication package.
This section explains how to access subsystem data form a function block.

Overview of Accessing Subsystem Data

Accessing subsystem data varies according to the type of communication module used.
The figure below shows the flow of data between function blocks and subsystem when
ACM11 or ACM12 is used:
FCS

Regulatory control block

Sequence control
block

SFC block

SEBOL
I N

OUT

Data inquiry/setting

ssread
sswrite
sswritebit

Data inquiry/setting

Regulatory control block/sequence control block data region

(*1)
Communication module
(ACM11, ACM12)

Communication module I/O image

Subsystem
communication Package

Communication content
definition database

Subsystem

Serial communication
(RS-232C, RS-422/RS-485)

Subsystem data

J010301E.EPS

*1:

RIO bus communication may be applied in LFCS2 or LFCS.

Figure Data Flow between the Function Blocks and Subsystem (when ACM11 or ACM12 is used)

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.3 Accessing Subsystem Data from a Function Block>

J1-11

The figure below shows the flow of data between function blocks and subsystem when
ACM21 or ACM22 is used:
FCS
Regulatory control
block

Sequence control
block

SFC block

SEBOL
I N

OUT

Data inquiry/setting

Data inquiry/setting

ssread
sswrite
sswritebit

Communication module I/O data area

Communication package

Communication module
(ACM21, ACM22)

Subsystem

Serial communication
(RS-232C, RS-422/RS-485)

Subsystem data

J010302E.EPS

Figure Data Flow between the Function Blocks and Subsystem (when ACM21 or ACM22 is used)

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.3 Accessing Subsystem Data from a Function Block>

J1-12

The figure below shows the flow of data between function blocks and subsystem when
ACM71 is used:
FCS
Regulatory control
block

Sequence control
block

SFC block

SEBOL
I N

OUT

Data inquiry/setting

Data inquiry/setting

ssread
sswrite
sswritebit

Communication module I/O data area

Communication package

Communication module
(ACM71)

Subsystem

Serial communication
(RS-232C, RS-422/RS-485)

Subsystem data

J010303E.EPS

Figure Data Flow between the Function Blocks and Subsystem (when ACM71 is used)

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.3 Accessing Subsystem Data from a Function Block>

J1-13

How to Access Subsystem Data

For a regulatory control block or sequence control block, the subsystem can be accessed in
fixed cycles by defining the contents of the data communication with the subsystem via the
Communication I/O Builder.
Same as analog I/O modules and digital I/O modules, subsystem data can be accessed by
performing data connection to the address defined via the Communication I/O Builder in
the case of a regulatory control or calculation block, and by performing sequence connection in the case of a sequence block.
SEE ALSO
For details regarding I/O connection, see the following:
C2, I/O Connection

In the case of SFC blocks, subsystem data defined via the Communication I/O Builder can
be accessed by using SEBOL statements specifically for accessing subsystem data.
ssread is used for reading, while sswrite and sswritebit are used for writing.
SEE ALSO
For details regarding SFC functions, see the following:
D5, Sequential Function Chart
For details regarding SEBOL functions, see the following:
H1.7, Subsystem Communication

How to Access Subsystem Data for Each I/O Type

The method for accessing subsystem data from a function block will vary depending on the
subsystem data I/O type as follows.
Access in the case of analog input and feedback input
Access in the case of analog output
Access in the case of discrete input and output
The method for each of the above will be explained next.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J1.3 Accessing Subsystem Data from a Function Block>

J1-14

Access in the Case of Analog Input and Feedback Input

Subsystem data can be treated as analog input signals or feedback input signals just like
with an analog input module, by specifying the subsystem data in the format %WWnnnn
and assigning it to the input terminal of a regulatory control block or calculation block, or the
FB terminal of a motor control block.
The diagram below illustrates the flow of data when subsystem data is assigned to the
regulatory control block as an analog input.
Regulatory control block

Input open check

PV COM

IN

Communication
input conversion

Communication
module

PVFCS

PV

Subsystem

Data acquired
from the subsystem

Data in the subsystem

J010304E.EPS

Figure Subsystem Input Data Flow (Analog Input)

There are two types of process for subsystem data:

Communication input conversion
Input open (IOP+ and IOP-) check
After going through communication I/O conversion, subsystem data becomes the input
value for the regulatory control block. The input open (IOP+ and IOP-) check is executed to
this input value.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.3 Accessing Subsystem Data from a Function Block>

J1-15

Communication I/O conversion and I/O open check are as follows.

Communication Input Conversion

The following input conversion processing is performed to data that has undergone data
type conversion (RAW data) by selecting communication input conversion for the input
signal conversion specification of the Function Block Detail Builder:
PVFCS=PVCOM GAIN+BIAS
PVFCS:
PVCOM:
GAIN:
BIAS:

Data after input conversion (PV value of the function block)

Subsystem data after data type conversion
Data conversion gain (7 digits including sign and decimal point, default 1.000)
Data conversion bias (7 digits including sign and decimal point, default 0.000)

GAIN and BIAS are set via the Function Block Detail Builder.
Some function blocks can designate communication input signal conversion from the input
signal conversion options.

IMPORTANT
Do not designate communication input conversion for the input signal conversion of function blocks that assigned with data other than subsystem data. This may cause data error
reading.

The following table is a list of blocks for which communication input conversion can be
designated:
Table Blocks for which Communication Input Conversion can be Designated (1/2)
Block type

Regulatory control block

Block type

Block code

Block name

PVI

Input Indicator Block

PVI-DV

Input Indicator Block with Deviation Alarm

PID

PID Controller Block

PI-HLD

Sampling PI Controller Block

PID-BSW

PID Controller Block with Batch Switch

ONOFF

Two-Position ON/OFF Controller Block

ONOFF-G

Three-Position ON/OFF Controller Block

PID-TP

Time-Proportioning ON/OFF Controller Block

PD-MR

PD Controller Block with Manual Reset

PI-BLEND

Blending PI Controller Block

PID-STC

Self-Tuning PID Controller Block

MLD-PVI

Manual Loader Block with Input Indicator

RATIO

Ratio Set Block

BSETU-2

Flow-Totalizing Batch Set Block

BSETU-3

Weight-Totalizing Batch Set Block

SS-DUAL

Dual-Redundant Signal Selector Block

Block code

Block name
J010305E.EPS

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.3 Accessing Subsystem Data from a Function Block>

J1-16

Table Blocks for which Communication Input Conversion can be Designated (2/2)
Block type

Operation blocks

Block type

Block code

Block name

ADD

Addition Block

MUL

Multiplication Block

DIV

Division Block

SQRT

Square Root Block

EXP

Exponential Block

LAG

First-Order Lag Block

INTEG

Integration Block

LD

Derivative Block

RAMP

Ramp Block

LDLAG

Lead/Lag Block

DLAY

Dead-Time Block

DLAY-C

Dead-Time Compensation Block

AVE-M

Moving-Average Block

AVE-C

Cumulative-Average Block

FUNC-VAR

Variable Line-Segment Function Block

TPCFL

Temperature and Pressure Correction Block

ASTM1

ASTM Correction Block: Old JIS

ASTM2

ASTM Correction Block: New JIS

CALCU

General-Purpose Calculation Block

CALCU-C

General-Purpose Calculation Block with String I/O

DSET-PVI

Data Set Block with Input Indicator

Block code

Block name
J010306E.EPS

TIP

When subsystem data is assigned to the input terminal of a function block where communication
input conversion cannot be designated, or when something other than communication input conversion is designated for the input signal conversion, then PVFCS = PVCOM.

Communication input conversion is not performed when subsystem data is assigned to the feedback
(FB) terminal of a motor control block (MC-2 or MC-3).

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.3 Accessing Subsystem Data from a Function Block>

J1-17

Input Open Check

An input open check is performed on the PVFCS obtained through communication input
conversion processing.
IOP+
PVFCS > input high limit detection setpoint (-25.0 to 125.0 %, the default is 106.25 %)
IOPPVFCS < input low limit detection setpoint (-25.0 to 125.0 %, the default is -6.25 %)
The input high limit and low limit detection setpoint values are input via the Function Block
Detail Builder.
The hysteresis value for the input high or low limit alarm check is used for the hysteresis
value when data status IOP+ or IOP- is canceled.

Access in the Case of Analog Output

Subsystem data can be output to the subsystem as a manipulated output value (MV) of the
regulatory control block just like with the analog output module by specifying the data in the
format %WWnnnn and assigning it to the output terminal of a regulatory control block or
calculation block.
The diagram below illustrates the flow of data when analog output is output from the regulatory control block to the subsystem:
Regulatory control block

MV

MVFCS

Communication
output conversion

OUT

MVCOM

Data conversion

Subsystem

Communication
module

Data in the subsystem

Data to be set
into the subsystem

J010307E.EPS

Figure Flow of Subsystem Output Data (Analog Output)

The following two processes are performed with respect to the data assigned to the OUT
terminal of the regulatory control block:
Communication output conversion
Data type conversion
Data assigned to the OUT terminal of the regulatory control block is output to the subsystem after going through communication output conversion and data type conversion.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.3 Accessing Subsystem Data from a Function Block>

J1-18

IMPORTANT
The following restrictions are applied with analog output to the subsystem:
Reverse output cannot be designated.
Neither pulse width output nor time-proportioning ON/OFF output can be designated.
When subsystem data is linked to the OUT terminal of a function block that has no
communication output conversion designation, the function blocks manipulated output
value (MV) is output to the subsystem as it is.
MVSUBS=MVFCU will be satisfied.
With the LFCS2 or LFCS, do not use velocity type outputs or an output velocity limiter for
the reasons given below (*1) :
The velocity analog output (MVn) is obtained by adding the DMVn (amount of output
change obtained via PID operation) to the output readback value (MVrb) from the communication module during each control period of the regulatory control block.
The output readback value (MVrb) is updated during each RIO bus communication period.
Because the output readback value (MVrb) update is delayed when the output readback
value (MVrb) refresh period is longer than the control period, an output value differing from
the actual output value is found and output to the communication module. To avoid this,
positional type output is specified in the Function Block Detail Builder. Moreover, when an
output velocity limiter is set, the output value becomes inaccurate for similar reasons, so do
not set an output velocity limiter.
FCS

PID operation
MVn
MVn = MVrb + MVn
MVn

Write data

MVrb

Output readback value

Communication module

Communication module I/O image

J010308E.EPS

Figure Flow of Velocity Type Output

*1:

Restriction for using in LFCS2, LFCS.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.3 Accessing Subsystem Data from a Function Block>

J1-19

Communication Output Conversion

The following output conversion processing is performed with respect to data that have
been assigned to the OUT terminal by selecting communication output conversion for the
output signal conversion specification of the Function Block Detail Builder:
MVCOM=(MVFCS-BIAS) 1 / GAIN
MVCOM:
MVFCS:
BIAS:
GAIN:

Subsystem setting data

Data output from function block (MV)
Data conversion bias (7 digits including sign and decimal point, default 0.000)
Data conversion gain (7 digits including sign and decimal point, default 1.000)

GAIN and BIAS are set via the Function Block Detail Builder.
Some function blocks do not have communication output conversion for the output signal
conversion.
The following table is a list of blocks for which communication output conversion can be
designated.
Table Blocks for which Communication Output Conversion can be Designated (1/2)
Block type

Regulatory control block

Block type

Block code

Block name

PVI

Input Indicator Block

PVI-DV

Input Indicator Block with Deviation Alarm

PID

PID Controller Block

PI-HLD

Sampling PI Controller Block

PID-BSW

PID Controller Block with Batch Switch

PID-TP

Time-Proportioning ON/OFF Controller Block

PD-MR

PD Controller Block with Manual Reset

PI-BLEND

Blending PI Controller Block

PID-STC

Self-Tuning PID Controller Block

MLD

Manual Loader Block

MLD-PVI

Manual Loader Block with Input Indicator

MLD-SW

Manual Loader Block with Auto/Man SW

RATIO

Ratio Set Block

PG-L13

13-Zone Program Set Block

BSETU-2

Flow-Totalizing Batch Set Block

BSETU-3

Weight-Totalizing Batch Set Block

VELLIM

Velocity Limiter Block

SS-H/M/L

H/M/L Signal Selector Block

AS-H/M/L

H/M/L Auto-Selector Block

SS-DUAL

Dual-Redundant Signal Selector Block

XCPL

Non-Interference Control Output Block

SPLIT

Control Signal Splitter Block

Block code

Block name
J010309E.EPS

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.3 Accessing Subsystem Data from a Function Block>

J1-20

Table Blocks for which Communication Output Conversion can be Designated (2/2)
Block type

Operation blocks

Block type

Block code

Block name

ADD

Addition Block

MUL

Multiplication Block

DIV

Division block

AVE

Averaging Block

SQRT

Square Root Block

EXP

Exponential Block

LAG

First-Order Lag Block

INTEG

Integration Block

LD

Derivative Block

RAMP

Ramp Block

LDLAG

Lead/Lag Block

DLAY

Dead-Time Block

DLAY-C

Dead-Time Compensation Block

AVE-M

Moving-Average Block

AVE-C

Cumulative-Average Block

FUNC-VAR

Variable Line-Segment Function Block

TPCFL

Temperature and Pressure Correction Block

ASTM1

ASTM Correction Block: Old JIS

ASTM2

ASTM Correction Block: New JIS

CALCU

General-Purpose Calculation Block

CALCU-C

General-Purpose Calculation Block with String I/O

DSW-16

Selector Switch Block for 16 Data

DSET

Data Set Block

DSET-PVI

Data Set Block with Input Indicator

Block code

Block name
J010310E.EPS

Data Type Conversion in the Case of Subsystem Data Output

32-bit floating point data (F32) is converted to data types I16, U16, I32, U32 and F32, which
are designated via the Communication I/O Builder.
When floating-point data is converted to integer data, the first decimal place and below are
rounded off. When the value prior to the data type conversion exceeds the maximum value
of the type to be converted to, the value prior to the conversion becomes the maximum
value (minimum value) of the conversion type.
When a value outside the range is designated, the block status changes to OOP. Set the
MV range within the subsystem allowed range.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.3 Accessing Subsystem Data from a Function Block>

J1-21

Access in the Case of Discrete Input and Discrete Output

TIP

When performing discrete output to the subsystem, a pulsive output cannot be designated in the
motor control block (MC-2, MC-3) or switch instrument block. If a pulsive output is designated, pulse
output to the subsystem may not be executed properly. In this case the duration of the pulse output
being ON will be unknown.

When performing discrete output to the subsystem, neither flashing output nor pulsive output can be
performed with respect to the discrete output. The flashing output requests and cancel requests from
the sequence table will be disregarded.

If the subsystem data is specified in the format %WBnnnnbb, each word (16 bits) can be
assigned to discrete inputs or discrete outputs. Subsystem data is identified by I/O number.
The DI number is the I/O number for discrete input and the DO number is the I/O number
for discrete output. In this case, MSB (most significant bit) corresponds to the smaller DI or
DO number and LSB (least significant bit) corresponds to the larger DI or DO number.
DI/DO number handled
in FCS
MSB

DI/DO number handled

in subsystem
LSB

MSB

LSB

14 15 16

16 15 14

17 18 19

30 31 32

32 31 30

19 18 17

J010311E.EPS

Figure DI/DO Number Arrangement

In some cases, depending on the subsystem, this number correlation is reversed. Because
of this, it is possible to set LSB and MSB reversal via the Communication I/O Builder.
If bit reversal is specified in the Communication I/O Builder, when the data obtained via
communication is stored in the communication I/O data storage area, the order of data
reverses in 16-bit units so that at the connection destination, what was the MSB becomes
the LSB.
The figure below illustrates bit reversal.

Connection
destination

X
0
0
1
6

X
0
0
1
5

X
0
0
1
4

X
0
0
0
3

X X
0 0
0 0
0 0
2 1

Bit reversal

Communication
a
I/O data

J010312E.EPS

Figure Bit Reversal

When the common switches or discrete I/O data inside the FCS is handled in word units,
the smallest bit number is stored in the MSB. On the other hand, some devices that are
connected via the communication I/O module (such as a PLC) store the smallest number in
the LSB. When connection is made to a device of this type, it may be necessary to specify
Reverse Bits.
IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.3 Accessing Subsystem Data from a Function Block>

J1-22

Moreover, on the builder, the most significant word (MSW) and the least significant word
(LSW) of a signal can be reversed.
When reversing the MSW and LSW is set on the builder, a signal sent from communication
line is put to memory image area after the MSW and LSW is reversed. A 32-bit signal is
converted by moving the lower 16 bits to the upper position and moving the upper 16 bits to
lower position. Thus the original signals upper part (MSW) becomes lower part (LSW) and,
vice versa, lower part becomes upper part.
The following figure illustrates how the words are reversed in a signal.
32-bit Datum
MSW
LSW
(Most Significant Word) (Least Significant Word)
Original Signal

D0001

D0002

Reverse MSW and LSW

Communication
D0002
I/O Data
Storage Area
Figure Reverse MSW and LSW

D0001
J010313E.EPS

When connecting the devices in which the 32-bit word data are in reversed arrangement,
i.e., the LSW (16 bits) is sent first with and the MSW (16 bits) is sent next to LSW. The data
are sent in this manner from the devices like MELSEC-A and FA-M3. When communicating
with this kind of devices, the words of communicated data need to be reversed.
SEE ALSO
For the settings of bit reversal on Communication I/O Builder, see the explanations for the subsystem
communication package used:
J3.6, Setting Items on Communication I/O Builder FA-M3
J4.6, Setting Items on Communication I/O Builder FA-M3
J5.6, Setting Items on Communication I/O Builder DARWIN
J6.6, Setting Items on Communication I/O Builder Gas Chromatography
J7.5, Setting Items on Communication I/O Builder YS Instrument
J8.6, Setting Items on Communication I/O Builder MELSEC-A
J9.6, Setting Items on Communication I/O Builder MELSEC-A
J10.6, Setting Items on Communication I/O Builder Modbus
J11.6, Setting Items on Communication I/O Builder PLC-5
J12.6, Setting Items on Communication I/O Builder SYSMAC
J13.6, Setting Items on Communication I/O Builder SIMATIC S5
J14.6, Setting Items on Communication I/O Builder DARWIN/DAQSTATION
J15.6, Setting Items on Communication I/O Builder SLC 500
J16.6, Setting Items on Communication I/O Builder PLC-5/SLC 500
J17.6, Setting Items on Communication I/O Builder Modbus

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

J1-23

<J1.3 Accessing Subsystem Data from a Function Block>

Simultaneity of Communication Data

When two data items in a subsystem are acquired from two communication registers and
they are handled as one signal in the FCS, data may not be properly processed if the
acquisition timings for the two data items in the subsystem are different. For this reason, it is
necessary to consider the simultaneity of communication data.
Communication between a communication module and FCS
Simultaneity of communication data is guaranteed in 32-bit units.
Communication between a communication module and subsystem
The number of bit units at which simultaneity of the communication is guaranteed
differs according to the subsystem connected.
For example, if the simultaneity of communication data is guaranteed in 32-bit units
between the communication module and subsystem, then simultaneity of the communication data in 32-bit units will also be guaranteed between the subsystem and the
FCS.
FCS

32-bit data

(a) + (b)

Data (a) and data (b) are acquired

at the same timing.

Communication module

(a)

(b)
16-bit data

16-bit data
On the Communication I/O Builder,
data (A) and data (B) may be specified
to be transmitted at the same acquisition
timing, thus the simultaneity of the
transmitted 32 bits in FCS is guaranteed.

Subsystem
(a)

(b)
16-bit data

16-bit data

If data (a) and data (b) are set for the same timing
(within the same scan period), simultaneity is
preserved between data (a) and data (b).
J010314E.EPS

Figure Simultaneity of Communication Data

SEE ALSO
See the followings for the subsystem communication package being used for the number of bit units at
which simultaneity of communication data is guaranteed in communication between the communication
module and subsystem:
J3.1, Communication Specifications FA-M3
J8.1, Communication Specifications MELSEC-A
J10.1, Communication Specifications Modbus
J17.1, Communication Specifications Modbus

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.4 Subsystem Data Type>

J1-24

J1.4 Subsystem Data Type

This section explains the subsystem data types supported by the communication
I/O modules.
The data type defines how the data from the subsystem be treated in the control
station (FCS). Data type is specified for each communication data via the Communication I/O Builder. The data type that can be specified varies depending on the subsystem connected.

Subsystem Data Types Supported

Table Subsystem Data Types Supported
Category

Input

Output

Name

Data type

16-bit signed integer data

I16

16-bit unsigned integer data

U16

32-bit signed integer data

I32

32-bit unsigned integer data

U32

32-bit floating-point data

F32

64-bit floating-point data (*1)

F64

Bit data (Discrete input)

DI

16-bit signed integer data

I16

16-bit unsigned integer data

U16

32-bit signed integer data

I32

32-bit unsigned integer data

U32

32 bit floating-point data

F32

64 bit floating-point data (*1)

F64

Bit data (Discrete output)

DO
J010401E.EPS

*1:

The 64-bit data simultaneous transmission is not supported in subsystem communication packages. So that do not use
AIF64 and AOF64 data.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.4 Subsystem Data Type>

J1-25

SEE ALSO
For more information about the settings of Communication I/O Builder, see the explanations for the
subsystem communication package:
J3.6, Setting Items on Communication I/O Builder FA-M3
J4.6, Setting Items on Communication I/O Builder FA-M3
J5.6, Setting Items on Communication I/O Builder DARWIN
J6.6, Setting Items on Communication I/O Builder Gas Chromatography
J7.5, Setting Items on Communication I/O Builder YS Instrument
J8.6, Setting Items on Communication I/O Builder MELSEC-A
J9.6, Setting Items on Communication I/O Builder MELSEC-A
J10.6, Setting Items on Communication I/O Builder Modbus
J11.6, Setting Items on Communication I/O Builder PLC-5
J12.6, Setting Items on Communication I/O Builder SYSMAC
J13.6, Setting Items on Communication I/O Builder SIMATIC S5
J14.6, Setting Items on Communication I/O Builder DARWIN/DAQSTATION
J15.6, Setting Items on Communication I/O Builder SLC 500
J16.6, Setting Items on Communication I/O Builder PLC-5/SLC 500
J17.6, Setting Items on Communication I/O Builder Modbus

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-26

J1.5 Overview of Setting Items Related to the

Subsystem
It is necessary to set communication I/O in the System View and Communication I/O
Builder in order to perform communication using the subsystem communication
package.
This section gives an overview of the setting items in System View and Communication I/O Builder.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-27

J1.5.1 Overview of Setting Items on System View

In System View, items primarily related to the communication I/O module are defined
using the following two tabs in the New IOM dialog box called from [File] - [Create
New] - [IOM].
Type and Position tab
This defines the communication module to be used and its installation position.
Set Details tab
This defines the subsystem to connect to the communication module and the
communication conditions (baud rate, parity, etc.) under which the communication module communicates with the subsystem.
The setting items on System View vary with the type of communication I/O modules.
The subsystem common settings and the setting items are explained respectively in
accordance with each type of I/O module.

Setting Items for ACM11, ACM12

This section explains the setting items on System View for the subsystem communication
packages applied to ACM11 and ACM12.
FA-M3 communication package (ACM11, ACM12)
DARWIN communication package (ACM11)
YS communication package (ACM12)
MELSEC-A communication package (ACM11, ACM12)
Modbus communication package (ACM11, ACM12)
A-B communication package (ACM11, ACM12)
SYSMAC communication package (ACM11, ACM12)
Siemens communication package (ACM11, ACM12)
SLC 500 Communication package (ACM11)
SEE ALSO
The subsystem common settings and the setting items are explained in this section. For more information
about the fixed and recommended settings of subsystems, see the users manuals of the used subsystem
packages:
J3.5, Setting Items on System View FA-M3
J5.5, Setting Items on System View DARWIN
J7.4, Setting Items on System View YS Instrument
J8.5, Setting Items on System View MELSEC-A
J10.5, Setting Items on System View Modbus
J11.5, Setting Items on System View PLC-5
J12.5, Setting Items on System View SYSMAC
J13.5, Setting Items on System View SIMATIC S5
J15.5, Setting Items on System View SLC 500

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-28

From System View, a dialog box for creating a new IOM can be opened. On this dialog box,
there is a Type and Position tab, on which the following items can be set.
Duplicate Next Card
High Speed Read
The following items can be set on the Set Details tab of the New IOM dialog box called from
System View:
Connection Device
Baud Rate
Parity
Data Bits
Stop Bits
RS Control
DR Check
CD Check
Communication Error Process
Options
After creating a new I/O module, the settings can be modified on the I/O module property
sheet.
From System View, a dialog box for creating a new IOM can be opened. On this dialog,
there are Type and Position and Set Details tabs, on which the following items can be
set.

Duplicate Next Card

Sets slot 1 and slot 2 of the same unit to dual-redundant configuration. Settings need to be
entered for slot 1. For slot 2, settings are automatically generated.
A package is required for dual-redundant configuration .

High Speed Read

This setting can be set to slot 1 only. By using the communication band of slot 2, the data
transmission between FCU and ACM11, ACM12 can be performed at high speed.
Thus, if this setting is validated, no I/O module can be put in slot 2.
SEE ALSO
For more information about High Speed Read, see the following:
Data Flow in Process I/O in C7.1.3, Timing of Process I/O

Connection Device
This item sets the type of connection device (subsystem).
The default is [FA-M3]. If the device is not FA-M3, this setting must be changed accordingly.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-29

Baud Rate
This sets the baud rate between the communication I/O module and subsystem.
The baud rate can be selected from the following options:
1200 bps
2400 bps
4800 bps
9600 bps
19200 bps
The default is [19200 bps].
However, subsystems may be restricted for selecting certain baud rates.

Parity
This sets the method for checking the parity of the subsystem data to be transmitted.
The parity can be selected from the following options:
Odd parity
Even parity
No parity
The default is [Even] parity.
When the baud rate is set to [19200 bps], the [No] parity cannot be set.
However, subsystems may be restricted for selecting certain parity settings.

Data Bits
This sets the data bit length of the subsystem data to be transmitted.
The data bit can be selected from the following:
7 bits
8 bits
The default is [8 bits].

IMPORTANT
Certain subsystems may require specific data bits. Please refer to the explanations regarding to the setting items in the related chapters of the corresponding subsystem.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-30

Stop Bits
This sets the stop bit of the subsystem.
The default is [1] bit.

IMPORTANT
Certain subsystems may require specific stop bit setting. Please refer to the explanations
regarding to the setting items in the related chapters of the corresponding subsystem.

RS Control
This item sets whether or not to perform RS control during subsystem data transmission.
By default, the [RS control] checkbox is not checked.

DR Check
This item sets whether or not to perform DR check during subsystem data transmission.
By default, the [DR check] check box is checked.

CD Check
This item sets whether or not to perform CD check during subsystem data transmission.
By default, the [CD check] checkbox is not checked.

Communication Error Process

This sets the parameters related to communication error handling during subsystem data
transmission.
The following three items must be set.
Response Timeout
This sets the tolerant time for getting response from the subsystem. The time is set in
units of seconds.
The setting range is 1 to 99.
The default setting is 4.
Number of Retries Upon Response Timeout
This item sets the number of retries performed when a communication error occurs.
The setting range is 0 to 99.
The default setting is 1.
Interval of Connection Retries
This sets the time interval of connection request to check whether the communication
with the station that generated a communication error has returned to normal (communication recovery) . The time is set in unit of seconds.
The setting range is 1 to 999.
The default setting is 30.

Options
Set options for the communication parameters that vary with the connected subsystem.b
Options are set by entering settings to the fields of Option 1 through 4 in the Set Detail tab
of the New IOM dialog box called from System View.
The default is no setting.
IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-31

Setting Items for ACM21, ACM22

This section explains the setting items on System View for the subsystem communication
packages applied to ACM21.
Gas chromatography communication package (ACM21)
SEE ALSO
The subsystem common settings and the setting items are explained in this section. For more information
about the fixed and recommended settings of subsystems, see the following:
J6.5, Setting Items on System View Gas Chromatography

The following items can be set on the Set Details tab of the New IOM dialog box called from
System View:
Baud Rate
Parity
Data Bits
Stop Bits
RS Control
DR Check
CD Check
Communication Error Process
Options
Start of Text Delimiter
End of Text Delimiter
For Gas Chromatography communication package, the settings need to be performed not
only on the Set Details tab of the Create New IOM dialog box, but also on the Constant tab
of FCS property sheet called from System View:
After creating the new I/O module, the settings can be modified on the I/O module property
sheet.
From System View, a dialog box for creating a new IOM can be opened. On this dialog,
there is a Set Details tab, on which the following items can be set.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-32

Baud Rate : SFCS

This sets the baud rate between the communication I/O module and subsystem.
The baud rate can be selected from the following options:
1200 bps
2400 bps
4800 bps
9600 bps
19200 bps
38400 bps
The default is [19200 bps].
However, subsystems may be restricted for selecting certain baud rates.

Parity : SFCS
This sets the method for checking the parity of the subsystem data to be transmitted.
The parity can be selected from the following options:
Odd parity
Even parity
No parity
The default setting is [Even] parity.

Data Bits : SFCS

This sets the data bit length of the subsystem data to be transmitted.
The data bit can be selected from the following:
7 bits
8 bits
The default setting is [8] bit.

IMPORTANT
Certain subsystems may require specific data bits. Please refer to the explanations regarding to the setting items in the related chapters of the corresponding subsystem.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-33

Stop Bits : SFCS

This sets the stop bit of the subsystem.
The default setting is [1] bit.

IMPORTANT
Certain subsystems may require specific stop bit setting. Please refer to the explanations
regarding to the setting items in the related chapters of the corresponding subsystem.

RS Control : SFCS
This item sets whether or not to perform RS control during subsystem data transmission.
By default, the [RS control] checkbox is not checked.

DR Check : SFCS
This item sets whether or not to perform DR check during subsystem data transmission.
By default, the [DR check] check box is checked.

CD Check : SFCS
This item sets whether or not to perform CD check during subsystem data transmission.
By default, the [CD check] checkbox is not checked.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-34

Communication Error Process : SFCS

This sets the parameters related to communication error handling during subsystem data
transmission.
There are following six setting items.
Response Timeout
This sets the tolerant time for getting response from the subsystem. The time is set in
unit of seconds.
The setting range is 1 to 99.
The default setting is 4.
Number of Retries Upon Response Timeout
This item sets the number of retries performed when a communication error occurs.
The setting range is 0 to 99.
The default setting is 1.
Interval of Connection Retries
This sets the time interval of connection request to check whether the communication
with the station that generated a communication error has returned to normal (communication recovery). The time is set in unit of seconds.
The setting range is 1 to 999.
The default setting is 30.
Processing of inter-character time-out as an error
When check the mark for Processing of inter-character timeout as an error, the timeout between transmission of characters will be treated as an error.
Inter-character timer
The time interval between two characters of transmitted text may be specified in
milliseconds.
Transmission enable monitoring time
The time for monitoring the interval between transmission request command and the
transmission start may be specified in milliseconds.

Options : SFCS
Set options for the communication parameters that vary with the connected subsystem.
Options are set by entering settings to the fields of Option 1 through 4 in the Set Detail tab
of the New IOM dialog box called from System View.
The default is no setting.

Start of Text : SFCS

Specify a Start of Text.
The default setting is 0x00.

End of Text : SFCS

Specify an ETX.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-35

Setting Items for ACM71

This section explains the setting items on System View for the subsystem communication
packages applied to ACM71.
FA-M3 communication package (ACM71)
MELSEC-A communication package (ACM71)
DARWIN/DAQSTATION communication package (ACM71)
PLC-5/SLC 500 communication package (ACM71)
Modbus communication package (ACM71)
SEE ALSO
The subsystem common settings and the setting items are explained in this section. For more information
about the fixed and recommended settings of subsystems, see the users manuals of the used subsystem
packages:
J4.5, Setting Items on System View FA-M3
J9.5, Setting Items on System View MELSEC-A
J14.5, Setting Items on System View DARWIN/DAQSTATION
J16.5, Setting Items on System View PLC-5/SLC 500
J17.5, Setting Items on System View Modbus

For the above subsystems, the optional packages need to be added to Options item on the
Constant tab in the FCS [Properties] dialog box called from System View.
Then the following items need to be set on Detailed Setting tab of the Create New IOM
dialog box called from System View: Information such as Attribute, Destination Address,
Router Address and Hop-Count routing information can be set in the routing table by
clicking the [Add] button.
A maximum of eight items of routing information can be set.
IP Address
Subnet Mask
Attribute
Destination Address
Router Address
Hop Count
The following items can be set in any of the tabs of Detailed Setting 2 through 5 of the New
IOM dialog box called from System View.
Connected Device Name
Options 1 (Response Timeout)
Options 2 (Number of Retries Upon Response Timeout)
Options 3 (Interval of Connection Retries)
Options 4 (Port Number on Subsystem)
Options 5 (Port Number on Subsystem)

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-36

From System View, a dialog box for creating a new IOM can be opened. On this dialog,
there is a Detailed Setting tab, on which the following items can be set.

IP Address
This item sets the IP address of the ACM71.
The default is no setting.

Subnet Mask
This item sets the subnet mask of the ACM71.
The default is no setting.

Attribute
This item specifies the host address host or network address net.
The default setting is host.

Destination Address
This item sets the destination host address or destination network address.
Set the host address area to 0 when setting the network address.
The default is no setting.

Router Address
This item sets the IP address of the router. This address must be on the same subnet as
the IP address of the ACM71.
The default is no setting.

Hop Count
This item sets the number of routers through which data travels from the FCS to the FA-M3.
(Up to eight routers can be used.)
The default setting is 1.
TIP
Attribute, Destination Address, Router Address and Hop Count need to be set only when required.

From System View, a dialog box for creating a new IOM can be opened. On this dialog,
there are Detailed Setting 2 to Detailed Setting 5 tabs, on which the following items can be
set.

Option 1
This sets the tolerant time for getting response from the subsystem. The time is set in unit of
seconds.
The setting range is between 0 and 99.
The default is no setting.
If 0 is specified, the system will operate in the same manner as when 4 is specified. In
other words, the Response Timeout will be 4 seconds.
IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-37

Option 2
This item sets the number of retries performed when a communication error occurs.
The setting range is between 0 and 99.
The default is no setting.
If 0 is specified, the system will operate in the same manner as when 1 is specified. In
other words, the communication retry will be performed for one time.

Option 3
Specify a time interval that the probe communication packets are sent to test if the connection can be established. The time is set in unit of seconds.
The setting range is between 0 and 999.
The default is no setting.
If 0 is specified, the system will operate in the same manner as when 30 is specified. In
other words, the Interval of Connection Retries will be 30 seconds.

Option 4
Set the port number of subsystem to this item.
The port number setting varies with the subsystem used.
If this is not set, communication can not be carried out.
The default is no setting.

Option 5
Set the port number of subsystem to this item.
The port number setting varies with the subsystem used.
If this is not set, communication can not be carried out.
The default is no setting.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-38

J1.5.2 Overview of Settings on Communication I/O Builder

Details of communication I/O with the subsystem are set via the Communication I/O
Builder.
To communicate with subsystems, first assign a storage area for communication
data for each subsystem connected, then it is necessary to define the type of data to
be acquired from the connected subsystem, and the area in the connected subsystem in which data is to be written. In order to define these, each assigned area is
divided in units of data that can be acquired via a single communication with the
destination or data that can be set. The communication method for each subsystem
is defined via the Communication I/O Builder. The figure below gives an overview of
the communication definition.
Communication module
I/O image area
%WW0001
%WW0002
Acquired through a single
communication

Communication
definition data 1

Data region assigned to

connected subsystem A
Communication
definition data 2

Connected subsystem A

Communication
definition data 3
Communication is executed in accordance
with the defined contents and data is acquired.

Specified by the
relative position within
the region

Function block

IN=PV(%WW0100)

J010501E.EPS

Figure Overview of Communication Definition

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-39

Setting Items
Setting items on Communication I/O Builder are explained in this section.
SEE ALSO
The subsystem common settings and the setting items are explained. For more information about the
fixed and recommended settings of subsystems, see the users manuals of the used subsystem packages:
J3.6, Setting Items on Communication I/O Builder FA-M3
J4.6, Setting Items on Communication I/O Builder FA-M3
J5.6, Setting Items on Communication I/O Builder DARWIN
J6.6, Setting Items on Communication I/O Builder Gas Chromatography
J7.5, Setting Items on Communication I/O Builder YS Instrument
J8.6, Setting Items on Communication I/O Builder MELSEC-A
J9.6, Setting Items on Communication I/O Builder MELSEC-A
J10.6, Setting Items on Communication I/O Builder Modbus
J11.6, Setting Items on Communication I/O Builder PLC-5
J12.6, Setting Items on Communication I/O Builder SYSMAC
J13.6, Setting Items on Communication I/O Builder SIMATIC S5
J14.6, Setting Items on Communication I/O Builder DARWIN/DAQSTATION
J15.6, Setting Items on Communication I/O Builder SLC 500
J16.6, Setting Items on Communication I/O Builder PLC-5/SLC 500
J17.6, Setting Items on Communication I/O Builder Modbus

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-40

The setting items on Communication I/O Builder include the following:

Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

IMPORTANT
On KFCS2/KFCS/RFCS5/RFCS2 communication I/O builder, the builder files created on
communication I/O builder of SFCS/LFCS2/LFCS/PFCS cannot be imported. Vice versa,
SFCS/LFCS2/LFCS/PFCS cannot import the builder files of KFCS2/KFCS/RFCS5/RFCS2
either. In order to use the builder files created on both builders respectively, it is necessary
to convert the builder files into CSV file format. Thus, to export the builder file into CSV
format on one builder and then import the CSV format file on the other builder.

Element
With respect to the address of the subsystem data buffer area, the element number is
indicated in the Communication I/O Builder as shown below. The element number is indicated for display purpose only. It is not selectable.
%WWnnnn
%WW:
nnnn:

Fixed
For standard type PFCS:
For enhanced type PFCS:
For SFCS, LFCS2 or LFCS:
*1:

1 to 1000
1 to 4000
1 to 4000 (*1)

SFCS, LFCS2 and LFCS is a station for CS 3000.

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-41

Buffer
This item sets the buffer used by a program.
The setting can be made within the following size range in word units.
For standard type PFCS:

1 to 1000

For enhanced type PFCS:

1 to 4000

For SFCS, LFCS2 or LFCS:

1 to 4000 (*1)

*1:

SFCS, LFCS2 and LFCS is a station for CS 3000.

The default is no setting.

The following must be noted when setting the buffer:
Must set the buffer size since this is a required setting item of the Communication I/O
Builder.
Other setting items cannot be specified unless the buffer is set.
When an odd number is used to define the size, the buffer size of the next even number is reserved by adding a value of one to the odd number.
In the case of PFCS, make sure that the total buffer setting does not exceed 1000 for
the standard type and 4000 for the enhanced type. If the setting exceeds the value, it
will be automatically adjusted to a value within the allowable range.
In the case of SFCS/LFCS2/LFCS, make sure that the total buffer setting does not
exceed 4000. If the setting exceeds 4000, it will be automatically adjusted to a value
within the allowable range (*1).
If the buffer size is set so that it becomes smaller than the data size setting, an error
will result and it will be automatically adjusted to fit the data size.
After properly setting the buffer and moving to the setting in the next line, an * (asterisk) is displayed in the sections for the program name of the reserved area and buffer.
Asterisked items can no longer be set.
*1:

SFCS, LFCS2 and LFCS is a station for CS 3000.

Program Name : PFCS/SFCS

When setting the name of the program for accessing the subsystem, entering the unit
number and slot number then the connection device name defined when the I/O module
was created may be displayed on Communication I/O Builder. This name is the same as the
program name.
u-sProgramName
u:
s:
ProgramName:

Unit Number
Slot Number
Connection device name defined when a new I/O module was created

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-42

Program Name : LFCS2/LFCS

When setting the name of the program for accessing the subsystem and entering the node
number, unit number and slot number, the connection device name defined when the I/O
module was created may be displayed on Communication I/O Builder. This name is the
same as the program name.
n-u-sProgramName
n:
u:
s:
ProgramName:

Node
Unit Number
Slot Number
Connection device name defined when a new I/O module was created

Size
This item sets the data size (data length) from the head address set in Device & Address.
The Size can be set differently on Communication I/O Builder vary with the type of communication I/O module and the subsystem package.
The default is no setting.
Notices for setting the data size are shown below: Vary with subsystem used, the notices
may be different.
Up to 30 data size settings are possible for each buffer. When using Gas Chromatography communication package, up to 208 settings are possible for each buffer.
Must set the Size since this is a required setting item for the Communication I/O
Builder. Other setting items cannot be set unless the data size is set.
When an odd number is used to define the size, the data size of the next even number
is reserved by adding a value of one to the odd number.
If the set data size exceeds the buffer size, it will automatically be cut off to fit in the
range.
After properly setting the size and moving to the setting in the next line, an * (asterisk) is displayed in the sections for the size that has been reserved. The area displayed with (*) asterisks can not be set.
The following shows the relationship between the buffer and size.
Program 1

Area 1 of the connection destination

Program 2

Area 2 of the connection destination

Program 3

Program 4

Area 30 of the connection destination

Program 5
Program 6
Program 7
Program 8
J010502E.EPS

Figure Buffer and Size

Port
Set the port number.
The Port setting varies with the subsystem used.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-43

IP Address
Sets the IP address.
The IP address needs to be set on communication I/O builder according to the type of
communication I/O module and subsystem used.
When using ACM11, ACM12, ACM21 or ACM22
The IP Address is not required to be set.
When using ACM71
Set the IP address of subsystem to this item.

Station
Set the station number of subsystem.
The Station setting varies with the subsystem used.
The default is no setting.

Device & Address

This sets the head address of a subsystem communication frame.
The Device & Address setting varies with the subsystem used.
The default is no setting.

Data Type
This item sets the data type of subsystem data.
Data Type contains the following options; the data types can be selected vary with the
subsystem used.
Input (16-Bit Signed)
Input (32-Bit Signed)
Input (16-Bit Unsigned)
Input (32-Bit Unsigned)
Input (32-Bit Floating)
Output (16-Bit Signed)
Output (32-Bit Signed)
Output (16-Bit Unsigned)
Output (32-Bit Unsigned)
Output (32-Bit Floating)
Input (Discrete)
Output (Discrete)
The default setting is [Input (16-Bit Signed)].

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.5 Overview of Setting Items Related to the Subsystem>

J1-44

Reverse
This sets whether or not to make the bit or word arrangement in the FCS in reverse order of
the subsystem data.
The Reverse setting varies with the subsystem used.

Scan
The analogue data communicated to FCS can be put to the I/O data storage area at the
beginning of each fast-scan.
The default setting for [Scan] is [Normal] so that, the analogue data communicated to FCS
are put to the storage area at the beginning of each normal scan. However, the discrete I/O
data are put into the I/O data storage area at each fast-scan.
Fast-scan can be specified on FCS property sheet.
When accessing the analogue data by fast scan, the load of CPU will increase. When
setting [Fast], the CPU performance should be put in consideration.
Settings for [Scan] can be selected as follows:
Normal
Fast
The default setting is [Normal].

Service Comment
This item sets the comment.
The service comment setting can be omitted.
A character string of up to 40 single-byte or 20 double-byte characters can be used for the
service comment.

Label
The name of the function block I/O terminal can be set as a user-defined label name. This
setting can be set on Communication I/O Builder.
The user-defined label can only be set when the [Detailed Setting Items] on the [View]
menu bar is selected. The user-defined label setting can be omitted.
The user-defined label name is an optional setting item.
A character string of up to 16 single-byte characters in the following format can be set as
the user-defined label:
%%[A-Z] [A-Z0-9]
%%:
A-Z:
A-Z0-9:

Fixed
The third character must be an uppercase letter.
The fourth and succeeding letters must be alphanumeric characters.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.6 On-Line Maintenance>

J1-45

J1.6 On-Line Maintenance

On-line maintenance such as addition and deletion of communication I/O modules is
supported.
This section explains the on-line maintenance items and how to download subsystem program.

Maintenance Items
On-line maintenance items with respect to the communication I/O module are listed below:
Communication I/O module deletion
Communication I/O module addition
Subsystem name change
Changing the contents of communication I/O module definition
When a communication I/O module is added or the subsystem name is changed, the
subsystem program is downloaded with respect to the communication I/O module. While
downloading a subsystem program, subsystem communication will be stopped.
SEE ALSO
Regarding subsystem program downloading, see the following in this chapter:
Downloading the Subsystem Program

When the contents of the communication I/O module definitions are changed, the communication I/O module is initialized. During initialization of the communication I/O module
(approximately 10 seconds), subsystem communication is temporarily suspended.
The following table shows the status of the communication I/O module and function block
during on-line maintenance.
Table Status of Communication I/O Module and Function Block during On-Line Maintenance
Type of
maintenance

Status of communication I/O module

Status of function block

Adding a
communication
I/O module,
changing
subsystem name

While a subsystem program is being downloaded to the

communication I/O module, it will show error status.
After downloading is complete and if communication is
normal, a "communication I/O module return to
normal" system alarm message will be sent.

During downloading, IOP or OOP is generated.

After downloading is complete and if
communication is normal, the IOP or OOP recovers,
and the function blocks with tracking designation
perform subsystem data tracking.

Changing
contents of
communication
I/O module
definitions

While a subsystem program is being downloaded to the

communication I/O module, the previous status is
retained and a system alarm message is not sent.
When downloading is complete and if there has been a
change in the status prior to downloading, a system
alarm message will be sent.

During downloading, OOP will occur. In the

definition of station constants, IOP inhibition during
downloading may be specified. After downloading,
when communication returns to normal status, the
OOP status vanishes and the function blocks with
tracking function will start to track the subsystem
data.
J010601E.EPS

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J1.6 On-Line Maintenance>

J1-46

TIP
When a change that requires to download subsystem program, it takes some time to complete downloading. In this case, the engineering function (builder function) is terminated without waiting for the completion of download. Though modification can be performed on different builders, do not carry out further
change while downloading. Download completion can be confirmed from the system alarm message sent
to HIS.

Downloading the Subsystem Program

The subsystem program is downloaded when one of the following operations is performed:
During off-line downloading, the program is downloaded to all modules.
When a communication I/O module is newly added or the subsystem name is
changed in on-line maintenance.
Downloading to a specific I/O module on FCS Status Display window.
This may be applied when a new communication I/O module is installed to replace the
failed module.
TIP
Downloading from FCS Status Display Window may not be applied to ACM71. ACM71 does not have the
contents that require downloading.

The subsystem program is downloaded in the nonvolatile memory (EEPROM) of the

communication I/O module. Because of this, once the subsystem program is downloaded, it
will not be erased even in case of power failure or the communication I/O module is detached or attached.
TIP

When performing off-line downloading to the control station (FCS), the FCS control will start after
subsystem program downloading is completed.

During subsystem program downloading, the data status of the function block connected to that
communication I/O module becomes input open (IOP) or output open (OOP).

SEE ALSO
Regarding the system alarm messages sent to the HIS during subsystem program downloading, see the
following:
J2.3, System Alarm Messages Specific to the Communication Module

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J2. Communication I/O Module>

J2-1

J2. Communication I/O Module

This chapter explains the interface, communication specifications and setting items
for the communication I/O module.
It also explains the system alarm messages specific to communication I/O modules.

Types of Communication I/O Modules that can be Used

The communication I/O modules that can be used for connecting FCS with a subsystem
are listed below:
ACM11:

RS-232C communication I/O module

ACM12:

RS-422/RS-485 communication I/O module

ACM21:

RS232C communication I/O card

ACM22:

RS-422/RS-485 communication I/O card

ACM71:

Ethernet communication module

Communication packages used for each subsystem at the communication destination and
available communication I/O modules are listed below:
FA-M3 communication package (ACM11, ACM12):

ACM11, ACM12

FA-M3 communication package (ACM71):

ACM71

DARWIN communication package (ACM11):

ACM11

Gas chromatography communication package (ACM21):

ACM21

YS communication package (ACM12):

ACM12

MELSEC-A communication package (ACM11, ACM12):

ACM11, ACM12

MELSEC-A communication package (ACM71):

ACM71

Modbus communication package (ACM11, ACM12):

ACM11, ACM12

A-B communication package (ACM11, ACM12):

ACM11, ACM12

SYSMAC communication package (ACM11, ACM12):

ACM11, ACM12

Siemens communication package (ACM11, ACM12):

ACM11, ACM12

DARWIN/DAQSTATION communication package (ACM71):

ACM71

SLC 500 communication package (ACM11):

ACM11

PLC-5/SLC 500 communication package (ACM71):

ACM71

Modbus communication package (ACM71):

ACM71

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J2.1 Communication Module (ACM11, ACM12)>

J2-2

J2.1 Communication Module (ACM11, ACM12)

The ACM11 and ACM12 are communication modules used for connecting FCS with a
subsystem.
This chapter explains the communication specifications and settings for the ACM11
and ACM12.

Interface for ACM11 and ACM12

The ACM11 and ACM12 modules may be installed in the communication module nest
(AMN33).
The ACM11 and ACM12 may be applied with the following interfaces:
ACM11:

RS-232C

ACM12:

RS-422 or RS-485 (use one or the other)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J2.1 Communication Module (ACM11, ACM12)>

J2-3

J2.1.1 Communication Specifications ACM11 and ACM12

The following section explains the specifications when communication with a subsystem is performed using the communication module (ACM11 and ACM12).

Communication Capacity ACM11 and ACM12

The capacity limitations when communicating with a subsystem using the communication
module (ACM11 and ACM12) are listed in the table below:
Table Subsystem Communication Capacity of the FCS ACM11 and ACM12
Item

Maximum quantity

Explanation

Number of communication modules

may be installed

2/standard type PFCS (*5)

4/enhanced type PFCS (*2)
4/SFCS (*3)
6/LFCS2, LFCS (*4)

Number of subsystem types may be

applied

2 types/standard type PFCS (*1)

4 types/enhanced type PFCS (*2)
4 types/SFCS (*3)
6 types/LFCS2, LFCS (*4)

Number of types is same as the communication

modules that can be loaded.

500 words
(1 word = 16 bits)

Maximum amount that can be accessed from the

regulatory control block/sequence control block.
This varies according to the type of subsystem.

Amount of data that can be

communicated with one
communication module
Number of subsystem stations that
can be communicated with one
communication module
Number of communication definitions
per one communication module

30 stations

30 definitions
J020101E.EPS

*1:
*2:
*3:
*4:
*5:

Maximum number for standard type PFCS. However when in dual-redundant configuration, this number changes.
Maximum number for enhanced type PFCS
Maximum number for SFCS
Maximum number for LFCS2, LFCS
Maximum number for standard type PFCS

SEE ALSO
For more information about dual-redundant configuration of communication modules, see the following:
Setting of Dual-Redundant Communication in chapter J10.9, Dual-Redundant Communication Modbus

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J2.2 Communication Module (ACM21, ACM22, ACM71)>

J2-4

J2.2 Communication Module (ACM21, ACM22,

ACM71)
The ACM21, ACM22 and ACM71 are communication I/O modules and used for connecting FCS with a subsystem.
This chapter explains the communication specifications, settings for the ACM21,
ACM22 and ACM71.

Interface for ACM21 and ACM22 : PFCS/SFCS

The ACM21 and ACM22 modules may be installed in the communication card nest
(AMN51).
The ACM21 and ACM22 have the following interfaces:
ACM21:

RS-232C

ACM22:

RS-422 or RS-485 (use one or the other)

Interface for ACM71 : Enhanced Type PFCS/SFCS

The ACM71 module may be installed in the communication nest (AMN51).
The ACM71 supports the following interface:
ACM71:

10 BASE-T

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J2-5

<J2.2 Communication Module (ACM21, ACM22, ACM71)>

J2.2.1 Communication Specifications ACM21 and ACM22

The following section explains the specifications when communication is performed
with a subsystem using the communication module (ACM21 and ACM22).

Communication Capacity ACM21 and ACM22

The capacity limitations when communicating with a subsystem using the communication
module (ACM21 and ACM22) are listed in the table below:
Table Subsystem Communication Capacity of the FCS ACM21 and ACM22
Item

Maximum quantity

Number of nest for communication

modules

1 nest/enhanced type PFCS (*1)

1 nest/SFCS (*2)

Number of communication modules

to be loaded

2/enhanced type PFCS (*1)

2/SFCS (*2)

Number of subsystem types

that FCS can communicate
Amount of data that can be
communicated with one
communication module

Explanation

1 type/enhanced type PFCS (*1)

1 type/SFCS (*2)
PFCS enhanced type: 4000 words
SFCS:
4000 words Maximum amount of communication I/O
(1word = 16 bits)

Number of communication
definitions per one communication
module

208 definitions

Number of ACM11/ACM12 and

ACM21/ACM22 that can be used
simultaneously

(*3)
J020201E.EPS

*1 :
*2 :
*3 :

Maximum number for enhanced type PFCS

Maximum number for SFCS
For one PFCS, the maximum number of four ACM11 or ACM12 modules and the maximum number of two ACM21 or
ACM22 cards may be installed.
For one LFCS2 or LFCS, the maximum number of six ACM11 or ACM12 modules may be installed and the
ACM21 and ACM22 cards can not. For one SFCS, the maximum number of four ACM11 or ACM12 modules and the
maximum number of two ACM21 or ACM22 cards may be installed.

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

J2-6

<J2.2 Communication Module (ACM21, ACM22, ACM71)>

J2.2.2 Communication Specifications ACM71

The following section explains the specifications when communication is performed
with a subsystem using the communication module (ACM71).

Communication Capacity ACM71

The capacity limitations when communicating with a subsystem using the communication
module (ACM71) are listed in the table below:
Table Subsystem Communication Capacity of the FCS ACM21 and ACM22
Item

Maximum quantity

Number of nest for communication

modules

1 nest/Enhanced Type PFCS (*1)

1 nest/SFCS (*2)

Number of communication modules

to be loaded

2/Enhanced Type PFCS (*1)

2/SFCS (*2)

Explanation

Number of subsystem types

that FCS can communicate

1 type/Enhanced Type PFCS (*1)

1 type/SFCS (*2)

Amount of data that can be

communicated with one
communication module

PFCS enhanced type: 4000 words

SFCS:
4000 words Maximum amount of communication I/O
(1word = 16 bits)
J020202E.EPS

*1 :
*2 :

Maximum number for PFCS enhanced type

Maximum number for SFCS

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J2.3 System Alarm Messages Specific to the Communication Module>

J2-7

J2.3 System Alarm Messages Specific to the

Communication Module
The following explains system alarm messages that are specific to the communication module (ACM11 and ACM12) as well as those occur when downloading a subsystem program into the communication module.

System Alarm Messages when the Communication Module is Abnormal :

PFCS/SFCS
When the communication module is abnormal, the system alarm message shown below is
sent to HIS.
STNss IOM FAIL UNITmm SLOTnn
STNss IOM Configuration Error UNITmm SLOTnn
STNss: FCS name
mm:
Unit number
nn:
Slot number

TIP
The system alarm message Configuration Error is sent when the subsystem program is not downloaded.

System Alarm Message when the Communication is Abnormal : LFCS2/

LFCS
When the communication is abnormal, the system alarm message as shown below is sent
to HIS:
STNss IOM FAIL UNITmm SLOTnn
STNss IOM Configuration Error UNITmm SLOTnn
STNss:
xx:
mm:
nn:

FCS name
Node number
Unit number
Slot number

TIP
The system alarm message Configuration Error is sent when the subsystem program is not loaded.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J2.3 System Alarm Messages Specific to the Communication Module>

J2-8

System Alarm Messages when the Communication Module Returns to

Normal : PFCS/SFCS
When the communication module returns to the normal state, the system alarm message
shown below is sent to HIS:
STNss IOM RECOVER UNITmm SLOTnn
STNss: FCS name
mm:
Unit number
nn:
Slot number

System Alarm Message when the Communication Module Returns to

Normal : LFCS2/LFCS
When communication returns to normal status, the system alarm message indicated below
is sent to HIS:
STNss IOM RECOVER RIO01 NODExx UNITmm SLOTnn
STNss:
xx:
mm:
nn:

FCS name
Node number
Unit number
Slot number

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J2.3 System Alarm Messages Specific to the Communication Module>

J2-9

Messages when Downloading the Subsystem Program

The following explains messages generated when the subsystem program is downloaded
to the communication module:

Message when Downloading Starts : PFCS/SFCS

When the subsystem program begins downloading to the communication module, the
system alarm message shown below is sent to HIS:
STNss IOM Download Start UNITmm SLOTnn
STNss: FCS name
mm:
Unit number
nn:
Slot number

Message when Downloading Starts : LFCS2/LFCS

When the subsystem program begins downloading to the communication module, the
system alarm message shown below is sent to HIS:
STNss IOM Download Start RIO01 NODExx UNITmm SLOTnn
STNss:
xx:
mm:
nn:

FCS name
Node number
Unit number
Slot number

Message when Downloading Ends Normally : PFCS/SFCS

When downloading of the subsystem program to the communication module is completed
normally, the system alarm message shown below is sent to HIS:
STNss IOM Download Complete UNITmm SLOTnn
STNss: FCS name
mm:
Unit number
nn:
Slot number

Message when Downloading Ends Normally : LFCS2/LFCS

When downloading of the subsystem program to the communication module is completed
normally, the system alarm message shown below is sent to HIS:
STNss IOM Download Complete RIO01 NODExx UNITmm SLOTnn
STNss:
xx:
mm:
nn:

FCS name
Node number
Unit number
Slot number

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J2.3 System Alarm Messages Specific to the Communication Module>

J2-10

Message when Downloading Ends Abnormally : PFCS/SFCS

When downloading of the subsystem program to the communication module is completed
abnormally, the system alarm message shown below is sent to HIS:
STNss IOM Download Error UNITmm SLOTnn Error = ####
STNss:
mm:
nn:
####:

FCS name
Unit number
Slot number
Error code

SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when Subsystem Program Downloading Ends Abnormally

Message when Downloading Ends Abnormally : LFCS2/LFCS

When downloading of the subsystem program to the communication module is completed
abnormally, the system alarm message shown below is sent to HIS:
STNss IOM Download Error RIO01 NODExx UNITmm SLOTnn Error = ####
STNss:
xx:
mm:
nn:
####:

FCS name
Node number
Unit number
Slot number
Error code

SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when Subsystem Program Downloading Ends Abnormally

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J2.3 System Alarm Messages Specific to the Communication Module>

J2-11

Error Codes when Subsystem Program Downloading Ends Abnormally

The error codes generated when the downloading of the subsystem program to the communication module is terminated abnormally are given in the table below:
Table Error Codes when Subsystem Program Downloading Ends Abnormally
Error code (hexadecimal)

Error description

2501 to 2509

FCS database error

250F to 2511

Internal error

2513 to 2514

FCU power failure

2516 to 251B

FCS database error

251C to 2529

Internal error

252B

Cannot access I/O module

252C to 254D

Downloading communication error

2559

Status error in specified I/O module

255A to 255F

Internal error

9D01 to 9DFF

FCS database error

A301 to A320

Downloading error

A321

The connected I/O module is not a communication module

A322 to A324

Error in receiving downloading communication

A334 to A335

Internal error

A336
A337 to A33A

Communication module error

Database error

A33C

In the process of downloading application program

A33D

Communication module error

A33E

Abnormal path up to the communication module

A33F

Disconnecting I/O with the system test function

A340

Communication module cleared during on-line maintenance

A701 to A730
A731
A732 to A735

Error in communication between work station and FCS

Number of subsystem programs exceeded 3
Error in communication between work station and FCS

A736

Requesting an application program to be downloaded to the same loading position

A737

Excessive number of loading requested

A738

The size of the subsystem program exceeds 30K bytes

A739 to A73C

Error in communication between work station and FCS

A741 to A750
C583

Internal error
Model code does not match

C591 to C5C0

Database error

C5C1 to C5C5

Time up for time monitoring

C5C6

Mode waiting time up for application program downloading

C5C7

Time up for application program downloading

Error code (hexadecimal)

Error description
J020301E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J2.4 System Alarm Messages Specific to Ethernet Communication>

J2-12

J2.4 System Alarm Messages Specific to Ethernet

Communication
The following explains system messages that are specific to the Ethernet communication module (ACM71).

System Messages
The following system messages are provided for indicating the state of ACM71 online
downloading.

System Message when Online Downloading Ends Normally (No.0471)

STNss Online Download Complete
STNss:

FCS name

System Alarm Message when Online Downloading Ends Abnormally

(No.0057)
STNss Online Download Error Call Code = xxxx-xxxx
Data = yyyy,yyyy,yyyy,yyyy
STNss:
xxxx-xxxx:
yyyy,yyyy,yyyy,yyyy:

FCS name
Error code
Error related data

User-Defined System Alarm Messages (No.0098/No.0099)

When communication is abnormal or returns to normal, user-defined system alarm messages can be applied based on the communication package specification and FCS tasks.

System Alarm Message when ACM71 is Abnormal (No.0081)

STNss IOM FAIL UNITmm SLOTnn
STNss:
mm:
nn:

FCS name
Unit number
Slot number

System Message when ACM71 Recovers to Normal (No.0082)

STNss IOM RECOVER UNITmm SLOTnn
STNss:
mm:
nn:

FCS name
Unit number
Slot number

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J2.4 System Alarm Messages Specific to Ethernet Communication>

J2-13

System Alarm Message when a PIO Functionality Error Occurs (No.0487)

STNss PIO Function Error PIO tt nn-mm-ss Code = uuuu Error = xxxx-yyyy
STNss:
tt:
xx:
mm:
nn:
uuuu:
xxxx:

FCS name
RIO bus number where the error occurred
Node number where the error occurred
Unit number where the error occurred
Slot number where the error occurred
Communication module code (ACM71: 9D07)
Error Code

Table Error Codes

xxxx

Description

1000

Network interface startup error

1100

Network interface stop error

20zz

Error when adding a route. zz: Routing Number (= 01 to 08)

21zz

Error when deleting a route. zz: Routing Number (= 01 to 08)

J020401E.EPS

yyyy:

Error Details Code

Table Error Details Codes

yyyy

Description

2965

Data access denied.

2966

Connection now in progress

2967

Connection is running disconnect.

296A

Message too long.

296B
296C
296D

Protocol type error

296F

Operation not supported by socket.

2971

Address family not supported.

2972

Address already in use.

2973

Can not assign requested address.

2974

Network is down.

2975

Network is unreachable.

2977

Connection abort.

2978

Connection reset.

2979

No buffer space available.

297A

Socket is already connected.

297B

Socket is not connected.

297C

Can not send after socket shutdown.

297E

TCP time out.

297F

Connection refused.
J020402E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

Blank Page

<J3. FA-M3 Communication (ACM11, ACM12)>

J3-1

J3. FA-M3 Communication (ACM11, ACM12)

The FA-M3 communication package is a subsystem communication package designed for the FACTORY ACE FA-M3 range-free controllers (hereinafter referred to
as FA-M3s) and the FA500, both are manufactured by Yokogawa. When the FA-M3
communication package is used, no need to make customized program to perform
communication between the FCS and the subsystem (FA-M3/FA500).
This chapter sections explain the communication between the FA-M3/FA500 and
FCS among the subsystem communication packages.
SEE ALSO
Regarding the subsystem communication package common to different subsystem communication
packages, see the following:
J1, General Information Regarding to Subsystem Communication

Applicable Models FA-M3

For the FA-M3 communication package, the following product is available.
PFS2210 CS 1000 FA-M3 communication package (ACM11, ACM12)
LFS2210 CS 3000 FA-M3 communication package (ACM11, ACM12)
With the FA-M3 communication package, the FA-M3 or FA500 is connected to the communication I/O module (ACM11 or ACM12) and subsystem communications are performed
between the FCS and FA-M3 or FA500. To connect the I/O module and FA-M3/FA500, the
following personal computer link modules are required on the FA-M3/FA500 side.
Table PC Link Modules for Connection FA-M3
When ACM11 (RS-232C)
is used
FA-M3
FA500

F3LC11-1N
LC01-0N
LC02-0N

When ACM12 (RS-422/RS-485)

is used
F3LC11-2N
LC02-0N
J030001E.EPS

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J3.1 Communication Specifications FA-M3>

J3-2

J3.1 Communication Specifications FA-M3

The section below explains the specifications when performing subsystem communication with the FA-M3/FA500.

Communication Capacity FA-M3

The capacity limitations specific to FA-M3/FA500 when performing subsystem communication with the FA-M3/FA500 are indicated below:
Table Capacity of Communications between FCS and FA-M3/FA500
Item

Maximum quantity

Explanation

Amount of data that can be communicated with

one communication module

500 words
(1 word=16 bits)

Maximum amount that can be

accessed from the regulatory control
block/sequence control block.

30 stations

Station number is specified as a

3-digit numeric value as
follows:
Upper 1 digit: CPU number (1 to 4)
Lower 2 digits: Station number
Specify on the Communication I/O
Builder.

Number of subsystem stations that can be

communicated with one communication module

Data size in one communication frame

64 words

One frame is defined in one line

on the builder. It is the same as
restricted by FA-M3 protocol.
J030101E.EPS

IMPORTANT
When connecting to the ACM11, the station number is fixed at 01.
When connecting to the ACM12, 30 stations can be connected within the station
number range from 02 to 32. When using the ACM12, do not use 01 for the station
number.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.1 Communication Specifications FA-M3>

J3-3

Transmission Specifications FA-M3

The transmission specifications when performing subsystem communication with the FAM3/FA500 are indicated below:
Table Transmission Specifications FA-M3
Item
Interface

Description
RS-232C (D-sub 25 pin)

ACM11

RS-422, RS-485

ACM12

Transmission method

Half duplex

Synchronization method

Start-stop synchronization

Baud rate

1200, 2400, 4800, 9600,

[19200] bps

Transmission procedure

Dedicated control procedure

Transmission code

ASCII

Data type

Control line

Time monitoring

Text frame

Remark

(*1)

Start bit

Data bit

[7] , 8

(*1)

Parity bit

None, [even], odd

(*1)

Stop bit

RS

Always ON

ER

Always ON

Transmission enable
monitoring time

1000ms

Reception character interval

monitoring time

1500ms

Character interval
timeout processing

Regarded as an error

Reception start character

$02 (STX)

EOT character

$03 (ETX) + $0d (CR)

Number of characters to send

Maximum 512 bytes

Number of characters to receive Maximum 512 bytes

XON/XOFF control

None

No response time setpoint

0 to 99 seconds [ 3 seconds]

(*1)

Number of communication retries upon error

0 to 99 times [1 time]

(*1)

Recovery communication time interval

0 to 999 seconds [20 seconds]

(*1)

ACM11 connector

D-sub 25 pin

ACM12 connector

M4 screw, 6 pole terminal block

FA-M3 connector (F3LC11-1N)

D-sub 9 pin

FA-M3 connector (F3LC11-2N)

M3.5 screw, 6 pole terminal block

FA500 connector (LC01-0N)

D-sub 25 pin

FA500 connector (LC02-0N)

RS-422, RS-485
(M3 screw, 6 pole terminal block)

RS-232C (D-sub 25 pin)

Number of words that can be handled in

one transmission
Item

AKB161(Dedicated Cable for

RS-422/RS-485)

64 words (AI/AO)
Description

Remark
J030102E.EPS

Note: [ ] indicates the recommended settings.

*1:
This can be changed using the property dialog box called from the System View.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.1 Communication Specifications FA-M3>

J3-4

Simultaneity of Communication Data FA-M3

The FA-M3/FA500 guarantees the simultaneity of communication data in 16 bit units.
Therefore, simultaneity of data in 16 bit units is guaranteed between the communication
module and the FA-M3/FA500.
TIP
The FA-M3/FA500 processes data in 16 bit units. Simultaneity of data in 32 bit units depends on the
application software for the FA-M3/FA500. It is necessary to set 32-bit data within the same control cycle
using the FA-M3/FA500 application software to guarantee simultaneity of communication data in 32 bit
units.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.2 Connecting FCS and FA-M3>

J3-5

J3.2 Connecting FCS and FA-M3

This section explains the connection type and cable connections between FCS and
FA-M3/FA500.

Connection Type FA-M3

An example of connection between FCS and FA-M3 (F3LC11-1N) is shown below:
HIS

Control bus

FCS

ACM11 (RS-232C communication module)

RDY
RCV
SND

CN1

RDY
RCV
SND

AMN33 (Nest for communication module)

CN1

RS-232C
MODEM

MODEM
RS-232C
FA-M3

F3LC11-1N
J030201E.EPS

Figure Connection Example between FCS and FA-M3

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J3-6

<J3.2 Connecting FCS and FA-M3>

Cable Connection when Using the ACM11 FA-M3

The following shows a cable connection when connecting the ACM11 and the FA-M3/
FA500.
A modem connection is required between the ACM11 and FA-M3/FA500, but if the length of
the RS-232C cable between the ACM11 and FA-M3/FA500 is 15 meters or less and if they
share the same grounding system, then it is possible to connect them directly.

IMPORTANT
The length of the RS-232C cable between the ACM11 and modem and between the
modem and FA-M3/FA500 must be 15 meters or less.

The following section describes the cable connections when using the F3LC11-1N personal computer link module to connect ACM11 and FA-M3:
Since the F3LC11-1N personal computer link module uses an RS-232C D-sub 9 pin
connector, use a cable with an RS-232C D-sub 9 pin connector and RS-232C D-sub 25 pin
connector when connecting the computer link unit to the ACM11.
Table RS-232C D-sub 9 Pin Connector Specifications FA-M3
Name

Direction of signal

Pin number

Signal name

CD

Carrier Detect

RD

Receive data

SD

Send data

ER

Data Terminal Ready

SG

Signal ground

DR

Data Ready

Detects when other side can receive.

An ON signal must always be sent from the
other side.

RS

Request to Send

This is ON when sending/receiving enabled.

CS

Clear to Send

This is always ON because external

transmission is disabled when it is OFF.

ACM11

FA-M3

Description
Not used with FA-M3

ON is output when sending/receiving enabled.

In the RDY state, ON is always output.

Not used
J030202E.EPS

9
6

1
D-sub 9 pin (female)
J030203E.EPS

Figure Pin Assignment of the RS-232C D-sub 9 Pin Connector FA-M3

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.2 Connecting FCS and FA-M3>

J3-7

Shown below are the cable connections when the FA-M3/FA500 and ACM11 are connected via modem and the FA-M3 and ACM11 are connected directly without modem:
SD
RD
RS
CS
ACM11

DR
SG
CD
ER
FG

20

20

SD
RD
RS
CS
DR

Modem (*1)

SG
CD
ER
FG

Sheathed cable
Protective ground (100 ohms or less)
J030204E.EPS

*1:

Generally FG and SG are connected for modem.

Figure Cable Connection between ACM11 and Modem

SD
RD
RS
CS
ACM11

CD
DR
ER
SG

20

SD
RD
RS
CS
CD

FA-M3

DR
ER
SG
Connector shell connection

Sheathed cable
Protective ground (100 ohms or less)
J030205E.EPS

Figure Cable Connection between FA-M3 and ACM11 (when connected directly)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J3-8

<J3.2 Connecting FCS and FA-M3>

The following shows the cable connections when using the LC01-0N and LC02-0N to
connect the ACM11 and the FA500.
The FA500 has an RS-232C D-sub 25 pin connector. The specifications of RS-232C D-sub
25 pin connector are as follows:
Table RS-232C D-sub 25 Pin Connector Specifications
Pin number

Signal name

Direction of signal

Name

ACM11

Description

FA500

FG

Frame ground

SD

Send data

Safety grounding

RD

Receive data

RS

Request to Send

This is ON when sending/receiving enabled.

CS

Clear to Send

This is always ON because external

transmission is disabled when it is OFF.

DR

Data Ready

Detects when other side can receive.

An ON signal must always be sent from the
other side.

SG

Signal ground

CD

Carrier Detect

20

ER

Data Terminal Ready

ON is output when sending/receiving enabled.

In the RDY state, ON is always output.
J030210E.EPS

Pin No.25

Pin No.14

Pin No.13

Pin No.1
J030211E.EPS

Figure Pin Assignment of the RS-232C D-sub 25 Pin Connector

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.2 Connecting FCS and FA-M3>

J3-9

The following shows a cable connection when directly connecting the ACM11 and the
FA500.
SD
RD
RS
CS
ACM11

CD
DR
ER
SG
FG

20

20

SD
RD
RS
CS
CD

FA500

DR
ER
SG
FG

Sheathed cable
Protective grounding (100 ohms or less)
J030212E.EPS

Figure Cable Connection between FA500 and ACM11 (when connected directly)

With the ACM11, the RS-232C circuit and FG (frame ground) are electrically insulated. This
has the function of preventing intrusion of noise from the FA-M3/FA500 side and improving
noise resistance. Satisfy all conditions given below to make this function effective:
For the frame ground, perform protective grounding (100 ohms or less) at the opposing side of the connection (the modem or FA-M3/FA500 side).
Attach only one side of the shield of the sheathed cable to the FG of the opposing side
of the connection. DO not ground the cable shield on the ACM11 side. Also, do not
use a connector shell that is conductive.
Connect the FG and the SG (signal ground) of the RS-232C circuit at the opposing
side of the connection. On the FA-M3/FA500, the frame ground (FG) and SG are
connected. When using a modem in which the FG and SG are not connected, use
Yokogawa Electrics AKB141 (RS-232C modem cable). For the AKB141 cable, SG
and FG are connected inside of the connector shell. Also, the cable shield can be
connected to the FG of the opposing side of the connection.
SEE ALSO
For details on cable connections, see the following:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J3-10

<J3.2 Connecting FCS and FA-M3>

Cable Connection Using the ACM12 FA-M3

The following section explains cable connections when making 1 to 1 connection and 1 to n
connection (4-wire connection, 2-wire connection) between the ACM12 and FA-M3/FA500
using the F3LC11-2N personal computer link module:
FA-M3 (F3LC11-2N)
FA500 (LC02-0N)

ACM12

ACM12

FA-M3 (F3LC11-2N)

TX +

SDB

TX +

SDB

TX -

SDA

TX -

SDA

RX +

RDB

RX +

RDB

RX -

RDA

RX -

RDA

SG

SG

SG

SG

FG

FG

FG

FG

(4-wire connection)

(2-wire connection)
J030206E.EPS

Figure 1 to 1 Connection Using RS-422 or RS-485 FA-M3

ACM12

FA-M3 (F3LC11-2N)
FA500 (LC02-0N)

FA-M3 (F3LC11-2N)
FA500 (LC02-0N)

SDB

SDB

SDB

SDA

SDA

SDA

RDB

RDB

RDB

RDA

RDA

RDA

SG

SG

SG

FG

FG

FG

TX +
TX RX +
RX SG
FG

FA-M3 (F3LC11-2N)
FA500 (LC02-0N)

J030207E.EPS

Figure 1 to n Connection Using RS-422 or RS-485 (4-wire connection) FA-M3

ACM12

FA-M3 (F3LC11-2N)

TX +
TX RX +
RX SG
FG

FA-M3 (F3LC11-2N)

SDB

SDB

SDA

SDA

RDB

RDB

RDA

RDA

SG

SG

FG

FG

FA-M3 (F3LC11-2N)
SDB
SDA
RDB
RDA
SG
FG
J030208E.EPS

Figure 1 to n Connection Using RS-422 or RS-485 (2-wire connection) FA-M3

IMPORTANT
When connecting FA500 and ACM12, 2-wire connection should not be used.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.2 Connecting FCS and FA-M3>

J3-11

With the ACM12, the FG (frame ground) and the SG (signal ground) for the RS-422 and
RS-485 are separated. Treat the shield for the RS-422 and RS-485 as follows:
Perform protective grounding (100 ohms or less) for the FG at the opposing side of the
connection (FA-M3/FA500 side).
Connect the shield for the cable between ACM12 and FA-M3/FA500 to the FG of the
FA-M3/FA500 side. Do not connect it to the FG of the ACM12 side.
SEE ALSO
For details on cable connections, see the following:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)

When connecting the ACM12 and FA-M3/FA500, it is necessary to attach a terminating

resistor on each side.

Setting a Terminating Resistor on the ACM12 Side FA-M3

When connecting the ACM12 and FA-M3/FA500, it requires a terminating resistor
(120 ohms 1/2W) between the RX+terminal and RX-terminal on the ACM12 side. The
ACM12 is shipped with a terminating resistor installed between the RX+terminal and RXterminal.
Set the connection method (4-wire or 2-wire ) using the 2-pole DIP switch (SW1) attached
to the ACM12. The unit is shipped from the factory with a 4-wire connection setting.
Table SW1 Setting for the ACM12 FA-M3
Connection method

SW1 setting for ACM12

2-wire

ON

ON

4-wire

OFF

OFF
J030209E.EPS

Setting a Terminating Resistor on the FA-M3 Side

A terminating resistor is required in FA-M3. Set the terminating resistor using the terminating resistor setting switch on the F3LC11-2N personal computer link module.

Setting a Terminating Resistor on the FA500 Side

A terminating resistor is required in FA500. Install a 220 ohms terminating resistor in the
LC02-0N personal computer link module.
SEE ALSO
For settings on the FA-M3/FA500, see the following:
J3.8, Settings on Subsystem FA-M3

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.3 Accessible Devices FA-M3>

J3-12

J3.3 Accessible Devices FA-M3

The FA-M3/FA500 internal data are called devices. Devices include bit devices and
word devices, as indicated below:
Bit device
This refers to data where each bit has a meaning. An internal relay is equivalent
to a bit device.
Word device
This refers to data where a word unit (1 word=16 bits) contains the meaning. A
data register is equivalent to a word device.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J3-13

<J3.3 Accessible Devices FA-M3>

List of Accessible Devices FA-M3

Table Accessible Devices FA-M3

Device type

Bit device

Word device

Special device

Device name

Address

Read

Remark

Write

Input relay

Xnnnnn

Output relay

Ynnnnn

(*1) (*2)

Internal relay

Innnn

(*2)

Shared relay

Ennnn

(*2)

Link relay

Lnnnn

(*2)

Special relay

Mnnn

(*2)

Time-up relay

TUnnn

(*2)

Count-up relay

CUnnn

(*2)

Subtracting timer present value

TPnnn

Accumulative timer present value

TInnn

Timer setpoint

TSnnn

(*1) (*2)

Subtracting counter present value

CPnnn

Accumulative counter present value

CInnn

Counter setpoint

CSnnn

Data register

Dnnnn

File register

Bnnnn

(*3)

Shared register

Rnnnn

(*4)

Index register

Vnnnn

(*4)

Link register

Wnnnn

Special register

Znn

Communication time

SPnn

(*6) nn=01 to 04

Communication status

STSnn

(*6) nn=01,17

(*5)

J030301E.EPS

:
*1:
*2:

*3:
*4:
*5:
*6:

Access allowed.
Blank: Access not allowed.
Always set the input relay (Xnnnnn) and output relay (Ynnnnn) so that the last two digits are 01, 17, 33, 49.
If I/O relay points do not exist because of empty slots, etc., that device will be skipped when read by the LC01-0N and
LC02-0N PC link modules.
If the number of points is smaller than 64 points (for example, 32 points, 16 points, 8 points, etc.) or empty slots exist,
all devices are read virtually as 64-point areas by the F3LC11-1N and F3LC11-2N PC link modules.
Bnnnn of the FA-M3 corresponds to the file register (SP25/SP35).
There are neither shared register nor index register in the FA500.
It is possible to write in the FA-M3. However, writing to any devices other than link devices that are assigned to
the self station will be invalid by refresh from other station.
Information on the status of communication with FA-M3/FA500 can be acquired using the special device. The
information obtained by the special device includes SPnn, which indicates communication time, and STSnn, which
indicates communication status.

SEE ALSO
Refer to chapter 2, Devices in the FACTORY ACE FA500 High Performance Programmable Controller/FA-M3 Range Free Controller Ladder Sequence Users Manual (IM 34M06P11-01E) for details regarding addresses of accessible devices.
Refer to the FACTORY ACE FA500 High Performance Programmable Controller/FA-M3 Range Free
Controller Personal Computer Link Module Users Manual and Monitor Module Users Manual (IM
34M05H41-01E) for details concerning reading input and output relays.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.4 Subsystem Data Storing Format FA-M3>

J3-14

J3.4 Subsystem Data Storing Format FA-M3

The following explains the format in which subsystem data acquired from the FA-M3/
FA500 is stored in the FCS.
The storing formats for FA-M3/FA500 bit devices, word devices and special devices
which indicate communication status are given below.

Bit Device FA-M3

When 16 m (m = 1, 2...) number of bit devices are read starting from address n, the FAM3/FA500 data is stored in the FCS as follows. Specify m as the data size via the Communication I/O Builder.
16 bits
n n n n n n
+ + + + + +
15 14 13 12 11 10

n
+
9

n
+
8

n
+
7

n
+
6

n
+
5

n
+
4

n
+
3

n
+
2

n
+
1

n
+
31

m=1

n
+
16

m=2

n+16 (m-1)+15

n+16 (m-1)
J030401E.EPS

Figure Image of Stored Bit Device FA-M3

Word Device FA-M3

When the number of 16 m (m=1, 2 ...) bit devices started from n (n is multiple of 16 plus 1)
are accessed by FCS, the data from the subsystem stored in the buffer as follows.
Specify m as the data size on the definition builder.
16 bits

Contents of the nth register

Contents of the n+1th register

Contents of the n+m-1th register

J030402E.EPS

Figure Image of Stored Word Device FA-M3

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.4 Subsystem Data Storing Format FA-M3>

J3-15

Special Device FA-M3

The FA-M3/FA500 special devices include SPnn data that indicates communication time
and STSnn data that indicates communication status. The following table describes SPnn
and STSnn:
Table Communication Time (SPnn) FA-M3
Explanation

Address

Read

Write

Maximum value for all-point communication time (seconds)

SP01

Yes

No

Present value for all-point communication time (seconds)

SP02

Yes

No

Maximum value for one point communication time (seconds)

SP03

Yes

No

Present value for one point communication time (seconds)

SP04

Yes

No

Remark

J030403E.EPS

Table Communication Status (STSnn) FA-M3

Explanation

Address

Read

Write

Communication status of stations 1 to 16

STS01

Yes

No

Communication status of stations 17 to 32

STS17

Yes

No

Remark

J030404E.EPS

Communication status will become as follows:

Stations defined via the Communication I/O Builder that are communicating normally:
1
Stations defined via the Communication I/O Builder that are faulty: 0
Stations that are not actually communicating (those not defined via the Communication I/O Builder): 1
In the case of special devices, designation of the station number in the communication I/O
builder has no particular significance, but the smallest station number of those that are
communicating is set.
The relationship between bits and stations is shown below. The smallest station number
corresponds to the smallest bit number.
STS01 configuration
15

00

Bit arrangement

16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01
STS17 configuration
15

Station number
00

Bit arrangement

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17
J030405E.EPS

Figure Relationship among Communication Time, Communication Status and Station Number
FA-M3

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.5 Setting Items on System View FA-M3>

J3-16

J3.5 Setting Items on System View FA-M3

FA-M3

In this section, setting items on System View for FA-M3/FA500, the specific functionality and the recommended settings are explained.
SEE ALSO
For more information regarding to Set Details tab on Create New IOM dialog box and subsystem common settings, see the following:
Setting Items for ACM11, ACM12 in J1.5.1, Overview of Setting Items on System View

For FA-M3, the setting items are as follows. This setting is done on the Set Details
tab of the New IOM dialog box called from the System View.
Connection Device
Baud Rate
Parity
Data Bits
Stop Bits
RS Control
DR Check
CD Check
Communication Error Process
Options
After creating the new I/O module, the settings can be modified on the I/O module
property sheet.

Connection Device FA-M3

Set [FA-M3] as the type of connection device (subsystem).

Baud Rate FA-M3

This sets the baud rate between the communication module and FA-M3/FA500.
Recommended setting is [19200 bps].
The baud rate set in the Set Details tab of the New IOM dialog box called from System
View, should match the speed setting of the DIP switch on the FA-M3/FA500.
SEE ALSO
For more information about baud rate setting on FA-M3/FA500, see the following:
J3.8, Settings on Subsystem FA-M3

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.5 Setting Items on System View FA-M3>

J3-17

Parity FA-M3
This sets the method for checking the parity of the subsystem data to be transmitted.
The recommended setting is [Even] parity.
When the baud rate is set to [19200 bps], the [No] parity cannot be set.
The parity set in the Set Details tab of Create New IOM dialog box should match the parity
setting of the DIP switch on the FA-M3/FA500.
SEE ALSO
For more information about DIP switch settings on FA-M3/FA500, see the following:
J3.8, Settings on Subsystem FA-M3

Data Bits FA-M3

This sets the data bit length of the subsystem data to be transmitted.
Recommended setting is [7] bits.
The bit length set in the in the Set Details tab of Create New IOM dialog box should match
the bit length setting of the DIP switch on the FA-M3/FA500.
SEE ALSO
For more information about DIP switch settings on FA-M3/FA500, see the following:
J3.8, Settings on Subsystem FA-M3

Stop Bits FA-M3

This sets the stop bit of the subsystem.
When using FA-M3/FA500, be sure to set [1] bit as stop bit.
The parity set in the Set Details tab of Create New IOM dialog box should match the parity
setting of the DIP switch on the FA-M3/FA500.

IMPORTANT
When using FA-M3/FA500, [2 bits] cannot be used as the stop bit.

SEE ALSO
For more information about DIP switch settings on FA-M3/FA500, see the following:
J3.8, Settings on Subsystem FA-M3

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.5 Setting Items on System View FA-M3>

J3-18

RS Control FA-M3
This item sets whether or not to perform RS control during subsystem data transmission.
When using FA-M3/FA500, disable RS control by leaving the [RS control] check box
unmarked.

DR Check FA-M3
This item sets whether to perform DR check during subsystem data transmission.
When using FA-M3/FA500, enable the DR check by checking the [DR check] check box.

CD Check FA-M3
This item sets whether to perform CD check during subsystem data transmission.
When using FA-M3/FA500, disable the CD check by leaving the [CD check] check box
unmarked.

Communication Error Process FA-M3

This sets the parameters related to communication error handling during subsystem data
transmission.
The following three items must be set.
Response Timeout
This sets the time limit for getting response from FA-M3/FA500. The time is set in unit
of seconds.
Recommended setting is [3] seconds.
Default setting is 4.
Number of Retries Upon Response Timeout
This item sets the number of retries performed when a communication error occurs.
Recommended setting is [1].
Interval of Connection Retries
This sets the time interval of connection requests for checking whether the communication with the station that generated a communication error has returned to normal
(communication recovery). The time is set in unit of seconds.
Recommended setting is [20].
Default setting is 30.

Options FA-M3
Set options for the communication parameters that vary with the connected subsystem.
Options are set by entering settings to the fields of Option 1 through 4 in the Set Detail tab
of the New IOM dialog box called from System View.
In the case of FA-M3/FA500, set 0 in option 1 through option 4.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.6 Setting Items on Communication I/O Builder FA-M3>

J3-19

J3.6 Setting Items on Communication I/O Builder

FA-M3
In this section, setting items on Communication I/O Builder for FA-M3/FA500, the
specific functionality and the recommended settings are explained.
SEE ALSO
For an overview of the setting items on Communication I/O Builder, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

For FA-M3/FA500, the setting items are as follows.

Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

Element FA-M3
Element

With respect to the address of the subsystem data buffer, the element number are displayed on Communication I/O Builder.

Buffer FA-M3
Buffer

This sets the buffer for communicated data.

Must set the buffer since this is a required setting item of the Communication I/O Builder.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.6 Setting Items on Communication I/O Builder FA-M3>

J3-20

Program Name FA-M3 : PFCS/SFCS

Program Name

Set the unit number, slot number and FA-M3 as Program Name on Communication I/O
Builder as follows:
u-sProgramName
u:
Unit number
s:
Slot number
ProgramName: FA-M3

Program Name FA-M3 : LFCS2/LFCS

Program Name

Set the unit number, slot number and FA-M3 as Program Name on Communication I/O
Builder as follows:
n-u-sProgramName
n:
u:
s:
ProgramName:

Node number
Unit number
Slot number
FA-M3

Size FA-M3
Size

This item sets the data size (data length) from the head address set in Device & Address.
Must set the Size since this is a required setting item on Communication I/O Builder.
For FA-M3/FA500, the setting range is 1 to 64 words.
SEE ALSO
For more information about Size setting item, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

Port FA-M3
Port

Port 1 is set for use.

IP Address FA-M3
IP Address

No need to set IP address.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.6 Setting Items on Communication I/O Builder FA-M3>

J3-21

Station FA-M3
Station

This sets the station number of the FA-M3/FA500.

The following indicates the station number format that can be set.
Xnn
X
nn

:
:

CPU number (1 to 4)
Station number (01 to 32)

IMPORTANT
When connecting to the ACM11, the station number is fixed at 01.
When connecting to the ACM12, the station number can be set in the range between
02 and 32. If the ACM12 is used, do not use 01 for the station number.

If the FA-M3 is used with the F3LC11-2N PC link module, match the setting for the station
number between the setting of Communication I/O Builder and the setting via the station
number setting switch in the PC link module.
SEE ALSO
For more information about station number setting DIP switch, see the following:
J3.8, Settings on Subsystem FA-M3

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.6 Setting Items on Communication I/O Builder FA-M3>

J3-22

Device & Address FA-M3

Device & Address

This sets the head address of FA-M3/FA500 data.

The addresses that can be set are the ones consist of eight or less alphanumeric characters shown below:
Input relay:

Xnnnnn

Output relay:

Ynnnnn

Internal relay:

Innnn

Shared relay:

Ennnn

Link relay:

Lnnnn

Special relay:

Mnnn

Time-up relay:

TUnnn

Count-up relay:

CUnnn

Subtracting timer present value:

TPnnn

Adding timer present value:

TInnn

Timer setpoint:

TSnnn

Subtracting counter present value: CPnnn

Adding counter present value:

CInnn

Counter setpoint:

CSnnn

Data register:

Dnnnn

File register:

Bnnnn

Shared register:

Rnnnn

Index register:

Vnnnn

Link register:

Wnnnn

Special register:

Znn

Communication time:

SPnn

Communication status:

STSnn

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.6 Setting Items on Communication I/O Builder FA-M3>

J3-23

Data Type FA-M3

Data Type

This sets data type of the subsystem data.

The data type can be selected from the following:
Input (16-Bit Signed)
Input (32-Bit Signed)
Input (16-Bit Unsigned)
Input (32-Bit Unsigned)
Input (32-Bit Floating)
Output (16-Bit Signed)
Output (32-Bit Signed)
Output (16-Bit Unsigned)
Output (32-Bit Unsigned)
Output (32-Bit Floating)
Input (Discrete)
Output (Discrete)

Reverse FA-M3
Reverse

This sets whether to make the bit or word arrangement in FCS in reverse order of the
subsystem data.
The following settings can be selected:
Bits
No
Words
However, when choosing [Bits], only the data of discrete inputs or discrete outputs can be
reversed. In this case, the default setting is [Bits].
Regarding to words, only the 32-bit input data or 32-bit output data can be reversed. In this
case the default setting is [No].

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.6 Setting Items on Communication I/O Builder FA-M3>

J3-24

Scan FA-M3
Scan

Set whether to read the communication I/O analog data into the communication I/O data
buffer at the beginning of high-speed scan of the FCS.

Service Comment FA-M3

Service Comment

A comment text can be set.

Label FA-M3
Label

The name of the function block I/O terminal can be set as a user-defined label.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.7 System Alarm Messages Specific to FA-M3>

J3-25

J3.7 System Alarm Messages Specific to FA-M3

This section explains the system alarm messages that are specific to FA-M3/FA500.
TIP
When the FA-M3 communication package acquires or sets the FA-M3/FA500 data from FCS, it transmits
the corresponding command to FA-M3/FA500 based on the setting in the Communication I/O Builder. At
the same time, the FA-M3/FA500 interprets the command received and returns a response to FCS. This
response includes a character string that indicates the communication status.
The response contains the character OK when communication is performed normally, and the character
ER together with the error code when communication is not performed normally.

System Alarm Message when a Communication Error Occurs

FA-M3 : PFCS/SFCS
When there is a communication error, the system alarm message as shown below is sent
to HIS:
STNss SS-COM
CODE=####
STNss:
mm:
nn:
zzz:
####:

Error UNITmm

SLOTnn

STNzzz

FCS name
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. The new system alarm message will not
be transmitted even if errors are generated by different causes.
SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs FA-M3

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.7 System Alarm Messages Specific to FA-M3>

J3-26

System Alarm Message when a Communication Error Occurs FA-M3

: LFCS2/LFCS
When a communication error occurs, the system alarm message as shown below is sent
to HIS:
STNss SS-COM Error RIO01 NODExx UNITmm SLOTnn STNzzz CODE=####
STNss:
xx:
mm:
nn:
zzz:
####:

FCS name
Node number
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. The new system alarm message will not
be transmitted even if errors are generated by different causes.
SEE ALSO
For details on error codes, see the following in this document:
Error Codes When a Communication Error Occurs FA-M3

System Alarm Message when Communication Returns to Normal

FA-M3 : PFCS/SFCS
When communication returns to the normal condition, the system alarm message indicated
below is sent to HIS:
STNss SS-COM
STNss:
mm:
nn:
zzz:

Recover

UNITmm

SLOTnn

STNzzz

FCS name
Unit number
Slot number
Subsystem station number

System Alarm Message when Communication Returns to Normal

FA-M3 : LFCS2/LFCS
When communication returns to normal status, the system alarm message indicated below
is sent to HIS:
STNss SS-COM Recover RIO01 NODExx UNITmm SLOTnn STNzzz
STNss:
xx:
mm:
nn:
zzz:

FCS name
Node number
Unit number
Slot number
Subsystem station number

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.7 System Alarm Messages Specific to FA-M3>

J3-27

Error Codes when a Communication Error Occurs FA-M3

There are following error code types for communication errors.
Definition error
Response message error
Communication error
Other error
SEE ALSO
For details on the contents of the errors, refer to the users manual for the FA-M3/FA500 being used.

Definition Error FA-M3

The following errors will occur if the content set via the Communication I/O Builder is
inappropriate. Check the setting made via the Communication I/O Builder when the following errors occur.
Table Definition Error FA-M3
Error code
(hexadecimal)

Description

A3B1

Inappropriate station number

A3B2

Inappropriate address name

A3B3

Inappropriate number of address digits

A3B4

Excessive number of points for communication processing

A3B5

Special device setting error

A3B6

Cannot create communication text

A3B8

Inappropriate address number

A3B9

Address number range error

A3BA

Address size range error

Processing after error occurrence

Communication is not performed with respect to

the definition generating the error. Check the
contents of the definition in the builder.

J030701E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.7 System Alarm Messages Specific to FA-M3>

J3-28

Response Message Error FA-M3

The following errors will occur if an error relating to the communication response is included in the response from the FA-M3/FA500. When the following error occur, perform
communication retry for the number of times set on System View.
Table Response Message Error FA-M3
Error code
(hexadecimal)

Description

A3C1

Station or CPU number error

A3C2

OK, ER error

A3C3

Command error

A3C4

Check sum error

A3C5

ETX, CR error

A3C6

No data received

A3C7

Error in receive data

Processing after error occurrence

Communication is retried after initialization

communication.

J030702E.EPS

SEE ALSO
For details on OK, ER, check sum, ETX, CR, and so on, refer to the FACTORY ACE FA500 High Performance Programmable Controller/FA-M3 Range Free Controller Personal Computer Link Module Users
Manual and the Monitor Module Users Manual (IM 34M05H41-01E).

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.7 System Alarm Messages Specific to FA-M3>

J3-29

Communication Error FA-M3

The following errors will occur due to disagreement of transmission specifications between
FCS and FA-M3/FA500, loss of communication data bits, illegible characters, or I/O module
error on the FA-M3/FA500 side. When the following errors occur, perform communication
retry for the number of times set on System View. If there is still an error during retry, perform recovery communication at each recovery communication time intervals set on System View.
Table Communication Error Code FA-M3
Error code
(hexadecimal)

Description

A391

Communication driver busy

A392

Communication line busy

A393

Communication line not ready

A394

Sending size is too large

A395

Use of communication port not declared

A397

Under run error

A398

Timeout between received characters

A399

Receive buffer overflow

A39A

Parity error in receive data

A39B

Receiving overrun error

A39C

Receiving framing error

A39D

No. of characters received is outside specifications

A39F

Other error

A3D0

CPU number designation error

A3D1

Command error

A3D2

Device designation error

A3D3

Setting value outside the range

A3D4

Number of data outside the range

A3D5

A3D6

CPU type error

A3D7

Parameter error

A3D8

Framing error

A3D9

Overrun error

A3DA

Parity error

Communication is retried. In case of error during retry,

information related to the error occurrence is held for
each station number and recovery communication with
respect to that station number is performed using the set
cycle.

A3DB

Sum check error

A3DC

Internal buffer overflow

A3DD

Character interval timeout

A3DE

CPU error

A3DF

A3E0

Error in device address designation

A3E1

Designation outside the common area range

A3E2

Device error

A3E3

Device not ready

A3E4

Other error

Error code
(hexadecimal)

Processing after error occurrence

Description

Processing after error occurrence

J030703E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.7 System Alarm Messages Specific to FA-M3>

J3-30

Other Errors FA-M3

The following errors occur when a response to FCS command cannot be received from FAM3/FA500 within the specified period of time. If the following errors occur, perform communication retry for the number of times set on System View as in the case of response
message error.
Table Other Errors FA-M3
Error code
(hexadecimal)
A3B0

Description

Processing after error occurrence

No response

A3FE

Receive time out

A3FF

Other error

Retried after initialization communication.

J030704E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.8 Settings on Subsystem FA-M3>

J3-31

J3.8 Settings on Subsystem FA-M3

When performing subsystem communication with the FA-M3/FA500, switch settings
for the FA-M3/FA500 side personal computer link modules are required.
This section explains the setting items for the FA-M3/FA500 side.
The FA-M3/FA500 setting items are listed below.
Terminating resistor setting
Station number setting
Baud rate setting
Data type setting

Switch Positions FA-M3

Switch positions for the F3LC11-1N and F3LC11-2N personal computer link modules are
shown below:
RDY

LC11-1N

C LINK

Front

Back
2 3
9

5 6

0 1

Baud rate setting switch

(1 decimal rotary switch)

7 8

O
F
F

1
2
3
4
5
6
7
8

Data type setting switch

(8 pole DIP switch)

J030801E.EPS

Figure Switch Positions for F3LC11-1N Personal Computer Link Module

RDY

7 8
2 3

C LINK

STATION
NO.

456

7 8

901

2 3

456

901

LC11-2N

Front

Back

Station number
setting switch
(2 decimal
rotary switches)

TERMINATOR

2 3

4
5 6

SD B

Terminating resistor
setting switch
0 1

4-WIRE
OFF

SD A

2-

Baud rate setting switch

(1 decimal rotary switch)

7 8

RD A
RD B
SG

O
F
F

1
2
3
4
5
6
7
8

Data format setting switch

(8 pole DIP switch)

SHIELD

J030802E.EPS

Figure Switch Positions for F3LC11-2N Personal Computer Link Module

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.8 Settings on Subsystem FA-M3>

J3-32

Terminating Resistor Setting FA-M3

If the FA-M3 is used with the F3LC11-2N PC link module, or the FA500 is used with the
LC02-0N PC link module, the terminating resistor setting is required.

Terminating Resistor Setting for the F3LC11-2N PC Link Module

For the F3LC11-2N PC link module, the terminating resistor setting is performed using the
terminating resistor setting switch.
Table Terminating Resistor Setting Switch (F3LC11-2N Personal Computer Link Module)
Connection method

Setting for terminating resistor setting switch

2-wire

4-wire

4
J030803E.EPS

Terminating Resistor Setting for the LC02-0N PC Link Module

There is no switch for the terminating resistor setting in the LC02-0N PC link module.
Therefore, install a 220  terminating resistor in the LC02-0N PC link module.

Station Number Setting FA-M3

As shown below, it is necessary to set the station number on the PC link module side
depending on the PC link module.

When the FA-M3 is Used with the F3LC11-1N PC Link Module

No station number setting is required on the PC link module side. The station number is
always processed as 01.

When the FA-M3 is Used with the F3LC11-2N PC Link Module

The station number setting is required on the PC link module side. Since the station number is used to distinguish multiple computer link modules, duplicate station numbers cannot
be set.
The station number is set using the two decimal rotary switches (station number setting
switches). The station numbers that can be set are within the range of 02 to 32. Do not set
numbers 00, 01 or 33 to 99.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.8 Settings on Subsystem FA-M3>

J3-33

The following shows the station number setting switches on the F3LC11-2N PC link module:
2

STATION
NO.

5
9

6
8

The diagram at left illustrates the setting for 02

4

5
9

6
8

F3LC11-2N
J030804E.EPS

Figure FA-M3 Station Number Setting Switch (F3LC11-2N Personal Computer Link Module)

When the FA500 is Used with the LC01-0N PC Link Module

Set the station number to 01.

When the FA500 is Used with the LC02-0N PC Link Module

Set the station number to 01 when the FA500 is connected to the ACM11 (RS-232C). Set
the station number between 02 and 32 when the FA500 is connected to the ACM12 (RS422/RS-485).

Baud Rate Setting FA-M3

When a subsystem communication is performed with the FA-M3/FA500, it is necessary to
set the baud rate for the PC link module on the FA-M3/FA500 side.
The baud rate setting is performed using a decimal rotary switch (baud rate setting switch).
Setting Baud rate (bps)

1
0
9

2 3

8 7

4
5
6

Cannot set

Cannot set

1200

2400

4800

9600

19200 (*1)

Cannot set

Cannot set

Cannot set
J030805E.EPS

Figure Setting of the Baud Rate Setting Switch

*1:

Recommended setting

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.8 Settings on Subsystem FA-M3>

J3-34

Data Type Setting FA-M3

When a subsystem communication is performed with the FA-M3/FA500, it is necessary to
set the data format for the PC link module on the FA-M3/FA500 side. The data format
setting is performed using an 8-pole DIP switch (data format setting switch).
OFF

OFF
O
F
F

1 2 3 4 5 6 7 8

ON

LC01-0N
LC02-0N
Number

ON
1
2
3
4
5
6
7
8

The drawing at left shows the setting for

the following condition:
Data length 7 bits
Even parity
Stop bit 1 bit
Uses check sum
Has EOT character designation
No protect function

F3LC11-1N
F3LC11-2N
Function

OFF

ON

Remarks

Data length

7 bits

8 bits

Parity check

No

Yes

Parity

Odd number Even number This is enabled only when parity bit [yes] is selected

Stop bit

1 bit

2 bits

Always set to [1 bit]

Check sum

No

Yes

Always set to [yes]

EOT character
designated

No

Yes

Always set to [yes]

Protect function No

Yes

Use with this always OFF

J030806E.EPS

Figure Settings for Data Type Setting Switch

IMPORTANT
When connecting FA-M3/FA500 to ACM11 or ACM12, always set the stop bit, check sum
and terminating character designation as follows:
Stop bit: 1 bit
Check sum: Yes
EOT character designation: Yes

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J3-35

<J3.9 Transmission Time between Communication Module and FA-M3>

J3.9 Transmission Time between Communication

Module and FA-M3
The transmission time between communication module and FA-M3/FA500 subsystem is to be discussed in this chapter.

Communication Time FA-M3

The time required for communication between a communication module and FA-M3/FA500
is figured as the total of the time T1 to T5. However, when a modem is connected, the delay
time by modem is added to T2 and T4.
Data acquisition begins

Communication
module

Data acquisition complete

Create message
to be sent

Interpret response
message, store data

FA-M3/FA500

FA-M3/FA500
processing time
T1

T2

T3

T4

T5
J030807E.EPS

T1:
T2:
T3:
T4:
T5:

Transmission message creation time approximately 10 ms

Send message transmission time
FA-M3/FA500 processing time. The FA-M3/FA500 processing is performed at a break in the ladder sequence program.
Response message transmission time
Response message interpretation time approximately 15 ms

Figure Time Chart of Communication between Communication Module and FA-M3/FA500

Calculating the Communication Time FA-M3

The send message transmission time (T2) and response message transmission time (T4)
are figured using the formula given below:
Transmission time (ms) =
No. of bits
per character

No. of characters to be sent no. of bits per character 1000

Baud rate (bps)
=

start bit

data bit +

parity bit

stop bit
J030808E.EPS

Start bit:
Data bit:
Parity bit:
Stop bit:
Baud rate:

1 bit fixed
7 bits or 8 bits
None, even or odd
1 bit fixed
1200, 2400, 4800, 9600, 19200 (bps)

TIP
The FA-M3/FA500 can handle a maximum of 64 words in a single communication transaction.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J3.9 Transmission Time between Communication Module and FA-M3>

J3-36

Calculation Example for Communication Time FA-M3

When the output data type is set via the Communication I/O Builder, the subsystem communication package reads data from the subsystem first. Then the package compares the
data read from the subsystem with the FCS data and only writes data to the subsystem
when discrepancies are detected.
Because of this, it is difficult to calculate the time required for communication when writing
data to a subsystem since the transmission time varies according to the number of data in
which the value has changed. Therefore, use the following guidelines for communication
time when writing to the subsystem.
When the values for most of the data to be written are not changed
Communication time=The time required for transmission when reading data from the
subsystem with respect to all definitions where write has been designated
When the values for a large number of the data to be written are changed
Communication time=About twice the amount of time required for transmission when
reading data from the subsystem with respect to all definitions where write has been
designated
The following is an example of calculating the transmission time between the communication module and FA-M3/FA500.
In this example, data contents of registers D0001 through 255 are divided into 3 transmissions of 64 data each and one transmission of 63 data, and read.
Transmission time is calculated based on the following conditions:
Baud rate:

19200 bps

Number of characters per data:

Number of bits per character:

10

FA-M3/FA500 processing time:

104 ms
(scan period 100 ms+processing time 4 ms)

Example of calculating transmission time required to read 64 data in a single

communication
Command character count=fixed length section+D0001=16+5=21
Response character count=fixed length section+64 data 4 =11+64 4=267
Time required for a single command transmission (T2) =21 10 1000/19200=11 (ms)
Time required for a single response reception (T4) =267 10 1000/19200=139 (ms)
Transmission time for one 64 data=10+11+ (100+4) +139+15=279 (ms)
Example of calculating transmission time required to read 63 data in a single
communication
Command character count=fixed length section+D0001=16+5=21
Response character count=fixed length section+63 data 4= 11+63 4=263
Time required for a single command transmission (T2) =21 10 1000/19200=11 (ms)
Time required for a single response reception (T4) = 263 10 1000/19200=137 (ms)
Transmission time for one 63 data=10+11+ (100+4) +137+15=277 (ms)
Example of calculating transmission time required to read 255 data
279 3 (times) +277=1114 (ms)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4. FA-M3 Communication (ACM71)>

J4-1

J4. FA-M3 Communication (ACM71)

The FA-M3 communication package is a subsystem communication package designed for the FACTORY ACE FA-M3 range-free controllers manufactured by
Yokogawa (hereinafter referred to as FA-M3s). When the FA-M3 communication
package is used, no need to make customized program to perform communication
between the FCS and the subsystem (FA-M3).
This chapter sections explain the subsystem communication package that are
specific to the communication between the FA-M3 and FCS.
SEE ALSO
For functions common to different subsystem communication packages, see the following:
J1, General Information Regarding to Subsystem Communication

Applicable Models FA-M3

The following FA-M3 communication packages (ACM71) are available.
PFS2231 CS 1000 FA-M3 communication package (ACM71)
LFS2231 CS 3000 FA-M3 communication package (ACM71)
The FA-M3 communication package (ACM71) perform communications between ACM71
(Ethernet communication module) installed in an FCS and a FA-M3 (Ethernet interface
module).
The applicable to FA-M3 communication package models are F3SP21, F3SP25, F3SP35,
F3SP28, F3SP38, F3SP53, F3SP58.

Operating Environment FA-M3

To use the FA-M3 communication package (ACM71), 350 Kbytes are required in the User
C/option area of the FCS used.

IMPORTANT
On Detailed Settings tab of FCS Constants Builder, the setting item SEBOL/User C Ratio
needs to be properly set in accordance with the communication program size.
If the default ratio 100 % is used, all resource is assigned for SEBOL and the communication program may fail when SEBOL program is running.

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J4.1 Communication Specifications FA-M3>

J4-2

J4.1 Communication Specifications FA-M3

The section below explains the communication specifications when ACM71 performs subsystem communications with FA-M3s.

Ethernet Communication Specifications

The Ethernet communication specifications include the following:
Communication protocol:

TCP/IP

The port number is fixed as 12289 (0x3001). Except this port number, the communication
specifications are in accordance with the Ethernet communication standards.

FA-M3 Communication Specifications

The communication specifications specific to the FA-M3 are as follows:
Table FA-M3 Communication Specifications
Item

Description

Data code setting

Binary

Data communication procedure

Uses only the higher link service. Events are not supported.

Available station(s)

Up to 4 stations CPU module that are connected to FA-M3 Ethernet

interface module
J040101E.EPS

Communication Capacity
The communication capacity is as follows:
Maximum number of FA-M3s allowed for communication:
*1

10 (*1)

This capacity stands for the number of FA-M3 can be communicated with one FCS. It is irrelevant to number of ACM71
modules.

The maximum size of data allowed for communication, including data communicated via
other communication packages used for applicable FCSs, is the size allowed in the communication I/O data storage area (4000 words).
Communication data size in one frame is as follows:
F3SP21, F3SP25, F3SP35
Word device:

64 words

Bit device:

16 words (256 bits)

F3SP28, F3SP38, F3SP53, F3SP58

Word device:

256 words

Bit device:

256 words (4096 bits)

One frame is defined in one line on communication builder. It is the same as restricted by
FA-M3 protocol.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.2 Connecting FCS and FA-M3>

J4-3

J4.2 Connecting FCS and FA-M3

This section explains the configuration of connections between FCSs and FA-M3s.

Connection Configuration
An example of connections between FCSs and FA-M3s is shown below:
Ethernet

HIS

HIS
Control bus

FCS

Ethernet
Router

HUB

FA-M3

FA-M3

HUB

FA-M3
J040201E.EPS

Figure Connection Example of FA-M3s

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.2 Connecting FCS and FA-M3>

J4-4

FA-M3 Ethernet Interface FA-M3

The following FA-M3 Ethernet interface module is available.
Table FA-M3 Ethernet Interface Module

Model name
F3LE01-5T

Name
Ethernet interface module 10BASE-5, 10BASE-T
J040202E.EPS

A 10Base-T interface module is used for an ACM71 while 10BASE-T or 10BASE-5 Ethernet interface module is used for the FA-M3. A HUB or other peripherals may be required for
adapting the interfaces.
SEE ALSO
See the users manual of FA-M3 Ethernet Interface Module Users Manual (IM 34M06H24-01E) for more
information on the network configuration method.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J4-5

<J4.2 Connecting FCS and FA-M3>

Addressing
The IP address and subnet mask must be specified for each ACM71 installed in the FCS.
Up to three IP addresses and subnet masks are specified for a single FCS, including the IP
address and subnet mask specified for the control bus of the FCS.
These three IP addresses must have different subnets, respectively.
HIS
Subnet 1
(control bus)

172.16.1.24
(255.255.0.0)
172.16.1.1
(255.255.0.0)

Subnet 2

172.16.1.2
(255.255.0.0)

Subnet 3

172.21.1.1
(255.255.0.0)

RDY
RCV
SND

CN1

RDY
RCV
SND

CN1

172.22.1.1
(255.255.0.0)

FCS

Ethernet

FA-M3

Control bus

FA-M3

RDY
RCV
SND

CN1

RDY
RCV
SND

CN1

FCS

Ethernet

FA-M3
Router
Ethernet
FA-M3

Subnet 4
(router destination, etc.)
J040203E.EPS

Figure Addressing

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.3 Accessible Devices FA-M3>

J4-6

J4.3 Accessible Devices FA-M3

The FA-M3s internal data is called the device. Devices include bit devices and word
devices, as indicated below.
Bit device
Bit device refers to data where each bit has a meaning. An example of bit devices is an internal relay.
Word device
Word device refers to data where each word (1 word = 16 bits) has a meaning.
An example of word devices is a data register.

Accessible Devices FA-M3

The following lists the FA-M3 devices that can be accessed.
Table Accessible Devices FA-M3
Device classification

Bit device

Word device

Device name

Address

Input relay

Xnnnnn

Output relay

Ynnnnn

Internal relay

Innnn

Shared relay

Ennnn

Link relay

Lnnnn

Special relay

Mnnn

Time-up relay

TUnnn

Count-up relay

CUnnn

Subtracting timer present value

TPnnn

Accumulative timer present value

TInnn

Timer setpoint

TSnnn

Subtracting counter present value

CPnnn

Accumulative counter present value

CInnn

Counter setpoint

CSnnn

Data register

Dnnnn

File register

Bnnnn

Shared register

Rnnnn

Index register

Vnnnn

Link register

Wnnnn

Special register

Znn
J040301E.EPS

SEE ALSO
See the users manual of the applicable FA-M3 CPU unit for more information on address specification.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.4 Subsystem Data Storing Format FA-M3>

J4-7

J4.4 Subsystem Data Storing Format FA-M3

The following explains the format in which subsystem data acquired from a FA-M3 is
stored in the FCS.

Bit Device FA-M3

Bit device data is stored in the communication I/O area, as shown below. If Reverse Bits is
enabled, the bit sequence in a word is reversed (and bits with the smaller numbers comprise the most significant byte). On the Communication I/O Builder, the assigned size m
can be specified.
16 bits

%WWxxxx

n n n n n n n
+ + + + + + +
15 14 13 12 11 10 9

n
+
8

n
+
7

n
+
6

n
+
5

n
+
4

n
+
31

n
+
3

n
+
2

n
+
1

m=1

n
+
16

m=2

n+16(m-1)+15

n+16(m-1)
J040401E.EPS

Figure Image of Stored Bit Device FA-M3

Word Device FA-M3

When reading the word device data start from address n to address m, the word device
data are stored in the communication I/O area, as shown below.
16 bits

%WWxxxx

Contents of the nth register

Contents of the n+1th register

Contents of the n+m-1th register

J040402E.EPS

Figure Image of Stored Word Device FA-M3

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.5 Setting Items on System View FA-M3>

J4-8

J4.5 Setting Items on System View FA-M3

FA-M3

In this section, setting items on System View for FA-M3, the specific functionality
and the recommended settings are explained.
SEE ALSO
For more information regarding to Detailed Setting tab on Create New IOM dialog box and subsystem
common settings, see the following:
Setting Items for ACM71 in J1.5.1, Overview of Setting Items on System View

For FA-M3, the setting items are as follows.

FCS Properties
Detailed Setting tab of Create New IOM dialog box
Set IP address, Subnet Mask, Attribute, Destination Address, Router Address
and Hop Count on this tab.
On any of the Detailed Setting tabs, 2 through 5, set Connected Device Name,
Option 1 (Response Timeout), Option 2 (Number of Retries Upon Response
Timeout), Option 3 (Interval of Connection Retries) and Option 4 (Port on FAM3).
After creating the new I/O module, the settings can be modified on Detailed Setting
tabs (2 to 5) of the I/O module property sheet.

FCS Properties FA-M3

Add [FA-M3_E] to Options on Constant tab of FCS property sheet.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.5 Setting Items on System View FA-M3>

J4-9

Create New IOM Dialog Box FA-M3

The following describes the settings on Detailed Setting tab of Create New IOM dialog box:
IP Address
Subnet Mask
Attribute
Destination Address
Router Address
Hop Count
SEE ALSO
For more information about setting items and setting details, see the following:
Setting Items for ACM71 in J1.5.1, Overview of Setting Items on System View

Similarly, select the following items in Detailed Setting tabs 2 through 5 in the Create New
IOM dialog box. Select any of the tabs of Detailed Setting 2 through 5.

Connected Device Name

Set FA-M3_E as the connected device name.

Option 1
This sets the tolerant time for getting response from the subsystem.

Option 2
This item sets the number of retries performed when a communication error occurs.

Option 3
Specify a time interval that the probe communication packets are sent to test if the connection can be established.

Option 4
For FA-M3, set [12289 (0x3001) ] as port number.
Since there is no default setting, this port number must be entered.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.6 Setting Items on Communication I/O Builder FA-M3>

J4-10

J4.6 Setting Items on Communication I/O Builder

FA-M3
In this section, setting items on Communication I/O Builder for FA-M3, the specific
functionality and the recommended settings are explained.
SEE ALSO
For an overview of the setting items on Communication I/O Builder, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

For FA-M3, the setting items are as follows.

Element

Buffer

Program Name

Size

Port

IP Address

Station

Device & Address

Data Type

Reverse

Scan

Service Comment

Label

Element FA-M3
Element

With respect to the address of the subsystem data buffer, the element numbers are displayed on Communication I/O Builder. The element number is indicated for display purposes only. It is not selectable.

Buffer FA-M3
Buffer

This item sets the buffer used by a program.

Be sure to set the buffer, since this setting in the Communication I/O Builder is mandatory.
Other setting items cannot be specified unless the buffer is set.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.6 Setting Items on Communication I/O Builder FA-M3>

J4-11

Program Name FA-M3

Program Name

Set the unit number, slot number and FA-M3_E as a program name of subsystem on
Communication I/O Builder as follows:
u-sProgram Name
u:
Unit number
s:
Slot number
Program Name: FA-M3_E

Size FA-M3
Size

This item sets the data size (data length) from the head address set in Device & Address.
Must set the Size since this is a required setting item on Communication I/O Builder.
For FA-M3, the setting ranges are limited as follows, the unit is in Word.
F3SP21, F3SP25, F3SP35
Word device:

64 Words

Bit device:

16 Words (256 bits)

F3SP28, F3SP38, F3SP53, F3SP58

Word device:

256 Words

Bit device:

256 Words (4096 bits)

SEE ALSO
For more information about Size setting item, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

IMPORTANT
Because of the restrictions on FA-M3 Ethernet interface module F3LE01-5T, a write error
occurs when greater than 249 words.

Port FA-M3
Port

Set the port to 1.

IP Address FA-M3
IP Address

This item sets the IP address of a FA-M3.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.6 Setting Items on Communication I/O Builder FA-M3>

J4-12

Station FA-M3
Station

This sets the station number of the FA-M3.

The following shows the station number format.
Xnn
X
nn

:
:

CPU number (1-4)

Station number (00-99)
Any number can be set for the station number as long as it is in the range between 00 and 99.

Device & Address FA-M3

Device & Address

This item sets the head address of FA-M3 data.

The following addresses consisting of a maximum of eight alphanumeric characters can be
set:
Input relay

:X0nnnn

Output relay

:Y0nnnn

Internal relay

:I0nnn

Shared relay

:E0nnn

Link relay

:L0nnn

Special relay

:M0nn

Time-up relay

:TUnnn

Count-up relay

:CUnnn

Subtracting timer present value

:TPnnn

Accumulative timer present value

:TInnn

Timer setpoint

:TSnnn

Subtracting counter present value

:CPnnn

Accumulative counter present value

:CInnn

Counter setpoint

:CSnnn

Data register

:D0nnn

File register

:B0nnn

Shared register

:R0nnn

Index register

:V0nnn

Link register

:W0nnn

Special register

:Z0n

SEE ALSO
For more information about address setting, see the following:
J4.3, Accessible Devices FA-M3

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.6 Setting Items on Communication I/O Builder FA-M3>

J4-13

Data Type FA-M3

Data Type

This item sets the data type of subsystem data.

The data type can be selected from among the following:
Input (16-Bit Signed)
Input (32-Bit Signed)
Input (16-Bit Unsigned)
Input (32-Bit Unsigned)
Input (32-Bit Floating)
Output (16-Bit Signed)
Output (32-Bit Signed)
Output (16-Bit Unsigned)
Output (32-Bit Unsigned)
Output (32-Bit Floating)
Input (Discrete)
Output (Discrete)

Reverse FA-M3
Reverse

Set whether to reverse the bit/word arrangement between the FCS and the subsystem.
Any of the following can be selected for reverse:
Bits
No
Words
However, the bits setting is valid only if the data type is either the discrete input or discrete
output. In this case, the default is [Bits].
The words setting is valid only if the data type is the 32-bit analog input or the 32-bit analog
output. In this case, the default is [No].

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.6 Setting Items on Communication I/O Builder FA-M3>

J4-14

Scan FA-M3
Scan

Set whether to read the communication I/O analog data into the communication I/O data
buffer at the beginning of high-speed scan of the FCS.

Service Comment FA-M3

Service Comment

This item sets the comment.

Label FA-M3
Label

The name of the function block I/O terminal can be set as a user-defined label.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.7 Settings on Subsystem FA-M3>

J4-15

J4.7 Settings on Subsystem FA-M3

This section describes the setting switches of the Ethernet interface module. In
order to perform subsystem communication with the FA-M3, it is necessary to set
the following switches in the Ethernet interface module on the FA-M3 side.
IP address setting switches
Condition setting switch

IP Address Setting
In order to perform subsystem communication with the FA-M3, it is necessary to set the IP
address in the Ethernet interf0Face module on the FA-M3 side.
The IP address setting is performed using two hexadecimal rotary switches (IP address
setting switches).
Example: Setting the IP address to 172. 21. 1. 2
1

A
1

XX

C
5

Hexadecimal

AC

15

01

02

Decimal

172

21

2
J040701E.EPS

Figure Setting of IP Address Setting Switches FA-M3

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.7 Settings on Subsystem FA-M3>

J4-16

Various Condition Setting

In order to perform subsystem communication with the FA-M3, it is necessary to set various
conditions such as data codes in the Ethernet interface module on the FA-M3 side.
These various condition settings are performed using an 8-pole DIP switch (condition
setting switch).
OFF

8 7 6 5 4 3 2 1

No.

Function

Set value for ACM71

Remarks (*1)

Data code setting

ON

ON: Binary, [OFF]: ASCII

Write protect

OFF

ON: Write protected, [OFF]: Not write protected

3-6 Always OFF

OFF

[OFF]

Line processing at TCP timeout

occurrence

OFF

ON: Does not close, [OFF]: Closes

Self loop-back test

OFF

ON: Test mode, [OFF]: Normal operation

J040702E.EPS

*1:

A value enclosed by [ ] indicates the setting at the time of factory shipment.

Figure Setting of Condition Setting Switch FA-M3

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.8 System Alarm Messages Specific to FA-M3>

J4-17

J4.8 System Alarm Messages Specific to FA-M3

This section describes the error codes of system alarm messages specific to FA-M3.

Error Code
The table below shows the error codes specific to the FA-M3.
Table Error Code FA-M3
Error code (Hexadecimal)

Description

A3B0

No response

A3B1

Station number setting error

A3B2

Inappropriate address name

A3B6

Too many communication processing points

A3B8

Inappropriate address number

A3B9

Address number range error

A3BB

IP address error

A3BC

Too many subsystems

A3BD

Card option error

A3BE

Card option setting error

A3D1

CPU number error ($01)

A3D2

Command error ($02)

A3D3

Device designation error ($03)

A3D5

Data count outside the range ($05)

A3D8

Parameter error ($08)

A3E1

CPU error ($51)

A3E2

CPU processing error ($52)

J040801E.EPS

The A3D1 and succeeding codes indicate errors generated when an error code is received
from the FA-M3. The error codes from the FA-M3 are indicated in parentheses.
SEE ALSO
See the FA-M3 Users Manual for more information on error codes.
For error codes pertaining to Ethernet communications, see the following:
J2.4, System Alarm Messages Specific to Ethernet Communication

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.9 Transmission Time between Communication Card and FA-M3>

J4-18

J4.9 Transmission Time between Communication

Card and FA-M3
This section explains the transmission time for communication between the communication card and a FA-M3.

Communication Performance
The transmission time for communication between the communication card and a FA-M3 is
calculated as a sum of T1 through T4 as shown below.
Communication begins

Communication
card

Communication complete

Request
generation
processing

Data

FA-M3

Data

Communication
processing
T1

T2

T3

T4

T1: Request generation time. Approximately 50 ms.

T2: Transmission time of request
T3: Response creation time (PLC CPU processing time)
T4: Transmission time of response
J040901E.EPS

Figure Time Chart for Communication between Communication Card and FA-M3

SEE ALSO
See the FA-M3 Users Manual for more information on T2 through T4.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J4.9 Transmission Time between Communication Card and FA-M3>

J4-19

Calculation Example
The following shows an example of calculating the transmission time when reading data of
64 data registers.
The communication time is calculated based on the following conditions:
Comparing with other processing times, the transmission times of request (T2) and response (T4) are trivial, all together about 1 to 5 milliseconds. Thus in this calculation, T2 +
T4 = 5 ms.
The FA-M3s scan period is 50 ms.
Transmission time of request (T2) + Transmission time of response (T4) = 5 ms
CPU processing time (T3)
= Number of points/Number of points processed in one scan3scan time
= 64/6450 = 50ms
4

Total time = Ti = 50 + 5 + 50 = 105 (ms)

i=1
J040902E.EPS

TIP
Note that the calculation is approximate since the actual communication time may vary by a wide margin
depending on network traffic.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

Blank Page

<J5. DARWIN Communication>

J5-1

J5. DARWIN Communication

The DARWIN communication package is a subsystem communication package
corresponding to the DARWIN series data acquisition unit DA 100 as well as hybrid
recorders DR231, DR232, DR241 and DR242 (hereinafter referred to as DARWIN)
manufactured by Yokogawa. By using the DARWIN communication package, the
communication between the FCS and a subsystem (DARWIN) can be performed
without making a customized program.
ACM11 is the only communication module that can be connected to DARWIN.
This chapter explains the communication between DARWIN and FCS among the
subsystem communication packages.
SEE ALSO
Regarding the subsystem communication package functions common to different subsystem communication packages, see the following:
J1, General Information Regarding to Subsystem Communication

Applicable Models DARWIN

For the DARWIN communication package, the following product is available:
PFS2211 CS 1000 DARWIN communication package (ACM11)
LFS2211 CS 3000 DARWIN communication package (ACM11)
The DARWIN communication package performs a subsystem communication between the
FCS and DARWIN, by connecting the DARWIN module to the communication module
(ACM11).
The following DARWIN modules can be connected to ACM11:
DARWIN series data acquisition unit DA100
RS-232C module
Hybrid recorders DR231, DR232, DR241 and DR242
RS-232C module

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J5.1 Communication Specifications DARWIN>

J5-2

J5.1 Communication Specifications DARWIN

The section below explains the specifications when performing subsystem communication with the DARWIN.

Communication Specifications DARWIN

The capacity limitations specific to DARWIN when performing subsystem communication
with the DARWIN are indicated below:
Table Capacity of Communication between FCS and DARWIN
Item

Maximum quantity

Explanation

Amount of data that can be communicated with

one communication module

500 words
(1 word=16 bits)

Maximum amount that can be

accessed from the regulatory control
block/sequence control block.

300 channels

Support one to one communication

only.

60 words

One frame is defined in one line on

the builder. It is the same as
restricted by DARWIN protocol.

Number of channels per one DARWIN unit

Data size in one communication frame

J050101E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.1 Communication Specifications DARWIN>

J5-3

Transmission Specifications DARWIN

The transmission specifications when performing subsystem communication with the DARWIN are indicated below:
Table Transmission Specifications DARWIN
Item

Description

Interface

RS-232C (D-sub 25 pins)

Transmission method

Half duplex

Remark
ACM11

Synchronization method

Start-stop synchronization

Baud rate

1200, 2400, 4800, 9600,

[19200] bps

(*1)

Transmission procedure

Dedicated control procedure

Binary mode

Transmission code

Binary

Data type

Control line

Start bit

Data bit

Parity bit

None, [even], odd

Stop bit

RS

Always ON

ER

Always ON

DR check

Yes

CD check

No

CS check

Transmission when ON only

Transmission enable
monitoring time

1000ms

(*1)

Reception character interval

10ms
monitoring time

Time monitoring

Text frame

Character interval
timeout processing

End of text

Reception start character

None

EOT character

None

XON/XOFF control

None

No response time setpoint

0 to 99 sec. [3 sec.]

(*1)

Number of retries for communication error

0 to 99 sec. [one time]

(*1)

Recovery communication time interval

0 to 999 sec [20 sec]

(*1)

Transmission wait time

1 sec.

Item

Description

Remark
J050102E.EPS

Note: [ ] indicates the recommended settings.

*1:
This can be changed using the property dialog box called from the System View.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.2 Connecting FCS and DARWIN>

J5-4

J5.2 Connecting FCS and DARWIN

The following explains the connection type and cable connections between FCS and
DARWIN.

Connection Type DARWIN

An example of the connection between FCS and DARWIN is shown below:
HIS

Control bus

FCS

ACM11 (RS-232C communication module)

RDY
RCV
SND

CN1

RDY
RCV
SND

AMN33 (Nest for communication module)

CN1

RS-232C
DARWIN

J050201E.EPS

Figure Connection Example between FCS and DARWIN

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.2 Connecting FCS and DARWIN>

J5-5

Cable Connection when Using the ACM11 DARWIN

To connect the ACM11 and DARWIN by cable, use the RS-232C D-sub 25 pin connector.
The ACM 11 and DARWIN can be directly connected if the length of RS-232C cable is 15
meters or less and the grounding system of ACM 11 is the same as that of DARWIN. Use
the ACM 12 when the cable length is more than 15 meters.
Table RS-232C D-sub 25 Pin Connector Specifications DARWIN
Pin number

Signal name

Title

FG

Frame ground

SD

Send data

RD

Receive data

RS

Request to Send

CS

Clear to Send

DR

Data Ready

SG

Signal ground

CD

Carrier Detected

20

ER

Data Terminal Ready

Direction of signal
ACM11

DARWIN

Description
Safety grounding

Used for handshake when data is received.

Used for handshake when data is sent.
Detects whether sending and receiving with
correspondent are allowed

When sending and receiving are allowed,

ON is output
J050202E.EPS

SEE ALSO
For details on safety grounding, see the following:
Figure Cable Connection between ACM11 and DARWIN (when connected directly)

Pin No. 25

Pin No. 14

Pin No. 13

Pin No. 1
J050203E.EPS

Figure Pin Assignment of the RS-232C D-sub 25 Pin Connector DARWIN

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.2 Connecting FCS and DARWIN>

J5-6

Shown below are the cable connections when the ACM11 and DARWIN are connected via
modem and connected directly without using a modem:
SD
RD
RS
CS
ACM11

DR
SG
CD
ER
FG

20

20

SD
RD
RS
CS
DR

Modem (*1)

SG
CD
ER
FG

Sheathed cable
Protective ground (100 ohms or less)
J050204E.EPS

*1:

Generally FG and SG are connected for modem.

Figure Cable Connection between ACM11 and Modem

SD
RD
RS
CS
ACM11

DR
SG
CD
ER
FG

20
1

Sheathed cable

20
1

SD
RD
RS
CS
DR

DARWIN

SG
CD
ER
FG

Protective ground (100 ohms or less)

J050205E.EPS

Figure Cable Connection between ACM 11 and DARWIN (when connected directly)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.2 Connecting FCS and DARWIN>

J5-7

With the ACM11, the RS-232C circuit and FG (frame ground) are electrically insulated. This
has the function of preventing intrusion of noise from the DARWIN side and improving
noise resistance. Satisfy all conditions given below to make this function effective:
For the frame ground, perform protective grounding (100 ohms or less) at the opposing side of the connection (the DARWIN side).
Attach only one side of the shield of the sheathed cable to the FG of the opposing side
of the connection. DO not ground the cable shield on the ACM11 side. Also, do not
use a connector shell that is conductive.
Connect the FG and the SG of RS-232C circuit on the opposing side of connection.
The FG and SG are connected on the DARWIN side. When using a modem in which
the FG and SG are not connected, use Yokogawa Electrics AKB141 (RS-232C
modem cable). For the AKB141 cable, SG and FG are connected inside of the connector shell. The cable shield can be connected to the FG on the opposing side of
connection.
SEE ALSO
For details on cable connections, see the following:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.3 Accessible Data DARWIN>

J5-8

J5.3 Accessible Data DARWIN

This section explains DARWIN internal data that can be accessed using communication I/O.

Accessible Data DARWIN

The following section describes the accessible internal data of DARWIN:
For DA 100
Measured data and alarm status
The measured channels are 001 through 560.
For DR231, DR232, DR241 and DR242
Measured data
The measured channels are 001 through 560.

IMPORTANT
An error will occur when there is no input channel acknowledged by DARWIN between specified channels.
The channels for integration or other calculations in DARWIN can not be accessed.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J5-9

<J5.4 Subsystem Data Storing Format DARWIN>

J5.4 Subsystem Data Storing Format DARWIN

This section explains the format in which the subsystem data acquired from DARWIN are stored in the FCS.
Subsystem data from DARWIN are stored in FCS without additional data processing
or data conversion.

Storage Format of Measured Data and Alarm Status DARWIN

Measured data from DARWIN
Data length Year Month Date

Hour Minute Year

A1 B1

C1 D1

DATA1

......

An

Bn

Cn

Dn

DATAn

Data in the FCS

Measured data

DATA1
DATA2
DATA3
:
:

:
:
:

DATAn
Alarm status

C1

D1

C2

D2

C3

D3
:
:
:

:
:

Cn

Dn
J050401E.EPS

Figure Storage Format of Measured Data and Alarm Status DARWIN

A1 to An:

Base unit number

B1 to Bn:

Channel number

C1 to Cn:

Alarm status (Lavel 1/2)

D1 to Dn:

Alarm status (Lavel 3/4)

Data1 to Datan:

Measured data

SEE ALSO
For details on alarm status, refer to Users Manual of DARWIN.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.5 Setting Items on System View DARWIN>

J5-10

J5.5 Setting Items on System View DARWIN

DARWIN

In this section, setting items on System View for DARWIN, the specific functionality
and the recommended settings are explained.
SEE ALSO
For more information regarding to Set Details tab on Create New IOM dialog box and subsystem common settings, see the following:
Setting Items for ACM11, ACM12 in J1.5.1, Overview of Setting Items on System View

For DARWIN, the setting items are as follows. This setting is done on the Set Details
tab of the New IOM dialog box called from System View.
Connection Device
Baud Rate
Parity
Data Bits
Stop Bits
RS Control
DR Check
CD Check
Communication Error Process
Options
After creating the new I/O module, the settings can be modified on the I/O module
property sheet.

Connection Device DARWIN

Set [DARWIN] as the type of connection device (subsystem).
Must perform this setting since the default is [FA-M3].

Baud Rate DARWIN

This sets the baud rate between the communication I/O module and DARWIN.
The recommended value for the baud rate is [19200 bps].

Parity DARWIN
This sets the method for checking the parity of the subsystem data to be transmitted.
The recommended setting for the parity is [Even].
When the transmission speed is set to [19200 bps], the [no] parity choice cannot be set.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.5 Setting Items on System View DARWIN>

J5-11

Data Bits DARWIN

This sets the data bit length of the subsystem data to be transmitted.
Be sure to select [8 bits] for the bit length when using DARWIN.

IMPORTANT
When using DARWIN, a communication error will occur if [7 bits] is selected.

Stop Bits DARWIN

This sets the stop bit of the subsystem data to be transmitted.
Be sure to select [1 bit] when using DARWIN.

IMPORTANT
When using DARWIN, [2 bits] cannot be chosen.

RS Control DARWIN
This item sets whether or not to perform RS control during subsystem data transmission.
When using DARWIN, enable RS control by checking the [RS control] check box.
By default, the [RS control] checkbox is not checked.

DR Check DARWIN
This item sets whether to perform DR check during subsystem data transmission.
When using DARWIN, disable DR check by leaving the [DR Check] check box unchecked.
By default, the [DR check] check box is checked.

CD Check DARWIN
This item sets whether to perform CD check during subsystem data transmission.
When using DARWIN, disable CD check by leaving the [CD Check] check box unchecked.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.5 Setting Items on System View DARWIN>

J5-12

Communication Error Process DARWIN

This item sets the parameters relating to communication error handling during subsystem data transmission.
The following three items must be set.
Response Timeout
This sets the time limit for getting response from DARWIN. The time is set in unit of
seconds.
Recommended setting is [3].
Default setting is 4.
Number of Retries Upon Response Timeout
This item sets the number of retries performed when a communication error occurs.
Recommended setting is [1].
Interval of Connection Retries
This sets the time interval of connection requests for checking whether the communication with the station that generated a communication error has returned to normal
(communication recovery) . The time is set in unit of seconds.
Recommended setting is [20].
Default setting is 30.

Options DARWIN
Set options for the communication parameters that vary with the connected subsystem.
Options are set by entering settings to the fields of Option 1 through 4 in the Set Detail tab
of the New IOM dialog box called from the System View.
In the case of DARWIN, set "0" in option 1 through option 4.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.6 Setting Items on Communication I/O Builder DARWIN>

J5-13

J5.6 Setting Items on Communication I/O Builder

DARWIN
In this section, setting items on communication builder for DARWIN, the specific
functionality and the recommended settings are explained.
SEE ALSO
For an overview of the setting items on Communication I/O Builder, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

For DARWIN, the setting items are as follows.

Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

Element DARWIN
Element

With addresses of the subsystem data buffer, the element numbers are displayed on
Communication I/O Builder .
The element numbers are for display only, cannot be set.

Buffer DARWIN
Buffer

This item sets the buffer used by a program.

Must set the buffer size since this is a required setting item of the Communication I/O Builder.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.6 Setting Items on Communication I/O Builder DARWIN>

J5-14

Program Name DARWIN : PFCS/SFCS

Program Name

Set the unit number, slot number and DARWIN program name of subsystem as follows:
u-sProgramName
u:
s:
ProgramName:

Unit Number
Slot Number
DARWIN

Program Name DARWIN : LFCS2/LFCS

Program Name

Set the node number, unit number, slot number and DARWIN as Program Name on Communication I/O Builder as follows:
n-u-sProgramName
n:
u:
s:
ProgramName:

Node
Unit Number
Slot Number
DARWIN

Size DARWIN
Size

This item sets the data size (data length) from the head address set in Device & Address.
Must set the Size since this is a required setting item on Communication I/O Builder.
For DARWIN, the setting range is limited to 64 words
Precautions on use of DARWIN are as follows:
For alarm status, set the same size as the measured data immediately before.
The setting cannot include a nonexistent channel nor extend beyond the range of
subunits.
SEE ALSO
For more information about Size setting item, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

Port FA-M3
Port

Port 1 is set for use.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.6 Setting Items on Communication I/O Builder DARWIN>

J5-15

IP Address DARWIN
IP Address

No need to set IP address.

Station DARWIN
Station

This sets the station number of the DARWIN.

In the case of DARWIN, a station number indicates the ID of each data.
The station numbers that can be set are 1 to 30.

Device & Address DARWIN

Device & Address

This sets the head address of DARWIN data.

The addresses can be set are shown below:
Measured data: DTscc
Alarm status:

ALscc

s is a subunit number, and cc is a channel number.

Data Type DARWIN

Data Type

This sets data type of the subsystem data.

The data type can be selected from the following:
For measured data
Input (16-Bit Signed)
For alarm status
Input (16-Bit Unsigned)

Reverse DARWIN
Reverse

This sets whether to make the bit or word arrangement in the FCS in reverse order of the
subsystem data.
With DARWIN, choose [No].
The default setting is [No].

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.6 Setting Items on Communication I/O Builder DARWIN>

J5-16

Scan DARWIN
Scan

Set whether to read the communication I/O analog data into the communication I/O data
buffer at the beginning of high-speed scan of the FCS.

Service Comment DARWIN

Service Comment

A comment text can be set.

Label DARWIN
Label

The name of the function block I/O terminal can be set as a user-defined label name.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.7 Communication Packet DARWIN>

J5-17

J5.7 Communication Packet DARWIN

The section below explains the communication text format when performing communication with the DARWIN.

Communication Packet for Byte Sequence Specification+Output Data

Selection DARWIN
The figure below shows the communication packet format for byte sequence
specification+output data selection:
Byte sequence specification + output data selection
'B' 'O' p1 ':' 'T' 'S' p2 CR LF
p1:
p2:

Byte output sequence

From '0' MSB (most significant byte)
Measured data output
From '0' MSB (most significant byte)
J050701E.EPS

Figure Communication Packet for Byte Sequence Specification + Output Data Selection
DARWIN

Communication Packet for Reply DARWIN

The figure below shows the communication packet format for reply:
Reply
'E' ERR CR LF
ERR: Error code
'0' Request normal receipt
'1' Error occurrence
J050702E.EPS

Figure Communication Packet for Reply DARWIN

Communication Packet for Trigger Execution DARWIN

The figure below shows the communication packet format for trigger execution:
Trigger execution
ESC 'M' CR LF
J050703E.EPS

Figure Communication Packet for Trigger Execution DARWIN

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J5-18

<J5.7 Communication Packet DARWIN>

Communication Packet for Measured Data Output Format Specification

DARWIN
The figure below shows the communication packet format for measured data output format
specification:
Measured data output format specification
'F' 'M' p3 '.'

p4
p3:
p4:
p5:

'.'

p5

CR LF

Operation mode
'1' Output measured data as binary data
Output head channel
Specify in three ASCII digits (no 0 suppression)
Output end channel
Specify in three ASCII digits (no 0 suppression)
J050704E.EPS

Figure Communication Packet for Measured Data Output Format Specification DARWIN

Communication Packet for Measured Data DARWIN

The figure below shows the communication packet format for measured data from
DARWIN.
Measured data output format specification
Data length Year Month Date

Hour Minute Year

Data length: 66 N
Year:
Month:
Date:
Hour:
Minute:
Second:

A1 B1

C1 D1

DATA1

A1 to n:
B1 to n:
C1 to n:
D1 to n:
DATA1 to DATAn:

......

An

Bn

Cn

Dn

DATAn

Base unit number

Channel number
Alarm status (level 1/2)
Alarm status (level 3/4)
Measured data
0 to 0x7FFE Normal data
0x7FFF
Plus over data
0x8001
Minus over data
0x8002
Measured data setting is skipped
0x8004
No abnormal data
0x8005
No data
J050705E.EPS

Figure Communication Packet for Measured Data DARWIN

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.8 System Alarm Messages Specific to DARWIN>

J5-19

J5.8 System Alarm Messages Specific to DARWIN

This section explains the system alarm messages that are specific to DARWIN.
TIP
When acquiring DARWIN data from FCS, the DARWIN communication package sends the corresponding command to the DARWIN based on the setting in the Communication I/O Builder. The DARWIN then
interprets the command it received and returns a response to FCS.

System Alarm Message Sent when a Communication Error Occurs

DARWIN : PFCS/SFCS
When there is a communication error, the system alarm message as shown below is sent
to HIS:
STNss SS-COM
CODE=####
STNss:
mm:
nn:
zzz:
####:

Error UNITmm

SLOTnn

STNzzz

FCS name
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. After that, a new system alarm message
will not be sent even if an error is generated by a different cause.
SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs DARWIN

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.8 System Alarm Messages Specific to DARWIN>

J5-20

System Alarm Message when a Communication Error Occurs DARWIN

: LFCS2/LFCS
When a communication error occurs, the system alarm message as shown below is sent
to HIS:
STNss SS-COM Error RIO01 NODExx UNITmm SLOTnn STNzzz CODE=####
STNss:
xx:
mm:
nn:
zzz:
####:

FCS name
Node number
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. The new system alarm message will not
be transmitted even if errors are generated by different causes.
SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs DARWIN

System Alarm Message Sent when Communication Returns to Normal

DARWIN : PFCS/SFCS
When communication returns to the normal condition, the system alarm message indicated
below is sent to HIS:
STNss SS-COM
STNss:
mm:
nn:
zzz:

Recover

UNITmm

SLOTnn

STNzzz

FCS name
Unit number
Slot number
Subsystem station number

System Alarm Message Sent when Communication Returns to Normal

DARWIN : LFCS2/LFCS
When communication returns to normal condition, the system alarm message indicated
below is sent to HIS:
STNss SS-COM Recover RIO01 NODExx UNITmm SLOTnn STNzzz
STNss:
xx:
mm:
nn:
zzz:

FCS name
Node number
Unit number
Slot number
Subsystem station number

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.8 System Alarm Messages Specific to DARWIN>

J5-21

Error Codes when a Communication Error Occurs DARWIN

The error codes at communication error include the following types:
Definition error
Response message error
Communication error
Other error
SEE ALSO
For the details of errors, refer to the users manual for the connected DARWIN.

Definition Error DARWIN

The following errors will occur when an item set on Communication I/O Builder is not
appropriate. Check the setting in the Communication I/O Builder when the following errors
occur:
Table Definition Errors DARWIN
Error Code
(hexadecimal)

Description

A3B1

Inappropriate address name

A3B2

Inappropriate subunit number

A3B3

Inappropriate channel number

A3B4

No data definition

A3B5

Size disagreement with data definition

A3B6

Inappropriate element type

A3B7

Inappropriate communication size allocation

Processing after error occurrence

No communication

J050801E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.8 System Alarm Messages Specific to DARWIN>

J5-22

Response Message Error DARWIN

The following errors will occur if there is an error in the response from DARWIN with regard
to the communication response. Retry communication when the following errors occur:
Table Response Message Errors DARWIN
Error Code
(hexadecimal)

Description

A3C1

"Byte sequence specification + ....." No response

A3C2

"Byte sequence specification + ....." Error reply

A3C3

"Byte sequence specification + ....." Format error

A3C4

Processing after error occurrence

<reserved>

A3C5

"Trigger execution" No response

A3C6

"Trigger execution" Error reply

A3C7

"Trigger execution" Format error

A3C8

<reserved>

A3C9

<reserved>

A3CA

Communication is performed during each scan.

"Measured data ....." No response

A3CB

"Measured data ....." Error reply

A3CC

"Measured data ....." Format error

A3CD

"Measured data ....." Channel error

A3CE

<reserved>

A3CF

<reserved>
J050802E.EPS

Communication Error DARWIN

The table below lists the errors caused by an abnormal communication:
Table Communication Errors DARWIN
Error code
(hexadecimal)

Description

A391

Communication driver busy

A392

Communication line busy

A393

Communication line not ready

A394

Sending size is too large

A395

Use of communication port not declared

A397

Under run error

A398

Timeout between received characters

A399

Receive buffer overflow

A39A

Parity error in receive data

A39B

Receiving overrun error

A39C

Receiving framing error

A39D

No. of characters received is outside specifications

A39F

Other error

Processing after error occurrence

J050803E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.8 System Alarm Messages Specific to DARWIN>

J5-23

Other Errors DARWIN

The following errors will occur if no response for FCS command is received from DARWIN
within the specified period of time. When the following errors occur, retry communication as
in the case of response message error:
Table Other Error DARWIN
Error code
(hexadecimal)
A3B0

Description

Processing after error occurrence

No response

A3FE

Receive time out

A3FF

Other error

Retried after initialization communication.

J050804E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.9 Error Handling when a Communication Error Occurs>

J5-24

J5.9 Error Handling when a Communication Error

Occurs
The communication errors given below may occur when any of the commands,
byte sequence specification + output data selection, trigger execution, specification of output format and output channel for measured data are executed.
No-response error
Reply error
Format error

Error after Execution of Byte Sequence Specification + Output Data

Selection
No-Response Error after Execution of Byte Sequence Specification +
Output Data Selection
When the time until a reply (or measured data) is returned after an execution of byte
sequence specification + output data selection exceeds the builders send-receive interval monitoring time, retries will be repeated for the number of times specified for number
of retries in the builder.
When communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a no-response error is set for the byte
sequence specification + output data selection and retries will be performed until the
communication recovers.

ACM11 side
DARWIN side

Byte sequence
specification +
output data selection

Byte sequence
specification +
output data selection
Send-receive interval
monitoring time
Retries
J050901E.EPS

Figure No-Response Error after Execution of Byte Sequence Specification + Output Data
Selection

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.9 Error Handling when a Communication Error Occurs>

J5-25

Reply Error after Execution of Byte Sequence Specification + Output Data

Selection
When byte sequence specification + output data selection is executed but the reply (or
measured data) is returned in error (E1+CR+LF), retries will be repeated for the number
of times specified for number of retries in the builder.
When communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a reply error is set for the byte sequence specification + output data selection and retries will be performed until the communication recovers.

ACM11 side

Byte sequence
specification +
output data selection

Byte sequence
specification +
output data selection
Reply
("E1"+CR+LF)

DARWIN side

Reply
("E1"+CR+LF)

Retries
J050902E.EPS

Figure Reply Error after Execution of Byte Sequence Specification + Output Data Selection

Format Error after Execution of Byte Sequence Specification + Output

Data Selection
When byte sequence specification + output data selection is executed but the reply (or
measured data) is returned in an unexpected frame format, retries will be repeated for the
number of times specified for number of retries in the builder.
When communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a format error is set for the byte
sequence specification + output data selection and retries will be performed until the
communication recovers.

ACM11 side
DARWIN side

Byte sequence
specification +
output data selection

Byte sequence
specification +
output data selection
Reply (?)

Reply (?)

Retries
J050903E.EPS

Figure Format Error after Execution of Byte Sequence Specification + Output Data Selection

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.9 Error Handling when a Communication Error Occurs>

J5-26

Error after Trigger Execution

No-Response Error after Trigger Execution
When the time until a reply (or measured data) is returned after trigger execution exceeds
the builders send-receive interval monitoring time, retries will be repeated for the number
of times specified for number of retries in the builder.
When communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a no-response error is set for the
trigger execution and retries will be performed starting from byte sequence specification
+ output data selection.

ACM11 side

Trigger execution
(=<GET>)
Send-receive interval
monitoring time

DARWIN side

Byte sequence
specification +
output data selection

Trigger execution
(=<GET>)
Send-receive interval
monitoring time
Retries

J050904E.EPS

Figure No-response Error after Trigger Execution

Reply Error after Trigger Execution

When trigger execution is executed but the reply (or measured data) is returned in error
(E1+CR+LF), retries will be repeated for the number of times specified for number of
retries in the builder.
When communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a reply error is set for the trigger
execution and retries will be performed starting from byte sequence specification + output
data selection.

ACM11 side
DARWIN side

Trigger execution
(=<GET>)

Byte sequence
specification +
output data selection

Trigger execution
(=<GET>)
Reply
(E1+CR+LF)

Reply
(E1+CR+LF)

Retries

J050905E.EPS

Figure Reply Error after Trigger Execution

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.9 Error Handling when a Communication Error Occurs>

J5-27

Format Error after Trigger Execution

When trigger execution is executed but the reply (or measured data) is returned in an
unexpected frame format, retries will be repeated for the number of times specified for
number of retries in the builder.
When communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a format error is set for the trigger
execution and retries will be performed starting from byte sequence specification + output
data selection.

ACM11 side

Trigger execution
(=<GET>)

DARWIN side

Byte sequence
specification +
output data selection

Trigger execution
(=<GET>)
Reply (?)

Reply (?)

Retries

J050906E.EPS

Figure Format Error after Trigger Execution

Error after Execution of Specification of Output Format and Output

Channel for Measured Data
No-Response Error after Execution of Specification of Output Format and
Output Channel for Measured Data
When the time until a reply (or measured data) is returned after an execution of specification of output format and output channel for measured data exceeds the builders sendreceive interval monitoring time, retries will be repeated for the number of times specified
for number of retries in the builder.
When communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a no-response error is set for the
specification of output format and output channel for measured data and retries will be
performed starting from byte sequence specification + output data selection.

ACM11 side
DARWIN side

Specification of
output format and
output channel for
measured data

Specification of
output format and
output channel for
measured data
Send-receive interval
monitoring time

Byte sequence
specification +
output data selection
Send-receive interval
monitoring time
Retries

J050907E.EPS

Figure No-Response Error after Execution of Specification of Output Format and Output
Channel for Measured Data

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.9 Error Handling when a Communication Error Occurs>

J5-28

Reply Error after Execution of Specification of Output Format and Output

Channel for Measured Data
When specification of output format and output channel for measured data is executed
but the reply (or measured data) is returned in error (E1+CR+LF), retries will be repeated
for the number of times specified for number of retries in the builder.
When communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a reply error is set for the specification
of output format and output channel for measured data and retries will be performed
starting from trigger execution.
Specification of
output format and
output channel for
measured data

ACM11 side

Specification of
output format and
output channel for
measured data
Reply
(E1+CR+LF)

DARWIN side

Trigger execution

Reply
(E1+CR+LF)

Retries

J050908E.EPS

Figure Reply Error after Execution of Specification of Output Format and Output Channel for
Measured Data

Format Error after Execution of Specification of Output Format and Output Channel for Measured Data
Causes of format errors and loss of data are given below:
Format error
The data length stored in the top two bytes of the measured data does not agree with
the actual data length, or the number of data requested and the number of data
actually returned differ.
Channel error
The data channel number does not continue on from the starting channel number.
When specification of output format and output channel for measured data is executed
but the reply (or measured data) is returned in an unexpected frame format or loss-of-data
occurs, retries will be repeated for the number of times specified for number of retries in
the builder.
When communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a format error is set for the trigger
execution and retries will be performed starting from byte sequence specification + output
data selection.

ACM11 side
DARWIN side

Specification of
output format and
output channel for
measured data

Specification of
output format and
output channel for
measured data
Reply (?)

Trigger execution

Reply (?)

Retries
J050909E.EPS

Figure Format Error after Execution of Specification of Output Format and Output Channel for
Measured Data

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J5-29

<J5.10 Transmission Time between Communication Module and DARWIN>

J5.10 Transmission Time between Communication

Module and DARWIN
The transmission time between communication module and DARWIN subsystem is
to be discussed in this chapter.

Communication Time DARWIN

The time required for communication between a communication module and the DARWIN can
be obtained by adding the times for phases P1 through P3 shown in the figure below. Phase
P1 is performed once prior to the communication, and will not be repeated unless a communication error occurs. The communication is executed by cyclically repeating phases P2
and P3 for each definition combination of data and status.
ESC "T"

CR

LF

"F" "M"
"E" ERR CR
ERR:

Communication
module

Specify byte
sequence and
select output data

Execute trigger
(=<GET>)

"1"

","

","

nnn

nnn:
mmm:

LF

Error code
0: Normal
1: Abnormal

P1

T2

T3

T4

T5

T6

P2

Data length Year Month Date Hour Minute Second A1

LF

Measured data
(*1)

Reply
T1

CR

Specify measured
data output format
and output channel

DARWIN
Reply

mmm

Start channel (ASCII 3 bytes)

End channel (ASCII 3 bytes)

T7

T8

P3

B1

C1

D1

DATA1

....

An

Bn

Cn

A1 to An:
B1 to Bn:
C1 to Cn:
D1 to Dn:
DATA1 to DATAn:

Dn

DATAn

Base unit number

Channel number
Alarm status
Alarm status
Measured data
J051001E .EPS

Figure Time Chart for Communication between Communication Module and DARWIN
T1:
T2:
T3:
T4:
T5:
T6:
T7:
T8:

Transmission message creation time

Transmission message communication time
DARWIN processing time
Response message transmission time
Transmission message creation time
Transmission message communication time
DARWIN processing time
Measured data transmission time

*1:

DARWIN may return an error reply when the "output format and the our put channel designation" signal is not properly
received from ACM11 communication module.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J5.10 Transmission Time between Communication Module and DARWIN>

J5-30

Example of Calculating the Communication Time Reading 60 Data in One

Transmission Frame
Condition:

Baud rate:

19200 bps

Number of bits for one character:

11 bits

Number of characters for one datum:

6 characters

T1: Transmission message creation time = 10 ms

T2: Transmission message communication time
= 4 11 1000/192000 = 2.3 ms
T3: DARWIN processing time = 10 ms
T4: Response message transmission time
= 4 11 1000/19200 = 2.3 ms
T5: Transmission message creation time = 15 ms
T6: Transmission message communication time
= 13 11 1000/19200 = 7.5 ms
T7: DARWIN processing time = 100 ms
T8: Measured data transmission time
= 368(*1) 11 1000/19200 = 210.9 ms
*1:

The fixed part 8 characters + 60 data 6 characters = 368 characters

Transmission time

= P2 + P3
= T1 + T2 + T3 + T4 + T5 + T6 + T7 + T8
= 10 +2.3 + 10 + 2.3 + 15 + 7.5 + 100 + 210.9
= 358 ms

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6. Gas Chromatography Communication>

J6-1

J6. Gas Chromatography Communication

The gas chromatography communication package is used to communicate between
the ACM21 (RS-232C communication card) and the Yokogawa Electrics gas chromatography or analyzer bus server manufactured by Yokogawa. When the gas chromatography communication package is used, communication can be performed between the FCS and a gas chromatography without a customized program.
This chapter explains the communication between the gas chromatography and
FCS among the subsystem communication packages.
SEE ALSO
Regarding the functions common to different subsystem communication packages, see the following:
J1, General Information Regarding to Subsystem Communication

Available Models Gas Chromatography : SFCS

The following product is available for the gas chromatography communication package:
LFS2212 Gas Chromatography Communication Package (ACM21)
With the gas chromatography communication package, a gas chromatography is connected to the communication module (ACM21) and communication is performed between
the FCS and gas chromatography.
The following gas chromatography types and analyzer servers manufactured by Yokogawa
Electric can be connected to the ACM21:
GC1000D:

Process gas chromatography (hereinafter referred to as GC1000)

GC1000S:

Process gas chromatography (hereinafter referred to as GC1000)

GCAS:

Analyzer bus server (hereinafter referred to as AS)

GC8AA type:

Process gas chromatography (hereinafter referred to as GC8)

C8AB type:

Process gas chromatography (hereinafter referred to as GC8)

C8AF type:

Process gas chromatography (hereinafter referred to as GC8)

GC8AG type:

Process gas chromatography (hereinafter referred to as GC8)

GC8P type:

Processor (hereinafter referred to as GC8)

In this chapter, GC1000, AS, and GC8 will be referred to as gas chromatography.

Operation Environment Gas Chromatography : SFCS

To run the package for communicating with Gas Chromatograph, 450Kbyte need to be
assigned to User C option area of FCS.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.1 Communication Specifications Gas Chromatography>

J6-2

J6.1 Communication Specifications Gas

Chromatography
The section below explains the specifications when performing subsystem communication with a gas chromatography.

Capacity of Communication Gas Chromatography : SFCS

The capacity specific to gas chromatography when performing subsystem communication
with a gas chromatography are indicated below:
Table Capacity of Communication Between FCS and Gas Chromatography
Item
Amount of data that can be
communicated with one
communication module
Maximum number of
definitions

Maximum quantity
4000 words
(1 word=16 bits)

Explanation
Maximum amount of communication I/O.

208
J060101E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.1 Communication Specifications Gas Chromatography>

J6-3

Transmission Specifications Gas Chromatography : SFCS

Transmission specifications specific to the gas chromatography when performing subsystem communication with a gas chromatography are shown in the table below:
Table Transmission Specifications Gas Chromatography : SFCS
Item

Contents

Interface

RS-232C (D-sub 25 pin)

Transmission method

Half duplex

Synchronization method

Start-stop synchronization
method

Baud rate

1200, 2400, 4800, 9600 bps

Transmission procedure

Dedicated handshaking

Transmission code

ASCII

Data format

Text frame

Time monitoring

Remarks
ACM21

1200 only for GC8

1200 and 2400 only for GC1000
(*1)

Start bit

Character length

(*1)

Parity bit

Even number

(*1)

Stop bit

Reception start character None

EOT character

CRLF ($0D$0A)

Send ready monitoring

time

3000 ms

Reception character
interval monitoring time

1000 ms

RS control

No

(*1)

DR check

No

(*1)

CD check

No

(*1)

No response time setpoint (*2)

10 seconds or more [30 seconds] (*1)

Number of retries at communication error

(*3)

3 times or more [3 times]

Time interval for communication recovery

(*4)

4 seconds or more [10 seconds] (*1)

Item

Contents

(*1)

Remarks
J060102E.EPS

Note: [ ] indicates recommended setting.

*1:
This can be changed in the Property dialog box called from System View.
*2:
In the case of GC1000/AS, input command induction is sent from the gas chromatography at fixed intervals (about 8
seconds). In the no-response time setting value, set 10 seconds or more as the setpoint for monitoring the input
command induction. When the set value is less than 10 seconds, it will be fixed at 10 seconds. Also, in the case of
GC8, since the input command induction is performed at a non-fixed cycle, it will have no meaning even if a value is
set.
The no-response time for normal communication other than input command induction is fixed at 4 seconds; the value
set in the no-response time setting will be ignored. A communication error will be generated if a no-response that lasts
for 4  (number of retries + 1) seconds occur while data is being received. If there is no response for 4 seconds or
more with respect to a transmit command, an error will be returned to the SEBOL sswrite statement at the command
source.
*3:
Set a value of 3 or more for the number of retries in the case reception was unsuccessful or data outside the transmission method was received. If the value set is less than 3, it will be fixed at 3.
*4:
Set a value of 4 or more for the time interval for communication recovery. If the value set is less than 4, it will be fixed at
4.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.2 Connecting FCS and Gas Chromatography>

J6-4

J6.2 Connecting FCS and Gas Chromatography

This section explains the connection type and cable connections between FCS and
a gas chromatography.

Connection Type Gas Chromatography : SFCS

An example of connection between ACM21 RS-232C communication card and gas chromatography is shown below:
ACM21

Communication
converter
(K9404LD)

GC1000

ACM21

ACM21

GC8P

GCAS

GC1000

ACM21

GC8AA
/GC8AB

GC8AF/GC8AG
J060201E.EPS

Figure Example of Connection between ACM21 and Gas Chromatography : SFCS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.2 Connecting FCS and Gas Chromatography>

J6-5

Cable Connection Gas Chromatography : SFCS

The following explains the cable connection when connecting the ACM21 and a gas chromatography.
SD
RD
RS
CS
ACM21 DSR
CD
DTR
SG
FG

RD
SD

4
5
6

GC1000/AS

8
20
7

Sheathed cable

SG
FG

Protective ground (100 ohms or less)

J060202E.EPS

Figure Cable Connection between ACM21 and GC1000/AS : SFCS

SD
RD
RS
CS
ACM21 DSR
CD
DTR
SG
FG

SD
RD

5
6

GC8

8
20
7

SG
FG

Sheathed cable
Protective ground (100 ohms or less)
J060203E.EPS

Figure Cable Connection between ACM21 and GC8 : SFCS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J6-6

<J6.3 Reading Gas Chromatography Data>

J6.3 Reading Gas Chromatography Data

The following four types of data from the gas chromatography can be read.
Analysis value
Calibration factor
Alarm status (error alarm, end alarm, confirmation alarm)
Sampling time

List of Data that can be Read from Gas Chromatography : SFCS

Listed in the table below are the addresses, commands, sizes and data types that can be
used in reading data from the gas chromatography:
Table Addresses, Commands, Sizes and Data Types for Data to be Read : SFCS
Data

Address Command

DSaaatt

DS
8n (*1) ,
6n (*2)

Analysis value

Calibration factor

Size

D1aaatt

D1

D2aaatt

D2

CCaaatt

CC

4n

Data type

Contents

Remarks

F32

With the GC1000/AS, analysis value

for peak 1 to 99
With the GC8, analysis value
for components 1 to 24

F32

Analysis value for peak 100 to 199

GC1000/AS only

F32

Analysis value for peak 200 to 255

GC1000/AS only

F32

Calibration factor

Error alarm

AS

AS

I16

Error alarm

End alarm

AE

AE

I16

Ends the alarm generated

GC1000/AS only

Confirmation alarm AC

AC

I16

All error alarms that occurred during

each hour

GC1000/AS only

Sampling time

TS

I16

Data sampling time (*3)

AS only

TS

J060301E.EPS

*1:
*2:
*3:

This is the size when sampling time is specified for read data.
This is the size when no sampling time is specified for the GC1000/AS.
In the case of GC8, this is always set to 6n regardless of whether sampling time is specified.
This is the data sampling time of analysis values sent from GC1000. This is appended at the top of the analysis values
group (DS/D1/D2). Only valid for AS. Invalid when GC1000 is connected directly.

The aaa and tt in the address as well as the size n vary depending on each gas chromatography type, as shown below:
Table Range and Contents of Address and Size : SFCS
Address
DS

aaa

tt

Analyzer number 001 to 240 Task number 01 to 31

n
Peak count 1 to 99

Applicable gas
chromatography
GC1000/AS

Analyzer number 001 to 006 Stream number 01 to 15 Peak count 1 to 24

GC8

D1

Analyzer number 001 to 240 Task number 01 to 31

Peak count 1 to 100

GC1000/AS

D2

Analyzer number 001 to 240 Task number 01 to 31

Peak count 1 to 56

GC1000/AS

Analyzer number 001 to 240 Task number 01 to 09

Peak count 1 to 99

GC1000/AS

CC

Analyzer number 001 to 006

Standard sample number Component count

01 to 03
1 to 24

GC8
J060302E.EPS

When accessing with a SEBOL ssread statement, specify integer (16-bit signed integer
data) for the data type in the ssread statement regardless of the data type of the data to be
read from the gas chromatography.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.3 Reading Gas Chromatography Data>

J6-7

Reading Analysis Values: DS/D1/D2 : SFCS

Analysis values acquired via communication are stored as follows for each peak number
(component number).
%WWnn

Number of reception times (U16)

%WWnn+1

Alarm status (U16)

%WWnn+2

Analysis data (F32)

%WWnn+4

Retention time (F32)

%WWnn+6

Sampling time (U32)

J060303E.EPS

Figure Storage Status of Analysis Values : SFCS

Number of Reception Times : SFCS

This is the number of times data has been received from the gas chromatography. After the
number passes 32767, it returns to 1. The number is 0 if no data has been received.

Alarm Status : SFCS

This is the local variable used to read the alarm status. The alarm status read has the
following meaning:
16 15 14 13

Bit 1 to 13: Always 0

Bit 14=1:

Retention time error

Bit 15=1:

Concentration low-limit error alarm

Bit 16=1:

Concentration high-limit error alarm

J060304E.EPS

Figure Alarm Status of an Analysis Value : SFCS

Sampling Time : SFCS

This is the number of seconds until sampling time, using 00:00:00 on January 1st as the
starting point.

IMPORTANT
A leap year is not considered in the sampling time. Because February always counts data
until the 28th, distinction between February 29 and March 1 in a leap year cannot be made.
For sampling time in a leap year, handle this with the application that processes read data.

Do as follows when connecting a function block to read analysis values:

Analysis data/retention time
In analog input such as PVI, specify the %WW number.
Number of reception times/alarm status/sampling time
Specify the %WB number and the bit length in the CI bit input. The %WB number can
be specified directly for the alarm status.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.3 Reading Gas Chromatography Data>

J6-8

Reading the Calibration Factor: CC : SFCS

Calibration factors acquired via communication are stored for each peak number (component number) as shown below:
%WWnn

Number of reception times (U16)

%WWnn+1

Alarm status (U16)

%WWnn+2

Calibration factor (F32)

J060305E.EPS

Figure Storage Status of Calibration Factors : SFCS

The bit assignment for alarm status is as follows:

0x8000

Sensitivity error

When data from the gas chromatography has not arrived even once, all data will be read as
0.

Number of Reception Times : SFCS

This is the number of times data has been received from the gas chromatography. After the
number passes 32767, it returns to 1. The number is 0 if no data has been received.

Alarm Status : SFCS

This is the local variable used to read the alarm status. The alarm status read has the
following meaning:
16 15 14 13

Bit 1 to 15: Always 0

Bit 16=1: Sensitivity error
J060306E.EPS

Figure Alarm Status of the Calibration Factor : SFCS

Do as follows when connecting a function block to read analysis values:

Calibration factor
In analog input such as PVI, specify the %WW number.
Number of reception times/alarm status
Specify the %WB number and the bit length in the CI bit input. The %WB number can
be specified directly for the alarm status.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.3 Reading Gas Chromatography Data>

J6-9

Reading the Alarm Status: AS/AE/AC : SFCS

The alarm information obtained via communication is stored as follows.
%WWnn

Type of alarm occurred (char4)

%WWnn+2

Month (U16)

%WWnn+3

Day (U16)

%WWnn+4

Hour (U16)

%WWnn+5

Minute (U16)

%WWnn+6

Analyzer number (U16)

%WWnn

(Empty)
J060307E.EPS

Figure Storage Status of Alarm Status : SFCS

The following type of time will be stored depending on the address type:
AS: Time of occurrence
AE: Time of recovery from error
AC: Periodic notification time
The alarm status that can be read is the oldest of those that have not been read. The
second oldest alarm status can be read by writing into AR/ER/CR.
When alarms have not been newly generated, a space is entered as the type of alarm
occurred.
Use the SEBOL ssread statement to read the alarm status.
The following is an example of alarm status assignment in the area starting with
%WW0097:
Communication definition: %WW0097 AS 8
%WW0097
%WW0099
%WW0100
%WW0101
%WW0102
%WW0103
%WW0104

Type of alarm occurred (string of 4 characters)

Month of alarm occurrence
Day of alarm occurrence
Hour of alarm occurrence
Minute of alarm occurrence
Analyzer number
(Empty)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.3 Reading Gas Chromatography Data>

J6-10

Reading the Sampling Time: TS : SFCS

The sampling time for the most recent analysis result is stored as follows.
%WWnn

Month (U16)

%WWnn+1

Day (U16)

%WWnn+2

Hour (U16)

%WWnn+3

Minute (U16)

%WWnn+4

Second (U16)

%WWnn+5

Analyzer number (U16)

J060308E.EPS

Figure Storage Status of Sampling Time : SFCS

TIP
When 1 (sampling time read available) is specified for Option 2 in System View, the TS monitoring is not
necessary since the value for the sampling time is converted to seconds and added to each analysis
value.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.4 Writing Data to Gas Chromatography>

J6-11

J6.4 Writing Data to Gas Chromatography

Indicated below are the two types of data that can be written to a gas chromatography.
Commands for the gas chromatography
Results of command execution for the gas chromatography

List of Data that can be Written to Gas Chromatography : SFCS

The addresses at which data can be written in a gas chromatography differ for GC1000/AS
and GC8.
Listed in the table below are the addresses, sizes, commands and data types for data to be
written.
Table Address, Size, Command and Data Type of Data to be Written (Common to GC1000/GC8) :
SFCS
Data

Address

Size

Command

Data type

Contents written as a
command

Error alarm reset

AR

AR (*1)

DO

None (always 1)

End alarm reset

ER

ER (*1)

DO

None (always 1)

Confirmation alarm reset CR

CR (*1)

DO

None (always 1)
J060401E.EPS

*1:

When AR/ER/CR commands are executed, the alarm status of the ACM21 communication module read by the AS/AE/
AC commands will be reset. Communication with respect to the gas chromatography is not performed.

Table Address, Size, Command and Data Type of Data to be Written (GC1000/AS only) :
SFCS
Data

Address

Size

Command

Data type

Contents written as a
command

Primary pattern
switching

SEaaa

SE

DO

Pattern number

Interrupt pattern

CEaaa

CE

DO

Pattern number

Run (start)

BEaaa

BE

DO

Always 1

Stop

FEaaa

FE

DO

Always 1

Task switching

XEaaa

XE

DO

Pattern number, task number

Time setting

TEaaa

TE(*1)

DO

Year, month, day, hour, minute,

second
J060402E.EPS

*1:

Only valid for AS. Invalid when GC1000 is connected directly.

Table Address, Size, Command and Data Type of Data to be Written (GC8 only) : SFCS
Data

Address

Size

Command

Data type

Contents written as a
command

Stream switching

SM0a

SM

DO

Stream number

Calibration

CM0a

CM

DO

Standard sample number

Run (start)

BM0a

BM

DO

None (always 1)

Stop

FM0a

FM

DO

None (always 1)

DO

Stream number, component

number, component list number

Range switching

RM0a

RM

J060403E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.4 Writing Data to Gas Chromatography>

J6-12

Results of Command Execution : SFCS

When data write is executed with respect to a gas chromatography, the results of the
execution are stored in the specified address.
Table Addresses at Which Command Execution Results are Stored, Size and Data Type of
Execution Results : SFCS
Data

Address

Size

Data type

Contents

Result of primary pattern

RSEaaa
switch execution

U32

Normal:
0x8000 0000
Abnormal: 0x8000 ####
(#### stands for error code)

Result of stream switch

execution

RSMOa

U32

Normal:
0x8000 0000
Abnormal: 0x8000 ####
(#### stands for error code)

Result of interrupt
pattern execution

RCEaaa

U32

Normal:
0x8000 0000
Abnormal: 0x8000 ####
(#### stands for error code)

U32

Normal:
0x8000 0000
Abnormal: 0x8000 ####
(#### stands for error code)

Result of calibration
execution

RCM0a

Result of run (start)

execution

RBEaaa
RBM0a

U32

Normal:
0x8000 0000
Abnormal: 0x8000 ####
(#### stands for error code)

Result of stop execution

RFEaaa
RFM0a

U32

Normal:
0x8000 0000
Abnormal: 0x8000 ####
(#### stands for error code)

Result of range switch

execution

RRM0a

U32

Normal:
0x8000 0000
Abnormal: 0x8000 ####
(#### stands for error code)

Result of task switch

execution

RXEaaa

U32

Normal:
0x8000 0000
Abnormal: 0x8000 ####
(#### stands for error code)

Result of time setting

execution

RTEaaa

U32

Normal:
0x8000 0000
Abnormal: 0x8000 ####
(#### stands for error code)
J060404E.EPS

Table Address (Analyzer Number) Range and Contents : SFCS

Connection
destination
GC1000

AS

GC8

Analyzer
number

Contents

001 to 240

Analyzer number of the GC1000

001 to 240

Analyzer number of the GC1000 under AS control

241 to 254

AS analyzer number when time setting command (TE) given to AS

241 to 254

Specification number when a time setting command (TE) is given to

AS and all analyzers under AS control

01 to 06

Analyzer number for GC8

J060405E.EPS

For AR/ER/CR, there is no address for command execution results since the commands
are completed immediately and there is no chance of an abnormal termination.
SEE ALSO
For precautions regarding command transmission (data write) to the gas chromatography, see the
following:
J6.8, Precautionary Notes for Gas Chromatography Communication

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.4 Writing Data to Gas Chromatography>

J6-13

How to Execute Commands : SFCS

When the content of a command is other than 0, this indicates that some command is
already being executed. When executing a command, confirm that the content of each
command is 0 and then write data in the command.
When the command is completed, the command content becomes 0. At the same time,
0x8000 0000 representing normal response or 0x8000 #### (error code) representing error
response will be stored.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.5 Setting Items on System View Gas Chromatography>

J6-14

J6.5 Setting Items on System View Gas

Chromatography
Gas Chromatography

In this section, setting items on System View for Gas Chromatography, the specific
functionality and the recommended settings are explained.
SEE ALSO
For more information regarding to Set Details tab on Create New IOM dialog box and subsystem common settings, see the following:
Setting Items for ACM21, ACM22 in J1.5.1, Overview of Setting Items on System View

When using Gas Chromatography, the following items need to be set on Set Details
tab of Create New IOM dialog box called from System View:
Options
The following items can be set on the Set Details tab of the New IOM dialog box
called from System View:
Baud Rate
Parity
Data Bits
Stop Bits
RS Control
DR Check
CD Check
Communication Error Process
Options
Start of Text Delimiter
End of Text Delimiter
After creating the new I/O module, the settings can be modified on the I/O module
property sheet.

FCS Properties Gas Chromatography : SFCS

Add [GC1000] to Options on Constant tab of FCS property sheet,
This item is set on Constants tab in FCS property sheet, cannot be set on Set Details
tab in Create New IOM dialog box.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.5 Setting Items on System View Gas Chromatography>

J6-15

Baud Rate Gas Chromatography : SFCS

This sets the baud rate between the communication I/O module and gas chromatography.
Select 9600 bps or less for the baud rate.

IMPORTANT
With the gas chromatography, select 9600 bps or less for the baud rate. Since the default
setting is [19200 bps], so that this setting must be changed. With the gas chromatography,
communication cannot be performed at a baud rate of 19200 bps or higher.

Parity Gas Chromatography : SFCS

This sets the method for checking the parity of the subsystem data to be transmitted.
The recommended setting for the parity is [Even].

Data Bits Gas Chromatography : SFCS

This sets the data bit length of the subsystem data to be transmitted.
The recommended setting for the parity is [7 bits].
The default is [8 bits].

Stop Bits Gas Chromatography : SFCS

This sets the stop bit of the subsystem.
When using a gas chromatography, always set [1 bit] for the stop bit.

IMPORTANT
When using a gas chromatography, [2 bits] cannot be set for stop bit.

RS Control Gas Chromatography : SFCS

This sets whether or not RS control is performed during subsystem data transmission.
When connecting a gas chromatography, disable RS control by leaving the [RS control]
check box unchecked.

DR Check Gas Chromatography : SFCS

This sets whether or not DR check is performed during subsystem data transmission.
When connecting a gas chromatography, disable DR Check by leaving the [DR Check]
check box unchecked.
By default, the [DR check] checkbox is checked.
IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.5 Setting Items on System View Gas Chromatography>

J6-16

CD Check Gas Chromatography : SFCS

This sets whether or not CD check is performed during subsystem data transmission.
When connecting with a gas chromatography, disable the CD check function by leaving the
[CD Check] check box unchecked.

Communication Error Process Gas Chromatography : SFCS

This sets the parameters related to communication error handling during subsystem data
transmission.
The setting items include the following six:
Response Timeout
This sets the time limit for getting response from the Gas Chromatography. The time is
set in unit of seconds.
Recommended setting is [30]. When the value is 9 or less, it is treated as 10.
Default setting is 4.
Number of Retries Upon Response Timeout
This item sets the number of retries performed when a communication error occurs.
Recommended setting is [3]. When the value is 2 or less, it is treated as 3.
Default setting is 1.
Interval of Connection Retries
This sets the time interval of connection requests for checking whether the communication with the station that generated a communication error has returned to normal
(communication recovery) . The time is set in unit of seconds.
Recommended setting is [10]. When the value is 3 or less, it is treated as 4.
Default setting is 30.
Processing of inter-character time-out as an error
When check the mark for Processing of inter-character timeout as an error, the timeout between transmission of characters will be treated as an error.
Inter-character timer
The time interval between two characters of transmitted text may be specified in
milliseconds.
The recommended setting is 1000 ms.
Transmission enable monitoring time
The time for monitoring the interval between transmission request command and the
transmission start may be specified in milliseconds.
The recommended setting is 1000 ms.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.5 Setting Items on System View Gas Chromatography>

J6-17

Options Gas Chromatography : SFCS

Settings of communication parameter options vary depending on the equipment connected. Set options by clicking the [Option] button 2 and [Option] button 3 in the Set Details
tab of the New IOM dialog box called from System View.

Options 2
For a gas chromatography, set a value of 0 to 2 in option 2 to chose whether or not the
sampling time is to be added to the data read as an analysis value.
The setting range is 0 to 2.
The value set in option 2 is the 2-bit ON/OFF converted to a decimal. The content of each
bit is shown in the table below:
Table Content of Each Bit : SFCS
Bit 2
(Classification of communication counterpart)

Bit 1
(Reading sampling time necessary or not)

0 When communication counterpart is GC1000/AS

0 When sampling time is not necessary

1 When communication counterpart is GC8

1 When sampling time is necessary

J060501E.EPS

The meaning when each of the values 0 to 3 is set in option 2 is as follows:

0: Communication counterpart is GC1000 or AS. Sampling time is not necessary.
1: Communication counterpart is GC1000 or AS. Sampling time is necessary.(*1)
2: Communication counterpart is GC8. Sampling time is not necessary.
*1:

Sampling time is available only via an AS.

When the communication counterpart is GC8, the sampling time cannot be read since it is
not part of transmission. If 3 is set for option 2 by mistake, it is the same as when 2 is
set.

Options 3
The following time settings may be specified in Option 3.
#A Time interval between communication retries.
When the transmission request text #E is not received from Gas Chromatography device,
the transmission invitation text #A may be sent at this time interval.
The value should be 4 or greater. If the set value less than 4, the minimum time interval is
limited as 4.

Start of Text : SFCS

No need to set this item.
Please leave the default setting (0x00) intact.

End of Text : SFCS

It is required to set <CRLF> (0x0D0A) as the end of text.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.6 Setting Items on Communication I/O Builder Gas Chromatography>

J6-18

J6.6 Setting Items on Communication I/O Builder

Gas Chromatography
In this section, setting items on Communication I/O Builder for gas chromatography,
the specific functionality and the recommended settings are explained.
SEE ALSO
For an overview of the setting items on Communication I/O Builder, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

For gas chromatography, the setting items are as follows.

Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

Element Gas Chromatography : SFCS

Element

With respect to the address of the subsystem data buffer, the element numbers are displayed on Communication I/O Builder. The element number is only for display no need to
set.

Buffer Gas Chromatography : SFCS

Buffer

This sets the buffer for communicated data.

Must set the buffer since this is a required setting item of the Communication
I/O Builder.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.6 Setting Items on Communication I/O Builder Gas Chromatography>

J6-19

Program Name Gas Chromatography : SFCS

Program Name

Set the unit number, slot number and GC1000 program name as follows:
u-sProgramName
u:
s:
Program Name:

Unit Number
Slot Number
GC1000

Size Gas Chromatography : SFCS

Size

This item sets the data size (data length) from the head address set in Device & Address.
Must set the Size since this is a required setting item on Communication I/O Builder.
When using gas chromatography, the Size setting varies with Address settings. The setting
is in word units. Up to 208 settings are possible for each buffer.
SEE ALSO
For more information about Size setting item, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

Port Gas Chromatography : SFCS

Port

Port 1 is set for use.

IP Address Gas Chromatography : SFCS

IP Address

No need to set IP address.

Station Gas Chromatography : SFCS

Station

This sets the station number of the gas chromatography.

For a gas chromatography, always specify 1.
The default is no setting.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.6 Setting Items on Communication I/O Builder Gas Chromatography>

J6-20

Device & Address Gas Chromatography : SFCS

Device & Address

This sets the head address of gas chromatography data.

SEE ALSO
For details on address settings of Gas Chromatography Device, see the followings:
J6.3, Reading Gas Chromatography Data
J6.4, Writing Data to Gas Chromatography

Data Type Gas Chromatography : SFCS

Data Type

This sets data type of the subsystem data.

The data type can be selected from the following:
Input (16-Bit Signed)
Input (32-Bit Signed)
Input (16-Bit Unsigned)
Input (32-Bit Unsigned)
Input (32-Bit Floating)
Output (16-Bit Signed)
Output (32-Bit Signed)
Output (16-Bit Unsigned)
Output (32-Bit Unsigned)
Output (32-Bit Floating)
Input
Output

Reverse Gas Chromatography : SFCS

Reverse

This sets whether to make the bit or word arrangement in FCS in reverse order of the
subsystem data.
The following settings can be selected:
Bits
No
Words
However, when choosing [Bits], only the data of discrete inputs or discrete outputs can be
reversed. In this case, the default setting is [Bits].
Regarding to words, only the 32-bit analog inputs or 32-bit analog output can be reversed.
In this case the default setting is [No].

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.6 Setting Items on Communication I/O Builder Gas Chromatography>

J6-21

Scan Gas Chromatography : SFCS

Scan

Set whether to read the communication I/O analog data into the communication I/O data
buffer at the beginning of high-speed scan of the FCS.

Service Comment Gas Chromatography : SFCS

Service Comment

A comment text can be set.

Label Gas Chromatography : SFCS

Label

The name of the function block I/O terminal can be set as a user-defined label.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.7 System Alarm Messages Specific to Gas Chromatography>

J6-22

J6.7 System Alarm Messages Specific to Gas

Chromatography
This section explains the system alarm messages that are specific to gas chromatography.

System Alarm Message when a Communication Error Occurs Gas

Chromatography : SFCS
When there is a communication error, the system alarm message as shown below is sent
to HIS:
STNss SS-COM Error UNITmm SLOTnn STNzzz CODE=####
STNss: FCS name
mm:
Unit number
nn:
Slot number
zzz:
Subsystem station number
####: Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. After that, a new system alarm message
will not be sent even if an error is generated by a different cause.

SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs Gas Chromatography : SFCS

System Alarm Message when Communication Returns to Normal Gas

Chromatography : SFCS
When communication returns to the normal condition, the system alarm message indicated
below is sent to HIS:
STNss SS-COM Recover UNITmm SLOTnn STNzzz
STNss:
mm:
nn:
zzz:

FCS name
Unit number
Slot number
Subsystem station number

Data Status Gas Chromatography : SFCS

When a communication error is detected, the data status for all data that has been read will
be BAD. When the communication error is recovered, the status for all data changes to NR.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.7 System Alarm Messages Specific to Gas Chromatography>

J6-23

Error Codes when a Communication Error Occurs Gas Chromatography :

SFCS
Table Error Codes When a Communication Error Occurs Gas Chromatography : SFCS
Error Code
(Hexadecimal)

Description

A3B0

Communication timeout occurred (waiting for data)

A3B1

Communication timeout occurred (waiting for answer back)

A3B2

Communication timeout occurred (GC1000 no response check)

A3C0

Transmission command not executed (#W received)

A3C1

Transmission command content invalid (#W# received)

A3C2

Invalid command communication control procedure

A3C3

Inappropriate data status inappropriate received

A3D0

Invalid command address name

A3D1

Invalid command address name

A3D2

Invalid command analyzer number

A3D3

Insufficient command argument

A3D4

Too many command arguments

A3D5

Invalid command argument value

A3D6

Invalid GASCHRO type at command object (command not for GC8 received)

A3D7

Invalid GASCHRO type at command object (command not for CC1000 received)

A3E0

Invalid address name for data received

A3E1

Abnormal DS/D1/D2 data number (analyzer number, task number, peak number)

A3E2

Abnormal DS/D1/D2 data numeric value (concentration, calculation value)

A3E3

Abnormal DS/D1/D2 data identifier (PPM, %, T)

A3E4

DS/D1/D2 database error

A3E5

Abnormal data error status code (A:CHL, A:CLL, A:RT)

A3E9

Abnormal CC data number (analyzer number, task number, peak number)

A3EA

Abnormal CC data numeric value (calibration factor)

A3EC

CC database error

A3ED

Abnormal CC data error status code (COE)

A3F1

Abnormal AS/AC/AE data number (analyzer number)

A3F2

Abnormal AS/AC/AE data numeric value (time)

A3F3

Abnormal AS/AC/AE data classifier (/, :)

A3F4

AS/AC/AE database error

A3F6

Abnormal AS/AC/AE data range (time)

A3F9

Abnormal TS data number (analyzer number)

A3FA

Abnormal TS data numeric value (time)

A3FB

Abnormal TS data identifier (/, :)

A3FC

TS database error

A3FE

Abnormal TS data range (time)

Error code
(hexadecimal)

Description
J060701E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.8 Precautionary Notes for Gas Chromatography Communication>

J6-24

J6.8 Precautionary Notes for Gas Chromatography

Communication
This section describes the precautionary note when reading data from and sending
commands to a gas chromatography.

Reading Data : SFCS

When the data registered for monitoring has not been obtained on the gas chromatography
side, all of the data in that address will be read as 0 and the data status as NRDY.

Determining whether Data Has Been Updated : SFCS

Determine whether or not the data read via a DS, D1, D2 or CC command has been
updated, according to whether or not the number of reception times while data status is
normal has been updated to a non-0 value.

Reading and Writing Alarm Status : SFCS

Reading the alarm status using each of the AS/AE/AC commands is enabled when a
command is written into AR/ER/CR.
Only one new alarm status for AS/AE/AC can be read for a single command write into AR/
ER/CR.
The alarm status is read one line at a time by repeating a single command write to AR/ER/
CR before reading and a single read from AS/AE/AC after reading as a pair.
If no new alarms are generated other than those read the previous time, the analyzer
number and alarm occurrence time stay the same as the previous time, and an alarm
status with the alarm type cleared with a space will be read. To retain the alarm type immediately prior to the clear, save that value to a separate buffer.
Execute the command write to AR/ER/CR and alarm read using AS/AE/AC commands
following the write in the same operation and SFC block.

Differences in Determining a Disconnection between the GC1000/AS and

GC8 : SFCS
With the GC8, when a series of analysis data is completely received, there may occur a
time period in which no communication data is sent from GC8. Because it is hard to differentiate between this condition and a situation where data cannot be received due to a
disconnected communication cable, it is impossible to detect a communication error from a
communication cable disconnection. If disconnection of a communication cable needs to
be detected, monitor the time until the next analysis data is received from the application
program that uses the analysis data, based on the corresponding analysis time (30 to 3600
seconds).
With the GC1000/AS, input command induction is sent at preset time intervals even during
the time analysis data is not being sent, so a disconnected communication cable can be
detected as a communication timeout.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J6.8 Precautionary Notes for Gas Chromatography Communication>

J6-25

Time until Write Communication is Completed : SFCS

Because the write communication is performed only at the end of analysis in the gas
chromatography, it may require a long time to complete the write communication.

Effects After Sending a Stop Command to the Analyzer : SFCS

With the GC8, when a stop command is sent to the connected analyzer, the input command induction will no longer be sent, thereby no commands whatsoever can be sent from
ACM21 after this. In such a case, execute the start (run) operation on the GC8 side. Communication will recover by starting the GC8.

Differences in Detecting Errors between GC1000/AS and GC8 : SFCS

With the GC1000/AS, the data status changes to BAD when a communication error occurs.
The nature of the communication error can be confirmed based on the error code stored in
the error variable.
With the GC1000/AS, the data status returns to normal when a normal data or an input
command induction is received. Therefore, the communication error can be identified by
the data status.
With the GC8, the data status changes to BAD when a communication error occurs just like
in the GC1000/AS, but cable disconnection may not be detected in all cases and the data
status may not change to BAD. With the GC8, communication errors cannot be identified
based on the data status.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

Blank Page

<J7. YS Instrument Communication>

J7-1

J7. YS Instrument Communication

The YS communication package is a subsystem communication package designed
for Yokogawas YS100 SERIES/YS1000 SERIES/YEW SERIES 80/YEW SERIES BCS
series instruments (hereinafter referred to as YS instruments). By using the YS
communication package, communications can be performed between an FCS and a
YS instrument without using a program.
This chapter explains the communication between the YS instrument and FCS
among the subsystem communication packages.
SEE ALSO
For functions common to different subsystem communication packages, see the following:
J1, General Information Regarding to Subsystem Communication

Applicable Models YS Instrument

The following YS communication packages are available.
PFS2220 CS 1000 YS communication package (ACM12)
LFS2220 CS 3000 YS communication package (ACM12)
When using the YS communication package, the SCIU (communication interface unit) is
connected to a communication module (ACM12) and the YS instruments are connected to
the SCIU in order to perform subsystem communication between an FCS and a YS instrument.
The following YS instruments can be connected.
SBSD
SLBC
SLCC
SLCD
SLMC
SLPC
SMRT
SMST-111
SMST-121
STLD
YS135/YS1350
YS136/YS1360
YS150/YS1500
YS170/YS1700

IM 33S01B30-01E

15th Edition : Jun.27,2007-00

<J7.1 Communication Specifications YS Instrument>

J7-2

J7.1 Communication Specifications YS Instrument

This section explains the communication specifications when performing subsystem communications with a YS instrument.

Communication Capacity YS Instrument

The following shows the maximum number of units can be connected to ACM12.
Number of SCIU units that can be connected to one ACM12:

10 units

Number of YS instruments that can be connected to one SCIU:

4 units

Number of YS instruments that can be connected to one ACM12: 10 units

When one ACM12 is connected with 10 YS instruments, the time required for an input
signal on YS instrument to be reflected on YS block (Access Time), or a time required for an
setting a value from YS block to YS instrument (Transmission Time) are as follows.
PFCS/SFCS Access Time:

Average 2.5 sec.; Maximum 5 sec.

PFCS/SFCS Transmission Time:

Average 1.3 sec.; Maximum 2.5 sec.

LFCS (*1) Access Time:

Average 3.2 sec.; Maximum 6.5 sec.

LFCS (*1) Transmission Time:

Average 2 sec.; Maximum 4 sec.

*1:

Communication time when using LFCS.

Since the maximum communication time may take 6.5 sec. when one ACM12 is connected
with 10 YS instruments, it is recommended to connect ACM12 with the following number of
YS instruments.
Number of SCIU units to be connected to one ACM12:

1 unit

Number of YS instruments to be connected to one SCIU:

4 units

Number of YS instruments will be connected to one ACM12:

4 units

It may take an average of two seconds or a maximum of three seconds for input from the
YS instrument to be reflected in the YS block under the following conditions:
The ACM12 is attached to the SFCS and four YS instruments are connected via the
SCIU.
The [High Speed Read] checkbox is checked in the Type and Position tab of the
Create New IOM dialog of the ACM12.
SEE ALSO
For more information about communication time, see the following:
J7.7, Transmission Time for YS Instrument

IMPORTANT
After the communication module is started, it takes 70 seconds for the YS block to write to
the YS instrument.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.2 Connecting FCS and YS Instrument>

J7-3

J7.2 Connecting FCS and YS Instrument

The following explains the configuration of connections between an FCS and YS
instruments.

Connection Configuration YS Instrument

An example of connection between an FCS and YS instruments is shown below:

ACM12

RS-485
RS-485

SCIU

YS
instrument

YS
instrument

SCIU

YS
instrument

SCIU

SCIU

YS
instrument

J070201E.EPS

Figure YS Instruments Connection

Each YS instrument is connected to the SCIU, which is connected via RS-485 to the
ACM12 installed in the FCS.

IMPORTANT
When the YS instruments connected to SCIU are changed, it is necessary to switch the
SCIU OFF/ON once. Be cautious that after the power switch OFF/ON, communication to all
the YS instruments will fail.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.2 Connecting FCS and YS Instrument>

J7-4

Connecting SCIU to ACM12

The specification for connecting an SCIU and an ACM12 module is as follows:
Model of SCIU:

SCIU-100

Distance of Transmission:

Up to 1200 meters (dependent on Cable

Specification)

Connection:

4 wires (For SCIU connection, it is referred

to as Segregated Receive/Send connection)

Cable Specification:

M4 terminals on both ends. Shield connection at

one end.
AKB162 (Max. 100 meters)
CO-SPEV-SB (A)3Px0.5SQ of Hitachi Cable, Ltd.
(Max. 500 meters)

SEE ALSO
For more information about the settings in SCIU, see SCIU (Communication Interface Unit) Users
Manual.

The Wiring of the cable for SCIU and ACM12 connection is shown as follows:
ACM12
TX +
TX RX +
RX SG
FG

SCIU
2
1
4
3
7
8

SDB
SDA
RDB
RDA
SG
FG

J070202E.EPS

Figure Wiring for Connecting one SCIU to ACM12

ACM12
TX +
TX RX +
RX SG
FG

SCIU

SCIU

2 SDB

SDB

1 SDA

SDA

4 RDB

RDB

3 RDA

RDA

7 SG

SG

8 FG

FG

J070203E.EPS

Figure Wiring for Connecting Multiple SCIUs to ACM12

IM 33S01B30-01E

15th Edition : Jun.27,2007-00

<J7.2 Connecting FCS and YS Instrument>

J7-5

Termination and shielding can be set as follows:

A 120 ohm resistor can be used as terminator of ACM12
Put the CN5 jumper at J5 position for SCIU termination. If termination is not required
then put the jumper at J7 position.
SCIU does not have FG terminal for RS-485 connection, so that the shield can be
connected to the terminal number 8, which is assigned as the FG terminal. Do not
connect the shield to FG terminal on ACM12.
SEE ALSO
For more information about the settings in SCIU, see SCIU (Communication Interface Unit) Users
Manual.

IMPORTANT
When connecting YS100/YS1000 to SCIU, the DCS-LCS communication provided in
YS100/YS1000 can be used. YS100/YS1000 can not connect to RS-485 interface
directly.
When configuring communication devices, only the connected YS instruments should
be registered, if a non-exist instrument is registered, all the connected instruments
may not be communicated properly.

IM 33S01B30-01E

15th Edition : Jun.27,2007-00

<J7.3 Accessible Data YS Instrument>

J7-6

J7.3 Accessible Data YS Instrument

The accessible data of YS instument via communication are explained as follows.

Collected Data
YS communication performs communications with YS instruments via the SCIU, collecting
data from each instrument. There are two types of collection intervals: high-speed and lowspeed. The PVs and MVs, which fluctuate constantly, are collected at a high speed, while
the MHs and MLs, which normally do not fluctuate, are collected at a low speed.
The table below lists different types of YS instruments and data collected from each instrument at the high and low speeds.
Table Collected Data According to Different Types of YS Instruments
YS Instrument Type

High Speed

Low Speed

SLCD

LS, PV, SV, MV

MH, ML, P, I, D

SLPC, YS170/YS1700,
YS150/YS1500

LS, PV, SV, MV

AUX1, AUX2, AUX3, MH, ML, P, I, D, BS, CS

SLMC

LS, PV, SV, MV

AUX1, AUX2, AUX3, MH, ML, P, I, BS, CS

SMST-111, YS135/YS1350 LS, PV, SV

None

SMST-121, YS136/YS1360 LS, PV, MV

MH, ML

SMRT

LS, PV, SV, MV

CALC, DL, MH, ML, P1, P2, P3, P4, EB

SBSD

LS, PV, SV, MV

VL, SUM, PH, PL, CC1, CC2/CC4, CC3, BSET

SLCC

LS, PV, SV, MV

SUM, DV, CC1, CC2/CC4, CC3

SLBC

LS, PV, SV, MV

VL, SUM, PH, PL, CC1, CC2/CC4, CC3, BSET

STLD

LS, PV

SUM, CC1, CC2/CC4, CC3

J070301E.EPS

Multiplication of Low speed scan to high speed scan can be set on the ACM12 property
tab.
SEE ALSO
For more information about the data items on YS instruments that can be set, see the following:
D1.33, Control Operations of YS Blocks

IM 33S01B30-01E

15th Edition : Jun.27,2007-00

<J7.4 Setting Items on System View YS Instrument>

J7-7

J7.4 Setting Items on System View YS Instrument

YS

In this section, setting items on System View for YS instrument, the specific functionality and the recommended settings are explained.
SEE ALSO
For more information regarding to Set Details tab on Create New IOM dialog box and subsystem
common settings, see the following:
Setting Items for ACM11, ACM12 in J1.5.1, Overview of Setting Items on System View

For YS instrument, the setting items are as follows. This setting is performed on the
Set Details tab of the New IOM dialog box called from System View.
Connection Device
Baud Rate
Parity
Data Bits
Stop Bits
RS Control
DR Check
CD Check
Communication Error Process
Options
After creating the new I/O module, the settings can be modified on the I/O module
property sheet.

Connection Device YS Instrument

Set [YS] as the type of connection device (subsystem).
Must perform this setting since the default is [FA-M3].

Baud Rate YS Instrument

This item sets the baud rate for communication between the communication module and
YS instrument.
When using the YS Instrument, select [9600bps] for Baud rate.
Since the default setting is [19200 bps], so that this setting must be changed.

Parity YS Instrument
This item sets the parity check method used for subsystem data to be transmitted.
When using the YS Instrument, select [Even] for Parity.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.4 Setting Items on System View YS Instrument>

J7-8

Data Bits YS Instrument

This item sets the data bit length of subsystem data to be transmitted.
For YS instrument, be sure to select [7 bits] for the bit length.
Since the default setting is [8 bits], so that this setting must be changed.

Stop Bits YS Instrument

This item sets the stop bit for subsystem data to be transmitted.
When using the YS Instrument, select [1] for Stop bits.

RS Control YS Instrument
This item sets whether or not to perform RS control during subsystem data transmission.
When using the YS instrument, disable [RS Control] by leaving the [RS Control] checkbox
unchecked.

DR Check YS Instrument
This item sets whether or not to perform DR check during subsystem data transmission.
When using the YS instrument, enable [DR Check] by placing a check in the [DR Check]
checkbox.

CD Check YS Instrument
This item sets whether or not to perform CD check during subsystem data transmission.
When using the YS instrument, disable [CD Check] by leaving the [CD Check] checkbox
unchecked.

Communication Error Process YS Instrument

This sets the parameters related to communication error process during subsystem data
transmission.
The following three items must be set.
Response Timeout
This item sets the time limit for getting response from YS instrument. The time is set in
unit of seconds.
Recommended setting is [1]. The default setting is [4].
Number of Retries Upon Response Timeout
This item sets the number of retries performed when a communication error occurs.
Recommended setting is [1].
Interval of Connection Retries
This sets the time interval of connection requests for checking whether the communication with the station that generated a communication error has returned to normal
(communication recovery). The time is set in unit of seconds.
Recommended setting is [30].

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.4 Setting Items on System View YS Instrument>

J7-9

IMPORTANT
When communication error occurs, communication reestablishment is carried out to every
abnormal YS instruments a certain interval. If multiple YS instruments become abnormal,
besides the specified communication cycle, an additional time period, i.e. [Response
Timeout] x [Number of Abnormal YS instruments] is required.
For this reason, to set a value to a YS instrument may not be updated within 5 seconds. In
this case, the setting value of the YS block may be reverted.

Options YS Instrument
The option settings for the communication parameters of each connection device are
specified in options 1 through 4 of the Set Details tab of the Create New IOM dialog box
called from System View.
When using the YS instrument, set the WDT (Watchdog Timer) time, and low speed update
communication interval magnification in options 2 through 4. Set 0 for option 1.
There are no default settings. Nevertheless, zero will be displayed as settings.

Option 2
This item specifies the WDT time setting.
The WDT time setting is the time interval (in seconds) of WDT communications triggered
from the ACM12 to the SCIU.
If 0 is set, the time interval will be 10 seconds, the setting range is 0 to 9999.

Option 4
This item specifies the low speed update communication interval magnification.
The interval magnification of low-speed update communication refers to a multiple of the
high-speed update interval at which interval data is updated at a low speed by a YS instrument.
If 0 is set, the magnification will be a factor of eight, the setting range is 0 to 20.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.5 Setting Items on Communication I/O Builder YS Instrument>

J7-10

J7.5 Setting Items on Communication I/O Builder

YS Instrument
In this section, setting items on Communication I/O Builder for YS instrument, the
specific functionality and the recommended settings are explained.
SEE ALSO
For an overview of the setting items on Communication I/O Builder, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

For YS instrument, the setting items are as follows.

Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

Element YS Instrument
Element

With addresses of the subsystem data buffer, the element numbers are displayed on
Communication I/O Builder. The element numbers are for display only, cannot be set.

Buffer YS Instrument
Buffer

This sets the buffer for communication data.

Must set the buffer size since this is a required setting item of the Communication I/O
Builder.

Program Name YS Instrument : PFCS/SFCS

Program Name

Set the unit number, slot number and YS program name as follows:
u-sProgramName
u:
s:
ProgramName:

Unit number
Slot number
YS
IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.5 Setting Items on Communication I/O Builder YS Instrument>

J7-11

Program Name YS Instrument : LFCS2/LFCS

Program Name

Set the node number, unit number, slot number and YS as Program Name as follows:
n-u-sProgramName
n:
u:
s:
ProgramName:

Node number
Unit number
Slot number
YS

Device & Address, Size, Data Type YS Instrument

Device & Address, Size, Data Type

The types of YS instruments to be connected to the SCIU are specified in Device & Address. Two types of addresses are specified: one for data input and the other for data
output.
A data-input address has 1 at the end of the address, while a data-output address has 2
at the end. Always define one set of data input and output addresses at a time.
The data size and data type to be set are determined by the device address.
The table below lists the setting items for different types of YS instruments:
Table Device & Address, Size, Data Type
YS Instrument Type

Device & Address

Size

Data type

SLCD1

16

AIU16

SLCD2

32

AOU16

SLPC, YS170/YS1700, SLPC1

YS150/YS1500
SLPC2

16

AIU16

32

AOU16

SLMC1

16

AIU16

SLMC2

32

AOU16

SMST-111,
YS135/YS1350

SMST11

16

AIU16

SMST12

32

AOU16

SMST-121,
YS136/YS1360

SMST21

16

AIU16

SMST22

32

AOU16

SMRT1

16

AIU16

SMRT2

32

AOU16

SBSD1 (*1)

16

AIU16

SBSD2 (*1)

32

AOU16

SLCC1 (*2)

16

AIU16

SLCC2 (*2)

32

AOU16

SLBC1 (*3)

16

AIU16

SLBC2 (*3)

32

AOU16

STLD1 (*4)

16

AIU16

STLD2 (*4)

32

AOU16

SLCD

SLMC

SMRT

SBSD

SLCC

SLBC

STLD

Function Block for Connection

SLCD

SLPC

SLMC

SMST-111

SMST-121

SMRT

SBSD

SLCC

SLBC

STLD
J070501E.EPS

AIU16:
AOU16:
*1:
*2:
*3:
*4:

Input (16-Bit unsigned)

Output (16-Bit unsigned)
When use CC4 YS instruments to replace CC2, use SBSD3 for SBSD1 and SBSD4 for SBSD2.
When use CC4 YS instruments to replace CC2, use SLCC3 for SLCC1 and SLCC4 for SLCC2.
When use CC4 YS instruments to replace CC2, use SLBC3 for SLBC1 and SLBC4 for SLBC2.
When use CC4 YS instruments to replace CC2, use STLD3 for STLD1 and STLD4 for STLD2.

IM 33S01B30-01E

15th Edition : Jun.27,2007-00

<J7.5 Setting Items on Communication I/O Builder YS Instrument>

J7-12

SEE ALSO
For more information about Size setting item, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

Port YS Instrument
Port

Port 1 is set for use.

IP Address YS Instrument
IP Address

The IP Address is not required to be set.

Station YS Instrument
Station

Set the destination SCIU number and YS instrument channel number using a 3-digit integral number.
SSC
SS:
C:

SCIU number (00 to 15)

Channel number (1 to 4)

This setting is made using the Communication I/O Builder.

Reverse YS Instrument
Reverse

This item sets whether or not to reverse the bit or word arrangement in the FCS and the bit
arrangement of subsystem data on the Communication I/O Builder.
Choose [No] for this setting.
The default setting is [No].

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.5 Setting Items on Communication I/O Builder YS Instrument>

J7-13

Scan YS Instrument
Scan

Set whether to read the communication I/O analog data into the communication I/O data
buffer at the beginning of high-speed scan of the FCS.

Service Comment YS Instrument

Service Comment

This item sets the comment.

Label YS Instrument
Label

The name of the function block I/O terminal can be set as a user-defined label.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.5 Setting Items on Communication I/O Builder YS Instrument>

J7-14

Example of Assignment and Settings

The following shows examples of settings when connections are made as shown below.

ACM12

SCIU
SCIU number
0

Channel number

SLCD

SLCD

SLPC

J070503E.EPS

Figure Connection Example of YS Instruments

Set the types and addresses of YS instruments to be connected on the Communication I/O
Builder as shown below.
Table Settings in Communication I/O Builder
Element

Buffer

Program
Name

%WW0001

144

1-2 YS

16

001

SLCD1

AIU16

%WW0017

32

001

SLCD2

AOU16

%WW0049

16

002

SLCD1

AIU16

%WW0065

32

002

SLCD2

AOU16

%WW0097

16

003

SLPC1

AIU16

%WW0113

32

003

SLPC2

AOU16

Size

Station

Device & Address

Data Type

J070504E.EPS

AIU16:
AOU16:
Note:

Input (16-Bit Unsigned)

Output (16-Bit Unsigned)
Reverse Data and Fast-Scan are set as follows:
Port:
[1]
Reverse:
[No]
Scan:
[Normal]

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.5 Setting Items on Communication I/O Builder YS Instrument>

J7-15

Link the element number to the IN terminal of each function block of the YS instrument
(hereinafter referred to as the YS block) on the Control Drawing Builder.
SLCD01

SLCD02

SLPC01

SLCD

SLCD

SLPC

IN

IN

IN

%WW0001

%WW0049

%WW0097
J070505E.EPS

Figure Connecting Function Blocks

If an error occurs during SCIU communication, a system alarm message will be generated
and the data status of the connected YS block will become IOP.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.6 System Alarm Messages Specific to YS Instruments>

J7-16

J7.6 System Alarm Messages Specific to YS

Instruments
The system alarm messages specific to YS Instruments will be explained in this
chapter.

System Alarm Message when Communication is Abnormal- YS Instrument : PFCS/SFCS

When the communication becomes abnormal, the system alarm message shown below
will be sent to HIS.
STNss SS-COM Error UNITmm SLOTnn STNzzz CODE=####
STNss
mm
nn
zzz
####

:
:
:
:
:

FCS name
Unit number
Slot number
Subsystem station number
Error code

The communication error message will be sent to HIS at the first time that the subsystem
communication becomes abnormal. No further system alarm message will be sent to HIS
even when a different error occurs, unless the communication recovers from the first
occurred error.
SEE ALSO
For more information about error codes, see the following in this chapter:
Communication Error Codes YS Instrument

System Alarm Message when Communication is Abnormal YS Instrument : LFCS2/LFCS

When the communication becomes abnormal, the system alarm message shown below
will be sent to HIS.
STNss SS-COM Error RIO01 NODExx UNITmm SLOTnn STNzzz CODE=####
STNss
xx
mm
nn
zzz
####

:
:
:
:
:
:

FCS name
Node number
Unit number
Slot number
Subsystem station number
Error code

The communication error message will be sent to HIS at the first time that the subsystem
communication becomes abnormal. No further system alarm message will be sent to HIS
even when a different error occurs, unless the communication recovers from the first
occurred error.
SEE ALSO
For more information about error codes, see the following in this chapter:
Communication Error Codes YS Instrument

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.6 System Alarm Messages Specific to YS Instruments>

J7-17

System Alarm Message when Communication Recovers from Abnormality YS Instrument : PFCS/SFCS
When the communication recovers from the abnormality, a system alarm message shown
below will be sent to HIS.
STNss SS-COM Recover UNITmm SLOTnn STNzzz CODE=####
STNss
mm
nn
zzz

:
:
:
:

FCS name
Unit number
Slot number
Subsystem station number

System Alarm Message when Communication Recovers from Abnormality YS Instrument : LFCS2/LFCS
When the communication recovers from the abnormality, a system alarm message shown
below will be sent to HIS.
STNss SS-COM Recover RIO01 NODExx UNITmm SLOTnn STNzzz CODE=####
STNss
xx
mm
nn
zzz

:
:
:
:
:

FCS name
Node number
Unit number
Slot number
Subsystem station number

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.6 System Alarm Messages Specific to YS Instruments>

J7-18

Communication Error Codes YS Instrument

Table Communication Error Codes YS Instrument
Error Code
(Hex)

Description

A391

Communication driver busy

A392

Communucation line busy

A393

Communuication line not ready

A394

Size for transmission too large

A395

Communication port is not declared for use

A397

Underline error

A398

Timeout between received characters

A399

Buffer for receiving overflow

A39A

Parity error in received data

A39B

Data receiving overrun

A39C

Framing error in received data

A39D

Unexpected character in received data

A39F

Other errors

A3B0

No response

A3B1

Station number out of range

SCIU station number or YS channel number is out of range;
or station numbers for address1 and address2 are different.

A3B3

Address out of range

Unexpected address is set

A3B5

Inappropriate size
Designated size is out of range

A3B6

Inappropriate type
Unexpected type is designated

A3B7

Non-continuous addresses
I/O adresses of the same device are not continuous

A3B8

Identical station numbers

Identical SCIU numbers or YS channel numbers exist.

A3C1

Unexpected SCIU number

A3C5

Inappropriate number of data

A3C6

Unexpected YS channel number

A3C7

Protocol error

A3C8

Data conversion error

A3C9

Inappropriate size of text

A3FE

Timeout for sending

A3FF

Other errors

Error Code
(Hex)

Description

Countermeasures

The items inappropriately configured

will not communicate.

Error occurs when receiving data

from SCIU.

Countermeasures
J070601E.EPS

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.7 Transmission Time for YS Instrument>

J7-19

J7.7 Transmission Time for YS Instrument

This section explains the transmission time for communication between an FCS and
a YS instrument.

Transmission Time YS Instrument

The figure below shows the time required for an input data from the YS instrument to be
reflected in the YS block.
YS
instrument

T1:
T2:
T3:
T4:

T1

SCIU

T2

ACM12

T3

FCS
input data

T4

YS block

Transmission time for communication between the YS instrument and SCIU

Transmission time for communication between the SCIU and the ACM12
Time required for data to be read from the ACM12 to the FCS as an input data
Time required for the FCS input data to be reflected in the YS block
J070701E.EPS

Figure Route from the YS Instrument to the YS Block

Transmission Time for Communication between YS Instrument and SCIU

Updated at a cycle time of 480 ms, regardless with number of YS instruments connected.

Transmission Time for Communication between SCIU and ACM12

The table below lists the times required to update data at high speed for each YS instrument.
Table Transmission Time for Communication between SCIU and ACM12
Content

Time (ms)

Send/receive text transfer time

71

SCIU return processing

100

Other

25
Total

196
J070702E.EPS

Time Required for Data to be Read from the ACM12 to the FCS as an Input
Data
With the LFCS (*1), it could take approximately 288 ms per YS instrument if the [High
Speed Read] checkbox in the property sheet of the ACM12 is checked.
With the SFCS (*1)/PFCS, it could take approximately 130 ms per YS instrument if the
[High Speed Read] checkbox in the property sheet of the ACM12 is checked.
*1:

LFCS and SFCS is a station for CS 3000.

Time Required for the FCS Input Data to be Reflected in the YS Block
The FCS input data is reflected in the YS block during the scanning period.

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J7.7 Transmission Time for YS Instrument>

J7-20

Example of Transmission Time Calculation

The table below lists the approximate times required from when the YS instrument value
changes until the data is reflected in the YS block, when the ACM12 installed and four YS
instruments are connected. The times differ between the PFCS/SFCS and LFCS.
Table Communication Time for the PFCS/SFCS
Max (ms)

Average (ms)

YS instrument to SCIU

480

240

SCIU to ACM12

784

392

ACM12 to FCS input data

520

260

1304

FCS input data to YS block

1000

500

1 second scan

2784

1392

Route

Total

Remarks

1964

J070703E.EPS

When only one YS instrument is connected, the maximum communication time =

480+196+130+1000 = 1806 (ms) and the average communication time = 903 (ms).
Table Communication Time for the LFCS
Route
YS instrument to SCIU
SCIU to ACM12

Max (ms)

Average (ms)

480

240

Remarks

784

392

1964

ACM12 to FCS input data

1152

576

2884

FCS input data to YS block

1000

500

1 second scan

3416

1708

Total

J070704E.EPS

When only one YS instrument is connected, the maximum communication time =

480+196+288+1000 = 1964 (ms) and the average communication time = 982 (ms).

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

<J7.7 Transmission Time for YS Instrument>

J7-21

The table below lists the approximate communication times required from when a value is
written to the MV of the YS block until the data is reflected in the YS instrument.
Table Communication Time for the PFCS/SFCS
Max (ms)

Average (ms)

Comment

YS block to FCS output data

200

100

When the high speed scan period is

200 ms

FCS output data to ACM12

520

260

1304

ACM12 to SCIU

196

98

SCIU to YS instrument

480

240

1396

698

Route

Total

Perform during read communication

J070705E.EPS

Table Communication Time for the LFCS

Route

Max (ms)

Average (ms)

Comment

200

100

When the high speed scan period is

200 ms

1152

576

2884

ACM12 to SCIU

196

98

SCIU to YS instrument

480

240

2028

1014

YS block to FCS output data

FCS output data to ACM12

Total

Perform during read communication

J070706E.EPS

The time for transmitting from FCS to ACM12 or vice versa, from ACM12 to FCS for reading the accessed data can be considered the same.

IM 33S01B30-01E

10th Edition : Dec.18,2003-00

Blank Page

<J8. MELSEC-A Communication (ACM11, ACM12)>

J8-1

J8. MELSEC-A Communication

(ACM11, ACM12)
The MELSEC-A communication package (ACM11, ACM12) is a subsystem communication package designed for the Mitsubishi Electric general-purpose PC MELSEC-A
(below referred to as MELSEC-A). By using the MELSEC-A communication package
(ACM11, ACM12), communication between the FCS and MELSEC-A can be performed without a customized program.
This chapter explains the communication between the MELSEC-A and FCS among
the subsystem communication packages.
TIP
Of the computer link units that can be connected to the ACM11 or ACM12, this section uses the example
of AJ71C24 type computer link unit to explain the functions. Any differences from the AJ71C24 type
computer link unit are explained as they come up.

SEE ALSO
Regarding the functions common to different subsystem communication packages, see the following:
J1, General Information Regarding to Subsystem Communication

Applicable Models MELSEC-A

For the MELSEC-A communication package (ACM11, ACM12), the following product is
available:
PFS9062 CS 1000 MELSEC-A communication package (ACM11, ACM12)
LFS 9062 CS 3000 MELSEC-A communication package (ACM11, ACM12)
With the MELSEC-A communication package (ACM11, ACM12), subsystem communication between the FCS and MELSEC-A is performed by connecting the MELSEC-A computer link unit and the communication module (ACM11 or ACM12).
The 13 models of the MELSEC-A computer link units that can be connected to the ACM11
or ACM12 are listed below. The three models AJ71C24-S8, AJ71C24-S6 and AJ71C24-S3
are generally referred to as the AJ71C24 type computer link units.
AJ71C24-S8
AJ71C24-S6
AJ71C24-S3
AJ71UC24
A1SJ71C24-R2
A1SJ71UC24-R2
A1SJ71C24-PRF
A1SJ71UC24-PRF
A1SJ71C24-R4
IM 33S01B30-01E

12th Edition : Mar.31,2005-00

J8-2

<J8. MELSEC-A Communication (ACM11, ACM12)>

A1SJ71UC24-R4
A1SCPUC24-R2
A2CCPUC24
A2CCPUC24-PRF
The communication modules that can be used in conjunction with the MELSEC-A
computer link unit vary with the model of the computer link unit.
Table Connection Availability between MELSEC-A Computer Link Units and Communication
Modules
Computer link unit

ACM11 (RS-232C)

ACM12 (RS-422/RS-485)

AJ71C24-S8
AJ71C24-S6
AJ71C24-S3

Can be connected
(Use a D-sub 25 pin connector)

Only the RS-422 can be connected

AJ71UC24

Can be connected
(Use a D-sub 25 pin connector)

Can be connected

A1SJ71C24-R2
A1SJ71UC24-R2
A1SJ71C24-PRF
A1SJ71UC24-PRF

Only 1:1 connections are possible

(Use a D-sub 9 pin connector)

A1SJ71C24-R4
A1SJ71UC24-R4

Cannot be connected

A1SCPUC24-R2

Only 1:1 connections are possible

(Use a D-sub 9 pin connector)

A2CCPUC24
A2CCPUC24-PRF

Can be connected
(Use a D-sub 9 pin connector)

Cannot be connected

Can be connected
Cannot be connected
Can be connected
J080001E.EPS

If the MELSEC-A CPU supports the above-mentioned MELSEC-A computer link units, it
will support the communication with FCS.

IM 33S01B30-01E

13th Edition : Dec.26,2005-00

J8-3

<J8.1 Communication Specifications MELSEC-A>

J8.1 Communication Specifications MELSEC-A

The section below explains the specifications when performing subsystem communication with the MELSEC-A.

Communication Capacity MELSEC-A

The capacity specific to MELSEC-A when performing subsystem communication with the
MELSEC-A are indicated below:
Table Capacity of Communications between FCS and MELSEC-A
Item

Maximum quantity

Explanation

Amount of data that can be communicated with

one communication module

500 words
(1 word=16 bits)

Maximum amount that can be

accessed from the regulatory control
block/sequence control block.

Number of subsystem stations that can be

communicated with one communication module

30 stations

Data size in one communication frame

Word Device: 64 words One frame is defined in one line on

Bit Device: 32 words the builder. It is the same as
(512 bits) restricted by MELSEC-A protocol.
J080101E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J8-4

<J8.1 Communication Specifications MELSEC-A>

Transmission Specifications MELSEC-A

The transmission specifications when performing subsystem communication with the
MELSEC-A are indicated below:
Table Transmission Specifications MELSEC-A
Item
Interface

Description
RS-232C (D-sub 25 pin)

ACM11

RS-422, RS-485

ACM12

Transmission method

Half duplex

Synchronization method

Start-stop synchronization

Baud rate

1200, 2400, 4800, 9600,

[19200] bps

Transmission procedure

MELSEC-A dedicated control

procedure type 4

Transmission code

Data type

Time monitoring

Text frame

Remark

(*1)

ASCII

Start bit

Data bit

[7], 8

(*1)

Parity bit

None, [even], odd

(*1)

Stop bit

Transmission enable
monitoring time

1000ms

Reception character
interval monitoring time

1500ms

Reception start character

$00 (NUL)

EOT character (0)

$0D (CR)

EOT character (1)

$0A (LF)

RS control

Yes, [No]

DR check

[Yes], No

CD check

Yes, [No]

No response time setpoint

0 to 99 seconds [4 seconds]

(*1)

Number of communication retries upon error 0 to 99 times [1 time]

(*1)

Recovery communication time interval

(*1)

0 to 999 seconds [30 seconds]

Transmission wait time

1 second

Number of words that can be handled in

one communication packet

Word device: 64 words

Bit device: 32 words
J080102E.EPS

Note: [ ] indicates the recommended settings.

*1:
This can be changed using the property dialog box called from System View.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.1 Communication Specifications MELSEC-A>

J8-5

Simultaneity of Communication Data MELSEC-A

The MELSEC-A guarantees the simultaneity of communication data in 16 bit units. Therefore, simultaneity of data in 16 bit units is guaranteed between the communication module
and the MELSEC-A.
TIP
The MELSEC-A processes data in 16 bit units. Simultaneity of data in 32 bit units depends on the
application software for the MELSEC-A. It is necessary to set 32-bit data within the same control cycle
using the MELSEC-A application software to guarantee simultaneity of communication data in 32 bit
units.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.2 Connecting FCS and MELSEC-A>

J8-6

J8.2 Connecting FCS and MELSEC-A

The following section explains the connection type and cable connections between
FCS and MELSEC-A.

Connection Type MELSEC-A

An example of the connection between FCS and MELSEC-A is shown below:
HIS

Control bus

FCS

ACM11 (RS-232C communication module)

RDY
RCV
SND

CN1

RDY
RCV
SND

AMN33 (Nest for communication module)

CN1

RS-232C
MODEM

MODEM

RS-232C

MELSEC-A

CPU unit
AJ71C24 type
computer link unit

AJ71C24 type
computer link unit

MELSEC-A

CPU unit

AJ71C24 type
computer link unit
MELSEC-A

CPU unit

RS-422

RS-422
J080201E.EPS

Figure Connection Example between FCS and MELSEC-A

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.2 Connecting FCS and MELSEC-A>

J8-7

Cable Connection when Using the ACM11 MELSEC-A

The cable connection when connecting the ACM11 and MELSEC-A is indicated below:
The connector shape varies according to the computer link unit of the connected MELSEC-A.
A modem connection is required between the ACM11 and MELSEC-A, but if the length of
the RS-232C cable between the ACM11 and MELSEC-A is 15 meters or less and if they
share the same grounding system, then it is possible to connect them directly.

IMPORTANT
The length of the RS-232C cable between the ACM11 and modem and between the modem and MELSEC-A must be 15 meters or less.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.2 Connecting FCS and MELSEC-A>

J8-8

Connection to AJ71C24, AJ71UC24

Since the AJ71C24 and AJ71UC24 use an RS-232C D-sub 25 pin connector, use a cable
with an RS-232C D-sub 25 pin connector when connecting these computer link units to the
ACM11.
Table RS-232C D-sub 25 Pin Connector Specifications MELSEC-A
Title

Direction of signal

Pin number

Signal name

FG

Frame ground

SD

Send data

RD

Receive data

RS

Request to send

When there is a send request, ON is output

CS

Clear to send

When OFF, the ACM11 does not transmit to

the outside

DR

Data ready

Detects whether sending and receiving with

correspondent are allowed

SG

Signal ground

CD

Carrier Detected

20

ER

Data Terminal Ready

ACM11

MELSEC-A

Description
Security grounding

When sending and receiving are allowed,

ON is output
J080202E.EPS

SEE ALSO
For details on safety grounding, see the followings:
Figure Cable Connection between ACM11 and Modem
Figure Cable Connection Between MELSEC-A and ACM11 (when MELSEC-A uses an RS-232C D-sub
25 pin connector, and directly connected)

Pin No. 25

Pin No. 14

Pin No. 13

Pin No. 1
J080203E.EPS

Figure Pin Assignment of the RS-232C D-sub 25 Pin Connector MELSEC-A

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.2 Connecting FCS and MELSEC-A>

J8-9

The following shows when the MELSEC-A and ACM11 are connected via modems and
when they are connected directly without modem:
SD
RD
RS
CS
ACM11

DR
SG
CD

20

ER

FG

Sheathed cable

20
1

SD
RD
RS
CS
DR

Modem (*1)

SG
CD
ER
FG

Protective grounding (100 ohms or less)

J080204E.EPS

*1:

As a rule, use a modem where FG and SG are connected.

Figure Cable Connection between ACM11 and Modem

SD
RD
RS
CS
ACM11

CD
DR

20

ER
SG
FG

20

Sheathed cable

SD
RD
RS
CS
CD

AJ71C24
AJ71UC24

DR
ER
SG
FG

Protective grounding (100 ohms or less)

J080205E.EPS

Figure Cable Connection between MELSEC-A and ACM11

(when MELSEC-A uses an RS-232C D-sub 25 pin connector, and directly connected)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.2 Connecting FCS and MELSEC-A>

J8-10

Connection to A1SJ71C24-R2, A1SJ71UC24-R2, A1SJ71C24-PRF,

A1SJ71UC24-PRF, A1SCPUC24-R2, A2CCPUC24 and A2CCPUC24-PRF
The A1SJ71C24-R2, A1SJ71UC24-R2, A1SJ71C24-PRF, A1SJ71UC24-PRF, A1SCPUC24R2, A2CCPUC24 and A2CCPUC24-PRF use an RS-232C D-sub 9 pin connector. Therefore, when connecting these computer link units and the ACM11, it is necessary to use a
cable that has both an RS-232C D-sub 9 pin connector and an RS-232C D-sub 25 pin
connector.
Table Specifications for the RS-232C D-sub 9 Pin Connector MELSEC-A
Signal direction

Pin number

Signal
number

CD

Carrier Detected

RD

Receive data

SD

Send data

ER

Data Terminal Ready

SG

Signal ground

DR

Data ready

Detects whether correspondent can send

and receive

RS

Request to send

ON is output when there is a request to send

CS

Clear to Send

ON is input when the RS is ON

Title

ACM11

Description

MELSEC-A

ON is output when sending and receiving

are allowed

Not used
J080206E.EPS

9
6

1
D-sub 9 pin (female)
J080207E.EPS

Figure Pin Assignment of the RS-232C D-sub 9 Pin Connector MELSEC-A

SD
RD
RS
ACM11

CS
CD
DR
ER
SG

20

SD
RD
RS
CS
CD
DR

A1SJ71C24-R2
A1SJ71C24-PRF
A1SJ71UC24-R2
A1SJ71UC24-PRF
A1SCPUC24-R2
A2CCPUC24
A2CCPUC24-PRF

ER
SG
Connector shell connection

Sheathed cable

Protective ground (100 ohms or less)

J080208E.EPS

Figure Cable Connection between MELSEC-A and ACM11

(When MESLSEC-A has a RS-232C D-sub 9 pin connector)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.2 Connecting FCS and MELSEC-A>

J8-11

With the ACM11, the RS-232C circuit and FG (frame ground) are electrically insulated. This
has the function of preventing intrusion of noise from the MELSEC-A side and improving
noise resistance. Satisfy all conditions given below to make this function effective:
For the frame ground, perform protective grounding (100 ohms or less) at the opposing side of the connection (the modem or MELSEC-A side).
Attach only one side of the shield of the sheathed cable to the FG of the opposing side
of the connection. DO not ground the cable shield on the ACM11 side. Also, do not
use a connector shell that is conductive.
Connect the FG and the SG (signal ground) of the RS-232C circuit at the opposing
side of the connection. When the FG and SG are not connected on the opposing side,
and if the RS-232C cable is manufactured by Yokogawa Electric, then use AKB141
(RS-232C modem cable) or AKB142 (RS-232C null modem cable). For the AKB141
and AKB142 cables, SG and FG are connected inside of the connector shell. Also, the
cable shield can be connected to the FG of the opposing side of the connection.
SEE ALSO
For details on cable connections, see the following:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.2 Connecting FCS and MELSEC-A>

J8-12

Cable Connection Using the ACM12 MELSEC-A

The cable connections for connecting the ACM12 and MELSEC-A are indicated below:
ACM12

MELSEC-A

ACM12

MELSEC-A

TX +

SDA

TX +

SDA

TX -

SDB

TX -

SDB

RX +

RDA

RX +

RDA

RX -

RDB

RX -

RDB

SG

SG

SG

SG

FG

FG

FG

FG

(4-wire connection)

(2-wire connection)
J080209E.EPS

Figure 1 to 1 Connection Using RS-422 or RS-485 MELSEC-A

ACM12
TX +
TX RX +
RX SG
FG

MELSEC-A

MELSEC-A

SDA

SDA

SDB

SDB

RDA

RDA

RDB

RDB

SG

SG

FG

FG

MELSEC-A
SDA
SDB
RDA
RDB
SG
FG
J080210E.EPS

Figure 1 to n Connection Using RS-422 or RS-485 (4 Wire Connection) MELSEC-A

IMPORTANT
For subsystem communication between the ACM12 and MELSEC-A, a 1 to n connection
using a 2 wire connection is not supported.

With the ACM12, the FG (frame ground) and the SG (signal ground) for the RS-422 and
RS-485 are separated. Treat the shield for the RS-422 and RS-485 as follows:
Perform protective grounding (100 ohms or less) for the FG at the opposing side of the
connection (MELSEC-A side).
Connect the shield for the cable between ACM12 and MELSEC-A to the FG of the
MELSEC-A side. Do not connect it to the FG of the ACM12 side.
SEE ALSO
For details on cable connections, see the following:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)

When connecting the ACM12 and MELSEC-A, it is necessary to attach a terminating

register on each side.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.2 Connecting FCS and MELSEC-A>

J8-13

Setting a Terminating Register on the ACM12 Side MELSEC-A

When connecting the ACM12 and MELSEC-A, it requires a terminating resistor (120 ohms
1/2W) between the RX+ terminal and RX- terminal on the ACM12 side. The ACM12 is
shipped with a terminating resistor installed between the RX+ terminal and
RX- terminal.
Set the connection method (4-wire or 2-wire ) using the 2-pole DIP switch (SW1) attached
to the ACM12. The unit is shipped from the factory with a 4-wire connection setting as
default.
Table SW1 Setting for the ACM12 MELSEC-A
Connection method

SW1 setting for ACM12

2-wire

ON

ON

4-wire

OFF

OFF
J080211E.EPS

Setting a Terminating Register on the MELSEC-A Side

On the MELSEC-A side, setting methods for the terminating resistor and other items vary
with the computer link unit.
SEE ALSO
For settings on the MELSEC-A side, see the following:
J8.7, Settings on Subsystem MELSEC-A

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.3 Accessible Devices MELSEC-A>

J8-14

J8.3 Accessible Devices MELSEC-A

MELSEC-A internal data are called devices. Devices are bit devices and word devices, as indicated below:
Bit device
This refers to data where each bit has a meaning. An internal relay is equivalent
to a bit device.
Word device
This refers to data where a word unit (1 word = 16 bits) contains the meaning. A
data register is equivalent to a word device.

Accessible Devices for Each MELSEC-A CPU Unit

The devices and range of device numbers that can be accessed, and the number of digits
for a device number differ according to the MELSEC-A CPU unit model. Also, depending on
the type of device, device numbers are expressed as decimal or hexadecimal.
TIP
The device number of the device accessed is set in the Device & Address of the Communication I/O
Builder.

The following section explains accessible devices for each MELSEC-A CPU unit. In this
section the MELSEC-A CPU units are categorized into the following three groups:
ACPU units
A0J2H, A1, A1N, A1S, A1SJ, A2, A2-S1, A2N, A2N-S1, A2S, A2C, A3, A3N, A3H,
A3M, A73, A52G, A7LMS-F
AnACPU units
A2A, A2A-S1, A3A
AnUCPU units
A2U, A2U-S1, A2US, A2US-S1, A3U, A4U
SEE ALSO
For details on the range of and restrictions on each device number for various MELSEC-A CPU unit
models, refer to the users manual for the MELSEC-A computer link unit to be connected.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.3 Accessible Devices MELSEC-A>

J8-15

Accessible Devices When Using an MELSEC-A ACPU Unit

When using an MELSEC-A ACPU unit, designate the device number using five digits.
Table Accessible Devices and Range of Device Numbers when Using an ACPU Unit
Device
classification

Bit device

Word device

Device name

Device number range

Expression

Input

X0000 to X07FF

Hexadecimal

Output

Y0000 to Y07FF

Hexadecimal

Internal relay

M0000 to M2047

Decimal

Latch relay

L0000 to L2047

Decimal

Step relay

S0000 to S2047

Decimal

Link relay

B0000 to B03FF

Hexadecimal

Annunciator

F0000 to F0255

Decimal

Special relay

M9000 to M9255

Decimal

Timer (contact)

TS000 to TS255

Decimal

Timer (coil)

TC000 to TC255

Decimal

Counter (contact)

CS000 to CS255

Decimal

Counter (coil)

CC000 to CC255

Decimal

Timer (present value)

TN000 to TN255

Decimal

Counter (present value)

CN000 to CN255

Decimal

Data register

D0000 to D1023

Decimal

Link register

W0000 to W03FF

Hexadecimal

File register

R0000 to R8191

Decimal

Special register

D9000 to D9255

Decimal

STS00, STS16

Decimal

Special device Communication status

Remarks

J080301E.EPS

IMPORTANT
When using the AJ71C24-S3 computer link unit to perform communication, device numbers M9000 to M9007 and M9248 to M9255 cannot be read directly due to restrictions on
the data designation on the MELSEC-A side. To read the contents of these devices, the
contents should first be temporarily transferred to another devices and then read.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.3 Accessible Devices MELSEC-A>

J8-16

Accessible Devices When Using an MELSEC-A AnACPU

or AnUCPU Unit
When a MELSEC-A AnACPU unit and AnUCPU unit are used, designate the device number using seven digits.
Table Accessible Devices and Range of Device Numbers when Using an AnACPU or AnUCPU
Unit
Device
classification

Bit device

Device name

Device number range (*1)

Expression

Input

X000000 to X0007FF
(X000800 to X001FFF)

Hexadecimal

Output

Y000000 to Y0007FF
(Y000800 to Y001FFF)

Hexadecimal

Internal relay

M000000 to M008191

Decimal

Latch relay

L000000 to L008191

Decimal

Step relay

S000000 to S008191

Decimal

Link relay

B000000 to B000FFF
(B001000 to B001FFF)

Hexadecimal

Annunciator

F000000 to F002047

Decimal

Special relay

M009000 to M009255

Decimal

Timer (contact)

TS00000 to TS02047

Decimal

Timer (coil)

TC00000 to TC02047

Decimal

Counter (contact)

CS00000 to CS01023

Decimal

Counter (coil)

CC00000 to CC01023

Decimal

Timer (present value)

TN00000 to TN02047

Decimal

Counter (present value)

CN00000 to CN01023

Decimal

Data register

D000000 to D006143
(D006144 to D008191)

Decimal

Link register

W000000 to W000FFF
(W001000 to W001FFF)

Hexadecimal

Word device

File register

R000000 to R008191

Decimal

Special register

D009000 to D009255

Decimal

STS00, STS16

Decimal

Special device Communication status

Remarks

J080302E.EPS

*1:

[ ] indicates the device range expanded by AnUCPU unit of MELSEC-A.

TIP

When performing communication using the AJ71C24-S8 and AJ71C24-S6 computer link units and if
the MELSEC-A CPU unit model is A2A, A2A-S1 or A3A, then designate a seven digit number for the
bit device or word device.

For the special device STSnn that indicates the communication status, specify the device number
using five digits regardless of the model of MELSEC-A CPU that is used.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.4 Subsystem Data Storing Format MELSEC-A>

J8-17

J8.4 Subsystem Data Storing Format MELSEC-A

The following explains the format in which subsystem data acquired from the
MELSEC-A is stored in the FCS.
The storing formats for MELSEC-A bit devices, word devices and special devices
that indicate status of communication are given below.

Bit Device MELSEC-A

When 16 m number (m = 1, 2, ...) of bit devices are read starting from address n, the
MELSEC-A data is stored in the FCS as indicated below. The data size is specified as m on
the Communication I/O Builder.
The multiple of 16 can be specified as n.
16 bits
n n n n n n
+ + + + + +
15 14 13 12 11 10

n
+
9

n
+
8

n
+
7

n
+
6

n
+
5

n
+
4

n
+
3

n
+
2

n
+
1

n
+
31

m=1

n
+
16

m=2

n+16 (m-1)+15

n+16 (m-1)
J080401E.EPS

Figure Image of Stored Bit Device MELSEC-A

Word Device MELSEC-A

When m number of word devices are read starting from address n, the MELSEC-A data is
stored in the FCS as indicated below:
16 bits

Contents of the nth register

Contents of the n+1th register

Contents of the n+m-1th register

J080402E.EPS

Figure Image of Stored Word Device MELSEC-A

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.4 Subsystem Data Storing Format MELSEC-A>

J8-18

Special Device MELSEC-A

The MELSEC-A special device is communication status data STSnn, which shows the
status of communication with each station.
Communication status will become as follows:
Stations defined via the Communication I/O Builder that are communicating normally:
1
Stations defined via the Communication I/O Builder that are faulty: 0
Stations that are not actually communicating (those not defined via the Communication I/O Builder): 1
In the case of special devices, designation of the station number in the Communication I/O
Builder has no particular significance, but the smallest station number of those that are
actually communicating is set. Also, the device number is designated using five digits as
indicated below, regardless of the MELSEC-A CPU unit model.
Table Communication Status and Device Number MELSEC-A
Explanation

Device number

Communication status of station numbers 0 to 15

STS00

Communication status of station numbers 16 to 31

STS16
J080403E.EPS

The relationship between bits and stations is shown below. The smallest station number
corresponds to the smallest bit number.
STS00 configuration
15

00

Bit arrangement

15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
STS16 configuration
15

Station number
00

Bit arrangement

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
J080404E.EPS

Figure Relationship between the Communication Status Bits and Station Numbers MELSEC-A

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.5 Setting Items on System View MELSEC-A>

J8-19

J8.5 Setting Items on System View MELSEC-A

MELSEC

In this section, setting items on System View for MELSEC-A, the specific functionality and the recommended settings are explained.
SEE ALSO
For more information regarding to Set Details tab on Create New IOM dialog box and subsystem
common settings, see the following:
Setting Items for ACM11, ACM12 in J1.5.1, Overview of Setting Items on System View

For MELSEC-A, the setting items are as follows. These settings are performed on
the Set Details tab of the New IOM dialog box called from System View.
Connection Device
Baud Rate
Parity
Data Bits
Stop Bits
RS Control
DR Check
CD Check
Communication Error Process
Options
After creating the new I/O module, the settings can be modified on the I/O module
property sheet.

Connection Device MELSEC-A

Set [MELSEC] as the type of connection device (subsystem).
Must perform this setting since the default is [FA-M3].

Baud Rate MELSEC-A

This sets the baud rate between the communication module and MELSEC-A.
The recommended value for the baud rate is [19200 bps].
The baud rate set in the Detail setting tab of the New IOM dialog box should match the setting
of the DIP switch on the MELSEC-A.
SEE ALSO
For the transmission specification switch settings on the MELSEC-A side, see the following:
J8.7, Settings on Subsystem MELSEC-A

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.5 Setting Items on System View MELSEC-A>

J8-20

Parity MELSEC-A
This sets the method for checking the parity of the subsystem data to be transmitted.
The recommended setting is [Even].
When the baud rate is set to [19200 bps], the [no parity] cannot be set.
The parity set in the Set Detail tab of the New IOM dialog box should match the parity
setting of the DIP switch on the MELSEC-A.
SEE ALSO
For the transmission specification switch settings on the MELSEC-A side, see the following:
J8.7, Settings on Subsystem MELSEC-A

Data Bits MELSEC-A

This sets the data bit length of the subsystem data to be transmitted.
The recommended bit length is [7 bits].
The default is [8 bits].
The data bit set in the Detail setting tab of the New IOM dialog box called from System
View should match the data bit setting of the DIP switch on the MELSEC-A.
SEE ALSO
For the transmission specification switch settings on the MELSEC-A side, see the following:
J8.7, Settings on Subsystem MELSEC-A

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.5 Setting Items on System View MELSEC-A>

J8-21

Stop Bits MELSEC-A

This sets the stop bit of the subsystem data to be transmitted. This setting is done using the
Detail setting tab of the New IOM dialog box called from the System View.
When using the MELSEC-A, select [1 bit] for the stop bit.
The default is [1 bit].

IMPORTANT
When using MELSEC-A, [2 bits] cannot be used as the stop bit.

The stop bit set in the Detail setting tab of the New IOM dialog box should match the stop
bit setting of the transmission specification setting switch on the MELSEC-A side.
SEE ALSO
For the transmission specification switch settings on the MELSEC-A side, see the following:
J8.7, Settings on Subsystem MELSEC-A

RS Control MELSEC-A
This sets whether or not RS control is performed during subsystem data transmission.
When using MELSEC-A, disable RS control by leaving the [RS control] check box unchecked.

DR Check MELSEC-A
This sets whether or not DR check is performed during subsystem data transmission.
When using MELSEC-A, enable the DR check function by checking the [DR check] check
box.

CD Check MELSEC-A
This sets whether or not CD check is performed during subsystem data transmission.
When using the MELSEC-A, disable the CD check by leaving the [CD check] check box
unchecked.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.5 Setting Items on System View MELSEC-A>

J8-22

Communication Error Process MELSEC-A

This sets the parameters related to communication error handling during subsystem data
transmission. This setting is done using the Set Details tab of the New IOM dialog box
called from System View.
The setting items include the following three:
Response Timeout
This sets the time limit for getting response from MELSEC-A. The setting unit is
seconds.
The setting range is 1 to 99.
The recommended setting is 4.
Number of Retries Upon Response Timeout
This sets the number of retries when a communication error occurs.
The setting range is 0 to 99.
The recommended setting 1.
Interval of Connection Retries
This sets the time interval for FCS to send a connection request to the station that a
communication error occurred. The setting unit is seconds.
The setting range is 1 to 999.
The recommended setting is 30.
The recommended settings for communication error handling are the default setpoint
values.

Options MELSEC-A
Settings of communication parameter options vary depending on the equipment connected. Set options by clicking the [Option] button 1 through [Option] button 4 in the Set
Details tab of the New IOM dialog box called from System View.
In the case of MELSEC-A, set 0 in option 1 through option 4.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.6 Setting Items on Communication I/O Builder MELSEC-A>

J8-23

J8.6 Setting Items on Communication I/O Builder

MELSEC-A
In this section, setting items on Communication I/O Builder for MELSEC-A, the
specific functionality and the recommended settings are explained.
SEE ALSO
For an overview of the setting items on Communication I/O Builder, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

For MELSEC-A, the setting items are as follows.

Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

Element MELSEC-A
Element

With respect to the address of the subsystem data buffer, the element numbers are displayed on Communication I/O Builder. The element numbers are not for set, only for
display.

Buffer MELSEC-A
Buffer

This sets the buffer for the communicated data.

Must set the buffer since this is a required setting item of the Communication I/O Builder.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.6 Setting Items on Communication I/O Builder MELSEC-A>

J8-24

Program Name MELSEC-A : PFCS/SFCS

Program Name

When setting the name of the program for accessing the subsystem, entering the unit
number, slot number and MELSEC as the program name.
u-sProgramName
u:
Unit number
s:
Slot number
ProgramName: MELSEC

Program Name MELSEC-A : LFCS2/LFCS

Program Name

When setting the name of the program for accessing the subsystem, entering the node
number, unit number, slot number and MELSEC as the program name.
n-u-sProgramName
n:
u:
s:
ProgramName:

Node number
Unit number
Slot number
MELSEC

Size MELSEC-A
Size

This item sets the data size (data length) from the head address set in Device & Address.
Must set the Size since this is a required setting item on Communication I/O Builder.
For MELSEC-A, the setting ranges are limited as follows, the unit is in Word.
Word Device:

1 to 64 Words

Bit Device:

1 to 32 Words

SEE ALSO
For more information about Size setting item, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.6 Setting Items on Communication I/O Builder MELSEC-A>

J8-25

Port MELSEC-A
Port

Port 1 is set for use.

IP Address MELSEC-A
IP Address

No need to set IP address for ACM11 or ACM12.

Station MELSEC-A
Station

This sets the station number of the MELSEC-A. This setting is done via the Communication
I/O Builder.
The station numbers that can be set are 0 to 31.
The station number setting in the Communication I/O Builder should match the setting of
the station number setting switch on the MELSEC-A side.
SEE ALSO
For the setting of the station number setting switch on the MELSEC-A side, see the following:
J8.7, Settings on Subsystem MELSEC-A

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.6 Setting Items on Communication I/O Builder MELSEC-A>

J8-26

Device & Address MELSEC-A

Device & Address

This sets the head address of MELSEC-A data.

The addresses can be set in five or seven alphanumeric characters shown below:
Input:

Xnnnn or Xnnnnnn

Output:

Ynnnn or Ynnnnnn

Internal relay:

Mnnnn or Mnnnnnn

Latch relay:

Lnnnn or Lnnnnnn

Step relay:

Snnnn or Snnnnnn

Link relay:

Bnnnn or Bnnnnnn

Annunciator:

Fnnnn or Fnnnnnn

Special relay:

Mnnnn or Mnnnnnn

Timer (contact):

TSnnn or TSnnnnn

Timer (coil):

TCnnn or TCnnnnn

Counter (contact):

CSnnn or CSnnnnn

Counter (coil):

CCnnn or CCnnnnn

Timer (present value):

TNnnn or TNnnnnn

Counter (present value):

CNnnn or CNnnnnn

Data register:

Dnnnn or Dnnnnnn

Link register:

Wnnnn or Wnnnnnn

File register:

Rnnnn or Rnnnnnn

Special register:

Dnnnn or Dnnnnnn

Communication status:

STS00 or STS16

SEE ALSO
For more information about address setting, see the following:
J8.3, Accessible Devices MELSEC-A

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.6 Setting Items on Communication I/O Builder MELSEC-A>

J8-27

Data Type MELSEC-A

Data Type

This sets data type of the subsystem data.

The data type can be selected from the following:
Input (16-Bit Signed)
Input (32-Bit Signed)
Input (16-Bit Unsigned)
Input (32-Bit Unsigned)
Input (32-Bit Floating)
Output (16-Bit Signed)
Output (32-Bit Signed)
Output (16-Bit Unsigned)
Output (32-Bit Unsigned)
Output (32-Bit Floating)
Input (Discrete)
Output (Discrete)

Reverse MELSEC-A
Reverse

This sets whether or not to make the bit or word arrangement in FCS in reverse order of the
subsystem data.
The following settings can be selected:
Bits
No
Words
However, when choosing [Bits], only the data of discrete inputs or discrete outputs can be
reversed. In this case, the default setting is [Bits].
Regarding to words, only the 32-bit analog inputs or the 32-bit analog outputs can be
reversed. In this case the default setting is [No].

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.6 Setting Items on Communication I/O Builder MELSEC-A>

J8-28

Scan MELSEC-A
Scan

Set whether to read the communication I/O analog data into the communication I/O data
buffer at the beginning of high-speed scan of the FCS.

Service Comment MELSEC-A

Service Comment

A comment text can be set.

Label MELSEC-A
Label

The name of the function block I/O terminal can be set as a user-defined label.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.7 Settings on Subsystem MELSEC-A>

J8-29

J8.7 Settings on Subsystem MELSEC-A

When performing subsystem communication with the MELSEC-A, switch
settings for the MELSEC-A side computer link unit are required.
This section explains the setting items for the MELSEC-A side and gives an example
of MELSEC-A side setting in the case of 1 to n connection.
Setting items for the MELSEC-A side are as follows:
Station number setting
Transmission control procedure (protocol) setting
Transmission specification setting
RS-232C CD terminal check setting
TIP
The explanation below is provided as a reference based on AJ71C24-S8 Computer Link Unit Users
Manual IB (title)-68282-C (9306) MEE published in June 1993 and AJ71UC24, A1SJ71C24-R2/R4/PRF,
A1SJ71UC24-R2/R4/PRF, A1SCPUC24-R2, A1SCPUC24, A2CCPUC24-PRF Computer Link/Multi-drop
Link Units (Computer Link and Printer Functions) Users Manual, SH (title)-3495-D(9501) published in
January 1995. Because of changes in the specifications for the MELSEC-A computer link unit, actual
settings may differ from the explanation given below. For MELSEC-A side setting items, always check the
users manual for the MELSEC-A computer link unit to be connected.
If there are discrepancies between the explanations given below and those found in the users manual,
the contents in the users manual for the MELSEC-A connected takes precedence.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.7 Settings on Subsystem MELSEC-A>

J8-30

Station Number Setting MELSEC-A

When connecting multiple AJ71C24 computer link units and performing subsystem communication, a station number is set in each AJ71C24 so that the FCS can specify which
AJ71C24 to access.
The AJ71C24 station number is set using the two decimal rotary switches (station number
setting switches) located on the front of the AJ71C24.
Table MELSEC-A Station Number Setting Switches
Station number setting
switch details
7

10

9
0

Description
(1) Set the AJ71C24 station numbers within the range of 00 to 31 (do not use a
setting 32 or over).
(2) 10 sets a place of 10 for the station number.
(3) 1 sets a place of 1 for the station number.
(4) Station numbers can be set to any number in the range 00 to 31 as long as
there are no duplicates. Thus, it is not necessary to set the numbers in the
order of connections on FCS side. Station numbers are not required to be
continuous.

1

(Above drawing shows the

setting for 01)
J080701E.EPS

TIP
The A1SJ71C24-R2, A1SJ71C24-PRF, A1SJ71UC24-R2, A1SJ71UC24-PRF and A1SCPUC24-R2
computer link units do not have station number setting switches. When performing subsystem communication with the FCS using dedicated protocol, set the station number to 00 in the Communication I/O
Builder.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.7 Settings on Subsystem MELSEC-A>

J8-31

Transmission Control Procedure (Protocol) Setting MELSEC-A

Select the transmission control procedure (protocol) to use in subsystem communication
with the hexadecimal rotary switch (mode setting switch) located on the front of the
AJ71C24.
Table MELSEC-A Mode Setting Switch
Mode setting
switch detail

Mode setting
switch number

B C D E

RS-232C side

RS-422 side

Remarks

Cannot be used

Type 1 protocol mode

No-protocol mode

Type 2 protocol mode

No-protocol mode

Type 3 protocol mode

No-protocol mode

[4]

Type 4 protocol mode

No-protocol mode

No-protocol mode

Type 1 protocol mode

No-protocol mode

Type 2 protocol mode

No-protocol mode

Type 3 protocol mode

No-protocol mode

Type 4 protocol mode

F 0 1 2
3 4 5

7 8 9 A

Setting details

No-protocol mode

No-protocol mode

Type 1 protocol mode

Type 1 protocol mode

MODE

Type 2 protocol mode

Type 2 protocol mode

Type 3 protocol mode

Type 3 protocol mode

Type 4 protocol mode

Type 4 protocol mode

Cannot be used

For unit test

This is the mode used when

RS-232C and RS-422 have separate
computers, or a printer is connected
to the no-protocol side. The interface
for both RS-232C and RS-422 each
operate independently.

This is the mode used when noprotocol computer linking is done

among all devices connected to the
RS-232C and RS-422. Data sent by
the computer can be received by all
AJ71C24.
This is the mode used when
dedicated protocol linking is
performed among all devices
connected to the RS-232C and
RS-422. Data sent by the computer is
received by the AJ71C24 designated
in the message.
The interface for both RS-232C and
RS-422 each operate independently.
J080702E.EPS

Note: [ ] indicates the recommended setting when connecting the ACM11 and the AJ71C24 computer link unit.

TIP

When the setting value of the mode setting switch is 9 to D, the interface for both RS-232C and RS422 are interlocked when operating. The transmission specifications for the RS-232C and RS-422
are the same.

When using the RS-232C and RS-422 in an independent mode, set the mode setting switch to 1 to 8.

When the mode setting switch is set to 9 to D and if there are interfaces that are not connecting
external devices, noise from the interface will enter and normal communication cannot be performed.
In this case, set the mode setting to 1 to 8.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J8-32

<J8.7 Settings on Subsystem MELSEC-A>

Transmission Specification Settings MELSEC-A

Transmission specifications are set with the 8-pole or 4-pole DIP switch (transmission
specification setting switch) located on the front of the AJ71C24.
Table MELSEC-A Transmission Specification Setting Switch
Switch
settings

Setting
switch

Setting switch status

Setting item

SW11

Main channel

SW12

Data bit

Remarks

ON

OFF

RS-422

[RS-232C]

8 bit

[7 bit]

Enabled when mode setting switch is set to 9

to D
8 bit for m:n data communication

Baud rate setting

Baud rate
SW13
SW14
SW15

ON

3
4

600

1200

2400

4800

9600

SW13

OFF ON

OFF

ON

OFF

ON

[OFF]

ON

SW14

OFF OFF

ON

ON

OFF

OFF

[ON]

ON

SW15

OFF OFF

OFF

OFF

ON

ON

[ON]

ON

6
7

SW16

Parity bit required

[Yes]

No

SW17

Even or odd parity

[Even]

Odd

This is enabled only when parity bit [yes] is

selected

SW18

Stop bit

2 bits

[1 bit]

This is always OFF when connected to ACM

SW21

Check Sum required?

[Yes]

No

This is always ON when connected to ACM

SW22

Write during RUN?

[Yes]

No

This is always ON when connected to ACM

SW23

Terminator on sending side?

Yes

[No]

This is valid only when using RS-422

SW24

Terminator on receiving
side?

Yes

[No]

This is valid only when using RS-422

ON

1
2
3
4

SW21
SW22
SW23
SW24

[19200] Cannot set

SW18

SW13
SW14
SW15
SW16
SW17

SW11
SW12

300

J080703E.EPS

Note: [ ] indicates the recommended setting when connecting the ACM11 and the AJ71C24 computer link unit.

TIP

The SW11 main channel setting indicates the interface for the connector to which the FCS is connected and is enabled only when the mode setting switch is set to 9 to D. When the mode setting
switch is set to 1 to 8 or F, it does not matter whether the SW11 is ON or OFF.

When communicating with the FCS, always make sure the stop bit, sum check and write during RUN
settings are set as follows:
Stop bit:
1 bit (SW18 OFF)
Sum check:
Yes (SW21 ON)
Can write during RUN?:
Yes (SW22 ON)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.7 Settings on Subsystem MELSEC-A>

J8-33

The following table shows settings for computer link units other than AJ71C24:
Table Settings for Computer Link Units Other than AJ71UC24
Setting switch

MODE

Setting item

Setpoint

Setting description

Type 4 (RS-232C side)

(*1)

Type 4 (RS-422/RS-485
side) (*2)

Protocol mode

SW11

Main channel

ON, OFF

RS-422, RS-232C (*3)

SW12

Character length

ON, [OFF]

8, [7] bits

SW13, SW14, SW15

Baud rate (bps)

[OFF, ON, ON]

[19200]

ON, OFF, ON

9600

OFF, OFF, ON

4800

ON, ON, OFF

2400

OFF, ON, OFF

1200

SW16

Parity bit

[ON], OFF

[Yes], No

SW17

Parity

[ON], OFF

[Even], odd

SW18

Stop bit

SW21

Check Sum

ON

Yes

SW22

Write during RUN

ON

Enabled

SW23

Computer link/Multi-drop
link selection

ON

Always select computer

link

SW24

Not used

OFF

1 bit

J080704E.EPS

Note:
*1:
*2:
*3:

[ ] indicates the recommended setting.

This is the setting when connecting to ACM11 using 1 to 1 connection.
This is the setting when connecting to ACM12 using 1 to 1 connection.
Can be ON or OFF when connecting to ACM11.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.7 Settings on Subsystem MELSEC-A>

J8-34

Table Settings for the A1SJ71C24-R2, A1SJ71UC24-R2, A1SJ71C24-PRF, A1SJ71UC24-PRF

Computer Link Units
Setting switch

Setting item

MODE

Protocol mode

SW03

Not used

SW04

Write during RUN

SW05. SW06, SW07 Baud rate (bps)

Setpoint
4

Setting description
Type 4 (RS-232C side)

ON

Enabled

[OFF, ON, ON]

[19200]

ON, OFF, ON

9600

OFF, OFF, ON

4800

ON, ON, OFF

2400

OFF, ON, OFF

1200

SW08

Character length

ON / [OFF]

8/[7] bits

SW09

Parity bit

[ON] / OFF

[Yes]/No

SW10

Parity

[ON] / OFF

[Even]/odd

SW11

Stop bit

OFF

1 bit

SW12

Check Sum

ON

Yes
J080705E.EPS

Note: [ ] indicates the recommended setting.

Table Settings for the A1SJ71C24-R4, A1SJ71UC24-R4 Computer Link Units

Setting switch

Setting item

Setpoint

Setting description

MODE

Protocol mode

Type 4 (RS-422/RS-485 side)

SW01

Master station/local station

Setting not necessary

SW02

Computer link
/multi-drop link setting

SW03

Not used

SW04

Write during RUN

SW05. SW06, SW07 Baud rate (bps)

ON

Select computer link

ON

Enabled

[OFF, ON, ON]

[19200]

ON, OFF, ON

9600

OFF, OFF, ON

4800

ON, ON, OFF

2400

OFF, ON, OFF

1200

SW08

Character length

ON / [OFF]

8/[7] bits

SW09

Parity bit

[ON] / OFF

[Yes]/No

SW10

Parity

[ON] / OFF

[Even]/odd

SW11

Stop bit

OFF

1 bit

SW12

Check Sum

ON

Yes
J080706E.EPS

Note: [ ] indicates the recommended setting.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.7 Settings on Subsystem MELSEC-A>

J8-35

Table Settings for the A1SCPUC24-R2 Computer Link Unit

Setting switch

Setting item

MODE

Protocol mode

SW01

Write during RUN

SW02, SW03, SW04

Baud rate (bps)

Setpoint

Setting description

Type 4 (RS-232C side)

ON

Enabled

[OFF, ON, ON]

[19200]

ON, OFF, ON

9600

OFF, OFF, ON

4800

ON, ON, OFF

2400

OFF, ON, OFF

1200

SW05

Character length

ON / [OFF]

8/[7] bits

SW06

Parity bit

[ON] / OFF

[Yes]/No

SW07

Parity

[ON] / OFF

[Even]/odd

SW08

Stop bit

OFF

1 bit

SW09

Check Sum

ON

Yes
J080707E.EPS

Note: [ ] indicates the recommended setting.

Table Settings for the A2CCPUC24 and A2CCPUC24-PRF Computer Link Units
Setting switch
MODE

Setting item
Protocol mode

SW11, SW12, SW13 Baud rate (bps)

Setpoint

Setting description

Type 4 (RS-232C side) (*1)

Type 4 (RS-422/RS-485 side)

(*2)

[OFF, ON, ON]

[19200]

ON, OFF, ON

9600

OFF, OFF, ON

4800

ON, ON, OFF

2400

OFF, ON, OFF

1200

SW14

Character length

ON / [OFF]

8/[7] bits

SW15

Parity bit

[ON] / OFF

[Yes]/No

SW16

Parity

[ON] / OFF

[Even]/odd

SW17

Stop bit

OFF

1 bit

SW18

Check Sum

ON

Yes

SW19

Main channel setting

SW20

Write during RUN

ON/OFF
ON

RS-422,RS-485/RS-232C (*3)
Enabled

TXD

Terminating resistor pin

setting (sender side)

A/B/C

RS-422/RS-485/none (*3)

RXD

Terminating resistor pin

setting (receiver side)

A/B/C

RS-422/RS-485/none (*3)
J080708E.EPS

Note:
*1:
*2:
*3:

[ ] indicates the recommended setting.

This is the setting when connecting to ACM11 using 1 to 1 connection.
This is the setting when connecting to ACM12 using 1 to 1 connection.
This can be either setting when connecting to ACM11.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.7 Settings on Subsystem MELSEC-A>

J8-36

RS-232C CD Terminal Check Setting MELSEC-A

The RS-232C CD terminal check setting is used to designate whether or not to have the
AJ71C24 computer link unit to perform a check to determine if the CD terminal (detects receiving carrier) is ON or OFF. The RS-232C CD terminal check is set by setting the address bit
as indicated below in the MELSEC-A sequence program.
15
Address 10BH

0
(Default: 0)

Bit 1 through bit 15 are irrelevant.

Write 0 or 1
(0: perform check (yes))
(1: do not perform check (no))
J080709E.EPS

Figure RS-232C CD Terminal Check Setting MELSEC-A

When connecting a communication module and the AJ71C24 computer link unit, use the
do not perform RS-232C CD terminal check setting. To set do not perform RS-232C
CD terminal check, set 1 in the AJ71C24 buffer memory address, 10BH.
TIP
When do not perform RS-232C CD terminal check is set, the MELSEC-A side changes to full-duplex
communication mode. The MELSEC-A communication packages (ACM11, ACM12) uses half-duplex
communication but there is no problem in using the MELSEC-A communication package (ACM11,
ACM12) and performing communication between the communication I/O module and the AJ71C24
computer link unit. However, this is provided when all cable connection specifications indicated in J8.2,
Connecting to the MELSEC-A are satisfied.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J8-37

<J8.7 Settings on Subsystem MELSEC-A>

Setting for 1 to n Connections

The section below describes the connections and MELSEC-A side settings when the
communication module and the MELSEC-A are connected as 1 to n.

1 to n Connections Using RS-232C MELSEC-A

Indicated below are the connections and settings for each switch when the ACM11 and
MELSEC-A are connected via RS-232C and when several MELSEC-A units are connected
via RS-422. The connections for the RS-232C portion have been simplified in the drawing.
ACM11

Station 0 link unit

RS-232-C

SD

Station 1 link unit

Station n link unit

RS-422

RS-422

SDA

SDA

SDA

SD SDB

SDB

SDB

RDA

RDA

RDA

RD

RD RDB

RDB

RDB

SG

SG SG

SG

SG

FG

FG

FG

FG

FG

J080710E.EPS

Figure 1 to n Connection Using RS-232C MELSEC-A

Table Switch Settings for 1 to n Connection Using RS-232C MELSEC-A
Link unit

Station 0 link unit

Station 1 link unit

Station n link unit

AJ71C24

MODE: D
SW11: OFF
SW23: ON
SW24: ON

MODE: 8
SW23: OFF
SW24: OFF

MODE: 8
SW23: ON
SW24: ON

AJ71UC24

MODE: D
SW11: OFF
SW23: ON
SW24: OFF
Install the supplied terminating resistors
to the sending and receiving sides

MODE: 8
SW23: ON
SW24: OFF

MODE: 8
SW23: ON
SW24: OFF
Install the supplied terminating resistors
to the sending and receiving sides

MODE: 8
TXD: C
RXD: C

MODE: 8
TXD: A
RXD: A

MODE: D
ACCPUC24
SW19: OFF
ACCPUC24-PRF TXD: A
RXD: A

J080711E.EPS

TIP

Terminating resistors for the A2CCPUC24 and A2CCPUC24-PRF computer link units are set using
the terminating resistor setting pin.
RS-422:
A
RS-485:
B
No terminating resistor:
C

Installed the supplied terminating resistors on the MELSEC-A side with computer link units other than
the A2CCPUC24 and A2CCPUC24-PRF.
RS-422:
330 ohms
RS-485:
110 ohms

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J8-38

<J8.7 Settings on Subsystem MELSEC-A>

1 to n Connections Using RS-422 MELSEC-A

Indicated below are the connections and settings for each switch when the ACM11 and
MELSEC-A are connected via RS-422:
Station 0 link unit

ACM12
RS-422
TX+
TXRX+
RXSG
FG

Station 1 link unit

Station n link unit

RS-422

RS-422

SDA

SDA

SDB

SDB

RDA

RDA

RDB

RDB

SG

SG

FG

FG

SDA
SDB
RDA
RDB
SG
FG

Terminating resistor
connection required
J080712E.EPS

Figure 1 to n Connection Using RS-232C MELSEC-A

Table Switch Settings for 1 to n Connection Using RS-422 MELSEC-A
Link unit

Station 0 link unit

Station 1 link unit

Station n link unit

MODE: 8
SW11: ON
SW23: OFF
SW24: ON

MODE: 8
SW23: OFF
SW24: OFF

MODE: 8
SW23: ON
SW24: ON

MODE: 8
SW11: ON
SW23: ON
SW24: OFF

MODE: 8
SW23: ON
SW24: OFF

MODE: 8
SW23: ON
SW24: OFF
Install the supplied terminating resistors
to the sending and receiving sides

MODE: 8
ACCPUC24
SW19: ON
ACCPUC24-PRF TXD: C
RXD: C

MODE: 8
TXD: C
RXD: C

MODE: 8
TXD: A
RXD: A

MODE: 8
A1SJ71C24-R4 SW02: ON
A1SJ71UC24-R4

MODE: 8
SW02: ON

MODE: 8
SW02: ON
Install the supplied terminating resistors
to the sending and receiving sides

AJ71C24

AJ71UC24

J080713E.EPS

IMPORTANT
1 to n connections using the 2-wire system are not supported in subsystem communication
between the ACM12 and MELSEC-A.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.7 Settings on Subsystem MELSEC-A>

J8-39

TIP

Terminating resistors for the A2CCPUC24 and A2CCPUC24-PRF computer link units are set using
the terminating resistor setting pin.
RS-422:
A
RS-485:
B
No terminating resistor:
C

Installed the supplied terminating resistors on the MELSEC-A side with computer link units other than
the A2CCPUC24 and A2CCPUC24-PRF.
RS-422:
330 ohms
RS-485:
110 ohms

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.8 System Alarm Messages Specific to MELSEC-A>

J8-40

J8.8 System Alarm Messages Specific to MELSEC-A

This section explains the system alarm messages that are specific to
MELSEC-A.

System Alarm Message when a Communication Error Occurs

MELSEC-A : PFCS/SFCS
When there is a communication error, the system alarm message as shown below is sent
to HIS:
STNss SS-COM Error UNITmm SLOTnn STNzzz CODE=####
STNss:
mm:
nn:
zzz:
####:

FCS name
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. After that, a new system alarm message
will not be sent even if an error is generated by a different cause.
SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs MELSEC-A

System Alarm Message when a Communication Error Occurs

MELSEC-A : LFCS2/LFCS
When a communication error occurs, the system alarm message as shown below is sent
to HIS:
STNss SS-COM Error RIO01 NODExx UNITmm SLOTnn STNzzz CODE=####
STNss:
xx:
mm:
nn:
zzz:
####:

FCS name
Node number
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. The new system alarm message will not
be transmitted even if errors are generated by different causes.
SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs MELSEC-A

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.8 System Alarm Messages Specific to MELSEC-A>

J8-41

System Alarm Message when Communication Returns to Normal

MELSEC-A : PFCS/SFCS
When communication returns to the normal condition, the system alarm message indicated
below is sent to HIS:
STNss SS-COM Recover UNITmm SLOTnn STNzzz
STNss:
mm:
nn:
zzz:

FCS name
Unit number
Slot number
Subsystem station number

System Alarm Message when Communication Returns to Normal

MELSEC-A : LFCS2/LFCS
When communication returns to normal status, the system alarm message indicated below
is sent to HIS:
STNss SS-COM Recover RIO01 NODExx UNITmm SLOTnn STNzzz
STNss:
xx:
mm:
nn:
zzz:

FCS name
Node number
Unit number
Slot number
Subsystem station number

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.8 System Alarm Messages Specific to MELSEC-A>

J8-42

Error Codes when a Communication Error Occurs MELSEC-A

Table Error Codes when a Communication Error Occurs MELSEC-A (1/2)
Error code
(hexadecimal)

Description

A391

Communication driver busy

A392

Communication line busy

A393

Communication line not ready

A394

Sending size is too large

A395

Use of communication port not declared

A397

Under run error

A398

Timeout between received characters

A399

Receive buffer overflow

A39A

Parity error in receive data

A39B

Receiving overrun error

A39C

Receiving framing error

A39D

No. of characters received is outside specifications

A39F

Other error

A3B0

No response

A3B1

Station number (0 to 31) is out of range

A3B2

Inappropriate address name

A3B3

Error in number of address digits

A3B4

Inappropriate address number

A3B5

Error in address number range

A3B6

Error in address size range

A3B7

Too many communication processing points

A3B8

Cannot create communication text

A3B9

STS size error

Error code
(hexadecimal)

Description

Remarks

Communication is not performed with respect to the

definition generating the error

Remarks
J080801E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.8 System Alarm Messages Specific to MELSEC-A>

J8-43

Table Error Codes when a Communication Error Occurs MELSEC-A (2/2)

Error code
(hexadecimal)

Description

A3C1

Sum check error

A3C2

Fault in response message

A3C3

Received message other than STX, ACK, NAK

A3C4

Station number or PC number error

A3C5

Receive data error

A3C6

There is no ETX

A3C7

NAK code error

A3D0

An access which is not allowed during RUN was tried

A3D1

Parity error

A3D2

Sum check error

A3D3

Protocol error

A3D4

Framing error

A3D5

Overrun error

A3D6

Error in character section

A3D7

Character error

A3D8

PC access error

A3E0

PC number error

A3E1

Mode error

A3E2

Error in designating special function unit

A3E3

Error in program step number

A3E8

Remote error

A3F0

Data link error

A3F1

Special function unit bus error

A3FE

Transmission timeout

A3FF

Other error

Error code
(hexadecimal)

Remarks

These errors are generated when a NAK (error in

communication contents) is received from the
MELSEC-A.

Description

Remarks
J080802E.EPS

SEE ALSO
For details on the contents of the errors, refer to the users manual for the MELSEC-A being used.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J8-44

<J8.9 Transmission Time between Communication Module and MELSEC>

J8.9 Transmission Time between Communication

Module and MELSEC
The transmission time between communication module and MELSEC subsystem is
to be discussed in this chapter.

Communication Time MELSEC-A

The communication time between the communication module and MELSEC-A is figured as
the total of the time T1 to T9 shown below. However, when the communication module and
MELSEC-A are connected directly without using a modem, T2, T5 and T8 are not added in.
Data acquisition begins

Communication
module

Data acquisition complete

Interpret
response message,
store data

Create message
to be sent

RTS
CTS

RTS
CTS

Modem

Data

Data

ACK

Modem
CTS
RTS
MELSEC-A

MELSEC-A
processing time
T1

T2

T3

T4

T5

T6

T7

T8

T9
J080901E.EPS

T1:
T2:
T3:
T4:

T5:
T6:
T7:
T8:
T9:

Transmission message creation time approximately 10 ms

Modem processing (delay) time on communication module side approximately 5 ms
Send message transmission time
MELSEC-A processing time. This is the time required to interpret and execute the message that was sent and create a
response message. With respect to a request coming from the MELSEC-A computer link unit, the MELSEC-A CPU unit
processes the number of points that can be processed at one time at each END when the CPU is in the RUN status.
The amount of intervention time within scan time and the number of scans required for the processing for each
MELSEC-A CPU unit are indicated in the table below.
Modem processing (delay) time on MELSEC-A side approximately 5 ms
Response message transmission time
Response message interpretation time approximately 15 ms
Modem processing (delay) time on communication module side approximately 5 ms
ACK transmission time

Figure Time Chart of Communication between Communication Module and MELSEC-A

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J8-45

<J8.9 Transmission Time between Communication Module and MELSEC>

Calculating the Communication Time MELSEC-A

The send message transmission time (T3), response message transmission time(T6) and
ACK transmission time (T9) are figured using the formula given below:
Transmission time (ms) = No. of characters to be sent no. of bits per character 1000
Baud rate (bps)
No. of bits
per character

start bit

data bit +

parity bit

stop bit
J080902E.EPS

Start bit:
Data bit:
Parity bit:
Stop bit:
Baud rate:

1 bit fixed
7 bits or 8 bits
None, even or odd
1 bit fixed
1200, 2400, 4800, 9600, 19200 (bps)

Table Number of Characters that can be Sent MELSEC-A

Read

Device

Send

Write

Respond

ACK

Send

Respond

Bit device (bit units)

19 Fixed (*1)
10 + No. of Bits
21 Fixed (*2)

7 Fixed

19 + No. of Bits (*1)

21 + No. of Bits (*2)

7 Fixed

Bit device (word units)

19 Fixed (*1)
10 + No. of Bits/4
21 Fixed (*2)

7 Fixed

19 + No. of Bits/4 (*1)

21 + No. of Bits/4 (*2)

7 Fixed

Word device

19 Fixed (*1)
10 + No. of Words4
21 Fixed (*2)

7 Fixed

19 + No. of Words  4 (*1)

21 + No. of Words  4 (*2)

7 Fixed
J080903E.EPS

*1:
*2:

For the 5-digit address (device number)

For the 7-digit address (device number)

Table MELSEC-A Processing Time

A0J2H, A1S,
A1N, A2N, A3N

A3H

AnA

AnU

No. of access
points

Batch read (word)

1.13 ms

0.81 ms

2.42 ms

3.51 ms

64 points

1 scan
(2 scans for device R)

Batch write (word)

1.13 ms

0.84 ms

2.60 ms

3.90 s

64 points

2 scans
(1 scan for RUN enablesetting,
except for R)

Processing

No. of scans (*1)

J080904E.EPS

*1:
*2:

The Bit Devices can be handled by Batch Read/Write words commands after grouping the bits into words. Total
number of accessible Bit Devices is:
64x16=1024.
Device R is the file register.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J8.9 Transmission Time between Communication Module and MELSEC>

J8-46

Calculation Example for Communication Time MELSEC-A

When the output data type is set via the Communication I/O Builder, the subsystem communication package reads data from the subsystem first. Then the package compares the
data read from the subsystem with the FCS data and only writes data to the subsystem
when discrepancies are detected.
Because of this, it is difficult to calculate the time required for communication when writing
data to a subsystem since the transmission time varies according to the number of data in
which the value has changed. Therefore, use the following guidelines for communication
time when writing to the subsystem:
When the values for most of the data to be written are not changed
Communication time = The time required for transmission when reading data from the
subsystem with respect to all definitions where write has been designated
When the values for a large number of the data to be written are changed
Communication time = About twice the amount of time required for transmission when
reading data from the subsystem with respect to all definitions where write has been
designated
The following is an example of calculating the time required for communication between a
communication module and the MELSEC-A. In this example, the contents of 50 data
registers are being read from the MELSEC-A A3H CPU unit.
Calculation of the communication time is based on the following conditions:
Baud rate is 19200 bps
Number of bits per character is 10
The MELSEC-A CPU scan period is 50 ms
Number of characters in the send message=19
Send message transmission time (T3)=19 10 1000/19200=9.89 (ms)
MELSEC-A processing time (T4)=50+0.81=50.81 (ms)
Number of characters in the response message=10+50 4=210
Response message transmission time (T6)=210 10 1000/19200=109.37 (ms)
The time required for transmitting ACK (T9)=7 10 1000/19200=3.64 (ms)
9

Total time = Ti = 10+5+9.89=50.81=5=109.37=15=5=3.64214 (ms)

i=1

J080905E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J9. MELSEC-A Communication (ACM71)>

J9-1

J9. MELSEC-A Communication (ACM71)

The MELSEC-A communication package (ACM71) is a subsystem communication
package designed for use with the Mitsubishi Electrics MELSEC-A series generalpurpose PLCs (hereinafter referred to as MELSEC-A). By using the MELSEC-A
communication package (ACM71), communications can be performed between an
FCS and a MELSEC-A over Ethernet.
The MELSEC-A communication package can be used on enhanced type PFCSs and
SFCSs only.
This chapter explains the communications between the MELSEC-A and an FCS
among the subsystem communication packages.
SEE ALSO
For functions common to different subsystem communication packages, see the following:
J1, General Information Regarding to Subsystem Communication

Applicable Models
The following MELSEC-A communication packages (ACM71) are available.
PFS2230 CS 1000 MELSEC-A communication package (ACM71)
LFS2230 CS 3000 MELSEC-A communication package (ACM71)
When using the MELSEC-A communication package (ACM71), the ACM71 (Ethernet
communication module) is installed in an FCS and a MELSEC-A to perform communications.
The applicable MELSEC models include MELSEC-A, MELSEC-QnA and MELSEC-Q
series PLCs. Note that the MELSEC-QnA and MELSEC-Q can be accessed within the
range of accessibility allowed for the MELSEC-A.
For the communication with MELSEC-QnA or MELSEC-Q, the following devices are not
accessible.
File Register (R)
Latch Relay (L)
Step Relay (S)
Edge Relay (V) (*1)
Integrating Timer (SS/SC/SN) (*1)
Special Link Relay (SB) (*1)
Special Link Register (SW) (*1)
Direct Input (DX) (*1)
Direct Output (DY) (*1)
Index Register (Z) (*1)
File Register (ZR) (*1)
*1:

New devices for QnA CPU

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J9. MELSEC-A Communication (ACM71)>

J9-2

Moreover, the following addresses are redirected:

Access to M9000-M9255 will be redirected to SM1000-SM1255
Access to D9000-D9255 will be redirected to SD1000-SD1255
The table below lists compatible MELSEC and Ethernet interface units that can be installed
on the MELSEC side.
Table Applicable Models and Ethernet Interface Units on the MELSEC side

Type name

A series

QnA series

Q series

Ethernet interface
unit model

Name

AJ71E71N-B2

A Series Ethernet interface unit, 10BASE-2

AJ71E71N-B5

A Series Ethernet interface unit, 10BASE-5

AJ71E71N-T

A Series Ethernet interface unit, 10BASE-T

AJ71E71N3-T

A Series Ethernet interface unit, 10BASE-T

A1SJ71E71N-B2

A Series Ethernet interface unit, 10BASE-2

A1SJ71E71N-B5

A Series Ethernet interface unit, 10BASE-5

A1SJ71E71N-T

A Series Ethernet interface unit, 10BASE-T

A1SJ71E71N3-T

A Series Ethernet interface unit, 10BASE-T

AJ71E71-S3

A Series Ethernet interface unit, 10BASE-5, 10BASE-2

A1SJ71E71-B2-S3

A Series Ethernet interface unit, 10BASE-2

A1SJ71E71-B5-S3

A Series Ethernet interface unit, 10BASE-5

AJ71QE71N-B2

QnA Series Ethernet interface unit, 10BASE-2

AJ71QE71N-B5

QnA Series Ethernet interface unit, 10BASE-5

AJ71QE71N-T

QnA Series Ethernet interface unit, 10BASE-T

AJ71QE71N3-T

QnA Series Ethernet interface unit, 10BASE-T

A1SJ71QE71N-B2

QnA Series Ethernet interface unit, 10BASE-2

A1SJ71QE71N-B5

QnA Series Ethernet interface unit, 10BASE-5

A1SJ71QE71N-T

QnA Series Ethernet interface unit, 10BASE-T

A1SJ71QE71N3-T

QnA Series Ethernet interface unit, 10BASE-T

AJ71QE71

QnA Series Ethernet interface unit, 10BASE-5, 10BASE-2

AJ71QE71-B5

QnA Series Ethernet interface unit, 10BASE-5

A1SJ71QE71-B2

QnA Series Ethernet interface unit, 10BASE-2

A1SJ71QE71-B5

QnA Series Ethernet interface unit, 10BASE-5

QJ71E71-B2

Q Series Ethernet interface unit, 10BASE-2

QJ71E71-B5

Q Series Ethernet interface unit, 10BASE-5

QJ71E71-100

Q Series Ethernet interface unit, 10BASE-T, 100BASE-TX

QJ71E71

Q Series Ethernet interface unit, 10BASE-5, 10BASE-T

J090001E.EPS

A 10BASE-T interface unit is used for an ACM71 while 10BASE-2, 10BASE-5, 10BASE-T
or 100BASE-TX Ethernet interface unit is used for the MELSEC.
A HUB or other peripherals must be used to convert between different interfaces.
SEE ALSO
Refer to the users manual of MELSEC series (MELSEC Ethernet Interface Unit Users Manual) for more
information on the network configuration method.

IM 33S01B30-01E

13th Edition : Dec.26,2005-00

<J9. MELSEC-A Communication (ACM71)>

J9-3

Operation Environment MELSEC-A

To run the package (ACM71) for communicating with MELSEC-A, 350Kbyte need to be
assigned to User C option area of FCS.

IMPORTANT
On Detailed Settings tab of FCS Constants Builder, the setting item SEBOL/User C Ratio
needs to be properly set in accordance with the communication program size.
If the default ratio 100 % is used, all resource is assigned for SEBOL and the communication program may fail when SEBOL program is running.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

J9-4

<J9.1 Communication Specifications MELSEC-A>

J9.1 Communication Specifications MELSEC-A

The section below explains the communication specifications when performing
subsystem communications with MELSEC-As.

Ethernet Communication Specifications

The Ethernet communication specifications include the following:
Communication protocol: TCP/IP

MELSEC-A Communication Specifications

The communication specifications specific to the MELSEC-A are as follows:
Table MELSEC-A Communication Specifications

Item

Description

Data code setting

Binary

Data communication
procedure

MELSEC communication Protocol-A compatible 1E frame

Available station(s)

Station(s) to which the E71 is installed

(access via MELSECNET is not allowed)

Communication
when CPU STOP

The setting in MELSEC-A may enable the communication event the controllers
CPU fails. However, when the communication error occurrence caused by the
breakage of wiring, communication will not continue.
J090101E.EPS

Communication Capacity
The communication capacity is as follows:
Maximum number of MELSEC-As allowed for communication: 5 (*1)
*1:

The maximum number of communication destination units for one FCS is irrelevant with the number of ACM71
modules installed in the FCS.

The maximum size of data allowed for communication, including data communicated via
other communication packages used for applicable FCSs, is the size allowed in the communication I/O data storage area (4000 words).
Communication data size in one frame is as follows:
Word device:

256 words

Bit device:

128 words (2048 bits)

One frame is defined in one line on communication builder. It is the same as restricted by
MELSEC-A protocol.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.2 Connecting FCS and MELSEC-A>

J9-5

J9.2 Connecting FCS and MELSEC-A

The following explains the configuration of connections between FCSs and
MELSEC-As.

Connection Configuration
An example of connections between FCSs and MELSEC-As is shown below:
Ethernet

HIS

HIS
Control bus

RDY
RCV
SND

CN1

RDY
RCV
SND

RDY
RCV
SND

CN1

CN1

FCS

RDY
RCV
SND

CN1

FCS

Ethernet

HUB

MELSEC-A

Router

MELSEC-A

HUB

MELSEC-A
J090201E.EPS

Figure Connection Example of MELSEC-As

IMPORTANT
When replace the malfunctioned ACM71 module with a new one, the communication
between the new ACM71 and the MELSEC may not be established properly, because the
hardware information in MELSEC is not refreshed. Restarting the MELSEC or reinitializing
the Ethernet interface can resolve this problem.

SEE ALSO
For more information about reinitializing the Ethernet interface, see the following:
Ethernet Interface Unit Users Manual of MELSEC

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

J9-6

<J9.2 Connecting FCS and MELSEC-A>

Addressing
The IP address and subnet mask must be specified for each ACM71 installed in the FCS.
Up to three IP addresses and subnet masks are specified for a single FCS, including the IP
address and subnet mask specified for the control bus of the FCS.
These three IP addresses must have different subnets, respectively.
HIS
Subnet 1
(control bus)

172.16.1.24
(255.255.0.0)
172.16.1.1
(255.255.0.0)

Subnet 2

172.16.1.2
(255.255.0.0)

Subnet 3

172.21.1.1
(255.255.0.0)

RDY
RCV
SND

CN1

RDY
RCV
SND

CN1

172.22.1.1
(255.255.0.0)

FCS

Ethernet

MELSEC-A

Control bus

MELSEC-A

RDY
RCV
SND

CN1

RDY
RCV
SND

CN1

FCS

Ethernet

MELSEC-A
Router
Ethernet

MELSEC-A

Subnet 4
(router destination, etc.)
J090203E.EPS

Figure Addressing

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.3 Accessible Devices MELSEC-A>

J9-7

J9.3 Accessible Devices MELSEC-A

The MELSEC-As internal data is called the device. Devices include bit devices and
word devices, as indicated below.
Bit device
Bit device refers to data where each bit has a meaning. An example of bit devices is an internal relay.
Word device
Word device refers to data where each word (1 word = 16 bits) has a meaning.
An example of word devices is a data register.

Accessible Devices
The range of accessible devices and device numbers, as well as the number of digits for a
device number differ according to the models of MELSEC-A CPU units. The device number
may be expressed as a decimal or hexadecimal value, depending on the type of device.
The following devices are accessible.
Table Accessible Devices in Six Digits
Device type

Bit device

Word device

Device name

Device number range

Expression

Input

X00000 to X007FF

Hexadecimal

Output

Y00000 to Y007FF

Hexadecimal

Internal relay

M00000 to M02047

Decimal

Special relay

M09000 to M09255

Decimal

Link relay

B00000 to B003FF

Hexadecimal

Annunciator

F00000 to F00255

Decimal

Timer (contact)

TS0000 to TS0255

Decimal

Timer (coil)

TC0000 to TC0255

Decimal

Counter (contact)

CS0000 to CS0255

Decimal

Counter (coil)

CC0000 to CC0255

Decimal

Data register

D00000 to D01023

Decimal

Special register

D09000 to D09255

Decimal

Link register

W00000 to W003FF

Hexadecimal

File register (*1)

R00000 to R08191

Decimal

Timer (present value)

TN0000 to TN0255

Decimal

Counter (present value)

CN0000 to CN0255

Decimal

Remarks

J090301E.EPS

*1:

Read or write the QnACPU/QCPU file register is prohibited.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

J9-8

<J9.3 Accessible Devices MELSEC-A>

Table Accessible Devices in Seven Digits
Device type

Bit device

Word device

Device name

Device number range (*1)

Expression

Input

X000000 to X0007FF

Hexadecimal

Output

Y000000 to Y0007FF

Hexadecimal

Internal relay

M000000 to M008191

Decimal

Special relay

M009000 to M009255

Decimal

Link relay

B000000 to B000FFF

Hexadecimal

Annunciator

F000000 to F002047

Decimal

Timer (contact)

TS00000 to TS02047

Decimal

Timer (coil)

TC00000 to TC02047

Decimal

Counter (contact)

CS00000 to CS01023

Decimal

Counter (coil)

CC00000 to CC01023

Decimal

Data register

D000000 to D006143

Decimal

Special register

D009000 to D009255

Decimal

W000000 to W000FFF

Hexadecimal

Link register
File register (*1)

R000000 to R008191

Decimal

Timer (present value)

TN00000 to TN02047

Decimal

Counter (present value)

CN00000 to CN01023

Decimal

Remarks

J090302E.EPS

*1:

Read or write the QnACPU/QCPU file register is prohibited.

SEE ALSO
Refer to the users manual of the applicable MELSEC-A CPU unit for more information on address
specification.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.4 Subsystem Data Storing Format MELSEC-A>

J9-9

J9.4 Subsystem Data Storing Format MELSEC-A

The following explains the format in which subsystem data acquired from a
MELSEC-A is stored in the FCS.

Bit Device MELSEC-A

Bit device data is stored in the communication I/O area, as shown below. If Reverse Bits
is enabled, the bit sequence in a word is reversed (and bits with the smaller numbers
comprise the most significant byte). On the Communication I/O Builder, the assigned size
m can be specified.
The multiple of 16 can be specified as n.
16 bits
n n n n n n
+ + + + + +
15 14 13 12 11 10

n
+
9

n
+
8

n
+
7

n
+
6

n
+
5

n
+
4

n
+
3

n
+
31

n
+
2

n
+
1

n=1

n
+
16

m=2

n+16 (m-1)+15

n+16 (m-1)
J090401E.EPS

Figure Image of Stored Bit Device MELSEC-A

Word Device MELSEC-A

When reading the word device data start from address n to address m, the word device
data are stored in the communication I/O area, as shown below.
16 bits

Contents of the nth register

Contents of the n+1th register

Contents of the n+m-1th register

J090402E.EPS

Figure Image of Stored Word Device MELSEC-A

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.5 Setting Items on System View MELSEC-A>

J9-10

J9.5 Setting Items on System View MELSEC-A

MELSEC

In this section, setting items on System View for MELSEC-A, the specific functionality and the recommended settings are explained.
SEE ALSO
For more information regarding to Detailed Setting tab on Create New IOM dialog box and subsystem
common settings, see the following:
Setting Items for ACM71 in J1.5.1, Overview of Setting Items on System View

For MELSEC-A, the setting items are as follows.

FCS Properties
Detailed Setting tab of Create New IOM dialog box
Set IP address, Subnet Mask, Attribute, Destination Address, Router Address
and Hop Count on this tab.
Similarly, select the following items in Detailed Setting tabs 2 through 5 in the
Create New IOM dialog box.
On any of the Detailed Setting tabs, 2 through 5, set Connected Device Name,
Option 1 (Response Timeout), Option 2 (Number of Retries Upon Response
Timeout), Option 3 (Interval of Connection Retries) and Option 4 (Port on
MELSEC-A).
After creating the new I/O module, the settings can be modified on Detailed Setting
tabs (2 to 5) of the I/O module property sheet.

FCS Properties MELSEC-A

Add [MELSEC_E] to Options on Constant tab of FCS property sheet.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.5 Setting Items on System View MELSEC-A>

J9-11

Create New IOM Dialog Box MELSEC-A

The following describes the settings on Detailed Setting tab of Create New IOM dialog box:
IP Address
Subnet Mask
Attribute
Destination Address
Router Address
Hop Count
SEE ALSO
For more information about setting items and setting details, see the following:
Setting Items for ACM71 in J1.5.1, Overview of Setting Items on System View

Similarly, select the following items in Detailed Setting tabs 2 through 5 in the Create New
IOM dialog box. Select any of the tabs of Detailed Setting 2 through 5.

Connected Device Name

Set MELSEC_E as the connection device name.

Option 1
This sets the tolerant time for getting response from the subsystem.
Recommended setting is 4 (seconds).

Option 2
This item sets the number of retries performed when a communication error occurs.
Recommended setting is 1 (time).

Option 3
Specify a time interval that the probe communication packets are sent to test if the connection can be established.
Recommended setting is 30 (seconds).

Option 4
The port number on MELSEC-A must be specified.
Since there is no default setting, this port number must be entered.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.6 Setting Items on Communication I/O Builder MELSEC-A>

J9-12

J9.6 Setting Items on Communication I/O Builder

MELSEC-A
In this section, setting items on Communication I/O Builder for MELSEC-A, the
specific functionality and the recommended settings are explained.
SEE ALSO
For an overview of the setting items on Communication I/O Builder, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

For MELSEC-A, the setting items are as follows.

Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

Element MELSEC-A
Element

With respect to the address of the subsystem data buffer, the element numbers are displayed on Communication I/O Builder. The element numbers are for display only, cannot be
set.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.6 Setting Items on Communication I/O Builder MELSEC-A>

J9-13

Buffer MELSEC-A
Buffer

This item sets the buffer used by a program.

Be sure to set the buffer, since this setting in the Communication I/O Builder is mandatory.

Program Name MELSEC-A

Program Name

Set the unit number, slot number and MELSEC_E as program name.
u-sProgramName
u:
s:
ProgramName:

Unit Number
Slot Number
MELSEC_E

Size MELSEC-A
Size

This item sets the data size (data length) from the head address set in Device & Address.
Must set the Size since this is a required setting item on Communication I/O Builder.
For MELSEC-A, the setting ranges are limited as follows, the unit is in Word.
Word Device:

1 to 256 Words

Bit Device:

1 to 128 Words (2048 points)

SEE ALSO
For more information about Size setting item, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

Port MELSEC-A
Port

Port 1 is set for use.

IP Address MELSEC-A
IP Address

This item sets the IP address of a MELSEC-A.

Station MELSEC-A
Station

The station number is not selectable.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.6 Setting Items on Communication I/O Builder MELSEC-A>

J9-14

Device & Address MELSEC-A

Device & Address

This item sets the head address of MELSEC-A data.

The address can be set in six or seven alphanumeric characters as shown below.
Input:

X0nnnn or X0nnnnn

Output:

Y0nnnn or Y0nnnnn

Internal relay:

M0nnnn or M0nnnnn

Special relay:

M0nnnn or M0nnnnn

Link relay:

B0nnnn or B0nnnnn

Annunciator:

F0nnnn or F0nnnnn

Timer (contact):

TSnnnn or TSnnnnn

Timer (coil):

TCnnnn or TCnnnnn

Counter (contact):

CSnnnn or CSnnnnn

Counter (coil):

CCnnnn or CCnnnnn

Timer (present value):

TNnnnn or TNnnnnn

Counter (present value):

CNnnnn or CNnnnnn

Data register:

D0nnnn or D0nnnnn

Special register:

D0nnnn or D0nnnnn

Link register:

W0nnnn or W0nnnnn

File register:

R0nnnn or R0nnnnn

SEE ALSO
For more information on address specification, see the following:
J9.3, Accessible Devices MELSEC-A

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.6 Setting Items on Communication I/O Builder MELSEC-A>

J9-15

Data Type MELSEC-A

Data Type

This item sets the data type of subsystem data.

The data type can be selected from among the following:
Input (16-Bit Signed)
Input (32-Bit Signed)
Input (16-Bit Unsigned)
Input (32-Bit Unsigned)
Input (32-Bit Floating)
Output (16-Bit Signed)
Output (32-Bit Signed)
Output (16-Bit Unsigned)
Output (32-Bit Unsigned)
Output (32-Bit Floating)
Input
Output

Reverse MELSEC-A
Reverse

This sets whether or not to make the bit or word arrangement in FCS in reverse order of the
subsystem data.
The following settings can be selected:
Bits
No
Words
However, when choosing [Bits], only the data of discrete inputs or discrete outputs can be
reversed. In this case, the default setting is [Bits].
Regarding to words, only the 32-bit analog inputs or the 32-bit analog outputs can be
reversed. In this case the default setting is [No].

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.6 Setting Items on Communication I/O Builder MELSEC-A>

J9-16

Scan MELSEC-A
Scan

Set whether to read the communication I/O analog data into the communication I/O data
buffer at the beginning of high-speed scan of the FCS.

Service Comment MELSEC-A

Service Comment

This item sets the comment.

Label MELSEC-A
Label

The name of the function block I/O terminal can be set as a user-defined label.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.7 MELSEC-A Communication Transactions>

J9-17

J9.7 MELSEC-A Communication Transactions

The following transactions will be explained in this section:
Response Timeout
Retries on Communication Error
Recovers from Response Timeout

Response Timeout
When ACM71 sends a command to MELSEC, ACM71 waits for the response of MELSEC.
A watchdog timer is used to count the waiting time, when the waiting time exceeds the
specified limit; a response timeout error will be initiated. The response timeout error is also
treated as a connection failure and triggers a TCP/IP connection retry for linking ACM71
and MELSEC.
The following circumstances will be explained:
Resending from ACM71
Resending from MELSEC

Resending from ACM71

When response timeout error occurs, ACM71 will perform TCP/IP retransmission. The
interval of retransmissions is doubled in proportion with the times of retransmissions. The
retransmission interval starts from 0.5 second and doubled to 1 second, and then 2, 4, 8,
16, 32 seconds. The prolonged retransmission intervals will be kept at 32 second.
The retransmissions are illustrated in the figure below supposing the response timeout
error is specified as 4 seconds. Before the response timeout error occurs, TCP/IP retransmissions are performed for 3 times.
SEE ALSO
For more information about response timeout, see the following:
Create New IOM Dialog Box - MELSEC-A in J9.5 Setting Items on System View

Response Timeout = 4sec

Response Timeout Error

0.5 to 1 sec
1 sec

2 sec

4 sec

8 sec

ACM71
Command

MELSEC
J090701E.EPS

Figure Resending from ACM71

When the timer for counting response time reaches limit, the response timeout error occurs. And the TCP/IP retransmissions will be carried out. When the connection is established again, the data exchange between the ACM71 and MELSEC will recover.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.7 MELSEC-A Communication Transactions>

J9-18

Under the following circumstances, ACM71 sends the close connection command.
ACM71 sends the open connection retries but the port on MELSEC is closed.
ACM71 response timeout error occurred.
SEE ALSO
For more information about connection closes on MELSEC, see the following:
Ethernet Interface Unit Users Manual of MELSEC

Resending from MELSEC

When the communication errors occur due to noises and thus the response is not obtained
for a specified time period, MELSEC will send the TCP transmission again. A time shorter
than the response timeout setting on ACM71 should be used as the TCP Retransmission
Timer Value of MELSEC Ethernet interface unit.
SEE ALSO
For more information about TCP retransmission timer setting of A series and QnA series, see the following:
Timer Settings in Ladder Program in J9.8.2 Communication Program on the MELSEC-A
For more information about TCP retransmission timer setting of Q series, see the following:
Q Series in J9.8.1 Setting Switches of Ethernet Interface Units

Response Timeout Error

Response Timeout
ACM71
Command
(Request)

ACK (Reception acknowledgement)

Response
(with requested data)
MELSEC
TCP Retransmission
Timer Value

J090702E.EPS

Figure Resending from MELSEC

When ACM71 is waiting for the response from MELSEC, if an error occurs in the
communication line and the response timeout error occurs, ACM71 will continue waiting
until the Keep Alive interval becomes timeout. ACM71 will close the connection when the
Keep Alive interval expires, and carry out the connection reties according to the retransmission cycle.
TIP
The Keep Alive feature checks the Ack signals exchanged between the connected destinations so as to
ensure the connection is normal.
When one port is closed and the Ack signal cannot be received, the other port of the connection will close
itself.
The keep-alive timeout of ACM71 is about 7 minutes (fixed).

IM 33S01B30-01E

11th Edition : Oct.28,2004-01

<J9.7 MELSEC-A Communication Transactions>

J9-19

Retries Upon Connection Error

When an open connection request from ACM71 is returned with an error, ACM71 will retry
the open request. If the request does not get any replay, this type of retry will not be carried
out. For an example, when ACM71 get an error reply and then ACM71 will send the request
for one more time (if the number of retries is 1). Thus the handshakes for establishing the
connection are two times.
In the example below, the first open connection request (SYN) is returned with an error
(RST+ACK), then the open connection request is sent again. When the proper response is
returned, the connection becomes established.
Connection
Retry

Connection Opened

ACM71
SYN

SYN

RST+ACK

ACK
SYN+ACK

MELSEC
J090703E.EPS

Figure Retries Upon Connection Error

Recovery Scheme
If the connection between ACM71 and MELSEC is not established, or if the ACM71 closed
the connection, the connection request will be sent periodically. Data exchange will be
carried out after the connection is established.
SEE ALSO
For more information about communication retries, see the following:
Create New IOM Dialog Box - MELSEC-A in J9.5 Setting Items on System View

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.8 Settings on Subsystem MELSEC-A>

J9-20

J9.8 Settings on Subsystem MELSEC-A

To perform subsystem communication with a MELSEC, appropriate settings are
required for the Ethernet interface unit and other items on the MELSEC side.
This section explains the setting switches of the Ethernet interface unit and a communication program.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.8 Settings on Subsystem MELSEC-A>

J9-21

J9.8.1 Setting Switches of Ethernet Interface Units

A Series
The following explains the setting switches of the A series Ethernet interface units
(AJ71E71N-B2, AJ71E71N-B5, AJ71E71N-T, A1SJ71E71N-B2, A1SJ71E71N-B5,
A1SJ71E71N-T, AJ71E71-S3, A1SJ71E71-B2-S3, A1SJ71E71-B5-S3).
Table Setting Switches of the A Series Ethernet Interface Units
Switch name
AJ71E71N
-B2/B5/T
A1SJ71E71N A1SJ71E71
-B2-S3
-B2/B5/T
/B5-S3
AJ71E71
-S3

Setting item

Description

Setting

SW1

SW1

Selects the line processing in the event of a TCP ULP

Line processing timeout error.
OFF: Closes the line in the event of a TCP ULP
setting in the
timeout error.
event of a TCP
ON: Keeps the line open even if a TCP ULP
timeout error
timeout error occurs.

SW2

SW2

Data code
setting

SW3
SW4
SW5
SW6

SW7

SW8

Selects the data code type of communication data with

other nodes.
OFF: Communicates using binary code.
ON: Communicates using ASCII code.
Not used (fixed to OFF)

OFF

OFF

OFF

SW3

CPU
communication
timing setting

Enables or disables writing of data from other nodes

while the PLC CPU is running.
OFF: Does not allow data to be written from other nodes
while the PLC CPU is running.
ON: Allows data to be written from other nodes while the
PLC CPU is running.

SW4

Initialization
timing setting

Selects the timing at which the initialization processing is

started up.
OFF: Quick start (start without delay)
ON: Normal start (start following the delay time of
20 seconds)

ON

OFF

J090801E.EPS

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.8 Settings on Subsystem MELSEC-A>

J9-22

QnA Series
The following explains the setting switches of the AnA series Ethernet interface units
(AJ71QE71N-B2, AJ71QE71N-B5, AJ71QE71N-T, A1SJ71QE71N-B2, A1SJ71QE71N-B5,
A1SJ71QE71N-T, AJ71QE71, AJ71QE71-B5, A1SJ71QE71-B2, A1SJ71QE71-B5).
Table Setting Switches of the QnA Series Ethernet Interface Units
Switch name
SW1

SW2

SW3

Setting item

Setting

Description

Line processing
setting in the
event of a TCP
timeout error

Selects the line processing in the event of a TCP ULP timeout error.
OFF: Closes the line in the event of a TCP ULP timeout error.
ON: Keeps the line open even if a TCP ULP timeout error occurs.

OFF

Data code setting

Selects the data code type of communication data with other nodes.
OFF: Communicates using binary code.
ON: Communicates using ASCII code.

OFF

Automatic startup
mode setting

Sets the startup procedure when the QE71 starts up.

OFF: Operates according to Y19 (initialization processing request signal)
ON: After power up or reset, reads parameters within the EEPROM to the
OFF
buffer memory regardless of Y19 (initialization processing request signal),
and performs initialization processing according to the parameters.

SW4
SW5
SW6

Not used (fixed to OFF)

OFF

SW7

CPU
communication
timing setting

Enables or disables writing of data from other nodes while the PLC CPU
is running.
OFF: Does not allow data to be written from other nodes while the PLC
CPU is running.
ON: Allows data to be written from other nodes while the PLC CPU is
running.

SW8

Initialization
timing setting

Selects the timing at which the initialization processing is started up.

OFF: Quick start (start without delay)
ON: Normal start (start following the delay time of 20 seconds)

ON

OFF
J090802E.EPS

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

J9-23

<J9.8 Settings on Subsystem MELSEC-A>

Q Series
The setting switches are not available on Q Series QJ71E71-B5/QJ71E71-100/QJ71E71/
QJ71E71-B2. For setting the Ethernet parameters, the MELSEC engineering tool (GX
Developer) should be used.
Table Settings of the Q Series Ethernet Interface Units
Switch name

Ethernet
operational
settings

Setting item

Description of setting

Setting

Communication data code

setting

Select the data code type when communicating

data with other nodes.

Binary code
communication

Initial timing setting

Select the waiting state of the socket of the

Ethernet unit.
Do not wait for OPEN.
Always wait for OPEN (OPEN from the
ladder program).

Always wait for OPEN

Input format

Select the IP address input format

Decimal

IP address

Specify the IP address of the local station

IP address of the
local station

Set whether or not to permit data write

operations from other nodes when the PLC CPU
is in the RUN state.

Check mark (enable)

TCP ULP Timer

Packet existance time at the time of TCP data

transmission. (x500 ms)

40 (20 seconds)

TCP Zero Window

Timer

The check interval of a receivable state.

(x500 ms)

4 (2 seconds)

TCP Retransmission
Timer

The retransmission interval at the time of TCP

data transmission. (x500 ms)

4 (2 seconds)

TCP End Timer

Check waiting time at the time of TCP closing

processing. (x500 ms)

4 (2 seconds)

Waiting time to division data arrival. (x500 ms)

3 (1.5 seconds)

Waiting time of a response. (x500 ms)

42 (21 seconds)

IP address
setting

Enable write at RUN time

IP Setup Timer
Ethernet
Timers Response Monitoring
Initial Settings
Timer

Destination existence
Time period between the physical connection
confirmation starting
36 (18 seconds)
breakages and connection probe starts. (x 500ms)
interval

Ethernet
open settings

Switch name

Destination existence
confirmation interval Interval of Connection Probes (x 500ms)
timer

10 (5 seconds)

Destination existence
Number of Connection Probes
confirmation resend
timer

Protocol

Select the communication method (protocol).

TCP/IP

Open system

Select the connection open system.

Unpassive open

Fixed buffer

Select the usage of the fixed buffer.

Send

Fixed buffer communication

Select whether or not to use the communication

procedure via the fixed buffer.

Procedure exist

Pairing open

Select whether pairing open is used or not.

No pairs

Existence confirmation

Select whether the continued existence of a

destination station for a connection should be
confirmed or not.

Confirm

Local station port No.

Set the local stations port No.

Set the port in the range of 401h to 1387h
(1025 to 4999) or 138Bh to FFFEh
(5003 to 65534). When communicated with the
same ACM71, the same port No. in MELSEC
PLCs should be used.

500h

Setting item

Description of setting

Setting
J090812E.EPS

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.8 Settings on Subsystem MELSEC-A>

J9-24

J9.8.2 Communication Program on the MELSEC-A

To perform subsystem communication with the A series or QnA series Ethernet
interface unit, a ladder program must be created on the MELSEC.
A ladder program is not necessary if Q series is used as an Ethernet interface unit.

Communication Operation
Communication between the MELSEC-A communication package (ACM71) and a
MELSEC is performed as shown below.
MELSEC-A
START

For A series and QnA series

Ethernet interface units, this
part needs to be handled by
Ladder programs.

Set communication
parameters
MELSEC-A Communication Package (ACM71)
Initialize
START
Open settings of
each port
Create a socket
Open processing
Connection request

Connect
Receives Connect

Send a command

Command
Receives commands

Response
Receive data

Disconnect

Response with
requested data

Disconnect
Close processing

J090803E.EPS

Figure Communication Operation

Since the A series and QnA series Ethernet interface unit only processes communication
commands, the following three functions must be created using the CPU ladder program.
Parameter settings
Processing until the line connection
Reconnection processing following the line disconnection

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.8 Settings on Subsystem MELSEC-A>

J9-25

Timer Settings in Ladder Program

The default timer settings for the sample ladder program are listed in the table below.
Table Timer Settings For The Sample Ladder Program

Object

Name

MELSEC
Ethernet
Interface Unit
(*1)

Setting (*2)

TCP Retransmission Timer Value (Timer01)

4 (2 Seconds)

TCP ULP Timeout Value (Timer02)

40 (20 Seconds)

TCP Zero Window Timer Value (Timer03)

4 (2 Seconds)

Description
TCP resend for 9 times.
(20/2) -1= 9

TCP End Timer Value (Timer04)

4 (2 Seconds)

TCP Setup Timer Value (Timer05)

3 (1.5 Seconds)

Response Monitoring Timer Value (Timer06)

42 (21 Seconds)

Destination Existence Check Start Interval Timer

Value (Timer07)

36 (18 Seconds) (t0)

Destination Existence Check Interval Timer

Value (Timer08)

10 (5 Seconds) (t1)

Number of Retransmit Tries For Destination

Existence Check (Number)

3 times (n)

Existence
Timeout = t0+{t1x(n-1)}
=18+{5x(3-1)}
=28 Seconds

J090809E.EPS

*1:
*2:

The unit of timer is 500msec.

The corresponding time is indicated in the parentheses.

When changing the above timer settings, the following rules should be observed:
Rule 1
Connection
Monitoring Time

Existence
Timeout

Response
Monitoring 
Timer Value

TCP ULP
Timeout Value

TCP End
Timer Value

TCP
Retransmission
Timer Value

Response
Timeout

TCP Setup
Timer Value

Rule 2
TCP
Retransmission
Timer Value

TCP
Zero Window
Timer Value
J090810E.EPS

SEE ALSO
For more information about Connection Monitoring Time and Response Timeout, see the following:
Create New IOM Dialog Box - MELSEC-A in J9.5 Setting Items on System View

Ladder Program
A sample ladder program for the communication between ACM71 and MELSEC-A is
shown as follows. This is made for connecting A series AJ71E71 via TCP/IP communication with Ethernet interface. For connecting QnA series, the numbers of the buffers and
memories should be different.
The program is outline as follows.
There are two procedures for establishment of connections and multiple ports can be
opened at the same time for the connections.
When a connection is closed, the port waits for the next connection. After the connection is closed, 500 ms delay is required for setting the open request.
IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.8 Settings on Subsystem MELSEC-A>

J9-26

Sample Ladder Program

This sample program is created with the assumption that the MELSEC Ethernet Interface
unit is inserted in the Slot 0 of the base unit.
SEE ALSO
For more information about device relay numbers when the interface unit is installed in a different slot,
see the MELSEC-A Programming Manual.

M9038
DTO

H0

H0000

DTO

H0

TO

H0

H0C0A80001 K1 Set IP address

(192.168.0.1)
H01C0 H0FFFFFF00 K1 Set subnet mask
(255.255.255.0)
H0003 K500
K1 Engineering unit of timers is 500msec

TO

H0

H000A K40

K1 TCP ULP Timeout (Timer02) =40 (20sec)

TO

H0

H000B K4

TO

H0

H000C K4

K1 TCP Zero Window Timer

Value (Timer03) = 4 (2sec)
K1 TCP Retransmission Timer
Value (Timer01) = 4 (2sec)

TO

H0

H000D K4

K1 TCP End Timer Value (Timer04) = 4 (2sec)

TO

H0

H000E K3

K1 IP Setup Timer Value (Timer05) = 3 (1.5sec)

TO

H0

H000F K42

K1 Response Monitoring Timer

Value (Timer06) = 42 (21sec)

TO

H0

H0007

K36

K1 Connection probe delay (Timer07)

= 36 (18sec)

TO

H0

H0008

K10

K1 Connection probe interval (Timer08)

= 10 (5sec)

TO

H0

H0009

K3

K1 Number of connection retries (Number) = 3

TO

H0

H01F0 H8000
SET

K1 Handshake during stop

Y0019 Set initialization request ON

X001A
FROM

H0

H0050

D100

K1 Read initialization error code

TO

H0

H0050

K0

K1 Clear initialization error code

RST
M0002 X0010

Y0019 Set initialization request OFF

X0019 Y0008
TO

H0

H0010

H8002

TO

H0

H0018

K1280
SET

X0018 Y0008

K1 Settings for Connection No.1

TCP/Unpassive/Negotiation/Probe
K1 Set port number for Connection No.1
(1280)
Y0008 Set connection No.1 open request ON

X0010

<>

K0 D101

FROM

H0

H005D D101

K1 Get connection No.1 open error code

TO

H0

H005D K0

K1 Clear connection No.1 open error code

FROM

H0

H01F0 D110

K1

WAND H0FFFE
TO

H0

H01F0 D110

D110

Set connection probe during STOP

for connection No.1 OFF

K1
Set connection No.1 open request OFF

RST

Y0008

SET

M0002 Deny connection No.1 open request

M0002

K5
T0

T0
RST

M0002

Re-open for the connection No.1

500 ms delay; Reopen starts when
the timer's timeout.
J090804E.EPS

Figure Sample Program (1/2)

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.8 Settings on Subsystem MELSEC-A>

J9-27

X0010
PLF

M0000

RST

Y0008

SET

M0002

M0000

When close the connection No.1, Set

the open request OFF

X0010
FROMP H0

H01F0 D110
WORP H0001

M0012 X0011

X0019

D110

Set connection probe during STOP for

connection No.1 ON

TOP

H0

H01F0 D110

K1

TO

H0

H0011

TO

H0

H001F K1280

K1 Settings for Connection No.2

TCP/Unpassive/Negotiation/Probe
K1 Set port number for Connection No.2 (1280)

Y0009
H8002

SET
X0018 Y0009

K1

Y0009 Set connection No.2 open request ON

X0011

<>

K0 D102

FROM

H0

H0067

D102

K1 Get connection No.2 open error code

TO

H0

H0067

K0

K1 Clear connection No.2 open error code

FROM

H0

H01F0 D110
WAND H0FFFD

TO

H0

H01F0 D110

K1
D110

Set connection probe during STOP for

connection No.2 OFF

K1

RST

Y0009 Set connection No.2 open request OFF

SET

M0012 Deny connection No.2 open request

M0012

K5
T1

T1
RST

M0012

PLF

M0010

RST

Y0009

SET

M0012

Re-open for the connection No.2

500 ms delay; Reopen starts when the
timer's timeout.

X0011
M0010

When close the connection No.2, Set

the open request OFF

X0011
FROMP H0

H01F0 D110
WORP H0002

TOP

H0

H01F0 D110

K1
D110

Set connection probe during STOP for

connection No.2 ON

K1

X001C
SET

Y0017

Request for COM, ERR, LED light-off.

END
J090811E.EPS

Figure Sample Program (2/2)

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

J9-28

<J9.8 Settings on Subsystem MELSEC-A>

Data Registers
The table below lists the data registers used in the sample program.
If any of these registers is already in use, use another register.
Table List of Data Registers
Register Number

Description

Data

D100

Initial Error Code

Holds the error code of the initial error.

D101

Connection No.1 Open Error

Code

Holds the error code of the connection

No.1 open error

D102

Connection No.2 Open Error

Code

Holds the error code of the connection

No.2 open error

D110

Toggle of the handshake

during STOP

Toggles the handshakes during STOP

J090805E.EPS

Timers
The following is the timer used in the sample program.
If this timer is already in use, use another timer.
SEE ALSO
When changing the timer, note that the timer settings differ according to the timers resolution. Refer to the
users manual for the applicable PLC CPU for more information.

Table List of Timers

Timer Number

Description

Timeout Value

T0

Delay timer for re-opening connection No1.

500 ms

T1

Delay timer for re-opening connection No2.

500 ms
J090806E.EPS

IM 33S01B30-01E

11th Edition : Oct.28,2004-01

<J9.8 Settings on Subsystem MELSEC-A>

J9-29

Device Relays (X0 to X1F, Y0 to Y1F)

The device relays used in the sample program are listed below.
SEE ALSO
For more information about device relay numbers when the interface unit is installed in a different slot,
see the MELSEC-A Programming Manual.
For more information about device relay, see MELSEC-A Ethernet Interface Unit Users Manual.

Table Device Relays

Device Number

Description

X10

Open Connection No.1 Complete

X11

Open Connection No.2 Complete

X18

Open Connection Error

X19

Initialization End Successfully

X1A

Initialization End with Error

X1C

COM. ERR. LED Light On

Y8

Request to Open Connection No.1

Y9

Request to Open Connection No.2

Y17

COM. ERR. LED Light Off

Y19

Request to Initialize
J090807E.EPS

IM 33S01B30-01E

11th Edition : Oct.28,2004-01

<J9.8 Settings on Subsystem MELSEC-A>

J9-30

Buffer Memory
SEE ALSO
For more information on writing and reading the buffer memory when interface unit is installed in a different slot, see the MELSEC-A Programming Manual.
For more information about buffer memory, see MELSEC-A Ethernet Interface Unit Users Manual.

The buffer memories used in the sample program are listed in the following table.
Table Buffer Memories
A Series
Address

QnA Series
Address

H0000

H0000

H0003

H0007
H0008

Description

Size

Local host IP

2 words

Time unit of timers (500 msec or 2000 msec)

1 word

H0011

Connection probe delay

1 word

H0012

Connection probe interval

1 word

H0009

H0013

Number of connection probes

1 word

H000A

H000B

TCP ULP timeout value

1 word

H000B

H000C

TCP zero window timer value

1 word

H000C

H000D

TCP retransmission timer value

1 word

H000D

H000E

TCP end timer value

1 word

H000E

H000F

IP setup timer value

1 word

H000F

H0010

Responce monitoring timer value

1 word

H0010

H0020

Settings for connection No.1

1 word

H0011

H0021

Settings for connection No.2

1 word

H0018

H0028

Port for connection No.1

1 word

H001F

H002F

Port for connection No.2

1 word

H01F0

H0067

Handshake during stop

1 word

H0050

H0069

Code of initialization error

1 word

H005D

H007C

Code of connection No.1 open error

1 word

H0067

H0086

Code of connection No.2 open error

1 word

H01C0

H0200

Subnet mask

2 words
J090808E.EPS

Other Elements
Other elements used in the sample program are listed as follows. If the element is already
reserved by other program, a different element can also be used.
M9038 : ACPU Special Relay (When CPU starts run, turns ON for only one scan-period)
M0000 : Flag for closing connection No.1 request
M0002 : Flag for rejecting connection No.1 open request
M0010 : Flag for closing connection No.2 request
M0012 : Flag for rejecting connection No.2 open request

IM 33S01B30-01E

11th Edition : Oct.28,2004-01

<J9.9 System Alarm Messages Specific to MELSEC-A>

J9-31

J9.9 System Alarm Messages Specific to MELSEC-A

This section describes the error codes of system alarm messages specific to
MELSEC-A.

Error Code
The table below shows the error codes specific to the MELSEC-A.
Table Error Code
Error code

Description

A3B0

No response

A3B2

Invalid address name

A3B4

Address number error

A3B5

Address range error

A3B7

Number of communication processing points exceeded

A3B8

Assigned communication I/O buffer size error

A3B9

IP address error

A3BA

Number of subsystem exceeds the limit

A3BB

Card option error

A3BC

Card option setting error

A3D0

PC number error (10H)

A3D1

Mode error (11H)

A3D2

Special function unit specification error (12H)

A3D3

Program step No. specification error (13H)

A3D8

Remote error (18H)

A3E0

Link error (20H)

A3E1

Special unit bus error (21H)

A3FF

Other errors
J090901E.EPS

The A3D0 and succeeding codes indicate errors generated when an error code is received
from the MELSEC-A.
The error codes of MELSEC are indicated in parentheses.
SEE ALSO
Refer to the MELSEC-A Users Manual for more information on error codes.
For error codes pertaining to Ethernet communications, see the following:
J2.4, System Alarm Messages Specific to Ethernet Communication

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.10 Transmission Time between Communication Card and MELSEC-A>

J9-32

J9.10 Transmission Time between Communication

Card and MELSEC-A
This section explains the transmission time for communication between the communication card and a MELSEC-A.

Communication Performance
The transmission time for communication between the communication card and a
MELSEC-A is calculated as a sum of T1 through T4 as shown below.
Communication begins

Communication
card

Communication complete

Request
generation
processing

Data

MELSEC-A

Data

Communication
processing
T1

T2

T3

T4

T1: Request generation time. Approximately 50 ms.

T2: Transmission time of request
T3: Response creation time (PLC CPU processing time)
T4: Transmission time of response
J091001E.EPS

Figure Time Chart for Communication between Communication Card and MELSEC-A

SEE ALSO
Refer to the MELSEC-A Users Manual for more information on T2 through T4.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.10 Transmission Time between Communication Card and MELSEC-A>

J9-33

Using this package to communicate with MELSEC-A in parallel to all the MELSEC-A PLCs
in sequence with their IP addresses. After processing a request of one MELSEC-A, it starts
to process the request of the next.
One transmission only handles one communication assignment on the builder. For an
example, assume there are two MELSEC-A PLCs, one has three communication assignments while the other has only one, transmissions are performed in the following sequence. However, communication delay caused in MELSEC-A PLC is not considered in
this assumption.
Assignment 1
Assignment 4

Subsystem 1

Subsystem 2

Assignment 1

Assignment 4

Assignment 2
Assignment 3

Assignment 2
Repeat
Assignment 4
Assignment 3
Assignment 4

J091003E.EPS

Figure Transmission Sequence

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.10 Transmission Time between Communication Card and MELSEC-A>

J9-34

Calculation Example
The following shows an example of calculating the transmission time when reading data of
100 data registers.
Assume that the scan time for the MELSEC is 50 ms.
The communication time is calculated based on the following conditions:
Comparing with other processing times, the transmission times of request (T2) and response (T4) are trivial, all together about 1 to 5 milliseconds. Thus in this calculation, T2 +
T4 = 5 ms.
The MELSEC-A CPUs scan period is 50 ms.
Transmission time of request (T2) + Transmission time of response (T4) = 5 ms
PLC CPU processing time (T3) = Number of points / Number of points processed in one
scan scan time
= 100 / 6450
100 ms (Round up to scan time)

Total time = Ti = 50 + 5 + 100 = 155 (ms)

i=1

J091002E.EPS

TIP
Note that the calculation is approximate since the actual communication time may vary by a wide margin
depending on network traffic.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

<J9.11 Troubleshooting>

J9-35

J9.11 Troubleshooting
This section describes how to troubleshoot problems.

Flowchart for Trouble Shooting

A troubleshooting flowchart is shown on the next page.
If a problem occurs, use the flowchart to check and remove the cause of the problem.

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

J9-36

<J9.11 Troubleshooting>

Unable to perform data communication.

Check to see if the Ethernet interface unit is

installed and the PLC CPU is running.
Is the CPU modules RUN LED lit?

NO

Check for an error.

Is the ERROR LED lit?

Refer to the users manual of the

applicable PLC CPU for troubleshooting,
and correct the error.

YES

NO

YES

Set the PLC CPU to run.

Check the condition of the

Ethernet interface unit.
Is the RUN LED of the
Ethernet interface unit lit?

NO

Reset the PLC CPU.

If the RUN LED of the Ethernet interface unit is not yet lit even after the CPU
is reset, a hardware error in the Ethernet interface unit is suspected.
Replace the Ethernet interface unit.

NO

Proper initialization settings are not performed in the ladder program.

Monitor the ladder program and check the error code of the initialization
settings and correct the error.

YES

Is the RDY LED on the

Ethernet interface unit flashing?

YES

Are the LEDs set to wait for line

connection (BUF1 to BUF8) in the
ladder program lit?

NO

YES

Is the BSY LED flashing?

YES

NO

Check the Ethernet interface unit

communication condition settings.

Is the data code of

the communication condition
set to binary?

NO

Set the data code of the

communication condition
to binary.

YES
Communication between the ACM71 and
the MELSEC-A Ethernet interface unit is
performed normally.
The communication I/O definitions are
suspected as the cause of the problem.
Check the system alarm message and
correct the builder setting causing the error.

A communication error caused by the

MELSEC-A communication package is
suspected.
Check the system alarm message and
correct the builder setting causing the error.

J091101E.EPS

Figure Flow Chart for Trouble Shooting (1/2)

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

J9-37

<J9.11 Troubleshooting>
I

Is the Ethernet interface

unit waiting for OPEN in the
ladder program?

NO

Reset the PLC CPU and run it again.

If the Ethernet interface still doesn't wait
for OPEN after the CPU starts running for
the second time, a problem in the ladder
program is suspected. Check the OPEN
error and correct the cause of the error.

NO

Lock the cable securely.

NO

Set the 10BASE-5 and 10BASE-2

switches properly.

NO

Provide the external power supply.

NO

Set the mode setting to ONLINE (0).

NO

A problem is suspected on the line.

Check the network paths.

YES

Is the cable securely connected?

In the case of AJ71E71-S3

or AJ71Q71

YES

Are the switches on the

10BASE-5 and 10BASE-2 set
properly?
YES
In the case of 10BASE-5
connection
Is the external power
supply provided?

YES

Is the mode setting ONLINE (0)?

YES

Does the PING go through?

YES
A communication error caused by the
MELSEC-A communication package is
suspected.
Check the system alarm message and
correct the builder setting causing the error.
J091102E.EPS

Figure Flowchart for Trouble Shooting (2/2)

IM 33S01B30-01E

11th Edition : Oct.28,2004-00

Blank Page

<J10. Modbus Communication (ACM11, ACM12)>

J10-1

J10. Modbus Communication (ACM11,

ACM12)
The Modbus communication package is a subsystem communication package
designed for the Modicon PLC using Modbus protocol manufactured by the
Schneider Electric SA (hereinafter referred to as Modicons) and the Memocon-SC
PLC using Modbus protocol manufactured by Yasukawa Electric (hereinafter referred to as Memocon-SC). The Modicon and Memocon-SC subsystems are collectively referred to as Modbus PLC. By using the Modbus communication package,
communication between the FCS and Modbus PLC can be performed without a
customized program.
This chapter explains the communication between the Modbus and FCS among the
subsystem communication packages.
SEE ALSO
Regarding the functions common to different subsystem communication packages, see the following:
J1, General Information Regarding to Subsystem Communication

Applicable Models Modbus

For the Modbus communication package, the following product is available:
PFS9053 CS 1000 Modbus communication package (ACM11, ACM12) (single type/
dual-redundant type)
LFS9053 CS 3000 Modbus communication package (ACM11, ACM12) (single type/
dual-redundant type)
With the Modbus communication package, Modbus PLC are connected to the communication I/O module (ACM11/ACM12) and subsystem communications are performed between
the FCS and Modbus. The following models of Modbus PLC can be connected to ACM11
or ACM12:
Schneider Electrics 484, 584, 584L, 884, 984, 984A, 984B, 984X, Micro84
Yasukawa Electrics Memocon-SC U84, 584, 684H, 694H, R84H-M, GL60S, GL20
TIP
Connections for a Modbus PLC other than those listed above are available as options. To connect a
Modbus PLC not listed above, please contact Yokogawa Electric Co.

SEE ALSO
For further details when performing dual-redundant communication, see the following:
J10.9, Dual-Redundant Communication Modbus

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J10.1 Communication Specifications Modbus>

J10-2

J10.1 Communication Specifications Modbus

The section below explains the specifications when performing subsystem communication with a Modbus PLC .

Communication Capacity Modbus

The capacity specific to Modbus when performing subsystem communication with a
Modbus PLC is indicated below:
Table Capacity of Communications between FCS and Modbus PLC
Item

Maximum quantity

Explanation of words

Amount of data that can be communicated with

one communication module

500 words
(1 word=16 bits)

Restricted by the maximum amount

may be accessed from the regulatory
control block/sequence control block.

Number of subsystem stations that can be

communicated with one communication module

30 stations

Data size in one communication frame

125 words

One frame is defined in one line on

the builder. It is the same as
restricted by MODBUS protocol.
J100101E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J10-3

<J10.1 Communication Specifications Modbus>

Transmission Specifications Modbus

The transmission specifications when performing subsystem communication with the
Modbus PLC are indicated below:
Table Transmission Specifications Modbus
Item
Interface

Description

Remark

RS-232C (D-sub 25 pin)

ACM11

RS-422

ACM12

Transmission method

Half duplex

Synchronization method

Start-stop synchronization

Baud rate

1200, 2400, 4800, 9600,

[19200] bps

Transmission procedure

Modbus protocol
(RTU mode)

Transmission code

Binary

Data type

Time monitoring

Text frame

(*1)

Start bit

Data bit

Must specify 8 on the New

IOM dialog box called from
System View.

Parity bit

None, [even], odd

(*1)

Stop bit

Transmission enable
monitoring time

1000 ms

Reception character interval

monitoring time

10 ms

Start of text

None

End of text

None

XON/XOFF flow control

NO

RS control

NO

(*1)

DR check

YES

(*1)

CD check

NO

(*1)

No response time setpoint

0 to 99 seconds [4 seconds]

(*1)

Number of communication retries upon error

0 to 99 times [1 time]

(*1)

Recovery communication time interval

0 to 999 seconds
[30 seconds]

(*1)

Transmission wait time

1 second

Number of words that can be handled in one

communication packet

125 words

Item

Description

Remark
J100102E.EPS

Note: [ ] indicates the recommended settings.

*1:
This can be changed using the property dialog box called from System View.

IMPORTANT
When performing subsystem communication with the Modbus PLC, be sure to specify 8
bits for the data bit length on System View. A communication error will occur if 7 bits is
specified.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.1 Communication Specifications Modbus>

J10-4

Simultaneity of Communication Data Modbus

The Modbus PLC guarantees the simultaneity of communication data in 16 bit units.
Therefore, simultaneity of data in 16 bit units is guaranteed between the communication
module and the Modbus PLC.
TIP
The Modbus PLC processes data in 16 bit units. Simultaneity of data in 32 bit units depends on the
application software for the Modbus PLC. It is necessary to set 32-bit data within the same control cycle
using the Modbus PLC application software to guarantee simultaneity of communication data in 32 bit
units.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.2 Connecting FCS and Modbus PLC>

J10-5

J10.2 Connecting FCS and Modbus PLC

This chapter explains the connection type and cable connections between FCS and
Modbus PLC.

Connection Type Modbus

An example of the connection between FCS and Modbus PLC is shown below.
HIS

Control bus

FCS

ACM11 (RS-232C communication module)

RDY
RCV
SND

CN1

RDY
RCV
SND

CN1

RS-232C

MODEM

RS-232C

MODEM

Modbus PLC

MODEM

Modbus PLC

MODEM

Modbus PLC

AMN33 (Nest for communication module)

J100201E.EPS

Figure Connection Example between CS 1000/CS 3000 and Modbus PLC

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.2 Connecting FCS and Modbus PLC>

J10-6

Cable Connection when Using the ACM11 Modbus

The cable connection when connecting the ACM11 and Modbus PLC is indicated below.
The connector shape varies according to the computer link unit of the connected Modbus
PLC.
A modem connection is required between the ACM11 and Modbus PLC, but if the length of
the RS-232C cable between the ACM11 and Modbus PLC is 15 meters or less and if they
share the same grounding system, then it is possible to connect them directly.

IMPORTANT
The length of the RS-232C cable between the ACM11 and modem and between the modem and Modbus PLC must be 15 meters or less.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.2 Connecting FCS and Modbus PLC>

J10-7

Connection to a Modbus PLC Having a D-sub 25 Pin Connector

Use a cable with RS-232C D-sub 25 pin connectors when connecting Modbus PLC to
ACM11 module.
Table RS-232C D-sub 25 Pin Connector Specifications Modbus
Pin number

Signal name

Direction of signal

Title

Description

ACM11 Modbus PLC

1

FG

Frame ground

SD

Send data

Security grounding

RD

Receive data

RS

Request to Send

When there is a send request, ON is output

CS

Clear to Send

When OFF, the ACM11 does not transmit to the

outside

DR

Data Ready

Detects whether sending and receiving are allowed

at correspondent Transmits only when ON

SG

Signal ground

CD

Carrier Detected

20

ER

Data Terminal Ready

When sending and receiving are allowed, ON is

output
J100202E.EPS

SEE ALSO
For details on safety grounding, see the followings:
Figure Cable Connection between Modem and ACM11
Figure Cable Connection between Modbus PLC and ACM11 (when Modbus PLC Uses an RS-232C Dsub 25 Pin Connector, and directly Connected )

Pin No. 25

Pin No. 14

Pin No. 13

Pin No. 1
J100203E.EPS

Figure Pin Assignment of the RS-232C D-sub 25 Pin Connector Modbus

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.2 Connecting FCS and Modbus PLC>

J10-8

The following shows when the Modbus PLC and ACM11 are connected via a modem and
when they are connected directly without a modem.
SD
RD
RS
CS
ACM11

DR
SG
CD
ER
FG

20

20

Sheathed cable

SD
RD
RS
CS
DR

Modem (*1)

SG
CD
ER
FG

Protective grounding
(100 ohms or less)
J100204E.EPS

*1:

As a rule, use a modem where FG and SG are connected.

Figure Cable Connection between Modem and ACM11

SD
RD
RS
CS
ACM11

CD
DR
ER
SG
FG

20

20

Sheathed cable

SD
RD
RS
CS
CD

Modbus PLC

DR
ER
SG
FG

Protective grounding
(100 ohms or less)
J100205E.EPS

Figure Cable Connection between Modbus PLC and ACM11

(when Modbus PLC Uses an RS-232C D-sub 25 Pin Connector, and directly Connected)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.2 Connecting FCS and Modbus PLC>

J10-9

Connection to a Modbus PLC Having a D-sub 9 Pin Connector

Use a cable with an RS-232C D-sub 9 pin connector and an RS-232C D-sub 25 pin connector when directly connecting ACM11 to the Modicon 984.
Table RS-232C D-sub 9 Pin Connector Specifications Modbus
Title

Direction of signal

Pin number

Signal name

Description

CD

Carrier Detected

RD

Receive data

SD

Send data

ER

Data Terminal Ready

SG

Signal ground

DR

Data Ready

Detects whether sending and receiving are

allowed at correspondent

RS

Request to Send

ON is output when there is a send request

CS

Clear to send

ON is input when RS is ON

ACM11 Modbus PLC

ON is output when sending and receiving are

enabled

Not used
J100206E.EPS

9
6

1
D-sub 9 pin (female)
J090207E.EPS

Figure Pin Assignment of the RS-232C D-sub 9 Pin Connector Modbus

Cable connections when a Modbus PLC and ACM11 are directly connected are shown
below.
SD
RD
RS
ACM11

CS
CD
DR
ER
SG

20

SD
RD
RS
CS
CD
DR
ER
SG
Connector shell connection

Sheathed cable

Protective grounding
(100 ohms or less)
J090208E.EPS

Figure Cable Connection between Modbus and ACM11

(when Modbus PLC Uses an RS-232C D-sub 9 Pin Connector, and directly Connected)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.2 Connecting FCS and Modbus PLC>

J10-10

With the ACM11, the RS-232C circuit and FG (frame ground) are electrically insulated. This
has the function of preventing intrusion of noise from the Modbus PLC side and improving
noise resistance. Satisfy all conditions given below to make this function effective:
For the frame ground, perform protective grounding (100 ohms or less) at the opposing side of the connection (the modem or Modbus PLC side).
Attach only one side of the shield of the sheathed cable to the FG of the opposing side
of the connection. DO not ground the cable shield on the ACM11 side. Also, do not
use a connector shell that is conductive.
Connect the FG and the SG (signal ground) of the RS-232C circuit at the opposing
side of the connection. When the FG and SG are not connected on the opposing side,
and if the RS-232C cable is one manufactured by Yokogawa Electric, then use
AKB141 (RS-232C modem cable) or AKB142 (RS-232C null modem cable). For the
AKB141 and AKB142 cables, SG and FG are connected inside of the connector shell.
Also, the cable shield can be connected to the FG of the opposing side of the connection.
SEE ALSO
For details on connection cables, see the following:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)

Connection Example of a Modbus PLC

Different model of Modbus PLC requires different wiring for cables.
The wiring details for different models of PLC are shown as below.
SEE ALSO
For more information about wiring details of other models of Modbus PLC, see the users manual of the
connected Modbus PLC.

Modicon 984A,
984B, 984X

Shield

ACM11

2 SD

2 SD

3 RD

3 RD

4 RS

4 RS

5 CS

5 CS

7 SG

7 SG

6 DSR

6 DR

8 CD

8 CD

20 DTR

20 ER

1 FG
(D-sub 25-pin)

1 FG
(D-sub 25-pin)
J100209E.EPS

Figure Cable Connection for Modicon 984A, 984B and 984X

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.2 Connecting FCS and Modbus PLC>

Memocon-SC U84,
GL60S

J10-11

ACM11

Shield

2 SD

2 SD

3 RD

3 RD

4 RS

4 RS

5 CS

5 CS

7 SG

7 SG

6 DSR

6 DR
8 CD

8 CD

20 ER

9 DTR

1 FG
(D-sub 25-pin)

1 FG
(D-sub 9-pin)

J100210E.EPS

Figure Cable Connection for Memocon-SC U84 and GL60S

Memocon-SC 584

ACM11

Shield

E SD

2 SD

K RD

3 RD

B RS

4 RS

W CS

5 CS

P SG

7 SG

T DSR

6 DR
8 CD
20 ER

A DTR
J FG
(D-sub 9-pin)

1 FG
(D-sub 25-pin)

J100211E.EPS

Figure Cable Connection for Memocon-SC 584

Memocon-SC R84H-M,
684H

Shield

ACM11

2 SD

2 SD

3 RD

3 RD

4 RS

4 RS

5 CS

5 CS

7 SG

7 SG

6 DSR

6 DR
8 CD

20 DTR
1 FG
(D-sub 25-pin)

20 ER
1 FG
(D-sub 25-pin)

J100212E.EPS

Figure Cable Connection for Memocon-SC R84H-M, 684H

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.2 Connecting FCS and Modbus PLC>

Modicon 984

Shield

ACM11

3 SD

2 SD

2 RD

3 RD

7 RS

4 RS

8 CS

5 CS

5 SG

7 SG

6 DR

6 DR

4 ER

8 CD

1 CD

20 ER

Connector Shell
(D-sub 9-pin)

J10-12

1 FG
(D-sub 25-pin)
J100213E.EPS

Figure Cable Connections for Modicon 984

Cable Connection when Using the ACM12 Modbus

Different model of Modbus PLC requires different wiring for cables.
SEE ALSO
For more information about cable wiring between ACM12 (RS-422/RS-485) and various Modbus PLC
models, see the users manual for the Modbus PLC.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.3 Accessible Devices Modbus>

J10-13

J10.3 Accessible Devices Modbus

The Modbus PLC internal data are called devices. Devices are bit devices and word
devices, as indicated below:
Bit device
This refers to data where each bit has a meaning. An internal relay is equivalent
to a bit device.
Word device
This refers to data where a word unit (1 word = 16 bits) contains the meaning. A
holding register is equivalent to a word device.
The Modbus PLC also has two devices called special coil and communication status.

Accessible Devices Modbus

Device & Address and Size are designated via the Communication I/O Builder to access
devices. In the case of a Modbus PLC, addresses have the following structure:
<function code> + <device type> + <address of the device>
For example, when designating input relay 10012 to 10015 via the Communication I/O
Builder, A10012 is set as the Device & Address and 1 is specified as the Size, where the
A of A10012 corresponds to the function code, 1 to the device type and 0012 to the
address of the device.
The range of device address and Modbus protocol function codes for the accessible
devices are listed in the following table.
Table Modbus Protocol Function Code and Devices (1/3) Modbus
Address
Device

Function
code

Modbus PLC
Address within
device type Modbus PLC device

A
B

Coil

XXXX

Y
A

XXXX

A
Link relay (*1)

B
X

02
12

XXXX

Y
Step status (*1)

Read
01

Input relay

Modbus protocol
function code
(hexadecimal)

XXXX

17

Write
OF
05
OF
05

1D
19
1D
19

J100301E.EPS

*1:

This is a device for Memocon-SC GL60S. Other models do not have this device.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.3 Accessible Devices Modbus>

J10-14

Table Modbus Protocol Function Code and Devices (2/3) Modbus

Address
Device

Input register

Function
code
A

Modbus PLC
Address within
device type Modbus PLC device
3

XXXX

Modbus protocol
function code
(hexadecimal)
Read

Write

04

10

A
03

B
Holding register

10

XXXX

10

1E

A
13

B
C

1E

XXXX

14

15

B
Link register (*1)

1F

Y
Z

1F
20
16

20

Function
code

1C
20

Z
A

1C
20

XXXX

Device

1B

A
B

4 byte register

1B
1F

XXXX

Extended register (*1)

1F

1A
1E

Z
A

1A
1E

XXXX

Step elapsed time (*1)

06
10

Constant register (*1)

06

XXXX

Modbus PLC
Address within
device type Modbus PLC device
Address

04

Read

Write

Modbus protocol
function code
(hexadecimal)
J100302E.EPS

*1:

This is a device for Memocon-SC GL60S. Other models do not have this device.

Table Modbus Protocol Function Code and Devices (3/3) Modbus

Address
Device

Special coil
Comm Status

Function
code

Modbus PLC
Address within
device type Modbus PLC device

Modbus protocol
function code
(hexadecimal)
Read

Write

SP001

07

STSXXX

J100303E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J10-15

<J10.3 Accessible Devices Modbus>

Meaning of the function code is indicated below:

A:
Read: Read a packet of data designated by the Communication I/O Builder in word
units.
Write: Write a packet of data designated by the Communication I/O Builder. With
readback.
B:
Read: Read a packet of data designated by the Communication I/O Builder in word
units.
Write: Only write the changed single bit device or single word device to the subsystem. With readback.
C:
Read: Read a packet of data designated by the Communication I/O Builder in word
units.
Write: Only write the changed single 32 bits register to the subsystem. With readback.
X:
Write: Write a packet of data designated by the Communication I/O Builder only once
when the change occur. No readback.
Y:
Write: Only write the changed single bit device or single word device once when the
change occurs. No readback.
Z:
Write: Only write the changed single 32bits register once when change occur. No
readback.
Table List of Function Codes Modbus
Function
code
A

B
C
X

Y
Z

Device

Read

Write

Readback?

Bit device

The whole packet defind in the builder

The whole packet defind in the builder

Yes

Word device

The whole packet defind in the builder

The whole packet defind in the builder

Yes

Bit device

The whole packet defind in the builder

1 bit

Yes

Word device

The whole packet defind in the builder

16 bits

Yes

Word device

The whole packet defind in the builder

32 bits

Yes

Bit device

The whole packet defind in the builder

No

Word device

The whole packet defind in the builder

No

Bit device

1 bit

No

Word device

16 bits

No

Word device

32 bits

No
J100304E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.3 Accessible Devices Modbus>

J10-16

TIP

Usually, A, B or C, which has a readback, is used as function code.

When there is readback, FCS reads the status of the devices designated in the Communication I/O
Builder back, then compare them with those stored in the I/O image of FCS. The communication
packet to write to the designated devices of Modbus PLC is sent when discrepancy is detected.

When there is no readback, the data in the FCS and ACM11 are compared, and the data is sent to
the Modbus PLC side only if a difference is detected.

SEE ALSO
The function codes supported, accessible devices and sizes differ depending on the Modbus PLC type.
Refer to the users manual for the Modbus PLC being used for details.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.4 Subsystem Data Storing Format Modbus>

J10-17

J10.4 Subsystem Data Storing Format Modbus

The following explains the format in which subsystem data acquired from the
Modbus PLC is stored in the FCS.
The storing formats for Modbus PLC bit devices, word devices and special coils,
which indicate communication status, are given below:

Bit Device Modbus

When 16 m number (m=1, 2, ...) of bit devices are read starting from address n , the
Modbus PLC data is stored in the FCS as indicated below. The data size is specified as m
via the Communication I/O Builder.
16 bits
n n n n n n
+ + + + + +
15 14 13 12 11 10

n
+
9

n
+
8

n
+
7

n
+
6

n
+
5

n
+
4

n
+
3

n
+
31

n
+
2

n
+
1

n=1

n
+
16

m=2

n+16 (m-1)+15

n+16 (m-1)
J100401E.EPS

Figure Image of Stored Bit Device Modbus

Word Device Modbus

When m number of word devices are read starting from address n, the Modbus PLC data is
stored in the FCS as indicated below:
16 bits

Contents of the nth register

Contents of the n+1th register

Contents of the n+m-1th register

J100402E.EPS

Figure Image of Stored Word Device Modbus

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J10-18

<J10.4 Subsystem Data Storing Format Modbus>

Special Coil Modbus

The data length for the Modbus PLC special coil is one word (16 bits). Subsystem data for
the special coil is stored in the FCS as shown below.
The bit reversal can be designated via the Communication I/O Builder.
(a) When there is no bit inversion designation

(b) When there is bit inversion designation

15

15

n
+
7

n
+ n
1

n
n +
1

n
+
7

The value of n, where the status of the special coil are stored,
differ depending on the type of Modbus PLC connected.
J100403E.EPS

Figure Image of Stored Special Coil Data Modbus

Communication Status Modbus

The Modbus PLC communication status STSnnn indicates the status of communication
with each station number from nnn to nnn+15.
The communication status will be as follows:
Stations defined on the Communication I/O Builder that are communicating normally:
0
Stations defined on the Communication I/O Builder that are faulty: 1
Stations that are not actually communicating (those not defined via the Communication I/O Builder): 0
In the case of communication status, designation of the station number in the Communication I/O Builder has no particular significance, but the smallest station number of those that
are actually communicating is set.
The relationship between bits and station numbers is shown below. The largest station
number corresponds to the smallest bit number.
STS000 configuration
15

00

Bit arrangement

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
STS016 configuration
15

Station number
00

Bit arrangement

16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
J100404E.EPS

Figure Relationship between the Communication Status Bits and Station Numbers Modbus

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.5 Setting Items on System View Modbus>

J10-19

J10.5 Setting Items on System View Modbus

MODBUS

In this section, setting items on System View for Modbus PLC, the specific functionality and the recommended settings are explained.
SEE ALSO
For more information regarding to Set Details tab on Create New IOM dialog box and subsystem
common settings, see the following:
Setting Items for ACM11, ACM12 in J1.5.1, Overview of Setting Items on System View

For Modbus PLC, the setting items are as follows. This setting is done on the Set
Details tab of the New IOM dialog box called from System View.
Connection Device
Baud Rate
Parity
Data Bits
Stop Bits
RS Control
DR Check
CD Check
Communication Error Process
Options
After creating the new I/O module, the settings can be modified on the I/O module
property sheet.

Connection Device Modbus

Set [MODBUS] as the type of connection device (subsystem).
Must perform this setting since the default is [FA-M3].

Baud Rate Modbus

This sets the baud rate between the communication module and Modbus PC.
The recommended setting for baud rate is [19200 bps].

Parity Modbus
This sets the method for checking the parity of the subsystem data to be transmitted.
The recommended setting for the parity is [Even].
When the baud rate is set to [19200 bps], [No] parity cannot be set.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.5 Setting Items on System View Modbus>

J10-20

Data Bits Modbus

This sets the data bit length of the subsystem data to be transmitted.
When using Modbus PLC, select [8 bits] for the data bit length.

IMPORTANT
For the Modbus PLC, a communication error will occur if [7 bits] is selected.

Stop Bits Modbus

This sets the stop bit of the subsystem data to be transmitted.
When using the Modbus PLC, select [1 bit] for the stop bit.

IMPORTANT
When using a Modbus PLC, [2 bits] cannot be set for stop bit.

RS Control Modbus
This sets whether or not RS control is performed during subsystem data transmission.
When using Modbus PLC, disable [RS Control] by leaving the [RS Control] check box
unchecked.

DR Check Modbus
This sets whether or not DR check is performed during subsystem data transmission.
For Modbus PLC, it is required to enable the DR check by checking [DR check] check box.

CD Check Modbus
This sets whether or not CD check is performed during subsystem data transmission.
When using Modbus PLC, disable [CD Check] by leaving the [CD Check] check box
unchecked.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.5 Setting Items on System View Modbus>

J10-21

Communication Error Process- Modbus

This sets the parameters related to communication error handling during subsystem data
transmission.
The following three items must be set.
Response Timeout
This sets the time limit for getting response from Modbus PLC. The time is set in unit
of seconds.
Recommended setting is [4].
Number of Retries Upon Response Timeout
This item sets the number of retries performed when a communication error occurs.
Recommended setting is [1].
Interval of Connection Retries
This sets the time interval of connection requests for checking whether the communication with the station that generated a communication error has returned to normal
(communication recovery) . The time is set in unit of seconds.
Recommended setting is [30].

Options Modbus
Settings of communication parameter options vary depending on the equipment connected. Set options by clicking the [Option] button in the Set Details tab of the New IOM
dialog box called from the System View.
In the case of Modbus PLC, define a method of recovery communication at the Option 1,
and 0 at the Options 2 to 4.
SEE ALSO
For more information about recovery communication, see the following:
J10.7, Recovery Communication Modbus

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.6 Setting Items on Communication I/O Builder Modbus>

J10-22

J10.6 Setting Items on Communication I/O Builder

Modbus
In this section, setting items on Communication I/O Builder for Modbus PLC, the
specific functionality and the recommended settings are explained.
SEE ALSO
For an overview of the setting items on Communication I/O Builder, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

For Modbus PLC, the setting items are as follows.

Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

Element Modbus
Element

With respect to the address of the subsystem data buffer, the element numbers are displayed on Communication I/O Builder as shown below. The element number is not for set,
only for display.

Buffer Modbus
Buffer

This sets the buffer for the communicated data.

Must set the buffer size since this is a required setting item of the Communication I/O
Builder.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.6 Setting Items on Communication I/O Builder Modbus>

J10-23

Program Name Modbus : PFCS/SFCS

Program Name

Set the unit number, slot number and MODBUS as program name in the following format:
u-sProgramName
u:
Unit number
s:
Slot number
ProgramName: MODBUS

Program Name Modbus : LFCS2/LFCS

Program Name

Set the node number, unit number, slot number and MODBUS as Program Name in the
following format:
n-u-sProgramName
n:
u:
s:
ProgramName:

Node number
Unit number
Slot number
MODBUS

Size Modbus
Size

This item sets the data size (data length) from the head address set in Device & Address.
Must set the Size since this is a required setting item on Communication I/O Builder.
The setting range is 1 to 125 words.
SEE ALSO
For more information about Size setting item, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

Port FA-M3
Port

Port 1 is set for use.

IP Address Modbus
IP Address

No need to set IP address.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.6 Setting Items on Communication I/O Builder Modbus>

J10-24

Station Modbus
Station

This sets the station number of the Modbus PLC.

The station numbers that can be set are 1 to 255.

Device & Address Modbus

Device & Address

Set the head address of Modbus PLC data.

The addresses can be set using 3 to 7 alphanumeric characters in the formats given below:
There is no default setting.
Coil:

A0xxxx, B0xxxx, X0xxxx, Y0xxxx

Input relay:

A1xxxx

Link relay:

ADxxxx, BDxxxx, XDxxxx, YDxxxx

Step status:

ASxxxx

Input register:

A3xxxx

Holding register:

A4xxxx, B4xxxx, C4xxxx, X4xxxx, Y4xxxx, Z4xxxx

Constant register:

ACxxxx, BCxxxx, CCxxxx, XCxxxx, YCxxxx, ZCxxxx

Step elapsed time:

A5xxxx

Link register:

ARxxxx, BRxxxx, CRxxxx, XRxxxx, YRxxxx, ZRxxxx

Extended register:

AAxxxx, BAxxxx, CAxxxx, XAxxxx, YAxxxx, ZAxxxx

4 byte register:

AWxxxx

Special coil:

SP001

Communication status:STSxxx
xxxx is the address within the Modbus PLC device. The range is 1 to 65535 (1H to
FFFFH) and is set as a decimal or hexadecimal number. If it is set with a hexadecimal
number, add H at the end. Also, with respect to the xxxx portion, the 0 prefixed at the
head can be omitted. For example, A023, A0023 and A00023 are all the same address for
the coil.
SEE ALSO
For details regarding address setting, see the following:
J10.3, Accessible Devices Modbus

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.6 Setting Items on Communication I/O Builder Modbus>

J10-25

Data Type Modbus

Data Type

This sets data type of the subsystem data.

The data type can be selected from the following:
Input (16-Bit Signed)
Input (32-Bit Signed)
Input (16-Bit Unsigned)
Input (32-Bit Unsigned)
Input (32-Bit Floating)
Output (16-Bit Signed)
Output (32-Bit Signed)
Output (16-Bit Unsigned)
Output (32-Bit Unsigned)
Output (32-Bit Floating)
Input (Discrete)
Output (Discrete)

Reverse Modbus
Reverse

This sets whether or not to make the bit or word arrangement in FCS in reverse order of the
subsystem data.
The following settings can be selected:
Bits
No
Words
However, when choosing [Bits], only the data of discrete inputs or discrete outputs can be
reversed. In this case, the default setting is [Bits].
Regarding to words, only the 32-bit analog inputs or the 32-bit analog outputs can be
reversed. In this case the default setting is [No].

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.6 Setting Items on Communication I/O Builder Modbus>

J10-26

Scan Modbus
Scan

Set whether to read the communication I/O analog data into the communication I/O data
buffer at the beginning of high-speed scan of the FCS.

Service Comment Modbus

Service Comment

A comment text can be set.

Label Modbus
Label

The name of the function block I/O terminal can be set as a user-defined label.

IM 33S01B30-01E

10th Edition : Dec.18,2003-01

<J10.7 Recovery Communication Modbus>

J10-27

J10.7 Recovery Communication Modbus

When there is no response from a station or when a CRC-16 code error is detected at
a station, the Modbus communication driver contained in the Modbus communication package considers the station having error and temporarily stops communication with that station. After recovery communication time intervals set with the
Detail setting tab of the System View, the transmission request is sent from FCS to
invite the response from subsystem. This is called recovery communication. This
section explains the recovery communication at the time a station error occurs.

Types and Natures of Recovery Communication

There are five types of recovery communication as indicated below. The setting for recovery communication method is done using Option 1 found in the Option section of the
Detail setting tab of the New IOM dialog box called from System View.
When option 1 setting is 0
When there is readback, recovery communication is performed with the READ command.
When there is no readback, the 08 command is used for recovery communication.
The 08 command is used for loop back check and confirms the connection is alive.
SEE ALSO
Some types of Modbus PLC do not support the use of the 08 command. Refer to the users manual for
the Modbus PLC being used for details.

When option 1 setting is 1

Recovery communication is performed using the READ command, regardless of
whether there is readback.
When option 1 setting is 2
Recovery communication is performed using the READ command when there is
readback.
When there is no readback, error status will be reset at the same timing as the recovery communication. If the station indicates an error again at the time of recovery
communication, a system alarm is generated each time the recovery communication
packet is transmitted.
When option 1 setting is 3
Recovery communication is performed using the READ command when there is
readback.
When there is no readback, recovery communication is performed using a WRITE
command in which the write size is 0.
When option 1 setting is 4
Recovery communication is performed using the READ command when there is
readback.
When there is no readback, recovery communication is performed with the WRITE
command using the data written just before the error occurred.
When option 1 setting is 5
Recovery communication is performed using the READ command when there is
readback.
When there is no readback, the station generating the error will not be regarded as
faulty. When 5 is designated, communication with the Modbus PLC that did not
respond stops for no longer than no response time (1+number of retries) at each
recovery communication time interval specified in the Detail setting tab of the New
IOM dialog box.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.7 Recovery Communication Modbus>

J10-28

IMPORTANT
When option 1 is set to 4, the recovery communication uses the write communication packet right before the error occurred for retransmission. It has to be very careful
when transmitting the control data to the subsystem.
In some types of Modbus PLC, the READ command may overwrite the existing data.
When data must be preserved, designate a function code that does not have
readback.

SEE ALSO
For more information about Set Details tab on Create New IOM dialog box of System View, see the
followings:
Setting Items for ACM11, ACM12 in J1.5.1, Overview of Setting Items on System View
J10.5, Setting Items on System View Modbus

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J10-29

<J10.8 Communication Packet Modbus>

J10.8 Communication Packet Modbus

This section explains the Modbus protocol. Communication packet a Modbus protocol command and the frame of the response is included in the communication
packet. The frame format of the communication packet is given below.
01 Command

01

Response

01 m2

02 Command

02

Response

02 m2

03 Command

03

Response

03 m2

04 Command

04

Response

04 m2

05 Command

05

n-1

Pattern

CRC

Response

05

n-1

Pattern

CRC

06 Command

06

n-1

DATA

CRC

Response

06

n-1

DATA

CRC

07 Command

07

CRC

Response

07

08 Command

08

code

DATA

CRC

Response

08

code

DATA

CRC

0F Command

0F

n-1

m16

Response

0F

n-1

m16

10 Command

10

n-1

Response

10

n-1

CRC

11 Command

11

n-1

CRC

Response

11

CRC

12 Command

12

n-1

Response

12 m2

n-1

m16

CRC

DATA 1

n-1

DATA m

m16

CRC

DATA 1

n-1

DATA m
m

DATA m
m

CRC

CRC

DATA 1

DT

CRC

CRC

DATA 1

n-1

CRC

DATA m

CRC

CRC

DATA 1

DATA m

CRC

CRC

m2

m16
DATA 1

m2

DATA 1

DATA m

CRC

CRC
DATA m

CRC

s:
n:

Station number
Relative value from the head address in the device
For example, in the case of holding register 40050, n=40050-40001=49
m:
The data size designated via the Communication I/O Builder (word units)
Pattern: 0xFF00 when ON, 0x0000 when OFF.
J100801E.EPS

Figure Frame Format of Communication Text (1/2) Modbus

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J10-30

<J10.8 Communication Packet Modbus>

13 Command

13

Response

13 m2 DATA 1

14 Command

14

Response

14 m2 DATA 1

15 Command

15

Response

15 m2 DATA 1

16 Command

16

Response

16 m2 DATA 1

17 Command

17

Response

17 m2 DATA 1

19 Command

19

n-1

Pattern

CRC

Response

19

n-1

Pattern

CRC

1A

n-1

DATA

CRC

1A

n-1

DATA

CRC

1B

n-1

DATA

CRC

1B

n-1

DATA

CRC

1C

code

DATA

CRC

1C

code

DATA

CRC

1D

n-1

m16

1D

n-1

m16

1E

n-1

Response

1E

n-1

1F Command

1F

n-1

Response

1F

n-1

20 Command

20

n-1

Response

20

n-1

1A Command
Response
1B Command
Response
1C Command
Response
1D Command
Response
1E Command

n-1

n-1

DATA m
m

n-1

n-1

CRC

CRC
DATA m

CRC

CRC
DATA m

CRC

CRC
DATA m

n-1

CRC

CRC

CRC
DATA m

m2 DATA 1

CRC

DATA m

CRC

DATA m

CRC

DATA m

CRC

DATA m

CRC

CRC
m2 DATA 1
CRC
m2 DATA 1
CRC
m2 DATA 1
CRC

s:
n:

Station number
Relative value from the head address in the device
For example, in the case of holding register 40050, n=40050-40001=49
m:
The data size designated via the Communication I/O Builder (word units)
Pattern: 0xFF00 when ON, 0x0000 when OFF.
J100802E.EPS

Figure Frame Format of Communication Text (2/2) Modbus

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.9 Dual-Redundant Communication Modbus>

J10-31

J10.9 Dual-Redundant Communication Modbus

This section explains the setting and control items when communication with a
subsystem such as a PLC is made dual-redundant using two communication modules (ACM11 or ACM12).

Overview of Dual-Redundant Communication

When the same model of two communication modules are installed in the same nest
(AMN33) are specified as dual-redundant, the subsystem dual-redundant communication
may be performed. One of the two modules is set as the referenced module of function
blocks such as regulatory blocks, sequence table block and switch instrument blocks. This
module is referred to as Master, the other one is referred to as Slave. The aster and slave is
automatically assigned according to the modules card number.
Also, of the two communication modules, the one being used as having correct data is
called the control side, while the opposite side is called the standby side.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.9 Dual-Redundant Communication Modbus>

J10-32

Reading Data During Dual-Redundant Communication

The two dual-redundant communication modules always read data from the subsystem
asynchronously. The read data is stored in the I/O image area of each communication
module.
The dual-redundant function is activated after the read data is stored, and looks for errors
in the master communication module and in the communication with the subsystem. When
an error is detected, data in the slave communication modules I/O image area overwrites
the data in the master communication modules I/O image area.
Regulatory control blocks
Switch instrument
Sequence tables
Internal
switches
Master Side
Communication Module
I/O image area

Slave Side
Communication Module
I/O image area

read

Card/Communication
Status output
Overwrite data
Dual-redundant function
Control Side

Stand-by Side

ACM11/ACM12

ACM11/ACM12

RS
card

RS
card

Subsystem
J100901E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.9 Dual-Redundant Communication Modbus>

J10-33

Writing Data During Dual-Redundant Communication

Each function block writes data to the I/O image area of the master communication module.
When the master side faults out, the slave side is overwritten by the data that was written in
the master side. Writing to the subsystem can only be performed from the control-side
communication module.
Information on switching between the control side and standby side, set in the communication modules I/O image area by the dual-redundant function, is sent to the subsystem
communication program.
Data write is performed to both the control side and standby side, but only the control-side
communication module performs communication for writing data to the subsystem, thereby
preventing duplicate data writing.
Regulatory control blocks
Switch instrument
Sequence tables

Master Side
Communication Module
I/O image area

Slave Side
Communication Module
I/O image area

write
Information on
switching between
the control side
and standby side
Overwrite data

Control Side

Dual-redundant function
Stand-by Side

ACM11/ACM12

ACM11/ACM12

RS
card

RS
card

Subsystem
J100902E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.9 Dual-Redundant Communication Modbus>

J10-34

Output to Common Switches

The status of each communication module and the status of the communication between
each module and the subsystem may be output to a common switch (%SWxxxx). When
both the status of module and status of communication are normal, this common switch is
kept ON.
Either the status of the module or the status of communication has error, the switch turns
OFF.
Using sequence table to monitor the status of this switch, the control sequence corresponding to the status of module or the status of the communication may be created.
TIP
It may take FCSs basic scan period (1 second) at the longest from when the control right transfers due to
a change in the status of communication or communication module until this change is reflected in the
status of the common switch.

To output the status of communication and communication module to the common switch,
a tag name linked to the card address should be assigned to the common switch as shown
below:
Tag name: Zddssymn
Z:
dd:
ss:
y:
m:
n:
*1:

When the RIO bus 1 is used.

Domain number (2 digits)
Station number (2 digits)
Node number (1 digit) (*1)
Unit number (1 digit)
Slot number (1 digit)
For PFCS, fixed to 1.
For SFCS, fixed to 1.

The following system alarm will be output upon loading, depending on whether or not
definition for the corresponding internal switch exists:
Common switch exists
STNss ACM Monitor Tag[Zddssymn]exists

Common switch does not exist

STNss No ACM Monitor Tag[Zddssymn]exists

IMPORTANT
When a tag with the above name exists, the status of communication and communication
module is output automatically to the PV of the designated tag name. Be careful not to use
the above tag names for other purposes.

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J10.9 Dual-Redundant Communication Modbus>

J10-35

Setting of Dual-Redundant Communication

Dual redundancy may be defined when a pair of communication modules installed in the
same communication mode nest (AMN33).

Slot Positions when Installing the Communication Modules

Six (three pairs) communication modules can be installed for dual redundancy in LFCS2 or
LFCS, and four (two pairs) modules can be installed in an SFCS (*1) or a PFCS (*2).
*1:
*2:

LFCS2, LFCS and SFCS is a station for CS 3000.

In a enhanced type PFCS, a total number of four communication modules can be installed regardless the
redundancy. In a standard PFCS, four (two pairs) modules can be applied for redundant configuration while one pair of
redundant modules and one single module (total 3 modules) can also be applied.

The communication module installed in the first slot will be the master module and the one
installed in the second slot will be the slave module.

Setting on System View

FCS Properties
Add the [ZACMWDPX] to the Options item on the Constant tab in the FCS [Properties...] dialog box called out on System View.
IOM Properties
Put a check mark on [Duplicate Next Card] item on the Type and Position tab in the
IOM [Properties...] dialog box called out on System View.

Setting on Communication I/O Builder : SFCS/PFCS

The assignment of communication I/O area may only be performed on the communication
module installed in the slot 1 (master ) on the Communication I/O Builder of the System
View.
The first line or the last line of the definition should have the items defined as follows
Size:

Station:

0 (Modbus number)

Device & Address:

ZACMWDPX

Data Type:

Output (Discrete)

Reverse:

No

The leading bit in the communication module I/O image area reserved by a dual-redundant
definition is used by the subsystem communication program for switching the write destination. The leading bit in the reserved area is set to 1 when dual-redundant communication
is active and 0 when it is not active.
This signal cannot be referred to as a communication datum, nor can be set.

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J10.9 Dual-Redundant Communication Modbus>

J10-36

The following system alarms are output upon loading in accordance with the definitions of
the master side and slave side. Each number indicates the position of the master-side card.
When there is an error in the dual-redundancy definition, dual-redundant communication
does not operate.
When dual-redundant definition is normal
STNss Redundant Def. Normal UNITmm SLOTnn

When dual-redundant definition is faulty

STNss Redundant Def. Error UNITmm SLOTnn
STNss: FCS station name
mm:
Unit number (1 to 5)
nn:
Slot number (1, 2)

Setting on Communication I/O Builder : LFCS

The assignment of communication I/O area may only be performed on the communication
module installed in the slot 1 (master) on the Communication I/O Builder of the System
View.
The first line or the last line of the definition should have the items defined as follows
Size:

Station:

0 (Modbus number)

Device & Address:

ZACMWDPX

Data Type:

Output (Discrete)

Reverse:

No

The leading bit in the communication module I/O image area reserved by a dual-redundant
definition is used by the subsystem communication program for switching the write destination. The leading bit in the reserved area is set to 1 when dual-redundant communication
is active and 0 when it is not active.
This signal can not be referred to as a communication datum, nor can be set.
The following system alarms are output upon loading in accordance with the definitions of
the master side and slave side. Each number indicates the position of the master-side
module. When there is an error in the dual-redundancy definition, dual-redundant communication does not operate.
When dual-redundant definition is normal
STNss Redundant Def. Normal RIOxx NODEyy UNITmm SLOTnn

When dual-redundant definition is faulty

STNss Redundant Def. Error RIOxx NODEyy UNITmm SLOTnn
STNss:
xx:
yy:
mm:
nn:

FCS station name

RIO bus number
Node number (1 to 8)
Unit number (1 to 5)
Slot number (1, 2)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.9 Dual-Redundant Communication Modbus>

J10-37

IMPORTANT
If the settings on the Communication I/O Builder are not correct, when running generation
after saving the setting, the generation program can not detect the errors nor error message displays.
Thus it is important to set all the settings correctly. Moreover, the settings can not be added
by online maintenance, nor erro message displays either.

How to Switch Dual Redundancy

In a dual-redundant communication module system, one of the communication modules
controls and the other stands-by. In the initial state, the master controls and the slave
stands-by.
When reading data from the subsystem, both the control-side and standbyside communication modules perform reading, but only the data from the control side is written to the
function block. When writing to the subsystem, only data of the control side is written.
The switching of the control side and standby side of dual-redundant communication
modules occur under the following conditions:
When the master side is faulty
When there is an error in the master side or in the communication with the subsystem
connected to the master side, and when the slave side and the communication with
the subsystem connected to the slave side are normal, control right is switched to the
slave side.
When the slave side is faulty
When the master side and the communication with the subsystem connected to the
master side are both normal, the master side has the control right regardless of the
status of the slave side or the communication with the subsystem connected to the
slave side.
No error will occur when reading data from the subsystem when the control right is
switched, because reading is switched at the same moment without delay.
When writing to the subsystem, data hunting may occur when the control right is switched.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.9 Dual-Redundant Communication Modbus>

J10-38

Restrictions on Dual-Redundant Communication

Restrictions when performing dual-redundant communication are indicated below:

Switching between Control Side and Stand-By Side

When switching from control side to stand-by side, the operations of subsystem reading
and writing and output to the common switch cannot be guaranteed to perform properly.
Specific items to be noted are listed below:
While data is written to the subsystem, hunting may occur if the value in analog output
or discrete output changes during switching.
While data is written to the communication modules I/O image area from the regulatory control block, the refresh processing will be performed during each FCS control
period. However, with some function blocks such as the sequence table block, the
refresh processing is performed only at the timings when write is performed. When
writing data to the communication modules I/O image area from these blocks, avoid
one shot execution so that the internal data will not be overwritten due to hunting or
tracking operation.

During On-Line Maintenance

Dual-redundant communication is not guaranteed during on-line maintenance.

High-Speed Read Specification

Make the same setting for high-speed read specification on both the master-side and
slave-side communication modules specified for dual redundancy.

Readback Availability
For data writing to the subsystem, only Perform readback is supported. No readback is
not supported.
In the case of Perform readback, first data is read from the subsystem, then compared to
the data in the FCS. If the data is different, it is written to the subsystem.
In the case of No readback specification, data in the FCS and data in the communication
module are compared without reading from the subsystem, and the data is written to the
subsystem only when a difference is found.
Because the data in the slave-side communication module is not refreshed while the
master-side communication module is normal, the data in the communication module is still
old when it is switched from slave to the master. In this case, the difference of data in the
FCS and in the communication module cannot be found since they cannot be compared,
so data write cannot be performed when readback is not specified. With Modbus communication, readback availability is determined by the function code of the address specified via
the Communication I/O Builder.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.10 System Alarm Messages Specific to Modbus PLC>

J10-39

J10.10 System Alarm Messages Specific to Modbus

PLC
This section explains the system alarm messages that are specific to Modbus PLC.

System Alarm Message when a Communication Error Occurs Modbus

: PFCS/SFCS
When there is a communication error, the system alarm message as shown below is sent
to HIS:
STNss SS-COM Error UNITmm SLOTnn STNzzz
CODE=####
STNss:
mm:
nn:
zzz:
####:

FCS name
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. After that, a new system alarm message
will not be sent even if an error is generated by a different cause.
SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs Modbus

System Alarm Message when a Communication Error Occurs Modbus

: LFCS2/LFCS
When a communication error occurs, the system alarm message as shown below is sent
to HIS:
STNss SS-COM Error RIO01 NODExx UNITmm SLOTnn STNzzz
CODE=####
STNss:
xx:
mm:
nn:
zzz:
####:

FCS name
Node number
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. The new system alarm message will not
be transmitted even if errors are generated by different causes.
SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs Modbus

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.10 System Alarm Messages Specific to Modbus PLC>

J10-40

System Alarm Message when Communication Returns to Normal

Modbus : PFCS/SFCS
When communication returns to the normal condition, the system alarm message indicated
below is sent to HIS:
STNss SS-COM Recover UNITmm SLOTnn STNzzz
STNss:
mm:
nn:
zzz:

FCS name
Unit number
Slot number
Subsystem station number

System Alarm Message when Communication Returns to Normal

Modbus : LFCS2/LFCS
When communication returns to normal status, the system alarm message indicated below
is sent to HIS:
STNss SS-COM Recover RIO01 NODExx UNITmm SLOTnn STNzzz
STNss:
xx:
mm:
nn:
zzz:

FCS name
Node number
Unit number
Slot number
Subsystem station number

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.10 System Alarm Messages Specific to Modbus PLC>

J10-41

Error Codes when a Communication Error Occurs Modbus

Table Error Codes when a Communication Error Occurs Modbus (1/2)
Error code
(hexadecimal)

Description

A391

Communication driver busy

A392

Communication line busy

A393

Communication line not ready

A394

Sending size is too large

A395

Use of communication port not declared

A398

Timeout between received characters

A399

Receive buffer overflow

A39A

Parity error in receive data

A39B

Receiving overrun error

A39C

Receiving framing error

A39D

No. of characters received is outside specifications

A39F

Other error
Communication is retried.
In case of error during retry, information related to the
error occurrence is held for each station number and
recovery communication with respect to that station
number is performed using the set cycle.

A3B0

No response

A3B1

Station number (1 to 255) is out of range

A3B2

Station number 0 cannot be set

A3B3

Inappropriate address name

A3B4

Inappropriate address number

A3B5

Too many communication processing points

A3B6

Write to a read-only device occurred

A3B7

Block definition error

A3B8

Odd number is used for 4-byte register size

A3B9

Option 1 setting is out of range

A3BA

Cannot create communication frame

A3BB

Dual-redundant definition error

Error code
(hexadecimal)

Processing after error occurrence

Description

Communication is not performed with respect to the

definition generating the error.

Processing after error occurrence

J101001E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.10 System Alarm Messages Specific to Modbus PLC>

J10-42

Table Error Codes when a Communication Error Occurs Modbus (2/2)

Error code
(hexadecimal)

Description

Communication is retried.
In case of error during retry, information related to the
error occurrence is held for each station number and
recovery communication with respect to that station
number is performed using the set cycle.

A3C0

CRC-16 error

A3C1

Response message error (STN)

A3C2

Response message error (address)

A3C3

Response message error (function code)

A3C4

Response message error (data)

A3C5

Response message error (size of received data)

A3C6

Response message error (length of received text)

A3D1

Error code $01 received

A3D2

Error code $02 received

A3D3

Error code $03 received

A3D4

Error code $04 received

A3D5

Error code $05 received

A3D6

Error code $06 received

A3D7

Error code $07 received

A3D8

Error code $08 received

A3D9

Error code $09 received

A3DA

Error code $0A received

A3DB

Error code $0B received

A3DC

Error code $0C received

A3DD

Error code $0D received

A3DE

Error code $0E received

A3DF

Error code $0F received

A3E0

Error code $10 received

A3E1

Error code $11 received

A3E2

Error code $12 received

A3E3

Error code $13 received

A3E4

Error code $14 received

A3E5

Error code $15 received

A3E6

Error code $16 received

A3E7

Error code $17 received

A3E8

Error code $18 received

Error code
(hexadecimal)

Processing after error occurrence

Description

Communication is performed every time.

However, a system alarm is generated only once when
the initial error occurs and is not sent again until that
error has returned to normal even if another error occurs.

Communication is performed every time.

However, a system alarm is generated only once when
the initial error occurs and is not sent again until that
error has returned to normal even if another error occurs.

Communication is performed every time.

However, a system alarm is generated only once when
the initial error occurs and is not sent again until that
error has returned to normal even if another error occurs.

Processing after error occurrence

J101002E.EPS

SEE ALSO
For details on the contents of the errors, refer to the users manual for the Modbus PLC being connected.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.11 Transmission Time between Communication Module and Modbus PLC>

J10-43

J10.11 Transmission Time between Communication

Module and Modbus PLC
The transmission time between communication module and Modbus PLC is to be
discussed in this chapter.

Communication Time Modbus

The time required for communication between a communication module and Modbus PLC
is figured as the total of the time T1 to T7. However, when the communication module and
Modbus PLC are directly connected without using a modem connection, T2 and T5 are not
added in.
Data acquisition begins

Communication
Module

Data acquisition complete

Create message
to be sent

Interpret response
message, store data
RTS
CTS

Modem

Data

Data

Modem
CTS
RTS
Modbus PLC

Interpret and execute

response message, create
response message (Modbus
PLC processing time)
T1

T2

T3

T4

T5

T6

T7
J101101E.EPS

T1:
T2:
T3:
T4:
T5:
T6:
T7:

Transmission message creation time approximately 10 ms

Modem processing (delay) time on communication module side approximately 5 ms
Send message transmission time
Modbus PLC processing time. This is the time required to interpret and execute the received message and create a
response message and is determined by the number of communication data and the number of scans of the Modbus
PLC.
Modem processing (delay) time on Modbus PLC side approximately 5 ms
Response message transmission time
Response message interpretation time approximately 15 ms

Figure Time Chart of Communication between Communication Module and Modbus PLC

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J10-44

<J10.11 Transmission Time between Communication Module and Modbus PLC>

Calculating the Communication Time Modbus

The send message transmission time (T3) and response message transmission time (T6)
are figured using the formula given below:
Transmission time (ms) = No. of characters to be sent no. of bits per character 1000
Baud rate (bps)
No. of bits
per character

start bit

data bit +

parity bit

stop bit
J101102E.EPS

Start bit:
Data bit:
Parity bit:
Stop bit:
Baud rate:

1 bit fixed
8 bits fixed (7 bits cannot be set)
None, even or odd
1 bit fixed
1200, 2400, 4800, 9600, 19200 (bps)

Table Number of Characters that can be Sent Modbus

Device

Read
Send

Write

Response

Coil

8 fixed

5+no. of coils/8 (*1)

Input relay

8 fixed

5+no. of relays/8 (*1)

Send
9+no. of coils/8 (*1)

Response
8 fixed

Holding register

8 fixed

5+2 no. of registers

9+2 no. of registers

8 fixed

Input register

8 fixed

5+2 no. of registers

J101103E.EPS

*1:

The digits after decimal point are round up.

The maximum number of characters that the Modicon (Modicon 484, 584, 984) can read or
write with a single communication and the maximum number of characters it can process
during a single scan are indicated in the table below.
SEE ALSO
For the information on Modbus PLCs other than Modicon 484, 584 and 984, refer to the users manual for
the Modbus PLC being used.

Table Modicon Communication Capacity (For Reading)

Device

Maximum capacity per each

communication

Maximum capacity per each scan

484

584/984

484

584/984

Coil

125

125

32

64

Input relay

125

125

32

64

Holding register

254

125

16

32

Input register

32

125

16

32
J101104E.EPS

Table Modicon Communication Capacity (For Writing)

Device

Maximum capacity per each

communication

Maximum capacity per each scan

484

584/984

484

584/984

Coil

50

64

Holding register

100

32
J101105E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J10.11 Transmission Time between Communication Module and Modbus PLC>

J10-45

Example of Calculating the Communication Time Modbus

When a write definition (specifying output data type such as AOI16, AOU16, AOI32,
AOU32, AOF32 or DO) has been set in the Communication I/O Builder, the communication
package reads data from the subsystem before it executes a write with regard to that
definition. Then, it compares the data read from the subsystem to the data in the FCS and
executes a write to the subsystem only with respect to the data whose value did not agree
with the data in FCS.
Therefore, it is difficult to calculate the communication time required for writing data to a
subsystem since the value fluctuates according to the number of data items that have been
changed. Use the following guidelines for the communication time when writing to a subsystem.
When the values of most data items to be written remain unchanged
Communication time=Communication time required to read all definitions specified for
the write
When the values of many data items to be written change
Communication time=Approximately twice the communication time required to read
all definitions specified for the write
The example below gives the calculation for the communication time between the communication module and Modbus PLC.
In this example, the contents of 50 holding registers in Modicon are read.
The communication time is calculated based on the following conditions.
For a Modicon capable of reading 32 retention registers during a single scan, two scans
are required to read the contents of 50 holding registers.
Baud Rate:

119200 bps

Number of bits per character:

11

Modicon scan period:

50 ms

Number of characters in the send message=8

Send message transmission time (T3)=8 11 1000/19200=4.58 (ms)
Modbus PC processing time (T4)=50 2=100 (ms)
Number of characters in the response message=5+2 50=105
Response message transmission time (T6)=105 11 1000/19200=60.15 (ms)
7

Total time=Ti=10+5+4.58+100+5+60.15+15200 (ms)

i=1

J101106E.EPS

TIP
When 1 to n communication is performed using multiple Modbus PLCs and if there is no response from
one PLC, recovery communication request sent to the PLC during each recovery communication time
interval designated in IOM property sheet (the default is 30 seconds). While, communication is not
performed during the no response time designated in IOM property sheet (default is 4 seconds). In other
words, if the recovery communication time interval and no response time values are set to the default
values, and if there is no response from one of the PLCs, communication to the normal Modbus PLCs
stops for 4 seconds in every 30 seconds.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

Blank Page

<J11. A-B Communication>

J11-1

J11. A-B Communication

The A-B communication package is a subsystem communication package that is
compatible with the PLC-5 family (hereinafter referred to as PLC-5) PCs manufactured by the Rockwell Automation, Inc. By using the A-B communication package,
communication between the FCS and the PLC-5 can be performed without a customized program. An asynchronous link layer protocol is used for this package.
This chapter explains the communication between the PLC-5 and FCS among the
subsystem communication packages.
SEE ALSO
Regarding the functions common to different subsystem communication packages, see the following:
J1, General Information Regarding to Subsystem Communication

Applicable Models PLC-5

For the A-B communication package, the following product is available:
PFS9054 CS 1000 A-B communication package (ACM11, ACM12)
LFS9054 CS 3000 A-B communication package (ACM11, ACM12)
The A-B communication package performs subsystem communication between the FCS
and PLC-5 by connecting the following link modules manufactured by the Rockwell Automation (hereinafter referred to as PLC-5 link modules) to the communication module
(ACM11 or ACM12). An asynchronous link layer protocol is used for the subsystem communication.
1785-KE
1770-KF2

IMPORTANT
Even though they have the same model name, there are some PLC-5 link modules that do
not use the asynchronous link layer protocol.

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J11.1 Communication Specifications PLC-5>

J11-2

J11.1 Communication Specifications PLC-5

This section explains the specifications when performing subsystem communication with the PLC-5.

Communication Capacity PLC-5

The capacity when performing subsystem communication with the PLC-5 are indicated
below:
Table Capacity of Communication between FCS and PLC-5
Item

Maximum quantity

Explanation

Amount of data that can be communicated with

one communication module

500 words
(1 word=16 bits)

Maximum amount that can be

accessed from the regulatory control
block or sequence control block.

Number of subsystem stations that can be

communicated with one communication module

30 stations

Data size in one communication frame

Word Device: 114 words One frame is defined in one line on

Bit Device: 16 words the builder. It is the same as
(256 bits) restricted by PLC-5 protocol.
J110101E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.1 Communication Specifications PLC-5>

J11-3

Transmission Specifications PLC-5

The table below lists the transmission specifications when performing subsystem communication with the PLC-5:
Table Transmission Specifications PLC-5
Item
Interface

Description
RS-232C (D-sub 25 pin)

ACM11

RS-422

ACM12

Transmission method

Half duplex

Synchronization method

Start-stop synchronization
method

Baud rate (bps)

1200, 2400, 4800, [9600]

Transmission procedure

PLC-5 family dedicated protocol

Transmission code

Binary

Data type

Time
monitoring

Remark

(*1)

Start bit

Data bit

Must specify 8 via the New IOM dialog box

called from the System View.

Parity bit

None, [even]

(*1)

Stop bit

Must specify 1 via the New IOM dialog box

called from the System View.

Transmission
enable monitoring 1000ms
time
Reception
character interval
monitoring time

10ms

Reception start
Text frame character
Last character

None

XON/XOFF control

None

RS control

None

(*1)

DR check

Yes

(*1)
(*1)

None

CD check

None

No response time setpoint

0 to 99 sec [4 sec]

Number of communication
retries upon error

0 to 99 times [one time]

(*1)

Recovery communication time

interval

0 to 999 sec [30 sec]

(*1)

Number of words that can be

114 words (AI/AO)
handled in one communication
16 words (DI/DO)
packet.
Item

Description

Remark
J110102E.EPS

Note: [ ] indicates the recommended settings.

*1:
This can be changed using the property dialog box called from the System View.

IMPORTANT
When performing subsystem communication with the PLC-5, be sure to specify [8
bits] for the data bit length. A communication error will occur if [7 bits] is specified.
When performing subsystem communication with the PLC-5, do not specify 19200
bps for the baud rate.
IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.2 Connecting FCS and PLC-5>

J11-4

J11.2 Connecting FCS and PLC-5

This section explains the connection between FCS and PLC-5, and the connection
cables.

Connection Type PLC-5

An example of connection between FCS and PLC-5 is shown below:
HIS

Control bus

FCS

ACM11 (RS-232C communication module)

RDY
RCV
SND

CN1

RDY
RCV
SND

AMN33 (communication module nest)

CN1

RS-232C
MODEM

MODEM
RS-232C
1770-KF2B

PLC-5
link module

PLC-5
J110201E.EPS

Figure Example of Connection between FCS and PLC-5

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.2 Connecting FCS and PLC-5>

J11-5

Cable Connection when Using the ACM11 PLC-5

The following describes the cable connection when connecting the ACM11 and PLC-5:
A modem connection is required between the ACM11 and PLC-5 link module, but a direct
connection is possible if the length of the RS-232C cable between the ACM11 and PLC-5
link module is 15 meters or less and the same grounding system is used for them.

IMPORTANT
The cable length between the ACM11 and modem as well as between the modem and the
PLC-5 must each be 15 meters or less.

The PLC-5 link module uses an RS-232C D-sub 25 pin connector. For this reason, a cable
with an RS-232C D-sub 25 pin connector is used when connecting a PLC-5 link module
and the ACM11.
Table RS-232C D-sub 25 Pin Connector Specifications PLC-5
Direction of signal

Pin number

Signal name

Title

FG

Frame ground

SD

Send data

RD

Receive data

RS

Request to Send

When there is a send request, ON is output

CS

Clear to Send

When OFF, the ACM11 does not transmit to the

outside

DR

Data Ready

Detects whether sending and receiving with

correspondent are allowed. Send data only when
ON

SG

Signal ground

CD

Carrier Detected

20

ER

Data Terminal Ready

ACM11

Description

PLC-5
Safety grounding

When sending and receiving are allowed, ON is

output
J110202E.EPS

SEE ALSO
For details on safety grounding, see the followings:
Figure Cable Connection between ACM11 and Modem
Figure Cable Connection between PLC-5 and ACM11 (when connected directly)

Pin No. 25

Pin No. 14

Pin No. 13

Pin No. 1
J110203E.EPS

Figure Pin Assignment of the RS-232C D-sub 25 Pin Connector PLC-5

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.2 Connecting FCS and PLC-5>

J11-6

The following shows when the PLC-5 and ACM11 are connected via modems and when
they are connected directly without modem:

SD
RD
RS
CS
ACM11

20

20

DR
SG
CD
ER
FG

Sheathed cable

SD
RD
RS
CS
DR

Modem (*1)

SG
CD
ER
FG

Protective grounding
(100 ohms or less)
J110204E.EPS

*1 : As a rule, use a modem where FG and SG are connected.

Figure Cable Connection between ACM11 and Modem

SD
RD
RS
CS
ACM11 DR
CD
ER
SG
FG

20

20

Sheathed cable

SD
RD
RS
CS
DSR PLC-5
CD
DTR
SG
FG

Protective grounding
(100 ohms or less)
J110205E.EPS

Figure Cable Connection between PLC-5 and ACM11 (when connected directly)

SEE ALSO
For details on cable connections, see the following:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)
The cable connection differs by the type of PLC-5. See the users manual for the PLC-5 being connected
regarding the cable connections for each type of PLC-5.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.2 Connecting FCS and PLC-5>

J11-7

With the ACM11, the RS-232C circuit and FG (frame ground) are electrically insulated. This
has the function of preventing intrusion of noise from the PLC-5 side and improving noise
resistance. Satisfy all conditions given below to make this function effective:
For the frame ground, perform protective grounding (100 ohms or less) at the opposing side of the connection (the modem or PLC-5 side).
Attach only one side of the shield of the sheathed cable to the FG of the opposing side
of the connection. Do not ground the cable shield on the ACM11 side. Also, do not use
a connector shell that is conductive.
Connect the FG and the SG (signal ground) of RS-232C circuit at the opposing side of
the connection.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.2 Connecting FCS and PLC-5>

J11-8

Cable Connection Using the ACM12 PLC-5

The following figures show the cable connection when connecting the ACM12 with link
module (1770-KF2) of PLC-5:
ACM12

1770-KF2
Shield

TX

16

TX

RT (*1)
18

RX

14

RX

25

SG

Cable length: 1200 meters

(4000 ft) or less

FG

5
6
8
20
25 pin (female) connector
J110206E.EPS

*1:

RT value for the 1770-KF2 link modules terminating resistor is in the range of 90 to 150 ohms (1/2 W). This varies
according to the type and length of the cable and resistor connected.

Figure 1 to 1 Connection Using RS-422 (4-Wire) PLC-5

IMPORTANT
The 1 to n connection is not supported in the communication between ACM12 and PLC-5.

With the ACM12, the FG (frame ground) and the SG (signal ground) for the RS-422 are
separated. Treat the shield for the RS-422 as follows:
Perform protective grounding (100 ohms or less) for the FG at the opposing side of the
connection (PLC-5 side).
Connect the shield for the cable between ACM12 and the PLC-5 link module, to the
FG of the PLC-5 link module.
SEE ALSO
For details on cable connections, see the following:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)

When connecting the ACM12 and the PLC-5 link module, a terminating resistor is required
on each side.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.2 Connecting FCS and PLC-5>

J11-9

Setting a Terminating Register on the ACM12 Side PLC-5

When connecting the ACM12 and PLC-5, a terminal resistor (120 ohms 1/2W) between the
RX+ terminal and RX- terminal on the ACM12 side is needed. The ACM12 is shipped with
the terminal resistor installed between the RX+ terminal and RX- terminal.
Set the connection method (4-wire or 2-wire ) using the 2-pole DIP switch (SW1) attached
to the ACM12. The unit is shipped from the factory with a 4-wire connection setting.
The SW1 setting for the ACM12 is indicated in the table below:
Table SW1 Setting for the ACM12
Connection method

SW1 setting for ACM12

2-wire

ON

ON

4-wire

OFF

OFF
J110207E.EPS

Setting a Terminating Register on the PLC-5 Link Module Side

The terminating resistor differs according to the PLC-5 link module used.
SEE ALSO
For details on the terminating resistor for the PLC-5 link module, refer to the users manual for the link
module connected.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.3 Accessible Files PLC-5>

J11-10

J11.3 Accessible Files PLC-5

PLC-5 internal data are stored as files. Internal data are generally called devices. The
PLC-5 files are bit device files and word device files, as indicated below:
Bit device file
This refers to data where each bit has a meaning. An output image file is equivalent to a bit device file.
Word device file
This refers to data where a word unit (1 word = 16 bits) contains the meaning.
An integer file is equivalent to a word device file.

Accessible Files and Basic Commands PLC-5

The table below lists the accessible files and basic commands:
Table Accessible Files PLC-5
File format

File type
number (*1)

Output image file

O000:mmm

Input image file

I001:mmm

Status file

S002:mmm

Bit file

B003:mmm

Timer file

T004:mmm

Counter file

C005:mmm

Word file Control file

R006:mmm

Integer file

N007:mmm

Floating-point file

F008:mmm

File type

File name

Address (*2)

PLC-5 command
(CMD/FNC)
Read

Bit file

0F/01

Remark

Write
I/O area; action during access
Not
is not guaranteed. All accesses
possible
are performed using B.
0F/26

0F/01

0F/00

J110301E.EPS

*1:
*2:

The file type numbers 0, 1 and 2 are fixed.

Numbers 3 through 8 can be changed or deleted.
The X of Xnnn:mmm is a file format.
nnn is the file type number. A 3-digit decimal number in the range of 000 to 999 can be set.
mmm is the element number. A 3-digit decimal number in the range of 000 to 999 can be set.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.3 Accessible Files PLC-5>

J11-11

Table Basic Command PLC-5

Title
Bit access
Word access

Address(*1)

Unprotected bit write mmmmmm05

Basic command (CMD)

Read

Write

05

Unprotected read

mmmmmm01

01

Unprotected write

mmmmmm08

08

Remark

J110302E.EPS

*1:

mmmmmm is the data address. An octal number in the range of 000000 to 777777 can be set.

SEE ALSO
For details on file type numbers, element numbers and data addresses, refer to the users manual for the
PLC-5 to be connected.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.4 Subsystem Data Storing Format PLC-5>

J11-12

J11.4 Subsystem Data Storing Format PLC-5

The following explains the format in which subsystem data acquired from the PLC-5
is stored in the FCS.
The storing formats for PLC-5 bit files and word files are given below:

Bit File PLC-5

When 16 m number (m=1, 2, ...) of bit devices are read starting from address n, the
PLC-5 data is stored in the FCS as indicated below. The data size is specified as m via the
Communication I/O Builder.
16 bits
n n n n n n
+ + + + + +
15 14 13 12 11 10

n
+
9

n
+
8

n
+
7

n
+
6

n
+
5

n
+
4

n
+
31

n
+
3

n
+
2

n
+
1

m=1

n
+
16

m=2

n+16 (m-1)

n+16 (m-1)+15

J110401E.EPS

Figure Image of Stored Bit File PLC-5

Word File PLC-5

When m number of word files are read starting from address n, the PLC-5 data is stored in
the FCS as indicated below:
16 bits

Contents of the nth register

Contents of the nth register

Contents of the n+m-1th register

J110402E.EPS

Figure Image of Stored Word File PLC-5

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.5 Setting Items on System View PLC-5>

J11-13

J11.5 Setting Items on System View PLC-5

PLC5

In this section, setting items on System View for PLC-5, the specific functionality
and the recommended settings are explained.
SEE ALSO
For more information regarding to Set Details tab on Create New IOM dialog box and subsystem
common settings, see the following:
Setting Items for ACM11, ACM12 in J1.5.1, Overview of Setting Items on System View

For PLC-5, the setting items are as follows. This setting is done on the Set Details
tab of the New IOM dialog box called from the System View.
Connection Device
Baud Rate
Parity
Data Bits
Stop Bits
RS Control
DR Check
CD Check
Communication Error Process
Options
After creating the new I/O module, the settings can be modified on the I/O module
property sheet.

Connection Device PLC-5

Set [PLC5] as the type of connection device (subsystem).
Must perform this setting since the default is [FA-M3].

Baud Rate PLC-5

This sets the baud rate between the communication I/O module and PLC-5.
Recommended setting is [9600 bps].

IMPORTANT
The default setting is [19200 bps] and PLC-5 can not use 19200bps, so that this setting
must be changed.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.5 Setting Items on System View PLC-5>

J11-14

Parity PLC-5
This sets the method for checking the parity of the subsystem data to be transmitted.
The recommended setting is [Even] parity.
An odd parity cannot be used for PLC-5.
The parity set on Set Details tab should match the parity setting on the PLC-5.

Data Bits PLC-5

This sets the data bit length of the subsystem data to be transmitted.
When using the PLC-5, always select [8 bits] for the data bit length.

IMPORTANT
For PLC-5, a communication error will occur if [7 bits] is selected.

Stop Bits PLC-5

This sets the stop bit of the subsystem data to be transmitted.
When using the PLC-5, select [1 bit] for the stop bit.

IMPORTANT
For PLC-5, [2 bits] cannot be selected as stop bit.

RS Control PLC-5
This sets whether or not RS control is performed during subsystem data transmission.
When using the PLC-5, disable RS control by leaving the [RS control] check box unchecked.

DR Check PLC-5
This sets whether or not DR check is performed during subsystem data transmission.
When using the PLC-5, enable the DR check by checking [DR check] check box.

CD Check PLC-5
This sets whether or not CD check is performed during subsystem data transmission.
When using the PLC-5, disable CD check by leaving the [CD check] check box unchecked.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.5 Setting Items on System View PLC-5>

J11-15

Communication Error Process PLC-5

This sets the parameters related to communication error handling during subsystem data
transmission. This setting is done using the Set Details tab of the New IOM dialog box
called from System View.
The setting items include the following three:
Response Timeout
This sets the time for detecting no response in the PLC-5. The setting unit is seconds.
Recommended setting is 4.
Number of Retries Upon Response Timeout
This sets the number of retries when a communication error occurs.
Recommended setting is 1.
Interval of Connection Retries
This sets the time interval for FCS to send a communication request packet to the
station that a communication error occurred. The setting unit is seconds.
Recommended setting is 30.

Options PLC-5
Settings of communication parameter options vary depending on the equipment connected. Set options by clicking the [Option] button in the Set Details tab of the New IOM
dialog box called from System View.
In the case of PLC-5, define the station number of the PLC-5 link module at the Option 1.
Octat numbers are used for settings. Define 0 at the Options 2 to 4.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.6 Setting Items on Communication I/O Builder PLC-5>

J11-16

J11.6 Setting Items on Communication I/O Builder

PLC-5
In this section, setting items on communication builder for PLC-5, the specific
functionality and the recommended settings are explained.
SEE ALSO
For an overview of the setting items on Communication I/O Builder, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

For PLC-5, the setting items are as follows.

Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

Element PLC-5
Element

With respect to the address of the subsystem data buffer area, the element numbers are
displayed on Communication I/O Builder. The element number cannot be set, only displayed.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.6 Setting Items on Communication I/O Builder PLC-5>

J11-17

Buffer PLC-5
Buffer

This sets the buffer for the communicated data.

Must set the buffer size since this is a required setting item of the Communication I/O
Builder.

Program Name PLC-5 : PFCS/SFCS

Program Name

Set the unit number, slot number and PLC5 as program name in the following format:
u-sProgramName
u:
Unit number
s:
Slot number
ProgramName: PLC5

Program Name PLC-5 : LFCS2/LFCS

Program Name

Set the node number, unit number, slot number and PLC5 as Program Name in following
format:
n-u-sProgramName
n:
u:
s:
ProgramName:

Node number
Unit number
Slot number
PLC5

Size PLC-5
Size

This item sets the data size (data length) from the head address set in Device & Address.
Must set the Size since this is a required setting item on Communication I/O Builder.
For PLC-5, the setting ranges are limited as follows, the unit is in Word.
Bit File:

1 to 16

Word File: 1 to 114

SEE ALSO
For more information about Size setting item, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.6 Setting Items on Communication I/O Builder PLC-5>

J11-18

Port PLC-5
Port

Port 1 is set for use.

IP Address PLC-5
IP Address

No need to set IP address.

Station PLC-5
Station

This sets the station number of the PLC-5 on the Data Highway or Data Highway Plus that
performs communication.
The station numbers are set using an octal value.

Device & Address PLC-5

Device & Address

This sets the head address of PLC-5 data. This setting is done via the Communication I/O
Builder.
The addresses that can be set are shown below:
Output image file: O000:mmm
Input image file:

I001:mmm

Status file:

S002:mmm

Bit file:

B003:mmm

Timer file:

T004:mmm

Counter file:

C005:mmm

Control file:

R006:mmm

Integer file :

N007:mmm

Floating-point file: F008:mmm

The mmm can be set using a value between 000 and 999.
SEE ALSO
For details on address setting, see the following:
J11.3, Accessible Files PLC-5

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.6 Setting Items on Communication I/O Builder PLC-5>

J11-19

Data Type PLC-5

Data Type

This sets data type of the subsystem data.

The data type can be selected from the following:
Input (16-Bit Signed)
Input (32-Bit Signed)
Input (16-Bit Unsigned)
Input (32-Bit Unsigned)
Input (32-Bit Floating)
Output (16-Bit Signed)
Output (32-Bit Signed)
Output (16-Bit Unsigned)
Output (32-Bit Unsigned)
Output (32-Bit Floating)
Input (Discrete)
Output (Discrete)

Reverse PLC-5
Reverse

This sets whether or not to make the bit or word arrangement in FCS in reverse order of the
subsystem data.
The following settings can be selected:
Bits
No
Words
However, when choosing [Bits], only the data of discrete inputs or discrete outputs can be
reversed. In this case, the default setting is [Bits].
Regarding to words, only the 32-bit analog inputs or the 32-bit analog outputs can be
reversed. In this case the default setting is [No].

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.6 Setting Items on Communication I/O Builder PLC-5>

J11-20

Scan PLC-5
Scan

Set whether to read the communication I/O analog data into the communication I/O data
buffer at the beginning of high-speed scan of the FCS.

Service Comment PLC-5

Service Comment

A comment text can be set.

Label PLC-5
Label

The name of the function block I/O terminal can be set as a user-defined label.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J11-21

<J11.7 Communication Packet PLC-5>

J11.7 Communication Packet PLC-5

This section explains the communication packet format for the communication with
the PLC-5.

Communication Packet for Bit Write PLC-5

The figure below shows the communication packet format for bit write:
Command
DLE SOH STN DLE
10

NUL

01

00

09

ID

10

STX DST SRC CMD STS TNS

02

FILE NO

24

01

00

0F

00

ELM NO

FNC

DLE

26

10

NUL AND MSK

3A

ETX BCC
03

OR MSK

00

Maximum of 16-word data

Response
DLE STX DST SRC CMD STS TNS
10

02

DST:
STN:
CMD:
TNS:
FNC:
ID:
FILE NO:
ELM NO:
AND MSK:
OR MSK:
STS:

09

01

4F

DLE
10

ETX BCC
03

Station number of PLC-5

Station number of the PLC-5 link module
Command
Transaction code
Function code
26 for bit write
File identification number
File number
Element number
Logical operation specification
Turn on the bit that needs to be reset.
Logical sum operation specification
Turn off the bit that needs to be reset.
0 is a normal response.
J110701E.EPS

Figure Communication Text for Bit Write PLC-5

TIP
With AND MSK and OR MSK, the most and least significant byte are reversed.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J11-22

<J11.7 Communication Packet PLC-5>

Communication Packet for Block Read PLC-5

The figure below shows the communication packet format for block read:
Command
DLE SOH STN DLE
10

01

PCT OST

09

10

TTL TNS

STX DST SRC CMD STS TNS

02

NUL
00

01

00

ID

0F

00

FILE NO

24

FNC

DLE

01

10

ELM NO

3A

ETX BCC
03

NUL SIZ
00

Maximum of 16-word data

Response (normal)
DLE
10

STX DST SRC CMD STS

02

01

TNS

DATA

DLE

4F

10

ETX BCC
03

Response (abnormal)
DLE
10

STX DST SRC CMD STS TNS

02

DST:
STN:
CMD:
TNS:
FNC:
ID:
FILE NO:
ELM NO:
PCT OST:
TTL TNS:
SIZ:
STS:

08

4F

DLE
10

ETX BCC
03

Station number of PLC-5

Station number of the PLC-5 link module
Command
Transaction code
Function code
01 for block read
File identification number
File number
Element number
Packet offset, always 0
Sum of data (in word)
Sum of data (in byte)
0 is a normal response.
J110702E.EPS

Figure Communication Packet for Block Read PLC-5

TIP
With 2-byte data, the most and least significant byte are reversed.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.7 Communication Packet PLC-5>

J11-23

Communication Packet for Block Write Change PLC-5

The figure below shows the communication packet format for block write change:
Command
DLE SOH STN DLE
10

01

09

PCT OST

TTL

10

STX DST SRC CMD STS TNS

02

TNS NUL
00

01

00

ID

0F

00

FILE NO

24

FNC

DLE

00

10

FILE NO

3A

ETX BCC
03

NUL DATA
00

Response
DLE

STX DST SRC CMD STS TNS

10

02

DST:
STN:
CMD:
TNS:
PCT OST:
TTL TNS :
STS:

09

08

4F

DLE
10

ETX BCC
03

Station number of PLC-5

Station number of the PLC-5 link module
Command
Transaction code
Packet offset, always 0
Sum of data (in word)
0 is a normal response.
J110703E.EPS

Figure Communication Text for Block Write Change PLC-5

TIP
With 2-byte data, the most and least significant byte are reversed.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.8 System Alarm Messages Specific to PLC-5>

J11-24

J11.8 System Alarm Messages Specific to PLC-5

This section explains the system alarm messages that are specific to PLC-5.

System Alarm Message Sent when a Communication Error Occurs

PLC-5 : PFCS/SFCS
When there is a communication error, the system alarm message as shown below is sent
to HIS:
STNss SS-COM Error UNITmm SLOTnn STNzzz CODE=####
STNss:
mm:
nn:
zzz:
####:

FCS name
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. After that, a new system alarm message
will not be sent even if an error is generated by a different cause.
SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs PLC-5

System Alarm Message when a Communication Error Occurs PLC-5 :

LFCS2/LFCS
When a communication error occurs, the system alarm message as shown below is sent to
HIS:
STNss SS-COM Error RIO01 NODExx UNITmm SLOTnn STNzzz CODE=####
STNss:
xx:
mm:
nn:
zzz:
####:

FCS name
Node number
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. The new system alarm message will not
be transmitted even if errors are generated by different causes.
SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs PLC-5

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.8 System Alarm Messages Specific to PLC-5>

J11-25

System Alarm Message Sent when Communication Returns to Normal

PLC-5 : PFCS/SFCS
When communication returns to the normal condition, the system alarm message indicated
below is sent to HIS:
STNss SS-COM Recover UNITmm SLOTnn TNzzz
STNss:
mm:
nn:
zzz:

FCS name
Unit number
Slot number
Subsystem station number

System Alarm Message when Communication Returns to Normal

PLC-5 : LFCS2/LFCS
When communication returns to normal status, the system alarm message indicated below
is sent to HIS:
STNss SS-COM Recover RIO01 NODExx UNITmm SLOTnn STNzzz
STNss:
xx:
mm:
nn:
zzz:

FCS name
Node number
Unit number
Slot number
Subsystem station number

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.8 System Alarm Messages Specific to PLC-5>

J11-26

Error Codes when a Communication Error Occurs PLC-5

The following are the error codes when communication error occurs:
Table Error Codes when a Communication Error Occurs PLC-5 (1/2)
Error code (hexadecimal)

Description

A391

Communication driver busy

A392

Communication line busy

A393

Communication line not ready

A394

Sending size is too large

A395

Use of communication port not declared

A397

Under run error

A398

Timeout between received characters

A399

Receive buffer overflow

A39A

Parity error in receive data

A39B

Receiving overrun error

A39C

Receiving framing error

A39D

No. of characters received is outside specifications

A39F

Other error

A3B0

Error in PLC-5 station number

A3B1

PLC-5 address does not accept a command code.

A3B2

OCT BIN error in basic command address

A3B3

Basic command address is outside the range

A3B4

DEC BIN error in PLC-5 command file number

A3B5

PLC-5 command file number is outside the range

A3B6

DEC BIN error in PLC-5 command element number

A3B7

PLC-5 command element number is outside the range

A3B8

Size error
J110801E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.8 System Alarm Messages Specific to PLC-5>

J11-27

Table Error Codes when a Communication Error Occurs PLC-5 (2/2)

Error code (hexadecimal)

Description

A3C1

Invalid command or format

A3C2

Cannot communicate due to problem at host

A3C3

Remote host does not exist, is disconnected, or shut down

A3C4

Host cannot complete the function due to hardware problem

A3C5

Addressing problem or memory protection problem

A3C6

Function cannot be executed due to command protect selection

A3C7

Processor in program mode

A3C8

No compatible mode file, or communication zone problem

A3C9

Remote node cannot buffer the command.

A3CB

Remote node problem due to download

A3CF

Error during EXT STS byte

A3D0

Error in received data size

A3D1

BCC error

A3D2

Transaction code error for received data

A3D3

Format error in received data

A3D4

EOT for received data reached 100 times

A3D5

Received undefined packet

A3E0

No response

A3E1

Reception time out

A3E2

Exceeded the retry count

J110802E.EPS

SEE ALSO
For details on the contents of the errors, refer to the users manual for the PLC-5 being used.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J11-28

<J11.9 Transmission Time between Communication Module and PLC-5>

J11.9 Transmission Time between Communication

Module and PLC-5
The transmission time between communication module and PLC-5 subsystem is to
be discussed in this chapter.

Communication Time PLC-5

The time required for communication between a communication I/O module and PLC-5 is
figured as the total of the time T1 to T12. In the subsystem communication with PLC-5, T5
through T8 are repeated seven times, although the number of times repeated may change.
Communication
module

Create transmission
message

ENQ

ENQ

*2

PLC-5
link module
EOT

ACK
T1

T2

T3

T4

T5

T6

T7

*1
T8

T6

T9 T10 T11 T12

J110901E.EPS

*1 :
*2 :
T1:
T2:
T3:
T4:
T5:
T6:
T7:
T8:
T9:
T10:
T11:
T12:

Response interpretation + ACK

PLC-5 response message processing time
Create transmission packet. About 10 ms
Packet transmission
PLC-5 ACK + EOT. About 3 ms
Response transmission
Communication module ENQ processing time. Approximately 5 ms
Communication module ENQ transmission time
PLC-5 EOT processing time. Approximately 3 ms
PLC-5 EOT transmission time. Approximately 2 ms
PLC-5 response message processing time. Approximately 3 ms
Response process
Response interpretation + ACK. About 15 ms
Communication module ACK transmission time. Approximately 2 ms

Figure Time Chart of Communication between Communication Module and PLC-5

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.9 Transmission Time between Communication Module and PLC-5>

J11-29

How to Calculate the Communication Time PLC-5

The send message transmission time (T2), communication module ENQ transmission time
(T6), PLC-5 link module EOT transmission time (T8) and the response message transmission time (T4, T10) are calculated using the following formula.
Also, the communication module ENQ transmission time is figured as 4 bytes, while the
PLC-5 link module EOT transmission time and the response message transmission time
are figured as 2 bytes.

Transmission time (ms) = No. of characters to be sent no. of bits per character 1000
Baud rate (bps)
No. of bits
per character

start bit

data bit

parity bit

stop bit
J110902E.EPS

Start bit:
Data bit:
Parity bit:
Sop bit:
Baud rate:

1 bit fixed
8 bits fixed (7 bits not possible)
None, even
1 bit fixed
1200, 2400, 4800, 9600 (bps)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J11.9 Transmission Time between Communication Module and PLC-5>

J11-30

Calculation Example for Communication Time PLC-5

When the output data type is set via the Communication I/O Builder, the subsystem communication package reads data from the subsystem before it writes for that definition. Then
the package compares the data read from the subsystem with the FCS data and only
writes data of differing value to the subsystem.
Because of this, it is difficult to calculate the time required for communication when writing
data to a subsystem since the transmission time varies according to the number of data in
which the value has changed. Therefore, use the following guidelines for communication
time when writing to the subsystem.
When the values for most of the data to be written are not changed
Communication time = The time required for transmission when reading data from the
subsystem with respect to all definitions where write has been designated
When the values for a large number of the data to be written are changed
Communication time = About twice the amount of time required for transmission when
reading data from the subsystem with respect to all definitions where write has been
designated
The following is an example of calculating the time required for communication between a
communication I/O module and the PLC-5:
Baud Rate:

9600 bps

Number of characters per dat:

Number of bits per character:

11

Request frame (read):

31 bytes

PLC ACK, EOT:

2 bytes

ACM ENQ:

4 bytes

PLC response message:

64 data
Analog data N009:001 to 065
11+2 64=139 bytes

ACM ACK:

2bytes

T2=31 11 1000/9600=35.52 (ms)

T4, T8=2 11 1000/9600=2.29 (ms)
T6=4 11 1000/9600=4.58 (ms)
T10=139 11 1000/9600=159.27 (ms)
Communication time

=T1+T2+T3+T4+7 (T5+T6+T7+T8) +T6+T9+T10+T11+T12

=10+35.52+3+2.29+7 (5+4.58+3+2) +4.58+3+159.27+15+2
=336.72 (ms)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12. SYSMAC Communication>

J12-1

J12. SYSMAC Communication

The SYSMAC communication package is designed for subsystem communication
with the SYSMAC C-Series PCs manufactured by Omron (hereinafter referred to as
SYSMAC). By using the SYSMAC communication package, communication between
the FCS and SYSMAC can be performed without a customized program.
This chapter explains the communication between the SYSMAC and FCS among the
subsystem communication packages.
SEE ALSO
Regarding the functions common to different subsystem communication packages, see the following:
J1, General Information Regarding to Subsystem Communication

Applicable Models SYSMAC

For the SYSMAC communication package, the following product is available:
PFS 9063 CS 1000 SYSMAC communication package (ACM11, ACM12)
LFS 9063 CS 3000 SYSMAC communication package (ACM11, ACM12)
The SYSMAC communication package performs a subsystem communication between
FCS and SYSMAC by connecting the SYSMACs upper link unit to a communication
module (ACM11 or ACM12).
The following upper link units of SYSMAC can be connected to ACM11 or ACM12:
C200H-LK201-V1, -LK202-V1
C500-LK201-V1, -LK203
C120-LK201-V1, -LK202-V1

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J12.1 Communication Specifications SYSMAC>

J12-2

J12.1 Communication Specifications SYSMAC

This section explains the specifications when performing subsystem communication with the SYSMAC.

Communication Capacity SYSMAC

The capacity specific to SYSMAC when performing subsystem communication with the
SYSMAC are indicated below:
Table Capacity of Communication between FCS and SYSMAC
Item

Maximum quantity

Explanation

Amount of data that can be communicated with

one communication module

500 words
(1 word=16 bits)

Maximum amount that can be

accessed from the regulatory control
block or sequence control block.

Number of subsystem stations that can be

communicated with one communication module

30 stations

Data size in one communication frame

Word Device: 29 words One frame is defined in one line on

Bit Device: 7 words the builder. It is the same as
(112 bits) restricted by SYSMAC protocol.
J120101E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.1 Communication Specifications SYSMAC>

J12-3

Transmission Specifications SYSMAC

The table below lists the transmission specifications when performing subsystem communication with the SYSMAC:
Table Transmission Specifications SYSMAC
Description

Item

Remark

RS-232C

ACM11

RS-422

ACM12

Transmission method

Half duplex

1 to 1 procedure fixed

Synchronization method

Start-stop synchronization

Baud rate (bps)

1200, 2400, 4800, [9600],

19200

Transmission code

ASCII

Interface

Data type

Control line

Time monitoring

Text frame

(*1)

Start bit

Data bit

Must specify 7 via the New IOM

dialog box called from the System View.

Parity bit

[Even], odd

(*1)

Stop bit

Must specify 2 via the New IOM

dialog box called from the System View.

RS

Always ON

DR

Transmit when ON

CD

Always ON

ER

Always ON

CS

Transmit when ON

Transmission enable
monitoring time

1000ms

Reception character interval

monitoring time

1500ms

Character interval
timeout processing

Regarded as an error

Reception start character

None

EOT character

$0D(CR)

XON/XOFF control

None

No response time setpoint

0 to 99 sec [4 sec]

(*1)

No. of communication retries

0 to 99 times [one time]

(*1)

Recovery communication time interval

0 to 999 sec [30 sec]

(*1)

Number of words that can be handled in

one communication packet

Word device 29
Bit device 7

Item

Remark

Description

J120102E.EPS

Note: [ ] indicates the recommended settings.

*1:
This can be changed using the Property dialog box called from the System View.

IMPORTANT
When performing subsystem communication with the SYSMAC, be sure to specify [7 bits]
for the data bit length. A communication error will occur if [8 bits] is specified.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.2 Connecting FCS and SYSMAC>

J12-4

J12.2 Connecting FCS and SYSMAC

This section explains the connection type and cable connections between FCS and
SYSMAC.

Connection Type SYSMAC

An example of connection between FCS and SYSMAC is shown below:
HIS

Control bus

FCS

ACM11 (RS-232C communication module)

RDY
RCV
SND

CN1

RDY
RCV
SND

AMN33 (communication module nest)

CN1

RS-232C
MODEM

MODEM
RS-232C

SYSMAC

J120201E.EPS

Figure Example of Connection between FCS and SYSMAC

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.2 Connecting FCS and SYSMAC>

J12-5

Cable Connection when Using the ACM11 SYSMAC

The cable with RS-232C D-sub 25 pin connector is used for cable connection of the ACM11
and SYSMAC.
The ACM11 and SYSMAC must be connected via a modem. However, they can be connected directly if the length of RS-232C cable between ACM11 and SYSMAC is 15 meters
or less and the grounding systems of ACM11 and SYSMAC are the same.

IMPORTANT
The cable length between the ACM11 and modem as well as between the modem and
SYSMAC must be 15 meters or less.

Table RS-232C D-sub 25 Pin Connector Specifications SYSMAC

Title

Direction of signal

Pin number

Signal name

FG

Safety grounding

SD

Send data

RD

Receive data

RS

Request to Send

When there is a send request, ON is output

(SYSMAC not used)

CS

Clear to Send

When OFF, transmission to the outside is not

possible. (SYSMAC not used)

DR

Data Ready

Detects whether sending and receiving with

correspondent are allowed.

SG

Signal ground

CD

Carrier Detect

20

ER

Data terminal ready

ACM11

SYSMAC

Description

When sending and receiving are allowed,

ON is output. (SYSMAC not used)
J120202E.EPS

Pin No. 25

Pin No. 14

Pin No. 13

Pin No. 1
J120203E.EPS

Figure Pin Assignment of the RS-232C D-sub 25 Pin Connector SYSMAC

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.2 Connecting FCS and SYSMAC>

J12-6

The following shows when the SYSMAC and ACM11 are connected directly without modem:
SD
RD
RS
CS
ACM11

DR
CD
ER
SG
FG

20

20

Sheathed cable

SD
RD
RS
CS
DR

SYSMAC

CD
ER
SG
FG

Protective ground (100 ohms or less)

J120204E.EPS

Figure Cable Connection between SYSMAC and ACM11 (when connected directly)

With the ACM11, the RS-232C circuit and FG (frame ground) are electrically insulated. This
has the function of preventing intrusion of noise from the SYSMAC side and improving
noise resistance. Satisfy all conditions given below to make this function effective:
For the frame ground, perform protective grounding (100 ohms or less) at the opposing side of the connection (the modem or SYSMAC side).
Attach only one side of the shield of the sheathed cable to the FG of the opposing side
of the connection. Do not ground the cable shield on the ACM11 side. Also, do not use
a connector shell that is conductive.
Connect the FG and the SG (signal ground) of RS-232C circuit at the opposing side of
the connection. When the FG and SG are not connected at the opposing side of the
connection, use an RS-232C cable manufactured by Yokogawa Electric: AKB141
(RS-232C modem cable) or AKB142 (RS-232C null-modem cable). Both AKB141 and
AKB142 have SG and FG connected inside the connector shell. The cable shield can
also be connected to the FG at the opposing side of the connection.
However, the cable AKB142 (RS-232C null-modem cable) is different from the cable
shown in the figure of Cable Connection between SYSMAC and ACM11 (when
connected directly).
If the AKB142 cable is used, you need to check if the ER signal on SYSMAC side (pin
20) is ON for reception.
If the ER signal is always OFF, you need to use the cable shown in the figure of Cable
Connection between SYSMAC and ACM11 (when connected directly).
SEE ALSO
For details on cable connections, see the following:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)

IM 33S01B30-01E

13th Edition : Dec.26,2005-00

<J12.2 Connecting FCS and SYSMAC>

J12-7

Cable Connection Using the ACM12 SYSMAC

The following explains the cable connection when connecting the ACM12 and SYSMAC:
ACM12

SYSMAC

ACM12

SYSMAC

TX +

SDA

TX +

SDA

TX -

SDB

TX -

SDB

RX +

RDA

RX +

RDA

RX -

RDB

RX -

RDB

SG

SG

SG

SG

FG

FG

FG

FG

(4-wire connection)

(2-wire connection)
J120205E.EPS

Figure 1 to 1 Connection via RS-422 SYSMAC

ACM12
TX +
TX RX +
RX SG
FG

SYSMAC

SYSMAC

SYSMAC

SDA

SDA

SDA

SDB

SDB

SDB

RDA

RDA

RDA

RDB

RDB

RDB

SG

SG

SG

FG

FG

FG
J120206E.EPS

Figure 1 to n Connection via RS-422 (4-wire connection) SYSMAC

IMPORTANT
The 1 to n 2-wire connection is not supported in the communication between ACM12 and
SYSMAC.

With the ACM12, the FG (frame ground) and the SG (signal ground) for the RS-422 are
separated. Treat the shield for the RS-422 as follows:
Perform protective grounding (100 ohms or less) for the FG at the opposing side of the
connection (SYSMAC side).
Connect the shield for the cable between ACM12 and SYSMAC to the FG of the
SYSMAC side. Do not connect it to the FG of the ACM12 side.
SEE ALSO
For details on cable connections, see the following:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)

When connecting the ACM12 and SYSMAC, it is necessary to attach a terminating register
on each side.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.2 Connecting FCS and SYSMAC>

J12-8

Setting a Terminating Register on the ACM12 Side SYSMAC

When connecting the ACM12 and SYSMAC, it is necessary to install a terminal resistor
(120 ohms 1/2W) between the RX+terminal and RX-terminal on the ACM12 side. The
ACM12 is shipped with a terminal resistor installed between the RX+terminal and RXterminal.
Set the connection method (4-wire or 2-wire ) using the 2-pole DIP switch (SW1) attached
to the ACM12. The unit is shipped from the factory with a 4-wire connection setting.
Table SW1 Setting for the ACM12 SYSMAC
Connection method

SW1 setting for ACM12

2-wire

ON

ON

4-wire

OFF

OFF
J120207E.EPS

Setting a Terminating Register on the SYSMAC Side

On the SYSMAC side, the setting of a terminal register differs depending on the type of link
unit of the SYSMAC connected.
SEE ALSO
For details on the SYSMAC side setting, refer to the manual for the SYSMAC being connected.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J12-9

<J12.3 Accessible Devices SYSMAC>

J12.3 Accessible Devices SYSMAC

SYSMAC internal data are called devices. The SYSMAC devices are bit devices and
word devices.
Bit device
This refers to data where each bit has a meaning. The timer relay and counter
switches one bit devices.
Word device
This refers to data where a word unit (1 word=16 bits) contains the meaning. An
LR area data is equivalent to a word device.

Accessible Devices SYSMAC

Table Accessible Devices SYSMAC
File type

Device name

Status
Bit device

Error
Timer/counter up data

IR area read/write

HR area read/write

AR area read/write
Word device
LR area read/write

DM area read/write

PV area read/write

Address (*1)

Header code

Size setting
range

Read

Write

YSTR

MS

YSTW

SC

YERR

MF

AGnnnn

RG

WG

1 to 7

XGnnnn

WG

1 to 7

ARnnnn

RR

WR

1 to 29

XRnnnn

WR

1 to 29

AHnnnn

RH

WH

1 to 29

XHnnnn

WH

1 to 29

AJnnnn

RJ

WJ

1 to 29

XJnnnn

WJ

1 to 29

ALnnnn

RL

WL

1 to 29

XLnnnn

WL

1 to 29

ADnnnn

RD

WD

1 to 29

XDnnnn

WD

1 to 29

ACnnnn

RC

WC

1 to 29

XCnnnn

WC

1 to 29
J120301E.EPS

*1:

The nnnn portion of an address can be set using a value between 0000 and 9999. However, the range in which the
setting can actually be made varies depending on the type of the SYSMAC being connected.
If the head address is A, read is done in word units and write in word units with readback.
If the head address is X, read is done in word units and write in word units without readback.

SEE ALSO
For details on address, see the SYSMAC C-Series Upper Link Unit (SBCC-398F).

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.4 Subsystem Data Storing Format SYSMAC>

J12-10

J12.4 Subsystem Data Storing Format SYSMAC

The following section explains the format in which subsystem data acquired from
the SYSMAC is stored in FCS.
The storing formats for SYSMAC bit devices and word devices are given below:

Bit Device SYSMAC

When 16 m number (m = 1, 2, ...) of bit devices are read starting from address n , the
SYSMAC data is stored in the FCS as indicated below. The data size is specified as m via
the Communication I/O Builder.
16 bits
n n n n n n
+ + + + + +
15 14 13 12 11 10

n
+
9

n
+
8

n
+
7

n
+
6

n
+
5

n
+
4

n
+
3

n
+
31

n
+
2

n
+
1

m=1

n
+
16

m=2

n+16 (m-1)+15

The corresponding bit numbers

for header codes MS, MF, SC,
RG and WG are as follows:
160
0 to 3
161
4 to 7
162
8 to 11
12 to 15
163

n+16 (m-1)
J120401E.EPS

Figure Image of Stored Bit Device SYSMAC

Word Device SYSMAC

When m number of word devices are read starting from address n, the SYSMAC data is
stored in the FCS as indicated below:
16 bits

Contents of the nth register

Contents of the n+1th register

Contents of the n+m-1th register

J120402E.EPS

Figure Image of Stored Word Device SYSMAC

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.5 Setting Items on System View SYSMAC>

J12-11

J12.5 Setting Items on System View SYSMAC

SYSMAC

In this section, setting items on System View for SYSMAC, the specific functionality
and the recommended settings are explained.
SEE ALSO
For more information regarding to Set Details tab on Create New IOM dialog box and subsystem
common settings, see the following:
Setting Items for ACM11, ACM12 in J1.5.1, Overview of Setting Items on System View

For SYSMAC, the setting items are as follows. These settings are performed on the
Set Details tab of the New IOM dialog box called from System View.
Connection Device
Baud Rate
Parity
Data Bits
Stop Bits
RS Control
DR Check
CD Check
Communication Error Process
Options
After creating the new I/O module, the settings can be modified on the I/O module
property sheet.

Connection Device SYSMAC

Set [SYSMAC] as the type of connection device (subsystem).
Must perform this setting since the default is [FA-M3].

Baud Rate SYSMAC

This sets the baud rate between the communication module and SYSMAC.
The recommended baud rate is [9600 bps].
The default is [19200 bps].

Parity SYSMAC
This sets the method for checking the parity of the subsystem data to be transmitted.
The recommended setting for the parity is [Even].
When using SYSMAC, [No] parity cannot be used as parity setting.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.5 Setting Items on System View SYSMAC>

J12-12

Data Bits SYSMAC

This sets the data bit length of the subsystem data to be transmitted.
When using the SYSMAC, always select [7 bits] for the bit length.
Be sure to confirm the setting since the default is [8 bits].

IMPORTANT
For the SYSMAC, a communication error will occur if [8 bits] is selected.

Stop Bits SYSMAC

This sets the stop bit of the subsystem.
When using the SYSMAC, select [2 bits] for the stop bit.
Always make the setting since the default is [1 bit].

IMPORTANT
For the SYSMAC, a communication error will occur if [1 bit] is selected.

RS Control SYSMAC
This sets whether or not RS control is performed during subsystem data transmission.
When using the SYSMAC, disable RS control by leaving the [RS control] check box unchecked.

DR Check SYSMAC
This sets whether or not DR check is performed during subsystem data transmission.
When using the SYSMAC, enable the DR check by checking the [DR check] check box.

CD Check SYSMAC
This sets whether or not CD check is performed during subsystem data transmission.
When using the SYSMAC, disable the CD check by leaving the [CD check] check box
unchecked.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.5 Setting Items on System View SYSMAC>

J12-13

Communication Error Process SYSMAC

This sets the parameters related to communication error handling during subsystem data
transmission.
The following three items must be set.
Response Timeout
This sets the time limit for getting response from SYSMAC. The time is set in unit of
seconds.
Recommended setting is [4].
Number of Retries Upon Response Timeout
This item sets the number of retries performed when a communication error occurs.
Recommended setting is [1].
Interval of Connection Retries
This sets the time interval of connection requests for checking whether the communication with the station that generated a communication error has returned to normal
(communication recovery). The time is set in unit of seconds.
Recommended setting is [30].

Options SYSMAC
Settings of communication parameter options vary depending on the equipment connected. Set options by clicking the [Option] button in the Set Details tab of the New IOM
dialog box called from the System View.
In the case of SYSMAC, when 0 is defined at the Option 1, one-to-one connection is
established; when 1 is defined, one-to-n connection is established. One-to-n connection
is supported on the ACM12 (RS-422) only.
For the Options 2 to 4, define 0.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.6 Setting Items on Communication I/O Builder SYSMAC>

J12-14

J12.6 Setting Items on Communication I/O Builder

SYSMAC
In this section, setting items on Communication I/O Builder for SYSMAC, the specific functionality and the recommended settings are explained.
SEE ALSO
For an overview of the setting items on Communication I/O Builder, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

For SYSMAC, the setting items are as follows.

Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

Element SYSMAC
Element

With respect to the address of the subsystem data buffer, the element numbers are displayed on Communication I/O Builder. The element number is not for set, only for display.

Buffer SYSMAC
Buffer

This sets the buffer for communicated data.

Must set the buffer since this is a required setting item of the Communication
I/O Builder.

Program Name SYSMAC : PFCS/SFCS

Program Name

Set the unit number, slot number and SYSMAC as program name in the following format.
u-sProgramName
u:
s:
ProgramName:

Unit number
Slot number
SYSMAC
IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.6 Setting Items on Communication I/O Builder SYSMAC>

J12-15

Program Name SYSMAC : LFCS2/LFCS

Program Name

Set the node number, unit number, slot number and SYSMAC as Program Name in the
following format.
n-u-sProgramName
n:
u:
s:
ProgramName:

Node number
Unit number
Slot number
SYSMAC

Size SYSMAC
Size

This item sets the data size (data length) from the head address set in Device & Address.
Must set the Size since this is a required setting item on Communication I/O Builder.
For SYSMAC, the setting ranges are limited as follows, the unit is in Word.
Status:

Error:

Timer/counter up data:

1 to 7

IR area read/write:

1 to 29

HR area read/write:

1 to 29

AR area read/write:

1 to 29

LR area read/write:

1 to 29

DM area read/write:

1 to 29

PV area read/write:

1 to 29

SEE ALSO
For more information about Size setting item, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

Port SYSMAC
Port

Port 1 is set for use.

IP Address SYSMAC
IP Address

No need to set IP address.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.6 Setting Items on Communication I/O Builder SYSMAC>

J12-16

Station SYSMAC
Station

This sets the station number of the SYSMAC.

The station numbers are set using a value within the range between 0 and 31. Note that
only up to 30 stations can be set.
If an ACM11 or ACM12 is connected with multiple SYSMACs, the station number indicates
the model number of the SYSMAC.

Device & Address SYSMAC

Device & Address

This sets the head address of SYSMAC data.

The addresses that can be set using 4 to 6 alphanumeric characters as shown below:
Status:

YSTR, YSTW

Error:

YERR

Timer/counter up data:

AGnnnn, XGnnnn

IR area read/write:

ARnnnn, XRnnnn

HR area read/write:

AHnnnn, XHnnnn

AR area read/write:

AJnnnn, XJnnnn

LR area read/write:

ALnnnn, XLnnnn

DM area read/write:

ADnnnn, XDnnnn

PV area read/write:

ACnnnn, XCnnnn

The nnnn can be set using a value between 0000 and 9999. However, the range in which
the setting can actually be made varies depending on the type of the SYSMAC being
connected.
SEE ALSO
For more information about address setting, see the SYSMAC C Series Upper Link Unit (SBCC-398F) of
Omron Co.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.6 Setting Items on Communication I/O Builder SYSMAC>

J12-17

Data Type SYSMAC

Data Type

This sets data type of the subsystem data.

The data type can be selected from the following:
Input (16-Bit Signed)
Input (32-Bit Signed)
Input (16-Bit Unsigned)
Input (32-Bit Unsigned)
Input (32-Bit Floating)
Output (16-Bit Signed)
Output (32-Bit Signed)
Output (16-Bit Unsigned)
Output (32-Bit Unsigned)
Output (32-Bit Floating)
Input (Discrete)
Output (Discrete)

Reverse SYSMAC
Reverse

This sets whether or not to make the bit or word arrangement in FCS in reverse order of the
subsystem data.
The following settings can be selected:
Bits
No
Words
However, when choosing [Bits], only the data of discrete inputs or discrete outputs can be
reversed. In this case, the default setting is [Bits].
Regarding to words, only the 32-bit analog inputs or the 32-bit analog outputs can be
reversed. In this case the default setting is [No].

Scan SYSMAC
Scan

Set whether to read the communication I/O analog data into the communication I/O data
buffer at the beginning of high-speed scan of the FCS.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.6 Setting Items on Communication I/O Builder SYSMAC>

J12-18

Service Comment SYSMAC

Service Comment

A comment text can be set.

Label SYSMAC
Label

The name of the function block I/O terminal can be set as a user-defined label.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J12-19

<J12.7 Communication Text SYSMAC>

J12.7 Communication Text SYSMAC

This section explains the communication text used when communicating with the
SYSMAC.

Basic Format of Send Text SYSMAC

The following describes the basic format of send text when communicating with the
SYSMAC:

1 to n System Send Text SYSMAC

The system in which ACM11 or ACM12 communicates with multiple SYSMACs is called 1
to n system. The figure below shows the basic format of 1 to n system send text:
@

Unit
number

Data
122 characters

Header

Unit number :
Data:
FCS:

FCS

CR

"00" to "31"
Varies by the header
Check sum (Frame Check Sum)
J120701E.EPS

Figure 1 to n System Send Text SYSMAC

1 to 1 System Send Text SYSMAC

The system in which ACM11 or ACM12 communicates with a single SYSMAC is called 1
to 1 system. The figure below shows the basic format of 1 to 1 system send text:
Header

Data
124 characters

Data:
FCS:

CR

Varies by the header

Check sum (Frame Check Sum)
J120702E.EPS

Figure 1 to 1 System Send Text SYSMAC

Status Communication SYSMAC

The following shows the communication text format when reading or writing each SYSMAC
device:

Status Read SYSMAC

The figure below shows the format of the communication text for status read:
Send text
@

Unit
number

MS

FCS

MS

Response
Code

CR

Receive text
@

Unit
number

Unit number:
MS:
Status data:
Fixed message:
Response Code:
FCS:

Status data

Fixed message

FCS

CR

"00" to "31"
Header code for status read
"0000" to "FFFF"
16 characters fixed
End code of receive text (error code)
Check sum (Frame Check Sum)
J120703E.EPS

Figure Communication Text for Status Read SYSMAC

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J12-20

<J12.7 Communication Text SYSMAC>

Status Write SYSMAC

The figure below shows the format of the communication text for status write:
Send text
@

Unit
number

SC

Mode data

FCS

CR

SC

Response
Code

FCS

CR

Receive text
@

Unit
number

Unit number:
SC:
Mode data:

"00" to "31"
Header code for status write
"00" is program mode
"01" is debug mode
"02" is monitor mode
"03" is operation mode
End code of receive text (error code)
Check sum (Frame Check Sum)

Response Code:
FCS:

J120704E.EPS

Figure Communication Text for Status Write SYSMAC

Failure Information Read SYSMAC

The figure below shows the format of the communication text for failure information read.
Send text
@

Unit
number

MF

Error clear

MF

Response
Code

FCS

CR

Receive text
@

Unit
number

Unit number:
MF:
Error clear:
Error data 1:
Error data 2:
Response Code:
FCS:

Error data 1

Error data 2

FCS

CR

"00" to "31"
Header code for failure information read
"00" means that "do not cancel the error."
"01" means that "cancel the error."
"0000" to "FFFF"
"0000" to "FFFF"
End code of receive text (error code)
Check sum (Frame Check Sum)
J120705E.EPS

Figure Communication Text for Failure Information Read SYSMAC

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J12-21

<J12.7 Communication Text SYSMAC>

Area Data Communication SYSMAC

Area Data Read SYSMAC
The figure below shows the format of the communication text for area data read.
Send text
@

Unit
number

(*1)

Head address number Number of read data

(*1)

Response
Code

FCS

CR

CR

Receive text
@

Unit
number

Read data 1

Read data 2

Read data n
Unit number:
*1:
Head address number:
Number of read data:
Response Code:
Read data:
FCS:

FCS

"00" to "31"
Header code for area data read
Either RR, RH, RJ, RL or RD
"0000" to "9999"
"0001" to "0029"
End code of receive text (error code)
"0001" to "FFFF"
Check sum (Frame Check Sum)
J120706E.EPS

Figure Communication Text for Area Data Read SYSMAC

Area Data Write SYSMAC

The figure below shows the format of the communication text for area data write:
TIP
Only one word of data is written in one write communication. If multiple words are specified as the data
size via the Communication I/O Builder, write communication will be repeated for the number of words
specified.

Send text
@

Unit
number

Receive text
Unit
@
number

(*1)

Head address number

(*1)

Response
Code

Unit number:
*1:
Head address number:
Response Code:
FCS:

FCS

Write data 1

FCS

CR

CR

"00" to "31"
Header code for area data write
Either WR, WH, WJ, WL or WD
"0000" to "9999"
End code of receive text (error code)
Check sum (Frame Check Sum)
J120707E.EPS

Figure Communication Text for Area Data Write SYSMAC

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J12-22

<J12.7 Communication Text SYSMAC>

Timer/Counter-Up Data Communication SYSMAC

Timer/Counter-Up Data Read SYSMAC
The figure below shows the format of the communication text for timer/counter-up data
read:
Send text
Unit
number

RG

Head timer number

Receive text
Unit
@
number

RG

Response ON/ ON/

Code
OFF OFF

Number of read timers

ON/
OFF

FCS

FCS

CR

CR

Timer data 1
Timer data 2
Timer data n
Unit number:
RG:
Head timer number:
Number of read timers:
Timer data:
Response Code:
FCS:

"00" to "31"
Header code when reading the timer/counter-up data
"0000" to "9999"
"0001" to "0112"
"0" is OFF
"1" is ON
End code of receive text (error code)
Check sum (Frame Check Sum)
J120708E.EPS

Figure Communication Text for Timer/Counter-Up Data Read SYSMAC

Timer/Counter-Up Data Write SYSMAC

The figure below shows the format of the communication text for timer/counter-up data
write:
TIP
Only one word of data is written in one write communication. If multiple words are specified as the data
size via the Communication I/O Builder, write communication will be repeated for the number of words
specified.

Send text
@

Unit
number

WG

Unit
number

Unit number:
WG:
Head timer number:
Timer data 1:
Response Code:
FCS:

ON/
OFF

FCS

CR

Timer data 1

Receive text
@

Head timer number

WG

Response
Code

FCS

CR

"00" to "31"
Header code for timer/counter-up data write
"0000" to "9999"
"0" is OFF
"1" is ON
End code of receive text (error code)
Check sum (Frame Check Sum)
J120709E.EPS

Figure Communication Text for Timer/Counter-Up Data Write SYSMAC

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J12-23

<J12.7 Communication Text SYSMAC>

Timer/Counter Present Value Area Communication SYSMAC

Timer/Counter Present Value Area Read SYSMAC
The figure below shows the format of the communication text for timer/counter present
value area read:
Send text
@

Unit
number

RC

Head timer number

Number of read timers

FCS

CR

CR

Receive text
@

Unit
number

RC

Response
Code

Read timer 1

Read timer 2

Read timer n
Unit number:
RC:
Head timer number:
Number of read timers:
Read timer:
Response Code:
Read data:
FCS:

FCS

"00" to "31"
Header code for timer/counter present value area read
"0000" to "9999"
"0001" to "0029"
"0001" to "9999"
End code of receive text (error code)
"0001" to "FFFF"
Check sum (Frame Check Sum)
J120710E.EPS

Figure Communication Text for Timer/Counter Present Value Area Read SYSMAC

Timer/Counter Present Value Area Write SYSMAC

The figure below shows the format of the communication text for timer/counter present
value area write:
TIP
Only one word of data is written in one write communication. If multiple words are specified as the data
size via the Communication I/O Builder, write communication will be repeated for the number of words
specified.

Send text
Unit
number

WC

Receive text
Unit
@
number

WC

Unit number:
WC:
Head address number:
Write data:
Response Code:
FCS:

Head address
number

Response
Code

FCS

Write data 1

FCS

CR

CR

"00" to "31"
Header code for timer/counter present value area write
"0000" to "9999"
End code of receive text (error code)
Check sum (Frame Check Sum)
J120711E.EPS

Figure Communication Text for Timer/Counter Present Value Area Write SYSMAC

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.7 Communication Text SYSMAC>

J12-24

Communication Text for Test Communication SYSMAC

The figure below shows the format of the communication text when performing a test
communication. The communication text for test communication is used when performing
an error recovery communication.
Send text
@

Unit
number

TS

Test data

FCS

CR

TS

Test data

FCS

CR

Receive text
@

Unit
number

Unit number:
TS:
Test data:
FCS:

"00" to "31"
Header code for test communication
Arbitrary characters except for CR (up to 122 characters)
Check sum (Frame Check Sum)
J120712E.EPS

Figure Communication Text for Test Communication SYSMAC

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.8 System Alarm Messages Specific to SYSMAC>

J12-25

J12.8 System Alarm Messages Specific to SYSMAC

This section explains the system alarm messages that are specific to SYSMAC.

System Alarm Message Sent when a Communication Error Occurs

SYSMAC : PFCS/SFCS
When there is a communication error, the system alarm message as shown below is sent
to HIS:
STNss SS-COM Error UNITmm SLOTnn STNzzz CODE=####
STNss:
mm:
nn:
zzz:
####:

FCS name
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. After that, a new system alarm message
will not be sent even if an error is generated by a different cause.
SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs SYSMAC

System Alarm Message when a Communication Error Occurs

SYSMAC : LFCS2/LFCS
When a communication error occurs, the system alarm message as shown below is sent to
HIS:
STNss SS-COM Error RIO01 NODExx UNITmm SLOTnn STNzzz CODE=####
STNss:
xx:
mm:
nn:
zzz:
####:

FCS name
Node number
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. The new system alarm message will not
be transmitted even if errors are generated by different causes.
SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs SYSMAC

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.8 System Alarm Messages Specific to SYSMAC>

J12-26

System Alarm Message Sent when Communication Returns to Normal

SYSMAC : PFCS/SFCS
When communication returns to the normal condition, the system alarm message indicated
below is sent to HIS:
STNss SS-COM Recover UNITmm SLOTnn STNzzz
STNss:
mm:
nn:
zzz:

FCS name
Unit number
Slot number
Subsystem station number

System Alarm Message when Communication Returns to Normal

SYSMAC : LFCS2/LFCS
When communication returns to normal status, the system alarm message indicated below
is sent to HIS:
STNss SS-COM Recover RIO01 NODExx UNITmm SLOTnn STNzzz
STNss:
xx:
mm:
nn:
zzz:

FCS name
Node number
Unit number
Slot number
Subsystem station number

Error Codes when a Communication Error Occurs SYSMAC

There are following error code types for communication errors:
Definition error
Response message error
Communication error
Other error
SEE ALSO
For details on errors, refer to Omron SBCC-398F SYSMAC C Series Upper Link Unit.

Definition Error
The following errors will occur if the content set via the Communication I/O Builder is
inappropriate. Check the setting made via the Communication I/O Builder when the following errors occur.
Table Definition Errors SYSMAC
Error code
(hexadecimal)

Description

A3B1

Unit number error

A3B2

Inappropriate address name

A3B3

Address number error

A3B4

Inappropriate size

Processing after error occurrence

Communication is not performed.

J120801E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.8 System Alarm Messages Specific to SYSMAC>

J12-27

Response Message Error SYSMAC

The following errors will occur if an error relating to the communication response is included in the response from the SYSMAC. When the following error occur, perform communication retry for the number of times set on the System View.
Table Response Message Error SYSMAC
Error code
(hexadecimal)

Description

Processing after error occurrence

A3C0

Text size error

Retry

A3C1

FCS error

Retry (*1)

A3C2

Unit number error

A3C3

Header code error

A3C4

Data conversion error

A3C5

Test data error

A3C6

Head text error

A3C7

Terminator error

Retry

J120802E.EPS

*1:

If there is still an error during retry, recovery communication is performed using the recovery communication time
intervals set in the New IOM dialog box called from the System View.

SEE ALSO
For details on unit number and header code, refer to Omron SBCC-398F SYSMAC C Series Upper Link
Unit.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.8 System Alarm Messages Specific to SYSMAC>

J12-28

Communication Error SYSMAC

The following errors will occur due to disagreement of transmission specifications between
FCS and SYSMAC, loss of communication data bits, illegible characters, or I/O module
error on the SYSMAC side. When the following errors occur, perform communication retry
for the number of times set on the System View.
Table Error Codes when a Communication Error Occurs SYSMAC (1/2)
Error code
(hexadecimal)

Description

A3D1

Cannot execute due to operation mode (0x01)

A3D2

Cannot execute due to monitor mode (0x02)

A3D3

Cannot execute due to PROM (0x03)

A3D4

Address overflow (0x04)

A3DB

Cannot execute due to program mode (0x0b)

A3DC

Cannot execute due to debug mode (0x0c)

A3DD

Cannot execute due to local mode (0x0d)

A3E0

Parity error (0x10)

A3E1

Framing error (0x11)

A3E2

Overrun error (0x12)

A3E3

FCS error (0x13)

A3E4

Format error (0x14)

A3E5

Numeric data error (0x15)

A3E6

No command error (0x16)

A3E8

Frame size over (0x18)

A3E9

EPROM error (0x19)

A3F0

I/O table creation error (0x20)

A3F1

CPU error (0x21)

A3F2

No memory error (0x22)

A3F3

Memory protect error (0x23)

A3F4

Parity error occurred (0xa0)

A3F5

Frame error occurred (0xa1)

A3F6

Overrun error occurred (0xa2)

A3F7

FCS error occurred (0xa3)

A3F8

Format error occurred (0xa4)

A3F9

Numeric data error occurred (0xa5)

A3FA

Frame size over occurred (0xa8)

A3FE

Program area error (0xb0)

A3FF

Other end code

Error code
(hexadecimal)

Description

Processing after error occurrence

Retry

Processing after error occurrence

J120803E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.8 System Alarm Messages Specific to SYSMAC>

J12-29

Table Error Codes when a Communication Error Occurs SYSMAC (2/2)

Error code
(hexadecimal)

Description

A391

Communication driver busy

A392

Communication line busy

A393

Communication line not ready

A394

Sending size is too large

A395

Use of communication port not declared

A397

Under run error

A398

Timeout between received characters

A399

Receive buffer overflow

A39A

Parity error in receive data

A39B

Receiving overrun error

A39C

Receiving framing error

A39D

No. of characters received is outside specifications

A39F

Other error

Error code
(hexadecimal)

Processing after error occurrence

Retry

Description

Processing after error occurrence

J120805E.EPS

Other Errors SYSMAC

The following error occurs when a response to FCS command cannot be received from
SYSMAC within the specified period of time. If the following error occurs, communication
retry is performed for the number of times set in the New IOM dialog box called from System View. If there is still an error during retry, recovery communication is performed using
the recovery communication time intervals set in the New IOM dialog box called from
System View.
Table Other Errors SYSMAC
Error code
(hexadecimal)
A3B0

Description
No response

Processing after error occurrence

Retry
J120804E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J12-30

<J12.9 Transmission Time between Communication Module and SYSMAC>

J12.9 Transmission Time between Communication

Module and SYSMAC
The transmission time between communication module and SYSMAC subsystem is
to be discussed in this chapter.

Communication Time SYSMAC

The time required for communication between a communication module and SYSMAC is
obtained as the total of the time T1 to T5 below. However, when modems are connected, the
delay time by modem is added to T2 and T4.
Data acquisition begins

Data acquisition complete

Create message
to be sent

Communication
module

Interpret response
message, store data

SYSMAC

SYSMAC
processing time
T1

T2

T3

T4

T5
J120901E.EPS

T1:
T2:
T3:
T4:
T5:

Transmission message creation time approximately 10 ms

Send message transmission time
SYSMAC processing time. Required for processing on the SYSMAC side.
Response message transmission time
Response message interpretation time approximately 15 ms

Figure Time Chart of Communication between Communication Module and SYSMAC

Calculating the Communication Time SYSMAC

The send message transmission time (T2) and response message transmission time (T4,
T10) are figured using the formula given below.
Transmission time (ms) = No. of characters to be sent no. of bits per character 1000
Baud Rate (bps)
No. of bits
per character

start bit

data bit +

parity bit

stop bit
J120902E.EPS

Start bit:
Data bit:
Parity bit:
Stop bit:
Baud Rate:

1 bit fixed
7 bits fixed (8 bits not possible)
Even, odd
2 bits fixed
1200, 2400, 4800, 9600, 19200 (bps)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J12.9 Transmission Time between Communication Module and SYSMAC>

J12-31

Calculation Example for Communication Time SYSMAC

When the output data type is set via the Communication I/O Builder, the subsystem communication package reads data from the subsystem first. Then the package compares the
data read from the subsystem with the FCS data and only writes data to the subsystem
when discrepancies detected.
Because of this, it is difficult to calculate the time required for communication when writing
data to a subsystem since the transmission time varies according to the number of data in
which the value has changed. Therefore, use the following guidelines for communication
time when writing to the subsystem.
When the values for most of the data to be written are not changed Communication
time=The time required for transmission when reading data from the subsystem with
respect to all definitions where write has been designated
When the values for a large number of the data to be written are changed Communication time=About twice the amount of time required for transmission when reading
data from the subsystem with respect to all definitions where write has been designated
The following is an example of calculating the time required for communication between a
communication module and the SYSMAC.
In this example, eight 29 data and one 23 data are individually read from the data 0001 to
255 in the LR area. Calculation of the communication time is based on the following conditions:
Baud Rate:

19200 bps

Command response:

1 to n

Number of characters per data:

Number of bits per character:

11

SYSMAC processing time:

100 ms

Example of calculating transmission time required to read 29 data in a single

communication
Command character count=17
Time required for a single command transmission (T2) =17 11 1000/19200=10 (ms)
Response character count=Fixed length area+29 data 4=11+29 4 =127
Time required for a single response reception (T4) =127 11 1000/19200=73 (ms)
Communication time for one 29 data=10+10+100+73+15=208 (ms)
Example of calculating transmission time required to read 23 data in a single communication
Command character count=17
Time required for a single command transmission (T2) =17 11 1000/19200=10 (ms)
Response character count=Fixed length area+23 data 4=11+23 4=103
Time required for a single response receipt (T4) =103 11 1000/19200=59 (ms)
Communication time for one 23 data=10+10+100+59+15=194 (ms)
Example of calculating transmission time required to read 23 data in a single communication
208 8 (times) +194=1858 (ms)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

Blank Page

<J13. Siemens Communication>

J13-1

J13. Siemens Communication

The Siemens communication package is a subsystem communication package that
is compatible with the PLC SIMATIC S5 (hereinafter referred to as SIMATIC S5)
manufactured by Siemens, Co. With the Siemens communication package, communication between the FCS and SIMATIC S5 can be performed without a customized
program.
This chapter explains the communication between the SIMATIC S5 and FCS among
the subsystem communication packages.
SEE ALSO
Regarding the functions common to different subsystem communication packages, see the following:
J1, General Information Regarding to Subsystem Communication

Applicable Models SIMATIC S5

For the Siemens communication package, the following products are available:
PFS9055 CS 1000 Siemens communication package (ACM11, ACM12)
LFS9055 CS 3000 Siemens communication package (ACM11, ACM12)
The Siemens communication package performs subsystem communication between the
FCS and SIMATIC S5 by connecting the communication processor manufactured by
Siemens to the communication module (ACM11 or ACM12). The following communication
processors can be connected to ACM11 or ACM12.
CP524
CP525
The Siemens communication package only supports the SIMATIC S5 models that support
3964R transmission protocol.

IMPORTANT
For communication with the ACM12, it is necessary to wait for 1 ms or more after the end of
transmission from the ACM12 until a response is sent from the communication processor.

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J13.1 Communication Specifications SIMATIC S5>

J13-2

J13.1 Communication Specifications SIMATIC S5

The section below explains the specifications when performing subsystem communication with the SIMATIC S5.

Communication Capacity SIMATIC S5

The capacity specific to SIMATIC S5 when performing subsystem communication with the
SIMATIC S5 are indicated below:
Table Capacity of Communication Between FCS and SIMATIC S5
Item

Maximum quantity

Explanation

Amount of data that can be communicated with

one communication module

500 words
(1 word=16 bits)

Maximum amount that can be

accessed from the regulatory control
block/sequence control block.

Number of subsystem stations that can be

communicated with one communication module

30 stations

Data size in one communication frame

Word Device: 64 words One frame is defined in one line on

Bit Device: 8 words the builder. It is the same as
(128 bits) restricted by SIMATIC S5 protocol.
J130101E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.1 Communication Specifications SIMATIC S5>

J13-3

Transmission Specifications SIMATIC S5

The transmission specifications when performing subsystem communication with the
SIMATIC S5 are indicated below:
Table Transmission Specifications SIMATIC S5 (1/2)
Item
Interface

Description
RS-232C

ACM11

RS-422

ACM12

Transmission method

Half duplex

Synchronization method

Start-stop synchronization
method

Baud rate (bps)

1200, 2400, 4800, [9600], 19200

Transmission procedure

3964R

Transmission code

Binary

Data type

Control line

Time monitoring

Text frame

Remark

(*1)

Start bit

Data bit

Must specify 8 via the New IOM dialog box

called from the System View

Parity bit

None, [even], odd

(*1)

Stop bit

Must specify 1 via the New IOM dialog box

called from the System View

RS

Always ON

DR

Transmit when ON

CD

Always ON

ER

Always ON

CS

Transmit when ON

Transmission enable
monitoring time

1000ms

Reception character
interval monitoring time

10ms

Character interval
timeout processing

Terminate the packet

Reception start character None

EOT character
Item

None
Description

Remark
J130102E.EPS

Note: [ ] indicates the recommended settings.

*1:
This can be changed using the property sheet called from System View.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J13-4

<J13.1 Communication Specifications SIMATIC S5>

Table Transmission Specifications SIMATIC S5 (2/2)
Item

Description

Remark

XON/XOFF control

None

Timer 1

1 to 99 sec [2 sec]

(*1)

Timer 2

1 to 99 sec [2 sec]

(*1)

Timer 3

1 to 99 sec [2 sec]

(*1)

Timer 4

1 to 99 sec [2 sec]

(*1)

Timer 5

1 to 99 sec [15 sec]

(*1)

Timer 6

1 to 99 sec [2 sec]

(*1)

Timer 7

1 to 99 sec [2 sec]

(*1)

Number of retries for communication error

0 to 99 times [5 times]

(*1)

No response detection time

0 to 99 seconds [4 seconds]

(*1) Equivalent to timer 3

Number of retries for communication error

0 to 99 times [1 time]

(*1)

Recovery communication time interval

0 to 999 seconds [ 30 seconds] (*1)

Number of words that may be handled in

one transmission

64 words (AI/AO)
8 words (DI/DO)
J130103E.EPS

Note: [ ] indicates the recommended settings.

*1:
This can be changed using the property sheet called from the System View.

IMPORTANT
When performing subsystem communication with the SIMATIC S5, be sure to specify [8
bits] for the data bit length on the System View. A communication error will occur if [7 bits] is
specified.

Timers 1 to 7 monitor the timeout as described below:

Timer 1:
Monitor the reception timeout between the STX transmission and DLE reception.
Timer 2:
Monitor the reception timeout between the command transmission and DLE reception.
Timer 3:
Monitor the reception timeout for the reception start STX reception. Timer 3 is equivalent to Siemens no response time.

Communication
processor

D
L
E

D
L
E

D
L
E
S
T
X

Timer 4

Transmission
text

Timer 3

S
T
X

Timer 2

Communication
module

Timer 1

Timer 4:
Monitor the reception timeout between the DLE transmission and the response text
reception.

D
L
E
Transmission
text

S
T
X
D
L
E
J130104E.EPS

Figure Explanation of Timers 1 through 4

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J13-5

<J13.1 Communication Specifications SIMATIC S5>

Timer 5:
If STX is received between the STX transmission and the DLE reception, wait for the
time of Timer 5, and start communication over from the beginning. If there is an error
in the response text, wait for the time of Timer 5, and then start communication over
from the beginning.
Timer 5
Communication
module
Communication
processor

S
T
X

S
T
X
S
T
X
Timer 5

Communication
module
Communication
processor

S
T
X

D
L
E

Transmission
text
D
L
E

D
L
E

S
T
X

D
L
E

S
T
X

Error
response
J130105E.EPS

Figure Explanation of Timer 5

Timer 6:
If NAK is received between the STX transmission and the DLE reception, wait for the
time of Timer 6 and start communication over from the beginning.
Timer 6
Communication
module
Communication
processor

S
T
X

S
T
X
N
A
K
J130106E.EPS

Figure Explanation of Timer 6

Timer 7:
If NAK is received between the command transmission and the DLE reception, wait
for the time of Timer 7 and start communication over from the beginning.
Timer 7
Communication
module
Communication
processor

S
T
X

S
T
X

Transmission
text
D
L
E

N
A
K
J130107E.EPS

Figure Explanation of Timer 7

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.2 Connecting FCS and SIMATIC S5>

J13-6

J13.2 Connecting FCS and SIMATIC S5

This section explains the connection type and cable connections between FCS and
SIMATIC S5.

Connection Type SIMATIC S5

An example of connection between FCS and SIMATIC S5 is shown below:
HIS

Control bus

FCS

ACM11 (RS-232C communication module)

RDY
RCV
SND

CN1

RDY
RCV
SND

AMN33 (communication module nest)

CN1

RS-232C
MODEM

MODEM
RS-232C
CP524/CP525

SIMATIC S5

J130201E.EPS

Figure Example of Connection between FCS and SIMATIC S5

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.2 Connecting FCS and SIMATIC S5>

J13-7

Cable Connection when Using the ACM11 SIMATIC S5

The following describes the cable connection when connecting the ACM11 and SIMATIC
S5:
The ACM11 and communication processor must be connected via a modem. However,
they can be connected directly if the length of the RS-232C cable between the ACM11 and
communication processor is 15 meters or less and the grounding systems of the ACM11
and the communication processor are the same.

IMPORTANT
The length of the RS-232C cable between the ACM11 and modem as well as the length
between the modem and communication processor must be 15 meters or less, respectively.

The communication processor uses an RS-232C D-sub 25 pin connector. Thus, a cable
with an RS-232C D-sub 25 pin connector is used when connecting the ACM11 and the
communication processor.
Table RS-232C D-sub 25 Pin Connector Specifications SIMATIC S5
Title

Direction of signal

Pin number

Signal name

FG

Frame ground

SD

Send data

RD

Receive data

RS

Request to Send

When there is a send request, ON is output

(except SIMATIC S5)

CS

Clear to Send

When OFF, ACM11 does not transmit to the

outside. (except SIMATIC S5)

DR

Data Ready

Detects whether sending and receiving with

correspondent are allowed.

SG

Signal ground

CD

Carrier Detected

20

ER

Data Terminal Ready

ACM11

Description

SIMATIC
Security ground

When sending and receiving are allowed, ON is

output. (except SIMATIC S5)
J130202E.EPS

SEE ALSO
For details on safety grounding, see the following:
Figure Cable Connection between Communication Processor and ACM11 (when Connected directly)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.2 Connecting FCS and SIMATIC S5>

J13-8

Pin No.13

Pin No.25

Pin No.14

Pin No.1
J130203E.EPS

Figure Pin Assignment of the RS-232C D-sub 25 Pin Connector SIMATIC S5

The following shows the cable connection when the communication processor and ACM11
are connected directly:
SD
RD
RS
CS
ACM11 DR
CD
ER
SG
FG

20

20

SD
RD
RS
CS
CD
DR

Communication
processor

ER
SG
FG

Protective grounding
(100 ohms or less)
J130204E.EPS

Figure Cable Connection between Communication Processor and ACM11 (when Connected
directly)

With the ACM11, the RS-232C circuit and FG (frame ground) are electrically insulated. This
has the function of preventing intrusion of noise from the SIMATIC S5 side and improving
noise resistance. Satisfy all conditions given below to make this function effective:
For the frame ground, perform protective grounding (100 ohms or less) at the opposing side of the connection (the modem or the communication processor side).
Attach only one side of the shield of the sheathed cable to the FG of the opposing side
of the connection. Do not ground the cable shield on the ACM11 side. Also, do not use
a connector shell that is conductive.
Connect the FG and the SG (signal ground) of RS-232C circuit at the opposing side of
the connection. When the FG and SG are not connected at the opposing side of the
connection, use an RS-232C cable manufactured by Yokogawa Electric: AKB141
(RS-232C modem cable) or AKB142 (RS-232C null-modem cable). Both AKB141 and
AKB142 have SG and FG connected inside the connector shell. The cable shield can
also be connected to the FG at the opposing side of the connection.
SEE ALSO
For details on cable connections, see the following:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.2 Connecting FCS and SIMATIC S5>

J13-9

Cable Connection Using the ACM12 SIMATIC S5

The following shows the cable connection when connecting the ACM12 and communication processor.
ACM12

Communication
processor

ACM12

Communication
processor

TX +

SDA

TX +

SDA

TX -

SDB

TX -

SDB

RX +

RDA

RX +

RDA

RX -

RDB

RX -

RDB

SG

SG

SG

SG

FG

FG

FG

FG

(4-wire connection)

(2-wire connection)
J130205E.EPS

Figure 1 to 1 Connection via RS-422 Communication Processor

IMPORTANT
The 1 to n connection is not supported in subsystem communication between the ACM12
and communication processor.

With the ACM12, the FG (frame ground) and the SG (signal ground) for the RS-422 are
separated. Treat the shield for the RS-422 as follows:
Perform protective grounding (100 ohms or less) for the FG at the opposing side of the
connection (communication processor side).
Connect the shield for the cable between ACM12 and communication processor to the
FG of the communication processor side. Do not connect it to the FG of the ACM12
side.
SEE ALSO
For details on cable connections, see the following:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)

When connecting the ACM12 and communication processor, it is necessary to perform

settings on the ACM12 and communication processor sides.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.2 Connecting FCS and SIMATIC S5>

J13-10

Setting a Terminating Register on the ACM12 Side SIMATIC S5

When connecting the ACM12 and a communication processor, a terminal resistor (120
ohms 1/2 W) is required between the RX+ terminal and RX- terminal on the ACM12 side.
The ACM12 is shipped with the terminal resistor installed between the RX+ terminal and
RX- terminal.
Set the connection method (4-wire or 2-wire ) using the 2-pole DIP switch (SW1) attached
to the ACM12. The unit is shipped from the factory with a 4-wire connection setting. The
SW1 setting for the ACM12 is indicated in the table below:
Table SW1 Setting for the ACM12 SIMATIC S5
Connection method

SW1 setting for ACM12

2-wire

ON

ON

4-wire

OFF

OFF
J130206E.EPS

Setting a Terminating Register on the Communication Processor Side

On the communication processor side, the setting of the terminal resistor differs depending
on the type.
SEE ALSO
For details on the settings on the communication processor side, refer to the users manual for the
communication processor being used.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.3 Accessible Devices SIMATIC S5>

J13-11

J13.3 Accessible Devices SIMATIC S5

SIMATIC S5 internal data are called devices.
There are bit devices and word devices.
Bit device
This refers to data where each bit has a meaning. The discrete input is equivalent to a bit device.
Word device
This refers to data where a word unit (1 word = 16 bits) contains the meaning.
The analog data input is equivalent to a word device.
The SIMATIC S5 also has a device called status.

Accessible Devices SIMATIC S5

Table Accessible Devices SIMATIC S5
Device name
Bit device

Word device

Other

Address (*1)

Read

Discrete input

DRnnnmmm

Discrete output

DWnnnmmm

Analog input

ARnnnmmm

Analog output

AWnnnmmm

Timer

TRnnnmmm

Status

STS

Write

Size setting range

1 to 8

1 to 8
1 to 64

1 to 64
1 to 64

2
J130301E.EPS

:
Can be accessed
Blank: Cannot be accessed
Note: The SIMATIC S5 command type is D (Data Block).
*1:
nnn is the data block number. A 3-digit number within the range of 003 to 255 can be set.
mmm is the data word number. A 3-digit number within the range of 000 to 255 can be set.
The nnnmmm portion varies depending on the type of SIMATIC S5 being used.

SEE ALSO
For details on the address, refer to the users manual for the SIMATIC S5 being used.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.4 Subsystem Data Storing Format SIMATIC S5>

J13-12

J13.4 Subsystem Data Storing Format SIMATIC S5

The following explains the format in which subsystem data acquired from the
SIMATIC S5 is stored in the FCS.
The storing formats for SIMATIC S5 bit devices, word devices and statuses are given
below.

Bit Device SIMATIC S5

When 16 m number (m = 1, 2, ...) of bit devices are read starting from address n, the
SIMATIC S5 data is stored in the FCS as indicated below. The data size is specified as m
via the Communication I/O Builder.

16 bits
n n n n n n
+ + + + + +
15 14 13 12 11 10

n
+
9

n
+
8

n
+
7

n
+
6

n
+
5

n
+
4

n
+
31

n
+
3

n
+
2

n
+
1

m=1

n
+
16

m=2

n+16 (m-1)+15

n+16 (m-1)
J130401E.EPS

Figure Image of Stored Bit Device SIMATIC S5

Conversion processing between the SIMATIC S5 data format and the communication
module data format is not performed for bit devices such as discrete input and discrete
output.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.4 Subsystem Data Storing Format SIMATIC S5>

J13-13

Word Device SIMATIC S5

When m number of word devices are read starting from address n, the SIMATIC S5 data is
stored in the FCS as indicated below:
16 bits

Contents of the nth register

Contents of the n+1th register

Contents of the n+m-1th register

J130402E.EPS

Figure Image of Stored Word Device SIMATIC S5

Conversion processing between the SIMATIC S5 data format and the communication
module data format is not performed for word devices such as analog input and analog
output.
As for word devices such as timers, the communication module data format is converted
into binary data according to the scaling factor represented by the 12th and 13th bits of the
SIMATIC S5 data format.
15

12

BCD
Scaling factor
0: 0.01 s
1: 0.1 s
2: 1 s
3: 10 s
SIMATIC S5 data format

15

Convert into binary in consideration

of the scaling factor.
The fractions are rounded off.

FCS internal data format

J130403E.EPS

Figure Binary Conversion of Communication Module Data Format SIMATIC S5

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.4 Subsystem Data Storing Format SIMATIC S5>

J13-14

Status SIMATIC S5
The status of SIMATIC S5 is stored in the FCS as indicated below:
MSB

LSB

First word

No response
BCC error
NAK reception
Transmission character error
Header error
Text length error
MSB

LSB
Second word PLC-system failure code
-> ERRNO value (1 byte)

J130404E.EPS

Figure Image of Stored Status SIMATIC S5

When an error occurs, 1 is stored in each bit that corresponds to the error.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.5 Setting Items on System View SIMATIC S5>

J13-15

J13.5 Setting Items on System View SIMATIC S5

S3964R

In this section, setting items on System View for SIMATIC S5, the specific functionality and the recommended settings are explained.
SEE ALSO
For more information regarding to Set Details tab on Create New IOM dialog box and subsystem
common settings, see the following:
Setting Items for ACM11, ACM12 in J1.5.1, Overview of Setting Items on System View

For SIMATIC S5, the setting items are as follows. This setting is done on the Set
Details tab of the New IOM dialog box called from System View.
Connection Device
Baud Rate
Parity
Data Bits
Stop Bits
RS Control
DR Check
CD Check
Communication Error Process
Options
After creating the new I/O module, the settings can be modified on the I/O module
property sheet.

Connection Device SIMATIC S5

Set [S3964R] as the type of connection device (subsystem).
Must perform this setting since the default is [FA-M3].

Baud Rate SIMATIC S5

This sets the baud rate between the communication module and SIMATIC S5.
The recommended the baud rate is [9600].
The default is [19200 bps].

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.5 Setting Items on System View SIMATIC S5>

J13-16

Parity SIMATIC S5
This sets the method for checking the parity of the subsystem data to be transmitted.
The recommended setting for the parity is [Even].

Data Bits SIMATIC S5

This sets the data bit length of the subsystem data to be transmitted.
When using the SIMATIC S5, always select [8 bits] for the bit length.

IMPORTANT
For the SIMATIC S5, a communication error will occur if [7 bits] is selected.

Stop Bits SIMATIC S5

This sets the stop bit of the subsystem data to be transmitted.
When using the SIMATIC S5, always select [1 bit] for the stop bit.

IMPORTANT
For the SIMATIC S5, [2 bits] cannot be used for the stop bit.

RS Control SIMATIC S5
This sets whether or not RS control is performed during subsystem data transmission.
When using the SIMATIC S5, disable RS control by leaving the [RS control] check box unchecked.

DR Check SIMATIC S5
This sets whether or not DR check is performed during subsystem data transmission.
When using the SIMATIC S5, enable the DR check by checking [DR check] check box.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.5 Setting Items on System View SIMATIC S5>

J13-17

CD Check SIMATIC S5
This sets whether or not CD check is performed during subsystem data transmission.
When using the SIMATIC S5, disable the CD check by leaving the [CD check] check box
unchecked.

Communication Error Process SIMATIC S5

This sets the parameters related to communication error handling during subsystem data
transmission.
The following three items must be set.
Response Timeout
This sets the time limit for getting response from SIMATIC S5. The time is set in unit of
seconds.
Set a time to Timer 3 as Response Timeout setting.
Recommended setting is [2] seconds.
Default setting is 4.
Number of Retries Upon Response Timeout
This item sets the number of retries performed when a communication error occurs.
Recommended setting is [5].
Default setting is 1.
Interval of Connection Retries
This sets the time interval of connection requests for checking whether the communication with the station that generated a communication error has returned to normal
(communication recovery) . The time is set in unit of seconds.
Default setting is 30.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.5 Setting Items on System View SIMATIC S5>

J13-18

Options SIMATIC S5
Settings of communication parameter options vary depending on the equipment connected. Set options by clicking the [Option] button 1 to 4 in the Set Details tab of the New
IOM dialog box called from the System View.
For the SIMATIC S5, set the time for each timer and the availability of readback using
options 1 through option 3. Set 0 for option 4 in normal conditions.

Option 1
Set the time for timers 1, 2 and 4.
aabbcc
aa:
bb:
cc:

Timer 1
Timer 2
Timer 4

For example, if 010203 is set in option 1, 1 second is set for timer 1, 2 seconds for timer 2
and 3 seconds for timer 4.

Option 2
Set the time for timers 5, 6 and 7.
ddeeff
dd:
ee:
ff:

Timer 5
Timer 6
Timer 7

For example, if 100203 is set in option 2, 10 seconds is set for timer 5, 2 seconds for timer
6 and 3 seconds for timer 7.

Option 3
Set whether to use readback or not. Set 0 when no readback is used and 1 when using
readback.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.6 Setting Items on Communication I/O Builder SIMATIC S5>

J13.6

J13-19

Setting Items on Communication I/O Builder

SIMATIC S5
In this section, setting items on Communication I/O Builder for SIMATIC S5, the
specific functionality and the recommended settings are explained.
SEE ALSO
For an overview of the setting items on Communication I/O Builder, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

For SIMATIC S5, the setting items are as follows.

Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

Element SIMATIC S5
Element

With respect to the address of the subsystem data buffer, the element numbers are displayed on Communication I/O Builder. The element number is not set, only displayed.

Buffer SIMATIC S5
Buffer

This sets the buffer for the communicated data.

Must set the buffer since this is a required setting item of the Communication I/O Builder.

Program Name SIMATIC S5 : PFCS/SFCS

Program Name

Set the unit number, slot number and S3964R as program name in the following format:
u-sProgramName
u:
s:
ProgramName:

Unit number
Slot number
S3964R
IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.6 Setting Items on Communication I/O Builder SIMATIC S5>

J13-20

Program Name SIMATIC S5 : LFCS2/LFCS

Program Name

Set the node number, unit number, slot number and S3964R as Program Name in the
following format:
n-u-sProgramName
n:
u:
s:
ProgramName:

Node number
Unit number
Slot number
S3964R

Size SIMATIC S5
Size

This item sets the data size (data length) from the head address set in Device & Address.
Must set the Size since this is a required setting item on Communication I/O Builder.
For SIMATIC S5, the setting ranges are limited as follows, the unit is in Word.
Discrete input:

1 to 8

Discrete output:

1 to 8

Analog input:

1 to 64

Analog output:

1 to 64

Timer:

1 to 64

Status:

Always set 2

SEE ALSO
For more information about Size setting item, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

Port SIMATIC S5
Port

Port 1 is set for use.

IP Address SIMATIC S5
IP Address

No need to set IP address.

Station SIMATIC S5
Station

This sets the station number of the SIMATIC S5.

The station numbers are set using a value between 1 and 255.
Set different station numbers for the address STS and other addresses. If the same station
number is set, the error code cannot be identified when the alarm is referenced after a
communication error has occurred.
IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.6 Setting Items on Communication I/O Builder SIMATIC S5>

J13-21

Device & Address SIMATIC S5

Device & Address

This sets the head address of SIMATIC S5 data.

The addresses that can be set using 3 to 8 alphanumeric characters as shown below:
Discrete input:

DRnnnmmm

Discrete output:

DWnnnmmm

Analog input:

ARnnnmmm

Analog output:

AWnnnmmm

Timer:

TRnnnmmm

Status:

STS

The nnnmmm portion varies depending on the SIMATIC S5 type being connected.
nnn is the data word number, and set using a three digit value between 003 and 225.
mmm is the data block number, and set using a three digit value between 000 and 225.
SEE ALSO
For more information about address setting, see the users manual of SIMATIC S5.

Data Type SIMATIC S5

Data Type

This sets data type of the subsystem data.

The data type can be selected from the following:
Input (16-Bit Signed)
Input (32-Bit Signed)
Input (16-Bit Unsigned)
Input (32-Bit Unsigned)
Input (32-Bit Floating)
Output (16-Bit Signed)
Output (32-Bit Signed)
Output (16-Bit Unsigned)
Output (32-Bit Unsigned)
Output (32-Bit Floating)
Input (Discrete)
Output (Discrete)
TIP
Simultaneity of communication data in 32 bit units is not guaranteed in the SIMATIC S5.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.6 Setting Items on Communication I/O Builder SIMATIC S5>

J13-22

Reverse SIMATIC S5
Reverse

This sets whether or not to make the bit or word arrangement in FCS in reverse order of the
subsystem data. This setting can be set on Communication I/O builders.
The following settings can be selected:
Bits
No
Words
However, when choosing [Bits], only the data of discrete inputs or discrete outputs can be
reversed. In this case, the default setting is [Bits].
Regarding to words, only the 32-bit analog inputs or the 32-bit analog outputs can be
reversed. In this case the default setting is [No].

Scan SIMATIC S5
Scan

Set whether to read the communication I/O analog data into the communication I/O data
buffer at the beginning of high-speed scan of the FCS.

Service Comment SIMATIC S5

Service Comment

A comment text can be set.

Label SIMATIC S5
Label

The name of the function block I/O terminal can be set as a user-defined label.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J13-23

<J13.7 Communication Packet SIMATIC S5>

J13.7 Communication Packet SIMATIC S5

This section explains the configuration of the communication packet for communication with the SIMATIC S5.

Command Telegram Communication Packet SIMATIC S5

The following describes the format of command telegram communication packet:
telegram command
identifier CMD TYP

$00 $00

A
or
E

dest./source number CPU no

adrs
/CF
high low
DB no DW no

XX

XX

XX

Data area

XX $FF $FF

command TYP:
dest./source adrs DB no:
dest./source adrs DW no:
number:
Data area:

E
T
X

B
C
C

$10 $03 XX

Header area
command CMD:

D
L
E

Data area

SEND command if A (write)

FETCH command if E (read)
D indicating a data block
$03 to $FF (3 to 255)
$00 to $FF (0 to 255)
Number of data
$0001 to $0040 (1 to 64 words)
Use only when SEND command
J130701E.EPS

Figure Command Telegram Communication Packet SIMATIC S5

Reply Telegram Communication Packet SIMATIC S5

The figure below shows the format of reply telegram communication packet:
telegram con- error
identifier tains number
Data area
$00 $00 $00
Header area
Data area:

D
L
E

E
T
X

B
C
C

$10 $03 XX

XX
Data area

Use only when FETCH command

J130702E.EPS

Figure Reply Telegram Communication Packet SIMATIC S5

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.8 System Alarm Messages Specific to SIMATIC S5>

J13-24

J13.8 System Alarm Messages Specific to

SIMATIC S5
This section explains the system alarm messages that are specific to SIMATIC S5.

System Alarm Message Sent when a Communication Error Occurs

SIMATIC S5 : PFCS/SFCS
When there is a communication error, the system alarm message as shown below is sent
to HIS:
STNss SS-COM Error UNITmm SLOTnn STNzzz CODE=####
STNss:
mm:
nn:
zzz:
####:

FCS name
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. After that, a new system alarm message
will not be sent even if an error is generated by a different cause.
SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs SIMATIC S5

System Alarm Message when a Communication Error Occurs

SIMATIC S5 : LFCS2/LFCS
When a communication error occurs, the system alarm message as shown below is sent to
HIS:
STNss SS-COM Error RIO01 NODExx UNITmm SLOTnn STNzzz CODE=####
STNss:
xx:
mm:
nn:
zzz:
####:

FCS name
Node number
Unit number
Slot number
Subsystem station number
Error code

When a communication error occurs in the subsystem, the system alarm message is
transmitted only once at the time the error occurs. The new system alarm message will not
be transmitted even if errors are generated by different causes.
SEE ALSO
For the error codes, see the following in this chapter:
Error Codes when a Communication Error Occurs SIMATIC S5

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.8 System Alarm Messages Specific to SIMATIC S5>

J13-25

System Alarm Message Sent when Communication Returns to Normal

SIMATIC S5 : PFCS/SFCS
When communication returns to the normal condition, the system alarm message indicated
below is sent to HIS:
STNss SS-COM Recover UNITmm SLOTnn STNzzz
STNss:
mm:
nn:
zzz:

FCS name
Unit number
Slot number
Subsystem station number

System Alarm Message when Communication Returns to Normal

SIMATIC S5 : LFCS2/LFCS
When communication returns to normal status, the system alarm message indicated below
is sent to HIS:
STNss SS-COM Recover RIO01 NODExx UNITmm SLOTnn STNzzz
STNss:
xx:
mm:
nn:
zzz:

FCS name
Node number
Unit number
Slot number
Subsystem station number

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.8 System Alarm Messages Specific to SIMATIC S5>

J13-26

Error Codes when a Communication Error Occurs SIMATIC S5

The following are the error codes for communication errors:
Definition error
Response message error
Abnormal communication error
Other error
SEE ALSO
For details on errors, refer to the users manual for the SIMATIC S5 being connected.

Definition Error SIMATIC S5

The following errors will occur if the content set via the Communication I/O Builder is
inappropriate. Check the setting made via the Communication I/O Builder when the following errors occur. Communication will not be performed if the values for timers 1, 2, 4, 5, 6
and 7 are incorrect.
Table Definition Errors SIMATIC S5
Error code
(hexadecimal)

Description

A3B1

Station not applicable

A3B2

There is no such command type

A3B3

Data block conversion error

A3B4

Data block No. (3 to 255) outside the range

A3B5

Data word No. conversion error

A3B6

Data word No. (0 to 255) outside the range

A3B7

Number of data outside the range

A3B8

Inappropriate type

A3B9

STS command double-defined

A3BA

Timer 1 setpoint value outside the range

A3BB

Timer 2 setpoint value outside the range

A3B

Timer 3 setpoint value outside the range

A3BC

Timer 4 setpoint value outside the range

A3BD

Timer 5 setpoint value outside the range

A3BE

Timer 6 setpoint value outside the range

A3BF

Timer 7 setpoint value outside the range

Processing after
error occurrence

Communication is not
performed.

All communication definition

invalid

J130801E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.8 System Alarm Messages Specific to SIMATIC S5>

J13-27

Response Message Error SIMATIC S5

The following errors will occur is there is an error relating to the communication response
from the SIMATIC S5. When the following errors occur, communication will be retried for
the number of times set in the New IOM dialog box called from the System View.
Table Response Message Error SIMATIC S5
Error code
(hexadecimal)

Processing after
error occurrence

Description

A3C0

BCC error

Retry (NAK)

A3C1

NAK reception (STX transmission DLE wait)

Retry (STX)

A3C2

NAK reception (text transmission DLE wait)

Retry (STX)

A3C3

NAK reception (receive start STX wait)

Next command

A3C4

NAK reception (DLE transmission text wait)

Retry (NAK)

A3C5

Transmission character error (STX transmission DLE wait)

Retry (STX)

A3C6

Transmission character error (text transmission DLE wait)

Retry (STX)

A3C7

Transmission character error (receive start STX wait)

Next command

A3C8

Transmission character error (DLE transmission text wait)

Retry (NAK)

A3C9

Response message error (Header error)

Retry (NAK)

A3CA

Text length error (STX transmission DLE wait)

Retry (STX)

A3CB

Text length error (text transmission DLE wait)

Retry (STX)

A3CC

Text length error (receive start DLE wait)

Next command

A3CD

Text length error (DLE transmission text wait)

Retry (NAK)
J130802E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.8 System Alarm Messages Specific to SIMATIC S5>

J13-28

Communication Error SIMATIC S5

The table below lists the errors that will occur due to I/O module errors on the SIMATIC S5
side. When the following errors occur, communication will be retried for the number of
times set in the New IOM dialog box called from System View.
Table Error Codes when a Communication Error Occurs SIMATIC S5
Error code
(hexadecimal)

Description

A391

Communication driver busy

A392

Communication line busy

A393

Communication line not ready

A394

Sending size is too large

A395

Use of communication port not declared

A397

Under run error

A398

Timeout between received characters

A399

Receive buffer overflow

A39A

Parity error in receive data

A39B

Receiving overrun error

A39C

Receiving framing error

A39D

No. of characters received is outside specifications

A39F

Other error

A3F0

PLC error response

Processing after
error occurrence

Next command
J130803E.EPS

Other Errors SIMATIC S5

The following errors occur when a response to FCS command cannot be received from
SIMATIC S5 within the specified period of time. If the following errors occur, perform communication retry for the number of times set on System View as in the case of response
message error.
Table Other Error SIMATIC S5
Error code
(hexadecimal)

Description

Processing after
error occurrence

A3D0

No response (STX transmission DLE wait)

Retry (STX)

A3D1

No response (text transmission DLE receive)

Retry (STX)

A3D2

No response (receive start STX wait)

Next command

A3D3

No response (DLE transmission text wait)

Retry (NAK)
J130804E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J13-29

<J13.9 Transmission Time between Communication Module and SIMATIC S5>

J13.9 Transmission Time between Communication

Module and SIMATIC S5
The transmission time between communication module and SIMATIC S5 subsystem
is to be discussed in this chapter.

Communication Time SIMATIC S5

The time required for communication between a communication I/O module and SIMATIC
S5 is figured as the total of the time T1 to T10. However, when a modem is connected, the
delay time by modem is added to T1, T2, T4, T6, T7 and T9.
Data acquisition
complete

Data acquisition begins

STX transmission

DLE transmission
STX
transmission

Creation of
send text

Communication
module

DLE transmission

Interpret
response
message,
store data

Creation of
send text
SIEMENS
SIMATIC S5
processing time

DLE transmission

T1

T2

T3

T4

T5

T6

T7

T8

T9

T10
J130901E.EPS

Figure Time Chart of Communication between Communication Module and SIMATIC S5

Note:
T1 to T10 are described below. The following times are figured assuming that the baud rate is 9600
bps and the number of bits per character is 11.
T1: STX transmission time. 131131000/9600=1.15 ms
T2: DLE transmission time. 131131000/9600=1.15 ms
T3: ACM transmission text creation time 10 ms
T4: Send packet transmission time
T5: SIMATIC S5 processing time
T6: STX transmission time. 131131000/9600=1.15 ms
T7: DLE transmission time. 131131000/9600=1.15 ms
T8: SIMATIC S5 response text creation time
T9: Response packet transmission time
T10: Response packet interpretation time/data storing time 1.15 ms+15 ms=16.15 ms

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J13.9 Transmission Time between Communication Module and SIMATIC S5>

J13-30

Calculating the Communication Time SIMATIC S5

The send packet transmission time (T3) and response packet transmission time (T9) are
figured using the formula given below:

Transmission time (ms) =

No. of characters
no. of bits

1000
to be sent
per character
Baud rate (bps)
J130902E.EPS

Calculation Example for Communication Time SIMATIC S5

When the output data type is set via the Communication I/O Builder, the subsystem communication package reads data from the subsystem before it writes for that definition. Then
the package compares the data read from the subsystem with the FCS data and only
writes data of differing value to the subsystem.
Because of this, it is difficult to calculate the time required for communication when writing
data to a subsystem since the transmission time varies according to the number of data in
which the value has changed. Therefore, use the following guidelines for communication
time when writing to the subsystem.
When the values for most of the data to be written are not changed
Communication time = The time required for transmission when reading data from the
subsystem with respect to all definitions where write has been designated
When the values for a large number of the data to be written are changed
Communication time = About twice the amount of time required for transmission when
reading data from the subsystem with respect to all definitions where write has been
designated
The following is an example of calculating the time required for communication between an
I/O module and the SIMATIC S5. In this example, 64 words of analog data are read during
a single communication from the SIMATIC S5. The communication time is calculated
based on the following conditions. The actual SIMATIC S5 processing time fluctuates by
the load on the SIMATIC S5 side.
Baud rate:

9600 bps

Number of bits per character:

11

SIMATIC S5 processing time:

10 ms

Send text transmission time (T4) = 13 111000/9600=14.90 (ms)

SIMATIC S5 processing time (T5) = 10 (ms)
SIMATIC S5 response text creation time (T8) = 10 (ms)
Response text transmission time (T9) = 135 111000/9600=154.69 (ms)
10

Total time = Ti

i=1

= 1.15+1.15+10+14.90+10+1.15+1.15+10+154.69+16.15=220.34 (ms)
J130903E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14. DARWIN/DAQSTATION Communication (ACM71)>

J14-1

J14. DARWIN/DAQSTATION Communication

(ACM71)
The DARWIN/DAQSTATION communication package (ACM71) is a subsystem communication package compatible with the DARWIN series data acquisition unit
DA 100, data collector DC100, hybrid recorders DR231, DR232, DR241, and DR242
(hereinafter referred to as DARWIN) as well as DAQSTATION DX series (hereinafter
referred to as DAQSTATION) manufactured by Yokogawa. The DARWIN/
DAQSTATION communication package (ACM71) allows communication between
FCS and DARWIN/DAQSTATION via Ethernet.
This communication package can be used on enhanced PFCS and SFCS only.
This chapter explains the communication between DARWIN/DAQSTATION and FCS
among the subsystem communication packages.
SEE ALSO
For functions common to different subsystem communication packages, see the following:
J1, General Information Regarding to Subsystem Communication

Applicable Models DARWIN/DAQSTATION

The following DARWIN/DAQSTATION communication package products are available:
PFS2232 CS 1000 DARWIN/DAQSTATION communication package (ACM71)
LFS2232 CS 3000 DARWIN/DAQSTATION communication package (ACM71)
When using the DARWIN/DAQSTATION communication package (ACM71), an ACM71
(Ethernet communication module) must be installed in an FCS in order to perform communication with a DARWIN Ethernet interface unit or DAQSTATION.
The following DARWIN/DAQSTATION can be connected to ACM71:
Data acquisition unit DA100 (standalone model, expandable model)
Ethernet module (DT300-41)
Data collector DC100 (standalone model, expandable model)
Ethernet module (DT300-41)
Hybrid recorders DR231, DR232, DR241, and DR242 (standalone model, expandable
model)
Ethernet module (DT300-41)
DAQSTATION DX series DX100/DX200

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J14. DARWIN/DAQSTATION Communication (ACM71)>

J14-2

Operating Environment DARWIN/DAQSTATION

To run the DARWIN/DAQSTATION package (ACM71), 350 Kbyte needs to be assigned to
the User C option area of the FCS used.

IMPORTANT
On Detailed Settings tab of FCS Constants Builder, the setting item SEBOL/User C Ratio
needs to be properly set in accordance with the communication program size.
If the default ratio 100 % is used, all resource is assigned for SEBOL and the communication program may fail when SEBOL program is running.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.1 Communication Specifications DARWIN/DAQSTATION>

J14-3

J14.1 Communication Specifications DARWIN/

DAQSTATION
The section below explains the specifications that should be used when performing
subsystem communication with the DARWIN/DAQSTATION.

Ethernet Communication Specifications

The Ethernet communication specifications include the following:
Communication protocol: TCP/IP

Transmission Specifications DARWIN/DAQSTATION

The transmission specifications when performing subsystem communication with the
DARWIN/DAQSTATION are indicated below:
Table Transmission Specifications DARWIN

Item

Description

Transmission Code

Binary

Data Exchange

Read Measured data, calculated data and alarm status

DARWIN:

Connectible Stations

Unit 0 of Stand-Alone Type

Unit 0 to 5 of Enhanced Type
DAQSTATION: Stations Connected to ACM71
J140101E.EPS

Communication Capacity DARWIN/DAQSTATION

The communication capacity is as follows:
Number of DARWIN/DAQSTATION that can communicate with one FCS:
5 modules (*1)
*1: It is possible to use DARWIN and DAQSTATION together.

Data that can be measured (DARWIN): Up to 300 channels per module

Data that can be measured (DAQSTATION): Up to 30 channels per module

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.2 Connecting FCS and DARWIN/DAQSTATION>

J14-4

J14.2 Connecting FCS and DARWIN/DAQSTATION

The following explains the configuration of connections between an FCS and one or
more DARWIN/DAQSTATION.

Connection Configuration DARWIN/DAQSTATION

An example of a connection between FCS and DARWIN/DAQSTATION is shown below:
Ethernet

HIS

HIS
Control bus

RDY
RCV
SND

CN1

RDY
RCV
SND

CN1

FCS
Ethernet

HUB

Ethernet
module
DARWIN

Ethernet
module
DAQSTATION

DARWIN
J140201E.EPS

Figure Example of Connection between FCS and DARWIN/DAQSTATION

Ethernet Interface on DARWIN/DAQSTATION

Ethernet interface on DARWIN/DAQSTATION are as follows:
DARWIN:

DT300-41 Ethernet Module

DAQSTATION:

Ethernet interface is provided as standard specification

SEE ALSO
For more information about the network configuration, see the users manual of the corresponding
DARWIN/DAQSTATION.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J14-5

<J14.2 Connecting FCS and DARWIN/DAQSTATION>

Addressing
The IP address and subnet mask must be specified for each ACM71 installed in the FCS.
Up to three IP addresses and subnet masks are specified for a single FCS, including the IP
address and subnet mask specified for the control bus of the FCS.
These three IP addresses must have different subnets, respectively.
HIS
Subnet 1
(control bus)

172.16.1.24
(255.255.0.0)
172.16.1.1
(255.255.0.0)

Subnet 2

DARWIN

172.16.1.2
(255.255.0.0)

Subnet 3

172.21.1.1
(255.255.0.0)

RDY
RCV
SND

CN1

RDY
RCV
SND

CN1

172.22.1.1
(255.255.0.0)

FCS

Ethernet

Control bus

DAQSTATION

RDY
RCV
SND

CN1

RDY
RCV
SND

CN1

FCS

Ethernet

DARWIN
Router
Ethernet
DAQSTATION

Subnet 4
(router destination, etc.)
J140202E.EPS

Figure Addressing

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.3 Accessible Data DARWIN/DAQSTATION>

J14-6

J14.3 Accessible Data DARWIN/DAQSTATION

This section explains DARWIN/DAQSTATION internal data that can be accessed
using communication I/O.

Accessible Data DARWIN/DAQSTATION

The following section describes the accessible internal data of DARWIN/DAQSTATION.
Measured Data
Measured data acquired by the DARWIN/DAQSTATION can be stored in the FCS via
ACM71.
Calculated Data
Calculated data contained in the DARWIN/DAQSTATION can be stored in the FCS
via ACM71.
Note that calculation start and stop are not supported by the DARWIN/DAQSTATION
communication package. These operations must be performed on the DARWIN/
DAQSTATION side.
Alarm Status
An alarm status contained in the DARWIN/DAQSTATION can be stored in the FCS via
ACM71.
For all the data above, the channels from which data is acquired and the area in which the
acquired data is stored or processed should be defined in the communication I/O area
using the engineering functions.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J14-7

<J14.4 Subsystem Data Storing Format DARWIN/DAQSTATION>

J14.4 Subsystem Data Storing Format DARWIN/

DAQSTATION
This section explains the format in which the subsystem data acquired from DARWIN/DAQSTATION is stored in the FCS.
Subsystem data from DARWIN/DAQSTATION is stored in FCS without additional
data processing or data conversion.

Storing Format of Measured Data and Alarm Status DARWIN/

DAQSTATION
Measured data from DARWIN/DAQSTATION
Data length

Year

Month

Date

Hour

Minute

Second A1

B1 C1

D1

DATA1

An

Bn

Cn Dn

DATAn

Data within FCS

Measured data

DATA1
DATA2
DATA3

:
:
:

:
:
DATAn
Alarm status

C1

D1

C2

D2

C3

D3
:
:
:

:
:

Cn

Dn

(C1)
Alarm2

(D1)
Alarm1

Alarm4

(C2)
Alarm2

Alarm3
(D2)

Alarm1

Alarm4

Alarm3

:
:
(Cn)
Alarm2

(Dn)
Alarm1

Alarm4

Alarm3

A1 to An
B1 to Bn
C1 to Cn
D1 to Dn
DATA 1 to DATA n

:Base unit number

:Channel number
:Alarm status (level 1/2)
:Alarm status (level 3/4)
:Measured data

Alarm

:No alarm
:High limit alarm
:Low limit alarm
:Difference high limit alarm
:Difference low limit alarm
:High limit on rate-of-change alarm
:Low limit on rate-of-change alarm

0
1
2
3
4
5
6

J140401E.EPS

Figure Storing Format of Measured Data and Alarm Status DARWIN/DAQSTATION

SEE ALSO
For details on alarm status, refer to the Users Manual of DARWIN/DAQSTATION used.
For details on measured data, see the following:
J14.9, Data Acquired from DARWIN/DAQSTATION

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.4 Subsystem Data Storing Format DARWIN/DAQSTATION>

J14-8

Storing Format of Calculated Data and Alarm Status DARWIN/

DAQSTATION
A Calculated datum consists of two words.
Calculated data from DARWIN/DAQSTATION
Data length Year Month Date Hour Minute Second E1 F1 G1 H1 DATA1-1 DATA1-2 En Fn Gn Hn DATAn-1 DATAn-2

Data within FCS

Calculated data

DATA1-1
DATA1-2
DATA2-1

:
:
:

DATA2-2
:
DATAn-1
DATAn-2
Alarm status

G1

H1

G2

H2

G3

H3
:
:
:

:
:

Gn

Hn

(G1)
Alarm2

(H1)
Alarm1

Alarm4

Alarm1

Alarm4

(G2)
Alarm2

Alarm3
(H2)
Alarm3

:
:
(Gn)
Alarm2

(Hn)
Alarm1

Alarm4

Alarm3

E1 to En
F1 to Fn
G1 to Gn
H1 to Hn
DATA 1 to DATA n

:Base unit number

:Channel number
:Alarm status (level 1/2)
:Alarm status (level 3/4)
:Calculated data

Alarm

:No alarm
:High limit alarm
:Low limit alarm
:Difference high limit alarm
:Difference low limit alarm
:High limit on rate-of-change alarm
:Low limit on rate-of-change alarm

0
1
2
3
4
5
6

J140402E.EPS

Figure Storing Format of Calculated Data and Alarm Status DARWIN/DAQSTATION

SEE ALSO
For details on alarm status, refer to the Users Manual of the DARWIN/DAQSTATION used.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.5 Setting Items on System View DARWIN/DAQSTATION>

J14-9

J14.5 Setting Items on System View DARWIN/

DAQSTATION
DARWIN/DAQSTATION

This section explains the items set in System View, particularly those unique to
DARWIN/DAQSTATION, and their recommended values.
SEE ALSO
For the general description of setting items in the Detailed Setting tab in the Create New IOM dialog box
and items set commonly for connected devices, see the following:
Setting Items for ACM71 in J1.5.1, Overview of Setting Items on System View

The following items should be set for DARWIN/DAQSTATION.

FCS Properties
Detailed Setting tab of the Create New IOM Dialog Box
The IP address, subnet mask, attributes, destination address, router address
and hop count must be set.
Either one of the Detailed Setting tabs 2 to 5 of the Create New IOM dialog box
The name of the connected device, option 1 (no response detection time),
option 2 (communication retry), option 3 (interval of retries) and options 4 and 5
(port numbers on the DARWIN/DAQSTATION side) must be set.
After creating the new I/O module, the settings can be modified in the Detailed
Setting tab and Detailed Setting tabs (2 to 5) displayed under the I/O module properties.

FCS Properties DARWIN/DAQSTATION

Select DAQ_E from the options in the Constants tab of the FCS Properties.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.5 Setting Items on System View DARWIN/DAQSTATION>

J14-10

Create New IOM Dialog Box DARWIN/DAQSTATION

Perform the following settings in the Detail Setting tab of the Create New IOM dialog box.
IP Address
Subnet Mask
Attribute
Destination Address
Router Address
Hop Count
SEE ALSO
For the general description of the setting items and setting contents, see the following:
Setting Items for ACM71 in J1.5.1, Overview of Setting Items on System View

Specify the following setting using either one of Detailed Setting tabs 2 through 5 in the
Create New IOM dialog box. Select a tab from Detailed Setting tabs 2 to 5.

Connected Device Name

Specify DAQ_E as the name of the connected device for both DARWIN and
DAQSTATION.

Option 1
Specify the no response detection time for both DARWIN and DAQSTATION.

Option 2
Specify the communication retry performed in the event of a communication error for both
DARWIN and DAQSTATION.

Option 3
Specify the interval of retries for recovery communication for both DARWIN and
DAQSTATION.

Option 4
Make sure to specify the port number for DARWIN communication 34151 in the case of
DARWIN.
If 0 is specified, the system will operate in the same manner as when 34151 is specified.
In other words, the port number for DARWIN communication is set to 34151 automatically.

Option 5
Make sure to specify the port number for DAQSTATION communication 34260 in the
case of DAQSTATION.
If 0 is specified, the system will operate in the same manner as when 34260 is specified.
In other words, the port number for DAQSTATION communication is set to 34260 automatically.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.6 Setting Items on Communication I/O Builder DARWIN/DAQSTATION>

J14-11

J14.6 Setting Items on Communication I/O Builder

DARWIN/DAQSTATION
This section explains the setting items of the Communication I/O Builder unique to
DARWIN/DAQSTATION, as well as their recommended values.
SEE ALSO
For an overview of the setting items of the Communication I/O Builder and settings common to connected
devices, see the relevant section in the following:
J1.5.2, Overview of Settings on Communication I/O Builder

The following items should be set in the case of DARWIN/DAQSTATION.

Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

Element DARWIN/DAQSTATION
Element

With respect to the address of the subsystem data buffer, the element number is indicated
on Communication I/O Builder. The element number is indicated for display purposes only.
It is not selectable.

Buffer DARWIN/DAQSTATION
Buffer

This item sets the buffer used by a program.

Always set the buffer size since this is a required setting item of Communication I/O
Builder.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.6 Setting Items on Communication I/O Builder DARWIN/DAQSTATION>

J14-12

Program Name DARWIN/DAQSTATION

Program Name

Set the unit number, slot number and DAQ_E program name of subsystem as follows:
u-sProgramName
u
s
Program Name

:
:
:

Unit number
Slot Number
DAQ_E

Size DARWIN/DAQSTATION
Size

Specify the data size (data length) from the head address set in the Device & Address
setting for both DARWIN and DAQSTATION.
The setting is in word units.
The data size is set differently according to the type of data acquired.

For Measured Data

It is possible to assign up to 60 words to DARWIN or 30 words to DAQSTATION as data
size.
A request exceeding the limit of the sub-unit is not allowed.
If data with a size of m words is assigned from address n, the data from DARWIN is stored
in the FCS as follows.
16bits

CH (n)
CH (n + 1)
CH (n + 2)

CH (n + m - 1)
J140601E.EPS

Figure Example of Data Size Setting (in the Case of Measured Data) DARWIN/DAQSTATION

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.6 Setting Items on Communication I/O Builder DARWIN/DAQSTATION>

J14-13

For Calculated Data

It is possible to assign up to 120 words to DARWIN or 60 words to DAQSTATION as data
size.
If data with a size of m words is assigned from address n, the data from DARWIN is stored
in the FCS as follows because calculated data is expressed by 32 bits.
16bits

CH(n)
CH (n + 1)

CH (n + (m/2) - 1)
J140602E.EPS

Figure Example of Data Size Setting (in the Case of Calculated Data) DARWIN/DAQSTATION

For Alarm Status

It is possible to assign up to 60 words to DARWIN or 30 words to DAQSTATION as data
size.
Set the same size as the measured data if measured data is stored immediately before an
alarm status. Set half the size of the calculated data if calculated data is stored immediately
before an alarm status.
If data with a size of m words is assigned from address n, the data from DARWIN is stored
in the FCS as follows.
16bits

CH (n)
CH (n + 1)
CH (n + 2)

CH (n + m - 1)
J140603E.EPS

Figure Example of Data Size Setting (In the Case of Alarm Status) DARWIN/DAQSTATION

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.6 Setting Items on Communication I/O Builder DARWIN/DAQSTATION>

J14-14

Port DARWIN/DAQSTATION
Port

Port 1 is set for use.

IP Address DARWIN/DAQSTATION
IP Address

Specify the appropriate IP address for both DARWIN and DAQSTATION.

Station DARWIN/DAQSTATION
Station

The station number can be specified freely because neither DARWIN nor DAQSTATION
uses any station number. However, it is recommended to specify a unique station number
for each definition of transmission frame. It is easier to identify the area in which an error
has occurred this way since the station number is returned as a system alarm message
when a communication error occurs.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.6 Setting Items on Communication I/O Builder DARWIN/DAQSTATION>

J14-15

Device & Address DARWIN/DAQSTATION

Device & Address

Specify the head address for both DARWIN and DAQSTATION.

If an alarm status should be acquired, it should be specified in the line immediately after a
specification to acquire either measured data or calculated data. An error will not occur
even if an address different from that of measured data or calculated data immediately
before is specified. The alarm status of the measured data or calculated data immediately
before is acquired.

In the Case of DARWIN

The following head addresses can be specified.
Measured Data
DTust
u

st

Unit number (0 in case of a standalone model. 0 to 5 for subunits in the case of an

expandable model.)
s is the slot number and t is the terminal number (st may be a value from 01 to 60 for both
standalone and expandable models.)

Standalone model

Expandable model
Unit 0

Unit 1

DT031 DT021 DT011 DT001

|
|
|
|
DT040 DT030 DT020 DT010

Unit 0

DT051 DT041 DT031 DT021 DT011 DT001

|
|
|
|
|
|
DT060 DT050 DT040 DT030 DT020 DT010
Unit 5

DT551 DT541 DT531 DT521 DT511 DT501

|
|
|
|
|
|
DT560 DT550 DT540 DT530 DT520 DT510
J140604E.EPS

Figure Correspondence between Head Address and Physical Position of DARWIN Terminals
DARWIN

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.6 Setting Items on Communication I/O Builder DARWIN/DAQSTATION>

J14-16

Calculated Data
DTAst
st

s is the slot number and t is the terminal number (st may be a value from 01 to 60 for both
standalone and expandable models.)

Alarm Status
ALust
u

st

Unit number (0 for a standalone model and 0 to 5 for an expandable model in the case of an
alarm status corresponding to measured data.A for an alarm status corresponding to
calculated data.)
s is the slot number and t is the terminal number (st may be a value from 01 to 60 for both
standalone and expandable models in the case of an alarm status corresponding to
measured data. st may be a value from 01 to 60 for both standalone and expandable
models in the case of an alarm status corresponding to calculated data as well.)

In the Case of DAQSTATION

The following head addresses can be specified.
Measured Data
QDTtt
tt

Terminal number (01 to 30)

Calculated Data
QDAtt
tt

Terminal number (31 to 60)

Alarm Status
QALtt
tt

Teminal number (01 to 30 for alarm status corresponding to measured data, and 31 to 60 for
alarm status corresponding to calculated data.)

Data Type DARWIN/DAQSTATION

Data Type

Specify the data type of the subsystem for both DARWIN and DAQSTATION.
Measured data:

Input (16-Bit Signed)

Calculated data:

Input (32-Bit Signed)

Alarm status:

Input (16-Bit Unsigned)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.6 Setting Items on Communication I/O Builder DARWIN/DAQSTATION>

J14-17

Reverse DARWIN/DAQSTATION
Reverse

Specify whether or not to make the bit or word arrangement in the FCS in reverse order of
the subsystem data.
Choose [No] for this setting.
The default setting is [No].

Scan DARWIN
Scan

For this setting, it should be specified whether or not to use a function to load the analog
communication I/O data in the I/O data buffer at the beginning of high-speed scan of the
FCS.

Service Comment DARWIN/DAQSTATION

Service Comment

A comment can be set.

Label DARWIN/DAQSTATION
Label

The name of the function block I/O terminal can be set as a user-defined label name.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J14-18

<J14.7 Settings on Subsystem DARWIN/DAQSTATION>

J14.7 Settings on Subsystem DARWIN/

DAQSTATION
In order to perform subsystem communication with DARWIN/DAQSTATION, appropriate settings are required for the Ethernet interface module on the DARQIN/
DAQSTATION side.
This section explains the setting switches of the Ethernet module on DARWIN and
setting items in DAQSTATION.

Setting Switches of Ethernet Module DARWIN

The following table shows the setting switches of the Ethernet module on DARWIN.
Table Ethernet Module Setting Switches on DARWIN

Switch name

Setting item

Description of setting

SW1
SW2

Mode setting

Set the mode of DARWIN

SW1 is ON and SW2 is OFF:
Setting mode (*1)
SW1 is OFF and SW2 is ON:
Test mode (*2)
SW1 is OFF and SW2 is OFF:
Communication mode (*3)

SW3

Setting of keep alive

SW3 is ON: Keep alive is enabled.

SW3 is OFF: Keep alive if disabled.

Setting

SW1 is OFF
SW2 is OFF

SW3 is ON
J140701E.EPS

*1:
*2:
*3:

A mode for setting IP address, subnet mask, and default gateway of DA100 on a PC.
A mode for testing the status of the physical connection.
A mode for communicating by connecting to a network.Specify this mode when reading measured data from a DA100.

Ethernet Setting Items DAQSTATION

The table below shows the Ethernet setting items for DAQSTATION.
Table Ethernet Setting Items for DAQSTATION
Setting item

Description of setting

Setting

Login function

Valid : Only registered users can log in.

Invalid : Users other than registered users can log in.

Invalid

User level selection

admin : Administrator
user : Users

user

User registration

ON : Register a user.
OFF : Do not register a user.

OFF

Communication timeout

ON : Check for communication timeout.

OFF : Do not check for communication timeout.

ON

Keep alive setting

ON : Enable keep alive

OFF: Disable keep alive

ON
J140702E.EPS

It is possible to log in to this function as a user if the login function is set to Invalid, by
accessing it with the user name user. A password is not required.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.8 Communication Packet DARWIN/DAQSTATION>

J14-19

J14.8 Communication Packet DARWIN/

DAQSTATION
The sections below explain the communication packet format when performing
communication with the DARWIN/DAQSTATION.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.8 Communication Packet DARWIN/DAQSTATION>

J14-20

J14.8.1 Communication Packet Used for Communicating with

DARWIN
The following communication packet formats are used when performing communication with the DARWIN.

Communication Packet for Byte Sequence Specification DARWIN

The figure below shows the communication packet format for byte sequence specification.
Specify 0 for p1 when using the DARWIN/DAQSTATION communication package.
Byte Sequence Specification
'E' 'B' p1 CR LF
p1

: Byte output sequence

'0' From MSB (most significant byte)
'1' From LSB (least significant byte)
J140801E.EPS

Figure Communication Packet for Byte Sequence Specification DARWIN

Communication Packet for Reply DARWIN

The figure below shows the communication packet format for reply.
Reply
'E' ERR CR LF
ERR: Error code
'0' The request was received normally.
'1' An error occurred.
J140802E.EPS

Figure Communication Packet for Reply DARWIN

Communication Packet for Requesting Measured Data and Calculated

Data DARWIN
The figure below shows the communication packet format for requesting measured data
and calculated data.
Specify 1 for p1 when using the DARWIN/DAQSTATION communication package.
Communication Packet for Requesting Measured Data and Calculated Data
'E' 'F' p1 ',' p2 ',' p3 CR LF
p1: Specification of data to be returned.
'0' Only measured data or calculated data is returned.
'1' Measured data or calculated data is returned along with the alarm status.
p2: The head channel to be returned
The head channel is specified using 3 digits in ASCII coding
(the first digit should be an A in case of calculated data).
p3: The end channel to be returned
The end channel is specified using 3 digits in ASCII coding
(the first digit should be an A in case of calculated data).
J140803E.EPS

Figure Communication Packet for Requesting Measured Data and Calculated Data DARWIN

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.8 Communication Packet DARWIN/DAQSTATION>

J14-21

Communication Packet for Measured Data and Calculated Data DARWIN

The figure below shows the communication packet format for measured data and calculated data.
Communication Packet for Measured Data and Calculated Data
Data length
Year

Month Date

A1

B1

An
E1

En

Hour

Minute

Second

C1

D1

DATA 1

Bn

Cn

Dn

DATA n

F1

G1

H1

DATAA 1

Fn

Gn

Hn

DATAA n

Data length:
Year:
Month:
Date:
Hour:
Minute:
Second:
A1 to An, E1 to En:
B1 to Bn, F1 to Fn:
C1 to Cn, G1 to Gn:
D1 to Dn, H1 to Hn:
DATA 1 to DATA n:
DATAA 1 to DATAA n:

MS DM

Base unit number

Channel number
Alarm status (level 1/2)
Alarm status (level 3/4)
Measured data
Calculated data

Measured data Calculated data

Meaning

7FFF

7FFF7FFF

Plus over data

8001

80018001

Minus over data

8002

80028002

The measured range is set to SKIP.

8004

80048004

Abnormal data

8005

80058005

No data
J140804E.EPS

Figure Communication Packet for Measured Data and Calculated Data DARWIN

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.8 Communication Packet DARWIN/DAQSTATION>

J14-22

J14.8.2 Communication Packet Used for Communicating with

DAQSTATION
The following communication packet formats are used when performing communication with DAQSTATION.

Communication Packet for Login Processing DAQSTATION

It is assumed that passwords are not used on the DAQSTATION side when using this
communication package.The login processing refers to a connection request.After the
connection is established normally, the DAQSTATION side requests entry of a user name.

Communication Packet for Requesting User Name Entry DAQSTATION

The figure below shows the communication packet format for requesting user name entry.
Communication Packet for Requesting User Name Entry
'E' ERR ERR NO CR LF
ERR:

Error code
'0'
'1'
ERR NO: Error number
'402
Other than '402'

The request was received normally.

An error occurred.
Either admin or user was entered.
Communication Error
J140805E.EPS

Figure Communication Packet for Requesting User Name Entry DAQSTATION

Communication Packet for User Name Entry DAQSATION

The figure below shows the communication packet format for user name entry.
Communication Packet for User Name Entry
U

R CR LF
J140806E.EPS

Figure Communication Packet for User Name Entry DAQSTATION

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.8 Communication Packet DARWIN/DAQSTATION>

J14-23

Communication Packet for User Name Reply DAQSTATION

The figure below shows the communication packet format for user name reply.
ERR NO is not returned if ERR is set to 0.
Communication Packet for User Name Entry
'E' ERR ERR NO CR LF
ERR:

Error code
'0'
The request was received normally.
'1'
An error occurred.
ERROR NO: Error number
J140807E.EPS

Figure Communication Packet for User Name Reply DAQSTATION

SEE ALSO
For the details of ERR NO, refer to the users manual for the DAQSTATION used.

Communication Packet for Byte Sequence Specification DAQSTATION

The figure below shows the communication packet format for byte sequence specification.
Specify 0 for p1 when using the DARWIN/DAQSTATION communication package.
Byte Sequence Specification
'B' 'O' p1 CR LF
p1: Byte output sequence
'0'
From MSB (most significant byte)
'1'
From LSB (least significant byte)
J140808E.EPS

Figure Communication Packet for Byte Sequence Specification DAQSTATION

Communication Packet for Reply DAQSTATION

The figure below shows the communication packet format for reply.
Reply
'E' ERR CR LF
ERR: Error code
'0' The request was received normally.
'1' An error occurred.
J140809E.EPS

Figure Communication Packet for Reply DAQSTATION

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.8 Communication Packet DARWIN/DAQSTATION>

J14-24

Communication Packet for Requesting Measured Data and Calculated

Data DAQSTATION
The figure below shows the communication packet format for requesting measured data
and calculated data.
Communication Packet for Requesting Measured Data and Calculated Data
'F' 'D' p1 ',' p2 ',' p3 CR LF
p1: Specification of data to be returned.
'0' The latest measured data or the calculated data is returned in ASCII coding.
'1' The latest measured data or the calculated data is returned in binary coding.
p2: The head channel to be returned
The head channel is specified using 2 digits in ASCII coding
(01 to 12/31 to 42 in case of DX100, 01 to 60 in case of DX200).
p3: The end channel to be returned
The end channel is specified using 2 digits in ASCII coding
(01 to 12/31 to 42 in case of DX100, 01 to 60 in case of DX200.)
J140810E.EPS

Figure Communication Packet for Requesting Measured Data and Calculated Data
DAQSTATION

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.8 Communication Packet DARWIN/DAQSTATION>

J14-25

Communication Packet for Measured Data and Calculated Data

DAQSTATION
The figure below shows the communication packet format for measured data and calculated data.
Communication Packet for Measured Data and Calculated Data
'E'

'B'

CR

LF

Length
FL

AT
BL

Year

SUM1
BYTE

Month Date

Hour

Minute

Second

A1

B1

C1

D1

DATA 1

An

Bn

Cn

Dn

DATA n

E1

F1

G1

H1

DATAA 1

En

Fn

Gn

Hn

DATAA n

MS

(Reserved)

Flag

SUM2
FL:
AT:
SUM1:
BL:
BYTE:
Year:
Month:
Date:
Hour:
Minute:
Second:
Flag:
A1 to An, E1 to En:
B1 to Bn, F1 to Fn:
C1 to Cn, G1 to Gn:
D1 to Dn, H1 to Hn:
DATA 1 to DATA n:
DATAA 1 to DATAA n:
SUM2:

Flag
Identifier
Checksum1
Number of blocks (specify 1.)
Number of bytes

Specification of measured data or calculated data

Channel number
Alarm status (level 1/2)
Alarm status (level 3/4)
Measured data
Calculated data
Checksum2

Measured data

Calculated data

Meaning

7FFF

7FFF7FFF

Plus over data

8001

80018001

Minus over data

8002

80028002

The measured range is set to SKIP.

8004

80048004

Abnormal data

8005

80058005

No data
J140811E.EPS

Figure Communication Packet for Measured Data and Calculated Data DAQSTATION

IM 33S01B30-01E

13th Edition : Dec.26,2005-00

J14-26

<J14.9 Data Acquired from DARWIN/DAQSTATION>

J14.9 Data Acquired from DARWIN/DAQSTATION

The section below explains the data specifications when performing subsystem
communication with DARWIN/DAQSTATION.
Measured Data
Alarm Status
Abnormal Data

Measured Data DARWIN/DAQSTATION

The measured data sent from DARWIN/DAQSTATION are stored in FCS intact. And signal
processing such as input conversion is not performed except for changing scales.
The measured data are handled differently depending on whether the scales are set or not
on the DARWIN/DAQSTATION.

If the Scale is not Set on the DARWIN/DAQSTATION Side

Measured data from the DARWIN/DAQSTATION side is sent and stored as integer data
after eliminating any decimal points.
The following shows an example of measured data when the scale is not set on the DARWIN side.
Table Example of Measured Data when the Scale is not Set on the DARWIN Side
Channel Mode

Scale

Wire
Input range Range
connection

Span

Scale

(L)

(R)

CH001

VOLT

OFF

2V

-2.0000

2.0000

CH002

VOLT

OFF

2V

-2.0000

2.0000

CH003

VOLT

OFF

2V

-2.0000

2.0000

CH004

VOLT

OFF

2V

-2.0000

2.0000

CH005

VOLT

OFF

2V

-2.0000

2.0000

CH006

TC

OFF

TypeR

0.0

1760.0

CH007

TC

OFF

TypeR

0.0

1760.0

CH008

TC

OFF

TypeR

0.0

1760.0

CH009

TC

OFF

TypeR

0.0

1760.0

CH010

TC

OFF

TypeR

0.0

1760.0

(L)

(R)

J140901E.EPS

If the above settings are made on the DARWIN side, the measured data values from
CH001 to CH005 are converted in the range from -2.0000 to 2.0000 to integers without
decimal points; i.e., values between -20000 and 20000 are stored in the FCS. For example,
if the measured data of CH002 is 1.5000 V, the value stored will be 15000 in the FCS.
Moreover, the measured data values for CH006 to CH010 are converted in the range from
0.0 to 1760.0 to integers without decimal points. This means the values between 0 and
17600 are stored in the FCS.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J14-27

<J14.9 Data Acquired from DARWIN/DAQSTATION>

If the Scale is Set on the DARWIN/DAQSTATION Side

The measured data on the DARWIN/DAQSTATION side is scaled linearly using the scale
set on the DARWIN/DAQSTATION side, and then sent and stored as integer data after
removing any decimal points.
The following shows an example of measured data when the scale is set on the DARWIN
side.
Table Example of Measured Data when the Scale is Set on the DARWIN Side
Channel Mode

Scale

Wire
Input range Range
connection

Span

Scale

(L)

(R)

(L)

(R)

CH001

VOLT

OFF

2V

-2.0000

2.0000

-30000

30000

CH002

VOLT

OFF

2V

-2.0000

2.0000

-30000

30000

CH003

VOLT

OFF

2V

-2.0000

2.0000

-30000

30000

CH004

VOLT

OFF

2V

-2.0000

2.0000

-30000

30000

CH005

VOLT

OFF

2V

-2.0000

2.0000

-30000

30000

CH006

TC

OFF

TypeR

0.0

1760.0

-30000

30000

CH007

TC

OFF

TypeR

0.0

1760.0

-30000

30000

CH008

TC

OFF

TypeR

0.0

1760.0

-30000

30000

CH009

TC

OFF

TypeR

0.0

1760.0

-30000

30000

CH010

TC

OFF

TypeR

0.0

1760.0

-30000

30000
J140902E.EPS

If the above settings are made on the DARWIN/DAQSTATION side, the measured data
values from CH001 to CH010 are converted according to the scale and the range set for
each channel. The values stored in FCS will be from -30000 to 30000. For example, if the
measured data of CH002 is 1.5000 V, the value stored in the FCS will be 22500.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J14-28

<J14.9 Data Acquired from DARWIN/DAQSTATION>

Example of Setting Measured Data DARWIN/DAQSTATION

This section explains how to assign data measured at CH001 and CH002 to two function
blocks on the FCS side, PVI-001 and PVI-002, assuming that the following settings have
been made on the DARWIN side.CH001 and CH002 are measured in the range from -2 V
to 2 V.
Table Example of Definition on the DARWIN Side

Channel

Mode

Scale

Wire
Input rage
connection

Range

Span

Scale

(L)

(R)

CH001

VOLT

OFF

2V

-2.0000

2.0000

CH002

VOLT

ON

2V

-2.0000

2.0000

CH003

SKIP

(L)

(R)
0

4000

J140903E.EPS

The following shows how to set the measured data on the FCS side.
1.

Define the element numbers for storing the measured data at CH001 and CH002 on
the DARWIN side in the FCS on Communication I/O Builder. An example of element
number definition is shown below.

Table Example of Element Number Definition by the Communication I/O Builder

Element
number

Program Data size

Station Device &
IP address
name
number address

Buffer
size

Data type

%WW0001 2

2-1DAQ_E 2

DT001

Input (16-Bit Signed)

%WW0002 *

%WW0003
J140904E.EPS

2.

Create function blocks PVI-001 and PVI-002 by the Function Block Overview Builder.
The following table shows an example of how to create the function blocks.

Table Example of How to Create Function Blocks by the Function Block Overview Builder

No

Tag Type
Tag
Low limit
name name comment
value

High limit Engineering Input signal

value
unit symbol conversion

Input
Totalizer
connection
time unit
information

001 PVI-001 PVI

-2.0000

2.0000

CommunicaNo
tion input

%WW0001

002 PVI-002 PVI

-2.0000

2.0000

CommunicaNo
tion input

%WW0002

003
J140905E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.9 Data Acquired from DARWIN/DAQSTATION>

3.

J14-29

Perform the detailed settings for PVI-001 on the Function Block Detail Builder. Specify
the data conversion gain and the data conversion bias as follows in order to convert
data from DARWIN on the FCS side.
Scale on the FCS side
2.0000

-20000

20000

Slope=

Value of data transmitted

from DARWIN

2.0000
=0.0001
20000

(data conversion gain=0.0001)

y intercept=0
(data conversion bias=0)

-2.0000

J140906E.EPS

Figure Correspondence between Data Value Sent from DARWIN and the Scale on the FCS Side
(PVI-001)
Basic
Tag Name

PVI-001

Model Name

PVI

Tag Comment
Lvl

Scan Period

Basic Scan

Scan coefficient

1
0

Scan phase
Input Signal Conversion
Input Signal Convention

SUBSYS

Data Conversion Gain

0.0001

Data Conversion Bias

0.000

Input High Limit Detection Set Value

106.25

Input Low Limit Detection Set Value

-6.25

Specify the values

for conversion.

Totalizer
Totalizer Time Unit

No

J140907E.EPS

Figure Data Conversion Gain and Data Conversion Bias Settings by the Function Block Detail
Builder (PVI-001)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.9 Data Acquired from DARWIN/DAQSTATION>

4.

J14-30

Perform the detailed settings for PVI-002 on the Function Block Detail Builder. Specify
the data conversion gain and data conversion bias as follows in order to convert data
from DARWIN on the FCS side.

Scale on the FCS side

2.0000

4000

Slope=

Value of data transmitted

from DARWIN

2.0000-(-2.0000)
=0.001
4000

(data conversion gain=0.001)

y intercept=-2.0000
-2.0000

(data conversion bias=-2.0000)

J140908E.EPS

Figure Correspondence between Data Value Sent from DARWIN and the Scale on the FCS Side
(PVI-002)
Basic
Tag Name

PVI-002

Model Name

PVI

Tag Comment
Lvl

Scan Period

Basic Scan

Scan coefficient

1
0

Scan phase
Input Signal Conversion
Input Signal Convention

SUBSYS

Data Conversion Gain

0.001

Data Conversion Bias

-2.0000

Input High Limit Detection Set Value

106.25

Input Low Limit Detection Set Value

-6.25

Specify the values

for conversion.

Totalizer
Totalizer Time Unit

No

J140909E.EPS

Figure Data Conversion Gain and Data Conversion Bias Settings by the Function Block Detail
Builder (PVI-002)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J14-31

<J14.9 Data Acquired from DARWIN/DAQSTATION>

Alarm Status DARWIN/DAQSTATION

Alarm status data sent from the DARWIN/DAQSTATION side is stored in the FCS in the
following manner.
16bits
Alarm2

Alarm1

Alarm4

Alarm3

CH (n)

Alarm2

Alarm1

Alarm4

Alarm3

CH (n + 1)

Alarm2

Alarm1

Alarm4

Alarm3

CH (n + 2)

Alarm2

Alarm1

Alarm4

Alarm3

CH (n + (m/2) - 1)
J140910E.EPS

Figure Storage Status of Alarm Status Data

The content of each alarm is set on the DARWIN/DAQSTATION side and transmitted as
one of the following six states.
0: No alarm
1: High limit alarm
2: Low limit alarm
3: Difference high limit alarm
4: Difference low limit alarm
5: High limit on rate-of-change alarm
6: Low limit on rate-of-change alarm
SEE ALSO
For details on the alarm status, refer to the Users Manual of the DARWIN/DAQSTATION.

Abnormal Data DARWIN/DAQSTATION

If data sent from the DARWIN/DAQSTATION side is abnormal, the data and data status
are stored in the FCS according to the type of abnormal data.
Table Data and Data Status Corresponding to Abnormal Data Type

Type of abnormal data

Data and data status stored on the FCS side

Data value

Data status

There is no module that was installed within the setting range. Maintains the previous data.

BAD

The setting range exceeds the unit range.

Maintains the previous data.

BAD

Plus over data

7FFF (7FFF7FFF) (*1)

Minus over data

8001 (80018001) (*1)

The measurement range is set to SKIP.

Maintains the previous data.

BAD

Abnormal data

Maintains the previous data.

BAD

No data (INVALID)

Maintains the previous data.

J140911E.EPS

*1:

The values in () are the data values set in the case of calculation channels.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J14-32

<J14.9 Data Acquired from DARWIN/DAQSTATION>

If There is a Module that has not been Installed Within the Setting Range
For the data buffers assigned on a communication I/O builder, if the module is not physically installed, the buffers will hold the previous data and the data status become BAD.
The following shows an example of definition by the Communication I/O Builder and the
status of data storage in the FCS.
Table Example of Settings by the Communication I/O Builder
Element
number

Program Data size

Station Device &
IP address
name
number address

Buffer
size

Data type

%WW0001 30

2-1DAQ_E 30

DT001

Analog input
(16-bit signed integer)

%WW0002 *

%WW0003 *
:

*
:

%WW0030 *

*
:

*
:

*
:

*
:

:
*
J140912E.EPS

DARWIN configuration

Main body

Unit 0

DT051 DT041 DT031 DT021 DT011 DT001

|
|
|
|
|
|
DT060 DT050 DT040 DT030 DT020 DT010

16bits

Previous data (data status BAD) %%WW0001

Previous data (data status BAD) %%WW0010

Previous data (data status BAD) %%WW0011
Corresponds to
buffer size 30

Previous data (data status BAD) %%WW0020

Previous data (data status BAD) %%WW0021

Maintains the previous data

because the module has not been installed.

Previous data (data status BAD) %%WW0030

Data storage status in FCS

J140913E.EPS

Figure Status of Data Storage in the FCS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J14-33

<J14.9 Data Acquired from DARWIN/DAQSTATION>

If the Setting Range Exceeds the Unit Range

For the data buffers assigned on a communication I/O builder, if the assignment is beyond
the range of the unit, the buffers will hold the previous data and the data status become
BAD.
The following shows an example of definition on Communication I/O Builder and the status
of data storage in the FCS.
Table Example of Settings on Communication I/O Builder

Element
number

Program Data size

Station Device &
IP address
name
number address

Buffer
size

Data type

%WW0001 30

2-1DAQ_E 30

DT051

Input (16-Bit Signed)

%WW0002 *

%WW0003 *
:
%WW0030 *

*
:

*
:

*
:

*
:

*
:

:
*
J140914E.EPS

DARWIN configuration

Main body

Unit 1

DT111 DT101 DT091 DT081 DT071 DT061

|
|
|
|
|
|
DT120 DT110 DT100 DT090 DT080 DT070

Unit 0

DT051 DT041 DT031 DT021 DT011 DT001

|
|
|
|
|
|
DT060 DT050 DT040 DT030 DT020 DT010

16bits

Previous data (data status BAD) %%WW0001

Previous data (data status BAD) %%WW0010

Previous data (data status BAD) %%WW0011

Corresponds to
buffer size 30

Previous data (data status BAD) %%WW0030

Maintains the previous data

Data storage status in FCS

because the setting range exceeded the unit range.

J140915E.EPS

Figure Status of Data Storage in the FCS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.9 Data Acquired from DARWIN/DAQSTATION>

J14-34

In Case of Plus Over Data

Value 7FFF (7FFF7FFF) (*1) is transmitted from the DARWIN/DAQSTATION side. Value
7FFF (7FFF7FFF) (*2) is stored on the FCS side, the data status does not become BAD.
However, when this signal is undergoing the Subsystem input processing of a function
block, the data status will become IOP+.
*1:
*2:

The value in () is the data value transmitted in the case of calculation channels.
The value in () is the data value transmitted in the case of calculation channels.

In Case of Minus Over Data

Value 8001 (80018001) (*1) is transmitted from the DARWIN/DAQSTATION side. Value
8001 (80018001) (*2) is stored on the FCS side, the data status does not become BAD.
However, when this signal is undergoing the Subsystem input processing of a function
block, the data status will become IOP-.
*1:
*2:

The value in () is the data value transmitted in the case of calculation channels.
The value in () is the data value transmitted in the case of calculation channels.

If the Measurement Range is set to SKIP

Value 8002 (80028002) (*1) is transmitted from a channel for which the measurement
range is set to SKIP on the DARWIN/DAQSTATION side. Previous value is held on the
FCS, and the data status becomes BAD.
*1:

The value in () is the data value transmitted in the case of calculation channels.

In Case of Abnormal Data

Abnormal data occurs if the power supply to a sub unit is turned off, a communication cable
is not connected to a sub unit, or an input module that should exist is not connected. Value
8004 (80048004) (*1) is transmitted from the DARWIN/DAQSTATION side. Previous value
is held on the FCS, and the data status becomes BAD.
*1:

The value in () is the data value transmitted in the case of calculation channels.

In Case of No Data (INVALID)

Data becomes invalid if the measured value is requested via the communication before the
first measurement after the power to the DARWIN/DAQSTATION side is turned on, is
completed. Value 8005 (80058005) (*1) is transmitted from the DARWIN/DAQSTATION
side. The previous value is maintained on the FCS side and processing continues. The
data status does not become BAD.
*1:

The value in () is the data value transmitted in the case of calculation channels.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J14-35

<J14.10 System Alarm Messages Specific to DARWIN/DAQSTATION>

J14.10 System Alarm Messages Specific to DARWIN/

DAQSTATION
This section describes the error codes displayed in system alarm messages that are
specific to DARWIN/DAQSTATION.

Definition Errors DARWIN/DAQSTATION

If there are mistakes in the settings by the Communication I/O Builder, the following definition errors may occur.
The communication will not be performed in case of definitions for which the following
errors occur.
Table Error Codes of Definition Errors DARWIN/DAQSTATION
Code

Meaning

A3B1

Inappropriate address name

A3B2

Inappropriate sub unit number

A3B3

Inappropriate channel number

A3B4

No data definition

A3B5

Size inconsistent with data definition

A3B6

Inappropriate element type

A3B7

Inappropriate communication size allocation

Processing after error occurrence

No communication is performed.

J141001E.EPS

Response Message Errors DARWIN/DAQSTATION

If there is an error in the response from the DARWIN/DAQSTATION, the communication is
retried for the number of times set on the Communication I/O Builder. The following errors
occur if the communication retry fails.
Table Error Codes of Response Message Errors DARWIN/DAQSTATION
Code

Meaning

A3C1

Byte sequence specification no-response

A3C2

Byte sequence specification reply error

A3C3

Byte sequence specification format error

A3C4

<reserved>

A3C5

Specification of output channel for

measured data no-response

A3C6

Specification of output channel for

measured data format error

A3C7

<reserved>

A3C8

User name entry request no-response

A3C9

User name entry request reply error

A3CA

User name entry no-response

A3CB

User name entry reply error

Processing after error occurrence

Communication is performed
for each scan.

J141002E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.10 System Alarm Messages Specific to DARWIN/DAQSTATION>

J14-36

Other Errors DARWIN/DAQSTATION

If other types of errors occur, the communication is retried for the number of times set on
Communication I/O Builder. The following errors occur if the communication retry fails.
Table Error Codes of Other Errors DARWIN/DAQSTATION
Code
A3FF

Meaning

Processing after error occurrence

Other error
J141003E.EPS

SEE ALSO
For error codes pertaining to Ethernet communication, see the following:
J2.4, System Alarm Messages Specific to Ethernet Communication

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.11 Error Handling when Communication Error Occurs DARWIN/DAQSTATION>

J14-37

J14.11 Error Handling when Communication Error

Occurs DARWIN/DAQSTATION
The sections below explain the communication errors that may occur when performing communication with DARWIN/DAQSTATION.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.11 Error Handling when Communication Error Occurs DARWIN/DAQSTATION>

J14-38

J14.11.1 Communication Errors when Communicating with

DARWIN
The following communication errors may occur during the communication with
DARWIN modules.

Errors after Execution of Byte Sequence Specification DARWIN

No-Response Error after Execution of Byte Sequence Specification
DARWIN
If the time before a reply is returned after executing byte sequence specification exceeds
the builders send-receive interval monitoring time, a number of retries equal to the
number of retries set in the builder will be attempted.
If the communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a no-response error is returned for the
byte sequence specification and further retries will be performed until the communication
recovers.
ACM71 side

Byte sequence
specification

Byte sequence
specification
Send-receive interval
monitoring time

DARWIN side

Retries
J141101E.EPS

Figure No-Response Error after Execution of Byte Sequence Specification DARWIN

Reply Error after Execution of Byte Sequence Specification DARWIN

If byte sequence specification is executed but the reply is returned in error (E1+CR+LF),
a number of retries equal to the number of retries set in the builder will be attempted.
If the communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a reply error is returned for the byte
sequence specification and further retries will be performed until the communication
recovers.
ACM71 side
DARWIN side

Byte sequence
specification

Byte sequence
specification
Reply
("E1"+CR+LF)

Reply
("E1"+CR+LF)

Retries
J141102E.EPS

Figure Reply Error after Execution of Byte Sequence Specification DARWIN

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.11 Error Handling when Communication Error Occurs DARWIN/DAQSTATION>

J14-39

Format Error after Execution of Byte Sequence Specification DARWIN

If byte sequence specification is executed but the reply is returned in an unexpected
frame format, a number of retries equal to the number of retries set in the builder will be
attempted.
If the communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a format error is returned for the byte
sequence specification and further retries will be performed until the communication
recovers.
ACM71 side

Byte sequence
specification

Byte sequence
specification
Reply
(?)

Reply
(?)

DARWIN side

Retries
J141103E.EPS

Figure Format Error after Execution of Byte Sequence Specification DARWIN

Error after Execution of Specification of Output Channel for Measured

Data DARWIN
No-Response Error after Execution of Specification of Output Channel for
Measured Data DARWIN
If the time before a reply is returned after executing specification of output channel for
measured data exceeds the builders send-receive interval monitoring time, a number of
retries equal to the number of retries set in the builder will be attempted.
If the communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a no-response error is returned for the
specification of output channel for measured data and further retries will be performed
from byte sequence specification.
ACM71 side
DARWIN side

Specification of
output channel
for measured data

Specification of
output channel
for measured data

Byte sequence
specification

Send-receive interval
monitoring time

Retries
J141104E.EPS

Figure No-Response Error after Execution of Specification of Output Channel for Measured
Data DARWIN

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.11 Error Handling when Communication Error Occurs DARWIN/DAQSTATION>

J14-40

Format Error after Execution of Specification of Output Channel for Measured Data DARWIN
If specification of output channel for measured data is executed but the reply is returned
in an unexpected frame format, a number of retries equal to the number of retries set in
the builder will be attempted.
If the communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a format error is returned for the
specification of output channel for measured data and further retries will be performed
from the next communication definition.
ACM71 side
DARWIN side

Specification of
output channel
for measured data

Specification of
output channel
for measured data
Reply
(?)

Reply
(?)

Retries
J141105E.EPS

Figure Format Error after Execution of Specification of Output Channel for Measured Data
DARWIN

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.11 Error Handling when Communication Error Occurs DARWIN/DAQSTATION>

J14-41

J14.11.2 Communication Errors when Communicating with

DAQSTATION
The following communication errors may occur during the communication with
DAQSTATION.

Error after Execution of Login Processing DAQSTATION

User Entry Request No-Response Error DAQSTATION
If the time it takes for the DAQSTATION side to return a user entry request after login
processing (normal connection processing) is executed and a reply stating that the connection has been established normally is returned exceeds the builders send-receive
interval monitoring time, a no-response error is returned for the user entry request. Next,
retry is performed from connection processing for the count equal to the number of retries
set in the builder.
This error occurs even if the communicating subsystem is a DARWIN model that does not
issue the request user entry.
ACM71 side

Login processing

Login processing
Send-receive interval
monitoring time

DAQSTATION side

Retries
J141106E.EPS

Figure User Entry Request No-Response Error DAQSTATION

User Entry Request Error DAQSTATION

A user entry request error occurs if a user name entry request other than E1 + error
code 402 is issued from DAQSTATION. Next, retry is performed from connection processing for the count equal to the number of retries set in the builder until the communication
recovers.
ACM71 side

Login
processing

DAQSTATION side

User name
entry
User name
entry request

Login
processing
Reply
(other than "E1"+402)

Recovery
communication time

User name
entry
User name
entry request

Reply

Retries
J141107E.EPS

Figure User Entry Request Error DAQSTATION

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.11 Error Handling when Communication Error Occurs DARWIN/DAQSTATION>

J14-42

Error after Execution of User Name Entry DAQSTATION

No-Response Error after Execution of User Name Entry DAQSTATION
If the time before a reply is returned after executing user name entry exceeds the builders
send-receive interval monitoring time, a number of retries equal to the number of retries
set in the builder will be attempted.
If the communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a no-response error is returned for the
user name entry and further retries will be performed until the communication recovers.
ACM71 side

User name entry

User name entry

Send-receive interval
monitoring time

DAQSTATION side

Retries
J141108E.EPS

Figure No-Response Error after Execution of User Name Entry DAQSTATION

Reply Error after Execution of User Name Entry DAQSTATION

If user name entry is executed but the reply is returned in error (E1+CR+LF), a number
of retries equal to the number of retries set in the builder will be attempted.
If the communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a reply error is returned for the user
name entry and further retries will be performed until the communication recovers.
ACM71 side
DAQSTATION side

User name entry

User name entry

Reply
("E1"+ERR+CR+LF)

Reply
("E1"+ERR+CR+LF)

Retries
J141109E.EPS

Figure Reply Error after Execution of User Name Entry DAQSTATION

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.11 Error Handling when Communication Error Occurs DARWIN/DAQSTATION>

J14-43

Error after Execution of Byte Sequence Specification DAQSTATION

No-Response Error after Execution of Byte Sequence Specification
DAQSTATION
If the time before a reply is returned after executing byte sequence specification exceeds
the builders send-receive interval monitoring time, a number of retries equal to the
number of retries set in the builder will be attempted.
If the communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a no-response error is returned for the
byte sequence specification and further retries will be performed until the communication
recovers.
ACM71 side

Byte sequence
specification

Byte sequence
specification
Send-receive interval
monitoring time

DAQSTATION side

Retries
J141110E.EPS

Figure No-Response Error after Execution of Byte Sequence Specification DAQSTATION

Reply Error after Execution of Byte Sequence Specification + Output Data

Selection
If byte sequence specification is executed but the reply is returned in error (E1+CR+LF),
a number of retries equal to the number of retries set in the builder will be attempted.
If the communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a reply error is returned for the byte
sequence specification and further retries will be performed until the communication
recovers.
ACM71 side
DAQSTATION side

Byte sequence
specification

Byte sequence
specification
Reply
("E1"+CR+LF)

Reply
("E1"+CR+LF)

Retries
J141111E.EPS

Figure Reply Error after Execution of Byte Sequence Specification DAQSTATION

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.11 Error Handling when Communication Error Occurs DARWIN/DAQSTATION>

J14-44

Format Error after Execution of Byte Sequence Specification

DAQSTATION
If byte sequence specification is executed but the reply is returned in an unexpected
frame format, a number of retries equal to the number of retries set in the builder will be
attempted.
If the communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries` a format error is returned for the byte
sequence specification and further retries will be performed until the communication
recovers.
ACM71 side

Byte sequence
specification

Byte sequence
specification
Reply
(?)

Reply
(?)

DAQSTATION side

Retries
J141112E.EPS

Figure Format Error after Execution of Byte Sequence Specification DAQSTATION

Error after Execution of Specification of Output Channel for Measured

Data DAQSTATION
No-Response Error after Execution of Specification of Output Channel for
Measured Data DAQSTATION
If the time before a reply is returned after executing specification of output channel for
measured data exceeds the builders send-receive interval monitoring time, a number of
retries equal to the number of retries set in the builder will be attempted.
If the communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a no-response error is returned for the
specification of output channel for measured data and further retries will be performed
from the byte sequence specification.
Specification of
output channel
for measured data

ACM71 side
DAQSTATION side

Specification of
output channel
for measured data

Byte sequence
specification

Send-receive interval
monitoring time

Retries
J141113E.EPS

Figure No-Response Error after Execution of Specification of Output Channel for Measured
Data DAQSTATION

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.11 Error Handling when Communication Error Occurs DARWIN/DAQSTATION>

J14-45

Format Error after Execution of Specification of Output Channel for Measured Data DAQSTATION
If specification of output channel for measured data is executed but the reply is returned
in an unexpected frame format, a number of retries equal to the number of retries set in
the builder will be attempted.
If the communication does not return to normal even after retries are repeated for the
number of times specified in the number of retries, a format error is returned for the
specification of output channel for measured data and further retries will be performed
from the next communication definition.
ACM71 side
DAQSTATION side

Specification of
output channel
for measured data

Specification of
output channel
for measured data
Reply
(?)

Reply
(?)

Retries
J141114E.EPS

Figure Format Error after Execution of Specification of Output Channel for Measured Data
DAQSTATION

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.12 Transmission Time between Communication Card and DARWIN/DAQSTATION>

J14-46

J14.12 Transmission Time between Communication

Card and DARWIN/DAQSTATION
This section explains the transmission time for communication between the communication card and a DARWIN/DAQSTATION.

Communication Performance
The transmission time for communication between the communication card and a
MELSEC-A is calculated as a sum of T1 through T4 as shown below.
Communication begins

Communication
card

Communication complete

Request
generation
processing

Data

DARWIN/
DAQSTATION

Data

Communication
processing
T1

T2

T3

T4

T1: Request generation time. Approximately 50 ms.

T2: Transmission time of request
T3: Response creation time (PLC CPU processing time)
T4: Transmission time of response
J141201E.EPS

Figure Time Chart for Communication between Communication Card and DARWIN/DAQSTATION

SEE ALSO
Refer to the DARWIN/DAQSTATION Users Manual for more information on T2 through T4.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J14.12 Transmission Time between Communication Card and DARWIN/DAQSTATION>

J14-47

Using this package to communicate with DARWIN/DAQSTATION in parallel to all the

DARWIN/DAQSTATION PLCs in sequence with their IP addresses. After processing a
request of one DARWIN/DAQSTATION, it starts to process the request of the next.
One transmission only handles one communication assignment on the builder. For an
example, assume there are two DARWIN/DAQSTATION PLCs, one has three communication assignments while the other has only one, transmissions are performed in the following
sequence. However, communication delay caused in DARWIN/DAQSTATION PLC is not
considered in this assumption.
Assignment 1
Assignment 4

Subsystem 1

Subsystem 2

Assignment 1

Assignment 4

Assignment 2
Assignment 3

Assignment 2
Repeat
Assignment 4
Assignment 3
Assignment 4

J141203E.EPS

Figure Transmission Sequence

Calculation Example
The following shows an example of calculating the transmission time when reading data of
60 registers of measured data.
The communication time is calculated based on the following conditions:
Comparing with other processing times, the transmission times of request (T2) and response (T4) are trivial, all together about 1 to 5 milliseconds. Thus in this calculation, T2 +
T4 = 5 ms.
The DARWIN/DAQSTATION CPUs scan time is 50 ms.
T1 = 50 ms

Transmission time of request (T2) + Transmission time of response (T4) = 5 ms

PLC CPU processing time (T3) = Number of points / Number of points processed in one
scan scan time
= 60 / 6050
= 50 ms

Total time = Ti = 50 + 5 + 50 = 105 (ms)

i=1

J141202E.EPS

TIP
Note that the calculation is approximate since the actual communication time may vary by a wide margin
depending on network traffic.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

Blank Page

<J15. SLC 500 Communication (ACM11)>

J15-1

J15. SLC 500 Communication (ACM11)

The SLC 500 communication package (ACM11) is a subsystem communication
package that is compatible with the SLC 500 family (hereinafter referred to as SLC
500) PCs manufactured by the Rockwell Automation, Inc. By using the SLC 500
communication package (ACM11), communications can be performed between an
FCS and a SLC 500 module without using a program. An asynchronous link layer
protocol is used for this package.
This chapter explains the communication between the PLC500 and FCS among the
subsystem communication packages.
SEE ALSO
For functions common to different subsystem communication packages, see the folowing:
J1, General Information Regarding to Subsystem Communication

Applicable Models SLC 500

The following SLC 500 communication packages (ACM11) are available.
PFS9056 CS 1000 SLC 500 communication package (ACM11)
LFS9056 CS 3000 SLC 500 communication package (ACM11)
The following SLC 500 models can be connected to ACM11:
SLC 500
SLC 5/01
SLC 5/02
SLC 5/03
SLC 5/04
The SLC 500 communication package (ACM11) performs subsystem communication
between the FCS and SLC 500 by connecting the following link modules manufactured by
the Rockwell Automation (hereinafter referred to as SLC 500 link modules) to the communication module (ACM11). An asynchronous link layer protocol is used for the subsystem
communication.
1785-KE
1770-KF2

IMPORTANT
Even though they have the same model name, there are some SLC 500 link modules that
do not use the asynchronous link layer protocol.

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J15.1 Communication Specifications SLC 500>

J15-2

J15.1 Communication Specifications SLC 500

This section explains the specifications when performing subsystem communication with the SLC 500.

Communication Capacity SLC 500

The capacity when performing subsystem communication with the SLC 500 are indicated
below.
Table Capacity of Communication between FCS and SLC 500
Item
Amount of data that can be
communicated by one
communication module
Number of subsystem stations
for which communication can be
handled by one communication
module
Communication size per
definition

Maximum number

Description

500 words
(1 word = 16 bits)

The maximum number of words that can

be accessed from a regulatory control
block or a sequence control block.

30 stations

Word device: 115 words

One definition corresponds to one

communication. It is equivalent to a limit
per SLC 500 protocol communication.
J150101E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J15-3

<J15.1 Communication Specifications SLC 500>

Transmission Specifications SLC 500

The table below lists the transmission specifications when performing subsystem communication with the SLC 500.
Table Transmission Specifications SLC 500
Item

Description

Interface

RS-232C (D-sub 25 pin)

Transmission method

Half-duplex

Synchronization method

Start-stop synchronized
communication

Baud rate (bps)

1200, 2400, [4800]

Transmission procedure

DF1 protocol

Transmission code

Binary
Start bit

Data format

Remark
ACM11

Data bit

Always specify 8 in the

Create New IOM dialog box
called up from the System
View.

Parity bit

None, [even]

(*1)

Always specify 1 in the

Create New IOM dialog box
called up from the System
View.

Stop bit

Enabled transmission
1000 ms
monitoring time
Time monitoring

Text frame

Monitoring time of
interval between
character reception

10 ms

Reception start
character

None

End character

None

RS control

None

(*1)

DR check

Yes

(*1)

CD check

None

(*1)

No-response time setting value

0 to 99 seconds [4 seconds]

(*1)

Communication retry

0 to 99 times [once]

(*1)

Interval of retries

0 to 999 seconds [30 seconds] (*1)

Item

Description

Remark
J150102E.EPS

Note: [ ] indicates the recommended settings.

*1:
This can be changed using the Property dialog box called on System View.

IMPORTANT
When performing subsystem communication with the SLC 500, be sure to specify [8
bits] for the data bit length. A communication error will occur if [7 bits] is specified.
When performing subsystem communication with the SLC 500, do not specify 19200
and 9600 bps for the baud rate.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.2 Connecting FCS and SLC 500>

J15-4

J15.2 Connecting FCS and SLC 500

This section explains the connection between FCS and SLC 500, and the connection
cables.

Connection Type SLC 500

An example of connection between FCS and SLC 500 is shown below:
HIS

Control bus

FCS

ACM11 (RS-232C communication module)

RDY
RCV
SND

CN1

RDY
RCV
SND

AMN33 (Nest for communication module)

CN1

MODEM

MODEM
RS-232C
1770-KF2

SLC 500
J150201E.EPS

Figure Example of SLC 500 Connection

Cable Connection when Using the ACM11 SLC 500

The following describes the cable connection when connecting the ACM11 and SLC 500.
A modem connection is required between the ACM11 and SLC 500 link module, but a
direct connection is possible if the length of the RS-232C cable between the ACM11 and
SLC 500 link module is 15 meters or less and the same grounding system is used for them.

IMPORTANT
The length of the RS-232C cable between the ACM11 and the modem as well as between
the modem and the SLC 500 module must each be 15 meters or less.
IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.2 Connecting FCS and SLC 500>

J15-5

The SLC 500 link module uses an RS-232C D-sub 25 pin connector. For this reason, a
cable with an RS-232C D-sub 25 pin connector is used when connecting a SLC 500 link
module and the ACM11.
Table RS-232C D-sub 25 Pin Connector Specifications SLC 500

Pin
Signal
number name

Name

FG

Frame ground

SD

Transmission data

RD

Reception data

RS

Transmission request

CS

Transmission enabled

DR

Data set ready

SG

Signal ground

CD

Reception carrier
detection

20

ER

Data terminal ready

Direction of signal
ACM11

SLC 500

Description
Safety grounding

This signal must be ON when

requesting a transmission.
The ACM11 cannot transmit data
to other stations when this signal
is OFF.
The ACM11 can only transmit
when this signal is ON, and it is
detected whether the target system
can send/receive data.

This signal must be ON when

communication is enabled.
J150202E.EPS

SEE ALSO
For details on safety grounding, see the folowings:
Figure Cable Connection between Modem and ACM11
Figure Cable Connection between SLC 500 and ACM11 (when connected directly)

Pin number 25

Pin number 14

Pin number 13

Pin number 1
J150203E.EPS

Figure Pin Assignment of the RS-232C D-sub 25 Pin Connector SLC 500

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.2 Connecting FCS and SLC 500>

J15-6

The following shows the cable connection when the SLC 500 and ACM11 module are
connected via modems and when they are connected directly without modem.

SD
RD
RS
CS
ACM11

20

20

DR
SG
CD
ER
FG

Shielded cable

SD
RD
RS
CS
DR

Modem (*1)

SG
CD
ER
FG

Protective grounding (100 ohm or less)

J150204E.EPS

*1:

As a rule, use a modem where FG and SG are connected.

Figure Cable Connection between Modem and ACM11

SD
RD
RS
CS
ACM11 DR
CD
ER
SG
FG

20

20

Shielded cable

SD
RD
RS
CS
DSR SLC 500
CD
DTR
SG
FG

Protective grounding (100 ohm or less)

J150205E.EPS

Figure Cable Connection between SLC 500 and ACM11 (when connected directly)

SEE ALSO
For details on connection cables, see the folowing:
A4.3, Wiring of Communication Module in Input & Output Modules (IM 33Y06K01-01E)
The cable connection differs by the type of SLC 500. See the users manual for the SLC 500 being connected regarding the cable connections for each type of SLC 500.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.2 Connecting FCS and SLC 500>

J15-7

With the ACM11, the RS-232C circuit and FG (frame ground) are electrically insulated. This
has the function of preventing intrusion of noise from the SLC 500 side and improving noise
resistance. Satisfy all conditions given below to make this function effective.
For the frame ground (FG), perform protective grounding (100 ohms or less) at the
opposing side of the connection (the modem or SLC 500 side).
Attach only one side of the shield of the sheathed cable to the FG of the opposing side
of the connection. Do not ground the cable shield on the ACM11 side. Also, do not use
a connector shell that is conductive.
Connect the FG and the SG (signal ground) of the RS-232C circuit at the opposing
side of the connection.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J15-8

<J15.3 Accessible Files SLC 500>

J15.3 Accessible Files SLC 500

SLC 500 internal data are stored as files. Internal data are generally called devices.
Only SLC 500 word files are accessible. A word file contains data represented by
words (1 word = 16 bits). In the case of SLC 500 modules, bit files are also accessed
in units of words, although data is represented by individual bits. It cannot access
files in units of bits.

Accessible Files SLC 500

The following files are accessible.
Table Accessible Files SLC 500
File type

Word
file

File name

File type
number

Address

Bit file

85

mmmnnn85

Timer file

86

mmmnnn86

Counter file

87

mmmnnn87

Control file

88

mmmnnn88

Integer file

89

mmmnnn89

Communication command
(CMD/FMC)
Read

Write

0F/A2

0F/AA

J150301E.EPS

*1:

Specify addresses using the format, mmmnnntt.

mmm is the file number.
nnn is the element number.

SEE ALSO
For details on file type numbers, element numbers, and data addresses, refer to the users manual for the
SLC 500 to be connected.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.4 Subsystem Data Storing Format SLC 500>

J15-9

J15.4 Subsystem Data Storing Format SLC 500

The following explains the format in which subsystem data acquired from the SLC
500 is stored in the FCS.
The storing formats for SLC 500 bit files and word files are given below:

Bit File SLC 500

Bit file data is stored in the communication I/O area, as shown below. If Reverse Bits is
enabled, the bit sequence in a word is reversed (and bits with the smaller numbers comprise the most significant byte).
16 bits
n n n n n n
+ + + + + +
15 14 13 12 11 10

n
+
9

n
+
8

n
+
7

n
+
6

n
+
5

n
+
4

n
+
31

n
+
3

n
+
2

n
+
1

m=1

n
+
16

m=2

n+16(m-1)

n+16(m-1)+15

J150401E.EPS

Figure Image of Stored Bit File SLC 500

Word File SLC 500

Word file data is stored in the communication I/O area, as shown below.
16 bits

Content of the nth register

Content of the n+1th register

Content of the n+m-1th register

J150402E.EPS

Figure Image of Stored Word File SLC 500

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.5 Setting Items on System View SLC 500>

J15-10

J15.5 Setting Items on System View SLC 500

SLC5

This section explains the items set on System View that are unique to SLC 500 and
their recommended values.
SEE ALSO
For the general description of setting items in the Set Details tab in the Create New IOM dialog box and
items set commonly for subsystems, see the folowing:
Setting Items for ACM11, ACM12 of J1.5.1, Overview of Setting Items on System View

The following items should be set when using SLC 500 modules. The setting is
performed via the Set Details tab of the Create New IOM dialog box called up from
System View.
Connection Device
Baud rate
Parity
Data Bits
Stop Bits
RS Control
DR Check
CD Check
Communication Error Process
Options
After creating the new I/O module, the settings can be modified on the I/O module
property sheet.

Connection Device SLC 500

Set [SLC5] as the type of the equipment (subsystem) connected.
Always perform this setting since the default is [FA-M3].

Baud Rate SLC 500

Specify the baud rate between the communication module and the SLC 500 module.
The recommended setting is [4800 bps].

IMPORTANT
Always set the proper speed; the default is [19200 bps] but SLC 500 modules cannot
transmit at 19200 bps.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.5 Setting Items on System View SLC 500>

J15-11

Parity SLC 500

This item sets the method for checking the parity of the subsystem data to be transmitted.
The recommended setting is [Even].
When using the SLC 500, [Odd] cannot be selected for the parity.

Data Bits SLC 500

This item sets the data bit length of the subsystem data to be transmitted.
When using the SLC 500, always select [8 bits] for the data bit length.

IMPORTANT
When using the SLC 500, a communication error will occur if [7 bits] is selected.

Stop Bits SLC 500

This item sets the stop bit of the subsystem data to be transmitted.
When using the SLC 500, always select [1 bit] for the stop bit.

IMPORTANT
When using SLC 500, [2 bits] cannot be set for the stop bit.

RS Control SLC 500

This item sets whether or not to perform RS control during subsystem data transmission.
When using the SLC 500, disable RS Control by leaving the [RS Control] checkbox unchecked.

DR Check SLC 500

This item sets whether or not to perform DR check during subsystem data transmission.
When using the SLC 500, enable DR Check by placing a check in the [DR Check]
checkbox.

CD Check SLC 500

This item sets whether or not to perform CD check during subsystem data transmission.
When using the SLC 500, disable CD Check by leaving the [CD Check] checkbox unchecked.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.5 Setting Items on System View SLC 500>

J15-12

Communication Error Process SLC 500

This item sets the parameters related to communication error handling during subsystem
data transmission.
The following three items must be set.
Response Timeout
This sets the time for detecting no response in the SLC500. The interval is set in units
of seconds.
The recommended setting is 4.
Number of Retries Upon Response Timeout
This item sets the number of retries performed in the event of a communication error.
The recommended setting is 1.
Interval of Connection Retries
This item sets the time interval for communicating to check whether the communication has returned to normal (recovery communication) with respect to the station that
generated a communication error. The interval is set in units of seconds.
The recommended setting is 30.

Options SLC 500

Set options for the communication parameters that vary with the subsystem. Options are
set by clicking on the Option button 1 through 4 in the Set Details tab of the Create New
IOM dialog box called from System View.
In the case of the SLC 500, define the station number of the SLC 500 link module at the
Option 1. The station numbers are set using an octal value.
For the Options 2 to 4, define 0.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.6 Setting Items on Communication I/O Builder SLC 500>

J15-13

J15.6 Setting Items on Communication I/O Builder

SLC 500
This section explains the items set in the Communication I/O Builder that are unique
to SLC 500 modules and their recommended values.
SEE ALSO
For an overview of the setting items with Communication I/O Builder and settings common to subsystems, see the folowing:
J1.5.2, Overview of Settings on Communication I/O Builder

The following items should be set when using SLC 500 modules.
Element
Buffer
Program name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

Element SLC 500

Element

With respect to the address of the subsystem data buffer, the element number is indicated
in the Communication I/O Builder. The element number is indicated for display purposes
only. It is not selectable.

Buffer SLC 500

Buffer

This item sets the buffer used by a program.

Always set the buffer size since this is a required setting item of Communication I/O
Builder.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.6 Setting Items on Communication I/O Builder SLC 500>

J15-14

Program Name SLC 500 : PFCS/SFCS

Program name

On the Communication I/O Builder, set the subsystem program name with unit number, slot
number, and SLC5 as a program name in the following format.
u-sProgramName
u
s
ProgramName

:
:
:

Unit number
Slot number
SLC5

Program Name SLC 500 : LFCS2/LFCS

Program name

Specify the subsystem program name with node number, unit number, slot number, and
SLC5 as program name in the following format.
n-u-sProgramName
n
u
s
ProgramName

:
:
:
:

Node number
Unit number
Slot number
SLC5

Size SLC 500

Size

This item sets the data size (data length) from the head address set in Device & Address.
Always set the size since this is a required setting item on Communication I/O Builder.
When using an SLC 500 module, the size should be set within the following setting range
and in units of words.
Word file: 1 to 115
SEE ALSO
For precautions when setting the size, see the folowing:
J1.5.2, Overview of Settings on Communication I/O Builder

Port SLC 500

Port

Port 1 is set for use.

IP Address SLC 500

IP Address

The IP Address is not required to be set.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.6 Setting Items on Communication I/O Builder SLC 500>

J15-15

Station SLC 500

Station

This sets the station number of the SLC 500 on the Data Highway or Data Highway Plus
that performs communication. The station numbers are set using an octal value.

Device & Address SLC 500

Device & Address

This sets the head address of SLC 500 data.

The addresses that can be set are shown below.
Bit file:

mmmnnn85

Timer file:

mmmnnn86

Counter file:

mmmnnn87

Control file:

mmmnnn88

Integer file:

mmmnnn89

mmm is the file number, and nnn is the element number.

SEE ALSO
For details on address setting, see the folowing:
J15.3, Accessible Files SLC 500

Data Type SLC 500

Data Type

This item sets the data type of subsystem data.

The data type can be selected from among the following.
Input (16-Bit Signed)
Input (32-Bit Signed)
Input (16-Bit Unsigned)
Input (32-Bit Unsigned)
Input (32-Bit Floating)
Output (16-Bit Signed)
Output (32-Bit Signed)
Output (16-Bit Unsigned)
Output (32-Bit Unsigned)
Output (32-Bit Floating)
Input (Discrete)
Output (Discrete)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.6 Setting Items on Communication I/O Builder SLC 500>

J15-16

Reverse SLC 500

Reverse

This sets whether or not to make the bit or word arrangement in the FCS in reverse order of
the subsystem data.
Any of the following can be selected for reverse:
Bits
No
Words
However, the bits setting is valid only if the data type is either the discrete input or discrete
output. In this case, the default is [Bits].
The words setting is valid only if the data type is the 32-bit analog input or the 32-bit analog
output. In this case, the default is [No].

Scan SLC 500

Scan

This item sets whether or not to use the function to read the analog communication I/O data
to the I/O data buffer at the beginning of each fast-scan of the FCS.

Service Comment SLC 500

Service Comment

This item sets the comment.

Label SLC 500

Label

The name of the function block I/O terminal can be set as a user-defined label name.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.7 System Alarm Messages Specific to SLC 500>

J15-17

J15.7 System Alarm Messages Specific to SLC 500

This section describes the error codes of system alarm messages specific to SLC
500.

System Alarm Message Sent when a Communication Error Occurs

SLC 500 : PFCS/SFCS
When a communication error occurs, the system alarm message as shown below is sent to
HIS.
STNss SS-COM Error UNITmm SLOTnn STNzzz CODE=####
STNss
mm
nn
zzz
####

:
:
:
:
:

FCS
Unit number
Slot number
Subsystem station number
Error code

The communication error message will be sent to HIS at the first time that the subsystem
communication becomes abnormal. After that, a new system alarm message will not be
sent even if an error is generated by a different cause.
SEE ALSO
For the error codes, see the folowing in this chapter:
Error Codes SLC 500

System Alarm Message Sent when a Communication Error Occurs

SLC 500 : LFCS2/LFCS
When a communication error occurs, the system alarm message as shown below is sent to
HIS.
STNss SS-COM Error RIO01 NODExx UNITmm SLOTnn STNzzz CODE=####
STNss
xx
mm
nn
zzz
####

:
:
:
:
:
:

FCS
Node number
Unit number
Slot number
Subsystem station number
Error code

The communication error message will be sent to HIS at the first time that the subsystem
communication becomes abnormal. After that, a new system alarm message will not be
sent even if an error is generated by a different cause.
SEE ALSO
For the error codes, see the folowing in this chapter:
Error Codes SLC 500

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.7 System Alarm Messages Specific to SLC 500>

J15-18

System Alarm Message Sent when Communication Returns to Normal

SLC 500 : PFCS/SFCS
When communication returns to normal status, the system alarm message indicated below
is sent to HIS.
STNss SS-COM Recover UNITmm SLOTnn STNzzz
STNss
mm
nn
zzz

:
:
:
:

FCS
Unit number
Slot number
Subsystem station number

System Alarm Message Sent when Communication Returns to Normal

SLC 500 : LFCS2/LFCS
When communication returns to normal status, the system alarm message indicated below
is sent to HIS.
STNss SS-COM Recover RIO01 NODExx UNITmm SLOTnn STNzzz
STNss
xx
mm
nn
zzz

:
:
:
:
:

FCS
Node number
Unit number
Slot number
Subsystem station number

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.7 System Alarm Messages Specific to SLC 500>

J15-19

Error Codes SLC 500

The table below shows the error codes specific to the SLC 500.
Table Error Codes SLC 500 (1/2)

Error code

Description

A391

Communication driver busy

A392

Communication line busy

A393

Communication line not ready

A394

Sending size is too large

A395

Use of communication port not declared

A397

Under run error

A398

Timeout between received characters

A399

Receive buffer overflow

A39A

Parity error in receive data

A39B

Receiving overrun error

A39C

Receiving framing error

A39D

No. of characters received is outside specifications

A39F

Other error

A3B0

No response

A3B1

Station number is out of range

A3B2

File type number is out of range

A3B3

Designated address is not correct.

A3B4

Designated address is not correct.

A3B5

File type number is out of range

A3B6

File number is out of range

A3B7

Element number is not a decimal number

A3B8

Element number is out of range

A3B9

Communication data size is out of range

A3BA

Incorrect address

A3BB

Size of received text is abnormal

A3BC

BCC error in received text

A3BD

TNS inconsistency in received text

A3BE

Size of received text is abnormal

A3BF

EOT received

A3C0

Received text abnormal

A3C1

Receives local STS error code 01 (No buffer space in destination node)

A3C2

Receives local STS error code 02

(No ACK returned from the designated destination node)

A3C3

Receives local STS error code 03 (detected identical token folder)

A3C4

Receives local STS error code 04 (local port is severed)

Error code

Description
J150701E.EPS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.7 System Alarm Messages Specific to SLC 500>

J15-20

Table Error Codes SLC 500 (2/2)

Error code

Description

A3D1

Receives local STS error code 10 (invalid command or invalid format)

A3D2

Receives local STS error code 20

(host computer contains error, communication failed)

A3D3

Receives local STS error code 30

(cannot find remote node, it might be severed or shutdown)

A3D4

Receives local STS error code 40

(host computer does not function properly due to hardware error)

A3D5

Receives local STS error code 50 (addressing or memory protection problem)

A3D6

Receives local STS error code 60

(command protected, the function cannot be completed)

A3D7

Receives local STS error code 70 (processor is in program mode)

A3D8

Receives local STS error code 80

(cannot find code exchange file or communication zone error)

A3D9

Receives local STS error code 90 (remote node cannot buffer the command)

A3DB

Receives local STS error code B0 (remote node error during downloading)

A3E1

Receives command 0F EXT STS error code 01 (block address conversion error)

A3E2

Receives command 0F EXT STS error code 02 (designated address is under range)

A3E3

Receives command 0F EXT STS error code 03 (designated address is over range)

A3E4

Receives command 0F EXT STS error code 04 (cannot find the symbol)

A3E5

Receives command 0F EXT STS error code 05 (incorrect symbol format)

A3E6

Receives command 0F EXT STS error code 06 (invalid address)

A3E7

Receives command 0F EXT STS error code 07 (file size abnormal)

A3E8

Receives command 0F EXT STS error code 08

(unable to fulfil the request, circumstances changed from the command starts)

A3E9

Receives command 0F EXT STS error code 09 (file size is too large)

A3EA

Receives command 0F EXT STS error code 0A

(transaction size is too large, address is over range)

A3EB

Receives command 0F EXT STS error code 0B (access denied, improper privilege)

A3EC

Receives command 0F EXT STS error code 0C

(failed to create conditions, cannot use the resources)

A3ED

Receives command 0F EXT STS error code 0D

(conditions established, resources are utilized)

A3EE

Receives command 0F EXT STS error code 0E (cannot shutdown)

A3EF

Receives command 0F EXT STS error code 0F

(requester does not have privilege to upload or download)

A3F0

Receives command 0F EXT STS error code 10 (histogram overflow)

A3F1

Receives command 0F EXT STS error code 11 (incorrect data type)

A3F2

Receives command 0F EXT STS error code 12 (parameter abnormal)

A3F3

Receives command 0F EXT STS error code 13

(address linked to the deleted data table exists)

Error code

Description
J150702E.EPS

SEE ALSO
For details on the contents of the errors, refer to the users manual for the SLC 500 being used.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J15-21

<J15.8 Transmission Time between Communication Module and SLC 500>

J15.8 Transmission Time between Communication

Module and SLC 500
The communication time between communication module and SLC 500 subsystem
is to be discussed in this section.

Communication Time SLC 500

The communication time between a communication module and an SLC 500 is calculated
as the total of the time of intervals T1 to T12 shown below. Normally, T5 to T8 are
repeated seven times during subsystem communication with the SLC 500. However, this
count may fluctuate.
Communication
module

Create transmission
message

ENQ

ENQ

*2

SLC 500
link module
EOT

ACK
T1

*1:
*2:
T1:
T2:
T3:
T4:
T5:
T6:
T7:
T8:
T9:
T10:
T11:
T12:

T2

T3

T4

T5

T6

T7

*1
T8

T6

T9 T10 T11 T12

Response message interpretation time + ACK processing time

SLC 500 response message processing time
Time required to create a transmission message. Approximately 10 ms
Time required to send a transmission message
SLC 500 ACK processing time and EOT processing time. Approximately 3 ms
Time required to send a response message
Communication module ENQ processing time. Approximately 5 ms
Time required to send communication module ENQ.
SLC 500 EOT processing time. Approximately 3 ms.
Time required to send SLC 500 EOT. Approximately 2 ms.
SLC 500 response message processing time. Approximately 3 ms
Time required to send a response message
Response message interpretation time + ACK processing time. Approximately 15 ms
Time required to send communication module ACK. Approximately 2 ms
J150801E.EPS

Figure Time Chart of Communication between Communication Module and SLC 500

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.8 Transmission Time between Communication Module and SLC 500>

J15-22

How to Calculate the Communication Time SLC 500

The request message transmission time (T2), communication module ENQ transmission
time (T6), SLC 500 link module EOT transmission time (T8), and the response message
transmission time (T4, T10) are calculated with the following formula.
Also, the communication module ENQ transfer time is figured as 4 bytes, while the SLC
500 link module EOT transfer time and the response message transfer time are figured as
2 bytes.

Transmission time (ms) Number of characters transmittednumber of bits per character1000

Baud rate (bps)
Number of bits
per character

Start
bit

Parity
Data


bit
bit

Stop
bit
J150802E.EPS

Start bit
Data bit
Parity bit
Stop bit
Baud rate

:
:
:
:
:

1 bit fixed
8 bits fixed (7 bits not possible)
None, even
1 bit fixed
1200, 2400, 4800 (bps)

Calculation Example for Communication Time SLC 500

When the output data type is set on Communication I/O Builder, the subsystem communication package reads data from the subsystem before it writes for that definition. Then the
package compares the data read from the subsystem with the FCS data and only writes
data of differing value to the subsystem.
Because of this, it is difficult to calculate the time required for communication when writing
data to a subsystem since the transmission time varies according to the number of data
items in which the value has changed. Therefore, use the following guidelines for communication time when writing to the subsystem.
When the values of most data items to be written remain unchanged
Communication time = The time required for transmission when reading data from the
subsystem with respect to all definitions where write has been designated
When the values of many data items to be written change
Communication time = About twice the amount of time required for transmission when
reading data from the subsystem with respect to all definitions where write has been
designated

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J15.8 Transmission Time between Communication Module and SLC 500>

J15-23

The following is an example of calculating the time required for communication between a
communication I/O module and the SLC 500:
Baud rate:

4800 bps

Number of characters per data:

Number of bits for one character: 11

Request frame (read):

31 bytes

PLC ACK, EOT:

2 bytes

ACM ENQ:

4 bytes

SLC response message:

64 data
Analog data 00700189 to 00706589
11264139 bytes

ACM ACK:

2 bytes

T2  31111000/4800  71.04 (ms)

T4, T8  2111000/4800  4.58 (ms)
T6  4111000/4800  9.2 (ms)
T10  139111000/4800  318.54 (ms)
Communication time  T1T2T3T47 (T5T6T7T8) T6T9T10T11T12
1071.0434.587 (59.232) 9.23318.54152
570.76 (ms)

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

Blank Page

<J16. PLC-5/SLC 500 Communication (ACM71)>

J16-1

J16. PLC-5/SLC 500 Communication (ACM71)

The PLC-5/SLC 500 communication package (ACM71) is a subsystem communication package that is compatible with the PLC-5 family (hereinafter referred to as PLC5) and the SLC 500 family (hereinafter referred to as SLC 500) PLCs manufactured by
the Rockwell Automation, Inc. By using the PLC-5/SLC 500 communication package
(ACM71), communications can be performed between an FCS and PLC-5/SLC 500
via Ethernet.
This communication package can be used on enhanced type PFCSs and SFCSs
only.
This chapter explains the communication between the PLC-5/SLC 500 and FCS
among the subsystem communication packages.
SEE ALSO
For functions common to different subsystem communication packages, see the folowing:
J1, General Information Regarding to Subsystem Communication

Applicable Models PLC-5/SLC 500

For the PLC-5/SLC 500 communication package, the following products are available:
PFS9074 CS 1000 PLC-5/SLC 500 communication package (ACM71)
LFS9074 CS 3000 PLC-5/SLC 500 communication package (ACM71)
When using the PLC-5/SLC 500 communication package (ACM71), the ACM71 (Ethernet
communication module) must be installed in an FCS and an Ethernet interface must be
installed on the PLC-5/SLC 500 module in order to perform communications.
The table below lists the modules compatible with the PLC-5/SLC 500 communication
package (ACM71) and the Ethernet interfaces used.
Table Applicable Models PLC-5/SLC 500

Type

Model name

Ethernet interface

PLC-5

PLC-5/20E, PLC-5/40E,
PLC-5/80E

Ethernet interface unit 10BASE-T, 10BASE-5,

10BASE-2 (Ethernet)

SLC 500

SLC 5/05 (*1)

Ethernet interface unit 10BASE-T (Ethernet)

J160001E.EPS

*1:

SLC 500, SLC 5/01, SLC 5/02, SLC 5/03, SLC 5/04 are not supported.

Operating Environment PLC-5/SLC 500

To run the PLC-5/SLC 500 communication package (ACM71), 500 Kbyte needs to be
assigned to the User C option area of the FCS used.

IMPORTANT
On Detailed Settings tab of FCS Constants Builder, the setting item SEBOL/User C Ratio
needs to be properly set in accordance with the communication program size.
If the default ratio 100 % is used, all resource is assigned for SEBOL and the communication program may fail when SEBOL program is running.
IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J16.1 Communication Specifications PLC-5/SLC 500>

J16-2

J16.1 Communication Specifications PLC-5/SLC 500

This section explains the specifications when performing subsystem communication with the PLC-5/SLC 500.

Ethernet Communication Specifications

The Ethernet communication specifications include the following:
Communication protocol: TCP/IP

PLC-5/SLC 500 Communication Specifications

The communication specifications specific to the PLC-5/SLC 500 are as follows.
Table PLC-5/SLC 500 Communication Specifications

Item

Description

Data code setting

Binary

Data transmission procedure

CSP protocol (*1)

Stations that can communicate Only stations connected to ACM71 (Access via the DH+ link, etc. is not allowed.)
J160101E.EPS

*1:

The CIP protocol is not supported.

Communication Capacity PLC-5/SLC 500

The communication capacity is as follows.
Number of PLC-5/SLC 500 modules that can communicate with one FCS:
5 models (*1)
*1: This capacity stands for the number of modules that one FCS can communicate with. It is irrelevant to the number
of ACM71 module.

The maximum size of data allowed for communication, including data communicated via
other communication packages used for the applicable FCS, is the size allowed in the
communication I/O data storage area (4000 words).

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J16.2 Connecting FCS and PLC-5/SLC 500>

J16-3

J16.2 Connecting FCS and PLC-5/SLC 500

The following explains the configuration of connections between an FCS and PLC-5/
SLC 500 modules.

Connection Configuration PLC-5/SLC 500

An example of connection between the FCS and PLC-5/SLC 500 is shown below.
Ethernet

HIS

HIS
Control bus

FCS

RDY
RCV
SND

CN1

RDY
RCV
SND

CN1

Ethernet
HUB

PLC-5

SLC 500
J160201E.EPS

Figure Example of Connection between FCS and PLC-5/SLC 500

Ethernet Interface on the PLC-5/SLC 500 Side PLC-5/SLC 500

The Ethernet interface of the ACM71 is 10BASE-T. If the Ethernet interface on the PLC-5
side is 10BASE-5 or 10BASE-2, the network should be configured using a hub or other
adapters.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J16-4

<J16.2 Connecting FCS and PLC-5/SLC 500>

Addressing
The IP address and subnet mask must be specified for each ACM71 installed in the FCS.
Up to three IP addresses and subnet masks are specified for a single FCS, including the IP
address and subnet mask specified for the control bus of the FCS.
These three IP addresses must have different subnets, respectively.
HIS
Subnet 1
(control bus)

172.16.1.24
(255.255.0.0)
172.16.1.1
(255.255.0.0)

Subnet 2

172.16.1.2
(255.255.0.0)

Subnet 3

172.21.1.1
(255.255.0.0)

RDY
RCV
SND

CN1

RDY
RCV
SND

CN1

172.22.1.1
(255.255.0.0)

FCS

Ethernet

PLC-5

Control bus

SLC 500

RDY
RCV
SND

CN1

RDY
RCV
SND

CN1

FCS

Ethernet

PLC-5
Router
Ethernet
SLC 500

Subnet 4
(router destination, etc.)
J160202E.EPS

Figure Addressing

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J16-5

<J16.3 Accessible Files PLC-5/SLC 500>

J16.3 Accessible Files PLC-5/SLC 500

This section describes accessible files when using PLC-5/SLC 500 modules.
PLC-5/SLC 500 internal data are stored as files. Internal data are generally called
devices. The PLC-5/SLC 500 files are bit device files and word device files, as indicated below.
Bit File
This refers to data where each bit has a meaning. An output image file is equivalent to a bit device file.
Word File
This refers to data where a word unit (1 word = 16 bits) contains the meaning.
An integer file is equivalent to a word device file.

Accessible Files and Basic Commands PLC-5

The table below lists the accessible files and basic commands of PLC-5.
Table Accessible Files PLC-5
File type

Bit file

File name

File format

Output image file

Address Communication command

File type
(CMD/FNC)
specification
number (*1)
for PLC-5 (*2)
Read
Write
0

O0:mmmm

Input image file

I1:mmmm

Status file

S2:mmmm

Bit file

B3:mmmm

Timer file

T4:mmmm

Counter file

C5:mmmm

Word file Control file

R6:mmmm

Integer file

N7:mmmm

Floating point file

F8:mmmm

0F/68

Not allowed

Remark
I/O area,
operation at
access is not
guaranteed.

0F/67

0F/68

0F/67

J160301E.EPS

*1:
*2:

The file type numbers 0, 1 and 2 are fixed. The values for file type numbers 3 to 8 can be changed in the range from 3
to 999.
Specify an address using the format, Xnnn:mmmm. Each address can consist of up to eight digits.
X is a file format.
nnn is the file type number. A 3-digit decimal number in the range of 0 to 999 can be set.
mmmm is the element number. A 4-digit decimal number in the range of 0 to 9999 can be set. 0 may be omitted.
If an element number is specified using four digits, the file type number should be specified using two digits.

SEE ALSO
Refer to the users manual of the applicable PLC-5/SLC 500 for more information on address specification.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J16.3 Accessible Files PLC-5/SLC 500>

J16-6

Accessible Files and Basic Commands SLC 500

The table below lists the accessible files and basic commands of SLC 500.
Table Accessible Files SLC500

Communication command
Address
(CMD/FNC)
specification
for SLC-500 (*2)
Read
Write

File name

File format

File type
number (*1)

Output image file

Input image file

Status file

S2:mmmm

Bit file

B3:mmmm

Timer file

T4:mmmm

Counter file

C5:mmmm

Word file Control file

R6:mmmm

Integer file

N7:mmmm

Floating point file

F8:mmmm

File type

Not allowed
Bit file

0F/68

0F/68

Remark

Cannot be
accessed directly
Not allowed from SLC 500
(*3).

0F/67

0F/67

J160301E.EPS

*1:
*2:

*3:

The file type number 2 is fixed. The values for file type numbers 3 to 8 can be changed in the range from 3 to 999.
Specify an address using the format, Xnnn:mmmm. Each address can consist of up to eight digits.
X is a file format.
nnn is the file type number. A 3-digit decimal number in the range of 0 to 999 can be set.
mmmm is the element number. A 4-digit decimal number in the range of 0 to 9999 can be set. 0 may be omitted.
If an element number is specified using four digits, the file type number should be specified using two digits.
It is not possible to read output image file O and input image file I of SLC 500 bit files directly. To read these files, first
copy them to bit file B on the SLC 500 side and then access bit file B.

SEE ALSO
Refer to the users manual of the applicable PLC-5/SLC 500 for more information on address specification.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J16.4 Subsystem Data Storing Format PLC-5/SLC 500>

J16-7

J16.4 Subsystem Data Storing Format PLC-5/SLC

500
The following explains the format in which subsystem data acquired from the PLC-5/
SLC 500 is stored in the FCS.
The storing formats for PLC-5/SLC 500 bit files and word files are given below:

Bit File PLC-5/SLC 500

Bit file data is stored in the communication I/O area, as shown below. If Reverse Bits is
enabled, the bit sequence in a word is reversed (and bits with the smaller numbers comprise the most significant byte). On the Communication I/O Builder, assign m for data size.
16 bits

%WWxxxx

n n n n n n
+ + + + + +
15 14 13 12 11 10

n
+
9

n
+
8

n
+
7

n
+
6

n
+
5

n
+
31

n
+
4

n
+
3

n
+
2

n
+
1

m=1

n
+
16

m=2

n+16(m-1)

n+16(m-1)+15

J160401E.EPS

Figure

Image of Stored Bit File PLC-5/SLC 500

Word File PLC-5/SLC 500

Word file data is stored in the communication I/O area, as shown below.
16 bits

%WWxxxx

Content of the nth register

Content of the n+1th register

Content of the n+m-1th register

J160402E.EPS

Figure Image of Stored Word File PLC-5/SLC 500

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J16.5 Setting Items on System View PLC-5/SLC 500>

J16-8

J16.5 Setting Items on System View PLC-5/SLC 500

PLC-5/SLC 500

This section explains the items set in System View that are unique to PLC-5/SLC 500
modules and their recommended values.
SEE ALSO
For the general description of the setting items in the Detailed Setting tab in the Create New IOM dialog
box and items set commonly for connected devices, see the folowing:
Setting Items for ACM71 in J1.5.1, Overview of Setting Items on System View

The following items should be set in the case of PLC-5/SLC 500.

FCS Properties
Detail Setting Tab of the Create New IOM Dialog Box
The IP address, subnet mask, attributes, destination address, router address
and hop count must be set.
Either one of the Detailed Setting tabs 2 to 5 of the Create New IOM dialog box
The name of the connected device, option 1 (no-response detection time),
option 2 (communication retry). Option 3 (interval of retries), and option 4 (port
number on the PLC-5/SLC 500 side) must be set.
After creating the new I/O module, the settings of Detailed Setting tab and
Detailed Setting tabs (2 to 5) can be modified on the I/O module property dialog
box.

FCS Properties PLC-5/SLC 500

Specify SLC5_E from the options in the Constant tab of the FCS properties.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J16.5 Setting Items on System View PLC-5/SLC 500>

J16-9

Create New IOM Dialog Box PLC-5/SLC 500

Perform the following settings in the Detailed Setting tab of the Create New IOM dialog box.
IP Address
Subnet Mask
Attribute
Destination Address
Router Address
Hop Count
SEE ALSO
For the general description of the setting items and setting contents, see the folowing:
Setting Items for ACM71 in J1.5.1, Overview of Setting Items on System View

Make the following setting using either one of Detailed Setting tabs 2 through 5 in the
Create New IOM dialog box. Select any one of the Detailed Setting tabs 2 to 5.

Connected Device Name

Specify SLC5_E as the connected device name.

Option 1
This item sets the time for detecting no response.

Option 2
This item sets the number of retries performed in the event of a communication error.

Option 3
This item sets the interval between communication recovery retries.

Option 4
The port number 2222 must be specified.
If 0 is specified, the system will operate in the same manner as when 2222 is specified.
This means that the port number for PLC-5/SLC 500 communication is automatically set to
2222.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J16.6 Setting Items on Communication I/O Builder PLC-5/SLC 500>

J16-10

J16.6 Setting Items on Communication I/O Builder

PLC-5/SLC 500
This section explains the setting items on Communication I/O Builder that are
unique to PLC-5/SLC 500 modules and their recommended values.
SEE ALSO
For an overview of the setting items on Communication I/O Builder and settings common to connected
devices, see the folowing:
J1.5.2, Overview of Settings on Communication I/O Builder

The following items should be set in the case of PLC-5/SLC 500 modules.
Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J16.6 Setting Items on Communication I/O Builder PLC-5/SLC 500>

J16-11

Element PLC-5/SLC 500

Element

With respect to the address of the subsystem data buffer, the element number is indicated
in the Communication I/O Builder. The element number is indicated for display purposes
only. It is not selectable.

Buffer PLC-5/SLC 500

Buffer

This item sets the buffer used by a program.

Always set the buffer size since this is a required setting item of the Communication I/O
Builder.

Program Name PLC-5/SLC 500

Program Name

Using the Communication I/O Builder, set the subsystem program name with unit number,
slot number and SLC5_E as a program name in the following format.
u-sProgramName
u
s
ProgramName

:
:
:

Unit number
Slot number
SLC5_E

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J16-12

<J16.6 Setting Items on Communication I/O Builder PLC-5/SLC 500>

Size PLC-5/SLC 500

Size

This item sets the data size (data length) from the head address set in Device & Address.
The setting is in word units.
The data size is set differently according to the type of data acquired, as listed in the following table.
Table Size PLC-5/SLC 500

File type

Bit file
(*1)

Maximum Assignment in Word

File name

Data structure in word

PLC-5

SLC 500

Output image file

12 (192 bits)

16 bits/1 word

Input image file

12 (192 bits)

16 bits/1 word

Status file

8 (128 bits)

8 (128 bits)

16 bits/1 word

Bit file

600 (600 data)

256 (256 data) 1 datum/16 bits (1 word)

Timer file

300 (100 data)

300 (100 data) 1 datum/3 words

Counter file

600 (200 data)

600 (200 data) 1 datum/3 words

600 (200 data)

600 (200 data)

600 (600 data)

256 (256 data) 1 datum/1 word

Word file
Counter file
(*2)
Integer file

Floating point file 600 (300 data)

1 datum/3 words

512 (256 data) 1 datum/2 words

J160601E.EPS

*1:

Bit file can be outlined as follows.

An element in output image file, input image file and status file represents a bit.
Status File

%WW000n

S2:000m+15

S2:000m

An element in bit file represents 16 bits.

%WW000n

B3:000m

%WW000n+1

B3:000m+1

%WW000n+2

B3:000m+2
J160604E.EPS

Figure Contents of Bit File PLC-5/SLC 500

*2:

Three words are used in order to access one data record in timer, counter, and control files. Two words are used in
order to access one data record in a floating point file. The contents of the timer/counter and control files are as follows:

Timer/Counter
%WW000n

Status bit

%WW000n+1

Setting value (.PRE)

%WW000n+2

Current value (.ACC)

Control
%WW000n

Status bit

%WW000n+1

Data length (.LEN)

%WW000n+2

Position (.POS)
J160602E.EPS

Figure Contents of Timer/Counter and Control Files PLC-5/SLC 500

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J16.6 Setting Items on Communication I/O Builder PLC-5/SLC 500>

J16-13

SEE ALSO
Refer to the users manual of the applicable PLC-5/SLC 500 for more information on data size.

Port PLC-5/SLC 500

Port

Port 1 is set for use.

IP Address PLC-5/SLC 500

IP Address

This item sets the IP address of the PLC-5/SLC 500.

Station PLC-5/SLC 500

Station

Station numbers are not used.

Device & Address PLC-5/SLC 500

Device & Address

This sets the head address of a file as listed in the table below.
Table Device & Address PLC-5/SLC 500
File type

Bit file

File name

Address
specification
for PLC-5

Address
specification
for SLC 500

Output image file

O0:mmmm

Input image file

I1:mmmm

Status file

S2:mmmm

S2:mmmm

Bit file

B3:mmmm

B3:mmmm

Timer file

T4:mmmm

T4:mmmm

Counter file

C5:mmmm

C5:mmmm

Word file Control file

R6:mmmm

R6:mmmm

Integer file

N7:mmmm

N7:mmmm

Floating point file

F8:mmmm

F8:mmmm
J160603E.EPS

Note : Specify an address using the format, Xnnn:mmmm. Each address can consist of up to eight digits.
X is a file format.
nnn is the file type number. A 3-digit decimal number in the range of 0 to 999 can be set. File type numbers 0 to 2
are fixed, but the values for file type numbers 3 to 8 can be changed in the range from 3 to 999.
mmmm is the element number. A 4-digit decimal number in the range of 0 to 9999 can be set. 0 may be omitted. If
an element number is specified using four digits, the file type number should be specified using two digits.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J16.6 Setting Items on Communication I/O Builder PLC-5/SLC 500>

J16-14

Data Type PLC-5/SLC 500

Data Type

This item sets the data type of subsystem data.

The data type can be selected from among the following:
Input (16-Bit Signed)
Input (32-Bit Signed)
Input (16-Bit Unsigned)
Input (32-Bit Unsigned)
Input (32-Bit Floating)
Output (16-Bit Signed)
Output (32-Bit Signed)
Output (16-Bit Unsigned)
Output (32-Bit Unsigned)
Output (32-Bit Floating)
Input (Discrete)
Output (Discrete)

Reverse PLC-5/SLC 500

Reverse

This item sets whether or not to make the bit or word arrangement in the FCS in reverse
order of the subsystem data.
Any of the following can be selected for reverse.
Bits
No
Words
However, the bits setting is valid only if the data type is either the discrete input or discrete
output. In this case, the default is [Bits].
The words setting is valid only if the data type is the 32-bit analog input or the 32-bit analog
output. In this case, the default is [No].

Scan PLC-5/SLC 500

Scan

This item sets whether or not to use the function to read the communication I/O analog data
to the I/O data buffer at the beginning of each fast-scan of the FCS.

Service Comment PLC-5/SLC 500

Service Comment

This item sets the comment.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J16.6 Setting Items on Communication I/O Builder PLC-5/SLC 500>

J16-15

Label PLC-5/SLC 500

Label

The name of the function block I/O terminal can be set as a user-defined label name.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J16.7 Setting on Subsystem PLC-5/SLC 500>

J16-16

J16.7 Setting on Subsystem PLC-5/SLC 500

It is necessary to set IP addresses, etc. for the Ethernet communication on the PLC5/SLC 500 side. However, it is not necessary to create a ladder program for communication on the PLC-5/SLC 500 side.
SEE ALSO
For details on the setting on the PLC-5/SLC 500 side, refer to the following manuals.
For PLC-5: RSLogix5 Programming for the PLC-500 Getting Reference Guide
For SLC 500: RSLogix500 Programming for the SLC500 and MicroLogix Families Reference Guide

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J16-17

<J16.8 System Alarm Messages Specific to PLC-5/SLC 500>

J16.8 System Alarm Messages Specific to PLC-5/SLC

500
This section describes the error codes of system alarm messages specific to PLC-5/
SLC 500.

Error Codes PLC-5/SLC 500

The table below shows the error codes specific to the PLC-5/SLC 500.
Table Error Codes PLC-5/SLC 500
Error code (hexadecimal)

Description

A3B0

No response

A3B1

CSP status error

A3B2

Illegal command or format

A3B3

Error on the PLC side

A3B4

PLC connection error

A3B5

PLC hardware error

A3B6

Address range error

A3B7

Command protect error

A3B8

The processor is in the program mode.

A3B9

Download error

A3BA

STS and other errors

A3C0

Error in EXT STS byte

A3C1

Data type parameter error

A3C2

Reception data size error

A3C3

New session error

A3C4

Send error

A3D1

Area definition error

A3D2

Port number error

A3D3

Card option data error

A3D4

File type error

A3D5

File number error

A3D6

A command element number is outside the allowed range.

A3D7

The number of communication processing points is exceeded.

A3D8

Data size structure error

A3D9

IP address error

A3DA

Station number error

A3DB

Error in the number of subsystems

A3DC

(Reserved)

A3DD

Address error

A3DE

(Reserved)
J160801E.EPS

SEE ALSO
For error codes pertaining to Ethernet communications, see the folowing:
J2.4, System Alarm Messages Specific to Ethernet Communication

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J16.9 Transmission Time between Communication Card and PLC-5/SLC 500>

J16-18

J16.9 Transmission Time between Communication

Card and PLC-5/SLC 500
The transmission time between a communication card and PLC-5/SLC 500 subsystem is to be discussed in this section.

Communication Performance
The transmission time between the communication card and PLC-5/SLC 500 is figured as
the total of the time T1 to T4 shown below.
Communication begins

Communication
card

Communication complete

Request
generation
processing

Data

PLC-5/SLC 500

Data

Response
processing
T1

T2

T3

T4

T1: Request generation time. 100 ms.

T2: Transmission time of request
T3: Response generation time (PLC CPU processing time)
T4: Transmission time of response
J160901E.EPS

Figure Time Chart of Communication between Communication Card and PLC-5/SLC 500

SEE ALSO
Refer to the users manual of the applicable PLC-5/SLC 500 for more information on T2 to T4.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J16.9 Transmission Time between Communication Card and PLC-5/SLC 500>

J16-19

Calculation Example
The following shows an example of calculating the transmission time when reading 100
data records of an integer (16-bit) file.
Calculation of the transmission time is based on the following conditions:
Comparing with other processing times, the transmission times of request (T2) and response (T4) are trivial, all together about 1 to 5 milliseconds. Thus in this calculation, T2 +
T4 = 5 ms.
PLC-5/SLC 500 scan interval:

100 ms

Transmission time of request (T2) + Transmission time of response (T4) = 5 ms

CPU processing time (T3) = 100 ms
4

Overall time  Ti  100 + 5 + 100  205 ms

i=1

J160902E.EPS

TIP
Note that the calculation is approximate since the actual communication time may vary by a wide margin
depending on network traffic.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

Blank Page

<J17. Modbus Communication (ACM71)>

J17-1

J17. Modbus Communication (ACM71)

The Modbus Communication Package (ACM71) is a subsystem communication
package compatible with Modicon Quantum and Premium PLCs made by Schneider
Electric. Hereinafter, Modicon Quantum and Premium subsystems will collectively
be referred to as Modbus/TCP PLCs. By using the Modbus Communication Package
(ACM71), it is possible to perform communication between an FCS and Modbus/TCP
PLCs without using any program.
Among several subsystem communication packages available, this chapter describes the package that allows communication between Modbus/TCP PLCs and an
FCS.
SEE ALSO
For further details regarding the functions common to different subsystem communication packages, see
the following:
J1, General Information Regarding to Subsystem Communication

Applicable Models Modbus

The following products of the Modbus Communication Package (ACM71) are available:
PFS2253 CS 1000 Modbus Communication Package (ACM71) (single type/dualredundant type)
LFS2253 CS 3000 Modbus Communication Package (ACM71) (single type/dualredundant type)
With the Modbus Communication Package (ACM71), an ACM71 (Ethernet communication
module) is installed in an FCS to allow communication with the Ethernet interface of a
Modbus/TCP PLC. The following models can use the two aforementioned products of the
Modbus Communication Package (ACM 71):
Modicon Quantum
Quantum I/O Scanner Module (140NOE77100)
Modicon Premium
Premium I/O Scanner Module (TSXETY410)

IM 33S01B30-01E

12th Edition : Mar.31,2005-00

<J17. Modbus Communication (ACM71)>

J17-2

Operating Environment Modbus

350 Kbytes of the user C/option area is required in the FCS to be used in order for the
Modbus Communication Package (ACM71) to run.

IMPORTANT
On Detailed Settings tab of FCS Constants Builder, the setting item SEBOL/User C Ratio
needs to be properly set in accordance with the communication program size.
If the default ratio 100% is used, all resource is assigned for SEBOL and the communication program may fail when SEBOL program is running.

SEE ALSO
For more information about dual-redundant configuration with Modbus Communication Package, see the
following:
J17.8, Dual-Redundant Communication Modbus

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J17.1 Communication Specifications Modbus>

J17-3

J17.1 Communication Specifications Modbus

This section describes the specifications for performing subsystem communication
with Modbus/TCP PLCs.

Ethernet Communication Specification Modbus

The Ethernet communication specification is as follows:
Communication protocol: TCP/IP

Modbus/TCP PLC Communication Specification

The communication specification specific to Modbus/TCP PLCs is listed in the table below.
Table Modbus/TCP PLC Communication Specification
Item

Description

Data encoding setting

Binary

Error control

N/A

Stations that can be

communicated with

Modbus/TCP PLC stations

J170101E.EPS

SEE ALSO
See OPEN Modbus/TCP SPECIFICATION Release 1.0 (March 29, 1999, Andy Swales, Schneider
Electric) for the protocol used by Modbus/TCP PLCs.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J17.1 Communication Specifications Modbus>

J17-4

Communication Capacity Modbus

The communication capacity is as follows:
Maximum number of Modbus/TCP PLCs that can be communicated: 5 (*1)
*1:

This capacity indicates the number of modules that a single FCS can communicate with. It is irrelevant to the number
of ACM71 modules installed.

The maximum amount of data allowed for communication, including data communicated
via other communication packages used for the applicable FCS, is the size of the communication I/O data buffer (4000 words).
The maximum number of definitions per ACM71 is 208; one definition is transmitted per
communication processing. The amount of data communicated per definition is as follows:
Word device (reading):

125 words

Word device (writing):

100 words

Bit device (reading):

125 words

Bit device (writing):

50 words

This is equivalent to the restrictions imposed on a single Modbus/TCP protocol communication.

Simultaneity of Communication Data Modbus

Modbus/TCP PLCs guarantee the simultaneity of communication data in 16-bit units.
Therefore, the simultaneity of data in 16-bit units is also guaranteed during communication
between an Ethernet communication module and a Modbus/TCP PLC.

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J17.2 Connecting FCS and Modbus/TCP PLC>

J17-5

J17.2 Connecting FCS and Modbus/TCP PLC

This section describes how FCSs and Modbus/TCP PLCs are connected.

Connection Type Modbus

The following figure shows an example of a connection between an FCS and two Modbus/
TCP PLCs.
Ethernet

HIS

HIS
Control bus

RDY
RCV
SND

CN1

RDY
RCV
SND

CN1

FCS
Ethernet

HUB

Modbus/TCP PLC

Modbus/TCP PLC
J170201E.EPS

Figure Example of Modbus/TCP PLC Connection

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

J17-6

<J17.2 Connecting FCS and Modbus/TCP PLC>

Addressing Modbus
An IP address and a subnet mask must be specified for each ACM71 that will be installed
in an FCS.
Up to three IP addresses and subnet masks can be assigned to a single FCS, since an IP
address and a subnet mask are also specified for the control bus of the FCS.
Note that these three IP addresses must be assigned to different subnets.
HIS
Subnet 1
(control bus)

172.16.1.24
(255.255.0.0)
172.16.1.1
(255.255.0.0)

Subnet 2

172.16.1.2
(255.255.0.0)

Subnet 3

172.21.1.1
(255.255.0.0)

RDY
RCV
SND

CN1

FCS

Ethernet

Modbus/TCP PLC

Control bus

Modbus/TCP PLC

RDY
RCV
SND

CN1

172.22.1.1
(255.255.0.0)

RDY
RCV
SND

CN1

RDY
RCV
SND

CN1

FCS

Ethernet

Modbus/TCP PLC
Router
Ethernet

Modbus/TCP PLC

Subnet 4
(downstream from router)
J170202E.EPS

Figure Addressing Modbus

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

<J17.3 Accessible Devices Modbus>

J17-7

J17.3 Accessible Devices Modbus

Internal data of a Modbus/TCP PLC is called devices. Devices consist of bit devices
and word devices as shown below.
Bit device
This term refers to data in which individual bit has meaning. An input relay is an
example of a bit device.
Word device
This term refers to data in which each sequence of bits arranged in word units
(1 word = 16 bits) has meaning. A holding register is an example of a word
device.
A Modbus/TCP PLC also has two devices called the special coil and communication
status.

Accessible Devices Modbus

Device & Address and Size must be specified by using Communication I/O Builder in
order to access devices. In the case of the Modbus/TCP PLC, the addresses have the
following structure:
<function code> + <device type> + <address of the device (*1)>
*1 :

The reference number set for the setting of [Device & Address] on the Communication I/O builder should be the zero
originated address of the subsystem (where the address starts from zero).

For the PLCs that compliant with IEC61131-3 such as Modicon Premium where the
address for communication starts from zero, the original address number should be
used.
(For example : For the input relay numbered %I0010, A10010 should be specified.)
For the PLCs such as Modicon Quantum, the address for communicating starts from
one, the original address number minus one should be used.
(For example : For the input relay numbered 10011, A10010 should be specified.)
TIP
In the Modbus communication package for ACM71 communication module, the Device &
Address parameter is based on the zero-originated address in the communication frame.
However, if the PLC address is based on the one-originated address, the setting for Device
& Address should be equal to this one-originated address minus one.
If you do not know where your PLC devices are zero-originated addressed or one-originated addressed, you need to query the vendor of the PLC.

For example, to define the input relays addressed 10012 to 10015 of Modicon Premium
PLC on the Communication I/O Builder. A10012 needs to be set for [Device & Address]
while 1 needs to be set for [Size]. Here, the A in A10012 stands for the function code, the
1 next to A stands for the device type and 0012 is the beginning of the reference numbers
of the devices.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

J17-8

<J17.3 Accessible Devices Modbus>

The following table lists the addresses and Modbus/TCP protocol function codes for the
accessible devices.
Table Bit Devices Modbus

Address
Device

Function
code

Device type
Address of
of
device within
Modbus/TCP PLC Modbus/TCP PLC

Modbus/TCP protocol
function code
(hexadecimal)
Read

A
0

05

XXXX (*1)

0F

Y
Input relay

0F

01

Coil

Write

XXXX (*1)

05

02

J170301E.EPS

*1 : For Modicon Premium PLC, XXXX stands for reference number.

Table Word Devices Modbus

Address
Device

Input register

Function
code
A
C

Device type
Address of
of
device within
Modbus/TCP PLC Modbus/TCP PLC
3

XXXX(*1)

Modbus/TCP protocol
function code
(hexadecimal)
Read

Write

04

10

B
C
Holding register

D
X

06

03
4

10
16 (*2)

XXXX(*1)

10

06

10

16 (*2)
J170302E.EPS

*1:
*2:

For Modicon Premium PLC, XXXX indicates a reference number.

Command 16 is not supported in Modicon Quantum/Premium PLCs.

Table Other Devices Modbus

Address
Device

Function
code

Device type
Address of
of
device within
Modbus/TCP PLC Modbus/TCP PLC

Modbus/TCP protocol
function code
(hexadecimal)
Read

Write

SP000

07 (*2)

Communication
status

STSXXX(*1)

Dual-redundant

ZACMWDPX

Special coil

J170303E.EPS

*1:
*2:

XXX indicates the station number of the Modbus/TCP PLC.

Command 07 is not supported in Modicon Premium PLCs.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.3 Accessible Devices Modbus>

J17-9

The meanings of the function codes are explained below.

A:
Read: Reads a data packet in the size designated by Communication I/O Builder in a
batch.
Write: Writes a data packet in the size designated by Communication I/O Builder in a
batch. With readback.
B:
Read: Reads a data packet in the size designated by Communication I/O Builder in a
batch.
Write: Writes to individual devices whose statuses have changed in 1-bit units in the
case of bit devices and 16-bit units in the case of word devices. With readback.
C:
Read: Reads a data packet in the size designated by Communication I/O Builder in a
batch.
Write: Writes to individual devices whose statuses have changed in 32-bit units. With
readback.
D:
Read: Reads a data packet in the size designated by Communication I/O Builder in a
batch.
Write: Writes to individual devices whose statuses have changed in 1-bit units. With
readback.
X:
Write: Writes a data packet in the size designated by Communication I/O Builder in a
batch upon the occurrence of a status change. No readback.
Y:
Write: Writes only to individual devices whose statuses have changed in the appropriate device units upon the occurrence of a status change. No readback.
Z:
Write: Writes only to individual devices whose statuses have changed in 32-bit units
upon the occurrence of a status change. No readback.
W:
Write: Writes only to individual devices whose statuses have changed in 1-bit units
upon the occurrence of a status change. No readback.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.3 Accessible Devices Modbus>

J17-10

Table List of Function Codes Modbus

Function code

Device

Read

Write

Readback

Bit device

The whole packet defined

in the builder

The whole packet defined

in the builder

Yes

Word device

The whole packet defined

in the builder

The whole packet defined

in the builder

Yes

Bit device

The whole packet defined

in the builder

In 1-bit units

Yes

Word device

The whole packet defined

in the builder

In 16-bit units

Word device

The whole packet defined

in the builder

In 32-bit units

Word device

The whole packet defined

in the builder

Yes
Yes

In 1-bit units

Yes

Bit device

The whole packet defined

in the builder

No

Word device

The whole packet defined

in the builder

No

Bit device

In 1-bit units

No

Word device

In 16-bit units

No

Word device

In 32-bit units

No

Word device

In 1-bit units

No

J170304E.EPS

TIP

Usually, the function codes A, B, C or D, which include readback, are used.

When a function code with readback is used, data is first read from the Modbus/TCP PLC side, and
the data read is then written to the appropriate FCS if the data type specified by Communication I/O
Builder is an input. If the data type specified is output, the data read is compared with the data stored
in the FCS. If the two sets of data are different, the data is transmitted to the Modbus/TCP PLC side.

When a function code without readback is used, the data stored in the FCS is compared with the data
held by the ACM71, and the data is transmitted to the Modbus/TCP PLC side only if a difference is
detected.

SEE ALSO
The function codes supported, accessible devices, and data sizes are all different depending on the type
of Modbus/TCP PLC. See the users manual of the Modbus/TCP PLC to be used for more information.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.4 Subsystem Data Storing Format Modbus>

J17-11

J17.4 Subsystem Data Storing Format Modbus

This section describes the formats in which subsystem data acquired from a
Modbus/TCP PLC are stored in an FCS.
The storing formats for Modbus/TCP PLC bit devices, word devices, special coil, and
communication status are explained in the following.

Bit Devices Modbus

When 16
m (m = 1, 2, ...) bit devices are read starting from address n, the Modbus/TCP
PLC data is stored in the FCS as shown below. Specify the data size as m by using Communication I/O Builder.
It is also possible to reverse the bit sequence in 16-bit units.
16 bits
n n n n n n
+ + + + + +
15 14 13 12 11 10

n
+
9

n
+
8

n
+
7

n
+
6

n
+
5

n
+
4

n
+
31

n
+
3

n
+
2

n
+
1

m=1

n
+
16

m=2
:
:
:
:
:

n + 16
(m - 1) + 15

n + 16
(m - 1)
J170401E.EPS

Figure Image of Stored Bit Devices Modbus

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

J17-12

<J17.4 Subsystem Data Storing Format Modbus>

Word Devices Modbus

When m word devices are read starting from address n, the Modbus/TCP PLC data is
stored in the FCS as shown below.
16 bits

Contents of the nth register

Contents of the n + 1th register

Contents of the n + m - 1th register

J170402E.EPS

Figure Image of Stored Word Devices Modbus

Special Coil Modbus

The data length of the Modbus PLC special coil is one word (16 bits). The subsystem data
for the special coil is stored in the FCS as shown below.
Whether nor not to reverse bits is designated by using Communication I/O Builder.
(a) When bit reverse is not specified
15

(b) When bit reverse is specified

n
+
7

n
+ n
1

15

n
n +
1

n
+
7

The value of n, where the status of special coil is stored,

depends on the type of connected Modbus/TCP PLC.
J170403E.EPS

Figure Image of Stored Special Coil Data Modbus

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.4 Subsystem Data Storing Format Modbus>

J17-13

Communication Status Modbus

The Modbus/TCP PLC's communication status STSnnn indicates the status of communication with each of the stations numbered from nnn to nnn+15.
The communication status is indicated as follows:
Stations defined by Communication I/O Builder that are communicating normally: 1
Stations defined by Communication I/O Builder that are faulty: 0
Stations that are not actually communicating (those not defined by Communication I/O
Builder): 1
The designation of the station number by Communication I/O Builder has no particular
significance in connection with the communication status; however, for convenience, set the
smallest station number among the stations that are actually communicating as the first bit.
The correspondence between bits and station numbers is shown below. The largest station
number corresponds to the smallest bit number.
Structure of STS001
15

00

Bit sequence

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16
Station
number
01

Station
number
16

Structure of STS017
15

00

Bit sequence

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
Station
number
17

Station
number
32
J170404E.EPS

Figure Correspondence between Communication Status Bits and Station Numbers Modbus

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.5 Setting Items on System View Modbus>

J17-14

J17.5 Setting Items on System View Modbus

MODBUS

This section describes the items that can be set in System View for Modbus/TCP
PLCs, including specific and recommended settings.
SEE ALSO
For an overview of the setting items in the Detailed Setting tab of the Create New IOM dialog box and the
settings common to different subsystems, see the following:
Setting Items for ACM71 in J1.5.1, Overview of Setting Items on System View

The following items must be set in order to use Modbus/TCP PLCs.

FCS Properties
Detailed Setting tab of the Create New IOM Dialog Box
The IP address, subnet mask, attributes, destination address, router address,
and hop count must be set.
Either one of the Detailed Setting tabs 2 to 5 of the Create New IOM dialog box
In any of the Detailed Setting tabs 2 through 5, the connected device name,
option 1 (no response detection time), option 2 (number of communication
retries upon error), option 3 (recovery communication time interval), and option
4 (port on Modbus/TCP PLC) settings must be set.
After creating a new I/O module, it is possible to change the settings in the Detailed
Setting tab and the Detailed Setting tabs 2 to 5 via IOM Properties.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.5 Setting Items on System View Modbus>

J17-15

FCS Properties Modbus

Select EMODBUS from the options in the Constant tab of the FCS Properties dialog box.

Create New IOM Dialog Box Modbus

Perform the following settings in the Detailed Setting tab of the Create New IOM dialog box.
IP Address
Subnet Mask
Attribute
Destination Address
Router Address
Hop Count
SEE ALSO
For the general description of the setting items and settings, see the following:
Setting Items for ACM71 in J1.5.1, Overview of Setting Items on System View

Set the following items in any of the Detailed Setting tabs 2 through 5 of the Create New
IOM dialog box. Select an appropriate tab from the Detailed Setting tabs 2 through 5.

Connected Device Name

Enter EMODBUS as the connection device name.

Option 1
This item sets the time for detecting a response timeout.

Option 2
This item sets the number of retries performed in the event of a communication error.

Option 3
This item sets the interval between communication recovery retries.

Option 4
Always set port number 502.
If 0 is specified, the system will operate in the same manner as if 502 were specified. In
other words, port number 502 will be set.
Since there is no default setting, be sure to enter the port number.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.6 Setting Items on Communication I/O Builder Modbus>

J17-16

J17.6 Setting Items on Communication I/O Builder

Modbus
This section describes the items that can be set by using Communication I/O Builder
for Modbus/TCP PLCs, including specific and recommended settings.
SEE ALSO
For an overview of the setting items using Communication I/O Builder and the settings common to
different subsystems, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

The following items must be set in order to use Modbus/TCP PLCs.

Element
Buffer
Program Name
Size
Port
IP Address
Station
Device & Address
Data Type
Reverse
Scan
Service Comment
Label

Element Modbus
Element

The element numbers of the addresses of the subsystem data buffer are displayed in
Communication I/O Builder. The element numbers are displayed for reference only; thus,
they cannot be set.

Buffer Modbus
Buffer

This item sets the buffer size used by a program.

In the case of the Modbus/TCP PLC, the setting range is from 1 to 1000.
Make sure to set the buffer size, as this is a required setting item of Communication I/O
Builder.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.6 Setting Items on Communication I/O Builder Modbus>

J17-17

Program Name MODBUS

Program Name

Enter the unit number, slot number, and EMODBUS as the program name in the field for
the program names of other devices using the following format:
u-sProgramName
u:
s:
ProgramName:

Unit number
Slot number
EMODBUS

Size Modbus
Size

This item sets the data size (data length) from the head address set in Device & Address.
Make sure to set the size, as it is a required setting item in Communication I/O Builder.
In the case of the Modbus/TCP PLC, the setting range is from 1 to 125 words; the size is
set in word units.
SEE ALSO
For a detailed description of the size, see the following:
J17.1, Communication Specifications Modbus
For precautions when setting the size, see the following:
J1.5.2, Overview of Settings on Communication I/O Builder

Port Modbus
Port

Set the port to 1.

IP Address Modbus
IP Address

This item sets the IP address of the Modbus/TCP PLC.

Station Modbus
Station

This item sets the station number of the Modbus/TCP PLC.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.6 Setting Items on Communication I/O Builder Modbus>

J17-18

Device & Address Modbus

Device & Address

This item sets the head address of the Modbus/TCP PLC data.
The following addresses can be set.
No address is set by default.
Coils:
Input relay:

A0xxxx, B0xxxx, X0xxxx, Y0xxxx

A1xxxx

Input registers:

A3xxxx, C3xxxx

Holding registers:

A4xxxx, B4xxxx, C4xxxx, D4xxxx, X4xxxx, Y4xxxx,

Z4xxxx, W4xxxx

Special coil:

SP000

Communication status:

STSxxx

Dual-redundant:

ZACMWDPX

xxxx is the address within the Modbus/TCP PLC device. The setting range is from 0 to
65535 (0H to FFFFH); it can be specified either as a decimal or hexadecimal number. If the
address is set as a hexadecimal number, suffix it with H.
Note that leading zeros of the xxxx part can be omitted. For example, coils A023, A0023,
and A00023 indicate the same address.
SEE ALSO
For a detailed description of the address specification, see the following:
J17.3, Accessible Devices Modbus
For more information about communication status, see the following:
J17.4, Subsystem Data Storing Format Modbus
For more information about dual-redundant configuration, see the following:
J17.8, Dual-Redundant Communication Modbus

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.6 Setting Items on Communication I/O Builder Modbus>

J17-19

Data Type Modbus

Data Type

This item sets the data type of the subsystem data.

The data type can be selected from the following:
Input (16-Bit Signed)
Input (32-Bit Signed)
Input (16-Bit Unsigned)
Input (32-Bit Unsigned)
Input (32-Bit Floating)
Output (16-Bit Signed)
Output (32-Bit Signed)
Output (16-Bit Unsigned)
Output (32-Bit Unsigned)
Output (32-Bit Floating)
Input (Discrete)
Output (Discrete)

Reverse Modbus
Reverse

This item specifies whether or not to reverse the bit or word sequences within the FCS and
in the subsystem data.
Any of the following options can be selected for the Reverse setting:
Bits
No
Words
Note that the Bits setting is only valid if the data type is either discrete input or discrete
output. In this case, the default setting is [Bits].
The Words setting is only valid if the data type is 32-bit analog input or 32-bit analog output.
In this case, the default setting is [No].

Scan Modbus
Scan

This item specifies whether or not to load the analog communication I/O data into the
communication I/O data buffer at the beginning of each high-speed scan of the FCS.

Service Comment Modbus

Service Comment

A comment can be entered in this item.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.6 Setting Items on Communication I/O Builder Modbus>

J17-20

Label Modbus
Label

The name of a function block I/O terminal can be set as a user-defined label name in this
item.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.7 Settings on Subsystem Modbus>

J17-21

J17.7 Settings on Subsystem Modbus

It is necessary to set IP addresses and other items for the Ethernet communication
on the Modbus/TCP PLC side. It is not necessary to create a ladder program for
communication on the Modbus/TCP PLC side, however.
SEE ALSO
See the users manual of the Modbus/TCP PLC to be connected for a detailed description of settings on
the Modbus/TCP PLC side.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.8 Dual-Redundant Communication Modbus>

J17-22

J17.8 Dual-Redundant Communication Modbus

This section explains the setting items and restrictions regarding to communication
with Modbus/TCP PLC subsystem in dual-redundant configuration using two
Ethernet communication modules.

Overview of Dual-Redundant Communication

Dual-redundant configuration consists of two ACM71 modules. The ACM71 in slot 1 takes
control right and the ACM71 in slot 2 stands by. When the ACM71 in slot 1 fails, the ACM71
in slot 2 takes over the control right. If the ACM71 in slot 1 recovers, it takes back the control
right and the ACM71 in slot 2 becomes standby again.
The ACM71 modules in slot 1 and slot 2 are reading data from subsystem PLC regardless
if the module is taking the control right or is standing by. However, only the module in control
status can write data to the subsystem PLC.

Dual-Redundant Configuration
A pair of Ethernet communication modules installed in a same FCS communication nest
can be put into dual-redundant configuration.

Installation of Ethernet Communication Modules

The dual-redundant configured Ethernet communication modules are supported in enhanced type PFCS and SFCS. Up to two (one pair) modules can be installed.

Settings on Communication I/O Builder

The dual-redundant configuration for the Ethernet modules in slot 1 and slot 2 must be
consistent. And the following settings need to be put in the first line or the last line in the
communication I/O builder of the modules in the slot 1 and slot 2.
Size:

Station:

Device & Address:

ZACMWDPX

Data Type:

Output (Discrete)

Reverse:

No

In the line of an element where ZACMWDPX is defined in the Device & Address column,
the data of the element have the following significances.
%WBxxxx16(*1) :

When this bit is 1, it indicates that the module is taking the

control right while if this bit is 0, the module is standby.

%WBxxxx15(*1) :

When this bit is 1, it indicates that the communication of

module functions properly while if this bit is 0, the commu
nication of the module malfunctions.

*1:

xxxx stand for the element number of the line that the dual-redundant configuration ZACMWDPX is defined.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.8 Dual-Redundant Communication Modbus>

J17-23

System Alarm Message

When the Ethernet communication modules are defined in dual-redundant configuration
and the control right is shifting from one module to the other, the following system alarm
message occurs.

In Service UNITmm SLOTnn

Out Service UNITxx SLOTyy
mm:
nn:
xx:
yy:

Unit Number (to control)

Slot Number (to control)
Unit Number (to standby)
Slot Number (to standby)

Restrictions on Dual-Redundant Communication

Restrictions when performing dual-redundant communication are indicated below:

Switching between Control Side and Stand-By Side

When switching from control side to stand-by side, the operations of subsystem reading
and writing and output to the common switches cannot be guaranteed to perform properly.
Specific items to be noted are listed below:
When data are written to the subsystem, hunting may occur if the value in analog
output or discrete output changes during switching.
When data are written to the communication module I/O image area from the regulatory control block, the data are refreshed at each FCS control period. However, with
some function blocks such as the sequence table blocks, the data are refreshed only
at the timings when write is performed. When writing data to the communication
module I/O image area from these blocks, one-shot execution should be avoided so
that the internal data will not be damaged by hunting or tracking.

During On-Line Maintenance

Dual-redundant communication is not guaranteed when downloading engineering data to
the modules during on-line maintenance.

High Speed Read

Both the modules paired in the dual-redundant configuration should have the same scan
period. If high speed read is required, both modules should be specified with high speed
read.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.8 Dual-Redundant Communication Modbus>

J17-24

Readback
For data writing to the subsystem, the option Perform readback is supported. The option
No readback is not supported. When readback is performed, data read from the Modbus/
TCP PLC are compared to the data in the FCS. If discrepancies exist, a write command is
sent to write the data from FCS to the subsystem.
When readback is not performed, data in the FCS and data in the communication module
are compared without reading from the Modbus/TCP PLC, and the data are written to the
Modbus/TCP PLC only when discrepancies are found.
Because the data in the standby side communication module is not refreshed while the
control side communication module is normal, the data in the communication module is still
old when it is switched from standby to control. In this case, the difference of the data in the
FCS and in the communication module cannot be found since they cannot be compared,
so data write are not performed if readback is not performed. Moreover, for Modbus communication, readback can be specified by the function code for the designated address
using the Communication I/O Builder.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.9 System Alarm Messages Specific to Modbus/TCP PLC>

J17-25

J17.9 System Alarm Messages Specific to Modbus/

TCP PLC
This section describes the error codes displayed in system alarm messages that are
specific to Modbus/TCP PLCs.

Error Codes Modbus

The table below lists the error codes specific to Modbus communication.
Table Error Codes Modbus (1/2)

Error code
(hexadecimal)

Description

A3B0

No response

A3B1

Station number is outside the range.

A3B2

Station number 0 cannot be set.

A3B3

Invalid address name

A3B4

Invalid address number

A3B5

Too many communication processing points

A3B6

A write operation to a read-only device was attempted.

A3B8

An odd number is used for a 4-byte register size.

A3B9

An option setting is outside the range.

A3BA

Cannot create communication frame

A3BB

Dual-redundant configuration error

A3BC

The IP address has not been set.

A3BD

The maximum number of connected subsystems is exceeded.

A3C1

Response message error (STN)

A3C2

Response message error (element)

A3C3

Response message error (function code)

A3C4

Response message error (data)

A3C5

Response message error (size of received data)

A3C6

Response message error (length of received text)

J170901E.EPS

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.9 System Alarm Messages Specific to Modbus/TCP PLC>

J17-26

Table Error Codes Modbus (2/2)

Error code
(hexadecimal)

Description

A3D1

Error code $01 received

A3D2

Error code $02 received

A3D3

Error code $03 received

A3D4

Error code $04 received

A3D5

Error code $05 received

A3D6

Error code $06 received

A3D7

Error code $07 received

A3D8

Error code $08 received

A3D9

Error code $09 received

A3DA

Error code $0A received

A3DB

Error code $0B received

A3DC

Error code $0C received

A3DD

Error code $0D received

A3DE

Error code $0E received

A3DF

Error code $0F received

A3E0

Error code $10 received

A3E1

Error code $11 received

A3E2

Error code $12 received

A3E3

Error code $13 received

A3E4

Error code $14 received

A3E5

Error code $15 received

A3E6

Error code $16 received

A3E7

Error code $17 received

A3E8

Error code $18 received

J170902E.EPS

SEE ALSO
For a detailed description of error codes pertaining to Ethernet communications, see the following:
J2.4, System Alarm Messages Specific to Ethernet Communication
See the users manual of the Modbus/TCP PLC to be connected for a detailed description of errors.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

J17-27

<J17.10 Transmission Time between Communication Card and ...>

J17.10 Transmission Time between Communication

Card and Modbus/TCP PLC
This section describes the time required for communication between a communication card and a Modbus/TCP PLC.

Communication Performance Modbus

The time required for communication between a communication card and a Modbus/TCP
PLC is calculated as the sum of the times T1 through T4 as shown below.
Communication start

Communication card

Communication end

Request
processing

Data

Modbus/TCP PLC

Data

Response
processing
T1

T2

T3

T4

T1: Request creation time, approximately 100 ms

T2: Transmission time of request
T3: Response creation time (PLC CPU processing time)
T4: Transmission time of response
J171001E.EPS

Figure Communication Timing Chart between a Communication Card and a Modbus/TCP PLC

SEE ALSO
See the users manual of the Modbus/TCP PLC for descriptions of T2 to T4.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00

<J17.10 Transmission Time between Communication Card and ...>

J17-28

Calculation Example Modbus

The following example shows how to calculate the communication time when reading 100
data records of an integer file.
The calculation of the communication time is based on the following conditions:
Comparing with other processing times, the transmission times of request (T2) and response (T4) are trivial, all together about 1 to 5 milliseconds. Thus in this calculation, T2 + T4
= 5 ms.
Modbus/TCP PLC scan cycle:

50 ms

Transmission time of request (T2) + Transmission time of response (T4) = 5 ms

CPU processing time (T3) = 50 ms
4

Overall time = Ti = 100  5  50 = 155 (ms)

i =1

J171002E.EPS

TIP
Note that the calculated communication time is approximate since the actual communication time may
vary significantly with the network traffic.

IM 33S01B30-01E

14th Edition : Dec.26,2006-00