Toshiba T2N, T2, T2E User Manual

DeviceNet Module DN211 for

PROSEC - T2/T2E/T2N

Instruction Manual

(Appendix3 DN211A)

6 F 3 B 0 3 6 4

REQUIREMENTS

• Read this instruction manual carefully before operating.

• Keep the manual aside to use when necessary.

• Pack the manual with the DN211 when transferring or

reselling.

January, 2001

© 2001 Toshiba Corporation

All rights reserved

UM-TS02***E16

6 F 3 B 0 3 6 4

© Copyright 1998 by Toshiba Corporation Tokyo, Japan
Toshiba Corporation reserves the right to make changes and improvements

to this publication and/or related products at any time without notice. No
obligation shall be incurred, except as noted in this publication.

This publication is copyrighted and contains proprietary material. No part of
this book may be reproduced, stored in a retrieval system, or transmitted in
any form or by any means — electrical, mechanical, by photocopying,
recording, or otherwise — without obtaining prior written permission from
Toshiba.

Important Information
Misuse of this equipment can result in property damage or human injury.

Because controlled system applications vary widely, you should satisfy
yourself as to the acceptabillity of this equipment for your intended purpose. In
no event will Toshiba Corporation be responsible or liable for either indirect or
consequential damage or injury that may result from the use of this
equipment.

No patent liability is assumed by Toshiba Corporation with respect to the use
of information, illustration, circuits equipment, of application examples in this
publication.

 1 

Safety Precautions

Thank you for purchasing Toshiba's DeviceNet module (DN211) for programmable controllers
PROSEC-T2 series (T2/T2E/T2N). This instruction manual describes the handling, precautions
and operation of the DN211.

Be sure to carefully read this manual and all of other related documents to learn the safety
precautions, notes, and knowledge about the DN211 before its installation, operation, or
inspection. This will allow you to operate your DN211 comfortably.

Important Information

1. Toshiba's DN211 is designed and manufactured for use with general industrial

equipment(manufacture line control devices, machine tools, etc.); it is not intended for use
with equipment and systems which will endanger people's life during operation.

Contact the Toshiba dealer in advance when you are going to use your DN211 for special

applications such as transport vehicles(train, etc.), medical equipment, aerospace equipment,
nuclear power control equipment, underwater relay equipment, or other similar applications.

6 F 3 B 0 3 6 4

2. Toshiba's DN211 is manufactured under strict quality control. However, be sure to install

safety systems to minimize the effect of a possible accident before you apply your DN211 to
the equipment which will endanger people's life or cause serious damage on the surroundings
if the DN211 should break down.

3. Toshiba's DN211 is meant for those who have general knowledge of handling control

equipment, especially the knowledge about installation, wiring, operation, and maintenance of
the DN211. Incorrect handling of the DN211 can cause electric shock, fire, failure, or/and
malfunction. Therefore, don't engage in the installation, wiring, operation, or maintenance of
the DN211 if your knowledge including electrical knowledge is not enough to handle control
equipment. Instead, ask the qualified person to do such work.

4. This instruction manual and accompanying documents are meant for those who have general

knowledge about the programmable controller and how to handle control equipment. If you
have any questions on the content of this manual, don't hesitate to contact the Toshiba dealer.

 2 

Safety Precautions (continued)

[Warning indication]

This instruction manual has the following important indications and symbols to prevent bodily injury
and property damage during operation. Be familiar with these safety indications to follow during
operation. After reading the text, keep the manual aside to consult when necessary.

Description of Safety Signs

Indication Meaning

Indicates misuse of the handling could cause a

DANGER

CAUTION

fatal accident or serious injury.

Indicates misuse of the handling could cause
injury or material damage.

6 F 3 B 0 3 6 4

Injury means a hurt, burn, or electric shock, which requires neither hospitalization nor long-term

medical treatment by visits. Some of the CAUTION items, however, could bring about grave

consequences depending on the situation. So be sure to always follow the CAUTION instructions.

 3 

Safety Precautions (continued)

•

Precaution for operation

DANGER

1. Configure an emergency-stop circuit, interlock circuit, and/or other similar safety
circuits outside the PC and DN211.

If the PC or DN211 gets failed or malfunctioned, it can cause an accident which will
lead to bodily injury and/or mechanical damage.

T2/T2E/T2N User’s Manuals

3. Preparation for Operation
(hardware)

CAUTION

2. Secure the safe environment before executing program modification, forcible output,
RUN, or HALT instruction during operation. An operational mistake can cause
mechanical damage or accident.

T2/T2E/T2N User’s Manuals

3. Preparation for Operation
(hardware)

6 F 3 B 0 3 6 4

•

DIP switch for setting the operating mode/communication rate

CAUTION

1. Set and keep "OSEN" on the DIP switch to OFF. Setting it to ON can get failed or
malfunctioned.

2. When you set "BUSOFF" on the DIP switch to OFF, transmission will restart
automatically even when busoff occurs. Unless the cause of the DN211's busoff
(cause of communication error) is solved, however, busoff may get repeated.

3. When you set both of communication rate DR0 and DR1 to ON and turn on the power
of the T2/T2E/T2N, "Communication Rate Setting Failed" will appear with the
following indications:

• The "MS" LED is blinking red.

• "F7" and the local station node address are being displayed alternately on the

7-segment LED.

To clear these indications, set DR0 and DR1 correctly and, issue a reset request or

turn OFF and ON the power.

4. Set the communication rates of your nodes being connected to the network, to the
same communication rate. Setting different communication rates on your

different nodes will cause slave devices or the DN211 to get malfunctioned,
resulting in no communication started.

Read the relevant manuals and descriptions to set the communication rate of your

slave devices.

5. Don't change over the communication rates while your T2/T2E/T2N is rising just after
the turning on power. In particular, never change the communication rate while
communicating with slave devices. Failing to do so will cause "Communication Rate
Setting Failed" to appear.

To clear this indication, set the DIP switch to the correct setting and, issue a reset

request or turn OFF and ON the power.

3.2.1 DIP Switch for Setting the Operation Mode/Communication Rate

 4 

Safety Precautions (continued)

•

Rotary switch for setting the node address

CAUTION

1. When you set a value within 64 to 99 to the node address of your DN211 and turn ON
the power of your T2/T2E/T2N, "Node Address Setting Failed" will appear with the
following indications:

• The "MS" LED is blinking red.

• "F6" and the local station node address are being displayed alternately on the

7-segment LED.

To clear these indications, set the correct value to the node address and, issue a

reset request or turn OFF and ON the power.

2. If your DN211 node address has the same value with another node and when the
DN211 comes into run state, "Node Address Duplicated" will appear with the following
indications:

• The "MS" LED is lighting red and/or the "NS" LED is lighting red.

• "70" and the local station node address are being displayed alternately on the

7-segment LED.

6 F 3 B 0 3 6 4

To clear these indications, set the correct value to the node address and, issue a

reset request or turn OFF and ON the power.

3.2.2 Rotary Switch for Node Address Setting

•

Mounting in the base unit

CAUTION

1. Since the DN211 is designed for Toshiba's T2 series, be sure to mount your
DN211 in the base unit, instead of using it in stand-alone; don't use it for other
applications. Unauthorized applications can cause electric shock, bodily injury,
and/or mechanical malfunction.

2. Be sure to turn OFF the power (on the T2 side and network side) before attaching or
detaching the DN211 and/or the terminal block. Failing to do so will cause electric
shock, malfunction, and/or failure.

3. Keep the DN211 free from foreign matter such as electric-wire waste. Failing to do so
could cause fire, failure, and/or malfunction.

4. Check the connectors, cables, and base unit of the DN211, for their firm connection
and mounting using stoppers and screws. Note loose connection or mounting can be
shaky or easily disconnected off, resulting in failure or malfunction of the DN211.

3.3 Mounting in the Base Unit

 5 

Safety Precautions (continued)

•

Connection with the network

CAUTION

1. Don't engage in attaching or detaching the DeviceNet cable with the network side
connector during network operation. Failing to do so can cause reverse connection
or short circuit of the network power, resulting in no communication with other nodes.

2. When you connect the DeviceNet cable with the network side connector, be sure not
to make the wrong connection. Failing to do so can cause short circuit of the network
power, resulting in no communication with other nodes.

3. Neither attach nor detach the network side connector with the device side connector
on the DN211 front panel while T2/T2E/T2N is rising just after the power is turned ON.
Failing to do so can cause the DN211 to fail or malfunction.

4. Attaching the opposite end of the network side connector with/from the device side
connector is not possible because of the specific form. Trying connecting the wrong
end by excessive force can damage both the network side connector and the device
side connector.

6 F 3 B 0 3 6 4

5. Be sure not to wire the cable in too tightly stretched state or in bent state.

Also, don't put heavy stuff on the cable. Otherwise, the cable could break.

6. Ask the qualified expert for the installation work of the DeviceNet cables because it
requires sufficient safety and noise-suppression measures. Refer to DeviceNet
Volume I, Release 1.3, for the standard installation.

3.4 Connection with the Network

 6 

Safety Precautions (continued)

•

Turning ON/OFF the power of master/slave and the network

CAUTION

1. Be sure to turn ON the network power before turning ON the power of the DeviceNet
devices.

Some nodes of the slave devices use the network power as the operation power while

other slave devices indicate an error when their work power is not supplied.
Therefore, be sure to switch ON the network power. Also note unless the network
power is switched ON, your DN211 cannot start communication with slave devices.

2. Be sure the network power is supplied to all the nodes being connected with the
network. The node to which no network power is supplied could cause
communication obstacle to other nodes.

3. Make sure the power of all slave devices is switched ON before the DN211 begins
communication. When the DN211 begins communication while the power of a slave
device is not switched ON, the DN211 will display an error message of no response
from that device.

6 F 3 B 0 3 6 4

4. While network communications are operating, don’t shut OFF the network power.
Failing to do so will cause the entire network communications to stop and, one of the
nodes become busoff state.

5. Switch OFF the T2/T2E/T2N side power at last after the DN211 begins
communications. This helps the master device (DN211) to be recognized from the
network and prevents slave devices from malfunctioning.

3.5 The Network Power/Grounding

 7 

Safety Precautions (continued)

Relating to the following sections:

•

How to handle your DN211 (software)

•

Examples of DN211 applications

•

RAS information

CAUTION

1. Chapter 4 describes the subjects necessary for using diverse functions of the DN211
from the T2/T2E/T2N. Chapter 5 describes, based on the subjects explained in
Chapter 4, setting the DN211 parameters, activating transmission,
inputting/outputting data with slave devices, and the procedure for reading RAS
information including event history, and sample programs.

Write programs after understanding the contents. As sample programs are basic,

you need to examine your programs from beginning to end before applying them to
actual systems.

6 F 3 B 0 3 6 4

4. How to Handle Your DN211 (software)

5. Examples of DN211 Applications

6. RAS Information (except RAS area on communication memory)

•

Allocation of slave device data to input/output data area

CAUTION

1. When a slave device has odd transmission/reception bytes in size, the actual size
plus 1 byte are allocated to the DN211 input/output area.

2. When you add a new slave device, enter a new value larger than the node addresses
of the present slave devices. For Figure 4.8, enter a value larger than "41" for the
node address of a new slave. If the node address of a new slave device is set to "18",
allocating data area of node addresses 20/30/40 will be shifted.

3. Don't change the input/output data size for slave devices (FLEX-I/O, etc.) which are
flexible in data allocation size. If changed, the slave devices with a node address
larger than that of the slave device changed data size will be shifted in their data
allocation.

4.4 Allocating Slave Device Data to the Input/Output Data Area

•

Operating mode of the T2/T2E/T2N and the DN211

CAUTION

1. If the T2/T2E/T2N turns into HALT/ERROR mode, the DN211 in run mode becomes
standby mode.

4.6.1 DN211 Operation Mode

5. Examples of DN211 Applications

 8 

Safety Precautions (continued)

•

Action when your DN211 is reset

CAUTION

1. Neither issue a request from the T2/T2E/T2N to DN211 while the DN211 is being
reset nor execute data input/output. Otherwise, the instruction requested will be
completed abnormal (error of station mode abnormal), or the module self-check will
fail turning into down mode.

•

Setting slave device parameters

CAUTION

1. The parameter setting request (slave device) sets the parameters of slave devices
on to the non-volatile memory in the DN211. As long as the slave devices
configuration is unchanged, you don’t need to execute this request every time when
the power is switched ON. In addition, when the parameters of the slave device
requested and the parameters of the slave device in the non-volatile memory are
same, this setting request is not executed.

6 F 3 B 0 3 6 4

[4.6.2 Reset Request]

2. When the slave devices configuration needs to be changed, delete the salve devices
parameters using a reset request before setting new slave devices parameters.

3. The number of times available for setting slave devices parameters in the non­volatile memory of the DN211 is 300 times.

4. The DN211 has the following restriction for transmitting "0 byte" to a slave device
from the DN211.

• When a slave device comes into no communication state with the DN211 due to

some reason (for example, the power of the slave device is OFF; the connector is
disconnected, etc.), the DN211 cannot recognize the slave device is abnormal.
Even after the cause of the failed communications is solved, the DN211 and the
slave device cannot communicate with each other.

Note: The above restriction of the present DN211 will be solved by a version-up of the
internal software.

4.6.4 Parameter Setting Request (slave device)

•

Installation environment and mounting in the base unit

CAUTION

1. Apply the environment specified in the User’s Manual of the T2/T2E/T2N.

When using your DN211 in the environment other than specified, the DN211 can

cause electric shock, fire, failure, and/or malfunction.

2. Mount your DN211 in the way specified in the User’s Manual of the T2/T2E/T2N.

If mounted in the direction other than specified or if mounted incorrectly, the DN211

could fall off, or cause fire, failure, and/or malfunction.

8.1 Installation Environment and Mounting in the Base Unit

 9 

Safety Precautions (continued)

•

Mounting/removing the module

CAUTION

1. Since the DN211 is designed for the T2 series, be sure to attach it to the base unit.
Don't use your DN211 in stand-alone state or to other applications.

Failing to do so could cause electric shock, injury, and/or failure.

2. Be sure to turn OFF the power before mounting, removing, wiring, or un-wiring the
DN211. Failing to do so can cause electric shock, malfunction, and/or failure.

3. Keep your DN211 free from foreign matter such as electric-wire waste. Failing to do
so could cause fire, failure, and/or malfunction.

4. Check the connectors and cables and the DN211 mount in the base unit, for their firm
connections and mount using stoppers/screws. Loose connection and mounting
becomes shaky and disconnected, resulting in failure or malfunction.

8.2 Mounting/Removing the Module

6 F 3 B 0 3 6 4

•

Wiring the power and grounding

CAUTION

1. Be sure to turn OFF the power before wiring cables. Failing to do so could cause
electric shock.

2. Use crimp-on connectors with sheath or cover the conducting part with tape when
wiring your T2/T2E/T2N power module. Also, handle the terminal block cover
correctly to avoid fall-off and damage when fixing. Be sure to fix the cover on the
terminal block when completing the wiring. If the conducting part is exposed, you can
have electric shock.

3. Be sure to have grounding. When not grounded, electric shock and/or malfunction
can occur.

4. Make sure the wiring is correct when connecting the DeviceNet cables to the network
side connector. The short circuit of the network power, etc. can fail communication
with other nodes.

5. When you are going to detach or connect the network side connector to/from the
device side connector on the DN211 front panel, don't engage yourself while the
T2/T2E/T2N side power is rising. Failing to do so can cause the DN211 to fail or
malfunction.

6. Attaching the opposite end of the network side connector with/from the device side
connector is not possible because of the specific form. Trying connecting the wrong
end by excessive force can damage both the network side connector and the device
side connector.

7. Ask a qualified person to wire cables. Incorrect wiring can cause fire, failure, and/or
electric shock.

8.3 Power Unit Wiring/Grounding

 10 

Safety Precautions (continued)

•

Basic caution in network Installation

CAUTION

1. Ask the qualified subcontractor for sufficient safety and noise-suppression
measures when installing the DeviceNet cable.

Refer to DeviceNet Volume I, Release1.3, for the standard installation.

2. It is recommended to consign a subcontractor specialized in safety measures and
standards.

3. Avoid the network components of the DeviceNet cable from being installed in a noisy
environment. When installing, be sure to furnish noise-suppression measures as
described in the following section.

•

Maintenance

6 F 3 B 0 3 6 4

8.4 Network Installation

CAUTION

1. Be sure to turn OFF the power mounting or removing the module, terminal block, and
cable. Failing to do so can cause electric shock, malfunction, and/or failure.

2. Carry out daily check, periodical check, and cleaning to keep the system in normal
condition.

3. If your DN211 does not operate normally, refer to "7. Troubleshooting" to identify the
cause of the trouble.

Contact a Toshiba's branch office (or dealer) or service agency for returning your

DN211 for repair when failed. Operation and safety of your DN211 can be
guaranteed only when repaired by Toshiba or a Toshiba's authorized service
agency.

4. Neither try to disassemble nor modify the hardware of the module. Similarly, don't
modify the software by any means. Failing to do so could cause fire, electric shock,
and/or injury due to failure or malfunctioning.

5. Make sure you are safe when measuring the voltage on the connector of the module.

Failing to do so could cause electric shock.

6. Stop the network and turn OFF the T2/T2E/T2N side power before replacing the
module.

Failing to do so could cause electric shock, malfunction, and/or failure.

7. Don't use your DN211 in abnormal condition such as smoking or nasty smelling.

Failing to do so could cause fire, electric shock, and/or failure.
If such an abnormal condition happens, turn OFF all the power supplies immediately

and contact a Toshiba branch office (or dealer) or authorized service agency.

Since it is very dangerous, don't engage yourself in modifying or repairing your

DN211 by any means.

Appendix (maintenance)

 11 

Usage Recommendations

Usage Recommendation

This section puts together the knowledge and handling manners necessary for correct operation.
Read the section carefully and be familiar with equipment knowledge, safety information, and
notes.

•

Network cnfiguration

Usage Recommendation

1. Don't make a network configuration whose extended trunk line and drop lines have
no node being connected.

2. Don't attach a terminal resistor to the node. It could cause communication error.

3. Attach a terminal resistor to both ends of the trunk line; don't attach a terminal
resistor on the end of a drop line. Attach only to both ends of the trunk line.

1.2 Network Configuration of the DeviceNet

6 F 3 B 0 3 6 4

•

Switch setting

Usage Recommendation

1. Use a small minus screwdriver for changing the value of the DIP switch.

3.2.1 DIP Switch for Setting the Operation Mode/Communication Rate

Usage Recommendation

1. Use a small minus screwdriver for changing values of the rotary switch.

3.2.2 Rotary Switch for Node Address Setting

•

Connecting your DN211 with the network side connector

1. Loosen the cable fixing screws on the connector before inserting a cable into the
network side connector. The cable cannot be fixed when the screws are kept
tightened.

2. Colors corresponding to cable colors are printed by the device side connector of the
DN211. Match the cable colors with the printed colors to have correct wiring.

3. The DN211 and the DN311 (DeviceNet module for T3/T3H) have different directions
for attaching the network side connector.

4. DeviceNet cable, power tap, and device tap (connecting the trunk line with drop
lines) are necessary when constructing a system using a DeviceNet. Refer to "3.6
The Network Components" for detail.

Some of the network components must be prepared by the user.

5. When you use the network side connector that has the upper and lower rows with
holes for cables (at the left-side Figure 3.5), the connector protrudes from the left­side DN211 about 5mm. When you attach or detach the left-side module of DN211,
you must detach the connector from DN211.

3.4.2 Connecting Network Side Connector to the DN211

 12 

Usage Recommendations (continued)

•

Network power configuration

Usage Recommendation

1. Consider not only current capacity of the trunk line but also current capacity of drop
lines when you install a node on a drop line.

2. In particular, when you are connecting nodes in daisy chain on a drop line, be careful
not to have insufficient current capacity.

3. Use a network power whose capacity is much larger than the total current
consumption necessary for the network.

3.5.2 How to Configure Network Power Units

•

Network power unit

Usage Recommendation

6 F 3 B 0 3 6 4

1. Use a network power whose capacity is much larger than the total current
consumption necessary for the network.

3.5.3 The Network Power Unit(24Vdc)

•

Registering your DN211 module

Usage Recommendation

1. When your DN211 is going to be I/O registered in the T2/T2E/T2N, leave blank for
the slot where the DN211 is installed.
After automatic allocation is performed, the DN211-installed slot is left blank.

4. How to Handle Your DN211 (software)

•

Node address of your DN211

Usage Recommendation

1. Set the node address of your DN211 to a value smaller than the node addresses of
slave devices(because of the feature of CAN currently used in the DeviceNet).

4.6.3 Parameter Setting Request (local node)

•

How to solve overrun errors

Usage Recommendation

1. Reduce the network communication speed when an overrun error occurs (500 kbps

-> 250 kbps -> 125 kbps).

7. Troubleshooting (Data Communication with Slave Devices)

 13 

About This Manual

Thank you for purchasing Toshiba's programmable controller PROSEC-T2 series (T2/T2E/T2N).
This manual describes the specification, handing manners, and sample programs of the DeviceNet

module (called as the "DN211") used for PROSEC-T2 series. Read this manual to handle and
operate your DN211 correctly.

This manual consists of the following chapters:

Chapter 1: Overview of the DeviceNet Module

Outlines functions of the DN211, specification, and application systems, etc. Read this chapter to
know basic performances of the DN211.

Chapter 2: Names and Functions of DN211 Parts

Describes the names and functions of DN211 parts. Read this chapter carefully since important
information, required for hardware settings in the next chapter, is included in this chapter.

6 F 3 B 0 3 6 4

Chapter 3: Preparation for Operation (hardware)

Describes the hardware preparation and setting necessary for your DN211 operation.

Chapter 4: How to Handle Your DN211 (software)

Explains accessing the DN211 from the T2/T2E/T2N and software settings.

Chapter 5: Examples of DN211 Applications

Describes sample programs of handling the DN/211 explained in Chapter 4.

Chapter 6: RAS Information (except RAS area on communication memory)

Describes the formats and contents of RAS information on the DN211 (except for RAS area on
communication memory).

Chapter 7: Troubleshooting

Explains possible causes and solutions when your DN211 malfunctions.

Chapter 8: Installation/Wiring Work

Explains how to install your DN211 and T2/T2E/T2N, how to wire transmission cables, and how to
arrange other preparation work.

Appendix

Describes the maintenance and check items and the execution time of READ/WRITE instructions
of the T2/T2E/T2N.

 14 

6 F 3 B 0 3 6 4

In addition to this instruction manual, the following descriptions about the T2/T2E/T2N, instruction
words, programmer, and computer link procedure transmission are also prepared for your reading.

• T2 User’s Manual Basic Hardware and Function (UM-TS02***-E001)

Describes hardware (basic unit, basic I/O) and the main unit functions of the T2.

• T2E User’s Manual Basic Hardware and Function (UM-TS02E**-E001)

Describes hardware (basic unit, basic I/O) and the main unit function of the T2E.

• T2E User’s Manual Enhanced Communication Function(UM-TS02E**-E003)

Describes the functions and how to handle the optional communication card for the T2E.

• T2N User’s Manual Basic Hardware and Function (UM-TS02N**-E001)

Describes hardware (basic unit, basic I/O) and the main unit functions of the T2E.

• Instruction Manual TOSLINE-S20LP T2N/T3H Stations (6F3B0356)

Describes the system configuration of the T2N built-in data link system "TOSLINE-S20LP"
and its device configuration, and the functions, performances, and handling of "TOSLINE­S20LP."

• Built-in Ethernet Module for T2N (PU235N/245N) Instruction Manual (6F3B0362)

Describes the Ethernet built-in T2N and the handling.

• T-Series Instruction Set (UM-TS03***-E004)

Explains a detailed specification of instruction words about the ladder diagram and SFC
programming languages, which are supported by Toshiba's T-series.

• T-Series Computer Link Operation Manual (UM-TS03***-E008)

Describes the specification and operating manners for the computer link function built in
Toshiba's T-series CPU.

Registered Trademarks:

n DeviceNet is a registered trademark of ODVA (Open DeviceNet Vendor Association).
n PowerTap, T-Port Tap, DeviceBox Tap, and FLEX I/0 are registered trademarks of RockWell

Automation Co., Ltd.

n COMBICON is a registered trademark of Phoenix Contact Corporation.

 15 

Contents

1. Overview of The DeviceNet Module ..................................................................19

1.1 Features and System Configuration Examples of the DeviceNet Module (DN211)19

1.2 Network Configuration of DeviceNet..................................................................21

1.3 Conformity Specification and Trademarks .........................................................25

1.4 The Basic Functions ...........................................................................................26

1.5 The DN211 Specification ....................................................................................30

6 F 3 B 0 3 6 4

1.2.1 The Network Configuration .......................................................................21

1.2.2 Trunk Line/Drop Line and Maximum Cable Length...................................22

1.2.3 The Terminal Resistor ..............................................................................24

1.4.1 The Polling Instruction/Response Mode...................................................26

1.4.2 The Bit Strobe Instruction/Response Mode..............................................27

1.4.3 Synchronization/Asynchronous Mode and Data Update Cycle .................28

1.5.1 The Function Specification .......................................................................30

1.5.2 Number of Mounting Modules ...................................................................31

2. Names and Functions of DN211 Parts.............................................................33

2.1 Outer Dimensions and Sizes ..............................................................................33

2.2 Names of DN211 Parts........................................................................................34

2.3 Functions of DN211 Parts....................................................................................36

3. Preparation for Operation (hardware)...............................................................38

3.1 DN211 Setting Flowchart (hardware)..................................................................38

3.2 Switch Setting ....................................................................................................39

3.2.1 DIP Switch for Setting the Operation Mode/Communication Rate .............39

3.2.2 Rotary Switch for Node Address Setting ...................................................41

3.3 Mounting in the Base Unit ..................................................................................42

3.4 Connection with the Network.............................................................................43

3.4.1 Connecting DeviceNet Cables to Network Side Connectors.....................44

3.4.2 Connecting the Network Side Connector to the DN211............................45

3.5 The Network Power/Grounding ..........................................................................47

3.5.1 The Network Power Mechanism................................................................47

3.5.2 How to Configure Network Power Units .....................................................48

3.5.3 The Network Power Unit (24 Vdc) .............................................................54

3.5.4 The Network Grounding ...........................................................................55

3.5.5 Procedure for Switching-ON/Shutting-OFF the Power ..............................56

3.6 The Network Components.................................................................................57

4. How to Handle Your DN211 (software).............................................................60

4.1 Configuration of the DN211 Communication Memory .........................................61

4.2 The Input/Output Data Area................................................................................62

4.3 The RAS Information Area .................................................................................66

 16 

6 F 3 B 0 3 6 4

4.4 Allocating Slave Device Data to the Input/Output Data Area..............................75

4.5 The Semaphore Area .........................................................................................76

4.6 Requests to the DN211 ........................................................................................79

4.6.1 The DN211 Operation Modes...................................................................80

4.6.2 Reset Request .........................................................................................81

4.6.3 Parameter Setting Request (local node) ..................................................82

4.6.4 Parameter Setting Request (slave device)...............................................85

4.6.5 Operation Mode Control Request.............................................................88

4.6.6 RAS Information Read Request................................................................89

4.6.7 Time Setting Request ...............................................................................90

4.7 Completion Status..............................................................................................91

5. Example of DN211 Applications.........................................................................92

5.1 The DN211 Operation Order...............................................................................92

5.2 Module Setting Procedure .................................................................................93

5.2.1 Accessing the DN211 in Module Setting ...................................................94

5.2.2 Configuration of a Module Setting Sample Program.................................96

5.2.3 Reset Request .........................................................................................97

5.2.4 Parameter Setting Request (local node) ..................................................99

5.2.5 Parameter Setting Request (slave device).............................................100

5.2.6 Operation Mode Control Request...........................................................106

5.2.7 RAS Information Read ............................................................................111

5.2.8 Time Setting Request .............................................................................114

5.3 Slave Data Input/Output................................................................................... 116

5.3.1 Slave Device Check ...............................................................................116

5.3.2 Asynchronous Mode Data Input/Output..................................................117

5.3.3 Synchronous Mode Data Input/Output ...................................................122

6. RAS Information (except RAS area on communication memory)..........129

6.1 Module Status / Network Status LED (MS/NS)................................................... 130

6.2 Indications of the 7-Segment LED ....................................................................131

6.3 RAS Information Reading Data ........................................................................ 133

6.3.1 The RAS Counter ...................................................................................133

6.3.2 Event History..........................................................................................136

6.3.3 Execution Node Information ....................................................................139

7. Troubleshooting..................................................................................................141

7.1 When Starting up the Module .......................................................................... 141

7.2 Reset Request (scan list clear).......................................................................... 142

7.3 When the Module Doesn't Become Run Mode ................................................. 143

7.4 Data Communication with Slave Devices......................................................... 146

 17 

6 F 3 B 0 3 6 4

8. Installation/Wiring Work.....................................................................................148

8.1 Installation Environment and Mounting in the Base Unit.................................. 148

8.2 Mounting/Removing the Module ...................................................................... 148

8.3 Power Unit Wiring/Grounding.......................................................................... 149

8.3.1 Power Unit Wiring...................................................................................149

8.3.2 Grounding..............................................................................................149

8.4 Network Installation ......................................................................................... 150

8.4.1 Installation Gists Outside the Board .......................................................150

8.4.2 Installation Gists Inside the Board ..........................................................153

Appendix

Appendix 1 Maintenance and Inspection......................................................154

Appendix 2 READ/WRITE Instruction Execution Time ..................................156

Appendix 3 DN211A ..……….………………………………………………………...157

 18 

6 F 3 B 0 3 6 4

1. Overview of the DeviceNet Module

1.1 Features and System Configuration Examples of the DeviceNet Module (DN211)

This section describes the features and system configuration examples of the DeviceNet module
(DN211) for the programmable controller PROSEC-T2 series (T2/T2E/T2N). The DN211 is an
interface module for connecting the DeviceNet, which is a device level network for FA, to the
PROSEC-T2 series.

Hereafter, the programmable controllers PROSEC−T2, PROSEC-T2E, and PROSEC-T2N are
respectively called the "T2", "T2E", and "T2N". Likewise, the DeviceNet module for the T2 series
is also called the "DN211."

(1) Conformed with DeviceNet

DeviceNet is a standardized device level network for factory automation(FA), developed by
RockWell Automation Co. in USA. A nonprofit organization, called ODVA (Open DeviceNet
Vendor Association), is serving as the center for the maintenance/extension of the DeviceNet
specification and for conformable products introduction.

The DN211, functioning as the master (parent station) device on a DeviceNet, performs data
input/output between the master device and the DeviceNet slave (child station) devices, which are
developed by different makers (vendors) in and outside Japan and conform with the DeviceNet, to
interface such slave devices with the T2/T2E/T2N .

(2) Input/Output Data Size, Number of Slave Devices, communication Rate and Network

Length

A DN211 allows a DeviceNet to have one network to be connected. The sizes of inputting and
outputting data, allowed between a DN211 and slave devices are 128 words for input and 128
words for output (one word = 16 points).

Input data and output data, so far as each of them is within 128 words in total, can be exchanged
data with up to 63 slave devices. (Since the amount of data outputted to a slave device and the
amount of data inputted from a slave device vary depending on the slave device, check the slave
device specification of data size).

The definition of input data and output data, dealt in this book, is shown in the following figures.

Output data : T2/T2E/T2N → DN211 → Slave device

Input data : T2/T2E/T2N ← DN211 ← Slave device

Figure 1.1 Definition of Output Data and Input Data

Three types of communication rates, namely 500 kbps, 250 kbps and 125 kbps are available. The
maximum network length varies depending on the communication rate (l00 m for 500 kbps, 250 m
for 250 kbps, and 500 m for 125 kbps).

The detail is explained in "1.2 Network Configuration of DeviceNet."

 19 

(3) Means of Inputting/Outputting Data

1

Input/Output

Input/Output

Input/Output

The DN211 supports "polling instruction/response" and "bit strobe instruction/response," both of
which are specified in the DeviceNet specification as the means of inputting/outputting data
to/from slave devices. The details of "polling instruction/response" and " bit strobe
instruction/response" are explained in "1.4 The Basic Functions."

(4) Examples of the System Configuration

This section describes a typical system configuration using the DN211, which is mounted on the
I/O slot of the T2/T2E/T2N. The DN211 allows the T2/T2E/T2N to exchange data with slave
devices on the DeviceNet.

In the following example, the DN211 is connected with slave devices, such as input/output devices,
sensor, and drive unit, which conforms with the DeviceNet specification. Moreover, a Toshiba's
original control LAN (TOSLINE-S20) is used to connect the T2/T2E/T2N with a higher-rank
controller.

A number of wiring combinations meeting the installation environment are available because the T
branch topology and the multi-drop topology are combinable when wiring a DeviceNet.

High-rank computer

T2N: PROSEC − T2N
T2E: PROSEC − T2E
S20: TOSLINE − S20

6 F 3 B 0 3 6 4

S

T

2

2

0

E

DeviceNet

device

Input/Output device

Sensor

Ethernet

TOSLINE−S20

D

T

2

N

D

N

N

2

2

1

1
1

DeviceNet

device

Sensor

Drive unitDrive unit

Sensor

device

Figure 1.2 Example of the System Configuration

 20 

1.2 Network Configuration of DeviceNet

Terminal

resistor

Terminal

resistor

This section describes the network configuration of the DeviceNet.

1.2.1 The Network Configuration

The network configuration of a DeviceNet consists of a trunk line and drop lines as shown in Figure

1.3.

(1) The Nodes

The nodes of the DeviceNet in Figure 1.3 have slave devices such as input/output devices, sensors,
and drive units, and a master device such as the DN211, to exchange data with each other. One
network can have up to 64 nodes and one master device. Physical arrangement of a master device
and slave devices has no particular restrictions.

Each of the DeviceNet devices on a network has a unique number (NA: node address) to identify
the node from the other nodes. The node address values must be within 0 to 63 in decimal scale,
and the node addresses in the network must be different from the others.

(2) The Trunk Line

According to the DeviceNet specification, a trunk line is a cable which connects nodes located
most distant. The trunk line can have nodes directly-connected with it (connection with no drop
line). The length of the trunk line varies depending on the communication rate of the network. The
both ends of the trunk line need a terminal resistor.

6 F 3 B 0 3 6 4

(3) The Drop Line

All the cables branched from taps on the trunk line fall on drop lines. The drop line has a maximum
length of 6 meters (from tap to most distant node) regardless of the communication rate on the
network (The total extension of drop lines varies depending on the communication rate on the
network). A drop line can have one or more nodes connected. The following three types of node
configurations are available, as shown in Figure 1.3.

a) Configuration of drop lines short from the tap/multiport tap
b) Configuration of multidrops on a drop line
c) Configuration of branches on a drop line (no branch configuration for the trunk line)

Branch configuration

Node 35

Node 30

Node 0

Node 45

Node 40

Multiport tap

Tap

Tap Multiport tap

Tap

Node 50

Node 55

Node 60
Multidrop

configuration

No drop line

Node

25

Node 5

Node

10

Node

15

Short drop line configuration

Node

20

Figure 1.3 Example of DeviceNet Network Configuration

 21 

Trunk line
Drop line

1.2.2 Trunk Line/Drop Line and Maximum Cable Length

Terminal

resistor

Short drop line configuration

Terminal

resistor

The DeviceNet specification stipulates the Thick Cable and the Thin Cable. For detail, see
DeviceNet Volume I. Currently, cables conforming with the standards of the Thick Cable and Thin
Cable are available in the commercial market. Buy ones which meet the configuration of your
network (Details are explained in "3.6 The Network Components").

(1) The Trunk Line

The trunk line of a DeviceNet consists of a Thick Cable or a Thin Cable (their mixture is also
possible). Since the Thin Cable is flexible compared with the Thick Cable, wiring the cable is easy.
Conversely, the Thick Cable allows longer network cabling than the Thin Cable. A maximum of the
trunk line length varies depending on the type of cable used and the communication rate on the
network. For details, see "3 The Maximum Network Length."

(2) The Drop Line

The drop lines of a DeviceNet consists of Thin Cables. Table 1.1 lists the length of drop lines and
the total length. A node on a drop line can be configured in a short drop line configuration/multi­drops configuration/short brunch configuration. Figure 1.4 shows how to calculate the drop line
length and the total length by different configurations.

Table 1.1 Maximum Drop Line Length

6 F 3 B 0 3 6 4

Communication
Rate

125 kbps 156 meters
250 kbps 6 meters 78 meters
500 kbps 39 meters

Branch configuration

Node 35

Node 30

Node 0

Node 45

i

Node 5

Node 40

Drop Line Total Extension by Network

Multiport tap

g

f

h

Tap Multiport tap

a

Node

10

Node

15

Tap

b

Node

20

e

d

c

Node

25

Tap

Node 50

Node 55

Node 60
Multidrop

configuration

Individual drop line length: a ≤ 6 m, b ≤ 6 m, c ≤ 6 m, and d ≤ 6 m (short drop line configuration)

e ≤ 6 m (multi-drops configuration)
f + g ≤ 6 m, f + h ≤ 6 m, f + i ≤ 6 m (branch configuration)

Total of drop lines extended : a + b + c + d + e + f + g + h + i

Figure 1.4 Example of Calculating the Drop Line Length

 22 

(3) The Maximum Cable Length

Terminal

Terminal

Terminal

Terminal

The distance between two nodes on the network cannot exceed the "Maximum cable length"
specified in the DeviceNet specification. In Figure 1.4, the distance from node 0 to node 60 is not
allowed to exceed the "Maximum cable length."

The "Maximum cable length" varies depending on the communication rate of the
network and the type of the cable used for the trunk line.

a) Table 1. 2 lists the maximum cable length for the case that the trunk line consists of a Thick

Cable alone and no drop line is connected on it (that is, all nodes are connected on the trunk line),
as shown in Figure 1.5. In this case, "maximum trunk line length between node 0 and node n" =
"maximum cable length."
Moreover, when the "maximum trunk line length between node 0 and node n" = "maximum
cable length," no new node can be attached outside node 0 and node n..

6 F 3 B 0 3 6 4

resistor

Figure 1.5 Distance Between Two Nodes on a Network With No Drop Line

Table 1.2 Maximum Cable Length (Thick Cable/Thin Cable alone)

Communication
Rate

125 kbps 500 m 100 m
250 kbps 250 m 100 m
500 kbps 100 m 100 m

Distance between two nodes ≤ Maximum cable length

• • • • • • • • •

Thick Cable
alone

Thin Cable alone

Node nNode 3Node 2Node 0

resistor

b) Figure 1.6 shows the maximum distance between two nodes in the case that a Thick Cable

or Thin Cable alone is used for the trunk line and that drop lines are used.
Table 1.2. lists the maximum cable length. In this case, the "maximum trunk line length
between two nodes" is as follows:

Maximum trunk line length between two nodes

= Maximum cable length

(value in Table 1.2)

− Total length of drop lines for both ends nodes of trunk line

For Figure 1.6, the maximum trunk line length between node 0 and node n is equal to the
maximum cable length (value in Table 1.2) minus total length of drop lines for node 0 and
node n.

resistor

Node 0

Distance between two nodes ≤ Maximum cable length

Node 3Node 2

 23 

• • • • • • • • •

Node n

resistor

6 F 3 B 0 3 6 4

Figure 1.6 Distance Between Two Nodes on a Network with Drop Lines

 24 

6 F 3 B 0 3 6 4

Terminal

Terminal

c) Figure 1.7 shows the maximum distance between two nodes in the case that the trunk line

consists of Thick Cable and Thin Cables and that drop lines are connected. Use the formulas in
Table 1.3. for calculating the maximum cable length.

In this case, the "maximum trunk line length between two nodes" is represented in the
following formula:

Maximum trunk line length between two nodes

= Maximum cable length (value in Table 1.3)

− Total length of drop lines for the nodes at

both ends of trunk line

For Figure 1.7, the maximum trunk line length between node 0 and node n is equal to the
maximum cable length (value in Table 1.3) minus the total length of the drop lines for node 0 and
node n.

Distance between two nodes ≤ Maximum cable length

resistor

Figure 1.7 Distance Between Two Nodes on a Network with Drop Lines

Table 1.3 Maximum Cable Length (Mixture of Thick Cable/Thin Cable)

Communication
Rate

125 kbps L-thick + 5 × L-thin ≤ 500 m
250 kbps L-thick + 2.5 × L-thin ≤ 250 m
500 kbps L-thick + L-thin ≤ 100 m

L-thin: Length of trunk line using thin cable (m)
L-thick: Length of trunk line using thick cable (m)

1.2.3 The Terminal Resistor

The DeviceNet needs a terminal resistor on both ends of the trunk line in order to reduce signal
reflections and stabilize communications. The specifications of the terminal resistor are as follows:

L-thin L-thick

• • • • • • • • •• • • • • • • • •

Calculation Formula

resistor

Node nNode 3Node 0

• 121Ω

• 1% of the metal film

• 1/4 W

Terminal resistors conforming with the above specifications are available in the commercial market.
See "3 .6 The Network Components."

Usage Recommendation

1. Don't make a network configuration whose extended trunk line and drop lines have no node
being connected.

2. Don't attach a terminal resistor to the node. It could cause communication error.

3. Attach a terminal resistor to both ends of the trunk line; don't attach a terminal resistor on the

 25 

end of a drop line. Attach only to both ends of the trunk line.

6 F 3 B 0 3 6 4

 26 

1.3 Conformity Specification and Trademarks

DeviceNet is a standardized device level network for factory automation (FA), which is developed
by RockWell Automation Co., Ltd. in USA. Currently, a nonprofit organization called ODVA
(Open DeviceNet Vendor Association) is serving as the center for the maintenance and extensions
of DeviceNet and introduction of conformable products.

The DeviceNet specification has Volume I: DeviceNet Communication Model and Protocol, and
Volume II: DeviceNet Device Profiles and Object Library, in which the hardware and software
specifications are defined.

The DeviceNet specification that the DN211 conforms with is found in Volume I, Release 1.3, and
Volume II, Release 1.2.

Trademarks:

n DeviceNet is a registered trademark of ODVA (Open DeviceNet Vendor Association).
n PowerTap, T-Port Tap, DeviceBox Tap, and FLEX I/0 are registered trademarks of RockWell

Automation Co., Ltd.

6 F 3 B 0 3 6 4

n COMBICON is a registered trademark of Phoenix Contact Corporation.

 27 

1.4 The Basic Functions

Node identification number that individual DeviceNet
devices have in the DeviceNet network. The values

This section describes the following two functions for communicating between the DN211 and
slave devices.

1) Polling instruction/response mode

2) Bit strobe instruction/response mode

1.4.1 The Polling Instruction/Response Mode

The polling instruction/response mode is used for exchanging an arbitrary size of data between the
master device ⇔ slave devices. The master device has information on slaves devices (items of
scan list, such as node address, input/output data volume, etc.) on the network.

For polling instructions, based on such information, the master device outputs an arbitrary size of
data to slave devices. Slave devices transmit response data (arbitrary data size) to a polling
instruction to the master device (polling response).

It depends on the specification of a slave device how the slave device interprets the polling
instruction and what data the slave device transmits as the polling response. For this
communication function, it is prerequisite that the slave device supports the polling
instruction/response mode. (Almost all the slave devices on the DeviceNet support this
communication system).

6 F 3 B 0 3 6 4

(1) The Polling Instruction

The example in Figure 1.8 indicates the DN211 is polling sensors, inputting sensor input information,
and trying to send output control data to the actuator. How to write polling output data to the
DN211 from the T2/T2E/T2N is found in "5. Communication with Slave Devices."

T2/T2E/T2N

Master

DN211

NA = 1

Slave 1

Proximity sensor

NA = 19

NA (Node Address):

range from 0 to 63 in decimal scale.
In the DeviceNet network, the node addresses of the
devices must be unique and different from each other.

Slave 3

Optoelectronic sensor

NA = 22

Polling responsePolling instruction /

Slave 5
Actuator
NA = 52

Figure 1.8 Example of Polling Instruction/Response Mode

(2) The Polling Response

A slave device which received a polling instruction transmits an arbitrary size of response data to
the master device. The content of response data varies depending on the specification of the slave
device. The mechanism the T2/T2E/T2N reads polling response data from the DN211 is explained
in"5. Communication with Slave Devices."

 28 

1.4.2 The Bit Strobe Instruction/Response Mode

NA = 23

NA = 22

The bit strobe instruction/response mode is used for exchanging a small size of data between the
master device ⇔ slave devices. In the bit strobe instruction, based on the information obtained
from the scan list, the master device broadcasts 1-bit output data to individual slave devices.

These individual devices transmit data (0-8 bytes) in response to the bit strobe instruction to the
master device (bit strobe response).

It depends on the specification of a slave device how the salve device interprets a bit strobe
instruction and what data the slave device transmits to the bit strobe response.

For this communication function, it is prerequisite that the slave device supports the bit strobe
instruction/response mode.

(1) The Bit Strobe Instruction

Broadcasts data to bit strobe instruction/response mode supporting slave devices on the network.
The bit strobe instruction contains 64-bit output data, and each of the 64 bits is assigned to
individual node addresses on the network (Figure 1. 9).

The example in Figure 1.9 indicates the DN211 is inputting sensor information by the bit strobe
mode and trying to send output control data to the actuator. The way of writing output data in bit
strobe from the T2/T2E/T2N to the DN211 is explained in "5. Communication with Salve Devices."

6 F 3 B 0 3 6 4

T2/T2E/T2N

Master
DN211
NA = 1

Slave 1

Proximity sensor

NA = 19

Slave 2

Proximity sensor

NA = 21

Figure 1.9 Example of the Bit Strobe Instruction/Response Mode

(2) The Bit Strobe Response

Slave 3

Photoelectric

sensor

Bit strobe instruction data

Bit number

Slave 4

Photoelectric

sensor

Bit strobe responseBit strobe instruction /

Slave 5
Actuator
NA = 52

• • • •• • • •• • • •

6351 5219 20 21 22 23 240 1

A slave device which received the bit strobe instruction transmits 0 to 8 byte response data to the
master device. The contents of response data varies depending on the specification of the slave
device. The way the T2/T2E/T2N reads bit-strobe response data from the DN211 is described in
"5. Communication with Slave Devices."

 29 

1.4.3 Synchronization/Asynchronous Mode and Data Update Cycle

data

T2N

As explained in the preceding section, the communication function between the DN211 and slave
devices has the polling instruction/response mode and the bit strobe instruction/response mode.
Data can be exchanged between the T2/T2E/T2N and the DN211 in synchronous mode or
asynchronous mode. This section describes the synchronous mode/asynchronous mode.

(1) The synchronous mode

At output: The T2/T2E/T2N writes output data to slave devices into the DN211 beforehand, and

activates a polling instruction/bit strobe instruction. When the polling instruction/bit
strobe instruction is activated, the DN211 sends the output data to slave devices.

At input: The DN211 receives data from slave devices by a polling response/bit strobe response.

After having received data from all slave devices, the DN211 arranges input data
before notifying the input completion to the T2/T2E/T2N. If the T2/T2E/T2N is reading
input data, it will check for the input completion by the DN211 before reading the input
data.

T2/T2E/T2N Data Update Cycle

6 F 3 B 0 3 6 4

T2/
TE2/

DN211

Slave

Output

Input

data

Output
instruction

Output

processing

Response Response

Input
completion

Iutput

processing

Output

data

Output
instruction

Output

processing

Input
completion

Intput

processing

Output data and input data exchanged between the T2/T2E/T2N ⇔ the DN211 are
synchronizing with the output/input cycles of the T2/T2E/T2N side program. For this reason, the
size of synchronous data value is equal to one-time output/input data to all slave devices.

 30 

(2) The asynchronous mode

T2N

data

At output: The T2/T2E/T2N writes output data to slave devices into the DN211. Disregarding the

timing of the T2/T2E/T2N's output data writing, the DN211 sends, by the scanning
cycle at the local station, written output data to a slave device. Unless output data is
updated by the T2/T2E/T2N, the DN211 sends the same data to slave devices.

At input: The DN211 receives data from slave devices by a polling response/bit strobe response.

After having received data from all slave devices, the DN211 updates input data. The
DN211 doesn't notify the completion of the data reception to the T2/T2E/T2N.
Disregarding the timing of input data update by the DN211, the T2/T2E/T2N reads
input data.

T2/T2E/T2N Data Update Cycle

T2/
T2E/

Output

Input

data

DN211 scan

6 F 3 B 0 3 6 4

Output

data

DN211

Slave

Output

processing

Response

Iutput

processing

Output

processing

Response

Intput

processing

Outpu

processing

Response

Intput

processing

Outpu

processing

Transfer of output data and input data between the T2/T2E/T2N ⇔ the DN211 and the transfer
between the DN211 ⇔ slave devices are asynchronous. Transfer between the T2/T2E/T2N ⇔
the DN211 are synchronizes with the scan cycle by the T2/T2E/T2N side, while the transfer
between the DN211 ⇔ slave devices are synchronizes with the scan cycle in the DN211.

Although data are secured by the byte (8 bits), the sequence program is simplified for data transfer
processing, compared with the synchronous mode. When the scan cycle by the DN211 side is
shorter than the scan cycle by the T2/T2E/T2N, delay of data update time between the
T2/T2E/T2N ⇔ slave devices becomes smaller.

The scan time by the DN211 varies depending on the number of slave devices being connected,
size of transmission data by the slave device, and the performances of the slave device being
connected.

 31 

1.5 The DN211 Specification

1.5.1 The Function Specification

Table 1.4 lists the function specification of the DN211. The general specification of the DN211
conforms with the T2/T2E/T2N main unit.

Table 1.4 Function Specification

Item Specification

Module form (pet name) DN211
Transmission specification Conformed with the DeviceNet

Media access system CSMA/NBA system (note)
Modulation Baseband
Transmission path Bus topology
Data rate 125 kbps 250 kbps 500 kbps
Max. network length 500 m 250 m 100 m
Max. number of nodes 64 units/network (1 master device, 63 slave devices)
Connector MSTBP 2.5/5-STF-5.08 AB GY AU SO

Connection cable DeviceNet THICK cable (thick cable)

Communication function 1. Polling instruction/response mode

RAS function 1. Self-check when the power is ON

Current consumption [mA] T2/T2E/T2N side (DC5V): 500 mA

Outer dimensions [mm] 32.5 (W) × 138 (H) × 102.1 (D)
Weight [g] 200
Board specification One slot (slot width)
Mounting T2/T2E/T2N base unit (basic/extension)

Number of modules See "1.5.2 Number of Mounting Modules."
Access READ/WRITE instruction (module control, data input/output)

Note: CSMA/NBA : Carrier Sense Multiple Access with Non-destructive Bitwise Arbitration

6 F 3 B 0 3 6 4

TMSTBP 2.5/5-STF-5.08 AB GY AU
Phoenix Contact Corporation

DeviceNet THIN cable (thin cable)

(synchronous/asynchronous)

2. Bit strobe instruction/response mode
(synchronous/asynchronous)

ROM, RAM, and CAN controllers
DN211 communication memory for T2/T2E/T2N

2. RAS information on the T2/T2E/T2N interface buffer memory

3. Information by reading RAS information

• Event trace

• CAN controller (circuit) information

4. Time setting function

5. Displaying the module status/network status on the 7­segment LED on the front panel

Network side (DC 24 V): 90 mA

I/O slot

 32 

1.5.2 Number of Mounting Modules

This section describes the number of the DN211 units available on the T2/T2E/T2N and the
instruction execution time when accessing the DN211 from the T2/T2E/T2N.

(1) Number of DN211 Units Available

The number of the DN211 units available on the T2/T2E/T2N system varies depending on the
power capacity of the T2 power module and the current consumption of the entire T2/T2E/T2N
system.

Table 1.5 5Vdc Power/Current consumption

Power module (PS261) 5 Vdc power 2500 mA

T2 CPU module (PU224) 5 Vdc current consumption 800 mA
T2E CPU module (PU234E) with optional card 5 Vdc current consumption 800 mA
T2N CPU module (PU245N) with optional card 5 Vdc current consumption 2000 mA

6 F 3 B 0 3 6 4

(when no external 24 Vdc is used)

DN211 5 Vdc current consumption 500 mA

For the T2/T2E:
Number of mounting basic base units: (2500-800) ÷ 500 = 3.4 → 3 units

Number of extended base units: 2500 ÷ 500 = 5 → 5 units
The maximum configuration of the T2 and the T2E is equal to basic base unit × 1 unit + extended

base unit × 3 unit; thus, the number of mounting DN211 units available reaches 18 units.

For the T2N:
Number of mounting basic base units: (2500-2000) ÷ 500 = 1 → 1 unit

Number of extended base units: 2500 ÷ 500 = 5 → 5 units
The maximum configuration of the T2N is equal to basic base unit × 1 unit + extended base unit ×

3 unit; thus, the number of mounting DN211 units available reaches 16 units.

The maximum number of the DN211 units available on your system varies depending on
the number of non-DN211 modules mounted.

 33 

6 F 3 B 0 3 6 4

(2) Instruction execution time when accessing the DN211 from the T2/T2E/T2N

When outputting data to slave devices from the T2/T2E/T2N through the DN211, the WRITE
instruction writes the output data in the DN211 from the T2/T2E/T2N. When inputting data from
slave devices through the DN211, the READ instruction reads from the DN211.

Table 1.6 lists the instruction execution times of the T2/T2E/T2N.
The DN211 has 128 words for the output data area (area where output data to slave devices are

stored) and 128 words for the input data area (area where input data from slave devices are
stored).

Table 1.7 lists the execution times for the WRITE/READ instructions by the T2/T2E/T2N when
accessing 128 words. When input/output data with slave devices is smaller than 128 words, the
instruction execution time becomes shorter.

Conversely, when accessing the output data area/input data area several times, the sum of
instruction execution times increases depending on the number of accessed times (the output data
area/input data area is explained in "4.2 The Input/Output Data Area.")

Table 1.6 READ/WRITE Instruction Execution Time (μs)

T2 T2E/T2N

READ instruction
WRITE instruction

N: Number of transfer words

Table 1.7 Maximum Execution Time for DN211 Access (ms)

READ instruction
WRITE instruction

Total 4.51 2.93

720 + 9.0 × N
721 + 15.0 × N

(128 words for input/output)

T2 T2E/T2N

1.87

2.64

430 + 5.6 × N
427 + 10.6 × N

1.15

1.78

The values in Table 1.7 indicate times for accessing the DN211. When you are mounting more than
one DN211 unit, calculate and total the instruction execution times to access individual

DN211 units.
One unit of T2/T2E/T2N cannot cover the entire DN211 units being mounted when the

total of the sum times necessary for the T2/T2E/T2N's accessing the DN211 units and
the sum time necessary for input, output, and internal processing except for accessing
the DN211 units are larger than the response time that your system requires.
In this case, divide your T2/T2E/T2N to mount DN211 units, depending on your system
configuration.

 34 

6 F 3 B 0 3 6 4

2. Names and Functions of DN211 Parts

This chapter explains the names and functions of DN211 parts.

2.1 Outer Dimensions and Sizes

Figure 2.1 Outer Dimensions and Sizes (unit: mm)

 35 

2.2 Names of DN211 Parts

1 2 3 4

DeviceNet

7-segment LED for node address / error code indication

D N 2 1 1

6 F 3 B 0 3 6 4

Black
Blue

White
Red

MS NS

NA / ERROR

LOADER

ON

1
OSEN
2
BUSOFF
3
DR1
4

LED for module status / network status indication

DIP switch for operation mode / communication rate
setting

Test connector (D-Sub, 9-pin)

Device side connector (connecting the DeviceNet)

Figure 2.2 Appearance (front panel)

 36 

6 F 3 B 0 3 6 4

NA-H NA-L

Rotary switch for setting node addresses

Figure 2.3 Appearance (side view)

 37 

2.3 Functions of DN211 Parts

(1) LED for module status/network status indication (MS/NS)

This LED can light green/red. By making a distinction between green and red and lighting and
blinking, the DN211's module status (MS) and network status (NS) are indicated.

6 F 3 B 0 3 6 4

LED Indication

status

MS Not lit • No power is supplied to the DN211.

Green lighting • The DN211 is operating normally.
Green blinking • The DN211 is reading switch settings.
Red blinking • The DN211 is encountering a recoverable trouble.

Red lighting • The DN211 is encountering a non-recoverable trouble (down

NS Not lit • No power is supplied to the DN211 (check MS).

Meaning of the indication (main trouble)

• Though the power is supplied to the DN211, the module doesn't
become run mode (∗ 1).

When the 7-segment LED for node address/error code indicates the
local station node address, the power is supplied.

→ Switch setting abnormal (DIP switch/rotary switch), etc.

status).
You may need to replace the module.

• Though the power is supplied to the DN211, the module doesn't
become run mode ( ∗ 1); check MS.

• The DN211 is encountering a non-recoverable trouble (down
status); check MS.

• No network power is supplied to the DN211.

Green lighting • The DN211 is normally communicating with slave devices.
Green blinking • No communication between the DN211 and slave devices is

established.

• No slave devices are registered in the DN211.

Red blinking • No communication is established with more than one slave devices.
Red lighting • The DN211 communication is stopped due to busoff (∗ 2).

• Communication is stopped due to the node address duplicated.

(* 1) See " 4.6 Requests to the DN211" for the run mode.
(* 2) Busoff: Individual nodes on the DeviceNet check for abnormal transmission paths; when the local

node is judged to be the cause of the abnormal transmission path, the local node is separated from
the transmission path. This state is called busoff.

 38 

(2) 7-Segment LED for Node Address/Error Code Indication (NA/ERROR)

While the DN211 is normally transmitting data with slave devices the local station node address is
displayed.

Node address: A node identification number that the DeviceNet devices (nodes) linked to the

network have. The values range within 0 to 63 in decimal scale. In a DeviceNet, the
node address of a node linked to the network must be unique.

In the following cases, module or network status is displayed in combination of this LED and the
LED for module status/network status indication.

• A trouble occur on the DN211 or on the network.

• An error occurs when the T2/T2E/T2N requests.

(Parameter setting and operation mode controlling, etc. are performed by the request from the
T2/T2E/T2N.)

• The DN211 is downed.
See "6.2 Indications of the 7-Segment LED" for the combinations and meanings of this LED and

the LED for module status/network status indication.

6 F 3 B 0 3 6 4

(3) DIP switch for setting the operation mode/communication rate

This DIP switch is used for setting the operation mode at DN211 busoff and a communication rate
on the network (500 kbps/250 kbps, 125 kbps).

"3.2 Switch Setting" explains the contents of the DIP switch and how to set it.

(4) Rotary switch for node address setting (NA-H/NA-L)

Is used for setting node addresses in the network of the DeviceNet.
The DN211 can have a node address within 0 to 63 (decimal scale) unless the node address doesn't

duplicate with another node address (slave device) in the network.
"3.2 Switch Setting" explains how to set the rotary switch.

(5) The test connector

This connector is only for maintenance. You may not use it.

(6) The device side connector (for DeviceNet connection)

This connector is for connecting the DeviceNet cable to the DN211.
"3.4 Connection with the Network" explains how to connect cables.

 39 

3. Preparation for Operation (hardware)

3.1 DN211 Setting Flowchart (hardware)
DANGER

1. Configure an emergency-stop circuit, interlock circuit, and/or other similar safety circuits
outside the PC and DN211.

If the PC or DN211 gets failed or malfunctioned, it can cause an accident which will lead to
bodily injury and/or mechanical damage.

CAUTION

2. Secure the safe environment before executing program modification, forcible output, RUN, or
HALT instruction during operation. An operational mistake can cause mechanical damage or
accident

The following flowchart shows the DN211 setting.

6 F 3 B 0 3 6 4

Start

Setting your DN211's node address /

operation mode / communication rate

Mounting the DN211 on the I/O slot of the

T2/T2E/T2N

Connecting the DN211 to the network

Supplying the network power to the DN211

Supplying the T2/T2E/T2N power

Set the node address for the DN211 with the rotary
switch on the side. Also set the operation mode and
communication rate with the DIP switch on the front
panel.
See '3.2 Switch Setting" for detail.

Mount the DN211 into the I/O slot of the T2/T2E/T2N
base unit.
See "Mounting module" in the Main Unit User’s Manual
for detail.

Using the network side connector (attached to DN211),
connect the DeviceNet cables to the DN211. See "3.4
Connection with the Network" for detail.

Supply the communication power for the DeviceNet
devices through the network cable.
See "3.5 The Network Power / Grounding" for detail.

After completing the above work, switch ON the power
of the T2/T2E/T2N.
See "Grounding" and "Power-supply Wiring" in the
Main Unit User’s Manual for the details of power­supply wiring / grounding.

End

Figure 3.1 DN211 Setting Flowchart

 40 

3.2 Switch Setting

LOADER

The DN211 has a DIP switch on the front panel and a rotary switch on the side. These switches
are used for setting the operation mode, communication rate, and node address of the DN211.

3.2.1 DIP Switch for Setting the Operation Mode/Communication Rate

∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼

6 F 3 B 0 3 6 4

ON

1 2 3 4

1
OSEN

2
BUSOFF

3
DR1

4
DR0

← DIP switch for setting the operation

mode/communication rate
Factory setting: OFF

∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼

Figure 3.2 DIP Switch for Setting the Operation Mode/Communication Rate

Table 3.1 DIP Switch Setting

DIP Switch Name Function

1 OSEN Is reserved for the system. Set to OFF and keep it.
2 BUSOFF Specifies the operation mode when the DN211 turns busoff (*1).

ON: When turned busoff, the DN211 initializes the internal network
controller to become standby mode. After solving the cause of the busoff
state, resume transmission with the instruction from the T2/T2E/T2N.

OFF: When turned busoff, the DN211 initializes the internal network
controller before resuming transmission (factory setting).

34DR1

DR0

Sets the communication rate. Refer to Table 3.2.

(*1) Busoff: Individual nodes on the DeviceNet check for abnormal transmission paths; when the local

node is judged to be the cause of abnormal transmission path, the local node is separated from the
transmission path. This state is called busoff.

Table 3.2 Communication Rate Setting

Communication

DR1 DR0

Rate

125 kbps OFF OFF ← Factory setting
250 kbps OFF ON
500 kbps ON OFF

 41 

Setting disabled ON ON

6 F 3 B 0 3 6 4

 42 

6 F 3 B 0 3 6 4

CAUTION

1. Set and keep "OSEN" on the DIP switch to OFF. Setting it to ON can get failed or
malfunctioned.

2. When you set "BUSOFF" on the DIP switch to OFF, transmission will restart automatically
even when busoff occurs. Unless the cause of the DN211's busoff (cause of communication
error) is solved, however, busoff may get repeated.

3. When you set both of communication rate DR0 and DR1 to ON and turn on the power of the
T2/T2E/T2N, "Communication Rate Setting Failed" will appear with the following
indications:

• The "MS" LED is blinking red.

• "F7" and the local station node address are being displayed alternately on the 7-segment

LED.

To clear these indications, set DR0 and DR1 correctly and, issue a reset request or turn

OFF and ON the power.

4. Set the communication rates of your nodes being connected to the network, to the same
communication rate. Setting different communication rates on your different

nodes will cause slave devices or the DN211 to get malfunctioned, resulting
in no communication started.

Read the relevant manuals and descriptions to set the communication rate of your slave

devices.

5. Don't change over the communication rates while your T2/T2E/T2N is rising just after the
turning on the power. In particular, never change the communication rate while
communicating with slave devices. Failing to do so will cause "Communication Rate Setting
Failed" to appear.

To clear this indication, set the DIP switch to the correct setting and, issue a reset request
or turn OFF and ON the power.

Usage Recommendation

1. Use a small minus screwdriver for changing the value of the DIP switch.

 43 

3.2.2 Rotary Switch for Node Address Setting

The DN211 board has a rotary switch for node address (0 to 63 in decimal scale) setting (Figure

3.3). NA-H is used for setting a 10-order figure while NA-L is used for setting a 1-order figure.
Since both of NA-H and NA-L can set a value from 0 to 9, the value can range within 0 to 99.
When a value within 64 to 99 is set, however, a "Node Address Setting Abnormal" error occurs
with the DN211 when the T2/T2E/T2N power is switched ON.

To clear the error, set the correct node address and, issue a reset request or switch OFF and ON
the power. In the DeviceNet, each of the node address values in the network must be unique.When
the DN211's node address duplicates with another node address, a "Node Address Duplicated"
error occurs with the DN211 when it turns run status. To clear the error, allocate the correct node
address and, issue a reset request or switch OFF and ON the power.

∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼

6 F 3 B 0 3 6 4

DN211 board

Front panel

Figure 3.3 Rotary Switch for Node Address Setting

NA-H NA-L

Factory setting = "0"

CAUTION

1. When you set a value within 64 to 99 to the node address of your DN211 and turn ON the
power of your T2/T2E/T2N, "Node Address Setting Failed" will appear with the following
indications:

• The "MS" LED is blinking red.

• "F6" and the local station node address are being displayed alternately on the 7-segment

LED.

To clear these indications, set the correct value to the node address and, issue a reset

request or turn OFF and ON the power.

2. If your DN211 node address has the same value with another node and when the DN211
comes into run state, "Node Address Duplicated" will appear with the following indications:

• The "MS" LED is lighting red and/or the "NS" LED is lighting red.

• "70" and the local station node address are being displayed alternately on the 7-segment

LED.

To clear these indications, set the correct value to the node address and, issue a reset
request or turn OFF and ON the power.

Usage Recommendation

1. Use a small minus screwdriver for changing values of the rotary switch.

 44 

3.3 Mounting in the Base Unit

PSP

S

DN211DN211PST2EDN211DN211

Mount your DN211 in the I/O slot of the base unit for the T2/T2E/T2N and lock the master device.
See "Mounting/Removing the Module" in the Main Unit User’s Manual for detail.

1. Since the DN211 is designed for Toshiba's T2 series, be sure to mount your DN211
in the base unit, instead of using it in stand-alone; don't use it for other applications.
Unauthorized applications can cause electric shock, bodily injury, and/or mechanical
malfunction.

2. Be sure to turn OFF the power (on the T2 side and network side) before attaching or
detaching the DN211 and/or the terminal block. Failing to do so will cause electric
shock, malfunction, and/or failure.

3. Keep the DN211 free from foreign matter such as electric-wire waste. Failing to do so
could cause fire, failure, and/or malfunction.

4. Check the connectors, cables, and base unit of the DN211, for their firm connection
and mounting using stoppers and screws. Note loose connection or mounting can be
shaky or easily disconnected off, resulting in failure or malfunction of the DN211.

6 F 3 B 0 3 6 4

CAUTION

More than one unit of DN211 can be mounted for one unit of the T2/T2E/T2N, as explained in
"1.5.2 Number of Mounting Modules." The DN211 can be mounted in the basic base unit and an
extended base unit.

Since the DN211 falls in a low-voltage I/O unit, place it at the left side of the unit, whereas arrange
high-voltage I/O units at the right side of the unit. Separate low-voltage units from high-voltage
units when wiring them ("8.4 Network Installation" explains network cables wiring).

T
2

Using the Basic Base Unit (BU218) for 8-Boards I/O Unit

Figure 3.4 Example of Mounting on the Base Unit

The current consumption of the T2/T2E/T2N side power of the DN211 (DC5V) is 0.5 A. To
examination the power capacity, refer to "Examining the Power Capacity" of the T2 User’s
Manual/T2E User’s Manual/T2N User’s Manual, besides "1.5.2 Number of Mounting Modules."

 42 

3.4 Connection with the Network

6. Ask the qualified expert for the installation work of the DeviceNet cables because it

Hole to
insert a
cable

This section describes how to connect the DeviceNet cable to the DN211.

1. Do not engage in attaching or detaching the DeviceNet cable with network side
connector during network operation. Failing to do so can cause reverse connection
or short circuit of the network power, resulting in no communication with other nodes.

2. When you connect the DeviceNet cable with the network side connector, be sure not
to make the wrong connection. Failing to do so can cause short circuit of the network
power, resulting in no communication with other nodes.

3. Neither attach nor detach the network side connector with the device side connector
on the DN211 front panel while the T2/T2E/T2N is rising just after the power is turned
ON. Failing to do so can cause the DN211 to fail or malfunction.

4. Attaching the opposite end of the network side connector with/from a device side
connector is not possible because of the specific form. Trying connecting the wrong
end by excessive force can damage both the network side connector and the device
side connector.

5. Be sure not to wire the cable in too tightly stretched state or in bent state.Also, don't
put heavy stuff on the cable. Otherwise, the cable could break.

6 F 3 B 0 3 6 4

CAUTION

requires sufficient safety and noise-suppression measures.
Refer to DeviceNet Volume I, Release 1.3, for the standard installation.
Also see "8.4 Network Installation" in this manual.

The DN211 supports the plug connection connector(open type). It has two types of network side
connectors attached, as shown in Figure 3.5. Follow the order stated below to connect the
DeviceNet cable to the DN211.

1) Connect the Devicenet cable to the network side connector and fix it.

2) Insert the network side connector into the device side connector on the front panel of the
DN211.

The connector at the left-side figure below has the upper and lower rows with holes for cables so
that the DN211 can be connected in the middle of the network daisy chain.

Meanwhile, the connector at the right-side figure below has a row with holes for cables so that the
DN211 can be connected at the network end. Select either of the connectors after discussing the
point you are going to connect your DN211 in the network.

Hole to insert a cable

Phoenix Contact

TMSTBP2.5/5-STF-5.08 AB GY AU

Figure 3.5 Network Side Connectors Attached to the DN211

 43 

MSTBP2.5/5-STF-5.08 AB GY AU SO

Phoenix Contact

3.4.1 Connecting DeviceNet Cables to Network Side Connector

∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼

(1) Preparing DeviceNet Cables

Use an open-type cable end (2 power cables, 2 signal cables, and 1 drain cable in discrete state) for
DeviceNet cables, which will be connected with the network side connector of the DN211. Or
purchase such an open-type cable end in the commercial market.

Color of cable coating Description

Black Power cable (V −)
Blue Signal cable (CAN_L)

− Shield/Drain
White Signal cable (CAN_H)
Red Power cable (V +)

5 to 7 mm

Approx. 30 mm

6 F 3 B 0 3 6 4

Figure 3.6 Processing of the DeviceNet Cable End

(2) Connecting DevicNet cables to the network side connector

This section describes how to connect DeviceNet cables to network side connectors by using
Figure 3.5 at the left side (upper and lower rows with holes for inserting cables) on the preceding
page. As shown in Figure 3.7, loosen screws on the cable connectors beforehand. Match the colors
of the cable coatings with those of the network side connector before inserting the cables into the
connectors. Tighten the screws for fixing cables.

Cable fixing screw

Color indication

Network side connector

Black

Blue

White

Shield/Drain

Red

Screws for fixing cables in lower­row holes is located on this side

Figure 3.7 Connecting Cables with Network Side Connector

 44 

6 F 3 B 0 3 6 4

 45 

3.4.2 Connecting the Network Side Connector to the DN211

Insert the network side connector into the device side connector on front panel of the DN211. Note
the network side connector cannot be attached upside down due to the specific form; don't try to
connect these connectors by force. Tighten the screws for fixing the network side connector on the
DN211.

6 F 3 B 0 3 6 4

Network connector
fixing screw

Figure 3.8 Mounting the Network Side Connector

 46 

6 F 3 B 0 3 6 4

Usage Recommendation

1. Loosen the cable fixing screw on the connector before inserting cables into the
network side connector. The cable cannot be fixed when the screws are kept
tightened.

2. Colors corresponding to cable colors are printed by the device side connector of the
DN211. Match the cable colors with the printed colors to have correct wiring.

3. The DN211 and the DN311 (DeviceNet module for the T3/T3H) have different
directions for attaching the network side connector.

4. DeviceNet cables, power tap, and device tap (connecting the trunk line with drop
lines) are necessary when constructing a system using a DeviceNet. Refer to "3.6
The Network Components" for detail.

Some of the network components must be prepared by the user.

5. When you use the network side connector that has the upper and lower rows with
holes for cables (at the left-side Figure 3.5), the connector protrudes from the left­side DN211 about 5mm. When you attach or detach the left-side module of DN211,
you must detach the connector from DN211.

 47 

3.5 The Network Power/Grounding

Protective

circuit

Protective

circuit

The maximum cable length from

In the DeviceNet, the power for communication (24 Vdc) is supplied from the power cables
(V+/V−) for the DeviceNet cables via the network side connector. This section describes how to

supply the network power to the DeviceNet cables and how to configure network power units.
Grounding the network is also explained.

3.5.1 The Network Power Mechanism

In order to supply the network power (24 Vdc) to the DeviceNet cables, the power tap (Figure 3.9)
specified in the DeviceNet must to be used. The power tap is an apparatus for connecting a 24 Vdc
power unit to the trunk cable. It has the following functions:

1) When more than one 24 Vdc power unit are connected to one network, the power tap prevents
adverse current flow to power units by potential differences.

2) The power tap supports a maximum of 16 A from a power unit directly connected to the tap.

3) The protective circuit (fuse or circuit breaker) restricts the current flow from the power tap to
the cables within 8 A.

6 F 3 B 0 3 6 4

4) Provides terminals for grounding the network.

Power tap

Signal CAN_H
Signal CAN_L

Shield/Drain

−

V
V +

Grounding terminal

Network power-supply unit

a power-supply unit to the power
tap is 3 meters.

DeviceNet
cables
Trunk cable

Shot key
diode

V −V +

The following power tap products, specified in the DeviceNet, are available.

Figure 3.9 Power Tap Configuration

Model name 1485T-P2T5-T5

(PowerTap)

Manufacturer Rockwell Automation

 48 

3.5.2 How to Configure Network Power Units

This section describes selecting and disposing power units for supplying the network power to
individual nodes of the DeviceNet.

(1) Maximum Current on the DeviceNet cable

The network power of the DeviceNet is set to rated 24 Vdc. The current which can be passed on
the network cable is as follows:

• Trunk line of thick cable: 8 A

Cable length 0m 25m 50m 100m 150m 200m 250m 300m 350m 400m 450m 500m
Max. current (A) 8.00 8.00 5.42 2.93 2.01 1.53 1.23 1.03 0.89 0.78 0.69 0.63

Thick cable Maximum Current

Maximum Current of Thick Cable

太ケーブル最大電流

8.00

6 F 3 B 0 3 6 4

7.00

6.00

5.00

4.00

3.00

電流値(A)

Current value (A)

Current value (A)

2.00

1.00

0.00
0m

50m

Figure 3.10 Current of the Trunk Line (thick cable)

100m

150m

200m

ケーブル長

Cable length

250m

300m

350m

400m

450m

500m

 49 

6 F 3 B 0 3 6 4

• Trunk line of thin cable: 3 A (up to 100 m)

Cable length 0m 10m 20m 30m 40m 50m 60m 70m 80m 90m 100m
Max. current (A) 3.00 3.00 3.00 2.06 1.57 1.26 1.06 0.91 0.80 0.71 0.64

Maximum Current of Thin Cable

細ケーブル最大電流

3.00

2.50

2.00

1.50

電流値(A)

1.00

Current value (A)

0.50

0.00

0m

• For drop line: 0.75 to 3.0 A

10m

Figure 3.11 Current of the Trunk Line (thin cable)

20m

30m

40m

Cable length

50m

ケーブル長

60m

70m

Formula: I = 4.57/L (however, I < 3 A)

80m

90m

I : Max. current of drop line (A)

L : Drop line length (0 to 6 m)

Usage Recommendation

1. Consider not only current capacity of the trunk line but also current capacity of a drop
line when you install a node on the drop line.

2. In particular, when you are connecting nodes in daisy chain on a drop line, be careful
not to have insufficient current capacity.

100m

 50 

(2) How to Know the Optimal Arrangement of Network Power Units

a) Sum of current consumption = 0.1A + 0.15A + 0.05A + 0.25A + 0.1A = 0.65 A

Since the sum of current consumption < maximum current, a single power-supply

Use the following procedure to know optimal arrangement of network power units.
a) Obtain the sum of the network currents consumed by individual nodes on the network. For t he

nodes which use the network power to operate, uses the sum of both currents.
b) Measure the full length of the network.
c) Based on the cable type (thick cable, thin cable) used for the trunk line and the full length of the

network obtained through procedure b), get the maximum current value available on the cable

by using Figure 3.10 and Figure 3.11
d) When the sum of the currents consumed on the network (procedure a) is smaller than the

maximum current available on the cable (procedure c), a network power unit installed at the

network end can be used to supply the power to all nodes ( = single power unit terminal

connection).
e) When the sum of the currents consumed on the network (procedure a) is larger than the

maximum current available on the cable (procedure c), install a network power unit near the

center of the network and examine whether it can supply the power to all nodes (= single power

unit central connection).
f) If the single power central connection is insufficient to supply the network power to all nodes,

install additional network power units.

6 F 3 B 0 3 6 4

Usage Recommendation

3. Use a network power whose capacity is much larger than the total current
consumption necessary for the network.

(3) Single Power Unit Terminal Connection

Below is an example of a network power unit installed at the end of the trunk line (thick cable) with
a total extension of 200 meters. The current consumption by the node is shown below.

+−

V

−

V

Network

power-supply

unit

b) Total of power cable length extended = 200 m
c) Maximum current = 1.53 A available on the cable, based on Figure 3.10
d)

e) Install a network power-supply unit with a rated current of 0.65 A or more.

0.1A 0.15A 0.05A 0.25A 0.1A
200 m

terminal connection can supply the power to all nodes.
(Select one with ample current in considering usage conditions.)

Node 1Node 1Node 1Node 1Node 1Power tap

3.12 Example of Single Power Terminal Connection

 51 

(4) Single Power Unit Central Connection

120 m

120 m

This section describes an example of installing a network power unit at the center of the trunk line
(Thick cable) with a total extension of 240 meters. The current consumption by the node is shown
below. Since the network power unit is installed at the center, the maximum current can be supplied
to all directions of the network.

6 F 3 B 0 3 6 4

Section 1

V

Power

tap

0.1A 0.25A 0.2A V

Network

power-supply

unit

Figure 3.13 Example of Single Power Unit Central Connection

+−

−

Section 2

0.15A 0.25A 0.15A

a) Sum of current consumption in section 1 = 0.1A + 0.25A + 0.2A = 0.55A
a') Sum of current consumption in section 2 = 0.15A + 0.25A + 0.15A = 0.55A

Node 6Node 5Node 4Node 1Node 2Node 3

b) Total length extended in section 1 = Total length extended in Section 2 = 120 m
c) Maximum current available on the cable based on Figure 3.10 = approx. 2.56 A

(Obtain the approximate value between 100 to 150 meter straight cable.)

d) Since the sum of current consumption < maximum current, a single power unit central

connection can supply the power to all nodes.

e) Install a network power unit with a rated current of 1.1A or more.

(Select one with ample current in considering usage conditions.)

When the current consumption by the section exceeds the maximum current available for the cable
in single power unit central connection, take measures in the table below. Figure 3.14 indicates an
example of an overloaded single power unit central connection.

Cable section where the current is applied
beyond the maximum current

Only one of the two section Move a node in the overloaded section to the

Both sections Use two power taps.

Countermeasure

other section.
Move the power tap closer to the section

overloaded.

 52 

6 F 3 B 0 3 6 4

120 m

120 m

Section 1

+−

V

Power

tap

1.1A 1.25A 0.5A V

Figure 3.14 Example of Overloaded Single Power Unit Central Connection

−

Network

power-supply

unit

Section 2

0.25A 0.25A 0.85A

a) Sum of current consumption in section 1 = 1.1A + 1.25A + 0.5A = 2.85A
a') Sum of current consumption in section 2 = 0.25A + 0.25A + 0.85A = 1.35A

Node 6Node 5Node 4Node 1Node 2Node 3

b) Total length extended in section 1 = Total length extended in Section 2 = 120 m
c) Maximum current available on the cable based on Figure 3.10 = approx. 2.56A (Obtain the

approximate value between 100 to 150 meter straight cable.)

d) Since the sum of current consumption in section 1 > maximum current, the current is

overloaded.

Solution: Move the power tap to the overcurrent section. See Figure 3. 15.

 52 

6 F 3 B 0 3 6 4

100 m

140 m

Section 1

V

Power

tap

1.1A 1.25A V

Network

power-supply

unit

Figure 3.15 Example of Solving the Overload

+−

−

0.5A 0.25A 0.25A 0.85A

Section 2

Node 6Node 5Node 4Node 1Node 2Node 3

a) Sum of current consumption in section 1 = 1.1A + 1.25A = 2.35A
a') Sum of current consumption in section 2 = 0.5A + 0.25A + 0.25A + 0.895A = 1.85A
b) Total length extended in section 1 = 100 m
b') Total length extended in section 2 = 140 m
c) Maximum current available on the cable in section 1, based on Figure 3.10 = approx. 2.19A

(Obtain the approximate value between 100 to 150 meter straight cable.)

d) Since both of the sums of current consumption in section 1/2 < maximum current, a single power

unit central connection can supply the power to all nodes.

e) Install a network power unit with a rated current of 4.2A or more.

(Select one with ample current in considering usage conditions.)

 53 

3.5.3 The Network Power Unit (24 Vdc)

The network power unit is not attached to the DN211; you have to buy such a unit in the
commercial market. Your network power unit must conform with the following specifications:

Item Specification

Output voltage 24Vdc ± 1%
Output current 16A or less
Input fluctuation Max. 0.3 %
Load fluctuation Max. 0.3 %
Effects by the ambient temperature Max. 0.03 % / °C
Input Voltage 120V ± 10 %

230V ± 10 % (if necessary) or

Automatic changeover within 95 to 250V
Input frequency 47 to 62 Hz
Output ripple 250 mVp - p

6 F 3 B 0 3 6 4

Output side capacity Max. 7000 µF
Ambient temperature During operation: 0 to 66°C ∗

When stored: −40 to 85°C

∗ : Rated output derating at 60°C is allowed.
Instantaenious max. output current less than 65A (at peek)
Protection against overvoltage Yes (No value specified)
Protection against overcurrent Yes (Max. current: 125 %)
Startup time 250 ms by the 5% value of the max. output voltage
Overshoot on startup Max. 0.2%
Stability 0 to 100% load (for all conditions)
Insulation Between output - AC power unit; between output - case

grounding
Conformity Required: UL

Recommended: FCC Class B, CSA, TUV, VDE
Ambiant humidity 20 to 90% (no dew)
Surge current capacity 10% of reserve capacity

Usage Recommendation

1. Use a network power whose capacity is much larger than the total current consumption
necessary for the network.

 54 

3.5.4 The Network Grounding

V −V +

Grounding

unit

V − V +

Grounding

l

For the DeviceNet, use 1-point grounding (class-3 grounding for control device only) for the
network grounding. If more than one point are grounded, the ground can loop. Conversely, the
network without being grounded is likely to malfunction due to external noises.

Use the power tap as the point for 1-point grounding. Connect the ground terminal of the power tap
with the FG terminal of the power unit before applying class-3 grounding for control device only as
shown in Figure 3.16. (Install a power tap near the center of the network and ground from it).

When more than one power units are used in the network, apply grounding to a power tap near the
center of the network.

Use a grounding line with a maximum of 3 meters (#8AWG power line).

6 F 3 B 0 3 6 4

Power tap

terminal

FG V −V +

Power-supply

unit

Power tap

termina

FG V −V +

Power-supply

Power tap grounded Power tap not grounded

Figure 3.16 How to Install Your Network

 55 

3.5.5 Procedure for Switching-ON/Shutting-OFF the Power

This section describes the order of switching on the slave devices power, the network power, and
the T2/T2E/T2N side power before starting up the DN211. Check all device wiring and settings
are completed before switching ON in the following order.

(1) When Starting up the System

a) The network power
b) The slave device power
c) The T2/T2E/T2N side power
d) Activating the DN211 communication
The DN211 doesn't yet start communication when the T2/T2E/T2N side power is switched ON.

Set the parameters of the local nodes and register the parameters of the slave devices in the
scanning list before engaging in communication start processing. See "5.2 Module Setting
Procedure" for detailed procedures.

6 F 3 B 0 3 6 4

1. Be sure to turn ON the network power before turning ON the power of the DeviceNet devices.

Some nodes of the slave devices use the network power as the operation power while other

slave devices indicate an error when their work power is not supplied. Therefore, be sure to
switch ON the network power. Also note unless the network power is switched ON, your
DN211 cannot start communication with slave devices.

2. Be sure the network power is supplied to all the nodes being connected with the network. The
node to which no network power is supplied could cause communication obstacle to other
nodes.

3. Make sure the power of all slave devices is switched ON before the DN211 begins
communication.

When the DN211 begins communication while the power of a slave device is not switched
ON, the DN211 will display an error message of no response from that device.

(2) When Deactivating the System

a) The slave devices power
b) The network power
c) (HALT the operation mode of the T2/T2E/T2N.)
d) The T2/T2E/T2N side power

CAUTION

CAUTION

4. While network communications are operating, don't shut OFF the network power. Failing to
do so will cause the entire network communications to stop and, one of the nodes become
busoff state.

5. Switch OFF the T2/T2E/T2N side power at last after the DN211 begins communication. This
helps the master device (DN211) to be recognized from the network and prevents slave
devices from malfunctioning.

 56 

3.6 The Network Components

Terminal

Terminal

resistor

Trunk line

This section explains the network components of the DeviceNet other than the master/slave
devices (Figure 3.17). Since peripheral devices are recommended on the following pages, which
are available in the commercial market, buy some of them when you need.

6 F 3 B 0 3 6 4

Node

Node

Node

Node

Node

Node

Multiport tap

Tap

Tap Multiport tap

Node

Node

Figure 3.17 Example of DeviceNet Network Configuration

NodeNode

Tap

Drop line

resistor

Node

Node

Node

 57 

(1) Thick Cable (for trunk line)

Manufacturer: Rockwell Automation

Item name Catalog No. Remarks

6 F 3 B 0 3 6 4

1 m with connectors 1485C-P1N5-M5
2 m with connectors 1485C-P2N5-M5
3 m with connectors 1485C-P3N5-M5
5 m with connectors 1485C-P5N5-M5
10 m with connectors 1485C-P10N5-M5
50 m with no connector 1485C-P1-A50
150 m with no connectors 1485C-P1-A150
300 m with no connectors 1485C-P1-A300

(2) Thin Cable (for trunk line and drop line)

Manufacturer: Rockwell Automation

Item name Catalog No. Remarks

1 m with connectors 1485R-P1M5-C
2 m with connectors 1485R-P2M5-C
3 m with connectors 1485R-P3M5-C
150 m with no connector 1485C-P1-C150
300 m with no connectors 1485C-P1-C300
600 m with no connectors 1485C-P1-C600

Shieldded mini-connectors (male, female)
attached

Shielded mini-connectors 871A-TS5-NM3
(male) and 871A-Ts5-N3 (female) for fixing

Discrete shielded mini-connector (male)
and open-type connector

Used for linking an open-type connector to
an open-type connector in daisy chain.
Used when connecting the DeviceBox Tap
with an open-type connector

 58 

(3) Tap/Multiport Tap

Manufacturer: Rockwell Automation

Item name Catalog No. Remarks

T-Port Tap 1485P-P1N5-MN5R1 T-branch (one drop line from the trunk line)

Both the trunk line and drop line use a
cable with shielded mini-connectors.

6 F 3 B 0 3 6 4

DeviceBox Tap (2 ports) 1485P-P2T5-T5
DeviceBox Tap (4 ports) 1485P-P4T5-T5
DeviceBox Tap (8 ports) 1485P-P8T5-T5

2 drop lines from the trunk line
4 drop lines from the trunk line
8 drop lines from the trunk line

The trunk line cable and drop line cable,
connected with a DeviceBox Tap, are
open-type and discrete.

(4) Others

Manufacturer: Rockwell Automation

Item name Catalog No. Remarks

Power Tap 1485T-P2T5-T5 Tap power capacity for the trunk line:

7.5 A
The trunk line connected with a PowerTap

with overcurrent protection uses a discrete
open-type connector (no shielded mini-

connector).
Terminator (male) 1485A-T1M5
Terminator (female) 1485A-T1N5

Terminates the trunk line.

These are used for a Thick Cable with

mini-connectors or T-Port Tap.

 59 

4. How to Handle Your DN211 (software)

This chapter describes the subjects necessary for using various functions of the DN211 in ladder
programs for the T2/T2E/T2N. More specifically, the following subjects are explained in this
chapter.

• Configuration and functions of the DN211 communication memory seeing from the

T2/T2E/T2N

• Functions and usage of various request instructions for operating the DN211

• DN211's response code to various request instructions (completion status)

Based on the subjects discussed in this chapter, Chapter 5 describes the procedures in the DN211
for setting parameters, activating transmission, inputting/outputting data with slave devices, and
reading RAS information including event history, and introduces sample programs.

CAUTION

6 F 3 B 0 3 6 4

1. Chapter 4 describes the subjects necessary for using diverse functions of the DN211 from the
T2/T2E/T2N. Chapter 5 describes, based on the subjects explained in Chapter 4, setting the
DN211 parameters, activating transmission, inputting/outputting data with slave devices, and
the procedure for reading RAS information including event history, and sample programs.

Write programs after understanding the contents. As sample programs are basic, you need
to examine your programs from beginning to end before applying them to actual systems.

Usage Recommendation

1. When your DN211 is going to be I/O registered in the T2/T2E/T2N, leave blank for the slot
where the DN211 is installed.
After automatic allocation is performed, the DN211-installed slot is left blank.

 60 

4.1 Configuration of the DN211 Communication Memory

Indicated below is the configuration of the DN211 communication memory seeing from the
T2/T2E /T2N.(Word address)

0000H

Input/output data area

263 words

0106H
0107H

RAS information area

6 F 3 B 0 3 6 4

456 words

02CEH
02CFH

Semaphore area

305 words

03FFH

Figure 4.1 DN211 Communication Memory Map

(1) The Semaphore Area

This area is used for issuing requests from the T2/T2E/T2N to operate the DN211 and for reading
the DN211 responses.

(2) The RAS information Area

This area of the DN211 displays the DN211's module status, communication status with network
and slave devices.

(3) The Input/Output Data Area

This area stores data to be exchanged between the DN211 and slave devices.
Output data from the T2/T2E/T2N is written in this area, while input data is read from this area.

This area also have the output and input semaphore registers used for synchronous
communications between the DN211 and slave devices.

 61 

6 F 3 B 0 3 6 4

 62 

4.2 The Input/Output Data Area

This area stores data to be exchanged between the DN211 and slave devices. Output data from
the T2/T2E/T2N is written in this area, while input data is read from this area.

This area also have the output and input semaphore registers used for synchronous
communications between the DN211 and slave devices. The addresses in Figure 4.2 indicate the
word addresses seen from the T2/T2E/T2N.

0000H

6 F 3 B 0 3 6 4

Polling/Bit strobe input data area

128 words/2048 bits

007FH

0080H

Polling output data area

128 words/2048 bits

00FFH

0100H

0103H
0104H Bit strobe output data semaphore (1 word)
0105H Polling output data semaphore (1 word)
0106H Input data semaphore (1 word)

Bit strobe output data area

4 words/64 bits

Figure 4.2 Input/Output Data Area Configuration

 63 

(1) Input Data Semaphore Register (0106H: 1 word)

This semaphore register is used when inputting data into the T2/T2E/T2N from the DN211
(effective only for synchronous transmission mode). The register is used both in the polling mode /
bit strobe mode.

• DN211 side operation

The DN211 writes data, collected from the slave devices in the polling mode or the bit strobe

mode, into "polling / bit strobe input data area" before setting "1" to this register.

• T2/T2E/T2N ladder program operation

The ladder program for the T2/T2E/T2N monitors this register. When detecting "1" is written

into this register, the ladder program reads data from the "polling / bit strobe input data area" and
then writes "0" in the register before notifying the DN211 of read completion.

Write the value "0" only in this semaphore register.

(2) Polling Output Data Semaphore Register (0105H: 1 word)

This semaphore register is used when outputting polling data to the DN211 from the T2/T2E/T2N
(effective only for synchronous transmission mode).

6 F 3 B 0 3 6 4

• T2/T2E/T2N ladder program operation

The ladder program writes data, to be outputted to the "polling output data area," to slave device

in the polling mode before writing "1" in this register, and then instructs the DN211 to start
output.

Write the value "1" only in this semaphore register.

• DN211 side operation

The DN211 monitors this register in the "scan interval wait time" cycle specified from the

T2/T2E/T2N. When detecting "1" is set to this register, the DN211 outputs output data in the
"polling output data area" to slave devices. When the output is completed, "0" is set to the
register. The "scan interval wait time" is explained in "4.6.3 Parameter Setting Request (local
node)."

(3) Bit Strobe Output Data Semaphore Register (0104H: 1 word)

This semaphore register is used when outputting bit strobe data to the DN211 from the
T2/T2E/T2N (effective only for synchronous transmission mode).

• T2/T2E/T2N ladder program operation

The ladder program writes data, to be outputted to slave devices in the bit strobe mode, into the

"bit strobe output data area" before writing "1" into this register, and then instructs the DN211 to
start output.

Write the value "1" only in this semaphore register.

• DN211 side operation

The DN211 monitors this register in the "scan interval wait time" cycle specified from the

T2/T2E/T2N. When detecting "1" is set to this register, the DN211 outputs output data in the "bit
strobe output data area" to slave devices. When the output is completed, "0" is set to the register.
The "scan interval wait time" is explained in "4.6.3 Parameter Setting Request (local node)."

 64 

(4) The Bit Strobe Output Data Area (0100H - 0103H: 4 words)

Bit strobe

WRITE
instr

uction

READ
instruction

Stores data that the DN211 outputs to slave devices in the bit strobe mode.
The ladder program for the T2/T2E/T2N writes output data in this area. The transmitting data in

the bit strobe mode is fixed at 8 bytes (64 bits).
The corresponding relation of the bits in this area and the node addresses of the slave devices is

indicated below.

Table 4.1 Bit Strobe Output Data Area Configuration

F E D C B A 9 8 7 6 5 4 3 2 1 0
0100H 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0101H 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
0102H 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
0103H 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48

(5) The Polling Output Data Area (0080H - 00FFH: 128 words)

6 F 3 B 0 3 6 4

Stores data that the DN211 will output to slave devices in the polling mode.
The ladder program for the T2/T2E/T2N writes output data in this area. The area has 128 words

(2048 bits) in size; unless the data size that the DN211 sends to salve devices doesn't exceed this
limit, up to 63 slave devices are connectable with one DN211.

How to allocate output data to slave devices from this area is explained in "4.4 Allocating Slave
Data to the Input/Output Data Area"

(6) The Polling/Bit Strobe Input Data Area (0000H - 007FH: 128 words)

Stores data collected by the DN211 from the slave devices in the polling mode and bit strobe mode.
The ladder program for the T2/T2E/T2N read data from this area. The area has 128 words (2048
bits) in size; unless the data size that slave devices send to the DN211 doesn't exceed this limit, up
to 63 slave devices are connectable with one DN211.

How to allocate input data from slave devices to this area is explained in "4.4 Allocating Slave Data
to Input/Output Data Area"

Figure 4.3. shows an overview of the output data area/input data area.

DN211T2/T2E/T2N

Slave

Input data

register area

Polling / Bit strobe

input data area

Polling

Output data

register area

Polling

output data area

output data area

Figure 4.3 Overview of Input/Output Data Area

 65 

Slave

Bit strobe

6 F 3 B 0 3 6 4

Output

Intput

Output

Writes

Writes output
Writes read

"0"

Writes
instruction

Writes output

semaphore

semaphore

data area

input data area

data area

(7) The usage of Output/Input Data Semaphore (for synchronous transmission mode

alone)

Figure 4.4 indicates the relation between output data semaphore (polling / bit strobe) and input data
semaphore. Oblique lines parts indicate each of the semaphore values is set to the "1".

T2/T2E/
T2N

Output data

Intput data

DN211

Writes in output

instruction "1"

processing

completion
"0"

processing

Reads from

completion

Writes in output

output

processing

Figure 4.4 Use of Semaphores in Synchronous Mode

(8) Cautions in Using the Input/Output Data Area

• The input data semaphore register is used both for the polling mode and the bit strobe

mode. Therefore, when some slave devices use the polling mode while other slave
de vices use the bit strobe mode, set data input/output processing in the alternative
way like :

output
comple­tion "0"

polling mode processing completion

polling mode processing completion → bit strobe mode

→

bit strobe mode processing completion

→ …

→

• Don't allow the WRITE instruction to execute in the input data area/input data

semaphore register. Otherwise, input data could be destroyed.

• When you write data in the polling output data area/bit strobe output data area with the

WRITE instruction, be careful of the top address of the area and the data size to be
written. Otherwise, data could destroy those in another area, causing the DN211
and/or slave devices to get malfunctioned.

 66 

4.3 The RAS Information Area

∼∼∼∼∼∼
∼∼∼∼∼∼

∼∼∼∼∼∼
∼∼∼∼∼∼

∼∼∼∼∼∼
∼∼∼∼∼∼

∼∼∼∼∼∼

This area indicates the DN211's module status and the communication status of the network and
slave devices. Don't write data into this area. Otherwise, the correct data may not be read. The
addresses in Figure 4.5 indicate the word addresses seen from the T2/T2E/T2N.

0107H Network power unit (1 word)
0108H Operation mode on busoff (1 word)

0109H Network communication rate (1 word)
010AH Local station node address (1 word)
010BH

∼∼∼∼∼∼

Input/Output data setting information (384 words)

028BH

6 F 3 B 0 3 6 4

Reserved (8 words)

0293H

Bit strobe no-response device (4 words)

0297H

Polling no-response device (4 words)

029BH Number of polling devices (1 word)
029CH Number of bit strobe devices (1 word)
029DH Number of on-line devices
029EH Number of total devices (1 word)

029FH

Configuration information (32 words)

02BFH

Node error counter (7 words)

02C6H Completion of module initialization (1 word)
02C7H Reserved (1 word)
02C8H

Polling/Bit strobe scan cycle (5 words)

02CDH Down information (1 word)
02CEH Station status (1 word)

Figure 4.5 RAS Information Area Configuration

 67 

Indicated below is detailed information that can be checked in the RAS information area.

(1) Station Status (02CEH: 1 word)

This register indicates the DN211's status with bit flags. Each bit has meaning when "1" is set.

Format

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

DOWN STBY Reserved POLL Reserved TXERR SYNC DRADR

Reserved RUN BITS Reserved NCOIN START BUSOFF

Figure 4.6 Configuration of Station Status Bits

Table 4.2 Meaning of Individual Bits of Station Status

6 F 3 B 0 3 6 4

Reserved

Bit Name Meaning

15 DOWN DN211 is set to the down mode.
14 Reserved
13 STBY DN211 is set to standby mode.
12 RUN DN211 is set to run mode.
11 Reserved
10 BITS Bit strobe mode transmission is operating.
9 POLL Poling mode transmission is operating.
8 Reserved
7 Reserved
6 NCOIN No slave device is registered in the DN211.
5 TXERR Some of the salve devices registered do not respond.
4 START DN211 is executing transmission.
3 SYNC DN211 is operating in synchronous mode.
2 BUSOFF DN211 is set to busoff status.
1 DPADR DN211 detected an duplicated node address when starting transmission.
0 Reserved

Table 4.3 on the next page indicates the configuration of the station status bits of the DN211 in
different modes.

 68 

Table 4.3 DN21's Modes and Station statuses

DN211's mode Bit "1" Station status

a Down mode DOWN 8000H

6 F 3 B 0 3 6 4

b After switching ON the power or after issuing a reset

request from the T2/T2E/T2N

c No slave device is registered (or deleted) in the

DN211 in mode b).

d When a slave device is registered in mode c) by a

parameter setting request

e When "standby" is requested by a module control

request from the T2/T2E/T2N

f When "transmission enabled, polling mode

transmission, asynchronous mode" is requested by
a module control request from the T2/T2E/T2N and
transmitted normally

g When "transmission enabled, bit strobe mode

transmission, asynchronous mode" is requested by
a module control request from the T2/T2E/T2N and
transmitted normally

h When "transmission enabled, polling mode and bit

strobe mode transmissions, asynchronous mode" is
requested by a module control request from the
T2/T2E/T2N and transmitted normally

I When asynchronous mode is requested in a mode

within f) to h)

STBY

STBY
NCOIN

STBY

STBY

RUN
START
POLL

RUN
START
BITS

RUN
START
POLL
BITS

Bits from f) to h),
followed by SYNC

2000H

2040H

2000H

2000H

1210H

1410H

1610H

1218H
1418H
1618H

j While transmitting with a slave device in a mode

within f) to i), the slave device stopped responses.

k When busoff occurs, the DIP switch of the DN211

(BUSOFF) remains OFF (when the DN211 has
control of restarting transmission)

l When busoff occurs, the DIP switch of the DN211

(BUSOFF) remains ON (changing to standby mode
when busoff occurring)

m An overlapped node address is detected when

starting transmission

The bits from f) to
i), followed by
TXERR

Station status bits before busoff
occurring, followed by :BUSOFF

STBY
BUSOFF

STBY
DPADR

1230H
1430H
1630H
1238H
1438H
1638H

2004H

2002H

 69 

(2) Down Information (02CDH: 1 word)

This register stores the cause of becoming the down mode when the DN211 turns down mode.
When this happens, some of the following down codes are displayed in the 7-segment LED on the
front panel.

Table 4.4 Down Information

6 F 3 B 0 3 6 4

Down information
(hex.)

F0H Watchdog timeout occurred
F1H Memory bus abnormal occurred
F2H TRAP occurred
F3H ROM's BCC check error occurred (on DN211 startup)
F4H RAM's read/write error occurred (on DN211 startup)
F5H Read/Write error occurred for the DN211 communication memory (on

F6H DN211 node address setting abnormal
F7H DN211 network communication rate setting abnormal
F8H Configuration data EEPROM read error occurred

Cause of down mode occurred

DN211 startup)

(3) Polling / Bit Strobe Scan Cycle (02C8H - 02CCH: 5 words)

This area stores the DN211's scan time in milliseconds for the polling mode or bit strobe mode
transmission.

When in asynchronous mode: The "scan cycle" means the time that the DN211 starts carrying out
data input/output with all slave devices until starting the next input/output.

• Only for the slave devices with the polling mode, the "scan cycle" means the time from

starting polling input/output until starting the next polling input/output.

• Only for the slave device with the bit strobe mode, the "scan cycle" means the time from

starting bit strobe input/output until starting the next bit strobe input/output.

• For the salve devices where the polling mode and bit strobe mode are intermingled, the

"scan cycle" means the time from starting bit strobe input/output, followed by performing
polling input/output, until starting the next bit strobe input/output.

When in synchronous mode: The "scan completion time" means the time from the T2/T2E/T2N's
writing "1" in the "bit strobe output data semaphore/polling output data semaphore" until the
DN211's writing "1" in the "input data semaphore."

Table 4.5 Scan Cycle Configuration

02C8H Scan cycle/Scan completion time

02C9H Asynchronous mode: Min. scan cycle value
02CAH Asynchronous mode: Max. scan cycle value
02CBH Synchronous mode: Min. scan cycle time value
02CCH Synchronous mode: Max. scan cycle time value

(4) Completion of module initialization (02C6H:1 word)

This register indicates the completion of initialization processing by switching ON the power or by
requesting resetting.

"1": Completion of initialization
"Value other than 1": Under initialization

 70 

6 F 3 B 0 3 6 4

 71 

(5) The Node Error Counter (02BFH to 02C5H: 7 words)

The CAN controller used in the DN211 has a function of notifying error state changes of the local
station error state (error active ⇔ error passive ⇔ busoff) based on the number of transmission
errors occurring.

The CAN controller also has a function of notifying the DN211 of "overrun error" if the DN211
fails to take the data sent from slave devices.

The DN211 maintains the current error state and a history of error state changes since
communication was activated. This register indicates a history of error state changes since
communication was activated and the total number of transmission times and reception times.

Table 4.6 Node Error Counter Configuration

02BFH Current error state (hexadecimal scale)

02C0H Number of transmission times since communication was activated
02C1H Number of reception times since communication was activated
02C2H Number of error active occurrence times

6 F 3 B 0 3 6 4

02C3H Number of error passive occurrence times
02C4H Number of busoff occurrence times
02C5H Number of overrun error occurrence times

Current error state Error code (hexadecimal scale)

Initial mode 00H

Error active state 01H

Error passive state 02H

Busoff state 03H

Overrun error occurrence 04H

Reserved Other

 72 

(6) Slave Device Configuration Information (029FH - 02BEH: 32 words)

This area indicates scan type information for slave devices, which is set in the DN211(stored in the
non-volatile memory).

Table 4.7 Slave Device Configuration Information

Address F 8 7 0

029FH Node address : 1 Node address : 0
02A0H Node address : 3 Node address : 2
02A1H Node address : 5 Node address : 4
02A2H Node address : 7 Node address : 6
02A3H Node address : 9 Node address : 8
02A4H Node address : 11 Node address : 10
02A5H Node address : 13 Node address : 12
02A6H Node address : 15 Node address : 14
02A7H Node address : 17 Node address : 16
02A8H Node address : 19 Node address : 18
02A9H Node address : 21 Node address : 20
02AAH Node address : 23 Node address : 22
02ABH Node address : 25 Node address : 24
02ACH Node address : 27 Node address : 26
02ADH Node address : 29 Node address : 28
02AEH Node address : 31 Node address : 30
02AFH Node address : 33 Node address : 32
02B0H Node address : 35 Node address : 34
02B1H Node address : 37 Node address : 36
02B2H Node address : 39 Node address : 38
02B3H Node address : 41 Node address : 40
02B4H Node address : 43 Node address : 42
02B5H Node address : 45 Node address : 44
02B6H Node address : 47 Node address : 46
02B7H Node address : 49 Node address : 48
02B8H Node address : 51 Node address : 50
02B9H Node address : 53 Node address : 52
02BAH Node address : 55 Node address : 54
02BBH Node address : 57 Node address : 56
02BCH Node address : 59 Node address : 58
02BDH Node address : 61 Node address : 60
02BEH Node address : 63 Node address : 62

6 F 3 B 0 3 6 4

Scan type Code (hexadecimal)

Unassigned 00H

Bit strobe mode 01H

Polling mode 02H

Polling & strobe 03H

Reserved Other

 73 

(7) The Number of Total Devices (029EH: 1 word)

Indicates the number of the slave devices, operable on the network, specified by a parameter
setting request from the T2/T2E/T2N (setting information)

(8) The Number of Online Devices (029DH: 1 word)

Indicates the number of the slave devices which are performing data input/output with the DN211
(execution information).

(9) The Number of Bit Strobe Devices (029CH: 1 word)

Indicates the number of the bit strobe mode slave devices, operable on the network, specified by a
parameter setting request from the T2/T2E/T2N (setting information).

(10) The Number of Polling Devices (029BH: 1 word)

Indicates the number of the polling mode slave devices, operable on the network, specified by a
parameter setting request from the T2/T2E/T2N (setting information).

Note: For the slave devices which support both the polling mode and bit strobe mode, both of the bit
strobe devices and polling devices are counted.

6 F 3 B 0 3 6 4

(11) The Polling No-Response Device Map (0297H - 029AH: 4 words)

Indicates, per bit, the individual polling-mode devices not responding to the transmission from the
DN211.The value in each frame in Table 4.8 indicates the node address of a slave device.
When a slave device becomes not responding, the corresponding bit turns ON. The bit for the
normal slave device is set to OFF. The corresponding bit for the slave device not selected is also set
to OFF.

F E D C B A 9 8 7 6 5 4 3 2 1 0

0297H 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0298H 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
0299H 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
029AH 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48

Table 4.8 Polling No-Response Slave Devices

(12) The Bit Strobe No-Response Device Map (0293H - 0296H: 4 words)

Indicates, per bit, the individual bit-strobe mode salve devices not responding to the transmission
from the DN211. The value in each frame in Table 4.9 indicates the node address of a slave device.
When a slave device becomes not responding, the corresponding bit turns ON. The bit for the
normal slave device is set to OFF. The corresponding bit for the slave device not selected is also set
to OFF.

F E D C B A 9 8 7 6 5 4 3 2 1 0

0293H 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0294H 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
0295H 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
0296H 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48

Table 4.9 Bit Strobe No-Response Slave Devices

 74 

(13) Input/Output Data Setting Information (010BH - 028AH: 384 words)

Indicates , per slave device (node address: NA), the allocations of input/output data for slave
devices in the input/output data area. The input/output data setting information has 6 words per 1
slave device.

Figure 4.7 indicates the top addresses of areas where individual node information is stored. Table

4.10 lists the meanings per slave device.

After the slave device parameters are set, data will be input in these areas when the
DN211 is set to run mode (transmission enabled status) by an operation mode control
request.

"0" is set to the areas where no slave device is found.

010BH NA = 0 018FH NA = 22 0213H NA = 44

0111H NA = 1 0195H NA = 23 0219H NA = 45
0117H NA = 2 019BH NA = 24 021FH NA = 46

011DH NA = 3 01A1H NA = 25 0225H NA = 47

0123H NA = 4 01A7H NA = 26 022BH NA = 48

6 F 3 B 0 3 6 4

0129H NA = 5 01ADH NA = 27 0231H NA = 49

012FH NA = 6 01B3H NA = 28 0237H NA = 50

0135H NA = 7 01B9H NA = 29 023DH NA = 51

013BH NA = 8 01BFH NA = 30 0243H NA = 52

0141H NA = 9 01C5H NA = 31 0249H NA = 53
0147H NA = 10 01CBH NA = 32 024FH NA = 54

014DH NA = 11 01D1H NA = 33 0255H NA = 55

0153H NA = 12 01D7H NA = 34 025BH NA = 56
0159H NA = 13 01DDH NA = 35 0261H NA = 57

015FH NA = 14 01E3H NA = 36 0267H NA = 58

0165H NA = 15 01E9H NA = 37 026DH NA = 59

016BH NA = 16 01EFH NA = 38 0273H NA = 60

0171H NA = 17 01F5H NA = 39 0279H NA = 61
0177H NA = 18 01FBH NA = 40 027FH NA = 62

017DH NA = 19 0201H NA = 41 0285H NA = 63

0183H NA = 20 0207H NA = 42
0189H NA = 21 020DH NA = 43

Figure 4.7 Input/Output Data Setting Information Addresses

 75 

Example) Input/output data setting information for node address = 1

• Input data offset indicates the offset address (in bytes) from the top (0000H) of input

data area.

• Output data offset indicates the offset address (in bytes) from the top (0080H) of

output data area.

• There are no items for the offset of bit strobe output data and for the number of bytes

because of the bit strobe output data area.

Table 4.10 Input/Output Data Setting Information for Node Address = 1

0111H Bit strobe input data offset
0112H Number of bit strobe input data bytes
0113H Polling input data offset
0114H Number of polling input data bytes
0115H Polling output data offset
0116H Number of polling output data bytes

6 F 3 B 0 3 6 4

(14) The Local Station Node Address (010AH:1 word)

The hexadecimal node address of the local station, specified with the rotary switch on the side face
of the module, is stored (00H - 3FH).

(15) The Network Communication Rate (0109H:1 word)

The network communication rate, set with the DIP switch on the front panel, is stored.

00H: Unassigned (setting disabled)
01H: 500kbps
02H: 250kbps
03H: 125kbps

(16) The Operation Mode on Busoff Occurring (0108H:1 word)

The DN211's operation mode setting is stored when the DN211 detects busoff state of the local
station.

00H: When busoff is detected, the module will be set to standby mode, followed by the

initialization of the CAN controller.
The procedure for resuming transmission is the same for starting ordinary
transmission. Chapter 5 describes the transmission start procedure.

01H: When busoff is detected, the operation mode of the module is left intact, and the

CAN controller is initialized, followed by resuming communication, if possible.

(17) Yes/No of Supplying the Network Power (0107H:1 word)

The supply mode of the network power is stored.

00H: Network power normal
01H: Network power abnormal

 76 

6 F 3 B 0 3 6 4

 77 

4.4 Allocating Slave Device Data to the Input/Output Data Area

∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼

∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼

Reception/transmission data of slave devices will be allocated to the input/output data area in the
order from smaller to larger node addresses. For example, in Table 4.11, Slave Device
Configuration, the input data area/output data area is allocated to the top and the subsequent
addresses without skipping, as shown in Figure 4.8. Allocation will be executed when run mode
(transmission state enabled) is set by an operation mode control request after setting slave device
parameters.

Table 4.11 Slave Device Configuration (sample)

Node address Transmission size Reception size

10 2 bytes 4 bytes
11 4 bytes 2 bytes
12 6 bytes 6 bytes
20 3 bytes 4 bytes
30 4 bytes 1 byte
40 4 bytes 6 bytes

6 F 3 B 0 3 6 4

Output data area Input data area

F· · · · · · · · · · · · · · · · 0 F· · · · · · · · · · · · · · · · 0
0080H NA = 10 0000H
0081H 0001H
0082H
0083H 0003H
0084H NA = 12 0004H NA = 12
0085H 0005H
0086H NA 0006H
0087H No allocation = 20 0007H
0088H 0008H No allocation NA = 30
0089H

008AH 000AH NA = 40
008BH

∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼

Figure 4.8 Input/Output Data Area in Slave Device Configuration (sample)

NA = 11

0002H NA = 11

NA = 30

0009H

NA = 40

000BH

∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼∼

NA = 10

NA = 20

CAUTION

1. When a slave device has odd transmission/reception bytes in size, the actual size plus 1

2. When you add a new slave device, enter a new value larger than the node addresses of the

3. Don't change the input/output data size for slave devices (FLEX-I/O, etc.) which are flexible in

byte are allocated in the DN211 input/output area.

present slave devices. For Figure 4.8, enter a value larger than "41"for the node address of a
new slave. If the node address of a new slave device is set to "18", allocating data area of
node addresses 20/30/40 will be shifted.

data allocation size. If changed, the slave devices with a node address larger than that of the
slave device changed data size will be shifted in their data allocation.

 78 

4.5 The Semaphore Area

This area is used for issuing a request from the T2/T2E/T2N for operating the DN211, or for
reading the DN211's response to a request. The addresses in Figure 4.9 indicate the word
addresses seen from the T2/T2E/T2N.

02CFH Reserved (1 word)

02D0H

6 F 3 B 0 3 6 4

Acknowledgement area (100 words)

0334H

Request area (200 words)

03FCH Acknowledgement flag register (1 word)
03FDH Request flag register (1 word)
03FEH Reserved (1 word)

03FFH Request register (1 word)

Figure 4.9 The Semaphore Area Configuration

 79 

6 F 3 B 0 3 6 4

(1) The Request Register (03FFH: 1 word): T2/T2E/T2N → DN211

This register is used for notifying the DN211 of a request when the T2/T2E/T2N issues the request
to the DN211. After writing "1" in the "request flag register," the ladder program of the
T2/T2E/T2N writes "256 (0100H)" in this register.

"0": No notice.
"256": Noticed

After reading a request from the "request area," the DN211 sets this register to "0."

(2) The Request Flag Register (03FDH: 1 word): T2/T2E/T2N → DN211

This register is used when the T2/T2E/T2N issues a request to the DN211. After writing request
data in the "request area," the ladder program of the T2/T2E/T2N writes "1" in this register.

"0": No request.
"1": A request is issued from the T2/T2E/T2N to the DN211
"Value other than 0 and 1": Reserved

The DN211 sets this register to "0" after reading a request in the "request area."

(3) The Acknowledgement Flag Register (03FCH: 1 word): DN211 → T2/T2E/T2N

This register is used for notifying the T2/T2E/T2N of the DN211's response after the T2/T2E/T2N
issues a request to the DN211. The ladder program of the T2/T2E/T2N checks this register for "1"
to be set after a request is issued to the DN211. When "1" is set to this register, the ladder program
reads response data of the DN211 from the "acknowledgement area" before writing "0" in this
register.

"0": No response.
"1": Responded to the T2/T2E/T2N from the DN211
"Value other than 0 and 1": Reserved

(4) The Request Area (0334H - 03FBH: 200 words): T2/T2E/T2N → DN211

Request data is written when the T2/T2E/T2N issues a request to the DN21.
The data is written in the area beginning "0334 H" as the top address.
The T2/T2E/T2N has the following six types of requests to the DN211.

• Reset request

• Parameter setting request (local node)

• Parameter setting request (slave device)

• DN211 operation mode control request

• RAS information read request

• Time setting request

Each of the six requests has a different composition of request data, which is described in "4.6
Requests to the DN211."

(5) The Acknowledgement Area (02D0H - 0333H: 100 words): DN211 → T2/T2E/T2N

When the T2/T2E/T2N issues a request to the DN211, the DN211 sets response data to the
T2/T2E/T2N to this acknowledgment area. The response data is set at the addresses beginning "02
D0H." The request data composition is described in "4.6 Requests to the DN211."

 80 

(6) How to Use the Semaphore Area

Writing in the

request area

ment area

Requested

acknowledgement

Reading the

Figure 4.10 illustrates the usage of the areas and registers discussed at (1) to (5).
The squares in oblique lines in the figure indicate that "1" has been set to the flag registers and that

"256" has been set to the request register.
a) Use a READ instruction to the acknowledgement flag register to check for "0."

If a value other than "0" is found, write "0" in this area (first time only)

b) Use a WRITE instruction to write request data to the DN211 in the request area (top address:

0334H).
c) Use a WRITE instruction to write "1" in the request flag register.
d) Use a WRITE instruction to write "256" in the request register.
e) Use a READ instruction to read the acknowledgement flag register and waits until "1" is set to

the register.
f) Use a READ instruction to read response data of the DN211 from the acknowledgement area

when "1" is found in the acknowledgement flag register. (top address: 02DOH).
g) Use a WRITE instruction to write "0" in the acknowledgement flag register.

→ Returns to b).

Reading the

acknowledge-

T2/T2E/T2N

6 F 3 B 0 3 6 4

Request flag
register

Request
register

Acknowl­edgement
flag register

DN211

Reading the
flag register

Request notification

Completing reading
the request area

Responded

DN211

internal processing

request

area

Figure 4.10 How to Use the Semaphore Area on Requests

Writing in the

acknowledgment area

Completes
reading the
acknowledge

-ment area

(7) Cautions When Using the Semaphore Area

a) Since only a pair of request area and acknowledgment area is furnished, issue the next

request after the DN211 returns the acknowledgement to a request from the

T2/T2E/T2N.
b) Don't write data (no WRITE instruction) in the acknowledgement area /

acknowledgement flag register. Otherwise, data could be destroyed.
c) When a WRITE instruction writes data in the request area, be careful of the top

address and the data size to be written. Failing to do so could lead to the destruction of

other data, causing the DN211 to get malfunctioned.

 81 

6 F 3 B 0 3 6 4

 82 

4.6 Requests to the DN211

When requested, an error is responded. The error codes are explained

This section describes different types of requests that the T2/T2E/T2N issues to the DN211. There
are six such types of requests that the T2/T2E/T2N issues to the DN211.

The six types of requests are classified into those executable and those not executable, depending
on the DN211's operation mode, which is explained in "4.6.1 The DN211 Operation Modes." Table

4.12 lists the relation between different types of requests and the operation modes.
The six types of requests are detailed in "4.6.2 Reset Request."

6 F 3 B 0 3 6 4

Table 4.12 List of Requests

Standby mode (STBY)Operatin mode

Local node

Parameters

unassigned

Local node

Parameters

assigned

Request name
[request code]

Reset
[0011H]

Paremeter setting
(local node)[0012H]

Parameter setting
(slave device)[0012H]

Operation mode control
[0013H]

RAS information reading
[0015H]

Time setting
[0018H]

Down mode

(DOWN)

Initialization

mode

(INIT)

× ¡ ¡ ¡

× × ¡ ¡ ×

× × ¡ ¡ ×

× × × ¡ ¡

¡ × ¡ ¡ ¡

× × ¡ ¡ ¡

¡ : Request enabled

: Though the request is enabled, an error could be responded depending on the down cause.

See "Table 4.4 Down Information" for the possible down cause.

Run mode

(RUN)

× : Request disabled ...

in "4.7 Completion Status."

 83 

4.6.1 The DN211 Operation Modes

switch ON the power

Reset request

The DN211 has the following operation modes:

1) Initialize Mode

• The DN211 is in the process of resetting when the power is turned ON or reset is requested.

• The reset processing turns "standby mode" when the reset processing is completed

succes sfully.

• The reset processing turns "down mode" when the reset processing fails to complete

succes sfully (e.g, when an error occurs in self-testing).

• Don't issue an instruction from the user program of the T2/T2E/T2N side during "initialize

mode."

2) Standby Mode

• The DN211 turns this mode when the reset processing is completed successfully after you turn

ON the power or request resetting.

• An operation mode control request can changes run mode to standby mode.

• Only this mode allows you to set the parameters of the local node/slave devices to the DN211.

• Unless the parameters of the local node is set, "run mode" cannot be set from this mode.

3) Run Mode

• After the parameters of the local node are set, an operation mode control request allows you to

change to run mode.

• This mode allows the DN211 to transmit to salve devices.

• This mode allows you to select a transmission mode (polling mode/bit strobe mode) with slave

devices.

• This mode allows you to select a transfer mode (synchronous/asynchronous mode) between
the T2/T2E/T2N ⇔ DN211.

4) Down mode

• Indicates that the DN211 has turned unrecoverable abnormal state.

• A reset request can change to "standby mode." If such a reset request gets an error response,

turn OFF and ON the power for recovery.

• See "Table 4.4 Down Information" for the possible cause of the down mode.

Figure 4.11 illustrates transitions of the DN211 operation modes. Inside square frames indicates the
operation mode of the DN211. The operation mode in thick squared frame is the one that the user
program can control. The thick arrowheads indicate the request that the user program can specify.

6 F 3 B 0 3 6 4

Power downed

Initialize

Self-check
completed
unsuccessfully

switch ON the power

Down

Self-check completed successfully

Reset request

Run request

Reset request

or

Unrecoverable error occurred

Standby

a) Standby request
b) T2/T2E/T2N: RUN → HALT
c) Busoff occurred

For the case BUSOFF on DIP­SW on front panel remains ON.

Run

(transmission enabled)

Figure 4.11 The DN211 Operation Modes

CAUTION

1. If the T2/T2E/T2N turns into HALT/ERROR mode, the DN211 in run mode becomes standby
mode.

 84 

4.6.2 Reset Request

(1) The Function

This request is used for resetting the DN211 from theT2/T2E/T2N. When receiving a reset request,
the DN211 executes initialization of the module. This request also can delete the scan list
(parameters of the slave devices being linked to the network) saved in the internal non-volatile
storage of the DN211.

During normal operation:

When a reset request is executed, the DN211 turns waiting for a parameter setting request
(standby mode). No response will be made to the T2/T2E/T2N when a reset request is completed
successfully. To confirm successful completion of the reset request, check the station status
(05D5H) for transiting from "initialize mode" to "standby mode."

When in abnormal state:

An error response (completion status) will be returned to the T2/T2E/T2N when the request is not
accepted.

INZ bit (14 bits)

STBY bit (12 bits)

6 F 3 B 0 3 6 4

Reset request Reset completion

NCOIN bit (6 bits)
(when clearing the scan list)

Station status 4000H 2000H/2040H

Figure 4.12 Station Status Operation on Reset Request

(2) The Data Part Format

a) Request

Request area
0334H Request code (0011H)
0335H Scan list clear 0: Don't clear it / 1: Clear it

b) Acknowledgement (only for abnormal state)

Acknowledgement area
02D0H Request code (0011H)
02D1H Completion status

See "4.7 Completion Status" for the above completion status.

(3) Execution Time: Since the T2/T2E/T2N writes "1" in the request register until the station status

changes to "2000H/2040H" from "4000H"

• When the scan list is found in the non-volatile storage: Scan list is not cleared... Approx. 1 second

Scan list is cleared ... Approx. 9 seconds

• When no scan list is found in the non-volatile storage: No scan list cleared ... Approx. 9 seconds

Scan list is cleared ... Approx. 9 seconds

(4) Others

• The 7-segment LED goes out during initialization processing after a reset request is accepted.

• Startup time takes approx. 9 seconds after switching ON the power when no scan list is found in

the non-volatile storage.

CAUTION

 85 

6 F 3 B 0 3 6 4

1. Neither issue a request from the T2/T2E/T2N to DN211 while the DN211 is being reset nor

execute data input/output. Otherwise, the instruction requested will be completed abnormal
(error of station mode abnormal), or the module self-check will fail turning into down mode.

 86 

4.6.3 Parameter Setting Request (local node)

(1) The Function

This request is used for setting the "local node parameters" of the DN211. This request can be
issued only when the DN211 is in standby mode.

After setting the "local node parameters" and "slave device parameters," set the DN211 to "run
mode (transmission-enabled)" by following "4.6.5 Operation Mode Control Request." If the slave
device parameters have already been set into the non-volatile storage of the DN211, set the
DN211 to run mode by following "4.6.5 Operation Mode Control Request" after setting "local node
parameters."

(2) Data Part Format

a) Request

Request area
0334H Request code (0012H)
0335H Request type = 0
0336H Port No. = 0
0337H Local station node address Setting value : 0 to 63
0338H Polling transmission mode Setting value: 0, 1
0339H Scan interval wait time Setting value: 2 to 10,000 ms

033AH Background poll ratio Setting value: 1 to 65535
033BH Retransmission counter Setting value: fixed at 1
033CH Transmission timing Setting value: in ms

6 F 3 B 0 3 6 4

b) Acknowledgement

Acknowledgement area
02D0H Request code (0012H)
02D1H Completion status

See "4.7 Completion Status" for the above completion status.

c) Local Station Parameters

Table 4.13 Local Station Parameters (1/2)

Parameter Description

Polling transmitting mode 0: Makes a polling request to all slave devices and waits for the polling

Scan interval wait time Specifies the wait time until starting the next access after completing

Background poll ratio Accesses the devices to which background polling was specified

Retransmission counter Fixed at "1"

response in batch.

1: Waits for polling response after requesting polling by the slave device.

access to all slave devices.
Minimum value: 2 ms Maximum value: 10,000 ms

(setting with slave parameters) at scan interval set to the poll ratio.
Example) When 5 is specified, access is made by 5 scans.
This parameter is effective both for polling mode devices 1 bit strobe

mode devices.

 87 

6 F 3 B 0 3 6 4

Table 4.14 Local Station Parameters (2/2)

Parameter Description

Transmission timing

d) Supplement to the Polling Transmission Mode
The DN211 resolution varies when a slave device in polling mode results in no response after

selecting the polling transmission mode.
◎ When the polling transmission mode = 0

• The master device performs polling requests asynchronously with the responses of slave

devices in polling mode; the master device waits for the polling response from a slave device
for 20 ms after executing a request. When the 20 ms exceeds, the next scan starts.

Is the value for slave devices to detect transmission timeout when the
DN211 doesn't access for a certain interval or more.

Set a value larger than the scan cycle to slave devices(usually, 100 ms
or more).

• When a slave device with background polling is installed, set a value of
time longer than (scan cycle x poll ratio).

• For synchronous mode communication, an interval time value
longer than the transmission interval of the user program must be

specified.

• As long as a no-responding slave device is found, the master device performs 20 ms of

response wait time per scan.

• The real scan cycle, when a no-responding slave device is found, is expressed in the

fol lowing formula:

Real scan cycle = Real scan cycle in normal operation + 20 ms

◎ When the polling transmission mode = 1

• The master device checks for the response from a slave device in polling mode and

sequentially executes polling requests to individual slave devices. When polling results in no
response from a slave device, the master device waits for 20 ms before executing a polling
request to the next slave device.

• When three consecutive timeouts occur for a no-responding slave device, the slave device is

delisted from the scan list in the DN211. This will allow the DN211 to transmit with the
remaining slave devices in normal operation, and no wait time for response takes place.

• Only the slave devices which have three consecutive timeouts of no response will be delisted

from the scan list. When a slave device has two consecutive timeouts of no response but
responds to the third polling, the number of timeouts of no response is cleared.

• The DN211 periodically checks for the response from the slave devices delisted from the

scan list; if a delisted slave device responds, the device is re-registered in the scan list.

• When n units of slave devices results in no response at the same time, the real scan cycle for

three consecutive timeouts is expressed in the following formula.

Real scan cycle = Real scan cycle in normal operation + n units x 20 ms

 88 

6 F 3 B 0 3 6 4

e) When a slave device in bit-strobe mode results in no response

The master device executes bit-strobe requests disregarding the polling transmission mode
selected; it waits for the bit-strobe response from a slave device for 20 ms after executing a
request. After the 20 ms of response wait time passes, the next scan starts.

• As long as a no-responding slave device is found, the master device executes 20 ms of

response wait time per scan.

• When a no-responding slave device is found, the real scan cycle is expressed in the fo llowing

formula.

Real scan cycle = Real scan cycle in normal operation + 20 ms

Usage Recommendation

1. Set the node address of your DN211 to a value smaller than the node addresses of slave
devices(because of the feature of CAN currently used in the DeviceNet).

 89 

4.6.4 Parameter Setting Request (slave device)

(1) The Function

This request is used for setting "slave devices parameters" in the DN211. The request can be
issued only when the DN211 is in standby mode.

Up to 10 salve devices can be set per parameter setting request.

As "slave devices parameters" setting is stored in the non-volatile memory of the DN211, no
additional setting is required when switching ON the power as long as the current slave devices
configuration is unchanged. When the slave devices parameters in the non-volatile memory are
identical with the slave devices parameters newly requested, no writing is executed into the non­volatile memory.
When the slave devices configuration is changed, delete the slave devices parameters before
registering new slave devices parameters.

Up to 300 times of slave devices parameters setting are available in the non-volatile
memory of the DN211.

(2) Data Part Format

a) Request

Request area
0334H Request code (0012H)
0335H Request type = 1
0336H Number of request devices Number of slave devices set by this request
0337H Port Number Fixed at 0
0338H Slave node address Setting value: 0 to 63
0339H Vendor ID * 1
033AH Product type * 1

033BH Product code * 1
033CH Scan type Setting value: 0, 1, 2
033DH Poll background Setting value: 0, 1

033EH Bit strobe reception size * 1

033FH Polling reception size * 1
0340H Reserved Fixed at 0
0341H Polling transmission size * 1
0342H Reserved Fixed at 0
0343H Major revision * 1
0344H Minor revision * 1
0345H Reserved Fixed at 0
0346H Reserved Fixed at 0
0347H Port number
0348H Slave node address
0349H Vendor ID

:

* 1: Refer to the description of the slave device.

Specify the polling transmission size/bit strobe reception size in bytes.

6 F 3 B 0 3 6 4

First slave device
setting information

Second slave device
setting information

 90 

6 F 3 B 0 3 6 4

b) Acknowledgement

Acknowledgement area
02D0H Request code (0012H)
02D1H Completion status

See "4.7 Completion Status" for the above completion status.

c) Slave Device Parameters

For slave device parameters, refer to the description of the relevant slave devices except for
the parameters listed in the following Table 4.15.

Note the DN211 has the following restrictions in transmitting " 0 byte" to a slave device.

Restrictions

When a slave device fails to communicate with the DN211 due to some reason (power of
the slave device side turned OFF, connector removed, etc.), the DN211 cannot identify
the slave device being malfunctioned.

Even after the cause of the failure is solved, no communication between the slave
device ⇔ DN211 can be resumed.

Note:
Though the present DN211 has the above-mentioned restrictions, an upgraded version
of the internal software will solve those restrictions.

Table 4.15 Slave Device Parameters

Parameter Description

San type Specifies the transmission system of a slave device.

0: Bit strobe
1: Polling
2: 2: Bit strobe and polling

Poll background polling Specifies an access interval that the DN211 can have to a device.

00: Scan polling (accessing for every scan)
01: Background polling (accessing by the number of scan times

specified by the poll ratio)

No value other than 0, 1, or 2 can be
specified (reserved).

 91 

(3) Other

• It takes about 4 seconds to set the parameters of a slave device to the non-volatile storage of

the DN211.

• While slave device parameters are being set, the local node address is blinking on the 7-

segment LED.

CAUTION

1. The parameter setting request (slave device) sets the parameters of slave devices on to the
non-volatile memory in the DN211. As long as the slave devices configuration is unchanged,
you don’t need to execute this request every time when the power is switched ON. In
addition, when the parameters of the slave device requested and the parameters of the slave
device in the non-volatile memory are same, this setting request is not executed.

2. When the slave devices configuration needs to be changed, delete the salve devices
parameters using a reset request before setting new slave devices parameters.

3. The number of times available for setting slave devices parameters in the non-volatile memory
of the DN211 is 300 times.

4. The DN211 has the following restriction for transmitting "0 byte" to a slave device from the
DN211.

• When a slave device comes into no communication state with the DN211 due to some

reason (for example, the power of the slave device is OFF; the connector is disconnected,
etc.), the DN211 cannot recognize the slave device is abnormal.
Even after the cause of the failed communications is solved, the DN211 and the slave
device cannot communicate with each other.

6 F 3 B 0 3 6 4

Note: The above restriction of the present DN211 will be solved by a version-up of the internal
software.

 92 

4.6.5 Operation Mode Control Request

(1) The Function

Specifies the operation mode of the DN211 module. When the DN211 is neither in down mode nor
initialize mode, a request is enabled. Run mode (transmission enabled) is available only when the
DN211 is in standby mode and the local node parameters are set. When the DN211 is set to run
mode, slave device data will be allocated to the input/output data area.

(2) Data Part Format

a) Request

Request area
0334H Request code (0013H)
0335H Specified information

Specified information: "1" has some meaning.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

0 0 0 0 0 0 0 0 0 0

6 F 3 B 0 3 6 4

STBY BITS START

RUN POLL SYNC

Figure 4.13 Composition of Specified Information Bits

Table 4.16 Meaning of Specified Information Bits

BIT Name Description

13 STBY Standby request: changes from run mode to standby mode.
12 RUN Run request: changes standby mode to run mode.
10 BITS Bit strobe mode transmission enabled

9 POLL Polling mode transmission enabled
4 START 1: Polling and bit strobe transmission start 0: Stop transmission

3 SYNC

T2/T2E/T2N ⇔ DN211 transfer mode
…1: Synchronous 0: Asynchronous

b) Acknowledgement

Acknowledgement area
02D0H Request code (0013H)
02D1H Completion status

See "4.7 Completion Status" for above completion status.

(3) Others

• The following combinations of requests are forbidden..

¬ standby request and run request are requested simultaneously.

- The already running mode (standby/run) is requested

• See the station status for the actual mode change confirmation.

• When you are changing BIT 10, 9, 4, or 3, first change to standby mode before requesting a run

request and a new setting.

• When BITs 10, 9, 4, and 3 are set to "1", no standby request is allowed.

 93 

4.6.6 RAS Information Read Request

(1) The Function

Reads the RAS information on the DN211 from the T2/T2E/T2N. This RAS information includes
RAS history counter, event history, and execution node information (execution information of the
slave devices that DN211 has); these three types of information are different from those in the
RAS information area.

Unless the DN211 is in initialize mode, these types of information can be read anytime.
The content of the RAS data read is explained in "6.3 RAS Information Reading Data."

(2) Data Part Format

a) Request

Request area

0334H Request code (0015H)
0335H Request information type

6 F 3 B 0 3 6 4

0336H Start position
0337H Number of events to read

The dotted line is valid only for event history.
A history of up to 10 events can be read.

Request type: 1…RAS history, 2…Event history, 3…Execution node information,

4…RAS information clear

Start position: Specifies from where to read event history.

0 specified: Newest event

b) Acknowledgement

Acknowledgement area

02D0H Request code (0015H)
02D1H Completion status
02D2H Number of RAS information words

02D3H RAS information
:
:

Number of RAS data words read

See "4.7 Completion Status" for the above completion status.

 94 

4.6.7 Time Setting Request

(1) The Function

Performs the time setting in the DN211. This time is used for event history data, which is read by
"RAS information read request." When the DN211 is in down mode or initialize mode, this function
cannot be used.

(2) Data Part Format

a) Request

0334H Request code (0018H)
0335H Month Year

0336H Hour Day
0337H Second Minute

6 F 3 B 0 3 6 4

Request area

b) Acknowledgement

Acknowledgement area
02D0H Request code (0018H)
02D1H Completion status

See "4.7 Completion Status" for the above completion status.

(3) Other

• Use to the BCD codes to enter a year, month, day, hour, minute, and second.

• Enter the last two digits of the Western calendar in the year item. For the year 2000, enter 00.

Example: 12:20:00, September 30, 1997

0334H 0118H
0335H 0997H
0336H 1230H
0337H 0020H

• Since the time set above will be updated by the timer in the DN211, it can be different from the

time of the T2/T2E/T2N. Daily adjustment of time is recommend .

 95 