Accessories DeviceNet™ 13451097 Ä.
Contents ________________________________________________________________ 1 1.1 1.2 1.3 1.
Contents ________________________________________________________________ 8 8.1 8.2 Monitoring _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Interruption of the DeviceNet communication _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Fault with regard to internal communication _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 39 39 40 9 9.1 9.2 9.
1 About this documentation ________________________________________________________________ 1 About this documentation This documentation only contains descriptions of the E94AYCDN (DeviceNet™) communication module. Note! This documentation supplements the mounting instructions supplied with the communication module and the Servo Drives 9400 hardware manual.
1 About this documentation ________________________________________________________________ Target group This documentation is intended for all persons who plan, install, commission and maintain the networking and remote servicing of a machine. Tip! Current documentation and software updates for Lenze products can be found in the download area at: www.lenze.
1 About this documentation 1.1 Document history ________________________________________________________________ 1.1 Document history Version 6 Description 1.0 04/2008 TD17 Field test version 2.0 06/2008 TD17 First edition 3.0 11/2008 TD17 General revision 4.0 01/2013 TD17 5.0 02/2014 TD17 • Update for C13861 / C14861 (module status) and C13862 / C14862 (network status) • New layout General updates Lenze · E94AYCDN communication module (DeviceNet™) · Communication Manual · DMS 5.
1 About this documentation 1.2 Conventions used ________________________________________________________________ 1.2 Conventions used This documentation uses the following conventions to distinguish different types of information: Type of information Identification Examples/notes Numbers Decimal Decimal separator Hexadecimal Binary • Nibble Standard notation Point 0x[0 ... 9, A ... F] In inverted commas Point Example: 1234 In general, the decimal point is used. Example: 1234.
1 About this documentation 1.3 Terminology used ________________________________________________________________ 1.3 Terminology used Term Meaning Drive Lenze inverters of the "Servo Drives 9400" product series Standard device Code Parameter which serves to parameterise and monitor the drive. In normal usage, the term is usually referred to as "Index". Subcode If a code contains several parameters, they are stored in so-called "subcodes".
1 About this documentation 1.4 Definition of the notes used ________________________________________________________________ 1.
2 Safety instructions 2.1 General safety instructions and application notes ________________________________________________________________ 2 Safety instructions Note! 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.
2 Safety instructions 2.2 Device and application-specific safety instructions ________________________________________________________________ 2.2 Device and application-specific safety instructions • During operation, the communication module must be firmly connected to the standard device. • 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).
3 Product description 3.1 Application as directed ________________________________________________________________ 3 Product description 3.1 Application as directed The communication module ... • is an accessory module which can be used in conjunction with the following standard devices: Product series Type designation Servo Drives 9400 HighLine E94AxHxxxx From hardware version From software version 1A 01.50 Servo Drives 9400 PLC E94AxPExxxx VA 02.
3 Product description 3.3 Product features ________________________________________________________________ 3.
3 Product description 3.4 Equipment ________________________________________________________________ 3.
4 Technical data 4.1 General data and operating conditions ________________________________________________________________ 4 Technical data 4.1 General data and operating conditions Area Values Order designation E94AYCDN Communication profile DeviceNet Interface 5-pole plug connector with screw connection Communication medium EN 11898 Network topology Line terminated at both ends (R = 120 ) Number of nodes Max. 64 Max.
4 Technical data 4.2 Protective insulation ________________________________________________________________ 4.2 Protective insulation Danger! Dangerous voltage If the Servo Drives 9400 are operated on a phase earthed mains with a rated mains voltage 400 V, external measures need to be implemented in order to ensure protection against accidental contact.
4 Technical data 4.2 Protective insulation ________________________________________________________________ The following illustration ... • shows the arrangement of the terminal strips and the separate potential areas of the drive. • serves to determine the decisive protective insulation between two terminals located in differently insulated separate potential areas. X1 X2 Reinforced insulation X100 X3 MXI1 Basic insulation Bus Functional insulation Ext.
4 Technical data 4.3 Protocol data ________________________________________________________________ Example Which type of protective insulation is there between the bus terminal of the device module on slot MXI1 or MXI2 and the mains terminal X100? The separate potential area with the better protective insulation is decisive. • The separate potential area of the bus terminal of the device module has a "functional insulation".
4 Technical data 4.5 Dimensions ________________________________________________________________ 4.5 Dimensions a 89 mm b 134 mm b1 87 mm e 23 mm E94YCXX005 [4-2] Dimensions Lenze · E94AYCDN communication module (DeviceNet™) · Communication Manual · DMS 5.
5 Installation ________________________________________________________________ 5 Installation Stop! Electrostatic discharge Electronic components within the communication module can be damaged or destroyed by electrostatic discharge. Possible consequences • The communication module is defective. • Fieldbus communication is not possible or faulty. Protective measures Free yourself from any electrostatic charge before you touch the module.
5 Installation 5.1 Mechanical installation ________________________________________________________________ 5.1 Mechanical installation 5.1.1 Mounting E94YCXX001G [5-1] 5.1.2 Mounting Dismounting E94AYCXX001H [5-2] Dismounting Lenze · E94AYCDN communication module (DeviceNet™) · Communication Manual · DMS 5.
5 Installation 5.2 Electrical installation ________________________________________________________________ 5.2 Electrical installation 5.2.1 Documentation relating to the standard device, host (PLC, scanner), system/machine Observe the notes and wiring instructions contained in this documentation. Wiring of the DeviceNet For communication with the scanner and all further components, Servo Drives 9400 have to be assembled with communication modules.
5 Installation 5.2 Electrical installation ________________________________________________________________ D1 ... n: Devices 1 ... n S: scanner (e.g. PLC, IPC) [5-3] E94YCDN008 DeviceNet line Note! • Connect a bus terminating resistor of 120 each to the first and the last node of the DeviceNet line. • Connect the shield at the voltage supply together with the "V-" connection to GND once. For this purpose, use the centre point of the DeviceNet line, if possible.
5 Installation 5.2 Electrical installation ________________________________________________________________ 5.2.2 DeviceNet connection The bus connection of the communication module is effected via the 5-pole plug connector with double screw connection (X225).
5 Installation 5.2 Electrical installation ________________________________________________________________ 5.2.3 Specification of the bus cable The nodes of the bus system must be wired with a fieldbus cable - a DeviceNet thick or thin cable according to the DeviceNet specifications (DeviceNet Adaption of CIP, Edition 1.1, Volume 3). DeviceNet thick and thin cables for instance are manufactured by Belden Inc., Lapp, C&M Corp., and Madison Cable Corp.
5 Installation 5.2 Electrical installation ________________________________________________________________ Data line properties Wire pair At least copper 18; at least 19 cores (individually tinned) Insulation diameter 3.81 mm (nominal) Colours Light blue / white Pair windings / m Approx. 10 Shielding per wire pair 2000/1000, Al/Mylar, Al side outside, w/shorting fold (pull tension) Impedance 120 +/- 10 % (at 1 MHz) Capacity between conductors 39.
5 Installation 5.2 Electrical installation ________________________________________________________________ Properties of the thin cable according to the DeviceNet specifications General properties Arrangement Two shielded, symmetrical cables, common axis with drain wire in the centre Overall shielding Coverage: 65 percent AWG 36, or at least 0.12 mm tinned copper braid (individually tinned) Drain wire At least copper 22; at least 19 cores (individually tinned) Outer diameter 6.096 mm (minimum) .
5 Installation 5.2 Electrical installation ________________________________________________________________ 5.2.4 Bus cable length The following bus cable lengths are possible depending on the baud rate and the cable type used (thick cable/thin cable): Baud rate [kbps] Bus cable lengths [m] Thick cable 125 500 250 250 500 100 Thin cable 100 If both thick and thin cables are used, the maximum cable lengths depending on the baud rate can be determined as follows: Baud rate [kbps] Max.
5 Installation 5.2 Electrical installation ________________________________________________________________ 5.2.5 Voltage supply The communication module is externally supplied with voltage at the 5-pole plug connector (X225) via the DeviceNet line. Note! Use a safely separated power supply unit (SELV/PELV) in accordance with EN 61800-5-1. • The communication module always requires an external voltage supply. • Communication with a standard device that is separated from the mains is not possible.
6 Commissioning 6.1 Before initial switch-on ________________________________________________________________ 6 Commissioning During commissioning, system-related data such as motor parameters, operating parameters, responses, and parameters for fieldbus communication are defined in the drive. For Lenze devices, this is done by means of codes. The codes of the drive and communication are saved non-volatilely as a data set in the memory module.
6 Commissioning 6.2 Configuring the host (PLC, scanner) ________________________________________________________________ 6.2 Configuring the host (PLC, scanner) For communication with the communication module, the host (PLC, scanner) must be configured first. Configuration for device control For the configuration of DeviceNet, the EDS file of the communication module has to be imported via the configuration software (e.g. »RSNetWorx« Rockwell software). The EDS file E94AYCDN_Vxxx.
6 Commissioning 6.3 Possible settings via DIP switch ________________________________________________________________ 6.3 Possible settings via DIP switch The following can be set via the DIP switch on the front: • Station address Range: MAC ID Switches: 1 ... 32 • Baud rate Range: Baud Switches: 1 and 2 Lenze setting: all switches OFF E94YCPM001D [6-1] 6.3.1 DIP switch Setting the station address (MAC ID) • The station address is set via the switches 1 ... 32 (MAC ID).
6 Commissioning 6.4 Initial switch-on ________________________________________________________________ 6.4 Initial switch-on Documentation for the standard device Note! Observe the safety instructions and information on residual hazards contained in this documentation. Establishing communication When the communication module is externally supplied, the standard device must also be switched on to establish communication.
7 Data transfer 7.1 Communication channels ________________________________________________________________ 7 Data transfer 7.1 Communication channels The Telegram types ( 35) are assigned to the communication channels according to their timecritical behaviour: The process data channel transmits I/O data. • The drive is controlled by means of the I/O data. • The host (PLC, scanner) can directly access the I/O data. In the PLC, the data are, for instance, directly stored in the I/O area.
7 Data transfer 7.2 Telegram types ________________________________________________________________ 7.2 Telegram types The "I/O data" (process data) and "Explicit Messages (parameter data) telegram types are transmitted between the host (PLC, scanner) and the drives (devices). 7.2.1 I/O data (process data) I/O data are transmitted or received according to the producer/consumer principle. There is one transmitter and no receiver or an optional number of receivers.
7 Data transfer 7.3 Configuring I/O data (PDO mapping) ________________________________________________________________ 7.3 Configuring I/O data (PDO mapping) For Servo Drives 9400 HighLine, the I/O data can be arranged individually (mapping). For this purpose, the »Engineer« provides a port configurator.
7 Data transfer 7.3 Configuring I/O data (PDO mapping) ________________________________________________________________ 3. Click the Edit PDO button. The selection window Process data object structure: PDO_RX0 will open: Here you can transfer the individual ports from the Port Selection list to the "PDO_RX0" receive PDO by clicking the >> button. The Up and Down buttons serve to shift the sequence of the ports within the PDOs.
7 Data transfer 7.3 Configuring I/O data (PDO mapping) ________________________________________________________________ The following example shows the mapping of the ports "LPortControl1" and "Lport32In1" into the reception PDO "PDO_RX0" and the mapping of the ports "LPortStatus1" and "LPort32Out1" into the transmission PDO "PDO_TX0": 4. Confirm the selection with OK. 5. Repeat the steps 2. to 4. for the transmit object PDO_TX0. 6.
8 Monitoring 8.1 Interruption of the DeviceNet communication ________________________________________________________________ 8 Monitoring 8.1 Interruption of the DeviceNet communication An interruption of the DeviceNet communication, e.g. by a cable break or a failure of the host (PLC, scanner), is detected by the communication module.
8 Monitoring 8.2 Fault with regard to internal communication ________________________________________________________________ 8.2 Fault with regard to internal communication The response to a communication error between the communication module and the standard device can be set via these codes: • C01501 (module in slot MXI1) • C01502 (module in slot MXI2). 40 Lenze · E94AYCDN communication module (DeviceNet™) · Communication Manual · DMS 5.
9 Diagnostics 9.1 LED status displays ________________________________________________________________ 9 Diagnostics The LEDs on the front of the communication module are provided for the purpose of fault diagnostics. Furthermore, you can query the current module status (C13861 / C14861) and the current network status (C13862 / C14862) via codes. 9.1 LED status displays LED status display Pos.
9 Diagnostics 9.2 Polling the current module status ________________________________________________________________ 9.2 Polling the current module status C13861 / C14861 shows the current module status of the DeviceNet node: 9.3 Value C13861/C14861 Module status Description 0 Nonexistent No online value available (communication module is offline). 1 Device Self Test The communication module is currently undergoing a self-test.
10 Error messages 10.1 Short overview of the DeviceNet error messages ________________________________________________________________ 10 Error messages This chapter supplements the error list in the reference manual and the »Engineer« online help for the Servo Drive 9400 by the error messages of the communication module. 10.1 Reference manual/»Engineer« online help for the Servo Drive 9400 Here you will find general information on diagnostics & fault analysis and on error messages.
10 Error messages 10.2 Possible causes and remedies ________________________________________________________________ 10.2 Possible causes and remedies This chapter lists all DeviceNet error messages in the numerical order of the error numbers. Possible causes and remedies as well as responses to the error messages are described in detail.
10 Error messages 10.2 Possible causes and remedies ________________________________________________________________ DeviceNet: Internal mapping error [0x00c86110] Response (Lenze setting printed in bold) Setting: not possible None System error Error Fault Quick stop by trouble Warning locked Warning Information Cause Remedy More than 64 bytes have been mapped Carry out Configuring I/O data (PDO mapping) ( 36) again.
10 Error messages 10.2 Possible causes and remedies ________________________________________________________________ DeviceNet: Communication error [0x00c88121] Response (Lenze setting printed in bold) Setting: C13880/3 / C14880/3 ( Adjustable response) None System fault Fault Trouble Quick stop by trouble Warning locked Warning Information Cause Remedy A communication error occurred Check cables and terminals.
10 Error messages 10.3 DeviceNet error messages ________________________________________________________________ 10.3 DeviceNet error messages Code [hex] Error designation Description 0x00 SUCCESS No fault 0x02 RESOURCE UNAVAILABLE Resource required to perform the service not available. 0x03 INVALID PARAM VALUE Invalid parameter value 0x08 SERVICE NOT SUPP Service is not supported. 0x09 INVALID ATTRIB VALUE Invalid attribute.
11 Parameter reference 11.1 Communication-relevant parameters of the standard device ________________________________________________________________ 11 Parameter reference This chapter supplements the parameter list and the table of attributes contained in the reference manual and in the »Engineer« online help for the Servo Drive 9400 with the parameters of the E94AYCDN (DeviceNet) communication module. 11.
11 Parameter reference 11.1 Communication-relevant parameters of the standard device ________________________________________________________________ C00637 Parameter | Name: C00637 | Resp. to new module in MXI2 Data type: UNSIGNED_32 Index: 23939 = 0x5D83 Response for the case where a new module has been plugged into slot 2 of the standard device.
11 Parameter reference 11.2 Parameters of the communication module for the MXI1 slot ________________________________________________________________ 11.2 Parameters of the communication module for the MXI1 slot In this chapter the parameters of the E94AYCDN communication module (DeviceNet) for slot MXI1 of the Servo Drive 9400 are listed in numerically ascending order. C13231 Parameter | Name: Data type: UNSIGNED_64 Index: 11344 = 0x2C50 C13231 | Service code This code is ...
11 Parameter reference 11.2 Parameters of the communication module for the MXI1 slot ________________________________________________________________ C13789 Parameter | Name: Data type: UNSIGNED_8 Index: 10786 = 0x2A22 C13789 | Service code This code is ... • used device-internally and may not be written by the user. • only displayed from »Engineer« version 2.9. Setting range (min. value | unit | max.
11 Parameter reference 11.2 Parameters of the communication module for the MXI1 slot ________________________________________________________________ C13852 Parameter | Name: Data type: UNSIGNED_16 Index: 10723 = 0x29E3 C13852 | All words to the basic device Display of the process data words 1 to 32 that are transferred from the communication module to the standard device. In the subcodes 1 to 32, all process data words from the communication module are displayed. Display area (min.
11 Parameter reference 11.2 Parameters of the communication module for the MXI1 slot ________________________________________________________________ C13855 Parameter | Name: Data type: UNSIGNED_8 Index: 10720 = 0x29E0 C13855 | Length of ports mapped into send PDO Display of the total data length (in bytes) of the ports that have been mapped into the send PDO. Display area (min. value | unit | max.
11 Parameter reference 11.2 Parameters of the communication module for the MXI1 slot ________________________________________________________________ C13863 Parameter | Name: Data type: UNSIGNED_8 Index: 10712 = 0x29D8 C13863 | Baud rate Display of the baud rate Selection list (read only) 0 125.00 kbps 1 250.00 kbps 2 500.
11 Parameter reference 11.2 Parameters of the communication module for the MXI1 slot ________________________________________________________________ C13883 Parameter | Name: Data type: UNSIGNED_8 Index: 10692 = 0x29C4 C13883 | Data length of consumed I/O data Setting of the data length (in bytes) of the I/O data received by the device via DeviceNet. Note: • If the data length is changed, the DeviceNet scanner will be informed about this change (consumed data size).
11 Parameter reference 11.2 Parameters of the communication module for the MXI1 slot ________________________________________________________________ C13901 Parameter | Name: Data type: VISIBLE_STRING Index: 10674 = 0x29B2 C13901 | Firmware: Compilation date Display of the firmware compilation date (string with a length of 20 bytes) The date ("MMM DD YYYY") and time ("hh:mm:ss") will be provided, e.g. "Mar 21 2005 12:31:21".
11 Parameter reference 11.3 Parameters of the communication module for the MXI2 slot ________________________________________________________________ 11.3 Parameters of the communication module for the MXI2 slot In this chapter the parameters of the E94AYCDN communication module (DeviceNet) for slot MXI2 of the Servo Drive 9400 are listed in numerically ascending order. C14231 Parameter | Name: Data type: UNSIGNED_64 Index: 10344 = 0x2868 C14231 | Service code This code is ...
11 Parameter reference 11.3 Parameters of the communication module for the MXI2 slot ________________________________________________________________ C14789 Parameter | Name: Data type: UNSIGNED_8 Index: 9786 = 0x263A C14789 | Service code This code is ... • used device-internally and may not be written by the user. • only displayed from »Engineer« version 2.9. Setting range (min. value | unit | max.
11 Parameter reference 11.3 Parameters of the communication module for the MXI2 slot ________________________________________________________________ C14852 Parameter | Name: Data type: UNSIGNED_16 Index: 9723 = 0x25FB C14852 | All words to standard device Display of the process data words 1 to 32 that are transferred from the communication module to the standard device. In the subcodes 1 to 32, all process data words from the communication module are displayed. Display area (min. value | unit | max.
11 Parameter reference 11.3 Parameters of the communication module for the MXI2 slot ________________________________________________________________ C14861 Parameter | Name: Data type: UNSIGNED_16 Index: 9714 = 0x25F2 C14861 | Module state Display of the current module state Selection list (read only) Info 0 Nonexistent No online value available (communication module is offline). 1 Device Self Test The communication module is currently undergoing a self-test.
11 Parameter reference 11.3 Parameters of the communication module for the MXI2 slot ________________________________________________________________ C14864 Parameter | Name: Data type: UNSIGNED_8 Index: 9711 = 0x25EF C14864 | Active MAC ID Display of the active MAC ID Display area (min. value | unit | max.
11 Parameter reference 11.3 Parameters of the communication module for the MXI2 slot ________________________________________________________________ C14884 Parameter | Name: Data type: UNSIGNED_8 Index: 9691 = 0x25DB C14884 | Data length of produced I/O data Setting of the data length (in bytes) of the I/O data to be transmitted by the device via DeviceNet. Note: • If the data length is changed, the DeviceNet scanner will be informed about this change (produced data size).
11 Parameter reference 11.3 Parameters of the communication module for the MXI2 slot ________________________________________________________________ C14920 Parameter | Name: Data type: UNSIGNED_8 Index: 9655 = 0x25B7 C14920 | Display: DIP switch position Display of the current DIP switch position • The value displayed corresponds to the sum of the DIP switch values (MAC ID: 1 ... 32, baud: 1 and 2). • The active MAC ID is displayed in C14864. • The active baud rate is displayed in C14863.
11 Parameter reference 11.4 Table of attributes ________________________________________________________________ 11.4 Table of attributes The table of attributes contains information required for communicating with the drive via parameters. How to read the table of attributes: Column Meaning Code Parameter name Cxxxxx Name Parameter short text (display text) Text hex Index under which the parameter is addressed. The subindex for array variables corresponds to the Lenze subcode number.
11 Parameter reference 11.
12 Implemented DeviceNet objects ________________________________________________________________ 12 Implemented DeviceNet objects A DeviceNet node can be seen as an accumulation of objects. An individual object is characterised by its class, its instances and attributes. Several services such as read and write services can be applied to these objects.
12 Implemented DeviceNet objects 12.1 Identity Class (0x01 / 1) ________________________________________________________________ 12.1 Identity Class (0x01 / 1) This object contains some information regarding the identification and general information relating to the device.
12 Implemented DeviceNet objects 12.2 DeviceNet Class (0x03 / 3) ________________________________________________________________ 12.2 DeviceNet Class (0x03 / 3) This object contains some information relating to the DeviceNet communication. Instance 0 Attribute Service(s) Designation Data type Value 1 GET Revision UINT 2 (0x02) Attribute Service(s) Designation Data type Value 1 GET MAC ID USINT 0 ... 63 (0x0 ... 0x3F) 2 GET Baud rate USINT 0 ... 2 (0x0 ...
12 Implemented DeviceNet objects 12.3 Assembly Class (0x04 / 4) ________________________________________________________________ 12.3 Assembly Class (0x04 / 4) This object contains some information relating to input and output data of the scanner. Instance 768 ...
12 Implemented DeviceNet objects 12.4 Connection Class (0x05 / 5) ________________________________________________________________ 12.
12 Implemented DeviceNet objects 12.
12 Implemented DeviceNet objects 12.
12 Implemented DeviceNet objects 12.5 Acknowledge Handler Class (0x2B / 43) ________________________________________________________________ 12.5 Acknowledge Handler Class (0x2B / 43) This object contains some information relating to feedbacks/confirmations: Instance 1 Attribute Service(s) Designation Data type Value 1 1) GET / SET Acknowledge Timer UINT 1 ... 65534 ms (0x0001 ...
12 Implemented DeviceNet objects 12.6 Lenze Class (0x65 / 101) ________________________________________________________________ 12.6 Lenze Class (0x65 / 101) This object contains some information regarding responses to communication faults.
12 Implemented DeviceNet objects 12.7 Lenze Class (0x66 / 102) ________________________________________________________________ 12.7 Lenze Class (0x66 / 102) This object contains some information relating to data lengths of the I/O data consumed and produced.
12 Implemented DeviceNet objects 12.8 Lenze Class (0x67 / 103) ________________________________________________________________ 12.8 Lenze Class (0x67 / 103) This object contains some information relating to the I/O image of the data produced (process input data of the scanner).
12 Implemented DeviceNet objects 12.9 Lenze Class (0x68 / 104) ________________________________________________________________ 12.9 Lenze Class (0x68 / 104) This object contains some information relating to the I/O image of the data consumed (process output data of the scanner).
12 Implemented DeviceNet objects 12.10 Lenze Class (0x6E / 110) ________________________________________________________________ 12.10 Lenze Class (0x6E / 110) This object contains some information regarding the access to Lenze codes.
12 Implemented DeviceNet objects 12.11 Examples for reading/writing with the »Class Instance Editor« ________________________________________________________________ 12.11 Examples for reading/writing with the »Class Instance Editor« The »Class Instance Editor« is a function of the Rockwell software »RSNetWorx«. 12.11.1 Writing integer codes The maximum speed (nmax) is to be set to 4500 rpm using code C00011. Enter the following in the input fields of the »Class Instance Editor« (fig.
12 Implemented DeviceNet objects 12.11 Examples for reading/writing with the »Class Instance Editor« ________________________________________________________________ 12.11.2 Reading integer codes The maximum speed (nmax) is to be read from code C0011. Enter the following in the input fields of the »Class Instance Editor« (fig.
12 Implemented DeviceNet objects 12.11 Examples for reading/writing with the »Class Instance Editor« ________________________________________________________________ 12.11.3 Writing codes with two decimal positions The current controller reset time is to be set to 6.50 ms using code C00076. Enter the following in the input fields of the »Class Instance Editor« (fig.
12 Implemented DeviceNet objects 12.11 Examples for reading/writing with the »Class Instance Editor« ________________________________________________________________ 12.11.4 Reading codes with two decimal positions The current controller reset time is to be read from code C00076. Enter the following in the input fields of the »Class Instance Editor« (fig.
13 DIP switch positions for setting the station address ________________________________________________________________ 13 DIP switch positions for setting the station address The station address results from the sum of the binary values of switches 1 ... 32. The following table shows the switch positions for the valid address range 0 ... 63.
13 DIP switch positions for setting the station address ________________________________________________________________ Station address (MAC ID DIP switch 32 16 8 4 2 1 39 ON OFF OFF ON ON ON 40 ON OFF ON OFF OFF OFF 41 ON OFF ON OFF OFF ON 42 ON OFF ON OFF ON OFF 43 ON OFF ON OFF ON ON 44 ON OFF ON ON OFF OFF 45 ON OFF ON ON OFF ON 46 ON OFF ON ON ON OFF 47 ON OFF ON ON ON ON 48 ON ON OFF OFF OFF OFF 49 ON ON OFF OFF OFF
Index ________________________________________________________________ A Acknowledge Handler Class (0x2B / 43) 73 Activating changed setting 33 Active MAC ID (C13864) 54 Active MAC ID (C14864) 61 All words from scanner (C13851) 51 All words from scanner (C14851) 58 All words from standard device (C14853) 59 All words to scanner (C13850) 51 All words to scanner (C14850) 58 All words to standard device (C14852) 59 All words to the basic device (C13852) 52 All words to the basic device (C13853) 52 Application
Index ________________________________________________________________ D E Data length of consumed I/O data (C13883) 55 Data length of produced I/O data (C13884) 55 Data length of produced I/O data (C14884) 62 Data transfer 34 Delete process data (C13885) 55 Delete process data (C14885) 62 Device and application-specific safety instructions 11 Device Heartbeat Message 35 Device protection 11 Device type 15 DeviceNet Communication error (error message) 46 Consumed I/O data length is contradictory (error m
Index ________________________________________________________________ L R Layout of the safety instructions 9 LED status displays 41 Length of consumed I/O data (C14883) 61 Length of ports mapped into receive PDO (C13854) 52 Length of ports mapped into receive PDO (C14854) 59 Length of ports mapped into send PDO (C13855) 53 Length of ports mapped into send PDO (C14855) 59 Lenze Class (0x65 / 101) 74 Lenze Class (0x66 / 102) 75 Lenze Class (0x67 / 103) 76 Lenze Class (0x68 / 104) 77 Lenze Class (0x6E / 1
)(('%$&. 88 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 have suggestions for improvement, please e-mail us to: feedback-docu@lenze.com Thank you very much for your support.
E94AYCDN communication module (DeviceNet™) · Communication Manual · EDS94AYCDN · 13451097 · DMS 5.0 EN · 02/2014 · TD17 Lenze Automation GmbH Postfach 10 13 52, D-31763 Hameln Hans-Lenze-Straße 1, D-31855 Aerzen Germany +49 5154 82-0 +49 5154 82-2800 lenze@lenze.com www.lenze.com Service Lenze Service GmbH Breslauer Straße 3, D-32699 Extertal Germany 008000 24 46877 (24 h helpline) +49 5154 82-1112 service@lenze.
