This documentation supplements the mounting instructions supplied with the
communication module and the "Inverter Drives 8400" hardware manual.
The features and functions of the communication module are described in detail.
Examples illustrate typical applications.
This documentation also contains...
ο Safety instructions that must be observed
ο Key technical data relating to the communication module
ο Information about the versions of the Lenze standard devices to be used
ο Notes on troubleshooting and fault elimination
The theoretical concepts are only explained to the level of detail required to understand
the function of the communication module.
Depending on the software version of the controller and the version of the Β»EngineerΒ«
software installed, the screenshots in this documentation may deviate from the
Β»EngineerΒ« representation.
This documentation does not describe any software provided by other manufacturers. No
liability can be accepted for corresponding data provided in this documentation. For
information on how to use the software, please refer to the host system (master)
documents.
All brand names mentioned in this documentation are trademarks of their respective
owners.
ο Tip!
Detailed information on PROFINET is provided on the homepage of the PROFIBUS
user organisation which also develops PROFINET communication technology:
www.profibus.com
6LEDS84AYCER EN 2.0 - 11/2010
Page 7
E84AYCER communication manual (PROFINET)
About this documentation
Target group
This documentation addresses to persons who configure, install, commission, and
maintain the networking and remote maintenance of a machine.
ο Tip!
Documentation and software updates of Lenze products can be found on the
Internet in the "Services & Downloads" area at:
www.Lenze.com
Validity information
The information in this documentation is valid for the following devices:
Extension moduleType designationFrom hardware
PROFINET communication moduleE84AYCERVA02.00
version
From software
version
EDS84AYCER EN 2.0 - 11/2010L7
Page 8
E84AYCER communication manual (PROFINET)
About this documentation
Document history
1.1Document history
Material numberVersionDescription
133139691.004/2010 TD17 First edition
133586922.011/2010 TD17 β’ General revision
β’ Update for SW version 02.00
Your opinion is important to us!
These instructions were created to the best of our knowledge and belief to give you the
best possible support for handling our product.
Perhaps we have not succeeded in achieving this objective in every respect. If you notice
this, please send your suggestions and points of criticism in a short e-mail to:
feedback-docu@Lenze.de
Thank you very much for your support.
Your Lenze documentation team
8LEDS84AYCER EN 2.0 - 11/2010
Page 9
1.2Conventions used
This documentation uses the following conventions to distinguish between different types
of information:
Type of informationIdentificationExamples/notes
Spelling of numbers
DecimalStandard spellingExample: 1234
Hexadecimal0x[0 ... 9, A ... F]Example: 0x60F4
Binary
β’ Nibble
Decimal separatorPointThe decimal point is always used.
Text
Program nameΒ» Β«PC software
Control elementBoldThe OK button... / The Copy command... / The
HyperlinkUnderlined
Symbols
Page reference (ο 9)Optically highlighted reference to another page. In
Step-by-step instructions
E84AYCER communication manual (PROFINET)
About this documentation
Conventions used
In inverted commas
Point
ο
Example: β100β
Example: β0110.0100β
For example: 1234.56
Example: Lenze Β»EngineerΒ«
Properties tab... / The Name input field...
Optically highlighted reference to another topic. In
this documentation it is activated via mouse-click.
this documentation it is activated via mouse-click.
Step-by-step instructions are indicated by a
pictograph.
EDS84AYCER EN 2.0 - 11/2010L9
Page 10
E84AYCER communication manual (PROFINET)
About this documentation
Terminology used
1.3Terminology used
TermMeaning
ControllerLenze frequency inverter of the "Inverter Drives 8400" product series which the
Standard device
Β»EngineerΒ«Lenze software which supports you throughout the whole machine life cycle -
Code"Container" for one or several parameters used to parameterise or monitor the
SubcodeIf a code contains several parameters they are stored in so-called "subcodes".
HWHardware
SWSoftware
I/O controllerPROFINET master
I/O devicePROFINET slave
IO supervisorEngineering and diagnostics tools
communication module can be used with.
ξApplication as directed
from planning to maintenance.
device.
This manual uses a slash "/" as a separator between code and subcode
(e.g. "C00118/3").
The I/O controller takes over the master function for data communication of the
decentralised field devices. The I/O controller usually is the communication
interface of a PLC.
The IO supervisor can access process data, diagnostic data, and alarm data.
(ο 14)
10LEDS84AYCER EN 2.0 - 11/2010
Page 11
1.4Notes used
The following pictographs and signal words are used in this documentation to indicate
dangers and important information:
Safety instructions
Structure of safety instructions:
ο½ Pictograph and signal word!
(characterise the type and severity of danger)
Note
(describes the danger and gives information about how to prevent dangerous
situations)
E84AYCER communication manual (PROFINET)
About this documentation
Notes used
PictographSignal wordMeaning
Danger!Danger of personal injury through dangerous electrical voltage
ο»
Danger!Danger of personal injury through a general source of danger
ο½
Stop!Danger of property damage
ο¨
Application notes
PictographSignal wordMeaning
Note!Important note for trouble-free operation
Reference to an imminent danger that may result in death or serious
personal injury if the corresponding measures are not taken.
Reference to an imminent danger that may result in death or serious
personal injury if the corresponding measures are not taken.
Reference to a possible danger that may result in damage to material assets
if the corresponding measures are not taken.
It is absolutely vital that the stated safety measures are implemented in order to
prevent serious injury to persons and damage to material assets.
Always keep this documentation to hand in the vicinity of the product during
operation.
2.1General safety instructions and application notes
ο Lenze drive components ...
β must only be used as directed.
ξApplication as directed
β must never be commissioned if they display signs of damage.
β must never be modified technically.
β must never be commissioned if they are not fully mounted.
β must never be operated without the required covers.
β can have live, moving and rotating parts during operation, depending on their
degree of protection. Surfaces can be hot.
ο The following applies to Lenze drive components ...
β Only use permissible accessories.
β Only use genuine spare parts supplied by the manufacturer of the product.
(ο 14)
ο Observe all regulations for the prevention of accidents, directives and laws that apply
to the location of use.
ο Observe all the specifications contained in the enclosed and related documentation.
β This is a precondition for ensuring safe, trouble-free operation and for making use of
the stated product features.
ξProperties
β The specifications, processes, and circuitry described in this document are for
guidance only and must be adapted to your own specific application. Lenze does not
take responsibility for the suitability of the process and circuit proposals.
ο All works on and with Lenze drive components may only be carried out by qualified
personnel. In accordance with IEC 60364 and CENELEC HD 384 these are persons who ...
β are familiar with installing, mounting, commissioning, and operating the product.
β have the qualifications necessary for their occupation.
β know and are able to apply all regulations for the prevention of accidents, directives
and laws that apply to the location of use.
(ο 15)
12LEDS84AYCER EN 2.0 - 11/2010
Page 13
E84AYCER communication manual (PROFINET)
Device- and application-specific safety instructions
2.2Device- and application-specific safety instructions
ο During operation, the communication module must be securely connected to the
standard device.
ο Use a safely separated power supply unit in accordance with EN 61800-5-1 ("SELV"/
"PELV").
ο Only use cables that meet the listed specifications.
ξSpecification of the Ethernet cable
(ο 30)
ο¬Documentation for the standard device, control system, plant/machine
All the other measures prescribed in this documentation must also be
implemented. Observe the safety instructions and application notes contained
in this manual.
Safety instructions
2.3Residual hazards
Protection of persons
ο If the Inverter Drives 8400 are used on a phase earthed mains with a rated mains
voltage β₯ 400 V, external measures need to be implemented in order to provide reliable
protection against accidental contact.
ξProtective insulation
Device protection
ο The communication module contains electronic components that can be damaged or
destroyed by electrostatic discharge.
ξInstallation
(ο 17)
(ο 22)
EDS84AYCER EN 2.0 - 11/2010L13
Page 14
E84AYCER communication manual (PROFINET)
Product description
Application as directed
3Product description
3.1Application as directed
The communication module ...
ο is an accessory module that can be used in conjunction with the following standard
devices:
Product seriesType designationFrom software version
Inverter Drives 8400 StateLineE84AVSCxxxxx05.00
Inverter Drives 8400 HighLineE84AVHCxxxxx05.00
Inverter Drives 8400 TopLineE84AVTCxxxxx01.00
ο is an item of equipment intended for use in industrial power systems.
ο should only be used under the operating conditions prescribed in this documentation.
ο should only be used in PROFINET networks.
Any other use shall be deemed inappropriate!
3.2Identification
The type designation and the hardware and software versions of the communication
module are indicated on the nameplate:
[3-1]Identification data
8400
Type:
HW:
Ser.No.:
HW:
SW:
SW:
1 Type designation (type)
E84 Product series
AVersion
YModule identification: Extension module
CModule type: Communication module
ERPROFINET
V/S V: Coated design
S: Standard design
2 Hardware version (HW)
3 Software version (SW)
E84YCPM001E
14LEDS84AYCER EN 2.0 - 11/2010
Page 15
3.3Properties
ο Interface module for the PROFINET communication system to be secured to the
expansion slots of the Inverter Drives 8400
ο The communication module can either be supplied internally by the standard device or
externally by a separate voltage source.
ο Support of the I&M0...4 functionality for the identification of the standard device
ο Automatic detection of the baud rate 100 Mbps
ο A line topology is enabled by the integrated 2-port switch.
ο Support of the LLDP protocol for the topology recognition
ο Support of the SNMP protocol for diagnostic purposes
ο Access to all Lenze parameters
E84AYCER communication manual (PROFINET)
Product description
Properties
3.4Terminals and interfaces
ο 2 RJ45 sockets for the PROFINET connection
ο 2-pole plug connector for the external voltage supply of the communication module.
ο Front LEDs for diagnosing the ...
β Voltage supply of the communication module;
β Connection to the standard device;
βPROFINET connection;
β PROFINET activity.
X255 External voltage supply of the communication
module
β’ 2-pole plug connector with spring
connection
ξExternal voltage supply
X256 PROFINET input (IN)
X257 PROFINET output (OUT)
β’ RJ45 sockets
β’ Each with 2 LED status displays for
diagnostics
ξNetwork topology
ξPROFINET connection
ξStatus displays at X256 and X257
(ο 32)
(ο 26)
(ο 28)
(ο 69)
5 LED status displays for diagnostics
MS
ξModule status displays
E84YCER001C
[3-2]E84AYCER communication module (PROFINET)
EDS84AYCER EN 2.0 - 11/2010L15
ME
BS
ξFieldbus status displays
BE
DE
(ο 67)
(ο 68)
Page 16
E84AYCER communication manual (PROFINET)
Technical data
General data and operating conditions
4Technical data
4.1General data and operating conditions
FieldValues
Order designationE84AYCER
Communication profilePROFINET
Communication mediumS/FTP (Screened Foiled Twisted Pair, ISO/IEC 11801 or EN 50173), CAT 5e
InterfaceRJ45: Standard Ethernet (in accordance with IEEE 802.3), 100Base-TX (Fast
Network topologyTree, star, and line
Type of nodeIO device with real time (RT) communication properties
Number of device nodesMax. 255 in the subnetwork
Max. cable length100 m
PUO ID number0x0106
Device identification (Device ID)0x8400
Baud rate100 Mbps
Switching method"Store and forward"
Switch latencyApprox. 125 ΞΌs at max. telegram length
Voltage supplyExternal supply via separate power supply unit
Conformities, approvals β’ CE
Ethernet)
β’ "+": V = 24 V DC (20.4 V - 0 % ... 28.8 V + 0 %), I = 140 mA
β’ "-": Reference potential for external voltage supply
β’UL
ο¬"Inverter Drives 8400" hardware manual
This manual contains data on ambient conditions and the electromagnetic
compatibility (EMC) that also apply to the communication module.
16LEDS84AYCER EN 2.0 - 11/2010
Page 17
4.2Protective insulation
ο» Danger!
Dangerous electrical voltage
If the Inverter Drives 8400 are used on a phase earthed mains with a rated mains
voltage β₯ 400 V, external measures need to be implemented in order to provide
reliable protection against accidental contact.
Possible consequences:
β’ Death or serious injury
Protective measures:
β’ If protection against accidental contact needs to be provided for the control
terminals of the controller and for the connections of the plugged-in device
modules, ...
β a double isolating distance must exist.
β the components to be connected must be provided with the second
Parameter dataApprox. 30 ms + a tolerance of 20 ms (typically)
There are no interdependencies between parameter data and process data.
Update cycle
+ 0 ... 1 ms
+ 1 ... x ms
β’ Some codes may require a longer processing time (see software manual/
Β»EngineerΒ« online help for Inverter Drive 8400).
Processing time in the module
Runtime of the application task of the technology
application used (tolerance)
EDS84AYCER EN 2.0 - 11/2010L19
Page 20
E84AYCER communication manual (PROFINET)
Technical data
Internal switch latency
4.5Internal switch latency
The integrated 2 port switch causes runtime delays which can be calculated as follows:
Runtime delay = ((36 permanent bytes + process data in bytes) x 8 x 10 nsec) + 4 ΞΌsec
Example:
20 process data words + 4 PROFIsafe words => 48 bytes
ο ((36 permanent bytes + 48 bytes) x 8 x 10 nsec) + 4 ΞΌsec
ο (84 bytes x 8 x 10 nsec) + 4 ΞΌsec
ο 6.72 ΞΌsec + 4 ΞΌsec = 10.72 ΞΌsec
According to the PROFINET specification, the shortest PROFINET IO telegram must have a
data length of 72 bytes. If the 36 permanent bytes are subtracted from the 72 bytes, 36
bytes are available for process data. If now less than 36 bytes of process data are used, the
PROFINET IO telegram is filled with "zero bytes" until it can be transmitted. As a
consequence for the calculation formula, the shortest PROFINET IO telegram with 18
process data words (36 bytes) has always the same length and thus the runtime delay is
the same, too.
The use of external switches can also lead to runtime delays. Depending on the
system constellation, it may be useful to create a star topology or a line/mix
topology.
ξNetwork topology
(ο 26)
20LEDS84AYCER EN 2.0 - 11/2010
Page 21
4.6Dimensions
E84AYCER communication manual (PROFINET)
Technical data
Dimensions
[4-2]Dimensions
E84AYCER6750578
E84YCER001B
TypeDimensions [mm]
abcc1
EDS84AYCER EN 2.0 - 11/2010L21
Page 22
E84AYCER communication manual (PROFINET)
Installation
5Installation
ο¨ Stop!
Electrostatic discharge
Electronic components within the communication module can be damaged or
destroyed by electrostatic discharge.
Possible consequences:
β’ The communication module is damaged.
β’ Fieldbus communication is not possible or is defective.
Protective measures:
β’ Release any electrostatic charge from your person before you touch the
module.
22LEDS84AYCER EN 2.0 - 11/2010
Page 23
E84AYCER communication manual (PROFINET)
5.1Mechanical installation
When the controller is switched-on, the communication module can be plugged into the
MCI slot or removed from there. During the process of being plugged in, the module is
automatically detected and its functions and version are checked for plausibility.
5.1.1Mounting for standard devices 0.25 kW and 0.37 kW
Installation
Mechanical installation
[5-1]Mounting for standard devices 0.25 kW and 0.37 kW
Mounting steps
1. Use a screwdriver to open the cover of the MCI slot of the standard device and remove
it (1, 2).
2. Loosen the securing screw for the communication module on the standard device (3).
3. Insert the communication module into the MCI slot of the standard device (4).
4. Tighten the securing screw again (5).
E84YCPM002D
EDS84AYCER EN 2.0 - 11/2010L23
Page 24
E84AYCER communication manual (PROFINET)
Installation
Mechanical installation
5.1.2Mounting for standard devices from 0.55 kW
[5-2]Mounting for standard devices from 0.55 kW
E84YCPM002A
Mounting steps
1. Apply a little pressure on the surface of the top side of the standard device MCI slot
cover to leave an indentation (1).
2. Tilt the cover forwards and remove it from the standard device (2).
3. Loosen the securing screw for the communication module on the standard device (3).
4. Insert the communication module into the MCI slot of the standard device (4).
5. Tighten the securing screw again (5).
24LEDS84AYCER EN 2.0 - 11/2010
Page 25
E84AYCER communication manual (PROFINET)
5.1.3Replacing the communication module
[5-3]Replacing the communication module
Installation
Mechanical installation
E84YCPM002B
Mounting steps
1. Loosen the securing screw for the communication module on the standard device (1).
2. Unplug the communication module from the MCI slot of the standard device (2).
3. Insert the new communication module into the MCI slot of the standard device (3).
4. Tighten the securing screw again (4).
EDS84AYCER EN 2.0 - 11/2010L25
Page 26
E84AYCER communication manual (PROFINET)
Installation
Electrical installation
5.2Electrical installation
ο¬Documentation for the standard device, control system, plant/machine
Observe the notes and wiring instructions contained in this documentation.
5.2.1EMC-compliant wiring
In typical systems, standard shielding is sufficient for Ethernet cables.
However, in environments with a very high level of interference, EMC resistance can be
improved by earthing the cable shield as well.
For this observe the following notes:
1. Remove the plastic sheath of the cable on a length of 2 cm.
2. Secure the cable shield to the shield connection of the standard device.
5.2.2Network topology
It is typical for PROFINET to have a rather free topology the limiting factor of which is large
message latencies due to e.g. switches connected in series.
ξInternal switch latency
The combination of a line and a stub is useful for system wiring.
PROFINET supports the following topologies:
ο Switch / star
[5-4]Switch / star topology (S = switch, D = IO device)
(ο 20)
S
DD
D
E94YCER005
26LEDS84AYCER EN 2.0 - 11/2010
Page 27
ο Tree via switches
E84AYCER communication manual (PROFINET)
Installation
Electrical installation
C
[5-5]Tree topology (C =IO controller, S = switch)
ο Switch / switch
[5-6]Switch/switch topology (S = switch)
ο IO controller / IO device
[5-7]Line topology (C = IO controller, D = IO device)
SS
S
SSS
C
DDDD
E94YCER006
E94YCER007
E94YCER008
EDS84AYCER EN 2.0 - 11/2010L27
Page 28
E84AYCER communication manual (PROFINET)
Installation
Electrical installation
5.2.3PROFINET connection
PROFINET is connected via RJ45 sockets X256 (input) and X257 (output).
[5-8]PROFINET connections X256 (IN) and X257 (OUT)
A standard Ethernet patch cable can be used for the connection to the communication
module.
ξSpecification of the Ethernet cable
The installation and removal of the Ethernet cables is optimised for the use of connectors
in accordance with the "Automation Initiative of German Domestic Automobile
Manufacturers" (AIDA).
To prevent the RJ45 socket from being damaged, hold the Ethernet cable
connector vertically when inserting it into or removing it from the socket.
E84YCER001E
28LEDS84AYCER EN 2.0 - 11/2010
Page 29
E84AYCER communication manual (PROFINET)
Pin assignment of the RJ45 sockets
RJ45 socketPinSignal
1Tx +
2Tx -
3Rx +
4-
5-
6Rx -
E94AYCXX004C
7-
8-
ο Tip!
The PROFINET interfaces feature an auto MDIX function. This function adjusts the
polarity of the RJ45 interfaces so that a connection is established irrespective of the
polarity of the opposite PROFINET interface, and irrespecive of the type of cable
used (standard patch cable or crossover cable).
The wiring and colour code are standardised in EIA/TIA 568A/568B.
According to the industrial standard, the use of 4-pin Ethernet cables is
permissible. The cable type only connects the assigned pins 1, 2, 3 and 6 to one
another.
Installation
Electrical installation
[5-10] Ethernet connector in accordance with EIA/TIA 568A/568B
PairPinSignalEIA/TIA 568AEIA/TIA 568B
31Tx +White / greenWhite / orange
2Tx -GreenOrange
23Rx +White / orangeWhite / green
14BlueBlue
5White / blueBlue / white
26Rx -OrangeGreen
47White / brownWhite / brown
8BrownBrown
E94YCEI004A
EDS84AYCER EN 2.0 - 11/2010L31
Page 32
E84AYCER communication manual (PROFINET)
Installation
Electrical installation
5.2.5External voltage supply
The communication module can be externally supplied with voltage via separate supply
cables at the 2-pole plug connector (X255).
With external voltage supply, always use a separate power supply unit, safely
separated in accordance with EN 61800-5-1 in every control cabinet ("SELV" /
"PELV").
ο External voltage supply of the communication module is necessary if the bus
communication is to continue when the supply of the standard device fails.
ο It is not possible to access parameters of a standard device disconnected from the
mains.
Wiring the X255 plug connector
ο¨ Stop!
Only wire the plug connector if the standard device is disconnected from the
mains.
E84AYCXX010
[5-11] Wiring of the 2-pole plug connector with spring connection
How to wire the plug connector with spring connection:
1. Press a screwdriver into the groove below the contact slot and keep it pressed.
2. Insert the supply cable into the contact slot.
3. Remove the screwdriver from the groove.
32LEDS84AYCER EN 2.0 - 11/2010
Page 33
E84AYCER communication manual (PROFINET)
Assignment of the X255 plug connector
DesignationDescription
+V = 24 V DC (20.4 V - 0 % ... 28.8 V + 0 %)
I = 140 mA
-Reference potential for the external voltage supply
Terminal data
FieldValues
Electrical connection2-pole plug connector with spring connection
Possible connectionsRigid:
0.2 ... 1.5 mm
Flexible:
Without wire end ferrule
0.2 ... 1.5 mm
With wire end ferrule, without plastic sleeve
0.2 ... 1.5 mm
With wire end ferrule, with plastic sleeve
0.2 ... 1.5 mm
2
(AWG 24 ... 16)
2
(AWG 24 ... 16)
2
(AWG 24 ... 16)
2
(AWG 24 ... 16)
Installation
Electrical installation
Stripping length10 mm
EDS84AYCER EN 2.0 - 11/2010L33
Page 34
E84AYCER communication manual (PROFINET)
Commissioning
Before initial switch-on
6Commissioning
During commissioning, system-specific data such as motor paramters, operating
parameters, responses, and parameters for fieldbus communication are specified for the
controller. In the case of Lenze devices this is carried out via the so-called codes.
The controller and communication codes are saved non-volatilely as a data record in the
memory module.
In addition there are diagnostic and monitoring codes for the nodes.
ξParameter reference
6.1Before initial switch-on
ο¨ Stop!
Before switching on the standard device and the communication module for the
first time, check the entire wiring for completeness, short circuit and earth fault.
(ο 78)
34LEDS84AYCER EN 2.0 - 11/2010
Page 35
E84AYCER communication manual (PROFINET)
6.2Configuring the PROFINET IO controller
The host system must be configured before communication with the communication
module is possible.
Configuration for device control
For the configuration of PROFINET, the current PROFINET device description file (XML) of
the E84AYCER communication module (PROFINET) has to be imported in the IO controller.
The device description file GSDML-Vx.z-Lenze-8400PNabb-yyyymmdd.xml can be found
on the Lenze Internet pages further on in the "Services & Downloads" area under:
Commissioning
Configuring the PROFINET IO controller
www.Lenze.com
Wildcards in the file name: "GSDML-Vx.z-Lenze-8400PN100-yyyymmdd.xml"
xMain version of the GSDML scheme used
zSubversion of the GSDML scheme used
aMajor version of the software version
bbMinor version of the software version
yyyyYear
mmMonth
ddDay
Definition of the user data length
The user data length is defined during the initialisation phase of the IO controller.
The Inverter Drives 8400 support the configuration of max. 16 process data words (max.
32 bytes).
Description of the device data base file
Selection textParameter data
(with consistency)
PCD (nW) AR cons.-n wordsn words
n = 1 ... 16 process data words
Process data
(with consistency)
Assigned
I/O memory
Example of device data base file selection
ο "PCD (8W) AR cons." = process data words (8 words)
ο Tip!
A detailed description of the consistency is provided in the chapter "Consistent
β’ The PROFINET function by means of which an accessible device can be
identified is supported. During execution of the function the red LED "ME"
blinks (Module status displays
β’ In the case of impermissible settings the red LED "BE" (Fieldbus status displays
(ο 68)
) blinks. The communication module then continues to operate with the
deleted name. Operation on the PROFINET requires a valid station name.
β’ If the station name is assigned by the IO controller via PROFINET the change
is activated immediately. The current station name is displayed in code
C13864
The station name ...
.
(ο 67).
ο is required for unambiguous addressing of the Inverter Drive 8400 by the IO controller.
ο can either be assigned by the IO controller via PROFINET or set manually in the
Β»EngineerΒ«.
ο has to be allocated in accordance with the PROFINET specification:
β 1 or several labels separated by ".".
β Max. length per label: 63 characters
β Max. total length: 240 characters
β Permissible characters: [a ... z], [0 ... 9], [.], [-]
β Labels must not begin or end with [-].
In the Β»EngineerΒ« the station name is set under the Settings tab.
Commissioning
Setting the station name
ο Then click Accept change. The station name is saved and written to code C13899
ο In the Lenze setting a deleted name is displayed. The name is also deleted if the "Reset
to factory defaults" command is executed by an IO supervisor or an IO controller.
.
EDS84AYCER EN 2.0 - 11/2010L37
Page 38
E84AYCER communication manual (PROFINET)
Commissioning
Setting the IP configuration
6.4Setting the IP configuration
If the communication module is to be made accessible via its IP parameters, the IP address,
subnet mask, and gateway address must either be assigned by the IO controller via
PROFINET or set manually in the Β»EngineerΒ«.
In the Β»EngineerΒ« the IP parameters are set under the Settings tab.
β’ The IP parameters are written to codes C13000 (IP address), C13001 (subnet
mask), and C13002
Use the [int] buttons to the right of the input fields to change to the decimal
code representation.
β’ The assignment of invalid combinations of IP address, subnet mask, and
gateway address can have the consequence that no connection to the
PROFINET can be established.
β’ In the case of impermissible settings the red LED "BE" (Fieldbus status displays
(ο 68)
β’ If the IP parameters are assigned by the IO controller via PROFINET the change
is activated immediately. The current parameter values are displayed in the
corresponding codes.
(gateway address) as decimal values.
) blinks.
38LEDS84AYCER EN 2.0 - 11/2010
Page 39
E84AYCER communication manual (PROFINET)
IP address (C13000)
ο Valid IP addresses are defined in accordance with RFC 3330.
In order to establish communication via an externally supplied communication
module, the standard device must be switched on as well.
After communication has been built up, the power on/off state of the standard
device is irrelevant.
Activating altered settings
To activate altered settings ...
β’ via standard device code C00002, execute device command "11: Save start
parameters", and ...
β’ then switch off the voltage supply of the communication module and switch
it on again.
Protection against uncontrolled restart
After a fault (e.g. short-term mains failure), it is sometimes undesirable or even
impermissible for the drive to restart.
In the Lenze setting of the Inverter Drives 8400, restart protection is activated.
The restart behaviour of the controller can be set via C00142 ("Autostart
option"):
β’ C00142 = 9 (Lenze setting)
β The controller remains inhibited (even when the fault is no longer active).
β Bit 0 (inhibit when device On) and bit 3 (inhibit in the case of undervoltage)
are set.
β An explicit controller enable causes the drive to start in a controlled
manner: LOW-HIGH edge at digital input X4/RFR.
β’ C00142 = 8 (enabled)
β In order to enable the device directly during switch-on, bit 0 must be set to
zero (FALSE).
β An uncontrolled restart of the drive is possible.
40LEDS84AYCER EN 2.0 - 11/2010
Page 41
7Data transfer
PROFINET transmits parameter data, configuration data, diagnostic data, alarm messages,
and process data between the host system (IO controller) and the controllers that are part
of the fieldbus (IO devices). Depending on their time-critical behaviour, the data are
transmitted via corresponding communication channels.
Communication channels
ο The process data channel transmits process data.
β With the process data the controller is actuated.
β The transmission of process data is time-critical.
β Process data are transmitted cyclically between the IO controller and the IO devices
that are part of the fieldbus according to the Provider/Consumer model (continuous
exchange of current input and output data).
β The IO controller can directly access the process data. In the PLC, for instance, the
data are directly assigned to the IO area.
β In the case of Inverter Drives 8400 protec maximally 16 process data words (16 bits/
word) can be exchanged for each direction.
β Process data are not stored in the Inverter Drive 8400 protec.
β Process data are e.g. setpoints, actual values, control and status words.
Please observe the direction of the flow of information!
β’ Process input data (Rx data):
β Process data from the controller (IO device) to the IO controller
β’ Process output data (Tx data):
β Process data from the IO controller to the controller (IO device)
ο Parameter data are transmitted via the acyclic channel.
β Usually the transmission of parameter data is not time-critical.
β The access to the parameter data depends on the PROFIdrive profile.
β Examples of parameter data are operating parameters, motor data, and diagnostic
information.
β The acyclic channel provides access to all Lenze codes.
β Parameter changes must be saved via code C00002 of the Inverter Drives 8400
protec.
EDS84AYCER EN 2.0 - 11/2010L41
Page 42
E84AYCER communication manual (PROFINET)
/3B0FL,Q
"
/3B0FL2XW
"
Process data transfer
Accessing process data / PDO mapping
8Process data transfer
8.1Accessing process data / PDO mapping
The process data (MCI PDOs) are transferred via the MCI interface.
ο Max. 16 words are exchanged for each direction.
ο The process data are accessed via the port blocks LP_MciIn and LP_MciOut. The port
blocks are also called process data channels.
ο The LP_MciIn port block maps the MCI PDOs received.
ο The LP_MciOut port block maps the MCI PDOs to be transmitted.
ο The port/function block interconnection of the process data objects (PDO) is made via
the Lenze Β»EngineerΒ«.
)LHOGξEXV
&RPPXQLFDWLRQξPRGXOH
0&,ξLQWHUIDFH
E&WUOB%ξ
E&WUOB%ξξ
Z&WUO
E,QξB%ξ
E,QξB%ξξ
Z,Qξ
Z,Qξξ
GQ,QξξBS
[8-1]External and internal data transfer between the bus system, controller, and application
ξξξξ
$SSOLFDWLRQ
)%ξLQWHUFRQQHFWLRQ
E6WDWHB%ξ
E6WDWHB%ξξ
Z6WDWH
E2XWξB%ξ
E2XWξB%ξξ
Z2XWξ
Z2XWξξ
GQ2XWξξBS
ο¬Software manual / Β»EngineerΒ« online help for the Inverter Drive 8400
Here you will find detailed information on the port/function block
interconnection in the Β»EngineerΒ« and the port blocks.
42LEDS84AYCER EN 2.0 - 11/2010
Page 43
E84AYCER communication manual (PROFINET)
Preconfigured port interconnection of the process data objects (PDO)
The Β»EngineerΒ« screenshots shown in the following are only examples for the
setting sequence and the resulting displays.
The data in the display fields may differ from the ones of your project.
8.2Preconfigured port interconnection of the process data objects (PDO)
The preconfigured port interconnection of the process data objects can be activated by
setting standard device code C00007 = "40: MCI".
The function block editor (FB Editor) serves to display the port blocks "LP_MciIn" and
"LP_MciOut" with the preconfigured interconnections:
Process data transfer
EDS84AYCER EN 2.0 - 11/2010L43
Page 44
E84AYCER communication manual (PROFINET)
Process data transfer
Configuring the port interconnection of the process data objects (PDO) freely
8.3Configuring the port interconnection of the process data objects (PDO) freely
ο How to freely configure the port interconnection in the Β»EngineerΒ«:
1. Go to the Process data objects tab and click Go to application.
2. Go to the Ports ta b, selec t the port blocks "MCI _IN" or "MCI_ OUT" and cl ick Activate
to activate them.
3. Click the Change variable ... button.
44LEDS84AYCER EN 2.0 - 11/2010
Page 45
E84AYCER communication manual (PROFINET)
Process data transfer
Configuring the port interconnection of the process data objects (PDO) freely
4. The button serves to assign signals to the process data words in the Assignment signal --> function block dialog box.
ο Select signals and then click the OK button.
EDS84AYCER EN 2.0 - 11/2010L45
Page 46
E84AYCER communication manual (PROFINET)
Process data transfer
Configuring the port interconnection of the process data objects (PDO) freely
Moreover you can assign signals to the individual control and status bits at the
WORD_1 and WORD_2 process data words via the and buttons.
ο Select the signals and then click OK.
46LEDS84AYCER EN 2.0 - 11/2010
Page 47
E84AYCER communication manual (PROFINET)
Process data transfer
Configuring the port interconnection of the process data objects (PDO) freely
ο Tip!
When the port blocks "LP_MciIn" and "LP_MciOut" are activated (see 1.) they will
be visible in the FB Editor. Here you can also assign signals to the process data
words.
EDS84AYCER EN 2.0 - 11/2010L47
Page 48
E84AYCER communication manual (PROFINET)
P
l
Parameter data transfer
The acyclic channel (PROFIdrive profile)
9Parameter data transfer
9.1The acyclic channel (PROFIdrive profile)
An optional service extension is the acyclic parameter data transfer.
Cyclic and acyclic PROFINET services can be operated simultaneously in the network.
Properties
ο Only one parameter request is processed at a time (no pipelining).
ο Spontaneous messages are not transmitted.
ο There are only acyclic parameter requests.
ο Profile-specific parameters can be read independently of the IO device state.
9.1.1Connection establishment of an IO controller to an IO device
An IO controller can always be used to request parameters from an IO device if the IO
device is in the "DATA_EXCHANGE" state.
arameterdata channe
Read
[9-1]Data communication via the acyclic channel
IO device
Write
IO
controller
E94YCER010
48LEDS84AYCER EN 2.0 - 11/2010
Page 49
E84AYCER communication manual (PROFINET)
9.1.2Acyclic data transmission process
Parameter data transfer
The acyclic channel (PROFIdrive profile)
IO controller
Parameter request
[9-2]Data communication via the acyclic channel
ο A "Write.req" is used to transmit the data set (DB47) in the form of a parameter request
to the IO device.
ο "Write.res" confirms the receipt of the message by the IO controller.
ο The IO controller requests the response of the IO device with "Read.req".
Write.req (DB47)
with data (parameter request)
Write.res
without data
Read.req
without data
Read.res (-)
without data
Read.req
without data
Read.res (+)Parameter response
with data (parameter response)
IO device
Parameter request
Parameter response
Parameter
processing
E94YCER011
ο The IO device responds with a "Read.res (-)" if processing is not yet completed.
ο After parameter processing, the parameter request is completed by transmitting the
parameter response in the form of a "Read.res (+)" to the IO controller.
EDS84AYCER EN 2.0 - 11/2010L49
Page 50
E84AYCER communication manual (PROFINET)
Parameter data transfer
The acyclic channel (PROFIdrive profile)
In the "Read/Write Block", the initiator specifies the access to data set "DB47". The data
which are written to this index or read by it contain a header and the parameter request or
the parameter response. The read data or the data to be written are contained in the "Data"
field.
The following subchapters describe the parameter request and the parameter response in
detail.
ο¬PROFINET specification
Here you will find detailed information on the PROFINET data telegram.
Assignment of the user data depending on the data type
Depending on the data type, the user data are assigned as follows:
β’ When a multi-parameter write request is processed, the parameter attribute,
index, subindex, and then the parameter format and parameter value are
repeated "n" times, "n" being the number of parameters requested.
β’ A parameter request must not exceed the maximum data length of
240 bytes.
Request header
Byte 1Byte 2Byte 3Byte 4
Request referenceJob identificationAxisNumber of indices
FieldData typeValues
Request referenceU8This value is specified by the IO controller.
Job identificationU80x02: Write parameter
AxisU80x00 or 0x01
Number of indicesU80x"n" (n = number of parameters requested)
Parameter attribute
Byte 5Byte 6
AttributeNumber of subindices
FieldData typeValues
AttributeU80x10: Value
Number of subindicesU80x00 or 0x01
Index and subindex
Byte 7Byte 8Byte 9Byte 10
IndexSubindex
High byteLow byteHigh byteLow byte
FieldData typeValues
IndexU160x0001 ... 0xFFFF (1 ... 65535)
SubindexU160x0001 ... 0xFFFF (1 ... 65535)
56LEDS84AYCER EN 2.0 - 11/2010
Page 57
E84AYCER communication manual (PROFINET)
Writing parameters to the controller
Parameter format
Byte 11Byte 12
FormatNumber of values
FieldData typeValues
FormatU80x02: Integer8
0x03: Integer16
0x04: Integer32
0x05: Unsigned8
0x06: Unsigned16
0x07: Unsigned32
0x09: Visible string
0x0A: Octet string
0x40: Zero
0x41: Byte
0x42: Word
0x43: Double word
Number of valuesU8 β’ 0x01
β’ Number of requested subindices. (If there is more
than one subindex, only the parameter value is
repeated.)
β’ In the case of string codes, the number of characters
is entered here.
Parameter data transfer
Parameter value
Byte 13Byte 14Byte 15Byte 16
Value
FieldData typeValues
ValueStringAny
U80x00 .... 0xFF
U160x0000 .... 0xFFFF
U320x0000 0000 .... 0xFFFF FFFF
EDS84AYCER EN 2.0 - 11/2010L57
Page 58
E84AYCER communication manual (PROFINET)
Parameter data transfer
Writing parameters to the controller
9.3.1Response after a correct write request
Response header
Byte 1Byte 2Byte 3Byte 4
Request reference
(mirrored)
FieldData typeValues
Request referenceU8Mirrored value of parameter request
Response identifierU80x01: Parameter written
AxisU80x00 or 0x01
Number of indicesU80x"n" (n = number of parameters requested)
For a multi-parameter request, correct and faulty messages, if any, are combined
in one telegram. The individual messages have the following data contents:
β’ Correct message
β Format: 0x40
β Number of values: 0x00
β’ Faulty message
β Format: 0x44
β Number of values: 0x01 or 0x02
β Error code without additional information (number of values = 0x01) or
β Error code with additional information (number of values = 0x02)
Faulty access to a parameter "n" will be reported in the response message of a
multi-parameter request at position n.
58LEDS84AYCER EN 2.0 - 11/2010
Page 59
E84AYCER communication manual (PROFINET)
Parameter data transfer
Writing parameters to the controller
Response header
Byte 1Byte 2Byte 3Byte 4
Request reference
(mirrored)
FieldData typeValues
Request referenceU8Mirrored value of parameter request
Response identifierU80x82: Parameter not written
AxisU80x00 or 0x01
Number of indicesU80x"n" (n = number of parameters requested)
Parameter format
Response identifierAxis
(mirrored)
β’ The data in bytes 7 + 8 are to be interpreted as error
Number of indices
code.
Byte 5Byte 6
FormatNumber of values
FieldData typeValues
FormatU80x44: Error
Number of valuesU80x01: Error code without additional information
0x02: Error code with additional information
Error code
Byte 7Byte 8Byte 9Byte 10
Error codeAdditional information (if available)
High byteLow byteHigh byteLow byte
FieldData typeValues
Error codeU160x0000 .... 0xFFFF
Additional information
(if available)
ξError information (error)
U16
(ο 62)
EDS84AYCER EN 2.0 - 11/2010L59
Page 60
E84AYCER communication manual (PROFINET)
Parameter data transfer
Writing parameters to the controller
9.3.3Telegram example: Write request
In the controller, the ramp time for quick stop is to be set to 50 ms.
ο Code to be written to: C00105
Parameter request
Byte 1Byte 2Byte 3Byte 4
Request referenceJob identificationAxisNumber of indices
0x000DReserved (PROFIdrive profile V2: Text cannot be read in cyclic
0x000EReserved (PROFIdrive profile V2: Name cannot be read in cyclic
0x000FNo text array availableAccess to unavailable text array (parameter value is
0x0010Reserved(PROFIdrive profile V2: No PPO-Write)-
0x0011Request cannot be executed
because of operating state
0x0012Reserved(PROFIdrive profile V2: Other error)-
0x0013Reserved (PROFIdrive profile V2: Date cannot be read in cyclic
0x0014Impermissible valueChange access with a value that is within the value
0x0015Response too longThe length of the current response exceeds the
0x0016Impermissible parameter
address
0x0017Impermissible formatWrite request: Impermissible parameter data format
0x0018Number of values not
consistent
0x0019Reserved--
...
0x0064
Access to unavailable parameter-
Change access to a parameter value that cannot be
changed
Change access with value outside the value limitsSubindex
data type of the parameter
Change access with non-zero value where this is not
permitted
Change access to a description element that cannot
be changed
not available)
available)
data transfer)
data transfer)
available)
Access is not possible for temporary reasons that are
not specified in detail
data transfer)
limits but is not permissible for other permanent
reasons (parameter with defined single values)
maximum transmittable length
Impermissible value or value which is not supported
for the attribute, number of subindexes, parameter
number, or subindex, or a combination
or parameter data format which is not supported
Write request: Number of parameter data values
does not match the number of subindexes in the
parameter address
information
Subindex
-
Subindex
Subindex
-
-
-
-
-
-
-
Subindex
-
-
-
-
62LEDS84AYCER EN 2.0 - 11/2010
Page 63
E84AYCER communication manual (PROFINET)
Parameter data transfer
Error information (error)
Error codeMeaningDescriptionAdditional
0x0065Manufacturer-specific--
...
0x00FF
information
EDS84AYCER EN 2.0 - 11/2010L63
Page 64
E84AYCER communication manual (PROFINET)
Parameter data transfer
Consistent parameter data
9.5Consistent parameter data
In the PROFINET communication system, data are permanently exchanged between the
host (CPU + IO controller) and the standard device via the plugged-on IO device interface
module. The IO controller and the CPU (central processing unit) of the host access a joint
memory: the dual port memory (DPM).
ο The DPM allows data exchange in both directions (write/read):
Central processing unit
(CPU)
Dual port memory
(DPM)
IO controller
It could happen that a slower IO controller writing would be overtaken by a faster CPU
reading within a cycle time without any further data organisation.
To avoid such an impermissible state, the parameter data to be transmitted must be
marked as "consistent".
Data communication with consistency
With consistency, either "reading" or "writing" is possible when the IO controller and the
CPU simultaneously access the memory:
ο The IO controller transfers data only as a complete data set.
ο The CPU can only access completely updated data sets.
ο The IO controller cannot read or write data as long as the CPU accesses consistent data.
The result becomes clear from the example below:
Central processing unit
(CPU)
CPU wants to read.IO controller wants to write at the same
Dual port memory
(DPM)
time.
IO controller
1. As the IO controller can only write when the CPU does not read, the IO controller has to
wait until the data are completely read by the CPU.
2. The IO controller only writes a complete data set into the DPM.
Consistency is achieved by a suitable IO controller configuration.
Please refer to the corresponding documentation of your configuring software.
64LEDS84AYCER EN 2.0 - 11/2010
Page 65
10Monitoring
Interruption of PROFINET communication
An interruption of PROFINET communication in the DATA_EXCHANGE state, e.g. by cable
break or failure of the IO controller is recognised by the IO device.
ο The response to the communication interruption is controlled via the following
settings:
1. During the initialisation of PROFINET communication the watchdog monitoring
time specified in the IO controller is transferred to the IO device.
If the IO device does not receive any valid process data in the DATA_EXCHANGE
state, the process data are treated according to the setting in C13885
the data that were sent last by the IO controller can be used or set to zero.)
After the watchdog monitoring time has elapsed, the IO device changes to the
NO_DATA_EXCHANGE status (see C13861
(Fieldbus status displays
E84AYCER communication manual (PROFINET)
Monitoring
. (Like this
), and the red LED "BE" is activated
(ο 68)).
There is no reponse in the IO device
2. To trigger a response in the IO device, you have to set a Response of the Inverter Drive 8400 (C13880
By setting a Reaction time delay (C13881
The response delay elapses when the DATA_EXCHANGE status is exited.
After this response delay has elapsed, the response set is executed with the error
message "PROFINET: Data_Exchange status quit [0x01bc6531]
) additionally in the Β»EngineerΒ« under the Monitoring tab.
.
) you can decelerate this response.
" (ο 76).
EDS84AYCER EN 2.0 - 11/2010L65
Page 66
E84AYCER communication manual (PROFINET)
Diagnostics
LED status displays
11Diagnostics
For purposes of fault diagnostics, the PROFINET module is provided with the LEDs on the
front. Furthermore you can carry out the Diagnostics with the Β»EngineerΒ«
β’ the green LED at the X256/X257 RJ45 sockets must be lit or blinking
The following status displays can be distinguished:
(ο 67) and BS (ο 68) should be lit permanently.
(ο 70).
(ο 69).
ο Module status displays
ο Fieldbus status displays (ο 68)
ο Status displays at X256 and X257 (ο 69)
(ο 67)
66LEDS84AYCER EN 2.0 - 11/2010
Page 67
11.1.1Module status displays
The LEDs MS, ME, and DE display the status of the module.
MS
E84AYCER communication manual (PROFINET)
Diagnostics
LED status displays
ME
DE
LEDColourStatusDescription
MSGreenOn
The communication module is supplied with voltage and has
established a connection to the standard device.
Blinking
200 ms
200 ms
The communication module is supplied with voltage, but has not
established a connection to the standard device. (Standard device is
switched off, in the initialisation phase, or not available.)
MERedOn
An error in the communication module has occurred.
Blinking
200 ms
200 ms
The "Node blinking test" PROFINET function is activated by the IO
controller.
The blinking LED serves to identify/localise accessible IO devices.
DERedOn
E84YCER006
The communication module is not accepted by the standard device
or the standard device is not active. (See notes in the documentation
of the standard device.)
EDS84AYCER EN 2.0 - 11/2010L67
Page 68
E84AYCER communication manual (PROFINET)
Diagnostics
LED status displays
11.1.2Fieldbus status displays
The LEDs BS and BE display the status of the fieldbus.
BS
BE
E84YCER006
LEDColourStatusDescription
BSGreenOffThe communication module is not active on the fieldbus or is in the
INIT status.
Blinking
200 ms
200 ms
The communication module is in the DATA_EXCHANGE status.
BERedOn
Bus error/fault is active (e.g. Ethernet cable not connected). The
communication module is in the NO_DATA_EXCHANGE state.
Blinking
200 ms
200 ms
Impermissible settings:
β’ Invalid station name
β’ Invalid IP parameters
The communication module has been initialised and continues to
work internally with the respective standard values.
68LEDS84AYCER EN 2.0 - 11/2010
Page 69
E84AYCER communication manual (PROFINET)
11.1.3Status displays at X256 and X257
The LEDs below RJ45 sockets X256 and X257 display the PROFINET connection status.
A
B
Diagnostics
LED status displays
A
B
LEDColourStatusDescription
AGreenOffThere is no PROFINET connection.
On
There is a PROFINET connection.
BYellowOffNo communication
On or
Jittering
50 ms
Communication active
E84YCER005
EDS84AYCER EN 2.0 - 11/2010L69
Page 70
E84AYCER communication manual (PROFINET)
Diagnostics
Diagnostics with the Β»EngineerΒ«
11.2Diagnostics with the Β»EngineerΒ«
In the Β»EngineerΒ« under the Diagnostics tab, various PROFINET diagnostic information can
be displayed.
70LEDS84AYCER EN 2.0 - 11/2010
Page 71
11.3Diagnostic data
ο The IO device sends an alarm message to the IO controller to signalise the diagnostic
data below.
E84AYCER communication manual (PROFINET)
Diagnostics
Diagnostic data
ο Code C13887
serves to inhibit the transmission of alarm messages to the IO controller.
By this, errors of a specific type can be systematically suppressed.
ο Errors and warnings in the Inverter Drive 8400 and the plugged-in module are sent to
the IO controller as extended diagnostic messages.
ο The diagnostic data can be displayed using the hexadecimal representation of the
ο Bytes 29 ... 32 of the diagnostic message indicate the error code of the Inverter Drive
8400.
ο To make reading easier, the following syntax is used to display the error number in the
logbook and standard device code C00165:
[error type].[error subject area no.].[error ID]
Example
162526
015
Diagnostic message of the error "PROFINET: Data_Exchange status quit [0x01bc6531]
Bit assignment
(bytes 29 ... 32)
30
31
Bit
00
29
Bit
Bit
Bit
26
0000
25
0
16
000
111111
015
00010011
10
0001
11
InformationValues from the example
ReservedBits 24 ... 31: 0x01 (00000001
Error type
Error subject areaBits 16 ... 23: 0xbc (10111100
Error IDBits 8 ... 15: 0x65 (01100101
Bits 0 ... 7: 0x31 (00110001
bin
bin
bin
bin
)
)
)
)
ο¬Software manual/Β»EngineerΒ« online help for the Inverter Drive 8400
Here you'll find some detailed information on the error codes.
":
72LEDS84AYCER EN 2.0 - 11/2010
Page 73
E84AYCER communication manual (PROFINET)
Short overview (A-Z) of the PROFINET error messages
12Error messages
This chapter provides the error messages of the communication module as a supplement
to the error list in the software manual and the Β»EngineerΒ« online help for the Inverter
Drive 8400.
ο¬Software manual/Β»EngineerΒ« online help for the Inverter Drive 8400
General information on diagnostics & fault analysis and error messages is
provided here.
12.1Short overview (A-Z) of the PROFINET error messages
The following table contains all error messages of the communication module in
alphabetical order with the preset error response and, if available, the parameter for
setting the error response.
Error messages
ο Tip!
When you click the cross-reference in the last column, you will get a detailed
description (causes and remedies) of the corresponding error message.
Error textError typeSubject area
PROFINET: Data_Exchange status quit0: None44425905C13880/1
PROFINET: Station name error1: Fault44425906-0x01bc6532
PROFINET: Record parameter: Invalid read4: Warning locked44425857-0x01bc6501
PROFINET: Record parameter: Invalid write4: Warning locked44425858-0x01bc6502
no.
Error no.Adjustable inDetailed
information
0x01bc6531
EDS84AYCER EN 2.0 - 11/2010L73
Page 74
E84AYCER communication manual (PROFINET)
Error messages
Possible causes and remedies
12.2Possible causes and remedies
In this chapter, all error messages of the communication module are listed in numerical
order of the error numbers. Possible causes and remedies and responses to the error
messages are described in detail.
ο Tip!
You will find a list of all error messages of the communication module in
alphabetical order in the previous chapter "Short overview (A-Z) of the PROFINET
error messages" (ο 73).
PROFINET: Exist. conn. to 8400 lost [0x01bc3100]
Response (Lenze setting in bold)Setting: not possible
ξ None ξ System fault : Fault ξ Trouble ξ Quick stop by trouble ξ Warning locked ξ Warning ξ Information
CauseRemedy
β’ Network cable (plug) is defective.
β’ Network cable at PROFINET terminal X256 or X257 is
disconnected.
β’ Voltage supply is interrupted.
PROFINET: Memory: No access [0x01bc5531]
PROFINET: Memory: Read error [0x01bc5532]
PROFINET: Memory: Write error [0x01bc5533]
Response (Lenze setting in bold)Setting: not possible
ξ None ξ System fault : Fault ξ Trouble ξ Quick stop by trouble ξ Warning locked ξ Warning ξ Information
CauseRemedy
Memory could not be accessed.Send device with error description to Lenze.
Response (Lenze setting in bold)Setting: not possible
ξ None ξ System fault : Fault ξ Trouble ξ Quick stop by trouble ξ Warning locked ξ Warning ξ Information
CauseRemedy
Parameter could not be read.Send device with error description to Lenze.
Response (Lenze setting in bold)Setting: not possible
ξ None ξ System fault : Fault ξ Trouble ξ Quick stop by trouble ξ Warning locked ξ Warning ξ Information
Check cables and connections.
Plug in network cable at PROFINET terminal X256 or
X257.
CauseRemedy
Parameter could not be written.Send device with error description to Lenze.
74LEDS84AYCER EN 2.0 - 11/2010
Page 75
PROFINET: Restart by watchdogreset [0x01bc6010]
Response (Lenze setting in bold)Setting: not possible
ξ None ξ System fault : Fault ξ Trouble ξ Quick stop by trouble ξ Warning locked ξ Warning ξ Information
CauseRemedy
Device is defective.Send device with error description to Lenze.
PROFINET: Internal error [0x01bc6011]
Response (Lenze setting in bold)Setting: not possible
ξ None ξ System fault : Fault ξ Trouble ξ Quick stop by trouble ξ Warning locked ξ Warning ξ Information
CauseRemedy
Device is defective.Send device with error description to Lenze.
PROFINET: Internal error [0x01bc6100]
Response (Lenze setting in bold)Setting: not possible
ξ None ξ System fault : Fault ξ Trouble ξ Quick stop by trouble ξ Warning locked ξ Warning ξ Information
E84AYCER communication manual (PROFINET)
Error messages
Possible causes and remedies
CauseRemedy
Internal errorSend device with error description to Lenze.
PROFINET: Internal error [0x01bc6101]
Response (Lenze setting in bold)Setting: not possible
ξ None ξ System fault : Fault ξ Trouble ξ Quick stop by trouble ξ Warning locked ξ Warning ξ Information
CauseRemedy
Internal errorSend device with error description to Lenze.
PROFINET: Invalid parameter set [0x01bc641f]
Response (Lenze setting in bold)Setting: not possible
ξ None ξ System fault : Fault ξ Trouble ξ Quick stop by trouble ξ Warning locked ξ Warning ξ Information
CauseRemedy
Loading of an active parameter set was not possible.Download application again (including module).
Response (Lenze setting in bold)Setting: not possible
ξ None ξ System fault : Fault ξ Trouble ξ Quick stop by trouble ξ Warning locked ξ Warning ξ Information
CauseRemedy
An invalid IP address has been assigned by the IO
controller via PROFINET or has been set in code C13000
PROFINET: Stack init error [0x01bc6534]
Response (Lenze setting in bold)Setting: not possible
ξ None ξ System fault : Fault ξ Trouble ξ Quick stop by trouble ξ Warning locked ξ Warning ξ Information
CauseRemedy
The stack cannot be initialised with the parameters
selected by the user. This may be due to a station name
which does not comply with the PROFINET specification.
PROFINET: Internal error [0x01bc6650]
Response (Lenze setting in bold)
ξ None ξ System fault : Fault ξ Trouble ξ Quick stop by trouble ξ Warning locked ξ Warning ξ Information
CauseRemedy
Internal errorSend device with error description to Lenze.
β’ Make sure that the IO controller has assigned a valid
.
IP address via PROFINET.
β’ Set a valid IP address.
ξSetting the IP configuration
Check and, if necessary, adapt PROFINET parameters:
ξSetting the IP configuration
ξSetting the station name
(ο 38)
(ο 38)
(ο 36)
EDS84AYCER EN 2.0 - 11/2010L77
Page 78
E84AYCER communication manual (PROFINET)
Parameter reference
Parameters of the communication module
13Parameter reference
This chapter supplements the parameter list and the table of attributes in the software
manual and in the Β»EngineerΒ« online help for the Inverter Drive 8400 by the parameters of
the E84AYCER communication module (PROFINET).
ο¬Software manual/Β»EngineerΒ« online help for the Inverter Drive 8400
General information on parameters is provided here.
13.1Parameters of the communication module
This chapter lists the parameters of the E84AYCER communication module (PROFINET) in
numerically ascending order.
If the "Reset to factory defaults" PROFINET command is executed by a supervisor
or an IO controller, the PROFINET-specific parameters will be reset to their
standard values:
β’ C13000
β’ C13001
β’ C13002
β’ C13010
β’ C13011
β’ C13012
β’ C13864
β’ C13899
β’ C13910
β’ C13911
β’ C13912
β’ C13913
β’ C13914
| IP address
| Subnetwork mask
| Gateway address
| Active IP address
| Active subnetwork mask
| Active gateway address
| Active station name
| Station name
| I&M1 system designation
| I&M1 installation site
| I&M2 installation date
| I&M3 additional information
| I&M4 signature code
78LEDS84AYCER EN 2.0 - 11/2010
Page 79
C13000
E84AYCER communication manual (PROFINET)
Parameter reference
Parameters of the communication module
C13001
C13002
Parameter | Name:
Data type: UNSIGNED_32
C13000 | IP address
Setting the IP address
ξSetting the IP configuration
(ο 38)
Setting range (min. value | unit | max. value)Lenze setting
04294967295 0
; Read access ; Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Parameter | Name:
Data type: UNSIGNED_32
C13001 | Subnetwork mask
Setting the subnet mask
ξSetting the IP configuration
(ο 38)
Setting range (min. value | unit | max. value)Lenze setting
04294967295 0
; Read access ; Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Parameter | Name:
Data type: UNSIGNED_32
C13002 | Gateway address
Setting the gateway address
ξSetting the IP configuration
(ο 38)
Setting range (min. value | unit | max. value)Lenze setting
04294967295 0
; Read access ; Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Index: 11575
Index: 11574
Index: 11573
= 2D37
d
= 2D36
d
= 2D35
d
h
h
h
C13003
Parameter | Name:
Data type: OCTET_STRING
C13003 | Physical address
Display of the MAC-ID
SubcodesInformation
C13003/1MAC ID: Station
C13003/2MAC ID: Port1
C13003/3MAC ID: Port2
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Index: 11572
= 2D34
d
h
EDS84AYCER EN 2.0 - 11/2010L79
Page 80
E84AYCER communication manual (PROFINET)
Parameter reference
Parameters of the communication module
C13010
C13011
Parameter | Name:
Data type: UNSIGNED_8
C13010 | Active IP address
Display of the active IP address
β’ The active IP address may differ from the contents of code C13000
, depending on whether the station name was
changed via the fieldbus or the parameter.
SubcodesInformation
C13010/1Active IP address.1
C13010/2Active IP address.2
C13010/3Active IP address.3
C13010/4Active IP address.4
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Parameter | Name:
Data type: UNSIGNED_8
C13011 | Active subnetwork mask
Display of the active subnetwork mask
β’ The active subnetwork mask may differ from the contents of code C13001
, depending on whether the station
name was changed via the fieldbus or the parameter.
Display range (min. value | unit | max. value)
0255
SubcodesInformation
C13011/1Active subnetwork mask.1
C13011/2Active subnetwork mask.2
C13011/3Active subnetwork mask.3
C13011/4Active subnetwork mask.4
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Index: 11565
Index: 11564
= 2D2D
d
= 2D2C
d
h
h
C13012
Parameter | Name:
Data type: UNSIGNED_8
C13012 | Active gateway address
Display of the active gateway address
β’ The active gateway address may differ from the contents of code C13002
, depending on whether the station
name was changed via the fieldbus or the parameter.
Display range (min. value | unit | max. value)
0255
SubcodesInformation
C13012/1Active gateway address.1
C13012/2Active gateway address.2
C13012/3Active gateway address.3
C13012/4Active gateway address.4
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Index: 11563
= 2D2B
d
h
80LEDS84AYCER EN 2.0 - 11/2010
Page 81
C13850
E84AYCER communication manual (PROFINET)
Parameter reference
Parameters of the communication module
C13851
Parameter | Name:
C13850 | All words to master
Data type: UNSIGNED_16
Index: 10725
= 29E5
d
Display of the process data words which are transmitted from the controller to the IO controller.
In the subcodes 1 to 16, all process data words to the IO controller are displayed. However, only the configured
process data words are valid.
Display range (min. value | unit | max. value)
065535
SubcodesInformation
C13850/1
...
C13850/16
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Parameter | Name:
C13851 | All words from master
Data type: UNSIGNED_16
Index: 10724
= 29E4
d
Display of the process data words which are transmitted from the IO controller to the controller.
In the subcodes 1 to 16, all process data words from the IO controller are displayed. However, only the configured
process data words are valid.
Display range (min. value | unit | max. value)
065535
SubcodesInformation
C13851/1
...
C13851/16
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
h
h
C13852
Parameter | Name:
C13852 | All words to standard device
Data type: UNSIGNED_16
Index: 10723
Display of the process data words 1 ... 16, which are transmitted from the IO controller to the controller.
Display range (min. value | unit | max. value)
065535
SubcodesInformation
C13852/1
...
C13852/16
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
= 29E3
d
h
EDS84AYCER EN 2.0 - 11/2010L81
Page 82
E84AYCER communication manual (PROFINET)
Parameter reference
Parameters of the communication module
C13853
C13860
Parameter | Name:
C13853 | All words from standard device
Data type: UNSIGNED_16
Index: 10722
Display of the process data words 1 ... 16, which are transmitted from the controller to the IO controller.
Display range (min. value | unit | max. value)
065535
SubcodesInformation
C13853/1
...
C13853/16
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Parameter | Name:
C13860 | Settings
Data type: UNSIGNED_8
Index: 10715
Display range (min. value | unit | max. value)
0255
SubcodesInformation
C13860/1Reserved
C13860/2Number of process data words
C13860/3Reserved
C13860/4Reserved
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
= 29E2
d
= 29DB
d
h
h
C13861
Parameter | Name:
C13861 | Bus status
Bit-coded display of current bus status
Value is bit-coded:
Bit 0 Initialised
Bit 1 Online
Bit 2 Connected
Bit 3 Address conflict
Bit 4 Hardware error
Bit 5 EEPROM error
Bit 6 Watchdog error
Bit 7 Protocol error
Bit 8 Profinet stack ok
Bit 9 Profinet stack not configured
Bit 10 Ethernet controller error
Bit 11 UDP stack error
Bit 12 Reserved
Bit 13 Reserved
Bit 14 Reserved
Bit 15 Reserved
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Data type: BITFIELD_16
Index: 10714
= 29DA
d
h
82LEDS84AYCER EN 2.0 - 11/2010
Page 83
C13862
E84AYCER communication manual (PROFINET)
Parameter reference
Parameters of the communication module
C13864
Parameter | Name:
Data type: UNSIGNED_32
C13862 | Bus counter
Display of data cycles per second (irrespective of data changes)
Display range (min. value | unit | max. value)
04294967295
SubcodesInformation
C13862/1Data cycles per second
C13862/2Read cycles per second
C13862/3Write cycles per second
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Parameter | Name:
Data type: VISIBLE_STRING
C13864 | Active station name
Displays the active station name used by the controller.
It may differ from the contents of code C13899
fieldbus or via C13899
ξSetting the station name
.
(ο 36)
, depending on whether the station name has been changed via the
SubcodesInformation
C13864/11st ... 30th character
C13864/231st ... 60th character
C13864/361st ... 90th character
C13864/491st ... 120th character
C13864/5121st ... 150th character
C13864/6151st ... 180th character
C13864/7181st ... 210th character
C13864/8211th ... 240th character
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Index: 10713
Index: 10711
= 29D9
d
= 29D7
d
h
h
EDS84AYCER EN 2.0 - 11/2010L83
Page 84
E84AYCER communication manual (PROFINET)
Parameter reference
Parameters of the communication module
C13867
Parameter | Name:
Data type: OCTET_STRING
C13867 | Display: Most recent diagnostic data
Display of diagnostic data sent by the controller most recently:
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
BytesInformation
0Slot
1
2Subslot
3
4Error code
...
7
8Slot
9
10Subslot
11
12Error code
...
15
Index: 10708
= 29D4
d
h
C13877
Parameter | Name:
Data type: UNSIGNED_16
C13877 | Bus error(1)
The code contains the error currently detected on the fieldbus.
β’ The error values can occur in combination with the error values from code C13878
.
Selection list (read only)Information
0 No fail
1 Internal error
2 Unit ID unknown
3 Max. units exceeded
4 Invalid size
5 Unit type unknown
6 Runtime plug
7 Invalid argument
8 Service pending
9 Stack not ready
10 Command unknown
11 Invalid address descriptor
12 Watchdog expired
13 Protocol not supported
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Index: 10698
= 29CA
d
h
84LEDS84AYCER EN 2.0 - 11/2010
Page 85
C13878
E84AYCER communication manual (PROFINET)
Parameter reference
Parameters of the communication module
C13880
Parameter | Name:
C13878 | Bus error(2)
Data type: BITFIELD_16
Index: 10697
The code contains the error currently detected on the fieldbus.
β’ The error values can occur in combination with the error values from code C13877
.
Value is bit-coded:Information
Bit 0 Reserved
... ...
Bit 6 Reserved
Bit 7 IP address error
Bit 8 Station name error
Bit 9 DataExch left
Bit 10 Stack boot error
Bit 11 Stack online error
Bit 12 Stack state error
Bit 13 Stack revision error
Bit 14 Stack init error
Bit 15 Stack CPU boot error
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Parameter | Name:
C13880 | Reaction on communication failure
Data type: UNSIGNED_8
Index: 10695
The action set in subcode 1 of the code is carried out when the node recognises that it is no longer in the
DATA_EXCHANGE status.
β’ Please also observe the notes in code C13881
.
β’ A change in the monitoring response becomes effective immediately.
Selection list
0 No response
1 Error
3 Quick stop by trouble
4 Warning locked
6 Information
SubcodesLenze settingInformation
C13880/10: No response"Watchdog/Data Exchange" monitoring
; Read access ; Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
= 29C9
d
= 29C7
d
h
h
C13881
Parameter | Name:
C13881 | Reaction time delay
Data type: UNSIGNED_16
Index: 10694
= 29C6
d
If the "DATA_EXCHANGE" status is exited, the response parameterised in C13880 is activated after the time set here
.
β’ The value = 65535 in this code deactivates monitoring.
β’ A change in the monitoring mode becomes effective immediately.
Setting range (min. value | unit | max. value)Lenze setting
0ms65535 0ms
; Read access ; Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
EDS84AYCER EN 2.0 - 11/2010L85
h
Page 86
E84AYCER communication manual (PROFINET)
Parameter reference
Parameters of the communication module
C13885
C13887
Parameter | Name:
C13885 | Clear process data
Data type: UNSIGNED_8
Index: 10690
= 29C2
d
This code is used to set the process data that are to be processed by the IO device in order to maintain internal
communication when the PROFINET has left the DATA_EXCHANGE status.
Selection list (Lenze setting printed in bold)Information
0 Use of most recent master PDOsThe last data sent by the IO controller are used.
1 PDOs are set to the value'0'The contents of the process data are set to the value "0".
; Read access ; Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Parameter | Name:
C13887 | Suppress signalling diag. mess. upon
Data type: BITFIELD_8
Index: 10688
= 29C0
d
This code serves to inhibit the transmission of alarm messages to the IO controller. By this, errors of a specific type
can be systematically suppressed. All errors are furthermore entered in the logbook.
β’ A change will only become effective immediately if no error number with the error type selected here is pending
in C00165.
Value is bit-coded:Information
Bit 0 Fault
Bit 1 Trouble
Bit 2 Quick stop by trouble
Bit 3 Warning locked
Bit 4 Warning
Bit 5 Reserved
Bit 6 Reserved
Bit 7 Reserved
; Read access ; Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
h
h
C13899
Parameter | Name:
C13899 | Station name
Data type: VISIBLE_STRING
Index: 10676
= 29B4
d
The name with a max. length of 240 characters is distributed to the subindices. The name can be entered starting
with subindex 1. The following unused subindices are not relevant.
β’ The station name must be assigned in accordance with the PROFINET specification. In the standard setting a
deleted name is displayed. The name is also deleted if the "Reset to factory defaults" command is executed by an
IO supervisor or an IO controller.
β’ A change of the station name will only become effective by switching the mains of the controller.
ξSetting the station name
(ο 36)
SubcodesLenze settingInformation
C13899/11st ... 30th character
C13899/231st ... 60th character
C13899/361st ... 90th character
C13899/491st ... 120th character
C13899/5121st ... 150th character
C13899/6151st ... 180th character
C13899/7181st ... 210th character
C13899/8211th ... 240th character
; Read access ; Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
h
86LEDS84AYCER EN 2.0 - 11/2010
Page 87
C13900
E84AYCER communication manual (PROFINET)
Parameter reference
Parameters of the communication module
C13901
C13902
C13910
Parameter | Name:
C13900 | Firmware product type
Data type: VISIBLE_STRING
Index: 10675
The code contains a string with a length of 8 bytes. The identification code "E84DFYER" is displayed.
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Parameter | Name:
C13901 | Firmware compilation date
Data type: VISIBLE_STRING
Index: 10674
The code contains a string with a length of 20 bytes. The software creation date ("MMM DD YYYY") and time
("hh:mm:ss") are displayed (e.g. "Mar 21 2005 12:31:21").
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Parameter | Name:
C13902 | Firmware version
Data type: VISIBLE_STRING
Index: 10673
The code contains a string with a length of 11 bytes. The identification code is displayed (e.g. "01.00.00.00").
; Read access ξ Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Parameter | Name:
C13910 | I&M1 System designation
Data type: VISIBLE_STRING
Index: 10665
Input/output of the I&M1 plant identification code
β’ The Lenze setting shows an empty string.
; Read access ; Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
= 29B3
d
= 29B2
d
= 29B1
d
= 29A9
d
h
h
h
h
C13911
C13912
Parameter | Name:
Data type: VISIBLE_STRING
C13911 | I&M1 Installation site
Input/output of the I&M1 location identification code
β’ The Lenze setting shows an empty string.
; Read access ; Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Parameter | Name:
Data type: VISIBLE_STRING
C13912 | I&M2 Installation date
Input/output of the I&M2 date of installation
β’ The Lenze setting shows an empty string.
; Read access ; Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Index: 10664
Index: 10663
= 29A8
d
= 29A7
d
h
h
EDS84AYCER EN 2.0 - 11/2010L87
Page 88
E84AYCER communication manual (PROFINET)
Parameter reference
Parameters of the communication module
C13913
C13914
Parameter | Name:
Data type: VISIBLE_STRING
C13913 | I&M3 additional information
Input/output if the I&M3 additional information
β’ The Lenze setting shows an empty string.
SubcodesLenze settingInformation
C13913/1I&M3 additional information
C13913/2I&M3 additional information
; Read access ; Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Parameter | Name:
Data type: OCTET_STRING
C13914 | I&M4 signature code
Input/output of the I&M4 signature
Setting range (min. value | unit | max. value)
SubcodesLenze settingInformation
C13914/100000000000000000000000000000
I&M4 signature
0000000000000000000000000
C13914/200000000000000000000000000000
I&M4 signature
0000000000000000000000000
; Read access ; Write access ξ CINH ξ PLC-STOP ξ No transfer ξ PDO_MAP_RX ξ PDO_MAP_TX ξ COM ξ MOT
Index: 10662
Index: 10661
= 29A6
d
= 29A5
d
h
h
88LEDS84AYCER EN 2.0 - 11/2010
Page 89
13.2Table of attributes
The table of attributes contains information which is required for communicating with the
controller via parameters.
How to read the table of attributes:
ColumnMeaningEntry
CodeParameter nameCxxxxx
NameParameter short text (display text)Text
IndexdecIndex by which the parameter is addressed.
hex5FFF
DataDSData structureESingle variable
DANumber of array elements (subcodes)Number
DTData typeBITFIELD_81 byte, bit-coded
FactorFactor for data transmission via a bus system,
AccessRRead access; Reading permitted
WWrite access; Writing permitted
CINHController inhibit required; Writing is only possible when the controller is inhibited
The subindex for array variables corresponds to the
Lenze subcode number.
depending on the number of decimal positions
E84AYCER communication manual (PROFINET)
Parameter reference
Table of attributes
24575 - Lenze code numberOnly required for access via bus
Accessing process data 42
Activating altered settings 40
Active gateway address (C13012) 80
Active IP address (C13010) 80
Active station name (C13864) 83
Active subnetwork mask (C13011) 80
Acyclic channel (PROFIdrive profile) 48
Acyclic data transfer 49
Acyclic data transmission process 49
All words from master (C13851) 81
All words from standard device (C13853) 82
All words to master (C13850) 81
All words to standard device (C13852) 81
Application as directed 14
Application notes (representation) 11
Approvals 16
B
Baud rate 16
Before initial switch-on 34
Bus counter (C13862) 83
Bus error(1) (C13877) 84
Bus error(2) (C13878) 85
Bus status (C13861) 82
C
C13000 | IP address 79
C13001 | Subnetwork mask 79
C13002 | Gateway address 79
C13003 | Physical address 79
C13010 | Active IP address 80
C13011 | Active subnetwork mask 80
C13012 | Active gateway address 80
C13850 | All words to master 81
C13851 | All words from master 81
C13852 | All words to standard device 81
C13853 | All words from standard device 82
C13860 | Settings 82
C13861 | Bus status 82
C13862 | Bus counter 83
C13864 | Active station name 83
C13867 | Display
Most recent diagnostic data
C13877 | Bus error(1) 84
C13878 | Bus error(2) 85
C13880 | Reaction on communication failure 85
C13881 | Reaction time delay 85
C13885 | Clear process data 86
C13887 | Suppress signalling diag. mess. upon 86
C13899 | Station name 86
84
C13900 | Firmware product type 87
C13901 | Firmware compilation date 87
C13902 | Firmware version 87
C13910 | I&M1 system designation 87
C13911 | I&M1 installation site 87
C13912 | I&M2 installation date 87
C13913 | I&M3 additional information 88
C13914 | I&M4 signature code 88
Cable length 16
Carry out the port interconnection in the Β»EngineerΒ«
44
Clear process data (C13885) 86
Codes 78
Colour code of the Ethernet cable 31
Commissioning 34
Communication channels 41
Communication medium 16
Communication profile 16
Communication time 19
Configuration for device control 35
Configuring consistent data 64
Configuring the IO controller 35
Conformities 16
Connection establishment of an IO controller to an IO
device
48
Consistent parameter data 64
Conventions 9
Conventions used 9
Copyright 2
D
Data communication with consistency 64
Data transfer 41
Data transmission (process) 49
Device- and application-specific safety instructions 13
Device data base file 35
Device description file 35
Device ID 16
Device identification 16
Device protection 13
Diagnostic data 71
Diagnostic messages 71
Diagnostics 66
Diagnostics with the Β»EngineerΒ« 70
Dimensions 21
Display
Most recent diagnostic data (C13867)
Document history 8
84
EDS84AYCER EN 2.0 - 11/2010L91
Page 92
E84AYCER communication manual (PROFINET)
Index
E
Electrical installation 26
EMC-compliant wiring 26
Error code of the Inverter Dive 8400 72
Error information (error) 62
Error messages 73
Fieldbus status displays 68
Firmware compilation date (C13901) 87
Firmware product type (C13900) 87
Firmware version (C13902) 87
G
Gateway address 39
Gateway address (C13002) 79
General data 16
General safety instructions and application notes 12
I
I&M1 installation site (C13911) 87
I&M1 system designation (C13910) 87
I&M2 installation date (C13912) 87
I&M3 additional information (C13913) 88
I&M4 signature code (C13914) 88
Identification 14
Initial switch-on 40
Installation 22
Interface 16
Interfaces 15
Internal switch latency 20
Interruption of PROFINET communication 65
IP address 39
IP address (C13000) 79
L
LED status displays 66
M
Mechanical installation 23
Module status displays 67
Monitoring 65
Mounting for standard devices 0.25 kW and 0.37 kW
23
Mounting for standard devices from 0.55 kW 24
N
Nameplate 14
Network topology 16, 26
Notes used 11
Number of nodes 16
O
Operating conditions 16
P
Parameter data 41
Parameter data transfer 48
Parameter reference 78
Parameters of the communication module 78
PDO mapping 42
Physical address (C13003) 79
Pin assignment of the RJ45 sockets 29
Process data transfer 42
Processing time 19
Product description 14
PROFINET
Data_Exchange status quit (error message)
Error
Lenze setting loaded (error message)
Exist. conn. to 8400 lost (error message) 74
Internal error (error message) 75, 77
Invalid module configuration (error message) 76
Invalid output data (error message) 76
Invalid parameter set (error message) 75
IP address error (error message) 77
Memory
Invalid write (error message) 76
Restart by watchdogreset (error message) 75
Stack init error (error message) 77
Station name error (error message) 77
PROFINET connection 28
PROFINET error messages (short overview) 73
Properties 15
Protection against uncontrolled restart 40
Protection of persons 13
Protective insulation 17
Protocol data 19
PUO ID number 16
76
R
Reaction on communication failure (C13880) 85
Reaction time delay (C13881) 85
Reading parameters from the controller 51
Replacing the communication module 25
Residual hazards 13
Runtime delays 20
S
Safety instructions 12
Safety instructions (representation) 11
Setting the IP configuration 38
Setting the station name 36
Settings (C13860) 82
Specification of the Ethernet cable 30
Station name (C13899) 86
Status displays (LEDs) 66
Status displays at X256 and X257 69
Structure of the Ethernet cable 30
Structure of the PROFINET data telegram 50
Subnet mask 39
Subnetwork mask (C13001) 79
Suppress signalling diag. mess. upon (C13887) 86
Switch latency 16, 20
Switching method 16
System error messages 73
U
Use of repeaters 27
User data assignment 50
User data length 35
Using the communication module 14
V
Validity of the documentation 7
Voltage supply 16, 32
W
Writing parameters to the controller 56
X
XML file for configuration 35
T
Table of attributes 89
Target group 7
Technical data 16
Telegram example
Read request
Write request 60
Terminals 15, 33
Terminology used 10
Terms 10
Type of node 16