We reserve the right to make changes to functions, technical data, standards, drawings and parameters.

SIMOVERT MASTERDRIVES Operating Instructions

ä
Communication Board DeviceNetä

Summary of Equivalent Parameter Numbers

CUVC & CUMC DC-Master CU2
"CB parameter 1" P711.x U711.x P696
"CB parameter 2" P712.x U712.x P697
"CB parameter 10" P720.x U720.x P705
"CB/TB actual values" P734.01 to P734.16 U734.01 to U734.16 P694.01 to P694.16
"CB/TB diagnostics" r732.x n732.x P731.x
"CB/TB TLg OFF Time" P722.x U722.x P695
"parameterizing enable" P053 P927 P053

The reproduction, transmission or use of this document or its

contents is not permitted without express written authority.
Offenders will be liable for damages. All rights, including rights
created by patent grant or registration of a utility model or design,
are reserved.

We have checked the contents of this document to ensure that

they coincide with the described hardware and software.
However, differences cannot be completely excluded, so that we
do not accept any guarantee for complete conformance.
However, the information in this document is regularly checked
and necessary corrections will be included in subsequent
editions. We are grateful for any recommendations for
improvement. SIMOVERTâ Registered Trade Mark
Edition: VB 6SE7087-6NX84-0FK0
ã Siemens AG 1998 All rights reserved
09.2000 Contents Contents 09.2000

Contents 6 START-UP ........................................................................................................6-1

6.1 Parameterization ...............................................................................................6-1

1 DEFINITIONS ...................................................................................................1-1 6.2 Process data combination.................................................................................6-6

6.2.1 Setpoint channel (master to drive) ....................................................................6-7
6.2.2 Actual value channel (drive to master)............................................................6-10
2 PRODUCT DESCRIPTION...............................................................................2-1 6.2.3 Other CBD-relevant parameters .....................................................................6-12

6.3 Information for the DeviceNet master .............................................................6-14

3 MOUNTING INSTRUCTIONS ..........................................................................3-1 6.3.1 Creating EDS Stub File for CBD .....................................................................6-14
6.3.2 Using Explicit Messaging with a PLC Scanner ...............................................6-14

4 CONNECTING-UP............................................................................................4-1
7 TROUBLESHOOTING .....................................................................................7-1
4.1 Connecting-up the bus cable ............................................................................4-1
4.1.1 5-pin Open Connector X438 .............................................................................4-1 7.1 CBD Alarms and faults......................................................................................7-1
7.1.1 Alarms ...............................................................................................................7-1
4.2 EMC measures .................................................................................................4-2 7.1.2 Fault messages.................................................................................................7-3
4.2.1 Potential bonding ..............................................................................................4-2
4.2.2 Routing cables ..................................................................................................4-3 7.2 Diagnostics........................................................................................................7-5
7.2.1 Diagnostic LEDs................................................................................................7-5
4.3 Bus termination .................................................................................................4-3 7.2.2 CBD diagnostic parameters ..............................................................................7-7
7.2.2.1 DeviceNetä Status - parameter r731.02...........................................................7-9
4.4 Ground connection............................................................................................4-3

4.5 DeviceNet Power Supply and Power Tap.........................................................4-4 8 APPENDIX........................................................................................................8-1

4.6 CBD Power Requirements ................................................................................4-4 8.1 Technical data...................................................................................................8-1

4.7 Interface X438...................................................................................................4-4 8.2 Revision data ....................................................................................................8-1

8.2.1 Firmware Version (viewable by parameter "CB/TB diagnostics" index 26 and
through DeviceNetä) ........................................................................................8-1
5 DATA TRANSFER VIA DEVICENET...............................................................5-1

5.1 General Information ..........................................................................................5-1 9 CBD QUICK SETUP GUIDE ............................................................................9-1

5.2 Parameter area (PKW) .....................................................................................5-1 9.1 Overview ...........................................................................................................9-1

5.2.1 Use of PKW object ............................................................................................5-2
5.2.1.1 DeviceNet GET SINGLE ...................................................................................5-2 9.2 Required Hardware and Software.....................................................................9-1
5.2.1.2 DeviceNet SET SINGLE ...................................................................................5-3
5.2.1.3 DeviceNet response..........................................................................................5-3 9.3 Required CBD Setup Parameters for CU1 or CU2 Boards ..............................9-2
5.2.1.4 Parameter ID (PKE) ..........................................................................................5-6
5.2.1.5 Parameter index (IND) ....................................................................................5-12 9.4 Required CBD Setup Parameters for CUMC and CUVC Boards .....................9-4
5.2.1.6 Parameter value (PWE) ..................................................................................5-13
5.2.1.7 Rules for PKW object processing ...................................................................5-15 9.5 Required CBD Setup Parameters for DC Master Boards.................................9-4

9.6 Status Indication by LED’s ................................................................................9-5

5.3 Process data area (PZD) ................................................................................5-16
5.3.1 Setting the number of PZD words...................................................................5-16 9.7 Process Data (PZD) ..........................................................................................9-5
5.3.2 Setting the meaning of the PZD words ...........................................................5-19
5.3.3 Instructions and rules regarding process data processing .............................5-22 9.8 Parameter Data (PKW) ...................................................................................9-10

9.9 Creating EDS Stub File for CBD .....................................................................9-12

Siemens AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 1 2 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Definitions Definitions 09.2000

1 Definitions WARNING Electrical equipment has components which are at dangerous voltage
levels.
If these instructions are not strictly adhered to, this can result in severe
QUALIFIED For the purpose of this Instruction Manual and product labels, a bodily injury and material damage.
PERSONNEL "Qualified person" is someone who is familiar with the installation,
mounting, start-up and operation of the equipment and the hazards Only appropriately qualified personnel may work on this equipment or in
involved. He or she must have the following qualifications: its vicinity.
1. Trained and authorized to energize, de-energize, clear, ground and This personnel must be completely knowledgeable about all the
tag circuits and equipment in accordance with established safety warnings and service measures according to this User Manual.
procedures. The successful and safe operation of this equipment is dependent on
2. Trained in the proper care and use of protective equipment in proper handling, installation, operation and maintenance.
accordance with established safety procedures.
3. Trained in rendering first aid.
NOTE The information in this Manual does not purport to cover all details or
variations in equipment, nor to provide for every possible contingency
DANGER For the purpose of this Instruction Manual and product labels, "Danger" to be met in connection with installation, operation or maintenance.
indicates death, severe personal injury and/or substantial property
damage will result if proper precautions are not taken. Should further information be desired or should particular problems
arise which are not covered sufficiently for the purchaser’s purposes,
please contact your local Siemens office.
Further, the contents of this Manual shall not become a part of nor
WARNING modify any prior or existing agreement, commitment or relationship.
For the purpose of this Instruction Manual and product labels,
The sales contract contains the entire obligation of Siemens. The
"Warning" indicates death, severe personal injury or property damage
warranty contained in the contract between the parties is the sole
can result if proper precautions are not taken.
warranty of Siemens. Any statements contained herein do not create
new warranties nor modify the existing warranty.

CAUTION For the purpose of this Instruction Manual and product labels, "Caution"
indicates that minor personal injury or material damage can result if
proper precautions are not taken.

NOTE For the purpose of this Instruction Manual, "Note" indicates information
about the product or the respective part of the Instruction Manual which
is essential to highlight.

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 1-1 1-2 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Definitions

CAUTION Electrostatically sensitive devices (ESD)

Electronic modules contain electrostatically sensitive devices that can
easily be destroyed if they are improperly handled. However, if your
work does involve the handling of such devices, please observe the
following information:
♦ Electronic modules should not be touched unless work has to be
carried out on them.
♦ If it is essential for you to touch an electronic module, make sure
that your body is electrostatically discharged beforehand.
♦ Modules must not be allowed to come into contact with electrically
insulating materials such as plastic foil, insulating table tops or
clothing made of synthetic fibres.
♦ Modules may only be set down or stored on electrically conducting
surfaces.
♦ The soldering tip of soldering devices must be earthed before they
are used on modules.
♦ Modules and electronic components should generally be packed in
electrically conducting containers (such as metallized plastic boxes
or metal canisters) before being stored or shipped.
♦ If the use of non-conducting packing containers cannot be avoided,
modules must be wrapped in a conducting material before being put
into such containers. Examples of such materials include electrically
conducting foam rubber or household aluminium foil.

For easy reference, the protective measures necessary when dealing

with electrostatic sensitive devices are illustrated in the sketches below:
♦ a = Conductive flooring
♦ b = Anti-static table
♦ c = Anti-static footwear
♦ d = Anti-static overall
♦ e = Anti-static chain
♦ f = Earthing connections of cabinets

d
b d b d

e e

f f f f f

a c c a c a
Sitting Standing Standing / Sitting

Fig. 1-1 ESD protective measures

SIEMENS AG 6SE7087-6NX84-0FK0
SIMOVERT MASTERDRIVES Operating Instructions 1-3
09.2000 Product description Product description 09.2000

2 Product description By contrast, DeviceNetä IO Message Connections provide special-

purpose communication paths between a transmitting device and one
or more receiving devices. Application-specific I/O data moves across
an I/O Connection. The meaning of the data within an I/O Message is
Board CBD The documentation (English language only) is always included with the implied by the associated Connection ID.
board. It is not possible to order the documentation separately.
The CBD supports the Predefined Master/Slave Connection Set as
The communication board can either be ordered as a spare part or as a defined in the DeviceNetä specification. Both poll and bit strobe I/O
package with a mounting kit. The mounting kit consists of the messages are supported.
communication board CBD, manual, connector and mounting
components. The CBD follows the DeviceNetä Device Profile for the Communication
Adapter (Device Type 12). The Communication Adapter Profile was
The mounting kit part number is 6SX7010-0FK00. This includes the chosen so that all the flexibility and advanced features of the
board, DeviceNetä plug, and instruction book. MASTERDRIVE could be used by the DeviceNetä master. For this
The communication board only is has part number 6SE7090-0XX84- same reason, the CBD did not implement the DeviceNetä AC Drives
0FK0. This is only the board. profile.
1
The CBD communications board is the DeviceNetä interface for the The CBD DeviceNetä messages can be roughly sub-divided into three
complete MASTERDRIVES series. areas:
♦ SIMOVERT FC (Frequency Control) ♦ DeviceNetä Configuration data, i. e. channel allocation, time-outs,
♦ SIMOVERT VC (Vector Control) and I/O assembly selections which use Explicit Messages, and
♦ SIMOVERT SC (Servo Control) ♦ Process data, i. e. control words, setpoints/reference values and
♦ SIMOVERT MC (Motion Control) status information and actual values which use I/O Messages, and

The CBD communications board permits MASTERDRIVES to be ♦ Drive parameter data to read/write drive parameter values which
coupled to higher-level automation units or other field devices via the use the vendor specific PKW object and Explicit Messages.
DeviceNetä protocol. The drive is controlled using the process data, for example power-
The CBD communications board can be simply inserted in the drive on/power-off and setpoint input. The number of process data words (4,
electronics box, and operates with all of the software- and hardware 8, or 16) is selected at power-up by dedicated CB parameters or
versions of MASTERDRIVES. For some drives, a 6SE7090-0XX84- dynamically through DeviceNetä. The use of each process data word
0KA0 adapter board and a LBA board are also required. is set at the drive and is dependent on the actual function of each
particular drive. The process data is processed with highest priority and
The CBD supports both DeviceNetä Explicit Messages and I/O in the shortest time segments.
Messages to implement the equivalent of the process data and
parameter data portions of drive communications. The vendor specific PKW object is used to read and change drive
parameters by the master using DeviceNetä. The explicit messaging
For DeviceNetä, Explicit Message Connections provide generic, multi- channel is used. Using this PKW object, the user has free access to all
purpose communication paths between two devices. They provide the parameters in the base drive (CU) and an optional technology board
means by which typical request/response oriented functions are (TB) via DeviceNetä. Examples include: Reading-out detailed
performed (for example module configuration). diagnostic information, fault messages etc. Thus, without influencing
Closed Loop Control on CU ² the performance of the process data transfer, additional information can
or be requested by a higher-level system (for example a PC) for drive
Technology Board TB ³ DeviceNetä is a trademark of visualization.
Open DeviceNetä Vendor
Dual-Port-RAM Association (O.D.V.A.).

CBD
TM
DeviceNet

Fig. 2-1 Coupling CBD to the drive via the dual port RAM interface

1
CB = Communication Board, e. g. CBD
2
CU = Control Unit, e. g. CU1, CU2, CU3, CUVC, CUMC, DC Master
3
TB = Technology Board, e. g. T300, T100

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 2-1 2-2 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Product description

Open-loop control In the process data area (refer to Figure 1.1), all of the information is
and operator control transferred that is required to control a drive within a particular
of MASTERDRIVES technological process. Control information (control words) and setpoints
ä
via DeviceNetä are sent to the drive from the DeviceNetä master. Information
regarding the drive status (status words) and actual values are
transferred in the other direction.
The CBD communications board stores the received process data in
the dual port RAM in the same sequence as it is transmitted in the
telegram. Each word in the dual port RAM is assigned an address. The
contents of the dual port RAM in the drive (CU + if required TB) can be
freely connected via parameters, for example the second word in the
process data area of the telegram can be connected to be used as the
as speed setpoint to the ramp-function generator. The same
mechanism is also true for other setpoints and for each individual
control word bit. This mechanism is also true for data traffic in the
opposite direction when transferring actual values and status words to
the master.
Diagnostic LED’s provide the user with fast information regarding the
instantaneous status of the CBD. More detailed diagnostic information
can be directly read-out of the CBD diagnostics memory using a
diagnostics parameter.

SIEMENS AG 6SE7087-6NX84-0FK0
SIMOVERT MASTERDRIVES Operating Instructions 2-3
09.2000 Mounting instructions Mounting instructions 09.2000

3 Mounting instructions Electronics box slot Boards

+1.B1 (left) Standard board CU
+1.B3 (center) CBD / SCB1 / SCB2 / TSY
If a 6SE7090-0XX84-0KA0 adapter board is required, the backplane Option boards
+1.B2 (right) CBD / SCB1 / SCB2 / TSY /
bus adapter (local bus adapter LBA, Order No.: 6SE7090-0XX84-
TB (e. g. T100 or T300)
4HA0) must first be installed before the board is used. Otherwise the
CBD is inserted directly on the CU board.
Installing the LBA ♦ Remove the CU board (lefthand slot in the electronics box) using the NOTES TB (technology boards, e. g. T300), must always be inserted in slot
bus expansion handles after first removing the connecting cable to the PMU and +1.B2 (RIGHT in the electronics box)! When a TB board is inserted, a
both retaining screws TSY option board cannot be used.
♦ Insert the LBA bus expansion in the electronics box (position, refer
If only one option board is used, then this must always be inserted in
to the diagram) so that it snaps into place
slot +1.B2 (RIGHT in the electronics box)!
♦ Re-insert the CU into the lefthand slot, tighten-up the retaining
screws on the handles, and insert the connecting cable to the PMU
♦ For CU1, CU2, CU3:
Insert CBD on the lower position of the adapter board and screw
into place. Insert the adapter board into slot 2 (righthand side) or slot
3 (center) of the electronics box, and screw into place. Only one of
each option board type may be inserted in the electronics box. If
-X187 +1.B1
only one option board is inserted, then it must always be inserted at
slot 2 (right). +1.B3
+1.B2
♦ For CUVC, CUMC, DC Master: R
TE
Insert CBD on either the upper or lower position of the adapter AP
AD ARD
board and screw into place. Insert the adapter board into slot 2 BO

(righthand side) or slot 3 (center) of the electronics box, and screw

into place. Check the drive instruction book to determine how many
option boards of each type may be inserted in the electronics box. If
only one option board is inserted, then it must always be inserted at
slot 2 (right).
-X185

D
CB
-X438

Fig. 3-2 CBD on adapter board with bus connector and electronics box with free
slots +1.B2 and +1.B3

Fig. 3-1 Installing the local bus adapter NOTE When installing the CU control electronics board (slot +1.B1) and the
option board(s), ensure that the handles are screwed flush with the
The adapter board with the CBD attached can either be inserted at slot surface of the electronics box (so that the board isn’t tilted)!
+1.B2 or +1.B3. Please refer to Fig. 3-2 for the slot designations.
Please note, that slot +1.B3 is the center slot in the electronics box!

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 3-1 3-2 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Connecting-up Connecting-up 09.2000

4 Connecting-up The bus connector for terminal strip X438 is supplied loose. These
loose components can also be individually ordered from Phoenix
Contact or Messrs. Phoenix Contact GmbH & Co (bus connector):
Order designation:
WARNING SIMOVERT MASTERDRIVES operate at high voltages. Phoenix number: Combicon MSTB 2.5/5-ST-5.08-AU
Only qualified, trained personnel are permitted to work on the unit. (cable side-sockets)
Death, severe bodily injury or significant material damage could result if
this is not observed. Cable meeting DeviceNetä specifications must be used.
Hazardous voltages are still present in the drive up to 5 minutes after it Thin cable: Belden 3084A
has been disconnected from the supply due to the DC link capacitors. Thick cable: Belden 3082A or 3083A or 3085A
Thus, before opening the drive, wait until the capacitors have been
completely discharged.
Relation of DeviceNetä Data Rate and Cable Distances:
The power- and control terminals are at hazardous voltage levels even
when the motor is stationary. Data Rate Trunk Distance Drop Length
The converter must always be disconnected and locked-out before (thick Cable) Maximum drop Cumulative
work is started.
125K 500m (1640 ft) 6m (20 ft) 156m (512 ft)
If it is absolutely necessary to work with a converter opened, it should 250K 250m (820 ft) 6m (20 ft) 78m (256 ft)
be noted that you could come into contact with components and parts
at hazardous voltage levels (shock hazard!). 500K 100m (328 ft) 6m (20 ft) 39m (128 ft)

CAUTION CBD contains components which can be destroyed by electrostatic NOTE Thin cable may be used as trunk. Maximum distance is 100 meters
discharge. These components can be easily destroyed if incorrectly (328 feet) for any baud rate.
handled.
Also refer to the ESD cautionary measures in the introduction section,
General information
4.2 EMC measures
DeviceNetä specifications must be followed if the DeviceNetä bus is to
operate fault-free
4.1 Connecting-up the bus cable
4.1.1 5-pin Open Connector X438
4.2.1 Potential bonding
Terminal Function ä Wire Color
DeviceNetä
X438.1 V- Black power supply common Prevent potential differences (e. g. as a result of using different power
supplies), between the converters and the bus master:
X438.2 CAN- Blue
♦ Use potential bonding cables:
X438.3 Shield
• 16 mm2 Cu for potential bonding cables up to 200 m
X438.4 CAN+ White
• 25 mm2 Cu for potential bonding cables over 200 m
X438.5 V+ Red power supply +24 VDC ±1%
♦ Route the potential bonding cables so that there is the smallest
Table 4-1 Assignment of open connector X438 possible surface area between the potential bonding cable and
signal cables.
♦ Connect potential bonding cables to the ground/protective conductor
Adapter Board
Green
CBD
through the largest possible surface area.
X438
LED Yellow
Red .5 .4 .3 .2 .1
CAN+
V+

Shield

CAN-

V-

TOP

Fig. 4-1 Front view of CBD with diagnostic LEDs, terminal strip X438 and bus
connector

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 4-1 4-2 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Connecting-up Connecting-up 09.2000

4.2.2 Routing cables 4.5 DeviceNet Power Supply and Power Tap
Please observe the following instructions when routing cables: Powering of the DeviceNetä bus is described in the DeviceNetä
♦ Do not route bus cables (signal cables), directly in parallel with specification. A DeviceNetä power tap should be used to protect the
power cables. network, The general power supply specification follows:
♦ Signal cables and associated potential bonding cables must have ♦ +24 V DC
the lowest possible clearance between them and be as short as
♦ Ability to support linear and switching regulators
possible.
♦ Tolerance of: +24 V DC ± 1 % and current capability of 0-16 amps
♦ Power cables and signal cables should be routed in separate cable
(single and multiple supply applications)
ducts.
♦ Supply outputs must be isolated from the AC line and chassis
♦ Shields should be connected through a large surface area.

4.3 Bus termination 4.6 CBD Power Requirements

Each CBD draws a maximum of 35 ma worst case (at 11 VDC) from
To guarantee fault-free operation of the DeviceNetä bus, the bus cable
the DeviceNetä power supply.
must be terminated using bus terminating resistors at both ends of the
trunk as described in the DeviceNetä specifications. The CBD is technically called an "isolated node with transceiver
powered by the network". The transceiver and half of the optocouplers
The resistor requirements are:
are powered by the DeviceNetä network. But the rest of the node is
♦ 121 Ω powered by the AC line.
♦ 1 % Metal Film
♦ ¼ Watt

4.7 Interface X438

4.4 Ground connection Regulator
P5
Grounding of the DeviceNetä bus is described in the DeviceNetä
specification. The specification follows:
♦ "DeviceNetä should be grounded at ONE location. Grounding at
more then one location may produce ground loops, while not 1 2 3 4 5
grounding the network will increase sensitivity to ESD and outside P5
noise sources. The single grounding location should be at a power
Opto 5 V+
tap. Sealed DeviceNetä power taps are designed to accommodate
TxD
grounding. Grounding near the physical center of the network is also 4 CAN+
desired."
3 Shield
♦ "The trunk drain/shield should be attached to the power supply RxD
2 CAN-
ground or V- with a copper conductor that is either solid, stranded,
or braided. Use a 1" copper braid or a #8 AWG wire that is less than 1 V-
3 meters/10 feet in length. This should then be attached to a good
earth or building ground (such as an 8 foot stake driven into the
ground, attached to building iron or to the cold water plumbing)."
♦ "If the network is already grounded, do NOT connect the grounding
terminal of the tap or ground of the supply to earth. If more than one Fig. 4-2 Approximate bus interface circuit
supply is on the network, then connect the drain wire/shield at ONE
supply only, preferably near the physical center of the network."

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 4-3 4-4 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Data transfer via DeviceNet Data transfer via DeviceNet 09.2000

5 Data transfer via DeviceNet 5.2.1 Use of PKW object

The vendor specific PKW object, class 100 (64 hex), is used to read
and change 6SE70 drive parameters and technology board (if supplied)
5.1 General Information parameters by the DeviceNetä Master. The explicit messaging mode is
used.
When transferring useful data, a differentiation is made between In this object, only 2 instances are implemented. Instance number 0
parameter data (PKW) and process data (PZD) (also refer to Section 2 accesses the class attribute. Instance number 1 accesses all drive and
"Product description"). technology board parameter numbers. For instance 1, the attribute
The actual CAN data telegram consists of the protocol header, the CAN number must presently always be 1. The first and second bytes of
identifier, up to 8 bytes of useful data and the protocol trailer. However, DeviceNetä data are interpreted as a 16 bit word and contain the
the methods used by DeviceNetä allow a useful data area to be any Parameter ID (PKE) which is defined later in section 5.2.1.4. The third
reasonable length. If data longer than 8 bytes is required, a byte of DeviceNetä data (1 to 255) maps directly to the low byte of the
fragmentation protocol allows the data to be sent as series of Parameter index (IND) which is defined later in section 5.2.1.5. The
telegrams. fourth byte of DeviceNetä data is interpreted as the high byte of the
Normally PKW data is not used – since drive commissioning is Parameter index (IND) and is presently always set to 0. For the set
performed by SIMOVIS or other means. service, the fifth and sixth bytes of DeviceNetä data are interpreted as
a 16 bit word and contain the low word of the parameter value (PWE1)
Using the vendor specific PKW object (which will be described later),
and the seventh and eighth bytes of DeviceNetä data are interpreted
the PKW useful data area consists of:
as a 16 bit word and contain the high word of the parameter value
(1) 2 words or 4 bytes for parameter value read tasks (called a "Get" (PWE2) which are defined later in section 5.2.1.6.
DeviceNetä service) and
♦ A GET SINGLE service code is required for task ID’s of 1, 4, 6, and
(2) 4 words or 8 bytes for parameter value change tasks (called a 9. Task ID’s are defined in section 5.2.1.4.
"Set" DeviceNetä service) and
♦ A SET SINGLE service code is required for task ID’s of 2, 3, 7, 8,
(3) 3 words or 6 bytes for parameter value responses. 11, 12, 13, and 14.
Separate from the parameter data, the process data area for ♦ A not supported response is sent for task ID’s of 0, 5, 10, and 15.
MASTERDRIVES consists of 16 words. Normally only process data is
used to communicate to the drive by sending and receiving PZD data.
This process data is normally sent by "polled I/O". 5.2.1.1 DeviceNet GET SINGLE
The CBD groups these 16 words into 3 choices:
This section contains technical DeviceNetä details required if a generic
(1) the first 4 PZD words
DeviceNetä master is used for explicit messages. If a PLC scanner will
(2) the first 8 PZD words be used, this section and the following two sections (5.2.1.2 and
(3) all 16 PZD words 5.2.1.3) can be skipped and the section Using Explicit Messaging with a
PLC Scanner (section 6.3.2) should be referenced instead.

♦ A GET SINGLE is sent as a fragmented explicit message.

5.2 Parameter area (PKW) It uses 9 bytes.
PKW data is normally not used – since drive commissioning is
performed by SIMOVIS or other means. If PKW data is not used, this Byte No. [ ä Designation
DeviceNetä ]
section can be skipped.
1 [ FRAG] [XID] [SRC/DST MAC Id ]
You can process the following tasks using the PKW mechanism:
2 [ [R/R] [Service] ] 0x0E [Get_Attribute_Single]
♦ reading drive parameters
3 [ Class ] 100 [PKW Object] [Vendor specific]
♦ writing drive parameters
4 [ Instance ] 1 [Instance Number] [always 1]
♦ reading the parameter description (parameter type, max./min. value
5 [ Attribute ] 1 [Attribute Number] [always 1]
etc.)
6 [ Data ] [Low byte Parameter ID (PKE)]
7 [ Data ] [High byte Parameter ID (PKE)]
8 [ Data ] [Low byte Parameter index (IND)] [range 0 to 255]
9 [ Data ] [High byte Parameter index (IND)] [for future use]

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 5-1 5-2 Operating Instructions SIMOVERT MASTERDRIVES
 09.2000 Data transfer via DeviceNet Data transfer via DeviceNet 09.2000

5.2.1.2 DeviceNet SET SINGLE Example 1 Read value of parameter P101.4

This section also contains technical DeviceNetä details required if a To read parameter P101.4, we would use a Get_Attribute_Single
generic DeviceNetä master is used for explicit messages. If a PLC service code with class #100, instance #1, and attribute #1. The first 2
scanner will be used, this section and the following section (5.2.1.3) can data bytes make up a data word of 6065 hex [task Parameter ID
be skipped and the section Using Explicit Messaging with a PLC (PKE)]. The third and fourth data bytes make up a data word of 4
Scanner (section 6.3.2) should be referenced instead. [Parameter index (IND)]. For more details, refer to example 1 in the
Parameter ID (PKE) section 5.2.1.4 and in the Parameter index (IND)
section 5.2.1.5 later.
♦ A SET SINGLE is sent as a fragmented explicit message.
It uses 14 bytes.
♦ The GET SINGLE that would be sent by the master:
Byte No. [ ä Designation
DeviceNetä ]
Byte No. [ ä Designation
DeviceNetä ]
1 [ FRAG] [XID] [SRC/DST MAC Id ]
1 [ FRAG] [XID] [SRC/DST MAC Id ]
2 [ Fragmentation Protocol ]
2 [ [R/R] [Service] ] 0x0E [Get_Attribute_Single]
3 [ [R/R] [Service] ] 0x10 [Set_Attribute_Single]
3 [ Class ] 100 [PKW Object] [Vendor specific]
4 [ Class ] 100 [PKW Object] [Vendor specific]
4 [ Instance ] 1 [Instance Number] [always 1]
5 [ Instance ] 1 [Instance Number] [always 1]
5 [ Attribute ] 1 [Attribute Number] [always 1]
6 [ Attribute ] 1 [Attribute Number] [always 1]
6 [ Data ] 0x65 [Low byte Parameter ID (PKE)]
7 [ Data ] [Low byte Parameter ID (PKE)]
7 [ Data ] 0x60 [High byte Parameter ID (PKE)]
8 [ Data ] [High byte Parameter ID (PKE)]
8 [ Data ] 4 [Low byte Parameter index (IND)] [range 0 to 255]
9 [ Data ] [Low byte Parameter index (IND)] [range 0 to 255]
9 [ Data ] 0 [High byte Parameter index (IND)] [for future use]
10 [ Data ] [High byte Parameter index (IND)] [for future use]
11 [ Data ] [Low byte, low word parameter value (PWE1)]
♦ The response that would be sent by the drive:
12 [ Data ] [High byte, low word parameter value (PWE1)]
Byte No. [ ä Designation
DeviceNetä ]
13 [ Data ] [Low byte, high word parameter value (PWE2)]
1 [FRAG] [XID] [SRC/DST MAC Id ]
14 [ Data ] [High byte, high word parameter value (PWE2)]
2 [ [R/R] [Service] ] 0x8E [Get_Attribute_Single]
3 [ Service Data ] 0x65 [Low byte Parameter ID (PKE)]
5.2.1.3 DeviceNet response 4 [ Service Data ] 0x40 [High byte Parameter ID (PKE)]
This section also contains technical DeviceNetä details required if a 5 [ Service Data ] 0xA0 [Low byte, low word parameter value (PWE1)]
generic DeviceNetä master is used for explicit messages. If a PLC 6 [ Service Data ] 0x0F [High byte, low word parameter value (PWE1)]
scanner will be used, this section can be skipped and the section Using 7 [ Service Data ] 0x00 [Low byte, high word parameter value (PWE2)]
Explicit Messaging with a PLC Scanner (section 6.3.2) should be
8 [ Service Data ] 0x00 [High byte, high word parameter value (PWE2)]
referenced instead.

Bytes 1 and 2 are part of the DeviceNetä protocol.

♦ The response is always be sent as a non-fragmented explicit
message. It uses 8 bytes. The response from the drive starts with byte 3 which contains a value of
65 hex, followed by a data byte of 40 hex. These 2 data bytes make up
Byte No. [ ä Designation
DeviceNetä ] a data word of 4065 hex [response Parameter ID (PKE)]. For more
1 [ FRAG] [XID] [SRC/DST MAC Id ] details, refer to example 1 in the Parameter ID (PKE) section 5.2.1.4
2 [ [R/R] [Service] ] 0x8E or 0x90 [Get/Set_Attribute_Single] later.
3 [ Service Data ] [Low byte Parameter ID (PKE)] Next is a data byte of A0 hex, followed by a data byte of 0F hex. These
2 data bytes make up a data word of 0FA0 hex [low word parameter
4 [ Service Data ] [High byte Parameter ID (PKE)]
value (PWE1)]. Next is a data byte of 00 hex, followed by a data byte of
5 [ Service Data ] [Low byte, low word parameter value (PWE1)] 00 hex. These 2 data bytes make up a data word of 0000 hex [high
6 [ Service Data ] [High byte, low word parameter value (PWE1)] word parameter value (PWE2)]. Thus, parameter P101.4 has a value of
7 [ Service Data ] [Low byte, high word parameter value (PWE2)] 0FA0 hex. For more details, refer to example 1 in the Parameter value
(PWE) section 5.2.1.6 later.
8 [ Service Data ] [High byte, high word parameter value (PWE2)]

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 5-3 5-4 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Data transfer via DeviceNet Data transfer via DeviceNet 09.2000

Example 2 Set value of parameter P554.1 = 3001 hex a data word of 422A hex [response Parameter ID (PKE)]. For more
To set parameter P554.1 = 3001 hex, we would use a details, refer to example 2 in the Parameter ID (PKE) section 5.2.1.4
Set_Attribute_Single service code with class #100, instance #1, and later.
attribute #1. The first 2 data bytes make up a data word of C22A hex Next is a data byte of 01 hex, followed by a data byte of 30 hex. These
[task Parameter ID (PKE)]. The third and fourth data bytes make up a 2 data bytes make up a data word of 3001 hex [low word parameter
data word of 1 [Parameter index (IND)]. Next are two data bytes that value (PWE1)]. Next is a data byte of 00 hex, followed by a another
make up a data word of 3001 hex [low word parameter value (PWE1)]. data byte of 00 hex. These 2 data bytes make up a data word of 0000
Next are 2 more data bytes that make up a data word of 0000 hex [high hex [high word parameter value (PWE2)]. Thus, parameter P554.1 has
word parameter value (PWE2)]. For more details, refer to example 2 in a value of 3001 hex. For a more details, refer to example 2 in the
the Parameter ID (PKE) section 5.2.1.4, in the Parameter index (IND) Parameter (PWE) section 5.2.1.6 later.
section 5.2.1.5 later, and in the Parameter value (PWE) section 5.2.1.6 Following is a description of the terms used in the above explanations.
later.

5.2.1.4 Parameter ID (PKE)

♦ The SET SINGLE that would be sent by the master:
1)
Byte No. [ ä Designation
DeviceNetä ] Parameter ID (PKE)
1 [ FRAG] [XID] [SRC/DST MAC Id ] High Byte Low Byte
2 [ Fragmentation Protocol ] Bit No.: 15 12 11 10 0
3 [ [R/R] [Service] ] 0x10 [Set_Attribute_Single] AK SPM PNU
4 [ Class ] 100 [PKW Object] [Vendor specific] 1) Included in: GET SINGLE, SET SINGLE, response
5 [ Instance ] 1 [Instance Number] [always 1]
6 [ Attribute ] 1 [Attribute Number] [always 1] The parameter ID (PKE) is always a 16-bit value.
7 [ Data ] 0x2A [Low byte Parameter ID (PKE)] Bits 0 to 10 (PNU) contain the number of the required parameter. The
8 [ Data ] 0xC2 [High byte Parameter ID (PKE)] significance of the parameters can be taken from the Section
9 [ Data ] 1 [Low byte Parameter index (IND)] [range 0 to 255]
"Parameter list" of the drive Instruction Manual. To distinguish between
U or b base board parameters and the P or r base board parameters
10 [ Data ] 0 [High byte Parameter index (IND)] [for future use] which share the same PNU numbers, the "Page Select" bit (bit 15) in
11 [ Data ] 0x01 [Low byte, low word parameter value (PWE1)] the IND (see section 5.2.1.5) is used.
12 [ Data ] 0x30 [High byte, low word parameter value (PWE1)] Bit 11 (SPM) is the toggle bit for parameter change reports.
13 [ Data ] 0x00 [Low byte, high word parameter value (PWE2)]
14 [ Data ] 0x00 [High byte, high word parameter value (PWE2)] The CBD does not support these parameter change reports.
Bits 12 to 15 (AK) contain the task- and response ID.
♦ The response that would be sent by the drive: For the task telegram (master → drive), you can take the significance of
Byte No. [ ä Designation
DeviceNetä ] the task ID from Table 5-1. It corresponds to the definitions in the
"PROFIBUS profile, variable-speed drives". Task IDs 10 to 15 are
1 [ FRAG] [XID] [SRC/DST MAC Id ]
specific for SIMOVERT MASTERDRIVES, and are not defined in the
2 [ [R/R] [Service] ] 0x90 [Set_Attribute_Single] PROFIBUS profile.
3 [ Service Data ] 0x2A [Low byte Parameter ID (PKE)]
4 [ Service Data ] 0x42 [High byte Parameter ID (PKE)]
5 [ Service Data ] 0x01 [Low byte, low word parameter value (PWE1)]
6 [ Service Data ] 0x30 [High byte, low word parameter value (PWE1)]
7 [ Service Data ] 0x00 [Low byte, high word parameter value (PWE2)]
8 [ Service Data ] 0x00 [High byte, high word parameter value (PWE2)]

Bytes 1 and 2 are part of the DeviceNetä protocol.

The response from the drive starts with byte 3 which contains a value of
2A hex, followed by a data byte of 42 hex. These 2 data bytes make up

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 5-5 5-6 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Data transfer via DeviceNet Data transfer via DeviceNet 09.2000

Task ID- Significance Response ID For the response telegram (drive → master), you can take the
significance of the response ID from Table 5-2. It also corresponds to
positive negative
the definitions in the "PROFIBUS profile, variable-speed drives". The
0 No task 0 7 or 8 response IDs 11 to 15 are specific for SIMOVERT MASTERDRIVES,
1 Request parameter value 1 or 2 ↑ and are not defined in the PROFIBUS profile. Depending on the task
ID, only certain response IDs are possible. If the response ID has the
2 Change parameter value (word) for non-indexed parameters 1 
value 7 (task cannot be executed), then an error number is deposited in
3 Change parameter value (double word) for non-indexed parameters 2  parameter value1 (PWE1).
4 Request description element 1 3 
5 Change description element (not supported by CBD) 3 
Response ID Significance
6 Request parameter value (array) 1 4 or 5 
0 No response
7 Change parameter value (array, word) for indexed parameters 2 4 
1 Transfer parameter value for non-indexed parameters (word)
8 Change parameter value (array, double word) for indexed parameters 2 5 
2 Transfer parameter value for non-indexed parameters (double word)
9 Request the number of array elements 6 
3 Transfer descriptive element 1
10 Reserved - 
4 Transfer parameter value (array word) for indexed parameters 2
11 Change parameter value (array, double word) and store in the EEPROM 2 5 
5 Transfer parameter value (array double word) for indexed parameters 2
12 Change parameter value (array, word) and store in the EEPROM 2 4 
6 Transfer the number of array elements
13 Change parameter value (double word) and store in the EEPROM 2 
7 Task cannot be executed (with error number)
14 Change parameter value (word) and store in the EEPROM 1 ↓
8 No operator change rights for the PKW interface
15 Read or change text (not supported by CBD) 15 7 or 8
9 Parameter change report (word) (not supported by CBD)
10 Parameter change report (double word) (not supported by CBD)
1 The required parameter description element is specified in IND
11 Parameter change report (array, word) 2 (not supported by CBD)
2 The required element of the indexed parameter is specified in IND
12 Parameter change report (array, double word) 2 (not supported by CBD)
Table 5-1 Task IDs (master → converter) 13 Reserved
14 Reserved
15 Transfer text (not supported by CBD)

1 The required parameter description element is specified in IND

2 The required element of the indexed parameter is specified in IND

Table 5-2 Response IDs (converter → master)

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 5-7 5-8 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Data transfer via DeviceNet Data transfer via DeviceNet 09.2000

Error numbers for the response 'task cannot be executed' (drive Example of error 104:
parameters). The error numbers are transferred in the PWE1 word of The ‘PKW No.’ parameter for the G-SST1 (interface 1) (number of net
the response. data in the PKW channel):
Minimum value: 0 (0 words)
No. Significance Maximum value: 127 (corresponds to: Variable length)
0 Illegal parameter No. (PNU) If the PNU does not exist Permissible values for USS: 0, 3, 4 and 127
1 Parameter value cannot be changed If the parameter is a visualization parameter If a change task, with a PWE which differs from 0, 3, 4 or 127, is issued
to the unit, the response is as follows: ‘Task cannot be executed’, with
2 Upper or lower limit exceeded −
error value 104.
3 Erroneous sub-index −
4 No array For tasks for indexed parameters to a non-
indexed parameter.
PKE Example 1 Read value of parameter P101.4
e. g. task: ‘Change parameter value (word,
array)’ for non-indexed parameter This example details the decoding of the task PKE and the response
PKE of example 1 in the Use of PKW object section 5.2.1 previously.
5 Incorrect data type −
6 Setting not allowed (can only be reset) −
(PKE): Task ID (request from master)
7 Descriptive element cannot be changed Task not possible for MASTERDRIVES
P101 (=065 hex): Rated motor voltage
11 No operator control rights −see "parameterizing enable" parameter
Read parameter value (array).
12 Key word missing Drive parameter: ‘Access key’ and/or ‘special
parameter access’ not correctly set Parameter ID (PKE)

15 No text array available − Bit No.: 15 12 11 10 0

17 Task cannot be executed as a result of the Drive status doesn’t permit the presently issued AK SPM PNU
operating status task Task ID
101 Parameter No. presently de-activated - Byte 1 Byte 0
102 Channel width too low Parameter response too long for telegram Binary value 0 1 1 0 0 0 0 0 0 1 1 0 0 1 0 1
103 Incorrect PKW No. Index response from base unit did not match HEX value 6 0 6 5
index requested
Bit 12..15: Value = 6 (= "6" hex); read parameter value (array)
104 Parameter value not admissible -
Bit 0..11: Value = 101 (= "065" hex); parameter number without set
105 Parameter is indexed For tasks for non-indexed parameters to an parameter change report
indexed parameter.
e. g. task: ‘PWE, change word’ for indexed
(PKE): Response ID (response from drive)
parameter
P101 (=065 hex): Rated motor voltage
106 Task is not implemented -
Transfer of requested parameter value (array).

Comment to error Parameter ID (PKE)

This error number is transferred, if the parameter response to a
number 102 parameter task is longer than the available 6 bytes of the response Bit No.: 15 12 11 10 0
telegram, and therefore cannot be transferred. AK SPM PNU
The data is not distributed over several data telegrams.
Response ID
Comment to error This error number is transferred, if the parameter value, which is to be
number 104 Byte 1 Byte 0
transferred, isn’t assigned a function in the drive, or if at that instant, the
change cannot be accepted for internal reasons (although it lies within Binary value 0 1 0 0 0 0 0 0 0 1 1 0 0 1 0 1
the limits). HEX value 4 0 6 5
Bit 12..15: Value = 4 (= "4" hex); transfer parameter value (array)
Bit 0..11: Value = 101 (= "065" hex); parameter number without set
parameter change report

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 5-9 5-10 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Data transfer via DeviceNet Data transfer via DeviceNet 09.2000

PKE Example 2 Set value of parameter P554.1 = 3001 hex 5.2.1.5 Parameter index (IND)
This example details the decoding of the task PKE and the response
1)
PKE of example 2 in the Use of PKW object section 5.2.1 previously. Parameter index (IND)
High Byte Low Byte
(PKE): Task ID (request from master) Bit No.: 15 14 8 7 0
P554 (=22A hex): Source for the ON/OFF1 command (control page Value = 0 Index
word 1, bit 0) select
Change parameter value (array, word) and store in the 1)
Included in: GET SINGLE, SET SINGLE
EEPROM.
Parameter ID (PKE) The index is an 8-bit value, and for DeviceNetä, is always transferred
Bit No.: 15 12 11 10 0 in the least significant byte (bits 0 to 7) of the parameter index (IND).
AK SPM PNU
The most significant byte (bits 8 to 15) of the parameter index (IND) has
the "Page Select" bit (bit 15) and seven bits (bits 8 to 14) of 0. If this
Task ID most significant byte (high byte) = 00, then the PKE requests the P or r
Byte 1 Byte 0 base board parameters. If this most significant byte (high byte) is = 80
Binary value 1 1 0 0 0 0 1 0 0 0 1 0 1 0 1 0 hex, then the PKE (see section 5.2.1.4) requests the U or b base board
parameters.
HEX value C 2 2 A
For an indexed parameter, the required index is transferred. The
Bit 12..15: Value = 12 (= "C" hex); change parameter value (array, significance of the indices can be taken from the Section "Parameter
Bit 0..11: word) and store in the EEPROM
list" of the drive Instruction Manual.
Value = 554 (= "22A" hex); parameter number without set
For a descriptive element, the number of the required element is
parameter change report
transferred. The significance of the descriptive elements can be taken
from the PROFIBUS profile, variable-speed drives (VDI/VDE 3689).
(PKE): Response ID (response from drive)
P554 (= 22A hex): Source for the ON/OFF1 command (control IND Example 1 Read value of parameter P101.4
word 1, bit 0):
This example details the decoding of the task IND of example 1 in the
Transfer of new value of changed parameter (array, word). Use of PKW object section 5.2.1 previously.
Parameter ID (PKE) (IND): P101 (=065 hex): Rated motor voltage
Bit No.: 15 12 11 10 0 Read parameter value with index 4.
AK SPM PNU Parameter index(IND)
Task ID
Bit No.: 15 14 8 7 0
Byte 1 Byte 0 Byte 3 Byte 2
Binary value 0 1 0 0 0 0 1 0 0 0 1 0 1 0 1 0 Binary value 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0
HEX value 4 2 2 A
HEX value 0 0 0 4
Bit 12..15: Value = 4 (= "4" hex); transfer parameter value (array)
Bit 15: Page Select Value = 0 for P or r parameters, = 1 for U or b
Bit 0..11: Value = 554 (= "22A" hex); parameter number without set parameters
parameter change report
Bits 8..14: Value always 0
Fig. 5-1 Examples, parameter ID (PKE) Bits 0....7: Index of parameter or the number of the descriptive element

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 5-11 5-12 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Data transfer via DeviceNet Data transfer via DeviceNet 09.2000

IND Example 2 Set value of parameter P554.1 = 3001 hex PWE Example 1 Read value of parameter P101.4
This example details the decoding of the task IND of example 2 in the This example details the decoding of the task PWE of example 1 in the
Use of PKW object section 5.2.1 previously. Use of PKW object section 5.2.1 previously. Since this example was a
(IND): P554 (=22A hex): Source for the ON/OFF1 command (control GET SINGLE, the PWE is only used in the response from the drive.
word 1, bit 0) Since the response ID of the PKW was 4, the parameter is a 16 bit
parameter and the value is completely contained in PWE1. If the
Change parameter value with index 1.
response ID of the PKW had been 5, the parameter would have been a
Parameter index(IND) 32 bit parameter and the value would have been contained in PWE1
Bit No.: 15 14 8 7 0 and PWE2.
Byte 3 Byte 2 (PWE): P101 (=065 hex): Rated motor voltage
Read parameter value with index 4.
Binary value 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
Parameter value (PWE)
HEX value 0 0 0 1
Low word Byte 1 Byte 0
Bit 15: Page Select Value = 0 for P or r parameters, = 1 for U or b
(PWE1)
parameters
Bit No.: 15 8 7 0
Bits 8..14: Value always 0
Hex value 0 F A 0
Bits 0....7: Index of parameter or the number of the descriptive element
Fig. 5-2 Examples, parameter index (IND) High word Byte 3 Byte 2
(PWE2)
Bit No.: 31 24 23 16
Hex value 0 0 0 0
5.2.1.6 Parameter value (PWE)
Bits 0..15: Parameter value for 16-bit parameter or low component for 32-
1) bit parameter
Parameter value (PWE)
Bits 16..31: Value = 0 for 16-bit parameter or high component for 32-bit
low word: Byte 1 Byte 0 parameter
Parameter value low (PWE1)
high word: Byte 3 Byte 2
Parameter value high (PWE2)
1)
Included In: SET SINGLE, response
AK: Task- or response ID
SPM: Toggle bit for processing the parameter change report (not
supported by CBD)

PNU: Parameter number

The parameter value (PWE) is always transferred as double word (32

bit). Only one parameter value can be transferred in a telegram.
A 32-bit parameter value is comprised of PWE1 (least significant word)
and PWE2 (most significant word).
A 16-bit parameter value is transferred in PWE1 (least significant word).
In this case, PWE2 (most significant word), must be set to 0.

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 5-13 5-14 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Data transfer via DeviceNet Data transfer via DeviceNet 09.2000

PWE Example 2 Set value of parameter P554.1 = 3001 hex 5.3 Process data area (PZD)
This example details the decoding of the task PWE of example 2 in the
Use of PKW object section 5.2.1 previously. Since the response ID of Control words and setpoints (tasks: Master → Drive) and status words
the PKW was 4, the parameter is a 16 bit parameter and the value is and actual values (responses: Drive → Master) are transferred using
completely contained in PWE1. If the response ID of the PKW had process data (PZD). At the drive, the process data is processed with
been 5, the parameter would have been a 32 bit parameter and the the highest priority and in the shortest time segments. The drive is
value would have been contained in PWE1 and PWE2. controlled using the process data, for example, motor start/ stop and
(PWE): P554 (=22A hex): Source for the ON/OFF1 command (control setpoint input.
word 1, bit 0) Change the parameter value with index 1 to 3001. Normally only "polled I/O" is used to communicate to the drive by
Parameter value (PWE) sending and receiving PZD data.

Low word Byte 1 Byte 0

(PWE1)
Bit No.: 15 8 7 0 5.3.1 Setting the number of PZD words
Hex value 3 0 0 1
DeviceNetä IO Message Connections are used to transfer process
data. The number of process data words (4, 8, or 16) is determined by
High word Byte 3 Byte 2
(PWE2) which DeviceNetä I/O Assembly Instance is selected. The send and
receive lengths can be different. The I/O Assembly Instance selection
Bit No.: 31 24 23 16 can be changed by 2 different methods described below. For either
Hex value 0 0 0 0 method, the following I/O Assembly definitions are used:
Bits 0..15: Parameter value for 16-bit parameter or low component for 32- ♦ For Consumed connection path for Poll I/O only (tasks: Master →
bit parameter Drive), the choices are:
Bits 16..31: Value = 0 for 16-bit parameter or high component for 32-bit • "120" first 4 PZD control and reference words
parameter
• "121" first 8 PZD words
Fig. 5-3 Examples, parameter value
• "122" all 16 PZD words
♦ For Produced connection path for Poll I/O only (responses: Drive →
5.2.1.7 Rules for PKW object processing Master), the choices are:
• "170" first 4 PZD status and actual value words
♦ The length of the task can be 2 words (for a GET SINGLE) or • "171" first 8 PZD words
4 words (for a SET SINGLE). The length of the response is always
• "172" all 16 PZD words
3 words.
♦ The least significant byte (for words) must always be sent first, and ♦ For Produced connection path for Bit Strobe I/O only (responses:
then the most significant byte. The least significant word (for double Drive → Master), this path is fixed at:
words) must always be sent first, and then the most significant word. • "170" first 4 PZD status and actual value words. It can not be
♦ One task or one response only refers to one parameter value. changed.
♦ The slave sends a response to a parameter task only when the data
is available from the base MASTERDRIVES unit. In standard
operation, this takes 64 .. 150 ms depending on the
MASTERDRIVES type.
♦ In certain drive statuses (especially for initialization statuses),
parameters are either not processed or with a long delay. In this
case, a response delay of up to 40 seconds must be expected.
♦ The master may only issue a new parameter task after a response
has been received regarding an issued parameter task.
♦ The master identifies the response to an issued task:
• evaluation of the response ID (refer to Table 5-2)
• evaluation of the parameter No. PNU
• if required by evaluating the parameter value PWE.

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 5-15 5-16 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Data transfer via DeviceNet Data transfer via DeviceNet 09.2000

Method 1 Setting the power-up and reset default value of the appropriate Method 2 Using the DeviceNetä explicit message channel. This method is not
produced or consumed connection path. Base drive parameters "CB recommended because the selection must be performed every
parameter 1" and "CB parameter 2" are used for this purpose. The I/O time the drive is powered up or the CBD is reset through
Assembly Instance is selected using a 3 digit number equivalent to the DeviceNetä ä. The I/O Assembly Instance is selected (using the
3 character ASCII symbol for the I/O assembly. symbolic segment method with a 3 character ASCII symbol) for each of
This is the recommended method. the following:
♦ Poll I/O messages – Connection object, instance 2
♦ "CB parameter 1" • Consumed - Get and Set of attribute 16 (Consumed connection
sets the power-up and reset default value of the produced path) - Attribute 16 can only be changed (set) when the poll
connection path of the DeviceNetä polled I/O for the CBD. The connection object is in the "configuring" state which is after the
selection choices: = 170 or 171 or 172 allocate, but before the EPR (expected packet rate) is set. At
♦ "CB parameter 2" power-up or reset the poll consumed connection path is
sets the power-up and reset default value of the consumed always defaulted to "CB parameter 2".
connection path of the DeviceNetä polled I/O for the CBD. The CUVC & CUMC DC-Master CU2
selection choices: = 120 or 121 or 122
"CB parameter 2" P712.x U712.x P697
♦ "CB parameter 1" and "CB parameter 2"
can be set independently. They can be set to the same or different
PZD lengths. • Produced - Get and Set of attribute 14 (Produced connection
path) - Attribute 14 can only be changed (set) when the poll
The produced connection path of the DeviceNetä bit strobe I/O for the
connection object is in the "configuring" state. At power-up or
CBD is fixed at 170.
reset the poll produced connection path is always defaulted
to "CB parameter 1".
CUVC & CUMC DC-Master CU2 CUVC & CUMC DC-Master CU2
"CB parameter 1" P711.x U711.x P696 "CB parameter 1" P711.x U711.x P696
"CB parameter 2" P712.x U712.x P697
♦ Bit Strobe I/O messages – Connection object, instance 3
• Consumed - Get only of attribute 16 (Consumed connection
path) - always 8 bytes of which only 1 bit is assigned to each
CBD. Currently, this bit is not used by the CBD. The receipt of bit
strobe I/O message from the DeviceNetä Master will produce a
status message back to the Master and does reset the drive
telegram monitoring function (refer to drive parameter “CB/TB
TLg OFF Time”).
CUVC & CUMC DC-Master CU2
"CB/TB TLg OFF Time" P711.x U711.x P696

• Produced - Get only of attribute 14 (Produced connection path) -

always 8 bytes. The DeviceNetä specification limits a bit strobe
response message to a maximum of 8 bytes.

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 5-17 5-18 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Data transfer via DeviceNet Data transfer via DeviceNet 09.2000

5.3.2 Setting the meaning of the PZD words Telegram: ä consume)

PZD receive (DeviceNetä
Master → drive
The use of each process data word is set at the drive and is dependent (Setpoint channel) PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD

on the actual function of the particular drive. Parameters that act as 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

selector switches are used and are explained in detail in section 6.2. STW1 HSW

Until these selector parameters are set, the process data will not control 1st 2nd 3rd 4th 5th 6th 7th 8th 9th 10th 11th 12th 13th 14th 15th 16th
the drive or reflect the drive actual values. word word word word word word word word word word word word word word word word

For the PZD combination, the number i of the process data (PZDi, i = 1 Combination values

to 16) is entered into the combination value (refer to Section 6.2.1 for:

"Setpoint channel (master to drive)"). 16-bit process data 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 3012 3013 3014 3015 3016

NOTE The process data combination displayed here is only valid if a 16-/32-bit PZDs 3001 3032 3034 3006 3037 3039 3041 3043 3045

technology board is not installed.

(Examples) 3001 3032 3004 3005 3036 3038 3040 3042 3044 3016
When using a technology board (for example a T300 or T100), the
process data combination can be taken from the technology board (also refer to 3001 3002 3033 3035 3007 3038 3010 3041 3013 3044 3016
manual. Section 6.2)

Telegram: ä produce)
PZD send (DeviceNetä
Drive → master
(actual-value PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD PZD
channel) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
ZSW HIW

1st 2nd 3rd 4th 5th 6th 7th 8th 9th 10th 11th 12th 13th 14th 15th 16th
word word word word word word word word word word word word word word word word
Combination values
for:
Assignment of P694 P694 P694 P694 P694 P694 P694 P694 P694 P694 P694 P694 P694 P694 P694 P694
actual-value i001 i002 i003 i004 i005 i006 i007 i008 i009 i010 i011 i012 i013 i014 i015 i016
parameters in the
case of 16-bit
process data

16-/32-bit process P694 P694 P694 P694 P694 P694 P694 P694 P694
data (examples) i001 i002 = i003 i004= i005 i006 i007= i008 i009= i010 i011= i012 i013 = i014 i015

(also refer to P694 P694 P694 P694 P694 P694 P694 P694 P694 P694 P694
Section 6.2) i001 i002 i003 = i004 i005 = i006 i007 i008= i009 i010 i011 = i012 i013 i014 = i015 i016

PZD: Process data HSW: Main setpoint

STW: Control word HIW: Main actual value
ZSW: Status word

Fig. 5-4 Fixed, specified assignments and combination values for CU2

The CUVC, CUMC, and DC Master are similar with different parameter
numbers.
CUVC & CUMC DC-Master CU2
"CB/TB actual values" P734.01 to P734.16 U734.01 to U734.16 P694.01 to P694.16

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 5-19 5-20 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Data transfer via DeviceNet Data transfer via DeviceNet 09.2000

Examples CUVC drive: 5.3.3 Instructions and rules regarding process data processing
♦ Connecting-up the setpoints in the CUVD drive:
♦ The lowest significant byte (for words) is always sent first and the
• P443.01 (Source main setpoint) = 3032 (using PZD word 2)
lowest significant word (for double words).
• P554.01 (Source ON/OFF1) = 3001 (using control word 1)
♦ Control word 1 must always be contained in the 1st word of the
received setpoints. If control word 2 is required, this must be located
♦ Connecting-up the actual values in the CUVC drive: in the 4th word.
• P734.01 = 32 (status word in PZD word 1) ♦ Bit 10 "control from the PLC" must always be set in control word
• P734.02 = 69 (main setpoint in PZD word 2) 1, otherwise the drive will not accept the new setpoints and control
• P734.03 = 148 (actual speed in PZD word 3) words.
♦ The consistency of the process data is guaranteed within the data
of a DeviceNetä IO Message Connection. Even if more than 4
DC Master drive:
words are required, the data is not sent to the drive until all data has
♦ Connecting-up the setpoints in the DC Master drive: been transferred through the DeviceNetä bus. Thus, all setpoints
• P443.01 (Source main setpoint) = 3032 (using PZD word 2), and control words are accepted by the drive at the same instant.
terminal 37 must be on
• P654.01 (Source ON/OFF1) = 3001 (using bit 0 of PZD word 1)

♦ Connecting-up the actual values in the DC Master drive:

• P734.01 = 32 (status word in PZD word 1)
• P734.02 = 209 (main setpoint in PZD word 2)
• P734.03 = 167 (actual speed in PZD word 3)

CU2 drive:
♦ Connecting-up the setpoints in the CU2 drive:
• P443.01 (Source main setpoint) = 3032
• P554.01 (Source ON/OFF1) = 3001 (using control word 1)
• P584.01 (Source Technology regulator enable) = 3004 (using
control word 2)
• P526.01 (Source Technology regulator setpoint) = 3005

♦ Connecting-up the actual values in the CU2 drive:

• P694.01 = 968 (status word in PZD word 1)
• P694.02 = 447 (main setpoint in PZD word 2)
• P694.03 = 218 (actual speed in PZD word 3)

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 5-21 5-22 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Start-up Start-up 09.2000

6 Start-up P090 (board, slot 2) and P091 (board, slot 3)

P090 and P091 are only required for the CU2.
(also refer to the drive Instruction Manual, Section "Parameter list")
6.1 Parameterization These parameters can also be changed at any time. Thus you can also turn off
the DeviceNetä connection with these parameters. This turn off will cause
Þ Section, Start-up / parameterization "Expert application" of the drive the DeviceNetää bus interface to disconnect from the drive. In this case,
Instruction Manual CBD stops communications via the bus, and neither receives DeviceNetä data
telegrams nor sends DeviceNetä data telegrams.

yes Possible option boards:

"CB parameter 1": I/O assembly for polled I/O produced connection path
Option boards? SCB, TSY, CB, TB
CUVC & CUMC DC-Master CU2
"Hardware configuration"
no P052 = 4 function selection "CB parameter 1" P711.x U711.x P696

The power-up and reset default value of the produced connection path of the
yes
CBD in DeviceNetä polled I/O connection can be set using this parameter. The poll I/O
slot +1B2? produced connection path is attribute 14 of instance 2 of the connection class
CBD in slot +1.B2 (class 5). The selection choices:
no P090 = 1 • "CB parameter 1" = 170 – 4 PZD status and actual value words -
equivalent to class 5, instance 2, attribute 14 = "170"
yes
CBD in
slot +1.B3? • "CB parameter 1" = 171 – 8 PZD status and actual value words -
equivalent to attribute 14 = "171"
P091 = 1 CBD in slot +1.B3
no • "CB parameter 1" = 172 – 16 PZD status and actual value words -
equivalent to attribute 14 = "172"
I/O Assembly for polled I/O
P696 = 170 ... 172 produced connection path "CB parameter 1" must be set to one of the valid values, even if the
DeviceNetä polled I/O connection will not actually be used. If the I/O assembly
P697 = 120 ... 122 I/O Assembly for polled I/O lies outside the valid range (170 .. 172), then fault F080 is displayed when
consumed connection path
status 4 "hardware configuration" is exited. After the fault has been
acknowledged, the unit again goes into the "hardware configuration" status,
P705 = 0 ... 2 Baud rate and the erroneous parameterization can be corrected. The cause of the F080
can be displayed with parameter "CB/TB diagnostics" index 1.

CUVC & CUMC DC-Master CU2

CBD bus address
P918 = n (0 ≤ n < 63) "CB/TB diagnostics" r732.1 n732.1 r731.1

P052 = 0 Exit "Hardware The following indexed parameter are used to define which values are sent, by
configuration"
entering the associated parameter No.

CUVC & CUMC DC-Master CU2

P695 = 0 ... 65535 Setting the telegram failure time in ms (0 = deactivated)
"CB/TB actual values" P734.01 to U734.01 to P694.01 to
P734.16 U734.16 P694.16
P053 = x Parameterizing enable CBD (refer below)
Example:
It is desired that the drive send 8 words of PZD status and actual value data
P052 = 5 Function selection "drive setting" every time the master sends a polled I/O telegram. Thus, "CB parameter 1"
should be set = 171.

Further information in the Section, start-up / parameterization "Expert

application" of the drive Instruction Manual.
Fig. 6-1 Parameterization "hardware configuration" of CU2.
CUMC, CUVC and DC Master are similar with different parameter
numbers.

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 6-1 6-2 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Start-up Start-up 09.2000

"CB parameter 2": I/O assembly for polled I/O consumed connection path ä
"CB parameter 10": Baud rate of the slave connected to the DeviceNetä
bus
CUVC & CUMC DC-Master CU2
CUVC & CUMC DC-Master CU2
"CB parameter 2" P712.x U712.x P697
"CB parameter 10" P720.x U720.x P705
The power-up and reset default value of the consumed connection path of the
DeviceNetä polled I/O connection can be set using this parameter. The poll I/O The baud rate of the Parameter value Baud rate
produced connection path is attribute 16 of instance 2 of the connection class slave connected to the
0 (pre-assignment) 125 kbps
(class 5). The selection choices: DeviceNetä bus is set
using this parameter. The 1 250 kbps
• "CB parameter 2" = 120 – 4 PZD control and reference words -
equivalent to class 5, instance 2, attribute 16 = "120" following table is valid: 2 500 kbps
• "CB parameter 2" = 121 – 8 PZD control and reference words -
If the baud rate lies outside the valid range (0 .. 2), fault F080 is displayed when
equivalent to attribute 16 = "121"
status 4 "hardware configuration" is exited. After the fault has been
• "CB parameter 2" = 122 – 16 PZD control and reference value words - acknowledged, the unit goes back into the status "hardware configuration" and
equivalent to attribute 16 = "122" the erroneous parameterization can be corrected. The cause of the F080 can
"CB parameter 2" must be set to one of the valid values, even if the be displayed with parameter "CB/TB diagnostics" index 1.
DeviceNetä polled I/O connection will not actually be used. If the I/O assembly
lies outside the valid range (120 .. 122), then fault F080 is displayed when CUVC & CUMC DC-Master CU2
status 4 "hardware configuration" is exited. After the fault has been "CB/TB diagnostics" r732.1 n732.1 r731.1
acknowledged, the unit again goes into the "hardware configuration" status,
and the erroneous parameterization can be corrected. The cause of the F080 In compliance with DeviceNetä specifications, if the baud rate is changed, the
can be displayed with parameter "CB/TB diagnostics" index 1. new value will not become effective until the drive is powered off and then
powered on again.
CUVC & CUMC DC-Master CU2
"CB/TB diagnostics" r732.1 n732.1 r731.1
ä MAC ID (Node address) of the drive
P918 (CB bus address) DeviceNetä
Example: (Also refer to the drive Instruction Manual, Section "Parameter list")
It is desired that the drive send 4 words of PZD control and reference data The MAC ID (or node address) of the drive on the DeviceNetä bus is set here.
when it sends a polled I/O telegram to this drive. Thus, "CB parameter 2"
should be set = 120.
"CB parameter 1" and "CB parameter 2" can be set independently. They can be NOTE After the above settings have been made, the CBD is initialized by the
set to the same or different PZD lengths. drive, and is ready for communications via the DeviceNetä bus. The
The first 4 PZD words are always sent by the drive in response to a bit strobe LED’s on the CBD show the CBD status. After being set up, and with
I/O message from the master. the master communicating, the red, yellow, and green LED’s will blink.
The red indicates that the CBD board itself is operating, the yellow
indicates that the CBD is successfully communicating to the CU or
technology board, and the green indicates that there is cyclic process
data (PZD) transfer with the master.
The drive will only communicate with the master. To change
parameters or control the drive by process data from the
DeviceNetää master, additional steps are required.
The parameterization must be enabled (by "parameterizing enable"
below), and the process data "connected-up" in the drive (see following
section 6.2).

"parameterizing enable"

CUVC & CUMC DC-Master CU2

"parameterizing enable" P053 P927 P053

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 6-3 6-4 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Start-up Start-up 09.2000

This parameter is important for CBD, if you wish to set or change parameters of 6.2 Process data combination
the drive (including technology board) via the DeviceNetä vendor specific PKW
object using the SET SINGLE service of the explicit messaging mode. Process data combination includes combining setpoints as well as
In this case, set parameter "parameterizing enable" (also refer to the drive control bits. The transferred process data only become effective when
Instruction Manual, Section "Parameter list") to an uneven value (e. g. 1, 3, 7 the used bits of the control words, the setpoints, status words and
etc.). Using parameter "parameterizing enable", you can define from which actual values are connected through to the dual port RAM interface
locations the parameter may be changed (PMU, CBD etc.). (Fig. 6-3).
Example: CBD stores the process data received at permanently fixed addresses
"parameterizing enable" = 1: Parameterizing enable only from CBD in the dual port RAM. Each process data (PZDi, i = 1..16) is assigned a
= 3: Parameterizing enable, from CBD + PMU combination value (e. g. 3001 for PZD1). The combination value is also
= 7: Parameterizing enable, from CBD + PMU +
used to define as to whether the appropriate PZDi (i = 1 ..16) involves a
SST1 (OP) 16-bit or a 32-bit value (refer to Fig. 5-4).
If the parameter change (= parameterizing enable) is enabled via CBD Using selector switches (for example P554.1 = selector switch for bit 0
("parameterizing enable" = 1, 3 etc.), all other parameter settings can be of control word 1), the individual bits of the control words and the
realized from the DeviceNetä bus master via the bus. setpoints can be assigned a specific PZDi in the dual port RAM. In this
If you wish to only read parameters of the drive (including technology board)
case the selector switch is assigned to the combination value
via the DeviceNetä vendor specific PKW object using the GET SINGLE service associated with the required PZDi (example, refer to Fig. 6-5).
of the explicit messaging mode, this parameter does not need to be set to
enable the CBD. From
Master Process data (PZD) - setpoint channel
For additional parameter setting, which involve data transfer via the PZD1 PZD2
STW HSW PZD3 PZD4 PZD5 PZD6
DeviceNetä bus (for example, process data (PZD) interlocking), you must know
Dual Port RAM
the number of process data words received from the slave. Setpoint Channel
E.g. P554.1 = 3001

STW 3001
STW1-Bit 0
HSW 3002/3032
TM Bus
DeviceNet Bus connector PZD3 3003
PZD4 3004
E.g. P443.1=3002
PZD5 3005/3035
PZD6 3006/3036

Source
PZD16 3016 HSW

CBD SIMOVERT MASTERDRIVE

To
Master Process data (PZD) - actual value channel
PZD1 PZD2
ZSW HIW PZD3 PZD4 PZD5 PZD6

Dual Port RAM

Actual Value Channel
(CB/TB actual values)
ZSW P694.1 P 694 .1
HIW P694.2 P 6 94.2
TM Bus P 6 94.3
DeviceNet Bus connector PZD3 P694.3
PZD4 P694.4 P 6 94.16

PZD5 P694.5
Statuses,
PZD6 P694..6 actual
values

PZD16 P694.16

CBD SIMOVERT MASTERDRIVE

Fig. 6-2 Process data "wiring" for the setpoint- and actual value channels

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 6-5 6-6 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Start-up Start-up 09.2000

6.2.1 Setpoint channel (master to drive) ♦ The first word (associated combination value: 3001) of the received
process data is always assigned to control word 1 (STW1). The
Þ Section Start-up / parameterization "Expert application" of the drive significance of the control word bit is provided in the converter
Instruction Manual Instruction Manual, Section "Start-up aids".
♦ The second word is always assigned to the main setpoint (HSW).
♦ If the main setpoint is transferred as 32-bit process data, then it also
yes
occupies word 3. In this case, the most significant part is transferred
Change process
data writing? in word 2 and the least significant part of the main setpoint, in
word 3.
no Connect receive
Refer to Section 5.3.1
♦ If a control word 2 (STW2) is transferred, then STW2 is always
channel:
- control words assigned the fourth word (associated combination value = 3004).
- setpoints The significance of the control word bit can be taken from the
converter Instruction Manual, Section "Start-up aids".
Connect response
♦ The combination value is always 4 digits. For the combination
channel: Refer to Section 5.3.2 values, associated with the process data (PZD1 to PZD16), please
- status words
- actual values
refer to Fig. 5-4.
♦ Data entry at the PMU is realized as a 4-digit number (e. g. 3001).
For parameterization via DeviceNetä bus, the combination value is
Refer to Section 5.3.3 entered via the bus, as well as via the PMU (e. g. combination value
Other CBD relevant
parameters 3001 is transferred as 3001 hex; refer to the following example in
Fig. 6-4).

Continue in Section Start-up / parameterization "Expert application" of

the drive Instruction Manual.
Fig. 6-3 Process data combination, setpoint channel

NOTE The process data combination of the setpoint channel can also be set
via the DeviceNetä bus, if "parameterizing enable" was previously set
to an uneven number (6.1 Parameterization).
♦ Using the "tens digit" of the combination value, a differentiation is
made between 16-bit process data (e.g. 3002) and 32-bit process
data (e.g. 3032).
♦ If process data is transferred as 16-bit quantity, then set the selector
switch (refer to the Section "Process data" in the drive Instruction
Manual), to the required combination value, associated with the
PZDI, for 16-bit process data (example: PZD2 occupied by 16-bit
process data; the associated combination value is then 3002).
♦ If process data is transferred as 32-bit quantity, then set the selector
switch (refer to the Section "Process data" in the drive Instruction
Manual), to the required combination value associated with the PZDi
for 32-bit process data. In this case, use the combination value of
the least significant PZDi (example: PZD2+PZD3 occupied by 32-bit
process data; the associated combination value is then 3032).

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 6-7 6-8 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Start-up Start-up 09.2000

Example for the PZD combination for control word 1 bits (STW1), main setpoint (HSW) 6.2.2 Actual value channel (drive to master)
setpoint channel and control word 2 bits (STW2).
Þ Section, Start-up / parameterization "Expert application" of the drive
At the converter via PMU Significance
Instruction Manual

Control word 1 bit 0 (Source ON/OFF1) via dual

P554.1 = 3001
port RAM interface (word 1)
yes
Change process
data writing?
Control word 1 bit 1 (Source ON/OFF2) via dual
P555.1 = 3001
port RAM interface (word 1) no Connect receive
channel: Refer to Section 5.3.1
- control words
- setpoints
16 bit main setpoint (Source main setpoint) via
P443.1 = 3002
dual port RAM interface (word 2)
Connect response
channel: Refer to Section 5.3.2
Control word 2, bit 28 (Source of message - status words
- actual values
P588.1 = 3004 "external warning 1") via dual port RAM
interface (word 4)

Other CBD relevant Refer to Section 5.3.3

Example: 32 bit main setpoint parameters

32 bit main setpoint (Source main setpoint) via

P443.1 = 3032
dual port RAM interface (words 2 and 3).

Fig. 6-4 Parameterizing example for CU2 for process data combination, setpoint
channel. Other drives are similar with different parameter numbers Continue in Section, Start-up / parameterization "Expert application" of
the drive Instruction Manual.

• Italics Fig. 6-5 Process data combination, actual value channel for CU2.
Other drives are similar with different parameter numbers.
Parameter number 443 (for PMU as decimal number, via DeviceNetä bus,
as equivalent HEX number = 1BB hex).
• Single underline:
The actual value process data (PZDi, i = 1..16) are assigned to the
Index (for PMU as decimal number, via DeviceNetä bus as equivalent HEX
appropriate status words and actual values using the indexed
number).
parameter "CB/TB actual values" (also refer to Fig. 5-4).
• Double underline:
Combination value: Defines, whether the parameter selected by the
CUVC & CUMC DC-Master CU2
parameter number is to be transferred as 16-bit or 32-bit value, and at
which position in the PZD setpoint telegram (PZDi), the parameter is to be "CB/TB actual values" P734.01 to P734.16 U734.01 to U734.16 P694.01 to P694.16
transferred.
Each index stands for a process data (e. g. 5 → PZD5 etc.). Please
Starting from the converter factory setting, the above parameterizing enter the number of the parameter, whose value you wish to transfer
example (Fig. 6-4) represents a functional wiring of the process data using the appropriate process data, into parameter "CB/TB actual
(setpoints). values" (also refer to the converter Instruction Manual, Section
"Parameter list") under the particular index.
The status word should always be entered in PZD1 word (Fig. 5-4) of
the PZD response (actual value channel), and the main actual value in
the PZD2 word. The further assignment of PZD (PZD1 up to, if
required, PZD16), is not defined. If the main actual value is transferred
as 32-bit value, then it occupies PZD2 and PZD3.
The significance of the status word bit is described in the converter
Instruction Manual, Section "Start-up aids".

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 6-9 6-10 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Start-up Start-up 09.2000

Example for the PZD combination for status word 1 (ZSW1), main actual value (HIW) 6.2.3 Other CBD-relevant parameters
actual value channel and status word 2 (ZSW2)
Þ Section, Start-up / parameterization "Expert application" of the drive
Instruction Manual
At the converter via PMU Significance

P694.1 = 968 Status word 1 (P968), is transferred in the actual value channel via
PZD1. yes
Change process
data writing?

P694.2 = 218 The actual value speed/frequency [n/f (act)] (P218), is transferred in
the actual value channel via PZD2 (in this case, as 16-bit quantity; no Connect receive
channel: Refer to Section 5.3.1
PZD3 is in this case not occupied). - control words
- setpoints

P694.4 = 553 Status word 2 (P553), is transferred in the actual value channel via
PZD4.
Connect response
channel: Refer to Section 5.3.2
- status words
- actual values
Example: 32-bit main actual value

P694.2 = 218 The actual value speed/frequency [n/f (act)] (P218), is transferred in
Refer to Section 5.3.3
the actual value channel via PZD2... Other CBD relevant
parameters

P694.3 = 218 ... and via PZD3 as 32-bit value.

Fig. 6-6 Parameterizing example for the CU2 process data combination, actual
value channel. Other drives have different parameter numbers.
Continue in the Section, Start-up / parameterization "Expert application"
of the drive Instruction Manual.
CUVC & CUMC DC-Master CU2 Fig. 6-7 Optional parameters

"CB/TB actual values" P734.01 to P734.16 U734.01 to U734.16 P694.01 to P694.16

"CB/TB TLg OFF Time"

NOTE If actual values are transferred as 32-bit data, then you must enter the
CUVC & CUMC DC-Master CU2
associated parameter numbers at 2 consecutive words (indices) (refer
to Fig. 6-6). "CB/TB TLg OFF Time" r722.x n722.x P695

Using parameter "CB/TB TLg OFF Time" (also refer to the drive Instruction
• Italics: Manual, Section "Parameter list") you can define whether the process data
P694 (CB/TB actual values), for PMU, displayed as decimal number, via entered by CBD in the dual port RAM is monitored by the drive. The parameter
DeviceNetä bus; transferred as equivalent HEX number (2B6 hex). value of this parameter corresponds to the telegram failure time in ms. The
parameter pre-assignment value is 10 ms, i. e. a maximum of 10 ms can lie
• Single underline: between 2 received process data DeviceNetä messages, otherwise the drive
Index (for PMU as decimal number, via DeviceNetä bus as equivalent HEX shuts down with fault F082. The monitoring is disabled for a parameter value of 0.
number): Specifies, at which position in the PZD actual value telegram
(PZDi), the actual value, selected by the parameter number, is The drive monitors process data entry into the dual port RAM from the instant
transferred. when CBD enters process data into the dual port RAM for the first time after
power-up of the drive. Fault F082 can only be initiated from this time instant
• Double underline: onwards!
Parameter number of the required actual value.
PZD data can be sent by DeviceNetä I/O (both Bit Strobe and Poll) messages.
PZD data can also be sent by DeviceNetä explicit messages using the
assembly class. PKW requests sent by explicit messages using the PKW object
(see previous Parameter area (PKW) section 5.2) do not update the PZD
information and do not affect this drive telegram monitoring function.

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 6-11 6-12 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Start-up Start-up 09.2000

NOTE If the "on" command (bit 0) is connected to the dual port RAM interface 6.3 Information for the DeviceNet master
(Section 6.2.1 "Setpoint channel (master to drive)"), then the following
must be observed for safety reasons: 6.3.1 Creating EDS Stub File for CBD
An "OFF2" or "OFF3" command must be additionally parameterized to
The following information is required for a user to create an EDS stub
the terminal strip/PMU (refer to the drive Instruction Manual, Section
file for the CBD. Depending on the management software used,
"Control word"), as otherwise the converter cannot be powered-down
portions of this information can be obtained directly from the CBD
with a defined command if the communications were to fail!
through DeviceNetä communications.
Vendor ID: 145
P692 (Response TLg OFF) Response to telegram failure Vendor Name: Siemens Energy & Automation
Device Type: Communication Adapter
P692 is only used on the CU2.
Product Code: 1
Using parameter P692 (also refer to the drive Instruction Manual, Section
Product Name: Siemens CBD
"Parameter list") you can define as to how the drive should respond to a
telegram failure. Major Revision: (must be obtained from CBD using DeviceNetä
communications)
For a parameter value 0 "Fault" the drive immediately shuts down with fault
Minor Revision: (must be obtained from CBD using DeviceNetä
F082, and the drive coasts down.
communications)
With parameter value 1 "OFF3 (fast stop)", the drive executes an OFF3 Catalog Number: MFLB 6SE7090-0XX84-0FK0
command (OFF with fast stop) and then goes into the fault status F082.
Strobed Connection: (Normally turn off Enable on Strobed for PLC
This parameter is only available from software version 1.3 (MASTERDRIVES scanners because Poll and Strobe cannot be
FC/CU1) and VC/CU2) and software version 1.2 (MASTERDRIVES SC/CU3). turned on/off in ladder logic. The CBD does
support Strobed for other applications)
o Enable
Input Size: 8 Bytes
Output Size: 8 Bytes
Polled Connection:
þ Enable
Input Size: 8 Bytes
Output Size: 8 Bytes
COS/Cyclic Connection:
o Enable
Input Size: 0 Bytes
Output Size 0 Bytes
40 character description: CBD - MASTERDRIVE Communication
Board

6.3.2 Using Explicit Messaging with a PLC Scanner

PKW data is normally not used – since drive commissioning is
performed by SIMOVIS or other means. If PKW data is not used, this
section can be skipped.
The following information should help in using the PKW object to read
and change drive parameters.
The explicit message program control feature is used. The Get Attribute
Single and Set Attribute Single services are used.
The vendor specific PKW object is used. It is class 100 (64 hex). Only
Instance 1 is used. Only attribute 1 is used. The drive parameter
number, parameter number index, and parameter value (if required) is
included in the data field.

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 6-13 6-14 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Start-up Start-up 09.2000

Example 1 Read value of parameter P101.4 Example 2 Set value of parameter P554.1 = 3001 hex
The PLC word data is in hex. The PLC word data is in hex.
Block Transfer Write Data: Block Transfer Write Data:

Command Size MAC ID Instance Command Size MAC ID Instance PWE High Word
IND
TXID Port Service Class Attribute PKE IND
TXID Port Service Class Attribute PKE PWE Low Word

PLC Word Data 05 01 00 0A 0E 03 0064 0001 0001 6065 0004 0000 0000
PLC Word Data 06 01 00 0E 10 03 0064 0001 0001 C22A 0001 3001 0000

• TXID = 05 (range 01 to FF hex = 1 to 255) should be incremented by PLC logic before each new • TXID = 06 (range 01 to FF hex = 1 to 255) should be incremented by PLC logic before each new
request Command = 01 (always 01) execute transaction block request
• Port = 00 (range 00 to 01) DeviceNetä port of scanner for command • Command = 01 (always 01) execute transaction block
(00 = Channel A, 01 = Channel B) • Port = 00 (range 00 to 01) DeviceNetä port of scanner for command
(00 = Channel A, 01 = Channel B)
• Size = 0A hex (choice of 0A hex for Get Single or 0E hex for Set Single)
• Size = 0E hex (choice of 0A hex for Get Single or 0E hex for Set Single)
• Service = 0E hex (choice of 0E hex = 14 for Get Single or 10 hex = 16 for Set Single)
• Service = 10 hex (choice of 0E hex = 14 for Get Single or 10 hex = 16 for Set Single)
• MAC ID = 03 (range 00 to 3F hex = 0 to 63) address of drive set in P918
• MAC ID = 03 (range 00 to 3F hex = 0 to 63) address of drive set in P918
• Class = 64 hex (always 64 hex) class number of PKW object
• Class = 64 hex (always 64 hex) class number of PKW object
• Instance = 01 (always 01)
• Instance = 01 (always 01)
• Attribute = 01 (always 01) • Attribute = 01 (always 01)
• PKE = 6065 hex (range 0000 to FFFF hex) 6065 hex = Read array parameter P101.4 – for more • PKE = C22A hex (range 0000 to FFFF hex) C22A hex = Set array parameter P554.1 –
details, refer to example 1 in the Parameter ID (PKE) section 5.2.1.4 previously for more details, refer to example 2 in the Parameter ID (PKE) section 5.2.1.4 previously
• IND = 0004 hex (range low byte = 00 to FF hex = 0 to 255), high byte = 0 • IND = 0001 hex (range low byte = 00 to FF hex = 0 to 255), high byte = 0
(may be non-zero in future) 0004 hex = index 4 – for more details, (may be non-zero in future) 0004 hex = index 4 – for more details,
refer to example 1 in the Parameter index (IND) section 5.2.1.5 previously refer to example 2 in the Parameter index (IND) section 5.2.1.5 previously
• PWE = 3001 hex – new 16 bit value of parameter P554.1 – high word is not used for 16 bit values
and is set to 0 -- for more details, refer to example 2 in the Parameter value (PWE)
Block Transfer Read Data: section 5.2.1.6 previously

Status Size MAC ID PWE Low Word

Block Transfer Read Data:
TXID Port Service PKE PWE High Word
Status Size MAC ID PWE Low Word
PLC Word Data 05 01 00 06 8E 03 4065 0FA0 0000 0000 0000 0000 0000
TXID Port Service PKE PWE High Word

• TXID = 05 -- must be same number as request TXID above PLC Word Data 06 01 00 06 90 03 422A 3001 0000 0000 0000 0000 0000
• Status = 01 -- (must be 01) -- transaction successful
• Port = 00 -- must be same number as request port above • TXID = 06 -- must be same number as request TXID above
• Size = 06 -- (must always be 06) • Status = 01 -- (must be 01) -- transaction successful
• Port = 00 -- must be same number as request port above
• Service = 0E hex -- must be same number as request service above + 80 hex
• Size = 06 -- (must always be 06)
• MAC ID = 3 -- must be same address of drive as request above
• Service = 90 hex -- must be same number as request service above + 80 hex
• PKE = 4065 hex = Transfer of requested parameter P101.4 16 bit value (array) -- for more details,
refer to example 1 in the Parameter ID (PKE) section 5.2.1.4 previously • MAC ID = 03 -- must be same address of drive as request above
• PKE = 422A hex = Transfer of set parameter P554.1 16 bit value (array) -- for more details,
• PWE = 0FA0 hex -- 16 bit value of parameter P101.4 – high word is not used for 16 bit values --
refer to example 2 in the Parameter ID (PKE) section 5.2.1.4 previously
for more details, refer to example 1 in the Parameter value (PWE) section 5.2.1.6 previously
• PWE = 3001 hex -- 16 bit new value of parameter P554.1 – high word is not used for 16 bit values --
for more details, refer to example 2 in the Parameter value (PWE) section 5.2.1.6 previously

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 6-15 6-16 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Start-up Start-up 09.2000

Example 3 Read value of 32 bit parameter P421.4 Example 4 Read value of parameter U003.1 (with CUMC)
The PLC word data is in hex. The PLC word data is in hex.
Block Transfer Write Data: Block Transfer Write Data:

Command Size MAC ID Instance Command Size MAC ID Instance

TXID Port Service Class Attribute PKE IND TXID Port Service Class Attribute PKE IND

PLC Word Data 05 01 00 0A 0E 03 0064 0001 0001 61A5 0004 0000 0000 PLC Word Data 07 01 00 0A 0E 03 0064 0001 0001 6003 8001 0000 0000

• TXID = 05 (range 1 to FF hex = 1 to 255) should be incremented by PLC logic before each new • TXID = 07 (range 01 to FF hex = 1 to 255) should be incremented by PLC logic before each new
request request
• Command = 01 (always 01) execute transaction block • Command = 01 (always 01) execute transaction block
• Port = 00 (range 00 to 01) DeviceNetä port of scanner for command • Port = 00 (range 00 to 01) DeviceNetä port of scanner for command
(00 = Channel A, 01 = Channel B)
(00 = Channel A, 01 = Channel B)
• Size = 0A hex (choice of 0A hex for Get Single or 0E hex for Set Single)
• Size = 0A hex (choice of 0A hex for Get Single or 0E hex for Set Single)
• Service = 0E hex (choice of 0E hex = 14 for Get Single or 10 hex = 16 for Set Single)
• Service = 0E hex (choice of 0E hex = 14 for Get Single or 10 hex = 16 for Set Single)
• MAC ID = 03 (range 00 to 3F hex = 0 to 63) address of drive set in P918
• MAC ID = 03 (range 00 to 3F hex = 0 to 63) address of drive set in P918
• Class = 64 hex (always 64 hex) class number of PKW object
• Class = 64 hex (always 64 hex) class number of PKW object
• Instance = 01 (always 01)
• Instance = 01 (always 01) • Attribute = 01 (always 01)
• Attribute = 01 (always 01) • PKE = 6003 hex (range 0000 to FFFF hex) 6003 hex = Read array parameter U003.1 –
• PKE = 61A5 hex (range 0000 to FFFF hex) 61A5 hex = Read array parameter P421.4 – for more details, refer to example 1 in the Parameter ID (PKE) section 5.2.1.4 previously
for more details, refer to the Parameter ID (PKE) section 5.2.1.4 previously • IND = 8001 hex (range low byte = 00 to FF hex = 0 to 255), (choice of high byte = 00 or 80 hex)
• IND = 0004 hex (range low byte = 00 to FF hex = 0 to 255), high byte = 0 8001 hex = index 1 – the high byte = 80 requests the U or b base board parameters,
the high byte = 00 requests the P or r base board parameters.
(may be non-zero in future) 0004 hex = index 4 – for more details,
The low byte = 01 requests index 1 of the parameter number, for more details
refer to the Parameter index (IND) section 5.2.1.5 previously refer to example 1 in the Parameter index (IND) section 5.2.1.5 previously

Block Transfer Read Data: Block Transfer Read Data:

Status Size MAC ID PWE Low Word Status Size MAC ID PWE Low Word

TXID Port Service PKE PWE High Word TXID Port Service PKE PWE High Word

PLC Word Data 05 01 00 06 8E 03 51A5 3888 0001 0000 0000 0000 0000 PLC Word Data 07 01 00 06 8E 03 4003 09C4 0000 0000 0000 0000 0000

• TXID = 05 -- must be same number as request TXID above • TXID = 07 -- must be same number as request TXID above
• Status = 01 -- (must be 01) -- transaction successful • Status = 01 -- (must be 01) -- transaction successful
• Port = 00 -- must be same number as request port above • Port = 00 -- must be same number as request port above
• Size = 06 -- (must always be 06) • Size = 06 -- (must always be 06)
• Service = 0E hex -- must be same number as request service above + 80 hex • Service = 0E hex -- must be same number as request service above + 80 hex
• MAC ID = 03 -- must be same address of drive as request above • MAC ID = 3 -- must be same address of drive as request above
• PKE = 51A5 hex = Transfer of requested parameter P421.4 32 bit value (array) -- • PKE = 4003 hex = Transfer of requested parameter U003.1 16 bit value (array) --
for more details, refer to the Parameter ID (PKE) section 5.2.1.4 previously for more details, refer to example 1 in the Parameter ID (PKE) section 5.2.1.4 previously
• PWE = 09C4 hex -- 16 bit value of parameter U003.1 – high word is not used for 16 bit values --
• PWE = 00013888 hex -- 32 bit value of parameter P421.4 -- for more details,
for more details, refer to example 1 in the Parameter value (PWE) section 5.2.1.6 previously
refer to the Parameter value (PWE) section 5.2.1.6 previously

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 6-17 6-18 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Troubleshooting Troubleshooting 09.2000

7 Troubleshooting Alarm A084: Bus off

Erroneous DeviceNetä CAN messages have been received or sent, and the
internal error counter has exceeded the error limit.
This section only describes the alarms and error numbers generated Effect: The erroneous CAN messages are ignored. Data which was last sent
from CBD. Other error- and alarm messages, the fault causes and the remains valid. If it involves process data in the erroneous CAN messages,
appropriate counter-measures, are described in the Section "Fault- and depending on the telegram failure monitoring setting ("CB/TB TLg OFF
alarm messages" of the drive Instruction Manual. Time"), fault F082 can be initiated (DPR telegram failure). There is no
response in the drive if the PKW Object or other DeviceNetä explicit
messages are erroneous.
7.1 CBD Alarms and faults Counter-measures:
• Check and if required correct parameter "CB parameter 10" (baud rate) for
7.1.1 Alarms every bus node.
• Check the DeviceNetä bus master
Alarm A081: ä idle condition warning
DeviceNetä
• Check the cable connection between the bus nodes
A zero length PZD data telegram has been received through either the poll or
• Check the cable shielding. Follow DeviceNetä specifications.
bit strobe I/O message channel. The alarm will be reset when a normal length
PZD data telegram is received. • Replace board CBD
Effect: The telegram is ignored. Data which was last sent remains valid.
Depending on the telegram failure monitoring setting ("CB/TB TLg OFF Alarms A081, A083 and A084 are additionally acquired as information
Time"), fault F082 can be initiated (DPR telegram failure). and stored in alarm parameter 6 (r958). In this case, the individual
Counter-measures: Check the DeviceNetä bus master. Some PLCs will send alarms are assigned to the appropriate bits in r958 (bit x = 1: Alarm
an idle condition when they are put in the "program" mode. present):

Alarm A083: Error warning r958 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Bit

Erroneous DeviceNetä CAN messages are received or sent and the internal
fault counter has exceeded the alarm limit. Alarm A081
Effect: The erroneous CAN messages are ignored. Data which was last sent
remains valid. If it involves process data in the erroneous CAN messages,
Alarm A083
depending on the telegram failure monitoring setting ("CB/TB TLg OFF
Time"), fault F082 can be initiated (DPR telegram failure). There is no Alarm A084
response in the drive if the PKW Object or other DeviceNetä explicit
messages are erroneous.
Counter-measures:
• Check and if required correct parameter "CB parameter 10" (baud rate) for
every bus node.
• Check the cable connection between the bus nodes
• Check the cable shielding. Follow DeviceNetä specifications.
• Replace board CBD

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 7-1 7-2 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Troubleshooting Troubleshooting 09.2000

7.1.2 Fault messages Fault F082: Dual port RAM telegram failure
The telegram failure monitoring time, set via parameter "CB/TB TLg OFF
The following fault messages can occur with the combination of CBD
Time" has expired (also refer to section 6.2.3 "Other CBD-relevant parameters"
and the control/technology board (CU/TB):
and to alarms A081, A083, and A084 in section 7.1.1)

CUVC & CUMC DC-Master CU2

Fault F080: TB/CB Init.
"CB/TB TLg OFF Time" P722.x U722.x P695
When initializing and parameterizing the CBD via the dual port RAM interface
(dual port interface) a fault/error has occurred. Causes and counter-measures:
Causes and counter-measures: • DeviceNetä master failed or is in "program" mode (the green LED on CBD
• For the CU2 only: CBD selected with parameter P090/P091, but not remains dark)
inserted, • Cable connection between the bus nodes interrupted (the green LED on
- correct parameters P090 and P091 CBD is dark)
- insert CBD - check the bus cable
• Incorrect CBD parameterization; cause of the erroneous parameterization in • The telegram monitoring time has been set too short (the green LED on
the diagnostics parameter "CB/TB diagnostics" index 1 (refer to Section CBD flashes)
7.2.2, "CBD diagnostic parameters") - increase the parameter value in "CB/TB TLg OFF Time"
CUVC & CUMC DC-Master CU2 • CBD defective

"CB/TB diagnostics" r732.1 n732.1 r731.1 - replace CBD

- correct CB parameter "CB parameter 1" to "CB parameter 10"

- correct CB bus address P918

Equivalent Parameter Numbers

CUVC & CUMC DC-Master CU2
"CB Parameter 1" P711.x U711.x P696
"CB Parameter 2" P712.x U712.x P697
"CB Parameter 10" P720.x U720.x P705

• CBD defective
- replace CBD

Fault F081: Dual port RAM heartbeat

The CBD no longer processes the heartbeat counter.
Causes and counter-measures:
• CBD incorrectly inserted in the electronics box,
- check CBD
• CBD defective.
- replace CBD

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 7-3 7-4 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Troubleshooting Troubleshooting 09.2000

7.2 Diagnostics Standard LED image LED Status Diagnostic information

for net data transfer
via the DeviceNetää green flashing cyclic process data (PZD) transfer via the
7.2.1 Diagnostic LEDs DeviceNetä bus ok.
bus
Only flashes for PZD transfers, not PKW transfers
The CBD has three LEDs for fast troubleshooting. Confusion is or DeviceNetä functions such as allocate. If the
eliminated due to the different colored LEDs. PZD update time is less than approximately 150
milliseconds, this green LED may not flash on for
every cycle compared with the red and yellow
LEDs.
Adapter red flashing CBD ok.
Board
yellow flashing dual port RAM interface ok. (CU/TB-Heartbeat-
Counter)

NOTE Under standard operating conditions, all three LEDs are lit in the same
clock cycle and for the same duration!

Fault/error, CBD LED Status Diagnostic information

LED's
LED Indicators
Green: Telegram data transfer ok.
green steady light Fault/error cause:
Red: CBD ok. red flashing Fatal CBD fault
Red
Yellow
Green

Yellow: Communications with TB/CU ok.

yellow steady light (replace CBD)

Parameterization by LED Status Diagnostic information

CBD

V+ .5 the drive (CU)

green steady light CBD waits for the start of parameterization
CAN+ .4
red flashing by the drive (CU)
Shield .3
yellow off (dark) e. g. for the CU2 only: if the CBD is not selected
CAN- .2 (P090/P091)
V-
.1
LED Status Diagnostic information
X438
green off (dark) CBD waits for
red flashing parameterization to be completed
yellow steady light by the drive (CU)

Online operation LED Status Diagnostic information

green off (dark) No PZD data transfer via the DeviceNetä bus
red flashing e. g. the bus connector has been withdrawn, EMC
fault, interchanged connections,
Fig. 7-1 yellow flashing node number (P918) is not supplied with net data
via the DeviceNetä bus.

NOTE If an LED is in a steady state condition (dark or bright) then this

signifies that the unit is in a non-standard operating status
(parameterizing phase or fault/error)!
At least one LED must flash (otherwise: Voltage OFF or CBD
defective)!

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 7-5 7-6 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Troubleshooting Troubleshooting 09.2000

7.2.2 CBD diagnostic parameters Significance of the "CB/TB diagnostics" index 1 (error identification configuring)
CBD diagnostics
CUVC & CUMC DC-Master CU2
CBD puts diagnostics information in a diagnostics buffer memory to
support commissioning and service. The diagnostics information can be "CB/TB diagnostics" r732.1 n732.1 r731.1
read-out using the indexed parameter "CB/TB diagnostics". This If an invalid value or an illegal combination of parameter values is
parameter display is hexadecimal. contained in the CB parameters, the drive goes into a fault condition
with fault F080 and fault value 5 (r949). The erroneous
CUVC & CUMC DC-Master CU2
parameterization cause can be determined using this CB diagnostics
"CB/TB diagnostics" r732.index n732.index r731.index parameter.
The CBD diagnostics buffer is assigned as follows for CBD: Coding:
Significance "CB/TB diagnostics" index Value Significance
(Hex)
Error ID, configuring 1
00 No error
DeviceNetä Status 2
01 Incorrect DeviceNetä MAC ID (slave address) (P918)
Counter for all telegrams received (to CBD and other devices) 3
02 Incorrect DeviceNetä polled I/O produced connection path ("CB
Internally assigned 4
parameter 1")
Internally assigned 5
03 Incorrect DeviceNetä polled I/O consumed connection path ("CB
Internally assigned 6 parameter 2")
Internally assigned 7 04 - 16 Internal
Counter for PZD telegrams received error-free 8 17 Invalid baud rate ("CB parameter 10")
Counter for bus off statuses 9 18 - 22 Internal
Internally assigned 10 23 - 44 Reserved
Internally assigned 11
Internally assigned 12 Summary of Equivalent Parameter Numbers
Internally assigned 13 CUVC & CUMC DC-Master CU2
Internally assigned 14 "CB parameter 1" P711.x U711.x P696
Internally assigned 15 "CB parameter 2" P712.x U712.x P697
Internally assigned 16 "CB parameter 10" P720.x U720.x P705
Internally assigned 17 "CB/TB actual values" P734.01 to U734.01 to P696.01 to
P734.16 U734.16 P694.16
Internally assigned 18
"CB/TB diagnosis" r732.x n732.x P731.x
Counter for telegrams transmitted 19
"CB/TB TLg OFF Time" P722.x U722.x P695
Internally assigned 20
"parameterizing enable" P053 P927 P053
Internally assigned 21
Internally assigned 22
Internally assigned 23
Internally assigned 24
Internally assigned 25
Software version 26
Software ID 27
Software date, day-month 28
Software date, year 29
Not used 30-32

Table 7-1 CBD diagnostics buffer

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 7-7 7-8 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Troubleshooting Troubleshooting 09.2000

7.2.2.1 ä Status - parameter r731.02

DeviceNetä "CB/TB diagnostics" CUVC & CUMC DC-Master CU2
index 03
"CB/TB diagnostics" P732.3 n732.3 r731.3
"CB/TB diagnostics" CUVC & CUMC DC-Master CU2 (counter, all
index 02 telegrams received) Counter for DeviceNetä telegrams which were received error-free since
"CB/TB diagnostics" P732.2 n732.2 r731.2 power-on. This counter includes all Group 2 DeviceNetä messages,
ä Status)
(DeviceNetä
including those not directed to this CBD.
Each hexadecimal digit contains a different status indicator.
Thousand’s Digit Hundred’s Digit Ten’s Digit One’s Digit "CB/TB diagnostics" CUVC & CUMC DC-Master CU2
IDLE Indicator Channel Allocation Reserved Network Status LED index 08
"CB/TB diagnostics" P732.8 n732.8 r731.8
(counter, PZD
receive telegrams) Counter for error-free received PZD DeviceNetä telegrams since power
LED Coding for Value LED State Indication on.
Network Status LED
(One’s Digit) 0 Off Device is not on-line.
• The device has not completed the Dup_MAC_ID test
"CB/TB diagnostics" CUVC & CUMC DC-Master CU2
yet. index 09
"CB/TB diagnostics" P732.9 n732.9 r731.9
(counter, bus off)
1 Flashing Device is on-line but has no connection in the Counter, bus off statuses since power on (alarm A084).
Green established state.
• This device is not allocated to a master. "CB/TB diagnostics" CUVC & CUMC DC-Master CU2
2 Solid Device is on-line and has connections in the established index 19
"CB/TB diagnostics" P732.19 n732.19 r731.19
Green state. (counter, PZD send
ä telegrams)
DeviceNetä Counter, error-free DeviceNetä telegrams sent since power on.
• This device is allocated to a master.
3 Flashing Not presently used.
Red "CB/TB diagnostics" CUVC & CUMC DC-Master CU2
index 26
4 Solid Red Failed communication device. "CB/TB diagnostics" P732.26 n732.26 r731.26
(Software version)
• This device has detected an error that has rendered Software release (in hex). Scaling is x 10. For example, 000A hex = 10
it incapable of communicating on the network decimal ÷ 10 = 1.0
(Duplicate MAC ID or Bus-off). This condition can be
reset only by cycling the power on the drive.
"CB/TB diagnostics" CUVC & CUMC DC-Master CU2
index 27
Bit Coding for "CB/TB diagnostics" P732.27 n732.27 r731.27
Bit in Digit (Bit in full word) Indication (Software
Channel Allocation identification code)
(Hundred’s Digit) 0 (8) 1 = Explicit Channel allocated
1 (9) 1 = I/O Poll Channel allocated "CB/TB diagnostics" CUVC & CUMC DC-Master CU2
2 (10) 1 = I/O Bit Strobe Channel allocated index 28
"CB/TB diagnostics" P732.28 n732.28 r731.28
(Software date)
3 (11) Future Use Software date, day (high byte) and month (low byte) in a hexadecimal
notation
Digit Coding for Value Indication
IDLE Indicator "CB/TB diagnostics"
0 Device is not in IDLE condition. CUVC & CUMC DC-Master CU2
(Thousand’s Digit) index 29
• A non-zero length POLL or BIT STROBE command was the "CB/TB diagnostics" P732.29 n732.29 r731.29
(Software date)
latest data received. Software date, year (in a hexadecimal notation)
1 Device is in IDLE condition. Also refer to alarm A081 in section 7.1.1
• A zero length POLL or BIT STROBE command was the latest
data received. PCB code CUVC & CUMC DC-Master CU2
"PCB code" r826 r723
The PCB code for the CBD is 145.

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 7-9 7-10 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 Appendix Appendix 09.2000

8 Appendix Notes

8.1 Technical data

Board name CBD (Communications Board DeviceNetä)
Order No. 6SE7090-0XX84-0FK0
Rated input voltage 5 V ± 5 %, approx. 400 mA, internally from the drive
Operating temperature range 0 °C to +55 °C (32 °F to 131 °F)
Storage temperature -25 °C to +70 °C (-13 °F to 158 °F)
Transport temperature -25 °C to +70 °C (-13 °F to 158 °F)
Environmental conditions
- climatic class: 3K3 according to DIN IEC 721 Part 3-3 / 04.90
- pollutant stressing: 3C2 according to DIN IEC 721 Part 3-3 / 04.90
Degree of pollution 2 DIN VDE 0110 Section 1/01.89. Moisture condensation not
permissible
Degree of protection IP00 DIN VDE 0470 Section1 / 11.92 =
^ EN 60529
Mechanical strength DIN IEC 68-2-6 / 06.90
Frequency range Constant amplitude of the
deflection acceleration
Hz mm m/s2 (g)
10 to 58 0.075
for stationary applications
above 58 to 500 9.8 (1)

Table 8-1 Technical data

8.2 Revision data

8.2.1 Firmware Version (viewable by parameter "CB/TB diagnostics"
index 26 and through DeviceNetä)

CUVC & CUMC DC-Master CU2

"CB/TB diagnostics" P732.26 n732.26 r731.26

Version 1.3 First released version

Version 1.4 There was one change in version 1.4. This change corrected a problem
with the PKW data sent over the DeviceNetä network. This problem
would only occur if the I/O assembly for polled I/O produced connection
path ("CB parameter 1") was set to 171 (8 PZD status and actual value
words) or set to 172 (16 PZD status and actual value words). With
these values for "CB parameter 1", the PKW response from the drive
would normally indicate an error with the Task ID of the response
PKE = 7 even for valid requests.

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 8-1 8-2 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 CBD Quick Setup Guide CBD Quick Setup Guide 09.2000

9 CBD Quick Setup Guide 9.3 Required CBD Setup Parameters for CU1 or CU2
Boards

9.1 Overview Please refer to section 9.4 for CUMC and CUVC boards and section
9.5 for the DC Master (6RA70).
The CBD supports the Predefined Master/Slave Connection Set as The serial interface on the CBD is used. In the 6SE70 Instruction Book,
defined in the DeviceNetä specification. Process data is sent and this serial interface is called "CB".
received using I/O messages that are capable of handling poll and/or P051 "Access Level" -- must be set to 3 to change the following parameters.
bit strobe messages. Normal 6SE70 parameters are read and changed
P052 "Function Select" -- must be set to 4 (hardware mode) to change the following
with a vendor specific PKW object using explicit messages. Technically,
parameters.
the CBD follows the DeviceNetä Device Profile for the Communication
Adapter (Device Type 12). The Communication Adapter Profile was P090 or P091 set depending on the CBD hardware slot. For example, if the CBD is the only
chosen so that all the flexibility and advanced features of the option board, it would be installed in position #2 (right) of the electronic box and
MASTERDRIVE could be used by the DeviceNetä master. For this P090 would be set = 1 and P091 set = 0.
same reason, the CBD did not implement the DeviceNetä AC Drives P696 "CB parameter 1" -- sets the number of PZD words (called produced data) sent
profile. by the drive in response to a polled I/O message from the master. For technical
details refer to the CBD Instruction Book. Also refer to the section 9.7.
The user should be familiar with DeviceNetä technology. The
DeviceNetä master has a choice of two methods in handling PZD The selection choices:
information to the drive. The master can use either polled I/O or bit • P696 = 170 – first 4 PZD status and actual value words
strobe I/O. It can also use both methods. For polled I/O, the master first • P696 = 171 – first 8 PZD status and actual value words
sends control data (called consumed data) to the specific drive and
• P696 = 172 – all 16 PZD status and actual value words
then the drive sends status data (called produced data) to the master.
For bit strobe I/O, the master first sends one bit strobe message (with P697 "CB parameter 2" -- sets the number of PZD words (called consumed data)
no control data) to all drives and then each drive sends 4 words of accepted by the drive from a polled I/O message from the master. Also refer to
status data (called produced data) to the master. Bit strobe I/O is a very the section 9.7.
efficient way for the master to get a status report from each drive on the The selection choices:
network. • P697 = 120 – first 4 PZD control and reference words
• P697 = 121 – first 8 PZD control and reference words
Commissioning Tips (1) Normally for PLC scanners turn off the Enable on Strobed for the • P697 = 122 – first 16 PZD control and reference words
CBD using the DeviceNet commissioning tool (such as DeviceNet
Manager). Use only polled I/O. This is recommended because Poll
P696 and P697 can be set independently. They can be set to the same
and Strobe cannot be turned on/off in ladder logic.
or different PZD lengths.
(2) Normally only polled I/O is used to communicate to the drive by
The first 4 PZD words (called produced data) are always sent by the
sending and receiving PZD data. PKW data is normally not used –
drive in response to a bit strobe I/O message from the master.
since drive commissioning is performed by SIMOVIS or other
means. Section 9.8 can be skipped.
P705 "CB parameter 10" -- selects the baud rate of DeviceNetä.
The selection range:

9.2 Required Hardware and Software • P705 = 0 -- 125 kbps

• P705 = 1 -- 250 kbps
Any hardware version of the 6SE70 may be used. Any software version • P705 = 2 -- 500 kbps
of the base microprocessor board (CU1 or CU2 or CUMC or CUVC)
P918 "CB bus address" -- sets the DeviceNetä MAC ID for the CBD and has a range
may be used. Any software version of the CBD may be used. A T100 or of 0 to 63
a T300 technology board can also be used.
P052 "Function Select" -- must be set to 0 to initialize the CBD with the preceding
parameters.
P053 "Parameter Access" -- can be set to allow drive parameters to be changed from
the DeviceNetä Master through CBD only if desired by user. For example, if
P053 is set = 7, then parameters can be changed from the base keypad, the
base serial port, and the communication board (the CBD).

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 9-1 9-2 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 CBD Quick Setup Guide CBD Quick Setup Guide 09.2000

P695 "CB/TB TigOFFTime" -- should initially be set to 0 which turns off the drive 9.4 Required CBD Setup Parameters for CUMC and CUVC
telegram monitoring function.
Boards
After the network is operating, the user should decide if the drive telegram
monitoring function should be turned on by setting P695 to a value of 10 or
If the CUMC needs to be defaulted (P060 = 2) – do not attach the CBD
higher. The units are milliseconds. If a valid telegram to this specific drive
updating the PZD data is not received within the parameterized time, a fault trip
until after the motor parameters are set (mode P060 = 5). It seems to
(F082) is set. After power-up, the monitoring does not start until the DeviceNetä work best if P711 through P720 are set before the CBD is plugged in.
Master first sends PZD data. PZD information can be sent by I/O (both Bit Otherwise a fault F080 may be generated and it is not always clear
Strobe and Poll) messages. PZD information can also be sent by explicit what is wrong. If there is no other option board, use P711.1 etc.
messages using the assembly class. PKW requests sent by explicit messages
using class 100 (see later parameter data section 9.8) do not update the PZD
information and do not affect this drive telegram monitoring function. P060 = 4 Board configuration menu

P051 "Access Level" -- should be set to its normal value for this specific installation. P711.x = 170 "CB parameter 1" see section 9.3 description of parameter "CB parameter 1"

r731 "CB/TB diagnosis" is an indexed display parameter that can be used to read P712.x = 120 "CB parameter 2" see section 9.3 description of parameter "CB parameter 2"
information to support start-up and for service/troubleshooting. If r731.1 is not P720.x = 2 "CB parameter 10" see section 9.3 description of parameter "CB parameter 10"
equal to zero, then one or more of the CBD parameters (P696 through P705
P918.x = slave address see section 9.3 description of parameter P918
and P918) are not set within their approved range. Also of interest is r731.3
which is a counter of all telegrams received (they may be addressed to the CBD P060 = 1
or other devices). r731.8 is a counter of PZD telegrams addressed to this r732 "CB/TB diagnosis" see section 9.3 description of r731
particular CBD. r731.19 is a counter of the telegrams sent error-free by the
CBD. P722.x "CB/TB TigOFFTime" see section 9.3 description of P695

NOTE After the above parameters have been changed, and P052 set back to NOTE After the above parameters have been changed, and P060 set back
0, the drive should be powered down for at least 10 seconds and then to 1, the drive should be powered down for at least 10 seconds and
powered back on. This power cycling allows the drive to initialize then powered back on. This power cycling allows the drive to initialize
communications with the DeviceNetä Master and to change the baud communications with the DeviceNetä Master and to change the baud
rate if requested. rate if requested.

9.5 Required CBD Setup Parameters for DC Master Boards

If the 6RA70 needs to be defaulted – do not attach the CBD until after
the motor parameters are set.

P711.x = 170 "CB parameter 1" see section 9.3 description of parameter "CB parameter 1"
P712.x = 120 "CB parameter 2" see section 9.3 description of parameter "CB parameter 2"
P720.x = 2 "CB parameter 10" see section 9.3 description of parameter "CB parameter 10"
P918.x = slave address see section 9.3 description of parameter P918
n732 "CB/TB diagnosis" see section 9.3 description of parameter r731
U722.x = "CB/TB TigOFFTime" see section 9.3 description of parameter P695

NOTE After the above parameters have been changed, the drive should be
powered down for at least 10 seconds and then powered back on. This
power cycling allows the drive to initialize communications with the
DeviceNetä Master and to change the baud rate if requested.

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 9-3 9-4 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 CBD Quick Setup Guide CBD Quick Setup Guide 09.2000

9.6 Status Indication by LED’s On a "Factory Default" 6SE70 MASTERDRIVE, these control functions
are set to "PMU", not serial communications CB. The "PMU" is the
The 6SE70 will not automatically be controlled via serial "Parameterization Unit" which is the membrane keypad in the front
communications when set-up per the previous section 9.3 or 9.4 or 9.5 cover of the 6SE70.
of this document, it will only communicate. The LED’s on the CBD show In order to control the "Start/Stop" function from CB (the DeviceNetä
the CBD status. After being set up, and with the master communicating, Master), parameter P554.1 (described in Section 5 "Parameter list" of
the red, yellow, and green LED’s will blink. The red indicates that the the 6SE70 Instruction Manual) should be set to "3001". This sets the
CBD board itself is operating, the yellow indicates that the CBD is source of the "Start/Stop" function to bit 0 of PZD word 1 of the
successfully communicating to the CU or technology board, and the telegrams on serial port CB. PZD word 1 is word 1 of the I/O data area.
green indicates that there is cyclic process data (PZD) transfer with the Different values for parameter P554.x must be used if different ports
master. and/or different words in the telegram are used.
The same concepts apply to all reference (setpoint) signals. PZD words
2 through 16 can be used for references for 6SE70 control functions or
9.7 Process Data (PZD) technology board functions (if supplied). Note that PZD words 5 to 8 are
only received if I/O assemblies "121" or "122" are selected. Also note
After the basic communications are successful, the process data that PZD words 9 to 16 are only received if I/O assembly "122" is
connections must be set up to allow control of the 6SE70. Together, the selected.
(1) DeviceNetä IO Message Connections and the (2) process data
section of the 6SE70 define the control word, status word, setpoints The following examples refer to the configurations with CU1, CU2, CU3
and actual values for the interface. Definition of the process data as control board. For CUMC and CUVC the respective parameters,
section is very flexible. Individual input, output, and control functions binectors and connectors have to be parameterized.
must be set (parameterized) for use with serial communications. It is
beyond the scope of this document to describe all of the functions and
how to set (parameterize) them. The 6SE70 Instruction Manual, resp.
Compendium describes the control word, status word, setpoints, and
actual values structures and it is imperative that this section be read
completely and understood before attempting to control a 6SE70 with a
DeviceNetä Master.
The number of PZD words used is determined by which I/O Assembly
Instance is selected. The I/O Assembly Instance selection can be
changed by 2 different methods:
(1) Setting the power-up and reset default value of the appropriate
produced or consumed connection path. Base drive parameters "CB
Parameter 1" and "CB Parameter 2" are used for this purpose. They
are described in the previous section 9.3 or 9.4. This is the
recommended method.
CUVC & CUMC DC-Master CU2
"CB Parameter 1" P711.x U711.x P696
"CB Parameter 2" P712.x U712.x P697

(2) Using the DeviceNetä explicit message channel. This method is

not recommended because the selection must be performed
every time the drive is powered up or the CBD is reset through
DeviceNetää. Refer to the CBD Instruction Book for details on using
this method.
Once the number of PZD words is set, the following example describes
how to assign the "Stop/Start" and "Speed Command" functions to the
DeviceNetä Master:

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 9-5 9-6 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 CBD Quick Setup Guide CBD Quick Setup Guide 09.2000

As an example, to control the "Speed Command" function from CB (the The following example describes how to access the "Status Word 1"
DeviceNetä Master), parameter P443.x (described in Section 5 and "Main Setpoint" from the DeviceNetä Master:
"Parameter list" of the 6SE70 Instruction Manual) must be set to On a "Factory Default" 6SE70 MASTERDRIVE, the actual values
"3002". This sets the source of the "Speed Command" function to PZD return information words are set to zero. In order to access the
word 2 of the incoming telegrams on serial port CB. Different values for standard status word from CB (the DeviceNetä Master), parameter
parameter P443.x must be used if different ports and/or different words P694.1 (described in Section 5 "Parameter list" of the 6SE70
in the telegram are used. Instruction Manual) must be set to "968". This selects what will be
After P554.1 is set to "3001", the following diagram describes the returned in PZD word 1 of the telegrams on serial port CB. PZD
function of each control bit in PZD word 1 of the information sent to the word 1 is word 1 of the I/O data area.
CBD. Remember, the low byte of a word is always sent out first on Parameters P694.2 through P694.16 can be set to other
DeviceNetä. "r" parameters or "d" parameters (if a technology board is used) to
access other actual values in PZD words 2 through 16. Note that
High byte Low byte PZD words 5 to 8 are only sent if I/O assemblies "171" or "172" are
selected. Also note that PZD words 9 to 16 are only sent if I/O
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
1 = Start assembly "172" is selected.
0 = STOP1 (normal Stop) As an example, to access the "Main Setpoint" (described in r447 in
Not used - must be enabled Section 5 "Parameter list" of the 6SE70 Instruction Manual) in PZD
Not used - must be enabled word 2, parameter P694.2 must be set to "447". This selects what
Not used - must be enabled will be returned in PZD word 2.
Not used - must be enabled Again, as an example. parameter P694.3 can be set to "218" to
Not used - must be enabled
access actual value of speed/frequency (described in r218) in PZD
Not used - must be enabled
Not used - must be enabled word 3.
Again, as an example. parameter P694.4 can be set to "003" to
Not used - must be enabled access drive output voltage (described in r003) in PZD word 4.
Not used - must be enabled After P694.1 is set to "968", the following diagram describes the
1 = Enable Serial Operation
function of each status bit in PZD word 1 of the return information
Not used - must be enabled
from the CB port. Remember, the low byte of a word is always sent
Not used - must be enabled
Not used - must be enabled out first on DeviceNetä.
Not used - must be enabled High byte Low byte
Not used - must be enabled 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
A suggested initial value of PZD word 1 is 0400 hex. PZD word 1
1 = Ready to Start
can then be changed to 0401 hex to actually start the drive. 1 = Ready
1 = Running
1 = Drive Fault
This same technique must be applied to all functions such as 0 = STOP2 (Coast Stop)
"Forward/Reverse, Fault Reset," and all other functions that are to be 0 = STOP3 (Cuick Stop)
1 = Base Unit Blocked
controlled by the DeviceNetä Master.
1 = Drive Warning
Also, drive status and feedback (or actual value) information such as
motor speed and other information must be set (parameterized) to the 1 = Setpoint Error Within Tolerance Band
appropriate "destination" in order to be "read" by the DeviceNetä 1 = Serial Operation Allowed
Master Module. Section 4.3 of the 6SE70 Instruction Book also explains 0 = Serial Operation Blocked
the details 1 = Comparison Frequency Reached
1 = Undervoltage Fault
1 = Main Contactor Energized
1 = Ramp Generator Active
1 = Clockwise Phase Sequence
1 = Kinetic Buffering Active

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 9-7 9-8 Operating Instructions SIMOVERT MASTERDRIVES
 09.2000 CBD Quick Setup Guide CBD Quick Setup Guide 09.2000

Commissioning and During commissioning or when trying to trace a problem, it is often 9.8 Parameter Data (PKW)
Problem Solving Tip desirable to verify that a specific reference (sent in a specific PZD
control and reference word) is being correctly transmitted from the PKW data is normally not used – since drive commissioning is
DeviceNetä Master to the 6SE70. The unused technology controller performed by SIMOVIS or other means. If PKW data is not used, this
setpoint in the SIMOVERT VC can be temporarily used. For example, if section can be skipped.
the questionable reference is being sent in PZD reference word 4, then
A vendor specific PKW object, class 100 (64 hex), is used to read and
P526.1 should be set to "3004". The reference being sent is then
change 6SE70 drive parameters and technology board (if supplied)
displayed as r529 on the local 6SE70 PMU ("Parameterization Unit" -
parameters by the DeviceNetä Master. The explicit messaging mode is
the membrane keypad in the front cover of the 6SE70). Any changes
used. In this object, only 2 instances are implemented. Instance
sent from the DeviceNetä Master will be instantly displayed.
number 0 accesses the class attribute. Instance number 1 accesses all
To verify that the CBD IO produce is sending correct data back to the drive and technology board parameter numbers. For instance 1, the
DeviceNetä Master, the selection of one of the PZD status and actual attribute number must presently always be 1.
value words can be temporarily re-assigned. For example, if the
For instance number 1, the DeviceNetä data is either 2 words (4 bytes)
questionable actual value is being sent in PZD actual value word 3,
for parameter read requests or 4 words (8 bytes) for parameter change
then P694.4 should be temporarily set to "529". This will result in the
requests. The DeviceNetä data portion for requests and responses
value of r529 (described in the previous paragraph) being sent to the
duplicates the parameter handling used by Siemens in other
DeviceNetä Master, where it can be verified. On the CUMC or CUVC
communication protocols, namely the Parameter ID (PKE), Parameter
refer to r550, r551, r552, and r553.
index (IND), and Parameter value (PWE1 and PWE2).
There a some minor differences with other Siemens protocols:
(1) The parameter read requests use only two words, since the
parameter value is not needed.
(2) A GET SINGLE service code is required for parameter reads which
are PKE task ID’s of 1, 4, 6, and 9.
A SET SINGLE service code is required for parameter changes
which are PKE task ID’s of 2, 3, 7, 8, 11, 12, 13, 14. If parameters
are to be change from the master, parameter P053 must be set as
described in section 9.3 or 9.4 or 9.5.
A not supported response is sent for task ID’s of 0, 5, 10, and 15.
(3) The response uses only three words, the parameter index is not
needed.
Details of these data words is given in the CBD Instruction Book. The
exact byte by byte layout of the GET SINGLE, the SET SINGLE, and
the response is also given in the CBD Instruction Book.
By using this method of parameter handling, all the documentation for
parameter handling that is already contained in all drive instruction
manuals can be referenced for description.

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 9-9 9-10 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 CBD Quick Setup Guide CBD Quick Setup Guide 09.2000

Example: 9.9 Creating EDS Stub File for CBD

To read parameter P101.4, we would use a Get_Attribute_Single
service code with class # 100, instance #1, attribute #1, a data word The following information is required for a user to create an EDS stub
of 6065 Hex [Parameter ID (PKE)] and a data word of 0004 Hex file for the CBD. Depending on the management software used,
[Parameter Index (IND)]. The word data (values in hex) required for portions of this information can be obtained directly from the CBD
the Block Transfer Write to the PLC scanner might appear as: through DeviceNetä communications.
Block Transfer Write Data: Vendor ID: 145.
Vendor Name: Siemens Energy & Automation
Command Size MAC ID Instance Device Type: Communication Adapter
Product Code: 1
TXID Port Service Class Attribute PKE IND
Product Name: Siemens CBD
Major Revision: (must be obtained from CBD using DeviceNetä communications)
PLC Word Data 05 01 00 0A 0E 03 0064 0001 0001 6065 0004 0000 0000
Minor Revision: (must be obtained from CBD using DeviceNetä communications)
• TXID = 05 (range 01 to FF hex = 1 to 255) should be incremented by PLC logic before each new
Catalog Number: MFLB 6SE7090-0XX84-0FK0
request Command = 01 (always 01) execute transaction block
Strobed Connection:
• Port = 00 (range 00 to 01) DeviceNetä port of scanner for command
(00 = Channel A, 01 = Channel B)
• Size = 0A hex (choice of 0A hex for Get Single or 0E hex for Set Single) Strobed Connection:
• Service = 0E hex (choice of 0E hex = 14 for Get Single or 10 hex = 16 for Set Single) (Normally turn off Enable on Strobed for PLC scanners because Poll
and Strobe cannot be turned on/off in ladder logic. The CBD does
• MAC ID = 03 (range 00 to 3F hex = 0 to 63) address of drive set in P918
support Strobed for other applications)
• Class = 64 hex (always 64 hex) class number of PKW object
o Enable
• Instance = 01 (always 01)
Input Size: 8 Bytes
• Attribute = 01 (always 01)
Output Size 8 Bytes
• PKE = 6065 hex (range 0000 to FFFF hex) 6065 hex = Read array parameter P101.
Polled Connection:
• IND = 0004 hex (range low byte = 00 to FF hex = 0 to 255), high byte = 00 (may be non-zero in future)
þ Enable
Input Size: 8 Bytes
The word data (response) received from the PLC scanner using a Block
Output Size 8 Bytes
Transfer Read might appear as:
COS/Cyclic Connection:
Block Transfer Read Data:
o Enable
Input Size: 0 Bytes
Status Size MAC ID PWE Low Word
Output Size 0 Bytes
40 character description: CBD - MASTERDRIVE Communication Board
TXID Port Service PKE PWE High Word

PLC Word Data 05 01 00 06 8E 03 4065 0FA0 0000 0000 0000 0000 0000
• TXID = 05 -- must be same number as request TXID above
• Status = 01 -- (must be 01) -- transaction successful
• Port = 00 -- must be same number as request port above
• Size = 06 -- (must always be 06)
• Service = 0E hex -- must be same number as request service above + 80 hex
• MAC ID = 03 -- must be same address of drive as request above
• PKE = 4065 hex = Transfer of requested parameter P101.4 16 bit value (array
• PWE = 0FA0 hex -- 16 bit value of parameter P101.4 – high word is not used for 16 bit values

SIEMENS AG 6SE7087-6NX84-0FK0 6SE7087-6NX84-0FK0 Siemens AG

SIMOVERT MASTERDRIVES Operating Instructions 9-11 9-12 Operating Instructions SIMOVERT MASTERDRIVES
09.2000 CBD Quick Setup Guide

$ Electronic Data Sheet for the CBD - Master Drive Communication Board
[File]
DescText = "CBD - Master Drive Communication Board";
CreateDate = 05-28-1999;
CreateTime = 15:38:40;
ModDate = 10-08-1999;
ModTime = 15:53:40;
Revision = 1.4;
[Device]
VendCode = 145; $ Vendor Code
ProdType = 12; $ Product Type
ProdCode = 1; $ Product Code
MajRev = 1; $ Major Rev
MinRev = 4; $ Minor Rev
VendName = "Siemens Energy & Automation";
ProdTypeStr = "Communications Adapter";
ProdName = "Siemens CBD";
Catalog = "MFLB 6SE7090-0XX84-0FK0";
[IO_Info]
Default = 0X0003;
PollInfo =
0x0003, $ Polled -- Strobe
1, $ default prod = Input1
1; $ default cons = Output1
StrobeInfo =
0x0003, $ Strobe -- Polled
2, $ default prod = Input2
2; $ default cons = Output2
Input1 = $ produced data if P711/U711=170
8, $ first 4 PZD status and actual value words
0, $ all bits significant
0x0001, $ Polled
"Produced I/O Data",
4,
"63 31 37 30", $ Assy obj inst 170 attr 3
"I/O Data produced by the CBD";
Input2 = $ produced data if P711/U711=170
8, $ first 4 PZD status and actual value words
0, $ all bits significant
0x0002, $ Strobe
"Produced I/O Data",
4,
"63 31 37 30", $ Assy obj inst 170 attr 3
"I/O Data produced by the CBD";
Output1 = $ Consumed data if P712/U712=120
8, $ first 4 PZD control and reference words
0, $ all bits significant
0x0001, $ Polled
"Produced I/O Data",
4,
"63 31 32 30", $ Assy obj inst 120 attr 3
"I/O Data consumed by the CBD";
Output2 = $ Consumed data if P712/U712=120
0, $ data not used
0, $ all bits significant
0x0002, $ Strobe
"Produced I/O Data",
4,
"63 31 32 30", $ Assy obj inst 120 attr 3
"I/O Data consumed by the CBD";
[ParamClass]
MaxInst=0;
Descriptor=0;
CfgAssembly=0;
[Params]
[EnumPar]
[Groups]

SIEMENS AG 6SE7087-6NX84-0FK0
SIMOVERT MASTERDRIVES Operating Instructions 9-13
 The following editions have been published so far: Edition Internal Item Number
VA 477 759 4070 76 J VA-76
VB 477 759 4070 76 J VB-76

Version VB consists of the following chapters:

Chapter Changes Pages Version date
1 Definitions 3 09.2000
2 Product Description 3 09.2000
3 Mounting Instructions 2 09.2000
4 Connecting-Up 4 09.2000
5 Data Transfer Via DeviceNet 22 09.2000
6 Start-Up 18 09.2000
7 Troubleshooting 10 09.2000
8 Appendix 2 09.2000
9 CBD Quick Setup Guide 12 09.2000

Group: Automation and Drives (A&D)

Division: Variable-Speed Drive Systems
Postfach 3269, D-91050 Erlangen
Siemens Aktiengesellschaft Subject to change Order No.: 6SE7087-6NX84-0FK0
Printed in the federal Republic of Germany
09.2000