UFD11A DeviceNet Fieldbus Interface

Transcription

1 UFD11A DeviceNet Fieldbus Interface Edition 10/2001 Manual / EN

2 SEW-EURODRIVE

3 Contents 1 Unit Design Front view DeviceNet Interface Installation instructions Configuration of the DeviceNet interface Control via DeviceNet with polled I/O Status scan via bit-strobe I/O Parameter setting via DeviceNet Duplicate MAC-ID detection Autosetup Installation and Operation without PC Installation and cabling Setting the inverter parameters (MOVITRAC 07) Autosetup Project planning of the fieldbus master Starting the inverters Installation and Operation with PC Installation and cabling Setting the inverter parameters (MOVITRAC 07) Startup software Project planning of the fieldbus master Starting the inverters Error Responses Fieldbus timeout SBUS timeout Unit error LEDs Power-Up States of the "BUS-FAULT" LED (red) States of the SYS-FAULT LED (red) States of the "MODNET" LED (green/red) States of the "PIO" LED (green/red) States of the "BIO" LED (green/red) States of the "USER" LED (green) DIP Switches Incorrect baud rate Incorrect process data length Operating the Interface List of Errors Statement of Conformance Abbreviations...43 Manual UFD11A DeviceNet Fieldbus Interface 3

4 1 Unit Design 1 Unit Design 1.1 Front view Figure 1: Layout of LEDs, connectors and DIP switches 05104AXX X1 X2 X3 S1 S2 Mod/Net PIO BIO BUS-F SYS-F USER DeviceNet SBus Diagnostics interface DIP switch DIP switch Module/network status State of polled I/O connection State of bit-strobe I/O connection Bus fault System fault Expert mode 4 Manual UFD11A DeviceNet Fieldbus Interface

5 DeviceNet Interface 2 2 DeviceNet Interface 2.1 Installation instructions Assembly Connector pin assignment The unit can be assembled directly onto the wall of a switch cabinet using the preassembled top-hat rail mounting or the four drilled holes integrated in the back of the housing. The spatial arrangement to the equipment that is to be connected (e.g., MOVITRAC 07) is generally open. The maximum line length and the fact that the gateway must be installed at the end or the beginning of the system bus (SBus) must be taken into consideration. For this reason it is recommended taking the spatial aspects into account. Figure 2: Connector pin assignment 05041AXX Fieldbus connector The connection of the fieldbus interface to the DeviceNet system is generally implemented using a shielded twisted-pair cable. Manual UFD11A DeviceNet Fieldbus Interface 5

6 2 DeviceNet Interface Wiring system bus UFD MOVITRAC 07 RS-485+ RS X3: Reference 0V5 5 RS-485- RS X1: System bus System bus ref. System bus high System bus low X2: V+ CAN H DRAIN CAN L V- GND SC11 SC System bus Terminating resistor System bus ref. Outgoing low Outgoing high System bus ref. Incoming low Incoming high S 11 S 12 ON OFF X10: GND SC22 SC21 GND SC12 SC MOVITRAC 07 System bus Terminating resistor System bus ref. Outgoing low Outgoing high System bus ref. Incoming low Incoming high S 11 S 12 ON OFF X10: GND SC22 SC21 GND SC12 SC Figure 3: System bus connection 05095AEN Please note: Use a 2-core twisted and shielded copper cable (data transfer cable with shield consisting of copper braiding). Connect the shield with a wide-area contact at the electronics terminal of MOVITRAC 07 or UFD11A and also connect the shield ends to GND. The cable must meet the following specifications (CAN bus or DeviceNet cables are suitable): Core cross-section 0.75 mm 2 (AWG18) Cable resistance 120 Ω at 1 MHz Capacitance per unit length 40 pf/m (12 pf/ft) at 1 khz The permitted overall cable length is dependent on the specified SBus baud rate: 250 kbaud: 160 m (528 ft) 500 kbaud: 80 m (264 ft) 1000 kbaud: 40 m (132 ft) Connect the system bus terminating resistor (S12 = ON) at the end of the system bus connection. Disconnect the terminating resistor (S12 = OFF) at the other devices. The UFD11A gateway must always be connected either at the beginning or the end of the system bus connection and features a permanently installed terminating resistor. No potential displacement may occur between the units connected with the SBus. Avoid a potential displacement by using appropriate measures, such as connecting the equipment ground with a separate line. Peer-to-peer wiring is not permitted. 6 Manual UFD11A DeviceNet Fieldbus Interface

7 DeviceNet Interface 2 Shielding and routing of bus cables The DeviceNet interface supports the RS-485 communications protocol and requires cable type A specified for DeviceNet in accordance with EN as shielded twistedpair cable for the physical connection. Professional shielding of the bus cables attenuates electrical interference that may occur in industrial environments. The following measures will enable you to obtain the best shielding properties: Tighten the mounting screws on the connectors, modules and equipotential bonding conductors by hand. Use connectors with metal housing or plated housing only. Connect the shielding in the connector with the greatest possible surface area. Place the shielding of the bus conductor on both sides. Do not route signal and bus cables parallel to power cables (motor leads); they must be routed in separate cable conduits. Use metallic, grounded cable racks in industrial environments. Route the signal cable and the corresponding equipotential bonding in close proximity using the shortest way possible. Avoid extending bus lines by means of plug connectors. Route the bus cables closely alongside existing grounding areas. If ground potential fluctuations are present, a compensating current may flow via the shield that is connected on both ends and to the ground potential (PE). In this case, ensure adequate equipotential bonding in accordance with relevant VDE regulations. Bus termination A bus termination is not provided on the UFD electronics. If the UFD module is used as the first or the last device of the DeviceNet branch, an external bus termination is required. We recommend DeviceNet connectors with integrated bus termination that separate the continuing bus in case the bus termination is connected. Manual UFD11A DeviceNet Fieldbus Interface 7

8 2 DeviceNet Interface 2.2 Configuration of the DeviceNet interface General The inverter must be given a specific DP configuration by the DeviceNet to define type and number of input and output data used for the transmission. The operator can control the drives via process data and read or write all parameters of the fieldbus interface via parameter channel. The figure shows a schematic view of the data exchange between automation device, fieldbus interface and an inverter with process data channel and parameter channel. Master Æ MOVITRAC 07 PM DATA PC DATA DeviceNet SBUS PC DATA UFD PM DATA PC DATA PC DATA 50425AXX Figure 4: Data exchange with parameter data (PM DATA) and process data (PC DATA) Process data configuration The UFD DeviceNet fieldbus interface makes for different process data configurations to exchange data between DeviceNet scanner and the UFD. The desired process data configuration must be selected via DIP switches. In addition, the process data length must be entered in bytes in the configuration tool for the scanner (e.g., RSNetWorx). The configurations are guided by the default process data width of three process data words for MOVITRAC 07 or MOVIDRIVE Compact. In the simplest case, three process data words each are transmitted from the controller for each MOVITRAC 07 or other device connected to the UFD. The UFD then distributes these process data words to the individual devices. The parameter channel is used for setting the parameters of the UFD and is passed on to the lower-level stations via explicit messages. The UFD accepts 1 to 24 process data words. 8 Manual UFD11A DeviceNet Fieldbus Interface

9 DeviceNet Interface Control via DeviceNet with polled I/O If more than one inverter is present, the corresponding process data words are added at the end (see figure). The number of process data words per inverter is three words for automatic setup. The PC configuration tool allows for setting process data widths of two words and one word. The following steps should be observed in configuring the fieldbus interface: Add the inverters connected to the SBus in ascending address order with their respective process data width. Example: inverter with address 1 and three words, then inverter with address 2 and three words, then inverter with address 3 and two words, and so forth. O:1.1 O:1.2 O:1.3 O:1.4 O:1.5 O:1.6 O:1.7 O:1.8 O:1.9 PA 1 PA 2 PA 3 PA 1 PA 2 PA 3 PA 1 PA 2 PA 3 MOVITRAC Æ 07 1 MOVITRAC Æ 07 2 MOVITRAC Æ 07 3 PE 1 PE 2 PE 3 PE 1 PE 2 PE 3 PE 1 PE 2 PE 3 I:1.1 I:1.2 I:1.3 I:1.4 I:1.5 I:1.6 I:1.7 I:1.8 I:1.9 Figure 5: Process data routing 50426AXX Manual UFD11A DeviceNet Fieldbus Interface 9

10 2 DeviceNet Interface Network startup with RSNetWorx Figure 6: RSNetWorx 05042AXX The connected devices can be scanned with RSNetWorx network manager. Doubleclicking the icon of the connected device UFD11A opens a diagnostics window which allows for monitoring of important fieldbus parameters and the process data words. Figure 7: Adjusting parameters via RSNetWorx 05043AXX 10 Manual UFD11A DeviceNet Fieldbus Interface

11 DeviceNet Interface 2 The process data width can be set in the I/O defaults register. This value must correspond to the process data width that has been set via DIP switches on the UFD, otherwise the scanner reports an error (77). Figure 8: Setting the process data length in RSNetWorx 05044AXX Next, the data are loaded into the scanner with Übernehmen (Accept). Then start the scanner and generate the scan list. Open the startup window by doubleclicking the scanner. Figure 9: Scan list 05045AXX Manual UFD11A DeviceNet Fieldbus Interface 11

12 2 DeviceNet Interface Add the device SEW Gateway UFD11A to the scan list in the Scan list register. The input/output data must be allocated to the PLC memory area In the input and output registers. The allocation can be carried out via discrete I/O memory area or via M-files (see the description of the PLC). 2.4 Status scan via bit-strobe I/O The status of the UFD can cyclically be scanned via bit-strobe I/O. The length of the process input data for bit-strobe I/O is 2 bytes. The inverter status parameter (index 8310) is mapped to the process input data word by the UFD. The strobe data must be activated in the I/O configuration and the length 2 RX bytes must be set to activate the bit-strobe I/O. Figure 10: Activating the bit-strobe I/Os 05046AXX 12 Manual UFD11A DeviceNet Fieldbus Interface

13 DeviceNet Interface 2 The 2 bytes in the INPUT data must be mapped into the PLC memory. This task is carried out in the INPUT register of the scanner initialization window. Figure 11: Mapping the bit-strobe I/Os 05047AXX 2.5 Parameter setting via DeviceNet Parameter setting of the UFD via RSNetWorx All UFD parameters and all parameters of the inverters connected to the gateway via SBus can be addressed using the RSNetWorx project planning software. In doing so, the parameters are divided into several groups: Table 1: Parameter groups Group SEW parameter channel Device parameters UFD parameters PO monitor PI monitor Meaning/function Access to all parameters via index and address Direct access to the fieldbus parameters of UFD and the devices connected via SBus Direct access to the fieldbus parameters of UFD Direct access to the process output data monitor Direct access to the process input data monitor Manual UFD11A DeviceNet Fieldbus Interface 13

14 2 DeviceNet Interface SEW parameter channel The SEW parameter channel consists of the following access mechanism: Table 2: Parameter group "SEW Parameter Channel" No. Group Parameter Meaning/function 1 SEW Parameter SEW-Param.-Index Index of the parameter used to read/write the data Channel 2 SEW Parameter Channel 3 SEW Parameter Channel SEW-Param.-Address SEW-Read/Write Address of the device from which the data is read/ written (UFD address = 0) Read/write data depending on the address and index set above Parameter setting procedure: 1. Setting the index to be read/written and downloading the index 2. Setting the address of the device and downloading the address 3. Setting the data to be written or reading the data Device parameters All parameters directly connected with the fieldbus communication can be read directly via RSNetWorx. First, the address of the device must be set from which the data are read (UFD = address 0). These parameters are listed in the following table (parameters that can only be read are designated with R = Read-Only in the No. column): Table 3: Parameter group "Device Parameter" No. Group Name Comment 2 SEW param. address Address of the device from which the data are read/written (UFD address = 0) 4R Device parameter Device identification Device identification 5R Device parameter Setpoint source Setpoint source 6R Device parameter Control source Control source 7R Device parameter Setp.descr.PO1 Process output data assignment for PD1 8R Device parameter Setp.descr.PO2 Process output data assignment for PD2 9R Device parameter Setp.descr.PO3 Process output data assignment for PD3 10R Device parameter Act.v.descr. PI1 Process input data assignment for PD1 11R Device parameter Act.v.descr. PI2 Process input data assignment for PD2 12R Device parameter Act.v.descr. PI3 Process input data assignment for PD3 13R Device parameter PD Configuration Process data configuration 18R Device parameter SBus baud rate SBus baud rate 14 Manual UFD11A DeviceNet Fieldbus Interface

15 DeviceNet Interface 2 UFD parameters The parameters that are provided only for the UFD can be read with this group via RSNetWorx. These parameters are listed in the following table (parameters that can only be read are designated with R = Read-Only in the No. column): Table 4: Parameter group "UFD Parameter" No. Group Name Comment 14R UFD Parameter Station address Station address 15R UFD Parameter Baud Rate DeviceNet baud rate 16R UFD Parameter Fieldbus Type Fieldbus type 17R UFD Parameter Timeout Response Timeout response PO monitor The process output data can be viewed using this group. First, the address of the device must be set from which the data is read (UFD = address 0). These parameters are listed in the following table (parameters that can only be read are designated with R = Read-Only in the No. column): Table 5: Parameter group "PO Monitor" No. Group Name Comment 2 SEW Param. Address Address of the device from which the data is read/ written (UFD address = 0) 19R PD monitor PO1 Setpoint Process data PO1 20R PD monitor PO2 Setpoint Process data PO R PD monitor PO24 Setpoint Process data PO24 PI monitor The process input data can be viewed using this group. First, set the address of the device from which the data are read (UFD = address 0). These parameters are listed in the following table (parameters that can only be read are designated with R = Read-Only in the No. column): Table 6: Parameter group "PI Monitor" No. Group Name Comment 2 SEW Param. Address Address of the device from which the data is read/ written (UFD address = 0) 43R PD monitor PI1 Setpoint Process data PI1 44R PD monitor PI2 Setpoint Process data PI R PD monitor PI24 Setpoint Process data PI24 Manual UFD11A DeviceNet Fieldbus Interface 15

16 2 DeviceNet Interface Exchanging explicit messages (parameter data) via register object The register object allows for direct access to all parameters of the UFD and the devices connected via SBus. For this purpose, an explicit message with the following structure must be transmitted: Table 7: Explicit message for the register object Byte offset Function Significance Example MAC- ID Class Service Instance Attribute Index Data Address Low High LSB MSB 01h 10h 07h 02h 04h 70h 20h 09h 00h 00h 00h 00h In the example in Table 7: Data format for the register object, the parameter with 2070h = 8304 will be described with the value 9 = CONTROLWORD1 by the UFD (address 0). Table 8: Register class services Service Coding Meaning Get_Attribut_Single 0x0E Reading the attribute Set_Attribut_Single 0x10 Writing the attribute 2.6 Duplicate MAC-ID detection A "Duplicate MAC-ID Check" is performed to ensure that all stations that are connected to the bus and are DeviceNet-compliant feature a different address. This test is performed after power up and indicated via LEDs. 16 Manual UFD11A DeviceNet Fieldbus Interface

17 Autosetup 3 3 Autosetup The Autosetup function allows the startup of the UFx fieldbus connection without a PC. The function is activated by means of the AS DIP switch. Activating the Autosetup DIP switch causes a single execution of the function. The function can be executed again by switching the DIP switch off and on again. First, the UFx searches the lower-level SBUS for drive inverters and indicates this through brief flashing of the SYS-FLT LED. For this purpose, different SBUS addresses must be set at the drive inverters (P813). We recommend assigning the addresses beginning with address 1 in ascending order based on the arrangement of the inverters in the switch cabinet. The process image on the fieldbus side is expanded by three words for each located drive inverter. If no drive inverter was located, the SYS-FLT LED remains lit. A total of up to eight drive inverters is taken into consideration. The figure shows the process image for three drive inverters with three words each of process output data and process input data. At the conclusion of the search, the UFx cyclically exchanges three process data words with each connected drive inverter. The process output data are fetched by the fieldbus, divided into blocks of three and transmitted. The process input data are read by the drive inverters, grouped and transmitted to the fieldbus master. Autosetup must be executed only once. The detected configuration is saved in nonvolatile memory. See the chapter on Installation and Operation without PC. Caution: Please execute autosetup again if you change the process data assignment of the drive inverters connected to the UFP; the UFP stores these values only once during autosetup. At the same time, the process data allocations of the connected drive inverters may not be changed dynamically after autosetup, for example by means of an IPOS program. If these facts are not taken into consideration, an error response may not be issued in case of a fieldbus timeout. Manual UFD11A DeviceNet Fieldbus Interface 17

18 3 Autosetup Figure 12: Data exchange of DeviceNet scanner UFD inverter 05048AXX 18 Manual UFD11A DeviceNet Fieldbus Interface

19 Installation and Operation without PC 4 4 Installation and Operation without PC 4.1 Installation and cabling See the chapter on DeviceNet Interface for installation notes. 4.2 Setting the inverter parameters (MOVITRAC 07) Connect the voltage supply for the UFx and all connected inverters. Set an individual SBus address (P813) at the inverters. Recommendation: Address setting beginning with address 1 in ascending order based on the arrangement of the inverters in the switch cabinet. Address 0 should not be assigned since it is used by the UFx. Set the setpoint source (P100) to SBus (value 10 for MC07). Set the control source (P101) to SBus (value 3 for MC07). Set the terminal assignments of the binary inputs (P60 ). Binary inputs that are not in use should be assigned no function. For safety purposes, the inverter must be enabled on the terminal side. The corresponding device documentation should be observed for this purpose. The P60- parameter can be set to 0, resulting in the following assignment: DI01 CW/Stop(wired to 24 V, CW direction of rotation enabled) DI02 CCW/Stop(wired to 24 V, CCW direction of rotation enabled) DI03 F.Setp.Ums.(not wired) DI04 n11/n21(not wired) DI05 n12/n22(not wired) Set the SBus timeout value (P815) to a value unequal 0, such as 1 s, to activate monitoring. If necessary, change the default values of the process data assignments (P870 P875). This step must be performed before executing autosetup (see the chapter on Autosetup ). 4.3 Autosetup Activate the Autosetup function via the DIP switch of the UFx. The function is active as long as the SYS-FLT LED flashes briefly followed by a long pause. If there is at least one detected inverter, the LED will extinguish. Autosetup can be reactivated by setting the DIP switch to off and on again. The SYS-FLT LED remains lit after autosetup if no inverter is detected. In this case, check the cabling of the SBus, the terminating resistors of the SBus and the voltage supply of the inverter. Manual UFD11A DeviceNet Fieldbus Interface 19

20 4 Installation and Operation without PC 4.4 Project planning of the fieldbus master For the project planning, set an individual DeviceNet address (MACID) via the DIP switches of the UFD. The DeviceNet address is set in binary form. Figure 13: Setting the DeviceNet-Mac ID on S2 / F1, F2 = reserved, OFF position 05050AXX A change of the DeviceNet address becomes effective only after switching the UFD off and on again. The DeviceNet scanner of the controller is configured with the help of the UFD11A.ESD file. The UFD is addressed under the specified DeviceNet address. The number of process data words with which the fieldbus master addresses the UFD is dependent on the number of connected inverters. The process data width for one inverter is three words. If more than one inverter is present, three words should be planned for each inverter, i.e. you must configure nine words for three MC07. Example for RSNetWorx: Install the UFD11A.EDS file in the RSNetWorx software. Perform a SingleScan to detect the devices online. Set the process data length (in bytes) in the scanner. Save the configuration. Expand your application program by the data exchange with the UFD. After saving the project, loading it in the PLC and starting the PLC program, the BUS-FLT LED of the UFD should extinguish. If this is not the case, please check cabling and terminating resistors of the DeviceNet and the project planning, especially the process data configuration. 20 Manual UFD11A DeviceNet Fieldbus Interface

21 Installation and Operation without PC Starting the inverters Up to eight inverters can be operated on the DeviceNet using one UFD. The DeviceNet scanner and the UFD exchange setpoints and actual values for all inverters connected to the UFD in related data packages. It is important for you to know which inverter is located at which position of the data package (process image). The following figure shows the relationship: Figure 14: Data exchange of DeviceNet scan UFD inverter 05096AXX The inverters are enabled by writing the value 0006h to the corresponding control word 1. The speed setpoint can be specified with the next word. The setpoint is scaled with 0.2 1/min per digit. Manual UFD11A DeviceNet Fieldbus Interface 21

22 5 Installation and Operation with PC 5 Installation and Operation with PC 5.1 Installation and cabling See the chapter on DeviceNet Interface for installation notes. The UFD features a 4-pole phone jack on the front. The UWS21A option, part number , establishes the connection to a COM interface of your PC. For this purpose, connect the desired COM of the PC with the UWS21A using the provided serial cable. The UWS21A is connected with the UFD via the provided phone cable. 5.2 Setting the inverter parameters (MOVITRAC 07) Connect the voltage supply for the UFx and all connected inverters. Set an individual SBus address (P813) at the inverters. Recommendation: Address setting beginning with address 1 in ascending order based on the arrangement of the inverters in the switch cabinet.. Do not assign address 0, since it is used by the UFx! 5.3 Startup software Install the Movitools software package on your PC. Start the software. Select the COM to which the UFD is connected and press the Update button. The UFD should appear at address 0 and the connected inverters at the following addresses. If the window does not show an entry, please check the COM interface and the connection via UWS21. Please check the SBus cabling und terminating resistors if only the UFD displays as an entry in the window. Select the UFD and call up the startup software for the gateway fieldbus. Select the Reconfigure fieldbus node menu item. Select your project path and project name. > Next Press the Update button. All UFDs connected to the inverter should display now. The configuration can be customized using the buttons Insert, Change and Delete. > Next 22 Manual UFD11A DeviceNet Fieldbus Interface

23 Installation and Operation with PC 5 Press the Autoconfiguration button. The process image for the UFD now displays in your controller. The process data width is shown at the bottom. This value is important for the project planning of the fieldbus master. > Next Save the project data and press the Download button. If the download should not work, the DIP switch may be set to AUTOSETUP. Autosetup must be deactivated for the PC project planning. The data exchanged between fieldbus master and UFD can be viewed with the process data monitor. Enabling on the terminal side is required for control of the inverters via fieldbus. You have already connected the terminals DI01 and DI02 (MC07). Select the first inverter with address 1 in the Connected devices window and start "Shell" to check the terminal assignment. The terminal assignment should be set as follows: Figure 15: Binary input terminals 05049AEN Repeat the previous step for all inverters that display in the Connected devices window. 5.4 Project planning of the fieldbus master Set an individual DeviceNet address (MACID) via the DIP switches of the UFD for the project planning. The DeviceNet address is set in binary form. Figure 16: Setting the DeviceNet-Mac ID at S2 / F1, F2 = reserved, OFF position 05050AXX A change of the DeviceNet address becomes effective only after switching the UFP off and on again. Manual UFD11A DeviceNet Fieldbus Interface 23

24 5 Installation and Operation with PC The DeviceNet scanner of the controller is configured with the help of the UFD11A.ESD file. The UFD is addressed under the specified DeviceNet address. The number of process data words with which the fieldbus master addresses the UFD is dependent on the number of connected inverters. The process data width for one inverter is three words. If more than one inverter is present, three words should be planned for each inverter, i.e. you must configure nine words for three MC07. Example for RSNetWorx: Install the UFD11A.EDS file in the RSNetWorx software. Perform a SingleScan to detect the devices online. Set the process data length (in bytes) in the scanner. Save the configuration. Expand your application program by the data exchange with the UFD. After saving the project, loading it in the PLC and starting the PLC program, the BUS-FLT LED of the UFD should extinguish. If this is not the case, please check cabling and terminating resistors of the DeviceNet and the project planning, especially the process data configuration. 5.5 Starting the inverters Up to eight inverters can be operated on the DeviceNet using one UFD. The DeviceNet scanner and the UFD exchange setpoints and actual values for all inverters connected to the UFD in related data packages. It is important for you to know which inverter is located at which position of the data package (process image). The process data monitor shows the relationship in the project planning of the fieldbus gateway. The inverters are enabled by writing the value 0006h to the corresponding control word 1. Note that the low byte 06h is loacted at the lower byte address and the high byte 00h at the higher address in case of a byte orientation of the memory. The speed setpoint is scaled with 0.2 1/min per digit. Caution: It is not permitted to change the process data assignments of the inverters connected to the UFD after startup using MT-Gateway. If this fact is not taken into consideration, an error response may not be issued in case of a fieldbus timeout. 24 Manual UFD11A DeviceNet Fieldbus Interface

25 Error Responses 6 6 Error Responses 6.1 Fieldbus timeout A fieldbus timeout response will be triggered at the UFx in case the fieldbus master is switched off or if there is an open circuit in the fieldbus cabling. The connected drive inverters are switched to a safe state by sending zeros to the process output data which corresponds to a rapid stop on control word 1. The fieldbus timeout error resets itself, i.e. the drive inverters receive once again the current process output data from the controller after the fieldbus communication has been restarted. This error response can be deactivated via P831 of the UFx. 6.2 SBUS timeout If one or several drive inverters at the SBUS can no longer be addressed by the UFx, the UFx displays the error code 91 System Fault on status word1 of the respective drive inverter. The SYS-FLT LED lights up, and the error is also indicated via the diagnostics interface. It is necessary to set SBUS timeout time P815 at the inverter unequal 0 for the drive inverter to stop. The error resets itself at the UFx, i.e. the current process data are replaced immediately after restarting the communication. 6.3 Unit error The UFx gateways detect a series of hardware defects and lock out subsequently. The exact error responses and remedial measures can be found in the error list. A hardware defect causes error 91 to be displayed on the process input data of the fieldbus in status words 1 of all drive inverters. The SYS-FLT LED at the UFx flashes regularly. The exact error code is displayed at the diagnostics interface in the status of the UFx using Movitools. Manual UFD11A DeviceNet Fieldbus Interface 25

26 7 LEDs 7 LEDs The DeviceNet interface UFD comprises six LEDs for diagnostic purposes: MODNET LED (green/red) indicates the module/network status of the UFD, PIO LED (green/red) indicates the status of the polled I/O connection, BIO LED (green/red) indicates the status of the bit-strobe I/O connection, BUS-FAULT LED (red) indicates bus errors, SYS-FAULT LED (red) indicates system errors and operating states of the UFD, USER LED (green) for application-specific diagnostics in expert mode. 7.1 Power-Up All LEDs are tested after the unit is switched on. The LEDs are switched on in the following sequence as part of the test: Table 9: Power-up LED test Time/LED MNS PIO BIO BUS-Fault SYS-Fault User 0 ms green off off off off off 250 ms red off off off off off 500 ms off green off off off off 750 ms off red off off off off 1000 ms off off green off off off 1250 ms off off red off off off 1500 ms off off off red off off 1750 ms off off off off red off 2000 ms off off off off off green 7.2 States of the "BUS-FAULT" LED (red) The BUS-FAULT LED displays the physical state of the bus node. The functionality is described in the following table, States of the Bus-Fault LED. Table 10: States of the Bus-Fault LED Status LED Meaning Error Active State Off The number of bus errors is within the normal range (Error- Active-State). DUPMAC Test Flashes red (125 ms cycle) The unit is performing a DUP-MAC check and cannot send any messages because no other stations are connected to the bus. (Error-Passive-State) Error-Passive-State Flashes red (1 s cycle) The number of physical bus errors is too high. No more error messages are actively written to the bus. (Error-Passive-State) Bus-Off State Red The number of physical errors continued to grow despite a switch to the Error-Passive-State. Access to the bus is deactivated (BusOff-State) 26 Manual UFD11A DeviceNet Fieldbus Interface

27 LEDs States of the SYS-FAULT LED (red) Table 11: States of the SYS-Fault LED OFF FLASHES briefly once followed by a long pause FLASHES regularly ON Normal operating state. The UFD is exchanging data with the connected inverters. Requirement: "RUN" LED is on. Autosetup is selected via DIP switches and UFD is currently configuring itself. If this state lasts more than one minute, switch Autosetup off and on again. Replace the module if Autosetup does not exit itself again repeatedly. The UFD is in an error state. If the UFD was started with the Autosetup DIP switch, switch the UFD off and on again. If the LED is now on, restart Autosetup by switching the DIP switch off and on again. If the UFD was started using Movitools, the status window displays an error message. Please check under the corresponding error description. The UFD exchanges no data with the connected inverters. It was not configured or the connected inverters do not respond. Repeat the configuration of the UFD. If the UFD was started with Autosetup, switch the Autosetup DIP switch off and on again. If the LED is still on after Autosetup, check the cabling and terminating resistors of the SBus as well as the voltage supply of the inverter. If the UFD was started using Movitools, select the Update button in the manager. All inverters should display in the Connected devices window. If this is not the case, check the cabling and terminating resistors of the SBus as well as the voltage supply of the inverter. If necessary, repeat the configuration of the UFD with Movitools. 7.4 States of the "MODNET" LED (green/red) The range of functions of the Mod/Net LED (module/network status LED) is defined in the DeviceNet specifications. The following table describes this functionality. Table 12: Status engine of Mod/Net LED Status LED Meaning Not switched on / offline On-line and in operational mode On-line, operational mode and connected Minor fault or connection timeout Critical fault or critical link failure Off Flashes green (1 s cycle) Green Flashes red (1 s cycle) Red Unit is off-line Unit is performing DUP-MAC check Unit is switched off The unit is on-line and no connection has been established DUP-MAC check was performed successfully A connection has not yet been established with a master Missing, incorrect or incomplete configuration Connection has been established with a master Connection is active (Established State) A correctable error has occurred Polled I/O or/and bit-strobe I/O connections are in timeout state A correctable error has occurred in the unit A non-correctable error has occurred DUP-MAC check has detected an error Manual UFD11A DeviceNet Fieldbus Interface 27

28 7 LEDs 7.5 States of the "PIO" LED (green/red) The PIO LED checks the polled I/O connection (process data channel). The functionality is described in the following table. Table 13: Status engine of PIO-LED Status LED Meaning DUP-MAC check Flashes green (125 ms cycle) Unit is performing DUP-MAC check Not switched on / offline but not DUP- MAC check On-line and in operational mode On-line, operational mode and connected Minor fault or connection timeout Critical fault or critical link failure Off Flashes green (1 s cycle) Green Flashes red (1 s cycle) Red Unit is off-line Unit is switched off Unit is on-line DUP-MAC check was performed successfully A PIO connection is being established with a master (Configuring State) Missing, incorrect or incomplete configuration On-line A PIO connection has been established (Established State) A correctable error has occurred Polled I/O connection is in timeout state A non-correctable error has occurred DUP-MAC check has detected an error 7.6 States of the "BIO" LED (green/red) The BIO LED checks the bit-strobe I/O connection. The functionality is described in the following table. Table 14: Status engine of BIO-LED Status LED Meaning DUP-MAC check Flashes green (125 ms cycle) Unit is performing DUP-MAC check Not switched on / offline but not DUP- MAC check On-line and in operational mode On-line, operational mode and connected Minor fault or connection timeout Critical fault or critical link failure Off Flashes green (1 s cycle) Green Flashes red (1 s cycle) Red Unit is off-line Unit is switched off Unit is on-line DUP-MAC check was performed successfully A BIO connection is being established with a master (Configuring State) Missing, incorrect, or incomplete configuration On-line A BIO connection has been established (Established State) A correctable error has occurred Bit-strobe I/O connection is in timeout state A non-correctable error has occurred DUP-MAC check has detected an error 7.7 States of the "USER" LED (green) OFF Normal operating state. The "USER" LED is reserved for expert mode. 28 Manual UFD11A DeviceNet Fieldbus Interface

29 DIP Switches 8 8 DIP Switches 05307AXX Figure 17: DIP switch assignment Table 15: Baud rate Baud rate DR0 DR1 125 kbaud kbaud kbaud 1 0 Reserved 1 1 Table 16: Process data length Process data length PD4 PD3 PD2 PD1 PD Manual UFD11A DeviceNet Fieldbus Interface 29

30 8 DIP Switches Table 16: Process data length Process data length PD4 PD3 PD2 PD1 PD Reserved Reserved AUTO SETUP: See the chapter on Installation and Operation without PC. F1: Function 1 reserved, set to "Off" F2: Function 2 reserved, set to "Off" ID0..5: MAC-ID of the module (bus address) If an incorrect baud rate or an incorrect process data length is entered, the device remains in the initialization state until the DIP switch assignments have been corrected. 8.1 Incorrect baud rate The PIO-LED flashes red steadily. As soon as you enter a correct baud rate, the initialization is carried out and the UFD switches to the on-line state. 8.2 Incorrect process data length The BIO-LED flashes red steadily. As soon as you enter a correct process data length, the initialization is carried out and the UFD switches to the on-line state. 30 Manual UFD11A DeviceNet Fieldbus Interface

31 Operating the Interface 9 9 Operating the Interface How do I get "online"? All stations recognized at the system bus, inverter and gateway, will be displayed in the MOVITOOLS manager following an "Update." You can operate the status bar, Shell, Assembler and Compiler on all connected inverters via the gateway. MT-Gateway supports project planning and startup of an UFD fieldbus node. A bus configuration can be projected offline or read online from the UFD and processed according to need. Before you start the MT-Gateway session, it may be advisable to ensure that the hardware Autosetup has been switched off (DIP switch 8 in Off setting). Prior to startup, make sure that there will be no danger to persons or system components in case of a bus error in the fieldbus or system bus. Project planning / Startup Example Two modes are available for project planning/startup. Analogous to the automatic hardware setup, the autoconfiguration mode assigns three process output and input data to each station starting with the lowest system bus address. Automatic configuration: Three stations with addresses 10, 11 and 12 => 9 PDs Fig. 18: Example automatic configuration 05037AXX The process data assignment can be freely configured in expert mode. The assignment can be done graphically (drag-and-drop). Manual UFD11A DeviceNet Fieldbus Interface 31

32 9 Operating the Interface Example Participant 10, PO1 has been configured Fig. 19: Participant 10, PO1 has been configured 05038AEN The package / bundle of process output data can look as follows: PO1..PO3 all receive three stations (e.g. control word 1, speed setpoint, ramp). The master receives 1PD (e.g. status word 2) from each inverter as process input data. Six process output and input data words will be saved in the master compared to the automatic setup option. Avoid multiple assignment of process input data since it makes no sense. Fig. 20: Multiple assignment 05039AXX 32 Manual UFD11A DeviceNet Fieldbus Interface

33 List of Errors List of Errors Error code Designation Reaction Cause Action 10 IPOS ILLOP IPOS program stopped 17 Stack Overflow SBus communication stopped 18 Stack Underflow SBus communication stopped 19 NMI SBus communication stopped 20 Undefined Opcode SBus communication stopped 21 Protection Fault SBus communication stopped 22 Illegal Word Operand Access 23 Illegal Instruction Access 24 Illegal External Bus Access SBus communication stopped SBus communication stopped SBus communication stopped 25 EEPROM SBus communication stopped 28 Fieldbus Timeout Connected inverters stopped (control word = 0) 32 IPOS Index Overflow IPOS program stopped 37 Watchdog error SBus communication stopped 45 Initialization error SBus communication stopped 77 Invalid IPOS control value IPOS program stopped Error in IPOS program, more information via IPOS variable H469 Inverter electronics is faulted, possibly due to EMC influence " " " " " " " " " " " " " " Error while accessing EEPROM No communication took place between master and slave within the projected response monitoring time. Programming principles violated, resulting in system stack overflow. Error during execution of system software Error after self-test during reset An attempt was made to set an invalid automatic mode (via external control). 91 System fault None Please observe the red SYS-FLT LED of the UFx. If this LED is on, one or several stations on the SBus could not be addressed within the timeout interval. If the red SYS-FLT LED flashes, the UFx itself is in an error state. In this case, error 91 was reported to the controller via fieldbus only. Correct, load and reset IPOS program Check ground connections and shieldings and correct, if necessary. If this error occurs again, contact SEW service for support. Activate factory settings, perform reset and set parameters for UFx again. If the error occurs again, contact SEW service for support. - Check the master communications routine; - Extend the fieldbus timeout interval (response monitoring) in the master project planning or deactivate monitoring Check and correct IPOS application program Check ground connections and shieldings and correct, if necessary. If this error occurs again, contact SEW service for support. Check DIP switches F1 and F2; they must be set to "Off." Perform a reset. If the error occurs again, contact SEW service for support. Check write values of external control Check voltage supply and SBus cabling; check SBus terminating resistors. If the UFx was projected with the PC, check the project planning. Switch UFx off and on again. If the error remains, query the error via diagnostics interface and perform the action described in this table. Manual UFD11A DeviceNet Fieldbus Interface 33

34 11 Statement of Conformance 11 Statement of Conformance 34 Manual UFD11A DeviceNet Fieldbus Interface

35 Statement of Conformance 11 Manual UFD11A DeviceNet Fieldbus Interface 35

36 11 Statement of Conformance 36 Manual UFD11A DeviceNet Fieldbus Interface

37 Statement of Conformance 11 Manual UFD11A DeviceNet Fieldbus Interface 37

38 11 Statement of Conformance 38 Manual UFD11A DeviceNet Fieldbus Interface

39 Statement of Conformance 11 Manual UFD11A DeviceNet Fieldbus Interface 39

40 11 Statement of Conformance 40 Manual UFD11A DeviceNet Fieldbus Interface

41 Statement of Conformance 11 Manual UFD11A DeviceNet Fieldbus Interface 41

42 11 Statement of Conformance 42 Manual UFD11A DeviceNet Fieldbus Interface

43 Abbreviations Abbreviations Abbreviation Allocate Attribute BIO - Bit-strobe I/O Class Device-Net scanner DUP-MAC check Explicit message body Explicit message Get_Attribute_Single Instance MAC-ID M-file Mod/Net Node-ID PIO - Polled I/O Release Reset Rung Service Set_Attribute_Single SLC500 Description Provides a service for setting up a connection. Attribute of an object class or instance. Describes the characteristics of the object class or instance more fully. All stations can be addressed with a broadcast message. The addressed stations respond with the process input data. DeviceNet object class. Plug-in module for the Allen Bradley PLC which connects the PLC fieldbus to the peripheral devices. Duplicate MAC-ID test. Includes the class no., instance no., attribute no. and the data. Parameter data message; assists in addressing the DeviceNet objects. Read service for a parameter. Instance of an object class. Divides the object classes into additional subgroups. Media Access Control identifier: node address of the device. Provides the data range between the PLC and the scanner module. Module/network Node address = MAC-ID Process data channel of DeviceNet; allows process output data to be sent and process input data to be received. Provides a service for dropping a connection. Provides a service for resetting an error. SLC500 program line Service performed via bus, e.g. read service, write service, etc. Write service for a parameter. Allen Bradley PLC Manual UFD11A DeviceNet Fieldbus Interface 43

44 SEW-EURODRIVE GmbH & Co P.O. Box 3023 D Bruchsal/Germany Phone Fax