Manual DeviceNet DFD11A Fieldbus interface
Contents
1. Time ModNet LED PIO LED BIO LED BUSOFF LED 0 Green Off Off Off 250 ms Red Off Off Off 500 ms Off Green Off Off 750 ms Off Red Off Off 1000 ms Off Off Green Off 1250 ms Off Off Red Off 1500 ms Off Off Off Green 1750 ms Off Off Off Red 2000 ms Off Off Off Off Table 4 Power up LED test c N The power up test is always performed unless the fieldbus is powered with 24 V EURODE 8 MOVIDRIVE DeviceNet DFD11A 2 7 2 ModNet LED Installation The range of functions of the ModNet LED module network status LED is defined in the DeviceNet specification Its range of functions is described in Table 5 Status LED Message Not switched on Off Unit is in off line status off line Unit is performing DUP MAC check e Unit is switched off On line and in Flashes green The unit is on line and no connection has been set up operational mode 1 s cycle DUP MAC check was performed successfully Noconnection has yet been established with a master e No configuration wrong configuration or configuration not complete On line operational Green On line mode and connected Connection has been established with a master Connection is active established state Minor fault or Flashes red Acorrectable error has occurred connection timeout 1 s cycle Polled 1 0 or and bit strobe 1 0 connections are2. 2 7 4 BIO LED The BIO LED checks the bit strobe 1 0 connection Its range of functions is described in Table 7 Status LED Message DUP MAC check Flashes green Unitis performing the DUP MAC check 125 ms cycle Not switched on Off Unitis in off line status off line but not DUP Unit is switched off MAC check On line and in opera Flashes green The unit is on line tional mode 1 s cycle e DUP MAC check was performed successfully ABIO connection is being established with a master configuring state configuration wrong configuration or configuration not complete On line operational Green On line mode and connected ABIO connection has been established established state Minor fault or connec Flashes red Acorrectable error has occurred tion timeout 1 s cycle Bit strobe 1 0 connection is in timeout state Critical fault or critical Red Anon correctable error has occurred link failure BusOff DUP MAC check has detected an error Table 7 Status table of the BIO LED 2 7 5 BUSOFF LED The BUSOFF LED displays the physical status of the bus node Its range of functions is described in Table 8 Status LED Message NO ERROR Off The number of bus errors is in the normal range error active state Flashes red je The unit is performing a DUP MAC check and cannot send 125 ms any messages because no other participants are connected to BUS WARNING cycle the bu
3. MOVIDRIVE Drive Inverters DeviceNet DFD11A Fieldbus Interface Manual Edition 11 98 SPCR OP ERR Re ee Ree eee III 0919 6714 1198 Important Notes Important Notes J J EU 2 a V V ODRIUE Read this manual carefully before you start the installation and startup of MOVIDRIVE drive inverters with the DFD11A DeviceNet option This manual assumes that the user has access to and is familiar with the documentation on the MOVIDRIVES system in particular the MOVIDRIVES system manual Safety notes Always follow the safety and warning instructions contained in this manual Safety notes are marked as follows Electrical hazard e g when working on live wires Mechanical hazard e g when working on hoists Important instructions for safe and fault free operation of the driven machine system e g pre setting before startup General safety notes on bus systems This communication system allows you to match the MOVIDRIVE drive inverter to the spe cifics of your application to a very high degree As with all bus systems there is a danger of invisible external as far as the inverter is concerned modifications to the parameters which give rise to changes in the inverter s behavior This may result in unexpected not uncon trolled though system behavior pP Each unit is manufactured and tested to current SEW EURODRIVE technical standards and specification
4. 21 e J J same Application with P C Type SLC500 4 1 Exchange of polled 1 0 process data START gt Cycle 0 Speed 1000 rpm Enable Objective In the following program process data are to be sent to MOVIDRIVE and the motor should run at a different speed Cycle 1 Speed 0 rpm Rapid stop The program sequence is shown in Fig 11 Cycle 2 Speed 400 rpm Enable Cycle 3 Speed 0 rpm Rapid stop Fig 11 Program sequence 01911AEN The program requires that the parameters listed in Table 19 must be set in the drive inverter Menu no Index Parameters Value 100 8461 Setpoint source Fieldbus 101 8462 Control signal source Fieldbus 870 8304 Process output data description 1 Control word 1 871 8305 Process output data description 2 Speed 872 8306 Process output data description 3 No function 873 8307 Process input data description 1 Status word 1 874 8308 Process input data description 2 Speed 875 8309 Process input data description 3 No function 876 8622 PO data enable YES Table 19 Setting the parameters for process data exchange The MOVIDRIVE drive inverter is now in fieldbus mode and can receive process data The program can now be written for the SLC500 28 MOVIDRIVE Dev
5. Project Planning and Startup Return codes for parameter setting SEW specific return codes The return codes which the inverter sends back in the event of faulty parameter setting are described in the manual for the fieldbus device profile and therefore do not form part of this docu mentation However the return codes are sent back in a different format in conjunction with DeviceNet Byte offset Function General error Code Table 17 Data format for the parameter response message The service code of an error message is always 94h hex The general error code of an inverter specific return code is always 7Fh proprietary error The additional code is identical to the additional code low described in the manual for the fieldbus device profile The example shows the proprietary error 70h Impermissible parameter index Return codes from DeviceNet DeviceNet specific return codes are sent in the error message if the data format is not maintained during transmission or if a service is performed which has not been implemented The coding of these return codes is described in the DeviceNet specification See appendix Timeout of explicit messages The timeout response is triggered by the DeviceNet option card The timeout interval must be set by the master after the connection has been established The DeviceNet specification refers to an expected packet rate rather than a timeout interval The expected packet r
6. Datenwort High HEX Wort 232 Explicit Message Body 01919AEN Fig 14 SEW parameter channel The data message which is to be sent is in N7 0 to N7 8 and N7 10 to N7 15 contain the data which have been received 02149AXX Fig 15 N file 7 NAV SURO MOVIDRIVE DeviceNet DFD11A 33 sam le Application with PLC SLC500 Request Response Function Value Function Value TXID 1 TXID 1 cmd 1 Start Status 1 Successful Connection 0 Connection 0 Size 8 Size 6 Service Eh Read request Service 8Eh Read response MAC_ID 8 MACID 8 Class 7 Data 1 2070h Instance 1 Data 2 9h Attribute 4 Data 3 0 Data 1 2070h Table 23b Data 2 Oh Data 3 0 Table 23a The SEW parameter data channel can be addressed via class 7 instances 1 8 and attribute 4 see statement of conformance In rung 5 the 9 bytes starting from N7 0 are copied into the MO file with a rising edge of bit B3 0 1 This process starts the reading of parameter 8304 2070h followed by the program waiting for the rising edge of the scanner status bit 1 3 0 15 in rung 6 This bit indicates that the data are present and request bit B3 0 1 can then be reset The received data still have to be written into the N file To this end 9 words of the M1 file N7 10 19 are written B3 0 1 B3 0 14 0005 L OSR J B3 0 1 130 15 B3 0 1
7. Set to indicate that attribute value is written to by the use of Set Attribute Single service 8 d ko MOVIDRIVE DeviceNet DFD11A a Device Net Statement of Conformance DeviceNet Required Object mplementation Object Class Attributes Open None Supported Services None Supported Object Instance Attributes Open None Supported Services None Supported MOVIDRIVE DeviceNet DFD11A Parameter Object ID Description 1 Revision 2 Max instance 8 Parameter class descriptor 9 Configuration assembly instance 10 Native language DeviceNet Services Get Attributes All Reset Get Attribute Single Set Attribute Single Restore Save 3 m Description Parameter value Link Path size Link path Descriptor Data ty pe Data size Parameter name string Units string Help string Minimum value md Maximum value 12 Default value 13 Scaling multiplier 14 Scaling divisor 15 Scaling base 16 4 Scaling offset 17 Multiplier link 18 link 19 Base link 20 Offset link 21 Decimal precision DeviceNet Services Attribute_All Get Attribute_Single Set Value OOO X O O Parameter Options Get Set Value z 164 25 4 IL H H H 194 Parameter Options Appendix m Appendix 6 3 Definiti
8. sew sew eurodrive com
9. the bit strobe connection is not in timeout status The inverter sends three process input data words to the PLC these are stored in input data words 1 3 10 to 1 3 12 in the input file IMPORTANT The set process data length determines the process data length of both the bit strobe 1 0 and the polled 1 0 messages i e the settings for the process data length of both the polled 1 0 and the bit strobe 1 0 always have to be identical in the control Timeout response with bit strobe 1 0 The timeout response is triggered by the DeviceNet option card The timeout interval must be set by the master after the connection has been established The DeviceNet specification refers to an expected packet rate rather than a timeout interval The expected packet rate is calculated on the basis of the timeout interval using the following formula Lrimeout Interval BitStrobelO 4 lExpected Packet Rate BitStrobelO It can be set using connection object class 5 instance 3 attribute 9 The range of values runs from 0 ms to 65535 ms in 5 ms steps If a timeout occurs for the bit strobe 1 0 messages this connection type enters timeout status Incoming bit strobe 1 0 messages no longer accepted The timeout response is not transmitted to the inverter MOVIDRIVE DeviceNet DFD11A V V A SOR 19 Project Planning and Startup The timeout response can be reset with DeviceNet using the reset ser
10. 26 ID 25 ID 24 4 ID 39 ID 38 ID 37 ID 36 ID 35 ID 34 ID 33 ID 32 5 ID 47 ID 46 ID 45 ID 44 ID 43 ID 42 ID 41 ID 40 6 ID 55 ID 54 ID 53 ID 52 ID 51 ID 50 ID 49 ID 48 7 ID 63 ID 62 ID 61 ID 60 ID 59 ID 58 ID 57 ID 56 Table 10 MAC ID assignment in the bit strobe I O message request fa J N Z 18 MOVIDRIVE DeviceNet DFD11A Project Planning and Startup Each participant which has received this bit strobe I O message responds with its current process input data The length of the process input data corresponds to the process data length for the polled 1 0 connection It can also be set using the DeviceNet PD Configuration parameter PLC Address range Output file purre Station 0 310 Address 0 3 11 1 Bit 16 MAC ID 16 0 3 12 0 3 13 y N 1 Input file LU PD1 PD2 Bio LS PPI ppo E3 11 1342 02123AEN Fig 7 Bit strobe 1 0 messages In the example above the bit strobe 1 0 message is stored in memory words 0 3 10 to 0 3 13 and Bit 16 is assigned to the device with station address 16 This bit corresponds to bit 0 of output data word 0 3 11 in the PLC Since this bit was set to the value 1 a fieldbus timeout is triggered in the inverter with station address 16 However the BIO LED remains continuously green to indicate that
11. Reference X13 0100 05 DCOM 24V V024 Reference potential binary signals DNDG RS 485 4 ST11 RS 485 ST12 X10 TF input TF1 Reference potential binary signals DGND Brake gt 0800 0001 D001 NO Relay contact Relay NO Relay NC 0001 Fault 0002 24V gt V024 Use this jumper to enable the drive inverter via the terminals 24V external 24V external lt 124 Reference potential binary signals DGND 2 Control mode FIELDBUS 01267AEN Use parameters P100 and P101 to switch control and setpoint processing of the servo inverter to FIELDBUS P100 Setpoint source FIELDBUS P101 Control signal source FIELDBUS 3 Input terminal 0101 NO FUNCTION Input terminal 0102 NO FUNCTION Input terminal 0103 NO FUNCTION Input terminal 0104 NO FUNCTION Input terminal 0105 NO FUNCTION Program the function of input terminals 0101 to 0105 to NO FUNCTION with parameters P600 to P604 P600 Binary input 0101 NO FUNCTION P601 Binary input DI02 NO FUNCTION P602 Binary input DI03 NO FUNCTION P603 Binary input DI04 NO FUNCTION P604 Binary input DI05 NO FUNCTION umma n X V A V AL V 12
12. data from device 11 I 3 002 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Process data from device 11 I 3 003 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Process data from device 10 I 3 004 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Process data from device 10 1 3 005 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PEDI device 8 polled IO I 3 006 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PED2 device 8 polled IO 1 3 007 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PED3 device 8 polled IO I 3 008 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PEDI device 8 bit strobe IO I 3 009 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PED2 device 8 bit strobe IO I 3 010 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PED3 device 8 bit strobe IO 1 3 011 00 00 00 OO OO OO OO OO OO OO 00 OO OO OO OO OO PEDI device 0 polled IO I 3 012 00 00 OO 00 00 OO OO OO OO OO OO OO OO 00 OO OO PED2 device 0 polled IO I 3 013 00 00 00 00 00 OO OO OO OO OO OO OO OO 00 00 OO PED3 device 0 polled IO I 3 014 00 00 00 00 00 00 OO OO OO OO OO OO 00 00 00 00 PED1 device 0 bit strobe IO I 3 015 00 00 OO 00 00 OO OO OO OO OO OO 00 00 00 OO PED2 device 0 bit strobe IO I 3 016 00 00 00 00 OO OO OO OO OO OO OO OO OO OO 00 OO PED3 device 0 bit strobe IO I 3 017 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PED1 device 4 polled IO I 3 018 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PED2 device 4 polled IO I 3 019 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PED3 de
13. in timeout status Acorrectable error has occurred in the unit Critical fault or Red Anon correctable error has occurred critical link failure BusOff DUP MAC check has detected an error Table 5 Status table of the ModNet LED 2 7 3 PIO LED The LED checks the polled 1 0 connection process data channel Its range of functions is described in Table 6 Status LED Message DUP MAC check Flashes green 125 ms cycle Unit is performing the DUP MAC check Not switched on off line but not DUP Off Unit is in off line status Unit is switched off MAC check On line and in Flashes green The unit is on line operational mode 1 s cycle DUP MAC check was performed successfully APIO connection is being established with a master configuring status e No configuration wrong configuration or configuration not complete On line operational Green On line mode and connected APIO connection has been established established status Minor fault or Flashes red Acorrectable error has occurred connection timeout 1 s cycle Polled 1 0 connection is in timeout status Critical fault or Red Anon correctable error has occurred critical link failure BusOff DUP MAC check has detected an error Table 6 Status table of the PIO LED MOVIDRIVE DeviceNet DFD11A V V 9 Installation Ced d
14. packet rate is calculated on the basis of the timeout interval using the following formula Timeout_Inverter Lrimeout Interval PolledlO 4 lexpected_Packet_Rate_PollediC The expected packet rate can be set using the connection object class 5 instance 2 attribute 9 The range of values runs from 0 ms to 65535 ms in 5 ms Steps The expected packet rate for the polled 1 0 connection is converted into the timeout interval and displayed in the device and the timeout interval in parameter P819 This timeout interval is retained in the device whenever the polled 1 0 connection is dropped and the device switches to timeout status after the timeout interval has elapsed The timeout interval must not be altered in the inverter using MX_SHELL or the DBG because it can only be activated via the bus F V i V DRIVE 2 Vni MOVIDRIVE DeviceNet DFD11A 17 Project Planning and Startup If a timeout occurs for the polled 1 0 messages this connection type enters timeout status Incom ing polled messages are no longer accepted The timeout response triggers timeout reaction set in the inverter The timeout response can be reset with DeviceNet by using the reset service of the connection object class 0x05 instance 0x02 undetermined attribute by dropping the connection by using the reset service of the identity object class 0x01 instance 0x01 undetermined attribute or with the reset bit i
15. the device profile It is independent of any particular fieldbus and is therefore a uniform feature This provides you the user with the opportunity of developing applications irrespective of the fieldbus As a result it is very easy to change over to other bus systems such as INTERBUS DFI11A option PROFIBUS DFP11A option or CAN bus DFC11A MOVIDRIVE offers you direct access to all drive parameters and functions via the DeviceNet inter face The drive inverter is controlled via the high speed cyclical process data Via this process data channel you can enter setpoints such as the setpoint speed ramp generator time for acceleration deceleration etc as well as triggering various drive functions such as enable control inhibit nor mal stop rapid stop etc However at the same time you can also use this channel to read back actual values from the drive inverter such as the actual speed current device status fault number and also reference signals The parameters of the inverter are set exclusively by using Explicit Messages whereas the process data exchange is replicated on the DeviceNet services of Polled 1 0 or Bit Strobe 1 0 This parame ter data exchange enables you to implement applications in which all the important drive parame ters are stored in the master programmable controller so that there is no need for manual parameter settings on the drive inverter itself MOVIDRIVE DeviceNet DFD11A Introduction Every Devic
16. time out action Produced connection path length Produced connection path 15 Consumed connection path length N DO C S a c N 16 Consumed connection path 17 Production inhibit ime DeviceNet Services Reset Delete Apply Attributes Get Attribute Single Set Attribute Single BEREE If yes fill out the Vendor Specific Additions form on page F 7 Set Value Limits Ou Parameter Options Peer to Peer Connections Max Instances Total Client Total Client LI Explicit Message L Sever Dynamic 1 0 L Server C App tig C Client Ll 27 Get Set Value Limits L 3p 2 LI x 20 65830 1 O U arameter Options No Ye X Get p indicate that atribute value is returned by the use of Get Attribute Single service Set to indicate that attribute value is written to by the use of Set Attribute Single service MOVIDRIVE DeviceNet DFD11A Ka 9 Appendix a Device Net Statement of Conformance DeviceNet Connection Obiect 0x05 Required Object Class ID Description Get Set Value Limits Object Attributes Open 1 Revision LI Lj Implementation None Supported DeviceNet Services Parameter Options Services L Ree C X None Supported baee Attribute Single Find Next Object Instance Object Instance Predefined M S Connections Peer to Pee
17. write service etc Set Attribute Single Write service for a parameter SLC500 Allen Bradley PLC Table 25 Definitions of terminology 46 MOVIDRIVE DeviceNet DFD11A 7 Index B Bit strobe I O 18 Bus termination 7 D Definitions of terminology 46 DeviceNet network setting up 13 DIP switches Setting 8 Display elements 8 BIOLED 10 BUSOFFLED 10 ModNet LED 9 PIOLED 9 Power up 8 E EDS file 13 Equipotential bonding 7 Example 26 Bit strobe I O 30 Explicit messages parametric data 31 Polled 1 0 process data 28 G General error codes 36 Installation 6 Bus cables 7 Inverter control mode fieldbus 11 P Pin assignment 6 Polled 1 0 14 Process data exchange 14 Project planning 11 Project planning for x process data words 15 S Startup 11 Statement of conformance 37 Supported unit types 6 T Timeout of explicit messages 25 Timeout response with bit strobe I O 19 Timeout response with polled 1 0 17 UIO DRIVE MOVIDRIVE DeviceNet DFD11A 47 We are available wherever you need us Worldwide SEW EURODRIVE right around the globe is transmission with manufacturing and assem your competent partner in matters of power bly plants in most major industrial countries EURODRIVE SEW EURODRIVE GmbH amp Co P O Box 30 23 D 76642 Bruchsal Germany Tel 49 7251 75 0 Fax 49 7251 75 19 70 Telex 7 822 391 http www SEW EURODRIVE com
18. 0006 k lt u gt 1747 SDN B3 0 1 0007 E 0008 CEND gt 01921AEN s VE MOVIDRIVE DeviceNet DFD11A Technical Data m 5 Technical Data Part no 822 903 1 Number of process data words 1 20r3 process data words can be selected using parameter P877 DeviceNet PD Configuration Baud rate e 125 250 or 500 kbaud can be selected via DIP switch Transmission level e 8501198 24V MAC ID 0 63 can be selected via DIP switch Number of station max 64 Supported services e Polled 1 0 1 3 words Bit Strobe 1 0 1 3 words e Explicit messages Get Attribute Single Set Attribute Single Reset Allocate 5 Connection Set Release 5 Connection Set Supported objects Identity object class Message router class DeviceNet object class Connection object class Register object class Parameter object class Communication protocol Master slave connection set acc to DeviceNet specification version 2 0 Connection system 2 wire bus and 2 wire supply voltage 24 VDC with 5 pole Phoenix terminal Pin assignment acc to DeviceNet specification Bus lengths 500 m at 125 kbaud 250 m at 250 kbaud 100 m at 500 kbaud for thick cable according to DeviceNet specification 2 0 Appendix B V _ TORODRNE D N LJ ra MOVIDRIVE DeviceNet DFD11A 35 m Appendix 6 Appendix 6 1 General error c
19. 255 During creation or downloading of a request to the scanner the contact plan program of the SLC5 processor assigns a TXID to the transmis sion Size 1 2 word 3 29 Size of the explicit message body in bytes Connection word 0 DeviceNet connection 0 Service Y word OEh Get_Attribut_Single Read 10h Set_Attribut_Single Write 05h Reset etc See DeviceNet specification for more services Explicit message body Class 1 word 0 255 DeviceNet class Instance 1 word 0 255 DeviceNet instance Attribute 1 word 0 255 DeviceNet attribute Data 0 26 words 0 65535 Data content Table 21 Coding of the memory area within the M file Command code cmd Description 0 Ignore transmssion block 1 Execute transmission block 2 Receive transmission status 3 Reset all client server transmissions 4 Delete transmission from idle loop 5 255 Reserved Network node status status Description 0 Ignore transmission block 1 Transmission completed successfully 2 Transmission in progress 3 Error Slave device not in the scan list 4 Error Slave is off line 5 Error DeviceNet network connection deactivated off line 6 Error Unknown transmission TXID 7 Not used 8 Error Invalid command code 9 Error Scanner buffer full 10 Error Other client server transmission in progress 11 Error No conne
20. E DeviceNet DFD11A V V A SOR 15 Project Planning and Startup 2 LAI IV DRIVE ly 3 lt z RC 16 Project planning for two process data words Process data length 2 can be set using the DeviceNet PD Configuration parameter In this case the setting 2 PD or 2PD Param must be selected in MX_SHELL or DBG As a result two process data words 4 bytes are processed in the inverter and two process input data words are sent to the control No process data are processed or sent back if the control transmits more than two process output data words Two process data words are processed and two process input data words are sent from the inverter to the control if the control transmits two process output data words PLC Address range Output file 0 3 10 PD 1 0 3 11 PD2 gt Input file 1 3 10 i 1 3 11 l 02121AEN Fig 5 Representation of two process data words in the PLC memory area The process output data are stored in the PLC output file and the process input data of the PLC are stored in the input file In the example above the output data words 0 3 10 and 0 3 11 are copied to process output data words 1 and 2 and processed by the inverter The inverter sends back two process input data words which are copied into input data words 1 3 10 and 1 3 11 of th
21. EDS files are automatically read in after the DeviceNet Manager software is called up The device list contains all devices which have been defined by an EDS file V V V U 3 DPI 5 SN MOVIDRIVE DeviceNet DFD11A 13 Project Planning and Startup 3 3 Process data exchange 3 3 1 Polled 1 0 The polled 1 0 messages correspond to the process data messages of the SEW fieldbus profile and up to three process data words can be exchanged between the control and the inverter The process data length be set with MX SHELL version 1 30 or later and DBG version 13 or later using the parameter P877 DeviceNet PD Configuration The inverter must be switched off and on again after this parameter has been changed in order to activate the set process data length The process data length can also be set using the parameter data channel of DeviceNet The pro cess data configuration takes effect immediately if the process data length is set using the param eter data channel IMPORTANT The set process data length determines the process data lengths of both the polled 1 0 and the bit strobe 1 0 messages i e the settings for the process data lengths of both the polled 1 0 and the bit strobe 1 0 always have to be identical in the control CEN 7 EURODRIVE 14 MOVIDRIVE DeviceNet DFD11A Project Planning and Startup Project planning for three process data words The factory setting of the proc
22. MOVIDRIVE DeviceNet DFD11A Project Planning and Startup 3 2 Setting up the DeviceNet network using the DeviceNet Manager software 3 2 1 Installing the EDS file B Device List Hac Drive Photoelectric Sensor f Software Communication Adapter Barcode Scanner Dodge EZLINK SCANport Device Human Machine Interface 2 SEW Ger teprofil Rockwell Automation Dodge SEN Eurodrive GmbH SEVY MOVITRAC FFD31C amp SEVY MOYVIDYN AFD11 SEVY MOY IDRIVE DFD114 01908AXX Fig 3 EDS file list There is an EDS file MDX eds and a bitmap file MDX bmp for the DFD11A option card These files must be installed using the DeviceNet Manager software To do this select Utilities Install EDS File from the menu The program then prompts you for the EDS file name and the bitmap file The EDS file is then installed More details on the installation of the EDS file can be found in the Allen Bradley documentation for the DeviceNet Manager After installation the device is available in the device list under the entry SEW Ger teprofil SEW Eurodrive GmbH SEW MOVIDRIVE DFD1 1A You can use the following Internet addresses for obtaining current EDS files and for further infor mation about DeviceNet SEW EURODRIVE www sew eurodrive de Allen Bradley www ab com Rockwell www rockwell com Open Device Net Vendor Association www odva org 3 2 2 Connecting the device to an existing network All
23. a BITS 4 byte data 0x05 1 X BOOL 0 1 Bad flag Bead 2 X BOOL 0 Input Direction Maxi 3 X UINT 16 bit Size mum 4 X X ARRAY 2 byte index Data BITS 4 byte data 0x06 1 X BOOL 0 1 Bad flag Read 2 X BOOL 0 Input Direction Default 3 X UINT 16 bit Size 4 X X ARRAY 2 byte index Data BITS 4 byte data 0x07 1 X BOOL 0 1 Bad flag Read 2 X BOOL 0 Input Direction Scaling 13 X UINT 16 bit Size 4 X X ARRAY 2 byte index Data BITS 4 byte data 0x08 1 X BOOL 0 1 BBad flag Read 2 X BOOL 0 Input Direction Attribute 3 X UINT 16 bit Size 4 X ARRAY 2 byte index Data BITS 4 byte data Table 11 Register object class Attribute 1 Bad flag signals whether an error occurred in the previous service Attribute 2 represents the direction of the instance and attribute 3 states the data length in bits The actual parameter data are represented in attribute 4 They are made up of the index 2 bytes and the data 4 bytes GV eA EURODRAIME 22 MOVIDRIVE DeviceNet DFD11A Project Planning and Startup The services Get Attribute Single and Set Attribute Single are available for transmission Service Coding Comment Get Attribut Single Read attribute Set_Attribut_Single 0x10 Write attribute Table 12 Register class services Example Parameter Setpoint description PO1 index 8304 2070h is to be written with the value CONTROL WORD 1 9 Byte offset 0 1 2 3 4 5 6 7 8 9 10 Func
24. ata have not been stored previously 19 Store operation failure The data could not be stored because an error occurred whilst saving them 1E Reserved for DeviceNet 1F Vendor specific error Proprietary error See the fieldbus device profile manual 20 Invalid parameter Invalid parameter This error message is used when a parameter does not satisfy the require ments of the specification and or the requirements of the application 21 CF Future extensions Reserved by DeviceNet for additional definitions DO FF Reserved for Object This area is intended for use if the error which has occurred cannot be Class and service errors assigned to any of the aforementioned error groups Table 24 General error codes L 59 A EURODRIME TAVV 36 MOVIDRIVE DeviceNet DFD11A 6 2 Statement of conformance Device Net Statement of Conformance General Device Data DeviceNet Physical Conformance Data DeviceNet Communication Data SOC data as of 9 16 1998 Conforms to DeviceNet Specification Vendor Name Device Profile Name Product Name Product Catalog Number Product Revision Network Power Consumption Max Connector Style Isolated Phy sical Lay er LEDs Supported None O MAC ID Setting Default MAC ID Communication Rate Setting Communication Rates Supported Device Network Behavior Check All That Apply UCMM Explicit Message Groups Supported Dynamic I O Message Groups Pe
25. ate is calculated on the basis of the timeout interval using the following formula t Timeout_Interval_ExplicitMessages 4 lexpected_Packet_Rate_ExplicitMessag It can be set using connection object class 5 instance 1 attribute 9 The range of values runs from 0 ms to 65535 ms in 5 ms steps If a timeout response is triggered for the explicit messages the connection for the explicit mes sages is automatically dropped providing the polled 1 0 or bit strobe 1 0 connections not in the ESTABLISHED status This is the default setting for DeviceNet The connection for explicit mes sages must be re established in order to be able to communicate with these messages again The timeout response is not transmitted to the inverter 7 Pe EURGDRIVE E V VV MOVIDRIVE DeviceNet DFD11A 25 same Application with PLC Type SLC500 4 Sample Application with PLC SLC500 The sample applications are based on a system configuration as shown in Fig 10 RSLogic500 for SLC500 DeviceNet Manager System Configuration 9324 RLOSOOEND 1787 MGR DeviceNet PC f A RS232C 852326 aarp AAB ON 1747 CP3 1747 cPa MAD Mer 16 16 Dev
26. attributes O c DeviceNet Services L Attributes Atribue Single ID Description Object list Maximum connections supported won Number of active connections 4 connections list DeviceNet Services L Get Attributes Al L Attribute Single If y es fill out the Vendor Specific Additions form on page F 7 Get Set Valuelimits OOOO OOOO Parameter Options Get Set ValueLimits Parameter Options Yes No X Get to indicate that attribute value is returned by the use of Get Attribute Single service Set to indicate that attribute value is written to by the use of Set Attribute Single service Jo 9 MOVIDRIVE DeviceNet DFD11A Appendix a Device Net Statement of Conformance DeviceNet DeviceNet Object 0x03 Required Object Class ID Description Get Set Value Limits Object Attributes Open 1 Revision 2 Implementation None Supported DeviceNet Services Parameter Options Services L Get Attibute_Single X None Supported Object Instance ID Description Get Set ValueLimits Attributes Open 1 29 2 Baudrate K 2 L None Supported BOI 4 Bus off counter X X 0 255 5 Allocation information x O 6 MAC ID switch changed x L 2 7 Baud rate switch changed 8 ID switch value L 298 9 Baud rate switch value 222 DeviceNet Services Parameter Options Services X Get At
27. ble The required cable is also described in the DeviceNet specification Volume 1 Appendix B The connection must be made according to the color code specified in Table 1 2 4 Shielding and routing of the bus cables Having the bus cable correctly shielded reduces electrical interference which can occur in an indus trial environment The following measures ensure the best possible shielding Fasten the retaining screws of plugs modules and potential compensating cables until finger tight Apply the bus cable shielding on both ends Do not route the signal and bus cables in parallel to the power cables motor leads use sepa rate cable ducts if at all possible Use only metal grounded cable racks in industrial environments Route the signal cables and the associated potential compensation closely to each other at the shortest distance Avoid using plug connections to extend bus cables Route the bus cables in close proximity to existing grounding surfaces Use bus connectors with a metal plated or metal housing IMPORTANT In the event of fluctuations in the ground potential a compensating current may flow along the shield which is connected at both ends and to the ground potential PE In this case make ade quate provision for potential compensation in accordance with the relevant VDE regulations 2 5 Bus termination In order to avoid disruptions in the bus system due to reflections etc each DeviceNet segment must be
28. cribes how to install the DFD11A DeviceNet option card in the drive inverter and how to start up the MOVIDRIVE on the DeviceNet fieldbus system As well as explaining all settings on the fieldbus interface this document also deals with the vari ous DeviceNet connection variants in the form of brief startup examples As well as this manual on the DeviceNet option you should request the following publications deal ing with the topic of fieldbuses in more detail so as to permit MOVIDRIVE to be connected to the DeviceNet fieldbus system in a straightforward and effective fashion e MOVIDRIVE Fieldbus Unit Profile manual MOVIDRIVE system manual The manual for the MOVIDRIVE fieldbus unit profile describes the fieldbus parameters and their coding as well as explaining the whole range of various control concepts and application options in the form of brief examples The MOVIDRIVES system manual contains a listing of all parameters of the drive inverter which can be read and or written via the various communications interfaces such as RS 485 and also via the fieldbus interface The MOVIDRIVE drive inverter in conjunction with the DFD11A option enables you to make the connection to master automation systems via DeviceNet thanks to the high performance univer sal fieldbus interface of the DFD11A option MOVIDRIVE and DeviceNet The device behavior of the inverter which forms the basis of DeviceNet operation is referred to as
29. ction to slave device 12 Error Response data are too long for the block 13 Error Invalid connection 14 Error Invalid size specified 15 Error Occupied 16 255 Reserved Table 22 Command and status codes 32 MOVIDRIVE DeviceNet DFD11A sample Application with PLC Type SLC500 The M files are divided into a request file MO file and a response file M1 file The data transmis sion is shown in Fig 13 SLC500 Scan unit 1747 SDN Request 0 transmission 1 MO file request block idle loop g Z gl 4 N Process requests N Contact scheme scan and responses 2 gt P Response Scanner response transmission 4 M1 file block idle loop 02148AEN Fig 13 Transmission of an explicit message Register object class 7h must be used in XE Wort224 order to read instance 1 to 8 or write Wort 225 instance 2 and 3 parameters from the inverter via the SEW parameter data chan Dienst MAC ID Wort 226 nel The data range is divided into the index 2 bytes and the parameter data 4 bytes Uber tragungs kopf Class Wort 227 Instance Wort 228 the sample program a data area is reserved in the integer file N file into Wort229 which the data of the M0 M1 files are writ Datenwort Low HEX Wort 231
30. e PLC MOVIDRIVE DeviceNet DFD11A Project Planning and Startup Project planning for one process data word Process data length 1 can be set using the DeviceNet PD Configuration parameter In this case the setting 7 PD or 1PD Param must be selected in MX SHELL or DBG As a result one process output data word 1 byte is processed in the inverter and one process input data word is sent to the control The control is permitted to send only one process output data word No process data are processed or sent back if more than one process output data word is sent by the control PLC Address range Output file 0 3 10 PD 1 mamas 2 1 Input file j uM mm N PD 1 30 ei 02122 Fig 6 Representation of one process data word in the PLC memory area The process output data are stored in the PLC output file and the process input data of the PLC are stored in the input file In the example above output data word 0 3 10 is copied to process output data word 1 and processed by the inverter The inverter sends back one process input data word which is copied to input data word 1 3 10 of the PLC Timeout response with polled 1 0 The timeout response is triggered by the DeviceNet option card The timeout interval must be set by the master after the connection has been established The DeviceNet specification refers to an expected packet rate rather than a timeout interval The expected
31. eNet option card is designed so the fieldbus specific MAC ID and baud rate settings are made using hardware switches on the option card This manual setting means the drive inverter can be integrated into the DeviceNet environment and switched on within a very short period of time The parameter setting process can be performed in a completely automated fashion by the DeviceNet master parameter download This future oriented variant offers the advantages of shortening the system startup time and simplifying the documentation of your application pro gram because all the important drive parameters can now be stored directly in your control pro gram Node 0 Node_2 Communication Interface 0 2 62 9J em 82 _ MOVIDRIVE DeviceNet 1 MOVIDYN Node_3 3 01922 Fig 1 DeviceNet with MOVITRAC 31C MOVIDRIVES MOVIDYN and PLC Using a fieldbus system requires additional monitoring functions in the drive engineering e g time monitoring of the fieldbus fieldbus timeout as well as ra apid stop concepts For example you can specifically adapt the monitoring functions of MOVIDRIVE to your application You can determine for instance which fault reaction of the drive inverter should be triggered in the event of a bus error rapid stop is a good idea for many applications although this can also be achieved by freezing the last setpoints so the drive continues operating with the
32. er to Peer Default I O Data Address Path Fragmented Explicit Messaging Supported If yes Acknowledge TimeOut Typical Target Addresses Consumption Service Production Service MOVIDRIVE DeviceNet DFD11A Volume Release SEW Eurodrive GmbH Vendor Specific SEWMOVIDRIVE DFD11A Appendix Fill in the blank or X the appropriate box N 2 Volume II Release 2 3 101 Open Hardwired Open Pluggable Yes No Module Network DIP Switch Other DIP Switch Other 125k bit s 250k bit s Group 2 Client Group 2 Server Peer To Peer Group 1 Group 1 Input Class Output Class Yes Class Class 11V dc worst case L Sealed Mini Sealed Micro Combo Mod Net L L Sofware Setabe 63 Sofware Setabe 500k bits Group 2 Only Client Group 2 Only Server Tool not a Device Group 2 L Group 3 Group 2 L Group 3 sa OOOO Re QOjORO Inst 64 Inst 64 x 0 1000 ms Inst J 7 1 Inst 7 7 1 of 9 Appendix H Device Net Statement of Conformance DeviceNet Identity Object 0x01 Required Object Class ID Description Get Set Value Limits Object Attributes Open 1 Revision L1 LI Implementation 2 Max instance L L None Supported 3 Number of Instances L L 4 Optional attributes list 5 Optional services list Ez L 6 Max Id of class attributes 7 Max Id of instance attribute
33. erminals The setting P100 Setpoint source FIELDBUS causes the inverter to get its setpoints from the fieldbus if P101 F ELDBUS the inverter is con trolled via the fieldbus i e enable rapid stop normal stop controller inhibit etc MOVIDRIVE will now respond to the process output data transmitted from the master programmable controller Activation of the fieldbus control mode is signalled to the master control by the PA data enabled bit in the status word For safety reasons the inverter must also be enabled on the terminal side for control via the field bus system Accordingly the terminals must be wired up or programmed in such a way that the inverter is enabled via the input terminals The easiest way of enabling the inverter on the terminal side is to wire input terminal 0100 CONTROLLER INHIBIT function to the 24 V signal and pro gram input terminals 0101 to 0105 to NO FUNCTION MOVIDRIVE DeviceNet DFD11A al AV V CS V 3 COOLE 11 Project Planning and Startup Procedure for startup of the MOVIDRIVE inverter with fieldbus interface 1 Switch the drive inverter to ENABLE on the terminal side Wire input terminal 0100 CONTROLLER INHIBIT function to the 24 V signal e g with a jumper Control head 13 Controller inhibit lt No function No function lt No function No function No function lt
34. erter changes to the rapid stop drive status In rung 2 process input data word 1 1 3 8 is copied to the DeviceNet output module via memory word 0 3 12 and process input data word 2 1 3 9 is copied to the SLC500 output module via memory word 0 1 0 4 3 Objective Exchange of explicit messages parameter data In this program parameter data are to be exchanged between the control and the inverter TXID Word 224 85 i The exchange of parameter data between the 5 Connection Word 225 inverter and the SLC500 is performed using files ST Word 226 leferred to as M files see the installation instruc tions for the DeviceNet scanner module Class Word 227 memory area from word 224 to 255 in these M Instance Word 228 files is reserved for explicit messages Fig 12 shows the structure of this memory area Attribute Word 229 o gt Word 230 This memory area is divided into two areas Transmission header 3 words iis dees Explicit message body 01916AEN Fig 12 M file MOVIDRIVE DeviceNet DFD11A C Type SLC500 2 MO eu AU SX SERVIS 31 same Application with PLC SLC500 These memory areas are described in more detail in Table 21 Memory area Function Length Value Description Transmission header jcmd status word See Table 22 cmd Entry of a command code status Entry of the transmission status TXID 1 2 word 1
35. ess data configuration is process data length 3 This setting be altered using the DeviceNet PD Configuration parameter In MX_SHELL or DBG the setting is displayed via the parameter DeviceNet PD configuration 3 PD or 3PD Param As a result three process data words 6 bytes are processed in the inverter and three process input data words are sent to the control No process data are processed or sent back if the control transmits more than three process out put data words Three process data words are processed and three process input data words are sent from the inverter to the control if the control transmits three process output data words PLC Address range Output file 0 3 10 PD 1 0 3 11 PD2 0 3 12 PD3 pm 9 PD2 Input file 6 PD1 PD2 mE m PD1 13 10 lt PD2 1 3 11 1 3 12 02120 Fig 4 Representation of three process data words in the PLC memory area The process output data are stored in the PLC output file and the process input data of the PLC are stored in the input file In the example above the output data words 0 3 10 0 3 11 and 0 3 12 are copied to process output data words 1 2 and 3 and processed by the inverter The inverter sends back three process input data words which are copied into input data words 1 3 10 1 3 11 and 1 3 12 of the PLC MOVIDRIV
36. et_Attribut_Single Instance 1 Get_Attribut_Single OUTPUT Instance 2 Set_Attribut_Single Get_Attribut_Single OUTPUT Instance 3 Set_Attribut_Single WRITE VOLATILE INPUT Get_Attribut_Single Instance 4 EE EE TIEN DPRAM INPUT Get Attribut Single READ MAXIMUM Instance 5 U Get_Attribut_Single READ DEFAULT Instance 6 INPUT Get_Attribut_Single READ SCALIN Instance 7 d Get Attribut Single d dd READ ATTRIBUTE Instance 8 02145AEN Fig 8 Description of the parameter channel C lt AV V P 2 V V TODOR MOVIDRIVE DeviceNet DFD11A 21 Project Planning and Startup The following table shows the attributes of the eight register object instances Class Instance Attribute Get Set Type value Meaning 0x07 10 01 1 BOOL 0 1 Bad flag Read 2 X BOOL 0 Input Direction 3 X UINT 16 bit Size 4 X X ARRAY 2 byte index Data BITS 4 byte data 0x02 1 X BOOL 0 1 Bad flag Read 2 X BOOL 1 Output Direction Write 3 X UINT 48 bit Size 4 X X ARRAY 2 byte index Data BITS 4 byte data 0x03 1 X BOOL 0 1 Bad flag Read 2 X BOOL 1 Output Direction Write 3 X UINT 48 bit Size Volatile X X ARRAY 2 byte index Data BITS 4 byte data 0x04 1 X BOOL 0 1 Bad flag Read 2 X BOOL 0 Input Direction Mini 3 X UINT 16 bit Size mum 4 X X ARRAY 2 byte index Dat
37. ic Additions form on page F 7 Set Value Limits Ou Parameter Options Get p indicate that atribute value is returned by the use of Get Attribute Single service Set to indicate that attribute value is written to by the use of Set Attribute Single service MOVIDRIVE DeviceNet DFD11A Peer to Peer Connections _ Instances Explicit Message L Total Server Client Dynamic I O L Total Server Client C App tig C Client O 24 3 L Get Se Value Limits s L 2 246 x 20 65830 O 2 E E Parameter Options Ye No Z 09 Appendix Device Net Statement of Conformance DeviceNet Required Object mplementation Object Class Attributes Open None Supported Services None Supported Object Instance Attributes Open L None Supported Services L None Supported Vendor Specific Additions Register Obiect 0x07 ID Description 1 Revision DeviceNet Services C Get Atribute Single ID Description Bad Flag Direction Size Data A C N DeviceNet Services Get Attribute Single X Attribute Single If yes fill out the Vendor Specific Additions form on page F 7 Get Set Value Limits OO Parameter Options Get Set Value Limits O L 7 16 48 2 65536 Parameter Options 8300 Yes No Get to indicate that attribute value is returned by the use of Get Atribute Single service
38. iceNet DFD11A Application with PLC Type SLC500 Start DeviceNet communication 0000 1747 SDN 52 4 7 B3 10 ADD 0001 05 Source A B3 2 0000000000000010 lt Source B 1 1 lt Dest 0000000000000010 Move Source B3 2 0000000000000010 lt 0002 Greater Than Source A B3 2 0000000000000010 lt Source B 3 3 lt 0003 Dest B3 2 0000000000000010 lt 01912AEN Output bit 0 3 0 0 is set in rung 0 program line 0 thereby starting DeviceNet communication see the description of the DeviceNet scanner Rungs 1 and 3 implement the status engine with which states 0 3 are implemented The current status is written to the outputs O 1 0 of the SLC500 output module in rung 2 GRT MOV 0003 Greater Than A gt B Source A B3 2 0000000000000010 lt 0 lt Source B 3 Dest B3 2 3 0000000000000010 lt 0004 Source A B3 2 0000000000000010 lt 6 lt Source B 0 Dest 0 33 0 lt 0 lt EQU 0005 Equal Source A B3 2 0000000000000010 lt Source 1 1 lt 01913AEN The figure illustrates the output of process data values to the scanner memory area S A V B STRODE MOVIDRIVE DeviceNet DFD11A 29 same Application with PLC Type SLC500 Status 0 is created in rung 4 In this status a 6 ENABLE is written to memory area 0 3 3 which represents process
39. iceNet ane Y Power Supply SLC500 Outputs Inputs Scanner Interface Inputs Interface Outputs Bs Gw k EX m Le 2 RS gz 5 1746 2 1747 1542 1747 SDN 1746 1816 1746 0816 1794 1794 1816 1794 ADN 1794 0V16 1485 2 1485A C2 01909AEN Fig 10 PLC system configuration The following devices are employed Device MAC ID SLC5 04 DeviceNet scanner 1747 SDN 1 INPUT module with 32 inputs OUTPUT module with 32 outputs DeviceNet adapter with input module with 16 inputs 11 DeviceNet adapter with output module with 16 outputs 10 MOVITRAC with FFD31C optional 0 MOVIDYN with AFD11A optional 4 MOVIDRIVE with DFD11A 8 Table 18 Devices used in the sample application gt j M DRIVE ry M 3U lt 1 RC o 26 MOVIDRIVE DeviceNet DFD11A Application with P C Type SLC500 The following memory areas have been specified with the help of the DeviceNet manager software KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK Se Se ke Se Se Se e Se 5k Se oe ee eoe eoe oe oe oe oe oe oe HAHAHAHAHA HAHAHAHA KKK KKK 1747 SDN Scanlist Map ko eee KKK Discrete Input Map 15 14 13 12 II 10 09 08 07 06 05 04 03 02 01 00 I 3 000 R R R R R R R R R R R R R R Status word of the scanner I 3 001 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Process
40. ing the DeviceNet Manager software 13 2 2 1 Installing the EDS file uiii iiri irte milione ee oii deb etras bc pr testati 13 3 2 2 Connecting the device to an existing network 13 4 9 Pro ess dala A ebd ex aaa rita 14 vro ip ec 14 22 ccn d T 18 3 4 Parameter data exchange aca n uc rb 20 3 4 1 The SEW parameter data channel sse 20 Sample Application with PLC Type SLC500 26 4 1 Exchange of polled 1 0 process data ener 28 4 2 Exchange of bit strobe ucibus 30 4 3 Exchange of explicit messages parameter 31 Technical DANG 35 P jj Sec 36 6 1 General error Co0des ne 36 6 2 Statement of conformance n naa 37 6 3 Definitions of terminology nn 46 iX u uu 41 MOVIDRIVE DeviceNet DFD11A Introduction fal e 4 y S Ma 1 Introduction This user manual for the DeviceNet DFD11A option des
41. l signal source 10 Communication Setpoint source Setpoint source 11 Communication PD configuration Process data configuration 12 Communication Setp descr PO1 Process output data assignment for PD1 13 Communication Setp descr P02 Process output data assignment for PD2 14 Communication Setp descr PO3 Process output data assignment for PD3 15 Communication Act v descr Process input data assignment for PD1 16 Communication Act v descr PI2 Process input data assignment for PD2 17 Communication Act v descr PI3 Process input data assignment for PD3 18 Communication PO data enable Enable process data 19 Communication Timeout response Timeout response 20R Communication Fieldbus type Fieldbus type 21R Communication Baud rate Baud rate via DIP switch 22R Communication Station address MAC ID via DIP switch 23R Monitor setpoint Monitor of process output data word 1 24R Monitor 2 setpoint Monitor of process output data word 2 25 Monitor PO3 setpoint Monitor of process output data word 3 26R Monitor actual value Monitor of process input data word 1 27R Monitor PI2 actual value Monitor of process input data word 2 28R Monitor PI3 actual value Monitor of process input data word 3 R Read Only Table 16 Fieldbus parameters The scaling and the representation within the message corresponds to the DeviceNet specification see the DeviceNet specification for coding 24 MOVIDRIVE DeviceNet DFD11A
42. most recently valid setpoints e g conveyor belt The range of control terminal functions is also ensured in fieldbus mode so you can continue to implement rapid stop concepts independent of the fieldbus by means of the drive inverter terminals The MOVIDRIVE drive inverter offers you numerous diagnostic options for startup and service purposes For example you can use the integrated fieldbus monitor to check both the setpoints sent by the master control and the actual values Furthermore you are supplied with numerous additional items of information about the status of the fieldbus option card The fieldbus monitor function in conjunction with the MX SHELL PC soft ware offers you an easy to use diagnostic facility permitting all drive parameters to be set includ ing the fieldbus parameters as well as displaying the fieldbus and device status information in detail MOVIDRIVE DeviceNet DFD11A d V V Po SA i TROON 5 Installation 2 Installation 2 1 Supported unit types The DFD11A option for the DeviceNet connection can be operated with all drive inverters in the MOVIDRIVE series 2 2 Installation of the option card Before you begin Take suitable measures to dissipate any electrical charge in your body before you touch the option card discharge strap conductive shoes etc Keep the option card in its original packaging and do not remove it until it is to be installed Do not to
43. n the control word 3 3 2 Bit strobe 1 0 Bit strobe 1 0 messages not contained in the SEW fieldbus profile They represent a process data exchange which is specific to DeviceNet The master sends out a broadcast message that is 8 bytes 64 bits long One bit in this message is assigned to each participant in accordance with its station address The value of this bit may be 0 or 1 triggering two different reactions in the recipient 0 Only send back the process input data Continuously green 1 Trigger fieldbus timeout response and send back process input data Continuously green Table 9 Bit strobe signal messages IMPORTANT The BIO LED can be consulted to distinguish between the timeout triggered by the bit strobe mes sage and a real timeout in the connection It remains continuously green if the timeout is triggered by the bit strobe message If the BIO LED flashes red there is a timeout in the bit strobe connection and no additional bit strobe messages are accepted Table 10 shows the data area of the bit strobe request message which represents the allocation of participants station address to data bits For example the participant with station address MAC ID 16 only processes bit 0 in data byte 2 Byte offset 7 6 5 4 3 2 1 0 0 ID7 ID6 ID5 ID4 ID3 ID2 ID 1 IDO 1 ID 15 ID 14 ID 13 ID 12 ID 11 ID 10 ID 9 ID 8 2 ID 23 ID 22 ID 21 ID 20 ID 19 ID 18 ID 17 ID 16 3 ID 31 ID 30 ID 29 ID 28 ID 27 ID
44. odes EN Error name Description 00 01 Reserved for DeviceNet 02 Resource unavailable The source required for performing the service is unavailable 03 07 Reserved for DeviceNet 08 Service not supported The service is not supported for the selected class instance 09 Invalid attribute value Invalid attribute data have been sent 0A Reserved for DeviceNet 0B Already in requested The selected object is already in the requested mode state mode state 0C Object state conflict The selected object cannot perform the service in its current status 00 Reserved for DeviceNet 0E Attribute not settable It is not possible to access the selected object for writing OF Privilege violation Violation of access entitlement 10 Device state conflict The current status of the device makes it impossible to perform the required service 11 Reply data too large The length of the transferred data is longer than the size of the receiving buffer 12 Reserved for DeviceNet 13 Not enough data The length of the transferred data is too short for the service to be performed 14 Attribute not supported The selected attribute is not supported 15 Too much data The length of the transferred data is too long for the service to be performed 16 Object does not exist The selected object is not implemented in the device 17 Reserved for DeviceNet 18 No stored attribute data The requested d
45. ons of terminology Term Description Allocate Provides a service for setting up a connection Attribute Attribute of an object class or instance Describes the characteristics of the object class or instance more fully BIO Bit strobe 1 0 All participants can be addressed with a broadcast message The addressed participants respond with the process input data Class DeviceNet object class DeviceNet scanner Plug in module for the Allen Bradley PLC which connects the PLC fieldbus to the peripheral devices DUP MAC check Duplicate MAC ID test Explicit message body Includes the class no instance no attribute no and the data Explicit message Parameter data telegram assists in addressing the DeviceNet objects Get_Attribute_Single Read service for a parameter Instance Instance of an object class Divides the object classes into additional subgroups MAC ID Media Access Control identifier Node address of the device M file Provides the data range between the PLC and the scanner module Mod Net Module network Node ID Node address MAC ID PIO Polled 1 0 Process data channel of DeviceNet allows process output data to be sent and process input data to be received Release Provides a service for dropping a connection Reset Provides a service for resetting an error Rung SLC500 program line Service Service performed over the bus e g read service
46. output data word 1 A 5000 is written to memory area 0 3 4 process output data word 2 which represents 1000 rpm This means the motor runs at 1000 rpm Status 1 is created in rung 5 In this status a 0 RAPID STOP is written to memory area 0 3 3 which represents process output data word 1 A 0 is written to memory area 0 3 4 process output data word 2 which represents 0 rpm This means the motor is stopped with the rapid stop States 2 and 3 are treated similarly to states 0 and 1 and are thus not explained any further MUL 0008 Multiply L3 6 0 lt ource 1 1 lt Dest 037 0 lt Move Source 6 lt Dest 0 3 6 z 0009 CEND gt 01914AEN In the figure above the current actual value of the device with address 8 which is located in mem ory area 3 6 process input data word 2 is multiplied by a constant factor in this case by 1 and written to output memory area 0 3 7 process output data word 2 of the device with address 0 In addition the value 6 ENABLE is written to the process output data word 1 of the device with address 0 0 3 6 Thus the device with address 0 follows the actual speed with enable signal from the device with address 8 4 2 Exchange of bit strobe 1 0 Objective In the following program the process input data are to be requested by MOVIDRIVE In addition a fieldbus timeout should be triggered with the strobe bit To do this the follo
47. r Connections Max Instances Complete the Object Instance section Explicit Message L Explicit Message L Total for each Instance type supported Paled Sever Client Indicate Production trigger Bit Strobed Dynamic 1 0 L Total Transport type and Transport Change of State L Server Client Class supported for Dynamic VO Cyclic Production trigger s cos App tig Transport type s Server Client L Transport class es L 2 3 L ID Description Get Set Value Limits Attributes Open 1 State xX 2 Instance type L 4 3 Transport Class trigger L 4 4 Produced connection ID IX O 5 Consumed connection ID KR 6 Initial comm characteristics x L 4 7 Produced connection size xX 226 8 Consumed connection size x xX 446 9 Expected packet rate X 65 12 Watchdog time out action L 2 13 Produced connection path lengh X 14 Produced connection path Ix 15 Consumed connection path lengh X 16 Consumed connection path O 17 Production inhibit time x DeviceNet Services Parameter Options Services X Delete L Apply Atributes X Get Atribute Single X Se Atribute Single Vendor Specific Additions If y es 1 out the Vendor Specific Yes L Additions form on page F 7 No X Get p indicate that attribute value is returned by the use of Get Atribute Single service Set p indicate tat attribute value is written to by the use of Set Attribute Single ser
48. s The manufacturer reserves the right to make changes to the technical data and designs as well as the user interface herein described which are in the interest of technical progress A requirement of fault free operation and fulfillment of any rights to claim under guarantee is that this information is observed MOVIDRIVE DeviceNet DFD11A Contents Introduction eee 4 Installation eee ener 6 2 1 Supported unit types aues omi J I iu radice dun Aedes ies ve Rd 6 2 2 Installation of the option card societe rra ina U RR GM Ea DTE PARA teni 6 2 9 cg e 6 2 4 Shielding and routing Of the bus cables 7 2 5 Bus termination SPON 7 2 6 Setting the DIP 8 2 7 Display elements n od Era rotes gara d Nue RS tad 8 2 1 Power up Sequence due 8 2 7 2 ModNet ED itti Doha C 9 ET PIO LED a a endende 9 2 4 BIO LED 10 2 1 9 BUSOFF LED Rm 10 Project Planning and Startup 11 3 1 Inverter control mode 11 3 2 Setting up the DeviceNet network us
49. s error passive state Flashes red e The number of physical bus errors is too high No more error 1 s cycle telegrams are actively written to the bus error passive state Red BusOff status BUS ERROR The number of physical bus errors has continued to grow despite the switch to the error passive state Access to the bus is deactivated Table 8 Status table of the BUSOFF LED 2 EURODRIME 10 MOVIDRIVE DeviceNet DFD11A Project Planning and Startup 3 Project Planning and Startup This chapter describes how to start up the MOVIDRIVE inverter with the DFD11A option using MX SHELL from version 1 30 or the DBG11A keypad from version 13 3 1 Inverter control mode fieldbus After the DeviceNet option card has been installed and the baud rate and MAC ID have been set using the DIP switches the parameters for the MOVIDRIVE inverter can be set immediately via the fieldbus system without further manual adjustment All drive parameters can be downloaded in this manner from the master programmable controller directly via DeviceNet after the power is switched on The inverter has to be switched to the appropriate contro mode prior to control via DeviceNet This can be done with parameter P100 Setpoint source and P101 Control signal source The factory set tings for these parameters are the values Bipol Fix setp or Terminals setpoint processing via analog setpoint and control via input t
50. s L1 LI DeviceNet Services Parameter Options Services L GetAtributes ru Reset X None Supported L GetAtribute Single L Find Next Object instance Object Instance ID Description Ge Set Vauelimits Attributes Open 1 Vendor L 315 2 Device type L 100 3 Product code X L 4 Revision L 1 01 5 Status bits supported X L 6 Serial number L 8229031 7 Product name L SEW MOVIDRIVE DFD11A 8 State L L 9 Config Consistency Value 10 Heartbeat Interval L DeviceNet Services Parameter Options Services SGetAtributes x Reset 0 X Attribute Single L SetAtribute Single Vendor Specific Additions If y es fill out the Vendor Specific Yes Additions form on page F 7 No XO Get to indicate that attribute value is returned by the use of Get Attribute Single service Set to indicate that attribute value is written to by the use of Set Attribute Single service 2 of 9 38 MOVIDRIVE DeviceNet DFD11A a Device Net Statement of Conformance DeviceNet Required Object Class Object Attributes Open mplementation X None Supported Services X None Supported Object Instance Attributes Open X None Supported Services X None Supported Vendor Specific Additiane Appendix Message Router Obiect 0x02 ID Description Revision Optional attribute list Optional service list Max ID of class attributes 7 Max ID of instance
51. tartup General SEW parameter data channel Parameters are written read via the parameter object in two steps 1st step Writing the index via instance 1 2nd step Writing reading the data via instances 2 to 8 No Group Name Comment 1 SEW parameter channel SEW Param Index Index of the parameter 2 SEW parameter channel SEW Read Write Read or write the value of the parameter 3 SEW parameter channel SEW Read WriteVo Read or write the value of the parameter but do not store permanently 4R SEW parameter channel SEW Minimum Read the minimum of the parameter 5R SEW parameter channel SEW Maximum Read the maximum of the parameter 6R SEW parameter channel SEW Default Read the default value of the parameter 7R SEW parameter channel SEW Scaling Read the scaling of the parameter 8R SEW parameter channel SEW Attribute Read the attributes of the parameter Table 15 SEW parameter data channel Consequently two services have to be performed in order to read write a parameter The data format of the SEW param data corresponds to MOVILINK see list of parameters Writing reading the fieldbus parameters The parameters required for operating the fieldbus have been directly incorporated into the param eter object They can be addressed directly via the instance No Group Name Comment 9 Communication Control source Contro
52. terminated with 120 bus terminating resistors at the first and last physical participant The bus terminating resistor must be wired between terminals 2 and 4 of the bus connector V V V VA DRIVE MOVIDRIVE DeviceNet DFD11A 7 Installation 2 6 Setting the DIP switches There are two DIP switch blocks of 4 DIP switches each on the DFD11A DeviceNet card Two DIP switches are used for setting the baud rate and 6 for setting the MAC ID Media Access Control Identifier The MAC ID represents the node address of the DFD11A Function Abbrev Number of bits Representation Labeling Meaning MAC ID NA 6 bits 0 1 NA5 0 0 63 B as s __ BE Na B NA B so NE Nao e g MAC ID 2 Baud rate DR 2 bits 0 1 DR1 0 00 125 kbaud 01 250 kbaud 51 10 500 kbaud 11 Invalid 52 nri B pno e g 10 500 kbaud Table 2 MAC ID and baud rate setting 2 7 Display elements The display elements comprise 4 bicolor LEDs Function Abbreviation Module network status LED ModNet Polled 1 0 PIO Bit strobe 1 0 BIO Bus off BUSOFF Table 3 Display elements 2 7 1 Power up sequence All LEDs are tested after the unit is switched on The LEDs are switched on in the following sequence as part of the test
53. tibute_Single X Set Atribute Single L None Supported X Allocate M S connection set X Release M S connection set Vendor Specific Additions If yes fill outthe Vendor Specific Yes Additions form on page 7 No X Get to indicate that attribute value is returned by the use of Get Attribute Single service Set to indicate that attribute value is written to by the use of Set Attribute Single service 449 40 MOVIDRIVE DeviceNet DFD11A Appendix Device Net Statement of Conformance DeviceNet Required Object Class Object Attributes Open mplementation None Supported Services X None Supported Object Instance Complete the Object Instance section for each Instance type supported Indicate Production trigger Transport type and Transport Class supported for Dynamic VO Attributes Open Services Vendor Specific Additions Connection Obiect 0x05 ID Description 1 Revision DeviceNet Services Reset Create Delete Get Attribute Single Find Next Object Instance Predefined M S Connections Explicit Message Polled Strobed Change of State Cyclic L LI oodd Production trigger s Transport type s Transport class es Cyclic Sever ID Description State Instance type Transport Class trigger Produced connection ID Consumed connection ID Initial comm characteristics Produced connection size Consumed connection size Expected packet rate Watchdog
54. tion Index Data Signific Low LSB i MSB Example 01h 10h 07h 02h 04h 70h 20h 00h 00h 00h Table 13 Data format for the parameter request message Byte offset 0 1 2 9 4 5 6 7 Function Index Signific LEE Low LSB Example 01h 90h 70h 20h 09h Table 14 Data format for the parameter response message Address range Output data Header Header Service Class Index 2070h Index Data low word Data low word 0 Data high word Dats high word 0000h i i 25 Header Index Data Input data Header Index Data Header N a Header Service Class Index 2070h f Index Data low word Data low word 0 Data high word Data high word 0000h 02124AEN Fig 9 Parametric data exchange Parameter object class class 15 The fieldbus parameters of the SEW inverter can be addressed directly via the instance with the parameter object In order to comply with the DeviceNet specification the data format for these instances deviates from the SEW fieldbus profile However it is also possible to address all parameters of the inverter via the parameter object Instances 1 to 8 are reserved for this MOVIDRIVE DeviceNet DFD11A 23 Project Planning and S
55. uch the option card more than necessary and only hold it by the edge of the circuit board Do not touch any components Installing the option card De energize the inverter Switch off the mains and the 24 V supply if used Remove the lower hood cover from the control module Unscrew the electronics shield clamp Remove the black cover plate Insert the option card into the guide rails of the OPTION1 slot and push it in Insert option card by applying moderate pressure on the front panel The option card has been installed correctly when it is flush with the control card Screw the electronics shield clamp back on e hood cover of the control module back on The DFD11 option card is now fully installed 2 3 Pin assignment The assignment of connecting terminals is described in the DeviceNet specification Volume I Appendix A DFD11A option card Pin no Abbrev Meaning Color 1 0V24 black 2 CAN_L CAN_L blue 1 3 DRAIN DRAIN shiny 2 4 CAN_H CAN_H white 3 5 V 24V red 4 Table 1 Connection terminal CAN bus 5 02119AEN Fig 2 Pin assignment CENAJ gt A J 6 MOVIDRIVE DeviceNet DFD11A Installation The DeviceNet option card is opto decoupled on the driver side in accordance with the DeviceNet specification Volume Chapter 9 This means the CAN bus driver must be powered with 24 V via the bus ca
56. vice 6 d 5 f a ES _ 42 MOVIDRIVE DeviceNet DFD11A Appendix Device Net Statement of Conformance DeviceNet Required Object mplementation Object Class Attributes Open None Supported Services X None Supported Object Instance ID 1 Connection Obiect 0x05 Description Revision DeviceNet Services L LI Reset Create Delete Get Attribute Single Find Next Object Instance Predefined M S Connections Complete the Object Instance section for each Instance type supported Indicate Production trigger Transport type and Transport Class supported for Dynamic VO Attributes Open Services Vendor Specific Additions Explicit Message L Polled L Bit Strobed Change of State L Cydic Production trigger s Cyclic Transport type s Server Transport class es ID Description 1 State 2 Instance type 3 Transport Class trigger 4 Produced connection ID 5 Consumed connection ID 6 Initial comm characteristics 7 Produced connection size 8 Consumed connection size 9 Expected packet rate 12 Watchdog time out action 13 Produced connection path length 14 Produced connection path 15 Consumed connection path length 16 Consumed connection path 17 Production inhibit ime DeviceNet Services BEREE Reset Delete Apply Attributes Get Attribute Single Set Attribute Single If yes fill outthe Vendor Specif
57. vice 4 polled IO I 3 020 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PED1 device 4 bit strobe IO I 3 021 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PED2 device 4 bit strobe IO I 3 022 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PED3 device 4 bit strobe IO Discrete Output Map 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 QO O 3 000 R R R R R R R R R R R Control word of the scanner O 3 001 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Process data to device 11 O 3 002 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Process data to device 10 0 3 003 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PADI device 8 Polled IO 0 3 004 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PAD2 device 8 Polled IO 0 3 005 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PAD3 device 8 Polled IO 0 3 006 00 00 00 00 OO OO OO OO OO OO OO OO OO OO 00 OO PADI device 0 polled IO O 3 007 00 00 00 00 00 OO OO OO 00 00 OO 00 OO 00 00 OO PAD2 device 0 polled IO 0 3 008 00 00 00 00 00 OO 00 OO OO OO OO OO OO OO OO 00 PAD3 device 0 polled IO 0 3 009 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PADI device 4 polled IO 0 3 010 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PAD2 device 4 polled IO O 3 011 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PAD3 device 4 polled IO 0 3 012 08 Bit strobe for device 8 The polled 1 0 data are displayed in italics and the bit strobe data in bold italics MOVIDRIVE DeviceNet DFD11A V DPI
58. vice of the connection object class 0x05 instance 0x03 undetermined attribute by dropping the connection or by using the reset service of the identity object class 0x01 instance 0x01 undetermined attribute 3 4 Parameter data exchange 3 4 1 The SEW parameter data channel The SEW parameter data channel represents a connection via which parameters in the inverter can be changed or read This channel is represented by explicit messages on the DFD11A DeviceNet option card Access to the SEW parameter data channel is by means of the register object class 7 and the parameter object class 15 Register object class class 7 The SEW parameter data channel can be addressed using the services Get Attribute Single and Set Attribute Single The following possibilities for addressing the parameter data channel derive from the way the register object is specified by DeviceNet so INPUT objects can only be read and OUTPUT objects can be read and written Resulting MOVILINK service with Instance INPUT OUTPUT Get Attribut Single Set Attribut Single 1 INPUT READ Invalid 2 OUTPUT READ WRITE 3 OUTPUT READ WRITE VOLATILE 4 INPUT READ MINIMUM Invalid 5 INPUT READ MAXIMUM Invalid 6 INPUT READ DEFAULT Invalid 7 INPUT READ SCALING Invalid 8 INPUT READ ATTRIBUTE Invalid m m V We N A V S J A ane EU FO D RIINE 20 MOVIDRIVE DeviceNet DFD11A Project Planning and Startup INPUT G
59. wing parameters must be set in the inverter Menuno ndex Parameters Value 100 8461 Setpoint source Fieldbus 101 8462 Control signal source Fieldbus 870 8304 Process output data description 1 Control word 1 871 8305 Process output data description 2 Speed 872 8306 Process output data description 3 No function 873 8307 Process input data description 1 Status word 1 874 8308 Process input data description 2 Speed 875 8309 Process input data description 3 No function 876 8622 PO data enable YES 831 8610 Fieldbus timeout response Rapid stop warn Table 20 Setting the parameters for process data exchange a gt FC T VV A V BURG DEINE 30 MOVIDRIVE DeviceNet DFD11A Application with P The MOVIDRIVE drive inverter is now in fieldbus mode and can receive process data The program can now be written for the SLC500 0 3 0 0 1747 SDN 13 20 0 3 12 0 1747 SDN 1747 SDN Mov 0002 Move Source 1 38 0 lt Dest 0 3 2 0 lt r Mov Move Source 139 0z Dest 0 1 0 0 lt 0003 01915 In rung 0 DeviceNet communication is once again enabled In rung 1 the strobe bit of device 8 is set in relationship to the input bit 1 3 2 0 from the DeviceNet input module Setting this bit triggers a fieldbus timeout in the inverter and the inv
Download Pdf Manuals
Related Search