1B30 11

Toc N-1
CS 1000/CS 3000
Reference
PROFIBUS
IM 33S01B30-01E 16th Edition
CONTENTS
PART-N
N1.
PROFIBUS
Overview of PROFIBUS ........................................................................ N1-1

N1.1
N2.
What is PROFIBUS? ..................................................................................... N1-2
PROFIBUS-DP (ACP71) ........................................................................ N2-1

N2.1
Overall Configuration ................................................................................... N2-2
N2.2
Operating Environment ................................................................................ N2-4
N2.3
PROFIBUS-DP Communication Module (ACP71) ....................................... N2-6
N2.4
I/O Data .......................................................................................................... N2-8
N2.5
Monitoring Slave Devices ........................................................................... N2-16
N2.6
N2.5.1
Assigning and Referencing a Slave Device ................................... N2-17
N2.5.2
Slave Diagnostic Information ........................................................ N2-19
Engineering ................................................................................................. N2-23

N2.6.1
Engineering Overview ................................................................... N2-24
N2.6.2
Operations with the PROFIBUS-DP Configurator ......................... N2-30
N2.6.3
Operations in System View ........................................................... N2-33
N2.6.4
Operations with the Communication I/O Builder ............................ N2-37
N2.6.5
Operations in Function Block Detail Builder .................................. N2-42
N2.7
Operation and Monitoring .......................................................................... N2-43
N2.8
Unusual Operations .................................................................................... N2-45
N2.9
N2.8.1
Start Operation ............................................................................. N2-46
N2.8.2
Actions in the Event of Faults ........................................................ N2-49
N2.8.3
Actions during Download .............................................................. N2-55
N2.8.4
Actions during Online Maintenance ............................................... N2-56
Messages .................................................................................................... N2-61

N2.9.1
System Alarm Messages .............................................................. N2-62
N2.9.2
Fieldbus Messages ....................................................................... N2-64
IM 33S01B30-01E 16th Edition : Dec.10,2007-00
Toc N-2
N3.
PROFIBUS-DP (ALP111) ....................................................................... N3-1

N3.1
Overall Configuration ................................................................................... N3-2
N3.2
Operating Environment ................................................................................ N3-5
N3.3
PROFIBUS-DPV1 Communication Module (ALP111) .................................. N3-7
N3.4
I/O Data .......................................................................................................... N3-9
N3.5
Monitoring and Diagnosing Devices ......................................................... N3-18
N3.6
N3.5.1
Overview of Slave Diagnostic Information ..................................... N3-19
N3.5.2
Assigning and Referencing Slave Diagnostic Information ............. N3-27
N3.5.3
Assigning and Referencing Device Specific Slave Diagnostic

Information ................................................................................... N3-29
N3.5.4
Assigning and Referencing Module Slave Diagnostic

Information ................................................................................... N3-31
N3.5.5
Assigning and Referencing Channel Slave Diagnostic

Information ................................................................................... N3-32
N3.5.6
Assigning and Referencing Device Communication Status ........... N3-35
Engineering ................................................................................................. N3-36

N3.6.1
Engineering Overview ................................................................... N3-37
N3.6.2
Operations with the PROFIBUS-DP Configurator ......................... N3-42
N3.6.3
Operations in System View ........................................................... N3-44
N3.6.4
Operations in Communication I/O Builder ..................................... N3-48
N3.6.5
Operations in Function Block Detail Builder .................................. N3-60
N3.7
Operation and Monitoring .......................................................................... N3-61
N3.8
Unusual Operations .................................................................................... N3-63
N3.9
N3.8.1
Actions in the Event of Faults ........................................................ N3-66
N3.8.2
Actions during Download .............................................................. N3-77
N3.8.3
Actions during Online Maintenance ............................................... N3-80
Messages .................................................................................................... N3-83

N3.9.1
System Alarm Messages .............................................................. N3-84
N3.9.2
Fieldbus Messages ....................................................................... N3-86
IM 33S01B30-01E
11th Edition : Oct.28,2004-00
<N1. Overview of PROFIBUS>
N1-1
N1. Overview of PROFIBUS

PROFIBUS is an open fieldbus standard that is widely used in Europe.
It was primarily created for use as a factory automation network, but has been
expanded for use in process automation, as well.
<N1.1 What is PROFIBUS?>
N1-2
N1.1 What is PROFIBUS?

PROFIBUS is a multimaster-type fieldbus for use with a system comprising master
and slave devices. Data can be transmitted to as many as 127 stations at desired
transmission speeds ranging between 9.6 Kbit/s and 12 Mbit/s. PROFIBUS uses a
twisted-pair cable (RS485) or fiber-optic cable as a transmission medium. Its overall
network distance can measure up to dozens of kilometers.
PROFIBUS products are divided into three different variations, each consisting of
compatible products, and can be used in a wide range of applications such as
controllers, devices and fieldbus networks.
The following describes the three types of variations:
PROFIBUS-DP
PROFIBUS-PA
PROFIBUS-FMS
PROFIBUS-DP
PROFIBUS-DP (Decentralized Periphery) allows high-speed data transmission between
controllers and slave devices such as remote I/Os and drives. PROFIBUS-DP can transmit
1 Kbyte of I/O data in less than 1 millisecond.
PROFIBUS-DPV1 with newly extended specifications is available as a type of PROFIBUSDP. The extended specifications of PROFIBUS-DPV1 encompass the dual-redundancy of
master devices and an alarm feature, among others.
PROFIBUS-PA
PROFIBUS-PA (Process Automation) employs function-block technology, offering the
physical-layer specifications designated by IEC1158-2 as an optional hazard-prevention
measure. PROFIBUS-PA uses a communication bus cable to power each node.
PROFIBUS-FMS
PROFIBUS-FMS (Fieldbus Message Specification) is an object-oriented model variation
that provides exceptional application performance for communications between intelligent
stations such as PLCs, DCSs and PCs.
TIP
The information contained in this section is excerpted from the Japan PROFIBUS Organizations website.
The Profibus interface provided by Yokogawa is in the category of PROFIBUS-DP. The

communication module ACP71 supports PROFIBUS-DP, and the FIO communication
module ALP111 supports PROFIBUS-DPV1 that offers extended specifications.
The PROFIBUS-DP communication is referred to as PROFIBUS-DP in explanations
related to the ACP71, and as PROFIBUS-DPV1 in explanations related to the ALP111
when applicable.
<N2. PROFIBUS-DP (ACP71) >
N2-1
N2. PROFIBUS-DP (ACP71)

This chapter explains communications between an ACP71 communication module
installed to an FCS and one or more slave devices that support PROFIBUS-DP, along
with the engineering tasks required. This chapter also explains those items that are
common with the PROFIBUS-DPV1 communication, which are implemented by the
ALP111, if any.
N2-2
<N2.1 Overall Configuration>
N2.1 Overall Configuration

I/O data communication with slave devices via PROFIBUS-DP is treated the same
way as communication with existing subsystems. In addition to linking subsystems,
PROFIBUS-DP allows the multidrop linking of various devices, including remote I/Os
and sensors.
This section explains the configuration and operating environment of communication function for a CS 1000/CS 3000 system and the PROFIBUS-DP interface using
ACP71 modules.
Configuration of Communication with PROFIBUS-DP

The figure below shows the overall configuration of communication using PROFIBUS-DP.
System builders, Operation and Monitoring, PROFIBUS-DP communication, and the
PROFIBUS-DP communication module (ACP71) are included in the communication
configuration with PROFIBUS-DP.
Export
PROFIBUS
definition
data file
PROFIBUS-DP
configurator
(manufactured by Hilscher)
Copy
Operation and Monitoring
System builders
Communication
I/O Builder
System
View
FCS Status
Display window
Function Block
Detail Builder
System
Alarm
window
Historical
Message
Report window
Control bus
FCS
ACP71
operating
status
Download
ACP71
Fail/Recover
message
Slave device
diagnostic
information
PROFIBUS-DP
communication
I/O data
PROFIBUS-DP
communication module (ACP71)
PROFIBUS-DP
I/O data
Slave device
Slave device
N020101E.EPS
Figure Overall Configuration of Communication with PROFIBUS-DP
N2-3
PROFIBUS-DP Communication Module (ACP71)

Communicates with slave devices and exchanges sent/received I/O data with PROFIBUSDP Communication function via the BN bus.
Operates as a master device (Class 1) on PROFIBUS-DP.
Acquires diagnostic information of PROFIBUS-DP, sends out fieldbus messages, and
maps them to the data status.
PROFIBUS-DP Communication
Exchanges I/O data with an ACP71 and stores the results in the communication I/O datastorage area. Accordingly, as with the communication I/O module, this function connects to
the function block using Communicaion I/O.
When a request is received from an HIS to acquire the operating status of an ACP71, the
status of the ACP71 is monitored and a message is transmitted upon detection of a fail/
recover.
PROFIBUS-DP Configurator (Product of Hilscher Co.)

Configures ACP71 and slave devices for PROFIBUS-DP communication, and exports the
configuration results.
Debugs PROFIBUS-DP communication through the ACP71.
System Builders
The following engineering functions are provided.
Copies the PROFIBUS definition data file of the PROFIBUS-DP configurator to an
internal folder.
Defines settings relating to an ACP71 from the Communication I/O Builder and downloads communication I/O definitions to an FCS and ACP71.
Download data to the ACP71 from System View using IOM download.
Defines function-block output conversions from Function Block Detail Builder.

The following operations are available via operation and monitoring console.
Downloads data to an ACP71 from the FCS Status Display window using IOM load,
and displays the operating status of the ACP71.
Checking fail/recover messages of an ACP71 from the System Alarm window.
Checking diagnostic reports of slave devices from the Historical Message Report
window.
<N2.2 Operating Environment>
N2-4
N2.2 Operating Environment

This section explains the operating environment for performing communication with
PROFIBUS-DP.
Operating Environment for Communication with PROFIBUS-DP

The following explains the operating environment, including hardware and software.
Hardware Environment
The following hardware environment is required for communication with PROFIBUS-DP.
Table Hardware Operating Environment
Type
Hardware
Communication module
ACP71
Nest
AMN52
Remarks
Nest for communication module (for PROFIBUS)
N020201E.EPS
Note: Can only be applied to enhanced type PFCS.

Can only be applied to SFCS and enhanced type PFCS.
The following hardware is also required for communication. Use hardware that conforms to
the PROFIBUS-DP specifications.
Table Devices Required for Communication with PROFIBUS-DP
Type
Description
Slave device
Without repeaters: Maximum of 31 units/ACP71 (*1)

With repeaters:
Maximum of 124 units/ACP71
Repeater
A device that connects multiple PROFIBUS-DP segments.
Terminator
This prevents electrical signal reflections. A terminator is required at both

ends of a communication cable.
T-shape connector
This is used to connect an ACP71 to PROFIBUS-DP.

N020202E.EPS
*1:
A single PROFIBUS-DP segment can be connected to a maximum of 32 master (ACP71) and slave devices. Accordingly, a maximum of 31 slave devices can be connected when no repeaters are used. The use of repeaters allows the
connection of up to four segments.
IM 33S01B30-01E
12th Edition : Mar.31,2005-00
N2-5
Software Environment
The following optional packages are required for communication with PROFIBUS-DP.
PFS2540 PROFIBUS Communication Package (*1)
LFS2540 PROFIBUS Communication Package (*2)
*1:
*2:
Package for the CS 1000.

Package for the CS 3000.
A third-party configurator is required for PROFIBUS-DP engineering.

System Configurator Version 2.818 and the later versions (Product of Hilscher Co.)
(*1)
*1:
The operating system includes Windows 95, Windows 98, Windows NT, Windows 2000, or Windows XP is required.
SEE ALSO
For more information about the operation environment, see the users manual of Hilscher Co. for system
configurator.
TIP
To define slave devices with the PROFIBUS-DP configurator, a file (GSD file) that defines the slave
device specifications and setting data is required.
A GSD file is either supplied by the device manufacturer or can be downloaded from the PROFIBUS
Organizations website.
IMPORTANT
In Windows 2000 or Windows XP environment, to permit the users that do not have Administrator privilege to use PROFIBUS-DP Configurator, the following operations may be
required.
Add the user for running the PROFIBUS-DP Configurator to the permission user list for the
folder and all subfolders and add the Full Control permission to the user for the folder that
the PROFIBUS-DP configurator is installed. By default, the PROFIBUS-DP configurator
files are installed under the following folder.
C:\Program Files\Yokogawa\SyCon
<N2.3 PROFIBUS-DP Communication Module (ACP71)>
N2-6
N2.3 PROFIBUS-DP Communication Module (ACP71)

The PROFIBUS-DP communication module (ACP71) is required for communication
with the PROFIBUS-DP.
This section explains the following items with respect to the PROFIBUS-DP communication module (ACP71).
Number of modules that can be mounted
Nest configuration
Size of data that can be communicated
Number of assignable communication I/O definitions
Connection of multiple ACP71s to the same bus
Mounting Format
A maximum of four ACP71s can be mounted per one FCS by using a PROFIBUS communication module nest (AMN52). (*1) (*2)
*1:
*2:
Can only be applied to enhanced type PFCS.

Can only be applied to SFCS and enhanced type PFCS.
Nest Configuration
The following explains the nest configuration when an ACP71 is mounted.
The ACP71 is mounted in nest 1.
Nest 2 will not be used.
Neither ACM21, ACM22 nor ACM71 can be mounted.
IMPORTANT
No other IOMs can be mounted in nest 1.
Nest 1
(AMN52)
Nest 3
CPU
Nest 4
Nest 5
N020301E.EPS
Figure Nest Configuration
IM 33S01B30-01E
12th Edition : Mar.31,2005-00
<N2.3 PROFIBUS-DP Communication Module (ACP71)>
N2-7
Size of Data that can be Communicated

The following indicates the size of data that can be communicated by an ACP71.
A maximum of 512 bytes of inputs
A maximum of 512 bytes of outputs
Number of Assignable Communication I/O Definitions

The following indicates the number of communication I/O definitions that can be assigned
to an ACP71.
A maximum of 200 definitions
Connecting Multiple ACP71s to the Same Bus

Multiple ACP71s can be connected to the same bus.
In this case, each ACP71 operates as an individual master during communication.
However, since the communication destinations slave device for an ACP71 is specified
when a PROFIBUS network is configured with the PROFIBUS-DP configurator, you cannot
reference or make settings for a slave device with which another ACP71 is set to communicate.
The cycle for communicating with PROFIBUS-DP is the sum of the cycles in which individual ACP71s communicate with a single slave device.
FCS
Range of I/O data communication

by single ACP71
ACP ACP
71 71
PROFIBUS-DP
Slave device
Slave device
Slave device
Slave device
N020302E.EPS
Figure Connecting Multiple ACP71s to the Same Bus
The system does not support the connection of a master device (PLC or PC) made by
another manufacturer to the same bus. Do not use the ALP111 together with the ACP71 on
the same bus.
<N2.4 I/O Data>
N2-8
N2.4 I/O Data

I/O data resulting from communication via an ACP71 is accessed from a function
block or Graphic window through the communication I/O data area.
This section explains the following items relating to I/O data:
How I/O data is stored to the communication I/O data area
Treating I/O data as analog I/O data
Treating I/O data as discrete I/O data
Reverse bits
Reverse bytes
Data status
Data update timing
I/O conversion with function block
Access using SEBOL
How I/O Data is Stored to the Communication I/O Data Area

With the PROFIBUS-DP configurator, 8-bit data is stored continually for its entire size
portion to the communication I/O data area (%WW: in increments of 16 bits).
However, when the data size indicated by the PROFIBUS-DP configurator is an odd-size
byte, the terminating byte data is filled in the upper byte and then stored. At this time, the
lower byte value becomes undefined.
Word data is handled in the same way as in subsystem communications.
%WB bit number
Communication I/O data area

01
08, 09
16
%WW0101
%WW0102
%WW0103
Data (first byte)
Data (second byte)
Data (third byte)
Data (fourth byte)
Data (fifth byte)
Free area
Value in the free area is undefined
N020401E.EPS
Figure Storing to the I/O Data Area
<N2.4 I/O Data>
N2-9
Treating I/O Data as Analog I/O Data

Data stored in the communication I/O data area is treated the same way as in subsystem
communication. To treat data as analog I/O data, designate a 16-bit or greater data type
such as input data (16-Bit Signed) in the Communication I/O Builder. When the data size
indicated by the PROFIBUS-DP configurator is an odd byte, the terminating byte data can
be stored in the communication I/O data area. However, the value cannot be guaranteed.
To treat every 8 bits of I/O data as analog I/O data, add ;E (expand 8-bit data to 16-bit
data) to the Device & Address on Communication I/O Builder. I/O data will be expanded to
16 bits and stored in the communication I/O data area.
%WB bit number

01
08, 09
16
%WW0101
Data (first byte)
%WW0102
Data (second byte)
%WW0103
Data (third byte)
N020402E.EPS
Figure Example of Expanding I/O Data to 16 Bits
The following lists the data types that can be designated with the Communication I/O
Builder at this time.
Input (16-Bit Signed)
Input (16-Bit Unsigned)
Output (16-Bit Signed)
Output (16-Bit Unsigned)
When outputting a value outside the data type range, it will be rounded off to the nearest
value within the data type range.
Table Rounding off Output Data
Data type
Output (16-Bit Signed)
Output (16-Bit Unsigned)
Before round-off
After round-off
Less than -127
-127
More than 128
128
More than 255
255
N020403E.EPS
Treating I/O Data as Discrete I/O Data

When I/O data is treated as discrete I/O data, data stored in the communication I/O data
area is treated the same way as in subsystem communication.
<N2.4 I/O Data>
N2-10
Reverse Bits
When I/O data is assigned as discrete I/O data and Reverse bits is designated, the bit
arrangement is reversed in increments of 16 bits, as is the case with subsystem communication.
Termination of data indicated as an odd byte size by the PROFIBUS-DP configurator is
reversed in increments of 8 bits, as shown below.
Slave device bit arrange
7
Communication
I/O data area
Free area
Data (first byte)

01
08, 09
% WB bit number
16
%WW0101
N020404E.EPS
Figure Reverse Bits
Reverse Bytes
Depending on the slave device, the byte positions of the upper byte and lower byte of
digital data may be reversed. In this case, assign I/O data as discrete I/O data and specify
reverse bytes. Specify this according to the specifications of the slave device used. The
specific byte mapping is shown below.
Mapping of Reverse Bits and Bytes

The layout of channel numbers for digital data varies depending on the specifications of the
slave device used. Make the following settings in Communication I/O Builder according to
the layout pattern of the channel numbers.
Table Layout Patterns of Channel Numbers and Specification in Communication I/O Builder
Pattern
Reverse bits
Reverse bytes
Remarks
Yes
No
Default: IS1 made by STAHL corresponds to this pattern.
Yes
Yes
VOS200 made by STAHL corresponds to this pattern.
No
No
No
Yes
Under normal circumstances, there is no slave device that

uses this pattern.
N020407E.EPS
<N2.4 I/O Data>
N2-11
Pattern 1
Upper-byte (first byte)
Channel number 7
(bit number)
Lower-byte (second byte)
15 14 13 12 11 10 9
x

x

x

x

x

x

x
Input/Output 1
Input/Output 2
Input/Output 3
Input/Output 4
Input/Output 5
Input/Output 6
Input/Output 7
Input/Output 8
Input/Output 9
Input/Output 10
Input/Output 11
Input/Output 12
Input/Output 13
Input/Output 14
Input/Output 15
Input/Output 16
N020408E.EPS
Figure Mapping with Reverse Bits, but without Reverse Bytes
Pattern 2
Channel number 15 14 13 12 11 10 9
(bit number)
x

x

x


6
5 4 3 2 1
0
Input/Output 1
Input/Output 2
Input/Output 3
Input/Output 4
Input/Output 5
Input/Output 6
Input/Output 7
Input/Output 8
Input/Output 9
Input/Output 10
Input/Output 11
Input/Output 12
Input/Output 13
Input/Output 14
Input/Output 15
Input/Output 16
N020409E.EPS
Figure Mapping with Reverse Bits as well as Reverse Bytes
<N2.4 I/O Data>
N2-12
Pattern 3
Channel number
(bit number)
x
x
10 11 12 13 14 15
Input/Output 1
Input/Output 2
Input/Output 3
Input/Output 4
Input/Output 5
Input/Output 6
Input/Output 7
Input/Output 8
Input/Output 9
Input/Output 10
Input/Output 11
Input/Output 12
Input/Output 13
Input/Output 14
Input/Output 15
Input/Output 16
N020410E.EPS
Figure Mapping without Reverse Bits or Reverse Bytes
Pattern 4
Channel number 8
(bit number)

10 11 12 13 14 15 0
x
x

1
2 3 4 5 6
7
Input/Output 1
Input/Output 2
Input/Output 3
Input/Output 4
Input/Output 5
Input/Output 6
Input/Output 7
Input/Output 8
Input/Output 9
Input/Output 10
Input/Output 11
Input/Output 12
Input/Output 13
Input/Output 14
Input/Output 15
Input/Output 16
N020411E.EPS
Figure Mapping without Reverse Bits, but with Reverse Bytes
<N2.4 I/O Data>
N2-13
Data Status
The data status for PROFIBUS-DP communication is the same as subsystem communication. The table below shows the data status:
Table Data Status
Data Status
Meaning
BAD
Invalid data value
NRDY
Indicates a temporary status in which data could not be acquired due to a

momentary power failure, power recovery, etc.
LPFL
Indicates the occurrence of a communication module error or a communication

error with a connected device.
NR (*1)
Data has been acquired normally.

N020405E.EPS
*1:
There is no actual NR data status, but this status is used only to indicate the absence of any of the other conditions
(BAD, NRDY or LPFL).
SEE ALSO
The data status is determined by the communication status and slave diagnostic information of a slave
device. For slave diagnostic information, see the following:
N2.5.2, Slave Diagnostic Information
Data Update Timing

Communication I/O data is refreshed based on the timing of a basic scan or high-speed
scan. Data update timing can be set in the item [Scan] on Communication I/O Module
builder.
<N2.4 I/O Data>
N2-14
I/O Conversion Using a Function Block

Element
Analog input
As with the analog input module, data from PROFIBUS can be treated as an analog input
signal by designating I/O data in the %WWnnnn (*1) format and assigning it to the input
terminal of the regulatory control block or calculation block.
*1:
nnnn is a number within the area.

nnnn:
1 to 4000
SEE ALSO
Analog inputs are treated the same way as in subsystem communication. For detailed information, see
the following:
J1.3, Accessing Subsystem Data from a Function Block
Analog Output
I/O data can be assigned to a function block as analog output (output terminal) by designating the data in the %WWnnnn (*1) format. Set the function blocks output-signal conversion
designation to Communication output (fully-open/tightly-shut).
*1:
nnnn is a number within the area.

nnnn:
1 to 4000
Communication output (fully-open/tightly-shut) includes the following designations:

Gain and bias designation
Full open and tight shut designation
SEE ALSO
For detailed information on the gain and bias specifications, see the following:
C4.8.3, Communication Output Conversion
The actual full-open and tight-shut output values are designated by the full open/tight shut
designation.
IMPORTANT
The following functions for process output cannot be used when the output signal conversion designation is set to Communication output (fully-open/tightly-shut).
Reverse output
Velocity output
Output velocity limiter
<N2.4 I/O Data>
N2-15
Discrete I/O
By designating I/O data in the %WBnnnnbb (*1) format, every word (16 bits) of I/O data can
be assigned to a discrete input or a discrete output.
*1:
nnnn is a number within the area. bb is a bit number in a word.
SEE ALSO
Discrete I/O is treated in the same way as in subsystem communication. For detailed information, see the
following:
J1.3, Accessing Subsystem Data from a Function Block
IMPORTANT
The following functions for process output cannot be used when data is output to %WB.
Pulsive output for MC instruments and switch instruments.
Flashing output
Access Using SEBOL

The use of a dedicated SEBOL statement allows access to I/O data communicated via
PROFIBUS-DP.
Use the ssread statement for reading and the sswrite statement and sswritebit statement
for writing.
SEE ALSO
For more information on SEBOL, see the following:
H1, SEBOL Details
<N2.5 Monitoring Slave Devices>
N2-16
N2.5 Monitoring Slave Devices

The status of a slave device connected to PROFIBUS-DP can be monitored by receiving data from the slave device.
This section explains the following items regarding how to determine the status of a
slave device.
Assigning and referencing the slave device
Slave diagnostic information
N2-17
N2.5.1 Assigning and Referencing a Slave Device

The status of slave devices defined in the PROFIBUS-DP configurator can be assigned to the communication I/O definitions. This makes it possible to use the status
of the slave devices to update the Graphic window, or output messages for sequence control.
The response status of a single slave device is indicated with one bit.
The response status of all slave devices can be assigned using a single communication I/O definition.
Correlation to the Element Number

The slave-device status is assigned to a corresponding element number (%WB) for each
node address.
Table Assignment to an Element Number (%WB)
Element Number
Contents
%WBnnnn01
Status of the slave device with node address 1
%WBnnnn02
.....
.....
%WBnnnn16
%WB(nnnn+1)01
.....
.....
%WBxxxxbb
Status of the slave device with node address X

X=(xxxx-nnnn)16+bb
.....
.....
%WB(nnnn+7)13
%WB(nnnn+7)14
Not used
%WB(nnnn+7)15
Not used
%WB(nnnn+7)16

N020501E.EPS
Note: nnnn is a number within the area for the communication I/O definition, while bb is a bit number in the word.
The status of a slave device is indicated by the data item (PV) value, as shown in the table
below:
Table Data Item Value and Slave Device Status
%WBnnnnbb.PV value
Contents
Slave device error
Slave device normal

N020502E.EPS
N2-18
Communication I/O Builder

To monitor the status of slave devices, perform settings in the Communication I/O Builder
as shown below.
Table Settings in the Communication I/O Builder
Item
Setting
Size
1 to 8
Station
ACP71 node address
Device & Address
STATUS
Data type
Input (Discrete)
Reverse
Bits
Remarks
Can be set according to the number of slave devices
N020503E.EPS
N2-19
N2.5.2 Slave Diagnostic Information

Slave Diagnostic Information reports the details on slave-device status. The following is done when slave diagnostic information is detected in the system.
Sets data status.
Forwards a fieldbus message.
The following method is available for a user to perform special processing based on
slave diagnostic information.
Referencing as communication I/O data
Slave Diagnostic Information consists of the following four portions:
Device common slave diagnostic information
Device specific slave diagnostic information
Module slave diagnostic information
Channel slave diagnostic information
Contents of slave diagnostic information include items detected by a slave device
and those detected by an ACP71.
Items detected by the ACP71 include configuration mismatching with the slave
device.
Contents of Slave Diagnostic Information

Slave Diagnostic Information contents of four parts, their contents are as follows:
Table Slave Diagnostic Information for a Slave Device
Type
Title
Error
detected by:
Description
Device
common slave
diagnostic
information
Station_Status1-3.
Common slave diagnostic information defined by the
Master_Add.
PROFIBUS specifications
Ident_Number
ACP71 or
slave device
Device
specific slave
diagnostic
information
Device related
diagnostic
Slave diagnostic information defined by the specifications of

each slave device
Slave device
Module slave
diagnostic
information
Identifier related
(module)
diagnostic
Presence of an error in a slave device module or I/O channel is

indicated with a bit. This bit indicates an error if even one of
Slave device
the module's I/O channels has experienced an error.
(Bit assignment depends on the specifications of the device).
Channel slave
diagnostic
information
Channel related
diagnostic
Slave diagnostic information for the module's I/O channel.

Each I/O channel has a detail code (Error Type) such as short
Slave device
circuit. Error Type includes items defined by PROFIBUS
specifications and those defined by slave-device specifications.
N020504E.EPS
N2-20
Setting the Data Status

When an error has been reported in the device common slave diagnostic information or
module slave diagnostic information, the status of applicable data is set in LPFL.
When an error has occurred in a slave device, the status of all data concerning that slave
device is set in LPFL.
When an error has occurred in a module, the status of all data concerning that module is
set in LPFL.
The occurrence of an error reported in the device specific slave diagnostic information and
channel slave diagnostic information will not be reflected in the data status.
IMPORTANT
When an error is detected in one of the modules channels, an error is set in all the
data status of the module containing that channel. If you do not wish to set an error in
all data status simultaneously, go to System view and select Do not reflect module
errors in the data status.
The bit assignment for module slave diagnostic information differs, depending on the
device specifications. Data status settings are possible only when the following bit
assignment is done.
Data status cannot be set with any other bit assignment. If the following bit assignment is not done, go to System view and select Do not reflect module errors in data
status.
Set for each ACP71 as to whether or not to reflect a module error in the data status.
If any of multiple slave devices connected to an ACP71 has a bit assignment other than the
one shown on the next page, it will be necessary to select Do not reflect module errors in
data status.
N2-21
Relative address
7
0
0
Bit number
Header information
Size of module slave diagnostic information

Fixed by the PROFIBUS specifications
7
Bit number
1
Slot 1 module
Slot 2 module
Slot 3 module
Slot 4 module
Slot 5 module
Slot 6 module
Slot 7 module
Slot 8 module
7
Bit number
2
Slot 9 module
Slot 10 module
Slot 11 module
Slot 12 module
Slot 13 module
Slot 14 module
Slot 15 module
Slot 16 module
N020505E.EPS
Note: The slot number starts with 0 in some devices, but these devices are treated the same way.
Figure Bit Assignment for Module Slave Diagnostic Information
Forwarding a Fieldbus Message

Slave diagnostic information from a slave device is forwarded as a fieldbus message.
The forwarded message is stored in the historical message log file and can be viewed from
the Historical Message Report window or the Message Monitor window.
SEE ALSO
For more information on fieldbus messages, see the following:
N2.9.2, Fieldbus Messages
N2-22
Referencing as Communication I/O Data

Slave diagnostic information from a slave device can be assigned in the communication I/O
definition for use as a reference. However, since the data status is set and the fieldbus
message is forwarded normally, there is no need to assign information in the communication I/O definition.
Use this function when you wish to use the application to perform a special task based on
the slave diagnostic information.
It is important to note the following when interpreting the slave diagnostic information.
You must have a thorough understanding of the specifications of PROFIBUS and
slave devices.
Details on slave diagnostic information are described in the PROFIBUS specifications
and device manuals. It is necessary to learn the contents of these materials in order to
interpret the slave diagnostic information properly.
The simultaneity of slave diagnostic information is guaranteed for up to four bytes.
In the communication I/O data area where slave diagnostic information has been
assigned, the simultaneity of data is guaranteed for up to four bytes.
An error might not be detected if an error occurrence/normal recovery takes place
within a time period that is shorter than the FCS scan cycle.
Example of Assigning Slave Diagnostic Information

The slave diagnostic information data is assigned to the communication I/O data area,
starting with the head byte according to the size specification.
The following example designates the size of the slave diagnostic information as 3 (6
bytes) and assigns data to %WW0101.
%WB bit number
% W area
01
08, 09
16
7,0
Bit number for each

byte of diagnostic data
%WW0101
%WW0102
%WW0103
Data (first byte)
Data (second byte)
Data (third byte)
Data (fourth byte)
Data (fifth byte)
Data (sixth byte)
N020506E.EPS
Figure Example of Assigning Slave Diagnostic Information
Settings with the Communication I/O Builder

To reference slave diagnostic information, perform the following settings with the Communication I/O Builder.
Table Settings with the Communication I/O Builder
Item
Setting
Size
1 to 128
Station
Slave device node

address
Device & Address
DIAG
Data type
Input (Discrete)
Reverse
No
Remarks
Size can be set according to the size of data for the
part to be referenced
N020507E.EPS
<N2.6 Engineering>
N2-23
N2.6 Engineering
Engineering tasks are broadly classified into two: those performed on System
builders and those performed using PROFIBUS-DP configurator.
This chapter provides an overview of the PROFIBUS-DP engineering, including
ACP71, and explains the operations performed with the PROFIBUS-DP configurator
and System builders.
<N2.6 Engineering>
N2-24
N2.6.1 Engineering Overview

Engineering tasks for PROFIBUS-DP can be divided into the following, according to
the operation process:
Engineering using System builders
Engineering using the PROFIBUS-DP configurator
The outline of engineering will be explained as follows.
Engineering Scope
The following shows the scope and targets for PROFIBUS engineering.
HIS
Control bus
FCS
Area engineered with

System builders
FCS
ACP71
Area engineered with the
PROFIBUS-DP configurator
Slave
device
Slave
device
N020601E.EPS
Figure Engineering Scope

Table Engineering Target
System
builders
PROFIBUS-DP
configurator
HIS
Yes
No
FCS
Yes
No
ACP71
Yes
Yes
Slave device
No
Yes
Engineering target
N020602E.EPS
Yes:
No:
Applicable
Not applicable
Engineering for an ACP71 is performed with the PROFIBUS-DP configurator and System
builders. To perform this engineering, a separate operation is required to allow System
builders to use data created with the PROFIBUS-DP configurator.
<N2.6 Engineering>
N2-25
About ACP71 Engineering

The PROFIBUS-DP configurator is used to create PROFIBUS-DP communication information and slave device-configuration information.
To link PROFIBUS-DP I/O data to a function block, the element number (%WW or %WB)
defined with the Communication I/O Builder must be linked to the PROFIBUS configurator
data.
These links can be defined by entering a portion of the PROFIBUS-DP configurator data in
the Communication I/O Builder.
Once the links are established, the ACP71 will begin operating.
The PROFIBUS configurator has a PROFIBUS-DP communication debug function. Communication with slave devices can be debugged by connecting the PROFIBUS-DP
configurator to the ACP71s dedicated RS port.
<N2.6 Engineering>
N2-26
Downloading PROFIBUS Definition Data

Configuration data created with the PROFIBUS-DP configurator (hereinafter called PROFIBUS definition data) is downloaded to an ACP71 using the HISs System builders.
To download the data, export the PROFIBUS-DP definition data created with the PROFIBUS configurator and copy that data file to the HIS.
Copying is executed from the ACP71 property sheet in System view. The PROFIBUS
definition data is downloaded to the ACP71 by clicking the [OK] button in the property sheet
after copying, or when an IOM load is executed.
When the ACP71 definitions are deleted, PROFIBUS definition data is deleted, as well.
PROFIBUS
definition data file
PROFIBUS-DP
configurator
HIS
Export
Copy
Control bus
Download
FCS
ACP71
PROFIBUS-DP
Slave device
Slave device
N020603E.EPS
Figure Downloading PROFIBUS Definition Data
<N2.6 Engineering>
N2-27
IMPORTANT
The PROFIBUS definition data file stores the data downloaded to an ACP71, but is
not a database where PROFIBUS-DP project data is stored. Thus, the PROFIBUSDP project cannot be edited from the PROFIBUS definition data file.
PROFIBUS-DP does not download data to a slave device.
The PROFIBUS definition data contains setting information for the slave device. This
setting information is set in the slave device from an ACP71 when the ACP71 or a
slave device starts up.
Do not download PROFIBUS definition data from the PROFIBUS configurator directly to an
ACP71.
The PROFIBUS configurator has a function to directly download PROFIBUS definition data
via the ACP71s RS port. However, do not use this function, since the following problems
will occur when it is used:
During PROFIBUS definition data download, all PROFIBUS-DP communications stop
and all I/O data becomes IOP/OOP.
Correct copying of PROFIBUS definition data to System builders cannot be guaranteed. While data is being downloaded from System builders, PROFIBUS definition
data in an ACP71 may be rewritten as different data or may be deleted.
<N2.6 Engineering>
N2-28
Engineering Procedures
The following shows the basic engineering procedures using System builders and the
PROFIBUS-DP configurator.
Settings on System builders can be performed along with settings on the PROFIBUS-DP
configurator.
(1)
System design
Engineering operations with
System builders

the PROFIBUS-DP configurator
(2)
Input and export with the
(3)
Copy the ACP71 definitions and
the PROFIBUS definition data file
(4)
Assign the communication I/O
definition to the element number
(5)
Link to a function block using
the Control Drawing Builder
Operation when
there is no FCS
Operation when
there is an FCS
(6)
Debug using the Test Function
(7)
Download
(8)
Debug PROFIBUS-DP
communication
(9)
Check for errors
END
N020604E.EPS
Figure Engineering Procedures
<N2.6 Engineering>
N2-29
System Design
Design the function-block configuration, including the slave device, communication specifications and control specifications.
Input and Export with the PROFIBUS-DP Configurator

Input design information (slave-device configuration, slave-device module configuration,
communication-information definitions) in the PROFIBUS-DP configurator, then export the
completed project.
Copy the ACP71 Definitions and the PROFIBUS Definition Data File
Define the ACP71 using System View. Copy the PROFIBUS definition data file using the
ACP71 property sheet.
However, no error will occur even if the PROFIBUS definition data file is not copied. Copy
the PROFIBUS definition data file prior to downloading.
Assign the Communication I/O Definition to the Element Number

Assign the communication I/O definition for an ACP71 to the element number. Define the
same settings as the PROFIBUS configurator settings.
Link to a Function Block Using the Control Drawing Builder

Link the element number for the communication I/O definition to a function block using the
Control Drawing Builder.
Debug Using the Test Function

Use the Test Function to debug the FCS application. I/O isolation and wiring can be performed.
The following operations can be done with isolated I/Os.
Direct data input to the communication I/O data area
Wiring between the designated communication I/O data
Download
Download engineered information to an FCS and ACP71.
PROFIBUS definition data is not downloaded during an off-line download. To download
PROFIBUS definition data, execute an IOM load for the ACP71 following the off-line download.
Debug PROFIBUS-DP Communication

Connect the ACP71 and slave devices, then debug PROFIBUS-DP communication using
the PROFIBUS configurator.
Check for Errors

If there is an error in the assignment of communication I/O definitions to the element number, a system alarm will be generated when an ACP71 is executed.
At this point, check to see that no system alarm is generated.
<N2.6 Engineering>
N2-30
N2.6.2 Operations with the PROFIBUS-DP Configurator

This section explains the following items regarding operations using the PROFIBUSDP configurator.
Procedure for creating a new project
Procedure for modifying a project
SEE ALSO
For detailed information on the method of use and debugging operations, refer to the included
PROFIBUS-DP Configurator Users Manual.
Procedure for Creating a New Project

1.
Create a project.
The project herein refers to the database that comprises 1 segment of PROFIBUSDP.
2.
Read the GSD file for the slave device to be used.
3.
Define an ACP71.
To define the ACP71, select [ACP71] or [COM-DPM/PKV20-DPM]. (*1)
*1:
For the PROFIBUS-DP configurator (System Configurator) with a version earlier than 2.818, only COM-DPM/PKV20DPM can be selected as PROFIBUS-DP Master.
If the revision number of ACP71 unit is 1 or greater, choose ACP71.

If the revision number of ACP71 unit is 0, choose COM-DPM/PKV20-DPM.
The location of the revision number engraved on ACP71 unit is illustrated as follows.
MAINT
CN1
REVISION
REVISION
U
1
H1 H2 F
1
H1
H2
N020617E.EPS
Figure Location of ACP71 Unit Revision Number
<N2.6 Engineering>
N2-31
IMPORTANT
When configuring the master device, the address of the master device should be set to a
number equal to 1 or greater than 1. By the default of system configurator version 2.818, 0
is set as the address.
The device address can be modified by changing the setting on the item [Station address]
of Master Configuration dialog box.
Master Configuration
General
OK
Description
Master0
Station address
Device
Cancel
0
ACP71
DP Support
DP Master Settings ...
Auto addressing
FMS Support
FMS Settings ...
CRL ...
CD ...
Actual Master
Module Information
Storage format
Compact
N020618E.EPS
Figure Master Configuration Dialog Box
4.
Define the slave device. If multiple modules can be set from the slave device, assign
the modules.
Set definitions specific to each slave device, if necessary.
5.
Export the project.

A PROFIBUS configuration data file (*1) will be created.
*1:
Since the version 2.818 of System Configurator, in order to match the corresponding project database <project>.pb,
the file name is changed from Export. dbm to <project>.dbm by simply adding the DBM extension to the project name.
<N2.6 Engineering>
N2-32
Procedure for Modifying a Project

1.
Open a project.
2.
Add, delete or change the slave device or the slave device module.
3.
Export the project.

A PROFIBUS configuration data file (*1) will be created.
*1:
Since the version 2.818 of System Configurator, in order to match the corresponding project database <project>.pb,
the file name is changed from Export. dbm to <project>.dbm by simply adding the DBM extension to the project name.
TIP
A PROFIBUS-DP configuration data file must be created to modify even a single setting item of the
PROFIBUS configurator. The following are some typical changes.
Adding a slave device
Deleting a slave device
Adding a module to the slave device
Deleting a module from the slave device
Changing a slave device module
Changing Set Details for the slave device
Changing bus parameters
IMPORTANT
When setting bus parameters, make sure the [Auto Clear] item is set as OFF (default). If
[Auto Clear] is set ON, the ACP71 module stops communication with all the slave devices
on the PROFIBUS-DP bus when any of devices fails or any malfunction event occurs. In
this case, all inputs and outputs of ACP71 become IOP or OOP. To recover from IOP and
OOP, it is necessary to run IOM download.
<N2.6 Engineering>
N2-33
N2.6.3 Operations in System View

This section explains the following items regarding operations in System view.
Procedure for Creating a New IOM

1.
Select [File], [Create New], then [IOM] from System view. The Create New IOM dialog
box will appear.
2.
In the Create New IOM property sheet, select AMN52(PROFIBUS Communication)

in [Category] of the [Type and Position] page.
3.
Select ACP71(PROFIBUS-DP Communication interface ) in [Type] of in the Create

New IOM property sheet.
4.
Set detail definitions for an ACP71 in the [Set Details] page.
5.
Click the [Copy] button in [PROFIBUS configuration data file] of the [Set Details] page.
The Open dialog box appears.
6.
Select PROFIBUS configuration data file from the Open dialog box, and click the [OK]
button. The PROFIBUS configuration data file will be copied.
7.
Click the [OK] button in the Create New IOM dialog box. The Create New IOM dialog
box will be closed.

1.
In System view, select an ACP71 for which you wish to change the setting contents.
Then, select [File] and [Properties] to display the property sheet.
2.
Display the [Set Details] page in the property sheet, then change the setting contents
as required.
3.
If any change has been made to the setting contents of the PROFIBUS-DP
configurator, click the [Copy] button in [PROFIBUS configuration data file]. The Open
dialog box will appear.
If there are no changes, skip step 4 and go to step 5.
4.
Select the PROFIBUS configuration data file from the Open dialog box, then click the
[OK] button. The PROFIBUS configuration data file will be copied.
5.
Click the [OK] button in the property sheet. The property sheet will be closed.
<N2.6 Engineering>
N2-34
Details of System View

This section explains details of System View, in particular, the ACP71 property and IOM
download.
Create New IOM Dialog Box

The following table lists the contents of the property sheet displayed for creating a new
IOM.
Table Contents of the Create New IOM Dialog Box
Tab
Item
Details
IOM Type
Type
and
Position
Installation Position
Remarks
Category
Select AMN52(PROFIBUS Communication)
Type
Select ACP71(PROFIBUS-DP Communication interface)
Unit
Only unit1 can be selected. This item cannot be selected if an IOM

other than ACP71 is set for that unit1 or if unit2 is used.
Slot
1 to 4 slots can be selected.

Cannot be selected.
High Speed Read

IOM Comment
N020605E.EPS
Create New IOM

Type and Position
Set Details
IOM Type
Category
AMN52(PROFIBUS Communication)
Type
ACP71(PROFIBUS-DP Communication interface)
Unit
Slot
Duplicate Next Card

High Speed Read
IOM Comment
OK
Cancel
N020606E.EPS
Figure Create New IOM Dialog Box
IM 33S01B30-01E
<N2.6 Engineering>
N2-35
ACP71 Property
Perform Fallback, Action when Module/Channel Fail Detected, PROFIBUS Configuration Data File
The table below lists the contents of the ACP71 property.

Table Contents of the ACP71 Property
Tab
Item
Change
IOM Type
No
Type
and
Position
High Speed Read
No
Details
Category
Type
Unit
Slot
Cannot be selected.
No
IOM Comment
Yes
IOM Category
No
IOM Type
No
Unit
No
Slot
No
Displays settings defined in the Type and position tab
Fallback operation is enabled/disabled by the check box.

By default, the setting is enabled. (box is checked)
Yes
Perform Fallback
Set
Details
Action when
module/channel fail
detected
PROFIBUS
configuration data
file
Tab
Yes
All points maintain

Current value
Yes
Reset all outputs
Yes
Set all corresponding

module input data to IOP
Yes
Action upon the detection of module failure is determined

by the check box. By default, the setting is enabled.
module input data to OOP
(box is checked)
Yes
1st slot no. of field

0 or 1 can be selected. The initial value is 1.
instruments in message
No
File Name
Displays the file name. Cannot be selected. The default

is blank. Updated after [Copy] is executed.
No
Creation date
Displays the time and date file was created. Cannot be

selected. The initial value is blank. Updated after [Copy]
is executed.
No
Date copied
Displays the time and date [Copy] was executed.

Cannot be selected. The initial value is blank. Updated
after [Copy] is executed.
Yes
[Copy]
Clicking the [Copy] button displays the file selection

dialog box and copying is executed. (*1)
The filename extension is DBM.
Item
Change
Fallback operation is determined by the option button.

The default setting is All points maintain Current value.
Action upon the detection of module failure is determined
by the check box. By default, the setting is disabled.
(box is not checked)
The value set for each item is restored to the initial value
(except for detail items relating to the PROFIBUS
configuration data file).
Yes
[default]
Remarks
Details
Remarks
N020607E.EPS
Yes:
No:
*1:
Can be changed even after a new IOM has been created.

Cannot be changed once a new IOM has been created.
PROFIBUS configuration data is downloaded when the [OK] button in the property sheet is clicked after the data has
been copied. Clicking the [Cancel] button in the property sheet after copying invalidates the file that was copied and
restores the file previously copied.
IM 33S01B30-01E
<N2.6 Engineering>
N2-36
Properties
Type and Position
Set Details
IOM Category
IOM Type
Unit
Slot
Perform Fallback
All points maintain Current value
Reset all outputs
Action when module/channel fail detected

Set all corresponding module input data to IOP
Set all corresponding module output data to OOP
1
1'st slot no. of field instruments in message
PROFIBUS configuration data file

File Name
Creation date
Date copied
Copy
Default
OK
Cancel
N020608E.EPS
Figure ACP71 Property Sheet
IOM Download
During IOM download, the following data will be downloaded to the ACP71.
PROFIBUS configuration data
ACP71 program
IOM download can be executed by selecting [Load], then [Download to IOM] from System
view.
IMPORTANT
The IOM Download Start/Complete system alarm is generated for both the PROFIBUS
configuration data and ACP71 program. In this case, correspondence with data to be
downloaded can be checked by the messages in the IOM download dialog box.
The ACP71 program will be downloaded only when Create New IOM or IOM download is
executed.
N2-37
<N2.6 Engineering>
N2.6.4 Operations with the Communication I/O Builder

This section explains the procedures and setting items concerning operations using
the Communication I/O Builder.
When the contents of the PROFIBUS configurator definition are not consistent with
the contents defined by the Communication I/O Builder, inconsistent data is set as
IOP or OOP. Consistent data will be treated normally.
Additionally, a system alarm will be forwarded in regard to the slave device containing inconsistent definitions.
An example of a cause of the inconsistency is that a module designated in the
addresses of other slave devices does not exist in the PROFIBUS definition.
Operation Procedures
The following describes the operation procedures using the Communication I/O Builder.
1.
Set the common setting items, then assign the communication I/O data area for an ACP71.
2.
Set communication I/O definitions for each slave device module.
Common Setting Items in the Communication I/O Builder

The following lists the common items for defining a single ACP71 in the Communication I/O
Builder.
Items other than the common items are set for modules for slave devices.
Table Common Setting Items in the Communication I/O Builder
Item
Description
Buffer
Designates the size of the area for storing communication I/O definition data
that is used in an ACP71.
Program Name
Designates the installation position of an ACP71 (u-s, u: unit number (fixed to 1),
s: slot number) and the program name (PROFIBUS)
Example: When slot 2 is designated
1-2PROFIBUS
N020609E.EPS
Communication I/O Items Set for Slave Device Modules

Data to be Reflected from the PROFIBUS-DP Configurator to the
In order to link the definitions for the PROFIBUS-DP created via the PROFIBUS-DP
configurator and the contents of communication I/O definitions, a part of the contents set with
the PROFIBUS-DP configurator must be reflected in the settings of the Communication I/O
Builder.
Data that must be reflected in the settings of the Communication I/O Builder is displayed in
the Slave Configuration dialog box for the PROFIBUS-DP configurator. The table below
lists that data:
Table Data that Must be Reflected in the Settings
Item
Content
Remarks
Station Address Slave device node address

Slot
Slot number defining the module Serial number starting with 1, no blanks in between
Idx
Index of data in the module
Reflected when a single module has multiple I/O data

N020610E.EPS
N2-38
<N2.6 Engineering>
Slave device node address

Slave Configuration
General
Device
Description
COM-DPS
Slave#2
Station address
Cancel
Activate device in actual configuration

Enable watchdog control
Max. length of in-/output data
Max. length of input data
Max. length of output data
Max. number of modules
Module
64 byte output con [0x80, 0xBF]
1 word output con [0xE0]
Slot Idx
1
1
1
2
1
3
1
4
1
5
1
6
1
7
OK
368
244
244
24
Byte
Byte
Byte
GSD file
Module
1 byte input con [0x90]
32 word input [0x40, 0x5F]
1 word output [0x60]
16 word output [0x6F]
Symbol
Module#1
Module#2
Module#3
Module#4
Module#5
Module#6
Module#7
HIL_7501.GSD
Length of in-/output data

Length of input data
Length of output data
Number of modules
Inputs Outputs In/Out

64 byte
1 word
2 word
3 word
4 word
8 word
Parameter Data...
111
69
42
7
Byte
Byte
Byte
Master#1
Identifier
0x80, 0xBF
0xE0
0xE1
0xE2
0xE3
0xE7
Type 1 Addr. 1 Len. Type

IB
0
1
IB
0
4
QW
IW
0
32
QW
QW
QW
Assigned master
Station address 1
1/ACP71
Actual slave
Station address 2
Slave#2
2/COM-DPS
0 Addr. 0 Len.
Append Module
0
Remove Module
0
0
0
1
16
2
Symbolic Names
Insert Module
Module slot number
N020611E.EPS
Figure Slave Configuration Dialog Box
The figure below shows an example of a dialog box for a module containing multiple
indexes.
Slave Configuration
General
Device
Description
BusCon
Slave#3
Station address
OK
Cancel

Byte
Byte
Byte
GSD file
Parameter Data...
EBH82079.GSD

244
244
244
1

Number of modules
226
210
16
1
Module
H&B Var.80
Inputs Outputs In/Out Identifier

1 Word
8 Word 0xD0, 0xF7, 0xDB,
Byte
Byte
Byte
Assigned master
Station address 1
Master#1
1/ACP71
Actual slave
Station address 3
Slave#3
3/BusCon
Slot Idx
1
1
1
2
1
3
1
4
1
5
1
6
1
7
Module
H&B Var.80
H&B Var.80
H&B Var.80
H&B Var.80
H&B Var.80
H&B Var.80
H&B Var.80
Symbol
Module#1
Module#1
Module#1
Module#1
Module#1
Module#1
Module#1
Type
IW
IW
IW
IW
IW
IW
IW
1 Addr. 1 Len. Type 0 Addr. 0 Len.

0
1
0
8
QW 0
8
0
12
0
12
0
12
0
12
0
12
Index of data inside the module
Append Module
Remove Module
Insert Module
Symbolic Names
N020612E.EPS
Figure Slave Configuration Dialog Box (With Multiple Indexes)
<N2.6 Engineering>
N2-39
Communication I/O Builder Items Defined for One Module

Communication I/O definitions are set for each slave device module. If a module has both
inputs and outputs, they are defined separately.
The table below lists the Communication I/O Builder items defined for one module.
Size:
Designates the data size for the slave device module on a

word-by-word basis. (*1)
Station:
Station Address for the Slave Configuration window
Device & Address:
Slot and Idx for the Slave Configuration window
Data Type:
Enter according to the slave device modules specifica

tions.
Reverse:
Refer to the slave device manual to determine whether

[Bits] or [No].
*1:
If an odd byte data is assigned, there is no data corresponding to the terminal byte of the area because the area is
designated on a word-by-word basis. In this case, the value of the terminal byte data for the area is undefined.
TIP
When a module is deleted using the PROFIBUS-DP configurator, the slot numbers following that module
will shift. Thus, modify the setting contents in [Device & Address].
However, this does not apply to slave devices to which no changes are made.
<N2.6 Engineering>
N2-40
Details of Communication I/O Builder

Buffer, Program Name, Size, Port, IP Address, Station, Device & Address, Data Type, Reverse,
Scan, Service Comment, Label
Definitions relating to the communication I/O data area are set in the Communication I/O
Builder.
The definition content is as shown below.
Table Definition Items in the Communication I/O Builder (1/2)
Definition
item
Input
Details
Remarks
Buffer
Yes Sets the size of the entire area for storing the ACP71 data.
Program
Name
Sets the installation position of a module and "PROFIBUS."

Example: When the module is loaded in unit 1, slot 2
1-2PROFIBUS
Yes
When the cursor is positioned over the program name, the program
name is displayed in the list, according to the installation position of
the ACP71 that has been created, as in the case of ACMxx.
Size
Sets the size to be assigned for a single slave device module.

The size is assigned on a word-by-word basis (in increments
Yes of 2 bytes).
The valid range of values is from 1 to 126. However, entering a
value outside this range will not generate an error in the builder.
Port
No
Sets the Port number.

However, this is not used in this function.
IP Address
No
Sets the IP address for other devices.

However, this is not used in this function.
Station
Sets the slave device node address.

Yes The valid range of values is from 0 to 125. However, entering a
value outside this range will not generate an error in the builder.
Designating a non-existent
slave device node address
will set data to IOP/OOP
upon execution.
Device &
Address
Sets the slot number and index for the slave device module.
Sets in the "Slot number-index" format.
When index = 1, "-index" can be omitted.
Example: "1-3" when slot number=1 and index=3
Designate ";E" to expand byte data to 16 bits.
Yes Example: 1-3;E
The valid range of slot numbers is from 1 to 60. The index
range is 1 to 60. However, entering a value outside this range
will not generate an error in the builder.
Designating an unused or
out of range slot
number/index will set data
to IOP/OOP upon
execution.
Setting an IP address will

not generate an error.
N020613E.EPS
Yes:
No:
-:
Input is required.
Input is not required.
Can be omitted.
<N2.6 Engineering>
N2-41
Table Definition Items in the Communication I/O Builder (2/2)

Definition
item
Input
Details
Remarks
Data
Type
Yes
Reverse
Sets whether or not to reverse the bit arrangement in the

FCS and bit arrangement in the subsystem.
The Reverse Bits may be selected as follows:
Yes
Bits
No
The default setting is Bits.
Scan
Sets whether or not to update communication I/O analog data

at the start of fast-scan.
The Specify Fast-scan may be selected as follows:
Yes
Normal
Fast
The default setting is Normal.
Set according to the slave device module specifications.

The default setting is blank.
Service
Comment
A comment can be set.
Label
The I/O terminal name can be set as a user-defined label.

This item is an optional setup item.
Only when the data type

is Input (Discrete) or
Output (Discrete), Bits
reverse can be selected.
N020614E.EPS
Yes:
No:
-:
Input is required.
Input is not required.
Can be omitted.
N2-42
<N2.6 Engineering>
N2.6.5 Operations in Function Block Detail Builder

Operations on Function Block Detail Builder will be explained as follows.
Settings on Function Block Detail Builder

Designates Communication Output (Fully-open/Tightly-shut) for [Output Signal Conversion], which is a setting item in the Function Block Detail Builder.
Table Setting Items in the Function Block Detail Builder
Tab
Basic or Output
(optional item setup)
Item
Output signal
conversion
Details
Output signal
conversion type
Setting Contents
Communication output
(Fully-open/Tightly-shut)
N020615E.EPS
Designating Communication Output (Fully-open/Tightly-shut) will display the following

items:
Table Displayed Items when Communication Output (Fully-open/Tightly-shut) is Selected
Detailed item
Default
Data Conversion Gain
1.000
Data Conversion Bias
0.000
Output Value for Full-open
106.25
Output Value for Tight-shut
-17.19
Remarks
Same as in the case of Communication
Output
Same as in the case of No
N020616E.EPS
SEE ALSO
For more information on output signal conversion, see the following:
C4.8, Output Signal Conversion
<N2.7 Operation and Monitoring>
N2-43
N2.7 Operation and Monitoring

Operation and Monitoring includes the function for displaying the ACP71 status and
the function for displaying various messages generated in PROFIBUS-DP communication.
SEE ALSO
For more information on the messages generated in PROFIBUS-DP communication, see the following:
N2.9, Messages
FCS Status Display Window

The status of an ACP71 is displayed in the FCS Status Display window of an HIS as follows:
Green:
PROFIBUS-DP communication can be performed
Red:
Hardware failure or PROFIBUS-DP communication cannot be performed.
The table below shows changes in the status display due to user operation.
Table Changes in Status Display Due to User Operation
Status display
User operation
With PROFIBUS
Without PROFIBUS
configuration data (*1) configuration data (*2)
Create new
Green
Red
IOM download
Green
Red
ACP71
replacement
Before IOM download

After IOM download
FCS offline download
Red
Red
Green
Red
Green
Red
Remarks
Status immediately after replacement

PROFIBUS configuration data is not
subject to download
N020701E.EPS
*1:
*2:
Indicates that copying of PROFIBUS configuration data is completed in System view.

Indicates that operations with the PROFIBUS-DP configurator are incomplete or that copying of PROFIBUS configuration data is not performed in System view.
N2-44
When AMN52 is used, the unit 1 and unit 2 positions are physically occupied.
However, only the unit 1 section is displayed in the FCS Status Display window. The unit 2
section is displayed as no IOM definitions. There are no changes to units 3 to 5. The status
is displayed according to the IOM definitions.
The following figure shows the FCS Status Display window.
.SF FCS0101 FCS Status Display
FCS
FCS
IOM
Domain : 01
MYPJT
FCS0101
V net1
1
V net2
2
AUT
Not Ready
Stand-By
Control
Hard Ready
Maintenance
Distillation column A
Station No
:1
Type
: PFCD-H
Revision
Generation
: R3.05. 00
:
10/28/2004 13 : 29
CPU Idle Time
: 57Sec
A
C
P
7
1
A
C
P
7
1
A
C
P
7
1
A
C
P
7
1
C
P
U
C
P
U
P
S
U
P
S
U
A
D
M
1
2
C
A
D
M
5
1
C
A
D
M
5
1
C
Comn Load Ave : 0%

Test Mode
Cur : 0%
: OFF
ControlStatus : RUN
I/O (OFF)
Comm I/O
: ON
Task Status
Task 1
Task 2
: RUN
: RUN
Task 3
Task 4
: RUN
: RUN
A
C
M
1
1
A
C
M
1
1
A
M
M
2
2
T
A
M
M
2
2
T
A
D
M
1
2
C
Ready
N020702E.EPS
Figure FCS Status Display Window
In the FCS Status Display window, the following data can be downloaded to the ACP71 by
clicking the [Load IOM] button.
PROFIBUS configuration data
ACP71 program
IM 33S01B30-01E
<N2.8 Unusual Operations>
N2-45
N2.8 Unusual Operations

This chapter explains unusual operations in PROFIBUS-DP communication.
N2-46
N2.8.1 Start Operation

The following explains the status of an ACP71 at the time of initial cold start and
restart.
FCS Internal Status during the Start Actions

The table below lists the FCS internal status at the time of initial cold start and restart.
Table FCS Internal Status
Start action
Function block's action
ACP71's action
Reads new input values.
Resets output values (*1).
Initial cold start
MAN fallback
Restart
Retains the status prior Reads new input values.

Resets outputs, then re-outputs the value prior to power failure (*1).
to power failure
N020801E.EPS
*1:
Resetting outputs means outputting 0 to the analog output and discrete output.
IMPORTANT
Do not access or write to the communication I/O (%WW, %WB) that have been assigned to
an ACP71 from the initialization sequence table.
N2-47
Initial Cold Start Actions

This section explains the actions of devices at the time of an initial cold start.
Input Actions
Read data remains 0 from the initial cold start until the ACP71 becomes capable of acquiring data from slave devices normally.
The status of this data is NRDY.
Output Actions
After maintenance or following a power recovery, the ACP71 begins outputting analog and
discrete outputs from 0. When the fail-safe function is enabled, the slave device retains the
output during the fail-safe monitoring time.
However, once the monitoring time has elapsed, the status becomes fail-safe. The slave
devices specifications determine whether the fail-safe function is enabled and how the
slave device outputs data in the fail-safe status.
Occurrence of
power failure
CPU action
status
Function block
mode
AUT
Power recovery
MAN
Output begins from reset status (0)
ACP71 output
Slave device
output
Enters the fail-safe status when the
fail-safe monitoring time is up
Fail-safe monitoring time
N020802E.EPS
Figure Actions at Initial Cold Start
N2-48
Restart Actions
This section explains the actions of devices at restart.
Input Actions
After power is recovered, the input data prior to the momentary power failure is retained
until the ACP71 becomes capable of acquiring data from slave devices normally. The
status of this data is NRDY.
Output Actions
The ACP71 outputs are reset at the initial cold start of the ACP71. However, after the initial
cold start the ACP71 begins outputting with the value prior to the power failure.
The function block continues control in AUT mode.
When fail-safe is enabled, the slave device retains the output during the fail-safe monitoring
time.
However, once the monitoring time has elapsed, the status becomes fail-safe. The slave
devices specifications determine whether fail-safe function is enabled and how the slave
device outputs data in the fail-safe status.
Occurrence of
power failure
Power recovery
CPU action
status
Function block
mode
AUT
AUT
Output resets at initial cold start of ACP71
Output begins from reset status (0)
ACP71 output
Slave device
output
Enters the fail-safe status when the
fail-safe monitoring time is up
Fail-safe monitoring time
N020803E.EPS
Figure Actions at Restart
N2-49
N2.8.2 Actions in the Event of Faults

This section explains the actions in the event of faults.
Actions Corresponding to the Power Failure/Failure Mode

The following actions are preformed in response to the respective power failure/failure
modes in the event of faults.
Table Actions By Power Failure/Failure Mode
Power
Failure/Failure
Mode
FCS control operation
ACP71 output action
Slave device output action
When a failure When power is When a failure When power is When a failure When power is
occurs
recovered
occurs
recovered
occurs
recovered
FCS power
failure
Initial cold start

or
restart
FCU action stop
Initial cold start Output fallback Output restart
Output reset
or
output restart
Fail-safe
operation (*1)
Output reset
or
output restart
Output fallback
Output restart
ACP71 failure
MAN fallback
Output restart
Output reset
Fail-safe
operation (*1)
Output reset
ACP71
maintenance
MAN fallback
Output restart
Output reset
Fail-safe
operation (*1)
Output reset
PROFIBUS
transmission stop MAN fallback
Output restart
Output restart
Fail-safe
operation (*1)
Output restart
Slave device
failure
MAN fallback
Output restart
Output restart
Output restart
Slave device
maintenance
MAN fallback
Output restart
Output restart
Output restart
Slave device single MAN fallback

power failure
Output restart
Output restart
Output restart
FCS control-right No change

transfer
Restart
No change
No change
No change
No change
N020804E.EPS
*1:
When access from the master device (ACP71) does not take place over a certain period of time, the output of slave
devices will be forcibly changed to the designated value. The slave-device specifications determine whether fail-safe is
enabled and the tolerant tim span can be set. The duration for monitoring access from the master device is set in the
slave devices watchdog timer. The watchdog timer settings are defined using the PROFIBUS-DP configurator.
N2-50
Actions in the Event of a Power Failure

System Operations in the Event of an FCS Power Failure
The FCU and ACP71 stop actions in the event of an FCS power failure.
The following start actions take place when power is recovered following the FCS power
failure.
When there is a prolonged power failure: Initial cold start
When there is a momentary power failure:Restart
SEE ALSO
For detailed information on whether an initial cold start or restart is performed when power is recovered,
see the following:
B2, Start Operations
System Operations in the Event of a Slave-Device Single Power Failure

A slave-device single power failure refers to a situation in which one or more slave devices
connected to the ACP71 experience a power failure. At this time, operation continues in the
ACP71, FCU and the slave devices to which power is supplied.
An example of a cause of a slave-device single power failure is a failure in the powersupply section of the slave device.
The ACP71 retains its previous output values when power is recovered following the slavedevice single power failure, regardless of the duration of the power failure.
In a function block directly connected to communication I/Os, when the slave device at the
connection destination experiences a power failure, the FCS control operation executes a
manual initialization (IMAN) after a MAN fallback.
Actions in the Event of a CPU Failure

The following lists the failure status of an FCS CPU in which a fault has occurred while the
system was running.
CPU action stop
Processor unit control-right transfer
N2-51
CPU Operation Stop

The ACP71 output operation executes an output fallback when a CPU operation stop
status occurs.
When there is a recovery from the CPU operation stop status, output restarts from the
actual output value upon recovery. Recovery in this case refers to when one of the following operations has been performed.
FCS start operation from the HIS
Start operation from the FCS operation panel
Output fallback is executed four seconds after the CPU abnormality is detected, as is the
case with other IOMs.
Output fallback settings for the ACP71 is performed using the ACP71 property sheet that is
opened from System view.
When [Perform Fallback] is enabled, set either All points maintain Current value or
Reset all outputs.
When [Perform Fallback] is disabled, the current value will be retained.
The FCS control operation performs an initial cold start upon recovery from a CPU operation stop status.
CPU operation stops
Recovery
CPU operation
status
Function block
mode
AUT
MAN
Current value is retained

ACP71 output
Slave device
output
N020805E.EPS
Figure Action when [Perform Fallback] is Enabled and [All Points Maintain Current Value] is Set
or when [Perform Fallback] is Disabled.

CPU operation stops
N2-52
Recovery
CPU operation
status
Function block
mode
AUT
MAN
Reset outputs
ACP71 output
Slave device
output
4 seconds
N020806E.EPS
Figure Action when [Perform Fallback] is Enabled and [Reset all outputs] is checked.
System Operation during Processor Unit Control-Right Transfer

When a processor unit control-right transfer occurs, FCS control restarts upon recovery.
There will be no other changes.
N2-53
Operations in the Event of Faults in the ACP71

System Operations during an ACP71 Failure
The following system operations are performed during an ACP71 failure, as is the case with
other IOMs.
ACP71 output operation
Resets outputs upon recovery from the ACP71 failure.
Performs a MAN fallback when an ACP71 failure occurs. Also, restarts output upon
recovery.
When there is an error in the ACP71, or if the communication status is abnormal, the data
prior to the fault occurrence can be read while the error continues. However, the data status
will be LPFL.
During an ACP71 failure, the slave device changes to the fail-safe status.
The slave device output in the fail-safe status depends on the devices specifications.
System Operations during ACP71 Maintenance

The system operations during ACP71 maintenance are the same as during an ACP71
failure.
System Operations during PROFIBUS Transmission Stop

PROFIBUS transmission stop status refers to a state in which PROFIBUS communication
has become disconnected for some reason and transmission with the slave device is no
longer being performed. In this case, the FCU, ACP71 and slave device continue operating
independently.
PROFIBUS transmission stop status occurs when the transmission line has become
disconnected.
System operations during PROFIBUS transmission stop status are the same as during a
slave device power failure.
N2-54
Operations in the Event of Faults in the Slave Device

System Operations during a Slave-Device Failure
A slave-device failure refers to a situation in which one or more slave devices connected to
the ACP71 experience a failure. In this case, the nonfailing slave device, the ACP71 and
FCU continue operating.
ACP71 output operation
Reverts to previous outputs when recoveries from the slave device failure.
Performs a MAN fallback when the slave device failure occurs. Restarts previous
output values when ACP71 recoveries.
System Operations during Slave Device Maintenance

The term slave-device failure refers to a state in which one or more slave devices connected to the ACP71 have been cut off from the PROFIBUS transmission route in order to
perform maintenance work. In this case, the slave device under maintenance, the ACP71
and FCU continue operating.
System operations during slave-device maintenance are the same as during a slavedevice failure.
N2-55
N2.8.3 Actions during Download

This section explains the actions during an offline download to the ACP71.
Actions during an Offline Download to the ACP71

ACP71 actions during an off-line download differ, depending on the definition content and
ACP71 status.
After executing an off-line download for the FCS, execute an IOM download for the ACP71,
if necessary, according to the condition. The reason for this is, there will be a lack of data
consistency in the ACP71 because the PROFIBUS definition data is not downloaded
during an off-line download to the ACP71.
See the table below for conditions under which an IOM download is required. The ACP71
operates as described in the table, if and only if the slave device is correctly connected and
powered.
Table ACP71 Actions during an Offline Download
Condition
Action after offline

download
IOM
download
Action after IOM

download
When using a completely

new ACP71 module.
When the ACP71 is replaced
before offline download.
Input becomes IOP.

Output becomes OOP. (*1)
Required
Reads new inputs and resets

outputs (*2)
Not required
Reads new inputs and

resets outputs (*2)
When there are

changes to the
definition content (*3)
When there are no changes
to the definition content
N020807E.EPS
*1:
*2:
*3:
The ACP71 reads new inputs and resets outputs for those slave devices connected to the ACP71 prior to replacement,
as well as the slave devices connected to a new ACP71 after replacement that meet all of the following conditions:
Node-address agreement
Ident Number (model code) agreement
I/O module configuration agreement
Resets outputs means that 0 is output for the analog output and discrete output.
This occurs in the situation that copying PROFIBUS configuration to a default project or a project offline, the copied
contents have discrepancies with PROFIBUS configuration contents downloaded to the ACP71.
N2-56
N2.8.4 Actions during Online Maintenance

When online maintenance is performed for the ACP71, actions of devices differ
according to the status during the maintenance.
The status during online maintenance include the following:

The PROFIBUS definition data is downloaded or not downloaded
The PROFIBUS definition data contents are correctly reflected in the communication I/O definitions
Do the PROFIBUS definition data contents agree with the actual slave device
configuration?
TIP
There is agreement when all of the following conditions are satisfied between the PROFIBUS definition
data and slave device.
Node address agreement
Ident Number (model code) agreement
FCS
Communication
I/O definitions
Reflected?
Is the data downloaded?
ACP71
PROFIBUS
definition data
Is there agreement?
Slave device
Slave device
N020808E.EPS
Figure Online Maintenance Status
N2-57
Creating a New ACP71

This section explains the actions when creating a new ACP71 according to the status
during online maintenance.
The following actions take place when the PROFIBUS definition data is copied using the
Create New IOM dialog box:
PROFIBUS definition data is downloaded.
The ACP71 reads new inputs and resets outputs.
At this point, the function block normally remains unaffected in terms of its action,
since there is no assignment of communication I/O definitions or links to the function
block.
However, if communication I/O definitions have been assigned and linked to the
function block beforehand, then the function block will perform an initial cold start.
The following actions take place when the PROFIBUS definition data is not copied using
the Create new IOM dialog box.
The PROFIBUS definition data is not downloaded.
The ACP71 does not communicate I/O data.
At this point, the function block normally remains unaffected in terms of its action since
there is no assignment of communication I/O definitions or link to the function block.
Even if communication I/O definitions have been assigned and linked to the function
block beforehand, the function block remains in MAN fallback without change.
Changing the ACP71 Properties

If the PROFIBUS definition data is copied and downloaded in the ACP71 property sheet,
communication with all slave devices will stop. At this time, inputs change to IOP or retain
their previous values, and outputs change to OOP.
Accordingly, the function block at the connection destination performs a MAN fallback.
Also, once downloading is complete the ACP71 resets all outputs.
PROFIBUS definition data must be downloaded when the setting contents for the
PROFIBUS-DP configurator have been changed.
The following are some typical changes.
Adding a module to the slave device
Deleting a module from the slave device
Changing Set Details for the slave device
N2-58
Even if you change setting items other than copying the PROFIBUS definition data in the
ACP71 property sheet, communication with slave devices will not stop. This means that no
outputs will be reset.
However, data update for the interface with the FCU temporarily stops. During this time, the
connection destination function block changes to OOP and performs a MAN fallback.
The table below indicates the actions of devices when ACP71 properties are changed,
according to the status during online maintenance.
Table Actions when ACP71 Properties are Changed (1/2)
Status during online maintenance

Agreement
between
PROFIBUS
PROFIBUS
definition
definition
Operation
data
data and
downloaded? communication
I/O definitions
Action
Agreement
between
PROFIBUS
definition data
and slave
device
configuration
Agree
Do not agree
Downloaded
Data existing only

in communication
I/O definitions
Function
block
After download
ACP71
Function
block
Reads new
Input is IOP
Communication inputs
Output
with all slave
Output
performs MAN
devices stops performs
fallback
MAN fallback
Data in
agreement
Copied or
recopied
PROFIBUS
definition
data file
During download
Input retains
previous
value or IOP
Output
performs
MAN fallback
-(*3)
Do not agree
Reads new
inputs
Resets
outputs (*1)
No
Input is IOP
corresponding
Output
I/O
performs MAN
communication
fallback
(*2)
Communication
with all slave
devices stops
Agree
Data existing only
in PROFIBUS
definition data
ACP71
Reads new
inputs
Resets
outputs (*1)
-(*3)
No
corresponding
I/O
communication
(*2)
N020809E.EPS
*1:
*2:
*3:
When configured device is different from the slave device, all I/O communication to that slave device may not be
performed. For more information, see the devices manual.
There is no link to the function block, since there are no communication I/O definitions. Accordingly, the operation
remains unaffected.
N2-59

Table Actions when ACP71 Properties are Changed (2/2)

Agreement
between
PROFIBUS
PROFIBUS
definition
definition
Operation
data
data and
downloaded? communication
I/O definitions
Data in
agreement
Action
Agreement
between
PROFIBUS
definition data
and slave
device
configuration
Agree
Do not agree
Changed
ACP71's
Set Details
only
Not
downloaded
Data existing only

in communication
I/O definitions
During download
Function
block
ACP71
Function
block
Input retains
previous value
or become
IOP (*5) Output
performs MAN
fallback
Reads new
inputs
Outputs
previous
output value
Reads new
inputs
Output
performs
MAN fallback
Input is IOP
Output
performs
MAN fallback
(*4)
Input is IOP
No corresOutput
ponding I/O
performs
communication
MAN fallback
(*2)
(*4)
No corresponding I/O
communication
(*2)
Reads new
inputs
Outputs
previous
output value
Reads new
inputs
Outputs are
re-output
Agree
Data existing only
in PROFIBUS
definition data
(*3)
Do not agree
After download
communication
(*2)
ACP71
Reads new
inputs
Outputs are
re-output
(*3)
communication
(*2)
N020810E.EPS
*1:
*2:
*3:
*4:
*5:
performed. For more information, refer to the devices manual.
There is no link to the function block since there are no communication I/O definitions. Accordingly, the operation
remains unaffected.
Since there is no PROFIBUS definition data in the first place or since the data does not agree with the other conditions,
the status is already IOP/OOP even before downloading. Accordingly, there are no operation changes due to online
downloading.
This can be selected using [IOM Online Updating] in the FCS property sheet.
IMPORTANT
When properties are changed, the PROFIBUS definition data and ACP71 set details are
downloaded.
When download of PROFIBUS definition data has completed normally, but there is an error
in downloading of ACP71s set details, the database managed by System view returns to
the status prior to downloading.
Accordingly, the PROFIBUS definition data managed by system view does not match the
PROFIBUS definition data in the ACP71.
Execute an IOM download to the ACP71 to cancel changes made to the ACP71 property
sheet and return to the previous status.
To change the properties, recopy and download the PROFIBUS definition data.
N2-60
Changing Communication I/O Definitions

When changing the configuration of communication I/O, data update may be paused
between FCU and interface.
At this moment, the connected function blocks outputs may become OOP and fallback to
MAN mode.
The table below indicates the actions when communication I/O definitions are changed,
according to the status during online maintenance.
Table Actions when Communication I/O Definitions are Changed
Status of
PROFIBUS
PROFIBUS
definition
definition
data
data file downloaded?
Agreement
between
PROFIBUS
definition
data and
communication
I/O definitions
Data in
agreement
Action
Agreement
between
PROFIBUS
definition data
and slave
device
configuration
Agree
Do not agree
Copying
completed
Not
downloaded
Data existing only

in communication
I/O definitions
Data existing only Agree

in PROFIBUS
definition data
During download
Function
block
ACP71
Function
block
Input retains
previous value
or become
IOP (*1) Output
performs MAN
fallback
Reads new
inputs
Outputs
previous
output value
Reads new
inputs
Output performs MAN
fallback
Input is IOP
Output performs MAN
fallback
I/O data not

communicated
to the subject
device (*2)
No
Input is IOP
corresponding
Output perI/O
forms MAN
communication
fallback
(*2)
Reads new
inputs
Outputs
previous
output value
Reads new
inputs
Outputs previous output
value
(*3)
Do not agree
Data existing only
in communication
I/O definitions
Not copied
After download
Input is IOP
Output performs MAN
fallback
No
corresponding
I/O
communication
(*2)
(*3)
ACP71
Reads new
inputs
Outputs are
re-output
I/O data not

Input is IOP communicated
Output per- to the subject
forms MAN device (*2)
fallback
N020811E.EPS
*1:
*2:
*3:
This can be selected using [IOM Online Updating] in the FCS property sheet.
performed. For more information, refer to the devices manual.
There is no link to the function block since there are no communication I/O definitions. Accordingly, the operation
remains unaffected.
Deleting the ACP71s Definition

This section explains the actions when the ACP71 definition is deleted.
All function blocks linked to the ACP71s I/O data become IOP or OOP.
If fallback is not designated, the output status prior to the download is retained.
If fallback is designated, fallback is performed.
<N2.9 Messages>
N2-61
N2.9 Messages
In PROFIBUS-DP communication, the following messages are displayed for the
ACP71 or slave device.
System alarm messages
Fieldbus messages
<N2.9 Messages>
N2-62
N2.9.1 System Alarm Messages

List of Messages
The following messages concerning the ACP71 are notified from the system.
Table List of Messages
Number
Event
Message
Remarks
0081
IOM error
STNss IOM Fail UNIT mm SLOT nn
0082
IOM recovery
STNss IOM Recover UNIT mm SLOT nn
0089
Communication
STNss SS-COM Error UNIT mm SLOT nn STN zzz CODE=####
error
0090
Communication
STNss SS-COM Recover UNIT mm SLOT nn STN zzz
recovery
N020901E.EPS
STNss:
mm:
nn:
zzz:
####:
Station name
Unit number
Slot number
Node address
Error code
When a communication error occurs at a slave device, a system-alarm message is generated at the first occurrence only.
No further system-alarm messages will be generated, even if another error arises due to a
different cause.
<N2.9 Messages>
N2-63
Error Codes Used for Communication Errors

The error codes used for communication errors include the following two types:
Definition error
Communication error
Definition Error
The following errors occur when the contents set by the communication I/O definitions are
invalid.
If any of the following errors occurs, check the settings for the Communication I/O Builder.
Table Definition Errors
Error
code
Description
CAB1
Station number invalid
CAB2
Other device address invalid, cannot be interpreted
CAB3
Other device address invalid, illegal character string detected
CAB4
Excessive communication processing points
CAB5
Other device address invalid, slot number out of range
CAB6
Other device address invalid, entry data other than a numerical

value detected in the index
CAB7
Other device address invalid, index value out of range
CAB8
Other device address invalid, index value exceeding the specified

digits
CAB9
Other device address invalid, delimiter character invalid
CABA
Corresponding device (module or channel) not specified in

PROFIBUS definition data
CABB
Data type incorrect, input designated for output data
CABC
Data type incorrect, output designated for input data
CABD
Other device address invalid, entry data for slot number is not
a numerical value
CABE
CABF

(expansion symbol)
Action to take
following the error
Do not perform communication

for the definition causing the
error. Check the definition
content in the builder.
N020902E.EPS
Communication Error
The following errors occur when there is a communication error with the slave device or
there is a failure in the slave device.
Table Communication Error
Error
code
Description
CA91
I/O data is not being communicated
CA92
Configuration error
CA93
Slave device module error
Action to take
following the error
Retry communication
N020903E.EPS
<N2.9 Messages>
N2-64
N2.9.2 Fieldbus Messages

Fieldbus messages are displayed according to the Slave Diagnostic Information and
contents of the ACP71 self-diagnosis.
These messages are stored in the historical message save file.
The messages can be viewed from the Historical Message Report window or Message Monitor window.
Messages relating to errors defined by the PROFIBUS-DP specifications are displayed as text. However, the contents of device specific errors are displayed in the
form of an error code. Refer to the devices manual for the meaning of the error
codes.
A single slave diagnostic information stores multiple causes of an error. Thus,

several different messages may be displayed from a single slave diagnostic information.
List of Messages
Fieldbus messages are divided into the following categories:
Slave device common messages
Slave device specific messages
Messages for each module in the slave device
Messages for each channel in the slave device
ACP71 self-diagnostic messages
IMPORTANT
The ACP71 manages Error Occurrence/Recovery status relating to the fieldbus
messages.
Thus, if the ACP71 restarts after an error occurrence message has been relayed, a
normal recovery message will not be forwarded.
When an error larger than the communication frame size of the slave diagnostic
information occurs, the part that could not fit in the communication frame might not be
relayed as a message. The communication frame size of the slave diagnostic information depends on the slave device.
The part that does not fit into the communication frame is part of the error of a specific
channel.
In this case, only the message for each module and the error for each channel that fits
in the communication frame will be relayed.
<N2.9 Messages>
N2-65
Slave Device Common Messages

Slave-device common messages indicate errors defined by the PROFIBUS specifications,
and are shared by all slave devices.
These messages include errors detected by the ACP71 and errors detected by the slave
device.
Table List of Messages (1/2)
Number
Event
Error
detected by:
Message
3201
Locked by another
master device
STNss PB UNIT mm SLOT nn Station Alarm STN zzz ID 0xXXXX

Master_Lock (Master STN yyy)
3202
The above returned

to normal
STNss PB UNIT mm SLOT nn Station Recover STN zzz ID 0xXXXX

Master_Lock
3203
Parameter setting failed

Param_Fault
3204
The above returned

to normal

Param_Fault
3205
Received an illegal frame STNss PB UNIT mm SLOT nn Station Alarm STN zzz ID 0xXXXX
Invalid_Slave_Response
from the slave device
3206
The above returned

to normal
3207
Received a request for

an unsupported functions Not_Supported
3208
The above returned

to normal

Not_Supported
3209
Configuration error

Cfg_Fault
3210
The above returned

to normal

Cfg_Fault
3211
Cannot transmit data

Station_Not_Ready
3212
The above returned

to normal

Station_Not_Ready

Invalid_Slave_Response
ACP71
Slave device
ACP71
Slave device
Slave device
Slave device
N020904E.EPS
STNss:
XXXX:
yyy:
Station name, mm: unit number, nn: Slot number, zzz: node address
Ident Number (Hexadecimal: Displayed with 0x added at the top).
Node address of the master device locking the slave device
<N2.9 Messages>
N2-66

Error
detected by:
Number
Event
Message
3213
Slave device not present

on the communication line

Station_Non_Existent
3214
The above returned

to normal

Station_Non_Existent
3215
Slave device is missing

from the cyclic
transmission list

Deactivated
3216
The above returned

to normal

Deactivated
3217
Setting parameters or
checking configuration

Param_Req
3218
The above returned

to normal

Param_Req
3219
Expansion area for slave

diagnostic information
overflowed

Ext_Diag_Overflow
3220
The above returned

to normal

Ext_Diag_Overflow
ACP71
ACP71
Slave device
ACP71 or
slave device
N020905E.EPS
STNss:
XXXX:
yyy:
Node address of the master device locking the slave device
Messages relating to the slave device are displayed according to the interpretation results
of the top 3 bytes of the Slave Diagnostic Information defined by the PROFIBUS specifications.
The following bit indicates the presence/absence of device-specific diagnostic information,
module diagnostic information, and channel diagnostic information. When this bit is
marked, the slave-device specific messages and subsequent error messages will be
displayed.
The messages relating to this bit will not be displayed.
Ext_Diag: Slave Diagnostic Information has expansion data
<N2.9 Messages>
N2-67
Slave Device Specific Messages

Slave device specific messages indicate errors defined by the device manufacturer.
These messages display the Slave Diagnostic Informations Device Related portion as an
error code.
Error
detected by:
Number
Event
Message
3231
Slave device error occurred
STNss PB UNIT mm SLOT nn Device Related Alarm STN zzz ID

0xXXXX CODE = ZZZZZZZZZZ
3232
The above returned

to normal
STNss PB UNIT mm SLOT nn Device Related Recover STN zzz ID

0xXXXX
Slave device
N020906E.EPS
STNss:
XXXX :
ZZZZZZZZZZ:
Error code (Hexadecimal: Maximum 126 characters, with top 2 characters indicating the error code
length (byte length)).
Messages for Each Module in the Slave Device

Number
Event
Error
detected by:
Message
3241
Module error occurred
STNss PB UNIT mm SLOT nn Module Alarm STN zzz ID 0xXXXX

MODULE yy
3242
The above returned

to normal
STNss PB UNIT mm SLOT nn Module Recover STN zzz ID 0xXXXX

MODULE yy
Slave device
N020907E.EPS
STNss:
XXXX:
yy:
Module slot number (decimal)
Module slots are numbered starting with either 1 or 0, depending on the slave device.
The slot number is set to begin with 1 when designating the Communication I/O Builder.
However, in System View you can set the slot number to display in the message, starting
with 0.
<N2.9 Messages>
N2-68
Messages for Each Channel in the Module

Number
Event
Error
detected by:
Message
3251
short circuit
STNss PB UNIT mm SLOT nn Channel Alarm STN zzz ID 0xXXXX

MODULE yy CHANNEL ww short circuit
3253
undervoltage

MODULE yy CHANNEL ww undervoltage
3255
overvoltage

MODULE yy overvoltage
3257
overload

MODULE yy CHANNEL ww overload
3259
overtemperature

MODULE yy CHANNEL ww overtemperature
3261
link break

Slave device
MODULE yy CHANNEL ww link break
3263
upper limit value

exceeded

MODULE yy CHANNEL ww upper limit value exceeded
3265
lower limit value

exceeded

MODULE yy CHANNEL ww lower limit value exceeded
3267
error

MODULE yy CHANNEL ww error
3269
Other errors

MODULE yy CHANNEL ww Error Type = vvvv
3270
The above error returned STNss PB UNIT mm SLOT nn Channel Recover STN zzz ID 0xXXXX
MODULE yy CHANNEL ww
to normal
N020908E.EPS
STNss:
XXXX:
yy:
Module slot number (decimal), ww: Channel number (decimal), vvvv: Error type (decimal)
ACP71 Self-Diagnostic Messages

Number
Event
Error
detected by:
Message
3281
PROFIBUS
communication stop
STNss PB UNIT mm SLOT nn Communication Stop (*1)
3282
PROFIBUS
communication recover
STNss PB UNIT mm SLOT nn Communication Recover
ACP71
N020909E.EPS
STNss:
*1:
Station name, mm: Unit number, nn: Slot number

This message is relayed when the PROFIBUS communication section in the ACP71 stops independently. The
PROFIBUS communication section stops when Auto Clear is enabled and the slave device fails, or when a
hardware error is detected.
<N3. PROFIBUS-DP (ALP111)>
N3-1
N3. PROFIBUS-DP (ALP111)

The parts of the PROFIBUS-DPV1 specifications defined as extensions to the
PROFIBUS-DP specifications are implemented on the ALP111, which is an FIO
communication module. This section explains the communication between slave
devices and an FCS via PROFIBUS-DPV1, as well as the engineering tasks required.
IM 33S01B30-01E
10th Edition : Dec.18,2003-00
N3-2
N3.1 Overall Configuration

I/O data communication with slave devices via PROFIBUS-DPV1 using ALP111
modules is treated the same way as communication via PROFIBUS-DP using ACP71
modules.
This section explains the configuration and operating environment of the communication function for a CS 3000 system and PROFIBUS-DPV1 using ALP111 modules.
Configuration of Communication Function with PROFIBUS-DPV1

The figure below shows the general configuration of the communication function with
PROFIBUS-DPV1.
The System Builder, operation and monitoring, PROFIBUS-DPV1 communication, and one
or more PROFIBUS-DPV1 communication modules (ALP111) are included in the communication function with PROFIBUS-DPV1.
Export
PROFIBUS
definition
data file
PROFIBUS-DP
configurator
(manufactured by
Hilscher)
Copy
System Builder
System
View
Communication
I/O Builder

FCS Status
Display window
Function Block
Detail Builder
System Alarm
window
Historical
Message Report
window
Control bus
FCS
ALP111
operating status
Download
ALP111
Fail/Recover
message
Slave device
diagnostic
information
PROFIBUS-DPV1
communication function
I/O data
PROFIBUS-DPV1
communication module (ALP111)
PROFIBUS-DP
I/O data
Slave device supporting

PROFIBUS-DPV1 communication
Slave device
N030101E.EPS
Figure Overall Configuration of Communication Function with PROFIBUS-DPV1
IM 33S01B30-01E
N3-3
PROFIBUS-DP Communication Module (ALP111)

ALP111 modules communicate with slave devices and transfer sent or received I/O data to
the PROFIBUS-DPV1 communication function.
ALP111 modules can operate as master devices of class 1 or class 2 according to the
PROFIBUS-DPV1 specification.
The ALP111 modules can also acquire PROFIBUS-DPV1 diagnostic information, transmit
fieldbus messages, and map them to the data status. The ALP111 modules can be operated as dual-redundant master devices.
TIP
A class 1 master device refers to a master device that is always connected via PROFIBUS-DPV1 to
manage slave devices and perform I/O communication. The connection is established at all times for both
synchronous communication and asynchronous communication.
However, up to now, only the synchronous communication is supported.
A class 2 master device refers to a master device for maintenance that is connected via PROFIBUSDPV1 as needed. It is intended to be used to change settings of a slave device online and read/write the
internal parameters of the device. It is connected to a slave device on a one-to-one basis, and the
connection is established or cut when needed.
PROFIBUS-DPV1 Communication Function

This function exchanges I/O data via an ALP111 and stores the results in the communication I/O data area. Accordingly, as with the communication I/O modules, this function is
used to connect to the function block using Communication I/O.
When a request from an HIS to acquire the operating status of an ALP111 module is
received, the status of the ALP111 module is monitored and a message is transmitted upon
detection of a fail/recover.
PROFIBUS-DP Configurator (Product of Hilscher Co.)

The PROFIBUS configurator defines ALP111 modules and slave devices for PROFIBUSDPV1 communication, and exports the results of the definitions as a file in DBM format.
The PROFIBUS-DP configurator can be installed on the same PC equipped with System
builders, or on another PC.
System Builder
The following functions are provided by System Builder.
Copying the PROFIBUS definition data file from the PROFIBUS-DP configurator to an
internal folder.
Defining the settings related to data in ALP111 modules and slave devices from
Communication I/O Builder and downloading communication I/O definitions to the
FCS and ALP111 modules.
Specifying registration, modification, deletion and module dual-redundancy of ALP111
modules from System View. In addition, it is possible to download data to the ALP111
modules using IOM download.
Defining function-block output conversions from Function Block Detail Builder.
IM 33S01B30-01E
N3-4

The following operations are available via operation and monitoring console.
Downloading data to an ALP111 from the FCS Status Display window using IOM
download, and displaying the operating status of the ALP111 modules.
Checking fail/recover messages of an ALP111 from the System Alarm window.
Checking slave diagnostic information of devices from the Historical Message Report
window.
IM 33S01B30-01E
N3-5
N3.2 Operating Environment

This section explains the operating environment used to perform communication
with PROFIBUS-DPV1.
Operating Environment for Communication with PROFIBUS-DPV1

The following explains the hardware and software operating environment.
Hardware Environment
The following hardware environment is required for communication with PROFIBUS-DPV1.
Table Hardware Operating Environment
Type
Communication module
Hardware
Remarks
ALP111
N030201E.EPS
The following hardware is also required for communication. Use hardware that conforms to
the PROFIBUS-DPV1 and PROFIBUS-DP specifications.
Table Devices Required for Communication with PROFIBUS-DPV1
Type
Description
Slave device
Without repeaters: Maximum of 31 units/ALP111 (*1)

With repeaters: Maximum of 125 units/ALP111
Repeater
A device that connects multiple PROFIBUS-DPV1 segments

N030202E.EPS
*1:
A maximum of 32 units can be connected to a single PROFIBUS-DP segment, including master devices (ALP111) and
slave devices. This means that up to 31 slave devices (up to 30 devices when two ALP111 modules are installed in
dual-redundant configuration) can be connected when no repeaters are used. The use of repeaters allows the
connection of up to four segments.
Software Environment
The following optional packages are required for communication with PROFIBUS-DPV1.
LFS2542 PROFIBUS Communication Package (for ALP111)
IM 33S01B30-01E
N3-6
PROFIBUS-DP Configurator
A third-party configurator is required for PROFIBUS-DPV1 engineering.
System Configurator Version 2.881 or later versions (Product of Hilscher Co.) (*1)
*1:
Windows 2000 or Windows XP is required as the operating environment.
SEE ALSO
For more information about the operating environment, see the System Configurators Manual provided
by Hilscher Co.
TIP
To define slave devices with the PROFIBUS-DP configurator, a file (GSD file) that defined the device
specifications and setting data is required.
GSD files are either supplied by the device manufacturer or can be downloaded from the PROFIBUS
Organizations website.
IMPORTANT
To permit users that do not have Administrator privileges in Windows 2000 or Windows XP
environment to use the PROFIBUS-DP configurator, the following operations may be
required.
Add the user who will be running the PROFIBUS-DP configurator to the permission user list
for the folder in which the PROFIBUS configurator is installed and all subfolders/subfiles,
and set the Full Control permission for the user. By default, the PROFIBUS-DP
configurator files are installed under the following folder.
C:\Program Files\Yokogawa\SyCon
IM 33S01B30-01E
<N3.3 PROFIBUS-DPV1 Communication Module (ALP111)>
N3-7
N3.3 PROFIBUS-DPV1 Communication Module

(ALP111)
The PROFIBUS-DPV1 communication module (ALP111) is required for communication with PROFIBUS-DPV1.
This section explains the items related to the PROFIBUS-DPV1 communication
module (ALP111).
Number of modules that can be mounted
Nest configuration
Size of data that can be communicated
Number of assignable communication I/O definitions
Mounting Format
ALP111 can be installed in a local node of ESB bus node unit (such as ANB10S or
ANB10D)or in a remote node of ER bus node unit (such as ANR10S or ANR10D).
The maximum number of modules for installation is as follows:
When installing ALR111 to an ER bus node unit against one (or, in redundant configuration, one pair of) EB401 modules, up to 8 modules of ALF111, ALR111, ALR121,
ALE111 and ALP111 can be installed.
For one FCU, up to 16 modules of ALF111, ALR111, ALR121, ALE111 and ALP111
can be installed for non-redundant configuration; or 8 pairs of above modules for
redundant configuration.
Mounting Position
ALP111 modules can be mounted in slot No.1 to slot No.8 of an ESB bus node unit or an
ER bus node unit. ALP111 modules can be made dual-redundant by mounting them in two
adjacent slots (an odd numbered slot and the subsequent slot).
There is no restriction regarding combination with other FIO I/O modules and communication modules such as ALF111 and ALE111 in a node.
IM 33S01B30-01E
<N3.3 PROFIBUS-DPV1 Communication Module (ALP111)>
N3-8
Dual-Redundant Modules
The PROFIBUS-DPV1 specification permits dual-redundant master devices, slave devices
and buses. This system, which uses ALP111 modules, only supports dual-redundant
master devices (ALP111). Slave devices and buses are configured as single devices.
Host controller
ALP111 on the
controlling side
ALP111 on the
standby side
I/O communication
Diagnostic communication
Slave
device 1
Slave
device 2
Slave
device 3
N030301E.EPS
Figure Dual-Redundant Master Devices (ALP111)
IMPORTANT
Definitions in the PROFIBUS-DP configurator for dual-redundant ALP111 modules
are the same as when they are defined as single modules. The same definitions are
used on both the controlling side and the standby side.
The address of standby ALP111 module should use the address that equals to X-1 (X:
master device address specified by the PROFIBUS-DP configurator). So that when
using PROFIBUS-DP configurator to configure ALP111 into a dual-redundant
scheme, the address of the master device must be specified in the range of 2 to 125.
And all the slave devices must not have an address that identical with the address of
the standby ALP111.
Size of data that can be Communicated

The following indicates the size of data that can be communicated by an ALP111.
A maximum input and output data is 1000 words. There are no restrictions in how the 1000
words can be allocated to inputs and outputs.
Number of Assignable Communication I/O Definitions

A maximum number of communication I/O definitions that can be assigned to an ALP111 is
200.
IM 33S01B30-01E
<N3.4 I/O Data>
N3-9
N3.4 I/O Data

I/O data resulting from communication via an ALP111 is accessed from a function
block or Graphic window through the communication I/O data area.
This section explains the items relating to I/O data:
Data types supported by ALP111
How to define I/O data
How I/O data is stored in the communication I/O data area
How to treat I/O data as analog I/O data
How to treat I/O data as discrete I/O data
Reverse bits
Reverse bytes
Data status
Data update timing
I/O conversion with function block
Access using SEBOL
Data Types Supported by ALP111

Data types supported by the ALP111 are treated as follows in Communication I/O Builder
and the PROFIBUS-DP configurator.
Data Types that can be Set in Communication I/O Builder

A data type defines how the data from slave devices be treated in the control station (FCS).
Data type is specified for each communication data via the Communication I/O Builder.
Note that the data types that can be set are the same as for subsystem communication.
Table Data Types that can be Set in Communication I/O Builder
Classification
Input
Output
Name
Data type
16-bit signed integer data
I16
16-bit unsigned integer data
U16
I32
U32
32-bit signed floating point data
F32
Bit data (discrete input)
DI
I16
U16
I32
U32
32-bit signed floating point data
F32
Bit data (discrete output)
DO
N030401E.EPS
ALP111 modules may not guarantee simultaneous transmission of data of 32 bits or more;
do not use 64-bit floating point data types.
IM 33S01B30-01E
<N3.4 I/O Data>
N3-10
Data Definition in the PROFIBUS-DP Configurator

Data that can be handled by slave devices are represented as byte data or word data, and
corresponding sizes are set in the PROFIBUS-DP configurator.
However, this does not mean that slave devices support only two data types. Byte data or
word data indicates the minimum building block of the I/O data areas of slave devices. See
the manual of the slave device used for what types of data are stored in the I/O data area in
units of minimum building block x size.
How to Define I/O Data

There are the three main ways to define communication data for PROFIBUS-DPV1 in
Communication I/O Builder. Select and use an appropriate definition method according to
the data required in the given applications and the specifications of slave devices.
Specification for Each Channel

In this definition method, data for I/O channels of a slave device is specified for each I/O
channel. This method allows detecting errors of each channel and reflecting them in the
data status.
Requirements for Employing This Definition Method
The slave device used must support channel slave diagnostic information. Verify that
the slave device supports this information by referring to the manual. The channel data
must have the appropriate data type layout specified in the communication I/O definitions. Moreover, the head channel data of this layout must be the data of channel 0.
SEE ALSO
For mapping of I/O data to the communication I/O data area and further details of requirements for employing this definition method, see the following:
How to Treat I/O Data as Analog I/O Data (in the Case of Specification for Each Channel and Channel Batch Specification) in N3.4, I/O Data
For details on channel slave diagnostic information, see the following:
N3.5.1, Overview of Slave Diagnostic Information
Application of This Definition Method

Only data for necessary channels can be defined in the communication I/O data area
without reserving the data area for all the channels at once. Thus, some data area can
be saved.
IM 33S01B30-01E
<N3.4 I/O Data>
N3-11
Channel Batch Specification

In this definition method, data for a number of consecutive I/O channels of a slave device is
specified at one go. This method allows detecting errors of each channel and reflecting
them in the data status.
The channel data must have the appropriate data type layout specified in the communication I/O definitions. Moreover, the head channel data of this layout must be the
data of channel 0.
SEE ALSO
For mapping of I/O data to the communication I/O data area and further details of requirements for
employing this definition method, see the following:
How to Treat I/O Data as Analog I/O Data (in the Case of Specification for Each Channel and Channel Batch Specification) in N3.4, I/O Data

Since the data area for all the channels is reserved in the communication I/O data
area at once, the total number of communication data definitions per ALP111 can be
reduced.
Module Specification (Definition Method Common with ACP71)

In this definition method, a slave device module is specified, and all relevant data for the
module is specified in a batch. Errors are detected for the entire module and reflected in the
data status. With this specification method, it cannot detect errors of individual channels
and reflect them in the data status.
There are no special requirements to use this method.
Use this method to define data that does not fall under definitions by specification for
each channel or channel batch specification. For example, use this method when a
certain data type among data for one module is different from others. Since the data
area for all the channels belonging to a module is reserved in the communication I/O
data area at once, the total number of communication data definitions per ALP111 can
be reduced.
IM 33S01B30-01E
<N3.4 I/O Data>
N3-12
How I/O Data is Stored in the Communication I/O Data Area (in the Case
of Module Specification)
The basic method of storing 8-bit data (1-byte data) in the communication I/O area for
definition by module specification is the same as for ACP71.
SEE ALSO
For how I/O data is stored in the communication I/O data area, see the following:
How I/O Data is Stored to the Communication I/O data Area in N2.4, I/O Data
How to Treat I/O Data as Analog I/O Data (in the Case of Module Specification)
In the case of definition by module specification, I/O data can be treated as analog data in
the same way as for ACP71.
SEE ALSO
For how to treat I/O data as analog I/O data, see the following:
Treating I/O Data as Analog I/O Data in N2.4, I/O Data
How to Treat I/O Data as Discrete I/O Data (in the Case of Module Specification)
In the case of definition by module specification, I/O data can be treated as discrete I/O
data in the same way as for ACP71.
SEE ALSO
For how to treat I/O data as discrete I/O data, see the following:
Treating I/O Data as Discrete I/O Data in N2.4, I/O Data
IM 33S01B30-01E
N3-13
<N3.4 I/O Data>
How to Treat I/O Data as Analog I/O Data (in the Case of Specification for
Each Channel and Channel Batch Specification)
In the case of analog data, the data corresponding to one module among the I/O data
communicated with slave devices is regarded to be arranged from channel 0, and the data
position is calculated.
I/O data for one
slave device
I/O data (module 1)
16 bits
I/O data (module 2)
I/O data (channel 0)
%WW0049
%WW0051
%WW0053

I/O data (module 3)
N030402E.EPS
Figure Data Mapping of Analog Data (16 bits)
The data position corresponding to each channel number in a slave device is calculated by
the following calculation formula:
Data position = data size (*1) x channel number
*1:
Data size signifies the size of the relevant data type specified in Communication I/O Builder. It is given in units of bytes.
The following table lists the correspondence between data types and data sizes.
Table Correspondence between Data Types and Data Sizes
Data type
Data size (bytes)
Remarks
Analog input (16-bit signed integer data)
(*1)
Analog input (32-bit signed integer data)
Analog input (16-bit unsigned integer data)
Analog input (32-bit unsigned integer data)
Analog input (32-bit floating point data)
Analog input (64-bit floating point data)
(*2)
Analog output (16-bit signed integer data)
(*1)
Analog output (32-bit signed integer data)
Analog output (16-bit unsigned integer data)
Analog output (32-bit unsigned integer data)
Analog output (32-bit floating point data)
Analog output (64-bit floating point data)
(*1)
(*1)
(*2)
N030403E.EPS
*1:
*2:
If 8-bit data is expanded to 16-bit data by adding the extension ;E in Device & Address of Communication I/O
Builder, the data position is calculated by setting the data size as 1 byte.
ALP111 modules may not guarantee simultaneous transmission of data of more than 32 bits; do not use 64-bit floating
point data types.
IMPORTANT
Data can only be defined by channel specification (specification for each channel and
channel batch specification) when it has the structures shown above. Special data structures where multiple data types coexist cannot be defined by channel specification. Slave
devices with special data structures must be defined by module specification.
IM 33S01B30-01E
<N3.4 I/O Data>
N3-14
How to Treat I/O Data as Discrete I/O Data (in the Cases of Specification
for Each Channel and Channel Batch Specification)
How to treat Input Data as Discrete I/O Data
The data range that can be referenced from the communication I/O data area is the same
as the range that can be referenced in the definitions set by module specification.
While an area is reserved for each word in the case of communication I/O data, data for
several channels is packed in units of one to several bytes in the case of data received from
slave devices. Such packed data is allocated by an ALP111 according to definitions made
in Communication I/O Builder. In order to connect %WB data to a function block, use only
the bits corresponding to the specific channel number, among those assigned to the communication I/O data area.
Data on a slave device
Data for the size of the
%WB area is copied.
DI input position
00110110
11110000
[Bit positions of %WB]

00000000
01111111
12345678
90123456
00110110
11110000
%WB003301
For channel 0
Data for several

channels is packed.
00110110
11110000
%WB003502
For channel 1
00110110
11110000
%WB003703
For channel 2
00110110
11110000
%WB003904
For channel 3
00110110
11110000
%WB004816
For channel 15
N030404E.EPS
Figure Settings of Discrete Input Data
IM 33S01B30-01E
N3-15
<N3.4 I/O Data>
Output of Discrete Output Data

When discrete output data is output to a slave device, only 1 bit specified by the channel
number is output.
Only bits corresponding
to specific channel
numbers are extracted.
A bit corresponding to the

desired channel number
is specified in %WB.
Slave device
ALP111
FCS
Output data
Communication
I/O data area
Function block
1. . . . 1. . . 1
Output Data
%W Data
1. . . . . . . . . .
1. . . . . . . . . .
MV
Output Data
%W Data
. . . . . 1. . . .
. . . . . 1. . . .
MV
Output Data
%W Data
. . . . . . . . . .1
MV
. . . . . . . . . .1
N030405E.EPS
Figure Settings of Discrete Output Data
Channel numbers correspond to %WB numbers as follows.

%WB number starts from 1 while channel number starts from 0.
%WB number
10
11
12
13
14
15
16
%WW000n
10
11
12
13
14
15
%WW000n+1
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Channel number
N030406E.EPS
Figure Correspondence between Channel Numbers and %WB Numbers
IM 33S01B30-01E
<N3.4 I/O Data>
N3-16
Reverse Bits (Common to All Definition Methods)

When reverse bits is specified, data is treated in the same way as for ACP71 in all the
definition methods.
SEE ALSO
For explanation of data handling when reverse bits is specified, see the following:
Reverse Bits in N2.4, I/O Data
Reverse Bytes (Common to All Definition Methods)

When reverse bytes is specified, data is treated in the same way as for ACP71 in all the
definition methods.
SEE ALSO
For explanation of data handling when reverse bytes is specified, see the following:
Reverse Bytes in N2.4, I/O Data
Data Status
The data status related to PROFIBUS-DP communication is the same as subsystem
communication.
SEE ALSO
The data status is determined by the communication status and slave diagnostic information of a slave
device.
For details on data status, see the following:
Data Statuses Handled for Subsystem in J1.2, Subsystem Data Identification
For details on slave diagnostic information, see the following:
N3.5, Monitoring and Diagnosing Devices
Data Update Timing

Communication I/O data is refreshed based on the timing of a basic scan or high-speed
scan.
The data update timing can be set in the item Scan on Communication I/O Builder.
IM 33S01B30-01E
<N3.4 I/O Data>
N3-17
I/O Conversion Using a Function Block

I/O signals are converted in function blocks in the same way as for ACP71.
SEE ALSO
For I/O conversion with function blocks, see the following:
I/O Conversion Using a Function Block in N2.4, I/O Data
Access Using SEBOL

The use of a dedicated SEBOL statement allows access to I/O data communicated with
PROFIBUS-DP.
Use the ssread statement for reading and the sswrite statement and sswritebit statement
for writing.
SEE ALSO
For details on SEBOL, see the following:
H1, SEBOL Details
IM 33S01B30-01E
<N3.5 Monitoring and Diagnosing Devices>
N3-18
N3.5 Monitoring and Diagnosing Devices

The status of a slave device connected to PROFIBUS-DPV1 can be monitored by
receiving data from the slave device.
This section explains the items regarding how to determine the status of a slave
device.
Overview of slave diagnostic information
Assigning and referencing slave diagnostic information
Assigning and referencing device specific slave diagnostic information
Assigning and referencing module slave diagnostic information
Assigning and referencing channel slave diagnostic information
Assigning and referencing device communication status
IM 33S01B30-01E
N3-19
N3.5.1 Overview of Slave Diagnostic Information

Slave diagnostic information reports the details regarding the status of a device. The
following processing is performed when slave diagnostic information is detected by
the system.
The data status is set.
A fieldbus message is forwarded.
The following method is available for a user to perform special processing based on
slave diagnostic information.
Referencing as communication I/O data
Slave Diagnostic Information consists of the following four parts:
Device common slave diagnostic information
Device specific slave diagnostic information
Module slave diagnostic information
Channel slave diagnostic information
The contents of slave diagnostic information include items detected by a slave
device and items detected by an ALP111.
Items detected by the ALP111 include configuration mismatch with the slave device.
Contents of Slave Diagnostic Information

Slave diagnostic information contents of four parts, their contents are as follows:
Table Slave Diagnostic Information for a Slave Device
Type
Title
Error
detected by:
Description
Device common
slave diagnostic
information
Station_Status1-3.
Master_Add.
Ident_Number
Common slave diagnostic information defined by the

PROFIBUS specifications
ALP111 or
slave device
Device specific
slave diagnostic
information
Device related
diagnostic
Slave diagnostic information defined by the specifications

of each device
Slave device
Module slave
diagnostic
information
The presence of an error in a device module or I/O channel

is indicated with a bit. This bit indicates an error if even one
Identifier related
Slave device
(module) diagnostic of a module's I/O channels has experienced an error. (Bit
assignment depends on the specifications of the device.)
Channel slave
diagnostic
information
Channel related
diagnostic
Slave diagnostic information for a module's I/O channels.

Each I/O channel has a detail code (Error Type), such as
short circuit. Error Type includes items defined in the
PROFIBUS specifications and those defined by the
specifications of a slave device.
Slave device
N030501E.EPS
IM 33S01B30-01E
N3-20
Setting the Data Status (in the Case of Module Specification)

When an error has been detected in the common device diagnosis information or module
diagnosis information, the data status of corresponding data is set to LPFL.
When an error has occurred in a slave device, the status of all data concerning that slave
device is set to LPFL.
When an error has occurred in a module, the status of all data concerning that module is
set to LPFL.
The occurrence of an error reported in the device specific slave diagnostic information and
channel slave diagnostic information will not be reflected in the data status.
IM 33S01B30-01E
N3-21
IMPORTANT
When an error is detected in one channel of the modules, an error is set in all the data
status of the module containing that channel. Select Do not reflect module errors in
the data status at the System View, if you do not wish to set an error in all data states
simultaneously.
The bit assignment for module slave diagnostic information differs depending on the
specification of a slave device. For this reason, data status can be set only when the
following bits are assigned.
Data status cannot be set with any other bit assignment. In that case, select Do not
reflect module errors in data status at the System View.
Set whether or not to reflect a module error in the data status for each ALP111.
If any one of the slave devices connected to an ALP111 has a bit assignment other than the
one shown below, it will be necessary to select Do not reflect module errors in data status.
Relative address
7
0
0
Bit number
Header information
Size of module slave diagnostic information

Fixed according to the PROFIBUS specifications
7
Bit number
1
Slot 1 module
Slot 2 module
Slot 3 module
Slot 4 module
Slot 5 module
Slot 6 module
Slot 7 module
Slot 8 module
7
Bit number
2
Slot 9 module
Slot 10 module
Slot 11 module
Slot 12 module
Slot 13 module
Slot 14 module
Slot 15 module
Slot 16 module
N030502E.EPS
Note: The slot number may start with 0 in some devices, but these devices are treated the same way.
Figure Bit Assignment for Module Slave Diagnostic Information
IM 33S01B30-01E
N3-22
Setting the Data Status (in the Case of Specification for Each Channel
and Channel Batch Specification)
Errors detected in each channel of a slave device are reflected in the data status. Errors
detected by a slave device are notified to an ALP111 as diagnostic information using
communication frames different from the frames used for I/O data. Errors related to channels (channel slave diagnostic information) are included in this diagnostic information. This
channel slave diagnostic information is reflected in the data status of the corresponding I/O
data as channel error information. For this reason, if an error occurs only in a certain channel, the error may be handled as either IOP or OOP in individual function blocks that are
connected with the channel.
SEE ALSO
For other information related to error diagnosis in the case of specification for each channel and channel
batch specification, see the following:
Handling of Overflow Error (Common to All the Data Specification Methods) in N3.5.1, Overview of Slave Diagnostic Information
Slave device
ALP111
Input data
FCS
Communication
I/O data area
Function blocks
%W Data
PV
Input Data
(Ch. x)
Input Data
Diagnostic
information
Data Status
IOP
Data Status
Channel
diagnostic
information (Ch. x)
N030503E.EPS
Figure Error Diagnosis of Input Data

Slave device
ALP111
Output data
FCS
Communication
I/O data area
Function blocks
%W Data
MV
Output Data
(Ch. y)
Output Data
Diagnostic
information
Data Status
OOP
Data Status
Channel
diagnostic
information (Ch. y)
N030504E.EPS
Figure Error Diagnosis of Output Data
IM 33S01B30-01E
N3-23
Setting the Data Status of Discrete Input Data (in the Case of Specification
for Each Channel and Channel Batch Specification)
In the case of discrete input data, it is possible to select which channel slave diagnostic
information should be reflected in the data status by specifying a channel number in Communication I/O Builder.
Set the bit corresponding
to the channel number
in %WB.
Slave device
ALP111
FCS
Input data
Communication
I/O data area
Input Data
Output data for
several channels
are packed.
Input Data
Diagnostic
information
Data Status
Channel
diagnostic
information (Ch. x)
Input Data
Channel
diagnostic
information (Ch. y)
Channel
diagnostic
information (Ch. z)
Data Status
Input Data
Data Status
%W Data
Data Status
%W Data
Data Status
%W Data
Data Status
Function blocks
PV
IOP
PV
IOP
PV
IOP
N030505E.EPS
Figure Setting the Data Status of Discrete Input Data
IM 33S01B30-01E
N3-24
Setting the Data Status of Discrete Output Data (in the Case of Specification for Each Channel and Channel Batch Specification)
In the case of discrete output data, it is possible to select which channel slave diagnostic
information should be reflected in the data status by specifying a channel number in Communication I/O Builder.
Only bits corresponding
to the specific channel
numbers are extracted.
Slave device
Set the bit corresponding

to the channel number
in %WB.
ALP111
FCS
Output data
Communication
I/O data area
1. . . . 1. . . 1
Output data for
several channels
are packed.
Diagnostic
information
Channel
diagnostic
information (Ch. x)
Channel
diagnostic
information (Ch. y)
Channel
diagnostic
information (Ch. z)
Output Data
%W Data
1. . . . . . . . . .
1. . . . . . . . . .
Data Status
Data Status
Output Data
%W Data
. . . . . 1. . . .
. . . . . 1. . . .
Data Status
Data Status
Output Data
%W Data
..........1
..........1
Data Status
Data Status
Function blocks
MV
OOP
MV
OOP
MV
OOP
N030506E.EPS
Figure Setting the Data Status of Discrete Output Data
IM 33S01B30-01E
N3-25
Reflecting Channel Slave Diagnostic Information in the Data Status (in

the Case of Specification for Each Channel and Channel Batch Specification)
Reflection in the Data Status by Error Cause
All errors indicated in channel slave diagnostic information are handled as communication
errors (BAD, NRDY or LPFL), regardless of the actual causes of the errors. As a result, the
states of the corresponding function blocks become IOP or OOP.
Handling of Module Errors

If, for example, a module is removed from a slave device, a module error is notified in the
module slave diagnostic information only; channel slave diagnostic information is not
notified. In such cases, where the module error bit is turned on and there is no channel
slave diagnostic information for the module, all the channels of the module are considered
as erroneous.
Relationship with Operation Specification at Module Error Detection

For data defined by channel specification, the following check boxes of the ALP111 property sheet are invalid. Error diagnosis by channel slave diagnostic information always takes
the priority.
Slave Devices without Channel Slave Diagnostic Information

There is no point in defining data by specifying channels for slave devices that have no
channel slave diagnostic information. Perform this definition using the module specification
method.
IM 33S01B30-01E
N3-26
Handling of Overflow Error (Common to All the Data Specification Methods)

If multiple channel errors occur at the same time in one slave device, an overflow error may
occur as all the channel errors cannot be stored in the slave diagnostic information.
Errors are detected for each channel as follows when an overflow error occurs.
When Module Slave Diagnostic Information is Available

When slave diagnostic information includes module slave diagnostic information, all the
modules for which errors are indicated in the module slave diagnostic information are
considered erroneous regardless of the availability of channel slave diagnostic information.
When Module Slave Diagnostic Information is not Available

Some devices only notify the presence of overflow via Station Status when overflow occurs
and do not set the module slave diagnostic information.
For this reason, if the diagnostic information indicates only overflow, i.e., without module
slave diagnostic information, all the points of the device are considered erroneous.
IMPORTANT
The size of the channel slave diagnostic information area differs depending on the device. If
the number of erroneous channels exceeds the storage area allotted to channel slave
diagnostic information, subsequent channel slave diagnostic information is discarded.
Check the specifications of the slave device in use regarding whether or not channel errors
can be reliably detected.
Forwarding a Fieldbus Message

Slave diagnostic information from a slave device is forwarded as a fieldbus message.
The forwarded message is stored in the historical message log file and can be viewed from
the Historical Message Report window or the Message Monitor window.
SEE ALSO
For details on fieldbus messages, see the following:
N3.9.2, Fieldbus Messages
IM 33S01B30-01E
N3-27
N3.5.2 Assigning and Referencing Slave Diagnostic Information

Slave diagnostic information from a slave device can be referenced by assigning the
communication I/O definitions. However, since the data status is set and the fieldbus
message is forwarded under normal circumstances, there is no need to assign the
information in the communication I/O definitions.
This function should be used when you wish to use an application to perform a
special task based on the slave diagnostic information.
It is important to note the following when interpreting the slave diagnostic information.
You must have a thorough understanding of the specifications of PROFIBUS
and the devices in use.
Details on slave diagnostic information are described in the PROFIBUS specifications and device manuals. It is necessary to understand the contents of these
materials in order to interpret the slave diagnostic information correctly.
The simultaneity of slave diagnostic information is guaranteed for data of up to
four bytes.
In the communication I/O data area, to which slave diagnostic information is
assigned, the simultaneity of data is guaranteed for data of up to four bytes.
An error might not be detected if a normal recovery takes place after the occurrence of the error within a time period that is shorter than the FCS scan cycle.
How to Reference the Entire Slave Diagnostic Information as Communication I/O Data
The following shows how to reference all slave diagnostic information of a slave device as
communication I/O data.
Example of Assigning Slave Diagnostic Information

The slave diagnostic information data is assigned to the communication I/O data area,
starting with the head byte and occupying an area according to the size specification.
The following example designates the size of the slave diagnostic information as 3 (6 bytes)
and assigns data to %WW0101.
Bit numbers of %WB
%W area
01
08, 09
16
0,7
Bit number of each byte

of diagnostic data
%WW0101
%WW0102
%WW0103
Data (first byte)
Data (second byte)
Data (third byte)
Data (fourth byte)
Data (fifth byte)
Data (sixth byte)
N030508E.EPS
Figure Example of Assigning Slave Diagnostic Information
IM 33S01B30-01E
N3-28
Settings with Communication I/O Builder

To reference slave diagnostic information, perform the following settings in Communication
I/O Builder.
Table Settings in Communication I/O Builder
Item
Setting
Remarks
Size
1 to 128 (words)
Specify the size according to the data amount of the

area to be referenced.
Station
Node address of
slave device
Device & Address
"DIAG"
Data Type
Input (Discrete)
Reverse
No
N030509E.EPS
IM 33S01B30-01E
N3-29
N3.5.3 Assigning and Referencing Device Specific Slave

Diagnostic Information
Device specific slave diagnostic information in slave diagnostic information can be
referenced by assigning in the communication I/O data area. This section describes
an example of assigning device specific slave diagnostic information in the communication I/O data area and how to make the settings in Communication I/O Builder.
Example of Assigning Device Specific Slave Diagnostic Information in

the Communication I/O Data Area
Device specific slave diagnostic information is stored in the communication I/O data area
sequentially, starting from the head byte and occupying an area corresponding to the data
size specified in Communication I/O Builder. Refer to the manual of the device in use for a
detailed description of the contents of the device specific slave diagnostic information.
Bit numbers of %WB
%W area
01
08, 09
16
0,7
Bit number of each byte of device

specific slave diagnostic information
%WW0101
%WW0102
%WW0103
Data (first byte)
Data (second byte)
Data (third byte)
Data (fourth byte)
Data (fifth byte)
Data (sixth byte)
N030510E.EPS
Figure Example of Assigning Device Specific Slave Diagnostic Information
When ALP111 Detects Errors

In the following cases, an ALP111 determines that an error has occurred even if device
specific slave diagnostic information is not available in the slave diagnostic information. In
such cases, the previous value of the data stored in the communication I/O data area is
maintained.
When Errors Occur in Communication with Slave Devices

When slave devices become faulty or communication errors such as configuration errors
occur.
When Overflow Occurs

When slave diagnostic information overflows, and device specific slave diagnostic information is not available.
IM 33S01B30-01E
N3-30
Settings Items in Communication I/O Builder

The following settings must be made in Communication I/O Builder when assigning device
specific slave diagnostic information in the communication I/O data area.
Table Settings for Assigning Device Specific Slave Diagnostic Information
Item
Setting
Size
1 to 32 (words)
Station
Node address of
slave device
Device & Address
"DIAG_DEV"
Data Type
Input (Discrete)
Reverse
No
Remarks
N030511E.EPS
IM 33S01B30-01E
N3-31
N3.5.4 Assigning and Referencing Module Slave Diagnostic

Information
Module slave diagnostic information in slave diagnostic information can be assigned in the communication I/O data area for use as reference data. This section
provides an example of assigning module slave diagnostic information in the communication I/O data area and how to make the settings in Communication I/O
Builder.
Example of Assigning Module Slave Diagnostic Information in the Communication I/O Data Area
Module slave diagnostic information is stored in the communication I/O data area sequentially, starting from the head byte and occupying an area corresponding to the data size
specified in Communication I/O Builder, in the same way as for device specific slave diagnostic information.
Refer to the manual of the device used for a detailed description of the contents of the
module diagnostic information.

In the following cases, an ALP111 determines that an error has occurred even if module
slave diagnostic information is not available in the slave diagnostic information. In such
cases, all the bits corresponding to data in the communication I/O data area are set to 1
(handled as errors).
When Errors Occur in Communication with Slave Devices

occur.

When slave diagnostic information overflows, and module slave diagnostic information is
not available.
Settings Items in Communication I/O Builder

The following settings must be made in Communication I/O Builder when assigning module
slave diagnostic information in the communication I/O data area.
Table Settings for Assigning Module Slave Diagnostic Information
Item
Setting
Size
1 to 32 (words)
Station
Node address of
slave device
Device & Address
"DIAG_MOD"
Data Type
Input (Discrete)
Reverse
No
Remarks
N030512E.EPS
IM 33S01B30-01E
N3-32
N3.5.5 Assigning and Referencing Channel Slave Diagnostic

Information
Channel slave diagnostic information in slave diagnostic information can be assigned in the communication I/O data area for use as reference data. This section
provides an example of assigning channel slave diagnostic information in the communication I/O data area and how to make the settings in Communication I/O
Builder.
Example of Assigning Channel Slave Diagnostic Information in the Communication I/O Data Area
Channel slave diagnostic information can reference multiple consecutive channels within
the same module with one definition.
The actual size of slave diagnostic information of one channel is three bytes, but an area of
two words (four bytes) is used for slave diagnostic information of one channel when the
information is mapped to the communication I/O data area. The value of the fourth byte is
always 0.
See the manual of the device in question for a detailed description of the contents of the
channel slave diagnostic information.
Bit numbers of %WB
%W area
01
08, 09
16
0,7
Bit number of each byte of channel

slave diagnostic information
%WW0101
%WW0102
%WW0103
Data (first byte)
Data (second byte)
Data (third byte)
Data (first byte)
Data (second byte)
Data (third byte)
First channel slave

Second channel slave
N030513E.EPS
Figure Example of Assigning Channel Slave Diagnostic Information
Values of channel slave diagnostic information are stored as follows in the communication I/
O data area.
Table Values of Channel Slave Diagnostic Information
Status
Data item
Normal
Value of first byte
Value of second byte
Value of third byte
Value of fourth byte
Error is notified by channel

ALP111 detected errors (*1)
slave diagnostic information
0
Data received from a slave
device is set as is.
0
0xFF
0
N030514E.EPS
*1:
Errors detected by an ALP111 are explained in the following.
IM 33S01B30-01E
N3-33

In the following cases, channel slave diagnostic information may not be notified from a
slave device. An application cannot judge that an error has occurred if nothing is done. For
this reason, an ALP111 determines that an error has occurred in these cases and stores
data in the communication I/O data area.
When Errors Occurs in Communication with Slave Devices

occur, an ALP111 treats them as erroneous.

An ALP111 treats all the channels of a module for which an error is indicated by module
slave diagnostic information as erroneous.
Moreover, an ALP111 treats all the channels of all the modules as erroneous if it receives
slave diagnostic information without module slave diagnostic information.
When a Module is Removed

If there is a module error and there is no channel slave diagnostic information, an ALP111
regards it as an error for all the channels of a module that was removed, etc. In this case, all
the channels of the module are handled as erroneous.
IM 33S01B30-01E
N3-34
Items Specified in Communication I/O Builder

To assign channel slave diagnostic information in the communication I/O data area, it is
necessary to specify the slot number and channel number of a module.
It is possible to reference channel slave diagnostic information of consecutive channels in
the range specified by the size starting from the channel number specified here.
The following settings must be made in Communication I/O Builder when assigning channel slave diagnostic information in the communication I/O data area.
Table Settings for Assigning Channel Slave Diagnostic Information
Item
Setting
Size
1 to 128 (words)
Station
Node address of a
slave device
Device & Address
See the table below.
Data Type
Input (Discrete)
Reverse
No
Remarks
Specify the size as (number of consecutive channels
to be referenced) x 2 (words).
N030515E.EPS
The table below lists how to define Device & Address (8 single-byte alphanumeric characters) shown in Table Settings for Assigning Channel Slave Diagnostic Information.
Table How to Define Device & Address
Definition
Description
Example
Slot number
Specify the slot number of a module of a slave device. Describe them

after the identifier "D" in the range of 1 to 60.
D3
Index
Specify an index of a module in the range 1 to 60 after "-."
Semicolon (;)
A semicolon divides parts of module specification and expansion part

including channel specification.
D3-1;1
Channel number
Specify the channel number of a module in the range 0 to 99. If this is

omitted, the channel number is regarded as 0.
D3-1;1
D3-1
N030516E.EPS
Syntax
Dmm-nn;xx (mm: slot number of a module, nn: index, xx: channel number)
Example of definition (in the case of the module slot number is 3 and channel number is 1)
D3;1
IM 33S01B30-01E
N3-35
N3.5.6 Assigning and Referencing Device Communication Status

The states of slave devices defined in the PROFIBUS-DP configurator can be assigned to communication I/O definitions. By doing so, the status of a slave device
can be used to update the Graphic window or output a message for sequence control.
The response status of a single slave device is indicated with one bit.
The response states of all slave devices can be assigned using a single communication I/O definition.
Correspondence with Element Numbers

When assigning communication states of slave devices to the communication I/O data
area, the states are assigned to element numbers (%WB) in the same as in the case of the
ACP71.
SEE ALSO
For the correspondence with element numbers (%WB) when communication states of slave devices are
assigned to the communication I/O data area, see the following:
Correlation to the Element Number in N2.5.1, Assigning and Referencing a Slave Device

To monitor the communication states of slave devices, perform the settings in the Communication I/O Builder shown below.
Table Settings in Communication I/O Builder
Item
Setting
Size
1 to 8
Station No.
Node address of an ALP111
Remarks
Specify according to the number of slave devices.
Device & Address "STATUS"

Data Type
Input (Discrete)
Reverse
Bits
N030517E.EPS
IM 33S01B30-01E
<N3.6 Engineering>
N3-36
N3.6 Engineering
Engineering tasks are broadly classified into two categories: tasks performed in
System Builder and tasks performed using the PROFIBUS-DP configurator.
This chapter provides an overview of the PROFIBUS-DP engineering, including
engineering of ALP111 modules, and explains the operations performed with the
PROFIBUS-DP configurator and System Builder.
IM 33S01B30-01E
<N3.6 Engineering>
N3-37
N3.6.1 Engineering Overview

Engineering tasks for PROFIBUS-DP can be divided into the following categories,
according to the operation process:
Engineering using System Builder
Engineering using the PROFIBUS-DP configurator
This section explains the outline of engineering.
Engineering Scope
The following figure and table show the scope and targets for PROFIBUS engineering.
HIS
Control bus
FCS
Area engineered
with System Builder
FCS
ALP111
Slave
device
Area engineered
with the PROFIBUS-DP
configurator
Slave
device
N030601E.EPS
Figure Engineering Scope

Table Engineering Target
Engineering target
System Builder
HIS
FCS
ALP111
Slave device
PROFIBUS-DP
configurator

N030602E.EPS
:
Applicable
Blank: Not applicable
Engineering of ALP111 modules is performed using the PROFIBUS-DP configurator and

System Builder. To perform this engineering, a separate operation is required to allow
System Builder to use PROFIBUS definition data created with the PROFIBUS-DP
configurator.
IM 33S01B30-01E
<N3.6 Engineering>
N3-38
About ALP111 Engineering

The PROFIBUS-DP configurator is used to create PROFIBUS-DPV1 communication
information and device configuration information.
To link PROFIBUS-DP I/O data to a function block, the element number (%WW or %WB)
defined in Communication I/O Builder must be linked to the PROFIBUS definition data of
the PROFIBUS-DP configurator.
These links can be defined by entering a part of the PROFIBUS definition data defined in
the PROFIBUS-DP configurator in Communication I/O Builder.
Once the links are established, the ALP111 for which the links are defined will begin operating.
Downloading PROFIBUS Definition Data

PROFIBUS definition data created with the PROFIBUS-DP configurator is downloaded to
an ALP111 using System Builder.
To download the data, it is necessary to export the PROFIBUS definition data using the
PROFIBUS-DP configurator and copy that data file to an appropriate folder where System
Builder can access it.
Copying is executed from the ALP111 property sheet in System View. The PROFIBUS
definition data is downloaded to the ALP111 by clicking the OK button in the property sheet
after copying, or when an IOM download operation is executed.
When the definitions stored in the ALP111 are deleted, the PROFIBUS definition data is
deleted as well.
PROFIBUS
definition data file
PROFIBUS-DP
configurator
System Builder
Export
Copy
Control bus
Download
FCU
ALP111
ALP111
PROFIBUS-DP
Slave device
Slave device
N030603E.EPS
Figure Downloading PROFIBUS Definition Data
IM 33S01B30-01E
<N3.6 Engineering>
N3-39
IMPORTANT
The PROFIBUS definition data file stores the data downloaded to an ALP111, but is
not a database where PROFIBUS-DP project data is stored. Thus, the PROFIBUS-DP
project cannot be edited from the PROFIBUS definition data file.
Download of data to a slave device does not involve PROFIBUS-DP.
The PROFIBUS definition data contains setting information for slave devices as well.
This setting information is set in a slave device from an ALP111 when the ALP111 or
the slave device starts up.
Do not download PROFIBUS definition data from the PROFIBUS-DP configurator directly
to an ALP111.
The PROFIBUS-DP configurator has a function to download PROFIBUS definition data
directly via the ALP111s RS port. However, do not use this function, since the following
problems will occur if it is used:
During the PROFIBUS definition data download operation, all PROFIBUS-DP communications stop and all I/O data becomes IOP/OOP.
It is not guaranteed that PROFIBUS definition data has been copied correctly to
System Builder. While data is being downloaded from the System Builder, PROFIBUS
definition data in an ALP111 may be rewritten as different data or may be deleted.
IM 33S01B30-01E
N3-40
<N3.6 Engineering>
Engineering Procedures
The following chart shows the basic engineering procedures using System Builder and the
PROFIBUS-DP configurator.
Settings in System Builder can be performed along with settings in the PROFIBUS-DP
configurator.
(1)
System design
Engineering operations
with System Builder

the PROFIBUS-DP configurator
(2)
Input and export with the
(3)
Copy the ALP111 definitions and
the PROFIBUS definition data file
(4)
Assign the communication I/O
definition to the element number
(5)
Link to a function block
using Control Drawing Builder
Operations not
involving an FCS
Operations
involving an FCS
(6)
Debug using the test function
(7)
Download
(8)
Debug PROFIBUS-DP
communication
(9)
Check for errors
END
N030604E.EPS
Figure Engineering Procedures
IM 33S01B30-01E
<N3.6 Engineering>
N3-41
System Design
Design the function-block configuration including slave devices, communication specifications and control specifications.
Input and Export with the PROFIBUS-DP Configurator

Input design information (slave-device configuration, slave-device module configuration,
communication-information definitions) in the PROFIBUS-DP configurator, then export the
completed project.
Copy the ALP111 Definitions and the PROFIBUS Definition Data File
Define the ALP111 in System View. Copy the PROFIBUS definition data file using the
ALP111 property sheet.
Note, however, that no error will occur even if the PROFIBUS definition data file is not
copied at this stage. Therefore, make sure to copy the PROFIBUS definition data file prior
to downloading.
Assign the Communication I/O Definition to the Element Number

Assign the communication I/O definition for the ALP111 to the element number. Define the
same settings as the PROFIBUS-DP configurator settings.
Link to a Function Block Using Control Drawing Builder

Link the element number for the communication I/O definition to a function block using
Control Drawing Builder.
Debug Using the Test Function

Use the test function to debug the FCS application. I/O isolation and wiring can be performed.
The following operations can be done for isolated I/O.
Direct data input to the communication I/O data area
Wiring between the designated communication I/O data
Download
Download the engineered information to the FCS and ALP111.
PROFIBUS definition data is not downloaded during an offline download operation. To
download PROFIBUS definition data, execute an IOM download operation for the ALP111
following the offline download.
Debug PROFIBUS-DP Communication

Connect the ALP111 and slave devices, then debug the PROFIBUS-DP communication
using the PROFIBUS-DP configurator.
Check for Errors

If there is an error in the assignment of communication I/O definitions to element numbers,
a system alarm will be generated when the ALP111 is started.
At this point, check to see that no system alarm has been generated.
IM 33S01B30-01E
<N3.6 Engineering>
N3-42
N3.6.2 Operations with the PROFIBUS-DP Configurator

This section explains the following items regarding operations using the PROFIBUSDP configurator.
SEE ALSO
For detailed information on how to use the PROFIBUS-DP configurator and the associated debugging
operations, refer to the included PROFIBUS-DP Configurator Users Manual.
Procedure for Creating a New Project

1.
Create a project.
The project herein refers to a database that comprises 1 segment of PROFIBUSDPV1.
2.
Read the GSD file for the device to be used.
3.
Define an ALP111.
To define an ALP111, select ALP111 from the master device selection menu.
4.
Define a slave device. If multiple modules can be set for the slave device, assign the
modules.
Set definitions specific to each slave device, if necessary.
5.
Save the project and then export it into a file.

The PROFIBUS configuration data file is created.
IM 33S01B30-01E
<N3.6 Engineering>
N3-43

1.
Open the project in question.
2.
Add, delete or change slave devices or modules of slave devices.
3.
Save the project and then export it into a file.

The PROFIBUS configuration data file is created.
IMPORTANT
Do not change any settings related to an ALP111 from the default values in the
PROFIBUS-DP configurator. The ALP111 may not function properly if any of the
settings is changed.
When setting bus parameters, make sure the Auto Clear item is set to OFF (default).
If Auto Clear is set to ON, the ALP111 module stops communication with all the slave
devices on the PROFIBUS-DP bus when any of the devices fails or any malfunction
event occurs. In this case, all inputs and outputs of the ALP111 become IOP or OOP.
To recover from the IOP or OOP status, it is necessary to execute an IOM download
operation.
TIP
A PROFIBUS configuration data file must be created to modify even a single setting item of the
PROFIBUS-DP configurator. If you have performed any of the following operations, change the settings
using the procedure explained in this section.
Adding a module to a slave device
Deleting a module from a slave device
Changing detail settings for a slave device
IM 33S01B30-01E
<N3.6 Engineering>
N3-44
N3.6.3 Operations in System View

This section explains the following items regarding operations in System view.
Procedure for Creating a New IOM

1.
Select the IOM folder in System View, and select [New] and then [Node] from the File
menu. The Create New Node dialog box appears. Create a node in order to create an
ALP111.
SEE ALSO
For details on the settings on the Create New Node dialog box, see the following:
Creating a New Node: KFCS2/KFCS/FFCS in F1.5.1, Creating a Node
2.
Select the newly created NODExx folder, and select [New] and then [IOM] from the
File menu. The Create New IOM dialog box appears.
3.
In the Create New IOM dialog box, select PROFIBUS-DPV1 Communication in

[Category] and PROFIBUS-DPV1 Communication (ALP111) in [Type] on the Type
and Position tab.
4.
Set detail definitions for an ALP111 on the Set Details tab.
5.
Click the Copy button in [PROFIBUS configuration data file] on the Set Details tab. The
Open dialog box appears.
6.
Select the PROFIBUS configuration data file from the Open dialog box, and click the
OK button. The PROFIBUS configuration data is copied.
7.
Click the OK button in the Create New IOM dialog box. The Create New IOM dialog
box closes.

1.
In System view, select an ALP111 for which you wish to change the settings. Then,
select [File] and [Properties] to display the property sheet.
2.
Display the Set Details tab in the property sheet, then change the settings as required.
3.
If any change has been made to the settings of the PROFIBUS-DP configurator, click
the Copy button in [PROFIBUS configuration data file]. The Open dialog box appears.
If there are no changes, skip step 4 and go to step 5.
4.
Select the PROFIBUS configuration data file from the Open dialog box, and click the
OK button. The PROFIBUS configuration data file is copied.
5.
Click the OK button in the property sheet. The property sheet closes.
IM 33S01B30-01E
<N3.6 Engineering>
N3-45
Details of System View

This section explains details of System View, in particular, the ALP111 properties and IOM
download function.
Create New IOM Dialog Box

The following table lists the contents of the dialog box displayed for creating a new IOM.
Table Contents of the Create New IOM Dialog Box
Tab
Item
IOM Type
Installation position
Detail
Remarks
Category
Select PROFIBUS-DPV1 Communication.
Type
Select PROFIBUS-DPV1 Communication (ALP111).
Slot
1 to 8 slots can be selected

Two adjacent ALP111 modules (in an odd numbered slot
and the subsequent slot) can be made dual-redundant for
the ALP111 in an odd numbered slot only.
Type
Duplicate Next Card
and
Position
Cannot be selected
Output Type
High Speed Read
IOM Comment
N030605E.EPS
Create New IOM

Type and Position
Set Details
IOM Type
Category
Profibus-DPV1 Communication
Type
ALP111(Profibus-DPV1 Communication)
Slot
Duplicate Next Card

Output Type
Output in a lump
Output immediately
High Speed Read

IOM Comment
OK
Cancel
N030606E.EPS
Figure Create New IOM Dialog Box (with ALP111 Selected)
IM 33S01B30-01E
<N3.6 Engineering>
N3-46
ALP111 Properties
Perform Fallback, Action when Module/Channel Fail Detected, PROFIBUS Configuration Data File,
Command
The table below lists the contents of the ALP111 property sheet.
Table ALP111 Property Sheet
Tab
Item
Change
IOM Type
Type
and
position Duplicate Next Card
High Speed Read
IOM Comment
Detail
Remarks
Category
PROFIBUS-DPV1 Communication
Type
PROFIBUS-DPV1 Communication (ALP111)
Slot position (S)

Same setting as the Create New IOM dialog box

IOM Category
Display settings defined in the Type and Position tab.
IOM Type
Slot
Fallback operation is enabled/disabled by the check box.

By default, the setting is enabled (the box is checked).

Perform Fallback
Action when
module/channel
fail detected
Set
Details
All points maintain

Current values
Reset all outputs

module input data to
IOP (*1)
The action to be taken upon the detection of module

failure is determined by the check box. By default, the
setting is disabled (the box is not checked).

module input data to
OOP (*1)
The action to be taken upon the detection of module

failure is determined by the check box. By default, the
setting is enabled (the box is checked).
Head of Slot numbers of

0 or 1 can be selected. The default value is 1.
Slave Device in Message
DPV1 Process Alarm from

Not supported.
Slave Device is notified
The check box setting is ignored.
as System Alarm
File Name
Displays the file name. Cannot be selected. The

default is blank. Updated after the Copy button is clicked.
Creation date
Displays the time and date file was created. Cannot

be selected. The default is blank. Updated after the
Copy button is clicked.
Date copied
Displays the time and date the Copy button was clicked.
Cannot be selected. The default is blank. Updated after
the Copy button is clicked.
[Copy]
Clicking the Copy button displays the file selection

dialog box and copying is executed. (*2)
The filename extension is DBM.
Command Line
A character string of
up to 32 characters
The default is blank. No settings are required.
[default]
PROFIBUS
configuration
data file
Tab
Fallback operation is determined by the option button.

The default setting is All points maintain Current value.
Item
Change
The value set for each item is restored to the default

value (except for detail items relating to the PROFIBUS
configuration data file).
Detail
Remarks
N030607E.EPS
:
Can be changed even after a new IOM has been created.
Blank: Cannot be changed once a new IOM has been created.
*1:
Valid when defining I/O data of slave devices using the module specification method.
*2:
The PROFIBUS configuration data is downloaded when the OK button in the property sheet is clicked after the data
has been copied. Clicking the Cancel button in the property sheet after copying invalidates the file that was copied and
restores the previously copied file.
IM 33S01B30-01E
N3-47
<N3.6 Engineering>
Properties
Type and Position
Set Details
IOM Category
Profibus-DPV1 Communication
IOM Type
ALP111(Profibus-DPV1)
Slot
1
Perform Fallback
Reset all outputs
Action when module/channel fail detected

DPV1 Process Alarm from Slave Device is notified as System Alarm
Head of Slot numbers of Slave Device in Message
This function is not supported.
PROFIBUS configuration data file

File Name
Creation date
Date copied
Copy
Command(L)
Default
OK
Cancel
N030608E.EPS
Figure ALP111 Property Sheet
IOM Download
During IOM download, the following data is downloaded to the ALP111.
ALP111 program
IOM download can be executed by selecting [Load] and then [Download to IOM] from
System View.
IMPORTANT
The IOM Download Start/Complete system alarm is generated for both the PROFIBUS
definition data and ALP111 program. In this case, the correspondence with data to be
downloaded can be checked by the messages in the IOM download dialog box.
The ALP111 program is downloaded only when creating a new IOM or executing IOM
download.
TIP
When downloading PROFIBUS configuration, the following system alarms may occur. Since these alarm
messages are triggered by the loading procedures, they do not indicate the occurrence of abnormality.
STNss configuration Error FIO k NODE mm SLOT nn (*1)
STNss SS-COM Error FIO k NODE mm SLOT nn PORT00 STN 255 code = C58A (*1)
*1:
STNss: Station name, k: Bus system number, mm: Node number, nn: slot number
IM 33S01B30-01E
<N3.6 Engineering>
N3-48
N3.6.4 Operations in Communication I/O Builder

This section explains the procedures and setting items concerning operations in
Communication I/O Builder.
When the definitions made in the PROFIBUS-DP configurator are not consistent with
the settings defined by Communication I/O Builder, inconsistent I/O data is set as
IOP or OOP. Consistent data can be handled normally.
Additionally, a system alarm related to slave devices containing inconsistent definitions is forwarded.
An example of a cause of inconsistency is that a module designated in Device &
Address does not exist in the PROFIBUS definition.
Operation Procedure
Perform the operations in Communication I/O Builder according to the following procedure.
1. Set the common setting items, then assign the communication I/O data area for the
ALP111 in use.
2. Set communication I/O definitions for each module of slave devices.
Common Setting Items in Communication I/O Builder

The following table lists the common items for defining a single ALP111 in Communication
I/O Builder.
Items other than the common items are set for each module of slave devices.
Table Common Setting Items in Communication I/O Builder
Item
Description
Buffer
Designate the size of the area for storing communication I/O definition data
to be used in an ALP111. The maximum value of the size is 1000.
Program Name
Designate the installation position of an ALP111 (Kl-n-s, l: bus system number,

n: node number, s: slot number) and the program name (PROFIBUS).
Example: When the module is installed on FIO bus system 1, node 2 and slot 4
K1-2-4PROFIBUS
N030609E.EPS
IM 33S01B30-01E
N3-49
<N3.6 Engineering>
Communication I/O Definition Items Set for each Module of Slave Devices
Data to be Reflected from the PROFIBUS-DP Configurator to Communication I/O Builder
In order to establish links between the definitions for PROFIBUS-DP created via the
PROFIBUS-DP configurator and the communication I/O definitions, a part of the settings
made with the PROFIBUS-DP configurator must be reflected in the settings of Communication I/O Builder.
The data that must be reflected in the settings of Communication I/O Builder is contained in
the Slave Configuration dialogue of the PROFIBUS-DP configurator. The table below lists
that data.
Table Data that Must be Reflected in the Settings
Item
Description
Remarks
Station
Address
Slot
Slot number defining a module
Serial number starting from 1, no blank

spaces between digits.
Idx
Index of data in a module
Reflected when a single module has

multiple I/O data.
N030610E.EPS
IM 33S01B30-01E
N3-50
<N3.6 Engineering>

Slave Configuration
General
Device
Description
COM-DPS
Slave#2
Station address
Cancel

368
244
244
24
Byte
Byte
Byte
GSD file
Module
32 word input [0x40, 0x5F]
1 word output [0x60]
16 word output [0x6F]
Symbol
Module#1
Module#2
Module#3
Module#4
Module#5
Module#6
Module#7
Parameter Data...
HIL_7501.GSD

Number of modules
Inputs Outputs In/Out

64 byte
1 word
2 word
3 word
4 word
8 word
Module
64 byte output con [0x80, 0xBF]
Slot Idx
1
1
1
2
1
3
1
4
1
5
1
6
1
7
OK
111
69
42
7
Byte
Byte
Byte
Master#1
Identifier
0x80, 0xBF
0xE0
0xE1
0xE2
0xE3
0xE7
Type 1 Addr. 1 Len. Type

IB
0
1
IB
0
4
QW
IW
0
32
QW
QW
QW
Assigned master
Station address 1
1/ALP111
Actual slave
Station address 2
Slave#2
2/COM-DPS
0 Addr. 0 Len.
Append Module
0
Remove Module
0
0
0
1
16
2
Symbolic Names
Insert Module
Module slot number
N030611E.EPS
Figure Slave Configuration Dialogue
The figure below shows an example of a dialogue for a module containing multiple indexes.
Slave Configuration
General
Device
Description
BusCon
Slave#3
Station address
OK
Cancel

Byte
Byte
Byte
GSD file
Parameter Data...
EBH82079.GSD

244
244
244
1

Number of modules
226
210
16
1
Module
H&B Var.80
Inputs Outputs In/Out Identifier

1 Word
8 Word 0xD0, 0xF7, 0xDB,
Byte
Byte
Byte
Assigned master
Station address 1
Master#1
1/ALP111
Actual slave
Station address 3
Slave#3
3/BusCon
Slot Idx
1
1
1
2
1
3
1
4
1
5
1
6
1
7
Module
H&B Var.80
H&B Var.80
H&B Var.80
H&B Var.80
H&B Var.80
H&B Var.80
H&B Var.80
Symbol
Module#1
Module#1
Module#1
Module#1
Module#1
Module#1
Module#1
Type
IW
IW
IW
IW
IW
IW
IW
1 Addr. 1 Len. Type 0 Addr. 0 Len.

0
1
0
8
QW 0
8
0
12
0
12
0
12
0
12
0
12
Index of data inside the module
Append Module
Remove Module
Insert Module
Symbolic Names
N030612E.EPS
Figure Slave Configuration Dialogue (With Multiple Indexes)
IM 33S01B30-01E
<N3.6 Engineering>
N3-51
Communication I/O Builder Items Defined in the Case of Module Specification

Communication I/O definitions are set for each slave device module. If a module has both
inputs and outputs, they must be defined separately.
The table below lists the items that must be defined for one module in Communication I/O
Builder.
Size: Designates the data size for a device module in units of words. (*1)
Station: The Station Address value set in the Slave Configuration window
Device & Address: The Slot and Idx values set in the Slave Configuration window
Data Type: Enter the appropriate data type according to the device modules specifications.
Reverse: Refer to the device manual to determine whether or not to reverse bits and
bytes.
*1:
If an odd-byte data size is assigned, there is no data corresponding to the terminal byte of the area because the area
size is designated in units of words. In this case, the value of the terminal byte data for the area is undefined.
TIP
When a module is deleted using the PROFIBUS-DP configurator, the slot numbers following that module
will shift. Therefore, the setting should be modified in [Device & Address].
However, this does not apply to slave devices to which no changes are made.
Communication I/O Builder Items Defined in the Case of Specification for

Each Channel
When defining communication data by specifying each channel, the following item is set
differently from the way it is set in the case of module specification. Other items are set in
the same way as in the case of module specification.
Device & Address: The Slot and Idx values set in the Slave Configuration window, and
the appropriate channel number
Communication I/O Builder Items Defined in the Case of Channel Batch

Specification
When defining communication data by specifying multiple channels, the following item is
set differently from the way it is set in the case of module specification. Other items are set
in the same way as in the case of module specification.
Device & Address: The Slot and Idx values set in the Slave Configuration window,
channel number and extension (R)
IM 33S01B30-01E
<N3.6 Engineering>
N3-52
Details of Communication I/O Builder

Buffer, Program Name, Size, Port, IP Address, Station, Device & Address, Data Type, Reverse,
Scan, Service Comment, Label
Definitions relating to the communication I/O data area are set in Communication I/O
Builder.
The table below lists the definitions to be made.
Table Definition Items in Communication I/O Builder
Definition
Entry
item
Buffer area
Program
Name
Size
Details
Remarks
Enter the size of the entire area for storing the ALP111 data.
Enter the installation position of a module followed by

PROFIBUS.
Example: When the module is installed on FIO bus system 1,
node 2 and slot 4
K1-2-4PROFIBUS
Enter the size to be assigned for a single slave device module.

The size is assigned in units of words (2 bytes). The valid
range of values is from 1 to 126. However if a value outside
this range is entered, it will not be generated as an error in
the builder.
Port
Enter the port number.

This is not used for ALP111, however.
Entering a port number

will not generate an error.
IP Address
Enter the IP addresses of other devices.

This is not used for ALP111, however.
Entering an IP address
will not generate an error.
Station
Enter the node address of a slave device.

The valid range of values is from 0 to 125. However if a value
outside this range is entered, it will not be generated as an
error in the builder.
Designating an unused
or out of range slot
number/index will cause
the status of the data in
question to be set to
IOP/OOP upon execution.
Device &
Address
Details of the definition are explained in the main text.

Define in the range of up to 8 single-byte alphanumeric
characters.
Data Type
Set according to the slave device specifications.

The default setting is blank.
Set whether or not to reverse the bit arrangement in the FCS

and data bit arrangement in the subsystem.
There are the following options for Reverse:
No
Yes
The default setting is No.
Scan
Set whether or not to update communication I/O analog data

at the start of fast-scan.
There are the following options for Scan:
Normal
Fast
The default setting is Normal.
Service
Comment
A comment can be entered.
Label
The I/O terminal name can be entered as a user-defined label.

This item is an optional setup item.
Reverse
N030613E.EPS
:
Entry is required.
Blank: Entry is not required.
-:
Can be omitted.
IM 33S01B30-01E
N3-53
<N3.6 Engineering>
Items Specified for [Device & Address]

When defining I/O data for a slave device by module specification or channel specification,
specify the following in the [Device & Address] item of Communication I/O Builder (using
up to 8 single-byte alphanumeric characters).
Table Items Specified for Device & Address
Definition
Description
Channel
Module
specification
specification
(single/batch)
AI/O
DI/O
AI/O
DI/O
(*1)
(*1)
(*1)
(*1)
Slot number
Specify the slot number of a slave device module.

Range: 1 to 60
Index
Specify the index of a slave device module, followed by -.

Range: 1 to 60
Semicolon (;)
Divide the part of module specification and the extension part

that includes channel specification.
Channel
number
Specify the channel number in a module.

Range: 0 to 99
If omitted, it is treated as if a module is specified.
Extension (E) An identifier for expanding byte data to 16 bits.
(*1)
Specification to reverse bytes: Reverse the upper and lower

Extension (S) bytes of digital data of a normal slave device whose upper and
lower bytes are reversed, and correspond it to the %WB numbers.
(*1)
(*1)
(*1)
Specification to maintain output values.

Specify this extension to continue outputting the final output
Extension (H)
value before downloading, during downloading changed
(*2)
PROFIBUS definitions to an ALP111 or after restarting the ALP111.
If omitted, the output value becomes 0.
(*1)
(*1)
(*1)
(*1)
Specification to output 0 value: Specify this extension to output

Extension (Z) 0 when initial cold start of an ALP111 after downloading.
(*2)
If omitted, 0 is output.
Use this option to intentionally specify operations in the default status.
(*1)
(*1)
(*1)
(*1)
(*1)
(*1)
If a channel number is specified using a semicolon (;),

specification of R results in the same definition as when only
Extension (R)
the head channel is specified and a consecutive number of
channels corresponding to the area size are defined.
N030615E.EPS
:
*1:
*2:
Entry is required.
Enter as necessary.
A definition error occurs if H and Z are specified at the same time.
IMPORTANT
Specifying to maintain the output value
Communication from an ALP111 to slave devices is stopped while downloading
PROFIBUS definitions to the ALP111. To maintain the final output value on the device side
(to mask the failsafe operation), it is necessary to extend the watch dog timer detection time
of a device or invalidate the watch dog timer operation itself. Make sure to take the safety
measure of the control loop into consideration before specifying this option.
IM 33S01B30-01E
<N3.6 Engineering>
N3-54
Syntax
mm[-nn][;[xxESHZR]]
(mm: slot number of a module, nn: index, xx: channel number, items in [] can be omitted), E,
S, H, Z and R are extensions
Example of entry 1: In the case of analog or digital data (no byte reversing) of channel
number 1 when the module slot number is 3
3;1
Example of entry 2: In the case of analog or digital data (no byte reversing) of channel
number 2 when the module slot number is 3 and index is 4
3-4;2
Priority of Overlapped Definitions

If several definitions that are exactly the same are made for the same module or channel,
the second and subsequent definitions are handled as errors. Also, if definitions for a
module as well as definitions for a channel coexist for the same module, only the definition
with the highest priority becomes valid. Other definitions are handled as errors at the
initialization processing of the ALP111. The table below lists the priority in the case of
overlapping definitions.
Table Priority In the Case of Overlapped Definitions
Priority order
High
Description of Device & Address
Remarks
mm
mm;[ESHZR]
mm;xx
mm;xx[ESHZR]
mm-nn
mm-nn;[ESHZR]
mm-nn;xx
Low
mm-nn;xx[ESHZR]
N030616E.EPS
mm: slot number of a module, nn: index, xx: channel number, E, S, H, Z and R: extensions
IM 33S01B30-01E
N3-55
<N3.6 Engineering>
Specification of Consecutive Channels

When defining 8 channels individually, two definition methods are available: the same
individual definition method as for ACP71 and defining consecutive channels in a batch.
If consecutive channels are defined in a batch, the data area size required will be the same
as for defining channels individually, but the number of definitions may be reduced. Use
these methods for their respective best uses as necessary. The figure below shows examples of defining eight 16-bit analog I/O points (I16, U16).
Individual Definition Compatible with ACP71
Size
Device & Address
%WW0101
3;0
%WW0102
%WW0103
3;1
Element number
%WW0104
%WW0105
3;2
%WW0106
%WW0107
3;3
%WW0108
%WW0109
3;4
%WW0110
%WW0111
3;5
%WW0112
%WW0113
3;6
%WW0114
%WW0115
3;7
%WW0116
Consecutive Batch Definition

Channel
number
0
Size
Device & Address
16
3;R
1
2
3
4
5
6
7
%WW0117
N030617E.EPS
Figure
Communication I/O Data when Extension R is Specified
Reserve the same area size as for individual definitions for size. The format used when
calling from %W is the same for both individual and batch definition.
IMPORTANT
If individual channels are specified and defined separately, the total number of communication I/O definitions increases. Keep the number of communication I/O definitions less than
200, the upper limit of definitions for a single ALP111.
IM 33S01B30-01E
N3-56
<N3.6 Engineering>
Examples of Specification of Consecutive Channels

The table below lists the size for each data type. The size for each data type is fixed to the
number of points (number of channels) x 2.
Table Data Types and Sizes
Size
Data type (size)
Analog
input/output
Discrete
input/output
Individual
definition
Batch
definition (R)
16 bits
Number of points x 2
32 bits
1 to 2 bytes
3 to 4 bytes
N030620E.EPS
The figure below shows examples of specifying consecutive channels by I/O type and size.
Eight 32-bit analog I/O points (I32, U32, F32)
Element number
%WW0101
%WW0103
%WW0105
%WW0107
%WW0109
%WW0111
%WW0113
%WW0115
Size
2
Channel
Device & Address number
3;0
0
3;1
3;2
3;3
3;4
3;5
3;6
3;7
1
2
3
4
5
6
7
Size
Device & Address
16
3;R
N030621E.EPS
Figure Example of 32-Bit Analog Inputs/Outputs
IM 33S01B30-01E
N3-57
<N3.6 Engineering>
Eight 1-byte discrete I/O points (DI, DO)

Element number
Size
Device & Address
%WW0101
3;0
%WW0103
3;1
%WW0105
3;2
%WW0107
3;3
%WW0109
3;4
%WW0111
3;5
%WW0113
3;6
%WW0115
3;7

Channel
number
0
1
2
3
4
5
6
7
Size
Device & Address
16
3;R
N030622E.EPS
Figure Example of 1-Byte Discrete Inputs/Outputs (DI, DO)
IM 33S01B30-01E
N3-58
<N3.6 Engineering>
2-byte discrete inputs/output, 16 points (DI, DO)

Element number
Size
Device & Address
%WW0101
3;0
%WW0103
3;1
%WW0105
3;2
%WW0107
3;3
%WW0109
3;4
%WW0111
3;5
%WW0113
3;6
%WW0115
3;7
%WW0117
3;8
%WW0119
3;9
%WW0121
3;10
%WW0123
3;11
%WW0125
3;12
%WW0127
3;13
%WW0129
3;14
%WW0131
3;15

Channel
number
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Size
Device & Address
32
3;R
N030623E.EPS
IM 33S01B30-01E
<N3.6 Engineering>
N3-59
4-byte discrete inputs/outputs, 32 points (DI, DO)

Element number
%WW0101
%WW0103
Size
Device & Address
3;0
3;1

Channel
number
0
1
Size
Device & Address
64
3;R
%WW0127
%WW0129
%WW0131
%WW0134
%WW0136
%WW0138
%WW0140
%WW0142
%WW0144
%WW0146
%WW0148
%WW0150
%WW0152
%WW0154
%WW0156
%WW0158
%WW0160
%WW0162
%WW0164
3;13
3;14
3;15
:
13
14
15
3;16 (*1)
3;17
3;18
3;19
3;20
3;21
3;22
3;23
3;24
3;25
3;26
3;27
3;28
3;29
3;30
3;31
(*1)
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
* (*1)
N030624E.EPS
*1:
Specify %W(odd) for channel numbers from 0 to 15, specify %W+1(even) for channel numbers from 16 to 31.
SEE ALSO
For how channel numbers and %WB numbers correspond in discrete I/O data, see the following:
How to Treat I/O Data as Discrete I/O Data (in the Cases of Specification for Each Channel and Channel Batch Specification) in N3.4, I/O Data
IM 33S01B30-01E
<N3.6 Engineering>
N3-60
N3.6.5 Operations in Function Block Detail Builder

Communication I/O data whose data type is defined as analog output can be assigned to a function block as analog output by designating the data using the
%WWnnn format.
This section explains the operations required in such cases, which are performed in
Function Block Detail Builder.
Settings in Function Block Detail Builder

Designate Communication Output (Fully-open/Tightly-shut) for [Output Signal Conversion], which is a setting item in Function Block Detail Builder.
Table Setting Items in Function Block Detail Builder
Tab
Item
Basic or Output
(optional setup item)
Detail
Setting
Output signal Output signal

Communication Output (Fully-open/Tightly-shut)
conversion conversion type
N030618E.EPS
Designating Communication Output (Fully-open/Tightly-shut) will display the following

items:
Table Displayed Items when Communication Output (Fully-open/Tightly-shut) is Selected
Detailed item
Default
Data Conversion Gain
1.000
Data Conversion Bias
0.000
Output Value for Full-open
106.25
Output Value for Tight-shut
-17.19
Remarks
Same as in the case of
Communication Output
Same as in the case of No
N030619E.EPS
SEE ALSO
For details on output signal conversion, see the following:
C4.8, Output Signal Conversion
IM 33S01B30-01E
N3-61
N3.7 Operation and Monitoring

Operation and monitoring includes a function for displaying the ALP111 status and a
function for displaying various messages generated in PROFIBUS-DPV1 communication.
SEE ALSO
For the details of various messages generated in PROFIBUS-DPV1 communication using ALP111
modules, see the following:
N3.9, Messages
FCS Status Display Window

Status Display of ALP111
The status of an ALP111 is displayed in the FCS Status Display window of an HIS as
follows:
Single configuration and normal: Green
Control side in dual-redundant configuration: Green indicates normal.
Standby side in dual-redundant configuration:
Yellow and mark indicates normal; Red indicates the diagnosis communication
error.
States other than above: Red
Status Display of Slave Devices

The error status of a slave device connected to an ALP111 is displayed independently from
the status of the ALP111; 1C (meaning port 1 error) is displayed in red. This occurs in the
following cases.
Errors occurred in one or more defined slave devices
An SS-COM error occurred
IM 33S01B30-01E
N3-62
Display Example of the Status Display Window

The following figure shows an example of the FCS Status Display window.
I/O UNIT
Node No.
Comment
I/O (OFF)
A
L
P
1
1
1

A
L
P
1
1
1
A
L
P
1
1
1
S
B
4
0
1
S
B
4
0
1
P
S
U
P
S
U
1C
IOM Load
Report
Close
N030701E.EPS
Figure FCS Status Display Window with ALP111 Defined
In the FCS Status Display window, the following data can be downloaded to the ALP111 by
clicking the [IOM Load] button.
ALP111 program
IM 33S01B30-01E
N3-63
N3.8 Unusual Operations

This chapter explains unusual operations in PROFIBUS-DPV1 communication.
Overview of Unusual Operations

The figure below shows areas where errors can be generated in PROFIBUS-DP communication.
FCU
Power failure of FCS
Power failure of FCU
Path error
ESB Bus
AA I I I I
P P
SS
EE
L L OOOO
S S
BB
BB
P P MM MM
U U
Local Node
Power failure of node

Power failure of ALP111
Disconnected PROFIBUS communication
Failure of slave device
PROFIBUS-DP
PROFIBUS-DP/DPV1
Slave device
N030801E.EPS
Figure Areas where Errors can be Generated in PROFIBUS-DP Communication
IM 33S01B30-01E
N3-64
Basic Operations Related to Output Processing

At Errors
The final output value is maintained as far as PROFIBUS communication from an
ALP111 to slave devices is possible.
If communication from an ALP111 to slave devices is stopped due to a failure of the
ALP111 module or a PROFIBUS path error, the specified fail-safe operation for each
slave device is followed.
The final output value is continued to be output when an ALP111 detects an error in
the host controller and is placed in the fallback status as well.
It is possible to select to reset the output to 0 when a fallback occurs.
At Recovery
The control is resumed at recovery by maintaining the output value at error occurrence.
TIP
Since no read back operation is prescribed in the PROFIBUS communication specifications, it is not
possible to perform tracking operation with a slave device if an error occurs.
SEE ALSO
For more information about output processing, see the following:
N3.8.1, "Actions in the Event of Faults"
IM 33S01B30-01E
N3-65
Setting Items Related to Unusual Operations

The following specification items are provided for unusual operations of an ALP111 and
slave devices.
ALP111
Specify the following two items in the IOM property sheet of an ALP111.
Specification of fallback operation (specification of output operation when an ALP111
detects a fallback of the host controller)
Whether or not to perform fallback operation
Output specification when a fallback occurs (specified output value for all ALP111
modules)
All points maintain Current value/Reset all outputs
Slave Devices
Set the following items using the PROFIBUS-DP configurator by referring to the manual of
each slave device.
Output actions
Specify the output action when a slave device is placed in the fail-safe status. (*1)
Specify the action for each slave device.
Enable fail- safe: Output the value specified for the slave device
Disable fail-safe: Maintain the previous output value
*1:
Fail-safe
If no access from the master device (ALP111) has taken place for a certain period of time, the output of the slave
devices in use will be forcibly changed to the designated value. The slave-device specifications determine whether failsafe operation is enabled and the setting range of the designated values. Operation of each device at fallback is set in
the detail settings of each device in the PROFIBUS-DP configurator, and the time to monitor access from the master
device (fail-safe monitoring time) is set as a bus common parameter of the PROFIBUS-DP configurator.
IM 33S01B30-01E
N3-66
N3.8.1 Actions in the Event of Faults

This section explains the actions in the event of faults.
Actions Corresponding to the Power Failure/Failure Mode

The following actions are performed in response to the respective power failure/failure
modes in the event of faults.
Table Actions By Power Failure/Failure Mode (1/2)
System status
Prolonged power
failure/FCS
FCS offline download
power
failure
Momentary power
failure/restart
Prolonged ALP111
power
fallback
failure/
CPU
No ALP111
STOP/RUN
fallback
FCU
power
failure
ALP111
Momentary fallback
power
failure/
No
reset
ALP111
fallback
Path
error
Function block
output action
ALP111 output action

(Upper section: Specification (Upper section:
to retain current value,
Not in fail-safe status,
Lower section: Specification
Lower section:
to reset output)
At fail-safe operation)
At
When a
At
recovery failure occurs recovery
When a
failure occurs
At
recovery
Tracking
(0)
Restart
output
Output previous
value again
(continuous
operation)
Restart
output
Tracking
(previous
value or 0)
Previous value
Previous
value
Retain output
Continue
output
Continue
output
Continue
output
Retain output
Continue
output
Tracking
Output previous
value again
(continuous
operation)
Output previous
value again
(continuous
operation)
ALP111 fallback
MAN
fallback
Tracking
(previous
value or 0)
No ALP111
fallback
MAN
fallback
When a
failure occurs
Retain output
Output
specified value
Retain output
Previous value
0
Previous
value
Output
specified value
Retain output
0
Previous
value
Previous
value
Continue
output
Continue
output
Retain output
Previous
value
Previous value
Previous
value
Retain output
Continue
output
Tracking
Continue
output
Continue
output
Continue
Retain output
output
No change
No change
Continue
output
Continue
output
Retain output
Prolonged
power failure
MAN
fallback
Tracking (0)
Restart
output
Momentary
power failure
(restart)
No change
Output
previous
value again
Restart
output
ALP111 failure
/maintenance
MAN
fallback
Tracking
(0)
Restart
output
Dual-redundant
ALP111 switch
No change
No change
Continue
output
Continue
output
FCU (CPU)
control-right transfer
Node
power
failure
Continue
output
Retain output
Output
specified value
Retain output
Output
specified value
Previous
value
Retain output
Output
specified value
Retain output
0
Previous
value
N030806E.EPS
IM 33S01B30-01E
N3-67
Table Actions By Power Failure/Failure Mode (2/2)
System status
Function block
output action

(Upper section: Specification (Upper section:
to retain current value,
Lower section: Specification
Lower section:
to reset output)
When a
failure occurs
At
recovery
When a
failure occurs
At
When a
At
recovery failure occurs recovery
PROFIBUS communication
stop (between ALP111
and slave devices)
MAN
fallback
Tracking
(previous value)
Continue
output
Restart
output
Slave device failure/

maintenance
MAN
fallback
Tracking
(previous value)
Continue
output
Restart
output
Retain output
Output
specified value
-
Previous
value
Previous
value
N030821E.EPS
TIP
In the case of an ALP111 mounted to the FCU of an FFCS, the "FCU power failure" of the power failure/
failure mode does not exist. In this case, the FCU power failure corresponds to the "FCS power failure" of
the power failure/failure mode.
Actions in the Event of FCS Power Failure (Prolonged Power Failure)

The FCU and ALP111 stop operating in the event of a prolonged FCS power failure. The
output actions of slave devices while the FCS is stopped vary depending on whether or not
fail-safe operation is enabled.
Input Actions
Input data becomes invalid until the ALP111 becomes capable of acquiring input data from
slave devices after the power supply to the FCS recovers.
Output Actions
Outputs from slave devices during an FCS power failure depend on the specification of failsafe operation of each slave device.
(If fail-safe operation is not specified for a slave device, the slave device maintains the
output value prior to the power failure until the CPU recovers.)
After the power supply to the FCS recovers, 0 is output to all the output points.
Stop
Recovery
CPU operation
status
Function block
mode
ALP111 output
Slave device
output
AUT
MAN
Outputs 0
Enters the fail-safe status and

outputs the specified value
Outputs 0
N030807E.EPS
Figure Output Actions in the Event of FCS Power Failure (Prolonged Power Failure, Slave Device
Fail-Safe Operation)
IM 33S01B30-01E
N3-68
Actions in the Event of FCS Power Failure (Momentary Power Failure and
Restart)
The FCU and ALP111 stop operating in the event of a momentary FCS power failure. The
output actions of slave devices that are forced to stop operating vary depending on whether
or not fail-safe operation is enabled.
The FCS restarts when it recovers from a momentary FCS power failure.
If the power failure period is longer than the fail-safe detection time of a slave device, the
slave device first outputs the fail-safe setting value and then outputs the previous value
once the CPU recovers.
Input Actions
The previous input data is retained until the ALP111 becomes capable of obtaining input
data of slave devices after the power supply to the FCS recovers.
Output Actions
After the FCS restarts, the FCU outputs the previous value to the ALP111, and the ALP111
resumes outputting data to the slave devices.
Stop
Recovery
CPU operation
status
Function block
mode
AUT
AUT
Outputs the previous value

ALP111 output
Slave device
output
N030808E.EPS
Figure Output Actions in the Event of FCS Power Failure (Momentary Power Failure and Restart)
IM 33S01B30-01E
N3-69
Actions in the Event of FCU Power Failure (Prolonged Power Failure and
CPU STOP/RUN)
When a prolonged power failure occurs in the FCU or FCS CPU STOP/RUN is being
executed from the HIS, only the actions of the FCU is stopped. During this period,
PROFIBUS communication between an ALP111 and slave devices is continued. The
output actions of the ALP111 at an FCU power failure depend on the specification of
fallback operation of the ALP111.
Input Actions
Since PROFIBUS communication between the ALP111 and slave devices continues
regardless of the actions of the FCU, the FCU becomes capable of obtaining the correct
input data immediately after its recovery.
Output Actions (ALP111 Fallback Status)

The output actions taken when the ALP111 goes into fallback status at an FCU power
failure can be specified by selecting either [All points maintain Current value] or [Reset all
outputs] for the fallback operation of the ALP111.
When [All points maintain Current value] is specified for the fallback operation of an
ALP111, the ALP111 maintains the output value while the FCU is stopped. The
ALP111 resumes outputting from the previous value after the FCU recovers.
Stop
Recovery
CPU operation
status
Function block
mode
AUT
MAN
Enters the fallback status and

maintains the output value
ALP111 output
Slave device
output
N030809E.EPS
Figure Output Actions in the Event of FCU Power Failure (Prolonged Power Failure: [Perform
Fallback] is Enabled and [All Points Maintain Current Value] is selected for an ALP111)
Reset all outputs

When [Reset all outputs] is specified for output retention, the ALP111 resets all the
output points when it enters the fallback status and resumes outputting from 0 after
the FCU recovers.
Stop
Recovery
CPU operation
status
Function block
mode
AUT
MAN
Enters the fallback status and
resets the output value
ALP111 output
Slave device
output
Outputs 0
N030810E.EPS
Figure Output Actions in the Event of FCU Power Failure (Prolonged Power Failure: [Perform
Fallback] is Enabled and [Reset All Points] is selected for an ALP111)
IM 33S01B30-01E
N3-70
Output Actions (ALP111 Non-Fallback status)

The ALP111 retains the previous output value at an FCU power failure.
The ALP111 resumes outputting from the previous value after the FCU recovers.
Actions in the Event of FCU Power Failure (Momentary Power Failure

and Restart)
Only the FCU stops operating in the event of a momentary FCU power failure. During this
period, PROFIBUS communication between an ALP111 and slave devices is continued.
The output actions of the ALP111 at a momentary FCU power failure depend on the specification of fallback operation of the ALP111.
Input Actions
The FCU becomes capable of obtaining correct input data immediately after its recovery.

Since ALP111 fallback does not occur in the case of normal momentary power failure, the
output actions when the ALP111 is in the non-fallback status are performed. The ALP111
performs fallback operation only when restart is specified for the FCU and the power failure
period is longer than the fallback detection time of the ALP111.
When [All points maintain Current value] is specified for the fallback operation of the
ALP111, the ALP111 maintains the output value while the FCU is stopped.
The ALP111 resumes outputting from the previous value after the FCU recovers.
Reset all outputs
If [Reset all points] is specified for output retention, an ALP111 resets all the output
points when the ALP111 enters the fallback status and resumes outputting from the
previous value after the FCU recovers.
Output Actions (ALP111 Non-Fallback Status)

The ALP111 retains the previous output value at an FCU power failure.
The FCU resumes outputting from the previous value after is recovery.
Actions in the Event of FCU (CPU) Control-Right Transfer

Actions performed when the FCU (CPU) control-right is transferred do not influence any
part of the system, including any ALP111 modules and slave devices.
IM 33S01B30-01E
N3-71
Actions in the Event of Node Power Failure (Prolonged Power Failure)
PROFIBUS I/O communication from an ALP111 to slave devices is stopped if a power

failure occurs in a node for a prolonged period.
The PROFIBUS communication is resumed after the recovery from the power failure.
Input Actions
The status of input data becomes BAD throughout a prolonged power failure of a node.
Output Actions
The FCU outputs 0 to an ALP111 after the recovery from a prolonged power failure of a
node.
Stop
Recovery
Node operation
status
Momentary power failure detection time
Function block
mode
AUT
MAN
Outputs 0
ALP111 output
Slave device
output

Outputs 0
N030811E.EPS
Figure Output Actions in the Event of Node Power Failure (Prolonged Power Failure, Slave
Device Fail-Safe Operation)
IM 33S01B30-01E
N3-72
Actions in the Event of Node Power Failure (Momentary Power Failure)
PROFIBUS I/O communication from an ALP111 to slave devices is stopped in the event of
a momentary power failure in a node.
The FCU outputs the previous value again at the recovery from the momentary power
failure of a node.
Input Actions
The previous input data value is retained during a node power failure if the node recovers
from the failure within the momentary power failure detection time.
The previous input data value is retained until the ALP111 also becomes capable of acquiring input data from slave devices after the node recovers from the power failure.
Output Actions
The FCU outputs the previous value again after the node recovers from the power failure.
Stop
Recovery
Node operation
status
Momentary power failure detection time
Function block
mode
AUT
ALP111 output
Slave device
output
N030812E.EPS
Figure Output Actions in the Event of Node Power Failure (Momentary Power Failure)
IM 33S01B30-01E
N3-73
Path Errors
Path errors refer to errors in the communication path between an FCU and an ALP111. The
output actions taken in the event of a path error depend on the specification of fallback
operation of the ALP111.
The FCU performs tracking at the recovery from a path error.
Input Actions
The status of input data becomes BAD while the path error persists.
The FCU becomes capable of obtaining correct input data after the recovery from the path
error.

When [All points maintain Current value] is specified for the fallback operation of the
ALP111, it maintains the current value during a path error.
The FCU performs output tracking of the ALP111 after the recovery from the path
error and continues to output the current value.
Reset all outputs
If [Reset all points] is specified for output retention, the ALP111 resets all the output
points when it enters the fallback status due to a path error.
The FCU performs output tracking of the ALP111 after the recovery from a path error
and continues to output the reset value.
Output Actions (ALP111 Non-Fallback Specification)

The current output value of the ALP111 is retained at a path error in the communication
with the FCU. The FCU continues outputting at the recovery from the path error.
IM 33S01B30-01E
N3-74
Actions in the Event of Failure/Maintenance of an ALP111

PROFIBUS I/O communication from an ALP111 to slave devices is stopped during ALP111
failure/maintenance.
The FCU outputs 0 to all the points at the recovery from the ALP111 error status.
Input Actions
The status of input data becomes BAD during the ALP111 failure/maintenance period.
Output Actions
The FCU outputs 0 to the ALP111 after the ALP111 recovers.
Stop
Recovery
ALP111 status
Function block
mode
AUT
MAN
Outputs 0
ALP111 output
Slave device
output

Outputs 0
N030813E.EPS
Figure Output Actions in the Event of ALP111 Operation Stop (at Slave Device Fail-Safe
Operation)
Dual-Redundant ALP111 Switch

When the functions of dual-redundant ALP111 modules are switched, the FCU outputs the
output value again to the ALP111 that becomes the control side after the switching.
Input Actions
After the switching of the functions of dual-redundant ALP111 modules is completed, the
FCU reads the input value from the ALP111 that takes control of the PROFIBUS communication after the switching; thus, the FCU becomes capable of obtaining correct input data.
Output Actions
When the functions of dual-redundant ALP111 modules are switched, the FCU outputs the
output value again to the ALP111 that that takes control of the PROFIBUS communication
after the switching.
IM 33S01B30-01E
N3-75
Actions in the Event of PROFIBUS Communication Stop (Disconnection

of Communication between an ALP111 and Slave Devices)
If an ALP111 detects that some slave devices are not responding due to disconnection of
PROFIBUS communication, the ALP111 notifies the communication error to the FCU, and
the corresponding function blocks perform MAN fallback.
If an ALP111 detects that some slave devices are not responding, a system alarm message (error code CA91) is generated.
Input Actions
The data status becomes BAD while the PROFIBUS communication is disconnected.
The FCU obtains input data from the ALP111 after the PROFIBUS communication recovers.
Output Actions
The FCU tracks the output value of the ALP111 after the recovery from disconnection of the
PROFIBUS communication.
Stop
Recovery
PROFIBUS
communication
status
Function block
mode
AUT
Notifies about a
communication error
MAN
ALP111 output
Slave device
output

N030814E.EPS
Figure Output Actions in the Event of PROFIBUS Communication Stop (at Slave Device Fail-Safe
Operation)
SEE ALSO
For details on system alarm messages, see the following:
N3.9.1, System Alarm Messages
IM 33S01B30-01E
N3-76
Actions in the Event of Slave Device Failure/Maintenance

If a slave device stops operating due to failure/maintenance, the FCU detects a PROFIBUS
communication error or slave device channel error.
The FCU detects when the PROFIBUS communication or the slave device channel recovers to normal, and performs tracking operation when the slave device recovers.
Input Actions
The data status becomes BAD during a slave device failure.
The input data from the ALP111 is reflected in the FCU after recovery from the slave device
failure.
Output Actions
If a slave device stops operating, the output from the ALP111 to the slave device is handled
as a communication error or channel error. The ALP111 outputs the previous value to the
slave device when the slave device recovers from the operation stop.
Stop
Recovery
Slave device
operation status
Function block
mode
AUT
Notifies about a
communication error MAN
ALP111 output
Slave device
output
N030815E.EPS
Figure Output Actions in the Event of Slave Device Operation Stop
IM 33S01B30-01E
N3-77
N3.8.2 Actions during Download

This section describes the following download operations:
Offline download to an FCS
IOM download to an ALP111
Online maintenance
The following operations may be performed during online maintenance:
Adding a new module
Changing IOM properties (including the specification of PROFIBUS definition
data)
Changing communication I/O definitions
SEE ALSO
For more information about online maintenance, see the following:
N3.8.3, "Actions during Online Maintenance"
Download Data
The following three types of data can be downloaded to an ALP111.
ALP111 detail settings
ALP111 programs
PROFIBUS definition data (*1)
*1:
The PROFIBUS definition data is the configuration data created by the PROFIBUS-DP configurator.
The following table lists the relationship between user operations during engineering and
the corresponding data to be downloaded.
Table User Operations and Download Data
Download data
User operation
ALP111 detail
settings
ALP111
programs
PROFIBUS
definition data
PROFIBUS
communication from an
ALP111 during download
Offline download to FCS
Temporarily suspended
IOM download to ALP111
(*1)
Temporarily suspended
Add new ALP111 module
Stopped (initial status)
Change ALP111 properties
(*2)
(*3)
Continued/temporarily
suspended (*4)
Change communication I/O

definitions
Continued
N030822E.EPS
:
:
-:
*1:
*2:
*3:
*4:
This data is always downloaded.

This data may be downloaded depending on conditions.
This data is not downloaded.
If there is a difference between the revisions of ALP111 programs, the ALP111 program of older revision is downloaded.
Only if there is a difference between the revisions of ALP111 programs, the ALP111 program of newer revision is
downloaded.
PROFIBUS definition data is downloaded only if a PROFIBUS definition data file is specified in the Properties dialog
box.
PROFIBUS communication is temporarily suspended only if either an ALP111 program or PROFIBUS definition data is
downloaded.
IM 33S01B30-01E
N3-78
System Operations during Download

The following describes system operations during download according the types of download to an ALP111.
Table System Operations during Download
System status
Function block
output action
During
download
At
recovery
During
download
At
recovery

(Upper section:
Lower section:
During
download
At
recovery
Retain output
Download to FCS offline
Tracking (0)
Restart
output
Download IOM to ALP111
MAN
fallback
Tracking (0)
Restart
output
Download ALP111
programs
MAN
fallback
Tracking
(previous
value or 0)
Stop
output
Restart
output
Download PROFIBUS
definition data
MAN
fallback
Tracking
(previous
value or 0)
Stop
output
Restart
output
MAN
fallback
Tracking
(previous
value or 0)
Stop
output
Restart
output
Change IOM properties

(other than specification
of dual-redundant)
MAN
fallback
Tracking
Continue
output
Continue
output
Retain
output
Continue output
Change communication
I/O definitions
MAN
fallback
Tracking
Continue
output
Continue
output
Retain
output
Continue output
(*1)
Online
mainte- Change IOM properties
(specification of
nance
dual-redundant)
Output
specified value
Retain output
Retain output
Output
specified value
Retain output
Output
specified value
Retain output
Output
specified value
Previous value
or 0 (*2)
Previous value
or 0 (*2)
Previous value
or 0 (*2)
N030823E.EPS
*1:
*2:
0 is set for newly added definitions.

Depends on the specification of output retention in ALP111 Communication I/O Builder.
IMPORTANT
When properties are changed, download the PROFIBUS definition data and ALP111 detail
settings. In case the downloading of the PROFIBUS definition data has normally been
completed, but the downloading of the detailed settings of the ALP111 has generated an
error, the database managed by System View reverts to the status prior to downloading. In
this case, the PROFIBUS definition data managed by System View does not match the
PROFIBUS definition data in the ALP111.
To cancel changes made to the ALP111 properties and return to the previous status,
execute an IOM download to the ALP111.
To change the properties, copy the PROFIBUS definition data again and then download it.
IM 33S01B30-01E
N3-79
Offline Download to an FCS

The downloading of ALP111 programs to an ALP111 is executed during offline download to
an FCS. After the offline download to the FCS is complete, execute an IOM download again
to the ALP111 if necessary depending on the following conditions. This is because the
PROFIBUS definition data is not downloaded during offline download and, as a result, the
PROFIBUS definition data may not match depending on the status of the ALP111.
Table Operations of an ALP111 and IOM Download Execution during Offline Download to an FCS
Condition
Action after
offline download
IOM download
Action after
IOM download
When using a completely

new ALP111 module
When an ALP111 is
replaced before offline
download
Input becomes IOP.

Output becomes OOP. (*1)
Required
Reads new inputs and

resets outputs (*2)
Not required
Reads new inputs

and resets outputs (*2)
When there are changes

to the definitions (*3)
When there are no changes
to the definitions
N030816E.EPS
*1:
*2:
*3:
The ALP111 reads new inputs and resets outputs for those slave devices connected to the ALP111 prior to replacement, as well as the slave devices connected to a new ALP111 after replacement that meet all of the following
conditions:
Node-address agreement
Identification Number (model code) agreement
Resetting outputs means outputting 0 to the analog output and discrete output.
This may occur under conditions where PROFIBUS definition data is copied offline to a default project, etc., causing
discrepancies between the copied data and the PROFIBUS definition data downloaded to the ALP111.
IM 33S01B30-01E
N3-80
N3.8.3 Actions during Online Maintenance

When online maintenance is performed on an ALP111, system operations vary with
ALP111 program download, PROFIBUS definition data download, and whether dualredundant specification is changed. This section describes actions during online
maintenance.
ALP111 Online Maintenance (ALP111 Program Download, Changing

PROFIBUS Definition, Changing Properties for Dual-Redundant Specification)
During online ALP111 maintenance in which ALP111 program download or PROFIBUS
definition load operations are performed or properties for dual-redundant specification are
changed, the I/O communication from the ALP111 to slave devices is stopped once. It is,
however, possible to continue outputting values before and after the online maintenance by
specifying the communication I/O definitions and fail-safe operation for slave devices.
TIP
PROFIBUS definition data must be downloaded when the settings for the PROFIBUS-DP configurator
have been changed.
Adding a module to a slave device
Deleting a module from a slave device
Changing detail settings of a slave device
Input Actions
During ALP111 online maintenance, the previous values are retained for both input and
status values.
IM 33S01B30-01E
N3-81
Output Actions (when Specified to Retain ALP111 Output)

The output value of the ALP111 after ALP111 online maintenance depends on the specification of output retention in the communication I/O definitions.
Retain output
If Retain output is specified for output retention, the output is resumed with the
previous value after the online maintenance is completed.
To retain output values from slave devices while performing online maintenance,
specify Retain output for the specification of fail-safe operation for the slave device
side as well.
Downloading start
Downloading completed
ALP111 operation
status
Function block
mode
AUT
MAN
ALP111 output
Slave device
output

retains the output value
N030818E.EPS
Figure Output Actions during ALP111 Online Maintenance (when Specified to Retain ALP111
Output)
Specification to output 0
If 0 output is specified for output retention, 0 is output when the online maintenance
is completed.
IM 33S01B30-01E
N3-82
ALP111 Online Maintenance (Changing Properties other than Dual-Redundant Specification/Changing Communication I/O Definitions)
After online maintenance of an ALP111, in which properties of the ALP111 or communication I/O Definitions have been changed, the ALP111 restarts but the output actions of the
ALP111 continue.
Input Actions
Since the PROFIBUS communication between the ALP111 and slave devices continues
regardless of the online maintenance operations of the ALP111, the FCU becomes capable
of obtaining correct input data immediately after the online maintenance.
Output Actions
During the ALP111 online maintenance, the output of the ALP111 is retained.
The output continues after the online maintenance is completed. Note that the default value
of 0 is output as output values for newly added or changed output definitions.
Downloading start
Downloading completed
ALP111 operation
status
Function block
mode
AUT
MAN
ALP111 output
Slave device
output
N030819E.EPS
Figure Output Actions during ALP111 Online Maintenance
Deleting ALP111 Modules

This section explains the actions when ALP111 definitions are deleted.
All function blocks linked to the I/O data of the ALP111 in use become IOP or OOP.
If fallback operation is not designated, the output status prior to the download is retained.
If fallback operation is designated, the ALP111 switches to fallback status.
IM 33S01B30-01E
<N3.9 Messages>
N3-83
N3.9 Messages
In PROFIBUS-DPV1 communication, the following messages are displayed for
ALP111 modules and slave devices.
System alarm messages
Fieldbus messages
IM 33S01B30-01E
<N3.9 Messages>
N3-84
N3.9.1 System Alarm Messages

List of Messages
The following messages concerning ALP111 modules are notified from the system.
Number
Event
Message
Remarks
0081
IOM error
STNss IOM Fail FIO k NODE mm SLOT nn
0082
IOM recovery
STNss IOM Recover FIO k NODE mm SLOT nn
0083
IOM database
error
STNss IOM Configuration FIO k NODE mm SLOT nn
0089
Communication
error
STNss SS-COM Error FIO k NODE mm SLOT nn STN zzz CODE=####
0090
Communication
recovery
STNss SS-COM Recover FIO k NODE mm SLOT nn STN zzz

N030901E.EPS
STNss:
k:
mm:
nn:
zzz:
####:
XXXX:
yy:
VV:
Station name
Bus system number
Node number
Slot Number
Node address
Error code
Identification Number (Hexadecimal: Displayed with 0x added at the top)
Module number
Specifier number (Hexadecimal: Displayed with 0x added at the top)
When communication errors occur on a slave device, a system alarm message is generated at the first error occurrence only.
No further system alarm messages will be generated, even if another error arises due to a
different cause.
SEE ALSO
For details on settings of ALP111 properties, see the following:
Details of System View in N3.6.3, Operations in System View
Error Codes Used for Communication Errors

The error codes used for communication errors include the following two types:
Definition error
Communication error
IM 33S01B30-01E
<N3.9 Messages>
N3-85
Definition Error
The following errors occur when the settings for the communication I/O definitions are
invalid.
Check the settings of Communication I/O Builder if any of the following errors occurs.
Table Definition Errors
Error
code
Action to take after

the occurrence of error
Description
CAB1
Station number invalid
CAB2
Invalid Device & Address, cannot be interpreted
CAB3
Invalid Device & Address, illegal character string detected
CAB4
Excessive communication processing points
CAB5
Invalid Device & Address, slot number out of range
CAB6
Invalid Device & Address, entry data other than a numerical value
detected in the index
CAB7
Invalid Device & Address, index value out of range
CAB8
CAB9
CABA
Do not perform communication

Invalid Device & Address, index value exceeding the specified digits for the definition causing the error.
Check the definition in
Invalid Device & Address, invalid delimiter character
Corresponding device (module or channel) not specified in
CABB
Illegal data type, input designated for output data
CABC
Illegal data type, output designated for input data
CABD
Invalid Device & Address, entry data for slot number is not
a numerical value
CABE
CABF

(extension symbol)
N030902E.EPS
Communication Error
The following errors occur when there is an error in the communication with slave devices
or a slave device fails.
Table Communication Errors
Error
code
Action to take after

the occurrence of error
Description
Inconsistent versions of FCU and EB401
(EB401 does not support ALP111 in remote node)
Use correct versions of FCU and EB401
C58A(*1)
PROFIBUS definitions do not exit in the ALP111
Execute an IOM download
C58B(*1)
Communication error on the ALP111 standby side
Check the connection of the connector
C588
CA91
I/O data is not being communicated
CA92
Configuration error
CA93
Slave device module error
CA94
Slave device channel error
CA95
Overflow of slave diagnostic information
Retry communication
N030903E.EPS
*1: In case these errors occur, the node address of STN zzz is always set to 255.
IM 33S01B30-01E
<N3.9 Messages>
N3-86
N3.9.2 Fieldbus Messages

Fieldbus messages are displayed according to the slave diagnostic information and
the ALP111 self-diagnostic information.
These messages are stored in the historical message log file.
The messages can be viewed from the Historical Message Report window or Message Monitor window.
Messages relating to errors defined by the PROFIBUS-DP and PROFIBUS-DPV1
specifications are displayed as text. Information of device specific errors, however, is
displayed in the form of an error code. See the manual of the device in use for the
descriptions of the error codes.
Slave diagnostic information contains multiple causes of errors. Therefore, several
different messages may be displayed from slave diagnostic information.
List of Messages
Fieldbus messages are divided into the following categories:
Slave device common messages
Slave device specific messages
Messages for each module in a slave device
Messages for each channel in a slave device
ALP111 self-diagnostic messages
IMPORTANT
The ALP111 manages Error Occurrence/Recovery status relating to the fieldbus
messages.
Therefore, if the ALP111 restarts after an error occurrence message have been
notified, a normal recovery message will not be forwarded.
When an error that generates more data than the communication frame size of the
slave diagnostic information occurs, the part of the error data exceeding the communication frame may not be forwarded as part of the message. The communication frame
size of the slave diagnostic information depends on the slave device.
The part that does not fit into the communication frame is part of the error data of a
specific channel.
In this case, only the message for each module and the error for each channel that fits
in the communication frame will be notified.
IM 33S01B30-01E
<N3.9 Messages>
N3-87
Slave Device Common Messages

Slave device common messages indicate errors defined in the PROFIBUS specifications.
These messages are common to all slave devices.
These messages include both errors detected by ALP111 modules and errors detected by
slave devices.
Number
Event
Error
detected by:
Message
3283
Locked by another
master device
STNss PB FIO k NODE mm SLOT nn Station Alarm STN zzz ID

0xXXXX Master_Lock (Master STN yyy)
3284
The above returned

to normal
STNss PB FIO k NODE mm SLOT nn Station Recover STN zzz ID

0xXXXX Master_Lock
3285
Parameter setting failed

0xXXXX Param_Fault
3286
The above returned

to normal

0xXXXX Param_Fault
3287
Received an illegal frame STNss PB FIO k NODE mm SLOT nn Station Alarm STN zzz ID
0xXXXX Invalid_Slave_Response
from a slave device
3288
The above returned

to normal

0xXXXX Invalid_Slave_Response
3289
Received a request for

an unsupported function

0xXXXX Not_Supported
3290
The above returned

to normal

0xXXXX Not_Supported
3291
Configuration error

0xXXXX Cfg_Fault
3292
The above returned

to normal

0xXXXX Cfg_Fault
3293
Cannot transmit data

0xXXXX Station_Not_Ready
3294
The above returned

to normal

0xXXXX Station_Not_Ready
ALP111
Slave
device
ALP111
Slave
device
Slave
device
Slave
device
N030904E.EPS
STNss: Station name, k: Bus system number, mm: Node number, nn: Slot number, zzz: Node address
XXXX: Identification Number (Hexadecimal: Displayed with 0x added at the top).
yyy: Node address of the master device locking the slave devices
IM 33S01B30-01E
<N3.9 Messages>
N3-88

Number
Event
Error
detected by:
Message
3295
Slave device not present

on the communication line 0xXXXX Station_Non_Existent
3296
The above returned

to normal

0xXXXX Station_Non_Existent
3297
Slave device is missing

from the cyclic
transmission list

0xXXXX Deactivated
3298
The above returned

to normal

0xXXXX Deactivated
3299
Setting parameters or
checking configuration

0xXXXX Param_Req
3300
The above returned

to normal

0xXXXX Param_req
3301
Expansion area for slave

overflowed

0xXXXX Ext_Diag_Overflow
3302
The above returned

to normal
ALP111
ALP111
Slave
device
ALP111
or
Slave
STNss PB FIO k NODE mm SLOT nn Station Recover STN zzz ID device
0xXXXX Ext_Diag_Overflow
N030905E.EPS
XXXX: Identification Number (Hexadecimal: Displayed with 0x added at the top)
yyy: Node address of the master device locking slave devices
Messages relating to slave devices are displayed according to the interpretation results of
the top 3 bytes of the slave diagnostic information defined by the PROFIBUS specifications.
However, the following slave diagnostic information is not error data but is to indicate
configuration status; no message is displayed in these cases.
Sync_Mode:
Sync function is valid
Freeze_Mode:
Freeze function is valid
WD_On (Watch dog on)_Mode:
Watch dog function is valid
The following bit indicates whether device specific slave diagnostic information, module
slave diagnostic information or channel slave diagnostic information is available or not.
When this bit is set, the slave device specific messages and subsequent error messages
will be displayed.
For this reason, no special messages related to this bit will be displayed.
Ext_Diag: Slave diagnostic information contains expansion data
The following bit indicates whether or not slave diagnostic information must be read from
slave devices. No message is displayed because it is not directly related to an error description.
Stat_Diag
IM 33S01B30-01E
N3-89
<N3.9 Messages>
Slave Device Specific Messages (Slave Devices Supporting PROFIBUSDP)

Slave device specific messages indicate errors defined by the device manufacturer.
These messages display the slave diagnostic informations device related portion as error
codes.
Table List of Messages (Salve Devices Supporting PROFIBUS-DP)
Number
Event
Error
detected by:
Message
3303
Slave device error occurred
STNss PB FIO k NODE mm SLOT nn Device

Related Alarm STN zzz ID 0xXXXX CODE=##########
3304
The above returned to normal
STNss PB FIO k NODE mm SLOT nn Device

Related Recover STN zzz ID 0xXXXX
Slave
devices
supporting
PROFIBUS-DP
N030906E.EPS
XXXX: Identification Number (Hexadecimal: Displayed with 0x added at the top)
##########: Error code (Hexadecimal: Maximum 126 characters, with the first 2 characters indicating the error code length
(byte length)).
Messages for Each Module in a Slave Device

Number
Event
Error
detected by:
Message
3323
Module error occurred
STNss PB FIO k NODE mm SLOT nn Module Alarm STN zzz ID

0xXXXX MODULE yy
3325
Module error occurred (*1)
STNss PB FIO k NODE mm SLOT nn Module Invalid Alarm STN

zzz ID 0xXXXX MODULE yy
3327
Module irregularity
occurred (*1)
STNss PB FIO k NODE mm SLOT nn Module Wrong Alarm STN

3329
Module not mounted (*1)
STNss PB FIO k NODE mm SLOT nn No Module Alarm STN

3330
The above returned

to normal
STNss PB FIO k NODE mm SLOT nn Module Recover STN

Slave
device
N030908E.EPS
XXXX: Identification Number (Hexadecimal: Displayed with 0x added at the head)
yy: Module slot number (decimal)
*1:
These messages are displayed only for slave devices that transmit MODULE_STATUS (slave diagnostic information
that indicates the status of newly added modules in PROFIBUS-DPV1). These messages are not always displayed for
all slave devices.
Module slots are numbered starting from either 1 or 0, depending on the device.
The slot number is set to begin from 1 when performing settings in Communication I/O
Builder. However, you can set the slot number to be displayed in messages, starting from 0,
in System View.
IM 33S01B30-01E
<N3.9 Messages>
N3-90
Messages for Each Channel in a Slave Device

Number
Event
Error
detected by:
Message
3331
Short circuit
STNss PB FIO k NODE mm SLOT nn Channel Alarm STN zzz ID

0xXXXX MODULE yy CHANNEL ww short circuit
3333
Undervoltage

0xXXXX MODULE yy CHANNEL ww undervoltage
3335
Overvoltage

0xXXXX MODULE yy overvoltage
3337
Overload

0xXXXX MODULE yy CHANNEL ww overload
3339
Overtemperature

0xXXXX MODULE yy CHANNEL ww overtemperature
3341
Link break

0xXXXX MODULE yy CHANNEL ww link break
3343
Upper limit value

exceeded

0xXXXX MODULE yy CHANNEL ww upper limit value exceeded
3345
Lower limit value

exceeded

0xXXXX MODULE yy CHANNEL ww lower limit value exceeded
3347
Error

0xXXXX MODULE yy CHANNEL ww error
3349
Other errors

0xXXXX MODULE yy CHANNEL ww Error Type = vvvv
3350
The above error

returned to normal
STNss PB FIO k NODE mm SLOT nn Channel Recover STN zzz ID

0xXXXX MODULE yy CHANNEL ww
Slave
devices
N030909E.EPS
XXXX: Identification Number (Hexadecimal: Displayed with 0x added at the head)
yy: Module slot number (decimal), ww: Channel number (decimal), vvvv: Error type (decimal)
ALP111 Self-Diagnostic Messages

Number
Event
Error
detected by:
Message
3351
PROFIBUS
communication stop
STNss PB FIO k NODE mm SLOT nn Communication Stop (*1)
3352
PROFIBUS
communication recover
STNss PB FIO k NODE mm SLOT nn Communication Recover
ALP111
N030910E.EPS
STNss: Station name, k: Bus system number, mm: Node number, nn: Slot number
*1:
This message is relayed when the PROFIBUS communication section in an ALP111 stops independently. The
PROFIBUS communication section stops when Auto Clear is enabled and a slave device fails, or when a hardware
error is detected.
SEE ALSO
For precautions related to Auto Clear, see the following:
Procedure for Modifying a Project in N3.6.2, Operations with the PROFIBUS-DP Configurator
IM 33S01B30-01E

1B30 11

Uploaded by

Copyright:

Available Formats

1B30 11

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1B30 11

Uploaded by

Copyright:

Available Formats

Toc N-1

Overview of PROFIBUS ........................................................................ N1-1

What is PROFIBUS? ..................................................................................... N1-2

PROFIBUS-DP (ACP71) ........................................................................ N2-1

Overall Configuration ................................................................................... N2-2

Operating Environment ................................................................................ N2-4

PROFIBUS-DP Communication Module (ACP71) ....................................... N2-6

I/O Data .......................................................................................................... N2-8

Monitoring Slave Devices ........................................................................... N2-16

Assigning and Referencing a Slave Device ................................... N2-17

Slave Diagnostic Information ........................................................ N2-19

Engineering ................................................................................................. N2-23

Engineering Overview ................................................................... N2-24

Operations with the PROFIBUS-DP Configurator ......................... N2-30

Operations in System View ........................................................... N2-33

Operations with the Communication I/O Builder ............................ N2-37

Operations in Function Block Detail Builder .................................. N2-42

Operation and Monitoring .......................................................................... N2-43

Unusual Operations .................................................................................... N2-45

Start Operation ............................................................................. N2-46

Actions in the Event of Faults ........................................................ N2-49

Actions during Download .............................................................. N2-55

Actions during Online Maintenance ............................................... N2-56

Messages .................................................................................................... N2-61

System Alarm Messages .............................................................. N2-62

Fieldbus Messages ....................................................................... N2-64

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

PROFIBUS-DP (ALP111) ....................................................................... N3-1

Overall Configuration ................................................................................... N3-2

Operating Environment ................................................................................ N3-5

PROFIBUS-DPV1 Communication Module (ALP111) .................................. N3-7

I/O Data .......................................................................................................... N3-9

Monitoring and Diagnosing Devices ......................................................... N3-18

Overview of Slave Diagnostic Information ..................................... N3-19

Assigning and Referencing Slave Diagnostic Information ............. N3-27

Assigning and Referencing Device Specific Slave Diagnostic

Assigning and Referencing Module Slave Diagnostic

Assigning and Referencing Channel Slave Diagnostic

Assigning and Referencing Device Communication Status ........... N3-35

Engineering ................................................................................................. N3-36

Engineering Overview ................................................................... N3-37

Operations with the PROFIBUS-DP Configurator ......................... N3-42

Operations in System View ........................................................... N3-44

Operations in Communication I/O Builder ..................................... N3-48

Operations in Function Block Detail Builder .................................. N3-60

Operation and Monitoring .......................................................................... N3-61

Unusual Operations .................................................................................... N3-63

Actions in the Event of Faults ........................................................ N3-66

Actions during Download .............................................................. N3-77

Actions during Online Maintenance ............................................... N3-80

Messages .................................................................................................... N3-83

System Alarm Messages .............................................................. N3-84

Fieldbus Messages ....................................................................... N3-86

11th Edition : Oct.28,2004-00

<N1. Overview of PROFIBUS>

N1. Overview of PROFIBUS

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

<N1.1 What is PROFIBUS?>