Munication With Profibus Systems

Communication with
PROFIBUS Systems
IM 33K03P10-50E
IM 33K03P10-50E
2nd Edition

Introduction
The integrated production control system CENTUM VP is the new products of distributed control
system (DCS) for large and medium-small scale process control.
This manual is written for use as a part of reference manual describing the functional details of
CENTUM VP. This manual focuses on functionalities of PROFIBUS. You can read the required
chapters when you need the details on the PROFIBUS functionalities.
This manual consists of the following chapters:
Chapter 1 Overview of PROFIBUS

This chapter describes the overview of PROFIBUS.
Chapter 2 PROFIBUS-DP (ACP71)
This chapter describes the communications between an ACP71 communication module installed
to an FCS and one or more slave devices that support PROFIBUS-DP, and the engineering tasks
required.
Chapter 3 PROFIBUS-DP (ALP111)
This chapter describes the communications between an ALP111 communication module installed
to an FCS and one or more slave devices that support PROFIBUS-DP and the engineering tasks
required.
Chapter 4 PROFIBUS-DP(ALP121)
This chapter describes the communications between an ALP121 communication module installed
to an FCS and one or more slave devices that support PROFIBUS-DP and the engineering tasks
required.
Media No. IM 33K03P10-50E (DVD) 2nd Edition : Jun. 2012 (YK) IM 33K03P10-50E 2nd Edition : Jun.29,2012-00
All Rights Reserved Copyright © 2011, Yokogawa Electric Corporation
ii
CENTUM VP Document Map

Installation
CENTUM VP Licence CENTUM VP
Installation Management Security Guide
IM 33K01C10-50E IM 33K01C20-50E IM 33K01C30-50E
Engineering
Field Control Stations Function Blocks Function Blocks Function Blocks

Reference Overview Reference Vol.1 Reference Vol.2
IM 33K03E10-50E IM 33K03E21-50E IM 33K03E22-50E IM 33K03E23-50E
Function Blocks Human Interface Human Interface Engineering

Reference Vol. 3 Stations Reference Vol. 1 Stations Reference Vol. 2 Reference Vol. 1
IM 33K03E24-50E IM 33K03F21-50E IM 33K03F22-50E IM 33K03G21-50E
Consolidated Alarm
Engineering Engineering Management Software Batch Management
Reference Vol. 2 Reference Vol. 3 Reference System Reference
IM 33K03G22-50E IM 33K03G23-50E IM 33K03H20-50E IM 33K03J10-50E
SEBOL Communication with Communication with Communication

Reference Subsystems Using RIO Subsystems Using FIO Devices Reference
IM 33K03K10-50E IM 33K03L10-50E IM 33K03L20-50E IM 33K03M10-50E
Optional Functions Communication with Compliance with Generic Subsystem

Reference PROFIBUS Systems FDA: 21CFR Part 11 Gateway Reference
IM 33K03N10-50E IM 33K03P10-50E IM 33K03Q10-50E IM 33K03R10-50E
System Integration Unified Gateway Engineering Test

OPC Station Reference Station Reference Vnet/IP Guide
IM 33K03R20-50E IM 33K03R30-50E IM 33K10A10-50E IM 33K10H20-50E
Engineering
Engineering CENTUM FOUNDATION
FOUNDATION fieldbus
Tutorial APCS Data Access Library fieldbus Reference
Reference
Tutorial
IM 33K02E10-50E IM 33K15U10-50E IM 33K15P10-50E IM 33K20T10-50E
FOUNDATION fieldbus
Engineering Guide
IM 33K20T20-50E
Operation and Monitoring
HIS Operation Operating Messages

IM 33K02D10-50E IM 33K02D20-50E
Hardware
Peripherals Field Control Stations Input & Output Modules Turbomachinery I/O Modules
IM 33K50C10-50E IM 33K50E40-50E IM 33K50G10-50E IM 33K10U10-50E
Communication Devices Migrated-FCS(FIO)

IM 33K50D10-50E IM 33K55W10-50E
IM 33K03P10-50E 1st Edition : Sep.22,2011-00

iii
Safety Precautions
n Safety, Protection, and Modification of the Product
• In order to protect the system controlled by the product as well as the product itself and
ensure safe operation, observe the safety precautions described in this user’s manual. We
assume no liability for safety if users fail to observe these precautions when operating the
product.
• If this product is used in a manner not specified in this user’s manual, the protection
provided by this product may be impaired.
• If any protection or safety circuit is required for the system controlled by the product or for
the product itself, prepare it separately and install it outside the product.
• When replacing parts or consumables, be sure to use the ones approved by Yokogawa
Electric Corporation (hereafter simply referred to as YOKOGAWA).
• Modification of the product is strictly prohibited.
• Do not use the product for any application not approved by YOKOGAWA.
• Do not use the accessories (power supply cord set, etc.) that came with the product for any
other products.
• The following symbols are used in the product and user’s manual to indicate that there are
precautions for safety:
Indicates that caution is required for operation. This symbol is placed on the product to refer
the user to the user’s manual in order to protect the operator and the equipment. In the
user’s manuals you will find precautions to avoid physical injury or death of the operator,
including electrical shocks.
Identifies a protective grounding terminal. Before using the product, ground the terminal.
Identifies a functional grounding terminal. Before using the product, ground the terminal.
Indicates an AC supply.
Indicates a DC supply.
Indicates that the main switch is ON.
Indicates that the main switch is OFF.

iv
n Notes on Handling User’s Manuals

• Please hand over the user’s manuals to your end users so that they can keep the user’s
manuals on hand for convenient reference.
• Please read the information thoroughly before using the product.
• The purpose of these user’s manuals is not to warrant that the product is well suited to any
particular purpose but rather to describe the functional details of the product.
• YOKOGAWA reserves the right to make improvements in the user’s manuals and product at
any time, without notice or obligation.
• If you have any questions, or you find mistakes or omissions in the user’s manuals, please
contact our sales representative or your local distributor.
n Warning and Disclaimer

The product is provided on an “as is” basis. YOKOGAWA shall have neither liability nor
responsibility to any person or entity with respect to any direct or indirect loss or damage arising
from using the product or any defect of the product that YOKOGAWA can not predict in advance.
n Notes on Software
• YOKOGAWA makes no warranties, either expressed or implied, with respect to the
software’s merchantability or suitability for any particular purpose, except as specified in the
terms of warranty.
• This product may be used on a machine only. If you need to use the product on another
machine, you must purchase another product.
• It is strictly prohibited to reproduce the product except for the purpose of backup.
• Store the DVD-ROM (the original medium) in a safe place.
• It is strictly prohibited to perform any reverse-engineering operation, such as reverse
compilation or reverse assembling on the product.
• No part of the product may be transferred, converted or sublet for use by any third party,
without prior written consent from YOKOGAWA.

Documentation Conventions
n Typographical Conventions
The following typographical conventions are used throughout the user’s manuals:
l Commonly used conventions throughout user’s manuals:
Character string to be entered:

The characters that must be entered are shown in monospace font as follows:
Example:
FIC100.SV=50.0
“▼” Mark
This symbol indicates the description for an item for which you should make a setting in the
product’s engineering window.
While operating an engineering window, the help information for the selected item can be
accessed from “Builder Definition Items” in the Help menu.
Listing more than one definition item after this symbol implies that the paragraph on the page
describes more than one definition item.
Example:
▼ Tag Name, Station Name
“Δ” Mark
Indicates a space between character strings that must be entered.
Example:
. ALΔPIC010Δ-SC
Character string enclosed by brackets ({ }):

Indicates an option that can be omitted.
Example:
. PRΔTAG{Δ.sheet name}

vi
l Conventions used to show key or button operations:
Characters enclosed by brackets ([ ]):

Characters enclosed by brackets within any description on a key or button operation, indicate
either a key on the HIS (Human Interface Station) keyboard, a key on the operation keyboard, a
button name on a window, or an item displayed on a window.
Example:
To alter the function, press the [ESC] key.
l Conventions used in command syntax or program statements:

The following conventions are used within a command syntax or program statement format:
Characters enclosed by angle-brackets:

Indicate character strings that user can specify freely according to certain guidelines.
Example:
#define <Identifier><Character string>
“...” Mark
Indicates that the previous command or argument may be repeated.
Example:
Imax (arg1, arg2, ...)
Characters enclosed by brackets ([ ]):

Indicate those character strings that can be omitted.
Example:
sysalarm format_string [output_value ...]
Characters enclosed by separators (| |):

Indicate those character strings that can be selected from more than one option.
Example:
opeguide <format_character_string> [, <output_value> ...]
OG,<element number>

vii
n Symbol Marks
Throughout this user’s manual, you will find several different types of symbols are used to identify
different sections of text. This section describes these icons.
CAUTION
Identifies instructions that must be observed in order to avoid physical injury and electric
shock or death of the operator.
WARNING
Identifies instructions that must be observed in order to prevent the software or hardware
from being damaged or the system from becoming faulty.
IMPORTANT
Identifies important information required to understand operations or functions.
TIP
Identifies additional information.
SEE
ALSO
Identifies a source to be referred to.

Clicking a reference displayed in green can call up its source, while clicking a reference
displayed in black cannot.
n Drawing Conventions
Some drawings may be partially emphasized, simplified, or omitted, for the convenience of
description.
Some screen images depicted in the user’s manual may have different display positions or
character types (e.g., the upper / lower case). Also note that some of the images contained in this
user’s manual are display examples.

viii
Copyright and Trademark Notices

n All Rights Reserved
The copyright of the programs and online manuals contained in the DVD-ROM or CD-ROM shall
remain in Yokogawa.
You are allowed to print out the required pages of the online manuals for using the product,
however, you are not allowed to print out the entire document. You can purchase the printed
manual from Yokogawa.
Except as stated above, no part of the online manual may be reproduced, either in electronic
or written form, registered, recorded, transferred, sold or distributed (in any manner including
without limitation, in the forms of paper documents, electronic media, films or transmission via the
network).
n Trademark Acknowledgments
• CENTUM, ProSafe, Vnet/IP, PRM, Exaopc and STARDOM are registered trademarks of
YOKOGAWA.
• Microsoft, Windows, Windows Vista, Visual Basic, Visual C++ and Visual Studio are either
registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries.
• Adobe, Acrobat and Acrobat Reader are either registered trademarks or trademarks of
Adobe Systems Incorporated in the United States and/or other countries.
• Ethernet is a registered trademark of XEROX Corporation.
• Java is a registered trademark of Sun Microsystems,Inc.
• MELSEC is a registered trademark of Mitsubishi Electric Corporation.
• Modicon and Modbus are registered trademarks of Schneider Electric SA.
• Memocon-SC is a registered trademark of Yaskawa Electric Corporation.
• PLC is a registered trademark of Rockwell Automation, Inc.
• SYSMAC is a registered trademark of OMRON Corporation.
• SIEMENS and SIMATIC are registered trademarks of Siemens Industrial Automation Ltd.
• FOUNDATION in FOUNDATION fieldbus is a registered trademark of Fieldbus Foundation.
• SmartPlant is a registered trademark of Intergraph Corporation.
• HART is a registered trademark of the HART Communication Foundation.
• PROFIBUS is a trademark of the PROFIBUS User Organization.
• All other company and product names mentioned in this user’s manual are trademarks or
registered trademarks of their respective companies.
• We do not use TM or ® mark to indicate those trademarks or registered trademarks in this
user’s manual.
• We do not use logos and logo marks in this user's manual.
IM 33K03P10-50E 2nd Edition : Jun.29,2012-00

Toc-1
CENTUM VP
Communication with PROFIBUS Systems
IM 33K03P10-50E 2nd Edition
CONTENTS
1. Overview of PROFIBUS............................................................................ 1-1
1.1 What is PROFIBUS?.......................................................................................... 1-2
2. PROFIBUS-DP (ACP71)............................................................................ 2-1
2.1 Overall Configuration........................................................................................ 2-2
2.2 Operating Environment..................................................................................... 2-4
2.3 PROFIBUS-DP Communication Module (ACP71).......................................... 2-5
2.4 I/O Data................................................................................................................ 2-7
2.5 Monitoring Slave Devices............................................................................... 2-15
2.5.1 Assigning and Referencing a Slave Device..................................... 2-16
2.5.2 Slave Diagnostic Information............................................................ 2-18
2.6 Engineering...................................................................................................... 2-22
2.6.1 Engineering Overview....................................................................... 2-23
2.6.2 Operations with the PROFIBUS-DP Configurator............................ 2-28
2.6.3 Operations in System View............................................................... 2-31
2.6.4 Operations with the Communication I/O Builder.............................. 2-35
2.6.5 Operations in Function Block Detail Builder..................................... 2-40
2.7 Operation and Monitoring............................................................................... 2-41
2.8 Unusual Operations......................................................................................... 2-43
2.8.1 Start Operation.................................................................................. 2-44
2.8.2 Actions in the Event of Faults........................................................... 2-47
2.8.3 Actions during Download.................................................................. 2-52
2.8.4 Actions during Online Maintenance.................................................. 2-53
2.9 Messages.......................................................................................................... 2-58
2.9.1 System Alarm Messages.................................................................. 2-59
2.9.2 Fieldbus Messages........................................................................... 2-61
3. PROFIBUS-DP (ALP111)........................................................................... 3-1
3.1 Overall Configuration........................................................................................ 3-2
3.2 Operating Environment..................................................................................... 3-5
3.3 PROFIBUS-DP Communication Module (ALP111)......................................... 3-6
3.4 I/O Data................................................................................................................ 3-8

Toc-2
3.5 Monitoring and Diagnosing Devices............................................................. 3-17
3.5.1 Overview of Slave Diagnostic Information........................................ 3-18
3.5.2 Assigning and Referencing Slave Diagnostic Information............... 3-26
3.5.3 Assigning and Referencing Device Specific Slave Diagnostic
Information........................................................................................ 3-28
3.5.4 Assigning and Referencing Module Slave Diagnostic
Information........................................................................................ 3-30
3.5.5 Assigning and Referencing Channel Slave Diagnostic
Information........................................................................................ 3-31
3.5.6 Assigning and Referencing Device Communication Status............. 3-34
3.6 Engineering...................................................................................................... 3-35
3.6.1 Engineering Overview....................................................................... 3-36
3.6.2 Operations with the PROFIBUS-DP Configurator............................ 3-41
3.6.3 Operations in System View............................................................... 3-43
3.6.4 Operations in Communication I/O Builder........................................ 3-47
3.6.5 Operations in Function Block Detail Builder..................................... 3-59
3.8.1 Actions in the Event of Faults........................................................... 3-65
3.8.2 Actions during Download.................................................................. 3-76
3.8.3 Actions during Online Maintenance.................................................. 3-79
3.9 Messages.......................................................................................................... 3-83
3.9.2 Fieldbus Messages........................................................................... 3-86
4. PROFIBUS-DP (ALP121)........................................................................... 4-1
4.1 System Configuration....................................................................................... 4-2
4.1.1 Overall Configuration.......................................................................... 4-3
4.1.2 Operating Environment....................................................................... 4-5
4.1.3 Application Capacity........................................................................... 4-7
4.2 PROFIBUS-DP Communication Module (ALP121)......................................... 4-8
4.2.1 Redundant Configuration.................................................................... 4-9
4.2.2 I/O Data............................................................................................. 4-14
4.3 System Builders............................................................................................... 4-22
4.3.1 Overview of Engineering of ALP121................................................. 4-23
4.3.2 Engineering Procedures................................................................... 4-27
4.3.3 System View..................................................................................... 4-38
4.3.4 GSD File............................................................................................ 4-43
4.3.5 Communication I/O Definition Support Tool..................................... 4-44
4.3.6 Function Block Detail Builder............................................................ 4-47
4.3.7 Checking before PROFIBUS Communication Definition
Downloading..................................................................................... 4-48
4.3.8 Saving PROFIBUS Communication Definitions, Downloading
PROFIBUS Communication Definitions........................................... 4-49

Toc-3
4.3.9 Advanced Engineering..................................................................... 4-50
4.3.10 Messages.......................................................................................... 4-68
4.4.1 FCS Status Display View.................................................................. 4-70
4.5.1 Actions in the Event of Prolonged FCS Power Failure..................... 4-73
4.5.2 Actions in the Event of Momentary FCS Power Failure................... 4-74
4.5.3 Actions in the Event of Prolonged CPU Power Failure.................... 4-75
4.5.4 Actions in the Event of Momentary Power Failure of CPU............... 4-77
4.5.5 Path Errors........................................................................................ 4-78
4.5.6 Actions in the Event of CPU Control-right Transfer.......................... 4-79
4.5.7 Actions in the Event of Prolonged FIO Node Power Failure............ 4-80
4.5.8 Actions in the Event of Momentary FIO Node Power Failure........... 4-81
4.5.9 Actions in the Event of Failure/Maintenance of an ALP121............. 4-82
4.5.10 Actions in the Event of ALP121 Control-right Transfer..................... 4-83
4.5.11 Actions in the Event of Disconnected PROFIBUS-DP
Communication................................................................................. 4-84
4.5.12 Actions in the Event of Slave Device Failure/Maintenance.............. 4-85
4.6 System Operations during Download........................................................... 4-86
4.6.1 Operation during Offline Download to an FCS................................. 4-87
4.6.2 Operation during ALP121 IOM Download........................................ 4-88
4.6.3 System Operation during ALP121 Definition Change Download..... 4-89
4.7 Messages.......................................................................................................... 4-98
4.7.2 Fieldbus Messages.........................................................................4-102

Blank Page
<1. Overview of PROFIBUS> 1-1
1. 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.

<1.1 What is PROFIBUS?> 1-2
1.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 two 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 two types of variations:
• PROFIBUS-DP
• PROFIBUS-PA
n 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.
n 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.
TIP
The information contained in this section is excerpted from the Japan PROFIBUS Organization’s website.
The Profibus interface provided by Yokogawa is in the category of PROFIBUS-DP.

<2. PROFIBUS-DP (ACP71)> 2-1
2. 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-DP communication, which are implemented by the ALP111, if any.

<2.1 Overall Configuration> 2-2
2.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 CENTUM VP system and the PROFIBUS-DP interface using ACP71 modules.
n 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-DP
PROFIBUS configurator
definition (manufactured by Hilscher)
data file
Copy
System builders Operation and Monitoring
System Historical
System Communication Function Block FCS Status
Alarm Message
View I/O Builder Detail Builder Display view
view Report window
Control bus
FCS ACP71 ACP71 Slave device
operating Fail/Recover diagnostic
status message information
Download
PROFIBUS-DP
communication
I/O data
PROFIBUS-DP
communication module (ACP71)
PROFIBUS-DP I/O data
Slave device Slave device

N020101E.ai
Figure Overall Configuration of Communication with PROFIBUS-DP

l PROFIBUS-DP Communication Module (ACP71)
Communicates with slave devices and exchanges sent/received I/O data with PROFIBUS-DP
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.
l PROFIBUS-DP Communication
Exchanges I/O data with an ACP71 and stores the results in the communication I/O data-storage
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.
l 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.
l 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.
l Operation and Monitoring

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

<2.2 Operating Environment> 2-4
2.2 Operating Environment

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

The following explains the operating environment, including hardware and software.
l Hardware Environment
The following hardware environment is required for communication with PROFIBUS-DP.
Table Hardware Operating Environment
Type Hardware Remarks
Communication module ACP71
Nest AMN52 Nest for communication module (for PROFIBUS)
Note: 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
Without repeaters: Maximum of 31 units/ACP71 (*1)
Slave device
With repeaters: Maximum of 124 units/ACP71
Repeater A device that connects multiple PROFIBUS-DP segments.
This prevents electrical signal reflections. A terminator is required at both
Terminator
ends of a communication cable.
T-shape connector This is used to connect an ACP71 to PROFIBUS-DP.
*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.
l PROFIBUS-DP Configurator
A third-party configurator is required for PROFIBUS-DP engineering.
• SYCON-PB/YOKO (Product of Hilscher Co.)
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
Organization’s website.
SEE
ALSO For more information about the operation environment, refer to:
The users’s manual of Hilscher Co. for SYCON-PB/YOKO.

<2.3 PROFIBUS-DP Communication Module (ACP71)> 2-5
2.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
n Mounting Format
A maximum of four ACP71s can be mounted per one FCS by using a PROFIBUS communication
module nest (AMN52). (*1)
*1: Can only be applied to SFCS and enhanced type PFCS.
n 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 CPU
(AMN52)
Nest 3 Nest 4 Nest 5
N020301E.ai
Figure Nest Configuration

<2.3 PROFIBUS-DP Communication Module (ACP71)> 2-6
n 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
n 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
n 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 destination’s 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
ACP ACP
Range of I/O data communication 71 71
by single ACP71
PROFIBUS-DP
Slave device Slave device Slave device Slave device
N020302E.ai
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.

<2.4 I/O Data> 2-7
2.4 I/O Data

I/O data resulting from communication via an ACP71 is accessed from a function block or
Graphic view 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
n 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.
Communication I/O data area %WB bit number
01 08, 09 16
%WW0101
Data (first byte) Data (second byte)
%WW0102 Value in the free area is undefined
Data (third byte) Data (fourth byte)
%WW0103
Data (fifth byte) Free area
N020401E.ai
Figure Storing to the I/O Data Area

<2.4 I/O Data> 2-8
n 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.
01 08, 09 16
%WW0101
Data (first byte)
%WW0102
Data (second byte)
%WW0103
Data (third byte)
N020402E.ai
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 Before round-off After round-off
Less than -127 -127
Output (16-Bit Signed)
More than 128 128
Output (16-Bit Unsigned) More than 255 255
n 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.

<2.4 I/O Data> 2-9
n 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 0
Communication
I/O data area Data (first byte) Free area
% WB bit number
01 08, 09 16
%WW0101 N020404E.ai
Figure Reverse Bits
n 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.
l 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
1 Yes No Default: IS1 made by STAHL corresponds to this pattern.
2 Yes Yes VOS200 made by STAHL corresponds to this pattern.
3 No No
Under normal circumstances, there is no slave device
4 No Yes
that uses this pattern.

<2.4 I/O Data> 2-10
• Pattern 1
Upper-byte (first byte) Lower-byte (second byte)
Channel number 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8
(bit number)
x – – – – – – – – Input/Output 1
x – – – – – – – – – Input/Output 2
x – – – – – – – – – – Input/Output 3
x – – – – – – – – – – – Input/Output 4
x – – – – – – – – – – – – Input/Output 5
x – – – – – – – – – – – – – Input/Output 6
x – – – – – – – – – – – – – – Input/Output 7
x – – – – – – – – – – – – – – – Input/Output 8
– – – – – – – x Input/Output 9
– – – – – – x – Input/Output 10
– – – – – x – – Input/Output 11
– – – – x – – – Input/Output 12
– – – x – – – – Input/Output 13
– – x – – – – – Input/Output 14
– x – – – – – – Input/Output 15
x – – – – – – – Input/Output 16
N020408E.ai
Figure Mapping with Reverse Bits, but without Reverse Bytes
• Pattern 2
Channel number 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
(bit number)
x Input/Output 1
x – Input/Output 2
x – – Input/Output 3
x – – – Input/Output 4
x – – – – Input/Output 5
x – – – – – Input/Output 6
x – – – – – – Input/Output 7
x – – – – – – – Input/Output 8
x – – – – – – – – Input/Output 9
x – – – – – – – – – Input/Output 10
x – – – – – – – – – – Input/Output 11
x – – – – – – – – – – – Input/Output 12
x – – – – – – – – – – – – Input/Output 13
x – – – – – – – – – – – – – Input/Output 14
x – – – – – – – – – – – – – – Input/Output 15
x – – – – – – – – – – – – – – – Input/Output 16
N020409E.ai
Figure Mapping with Reverse Bits as well as Reverse Bytes

<2.4 I/O Data> 2-11
• Pattern 3
Channel number 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
(bit number)
x – – – – – – – – – – – – – – – Input/Output 1
x – – – – – – – – – – – – – – Input/Output 2
x – – – – – – – – – – – – – Input/Output 3
x – – – – – – – – – – – – Input/Output 4
x – – – – – – – – – – – Input/Output 5
x – – – – – – – – – – Input/Output 6
x – – – – – – – – – Input/Output 7
x – – – – – – – – Input/Output 8
x Input/Output 16
N020410E.ai
Figure Mapping without Reverse Bits or Reverse Bytes
• Pattern 4
Channel number 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7
(bit number)
x Input/Output 8
x – – – – – – – – – – – – – – – Input/Output 9
x – – – – – – – – – – – – – – Input/Output 10
x – – – – – – – – – – – – – Input/Output 11
x – – – – – – – – – – – – Input/Output 12
x – – – – – – – – – – – Input/Output 13
x – – – – – – – – – – Input/Output 14
x – – – – – – – – – Input/Output 15
x – – – – – – – – Input/Output 16
N020411E.ai
Figure Mapping without Reverse Bits, but with Reverse Bytes

<2.4 I/O Data> 2-12
n 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
Indicates a temporary status in which data could not be acquired due to a
NRDY
momentary power failure, power recovery, etc.
Indicates the occurrence of a communication module error or a communication
LPFL
error with a connected device.
NR (*1) Data has been acquired normally.
*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:
2.5.2, “Slave Diagnostic Information”
n 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.

<2.4 I/O Data> 2-13
n I/O Conversion Using a Function Block

▼ Element
l 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 For more information about subsystem communication, refer to:
1.3, “Accessing Subsystem Data from a Function Block” in the Communication with Subsystems Using RIO
(IM 33K03L10-50E)
l 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 block’s 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
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
SEE
ALSO For more information about the gain and bias specifications, refer to:
4.8.3, “Communication Output Conversion” in the Function Blocks Overview (IM 33K03E21-50E)

<2.4 I/O Data> 2-14
l 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.
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
SEE
ALSO For more information about Discrete I/O,refer to:
1.3, “Accessing Subsystem Data from a Function Block” in the Communication with Subsystems Using RIO
(IM 33K03L10-50E)
n 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, refer to:
SEBOL Reference (IM 33K03K10-50E)

<2.5 Monitoring Slave Devices> 2-15
2.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

2.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 view, 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.
n 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
..... .....
%WB(nnnn+1)01 Status of the slave device with node address 17
..... .....
Status of the slave device with node address X
%WBxxxxbb
X=(xxxx-nnnn)x16+bb
..... .....
%WB(nnnn+7)14 Not used
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
0 Slave device error
1 Slave device normal

n 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 Remarks
Size 1 to 8 Can be set according to the number of slave devices
Station ACP71 node address
Device & Address “STATUS”
Data type Input (Discrete)
Reverse Bits

2.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.
n 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
Error detected
Type Title Description
by:
Device common Station_Status1-3.
Common slave diagnostic information defined by the ACP71 or slave
slave diagnostic Master_Add.
PROFIBUS specifications device
information Ident_Number
Device specific
Device related Slave diagnostic information defined by the specifications of
slave diagnostic Slave device
diagnostic each slave device
information
Presence of an error in a slave device module or I/O channel is
Module slave Identifier related
indicated with a bit. This bit indicates an error if even one of the
diagnostic (module) Slave device
module’s I/O channels has experienced an error.
information diagnostic
(Bit assignment depends on the specifications of the device).
Slave diagnostic information for the module’s I/O channel.
Channel slave
Channel related Each I/O channel has a detail code (Error Type) such as
diagnostic Slave device
diagnostic short circuit. Error Type includes items defined by PROFIBUS
information
specifications and those defined by slave-device specifications.

n 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 module’s 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.”

Relative address
7 0 Bit number
0
0 1 Header information
Size of module slave diagnostic information
Fixed by the PROFIBUS specifications
7 0 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 0 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.ai
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
n 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:
2.9.2, “Fieldbus Messages”

n 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.
l 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.
% W area %WB bit number
01 08, 09 16 Bit number for each

byte of diagnostic data
0 7,0 7
%WW0101
%WW0102
%WW0103
Data (fifth byte) Data (sixth byte)
N020506E.ai
Figure Example of Assigning Slave Diagnostic Information
l 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
Size can be set according to the size of data for the
Size 1 to 128
part to be referenced
Slave device node
Station
address
Device & Address “DIAG”
Data type Input (Discrete)
Reverse No

<2.6 Engineering> 2-22
2.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.

2.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.
n Engineering Scope
The following shows the scope and targets for PROFIBUS engineering.
HIS
Control bus
Area engineered with

FCS FCS System builders
ACP71
Area engineered with the

PROFIBUS-DP configurator
Slave Slave
device device
N020601E.ai
Figure Engineering Scope
Table Engineering Target

PROFIBUS-DP
Engineering target System builders
configurator
HIS Yes No
FCS Yes No
ACP71 Yes Yes
Slave device No Yes
Yes: Applicable
No: 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.

n 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 ACP71’s dedicated RS port.
n Downloading PROFIBUS Definition Data

Configuration data created with the PROFIBUS-DP configurator (hereinafter called PROFIBUS
definition data) is downloaded to an ACP71 using the HIS’s 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

N020603E.ai
Figure Downloading PROFIBUS Definition Data

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 PROFIBUS-DP 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 ACP71’s 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.

n 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 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
(6)
Operation when Debug using the Test Function
there is no FCS
Operation when
there is an FCS (7)
Download
(8)
Debug PROFIBUS-DP
communication
(9)
Check for errors
END
N020604E.ai
Figure Engineering Procedures

l System Design
Design the function-block configuration, including the slave device, communication specifications
and control specifications.
l 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.
l 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.
l 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.
l 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.
l 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
l 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.
l Debug PROFIBUS-DP Communication

Connect the ACP71 and slave devices, then debug PROFIBUS-DP communication using the
PROFIBUS configurator.
l 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.

2.6.2 Operations with the PROFIBUS-DP Configurator

This section explains the following items regarding operations using the PROFIBUS-DP
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 User’s Manual.
n Procedure for Creating a New Project

1. Create a project.
The project herein refers to the database that comprises 1 segment of PROFIBUS-DP.
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/PKV20-DPM 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
U H1 H2 F
REVISION
U H1 H2 F 1 1 0 3
1 1 0 3
N020617E.ai
Figure Location of ACP71 Unit Revision Number

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 Cancel
Station address 0
Device ACP71
DP Support
DP Master Settings ... Auto addressing
FMS Support
FMS Settings ... CRL ...
CD ...
Actual Master
Module Information
Storage format Compact
N020618E.ai
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 (*2) will be created.
*2: 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.

n 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.

2.6.3 Operations in System View

This section explains the following items regarding operations in System view.
n 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.

n Details of System View

This section explains details of System View, in particular, the ACP71 property and IOM
download.
l 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 Remarks
Category Select “AMN52(PROFIBUS Communication)”
IOM Type
Type Select “ACP71(PROFIBUS-DP Communication interface)”
Only unit1 can be selected. This item cannot be selected if an IOM
Type and Unit
Installation Position other than ACP71 is set for that unit1 or if unit2 is used.
Position
Slot 1 to 4 slots can be selected.
High Speed Read Cannot be selected.
IOM Comment
Create New IOM

Type and Position Set Details
IOM Type
Category AMN52(PROFIBUS Communication)
Type ACP71(PROFIBUS-DP Communication interface)
Installation Position
Unit 1 Slot 1
Duplicate Next Card
High Speed Read
IOM Comment
OK Cancel
N020606E.ai
Figure Create New IOM Dialog Box

l 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 Details Remarks
Category “AMN52(PROFIBUS Communication)”
IOM Type No
Type “ACP71(PROFIBUS-DP Communication interface)”
Type Installation Unit
and No
Position Slot
Position
High Speed
No Cannot be selected.
Read
IOM Comment Yes
IOM Category No
IOM Type No
Displays settings defined in the Type and position tab
Unit No
Slot No
Fallback operation is enabled/disabled by the check box.
Yes
By default, the setting is “enabled.” (box is checked)
Perform Fallback All points maintain
Yes Fallback operation is determined by the option button.
Current value
The default setting is “All points maintain Current value.”
Yes Reset all outputs
Set all corresponding Action upon the detection of module failure is determined
Yes module input data to by the check box. By default, the setting is “disabled.”
IOP (box is not checked)
Action when
Set all corresponding Action upon the detection of module failure is determined
module/channel
Yes module input data to by the check box. By default, the setting is “enabled.”
fail detected
Set OOP (box is checked)
Details
1st slot no. of field
Yes “0” or “1” can be selected. The initial value is “1.”
instruments in message
Displays the file name. Cannot be selected. The default
No File Name
is blank. Updated after [Copy] is executed.
Displays the time and date file was created. Cannot be
No Creation date selected. The initial value is blank. Updated after [Copy]
PROFIBUS is executed.
configuration Displays the time and date [Copy] was executed. Cannot
data file No Date copied be selected. The initial value is blank. Updated after
[Copy] is executed.
Clicking the [Copy] button displays the file selection
Yes [Copy] dialog box and copying is executed. (*1)
The filename extension is “DBM.”
The value set for each item is restored to the initial
[default] Yes value (except for detail items relating to the PROFIBUS
configuration data file).
Yes: Can be changed even after a new IOM has been created.
No: Cannot be changed once a new IOM has been created.
*1: 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.

Properties
IOM Category AMN52(PROFIBUS Communication)

IOM Type ACP71(PROFIBUS-DP Communication interface)
Unit 1 Slot 1
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'st slot no. of field instruments in message 1
PROFIBUS configuration data file

File Name
Creation date
Date copied
Copy
Default
OK Cancel
N020608E.ai
Figure ACP71 Property Sheet
l 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.

2.6.4 Operations with the Communication I/O Builder

This section explains the procedures and setting items concerning operations using the
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.
n 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.
n 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
Designates the size of the area for storing communication I/O definition data
Buffer
that is used in an ACP71.
Designates the installation position of an ACP71 (u-s, u: unit number (fixed to 1),
s: slot number) and the program name (PROFIBUS)
Program Name
Example: When slot 2 is designated
1-2PROFIBUS
n Communication I/O Items Set for Slave Device Modules
l Data to be Reflected from the PROFIBUS-DP Configurator to the

Communication I/O Builder
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

Slave device node address
Slave Configuration
General
Device COM-DPS Station address 2 OK
Description Slave#2 Cancel
Activate device in actual configuration
Parameter Data...
Enable watchdog control GSD file HIL_7501.GSD
Max. length of in-/output data 368 Byte Length of in-/output data 111 Byte
Max. length of input data 244 Byte Length of input data 69 Byte Assigned master
Max. length of output data 244 Byte Length of output data 42 Byte Station address 1
Max. number of modules 24 Number of modules 7
Master#1
Module Inputs Outputs In/Out Identifier
1/ACP71
64 byte output con [0x80, 0xBF] 64 byte 0x80, 0xBF
1 word output con [0xE0] 1 word 0xE0
Actual slave
2 word output con [0xE1] 2 word 0xE1 Station address 2
Slave#2
8 word output con [0xE7] 8 word 0xE7 2/COM-DPS
Slot Idx Module Symbol Type 1 Addr. 1 Len. Type 0 Addr. 0 Len.
1 1 1 byte input con [0x90] Module#1 IB 0 1 Append Module
2 1 4 byte input con [0x93] Module#2 IB 0 4
3 1 2 word output con [0xE1] Module#3 QW 0 2 Remove Module
4 1 32 word input [0x40, 0x5F] Module#4 IW 0 32
Insert Module
5 1 1 word output [0x60] Module#5 QW 0 1
6 1 16 word output [0x6F] Module#6 QW 0 16 Symbolic Names
7 1 2 word output con [0xE1] Module#7 QW 0 2
Module slot number

N020611E.ai
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 BusCon Station address 3 OK
Parameter Data...
Enable watchdog control GSD file EBH82079.GSD
Master#1
1/ACP71
H&B Var.80 1 Word 8 Word 0xD0, 0xF7, 0xDB,
Actual slave
Station address 3
Slave#3
3/BusCon
1 1 H&B Var.80 Module#1 IW 0 1 Append Module
1 2 H&B Var.80 Module#1 IW 0 8 QW 0 8
1 3 H&B Var.80 Module#1 IW 0 12 Remove Module
1 4 H&B Var.80 Module#1 IW 0 12
Insert Module
1 6 H&B Var.80 Module#1 IW 0 12 Symbolic Names
Index of data inside the module N020612E.ai
Figure Slave Configuration Dialog Box (With Multiple Indexes)

l 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 Dialog
• Device & Address:
Slot and Idx for the Slave Configuration Dialog
• Data Type:
Enter according to the slave device module’s specifications.
• 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.

n 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
Input Details Remarks
item
Buffer Yes Sets the size of the entire area for storing the ACP71 data.
Sets the installation position of a module and “PROFIBUS.”
Example: When the module is loaded in unit 1, slot 2 1-2PROFIBUS
Program
Yes When the cursor is positioned over the program name, the program
Name
name is displayed in the list, according to the installation position of
the ACP71 that has been created, as in the case of ACMxx.
Sets the size to be assigned for a single slave device module.
The size is assigned on a word-by-word basis (in increments of 2
Size Yes 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.
Sets the IP address for other devices. Setting an IP address will
IP Address No
However, this is not used in this function. not generate an error.
Designating a non-existent
Sets the slave device node address.
slave device node address
Station Yes The valid range of values is from 0 to 125. However, entering a
will set data to IOP/OOP
value outside this range will not generate an error in the builder.
upon execution.
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.
Designating an unused or
Example: “1-3” when slot number=1 and index=3
Device & out of range slot number/
Yes Designate “;E” to expand byte data to 16 bits.
Address index will set data to IOP/
Example: 1-3;E
OOP upon execution.
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.
Yes: Input is required.
No: Input is not required.
-: Can be omitted.

Table Definition Items in the Communication I/O Builder (2/2)
Definition
Input Details Remarks
item
Set according to the slave device module specifications.
Data Type Yes
The default setting is blank.
Sets whether or not to reverse the bit arrangement in the
FCS and bit arrangement in the subsystem. Only when the data type
The Reverse Bits may be selected as follows: is Input (Discrete) or
Reverse Yes
• Bits Output (Discrete), Bits
• No reverse can be selected.
The default setting is “Bits.”
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:
Scan Yes
• Normal
• Fast
The default setting is “Normal.”
Service
- A comment can be set.
Comment
The I/O terminal name can be set as a user-defined label.
Label -
This item is an optional setup item.
Yes: Input is required.
No: Input is not required.
-: Can be omitted.

2.6.5 Operations in Function Block Detail Builder

Operations on Function Block Detail Builder will be explained as follows.
n 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 Item Details Setting Contents
Basic or Output Output signal Output signal “Communication output
(optional item setup) conversion conversion type (Fully-open/Tightly-shut)”
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 Remarks
Data Conversion Gain 1.000 Same as in the case of “Communication
Data Conversion Bias 0.000 Output”
Output Value for Full-open 106.25
Same as in the case of “No”
Output Value for Tight-shut -17.19
SEE
ALSO For more information on output signal conversion, see the following:
“l Output Signal Conversion” in “n Output Processing Common to Regulatory Control Block” in 4,
“Output Processing” in the Function Blocks Overview (IM 33K03E21-50E)

<2.7 Operation and Monitoring> 2-41
2.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:
2.9, “Messages”
n FCS Status Display View

The status of an ACP71 is displayed in the FCS Status Display view 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 Remarks
configuration data (*1) configuration data (*2)
Create new Green Red
IOM download Green Red
Status immediately after
ACP71 Before IOM download Red Red
replacement
replacement
After IOM download Green Red
PROFIBUS configuration data
FCS offline download Green Red
is not subject to download
*1: Indicates that copying of PROFIBUS configuration data is completed in System view.
*2: Indicates that operations with the PROFIBUS-DP configurator are incomplete or that copying of PROFIBUS configuration data is
not performed in System view.

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 view. 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 view.
.SF FCS0101 FCS Status Display

FCS
FCS
IOM
MYPJT Domain : 01 V net1 V net2

FCS0101 1 2 AUT
Distillation column A Not Ready
Stand-By
Station No :1
Control
Type : PFCD-H Hard Ready
Revision : R4.03. 00 Maintenance
Generation : A A A A C C P P
10/22/2010 13 : 29 C C C C P P S S
P P P P U U U U
7 7 7 7
CPU Idle Time : 57Sec 1 1 1 1
Comn Load Ave : 0%
Cur : 0%
Test Mode : OFF
ControlStatus : RUN
I/O (OFF) : 3 4 5
Comm I/O : ON
Task Status :
Task 1 : RUN
Task 2 : RUN A A A A A A A A
Task 3 : RUN C C M M D D D D
M M M M M M M M
Task 4 : RUN 1 1 2 2 1 1 5 5
1 1 2 2 2 2 1 1
T T C C C C
Ready
N020702E.ai
Figure FCS Status Display View
In the FCS Status Display view, the following data can be downloaded to the ACP71 by clicking
the [Load IOM] button.
• PROFIBUS configuration data
• ACP71 program

<2.8 Unusual Operations> 2-43
2.8 Unusual Operations

This chapter explains unusual operations in PROFIBUS-DP communication.

2.8.1 Start Operation

The following explains the status of an ACP71 at the time of initial cold start and restart.
n 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
Initial cold start MAN fallback Reads new input values. Resets output values (*1).
Retains the status prior to Reads new input values.
Restart
power failure Resets outputs, then re-outputs the value prior to power failure (*1).
*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.

n Initial Cold Start Actions

This section explains the actions of devices at the time of an initial cold start.
l 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.
l 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
device’s specifications determine whether the fail-safe function is enabled and how the slave
device outputs data in the fail-safe status.
Occurrence of Power recovery
power failure
CPU action
status
Function block AUT MAN

mode
ACP71 output Output begins from reset status (0)
Slave device
output
Enters the fail-safe status when the

fail-safe monitoring time is up
Fail-safe monitoring time

N020802E.ai
Figure Actions at Initial Cold Start

n Restart Actions
This section explains the actions of devices at restart.
l 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.
l 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 device’s
specifications determine whether fail-safe function is enabled and how the slave device outputs
data in the fail-safe status.
Occurrence of Power recovery
power failure
CPU action
status
Function block AUT AUT

mode
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.ai
Figure Actions at Restart

2.8.2 Actions in the Event of Faults

This section explains the actions in the event of faults.
n 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
FCS control operation ACP71 output action Slave device output action
Power Failure/
Failure Mode When a failure When power When a failure When power When a failure When power
occurs is recovered occurs is recovered occurs is recovered
Initial cold start Output reset or Fail-safe Output reset or

FCS power failure - -
or restart output restart operation (*1) output restart
FCU action stop - Initial cold start Output fallback Output restart Output fallback Output restart
Fail-safe
ACP71 failure MAN fallback Output restart - Output reset Output reset
operation (*1)
ACP71 Fail-safe
MAN fallback Output restart - Output reset Output reset
maintenance operation (*1)
PROFIBUS Fail-safe
MAN fallback Output restart - Output restart Output restart
transmission stop operation (*1)
Slave device
MAN fallback Output restart - Output restart - Output restart
failure
Slave device
MAN fallback Output restart - Output restart - Output restart
maintenance
Slave device
single power MAN fallback Output restart - Output restart - Output restart
failure
FCS control-right
No change No changet No change No change No change No change
transfer
*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 device’s watchdog
timer. The watchdog timer settings are defined using the PROFIBUS-DP configurator.
IM 33K03P10-50E 2nd Edition : Jun.29.2012-00

n Actions in the Event of a Power Failure
l 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” in the Field Control Stations Reference (IM 33K03E10-50E)
l 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 power-supply
section of the slave device.
The ACP71 retains its previous output values when power is recovered following the slave-
device 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.
n 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

l 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

mode
Current value is retained

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

CPU operation stops Recovery
CPU operation
status

mode
Reset outputs
ACP71 output
Slave device 4 seconds

output
N020806E.ai
Figure Action when [Perform Fallback] is Enabled and [Reset all outputs] is checked.
l 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.
n Operations in the Event of Faults in the ACP71
l 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.
• FCS control operation
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 device’s specifications.
l System Operations during ACP71 Maintenance

The system operations during ACP71 maintenance are the same as during an ACP71 failure.
l 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.

n Operations in the Event of Faults in the Slave Device
l 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.
• FCS control operation
Performs a MAN fallback when the slave device failure occurs. Restarts previous output
values when ACP71 recoveries.
l 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 slave-device
failure.

2.8.3 Actions during Download

This section explains the actions during an offline download to the ACP71.
n 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
Action after IOM
Condition Action after offline download IOM download
download
When using a completely new
ACP71 module.
When the ACP71 is replaced Input becomes IOP. Reads new inputs and
Required
before offline download. Output becomes OOP. (*1) resets outputs (*2)
When there are changes to the
definition content (*3)
When there are no changes to Reads new inputs and resets
Not required -
the definition content outputs (*2)
*1: 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
*2: “Resets outputs” means that 0 is output for the analog output and discrete output.
*3: 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.

2.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
• I/O module configuration agreement
FCS
Communication
I/O definitions
Reflected?
Is the data downloaded?
ACP71
PROFIBUS
definition data
Is there agreement?

N020808E.ai
Figure Online Maintenance Status

n 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.
n 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

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 Action
Agreement Agreement During download After download
between between
PROFIBUS
PROFIBUS PROFIBUS
definition
Operation definition definition Function Function
data ACP71 ACP71
data and data and block block
downloaded?
communication slave device
I/O definitions configuration
Reads
Input is
new
IOP Reads new
Communication inputs
Output inputs
Agree with all slave Output
performs Resets outputs
Data in devices stops performs
MAN (*1)
agreement MAN
fallback
fallback
Input
Do not agree retains
Input is
previous No
IOP
Copied or value or corresponding
Output
recopied Data existing IOP I/O
performs
PROFIBUS Downloaded only in Output communication
- MAN
definition communication performs (*2)
fallback
data file I/O definitions MAN
fallback Communication
with all slave
Reads new
devices stops
inputs
Agree
Resets outputs
Data existing (*1)
only in
-(*3) -(*3) No
PROFIBUS
definition data corresponding
Do not agree I/O
communication
(*2)
*1: “Resets outputs” means that 0 is output for the analog output and discrete output.
*2: 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 device’s manual.
*3: There is no link to the function block, since there are no communication I/O definitions. Accordingly, the operation remains
unaffected.

Table Actions when ACP71 Properties are Changed (2/2)
between between
PROFIBUS
PROFIBUS PROFIBUS
definition
Operation definition definition Function Function
data ACP71 ACP71
downloaded?
Input
retains
previous Reads
Reads new
value or new inputs Reads new
inputs
become Output inputs
Data in Agree Outputs
IOP (*1) performs Outputs are
agreement previous
Output MAN re-output
output value
performs fallback
MAN
fallback
Do not agree Input is Input is
IOP No IOP No
Changed Data existing Output corresponding Output corresponding
ACP71’s Not only in performs I/O performs I/O
Set Details downloaded — MAN communication MAN communication
communication
only I/O definitions fallback (*3) fallback (*3)
(*2) (*2)
Reads new
Reads new
inputs
inputs
Agree Outputs
Outputs are
Data existing previous
re-output
only in output value
– (*4) – (*4)
PROFIBUS No No
definition data corresponding corresponding
Do not agree I/O I/O
communication communication
(*3) (*3)
*1: This can be selected using [IOM Online Updating] in the FCS property sheet.
*2: 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.
more information, refer to the device’s manual.
*4: There is no link to the function block since there are no communication I/O definitions. Accordingly, the operation remains
unaffected.
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 ACP71’s 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.

n 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
between between
Status of PROFIBUS
PROFIBUS PROFIBUS
PROFIBUS definition
definition definition Function Function
definition data ACP71 ACP71
data file downloaded?
Input
retains
previous Reads new
Reads new
value or inputs Reads new
inputs
become Output inputs
Data in Agree Outputs
IOP (*1) performs Outputs are
agreement previous
Output MAN re-output
output value
performs fallback
MAN
fallback
Copying Do not agree Input is
Input is IOP No
completed IOP I/O data not
Data existing Output corresponding
Output communicated
only in performs I/O
— performs to the subject
Not communication MAN communication
MAN device (*2)
downloaded I/O definitions fallback (*2)
fallback
Reads new Reads new
Data existing inputs inputs
only in Agree Outputs Outputs
– (*3) previous – (*3) previous
PROFIBUS
definition data output value output value
Do not agree
Input is No
Input is IOP I/O data not
Data existing IOP corresponding
Output communicated
only in Output I/O
Not copied — performs to the subject
communication performs communication
MAN device (*2)
I/O definitions MAN (*2)
fallback
fallback
*1: This can be selected using [IOM Online Updating] in the FCS property sheet.
more information, refer to the device’s manual.
*3: There is no link to the function block since there are no communication I/O definitions. Accordingly, the operation remains
unaffected.
n Deleting the ACP71’s Definition

This section explains the actions when the ACP71 definition is deleted.
All function blocks linked to the ACP71’s 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.

<2.9 Messages> 2-58
2.9 Messages
In PROFIBUS-DP communication, the following messages are displayed for the ACP71 or
slave device.
• System alarm messages
• Fieldbus messages

<2.9 Messages> 2-59
2.9.1 System Alarm Messages
n 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
Communication
0089 STNss SS-COM Error UNIT mm SLOT nn STN zzz CODE=####
error
Communication
0090 STNss SS-COM Recover UNIT mm SLOT nn STN zzz
recovery
STNss: Station name
mm: Unit number
nn: Slot number
zzz: 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.

<2.9 Messages> 2-60
n Error Codes Used for Communication Errors

The error codes used for communication errors include the following two types:
• Definition error
• Communication error
l 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 Action to take following the
Description
code error
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
Other device address invalid, entry data other than a numerical value
CAB6
detected in the index
CAB7 Other device address invalid, index value out of range
Other device address invalid, index value exceeding the specified Do not perform communication
CAB8
digits for the definition causing the
error. Check the definition
CAB9 Other device address invalid, delimiter character invalid
content in the builder.
Corresponding device (module or channel) not specified in
CABA
PROFIBUS definition data
CABB Data type incorrect, input designated for output data
CABC Data type incorrect, output designated for input data
Other device address invalid, entry data for slot number is not a
CABD
numerical value
CABE Other device address invalid, illegal character string detected
Other device address invalid, illegal character string detected
CABF
(expansion symbol)
l 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 Action to take following the
Description
code error
CA91 I/O data is not being communicated
CA92 Configuration error Retry communication
CA93 Slave device module error

<2.9 Messages> 2-61
2.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 device’s 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.
n 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.

<2.9 Messages> 2-62
n 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)
Error
Number Event Message detected
by:
Locked by another master STNss PB UNIT mm SLOT nn Station Alarm STN zzz ID 0xXXXX
3201
device Master_Lock (Master STN yyy)
ACP71
The above returned to STNss PB UNIT mm SLOT nn Station Recover STN zzz ID 0xXXXX
3202
normal Master_Lock
STNss PB UNIT mm SLOT nn Station Alarm STN zzz ID 0xXXXX
3203 Parameter setting failed
Param_Fault Slave
The above returned to STNss PB UNIT mm SLOT nn Station Recover STN zzz ID 0xXXXX device
3204
normal Param_Fault
Received an illegal frame STNss PB UNIT mm SLOT nn Station Alarm STN zzz ID 0xXXXX
3205
from the slave device Invalid_Slave_Response
ACP71
3206
normal Invalid_Slave_Response
Received a request for an STNss PB UNIT mm SLOT nn Station Alarm STN zzz ID 0xXXXX
3207
unsupported functions Not_Supported Slave
3208
normal Not_Supported
3209 Configuration error
Cfg_Fault Slave
3210
normal Cfg_Fault
3211 Cannot transmit data
Station_Not_Ready Slave
3212
normal Station_Not_Ready
STNss: Station name, mm: unit number, nn: Slot number, zzz: node address
XXXX: Ident Number (Hexadecimal: Displayed with “0x” added at the top).
yyy: Node address of the master device locking the slave device

<2.9 Messages> 2-63
Error
by:
Slave device not present STNss PB UNIT mm SLOT nn Station Alarm STN zzz ID 0xXXXX
3213
on the communication line Station_Non_Existent
ACP71
3214
normal Station_Non_Existent
Slave device is
3215 missing from the cyclic
Deactivated
transmission list ACP71
3216
normal Deactivated
Setting parameters or STNss PB UNIT mm SLOT nn Station Alarm STN zzz ID 0xXXXX
3217
checking configuration Param_Req
Slave device
3218
normal Param_Req
Expansion area for slave
3219 diagnostic information
Ext_Diag_Overflow ACP71 or
overflowed
slave device
3220
normal Ext_Diag_Overflow
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

<2.9 Messages> 2-64
n Slave Device Specific Messages

Slave device specific messages indicate errors defined by the device manufacturer.
These messages display the Slave Diagnostic Information’s Device Related portion as an error
code.
Error
Number Event Message
detected by:
Slave device error STNss PB UNIT mm SLOT nn Device Related Alarm STN zzz ID
3231
occurred 0xXXXX CODE = ZZZZZZZZZZ
Slave device
The above returned to STNss PB UNIT mm SLOT nn Device Related Recover STN zzz ID
3232
normal 0xXXXX
ZZZZZZZZZZ: Error code (Hexadecimal: Maximum 126 characters, with top 2 characters indicating the error code length (byte
length)).
n Messages for Each Module in the Slave Device

Error
detected by:
STNss PB UNIT mm SLOT nn Module Alarm STN zzz ID 0xXXXX
3241 Module error occurred
MODULE yy
Slave device
The above returned to STNss PB UNIT mm SLOT nn Module Recover STN zzz ID 0xXXXX
3242
normal MODULE yy
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.

<2.9 Messages> 2-65
n Messages for Each Channel in the Module

Error
by:
STNss PB UNIT mm SLOT nn Channel Alarm STN zzz ID 0xXXXX
3251 short circuit
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
upper limit value STNss PB UNIT mm SLOT nn Channel Alarm STN zzz ID 0xXXXX
3263
exceeded MODULE yy CHANNEL ww upper limit value exceeded
lower limit value STNss PB UNIT mm SLOT nn Channel Alarm STN zzz ID 0xXXXX
3265
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
STNss PB UNIT mm SLOT nn Channel Recover STN zzz ID
The above error
3270 0xXXXX
returned to normal
MODULE yy CHANNEL ww
yy: Module slot number (decimal), ww: Channel number (decimal), vvvv: Error type (decimal)
n ACP71 Self-Diagnostic Messages

Error
detected by:
PROFIBUS
3281 STNss PB UNIT mm SLOT nn Communication Stop (*1)
communication stop
ACP71
PROFIBUS
3282 STNss PB UNIT mm SLOT nn Communication Recover
communication recover
STNss: Station name, mm: Unit number, nn: Slot number
*1: 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.

Blank Page
<3. PROFIBUS-DP (ALP111)> 3-1
3. PROFIBUS-DP (ALP111)
The parts of the PROFIBUS-DP 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-DP, as well as the engineering tasks required.

3.1 Overall Configuration

I/O data communication with slave devices via PROFIBUS-DP 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 CENTUM VP system and PROFIBUS-DP using ALP111 modules.
n Configuration of Communication Function with PROFIBUS-DP

The figure below shows the general configuration of the communication function with
PROFIBUS-DP.
The System Builder, operation and monitoring, PROFIBUS-DP communication, and one or more
PROFIBUS-DP communication modules (ALP111) are included in the communication function
with PROFIBUS-DP.
Export PROFIBUS-DP
PROFIBUS configurator
definition (manufactured by
data file Hilscher)
Copy
System Builder Operation and Monitoring
FCS Status Historical

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

PROFIBUS-DP communication
N030101E.ai
Figure Overall Configuration of Communication Function with PROFIBUS-DP

l PROFIBUS-DP Communication Module (ALP111)
ALP111 modules communicate with slave devices and transfer sent or received I/O data to the
PROFIBUS-DP communication function.
ALP111 modules can operate as master devices of class 1 or class 2 according to the
PROFIBUS-DP specification.
The ALP111 modules can also acquire PROFIBUS-DP 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-DP to manage
slave device and perform I/O communication. The connection is established at all times for both synchronous
communication and asynchronous communication.
l PROFIBUS-DP 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.
l PROFIBUS-DP Configurator (Product of Hilscher Co.)

The PROFIBUS configurator defines ALP111 modules and slave devices for PROFIBUS-DP
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.
l 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.

l Operation and Monitoring
The following operations are available via operation and monitoring console.
• Downloading data to an ALP111 from the FCS Status Display view using IOM download,
and displaying the operating status of the ALP111 modules.
• Checking fail/recover messages of an ALP111 from the System Alarm view.
• Checking slave diagnostic information of devices from the Historical Message Report
window.

<3.2 Operating Environment> 3-5
3.2 Operating Environment

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

The following explains the hardware and software operating environment.
l Hardware Environment
The following hardware environment is required for communication with PROFIBUS-DP.
Type Hardware Remarks
Communication module ALP111
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
Without repeaters: Maximum of 31 units/ALP111 (*1)
Slave device
With repeaters: Maximum of 125 units/ALP111
Repeater A device that connects multiple PROFIBUS-DP segments
*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.
l PROFIBUS-DP Configurator
A third-party configurator is required for PROFIBUS-DP engineering.
• SYCON-PB/YOKO (Product of 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
Organization’s website.
SEE
ALSO For more information about the operating environment, refer to:
The SYCON-PB/YOKO’s Manual provided by Hilscher CO.

<3.3 PROFIBUS-DP Communication Module (ALP111)> 3-6

(ALP111)
The PROFIBUS-DP communication module (ALP111) is required for communication with
PROFIBUS-DP.
This section explains the items related to the PROFIBUS-DP 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
l Mounting Format
ALP111 can be installed in an ESB Bus Node (such as ANB10S or ANB10D) or in an ER Bus
Node Unit (such as ANR10S or ANR10D). However, for AFV30x and AFV40x, ER Bus Node is
not supported.
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, AGS813, AGP813, ALE111
and ALP111 can be installed for non-redundant configuration (for AFV30x or AFV40x, up to
32 modules; besides, mixed with ALF111 modules, the total can be 64); or 8 pairs of above
modules for redundant configuration (for AFV30x or AFV40x, up to 16 pairs).
l 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.

l Dual-Redundant Modules
The PROFIBUS-DP 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 ALP111 on the

controlling side standby side
I/O communication
Diagnostic communication
Slave Slave Slave

device 1 device 2 device 3
N030301E.ai
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.
l 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.
l Number of Assignable Communication I/O Definitions

A maximum number of communication I/O definitions that can be assigned to an ALP111 is 200.

<3.4 I/O Data> 3-8
3.4 I/O Data

I/O data resulting from communication via an ALP111 is accessed from a function block or
Graphic view 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
Hereinafter, for AFV30x and AFV40x, %WW will represent %WW and %XW, and %WB will
represent %WB and %XB.
IMPORTANT
For AFV30x and AFV40x, one ALP111 cannot be defined with both %WW and %XW.

<3.4 I/O Data> 3-9
n Data Types Supported by ALP111

Data types supported by the ALP111 are treated as follows in Communication I/O Builder and the
l 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 Name Data type
Input 16-bit signed integer data I16
16-bit unsigned integer data U16
32-bit signed integer data I32
32-bit signed floating point data F32
Bit data (discrete input) DI
Output 16-bit signed integer data I16
32-bit signed integer data I32
32-bit signed floating point data F32
Bit data (discrete output) DO
ALP111 modules may not guarantee simultaneous transmission of data of 32 bits or more; do not
use 64-bit floating point data types.
l 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.

<3.4 I/O Data> 3-10
n How to Define I/O Data

There are the three main ways to define communication data for PROFIBUS-DP 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.
l 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.
• 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.
SEE
ALSO • For more information about mapping of I/O data to the communication I/O data area and further details of
requirements foe employing this definition method, refer to:
“n How to Treat I/O Data as Analog I/O Data (in the Case of Specification for Each Channel and Channel
Batch Specification)” in 3.4, “I/O Data”
• For more information about channel slave diagnostic information, refer to:
3.5.1, “Overview of Slave Diagnostic Information”
l 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.
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.
SEE
ALSO For more information about mapping of I/O data to the communication I/O data area and further details of
requirements for employing this definition method, refer to:
“n How to Treat I/O Data as Analog I/O Data (in the Case of Specification for Each Channel and Channel
Batch Specification)” in 3.4, “I/O Data”

<3.4 I/O Data> 3-11
l 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.
n 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:
“n How I/O Data is Stored to the Communication I/O Data Area” in 2.4, “I/O Data”
n 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:
“n Treating I/O Data as Analog I/O Data” in 2.4, “I/O Data”
n 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:
“n Treating I/O Data as Discrete I/O Data” in 2.4, “I/O Data”

<3.4 I/O Data> 3-12
n 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
Communication I/O data area
I/O data (module 1)
16 bits I/O data (channel 0) %WW0049
I/O data (module 2) I/O data (channel 0)

I/O data (channel 1) %WW0051
I/O data (channel 1)
I/O data (module 3)
I/O data (channel 2) I/O data (channel 2) %WW0053
N030402E.ai
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) 2 (*1)
Analog input (32-bit signed integer data) 4
Analog input (16-bit unsigned integer data) 2 (*1)
Analog input (32-bit unsigned integer data) 4
Analog input (32-bit floating point data) 4
Analog input (64-bit floating point data) 8 (*2)
Analog output (16-bit signed integer data) 2 (*1)
Analog output (32-bit signed integer data) 4
Analog output (16-bit unsigned integer data) 2 (*1)
Analog output (32-bit unsigned integer data) 4
Analog output (32-bit floating point data) 4
Analog output (64-bit floating point data) 8 (*2)
*1: 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.
*2: 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.

<3.4 I/O Data> 3-13
n How to Treat I/O Data as Discrete I/O Data (in the Cases of
Specification for Each Channel and Channel Batch Specification)
l 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 [Bit positions of %WB]
00000000 01111111
Data for the size of the 12345678 90123456
DI input position
%WB area is copied.
00110110 11110000 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.ai
Figure Settings of Discrete Input Data

<3.4 I/O Data> 3-14
l 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 A bit corresponding to the
numbers are extracted. 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 . . . . . . . . . .1 MV
N030405E.ai
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
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
%WW000n 0 1 2 3 4 5 6 7 8 9 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.ai
Figure Correspondence between Channel Numbers and %WB Numbers

<3.4 I/O Data> 3-15
n 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:
“n Reverse Bits” in 2.4, “I/O Data”
n 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:
“n Reverse Bytes” in 2.4, “I/O Data”
n 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:
“n Data Statuses Handled for Subsystem” in 1.2, “Subsystem Data Identification” in the Communication
with Subsystems Using RIO (IM 33K03L10-50E)
• For details on slave diagnostic information, see the following:
3.5, “Monitoring and Diagnosing Devices”

The data update timing can be set in the item “Scan” on Communication I/O Builder.

<3.4 I/O Data> 3-16
n 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:
“n I/O Conversion Using a Function Block” in 2.4, “I/O Data”
n Access Using SEBOL

The use of a dedicated SEBOL statement allows access to I/O data communicated with
PROFIBUS-DP.
writing.
SEE
ALSO For details on SEBOL, see the following:

<3.5 Monitoring and Diagnosing Devices> 3-17
3.5 Monitoring and Diagnosing 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 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

3.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
• 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.
n 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
Error
Type Title Description
detected by:
Device common Station_Status1-3.
Common slave diagnostic information defined by the ALP111 or
slave diagnostic Master_Add.
PROFIBUS specifications slave device
information Ident_Number
Device specific
Device related Slave diagnostic information defined by the specifications of
slave diagnostic Slave device
diagnostic each device
information
The presence of an error in a device module or I/O channel
Module slave
Identifier related is indicated with a bit. This bit indicates an error if even one
diagnostic Slave device
(module) diagnostic of a module’s I/O channels has experienced an error. (Bit
information
assignment depends on the specifications of the device.)
Slave diagnostic information for a module’s I/O channels.
Channel slave Each I/O channel has a detail code (Error Type), such
Channel related
diagnostic as short circuit. Error Type includes items defined in Slave device
diagnostic
information the PROFIBUS specifications and those defined by the
specifications of a slave device.

n 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.

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 Bit number
0
0 1 Header information
Size of module slave diagnostic information
Fixed according to the PROFIBUS specifications
7 0 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 0 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.ai
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

n 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.
Input data
Communication
I/O data area Function blocks
Input Data
(Ch. x)
Input Data %W Data PV
Data Status IOP
Diagnostic
information Data Status
Channel
diagnostic
information (Ch. x)
N030503E.ai
Figure Error Diagnosis of Input Data
Output data
Communication
I/O data area Function blocks
Output Data
(Ch. y)
Output Data %W Data MV
Data Status OOP
Diagnostic
information Data Status
Channel
diagnostic
information (Ch. y)
N030504E.ai
Figure Error Diagnosis of Output Data
SEE
ALSO For more information about other information related to error diagnosis in the case of specification for each
channel and channel batch specifications, refer to:
“n Handling of Overflow Error (Common to All the Data Specification Methods)” in 3.5.1, “Overview of
Slave Diagnostic Information”

l 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
Set the bit corresponding

to the channel number
in %WB.

Input data
Communication
I/O data area
Function blocks
Input Data
Output data for
several channels Input Data %W Data PV
are packed. Diagnostic Data Status IOP
Data Status
information
Channel Input Data %W Data PV

diagnostic
information (Ch. x) Data Status IOP
Data Status
Channel
diagnostic
information (Ch. y) Input Data %W Data PV
Channel Data Status IOP
diagnostic Data Status
information (Ch. z)
N030505E.ai
Figure Setting the Data Status of Discrete Input Data

l 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
Only bits corresponding

to the specific channel Set the bit corresponding
numbers are extracted. to the channel number
in %WB.

Output data
Communication
I/O data area
Function blocks
1. . . . 1. . . 1 Output Data %W Data
Output data for
1. . . . . . . . . . 1. . . . . . . . . . MV
several channels
are packed. Data Status OOP
Diagnostic Data Status
information
Output Data %W Data
Channel . . . . . 1. . . . . . . . . 1. . . . MV
diagnostic
information (Ch. x) Data Status OOP
Data Status
Channel
diagnostic Output Data %W Data
information (Ch. y) ..........1 ..........1 MV
Channel Data Status OOP
diagnostic Data Status
information (Ch. z)
N030506E.ai
Figure Setting the Data Status of Discrete Output Data

n Reflecting Channel Slave Diagnostic Information in the Data Status

(in the Case of Specification for Each Channel and Channel Batch
Specification)
l 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.
l 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.
l 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.
• Set all corresponding module input data to IOP
• Set all corresponding module output data to OOP
l 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.

n 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.
l 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.
l 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.
n 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:
3.9.2, “Fieldbus Messages”

3.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.
n 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.
l 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
%W area Bit numbers of %WB
01 08, 09 16 Bit number of each byte

7 0,7 0 of diagnostic data
%WW0101
%WW0102
%WW0103
N030508E.ai
Figure Example of Assigning Slave Diagnostic Information

l 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
Specify the size according to the data amount of the
Size 1 to 128 (words)
area to be referenced.
Node address of
Station
slave device
Device & Address “DIAG”
Data Type Input (Discrete)
Reverse No

3.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.
n 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.
01 08, 09 16 Bit number of each byte of device

7 0,7 0 specific slave diagnostic information
%WW0101
%WW0102
%WW0103
N030510E.ai
Figure Example of Assigning Device Specific Slave Diagnostic Information
n 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.
l When Errors Occur in Communication with Slave Devices

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

When slave diagnostic information overflows, and device specific slave diagnostic information is
not available.

n 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
Node address of
Station
slave device
Device & Address “DIAG_DEV”
Reverse No

3.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.
n 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

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).
l When Errors Occur in Communication with Slave Devices

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

When slave diagnostic information overflows, and module slave diagnostic information is not
available.
n 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
Node address of
Station
slave device
Device & Address “DIAG_MOD”
Reverse No

3.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.
n 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.
01 08, 09 16 Bit number of each byte of channel

7 0,7 0 slave diagnostic information
%WW0101
%WW0102 First channel slave
Data (third byte) 0 diagnostic information
%WW0103
Second channel slave
Data (third byte) 0 diagnostic information
N030513E.ai
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 Error is notified by channel
Normal ALP111 detected errors (*1)
slave diagnostic information
Value of first byte 0 0
Data received from a slave device
Value of second byte 0 0
is set as is.
Value of third byte 0 0xFF
Value of fourth byte 0 0 0
*1: Errors detected by an ALP111 are explained in the following.


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.
l When Errors Occurs in Communication with Slave Devices

When slave devices become faulty or communication errors such as configuration errors 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.
l 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.

n 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
Specify the size as (number of consecutive channels
to be referenced) x 2 (words).
Node address of a
Station
slave device
Device & Address See the table below.
Reverse No
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
Specify the slot number of a module of a slave device. Describe them
Slot number D3
after the identifier “D” in the range of 1 to 60.
Index Specify an index of a module in the range 1 to 60 after “-.” D3-1
A semicolon divides parts of module specification and expansion part
Semicolon (;) D3-1;1
including channel specification.
Specify the channel number of a module in the range 0 to 99. If this is
Channel number D3-1;1
omitted, the channel number is regarded as 0.
l 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

3.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 view or output a message for sequence control.
The response states of all slave devices can be assigned using a single communication
I/O definition.
n 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:
“n Correlation to the Element Number” in 2.5.1, “Assigning and Referencing a Slave Device”
n Communication I/O Builder

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
Size 1 to 8 Specify according to the number of slave devices.
Station No. Node address of an ALP111
Device & Address “STATUS”
Reverse Bits

3.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.

3.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.
n Engineering Scope
The following figure and table show the scope and targets for PROFIBUS engineering.
HIS
Control bus
Area engineered
FCS FCS with System Builder
ALP111
Area engineered
with the PROFIBUS-DP
Slave Slave configurator
device device
N030601E.ai
Figure Engineering Scope
Table Engineering Target

PROFIBUS-DP
Engineering target System Builder
configurator
HIS x
FCS x
ALP111 x x
Slave device x
x: 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.

n About ALP111 Engineering

The PROFIBUS-DP configurator is used to create PROFIBUS-DP 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.
n 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

N030603E.ai
Figure Downloading PROFIBUS Definition Data

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 ALP111’s 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.

The following chart shows the basic engineering procedures using System Builder and the
Settings in System Builder can be performed along with settings in the PROFIBUS-DP
configurator.
(1)
System design
Engineering operations Engineering operations with

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
(6)
Debug using the test function
Operations not
involving an FCS
Operations
involving an FCS (7)
Download
(8)
Debug PROFIBUS-DP
communication
(9)
Check for errors
END
N030604E.ai

l System Design
Design the function-block configuration including slave devices, communication specifications
and control specifications.
l 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.
l 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.
l 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.
l 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.
l 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
l 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.
l Debug PROFIBUS-DP Communication

Connect the ALP111 and slave devices, then debug the PROFIBUS-DP communication using
the PROFIBUS-DP configurator.
l 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.

3.6.2 Operations with the PROFIBUS-DP Configurator

This section explains the following items regarding operations using the PROFIBUS-DP
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 User’s Manual.
n Procedure for Creating a New Project

1. Create a project.
The project herein refers to a database that comprises 1 segment of PROFIBUS-DP.
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.


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

3.6.3 Operations in System View

This section explains the following items regarding operations in System view.
n 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.
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-DP Communication” in [Category]
and “PROFIBUS-DP 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.
SEE
ALSO For more information about the setting on the Create New Node dialog box, refer to:
“n Creating a New Node : FFCS Series/KFCS2/KFCS” in 2.5.1, “Creating a Node” in the Engineering
Reference Vol.1 (IM 33K03G21-50E)

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.

n Details of System View

This section explains details of System View, in particular, the ALP111 properties and IOM
download function.
l 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 Detail Remarks
Category Select “PROFIBUS-DP Communication.”
IOM Type
Type Select “PROFIBUS-DP Communication (ALP111).”
Installation position Slot 1 to 8 slots can be selected
Two adjacent ALP111 modules (in an odd numbered slot and
Type and
Duplicate Next Card the subsequent slot) can be made dual-redundant for the
Position
ALP111 in an odd numbered slot only.
Output Type Cannot be selected
High Speed Read
IOM Comment
Create New IOM

IOM Type
Category Profibus-DP Communication
Type ALP111(Profibus-DP Communication)
Installation Position
Slot 1
Duplicate Next Card

Output Type
Output in a lump Output immediately
High Speed Read
IOM Comment
OK Cancel
N030606E.ai
Figure Create New IOM Dialog Box (with ALP111 Selected)

l 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 Detail Remarks
Category “PROFIBUS-DP Communication”
IOM Type
Type “PROFIBUS-DP Communication (ALP111)”
Type Installation Position Slot position (S)
and
position Duplicate Next Card x Same setting as the Create New IOM dialog box
High Speed Read x
IOM Comment x
IOM Category
IOM Type Display settings defined in the Type and Position tab.
Slot
Fallback operation is enabled/disabled by the check
x box. By default, the setting is “enabled” (the box is
checked).
Perform Fallback
All points maintain Fallback operation is determined by the toggle switch.
x
Current values The default setting is “All points maintain Current
x Reset all outputs value.”
Set all corresponding The action to be taken upon the detection of module
x module input data to failure is determined by the check box. By default, the
IOP (*1) setting is “disabled” (the box is not checked).
Set all corresponding The action to be taken upon the detection of module
x module input data to failure is determined by the check box. By default, the
Action when OOP (*1) setting is “enabled” (the box is checked).
module/channel fail Head of Slot numbers
detected x of Slave Device in “0” or “1” can be selected. The default value is “1.”
Message
Set
Details Process Alarm from
The message type is determined by the check box.
Slave Device is
x By default, the setting is “disabled” (the box is not
notified as System
checked).
Alarm
Displays the file name. Cannot be selected. The default
File Name
is blank. Updated after the Copy button is clicked.
Displays the time and date file was created. Cannot be
Creation date selected. The default is blank. Updated after the Copy
PROFIBUS button is clicked.
configuration data Displays the time and date the Copy button was
file Date copied clicked. Cannot be selected. The default is blank.
Updated after the Copy button is clicked.
Clicking the Copy button displays the file selection
x [Copy] dialog box and copying is executed. (*2)
The filename extension is “DBM.”
A character string of
Command Line x The default is blank.
up to 32 characters
The value set for each item is restored to the default
[default] x value (except for detail items relating to the PROFIBUS
configuration data file).
x: 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.

Properties
IOM Category Profibus-DP Communication

IOM Type ALP111(Profibus-DP)
Slot 1
Perform Fallback
Reset all outputs

Set all corresponding module input data to IOP
Process Alarm from Slave Device is notified as System Alarm This function is not supported.
Head of Slot numbers of Slave Device in Message 1
PROFIBUS configuration data file

File Name
Creation date
Date copied
Copy
Command(L)
Default
OK Cancel
N030608E.ai
Figure ALP111 Property Sheet
l IOM Download
During IOM download, the following data is downloaded to the ALP111.
• PROFIBUS definition data
• 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

3.6.4 Operations in Communication I/O Builder

This section explains the procedures and setting items concerning operations in
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.
n 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.
n 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
Designate the size of the area for storing communication I/O definition data to
Buffer
be used in an ALP111. The maximum value of the size is 1000.
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).
Program Name
Example: When the module is installed on FIO bus system 1, node 2 and slot 4
K1-2-4PROFIBUS

n Communication I/O Definition Items Set for each Module of Slave

Devices
l 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 Slave device node address
Serial number starting from 1, no blank
Slot Slot number defining a module
spaces between digits.
Reflected when a single module has
Idx Index of data in a module
multiple I/O data.

Slave device node address
Slave Configuration
General
Device COM-DPS Station address 2 OK
Parameter Data...
Enable watchdog control GSD file HIL_7501.GSD
Master#1
1/ALP111
64 byte output con [0x80, 0xBF] 64 byte 0x80, 0xBF
Actual slave
2 word output con [0xE1] 2 word 0xE1 Station address 2
Slave#2
8 word output con [0xE7] 8 word 0xE7 2/COM-DPS
1 1 1 byte input con [0x90] Module#1 IB 0 1 Append Module
2 1 4 byte input con [0x93] Module#2 IB 0 4
3 1 2 word output con [0xE1] Module#3 QW 0 2 Remove Module
4 1 32 word input [0x40, 0x5F] Module#4 IW 0 32
Insert Module
5 1 1 word output [0x60] Module#5 QW 0 1
6 1 16 word output [0x6F] Module#6 QW 0 16 Symbolic Names
7 1 2 word output con [0xE1] Module#7 QW 0 2
Module slot number

N030611E.ai
Figure Slave Configuration Dialogue
The figure below shows an example of a dialogue for a module containing multiple indexes.
Slave Configuration
General
Device BusCon Station address 3 OK
Parameter Data...
Enable watchdog control GSD file EBH82079.GSD
Master#1
1/ALP111
H&B Var.80 1 Word 8 Word 0xD0, 0xF7, 0xDB,
Actual slave
Station address 3
Slave#3
3/BusCon
1 1 H&B Var.80 Module#1 IW 0 1 Append Module
1 2 H&B Var.80 Module#1 IW 0 8 QW 0 8
1 3 H&B Var.80 Module#1 IW 0 12 Remove Module
Insert Module
1 6 H&B Var.80 Module#1 IW 0 12 Symbolic Names
Index of data inside the module N030612E.ai
Figure Slave Configuration Dialogue (With Multiple Indexes)

l 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 Dialogue
• Device & Address: The Slot and Idx values set in the Slave Configuration Dialogue
• Data Type: Enter the appropriate data type according to the device module’s 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.
l 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 Dialogue, and the
appropriate channel number
l 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 Dialogue, channel
number and extension (R)

n Details of Communication I/O Builder

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 Details Remarks
item
Buffer x Enter the size of the entire area for storing the ALP111 data.
Enter the installation position of a module followed by
Program “PROFIBUS.”
x
Name 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
Size x 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.
Enter the port number. Entering a port number
Port
This is not used for ALP111, however. will not generate an error.
Enter the IP addresses of other devices. Entering an IP address
IP Address
This is not used for ALP111, however. will not generate an error.
Enter the node address of a slave device.
The valid range of values is from 0 to 125. However if a value
Station x
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/
Details of the definition are explained in the main text.
Device & index will cause the status
x Define in the range of up to 8 single-byte alphanumeric
Address of the data in question to
characters.
be set to IOP/OOP upon
execution.
Set according to the slave device specifications.
Data Type x
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:
Reverse x
• No
• Yes
The default setting is “No.”
Set whether or not to update communication I/O analog data
at the start of fast-scan.
There are the following options for Scan:
Scan x
• Normal
• Fast
The default setting is “Normal.”
Service
- A comment can be entered.
Comment
The I/O terminal name can be entered as a user-defined
Label -
label. This item is an optional setup item.
x: Entry is required.
Blank: Entry is not required.
-: Can be omitted.

n 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
Channel
Module
specification
Definition Description specification
(single/batch)
AI/O DI/O AI/O DI/O
Specify the slot number of a slave device module.
Slot number x x x x
Range: 1 to 60
Specify the index of a slave device module, followed by “-.”
Index x(*1) x(*1) x(*1) x(*1)
Range: 1 to 60
Divide the part of module specification and the extension part that
Semicolon (;) x x
includes channel specification.
Specify the channel number in a module.
Channel
Range: 0 to 99 x x
number
If omitted, it is treated as if a module is specified.
Extension (E) An identifier for expanding byte data to 16 bits. x(*1) x(*1)
Specification to reverse bytes: Reverse the upper and lower bytes
Extension (S) of digital data of a normal slave device whose upper and lower bytes x(*1) x(*1)
are reversed, and correspond it to the %WB numbers.
Specification to maintain output values.
Specify this extension to continue outputting the final output value
Extension (H)
before downloading, during downloading changed PROFIBUS x(*1) x(*1) x(*1) x(*1)
(*2)
definitions to an ALP111 or after restarting the ALP111.
If omitted, the output value becomes 0.
Specification to output 0 value: Specify this extension to output
Extension (Z) 0 when initial cold start of an ALP111 after downloading.
x(*1) x(*1) x(*1) x(*1)
(*2) If omitted, 0 is output.
Use this option to intentionally specify operations in the default status.
If a channel number is specified using a semicolon (;), specification
of “R” results in the same definition as when only the head channel is
Extension (R) x(*1) x(*1)
specified and a consecutive number of channels corresponding to the
area size are defined.
x: Entry is required.
*1: Enter as necessary.
*2: 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.

l 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
when the module slot number is 3 and index is 4
3-4;2
l 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 Description of Device & Address Remarks
High mm
mm;[ESHZR]
mm;xx
mm;xx[ESHZR]
mm-nn
mm-nn;[ESHZR]
mm-nn;xx
Low mm-nn;xx[ESHZR]
mm: slot number of a module, nn: index, xx: channel number, E, S, H, Z and R: extensions

l 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 Consecutive Batch Definition
Channel
Element number Size Device & Address number Size Device & Address
%WW0101 1 3;0 0 16 3;R
%WW0102 * * * *
%WW0103 1 3;1 1 * *
%WW0104 * * * *
%WW0105 1 3;2 2 * *
%WW0106 * * * *
%WW0107 1 3;3 3 * *
%WW0108 * * * *
%WW0109 1 3;4 4 * *
%WW0110 * * * *
%WW0111 1 3;5 5 * *
%WW0112 * * * *
%WW0113 1 3;6 6 * *
%WW0114 * * * *
%WW0115 1 3;7 7 * *
%WW0116 * * * *
%WW0117
N030617E.ai
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.

l 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) Individual
Batch definition (R)
definition
16 bits 1 Number of points x 2
Analog input/output
Discrete input/ 1 to 2 bytes 1 Number of points x 2
output 3 to 4 bytes 2 Number of points x 2
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)
Channel
%WW0101 2 3;0 0 16 3;R
* * * *
%WW0103 2 3;1 1 * *
* * * *
%WW0105 2 3;2 2 * *
* * * *
%WW0107 2 3;3 3 * *
* * * *
%WW0109 2 3;4 4 * *
* * * *
%WW0111 2 3;5 5 * *
* * * *
%WW0113 2 3;6 6 * *
* * * *
%WW0115 2 3;7 7 * *
* * * *
N030621E.ai
Figure Example of 32-Bit Analog Inputs/Outputs

• Eight 1-byte discrete I/O points (DI, DO)
Channel
%WW0101 1 3;0 0 16 3;R
* * * *
%WW0103 1 3;1 1 * *
* * * *
%WW0105 1 3;2 2 * *
* * * *
%WW0107 1 3;3 3 * *
* * * *
%WW0109 1 3;4 4 * *
* * * *
%WW0111 1 3;5 5 * *
* * * *
%WW0113 1 3;6 6 * *
* * * *
%WW0115 1 3;7 7 * *
* * * *
N030622E.ai
Figure Example of 1-Byte Discrete Inputs/Outputs (DI, DO)

• 2-byte discrete inputs/output, 16 points (DI, DO)
Channel
%WW0101 1 3;0 0 32 3;R
* * * *
%WW0103 1 3;1 1 * *
* * * *
%WW0105 1 3;2 2 * *
* * * *
%WW0107 1 3;3 3 * *
* * * *
%WW0109 1 3;4 4 * *
* * * *
%WW0111 1 3;5 5 * *
* * * *
%WW0113 1 3;6 6 * *
* * * *
%WW0115 1 3;7 7 * *
* * * *
%WW0117 1 3;8 8 * *
* * * *
%WW0119 1 3;9 9 * *
* * * *
%WW0121 1 3;10 10 * *
* * * *
%WW0123 1 3;11 11 * *
* * * *
%WW0125 1 3;12 12 * *
* * * *
%WW0127 1 3;13 13 * *
* * * *
%WW0129 1 3;14 14 * *
* * * *
%WW0131 1 3;15 15 * *
* * * *
N030623E.ai

• 4-byte discrete inputs/outputs, 32 points (DI, DO)
Channel
%WW0101 2 3;0 0 64 3;R
* * * *
%WW0103 2 3;1 1 * *
* * * *
: :
%WW0127 2 3;13 13 * *
* * * *
%WW0129 2 3;14 14 * *
* * * *
%WW0131 2 3;15 15 * *
* * * *
2 3;16 (*1) * *
%WW0134 * * (*1) 16 * * (*1)
2 3;17 * *
%WW0136 * * 17 * *
2 3;18 * *
%WW0138 * * 18 * *
2 3;19 * *
%WW0140 * * 19 * *
2 3;20 * *
%WW0142 * * 20 * *
2 3;21 * *
%WW0144 * * 21 * *
2 3;22 * *
%WW0146 * * 22 * *
2 3;23 * *
%WW0148 * * 23 * *
2 3;24 * *
%WW0150 * * 24 * *
2 3;25 * *
%WW0152 * * 25 * *
2 3;26 * *
%WW0154 * * 26 * *
2 3;27 * *
%WW0156 * * 27 * *
2 3;28 * *
%WW0158 * * 28 * *
2 3;29 * *
%WW0160 * * 29 * *
2 3;30 * *
%WW0162 * * 30 * *
2 3;31 * *
%WW0164 * * 31 * *
N030624E.ai
*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:
“n How to Treat I/O Data as Discrete I/O Data (in the Cases of Specification for Each Channel and
Channel Batch Specification)” in 3.4, “I/O Data”

3.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.
n 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 Detail Setting
Basic or Output Output signal Output signal
“Communication Output (Fully-open/Tightly-shut)”
(optional setup item) conversion conversion type
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 Remarks
Data Conversion Gain 1.000 Same as in the case of
Data Conversion Bias 0.000 “Communication Output”
Output Value for Full-open 106.25
Same as in the case of “No”
Output Value for Tight-shut -17.19
SEE
ALSO For details on output signal conversion, see the following:
“l Output Signal Conversion” in “n Output Processing Common to Regulatory Control Block” in 4,
“Output Processing” in the Function Blocks Overview (IM 33K03E21-50E)


Operation and monitoring includes a function for displaying the ALP111 status and a
function for displaying various messages generated in PROFIBUS-DP communication.
SEE
ALSO For the details of various messages generated in PROFIBUS-DP communication using ALP111 modules, see the
following:
3.9, “Messages”
n FCS Status Display View
l 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
l 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

l Display Example of the Status Display Window
The following figure shows an example of the FCS Status Display window.
I/O UNIT
Node No. : 1
Comment :
I/O (OFF) :
Δ
A A A S S P P
L L L B B S S
P P P 4 4 U U
1 1 1 0 0
1 1 1 1 1
1 1 1
1C
IOM Load Report Close

N030701E.ai
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.
• PROFIBUS definition data
• ALP111 program


This chapter explains unusual operations in PROFIBUS-DP communication.
n 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
EE SS Power failure of node
L L OOOO S S
BB BB
P P MM MM U U
Power failure of ALP111
ESB Bus Node
Disconnected PROFIBUS communication
PROFIBUS-DP Failure of slave device
PROFIBUS-DP
Slave device
N030801E.ai
Figure Areas where Errors can be Generated in PROFIBUS-DP Communication

n Basic Operations Related to Output Processing
l 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.
l 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:
3.8.1, “Actions in the Event of Faults”

n Setting Items Related to Unusual Operations

The following specification items are provided for unusual operations of an ALP111 and slave
devices.
l 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
l 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 fail-safe 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.

3.8.1 Actions in the Event of Faults

This section explains the actions in the event of faults.
n 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)
ALP111 output action
Slave device output
(Upper section:
action
Specification to retain
Function block output (Upper section: Not in
current value,
action fail-safe status,
Lower section:
System status Lower section: At fail-
Specification to reset
safe operation)
output)
When a
When a failure At When a failure At
failure At recovery
occurs recovery occurs recovery
occurs
Prolonged power Retain output
Restart
failure/FCS offline - Tracking (0) - Output 0
output
FCS download specified value
power Output previous Retain output
failure Momentary power value again Restart Previous
- - Output
failure/restart (continuous output value
operation) specified value
Tracking Previous Continue

Prolonged ALP111 Previous value Retain output
- (previous value value output
power fallback
or 0) 0 0 0 0
failure/CPU
STOP/ No
Continue Continue Continue
RUN ALP111 - Tracking Retain output
output output output
fallback
FCU
power Output previous Previous value Retain output
failure ALP111 value again Previous Previous
-
Momentary fallback (continuous value value
operation) 0 0
power
failure/ Output previous
reset No
value again Continue Continue Previous
ALP111 - Retain output
(continuous output output value
fallback
operation)
Tracking Previous Continue
MAN Previous value Retain output
ALP111 fallback (previous value value output
Path fallback
or 0) 0 0 0 0
error
MAN Continue Continue Continue
No ALP111 fallback Tracking Retain output
fallback output output output
FCU (CPU) control-right No Continue Continue Continue
No change Retain output
transfer change output output output
Retain output
Prolonged power MAN Restart
Tracking (0) - Output 0
Node failure fallback output
specified value
power
failure Retain output
Momentary power No Output previous Restart Previous
- Output
failure (restart) change value again output value
specified value
Retain output
MAN Restart
ALP111 failure /maintenance Tracking (0) - Output 0
fallback output
specified value
No Continue Continue Previous
Dual-redundant ALP111 switch No change Retain output
change output output value

Table Actions By Power Failure/Failure Mode (2/2)
ALP111 output action Slave device output action
(Upper section: Specification (Upper section: Not in fail-
Function block `output action to retain current value, safe status,
System status Lower section: Specification Lower section: At fail-safe
to reset output) operation)
When a failure When a failure When a failure At
At recovery At recovery
occurs occurs occurs recovery
PROFIBUS Retain output
communication stop Tracking Restart Previous
MAN fallback Continue output Output
(between ALP111 and (previous value) output value
slave devices) specified value
Slave device failure/ Tracking Restart Previous
MAN fallback Continue output -
maintenance (previous value) output value
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.
n 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.
l 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.
l Output Actions
Outputs from slave devices during an FCS power failure depend on the specification of fail-safe
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

mode
Outputs 0
ALP111 output
Enters the fail-safe status and

Slave device outputs the specified value
output Outputs 0
N030807E.ai
Figure Output Actions in the Event of FCS Power Failure (Prolonged Power Failure, Slave Device Fail-
Safe Operation)

n 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.
l 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.
l 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 AUT AUT

mode
Outputs the previous value
ALP111 output
Slave device
output
N030808E.ai
Figure Output Actions in the Event of FCS Power Failure (Momentary Power Failure and Restart)

n 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.
l 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.
l 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.
• All points maintain Current value
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

mode
Enters the fallback status and

maintains the output value
ALP111 output

Slave device
output
N030809E.ai
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

mode
resets the output value
ALP111 output
Slave device Outputs 0

output
N030810E.ai
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)

l 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.
n 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.
l 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.
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.
l 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.
n Actions in the Event of FCU (CPU) Control-Right Transfer

For AFV30x and AFV40x, data scanning will stop for one second when transferring control right.

n 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.
l Input Actions
The status of input data becomes BAD throughout a prolonged power failure of a node.
l 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

mode
Outputs 0
ALP111 output

output Outputs 0
N030811E.ai
Figure Output Actions in the Event of Node Power Failure (Prolonged Power Failure, Slave Device Fail-
Safe Operation)

n 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.
l 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.
l 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
AUT
Function block
mode Outputs the previous value
ALP111 output
Slave device
output
N030812E.ai
Figure Output Actions in the Event of Node Power Failure (Momentary Power Failure)

n 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.
l 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.

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.
l 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.

n 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.
l Input Actions
The status of input data becomes BAD during the ALP111 failure/maintenance period.
l Output Actions
The FCU outputs 0 to the ALP111 after the ALP111 recovers.
Stop Recovery
ALP111 status

mode
Outputs 0
ALP111 output

outputs the specified value
output
N030813E.ai
Figure Output Actions in the Event of ALP111 Operation Stop (at Slave Device Fail-Safe Operation)
n 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.
l 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.
l 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.

n 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.
l 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.
l 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
Notifies about a
Function block AUT communication error MAN
mode
ALP111 output
Slave device Outputs the previous value
output
N030814E.ai
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:
3.9.1, “System Alarm Messages”

n 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.
l 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.
l 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
Notifies about a
Function block AUT communication error MAN
mode
ALP111 output

Slave device
output
N030815E.ai
Figure Output Actions in the Event of Slave Device Operation Stop

3.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:
3.8.3, “Actions during Online Maintenance”
n 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 PROFIBUS

communication from
User operation ALP111 detail ALP111 PROFIBUS an ALP111 during
settings programs definition data download
Offline download to FCS Yes Yes - Temporarily suspended
IOM download to ALP111 Yes Yes (*1) Yes Temporarily suspended
Add new ALP111 module Yes Yes Yes Stopped (initial status)
Continued/temporarily
Change ALP111 properties Yes Δ (*2) Δ (*3)
suspended (*4)
Change communication I/O
Yes - - Continued
definitions
Yes : This data is always downloaded.
Δ : This data may be downloaded depending on conditions.
- : This data is not downloaded.
*1: If there is a difference between the revisions of ALP111 programs, the ALP111 program of older revision is downloaded.
*2: Only if there is a difference between the revisions of ALP111 programs, the ALP111 program of newer revision is downloaded.
*3: PROFIBUS definition data is downloaded only if a PROFIBUS definition data file is specified in the Properties dialog box.
*4: PROFIBUS communication is temporarily suspended only if either an ALP111 program or PROFIBUS definition data is
downloaded.

n System Operations during Download

The following describes system operations during download according the types of download to
an ALP111.
Table System Operations during Download
Slave device output action
(Upper section: Not in fail-safe
Function block output
ALP111 output action status,
action
System status Lower section: At fail-safe
operation)
During At During At During
At recovery
download recovery download recovery download
Retain output
Tracking Restart
Download to FCS offline - - Output 0
(0) output
specified value
MAN Tracking Restart
Download IOM to ALP111 - Retain output 0
fallback (0) output
Tracking Retain output
Download ALP111 MAN Restart Previous value
(previous Stop output Output
programs fallback output or 0 (*2)
value or 0) specified value
MAN Tracking Retain output
Download PROFIBUS Restart Previous value
fallback (previous Stop output Output
definition data output or 0 (*2)
(*3) value or 0) specified value
Online Retain output
mainte- Change IOM properties MAN
Tracking
Restart Previous value
nance (specification of dual- (previous Stop output Output
fallback output or 0 (*2)
redundant) value or 0) specified value
Change IOM properties
MAN Continue Continue
(other than specification Tracking Retain output Continue output
fallback output output
of dual-redundant)
MAN
Change communication Continue Continue Continue output
fallback Tracking Retain output
I/O definitions output output (*1)
(*3)
*1: 0 is set for newly added definitions.
*2: Depends on the specification of output retention in ALP111 Communication I/O Builder.
*3: By checking an option on “Constant 3” tab of FCS properties sheet, the OOP alarm and MAN fallback occurrence may be
avoided.
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.

n 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
Action after offline Action after IOM
Condition IOM download
download download
When using a completely
new ALP111 module
When an ALP111 is
Input becomes IOP. Reads new inputs and
replaced before offline Required
Output becomes OOP. (*1) resets outputs (*2)
download
When there are changes to
the definitions (*3)
When there are no changes Reads new inputs and
Not required -
to the definitions resets outputs (*2)
*1: 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:
. • Identification Number (model code) agreement
*2: Resetting outputs means outputting 0 to the analog output and discrete output.
*3: 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.

3.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 dual-
redundant specification is changed. This section describes actions during online
maintenance.
n 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
l Input Actions
During ALP111 online maintenance, the previous values are retained for both input and status
values.

l 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

mode (*1)
ALP111 output

retains the output value
Slave device Outputs the previous value
output
*1: By changing the PROFIBUS definitions on the builder, MAN fallback occurrence
may be avoided.
N030818E.ai
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.

n 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.
l 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.
l 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.
ALP111 operation
status

mode (*1)
ALP111 output
Slave device
output
*1: By changing the communication I/O definitions on the builder, MAN fallback
occurrence may be avoided.
N030819E.ai
Figure Output Actions during ALP111 Online Maintenance
n 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.

n Suppress OOP Alarms and MAN Fallback During Online Maintenance

▼ Suppress OOP alarms during online maintenance of ALP121 and dual-redundant ALP111
When performing online downloading of maintenance changes of PROFIBUS definitions and
communication I/O definitions of ALP111 modules, the function blocks connected to the ALP111
may trigger an OOP alarm and perform MAN fallback action.
On the builder, an option is available to suppress the OOP occurrence and MAN fallback action
during online maintenance of AlP111.
Satisfying the following requirement, OOP alarm and MAN fallback occurrence may be avoided:
• FCS revision number is R4.01.60 or newer.
• ALP111 is installed in an ESB Bus Node.
• ALP111 is in a dual-redundantly configuration.
• ALP111 module, controlling side and standby side is running normally.
On “Constant 3” tab of FCS properties sheet, the option of “Suppress OOP alarms during online
maintenance of ALP121 and dual-redundant ALP111” is checked.

<3.9 Messages> 3-83
3.9 Messages
In PROFIBUS-DP communication, the following messages are displayed for ALP111
modules and slave devices.

<3.9 Messages> 3-84
n 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 CODE=#### (*1)
0082 IOM recovery STNss IOM Recover FIO k NODE mm SLOT nn
IOM database
0083 STNss IOM Configuration FIO k NODE mm SLOT nn
error
Communication
0089 STNss SS-COM Error FIO k NODE mm SLOT nn STN zzz CODE=####
error
Communication
0090 STNss SS-COM Recover FIO k NODE mm SLOT nn STN zzz
recovery
*1: CODE=XXXX will be affixed only for AFV30x or AFV40x.
STNss: Station name
k: Bus system number
mm: Node number
nn: Slot Number
zzz: Node address
####: Error code
XXXX: Identification Number (Hexadecimal: Displayed with “0x” added at the top)
yy: Module number
VV: 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:
“n Details of System View” in 3.6.3, “Operations in System View”
n Error Codes Used for Communication Errors


<3.9 Messages> 3-85
l 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.
Error Action to take after the
Description
code occurrence of error
CAB2 Invalid Device & Address, cannot be interpreted
CAB3 Invalid Device & Address, illegal character string detected
CAB5 Invalid Device & Address, slot number out of range
Invalid Device & Address, entry data other than a numerical value
CAB6
CAB7 Invalid Device & Address, index value out of range
Do not perform
CAB8 Invalid Device & Address, index value exceeding the specified digits communication for the
definition causing the error.
CAB9 Invalid Device & Address, invalid delimiter character
Check the definition in
Corresponding device (module or channel) not specified in Communication I/O Builder
CABA
CABB Illegal data type, input designated for output data
CABC Illegal data type, output designated for input data
Invalid Device & Address, entry data for slot number is not a
CABD
numerical value
CABE Invalid Device & Address, illegal character string detected
Invalid Device & Address, illegal character string detected
CABF
(extension symbol)
l 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 Action to take after the occurrence of
Description
code error
Inconsistent versions of FCU and EB401
C588 Use correct versions of FCU and EB401
(EB401 does not support ALP111 in remote node)
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
CA92 Configuration error
CA93 Slave device module error Retry communication
CA94 Slave device channel error
CA95 Overflow of slave diagnostic information
*1: In case these errors occur, the node address of STN zzz is always set to 255.

<3.9 Messages> 3-86

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 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.
n List of Messages
Fieldbus messages are divided into the following categories:
• 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.

<3.9 Messages> 3-87
n 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.
Error
by:
Locked by another STNss PB FIO k NODE mm SLOT nn Station Alarm STN zzz ID
3283
master device 0xXXXX Master_Lock (Master STN yyy)
ALP111
The above returned to STNss PB FIO k NODE mm SLOT nn Station Recover STN zzz ID
3284
normal 0xXXXX Master_Lock
STNss PB FIO k NODE mm SLOT nn Station Alarm STN zzz ID
3285 Parameter setting failed
0xXXXX Param_Fault
Slave device
3286
normal 0xXXXX Param_Fault
Received an illegal frame STNss PB FIO k NODE mm SLOT nn Station Alarm STN zzz ID
3287
from a slave device 0xXXXX Invalid_Slave_Response
ALP111
3288
normal 0xXXXX Invalid_Slave_Response
Received a request for an STNss PB FIO k NODE mm SLOT nn Station Alarm STN zzz ID
3289
unsupported function 0xXXXX Not_Supported
Slave device
3290
normal 0xXXXX Not_Supported
3291 Configuration error
0xXXXX Cfg_Fault
Slave device
3292
normal 0xXXXX Cfg_Fault
3293 Cannot transmit data
0xXXXX Station_Not_Ready
Slave device
3294
normal 0xXXXX Station_Not_Ready
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

<3.9 Messages> 3-88
Error
by:
Slave device not present
3295 on the communication
0xXXXX Station_Non_Existent
line ALP111
3296
normal 0xXXXX Station_Non_Existent
Slave device is
3297 missing from the cyclic
0xXXXX Deactivated
transmission list ALP111
3298
normal 0xXXXX Deactivated
Setting parameters or STNss PB FIO k NODE mm SLOT nn Station Alarm STN zzz ID
3299
checking configuration 0xXXXX Param_Req
Slave device
3300
normal 0xXXXX Param_req
0xXXXX Ext_Diag_Overflow ALP111 or
overflowed
Slave device
3302
normal 0xXXXX Ext_Diag_Overflow
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

<3.9 Messages> 3-89
n Slave Device Specific Messages (Slave Devices Supporting

PROFIBUS-DP)
Slave device specific messages indicate errors defined by the device manufacturer.
These messages display the slave diagnostic information’s device related portion as error codes.
Table List of Messages (Salve Devices Supporting PROFIBUS-DP)
Error detected
by:
STNss PB FIO k NODE mm SLOT nn Device
3303 Slave device error occurred Slave devices
Related Alarm STN zzz ID 0xXXXX CODE=##########
supporting
STNss PB FIO k NODE mm SLOT nn Device PROFIBUS-DP
3304 The above returned to normal
Related Recover STN zzz ID 0xXXXX
##########: Error code (Hexadecimal: Maximum 126 characters, with the first 2 characters indicating the error code length
(byte length)).
n Messages for Each Module in a Slave Device

Error
detected by:
STNss PB FIO k NODE mm SLOT nn Module Alarm STN zzz ID
0xXXXX MODULE yy
STNss PB FIO k NODE mm SLOT nn Module Invalid Alarm STN
3325 Module error occurred (*1)
zzz ID 0xXXXX MODULE yy
Module irregularity occurred STNss PB FIO k NODE mm SLOT nn Module Wrong Alarm STN
3327 Slave device
(*1) zzz ID 0xXXXX MODULE yy
STNss PB FIO k NODE mm SLOT nn No Module Alarm STN
3329 Module not mounted (*1)
zzz ID 0xXXXX MODULE yy
The above returned to STNss PB FIO k NODE mm SLOT nn Module Recover STN
3330
normal zzz ID 0xXXXX MODULE yy
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 modules). 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.

<3.9 Messages> 3-90
n Messages for Each Channel in a Slave Device

Error
detected by:
STNss PB FIO k NODE mm SLOT nn Channel Alarm STN zzz ID
3331 Short circuit
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 Slave devices
0xXXXX MODULE yy CHANNEL ww link break
Upper limit value STNss PB FIO k NODE mm SLOT nn Channel Alarm STN zzz ID
3343
exceeded 0xXXXX MODULE yy CHANNEL ww upper limit value exceeded
Lower limit value STNss PB FIO k NODE mm SLOT nn Channel Alarm STN zzz ID
3345
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
The above error STNss PB FIO k NODE mm SLOT nn Channel Recover STN zzz ID
3350
returned to normal 0xXXXX MODULE yy CHANNEL ww
XXXX: Identification Number (Hexadecimal: Displayed with “0x” added at the head)
yy: Module slot number (decimal), ww: Channel number (decimal), vvvv: Error type (decimal)
n ALP111 Self-Diagnostic Messages

Error
detected by:
PROFIBUS
3351 STNss PB FIO k NODE mm SLOT nn Communication Stop (*1)
communication stop
ALP111
PROFIBUS
3352 STNss PB FIO k NODE mm SLOT nn Communication Recover
communication recover
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:
“n Procedure for Modifying a Project” in 3.6.2, “Operations with the PROFIBUS-DP Configurator”

<4. PROFIBUS-DP (ALP121)> 4-1
4. PROFIBUS-DP (ALP121)
This chapter explains the functions, engineering tasks required, operation and
monitoring, and messages of ALP121, which is a communication module installed on an
FCS.
Note that the manual of the PROFIBUS-DP configurator is provided as a PDF file and
supplied with the CENTUM VP software media.

<4.1 System Configuration> 4-2
4.1 System Configuration

This section explains configuration of the functions allowing communication between the
CENTUM VP system including ALP121 and devices supporting PROFIBUS-DP, as well as
the operating environment.

4.1.1 Overall Configuration

The communication functions of PROFIBUS-DP are configured with the System builders,
operation and monitoring function, I/O module common access function, and PROFIBUS-
DP communication module ALP121.
The figure below shows the configuration of PROFIBUS-DP communication functions.
System builders Operation and Monitoring function

• ALP121 support • Access
• PROFIBUS-DP PROFIBUS • ALP121
configurator Communication I/O data as status display • Monitoring of alarms,
integration Definition Support Tool process data • IOM report fieldbus messages
PROFIBUS Communi- Function Face plates, Historical

FCS Status System
System -DP Block graphics, Message
cation Display Alarm
View configurator I/O Builder Detail trend etc. Report
View View
Builder window
ALP121 ALP121 Slave device

Download Tag access operation related diagnostic
status alarm information
FCS
Control function
Communication I/O
• PROFIBUS definition online change

I/O module common
access function • ALP121 module redundancy
• ALP121 network redundancy
Definition I/O data Alarm

load notification
PROFIBUS-DP
communication module (ALP121)
I/O data
PROFIBUS-DP PROFIBUS
Slave device DP/PA Coupler
HART device PROFIBUS-PA device

N040101E.ai
Figure Configuration of Communication Functions with PROFIBUS-DP

l PROFIBUS-DP Communication Module (ALP121)
ALP121 is a module that allows communication between slave devices connected to PROFIBUS
and the CENTUM VP system.
The ALP121 is installed on an FCS, and sends I/O data received from slave devices to the I/O
module common access function and also sends engineering data to slave devices. Moreover,
the ALP121 receives outputs from the I/O module common access function.
TIP
Slave devices refer to Fieldbus devices connected to PROFIBUS communication cables.
l I/O Module Common Access Function

It is a commonly used function to access FIO modules.
This function is used to send data and messages received by ALP121 to an HIS and notify the
ALP121 status to an HIS. In addition, this function sends engineering data to slave devices or
sends output data set by function blocks to the ALP121.
l System Builders
System builders allow the following definitions and operations.
• Defining ALP121
• Changing IOM properties
• Defining PROFIBUS communication between ALP121 and slave devices
• Defining communication I/O
• Downloading PROFIBUS communication definitions
• Downloading IOM definitions
• Defining communication I/O data through function blocks
l Operation and Monitoring Function

The operation and monitoring functions allow the following operations and checks.
• Displaying the operating status of ALP121
• IOM download
• IOM report operation
• Checking system alarm messages related to ALP121
• Checking diagnostic information of slave devices

4.1.2 Operating Environment

The hardware and software environment required for the CENTUM VP system to perform
PROFIBUS-DP communication using ALP121.
n Hardware Environment
ALP121 operates with the following FCSs.
Item Specification
CPU can be either single or redundant configuration.
CENTUM FCS
AFV30S, AFV30D, AFV40S, AFV40D (Here in after AFV30S, AFV30D,
Compact FCS: AFV30/AFV40
AFV40S and AFV40D are collectively called FFCS-V.)
ESB bus node unit Can be installed on ANB10S and ANB10D. 10 m max.
Optical ESB bus node unit Can be installed on ANB11S and ANB11D. 50 km max.
Restrictions on installing the ALP121 on the FFCS-V are summarized below.

Table Restrictions on Installing ALP121 on FFCS-V
Basic control Basic control
Basic control
Item function + extension function + extension
function
of 10 nodes of 14 nodes
Maximum number of ALP121
8 16 32
that can be installed
Maximum number of ALR111/
ALR121/ALP111 or ALP121/
8 16 32
ALE111/AGS813/AGP813 that
can be installed
Maximum number of ALF111/

ALR111/ALR121/ALP111 or
30 48 64
ALP121/ALE111/AGS813/
AGP813 that can be installed
TIP
• ALP121 cannot be installed on ER bus node units (ANR10S, ANR10D).
• ALP111 and ALP121 cannot be installed on the same FCS together.

n Software Environment
The PROFIBUS communication function operates in the following software environment.
Table Software Environment
Software Details
LFS1700: Basic control function (AFV30, AFV40)
Basic control function Control Function for Field Control Station (for AFV30, AFV40,
Vnet/IP and FIO)
Standard builder function LHS5100/LHM5100: Standard builder function
Included in the standard builder function.
PROFIBUS-DP configurator of SYCON.net/YOKO
TIP
• The PROFIBUS-DP configurator of SYCON.net/YOKO is a product of Hilscher.
• The PROFIBUS-DP configurator of SYCON.net/YOKO can be used together with the conventional
SYCON-PB/YOKO on the same PC.
• The PROFIBUS-DP configurator of SYCON.net/YOKO cannot be used together with SYCON.net of the
standard product of Hilscher on the same PC. Do not install SYCON.net of the standard product.
• The manual of the PROFIBUS-DP Configurator is provided as a PDF file and stored in the folder (<DVD
ROM Drive>: \CENTUM\PDFFILE\PROFIBUS_Configurator\en\) of the CENTUM VP software media.
• To define slave devices with the PROFIBUS-DP configurator of SYCON.net/YOKO, a GSD file that defines
device specifications and data that can be set, is required.
• A GSD file can be downloaded from the website of the PROFIBUS User Organization.

4.1.3 Application Capacity

The table below summarizes application capacity available when using ALP121 to
perform PROFIBUS-DP communication.
Table Application Capacity

Item Specification
Number of ports 1 port/ ALP121
Number of slave devices that can be connected Without repeater: Up to 31 devices /ALP121
in single configuration With repeater: Up to 123 devices / ALP121
Number of slave devices that can be connected Without repeater: Up to 30 devices / ALP121
in module redundancy configuration With repeater: Up to 123 devices / ALP121
Up to 1000 words / ALP121
Number of communication I/O data points
Up to 8000 words / FCS
Number of communication I/O definitions Up to 200 definitions / ALP121
Number of stations that can be defined Up to 125 stations / ALP121
Cyclic communication: Up to 244 bytes / communication
Communication capacity
Non-cyclic communication: Up to 240 bytes / communication
Synchronism of data of 4 bytes or less within communication
Data synchronization guarantee
definitions is guaranteed.


(ALP121)
This section explains the redundancy function and I/O data, among the control functions
related to ALP121.

4.2.1 Redundant Configuration

ALP121 communication modules can be used in single configuration, but the reliability is
improved by using them in redundant configuration. PROFIBUS-DP allows two types of
redundant configuration, “module redundancy” and “network redundancy.”
n Overview of Module Redundancy and Network Redundancy

The module redundancy refers to a redundant configuration of standby redundancy type using
two ALP121 communication modules connected with PROFIBUS-DP communication cables.
The figure below shows the module redundancy configuration.
Host Controller(FCS)
ALP121 ALP121
(control) (standby)
Slave Device
I/O 1
communication
Slave Device
2
Slave Device
3
PROFIBUS-DP
N040201E.ai
Figure Module Redundancy Configuration

In the network redundancy configuration, not only two adjacent ALP121 modules, but also
communication interfaces of slave devices are made redundant in order to separate their
networks.
The figure below shows the network redundancy configuration.
Host Controller(FCS)
ALP121 ALP121
(control) (standby)
PNO redundancy
I/O Slave device
communication 1
Primary Backup
PNO redundancy
Slave device
2
Primary Backup
PNO redundancy
Slave device
3
Primary Backup
PROFIBUS-DP
N040202Eai
Figure Network Redundancy Configuration
To configure a redundant network, a set of two ALP121’s are installed in an odd-number slot and
the next slot (the odd number + 1).
One of the dual-redundant ALP121 modules operates on the control side, and another on the
standby side. Switching between the control side and standby side is controlled by the FCS.
TIP
The PNO redundancy type conforms to the “Slave Redundancy V1.2” specifications issued by PNO (PROFIBUS
User Organization).

The characteristics of two types of redundant configuration are summarized in the table below.
Table Differences between Module Redundancy and Network Redundancy
Item Module redundancy Network redundancy
• ALP121
Target of redundancy ALP121 • Cable in communication path
• Communication ports of slave devices
Slave device in single configuration. Slave device conforming to PNO
Slave device that can be However, it is possible to connect to redundancy specification.
connected either the Primary or Backup port of a However, it is not possible to connect
PNO redundancy slave device. slave devices in single configuration.
• When ALP121 on the control side is in
the Fail status and the standby side in
the normal status.
When ALP121 on the control side is in • Any of slave devices of ALP121 on the
Transfer timing the Fail status and the standby side in control side is in the Fail status and all
the normal status. the slave devices of ALP121 path on
the standby side are all normal, except
for slave devices whose ports are both
in the Fail status.
Data of ALP121 on the control side is Data of ALP121 on the control side is
Data input to FCS
used. used.
Output from ALP121 on the control Data output from ALP121 on the control
Data output from FCS
side and standby sides
Alarm message of slave Notified to FCS from ALP121 on the Notified to FCS from ALP121 either on the
devices control side control or standby side

n Module Redundancy
In this configuration, ALP121 communication modules are made dual-redundant.
l Master Device Address in Module Redundancy Configuration

The Master device address for redundant ALP121 module are set to the following values.
• Master device address on the control side: 2
• Master device address on the standby side: 1
IMPORTANT
• In module redundancy configuration, the PROFIBUS communication definitions made
using the PROFIBUS-DP configurator are the same as in single configuration. The same
definitions are used for both the control and standby sides.
• Set Profile for Master Redundant of the Profile bus parameter in the PROFIBUS-DP
configurator.
l Control-right Transfer of ALP121

The control right is transferred if any of the following conditions is satisfied.
• ALP121 on the control side is in the Fail status and ALP121 on the standby side is in the
normal status.
• No slave device is detected by ALP121 on the control side and ALP121 on the control side
is not detected via PROFIBUS by ALP121 on the standby side.
TIP
When ALP121 on the control side is not detected via PROFIBUS by ALP121 on the standby side, PROFIBUS
connector abnormality of ALP121 on the control side is assumed.
l Control Right of ALP121 when PROFIBUS Communication Definitions are

Changed
If an error occurs while changing PROFIBUS communication definitions online, the control right
of ALP121 is transferred.

n Network Redundancy
In order to implement the network redundancy configuration, PNO redundancy slave devices are
required. A PNO redundancy slave device has 2 ports, Primary and Backup.
Two ALP121 modules operate as the master to communicate with slave devices.
l Master Device Addresses in Network Redundancy Configuration

Device addresses of ALP121 modules in the network redundancy configuration are set to the
following values automatically by the PROFIBUS-DP configurator.
• Master device address on the control side :2
• Master device address on the standby side :2
IMPORTANT
Do not connect slave devices that do not support PNO redundancy in network redundancy
configuration.
TIP
Both the Primary and Backup ports of a slave device operate with the same station address. Set the station
addresses of slave devices in the range from 3 to 125.
l Control-right Transfer of ALP121

The control right is transferred if any of the following conditions is satisfied.
• ALP121 on the control side is in the Fail status and ALP121 on the standby side is in the
normal status.
• Any of slave devices of ALP121 on the control side is in the Fail status and all the slave
devices of ALP121 on the standby side are all normal, except for slave devices whose
Primary and Backup ports are both in the Fail status.
l Control Right of ALP121 when PROFIBUS Communication Definitions are

Changed
If an error occurs while changing PROFIBUS communication definitions online, the control right
of ALP121 is transferred.
IMPORTANT
In the case of redundant network, make the following settings using the PROFIBUS-DP
configurator.
• Select and enable the [Activate Redundancy Mode] check box in the Redundancy setting
window of the PROFIBUS-DP configurator for all PNO redundancy slave devices.
• Set Profile for single configuration of the Profile bus parameter in the PROFIBUS-DP
configurator.

4.2.2 I/O Data

FCS’s communication I/O function is used for data exchange between FCS and
PROFIBUS devices. By using the communication I/O function, it becomes possible to
access PROFIBUS data from function blocks or the Graphic View, just like other process
data.
I/O data of ALP121 can be stored in the communication I/O data area as analog I/O data
or discrete I/O data. Stored data can be converted to analog I/O signals or discrete I/O
signals of regulatory blocks, calculation blocks, sequence control blocks, etc.
Moreover, in the case of SFC blocks, it is possible to directly access communication I/O
data of FCS by using SEBOL statements.
IMPORTANT
For FFCS-V, one ALP121 and dual-redundant ALP121 cannot be defined with both %WW and
%XW.
n Data Types Supported by ALP121

The table below shows I/O data types that can be set in Communication I/O Builder.
Table Data Types that can be Set
Classification Data type Name
I16 16-bit signed integer data
U16 16-bit unsigned integer data
Input
F32 32-bit floating point data
DI Bit data of discrete input
Output
F32 32-bit floating point data
DO Bit data of discrete output

n Storing I/O Data

I/O data is stored continually to the communication I/O data area in units of size set by the
The figure below shows how byte data is stored.
Word data is handled in the same way as in subsystem communication.
01 08, 09 16
%WW0101
%WW0102 Value in the free
Data (third byte) Data (fourth byte) area is undefined
%WW0103
Data (fifth byte) Free area
N040203E.ai
Figure How Byte Data is Stored in Communication I/O Data Area
TIP
If the data size specified by the PROFIBUS-DP Configurator is an odd-size byte, the lower byte area is treated as
free area and the value becomes undefined.
n Storage of Analog I/O Data

I/O data can be stored in the communication I/O data area as analog I/O data in the same way as
in subsystem communication.
TIP
• To treat byte data as analog I/O data, set a 16-bit or greater data type.
• If the data size specified by the PROFIBUS-DP configurator is an odd-size byte, the value of byte data
stored last in the communication I/O data cannot be guaranteed.
To treat every 8 bits of byte data separately as analog I/O data, set “;E” to the “Device &
Address” on Communication I/O Builder. Byte data will be expanded to 16 bits and stored in the
communication I/O data area.
01 08, 09 16
%WW0101
Data (first byte)
%WW0102
Data (second byte)
%WW0103
Data (third byte)
N040204E.ai
Figure How I/O Data Expanded to 16 Bits is Stored

Values outside the byte data range are stored after converting them to 8-bit data. The table below
shows values of data outside the range after conversion.
Table Converted Values of Data outside Range
Data type Before conversion After conversion
-127 or less -127
Analog output (16-bit signed integer)
128 or more 128
Analog output (16-bit unsigned integer) 255 or more 255
n Storage of Discrete I/O Data

I/O data can be stored in the communication I/O data area as discrete I/O data in the same way
as in subsystem communication.
n Storage of Discrete I/O Data with Reverse Bits

I/O data can be stored in the communication I/O data area as discrete I/O data with reverse bits
in the same way as in subsystem communication.
Termination of byte data indicated as an odd size by the PROFIBUS-DP configurator is reversed
in units of 8 bits and then stored, as shown below.
Slave device bit arrange
7 0
Communication
Data (first byte) Free area
I/O data area %WB bit number
01 08, 09 16
%WW0101 N040205E.ai
Figure Storage of Discrete I/O Data with Reverse Bits

n Storage of Discrete I/O Data with 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, set reverse bytes according to the specifications of the slave device used when
storing discrete I/O data in the communication I/O data area.
l Example of Mapping with 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 byte Remarks
1 Yes No Initial value: IS1 made by STAHL corresponds to this pattern.
2 Yes Yes VOS200 made by STAHL corresponds to this pattern.
3 No No
4 No Yes
• Pattern 1
Upper-Byte (first byte) Lower-Byte (second byte)
Channel number 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8
(bit number)
x ― ― ― ― ― ― ― ― Input/Output 1
x ― ― ― ― ― ― ― ― ― Input/Output 2
x ― ― ― ― ― ― ― ― ― ― Input/Output 3
x ― ― ― ― ― ― ― ― ― ― ― Input/Output 4
― x ― ― ― ― ― ― ― ― ― ― ― Input/Output 5
― ―
x ― ― ― ― ― ― ― ― ― ― ― Input/Output 6
x ― ― ― ― ― ― ― ― ― ― ― ― ― ― Input/Output 7
x ― ― ― ― ― ― ― ― ― ― ― ― ― ― ― Input/Output 8
― ― ― ― ― ― ― x Input/Output 9
― ― ― ― ― ― x ― Input/Output 10
― ― ― ― ― x ― ― Input/Output 11
― ― ― ― x ― ― ― Input/Output 12
― ― ― ― x ― ― ― Input/Output 13
― ― x ― ― ― ― ― Input/Output 14
― x ― ― ― ― ― ― Input/Output 15
x ― ― ― ― ― ― ― Input/Output 16
N040206E.ai
Figure Mapping with Reverse Bits, but without Reverse Bytes

• Pattern 2
Channel number 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
(bit number)
x Input/Output 1
x ― Input/Output 2
x ― ― Input/Output 3
x ― ― ― Input/Output 4
x ― ― ― ― Input/Output 5
x ― ― ― ― ― Input/Output 6
x ― ― ― ― ― ― Input/Output 7
x ― ― ― ― ― ― ― Input/Output 8
x ― ― ― ― ― ― ― ― Input/Output 9
x ― ― ― ― ― ― ― ― ― Input/Output 10
x ― ― ― ― ― ― ― ― ― ― Input/Output 11
x ― ― ― ― ― ― ― ― ― ― ― Input/Output 12
― x ― ― ― ― ― ― ― ― ― ― ― Input/Output 13
― ―
x ― ― ― ― ― ― ― ― ― ― ― Input/Output 14
x ― ― ― ― ― ― ― ― ― ― ― ― ― ― Input/Output 15
x ― ― ― ― ― ― ― ― ― ― ― ― ― ― ― Input/Output 16
N040207E.ai
Figure Mapping with Reverse Bits as well as Reverse Bytes
• Pattern 3
Channel number 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
(bit number)
x ― ― ― ― ― ― ― ― ― ― ― ― ― ― ― Input/Output 1
x ― ― ― ― ― ― ― ― ― ― ― ― ― ― Input/Output 2
x ― ― ― ― ― ― ― ― ― ― ― ― ― Input/Output 3
x ― ― ― ― ― ― ― ― ― ― ― ― Input/Output 4
x ― ― ― ― ― ― ― ― ― ― ― Input/Output 5
x ― ― ― ― ― ― ― ― ― ― Input/Output 6
x ― ― ― ― ― ― ― ― ― Input/Output 7
x ― ― ― ― ― ― ― ― Input/Output 8
x Input/Output 16
N040208E.ai
Figure Mapping without Reverse Bits and Reverse Bytes

• Pattern 4
Channel number 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7
(bit number)
x Input/Output 8
x ― ― ― ― ― ― ― ― ― ― ― ― ― ― ― Input/Output 9
x ― ― ― ― ― ― ― ―― ― ― ― ― ― Input/Output 10
x ― ― ― ― ― ― ― ― ― ― ― ― ― Input/Output 11
x ― ― ― ― ― ― ― ― ― ― ― ― Input/Output 12
x ― ― ― ― ― ― ― ― ― ― ― Input/Output 13
x ― ― ― ― ― ― ― ― ― ― Input/Output 14
x ― ― ― ― ― ― ― ― ― Input/Output 15
x ― ― ― ― ― ― ― ― Input/Output 16
N040209E.ai
Figure Mapping without Reverse Bits, with Reverse Bytes
n Data Status
Data status is determined by the status of communication with slave devices and diagnostic
information.
The table below summarizes different data statuses.
Table Data Status
Data status Meaning
BAD Invalid data value
Indicates a temporary status in which data could not be acquired due to a momentary power
NRDY
failure, power recovery, etc.
Indicates the occurrence of a communication module error or a communication error with a
LPFL
connected device.
NR (*1) Data has been acquired normally.
*1: NR denotes cases where the status does not fall under neither of the data statuses above (BAD, NRDY or LPFL).
SEE
ALSO • For details of data statuses, see the following:
“n Data Statuses Handled for Subsystem” in 1.2, “Subsystem Data Identification” in the Communication
with Subsystems Using FIO (IM 33K03L20-50E)
• For explanation of diagnosis information, see the following:
“n Specification of Diagnostic Information” in 4.3.9 “Advanced Engineering”


TIP
Data update timing can be set in the definition item [Scan] on Communication I/O Builder.
n I/O Conversion
I/O data of ALP121 can be converted to the following data types in function blocks including
regulatory block, calculation block and sequence control block.
• Analog input signal
• Analog output signal
• Discrete I/O signal
l Analog Input
I/O data can be treated as an analog input signal by setting I/O data in the %WWnnnn or
%XWnnnn format and connecting it to a regulatory control block or calculation block.
TIP
nnnn is a number within the area.
nnnn: 0001 to 4000
SEE
ALSO For detailed information on how to treat analog inputs, see the following:
1.3, “Accessing Subsystem Data from a Function Block” in the Communication with Subsystems Using FIO
(IM 33K03L20-50E)
l Analog Output
I/O data can be treated as an analog output of function blocks such as a regulatory control block,
calculation block, and sequence control block by setting I/O data in the %WWnnnn or %XWnnnn
format.
TIP
nnnn: 0001 to 4000
SEE
ALSO For detailed information on analog outputs, see the following:
4.3.6, “Function Block Detail Builder”

l Discrete I/O
By setting I/O data in the %WBnnnnbb or %XBnnnnbb format, every word of I/O data can be
treated as a discrete input or a discrete output.
TIP
bb is a bit number in a word.
SEE
ALSO For detailed information on discrete I/O, see the following:
1.3, “Accessing Subsystem Data from a Function Block” in the Communication with Subsystems Using FIO
(IM 33K03L20-50E)
n Accessing I/O Data Using SEBOL Statements

SEBOL statements can be used to access FCS communication I/O data from SFC blocks.
writing.
SEE
ALSO For more information on SEBOL, see the following:

<4.3 System Builders> 4-22
4.3 System Builders

This section explains engineering tasks for ALP121.

4.3.1 Overview of Engineering of ALP121

This section explains the overview of engineering.
n System Builders of ALP121

The figure below shows the mutually related functions that are used in engineering tasks of
ALP121.
System View PROFIBUS

•PROFIBUS Communication Definition Check before Downloading Start-up PROFIBUS-DP Create
communication
•Saving PROFIBUS Communication Definitions Configurator definition file
•Downloading PROFIBUS Communication Definitions
Start-up
Reading PROFIBUS
communication
Reference data Communication I/O definition
Function Block Communication I/O
Definition Support
Detail Builder Builder
Tool
N040301E.ai
Figure System Builders of ALP121
l System View
The System View is used to create new ALP121 definitions and set redundant ALP121
configuration.
In addition, it is used to start the PROFIBUS-DP configurator, Communication I/O Builder, and
Communication I/O Definition Support Tool.
l PROFIBUS-DP Configurator of SYCON.net/YOKO Made by Hilscher Co.

This is used to specify configuration information of master devices and slave devices as well as
PROFIBUS communication definitions.
l Communication I/O Definition Support Tool

This tool displays module configuration information of slave devices specified by the PROFIBUS-
DP configurator to support inputs to Communication I/O Builder.
l Communication I/O Builder

This builder assigns I/O data of PROFIBUS-DP communication to element numbers of
l Function Block Detail Builder

This builder sets communication I/O data to analog output data of regulatory control blocks,
calculation blocks, sequence control blocks and other function blocks.
l PROFIBUS Communication Definition Check before Downloading

This function is started from the Tools menu of the System View. Only the current project can be
operated.
The function displays status of downloading PROFIBUS communication definitions and
differences from the definitions saved previously. It is also possible to check slave devices whose
settings are changed when PROFIBUS communication definitions are downloaded.

l Saving PROFIBUS Communication Definitions
This function is started from the Tools menu of the System View. Only the default project and
user-defined projects can be operated.
This function creates PROFIBUS communication definition databases based on PROFIBUS
communication definition information file specified and saved using the PROFIBUS-DP
configurator.
l Downloading PROFIBUS Communication Definitions

This function is started from the Tools menu of the System View. Only the current project can be
operated.
This function creates PROFIBUS communication definition databases based on PROFIBUS
communication definition information file specified and saved using the PROFIBUS-DP
configurator, and then downloads to ALP121 via FCS.

The following chart shows the basic engineering procedures using the System builders and the
Definition of ALP121 in System View
Setting PROFIBUS communication

definition by PROFIBUS-DP configurator
Communication I/O definitons by

Communication I/O Definition Support Tool
Link to a function block using Test

Control Drawing Builder
Operations not using Debugging using test function

actual FCS
Operations using
actual FCS PROFIBUS-DP communication definition
check before downloading
Debugging using download function
Error check
END
N040302E.ai
l Definition of ALP121 in the System View

Define ALP121 in the System View.
l Setting of PROFIBUS Communication Definition by the PROFIBUS-DP

Configurator
Start the PROFIBUS-DP configurator from the System View and specify slave device
configuration, slave device module configuration, and communication information definitions.
l Communication I/O Definitions by Communication I/O Definition Support Tool

Start the Communication I/O Definition Support Tool from the System View. The Communication
I/O Definition Support Tool displays module information of slave devices specified with the
PROFIBUS-DP configurator. Information displayed on this tool is assigned to element numbers
of Communication I/O Builder by mouse operations.
l 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.

l Debugging Using Test Function
Use the test function to debug the FCS application. I/O isolation and wiring can be performed.
l PROFIBUS-DP Communication Definition Check before Downloading

Start this function from the Tools menu of the System View.
This function displays download condition of PROFIBUS communication definitions and
differences from definitions saved previously.
l Download
This function downloads the engineered information to the FCS and ALP121.
l Error Check
If there is an error in the assignment of communication I/O definitions to element numbers, a
system alarm will be generated when the ALP121 is started. At this point, check to see if any
system alarms have been generated.
SEE
ALSO For detailed engineering procedures, see the following:
4.3.2, “Engineering Procedures”

4.3.2 Engineering Procedures

This section explains the procedures of the following engineering tasks.
For more information about the PROFIBUS-DP configurator, refer to the manual of the
The following engineering tasks are performed:
• Creating new ALP121
• Setting PROFIBUS communication definitions
• Saving PROFIBUS communication definitions
• Assigning PROFIBUS communication definitions to element numbers of
Communication I/O Builder
• Downloading PROFIBUS communication definitions
• Changing redundancy definition items in the IOM Properties
• Reusing PROFIBUS communication definitions of ALP111
• Migrating from ALP111 to ALP121
• Changing the slave devices of the same station address for a different model
SEE
ALSO For the specific operating methods of the System View, Communication I/O Definition Support Tool, etc., see the
following:
4.3.3, “System View” and subsequent sections

n Creating New ALP121

To create a new ALP121 in the System View, follow the procedure below.
1. Select an IOM folder from the tree view of the System View and create a new node.
2. Select a node folder for which ALP121 is to be created from the tree view of the System
View.
3. From the menu bar, select [File] - [Create New] - [IOM].
The Create New dialog box of IOM appears.
4. Click the [Type and Position] tab. Set the following items.
• “IOM Type”
Category: Select “Profibus-DP communication” from the Category list.
Type: Select “ALP121 (Profibus-DP communication)” from the Type list.
• “Installation Position”
Enter or select the slot number in which the ALP121 card is installed in the Slot field.
• “Duplicate Next Card”
Select the “Duplicate Next Card” check box if the adjacent card is made redundant.
• “High Speed Read”
Select the “High Speed Read” check box to read data from IOM at high speed.
5. Click the [Set Details] tab ,then change the settings as required.
6. Check the settings in the Create New dialog box of IOM and click the [OK] button.
TIP
• For ALP121, it is possible to set OOP suppression function regardless of whether IOM is in single or
redundant configuration.
• Set the “Type of Redundancy” on IOM property if you selected the “Duplicate Next Card”.

n Setting PROFIBUS Communication Definitions

PROFIBUS communication definitions are set in one of the following methods.
• Define anew
• Change existing definitions
l Defining Anew
Follow the procedure below to make new PROFIBUS communication definitions.
1. Obtain the GSD file of the slave device used.
2. From the Start menu, select [All Programs] - [YOKOGAWA CENTUM] - [Copy Tool for
Fieldbus associated files].
The Copy Tool for Fieldbus associated files starts up.
3. Set the folder name in which the obtained GSD file is stored as the copy source folder.
Moreover, set <CENTUM VP Project Top Folder>\PROFIBUS\GSDFILE\ as the copy
destination folder.
4. Check the settings and click the [OK] button.
5. Double-click “sALP121” in the list view of the System View.
The Builder Start dialog box appears.
6. Select “PROFIBUS-DP Configurator.”
7. Check the settings and click the [OK] button.
The PROFIBUS-DP configurator starts up.
8. Import the GSD file and make PROFIBUS communication definition settings.
9. Save the set file and then close the PROFIBUS-DP configurator.
TIP
“s” in “sALP121” indicates a slot number.
SEE
ALSO For the manual of the PROFIBUS-DP configurator, see the following:
Manual stored in <DVD-ROM Drive>: \CENTUM\PDFFILE\PROFIBUS_Configurator\en\

l Changing Existing Definitions
Follow the procedure below to change definitions.
1. If there are slave devices to be added anew, obtain new GSD files.
2. Use the Fieldbus related file copy tool and copy the GSD files to <CENTUM VP Project Top
Folder>\PROFIBUS\GSDFILE\.
3. Start the PROFIBUS-DP configurator from the System View, import the GSD file and
change the PROFIBUS communication definitions.
4. Save the settings and then close the PROFIBUS-DP configurator.
5. Select the applicable ALP121 in the System View’s list view and select [Tools] -
[PROFIBUS-DP] - [Pre-check before downloading PROFIBUS communication settings...]
from the menu bar.
Differences from the settings made before making the changes are displayed after the
checking before PROFIBUS communication definition download.
6. Check the modified settings.
If you wish to change the modified setting again, start the PROFIBUS-DP configurator and
make the settings again.
n Saving PROFIBUS Communication Definitions

In the case of default project or user-defined project, select [Save PROFIBUS communication
settings...].
Follow the procedure below to save PROFIBUS communication definitions.
1. Select the applicable ALP121 in the list view of the System View.
2. Select [Tools] - [PROFIBUS-DP] - [Save PROFIBUS communication settings...] from the
menu bar.
A database for downloading PROFIBUS communication definitions is created based on the
saved PROFIBUS communication definition data.

n Assigning PROFIBUS Communication Definitions to Element

Numbers of Communication I/O Builder
Follow the procedure below to assign PROFIBUS communication definitions to element numbers
of Communication I/O Builder.
• Assign anew
• Make additional assignment
• Change assigned I/O
l Assigning Anew
Follow the procedure below to define new PROFIBUS communication for ALP121 in
2. Select “Communication I/O Builder and Support Tool.”
3. Check the specifications and click the [OK] button.
The Communication I/O Definition Support Tool and Communication I/O Builder start up.
4. Select modules of slave devices you wish to assign with the Communication I/O Definition
Support Tool.
5. Drop modules of slave devices you wish to assign to odd element numbers with the
Communication I/O Definition Support Tool.
PROFIBUS communication definitions of the modules of slave devices selected with the
Communication I/O Definition Support Tool are set as definition items of Communication I/O
Builder.
6. Modify definition items as necessary in Communication I/O Builder.
7. Click [File] - [Save] or [File] - [Download] from the File menu of Communication I/O Builder.
The definitions are saved or downloaded.
TIP
• ”s” in “sALP121” indicates a slot number.
• If you do not assign the PROFIBUS communication definitions to element numbers of Communication
I/O Builder after creating a ALP121, The Communication I/O Builder for %WW starts up by operation
of procedure 3. If you wish to assign the PROFIBUS communication definitions to element numbers of
Communication I/O Builder for %XW, Start up Communication I/O Builder of the applicable FCS. The
Communication I/O Builder for %XW starts up automatically after assigning PROFIBUS communication
definitions to element number of %XW and saving it.

l Making Additional Assignment
Follow the procedure below to add modules of slave devices that were not assigned in the first
engineering to Communication I/O Builder.
Support Tool.
5. Drag and drop modules of slave devices you wish to assign to odd element numbers not yet
assigned in the secured area with the Communication I/O Definition Support Tool.
Builder.
7. Click [File] - [Save] from the File menu of Communication I/O Builder.
The definitions are saved.
8. Click [File] - [Download] from the File menu of Communication I/O Builder.
The definitions are saved and downloaded.
TIP
• “s” in “sALP121” indicates a slot number.
• If you will add modules of slave devices and define to Communication I/O Builder after the first engineering,
follow the operation below. You will extend the size of “Buffer” on Communication I/O Builder, Drag and drop
modules of slave devices you wish to assign to odd element numbers not yet assigned in the secured area
with the Communication I/O Definition Support Tool.

l Changing Assignment
Follow the procedure below to expand the storage area size and change the existing assignment
definition status in Communication I/O Builder.
4. In Communication I/O Builder, delete the definitions assigned to element numbers to be
changed.
Support Tool.
6. Drag and drop modules of slave devices you wish to assign to odd element numbers not yet
assigned in the secured area with the Communication I/O Definition Support Tool.
Builder.
8. Click [File] - [Save] from the File menu of Communication I/O Builder.
9. Click [File] - [Download] from the File menu of Communication I/O Builder.
The definitions are saved and downloaded.
TIP
”s” in “sALP121” indicates a slot number.

n Downloading PROFIBUS Communication Definitions

Follow the procedure below to download PROFIBUS communication definitions.
• Offline download
• Online download
Offline download involves initialization of the ALP121, while online download does not involve
initialization of the ALP121.
l Offline Downloading
Perform offline download when downloading PROFIBUS communication definitions to the FCS
station and ALP121 for the first time.
Follow the procedure below to download definitions to the FCS station and ALP121 offline.
1. Select a node folder in System View’s tree view and select [Load] - [Download to IOM...] in
the menu bar.
The IOM download dialog box appears.
2. Select a slot to which definitions are to be downloaded and click the [OK] button.
The ALP121 program, IOM property information, PROFIBUS communication definitions,
and I/O information are downloaded to the selected ALP121.
l Online Download
Online download is possible only when the project for which PROFIBUS communication
definitions are created is the current project.
Follow the procedure below to download definitions to the FCS station and ALP121 online.
1. From the System View’s list view, select the applicable ALP121 and select [Tools] -
[PROFIBUS-DP] - [Download PROFIBUS communication settings...] from the menu bar.
The difference from the PROFIBUS communication definition downloaded previously is
displayed in the dialog box.
2. Check the information and click the [Yes] button.
Online download is started and the download processing start message appears in the
System View’s message display area.
When the download succeeds, the completion message appears in the System View’s
message display area.
TIP
The ALP121 is initialized when any of the bus parameters and master settings has been changed by the

n Changing Redundancy Definition Items in the IOM Properties

Change redundancy definitions in the following cases.
• When the configuration was changed from single to redundant configuration
• When the configuration was changed from redundant to single configuration
• When the configuration type was changed from network redundancy to module redundancy
• When the configuration type was changed from module redundancy to network redundancy
Follow the procedure below to change redundancy definitions.
1. Select the slot whose redundant configuration you wish to change and change redundancy
definitions, click the [OK] button.
The IOM property information and I/O information are downloaded to the selected ALP121.
2. Select a node folder in the System View’s tree view and select [Load] - [Download to IOM...]
from the menu bar.
The IOM Download dialog box appears.
3. Start the PROFIBUS-DP configurator from the System View and change the PROFIBUS
communication definitions.
4. Save the settings and then close the PROFIBUS-DP configurator.
TIP
The ALP121 program, IOM property information, PROFIBUS communication definitions, and I/O information are
downloaded to the selected ALP121 when you select [IOM Load] of HIS’s Node Status Display dialog box as well.
n Reusing PROFIBUS Communication Definitions of ALP111

Follow the procedure below to reuse ALP111 PROFIBUS communication definitions created with
existing projects for ALP121.
1. Use the Fieldbus related file copy tool to copy the GSD file of slave device used when
making ALP111 PROFIBUS communication definitions to <CENTUM VP Project Top
Folder>\PROFIBUS\GSDFILE\.
2. In the System View, select ALP121 for which PROFIBUS communication definitions are to
be made and start the PROFIBUS-DP configurator.
3. Import the GSD file and import the project file for which ALP111 PROFIBUS communication
definitions were made and set PROFIBUS communication definitions.
4. Save PROFIBUS communication definitions and close the PROFIBUS-DP configurator.
5. Select the applicable ALP121 in the System View’s list view and select [Tools] -
[PROFIBUS-DP] - [Save PROFIBUS communication settings...] from the menu bar.
A database for downloading PROFIBUS communication definitions is created based on the
PROFIBUS communication definition data.
6. Double-click [sALP121] in the list view of the System View.
7. Select “Communication I/O Builder and Support Tool” and click the [OK] button.
The Communication I/O Definition Support Tool and Communication I/O Builder appear.
Use the Communication I/O Definition Support Tool to assign slave device modules to
element numbers such as %WW and %XW in Communication I/O Builder.
8. In Communication I/O Builder, select [File] - [Save] in the menu bar.
9. Close the System View.

10. Select [YOKOGAWA CENTUM] - [Project’s Attribution Utility] from the Start menu.
The Project Attribute Change Utility appears.
11. Change the project attributes to the current project.
12. Close the Project Attribute Change Utility.
13. In the System View’s tree view, select the FCS station folder of the current project and select
[Load] - [Offline Download to FCS] - [Download] from the menu bar.
The Offline Download dialog box appears.
14. Click the [OK] button.
Offline download is started. A message appears during downloading.
15. In the System View’s tree view, select the node folder and select [Load] - [Download to
IOM...] from the menu bar.
The IOM Download dialog box appears.
16. Select the slot to which the definition is to be downloaded and click the [OK] button.
The ALP121 program, IOM property information, PROFIBUS communication definition, and
I/O information are downloaded to the selected ALP121.
IMPORTANT
Only PROFIBUS communication definition project files for ALP111 created in SYCON-PB/YOKO
V2.959 or later can be imported.
TIP
n Migrating from ALP111 to ALP121

Follow the procedure below to upgrade the system revision to change to engineering tasks using
ALP121.
1. Perform the standard system revision upgrade operations.
2. Write down necessary information from the IOM property information of ALP111 and then
delete the IOM of ALP111.
3. Follow the procedure in “n Reusing PROFIBUS Communication Definitions of ALP111.”

n Changing the slave devices of the same station address for a different
model
To change the slave devices of the different model as the same station address , follow the
procedure below.
1. Remove the changing slave device from the Profibus line.
2. Delete the setting of %WW or %XW for removed the slave device in Communication I/O
Builder.
3. Delete the setting of the removed the slave device in PROFIBUS-DP Configurator.
4. Set the same station address for a new slave device in PROFIBUS-DP Configurator.
5. Save PROFIBUS communication definitions and close the PROFIBUS-DP configurator.
7. Set the %WW or %XW for the changed slave device in PROFIBUS-DP Configurator.
8. Connect a new slave device on Profibus line.

4.3.3 System View

The IOP / OOP suppression and ALP121 dual-redundancy settings are made in the
System View’s FCS Properties and IOM Properties.
Note that the PROFIBUS-DP configurator used when engineering ALP121 and slave
devices is also started from the System View.
n FCS Properties
The IOP suppression to ALP121 cards can be set.
In this sheet, OOP suppression to ALP121 cards in single or redundant configuration can be set.
If you set the OOP suppression, no OOP alarms are sent to an FCS during online maintenance
of ALP121.
l Constant Tab
The IOM online updating option can be selected on [Constant] tab of FCS properties sheet.
The option of [IOP Occurs in Connected Blocks] can be selected or unselected. By initial value, it
is not selected.
l Constant 3 Tab
The OOP suppression is set in the [Constant 3] tab.
Table FCS Properties: Constant 3 Tab
Item Remarks
MV of Switch Instrument/MC Instrument follows its CSV change
TM/CTS/CTP blocks hold PALM after CTUP
Raised %AN sends out alarm when AOF released
Suppress OOP alarms during online maintenance of ALP121 and
Not enabled by Initial value
dual-redundant ALP111
CENTUM-XL compatible IOP reactions
Suppress system alarm when CALCU calculation error occurs
Use HKU of System Cabinet
Initiate process alarm when CAL is set or released
Allow to change function block to PRD mode while CAL is on(XL
compatible)
LC64-E starts with its internal status intact when FCS performs an
initial start
Command (L)

Properties
type Constant Constant 2 Constant 3 State Transition Line1 Network
MV of Switch Instrument/MC Instrument follows its CSV change
TM/CTS/CTP blocks hold PALM after CTUP
Raised %AN sends out alarm when AOF released
Suppress OOP alarms during online maintenance of ALP121 and dual-redundant ALP111
CENTUM-XL compatible IOP reactions
Suppress system alarm when CALCU calculation error occurs
Use HKU of System Cabinet
Initiate process alarm when CAL is set or released
Allow to change function block to PRD mode while CAL is on (XL compatible)
LC64-E starts with its internal status intact when FCS performs an initial start
Command (L)
Revert to inital value
OK Cancel
N040303E.ai
Figure FCS Properties: Constant 3 Tabs
TIP
The “Suppress OOP alarms during online maintenance of ALP121 and dual-redundant ALP111” definition item is
set commonly for all FCSs.

n IOM Properties
▼ Type of Redundancy,Perform Fallback,Action when module/channel fail detected, Command
Dual-redundancy of ALP121 is set in the IOM Properties sheet.
Table IOM Properties: Type and Position Tab
Item Detail Remarks
Category Select “Profibus-DP Communication.”
IOM Type
Type Select “ALP121 (Profibus-DP Communication).”
Installation Position Slot 1 to 8 slots can be selected.
Two adjacent ALP121 modules (in an odd numbered slot
Duplicate Next Card and the subsequent slot) can be made dual-redundant for
the ALP121 in an odd numbered slot only.
Output Type Cannot be selected.
High Speed Read
IOM Comment
Properties
IOM Type
Category Profibus-DP Communication
Type ALP121 (Profibus-DP Communication)
Installation Postion
Slot 3
Duplicate Next Card
Output Type
Output in a lump Output immediately
High Speed Read
IOM Comment
OK Cancel
N040314E.ai
Figure IOM Properties: Type and Position Tabs

Table IOM Properties: Set Details Tab
Item Detail Remarks
IOM Category
IOM Type Display settings defined in the Type and Position tab.
Slot
The definition item is validated if “Duplicate Next Card” in
the Type and Position tab is selected.
Type of Redundancy Module Redundancy
Redundancy type is determined by radio buttons. The
Network Redundancy default setting is “Module redundancy.”
Fallback operation is enabled/disabled by the check box.
By default, the setting is “enabled” (the box is checked).
Perform Fallback All points maintain Current
value Fallback operation is determined by radio buttons. The
default setting is “All points maintain current values.”
Reset all outputs
The action to be taken upon the detection of module
Set all corresponding module
failure is determined by the check box. By default, the
input data to IOP (*1)
setting is “disabled” (the box is not checked).
The action to be taken upon the detection of module
Set all corresponding module
Action when module/ input data to OOP (*1) failure is determined by the check box. By default, the
channel fail detected 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
Prefixed slave device channel
“0” or “1” can be selected. The default value is “0.”
number in alarm message
A character string of up to 32
Command (L) The default is blank.
characters
Default The value set for each item is restored to the default value.
*1 Valid only when I/O data of slave devices is defined in the module specification.
Properties
IOM Category Profibus-DP Communication

IOM Type ALP121(Profibus-DP Communication)
Slot 3
Type of Redundancy
Module Redundancy
Network Redundancy
Perform Fallback
Restart all output

Set all corresponding module intput data to IOP
Head of Slot numbers of Slave Device in Message 1
Prefixed slave device channel number in alarm message 0
Command (L)
Default
OK Cancel
N040304E.ai
Figure IOM Properties: Set Details Tab

n PROFIBUS-DP Configurator
The PROFIBUS-DP configurator is controlled exclusively.
Due to the exclusive control, there are the following restrictions on its start.
• It is not allowed to start multiple instances of PROFIBUS-DP configurator for ALP121 on a
single PC.
• Only one instance of PROFIBUS-DP configurator can be started per system. A startup
error occurs if an instance of PROFIBUS-DP configurator is started on a PC while another
instance of PROFIBUS-DP configurator is already started on another PC.
• While the PROFIBUS-DP configurator is active, it is not possible to delete FCS stations
and/or ALP121 cards on the System View.
• While the PROFIBUS-DP configurator is active, it is not possible to close the System View.
IMPORTANT
The below describes the notices on using PROFIBUS-DP Configurator.
• It does not support Time Synchronization Function. The check box of the Time
Synchronization for V2 device set OFF. And for more information about the PROFIBUS-DP
Configurator, refer to the manual of the PROFIBUS-DP Configurator.
• When it changes “Symbolic Name” of the slave devices,it must set it in ASCII.

4.3.4 GSD File

To make PROFIBUS communication definitions on the PROFIBUS-DP configurator, it is
necessary to import the obtained GSD file.
A GSD file can be copied using the Copy Tool for Fieldbus associated files.
Copy Tool for Fieldbus associated files

Select copy folder or file, and destination folder
Select copy source
Copy folders
Copy files
Select copy destination
Advanced... Protect key... OK Cancel

N040305E.ai
Figure Copy Tool for Fieldbus associated files
Follow the procedure below to import a GSD file to the PROFIBUS-DP configurator.
1. Select [All Programs] - [YOKOGAWA CENTUM] - [Copy Tool for Fieldbus associated files]
from the Start menu.
The Copy Tool for Fieldbus associated files appears.
2. Select the “Select Folder” radio button in the Select Copy Source section and enter the path
to the folder in which the obtained GSD file is stored in the text edit box. Alternatively, click
the […] button and select the folder path.
3. Select the copy destination folder.
Path name: <CENTUM VP Project Top Folder>\PROFIBUS\GSDFILE\
4. Click the [OK] button.
The GSD file to be used is copied under the specified folder.
SEE
ALSO For the manual of the PROFIBUS-DP configurator, see the following:
Manual stored in <DVD-ROM Drive>: \CENTUM\PDFFILE\PROFIBUS_Configurator\en\

4.3.5 Communication I/O Definition Support Tool

The support tool displays the I/O configuration information of PROFIBUS communication
definitions specified with the PROFIBUS-DP configurator.
Displayed information can be pasted onto the Communication I/O Builder by using the
drag & drop operation.
n Window Structure of the Communication I/O Definition Support Tool

The structure of the Communication I/O Definition Support Tool window is as follows.
• PROFIBUS communication definition information display area
This area displays PROFIBUS communication definitions of slave device modules specified
with the PROFIBUS-DP configurator.
The PROFIBUS communication definition is displayed by the ascending order of Station
address, Slot and Index.
• [Update] button
This button refreshes and displays data shown in the PROFIBUS communication definition
information display area.
Communication I/O Support Tool PJT FCS0101 NODE1 3ALP121
PROFIBUS communication settings
Selection/Total size 0/ 0 Word
Assigned element Station address Slot Index Slave device name Tag name of the module Data Type Size
Update Close
N040315E.ai
Figure Communication I/O Definition Support Tool

n Data Displayed in the PROFIBUS Communication Definition

Information Display Area
The table below summarizes data displayed in the PROFIBUS communication definition
information display area.
Table Data Displayed in the PROFIBUS Communication Definition Information Display Area
Display item Explanation
This item displays assigned element number of communication I/O definition. If an
assigned element number is already shown, it means that it is already assigned to
%WW or %XW.
With this display item, you can see whether PROFIBUS communication definition
Assigned element
is already assigned to an element number using Communication I/O Builder or not
as well as if it is already assigned, to which element number, %WW or %XW, it is
assigned. Moreover, you can check the definition is not assigned to %WW or %XW
redundantly.
Station address This item shows the station address set in the PROFIBUS-DP configurator.
Slot This item shows the slot set in the PROFIBUS-DP configurator.
Index This item shows the index set in the PROFIBUS-DP configurator.
Slave device name This item shows the name set in the PROFIBUS-DP configurator.
Tag name of the module This item shows the module tag name set in the PROFIBUS-DP configurator.
Data type This item shows the data type set in the PROFIBUS-DP configurator.
This item shows data length set in the PROFIBUS-DP configurator.
While the PROFIBUS-DP configurator displays the size in units of bytes, this tool
Size displays the size in word units.
If the size displayed in Communication I/O Builder is 1 to 2 bytes, this tool displays 1
word, and if 3 to 4 bytes, it displays 2 words.
This item displays assignment size required for all slave device modules specified
with the PROFIBUS-DP configurator as the total size. Moreover, it displays the
Selection/Total size
total assignment size of slave device modules selected on the Communication I/O
Definition Support Tool as the selection size.
n Starting the Communication I/O Definition Support Tool

Follow the procedure below to start the Communication I/O Definition Support Tool.
1 Double-click “sALP121” in the list view of the System View.
2 Select “Communication I/O Builder and Support Tool” and click the [OK] button.
Communication I/O Builder and Communication I/O Definition Support Tool appear.
Start Builder
PROFIBUS-DP Configurator
Communication I/O Builder and Support Tool
OK Cancel
N040316E.ai
Figure Builder Startup Dialog Box
TIP

l Assigning Module Information of Slave Device
Follow the procedure below to assign information displayed in the PROFIBUS communication
definition information display area of the Communication I/O Definition Support Tool to element
numbers of Communication I/O Builder.
1. Select module information of slave device you wish to set from the module information of
slave devices shown in the PROFIBUS communication definition information display area.
2. Select an odd element number in Communication I/O Builder.
The module information of slave device displayed in the PROFIBUS communication
definition information display area is set as the definition in Communication I/O Builder.
The table below summarizes items set in Communication I/O Builder.
Setting items other than element number and user definition label can be set as setting items of
Communication I/O Builder using the Communication I/O Definition Support Tool.
Table Items Set in Communication I/O Builder
Setting item Description
Element number This item displays an element number.
The size of all modules displayed by the Communication I/O Definition Support Tool is
Buffer
automatically calculated and set as the buffer size.
The program name of slave device dragged and dropped with the Communication I/O
Program Name
Definition Support Tool is automatically set.
The “size” of the module selected in the PROFIBUS communication definition information
Size
display area is specified.
Port 1 is set by initial value.
IP address Blank
The “station address” of the module selected in the PROFIBUS communication definition
Station
information display area is specified.
The “slot” and “index” of the module selected in the PROFIBUS communication definition
Device & Address information display area are specified and displayed in the format of <slot>-<index>. If
“index” is only 1 for a module, display of “index” is omitted.
The following initial values are set based on “data element” of the module selected in the
PROFIBUS communication definition information display area is specified.
IB: Input (Discrete)
Data Type
IW: Input (16-bit Unsigned)
QB: Output (Discrete)
QW: Output (16-bit Unsigned)
The following initial values are set based on “data element” of the module selected in the
PROFIBUS communication definition information display area is specified.
Reverse
IB/QB: Yes
IW/QW: None
Scan “None” is set by initial value.
The “slave device name” and “module tag name” of the module selected in the
PROFIBUS communication definition information display area are specified and
displayed in the format of <slave device name>,<module tag name>. If the number of
characters exceeds the maximum character string length of 40 characters, the string is
Service Comment truncated at 40 characters.
“Slave device name”: Up to 20 characters.
“Module tag name”: Number of characters obtained by subtracting the number of “slave
device name” characters and one character of comma from the maximum character
string length of 40 characters.
Label Blank

4.3.6 Function Block Detail Builder

By using Function Block Detail Builder to change the I/O data type to %WWnnnn or
%XWnnnn, I/O data can be treated as analog output data of regulatory control blocks,
calculation blocks, sequence control blocks, and other function blocks.
n Setting of Function Block Detail Builder

Follow the procedure below to treat I/O data as analog output data of function blocks.
1. Click the [Basic or Output] tab of Function Block Detail Builder.
2. Select “Communication Output (Fully-open/Tightly-shut)” for the output signal conversion of
the [Output Signal Conversion] item.
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
SEE
ALSO For more information on output signal conversion, see the following:
4.8, “Output Signal Conversion” in the Function Blocks Overview (IM 33K03E21-50E)

4.3.7 Checking before PROFIBUS Communication

Definition Downloading
This function displays the status of PROFIBUS communication definition download and
differences from the previously saved definitions. The operation target is ALP121 of the
current project.
n Checking before PROFIBUS Communication Definition Downloading

Follow the procedure below to perform checking before PROFIBUS communication definition
downloading.
1. Select the ALP121 of the current project in the System View.
2. In the System View, select [Tools] - [PROFIBUS-DP] - [Pre-check before downloading
PROFIBUS communication settings...].
TIP
If the module redundancy or network redundancy configuration is used, [Pre-check before downloading
PROFIBUS communication settings...] can only be selected when an odd slot is selected.

4.3.8 Saving PROFIBUS Communication Definitions,

Downloading PROFIBUS Communication Definitions
PROFIBUS communication definition information set or saved with the PROFIBUS-
DP configurator is used to create a PROFIBUS communication definition database or
downloaded to the ALP121.
n Saving PROFIBUS Communication Definitions

This function is used to set PROFIBUS communication information using the PROFIBUS-DP
configurator and create a PROFIBUS communication definition database based on the saved
PROFIBUS communication definition information. The operation target is ALP121 of a default
project or user-defined project.
Follow the procedure below to save PROFIBUS communication definitions.
1. Select ALP121 of a default project or user-defined project in the System View.
2. In the System View, select [Tools] - [PROFIBUS-DP] - [Save PROFIBUS communication
settings...].
n Downloading PROFIBUS Communication Definitions

This function is used to set PROFIBUS communication information with the PROFIBUS-DP
configurator, create a PROFIBUS communication definition database based on the saved
PROFIBUS communication definition information, and download it to ALP121. The operation
target is ALP121 of the current project.
Checking before PROFIBUS communication definition downloading is performed before the
database is downloaded.
Follow the procedure below to download PROFIBUS communication definitions.
1. Select ALP121 of the current project in the System View.
2. In the System View, select [Tools] - [PROFIBUS-DP] - [Download PROFIBUS
communication settings...].
It detects the difference from the PROFIBUS communication definition, and a confirmation
dialog box is appeared whether or not perform the download.
3. Click the [Yes] button.
When it is not accompanied by re-initialization of ALP121, it is downloaded.
When it is accompanied by re-initialization of ALP121, moreover a confirmation dialog box is
appeared whether or not perform the download with re-initialization of ALP121.
If you click the [Yes] button, the definitions are downloaded.
If you click the [No] button, the definitions are not downloaded.
TIP
Only Bus parameter and Master Settings of the master devices cause ALP121 re-initialization.

4.3.9 Advanced Engineering

The following definition items are included in advanced engineering operations.
• Specification of I/O Data
• Specification of Diagnostic Information
• Specification of Device Specific Diagnostic Information
• Specification of Module Diagnostic Information
• Specification of Channel Diagnostic Information
• Specification of Device Communication Status Information
n Specification of I/O Data

I/O data of PROFIBUS-DP is defined using Communication I/O Builder in the following methods.
l Module Specification
In this method, a slave device module is specified, and all relevant data for the module is
specified at once. Errors are detected for the entire module and reflected in the data status.
With module specification, it cannot detect errors of individual channels and reflect them in the
data status.
• Scope of application
Use this method to specify data that does not fall under definitions by specification for each
channel or channel batch specification.
Example:
- Array data for specifying slot numbers
- Multiple data types are used to specify “slot number-index number”
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 ALP121 can be reduced.
l Specification for Each Channel

In this method, data for I/O channels of a slave device is specified for each I/O channel. Errors
can be detected for each channel and reflected in the data status.
• Requirements for employing this method
The slave device used must support “channel diagnostic information.”
communication I/O definitions.
Moreover, the head channel data of this layout must be the data of channel 0.
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, the required data area
can be reduced.

l Channel Batch Specification
In this definition method, data for a number of consecutive I/O channels of a slave device is
specified at once. This method allows detecting errors of each channel and reflecting them in the
data status.
• Requirements for employing this method
communication I/O definitions. Moreover, the head channel data of this layout must be the
data of channel 0.
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 ALP121 can be reduced.
l I/O Data Engineering Method

Follow the procedure below to specify PROFIBUS-DP I/O data using Communication I/O Builder.
1. Set common setting items and assign the communication I/O data area to ALP121.
Table Common Setting Items in Communication I/O Builder
Designate the size of the area for storing communication I/O definition data to be used in
Buffer
an ALP121. The maximum value of the size is 1000.
Designate the installation position of an ALP121 (Kl-n-s, l: bus system number, n: node
number, s: slot number) and the program name (PROFIBUS).
Program Name
Example: When the module is installed on FIO bus system 1, node 2 and slot 4
K1-2-4PROFIBUS
2. Specify communication I/O information for each slave device module.

• When setting data by module specification.
Set data for each module of the slave device.
The following items shall be set in Communication I/O Builder.
Table Module Specification
Size Enter the size to be assigned for a single device module in units of words (*1).
Station Station Address in the Slave Configuration dialog box.
Device & Address Slot and Idx in the Slave Configuration dialog box.
Data Type Specify the type according to the module specification of the device.
Reverse Refer to the manual of the device and specify “No” for bit reversal and byte reversal.
*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.
• When setting data by specification for each channel

The following item is set differently from setting data by module specification.
Table Specification for Each Channel
Device & Address Slot, Idx and channel number in the Slave Configuration dialog box.

• When setting data by channel batch specification
The following item is set differently from setting data by module specification.
Table Communication I/O Items Defined in the Case of Channel Batch Specification
Device & Address Slot, Idx, channel number, extension (R) in the Slave Configuration dialog box.
l Items that can be Set in Communication I/O Builder

Set the following items associated with the communication I/O data area to engineer I/O data of
PROFIBUS-DP using Communication I/O Builder.
Table Setting Items in Communication I/O Builder
Setting item Detail Remarks
Enter the size of the entire area for storing the
Buffer
ALP121 data.
Enter the installation position of a module followed
Program Name
by “PROFIBUS.”
Enter the size to be assigned for a single slave
device module. The size is assigned in units of Entering an out of range value will not
Size
words (2 bytes). The valid range of values is from generate an error in the builder.
1 to 126.
Enter the port number. Entering a port number will not
Port
This is not used for ALP121, however. generate an error.
Enter the IP addresses of other devices. This is Entering an IP address will not
IP Address
not used for ALP121, however. generate an error.
Enter the node address of a slave device. The Entering an out of range value will not
Station
valid range of values is from 0 to 125. generate an error in the builder.
Designating an unused or out of
Define in the range of up to 8 single-byte range slot number/index will cause
Device & Address
alphanumeric characters. the status of the data in question to
be set to IOP/OOP upon execution.
Data Type Set according to the slave device specifications.
Set whether or not to reverse the bit arrangement
Reverse in the FCS and data bit arrangement in the
subsystem.
Set whether or not to update communication I/O
Scan
analog data at the start of fast-scan.
Service Comment A comment can be entered.
The I/O terminal name can be entered as a user-
Label
defined label. This item is an optional setup item.

l Items Specified for [Device & Address]
When defining I/O data for a slave device by module or channel specification, specify the
[Device & Address] item of Communication I/O Builder in the following format.
mm[-nn][;[xxESHZR]]
mm: Slot number of module
nn: Index number
xx: Channel number
[ ]: Can be omitted
E, S, H, Z, R: Extension
when the module slot number is 3
3;1
when the module slot number is 3 and index number is 4
3-4;2

Table Specification Format for Device & Address
Channel
Module
specification
Definition Description specification
(single/batch)
AI/AO DI/DO AI/AO DI/DO
Specify the slot number of a slave device module.
Slot number Yes Yes Yes Yes
Range: 1 to 60
Specify the index number of a slave device module after
Index Yes (*1) Yes (*1) Yes (*1) Yes (*1)
“-.” Range: 1 to 60
Divide the part of module specification and the
Semicolon (;) No No Yes Yes
extension part that includes channel specification.
Channel Specify the channel number in a module. Range: 0 to 99
No No Yes Yes
number If omitted, it is treated as if a module is specified.
Extension (E) An identifier for expanding byte data to 16 bits. Yes (*1) No Yes (*1) No
Specification to reverse bytes: Reverse the upper and
lower bytes of digital data of a normal slave device
Extension (S) No Yes (*1) No Yes (*1)
whose upper and lower bytes are reversed, and
correspond it to the %WB numbers.
Specification to maintain output values.
Specify this extension to continue outputting the final
Extension (H) output value before downloading, during downloading
Yes (*1) Yes (*1) Yes (*1) Yes (*1)
(*2) changed PROFIBUS communication definition data to
an ALP121 or after restarting the ALP121.
If omitted, the output value becomes 0.
Specification to output 0 value. Specify this extension
to output 0 when initial cold start of an ALP121 after
Extension (Z) downloading.
Yes (*1) Yes (*1) Yes (*1) Yes (*1)
(*2) If omitted, 0 is output.
Use this option to intentionally specify operations in the
default status.
If a channel number is specified using a semicolon
(;), specification of “R” results in the same operation
Extension (R) No No Yes (*1) Yes (*1)
as when only the head channel of the area size
corresponding to all data is defined.
Yes: Entry is required.
No: Entry not allowed.
*1: Enter as necessary.
*2: A definition error occurs if H and Z are specified at the same time.

• 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 ALP121. The
table below lists the priority in the case of overlapping definitions.
Table Priority in the Case of Overlapped Definitions
Priority order Description of [Device & Address]
High mm
mm; [ESHZR]
mm; xx
mm; xx [ESHZR]
mm-nn
mm-nn; [ESHZR]
mm-nn; xx
Low mm-nn; xx [ESHZR]
nn: Index number
xx: Channel number
E, S, H, Z, R: Extension

l Specification of Consecutive Channels
When defining 8 channels individually, two definition methods are available.
• Defining each channel individually
• 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 each channel individually, but the number of definitions may be reduced. The figure
below shows examples of defining eight 16-bit analog I/O points (I16, U16).
The asterisk indicates that the channel has been assigned.
Individual Channel Definition Consecutive Batch Definition
Channel
%WW0101 1 3;0 → 0 16 3;R
%WW0102 * * * *
%WW0103 1 3;1 → 1 * *
%WW0104 * * * *
%WW0105 1 3;2 → 2 * *
%WW0106 * * * *
%WW0107 1 3;3 → 3 * *
%WW0108 * * * *
%WW0109 1 3;4 → 4 * *
%WW0110 * * * *
%WW0111 1 3;5 → 5 * *
%WW0112 * * * *
%WW0113 1 3;6 → 6 * *
%WW0114 * * * *
%WW0115 1 3;7 → 7 * *
%WW0116 * * * *
N040306E.ai
Figure Communication I/O Data when Extension R is specified
Specify the same area size as for individual channel definition for “Size.” The format used when
calling from %W is the same for both individual and batch definitions.
IMPORTANT
If individual channel definitions are specified, 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 ALP121.

Examples of specification of consecutive channels are shown below.
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)
Individual definition Batch definition
Analog input/output
1 to 2 byte 1 Number of points x 2
Discrete input/output
3 to 4 byte 2 Number of points x 2
The figure below shows examples of specifying consecutive channels by I/O type and size.
The asterisk indicates that the channel has been assigned.
• Eight 32-bit analog I/O points (I32, U32, F32)
Channel
Element number Size Device & Address Size Device & Address
number
%WW0101 2 3;0 → 0 16 3;R
%WW0102 * * * *
%WW0103 2 3;1 → 1 * *
%WW0104 * * * *
%WW0105 2 3;2 → 2 * *
%WW0106 * * * *
%WW0107 2 3;3 → 3 * *
%WW0108 * * * *
%WW0109 2 3;4 → 4 * *
%WW0110 * * * *
%WW0111 2 3;5 → 5 * *
%WW0112 * * * *
%WW0113 2 3;6 → 6 * *
%WW0114 * * * *
%WW0115 2 3;7 → 7 * *
%WW0116 * * * *
N040307J.ai
Figure Example of 32-Bit Analog Inputs/Outputs

• Eight 1-byte discrete I/O points (DI, DO)
Channel
Element number Size Device & Address Size Device & Address
number
%WW0101 1 3;0 → 0 16 3;R
%WW0102 * * * *
%WW0103 1 3;1 → 1 * *
%WW0104 * * * *
%WW0105 1 3;2 → 2 * *
%WW0106 * * * *
%WW0107 1 3;3 → 3 * *
%WW0108 * * * *
%WW0109 1 3;4 → 4 * *
%WW0110 * * * *
%WW0111 1 3;5 → 5 * *
%WW0112 * * * *
%WW0113 1 3;6 → 6 * *
%WW0114 * * * *
%WW0115 1 3;7 → 7 * *
%WW0116 * * * *
N040308J.ai

• 2-byte discrete inputs/output, 16 points (DI, DO)
Channel Device & Address
Element number Size Device & Address Size
number
%WW0101 1 3;0 → 0 32 3;R
%WW0102 * * * *
%WW0103 1 3;1 → 1 * *
%WW0104 * * * *
%WW0105 1 3;2 → 2 * *
%WW0106 * * * *
%WW0107 1 3;3 → 3 * *
%WW0108 * * * *
%WW0109 1 3;4 → 4 * *
%WW0110 * * * *
%WW0111 1 3;5 → 5 * *
%WW0112 * * * *
%WW0113 1 3;6 → 6 * *
%WW0114 * * * *
%WW0115 1 3;7 → 7 * *
%WW0116 * * * *
%WW0117 1 3;8 → 8 * *
%WW0118 * * * *
%WW0119 1 3;9 → 9 * *
%WW0120 * * * *
%WW0121 1 3;10 → 10 * *
%WW0122 * * * *
%WW0123 1 3;11 → 11 * *
%WW0124 * * * *
%WW0125 1 3;12 → 12 * *
%WW0126 * * * *
%WW0127 1 3;13 → 13 * *
%WW0128 * * * *
%WW0129 1 3;14 → 14 * *
%WW0130 * * * *
%WW0131 1 3;15 → 15 * *
%WW0132 * * * *
N040309J.ai

• 4-byte discrete inputs/outputs, 32 points (DI, DO)
Channel
%WW0101 2 3;0 → 0 64 3;R
%WW0102 * * * *
%WW0103 2 3;1 → 1 * *
%WW0104 * * * *
: :
%WW0127 2 3;13 → 13 * *
%WW0128 * * * *
%WW0129 2 3;14 → 14 * *
%WW0130 * * * *
%WW0131 2 → 15 * *
%WW0132 * * * *
%WW0133 2 3;16 (*1) * *
%WW0134 * * (*1) → 16 * * (*1)
%WW0135 2 3;17 * *
%WW0136 * * → 17 * *
%WW0137 2 3;18 * *
%WW0138 * * → 18 * *
%WW0139 2 3;19 * *
%WW0140 * * → 19 * *
%WW0141 2 3;20 * *
%WW0142 * * → 20 * *
%WW0143 2 3;21 * *
%WW0144 * * → 21 * *
%WW0145 2 3;22 * *
%WW0146 * * → 22 * *
%WW0147 2 3;23 * *
%WW0148 * * → 23 * *
%WW0149 2 3;24 * *
%WW0150 * * → 24 * *
%WW0151 2 3;25 * *
%WW0152 * * → 25 * *
%WW0153 2 3;26 * *
%WW0154 * * → 26 * *
%WW0155 2 3;27 * *
%WW0156 * * → 27 * *
%WW0157 2 3;28 * *
%WW0158 * * → 28 * *
%WW0159 2 3;29 * *
%WW0160 * * → 29 * *
%WW0161 2 3;30 * *
%WW0162 * * → 30 * *
%WW0163 2 3;31 * *
%WW0164 * * → 31 * *
*1: Specify %W (odd) for channel numbers from 0 to 15, and specify %W+1 (even) for channel numbers
from 16 to 31. N040310J.ai

n Specification of Diagnostic Information

If you wish to make applications perform special processing based on the diagnostic information,
set the diagnostic information from a slave device as the communication I/O definition to allow
referencing of diagnostic information.
TIP
Be aware of the following points when analyzing the diagnostic information.
• You must be familiar with specifications of PROFIBUS and devices.
The details of diagnostic information are specified in the PROFIBUS Specification and manuals of devices.
Check the contents in each manual when analyzing the diagnostic information.
• Simultaneity of diagnostic information is guaranteed up to 4 bytes.
In the communication I/O data area to which the diagnostic information is assigned, simultaneity of data is
guaranteed up to 4 bytes.
• If an error occurs and the device recovers to normal in an interval shorter than the scan period of FCS, the
error may not be detected.
l Example of Assigning Diagnostic Information

The 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 diagnostic information as 3 (6 bytes) and
%W area %WB bit number
01 08, 09 16 Bit number for each
7 0,7 0 byte of diagnostic data
%WW0101
%WW0102
%WW0103
N040311E.ai
Figure Example of Assigning Diagnostic Information
l Setting Items to Reference Diagnostic Information

To reference the diagnostic information, make the following I/O definitions in Communication I/O
Builder.
Table Setting Item in Communication I/O Builder
Setting item Setting Remarks
Station Node address of slave device
Device & Address DIAG
Data Type Discrete input (DI)
Reverse No

n Specification of Device Specific Diagnostic Information

By setting device specific diagnostic information in the communication I/O data area, it becomes
possible to reference the device specific diagnostic information.
l Example of Assigning Device Specific Diagnostic Information

Device specific diagnostic information is assigned sequentially, starting from the head byte and
occupying an area corresponding to the data size specified in Communication I/O Builder.
%W area bit numbers of %WB
01 08, 09 16 Bit number of each

7 0,7 0 byte of device specific
%WW0101 diagnostic information
%WW0102
%WW0103
N040312JE.ai
Figure Example of Assigning Device Specific Diagnostic Information
TIP
See the manual of applicable device for details of the contents of the device specific diagnostic information.
l Setting Items to Reference Device Specific Diagnostic Information

To reference the device specific diagnostic information, make the following I/O definitions in
Device & Address DIAG_DEV
Reverse No
TIP
ALP121 detects errors in the following cases.
• Failures of slave devices and communication errors such as configuration errors occur.
• Diagnostic information overflows and there is no device specific diagnostic information.
In the abnormal status, data in the communication I/O data area maintains the previous value.

n Specification of Module Diagnostic Information

By setting the slave device module diagnostic information in the communication I/O data area, it
becomes possible to reference the module diagnostic information.
l Example of Assigning Module Diagnostic Information

Module diagnostic information is assigned sequentially, starting from the head byte and
occupying an area corresponding to the data size specified in Communication I/O Builder, just
like device specific diagnostic information.
TIP
See the manual of applicable device for details of the module diagnostic information.
l Setting Items to Reference Module Diagnostic Information

To reference the module diagnostic information, make the following I/O definitions in
Device & Address DIAG_MOD
Reverse No
TIP
• Diagnostic information overflows and there is no module diagnostic information.

n Specification of Channel Diagnostic Information

By setting the slave device channel diagnostic information in the communication I/O data area, it
becomes possible to reference the channel diagnostic information.
l Example of Assigning Channel Diagnostic Information

Channel diagnostic information is assigned sequentially, starting from the head byte, by setting
the data size corresponding to the number of channels specified in Communication I/O Builder.
The actual size used for diagnostic information of one channel is three bytes, but an area of
four bytes is used for diagnostic information of one channel when the information is set in the
communication I/O data area. The value of the fourth byte is always 0.
%W area Bit nmbers of %WB
01 08, 09 16 Bit number of each

7 0,7 0 byte of channel
%WW0101 diagnostic information
%WW0102 First channel dlave
Data (third byte) 0 diagnostic informatiion
%WW0103
Second channel dlave
Data (third byte) 0 diagnostic informatiion
N040313E.ai
Figure Example of Assigning Channel Diagnostic Information
l Value of Each data

Values of channel diagnostic information are set as follows.
Table Values of Channel Diagnostic Information
Status
Data item Error is notified by channel ALP121 detected
Normal
diagnostic information errors
Value of first byte 0 0
Data received from a slave
Value of second byte 0 0
device is set as is.
Value of third byte 0 0xFF
Value of fourth byte 0 0 0
TIP
See the manual of applicable device for details of the contents of the channel diagnostic information.

l Setting Items to Reference Channel Diagnostic Information
To reference the channel diagnostic information, make the following I/O definitions in
Specify the size as (number of consecutive
channels to be referenced) x 2 (words).
Slot number, index, and channel number of
Device & Address
slave device. Ex: D3-1;1
Reverse No
Specify the [Device & Address] item of Communication I/O Builder in the following format.
Dmm-nn;xx
nn: Index
xx: Channel number
Example of entry in [Device & Address]:

In the case of slot number of module =3, channel number=1
D3;1
Table Details of [Device & Address] Format
Definition Description Example
Specify the slot number of a slave device module after the identifier “D.”
Slot number D3
Range: 1 to 60
Specify the index of a slave device module after “-.”
Index D3-1
Range: 1 to 60
Divide the part of module specification and the extension part that includes
Semicolon (;) D3-1;1
channel specification.
Specify the channel number of a module in the range 0 to 99.
Channel number D3-1;1
If this is omitted, the channel number is regarded as 0.
TIP
• Diagnostic information overflows and there is no module diagnostic information.

n Specification of Device Communication Status Information

It is possible to monitor the communication status by assigning the statuses of slave devices
defined in the PROFIBUS-DP configurator to communication I/O definitions.
By doing so, the status of a slave device can be used to update the Graphic view or output a
message for sequence control.
The response statuses of all slave devices can be assigned using a single communication I/O
definition.
l Correspondence with Element Numbers

When assigning communication statuses of slave devices to the communication I/O data area,
element numbers indicating device statuses can be specified in the following format.
%WBnnnn01
nnnn: Indicates the area number of communication I/O definition.
Table Details of Element Number (%WB) Format
Element number Description
%WBnnnn01 Not used
%WBnnnn02 Not used
%WBnnnn03 Status of slave device at node address 3
ּּּ ּּּ
%WBnnnn16 Status of slave device at node address 16
%WB(nnnn+1)01 Status of slave device at node address 17
ּּּ ּּּ
Status of slave device at node address X
%WBxxxxbb
X=(xxxx – nnnn) x 16 + bb
ּּּ ּּּ
%WB(nnnn+7)13 Status of slave device at node address 125
bb: Indicates the bit number in word.
Example slave device status display:

The status of slave device is shown as follows depending on the value of data item (PV).
Table Value of Data Item and Status of Slave Device
Value of %WBnnnnbb.PV Description
0 Abnormality of slave device
1 Normal status of slave device

l Communication Status Monitoring Setting Items
To monitor the communication statuses of slave devices, make the following I/O definitions in
Specify the size according to the
Size 1 to 8
number of slave devices.
Device & Address STATUS
Reverse Bits

4.3.10 Messages
The table below summarizes messages displayed when you save PROFIBUS
communication definitions, download PROFIBUS communication definitions, and check
before PROFIBUS communication definition downloading.
Table Messages Displayed

Message Display condition
There is no information on PROFIBUS communication When saving operation using the PROFIBUS-DP
definitions. Save information with the PROFIBUS-DP configurator has never been performed with the
configurator. applicable ALP121.
After saving information with the PROFIBUS-DP When PROFIBUS communication definitions have
configurator, PROFIBUS communication definitions never been saved nor downloaded after saving
have never been saved nor downloaded. information with the PROFIBUS-DP configurator.
No difference was detected. When no difference was detected.
The following difference was detected.
When a difference was detected.
<Display difference information>
When no difference was detected even though
Download is not performed because no difference was
PROFIBUS communication definitions were
detected.
downloaded
The following difference was detected. Do you want to
When PROFIBUS communication definitions were
download?
downloaded and a difference was detected.
<Display difference information>
When PROFIBUS communication definitions were
ALP121 re-initialization parameter has been changed.
downloaded and ALP121 re-initialization parameter
Do you want to perform initialized download?
was changed.


With the operation and monitoring function, it is possible to display the ALP121 status in
the FCS Status Display View, or execute IOM load and display IOM report from the FCS
Status Display view.

4.4.1 FCS Status Display View

In the FCS Status Display View, it is possible to display the status of ALP121, execute IOM
load, and display IOM report.
n ALP121 Status Display

The status of an ALP121 is displayed in the following color coding in the Node Status Display
dialog box of an HIS as follows.
• Single configuration and normal: Green
• Control side in module redundancy or network redundancy configuration and normal: Green
• Standby side in module redundancy or network redundancy configuration and normal:
Yellow, with a Δ symbol at the beginning of module name
• Status other than above: Red, with a X symbol at the beginning of module name
l Status Display of Slave Devices

The error status of a slave device connected to an ALP121 is displayed in the Node Status
Display dialog box.
If the following statuses are detected, “1C” in red characters is displayed in the Status Display
field of a slave device.
• Errors occurred in one or more defined slave devices
• An SS-COM error occurred
In case of the module redundancy configuration, “1C” can be displayed at the control side
ALP121 only. “1C” is not displayed at the standby side ALP121.
In case of the network redundancy configuration, “1C” can be displayed at each side of ALP121
independently according to the status of each network.
l Node Status Display Dialog Box

The Node Status Display dialog box is shown below.
I/O UNIT
Node No. : 1
Comment :
I/O (OFF) :
Δ
A A A S S P P
L L L B B S S
P P P 4 4 U U
1 1 1 0 0
2 2 2 1 1
1 1 1
1C
IOM Load Report Close

N040401E.ai
Figure Node Status Display Dialog Box where ALP121 is Defined

n IOM Load
In IOM load, the following information is loaded to ALP121.
• ALP121 program
• ALP121 property data
• Communication I/O definition data
• PROFIBUS communication definition data
Perform the following operation to execute IOM load.
In the Node Status Display dialog box, select one ALP121 module and click the [IOM Load]
button.
The above information is downloaded to the selected ALP121.
TIP
• IOM load is valid on the HIS whose standard builder function is enabled.
• If you execute IOM load on an operating ALP121, the PROFIBUS communication of the ALP121 stops and
IOM fail, IOP and OOP occur.
• If you execute IOM load on the ALP121 on the control side in redundant configuration, the control right is
transferred and ALP121 to which files are downloaded becomes the standby side.
n IOM Report
When an IOM report is created, the following information is displayed in a dialog box, output to a
printer, or saved to a file:
• Statistic information held by ALP121
• Revision information of ALP121 program loaded to ALP121
• Revision information of database loaded to ALP121
• Status information of slave device on PROFIBUS
• Diagnostic information of slave device on PROFIBUS
• Port information of PNO redundancy slave device in network redundancy configuration
Perform the following operation to create IOM report.
In the Node Status Display dialog box, select one ALP121 module and click the [Report] button.
The information of the selected ALP121 is displayed in a dialog box, output to a printer, or saved
to a file.


In PROFIBUS-DP communication, the following errors may occur.
• Power failure of FCS, CPU, and FIO node
• Path error between CPU and ALP121
• Disconnected PROFIBUS-DP communication
• Failure of slave device
This section explains how input actions of function blocks and output actions of slave
devices change if a power failure or path error occurs and the system is placed in unusual
status.
The figure below shows areas where PROFIBUS-DP communication errors may occur.
FCU
EE CC Power failure of FCS

I I I I I I I I CC PP PP
OOOOOOOO 4 4 4 4 S S
MMMMMMMM 0 0 0 0 U U Power failure of CPU
11
11
Path error
ESB Bus
I I AA I I I I SS P P
Power failure of FIO node
OO L L OO O O B B S S
MM P P MM M M U U
Failure of ALP121
FIO node
Disconnected PROFIBUS-DP
communication
PROFIBUS-DP Failure of slave device
PROFIBUS-DP
N030801J.ai
Figure Areas where Errors may Occur in PROFIBUS-DP Communication

4.5.1 Actions in the Event of Prolonged FCS Power Failure

The CPU and ALP121 stop operating in the event of a prolonged FCS power failure.
The output actions of slave devices during an FCS power failure vary depending on the
specification of fail-safe operation.
n Input Actions
Input data of function blocks becomes invalid until the ALP121 acquires input data from slave
n Output Actions
If no fail-safe operation is specified for a slave device, the slave device maintains the output value
before stopping, until the CPU restarts.
After the power supply to the FCS recovers, 0 is output from the slave device.
Stop Recovery
CPU operation
status
Function AUT MAN

block mode
Outputs 0
ALP121 output

output
Enters the fail-safe

status and outputs
the specified value
N040502E.ai
Figure Output Actions in the Event of Prolonged FCS Power Failure
Table Output Actions of Slave Device

At occurrence
At recovery
No specification of fail-safe operation Fail-safe operation specified
Maintain the output value before
Output the specified value 0
stopping
TIP
On fail-safe operations
If access from the master device is disrupted for a certain period of time, slave devices forcibly change their
outputs to the specified values.
The availability of fail-safe function and specified value depend on the specification of slave devices and can be
set using the PROFIBUS-DP configurator.

4.5.2 Actions in the Event of Momentary FCS Power Failure

The FCU and ALP121 stop operating in the event of a momentary FCS power failure.
The output actions of slave devices during an FCS power failure vary depending on the
specification of fail-safe operation.
If the momentary power failure period is longer than the fail-safe detection time of a slave
device, the slave device first outputs the specified fail-safe value.
n Input Actions
Input data of function blocks becomes invalid until the ALP121 acquires input data from slave
n Output Actions
before stopping, until the CPU restarts.
After the power supply to the FCS recovers, the slave device resumes outputting from the output
value before stopping.
Stop Recovery
CPU operation
status
Function AUT AUT

block mode
Outputs the
previous value
ALP121 output
Slave device
output
N040503E.ai
Figure Output Actions in the Event of Momentary FCS Power Failure

At occurrence
No specification of fail-safe At recovery
Fail-safe operation specified
operation
Maintain the output value before Resume outputting from the output
Output the specified value
stopping value before stopping

4.5.3 Actions in the Event of Prolonged CPU Power Failure

When a prolonged power failure occurs in the CPU or CPU STOP is executed from the
HIS’s FCU Operation Status Display View, the CPU stops. While the CPU is stopped,
PROFIBUS-DP communication between the ALP121 and slave devices is continued.
n Input Actions
Since PROFIBUS-DP communication between the ALP121 and slave devices continues even
while the CPU is stopped, the CPU acquires input data from slave devices immediately after it
restarts and the data is displayed as input data of function blocks.
n Output Actions under ALP121 Fallback Specification

The output actions taken by a slave device when the ALP121 fallback detection time elapses and
the ALP121 goes into fallback status can selected from the following options.
• All points maintain current value
TIP
The output actions of a slave device while ALP121 is in the fallback status are specified in the IOM Properties of
ALP121.
l All Points Maintain Current Value

The slave device maintains the output value before stopping. The slave device resumes
outputting from the output value before stopping when the CPU restarts.
Stop Recovery
CPU operation
status
Function AUT MAN

block mode
ALP121 output
Outputs the
Slave device previous value
output
N040504E.ai
Figure Output Actions in the Event of Prolonged CPU Power Failure (All Points Maintain Current Value)

At occurrence At recovery
Maintain the output value before stopping Resume outputting from the output value before stopping

l Reset All Outputs
The slave device outputs 0.
The slave device resumes outputting 0 when the CPU restarts.
Stop Recovery
CPU operation
status
Function AUT MAN

block mode
ALP121 output

output
N040505E.ai
Figure Output Actions in the Event of Prolonged CPU Power Failure (Reset All Outputs)

0 Resume outputting from 0
n Output Actions under ALP121 Non-fallback Specification

The slave device maintains the output value before stopping while the CPU is stopped.
The slave device resumes outputting from the output value before stopping when the CPU
restarts.

4.5.4 Actions in the Event of Momentary Power Failure of

CPU
While the CPU is stopped, PROFIBUS-DP communication between the ALP121 and slave
devices is continued.
n Input Actions
Since PROFIBUS-DP communication between the ALP121 and slave devices continues
regardless of operations of the CPU, the CPU acquires input data from slave devices
immediately after the power supply to the CPU recovers and the data is displayed as input data
of function blocks.


The slave device maintains the output value before stopping. The slave device resumes
outputting from the output value before stopping when the power supply to the CPU recovers.
l Reset All Outputs

The slave device outputs 0. The slave device resumes outputting from the output value before
stopping when the power supply to the CPU recovers.
0 Resume outputting from the output value before stopping

The slave device maintains the output value before stopping while the CPU is stopped.
The slave device resumes outputting from the output value before stopping when the power
supply to the CPU recovers.

4.5.5 Path Errors

The output actions taken in the event of a path error vary depending on whether or not
fallback operation of the ALP121 is enabled.
n Input Actions
The status of input data of a function block becomes BAD while the path error persists.
Once the FCU recovers from path error, the FCU immediately acquires input data from slave
devices and the data is displayed as input data of the function blocks.


While a path error persists, the slave device maintains the output value before stopping. The
slave device resumes outputting from the output value before stopping once it recovers from the
path error.
l Reset All Outputs

The slave device outputs 0.
The slave device resumes outputting from 0 once it recovers from the path error.
0 Resume outputting from 0

If a path error occurs, the slave device maintains the output value before stopping. The slave
device resumes outputting from the output value before stopping once it recovers from the path
error.

4.5.6 Actions in the Event of CPU Control-right Transfer

When a CPU control-right transfer occurs, I/O updating stops up to 1 to 2 scans.
I/O updating stops up to 1 to 2 scans Resume outputting from the output value at transfer

4.5.7 Actions in the Event of Prolonged FIO Node Power

Failure
If a power failure occurs in a FIO node for a prolonged period, the following operations
stop.
• Operation of ALP121
• PROFIBUS-DP communication between ALP121 and slave devices
The PROFIBUS-DP communication is resumed after the power supply to the FIO node
recovers.
n Input Actions
The status of input data of a function block becomes BAD during a prolonged power failure of a
FIO node.
Once the power supply to the FIO node recovers, the CPU acquires input data from slave
devices after ALP121 starts up, and the data is displayed as input data of function blocks.
n Output Actions
During a FIO node power failure, the output actions taken by a slave device follows the specified
fail-safe operation of the slave device.
before stopping, until the power supply to the FIO node recovers.
Once the power supply to the FIO node recovers, the slave device outputs 0.
Stop Recovery
FIO node
operation status
Momentary power
failure detection time
AUT MAN
Function
block mode
Outputs 0
ALP121 output

output Outputs 0
N040506E.ai
Figure Output Actions in the Event of Prolonged FIO Node Power Failure

At occurrence
At recovery
Maintain the output value before stopping Output the specified value 0

4.5.8 Actions in the Event of Momentary FIO Node Power

Failure
PROFIBUS-DP communication between the ALP121 and slave devices is stopped in the
event of a momentary power failure in a FIO node.
The output actions of slave devices vary depending on the specification of fail-safe
operation.
Once the power supply to the FIO node recovers, the previous value is output.
n Input Actions
The previous input data value of function blocks is maintained during a FIO node power failure if
the FIO node recovers from the failure within the momentary power failure detection time.
The previous input data value of function blocks is maintained until the ALP121 becomes capable
of acquiring input data from slave devices after the power supply to the FIO node recovers.
n Output Actions
During a FIO node power failure, the output actions taken by a slave device follows the specified
fail-safe operation of the slave device.
before stopping, until the power supply to the FIO node recovers.
Once the power supply to the FIO node recovers, the slave device resumes outputting from the
output value before stopping.
Stop Recovery
FIO node
operation status
Momentary power
failure detection time
AUT
Function
block mode Outputs the
previous value
ALP121 output
Slave device
output
N040507E.ai
Figure Output Actions in the Event of Momentary FIO Node Power Failure

At occurrence
operation

4.5.9 Actions in the Event of Failure/Maintenance of an

ALP121
PROFIBUS-DP communication between the ALP121 and slave devices is stopped during
ALP121 failure/maintenance.
n Input Actions
The status of input data of a function block becomes BAD during ALP121 failure/maintenance.
n Output Actions
During ALP121 failure/maintenance, the output actions taken by a slave device follows the
specified fail-safe operation of the slave device.
before stopping, until the ALP121 recovers.
Once the ALP121 recovers, the slave device outputs 0.
Stop Recovery
ALP121
operation status
Function AUT MAN

block mode
Outputs 0
ALP121 output
output
N040508E.ai
Figure Actions in the Event of Failure/Maintenance of an ALP121

At occurrence
At recovery

4.5.10 Actions in the Event of ALP121 Control-right Transfer

When the control-right transfer of dual-redundant ALP121 modules occurs, the output
actions are taken for the ALP121 that becomes the control side after the transfer.
n Input Actions
When the control-right transfer occurs, the FCU acquires input data from the ALP121 that
becomes the control side after the transfer and the data is displayed as input data of function
blocks.
n Output Actions
When the control-right transfer occurs, the slave device resumes outputting the output value
before stopping.

4.5.11 Actions in the Event of Disconnected PROFIBUS-DP

Communication
If slave devices stop responding due to disconnection of PROFIBUS-DP communication,
the ALP121 notifies the communication error message to the CPU.
n Input Actions
The status of input data of a function block becomes BAD while the PROFIBUS-DP
communication is disconnected.
After the PROFIBUS-DP communication recovers, the CPU acquires input data from the ALP121
and the data is displayed as input from function blocks.
n Output Actions
While the PROFIBUS communication is disconnected, the output actions taken by a slave device
follow the specified fail-safe operation of the slave device.
before stopping, until the PROFIBUS-DP communication recovers.
Once the PROFIBUS-DP communication recovers, the slave device resumes outputting from the
output value before stopping.
Stop Recovery
PROFIBUS
communication
status
Function AUT MAN

block mode Notifies about a
communication error
ALP121 output

Slave device
output
Outputs the
previous value
N040509E.ai
Figure Output Actions in the Event of Disconnected PROFIBUS-DP Communication
TIP
The SS-COM Error CA91 system alarm is issued when the ALP121 detects no response.

At occurrence
operation
Maintain the output value Resume outputting from the output value
before stopping before stopping

4.5.12 Actions in the Event of Slave Device

Failure/Maintenance
During the slave device failure/maintenance, the CPU detects a PROFIBUS-DP
communication error or slave device channel error.
Once the slave device recovers from the error status, the CPU detects recovery of the
PROFIBUS-DP communication or the slave device channel to normal.
n Input Actions
The status of input data of a function block becomes BAD during the slave device failure.
Once the slave device recovers from the failure, the CPU acquires input data from the ALP121
and the data is displayed as input data from function blocks.
n Output Actions
While a slave device is stopped, the output from the ALP121 to the slave device is handled as a
communication error or channel error.
Once the slave device operation recovers, the slave device resumes outputting from the output
value before stopping.
Stop Recovery
Slave device
operation status
Function AUT MAN

block mode Notifies about a
communication error
ALP121 output
Outputs the
previous value
Slave device
output
N040510E.ai
Figure Output Actions in the Event of Slave Device Operation Stop

Communication error or channel error Resume outputting from the output value before stopping

<4.6 System Operations during Download> 4-86
4.6 System Operations during Download

There are the following three types of download operations:
• Offline download to an FCS
• IOM download to an ALP121
• Download at ALP121 definition change

4.6.1 Operation during Offline Download to an FCS

The downloading of ALP121 programs is executed during offline download to an FCS.
The system operation after completion of the offline download to the FCS varies
depending on the system status before the offline download.
The table below summarizes operation in each system status.
Table Operation during Offline Download to an FCS

System status Operation after offline download
When using a completely new ALP121 module
When an ALP121 is replaced before offline download Input becomes IOP.
Output becomes OOP. (*1)
When there are changes to PROFIBUS
communication definitions (*3)
When there are no changes to PROFIBUS
Reads new inputs and resets outputs. (*2)
communication definitions
*1: The ALP111 reads new inputs and resets outputs for those slave devices connected to the ALP121 prior to replacement, as well
as the slave devices connected to a new ALP121 after replacement that meet all of the following conditions:
. • Identification Number (model code) agreement
*2: Resetting outputs means outputting 0 to the analog output and digital output.
*3: This may occur under conditions where there are discrepancies between the system data and the PROFIBUS communication
definition data downloaded to the ALP121.
IMPORTANT
PROFIBUS communication definition data is not downloaded in offline download to an FCS.
Depending on the ALP121 status, PROFIBUS communication definition data may become
inconsistent. If this happens, execute IOM download again to ALP121.
Output actions of slave devices are different between during offline download to an FCS and
after completion of the download.
During offline download to an FCS, the output actions taken by a slave device follows the
specified fail-safe operation of the slave device. If no fail-safe operation is specified for a slave
device, the slave device maintains the output value before stopping, until the offline download to
an FCS is completed.
When the offline download to an FCS is completed, the slave device outputs 0.
During offline download to an FCS
After completion of offline
Fail-safe operation download
No specification of fail-safe operation
specified

4.6.2 Operation during ALP121 IOM Download

If IOM download is executed to an operating ALP121, ALP121 stops PROFIBUS-DP
communication and an IOM fail, IOP, and OOP occur.
If IOM download is executed on the redundant ALP121 on the control side, the control-
right is transferred.
n IOM Download
Execute IOM download when ALP121 is in the following statuses.
• When using a completely new ALP121 module
• When an ALP121 is replaced before offline download to an FCS
When you execute IOM download, the system operation changes as follows.
l Input Actions
When the IOM download is completed, the input data from slave devices is acquired.
l Output Actions
The output actions taken by a slave device are different between during IOM download of
ALP121 and after completion of the download.
When the IOM download is completed, the slave device outputs 0.
During IOM download After completion of IOM download
Maintain the output value before stopping 0

4.6.3 System Operation during ALP121 Definition Change

Download
If any of the PROFIBUS communication definitions for ALP121 is changed, the system
operation changes.
• Download of ALP121 program
• Download of IOM properties whose dual-redundant specification is changed
• Download of IOM properties whose settings other than dual-redundant specification
are changed
• Download of changed communication I/O definitions
• Download of PROFIBUS communication definitions

n Downloading ALP121 program and Downloading IOM Properties with

Changed Dual-redundant Specification
PROFIBUS-DP communication between the ALP121 and slave devices stops temporarily.
l Input Actions
While the change in PROFIBUS communication definitions for ALP121 is being changed, the
previous values are maintained for both input data and statues of function blocks.
l Output Actions
The output actions taken by a slave device when the ALP121 fallback detection time elapses
and the ALP121 goes into fallback status can selected from “All points maintain current value” or
“Reset all outputs.”
• ”All points maintain current value”
Once changing of PROFIBUS communication definitions is completed, the slave
device resumes outputting from the previous value before changing the PROFIBUS
ALP121
operation status
Function AUT MAN

block mode(*1)
ALP121 output
Slave device
output
Outputs the
previous value
*1: It is possible to prevent MAN fall-back via the builder specification.
N040511E.ai
Figure Output Operation during Change in PROFIBUS Communication Definitions for ALP121 (when All
Points Maintain Current Value is Specified)

During change in PROFIBUS communication definitions After completion of change in
No specification of fail-safe PROFIBUS communication
Fail-safe operation specified definitions
operation
TIP
PROFIBUS-DP communication stops while change in PROFIBUS communication definitions is performed. In
order to maintain the output values from slave devices, specify “Maintain output value” or “Do not detect fail-safe”
as the fail-safe operation on the slave device side.

• “Reset all outputs”
When the change in PROFIBUS communication definitions is completed, the slave device
outputs 0.
When the following information is downloaded, the output actions taken by a slave device vary
between during change in PROFIBUS communication definitions and after completion of change
in PROFIBUS communication definitions.
• ALP121 program
• IOM properties whose dual-redundant specification is changed
The output actions of slave device are summarized below.
operation
stopping

n Downloading IOM Properties Whose Settings other than Dual-

Redundant Specification is Changed/Communication I/O Definitions
ALP121 is restarted. However, the output actions of ALP121 continue.
l Input Actions
PROFIBUS-DP communication between the ALP121 and slave devices continues regardless of
operations of the change in PROFIBUS communication definitions for ALP121. Once the change
in PROFIBUS communication definitions is completed, the CPU immediately acquires the input
data from slave devices and the data is displayed as input data of function blocks.
l Output Actions
The output of ALP121 is maintained during change in PROFIBUS communication definitions.
The output continues after the completion of change in PROFIBUS communication definitions.
Note that in the case of newly added or changed ALP121 output definitions, the initial value of 0
is output.
ALP121
operation status
Function AUT MAN

block mode(*1)
ALP121 output
Slave device
output
*1: It is possible to prevent MAN fall-back via the builder specification.

N040512E.ai
Figure Output Actions during change in PROFIBUS communication definitions of ALP121
When the following information is downloaded, the output actions taken by a slave device vary
between during change in PROFIBUS communication definitions and after completion of change
in PROFIBUS communication definitions.
• IOM properties whose settings other than dual-redundant specification are changed
• Changed communication I/O definitions
The output actions of slave device are summarized below.
After completion of change in PROFIBUS communication
During change in PROFIBUS definitions
communication definitions
Changed definition New definition
0

n Deleting ALP121 Definitions

If you delete ALP121 definitions, all function blocks linked to the I/O data of ALP121 become IOP
or OOP.
If fallback operation is not specified, the output status before the download is maintained.
If fallback operation is specified, ALP121 goes into fallback status.
n Downloading of PROFIBUS Communication Definitions when Items

not Causing ALP121 Re-initialization are Changed
PROFIBUS-DP communication between the ALP121 and slave devices whose definitions are
not changed continues during loading of PROFIBUS communication definitions and the inputs/
outputs also continue.
TIP
If the target device of PROFIBUS communication is a remote I/O, I/O configuration and I/O data assignment of
each remote I/O module cannot be changed in online maintenance.
If only one parameter of one remote I/O module is changed, the entire remote I/O is re-initialized.
l Input Actions of Devices not Target of Change

The input actions continue during changes are made.
l Output Actions of Devices no Target of Change

The output actions continue during changes are made.
ALP121
operation status
Function AUT
block mode
ALP121 output
Slave device
output
N040513E.ai
Figure Output Actions when Items not Causing Re-initialization are Changed (Device not Target of
Change)

During change in PROFIBUS communication After completion of change in PROFIBUS
definitions communication definitions
Continue outputting Continue outputting

l Input Actions of Target Device of Change
During loading of PROFIBUS communication definitions, the previous values are maintained for
both input value and status. When the loading is completed, the input values are read with the
new definitions.
l Output Actions of Target Device of Change

During loading of PROFIBUS communication definitions, ALP121 outputs are maintained.
However, the output value becomes 0 for approximately 1 second temporarily at the timing of
reset.
ALP121
operation status
Function AUT MAN

block mode
ALP121 output

until middle of loading
Slave device
output
Outputs 0 temporarily
N040514E.ai
Figure Output Actions when Items not Causing Re-initialization are Changed (Target Device of Change)
TIP
If there are multiple target devices, the output values of individual devices may become 0 at the same time.

During change in PROFIBUS communication After completion of change in PROFIBUS
definitions communication definitions
Continue outputting (reset 0 for one second Resume outputting from the output value before
temporarily) stopping
l Downloading PROFIBUS Communication Definitions to ALP121 in Dual-

redundant Configuration
When downloading PROFIBUS communication definitions to ALP121 in dual-redundant
configuration, the definitions are downloaded to ALP121 on the control side first and then to
ALP121 on the standby side.
TIP
The control right of PNO redundancy slave devices is transferred by the control-right Transfer of ALP121 on
the network redundancy configuration. If the control right is transferred the Primary to the Backup on PNO
redundancy slave devices, the restart of the slave devices oneself may occur. When it completed the download
of PROFIBUS Communication definitions, the slave device on the Backup side is in Fail status on ALP on the
standby side.
It detects the Subsystem communication error(Error code: 0xCA91)/Subsystem communication recovery. But the
slave devices are not broken.

n Downloading PROFIBUS Communication Definitions when Items

Causing ALP121 Re-initialization are Changed
If you change the Bus Parameter and Master Settings, which are common to the entire network,
ALP121 restarts and the change of target slave devices cause the re-initialization.
l Input Actions
During loading of PROFIBUS communication definitions, the previous values are maintained for
both input value and status.
l Output Actions
During change in PROFIBUS communication definitions, the output actions taken by a slave
device follows the specified fail-safe operation of the slave device.
before stopping, until the change in PROFIBUS communication definitions is completed.
The output actions taken by a slave device when the ALP121 goes into fallback status can be
selected from “All points maintain current value” or “Reset all outputs.”
• “All points maintain current value”
Once loading of PROFIBUS communication definitions is completed, the slave device
resumes outputting from the previous value before starting the change in PROFIBUS
ALP121
operation status
Function AUT MAN

block mode
ALP121 output
Outputs the
Slave device output previous value
(no fallback specification,
continue output at fallback)
Outputs 0 temporarily
Outputs the
previous value
Slave device output
(output 0 at fallback)
Occurrence of fallback
N040515E.ai
Figure Output Actions when Items Causing Re-initialization are Changed

During change in PROFIBUS communication definitions
After completion of change in
No specification of fail-safe PROFIBUS communication definitions
operation
stopping. Resume outputting from the output value
However, output 0 for one before stopping
second temporarily.

• “Reset all outputs”
During change in PROFIBUS communication definitions, the output actions taken by a slave
device follows the specified fail-safe operation of the slave device.
If no fail-safe operation is specified for a slave device, the slave device maintains the
output value before stopping, until the change in PROFIBUS communication definitions is
completed.
The slave device outputs 0 when the change in PROFIBUS communication definitions is
completed.
operation
stopping
n Actions Taken when Errors are Detected during Downloading of

PROFIBUS Communication Definitions
The following actions are taken if an error is detected during downloading of PROFIBUS
l If ALP121 Card is Removed during IOM Load

Downloading of PROFIBUS communication definitions is not normally completed. If you insert
ALP121 again, an IOM fail of ALP121 occurs.
Execute IOM load and download PROFIBUS communication definitions again.
l If an Error Occurs during Downloading of PROFIBUS Communication

Definitions to Control-side ALP121 in Dual-redundant Configuration
Download PROFIBUS communication definitions again.
l If an Error Occurs during Downloading of PROFIBUS Communication

Definitions to Standby-side ALP121 in Dual-redundant Configuration
An IOM fail occurs if PROFIBUS communication definitions do not agree between the control
side and standby side.
Execute IOM load to the ALP121 on the standby side.

n IOP and OOP Suppression during Online Maintenance

▼ Suppress OOP alarms during online maintenance of ALP121 and dual-redundant ALP111
It is possible to specify whether or not to suppress IOP and OOP during online maintenance in
the FCS Properties.
l IOP Suppression
To suppress IOP during online maintenance, clear the “IOP Occurs in Connected Blocks” check
box under the Operation at IOM Change section in the “Constant” tab of the FCS Properties
sheet.
l OOP Suppression
OOP is generated during online maintenance if the “Suppress OOP alarms during online
maintenance of ALP121 and dual-redundant ALP111” check box in the “Constant 3” tab of the
FCS Properties sheet is cleared.
The table below shows relationship between changes of definitions related to ALP121 and IOP/
OOP suppression.
Table Relationship between Changes of Definitions Related to ALP121 and IOP/OOP Suppression
Alarm Alarm generation during ALP121 definition change

Definition changed
type Do not suppress IOP and OOP Suppress IOP and OOP
IOP Generated No (*1)
IOM properties
OOP Generated No (*1)
IOP Generated No (*1)
Communication I/O definitions
OOP Generated No (*1)
Target device of change:
Target device of change: No
IOP Generated
PROFIBUS definitions (when Device not target of change: No
Device not target of change: No
items not causing ALP121 re-
initialization are changed) Target device of change:
Target device of change: No
OOP Generated
PROFIBUS definitions (when IOP Generated (*2) No
items causing ALP121 re-
initialization are changed) OOP Generated (*2) No
*1: In loading caused by changes to IOM properties performed after upgrading the ALP121 program revision, IOP and OOP alarms
are generated regardless of specification of IOP/OOP suppression because the ALP121 program is loaded to ALP121.
*2: When it is module redundancy or network redundancy, the load of PROFIBUS communication definitions(when items causing
ALP121 re-initialization are changed) is performed the load of ALP121 information and the load of PROFIBUS communication
definitions in order.
The data status of the function block of the connection may become NR each load temporarily.

<4.7 Messages> 4-98
4.7 Messages
In PROFIBUS-DP communication, the following messages can be displayed for ALP121
modules and slave devices.

<4.7 Messages> 4-99

The table below summarizes system alarm messages related to ALP121.
Table System Alarm Messages Related to ALP121

Number Message name Message
0081 IOM error (for ADM/AMM, FIO related) STNss IOM Fail FIO k NODE mm SLOT nn
0082 IOM recovery (for ADM/AMM, FIO related) STNss IOM Recover FIO k NODE mm SLOT nn
IOM database error (for ADM/AMM, FIO
0083 STNss IOM Configuration FIO k NODE mm SLOT nn
related)
STNss SS-COM Error FIO k NODE mm SLOT nn
0089 Subsystem communication error
STN zzz CODE=####
STNss SS-COM Recover FIO k NODE mm SLOT nn
0090 Subsystem communication recovery
STN zzz
IOM service notification (for ADM/AMM, FIO
0459 STNss IOM In Service k NODE mm SLOT nn
related)
IOM out of service notification (for ADM/
0460 STNss IOM Out Service k NODE mm SLOT nn
AMM, FIO related)
STNss PB FIO k NODE mm SLOT nn Slave Device
4056 Transfer of slave device control-right Switch Over From Backup to Primary STN zzz ID
0xXXXX
STNss: Station name, k: bus system number, mm: Node number, nn: Slot Number
zzz: Node address of slave device, ####: Error code
XXXX: Ident Number
TIP
No further Subsystem communication error messages will be notified on the same slave devices, even if another
error occurs due to a different cause while a Subsystem communication error in occurring on a slave device.

<4.7 Messages> 4-100
n Detail Error Codes for Subsystem Communication Errors

When communication errors occur on a slave device, error codes are displayed on system alarm
messages.
l Definition Errors
Definition errors occur when the settings for the communication I/O definitions are invalid.
The table below shows error codes and description of definition errors.
Error Action to take after the
Description
code occurrence of error
CAB2 Invalid Device & Address, cannot be interpreted
CAB3 Invalid Device & Address, illegal character string detected
CAB5 Invalid Device & Address, slot number out of range
Invalid Device & Address, entry data other than a numerical value
CAB6
CAB7 Invalid Device & Address, index value out of range
Do not perform communication
Invalid Device & Address, index value exceeding the specified
CAB8 to the slave devices causing the
digits
communication error. Check the
CAB9 Invalid Device & Address, invalid delimiter character definitions in Communication I/O
Builder.
Corresponding device (module or channel) not specified in
CABA
CABB Illegal data type, input designated for output data
CABC Illegal data type, output designated for input data
Invalid Device & Address, entry data for slot number is not a
CABD
numerical value
CABE Invalid Device & Address, illegal character string detected
Invalid Device & Address, illegal character string detected
CABF
(extension symbol)

l Communication Errors
Communication errors occur when there is an error in the communication between slave devices
and ALP121 or a slave device fails.
The table below shows error codes and description of definition errors.
Table Communication Errors
Error Action to take after the occurrence
Description
code of error
Execute PROFIBUS communication
C58A (*1) PROFIBUS definitions do not exist in the ALP121
definition download.
Check the connection of the
C58B (*1) Communication error on the ALP121 standby side
connector.
Check definition information with
Check definition information with
CA92 Configuration error
PROFIBUS –DP configurator.
CA93 Slave device module error Check the slave device.
CA94 Slave device channel error Check the slave device.
CA95 Overflow of slave diagnostic information Check the slave device.
*1: In case these errors occur, the slave station number of STN zzz is always set to 255.


The PROFIBUS diagnostic information and result of self-diagnosis of ALP121 are
displayed as Fieldbus messages in the Historical Message window or Message Monitor
window.
If an error occurs in a slave device, not only a Fieldbus message but also a system alarm
message is displayed.
TIP
• An error code is also displayed in messages caused by device specific errors. See the manual and GSD file
of each device for the description of error codes.
• Each diagnostic information item contains information of multiple errors. Therefore, several different
messages may be displayed from each diagnostic information item.
n List of Messages
Fieldbus messages are divided into the following five categories:
• Messages for each module in a slave device
• Messages for each channel in a slave device
• ALP121 self-diagnostic messages
IMPORTANT
• The ALP121 manages the recovery status of errors ALP121 detected. Therefore, if you
restart ALP121 after a message related to an error it has detected is displayed, a normal
recovery message will not be displayed even when the ALP121 recovers from the error.
• If an error that generates more data than the communication frame size of the diagnostic
information occurs, the part of the error data exceeding the communication frame may
not be notified as part of the message. The communication frame size of the diagnostic
information depends on the slave device.

l Slave Device Common Messages
Slave device common messages are displayed when errors defined in the PROFIBUS
specifications occur. These messages are common to all slave devices.
These messages are displayed for both errors detected by ALP121 and errors detected by slave
devices.
Error
detected by
Locked by another STNss PB FIO k NODE mm SLOT nn Station Alarm STN
3283 ALP121
master device zzz ID 0xXXXX Master_Lock(Master STN yyy)
The error above returned STNss PB FIO k NODE mm SLOT nn Station Recover
3284 ALP121
to normal STN zzz ID 0xXXXX Master_Lock
STNss PB FIO k NODE mm SLOT nn Station Alarm STN
3285 Parameter setting failed Slave device
zzz ID 0xXXXX Param_Fault
3286 Slave device
to normal STN zzz ID 0xXXXX Param_Fault
Received an illegal frame STNss PB FIO k NODE mm SLOT nn Station Alarm STN
3287 ALP121
from a slave device zzz ID 0xXXXX Invalid_Slave_Response
3288 ALP121
to normal STN zzz ID 0xXXXX Invalid_Slave_Response
Received a request for STNss PB FIO k NODE mm SLOT nn Station Alarm STN
3289 Slave device
an unsupported function zzz ID 0xXXXX Not_Supported
3290 Slave device
to normal STN zzz ID 0xXXXX Not_Supported
3291 Configuration error Slave device
zzz ID 0xXXXX Cfg_Fault
3292 Slave device
to normal STN zzz ID 0xXXXX Cfg_Fault
3293 Cannot transmit data Slave device
zzz ID 0xXXXX Station_Not_Ready
3294 Slave device
to normal STN zzz ID 0xXXXX Station_Not_Ready
Slave device not present
3295 on the communication ALP121
zzz ID 0xXXXX Station_ Non _Existent
line
3296 ALP121
to normal STN zzz ID 0xXXXX Station_Non_Existent
Slave device is
3297 missing from the cyclic ALP121
zzz ID 0xXXXX Deactivated
transmission list
3298 ALP121
to normal STN zzz ID 0xXXXX Deactivated
Setting parameters or STNss PB FIO k NODE mm SLOT nn Station Alarm STN
3299 Slave device
checking configuration zzz ID 0xXXXX Param_Req
3300 Slave device
to normal STN zzz ID 0xXXXX Param_Req
STNss PB FIO k NODE mm SLOT nn Station Alarm STN ALP121
zzz ID 0xXXXX Ext_Diag_Overflow Slave device
overflowed
The error above returned STNss PB FIO k NODE mm SLOT nn Station Recover ALP121
3302
to normal STN zzz ID 0xXXXX Ext_Diag_Overflow Slave device
zzz: Node address of slave device
yyy: Node address of the master device locking the slave devices

Messages relating to slave devices are displayed using the top 3 bytes of the slave diagnostic
information defined by the PROFIBUS specifications. However, no message is displayed if the
following bits are turned on.
Table Slave Diagnostic Bit Information
Bit name Specification Operation
Sync_Mode Enable/disable Sync function
These bits indicate configuration status. No message
Freeze_Mode Enable/disable Freeze function
is displayed because they are not error data.
WD_On_Mode Enable/disable Watch dog function
This bit indicates whether slave device specific
diagnostic information, module diagnostic
Whether or not slave diagnostic
Ext_Diag information or channel diagnostic information is
information contains expansion data
available or not. No message is displayed because it
is not error data.
Whether or not it is necessary to read This bit indicates whether or not slave diagnostic
Stat_Diag diagnostic information from slave information must be read from slave devices. No
device message is displayed because it is not error data.

l Slave Device Specific Messages
Slave device specific messages indicate errors defined by the device vendor.
These messages display the slave diagnostic information’s device related portion as error codes.
Number Message name Message Error detected by:
Slave device error STNss PB FIO k NODE mm SLOT nn Device Related
3303 V0 slave device
occurred Alarm STN zzz ID 0xXXXX CODE=########
The error above STNss PB FIO k NODE mm SLOT nn Device Related
3304 V0 slave device
returned to normal Recover STN zzz ID 0xXXXX
STNss PB FIO k NODE mm SLOT nn Device Related
Diagnostic Alarm
3305 Diagnostic Alarm STN zzz ID 0xXXXX MODULE yy V1 slave device
received
Specifier 0xVV CODE= ########
Process Alarm
3307 Process Alarm STN zzz ID 0xXXXX MODULE yy V1 slave device
received
3309 Pull Alarm received Pull Alarm STN zzz ID 0xXXXX MODULE yy Specifier V1 slave device
0xVV CODE= ########
3311 Plug Alarm received Plug Alarm STN zzz ID 0xXXXX MODULE yy Specifier V1 slave device
0xVV CODE= ########
Status Alarm
3313 Status Alarm STN zzz ID 0xXXXX MODULE yy V1 slave device
received
Update Alarm
3315 Update Alarm STN zzz ID 0xXXXX MODULE yy V1 slave device
received
Slave device STNss PB FIO k NODE mm SLOT nn Device Related
3317 specific alarm Manufacturer-specific Alarm 0xUU STN zzz ID 0xXXXX V1 slave device
received MODULE yy Specifier 0xVV CODE= ########
Slave device status
3319 Status Message STN zzz ID 0xXXXX MODULE yy V1 slave device
message received
STNss PB FIO k NODE mm SLOT nn Device
Slave device
Related Manufacturer-specific Status 0xUU STN
3321 specific status V1 slave device
zzz ID 0xXXXX MODULE yy Specifier 0xVV CODE=
message received
########
Slave device STNss PB FIO k NODE mm SLOT nn Slave Device
PNO redundancy
3356 control-right transfer Switch Over From Backup to Primary STN zzz ID
slave device
occurred 0xXXXX
yy: Module number, VV: Specifier number (Hexadecimal: Displayed with “0x” added at the top)
UU Alarm/Status Type (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))

l Messages for Each Module in a Slave Device
These messages are displayed when errors occur in modules of slave devices.
STNss PB FIO k NODE mm SLOT nn Module Alarm
STN zzz ID 0xXXXX MODULE yy
STNss PB FIO k NODE mm SLOT nn Module
3325 Module error occurred (*1)
Invalid Alarm STN zzz ID 0xXXXX MODULE yy
3327 Module irregularity occurred (*1)
Wrong Alarm STN zzz ID 0xXXXX MODULE yy
STNss PB FIO k NODE mm SLOT nn No Module
3329 Module not mounted (*1)
Alarm STN zzz ID 0xXXXX MODULE yy
3330 The error above returned to normal
Recover STN zzz ID 0xXXXX MODULE yy
yy: Slot number (decimal)
*1: These messages are displayed only to slave devices that send MODULE_STATUS (diagnostic information indicating module
status). They are not displayed for all slave devices.
SEE
ALSO For the setting of the head number of slot number of modules, see the following:
“n IOM Properties” of 4.3.3, “System View”

l Messages for Each Channel in a Module
These messages are displayed when errors occur in channels of modules.
3331 short circuit
0xXXXX MODULE yy CHANNEL ww short circuit
3333 undervoltage
0xXXXX MODULE yy CHANNEL ww undervoltage
3335 overvoltage
0xXXXX MODULE yy CHANNEL ww 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 Errors other than above
0xXXXX MODULE yy CHANNEL ww Error Type=vvvv
Normal recoveries other than STNss PB FIO k NODE mm SLOT nn Channel Recover STN zzz
3350
above ID 0xXXXX MODULE yy CHANNEL ww
yy: Module slot number (decimal), ww: Channel number (decimal)
vvvv: Error type (decimal)
SEE
ALSO For the setting of the head number of channels, see the following:
“n IOM Properties” of 4.3.3, “System View”
l ALP121 Self-Diagnostic Messages

These messages are displayed when errors occur at self-diagnosis performed by ALP121.
3351 PROFIBUS communication stop STNss PB FIO k NODE mm SLOT nn Communication Stop
STNss PB FIO k NODE mm SLOT nn Communication
3352 PROFIBUS communication recover
Recover
TIP
• If ALP121 self-diagnostic messages occur, IOM fails also occur at the same time.
• If ALP121 self-diagnostic messages occur, ALP121 may be faulty. Replace the ALP121 card.

Blank Page
Ind-1
CENTUM VP
Communication with PROFIBUS Systems
IM 33K03P10-50E 2nd Edition
INDEX
A F
Actions during Download FCS Status Display View
ACP71.........................................................2-52 ACP71.........................................................2-41
ALP111........................................................3-76 ALP111........................................................3-60
Actions during Online Maintenance ALP121........................................................4-70
ACP71.........................................................2-53 Fieldbus Messages
ALP111........................................................3-79 ACP71.........................................................2-61
Actions in the Event of Faults ALP111........................................................3-86
ACP71.........................................................2-47 ALP121......................................................4-102
ALP111........................................................3-65 Function Block Detail Builder...............................4-47
Advanced Engineering
Specification of Channel Diagnostic H
Information................................................4-64
Hardware Environment
Specification of Device Communication
ACP71........................................................... 2-4
Status Information.....................................4-66
ALP111.......................................................... 3-5
Specification of Device Specific Diagnostic
Information................................................4-62 ALP121.......................................................... 4-5
Specification of Diagnostic Information.......4-61
Specification of I/O Data..............................4-50 I
Specification of Module Diagnostic I/O Data
Information................................................4-63 ACP71........................................................... 2-7
Assigning and Referencing a Slave Device.........2-16 ALP111.......................................................... 3-8
ALP121........................................................4-14
C
Communication I/O Definition Support Tool........4-44 M
Messages
D ACP71.........................................................2-58
Device Communication Status ALP111........................................................3-83
ALP111........................................................3-34 ALP121........................................................4-98
Downloading PROFIBUS Communication Monitoring and Diagnosing Devices....................3-17
Definitions.................................................4-24, 4-49 Monitoring Slave Devices....................................2-15
E O
Engineering Operations in Communication I/O Builder
ACP71.........................................................2-22 ALP111........................................................3-47
ALP111........................................................3-35 Operations in Function Block Detail Builder
ACP71.........................................................2-40
ALP111........................................................3-59
Operations in System View
ACP71.........................................................2-31
ALP111........................................................3-43

Ind-2
Operations with the Communication I/O Builder U
ACP71.........................................................2-35 Unusual Operations.............................................4-72
Operations with the PROFIBUS-DP Configurator
ACP71.........................................................2-28
ALP111........................................................3-41
P
PROFIBUS............................................................. 1-1
PROFIBUS-DP...................................................... 1-2
ACP71........................................................... 2-1
ALP111.......................................................... 3-1
ALP121.......................................................... 4-1
PROFIBUS-DP Communication Module............... 2-5
PROFIBUS-DP Communication Module
(ACP71)............................................................... 2-3
(ALP111).............................................................. 3-3
(ALP121).......................................................4-4, 4-8
PROFIBUS-DP Configurator
ACP71........................................................... 2-3
ALP111.......................................................... 3-3
ALP121...............................................4-23, 4-42
PROFIBUS Communication Definition
Check before Downloading......................4-23, 4-48
PROFIBUS Definition Data
ACP71.........................................................2-24
ALP111........................................................3-37
S
Saving PROFIBUS Communication
Definitions.................................................4-24, 4-49
Slave Diagnostic Information
Assigning and Referencing.........................3-26
Channel.......................................................3-31
Device Specific............................................3-28
Module.........................................................3-30
Overview......................................................3-18
Slave Diagnostic Information......................2-18
Start Operation
ACP71.........................................................2-44
System Alarm Messages
ACP71.........................................................2-59
ALP111........................................................3-84
ALP121........................................................4-99
System Builders...................................................4-22
System Operation during ALP121 Definition
Change Download.............................................4-89
System Operations during Download..................4-86
System View........................................................4-38

Rev-1
Revision Information
l Title : CENTUM VP Communication with PROFIBUS Systems
l Manual No. : IM 33K03P10-50E
Jun. 2012/2nd Edition/R5.02.00 or later*

* : Denotes the release number of the software corresponding to the contents of this user's manual. The
revised contents are valid until the next edition is issued.
Chapter 4 Add the information about ALP121.
Sep. 2011/1st Edition/R5.01 or later

Newly published
n For Questions and More Information

If you have any questions, you can send an E-mail to the following address.
E-mail: support-CENTUM@csv.yokogawa.co.jp
n Written by Yokogawa Electric Corporation
n Published by Yokogawa Electric Corporation
2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN
n Printed by KOHOKU PUBLISHING & PRINTING INC.

Blank Page

Munication With Profibus Systems

Uploaded by

Document Information

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

Munication With Profibus Systems

Uploaded by

Copyright:

Available Formats

Communication with

Chapter 1 Overview of PROFIBUS

CENTUM VP Document Map

Field Control Stations Function Blocks Function Blocks Function Blocks

Function Blocks Human Interface Human Interface Engineering

SEBOL Communication with Communication with Communication

Optional Functions Communication with Compliance with Generic Subsystem

System Integration Unified Gateway Engineering Test

Operation and Monitoring

HIS Operation Operating Messages

Communication Devices Migrated-FCS(FIO)

IM 33K03P10-50E 1st Edition : Sep.22,2011-00

Indicates that the main switch is ON.

Indicates that the main switch is OFF.

IM 33K03P10-50E 1st Edition : Sep.22,2011-00

n Notes on Handling User’s Manuals

n Warning and Disclaimer

IM 33K03P10-50E 1st Edition : Sep.22,2011-00

l Commonly used conventions throughout user’s manuals:

Character string to be entered:

Character string enclosed by brackets ({ }):

IM 33K03P10-50E 1st Edition : Sep.22,2011-00

Characters enclosed by brackets ([ ]):

l Conventions used in command syntax or program statements:

Characters enclosed by angle-brackets:

Characters enclosed by brackets ([ ]):

Characters enclosed by separators (| |):

IM 33K03P10-50E 1st Edition : Sep.22,2011-00

Identifies a source to be referred to.

IM 33K03P10-50E 1st Edition : Sep.22,2011-00

Copyright and Trademark Notices

IM 33K03P10-50E 2nd Edition : Jun.29,2012-00

IM 33K03P10-50E 2nd Edition

IM 33K03P10-50E 2nd Edition : Jun.29,2012-00

IM 33K03P10-50E 2nd Edition : Jun.29,2012-00

IM 33K03P10-50E 2nd Edition : Jun.29,2012-00

IM 33K03P10-50E 1st Edition : Sep.22,2011-00

1.1 What is PROFIBUS?

The Profibus interface provided by Yokogawa is in the category of PROFIBUS-DP.

IM 33K03P10-50E 1st Edition : Sep.22,2011-00

IM 33K03P10-50E 1st Edition : Sep.22,2011-00

2.1 Overall Configuration

n Configuration of Communication with PROFIBUS-DP

System builders Operation and Monitoring

PROFIBUS-DP I/O data

Slave device Slave device

Figure Overall Configuration of Communication with PROFIBUS-DP

IM 33K03P10-50E 1st Edition : Sep.22,2011-00

l PROFIBUS-DP Configurator (Product of Hilscher Co.)

l Operation and Monitoring

IM 33K03P10-50E 1st Edition : Sep.22,2011-00

2.2 Operating Environment

n Operating Environment for Communication with PROFIBUS-DP

IM 33K03P10-50E 2nd Edition : Jun.29,2012-00

2.3 PROFIBUS-DP Communication Module

Nest 3 Nest 4 Nest 5

Figure Nest Configuration

IM 33K03P10-50E 2nd Edition : Jun.29,2012-00

n Size of Data that can be Communicated

n Number of Assignable Communication I/O Definitions

n Connecting Multiple ACP71s to the Same Bus

Slave device Slave device Slave device Slave device

Figure Connecting Multiple ACP71s to the Same Bus