Micromaster Drive On Rockwell ControlLogix v10 en

Application about Communication
Integration of a MicroMaster Drive with Rockwell ControlLogix using DeviceNet

Third-Party Integration
Warranty, liability and support
MicroMaster DeviceNet Integration Note
Item-Number: 32989737
The application examples are not binding and do not claim to be complete regarding the circuits shown, equipping and any eventuality. The application examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible in ensuring that the described products are correctly used. These application examples do not relieve you of the responsibility in safely and professionally using, installing, operating and servicing equipment. When using these application examples, you recognize that Siemens cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these application examples at any time without prior notice. If there are any deviations between the recommendations provided in these application examples and other Siemens publications - e.g. Catalogs - then the contents of the other documents have priority.
Copyright Siemens AG 2009 All rights reserved 32989737_Micromaster_Drive_on_Rockwell_ControlLogix_v10_en.doc
Warranty, liability and support

We do not accept any liability for the information contained in this document. Any claims against us - based on whatever legal reason - resulting from the use of the examples, information, programs, engineering and performance data etc., described in this application example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act (Produkthaftungsgesetz), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract (wesentliche Vertragspflichten). However, claims arising from a breach of a condition which goes to the root of the contract shall be limited to the foreseeable damage which is intrinsic to the contract, unless caused by intent or gross negligence or based on mandatory liability for injury of life, body or health The above provisions does not imply a change in the burden of proof to your detriment. Copyright 2007 Siemens A&D. It is not permissible to transfer or copy these application examples or excerpts of them without first having prior authorization from Siemens A&D in writing. For questions about this document please use the following e-mail address: mailto:csweb@ad.siemens.de
Version V1.1
Issue 10.01.2009
2/52
Foreword
MicroMaster DeviceNet Integration
Foreword
Objective of the application Siemens designs and sells automation products to meet the needs of customers around the globe. It is common to find automation equipment from a multitude of vendors in plants around the world. In order to meet the automation and integration needs of these customers, Siemens provides a variety of communication options for its products to facilitate integration with products from various vendors. This application shows how to integrate a MICROMASTER drive with a Rockwell Allen Bradley ControlLogix controller using the DeviceNet protocol. Main contents of this application
This application deals with the following key elements: Delimitation This application does not include a complete description of the Rockwell configuration and programming tools nor does it provide a complete description of the MICROMASTER drive capabilities. Details of these tools and equipment should be obtained from appropriate technical training sources. Structure of the document The documentation of this application is divided into the following main sections.
Section Application Example Description This section contains a general overview of the application example. It also provides an overview of the development architecture. This section provides functional details of the hardware and software components used in the application example. This section provides a step-by-step description of the integration and test processes. Concepts and known pitfalls for each step are listed. This section provides a list of video clip examples that can be viewed to assist the reader in understanding the concepts that have been presented.
Configuration for Cyclic Data Exchange Reading and Writing Parameter Data Diagnostics
Establishing Communications Configuration Steps
Appendix
Version V1.1
Issue 10.01.2009
3/52
Foreword
Reference to Automation and Drives Service & Support This entry is from the internet application portal of Automation and Drives Service & Support. Clicking the link below directly displays the download page of this document. http://support.automation.siemens.com/WW/view/en/32989737
Version V1.1
Issue 10.01.2009
4/52
Foreword
Table of Contents
Table of Contents ......................................................................................................... 5 Application Description ............................................................................................... 7 1 1.1 1.2 2 2.1 2.2 2.3 2.4 MicroMaster DeviceNet Integration............................................................... 7 Overview........................................................................................................... 7 Requirements ................................................................................................... 7 Establishing Communications ...................................................................... 8 Overview........................................................................................................... 8 Configuration Activities ..................................................................................... 8 Alternative solutions ..................................................................................... 9 Required hardware and software components ............................................... 10 Verification ...................................................................................................... 12
Configuration and Operation of the Application ..................................................... 13 3 3.1 3.2 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6 3.3.7 3.3.8 3.3.9 3.3.10 3.3.11 3.3.12 3.3.13 3.3.14 3.3.15 3.3.16 3.3.17 3.3.18 Configuration of the DeviceNet communication........................................ 13 MicroMaster Setup.......................................................................................... 13 Rockwell ControlLogix Configuration .............................................................. 14 Configuration Steps ........................................................................................ 14 RSLinx Communication Configuration ............................................................ 14 Create a new RSLogix 5000 Project............................................................... 18 Configure DeviceNet Module.......................................................................... 19 Select Communications Path to Controller ..................................................... 20 Create DeviceNet Configuration File .............................................................. 22 Install the Micromaster EDS File .................................................................... 24 Browse DeviceNet Network for Nodes ........................................................... 27 Configure and Download DeviceNet Nodes ................................................... 29 Save and Exit the RSNetworx ........................................................................ 34 Manually Set DeviceNet Scanner to Run ....................................................... 35 Manually Command Motor.............................................................................. 37 Diagnostic Information .................................................................................... 38 Setting DeviceNet Scanner to Run with Logic ................................................ 40 Create Data Type for Data Buffer ................................................................... 40 Create Tags for Reading and Writing PKWs .................................................. 41 Create Logic for Reading PKWs..................................................................... 43 Create Logic for Writing PKWs ....................................................................... 48 Conclusion ...................................................................................................... 49
Appendix ..................................................................................................................... 50 4 5 Flash Animations.......................................................................................... 50 Internet links ................................................................................................. 51
Version V1.1
Issue 10.01.2009
5/52
Foreword
History ........................................................................................................... 52
Version V1.1
Issue 10.01.2009
6/52
Application Description MicroMaster DeviceNet Integration

MicroMaster DeviceNet Integration Item-Number: 32989737
Application Description
Content This application example provides step-by-step instructions for configuring a MicroMaster drive to be controlled from a Rockwell ControlLogix controller using a DeviceNet network. Animations of the individual configuration steps necessary are also included.
1
1.1

Overview
Introduction
Siemens provides a DeviceNet communications card for certain Master Drive products. This application note provides integration details to connect the Master Drives to the Rockwell ControlLogix platform. The integration covers both Process Data (PZD) transfers and Parameter (PKW) transfers. Overview The figure below provides an overview of the desired configuration.
Figure 1-1
Rockwell (Allen Bradley) ControlLogix Controller
DeviceNet
DeviceNetCard
Siemens AG Master Drives
1.2
Requirements
The integration solution must provide the read/write functionality for both PZD and PKW values from a Rockwell Controllogix Controller.
Version V1.1
Issue 10.01.2009
7/52
Application Description Establishing Communications

Establishing Communications
Specific hardware and software items from both vendors are required to establish the DeviceNet communications.
2.1
Overview
Configuration Architecture In order to integrate the Micromaster with the ControlLogix Controller, a DeviceNet Scanner module is required in the ControlLogix platform and a DeviceNet communications board (CB) is required in the MicroMaster. Additionally, specific configuration software is required. The following figure schematically shows the major components of the solution:
Figure 2-1
PG (for configuration) ControlLogix Controller MicroMaster 440 FD (with DeviceNet module) Motor
RS 232 Serial connection (DF1 protocol)
DeviceNet
Power
Configuration Figure 2-1 contains an engineering workstation (PG) on which the Rockwell RSLogix 5000 configuration software RS Linx is running. The configuration software will communicate with the ControlLogix Controller using the DF1 communications protocol through a serial port of the PG. The MicroMaster Basic Operating Panel (BOP) is all that is required to configure the MicroMaster drive.
2.2
Configuration Activities
The following activities must occur in order to establish the DeviceNet communications: 1. Communications must be established between the engineering workstation and the ControlLogix Controller 2. The hardware must be configured correctly in the ControlLogix Controller.
Version V1.1
Issue 10.01.2009
8/52

3. The MicroMaster Electronic Data Sheet (EDS) file must be added to the Device Catalog of the Rockwell DeviceNet configuration software. 4. The DeviceNet network must be configured and downloaded to the DeviceNet Scanner Module. 5. The DeviceNet Scanner Module must be placed in the Run Mode. 6. Testing must be performed to verify cyclic communications (PZD data). 7. Logic must be programmed in the ControlLogix Controller to lock the DeviceNet Scanner in Run Mode. 8. Logic must be programmed in the ControlLogix Controller to read PKW values. 9. The PKW read logic must be tested.
10. Logic must be programmed in the ControlLogix Controller to write PKW values. 11. The PKW write logic must be tested.
Advantage to Customers This solution provides existing Rockwell customers with the opportunity to use the Siemens MicroMaster drive. Alternative solutions The Siemens Automation Customer Support portal offers a number of other suggestions to connect SIMATIC components to Allen-Bradley/Rockwell networks. For more details, see ref. \4\.
Version V1.1
Issue 10.01.2009
9/52

2.3
Required hardware and software components

Table 2-1
Hardware Components
Component ControlLogix 4-slot Chassis ControlLogix Power Supply No. 1 1 1756-A4 1756-PA75 MLFB Note Any suitable chassis can be used. Any ControlLogix power supply suitable for the selected chassis and power source can be used. Any suitable Controller (CPU) can be used.
ControlLogix Controller (CPU)

1 1 1
1756-L55 1756-DNB
ControlLogix DeviceNet Scanner DeviceNet Cable
Refer to Siemens document DeviceNet Option Module Operating Instructions (6SE6400-5BC000BP0) Chapter 4 for cable requirements Siemens Simatic-TI programming cable 2601090-0001C or an industry standard null modem RS232 cable will work. 6SE6440-2AB11-2AA1 Any Master drive with a DeviceNet communication board can be used. Any means of configuring PKWs can be used.
Communications cable (between the engineering workstation and the ControlLogix Controller) Siemens MicroMaster 440 Drive Siemens MicroMaster 4 Basic Operating Panel (BOP) Siemens MicroMaster DNM DeviceNet Communications Option Module Siemens Motor
6SE6400-0BP00-0AA0
6SE6400-1DN00-0AA0
1LA2060-2AA10
Any motor suitable for the Master drive can be used.
Version V1.1
Issue 10.01.2009
10/52

Software Components
Table 2-2
Component Rockwell RSLinx Classic Lite communications software RSLogix 5000 Programming Software MicroMaster Electronic Data Sheet (EDS) file: MM4v1-1.eds
No. 1
Version V2.50.00.20
Note Any version may be used as long as it supports communications to the DeviceNet network. Any version that supports the hardware components (CPU and DeviceNet Scanner) can be used. Used the EDS file for the specific DeviceNet communications board that is used.
V15.01.00
V1.1
Example Files and Projects The following list includes all files and projects used in this application example.
Table 2-3
Component MicroMaster Drive on Rockwell ControlLogix.doc MicroMaster DeviceNet communications board (CB) manual. <BID-Nr>_PLC_Files.zip This document.
Note
cf. \3\ in the appendix Internet links
RSLogix5000 sample project (MicroMaster_DeviceNet_Demo.ACD), RSLogix5000 sample DeviceNet configuration file (MicroMasterDeviceNetDemo.dnt), and the MicroMaster EDS file (MM4v1-2.eds). The configuration movie clips listed in the Appendix of this document.
<BIDNr>_MicroMasterConfigAVIs.zi p
Version V1.1
Issue 10.01.2009
11/52

2.4
Verification
Verification testing is performed with the configuration steps.
Version V1.1
Issue 10.01.2009
12/52
Configuration and Operation of the Application Configuration of the DeviceNet communication

Configuration and Operation of the Application

Content This section describes the configuration process for the DeviceNet communications.
Configuration of the DeviceNet communication

Before beginning the ControlLogix configuration and programming, the Micromaster drive should be configured for DeviceNet communications. This application example presumes that the reader is familiar with the Micromaster product and can set the PKWs to the values that are provided. Likewise, the Rockwell ControlLogix hardware must be assembled in accordance with the slot assignments provided to match the sample project.
3.1
MicroMaster Setup
Use the MicroMaster 440 Basic Operator Panel (BOP) to configure the drive for the motor that is being used. Set the following parameters on the drive for the DeviceNet communications.1
Table 3-1
Parameter P0700.0 P0700.1 P0700.2 P0719.0 P0719.1 P0719.2 P0918 P0927 P1000.0 P1000.1
1
Value 6 2 2 0 0 0 3 255 6 2
Comment DeviceNet card (CB on COM link) Terminal Terminal Binector/Connector (BICO) functionality Binector/Connector (BICO) functionality Binector/Connector (BICO) functionality Default All bits set DeviceNet card (CB on COM link) Analog setpoint
Select digital command source:
Control/Setpoint source:
Network node address (MAC ID): Interface for parameter modification: Select digital command dource:
Refer to Siemens document DeviceNet Option Module Operating Instructions (6SE64005BC00-0BP0), Chapter 5 for more detailed information.
Version V1.1
Issue 10.01.2009
13/52

MicroMaster DeviceNet Integration Parameter P1000.2 P2040 P2041.00 P2041.01 P2041.02 P2041.02
Item-Number: 32989737 Comment
Value 2 >0 0 0 0 0 52 21 0 0 1 0 0 0 Analog setpoint Yes Default (4 PZD input words) Default (4 PZD output words) Default (125 kbps)
Communication failure creates fault on drive? Number of PZD input words: Number of PZD output words: Baudrate on the DeviceNet: Diagnostics mode: Default (use standard diagnostics) Actual status Actual frequency Binary input values Binary input values Actual status Actual frequency Binary input values Binary input values Status registers transmitted on DeviceNet: P2051.0 P2051.1 P2051.2 P2051.3 r2050.0 r2050.1 r2050.2 r2050.3
Commands received from DeviceNet:
3.2
Rockwell ControlLogix Configuration

The Rockwell ControlLogix should be assembled with the chassis and power supply. The following configuration must be used:
Table 3-2
Slot 0 1
Component Controller (CPU) DeviceNet Scanner
3.3
3.3.1
Configuration Steps
RSLinx Communication Configuration RSLinx is Rockwell Automations communication component with which the ControlLogix controller is configured and programmed. In this example application RSLinx is running the DF1 protocol via the serial port of the
Version V1.1
Issue 10.01.2009
14/52

computer. RSLinx runs as a service on the computer, so it is active once the computer starts up.
Table 3-3
1.
Start RSLinx. Its icon is located in the lower right area of the taskbar. Click it to invoke the configuration screen. Once the configuration screen appears, select the Communications menu item.
2.
3.
From the Communications sub-menu, select Configure Drivers.
4.
From the Configure Drivers window, select the Configure button.
Version V1.1
Issue 10.01.2009
15/52

5.
From the Configure RS-232 DF1 Devices window, select the AutoConfigure button.
6.
If the cable is correct and the controller is powered on, a message stating Auto Configuration Successful will appear. Select the OK button to close the window.
7.
Select the Close button from the Configure Drivers window.
Version V1.1
Issue 10.01.2009
16/52

8.
Close the RSLinx window.
RSLinx is now configured to allow RSLogix 5000 to communicate with the ControlLogix Controller.
NOTE
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select "Configure RSLinx" from the menu.
Version V1.1
Issue 10.01.2009
17/52

3.3.2
Create a new RSLogix 5000 Project Once communications are configured, create a new project by starting RSLogix 5000. The screen should display the main menu window.
Table 3-4
1.
Select the File menu item.
2.
Select New.
3.
Select the CPU type, add a name and a description and select the OK button.
4.
A new project has been created.
NOTE
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select "New Program" from the menu.
Version V1.1
Issue 10.01.2009
18/52

3.3.3
Configure DeviceNet Module After following the steps in 3.3.2, it is necessary to add the DeviceNet scanner to the project hardware configuration.
Table 3-5
1.
Right click the 1756 Backplane item and select new module.
2.
Expand the Communications selection and scroll to the 1756-DNB module.
3.
On the side of each ControlLogix module is a label. The label contains the firmware revision of the module. RSLogix needs to be configured with the proper firmware revision. In the example to the right, the Major Revision number is 6 and the Minor revision number is 2. Configure the Major Revision of the DeviceNet scanner and select the OK button.
4.
Version V1.1
Issue 10.01.2009
19/52

5.
Configure the Minor Revision number and the symbolic name of the DeviceNet scanner.
NOTE
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select "Configure DeviceNet Scanner" from the menu.
3.3.4
Select Communications Path to Controller RSLogix needs a communications path in order to communicate with the controller. This is accomplished by selecting the path.
Table 3-6
1.
Select the Who Active button beside the Path drop-down box on the RSLogix 5000 window. Once the Who Active window appears, the active path will animate by blinking the small icons to the left of an active path. Select the path.
2.
Version V1.1
Issue 10.01.2009
20/52

3.
Once the path is highlighted, select the Set Project Path button.
4.
When the path is set, select the Download button.
5.
Select the Download button from the Download window.
6.
The download is now in progress.
Version V1.1
Issue 10.01.2009
21/52

7.
After the download completes, the RSLogix 5000 should be online with the controller. As soon as the controller is online, the gears displayed to the left of the "Path:" selection will begin to rotate. NOTE
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select "Set Communication Path" from the menu.
3.3.5
Create DeviceNet Configuration File Configure a DeviceNet Configuration File.
Table 3-7
1.
First select the properties of the DeviceNet Scanner.
2.
Select the RSNetWorx tab from the Module Properties window.
Version V1.1
Issue 10.01.2009
22/52

3.
Enter the name of the configuration file.
4.
Select the Apply button.
5.
Select the Yes button from the warning screen.
6.
The DeviceNet configuration file is created.
NOTE
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select "Create DeviceNet Config File" from the menu.
Version V1.1
Issue 10.01.2009
23/52

3.3.6
Install the Micromaster EDS File Launch the DeviceNet configuration editor.
Table 3-8
1.
Launch the DeviceNet Editor by selecting the button to the left of View and Edit the DeviceNet network.
2.
If the configuration file does not exist, you will get a message asking you to approve the creation of it. Select the Yes button.
3.
RSNetworx will launch.
4.
Once RSNetworx for DeviceNet launches, select the Tools->EDS Wizard menu item.
Version V1.1
Issue 10.01.2009
24/52

5.
Select the Next button.
6.
Select Register an EDS File and select the Next button.
7.
Browse and select the MM4v1-1.eds file and select the Next button.
8.
Version V1.1
Issue 10.01.2009
25/52

9.
10.
11.
12.
The installation is complete.
Version V1.1
Issue 10.01.2009
26/52

MicroMaster DeviceNet Integration NOTE Item-Number: 32989737
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select "Create DeviceNet File" from the menu.
3.3.7
Browse DeviceNet Network for Nodes The DeviceNet network should be functional at this point. The next step is to browse the network for nodes.
Table 3-9
1.
Select the Online button from the toolbar. A path to the DeviceNet network must be selected.
2.
Version V1.1
Issue 10.01.2009
27/52

3.
Drill down through the existing communications path until the DeviceNet network is found. You will know you have reached it when the OK button becomes active. Select the OK button.
4.
Select the OK button for the information message. The DeviceNet scanner will scan for all 64 nodes on the network.
5.
6.
When it completes, the nodes that have been located will be shown connected to the network. The MM4 Drive Module (MicroMaster) and the DeviceNet scanner should appear connected.
NOTE
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select "Browse Network" from the menu.
Version V1.1
Issue 10.01.2009
28/52

3.3.8
Configure and Download DeviceNet Nodes The next step is to configure and download the nodes that the scanner located.
Table 3-10
1.
No configuration is required for the Micromaster MM4 Drive Module node. Use the mouse and right click its icon.
2.
Select Download to Device.
3.
Select the Yes button.
4.
Select the DeviceNet scanner module and right click it.
5.
Select Properties from the context menu.
Version V1.1
Issue 10.01.2009
29/52

6.
Select the Scanlist tab.
7.
Select the Download button.
8.
Download takes place.
9.
Once downloading completes, the Scanlist Configuration screen will appear. Ensure the MM4 Drive Module is highlighted and select the right arrow button to add the MM4 Drive Module to the scanlist.
Version V1.1
Issue 10.01.2009
30/52

10.
Select the Edit I/O Parameters button to verify I/O sizes.
11.
Note that the Poll size for both input and output is 8 bytes. This equates to the 4 PZD input words and 4 PZD outputs words of the MicroMaster drive. Select the OK button to close the window. Once the window disappears, select the Input tab.
Version V1.1
Issue 10.01.2009
31/52

12.
Note the mapping location of the input words. In this case, the 8 input bytes are mapped to the first 8 bytes (2 dwords) of the DeviceNet Scanners input data area. These 8 bytes represent the 8 bytes of status from the MicroMaster drive. Select the Output tab.
13.
Like the inputs, the outputs are mapped to the first 8 bytes (2 dwords) of the DeviceNet Scanners data output area. This area corresponds to the 8 bytes of control words to the MicroMaster drive. Select the Module tab.
Version V1.1
Issue 10.01.2009
32/52

14.
From the Module page, select the Download to Scanner button.
15.
Once download completes, select the OK button.
Version V1.1
Issue 10.01.2009
33/52

16.
RSNetworx automatically prompts for a download when exiting the DeviceNet Scanners configuration dialog. Select the Yes button.
17.
The download will complete. After approximately 60 seconds, the three LEDs on the front of the DeviceNet Scanner module should be green. The MOD/NET and OK LEDs should be constantly lit, while the I/O LED should be flashing.
NOTE
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select "Download Devices" from the menu.
3.3.9
Save and Exit the RSNetworx Save the configuration and exit RSNetworx.
Version V1.1
Issue 10.01.2009
34/52

Table 3-11
1.
Select the Save button on the toolbar.
2.
The button will gray out indicating the save operation completed.
3.
Close RSNetworx.
NOTE
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select "SaveAndExit" from the menu.
3.3.10
Manually Set DeviceNet Scanner to Run The DeviceNet Scanner must be commanded to the run state in order to exchange data with other DeviceNet nodes. This is accomplished by setting a command bit in the scanners memory area of the Controller.
Table 3-12
1.
The Controller must be placed into Run Mode. To do this, right click the Controller Tags menu item. Select the Monitor Tags menu choice.
2.
3.
Expand the Local 1:O tags. (In the designation "1:0", "1" represents the module in slot 1, while "O" stands for outputs.)
Version V1.1
Issue 10.01.2009
35/52

4.
Expand the Command Register tags.
5.
Change the value of the CommandRegister.Run tag to 1 and press the Enter key.
6.
Next turn the key on the controller to REM (Remote) and select the Program button in the upper left area of the RSLogix 5000 window.
7.
Select the Run Mode menu choice.
8.
Select the Yes button.
9.
The status of the controller should change to Run Mode. The text on the front of the DeviceNet Scanner should state RUN. All three LEDs, MOD/NET, I/O, and OK should be constantly lit green.
Version V1.1
Issue 10.01.2009
36/52

MicroMaster DeviceNet Integration NOTE Item-Number: 32989737
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select "Set To Run" from the menu.
3.3.11
Manually Command Motor Once the controller and DeviceNet Scanner are in Run, the MicroMaster drive can be commanded to run the motor.
Table 3-13
1.
First expand the output data tags.
2.
Change the view of the first dword to hex.
3.
Set the most-significant word to 0x4000 and the least-significant word to 0x047E. This commands the motor for full speed with a stop command. Next, set the least-significant word to 0x047F. This commands the motor to run at full speed with a "run forward" command. If the MicroMaster is configured properly for the motor, the motor should run forward at full speed. Now expand the input data area to verify feedback from the MicroMaster: Expand the input tags. Change the view of the first dword to hex. Note that the value of the most-significant word is 0x3FFF indicating full speed. The least-significant word is the current status.
4.
5.
Version V1.1
Issue 10.01.2009
37/52

6.
Collapse the input data tags and command the motor to stop.
7.
Expand the input tag area again and verify the motor has stopped.
The feedback shows the motor has stopped turning.

NOTE
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select " Command Motor " from the menu.
3.3.12
Diagnostic Information The DeviceNet Scanner contains several diagnostic tags. These are noted as the Local 1:S tags. For this example application three of them will be noted. First there is DeviceFailureRegisters. Any device that has failed will have its designated address bit set to "1". Addresses are designated leastsignificant bit to most-significant bit with address 0 being assigned to the least-significant bit. A DeviceNet network consists of 64 nodes so there are 8 double word registers for the DeviceFailureRegisters.
Version V1.1
Issue 10.01.2009
38/52

There are also ActiveNodeRegisters. Like the DeviceFailureRegisters, there is a bit that is set for each active node. In the following screen capture, note that bit 3 of the first register is set to "1" indicating that the MicroMaster is communicating:
There are also DeviceStatus registers that provide a byte of status for each DeviceNet node:
Version V1.1
Issue 10.01.2009
39/52

3.3.13
Setting DeviceNet Scanner to Run with Logic Program logic is used to ensure the DeviceNet scanner goes to run when the controller does. The following is a latching ladder logic rung that will accomplish the task using the DeviceNet Scanners CommandRegister.Run tag.
3.3.14
Create Data Type for Data Buffer In order to read and write MicroMaster parameters (PKWs), create a buffer data type to be used for read requests and write commands.
Version V1.1
Issue 10.01.2009
40/52

Table 3-14
1.
First expand the Data Types selection.
2.
Next right click User-Defined and select the New Data Type menu item.
3.
Enter the data type name. In this example, we will use Buffer.
4.
Next configure the contents. For this example, 8 bytes (SINT in Rockwell terminology) will be configured. This can be expanded if required. Select the Apply button to save the data type profile.
3.3.15
Create Tags for Reading and Writing PKWs Tags will need to be configured to facilitate reading and writing parameters. Two Boolean tags will be created to command reads and writes, three tags will utilize the newly created Buffer data type, and two will be of the MESSAGE data type for the MSG functions used for sending requests and commands to the MicroMasters DeviceNet communication board (CB). The tags are:
Version V1.1
Issue 10.01.2009
41/52

MicroMaster DeviceNet Integration Name Type Item-Number: 32989737 Function
Read Write ReadRequest ReadResponse WriteCommand
Bool Bool Buffer Buffer Buffer
Read request trigger. Write command trigger. Read request data for reading parameters. Response from parameter read request. Write command data for writing parameters. Response from the write command.
WriteResponse Buffer ReadParms WriteParms
MESSAGE MSG function instance tag for read requests. MESSAGE MSG function instance tag for write commands.
Table 3-15
1.
To configure tags, select Controller tags.
2.
Select the Edit Tags tab at the bottom of the page. Add the tags and then Save the project.
3.
NOTE
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select " Create Tags" from the menu.
Version V1.1
Issue 10.01.2009
42/52

3.3.16
Create Logic for Reading PKWs The MSG instruction is used to read parameters from the MicroMaster. This section centers around section 3.2.4 of the Siemens document DeviceNet Option Module Operating Instructions (6SE6400-5BC00-0BP0). The logic in this section reads parameter r964.002, the firmware version of the MicroMaster.
Table 3-16
1.
To enter the logic, go to the MainRoutine Task. Double click MainRoutine.
2.
Once in the logic, right click the (End) rung and add a new rung.
3.
Select a normally open contact.
Version V1.1
Issue 10.01.2009
43/52

4.
Select the read tag from the list of tags.
5.
Next select the Input/Output tab of the message instructions and enter a MSG function. Configure the MSG functions instance tag to the ReadParms tag that was created earlier.
6.
Click the Configuration button to the right of the ReadParms tag name. The Configuration dialog box will open.
Version V1.1
Issue 10.01.2009
44/52

7.
Configure the message communications using the CIP Generic message type. Configure the Service Code, Class, Instance, and Attribute per the requirement of section 3.2.4 of the Siemens document DeviceNet Option Module Operating Instructions (6SE6400-5BC00-0BP0). For the Source Element use the ReadRequest tag that was configured earlier. The Source Element will contain the read request, the parameter number, and the parameter index. The total request will be 4 bytes long. For the Destination, use the ReadResponse tag that was created earlier. This will hold the response value from the MicroMaster. Next click the Communication tab. Select the Browse button to browse for the message communications path. Select the DeviceNet Scanner module. Type the suffix ,2,3 after the name of the DeviceNet card so that the text is DeviceNetScanner,2,3. DeviceNetScanner is the name of the DeviceNet Scanner card entered during hardware configuration. This value will change according to the name in the DeviceNet Scanner module properties. The value "2" is required. It is the numeric representation of the DeviceNet communications port on the module. This value is always 2. The value "3" is the node address of the MicroMaster. This value will change based upon the node address that has been set for the MicroMaster. One important note, DO NOT CHECK the Connection check box. If it is checked, the read request WILL NOT function.
8.
Version V1.1
Issue 10.01.2009
45/52

9.
Select the OK button to apply the configuration.
10.
Next download the program to the controller. Note that the communications are offline for the download. Runtime edits can also be made.
11.
Confirm the Download operation.
12.
Once the download completes, confirm placing the controller back in Run Mode by selecting the Yes button.
Version V1.1
Issue 10.01.2009
46/52

13.
Vertically Tile the Logic Window and the Controller Tag window.
14.
Write the read request data into the ReadRequest tag. Note that the data is BYTE SWAPPED as stated in the Siemens manual.
15.
Once this is done, set the Read tag to "1" to enable the MSG block.
16.
Note in the ladder logic status that the Done (DN) bit is set indicated that the read request worked. In the Read Response tag, the values returned are hex "C4 43 d0 00 00 00". The "C4 63" is a valid response to the parameter read request. The data is byte swapped. It corresponds to the expected response from section 3.2.4 of the Siemens manual. The actual value is hex "00 d0" which in decimal is 208. This MicroMaster has firmware version 2.08. The last 2 bytes, "00 00", are the index value. This value is always zero.
NOTE
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select "Create Read Logic" from the menu.
Version V1.1
Issue 10.01.2009
47/52

3.3.17
Create Logic for Writing PKWs This example for writing MicroMaster parameters is from section 3.2.5 of the Siemens manual. Parameter P1203, "Flying Start", will be set to a value of "99".
Table 3-17
1.
The logic is very similar to the "Read PKW" logic.
2.
As defined in section 3.2.5 of the Siemens manual, the service code is different for the write command.
3.
The communications path is still the same.
Version V1.1
Issue 10.01.2009
48/52

4.
Write commands are similar to the read commands. The following screen capture shows the write to P1203 example from section 3.2.5 of the Siemens manual. Note the values in the write response tag and the Done (DN) bit on the output of the MSG instruction.
NOTE
You can watch a Flash animation of this operation. To start the animations, follow the instructions in chapter 4, and select Verify Write Operation from the menu.
3.3.18
Conclusion This application example has shown the basic requirements for cyclic data exchange and acyclic reading and writing to/from a Siemens MicroMaster drive and a Rockwell (Allen Bradley) ControlLogix Controller using DeviceNet. The concepts presented here should be applicable to other Siemens DeviceNet products.
Version V1.1
Issue 10.01.2009
49/52
Appendix Flash Animations

Appendix
4 Flash Animations
A flash animation of each configuration step is included with this application example. To watch the animations, extract the Zip archive into any directory and start the animation framework by double-clicking Start.exe. The individual clips are started by clicking their corresponding menu entries:
Menu entry Configure RSLinx New Program
Description Configuring the RSLinx communication software to communicate to the ControlLogix Controller. Creation of a new RSLogix5000 project. Configuring the ControlLogix hardware including the DeviceNet Scanner. Setting the project communications path so communications can occur with a controller. Definition of the DeviceNet configuration files. Browsing the DeviceNet network to locate connected nodes. Downloading the configuration to DeviceNet nodes. Configuration of the DeviceNet nodes. Saving and exiting the DeviceNet network configuration software. Manually setting the DeviceNet Scanner to Run Mode. Entering data values to the drive to command a motor to run using the PZD command words and monitoring feedback from the PZD status words. Testing and verifying that the write operation functioned properly. Programming logic to latch the DeviceNet Scanner in Run Mode. Configuring a custom data type to hold read/write request and response data. Creating of custom tags for reading and writing PKWs. Programming of the MSG block to read parameters (PKWs) from the MicroMaster drive. Verification of correct operation is also shown. Programming of the MSG block to write parameters (PKWs) to the MicroMaster drive.
See... 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5, 3.3.6 3.3.7 3.3.8 3.3.8 3.3.9 3.3.10 3.3.11
Configure DeviceNet Scanner Set Communications Path Create DeviceNet Config File Browse Network Download Devices Create DeviceNet File SaveAndExit Set To Run Command Motor
Verify Write Operation Program Run Logic Create Buffer Data Type Create Tags Create Read Logic
3.3.12 3.3.13 3.3.14 3.3.15 3.3.16
Create Write Logic
3.3.17
Version V1.1
Issue 10.01.2009
50/52
Appendix Internet links

Internet links
Topic \1\ \2\ \3\ Reference to the entry Siemens A&D Customer Support Operating Instructions: MICROMASTER DeviceNet Option Module Reference to a collection of articles regarding the connection of Rockwell components Title http://support.automation.siemens.com/WW/view/e n/32989737 http://www.ad.siemens.de/support http://support.automation.siemens.com/WW/view/e n/9144187
\4\
http://support.automation.siemens.com/WW/view/e n/32989862
Version V1.1
Issue 10.01.2009
51/52
Appendix History
History
Table 6-1 History
Version V1.0 V1.1
Date 24/09/07 10/01/09 First edition
Modification Adaptation to CS Design Guidelines
Version V1.1
Issue 10.01.2009
52/52

Micromaster Drive On Rockwell ControlLogix v10 en

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Micromaster Drive On Rockwell ControlLogix v10 en

Diunggah oleh

Hak Cipta:

Format Tersedia

Application about Communication

Integration of a MicroMaster Drive with Rockwell ControlLogix using DeviceNet

Warranty, liability and support

MicroMaster DeviceNet Integration Note

Copyright Siemens AG 2009 All rights reserved 32989737_Micromaster_Drive_on_Rockwell_ControlLogix_v10_en.doc

Warranty, liability and support

MicroMaster DeviceNet Integration

Establishing Communications Configuration Steps

MicroMaster DeviceNet Integration

Copyright Siemens AG 2009 All rights reserved 32989737_Micromaster_Drive_on_Rockwell_ControlLogix_v10_en.doc

MicroMaster DeviceNet Integration

Copyright Siemens AG 2009 All rights reserved 32989737_Micromaster_Drive_on_Rockwell_ControlLogix_v10_en.doc

MicroMaster DeviceNet Integration

Copyright Siemens AG 2009 All rights reserved 32989737_Micromaster_Drive_on_Rockwell_ControlLogix_v10_en.doc

Application Description MicroMaster DeviceNet Integration

MicroMaster DeviceNet Integration

Rockwell (Allen Bradley) ControlLogix Controller

Siemens AG Master Drives

Application Description Establishing Communications

RS 232 Serial connection (DF1 protocol)

Application Description Establishing Communications

Application Description Establishing Communications

Required hardware and software components

ControlLogix Controller (CPU)

ControlLogix DeviceNet Scanner DeviceNet Cable

Any motor suitable for the Master drive can be used.

Application Description Establishing Communications

cf. \3\ in the appendix Internet links

Application Description Establishing Communications

Copyright Siemens AG 2009 All rights reserved 32989737_Micromaster_Drive_on_Rockwell_ControlLogix_v10_en.doc

Configuration and Operation of the Application Configuration of the DeviceNet communication

Configuration and Operation of the Application

Configuration of the DeviceNet communication

Copyright Siemens AG 2009 All rights reserved 32989737_Micromaster_Drive_on_Rockwell_ControlLogix_v10_en.doc

Select digital command source:

Configuration and Operation of the Application Configuration of the DeviceNet communication

Item-Number: 32989737 Comment

Commands received from DeviceNet:

Rockwell ControlLogix Configuration

Component Controller (CPU) DeviceNet Scanner

Configuration and Operation of the Application Configuration of the DeviceNet communication

Copyright Siemens AG 2009 All rights reserved 32989737_Micromaster_Drive_on_Rockwell_ControlLogix_v10_en.doc

From the Communications sub-menu, select Configure Drivers.

From the Configure Drivers window, select the Configure button.

Configuration and Operation of the Application Configuration of the DeviceNet communication

Copyright Siemens AG 2009 All rights reserved 32989737_Micromaster_Drive_on_Rockwell_ControlLogix_v10_en.doc

Select the Close button from the Configure Drivers window.

Configuration and Operation of the Application Configuration of the DeviceNet communication

Close the RSLinx window.

Configuration and Operation of the Application Configuration of the DeviceNet communication

Select the File menu item.

A new project has been created.

Configuration and Operation of the Application Configuration of the DeviceNet communication

Copyright Siemens AG 2009 All rights reserved 32989737_Micromaster_Drive_on_Rockwell_ControlLogix_v10_en.doc

Expand the Communications selection and scroll to the 1756-DNB module.

Configuration and Operation of the Application Configuration of the DeviceNet communication

Copyright Siemens AG 2009 All rights reserved 32989737_Micromaster_Drive_on_Rockwell_ControlLogix_v10_en.doc

Configuration and Operation of the Application Configuration of the DeviceNet communication

When the path is set, select the Download button.

Copyright Siemens AG 2009 All rights reserved 32989737_Micromaster_Drive_on_Rockwell_ControlLogix_v10_en.doc

Select the Download button from the Download window.

The download is now in progress.