Hardware and Engineering

Caution!

Dangerous electrical voltage!

Before commencing the installation

●

Disconnect the power supply of the
device.

●

Ensure that the device cannot be
accidentally restarted.

●

Verify isolation from the supply.

●

Earth and short circuit.

●

Cover or enclose neighbouring units that
are live.

●

Follow the engineering instructions
(AWA) of the device concerned.

●

Only suitably qualified personnel may
work on this device/system.

●

Before installation and before touching
the device ensure that you are free of
electrostatic charge.

●

Connecting cables and signal lines
should be installed so that inductive or
capacitive interference do not impair the
automation functions.

●

Install automation devices and related
operating elements in such a way that
they are well protected against
unintentional operation.

●

Suitable safety hardware and software
measures should be implemented for
the I/O interface so that a line or wire
breakage on the signal side does not
result in undefined states in the
automation devices.

●

Ensure a reliable electrical isolation of
the low voltage for the 24 volt supply.
Only use power supply units complying
with IEC 60 364-4-41 or HD 384.4.41 S2.

●

Deviations of the mains voltage from the
rated value must not exceed the
tolerance limits given in the
specifications, otherwise this may cause
malfunction and dangerous operation.

●

Emergency stop devices complying with
IEC/EN 60 204-1 must be effective in all
operating modes of the automation
devices. Unlatching the emergency-stop
devices must not cause uncontrolled
operation or restart.

●

Devices that are designed for mounting
in housings or control cabinets must only
be operated and controlled after they
have been installed with the housing
closed. Desktop or portable units must
only be operated and controlled in
enclosed housings.

●

Measures should be taken to ensure the
proper restart of programs interrupted
after a voltage dip or failure. This should
not cause dangerous operating states
even for a short time. If necessary,
emergency-stop devices should be
implemented.

IBM is a registered trademark of International
Business Machines Corporation.

All other brand and product names are
trademarks or registered trademarks of the
owner concerned.

No part of this manual may be reproduced in
any form (printed, photocopy, microfilm or
any otherprocess) or processed, duplicated
or distributed by means of electronic
systems without written permission of
Moeller GmbH, Bonn.

Subject to alterations without notice.

/99

B 27-

30 G

List of revisions for the manual AWB 27-1300 GB

Modification date Page

Description

New

Modifica-
tion

Remove

09/99

Complete
manual

PS 416-NET-441 (Slave)

/99

270

1330

About This Manual

Contents

The PS 416-NET-440 and PS 416-NET-441 cards
are the interface from the PS 416-PLC to
PROFIBUS-DP. This manual describes hardware
and engineering as well as the test and
commissioning functions for these cards.

The PS 416-NET-441 slave card is configured with
the Sucosoft S 40 Topology Configurator. For
configuring the PS 416-NET-440 master card use
the Sucosoft S 40 Topology Configurator and the
PROFIBUS-DP configurator CFG-DP.

Additional
documentation

The PROFIBUS configurator is described in detail in
the electronic manual AWB-EM 2700-1336 GB. This
is a PDF file supplied with the configurator on the
Sucosoft S 40 CD-ROM.

For detailed information about the Sucosoft S 40
Topology Configurator, refer to the manual “S 40
User Interface” (AWB 2700-1305 GB).

About This Manual

/99

270

1330

Symbols

The symbols used in this manual have the following
meaning:

왘 Indicates handling instructions.

Indicates useful tips and additional information.

Note
Warns of the possibility of damage to products,
adjacent equipment or data.

Caution!
Warns of the possibility of serious damage to
products, adjacent equipment or data and risk of
serious or fatal personal injury.

/99

270

1330

About the Cards

General information

The PS 416-NET-440 and PS 416-NET-441 cards
form the interface between the PS 416 and the
PROFIBUS-DP field bus, the industry standard
based on EN 50 170 Vol. 2.

Purpose

PS 416-NET-440
This card provides the master function for the
PROFIBUS-DP field bus. It manages and handles the
exchange of data between the user program on the
PS 416 and the connected slaves. A maximum of
125 slaves can be addressed; without repeater, up
to 30.

This card also provides numerous diagnostic
options.

PS 416-NET-441
The slave card is required for connecting a PS 416
PLC to the PROFIBUS-DP field bus. It manages and
handles data exchange between the user program of
the PS 416 and one or more connected network
masters.

It, too, provides diagnostic data.

About the Cards

/99

270

1330

Hardware and software
requirements

The table presents an overview of the hardware and
software requirements for operating the
PS 416-NET-440 and PS 416-NET-441 cards in the
PS 416 PLC.

The device configuration files (*.GSD) for the cards
are included in the CFG-DP configuration software.

If other manufacturers’ devices are used, the
required files are available from Moeller’s service
mailbox and website and from the PROFIBUS User
Organization (PNO):

Analog modem +49 228 6021414

ISDN

+49 228 6021881

http://www.moeller.net/automation

http://www.profibus.com

PS 416-NET-440

PS 416-NET-441

Rack

PS 416-BGT-400/-410/-420

PS 416-BGT-421
(with potential equalization bar)

PS 416-ZBX-401/-402/-403

CPU

PS 416-CPU-x00 (in the basic unit)

Power supply

PS 416-POW-400/-410/-420

Sucosoft S 40

from version 2.1

from version 4.0

Operating system for
PS 416-CPU-x00

from version 2.1

from version 4.0

CFG-DP configuration
software

from version 1.0

–

Setup of PS 416-NET-440

/99

270

1330

Setup of
PS 416-NET-440

Figure 1: .PROFIBUS-DP card PS 416-NET-440

LEDs
CFG interface
Protective cap for the CFG interface
PROFIBUS-DP interface

P
R
O
F

B
U
S

D
P

network

PROFIBUS-DP

0100018

run

ready

status

error

NET-440

C
F
G

About the Cards

/99

270

1330

Notes on the PS 416-NET-440

LEDs

The four LEDs indicate the status of the card and the
complete PROFIBUS-DP bus (see Chapter 6,
Page 37):

the red LED indicates error conditions

the green LED indicates error-free operation

the yellow LEDs provide information about the
status of the card

CFG interface

The 9-pin subminiature connector is used to connect
a PC to the CFG-DP configuration software
(see Chapter 2, Page 12).

Protective cap

If the CFG interface is not used during operation of
the PS 416-NET-440, the connector must be fitted
with the protective cap to prevent electrostatic
interference.

PROFIBUS-DP interface

The 9-pin subminiature connector is used for
connecting the card to the PROFIBUS-DP field bus
(see Chapter 2, Page 12).

Setup of PS 416-NET-441

/99

270

1330

Setup of
PS 416-NET-441

Figure 2: PROFIBUS-DP card PS 416-NET-441

LEDs
PROFIBUS-DP interface

network

PROFIBUS-DP

0100018

bus

diag
config-
error

NET

-441

About the Cards

/99

270

1330

Notes on the PS 416-NET-441

LEDs

The three LEDs indicate the status of the card and
the complete PROFIBUS-DP bus (see Chapter 6,
Page 37):

the red LED indicates error conditions

the green LED indicates error-free operation

the yellow LED provides information about the
status of the card

PROFIBUS-DP interface

The 9-pin subminiature connector is used for
connecting the card to the PROFIBUS-DP field bus
(see Chapter 2, Page 11).

/99

270

1330

Configuration

Electromagnetic
compatibility (EMC)

For information about laying cables and screening,
please refer to manual AWB 27-1287-GB “EMC –
Engineering Guidelines for Programmable
Controllers”.

Number of cards and
slots

The PS 416-NET-440 master and PS 416-NET-441
slave cards can be used in all basic units (racks with
CPU).

PS 416-NET-440
This card requires two slots and can be placed in any
of the slots to the right of the CPU. A maximum of
seven PS 416-NET-440 cards can be fitted. Be sure
to calculate the required electrical power (from
Sucosoft S 40 V 4.0, this is done automatically by the
Topology Configurator).

PS 416-NET-441
This card requires one slot and can be placed in any
of the slots to the right of the CPU. To determine the
possible number of cards, you must calculate the
required electrical power.

PROFIBUS-DP
interface

The cards are connected to the PROFIBUS-DP field
bus via an isolated RS-485 interface, which is
located on the front of the PS 416-NET-440 or the
PS 416-NET-441 in the form of a female Sub-D
connector.

Use the special PROFIBUS-DP connector
ZB 4-209-DS2, which contains the circuitry
required for interference-free operation up to a
transfer speed of 12 Mbit/s.

Configuration

/99

270

1330

Connection assignment

The PROFIBUS-DP bus interface is a 9-pin male
Sub-D connector.

Figure 3: PROFIBUS-DP pin assignment

CFG interface

The PS 416-NET-400 card is connected to a PC
running the CFG-DP configuration software via an
RS 232 C interface (COM). The port is a female Sub-
D connector, located on the front of the
PS 416-NET-440. The PS 416-ZBK-210
programming cable can be used to make the
connection.

Pin

Designation

Meaning

RxD/TxD-P

Transmit/receive data line, positive

DGND

Data ground

Supply voltage +5 V

RxD/TxD-N

Transmit/receive data line, negative

Wiring and cabling

/99

270

1330

Connection assignment

The CFG interface is a 9-pin male Sub-D connector.

Figure 4: CFG connector pin assignment

Wiring and cabling

Connecting the cards

The PS 416-NET-440 and -441 communicate with
the connected stations via the PROFIBUS-DP field
bus. The data transmission medium for the
PROFIBUS-DP field bus is the screened ZB 4-900-
KB1 two-wire cable. This cable is supplied in 100 m
rolls and must be configured and fitted with
ZB 4-209-DS2 connectors by the user.

If the CFG port is not used during operation of the
card, the connector must be fitted with the
protective cap to prevent electrostatic
interference.

Pin

Designation

Meaning

RxD

Receive data

TxD

Transmit data

DGND

Data ground

Configuration

/99

270

1330

왘 To connect the card to the network’s PROFIBUS-

DP line, use the ZB 4-209-DS2 data plug.

왘 To fit the screen, remove a section of insulation

from all PROFIBUS cables.

왘 Attach the cable with the ZB 4-102-KS1 screen to

the potential equalization bar (see Fig. 5).

왘 If the PS 416-NET-440 or PS 416-NET-441 is the

first or last station on the line, switch the bus
terminating resistors on the data plug on by
turning the switch to ON.

Connecting stations

왘 Use a suitable data plug (e.g. a ZB 4-209-DS2 for

the 9-pin Sub-D connector) to connect the
stations to the network’s PROFIBUS-DP line.

왘 To fit the screen, remove a section of insulation

from all PROFIBUS cables.

왘 Attach the cable with the ZB 4-102-KS1 screen to

the potential equalization bar (see Fig. 5).

왘 If the station is located at the beginning or end of

the network’s PROFIBUS-DP line, switch the bus
terminating resistors on.

Wiring and cabling

/99

270

1330

Figure 5: Screening the data cable

PROFIBUS-DP data plug ZB 4-209-DS2
PROFIBUS-DP cable ZB 4-900-KB1
Screen ZB 4-102-KS1

B
A

PROFIBUS

DGND

(+5 V)

RxD/TxD-N

RxD/TxD-P

RxD/

TxD-P

PS 416-ZBX-40x

RxD/TxD-N

RxD/TxD-P
RxD/TxD-N

⫻8

Configuration

/99

270

1330

Connecting the PC to the PS 416-NET-440

To configure the PS 416-NET-440 with the CFG-DP
configuration software, connect the PC to the card
using the preassembled PS 416-ZBK-210 cable.

The cable is 2 m long. If this is not enough, you can
assemble your own cable using the PS 416-ZBS-411
and PS 416-ZBS-410 data plugs. The cable must be
no longer than 15 m.

Power supply

The power supply module PS 416-POW-4x0
internally supplies the cards with 5 V DC via the
rack’s system bus.

The card’s current consumption is:

PS 416-NET-440: max. 0.8 A

PS 416-NET-441: max. 0.5 A

To prevent errors during startup of PROFIBUS-DP,
set the system’s power supply up so that the
connected remote stations on the PROFIBUS-DP
line of the PS 416-NET-440 are switched on
simultaneously by the PS 416 PLC.

/99

270

1330

Installation

Fitting and removing
cards

Use the master and slave cards only in a basic unit
(rack with CPU).

In the rack, the

PS 416-NET-440 occupies two slots, and the

PS 416-NET-441 occupies one slot.

The PS 416-NET-440 and PS 416-NET-441 cards
can be installed in any slot of the basic unit to the
right of the power supply and the CPU.

왘 Slide the card into the rack until it snaps into

place.

왘 Tighten the fixing screws.

Removal of the cards is in reverse order.

Caution!
Do not remove or insert cards when live.
Before touching the card, free yourself of
electrostatic charge.
Voltage peaks at the bus connector can lead to
faults and can damage the card.

Installation

/99

270

1330

Connecting the card

왘 Make the connections to the PROFIBUS-DP

configurator CFG-DP (for PS 416-NET-440 only)
and to the PROFIBUS-DP field bus (see
Chapter 2 , Page 13).

왘 Use the screws on the data plugs to secure them

to the card.

If the CFG port is not used during operation of the
card, the connector must be fitted with the
protective cap to prevent electrostatic
interference.

/99

270

1330

Software Configuration

Configuring the
PS 416-NET-440

To configure the PS 416-NET-440 card, use the
Sucosoft S 40 Topology Configurator and the
PROFIBUS CFG-DP configurator.

Sucosoft Topology Configurator

In the Sucosoft S 40 Topology Configurator, specify
all cards used in the PS 416.

왘 In Sucosoft S 40, start the Topology

Configurator.

왘 Create a new topology configuration with a

PS 416-CPU-x00, or load an existing topology
configuration for a PS 416 with an operating
system version 2.1 or higher.

왘 Mark the card next to which you want to insert the

PS 416-NET-440, and click on the Local
Expansion button.

Software Configuration

/99

270

1330

왘 From the list of available cards, select the

PS 416-NET-440 and confirm with OK. A Suconet
K line number is then assigned to the
PROFIBUS-DP line (max. 9 lines). The
PROFIBUS-DP slaves are specified and
parameterized in the PROFIBUS-DP configurator
CFG-DP.

왘 When you have configured all PS 416 cards, save

the configuration file.

Seven PS 416-NET-440 cards can be inserted in
each rack. Be sure to calculate the required
electrical power (from Sucosoft S 40 V 4.0, this is
done automatically by the Topology
Configurator).

Configuring the
PS 416-NET-440

/99

270

1330

PROFIBUS-DP Configurator

With the CFG-DP configurator, you can

transfer new firmware versions to the
PS 416-NET-440

configure the PS 416-NET-440 and set the bus
parameters for PROFIBUS-DP

parameterize slave stations and assign them to
the PROFIBUS-DP master cards

assign slave stations to groups that respond to
the PROFIBUS-DP command “global control”
(e.g. SYNC or FREEZE)

print the configuration you have created

load the created configuration to the
PS 416-NET-440

monitor and diagnose the PS 416-NET-440 and
the assigned network line with its stations

start and stop communication in the network line
of the PS 416-NET-440

For a detailed description of the CFG-DP
Configurator and its operation, refer to the electronic
manual AWB-EM 2700-1336 GB. The manual (PDF
file) and the configurator are supplied with the
Sucosoft S 40 software.

Caution!
Do not interrupt firmware transmission as this
prevents subsequent access to the card.

Software Configuration

/99

270

1330

Configuring the
PS 416-NET-441

To configure the PS 416-NET-441 card, use the
Sucosoft S 40 Topology Configurator.

Sucosoft Topology Configurator

In the Sucosoft S 40 Topology Configurator, specify
all cards that are used in the PS 416.

왘 In Sucosoft S 40, start the Topology

Configurator.

왘 Create a new topology configuration with a

PS 416-CPU-x00, or load an existing topology
configuration for a PS 416 with an operating
system version 4.0 or higher.

왘 Mark the card next to which you want to insert the

PS 416-NET-440, and click on the Local
Expansion button.

Configuring the
PS 416-NET-441

/99

270

1330

왘 From the list of available cards, select the

PS 416-NET-441 and confirm with OK.

왘 When you have configured all PS 416 cards, save

the configuration file.

The number of PS 416-NET-441 cards that can
be used is determined by the power of the power
supply card. A power test is performed
automatically in the Sucosoft S 40 Topology
Configurator.

Software Configuration

/99

270

1330

Defining send and receive data parameters

왘 Open the Parameters window by double-clicking

the PS 416-NET-441 card in the current topology
configuration.

왘 Mark the card in the current topology

configuration and select ‹Edit

➞ Set

Parameters...›.

In the Station field, define the address to be assigned
to the PS 416-NET-441 as slave on the
PROFIBUS-DP line. Valid addresses are 0 to 125 (0
is reserved for diagnostics and should therefore be
avoided). The entered address and the address in the
configuration of the master for the PROFIBUS-DP
line of the PS 416-NET-441 must be the same.

왘 In the Receive Data field, enter the number of

bytes that the slave PS 416-NET-441 is to receive
from the line master. You can either select a
figure from the list of predefined values or enter a
value directly in the field.

Configuring the
PS 416-NET-441

/99

270

1330

왘 In the Send Data field, enter the number of bytes

that the PS 416-NET-441 is to send to the line
master. You can either select a figure from the list
of predefined values or enter a value directly in
the field.

왘 Confirm your inputs with OK.
왘 When you have configured all PS 416 cards, save

the file.

Always define send and receive data from the
point of view of the device (CPU) for which the
configuration is being created. The inputs made
here must be the same as the corresponding
parameter settings in the master’s
PROFIBUS-DP configurator.
If the master’s PROFIBUS-DP configurator
permits free lengths, you can enter any value from
0 and 244 for send and receive data. Otherwise,
you must select a value from the list. The listed
lengths correspond with those that are defined in
the device’s GSD file. These values can therefore
be defined with any standard-compliant
PROFIBUS-DP configurator. The sum of all send
and receive data must not exceed 400.

/99

270

1330

Operation

Addressing the cards

PROFIBUS-DP cards

Moeller’s 5-digit notation is used for reading and
writing in the PROFIBUS-DP network line. A
mirroring procedure is used to access the data. At
the beginning of each program cycle, the input
values are read from the dual-port RAM of the
PS 416-NET-440/-441, and at the end of the
program cycle, the output values are written to the
dual-port RAM of the PS 416-NET-440/-441.

The I/O data can be accessed by bit, byte, word, or
double word.

The data is assigned to the user program variables
when the variables are declared in the user program
by Sucosoft S 40.

The address notation assignment corresponds with
the notation for Suconet K:

Operand:

I, Q (master); RD, SD (slave)

Data width: X, B, W, D

For addressing slave card PS 416-NET-441, the first
two places of the address –

and

<Station

No.>

– are always “0” (zero). The third place defines

the slot in which the card is located.

Operation

/99

270

1330

The master declares the input and output data in
packets as separate modules in the PROFIBUS-DP
configuration, even if the network station consists of
only one physical module. The input and output data
is addressed through different module numbers.

A user program may therefore contain different
numbers for input and output data in the third place
of the five-digit address.

Example:
Slave PS 416-NET-441 is connected to line 1 and
has 10 input bytes and 10 output bytes.

Addressing the cards

/99

270

1330

The output data from the slave is shown in the lower
list box, labelled “Module#2”, and will be read by
master PS 416-NET-440 with address operators
%IB1.7.1.0 to %IB1.7.1.9.

The slave input data, labelled “Module#1”, is
supplied by master PS 416-NET-440 with address
operators %QB1.7.0.0 to %QB1.7.0.9.

The address notation is documented in detail in
manual AWB 2700-1306 GB “Sucosoft S 40:
Language Elements for PS 4-150/-200/-300 and
PS 416”, chapter 2, section “Directly represented
variables”.

PROFIBUS-DP stations

Master PS 416-NET-440 manages the PROFIBUS
line. The line number is assigned automatically in the
Sucosoft S 40 Topology Configurator.

In the Sucosoft S 40 Topology Configurator, enter
the slave’s station number, which is the same as the
Station Address in the CFG-DP configurator.

The address notation requires the listed module
number – “Module#x” – to be reduced by 1 each
time in the PROFIBUS-DP configurator.

Operation

/99

270

1330

Moeller slave devices consisting of several modules
(e.g. an EM 4-204-DX1 with local expansion
modules), are addressed in the order in which they
are connected. The EM 4, for example, would have
module number 0 and the connected LE 4 module
numbers 1 to a maximum of 6 in ascending order.

Other makes of PROFIBUS-DP station are
addressed in accordance with the description in the
associated device master data (*.GSD) files. Consult
the device’s documentation for address details.

Example for PS 416-NET-440:

VAR

AnalogInput AT %IW2.3.1.0 : INT;
(* Analogue input word 0 of 1st LE of
3rd station in 2nd line *)
LimitValue: INT := 800 ;

END_VAR

AnalogInput

LimitValue

JMPC

Alarm

.
.
.
Alarm:

To address the input and output values of the
PROFIBUS-DP stations, master
PS 416-NET-440 must use address ID %I or %Q,
with a corresponding data width definition (X, B,
W or D). There are, for example, no special IDs for
analog values (%IAW, %QAW), which are
addressed using normal input and output
addresses.

Working principle of the
PS 416-NET-440/-441

/99

270

1330

Example for PS 416-NET-441:

VAR

SetSpeed AT%SDW0.0.4.0:INT;
(*sends an integer value to the
master's receive data field*)
DefaultValue:INT:=800;

END_VAR

DefaultValue

SetSpeed

.
.
.

Working principle of the
PS 416-NET-440/-441

After the PLC is powered up, the PS 416-NET-440/-
441 performs a self-test. Any errors occurring during
the self-test are signalled by the LEDs on the front
panel (see Page 37).

/99

270

1330

Testing/Commissioning/Diagnostics

Commissioning the
PS 416-NET-440

For commissioning, the previously created
configuration must be transmitted to the
PS 416-CPU-x00. The procedure for configuring the
PS 416-NET-440 card is described in Chapter 4,
Page 19.

Requirements for downloading

To download a PROFIBUS-DP configuration to the
PS 416-NET-440,

the PS 416-CPU-x00 must be in status “ready”,
i.e. it must not be processing a program

and no program must be marked as active on the
PS 416-CPU-x00.

First, perform the following steps if the
PS 416-CPU-x00

is already processing a user program,

already contains a user program,

the existing configuration is to be changed,

the card has been replaced.

If no user program is loaded in the CPU, skip straight
to the Download section.

왘 In Sucosoft S 40, go to Test & Commissioning.

Testing/Commissioning/
Diagnostics

/99

270

1330

왘 Click the Halt button in the Program Status dialog

to stop the program.

왘 Click the Deactivate button to deactivate the user

program as the current process.

Downloading

왘 With the PROFIBUS-DP configurator CFG-DP,

transfer the firmware once to the card (for new
firmware versions only).

Caution!
Do not interrupt firmware transmission as this
prevents subsequent access to the cards.

Commissioning the
PS 416-NET-440

/99

270

1330

왘 Then use the CFG-DP configurator to transfer the

PROFIBUS-DP configuration to the
PS 416-NET-440.

왘 In the Sucosoft S 40 topology configurator,

create the configuration for the PS 416 master
CPU in which the PS 416-NET-440 card is
installed.
When the program code is generated, this
configuration is linked with the PLC user program
and then sent to the master CPU with Sucosoft
S 40.

왘 In Test & Commissioning ➞ Program Status in

Sucosoft S 40, click the Cold Start button (see
Page 33). The PROFIBUS-DP configuration in the
PS 416-NET-440 will be compared with the
configuration data of the CPU.

During operation, diagnostic data from the
PS 416-NET-440 and the network slave can be
evaluated either using diagnostics bytes or the
function block “PdpStationDiag” in the PS 416 user
program (see Chapter 6, Pa ge 41).

This comparison of the PROFIBUS-DP
configuration with the PLC program in the PS 416
CPU takes place only during the first cold start.

Testing/Commissioning/
Diagnostics

/99

270

1330

PROFIBUS-DP communication

The PROFIBUS-DP communication depends on the
CPU’s operating status.

When the PS 416 CPU changes from “ready” to
“run”, data transfer via PROFIBUS-DP begins. The
“run” LED of the PS 416-NET-440 is lit continuously,
provided at least one station complying with the
desired configuration is connected.

When an error occurs and the status of the PS 416
CPU changes from “run” to “ready” or “not ready”,
data exchange via PROFIBUS-DP stops, and the
“run” LED on the PS 416-NET-440 flashes at regular
intervals.

Commissioning the
PS 416-NET-441

The following steps must be performed to
commission the PS 416-NET-441 card:

왘 In the Sucosoft S 40 topology configurator,

create the configuration for the PS 416 slave CPU
in which the PS 416-NET-441 card is installed.

When the program code is generated, this
configuration is linked with the PLC user program. It
must then be sent to the slave CPU with Sucosoft
S 40.

The procedure for configuring the PS 416-NET-441
card is described in Chapter 4, P age 22.

Status indication in the
operating phase

/99

270

1330

Status indication in the
operating phase

The status of the PS 416-NET-440 and
PROFIBUS-DP communications is indicated by four
LEDs. The PS 416-NET-441 has three LEDs for this
purpose. They are located on the module’s front
panel.

During error-free data exchange with all
configured stations, all three LEDs of the
PS 416-NET-440 are lit. They are:
“run”, “ready” and “status”.

LED

Colour

Status

Meaning

PS 416-NET-440

run

green

Communication with at least one station in progress

cyclic flashing

Ready for communication

acyclic flashing

Parameter error

off

Communication interrupted

ready

yellow

PS 416-NET-440 ready for operation

cyclic flashing

Firmware must be transmitted or is being transmitted
(1 Hz or 2 Hz)

acyclic flashing

Hardware or firmware error

off

Hardware error

status

yellow

PS 416-NET-440 has the token, i.e., is the currently active
master of the network line

error

red

Transmission error during communication

PS 416-NET-441

bus

yellow

User data exchange with the PROFIBUS-DP master

flashing

No user data exchange. If the “config-error” LED also
flashes, the actual and set configuration do not correspond.

off

Startup phase

diag

red

A hardware error has occurred in the device.
The “config-error” LED is also lit.

off

Hardware OK

config error

red

Hardware fault in device. The “diag” LED is also lit.

flashing

Actual and set configuration do not correspond.
The “bus” LED also flashes.

off

Configuration OK

Testing/Commissioning/
Diagnostics

/99

270

1330

Overview of diagnostic
bytes

Error messages from master CPU:

Comparison of data between PS 416-CPU and

PS 416-NET-440

Diagnostic byte from master PS 416-NET-440:

Information about master PS 416-NET-440;

group information from slaves

Diagnostic byte from slave PS 416-NET-441:

Byte0: information about status of slave

PS 416-NET-441; read by the slave CPU

Byte1: communication status of slave

PS 416-NET-441; read by the slave CPU

Extended byte1: information about slave CPU;

master CPU reads operating status of slave CPU

Extended byte2: service information about slave CPU

(e.g. state of backup battery)

General byte: indicator for extended diagnostic data

from slave; read by the master CPU

Function block “PdpStationDiag”:

Extended diagnostic message from slave; called by the

master CPU

CPU

POW

NET-440

CPU

POW

NET-441

PROFIBUS-DP

,,,

Master PS 416

Slave PS 416

CPU error messages

/99

270

1330

Diagnostic bytes indicate errors that have occurred
during testing, commissioning or operation. Their
physical location is

in master CPU PS 416 (

)

in master card PS 416-NET-440 (

)

in slave card PS 416-NET-441(

)

Diagnostic bytes are called, however, in the PLC user
program. The following bytes are used:

in the user program of master

CPU PS 416

in the user program of slave CPU PS 416

CPU error messages

Messages from the PS 416 CPU operating

system

During operation of the PS 416 with the
PS 416-NET-440 card, errors may arise during
transfer or cold start of the user program.

If, during the cold start of a user program, an I/O
error message appears, check the user
program’s I/O declarations in PROFIBUS-DP
operation against the S 40 configuration and
against the PROFIBUS-DP configuration.

Testing/Commissioning/
Diagnostics

/99

270

1330

The following error codes are possible:

82C0

Error when reading the PROFIBUS-DP
configuration. (Indication during cold start)

82C2

The PS 416-NET-440 does not have a
PROFIBUS-DP configuration. (Indication
after transfer)

80FE

Error during parameter configuration of
PS 416-NET-440. (Indication after transfer
or during cold start; internal error)

82C3

Insufficient free memory for PROFIBUS-DP
configuration. (Indication during cold start)

82C4

There is no station with the specified
address in the PROFIBUS configuration.
(Indication after cold start)

82C5

More than 24 modules were configured for
one station. (Indication after cold start)

82C6

The operating system of the PS 416 CPU
does not know the configuration of the
PROFIBUS-DP line, because

the module is not inserted;

the assignment of line numbers to slot
numbers in the topology configuration is
not correct.

Diagnostic byte
of the master card

/99

270

1330

Diagnostic byte
of the master card

PS 416-NET-440

The PS 416-NET-440 provides the user program
with a diagnostic byte, which is addressed with the
type “IS” input operator.

Assuming the PS 416-NET-440 is inserted in slot 6 of
the rack, then the diagnostic byte for this card is
declared as follows:

VAR

Status_440 AT %ISB0.0.6.0 : BYTE ;

END_VAR

The meaning of the bits of the diagnostic bytes is as
follows:

During error-free operation, all bits have the value “0”
(zero).

Bit 0:

reserved

Bit 1:

reserved

Bit 2:

reserved

Bit 3:

Group information; is set when a configured
station does not report on the bus. (“error”
LED of PS 416-NET-440 is lit)

Bit 4:

reserved

Bit 5:

is set when the PLC does not exchange data
with any station in operating status “run”.

Bit 6:

is set when the PS 416-NET-440 does not
have a valid configuration.

Bit 7:

is set when the self-test of the
PS 416-NET-440 was unsuccessful.

Testing/Commissioning/
Diagnostics

/99

270

1330

Evaluation of the diagnostic byte in the user program
must consist of either:

evaluating the individual bits using the special
Moeller point notation

LD Status_440.3 (* Line station not reporting *)

checking the whole diagnostic byte for errors

Status_440

JMPC

Error

Diagnostic byte
of slave card

PS 416-NET-441

The PS 416-NET-441 provides the user program
with two diagnostic bytes, which are addressed with
the type “IS” input operator.

Assuming the PS 416-NET-441 is inserted in slot 5 of
the rack, then the diagnostic bytes for this card are
declared as follows:

VAR

Status1_441 AT %ISB0.0.5.0 : BYTE ;
Status2_441 AT %ISB0.0.5.1 : BYTE ;

END_VAR

Diagnostic byte
of slave card

09/99 AWB 2700-1330 GB

햴

BYTE 0

Bit 0:

The card is defective. Replace the card. The
signal is cleared automatically once the error
is rectified. A reset in the diagnostic status of
the CPU is not necessary.

Bit 1:

If a hardware fault has occurred; replace the
faulty card. The signal is cleared
automatically once the fault is rectified. A
reset in the diagnostic status of the CPU is
not necessary.

Bit 2:

If the input/output values are invalid, the card
performs an internal parameter configuration
shortly after power is restored or the
program is transferred. During this time, the
values that were read or written are invalid.
Permissible values can be read or output as
soon as the signal is cleared. The signal is
cleared automatically once the fault is
rectified.

A reset in the diagnostic status of

the CPU is not necessary.

Bit 3:

In case of a timeout, the communication
partners do not respond. This is either due to
a faulty card or a fault in the PROFIBUS-DP
line. Switch the system off and on again and
observe the notes about cable routing in the
manuals. The signal is cleared automatically
once the fault is rectified. A reset of the
diagnostic status of the CPU is not
necessary.

Testing/Commissioning/
Diagnostics

/99

270

1330

BYTE 1

Bit 2:

A configuration error indicates that the local
configuration does not match the sent
PROFIBUS-DP configuration of the master.
Check the configured send and receive data
lengths in the Sucosoft S 40 topology
configuration and the PROFIBUS-DP
configuration of the master. The signal is
cleared automatically once the fault is
rectified. A reset in the diagnostic status of
the CPU is not necessary.

Bit 3:

If “SYNC” is active, the station’s receive data
(the output data for the PROFIBUS-DP
master) has been frozen with a “SYNC”
command from the master. The message
disappears automatically when an
“UNSYNC” command is received.

Bit 4:

If “FREEZE” is active, the card’s send data
(the input data for the PROFIBUS-DP
master) has been frozen with a “FREEZE”
command from the master. The message
disappears automatically when an
“UNFREEZE” command is received.

For a description of the “PdpFreezeSync”
function block, see manual AWB 2700-1306
“Language Elements for PS 4-150/-200/-300 and
PS 416”.

Diagnostic byte
of slave card

/99

270

1330

Bit 6:

If no PROFIBUS-DP communication is
taking place, the master of the
PROFIBUS-DP line does not exchange user
data with the station. Check:

the master’s power supply

that the master is in the correct operating
mode for communication

for an interrupted connection

that the PROFIBUS-DP address is
correct

that the station has been configured in
the PROFIBUS-DP configurator

that the data length in the PROFIBUS-DP
configurator corresponds with the locally
configured data lengths. If the
configuration data is not the same, bit 2 –
“config-error” – will be set.

The signal is cleared automatically once the
fault is rectified.

A reset in the diagnostic

status of the CPU is not necessary.

Testing/Commissioning/
Diagnostics

/99

270

1330

Card PS 416-NET-441 provides extended, station-
specific information to the respective PROFIBUS-DP
master in the line. On PROFIBUS-DP masters
PS 416-NET-440 and LE 4-504-BS1 from Moeller,
this extended information is scanned with the help of
function block “PdpStationDiag”. For details about
scanning extended diagnostic data with other
PROFIBUS-DP masters, refer to the manufacturer’s
documentation.

The extended diagnostic information is stored in two
bytes, whose significance is also described in the
GSD file:

First byte of the extended diagnosis

Bit 0:

The PLC is in status “not ready”. The PS 416
PLC with card PS 416-NET-441 has a fatal
error or does not have an operating system.
Load an operating system or replace the
CPU.

Bit 1:

The PLC is in Halt mode. The PS 416 PLC
has stopped.

Bit 2:

If the message “Diag” appears, one or more
diagnostic messages are pending on the
PS 416 PLC. In Sucosoft S 40, call up the
diagnostic messages with “Test &
Commissioning” and check the extended
information in the second byte.

Diagnostic byte
of slave card

/99

270

1330

Second byte of extended diagnosis (message

bits of host CPU)

Slave stations – general

Each slave in the PROFIBUS-DP has a diagnostic
byte that can be addressed with the type “IS” input
operator by the user program of master CPU PS 416.
The line number and station number are defined by
the configuration; the card number is always “0”.

Bit 0:

If the message “DAK” appears, there is an
error in the local configuration. The topology
configuration for the slave CPU does not
correspond with the actual configuration. If
no card is recognized in the slot, the card did
not respond when it was addressed, or a
nonexistent card was addressed.

Bit 1:

If the message “DDK” appears, there is an
error in the remote configuration.

The

topology configuration of one or more
network lines connected to the slave CPU
does not correspond with the actual
configuration. In Test & Commissioning in
the Sucosoft S 40 Topology Configurator,
use the network diagnostics to check which
lines and stations are affected.

Bit 2:

The message “DBM” (battery monitor),
indicates that the backup battery is empty
and must be replaced. It is located at the
front of the PS 416 CPU or in the PCMCIA
SRAM memory card of the CPU.

Testing/Commissioning/
Diagnostics

/99

270

1330

Example:
The diagnostic byte of the tenth station on network
line 2 is assigned by the variable declaration.

VAR

Status_Slave AT %ISB 2.10.0.0 : BYTE ;

END_VAR

Bits 4 and 6 are important for diagnosis. They can be
declared and evaluated as Boolean variables.

VAR

Bit4_Slave10 AT %IS2.10.0.0.4 : BOOL ;
Bit6_Slave10 AT %IS2.10.0.0.6 : BOOL ;

END_VAR

In the former case, only those bits relevant to the
diagnostic byte must be filtered out before evaluation
(in the example these are bits 4 and 6):

2#01010000

AND

Status_Slave

Cleared

The two relevant bits have the following meaning:

Bit 4:

Diagnostic bit.
Extended diagnostic data for the station is
available. This data can be read in the user
program with function block
“PdpStationDiag”. This bit is reset to “0”
after its evaluation by the function block.

Bit 6:

Communication bit.
This is set when there is an error in the data
exchange with the station, for example when
the station is not connected or is incorrectly
configured.

Function block
“PdpStationDiag”

/99

270

1330

Function block
“PdpStationDiag”

Extended diagnostic messages from slaves

Requesting diagnostic data from PROFIBUS-DP
station

Prototype of the function block

Meaning of operands

PdpStationDiag

ARRAY[1..100] OF BYTE

Diagnostics

BOOL

Strobe

Active

BOOL

USINT

MasterSlot

State1

BYTE

USINT

StationAddress

State2

BYTE

State3

BYTE

MasterAddress

USINT

Ident

UINT

error

UINT

Name

Meaning

Diagnostics

Transfers an array of 100 bytes. The station’s extended diagnostic data is stored here

Strobe

Enables the function block; the diagnostic job is initiated

MasterSlot

Slot number of associated PS 416-NET-440 card
Value range: 4 to 19; decimal

StationAddress

Address of the PROFIBUS-DP slave whose diagnostic data is to be read

Active

Display of job processing status
1: job accepted; 1 to 0: job finished

State 1

Standard diagnostic byte 1 of PROFIBUS-DP

State 2

Standard diagnostic byte 2 of PROFIBUS-DP

State 3

Standard diagnostic byte 3 of PROFIBUS-DP

MasterAddress

Provides address of master module to which addressed slave is assigned

Ident

Provides specific ID of PROFIBUS-DP station

Error

Error messages

Testing/Commissioning/
Diagnostics

/99

270

1330

Description

Function block “PdpStationDiag” can be used to
scan the standard and extended diagnostic data (if
available) of the PROFIBUS-DP slave. The scan is
performed with a rising edge at the Strobe input of
the function block. The address parameters
(StationAddress, MasterAddress, MasterSlot, Ident)
are used to define the slave whose diagnostic data is
to be read.

If output Active is “1”, the job was accepted after an
input value validity check. As long as this output
stays “1”, the status of input Strobe is ignored. If
output Active changes from “1” to “0” and output
Error is “0”, then the job was processed successfully.

If, however, output Error has a value other than zero,
an error has occurred. The error can be identified by
means of the value at output Error.

The value of output Error has the following meaning:

Function block “PdpStationDiag” must be
instantiated only once for each PS 416-NET-440
in the user program.

No error

Defective function block;
defective function block library

Diagnostic data cannot be requested

Error when receiving diagnostic data

Invalid slot number
Permissible range: 4 to 19

Invalid station number
Permissible range: 1 to 125

Function block
“PdpStationDiag”

/99

270

1330

The Diagnosis parameter specifies a 100-element
array of type BYTE. The extended diagnostic data of
the addressed slave is entered here.

If the job is carried out successfully, then the
PS 416-NET-440 always returns 100 bytes,
regardless of the actual length of the diagnostic data.

The topology configuration does not specify a
card for the specified slot

The PS 416-NET-440 is not specified for the
specified slot

The PS 416-NET-440 is not ready for
operation

The PROFIBUS-DP configuration does not
contain the specified station

No diagnostic data is available for the
specified station

The slot is already occupied by another
function block (blocks PdpStationDiag or
PdpFreezeSync were not called sequentially,
and at least one of these blocks is still active)

Make sure that the array sent at the Diagnosis
input/output is 100 bytes long!

Testing/Commissioning/
Diagnostics

/99

270

1330

When the job is completed successfully, the function
block returns three diagnostic bytes from the
PROFIBUS-DP.

Extended diagnostics/device-specific

Standard slave
diagnostics

15 14 13 12 11 10

State 1

State 2

State 3

MasterAddress

Ident

Diagnostics

State1

Bit 0:

No response from station

Bit 1:

Station not ready for data transfer

Bit 2:

Station parameters incorrectly configured

Bit 3:

Station-specific diagnostic data is available

Bit 4:

Station has detected an unknown
command.

Bit 5:

Implausible response from station

Bit 6:

Incorrect parameter settings (e.g. ID number)

Bit 7:

Station parameters were configured by
another master

State2

Bit 0:

Station parameters not configured

Bit 1:

Static diagnosis

Bit 2:

Permanently set to 1

Bit 3:

Response monitoring active

Bit 4:

Freeze command active

Bit 5:

Sync command active

Function block example

/99

270

1330

Function block
example

Slot 7 of a PS 416 rack contains a PS 416-NET-440
card, which manages the PROFIBUS-DP line with
two slave stations:

one CM 4-504-GS1 (gateway)

one EM 4-204-DX1 with local expansion modules

Initially, the topology configuration is created in the
Sucosoft S 40 Topology Configurator. The
procedure configurating topologies is described in
manual AWB 2700-1305 GB “Sucosoft S 40 User
Interface”.

Bit 6:

Reserved

Bit 7:

PROFIBUS-DP configuration does not
contain the specified station

State3

Bit 0 to bit 6: reserved

Bit 7:

Extended station diagnostic data longer than
100 bytes

Testing/Commissioning/
Diagnostics

/99

270

1330

The two slave stations are added and parameterized
in the PROFIBUS-DP configurator CFG-DP. For
details about operating the CFG-DP configurator,
refer to the electronic manual
AWB EM 2700-1336 GB (PDF file for Acrobat
Reader), which is included with the Sucosoft S 40
software.

To set the parameters of slave CM 4-504-GS1 with
station address 10, 16 bytes will be transferred in
each direction in this example.

Testing/Commissioning/
Diagnostics

/99

270

1330

This configuration is stored and sent to the
PS 416-NET-440 card.

The sample program listed below uses the topology
configuration created with Sucosoft S 40 to generate
an executable program for the PS 416. The
configuration is then transferred to the PS 416 CPU.

As well as carrying out an error analysis, you should
implement the following program sequences when
working with the function block.

Function block example

/99

270

1330

The functions of the individual program sections are
listed below and are labelled with a corresponding
comment at the start of each section:

Registering all set diagnostic bits

Calling the function block for all registered
diagnostic bits

Entering the diagnostic data in a station-specific
buffer

Enabling the function block for a restart

Evaluating the diagnostic data

If diagnostic messages occur frequently and from
several stations at the same time, you should assign
priority to the function block call. This ensures that all
diagnostic data from the most important stations is
received.

The following example suggests a solution for the
function block whenever two stations send a
diagnosis at the same time. The solution guarantees
that each diagnostic message will be evaluated, even
if one of the stations continually sets the diagnostic
bit.

The master card always contains only the last
diagnostic message of a station. The diagnostic
bit remains set until the diagnostic data is fetched
by a function block call.

Testing/Commissioning/
Diagnostics

/99

270

1330

Program DP_Diagnostics

VAR

(* Status DP line, master in slot 7 *)

DP_Status_Line_1

AT %ISB0.0.7.0 :

BYTE;

(* DP---Line 1---Station 4---Module 0---EM4-204-DX1--- *)
(* Status byte, station 4 *)

Status_EM_4_204_ADR_4

AT %ISB1.4.0.0 :

BYTE;

em4204DX1_Modul0_IB0

AT %IB1.4.0.0 :

BYTE;

em4204DX1_Modul0_IB1

AT %IB1.4.0.1 :

BYTE;

le4206AA1_Modul1_IW0

AT %IW1.4.1.0 :

UINT;

le4206AA1_Modul1_IW2

AT %IW1.4.1.2 :

UINT;

le4206AA1_Modul1_IW4

AT %IW1.4.1.4 :

UINT;

le4206AA1_Modul1_IW6

AT %IW1.4.1.6 :

UINT;

le4206AA1_Modul1_QW0

AT %QW1.4.1.0 :

UINT;

le4206AA1_Modul1_QW2

AT %QW1.4.1.2 :

UINT;

le4116XD1_Modul2_QB0

AT %QB1.4.2.0 :

BYTE;

le4116XD1_Modul2_QB1

AT %QB1.4.2.1 :

BYTE;

le4116XD1_Modul3_QB0

AT %QB1.4.3.0 :

BYTE;

le4116XD1_Modul3_QB1

AT %QB1.4.3.1 :

BYTE;

le4116DX1_Modul4_IB0

AT %IB1.4.4.0 :

BYTE;

le4116DX1_Modul4_IB1

AT %IB1.4.4.1 :

BYTE;

le4308HX1_Modul5_IB0

AT %IB1.4.5.0 :

BYTE;

le4308XH1_Modul6_QB0

AT %QB1.4.6.0 :

BYTE;

(* DP---Line 1------Station 10--- GateWay--CM4-504-GS1--------- *)
(* Status byte, station 10 *)

Status_GateWay_ADR_10

AT %ISB1.10.0.0:

BYTE;

cm4504_IB0

AT %IB1.10.0.0 :

BYTE;

(* max. 16 bytes: 0 - 15 *)
cm4504_IB15

AT %IB1.10.0.15:

BYTE;

cm4504_QB0

AT %QB1.10.0.0 :

BYTE;

(* max 16 bytes: 0 - 15 *)
cm4504_QB15

AT %QB1.10.0.15:

BYTE;

Function block example

/99

270

1330

(***********************************************************************************)
(*

Diagnosis of all line stations *)

(***********************************************************************************)

FB_DP_Diag

PDPSTATIONDIAG;

Strobe

BOOL;

FB_DP_Diag_F_Edge

F_TRIG;

DP_Diag

ARRAY[1..100] OF BYTE;

DP_Address

USINT;

DP_MASTERSLOT :

USINT;

GateWay_ADR_10_Diag

ARRAY[1..100] OF BYTE;

Buffer_Adr4

ARRAY[1..13] OF BYTE;

Buffer_Adr10

ARRAY[1..6] OF BYTE;

ADR4_Diag_Flag

BOOL;

ADR10_Diag_Flag

BOOL;

DiagCounter

USINT;

TestDiagBit_ADR4

FB_DiagBitCounter;

TestDiagBit_ADR10

FB_DiagBitCounter;

END_VAR

DP_Status_Line_1(* Status byte DP *)

(* Evaluate DP line status byte *)

(*...*)

(* Status byte for DP station

Status_EM_4_204_ADR_4.6

(* Communication bit for station 4 *)

Status_GateWay_ADR_10.6

(* Communication bit for station 10 *)

(* Evaluate communication bit *)

(*...*)

(** Begin ******************* Evaluate diagnosis ***********************************)

(***********************************************************************************)
(*

(***********************************************************************************)

(* Diagnostic bit counter Addr.4 *)

CAL TestDiagBit_ADR4(

enable :=1,
InBit :=Status_EM_4_204_ADR_4.4
|
:=SetDiagBitCounter)

(* Diagnostic bit counter Addr.10 *)

Testing/Commissioning/
Diagnostics

/99

270

1330

CAL TestDiagBit_ADR10(

enable :=1,
InBit :=Status_GateWay_ADR_10.4
|
:=SetDiagBitCounter)

(* Diagnostic detected then set diagnostic flags *)

FB_DP_Diag.Active

JMPC

_DiagCall

(* Diagnostic request still active *)

DiagCounter

(* Counter of detected diagnostic events *)

(* All diagnostics requests have been sent*)

JMPC

_ADR4

(* Entry of new diagnostic flags possible *)

JMP

_DiagSelect

(* Continue processing diagnostic flags *)

_ADR4:

(* Set diagnostic flag if ADR 4 reports diagnostic*)

Status_EM_4_204_ADR_4.4

JMPCN

_ADR10

DiagCounter

ADD

DiagCounter

(* Increment diagnostic counter *)

ADR4_Diag_Flag

(* Set diagnostic flag for addr. 4*)

_ADR10:

(* (* Set diagnostic flag if ADR 10 reports diagnostic**)

Status_GateWay_ADR_10.4

JMPCN

_ADRx

DiagCounter

ADD

DiagCounter

ADR10_Diag_Flag

(* (* Set diagnostic flag for addr. 10 **)

_ADRx:
(*...*)

Function block example

/99

270

1330

(***********************************************************************************)
(*

Function block call for all registered diagnostic bits*)

(***********************************************************************************)

_DiagSelect:

(* Process set diagnostic flags *)

ADR4_Diag_Flag

JMPC

_prepareDiag_ADR4

ADR10_Diag_Flag

JMPC

_prepareDiag_ADR10

JMP

_DiagCall

(* No diagnostic bit set *)

_prepareDiag_ADR4:

(* Enter parameters for diagnostics function block *)

Status_EM_4_204_ADR_4.4

FB_DP_Diag.Strobe

DP_Address

DP_MASTERSLOT

ADR4_Diag_Flag

JMP

_DiagCounter

_prepareDiag_ADR10:

Status_GateWay_ADR_10.4

FB_DP_Diag.Strobe

DP_Address

DP_MASTERSLOT

ADR10_Diag_Flag

JMP

_DiagCounter

_DiagCounter:(* Decrement diagnosis counter *)

DiagCounter

SUB

DiagCounter

Testing/Commissioning/
Diagnostics

/99

270

1330

(***********************************************************************************)
(*

Function block call

(***********************************************************************************)

_DiagCall:

CAL FB_DP_Diag(

STROBE :=,
MASTERSLOT :=DP_MASTERSLOT,
STATIONADDRESS :=DP_Address,
DIAGNOSE :=DP_Diag
|
:=ACTIVE,
:=STATE1,
:=STATE2,
:=STATE3,
:=MASTERADDRESS,
:=IDENT,
:=ERROR)

(* Evaluate falling edge of Active output *)
CAL FB_DP_Diag_F_Edge(

CLK :=FB_DP_Diag.Active
|
:=Q)

FB_DP_Diag_F_Edge.Q

JMPCN

_DiagEnd
(* Falling edge detected *)

FB_DP_Diag.Error

(* FB error detection *)

JMPC

_NoError

(* error-free *)

(*...*)

JMP

_DiagStrobe0

_NoError:

(* Enter diagnostic data in station diagnostics buffer *)

DP_Address

JMPC

_DiagData_ADR4

DP_Address

JMPC

_DiagData_ADR10

JMP

_DiagStrobe0

Function block example

/99

270

1330

(***********************************************************************************)
(*

Enter diagnostic data in station-specific buffer*)

(***********************************************************************************)

_DiagData_ADR4:

(* Verify Master address and ID No. *)

FB_DP_Diag.Masteraddress

FB_DP_Diag.Ident

(*...*)

(* Enter diagnosis data in buffer *)

FB_DP_Diag.STATE1

Buffer_Adr4[1]

FB_DP_Diag.STATE2

Buffer_Adr4[2]

FB_DP_Diag.STATE3

Buffer_Adr4[3]

DP_Diag[1]

Buffer_Adr4[4]

DP_Diag[2]

Buffer_Adr4[5]

DP_Diag[3]

Buffer_Adr4[6]

DP_Diag[4]

Buffer_Adr4[7]

DP_Diag[5]

Buffer_Adr4[8]

DP_Diag[6]

Buffer_Adr4[9]

DP_Diag[7]

Buffer_Adr4[10]

DP_Diag[8]

Buffer_Adr4[11]

DP_Diag[9]

Buffer_Adr4[12]

TestDiagBit_ADR4.SetDiagBitCounter

Buffer_Adr4[13]

JMP

_DiagStrobe0

Testing/Commissioning/
Diagnostics

/99

270

1330

_DiagData_ADR10:

(* Verify Master address and ID No. *)

FB_DP_Diag.Masteraddress

FB_DP_Diag.Ident

(*...*)

(* Enter diagnosis data in buffer *)

FB_DP_Diag.STATE1

Buffer_Adr10[1]

FB_DP_Diag.STATE2

Buffer_Adr10[2]

FB_DP_Diag.STATE3

Buffer_Adr10[3]

DP_Diag[1]

Buffer_Adr10[4]

DP_Diag[2]

Buffer_Adr10[5]

TestDiagBit_ADR10.SetDiagBitCounter

Buffer_Adr10[6]

JMP

_DiagStrobe0

(***********************************************************************************)
(*

Enable function block for a restart

(***********************************************************************************)

_DiagStrobe0:

(* Output Strobe 0 after falling edge *)

CAL FB_DP_Diag(

STROBE :=0,
MASTERSLOT :=,
STATIONADDRESS :=,
DIAGNOSE :=DP_Diag)

_DiagEnd:

(***********************************************************************************)
(*

Evaluate diagnostic data

(***********************************************************************************)
(*...*)

(** End ******************* Evaluate diagnostic data ********************************)

Function block example

/99

270

1330

(***********************************************************************************)
(*

I-O Addressing of DP Stations

(***********************************************************************************)

16#FF

le4116XD1_Modul2_QB1

(*...*)

_END:
END_PROGRAM

FUNCTION_BLOCK FB_DiagBitCounter
VAR_OUTPUT

SetDiagBitCounter:BYTE;

END_VAR
VAR_INPUT

enable

BOOL;

InBit

BOOL;

END_VAR
VAR

Set_Edge

R_TRIG;

END_VAR

enable

JMPCN _End

(* Evaluate if bit was set *)
CAL Set_Edge(

CLK :=InBit
|
:=Q)

Set_Edge.Q

JMPC

_SetBit

JMP

_End

(* Count occurrences of DiagBit *)
_SetBit:

SetDiagBitCounter

BYTE_TO_USINT
ADD

USINT_TO_BYTE
ST

SetDiagBitCounter

_END:
END_FUNCTION_BLOCK

/99

270

1330

Appendix

Technical data

Current consumption

max. 0.8 A (PS 416-NET-440);
0.5 A (PS 416-NET-441)

Ambient temperature

(0 to 55) °C

Storage temperature

(–20 to 70) °C

Isolation voltage

850 V DC

Vibration resistance

1 g/(0 to 150) Hz

Shock resistance

15 g/11 ms

Degree of protection

IP 20

Weight

210 g (PS 416-NET-440);
130 g (PS 416-NET-441)

Interface

PROFIBUS-DP (EN 50 170, Vol.

Station type

PS 416-NET-440: master (class 1)
PS 416-NET-441: slave

Electrical standard

RS 485

Electrical isolation

Yes

Baud rate detection

automatic

Baud rate [kbit/s]

Cable lengths [m]

9.6

1200

19.2

1200

93.75

1200

187.5

1000

500

400

1500

200

3000

100

6000

100

12000

100

Cable

ZB 4-900-KB1;
specifically for PROFIBUS-DP

Connector

ZB 4-209-DS2; special PROFIBUS-DP
connector up to 12 Mbit/s with switchable
bus terminating resistors

Document Outline