Application about Communication

Transcription

1 Application about Communication Integration of a MicroMaster Drive with Rockwell ControlLogix using DeviceNet Third-Party Integration

2 Warranty, liability and support Note 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. 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 address: mailto:csweb@ad.siemens.de Version V1.1 Issue /52

3 Foreword 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: Configuration for Cyclic Data Exchange Reading and Writing Parameter Data Diagnostics 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 Establishing Communications Configuration Steps Appendix 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. Version V1.1 Issue /52

4 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. Version V1.1 Issue /52

5 Foreword Table of Contents Table of Contents... 5 Application Description MicroMaster DeviceNet Integration Overview Requirements Establishing Communications Overview Configuration Activities... 8 Alternative solutions Required hardware and software components Verification Configuration and Operation of the Application MicroMaster Setup Rockwell ControlLogix Configuration Configuration Steps RSLinx Communication Configuration Create a new RSLogix 5000 Project Configure DeviceNet Module Select Communications Path to Controller Create DeviceNet Configuration File Install the Micromaster EDS File Browse DeviceNet Network for Nodes Configure and Download DeviceNet Nodes Save and Exit the RSNetworx Manually Set DeviceNet Scanner to Run Manually Command Motor Diagnostic Information Setting DeviceNet Scanner to Run with Logic Create Data Type for Data Buffer Create Tags for Reading and Writing PKWs Create Logic for Reading PKWs Create Logic for Writing PKWs Conclusion Appendix Flash Animations Internet links Version V1.1 Issue /52

6 Foreword 6 History Version V1.1 Issue /52

7 Application Description MicroMaster DeviceNet Integration 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 MicroMaster DeviceNet Integration 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 DeviceNet- Card 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 /52

8 Application Description Establishing Communications 2 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) RS 232 Serial connection (DF1 protocol) ControlLogix Controller DeviceNet MicroMaster 440 FD (with DeviceNet module) 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. Power Motor 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 /52

9 Application Description Establishing Communications 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 /52

10 Application Description Establishing Communications 2.3 Required hardware and software components Hardware Components Table 2-1 Component No. MLFB Note ControlLogix 4-slot Chassis ControlLogix Power Supply ControlLogix Controller (CPU) ControlLogix DeviceNet Scanner A4 Any suitable chassis can be used PA75 Any ControlLogix power supply suitable for the selected chassis and power source can be used L55 Any suitable Controller (CPU) can be used DNB DeviceNet Cable 1 Refer to Siemens document DeviceNet Option Module Operating Instructions (6SE6400-5BC00-0BP0) Chapter 4 for cable requirements 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 1 Siemens Simatic-TI programming cable C or an industry standard null modem RS232 cable will work. 1 6SE6440-2AB11-2AA1 Any Master drive with a DeviceNet communication board can be used. 1 6SE6400-0BP00-0AA0 Any means of configuring PKWs can be used. 1 6SE6400-1DN00-0AA0 Siemens Motor 1 1LA2060-2AA10 Any motor suitable for the Master drive can be used. Version V1.1 Issue /52

11 Application Description Establishing Communications Software Components Table 2-2 Component No. Version Note Rockwell RSLinx Classic Lite communications software RSLogix 5000 Programming Software MicroMaster Electronic Data Sheet (EDS) file: MM4v1-1.eds 1 V Any version may be used as long as it supports communications to the DeviceNet network. 1 V Any version that supports the hardware components (CPU and DeviceNet Scanner) can be used. 1 V1.1 Used the EDS file for the specific DeviceNet communications board that is used. 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 <BID- Nr>_MicroMasterConfigAVIs.zi p 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. Version V1.1 Issue /52

12 Application Description Establishing Communications 2.4 Verification Verification testing is performed with the configuration steps. Version V1.1 Issue /52

13 Configuration and Operation of the Application Content This section describes the configuration process for the DeviceNet communications. 3 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 Table 3-1 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 Parameter Value Comment Select digital command source: P DeviceNet card (CB on COM link) P Terminal P Terminal Control/Setpoint source: P Binector/Connector (BICO) functionality P Binector/Connector (BICO) functionality P Binector/Connector (BICO) functionality Network node address ( MAC ID ): P Default Interface for parameter modification: P All bits set Select digital command dource: P DeviceNet card (CB on COM link) P Analog setpoint 1 Refer to Siemens document DeviceNet Option Module Operating Instructions (6SE6400-5BC00-0BP0), Chapter 5 for more detailed information. Version V1.1 Issue /52

14 Parameter Value Comment P Analog setpoint Communication failure creates fault on drive? P2040 >0 Yes Number of PZD input words: P Default (4 PZD input words) Number of PZD output words: P Default (4 PZD output words) Baudrate on the DeviceNet: P Default (125 kbps) Diagnostics mode: P Default (use standard diagnostics) Status registers transmitted on DeviceNet: P Actual status P Actual frequency P Binary input values P Binary input values Commands received from DeviceNet: r Actual status r Actual frequency r Binary input values r Binary input values 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 Component 0 Controller (CPU) 1 DeviceNet Scanner 3.3 Configuration Steps RSLinx Communication Configuration RSLinx is Rockwell Automation s 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 /52

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

16 5. From the Configure RS-232 DF1 Devices window, select the Auto- Configure 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 /52

17 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 /52

18 3.3.2 Create a new RSLogix 5000 Project Once communications are configured, create a new project by starting RSLogix The screen should display the main menu window. Table 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 /52

19 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 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 Configure the Major Revision of the DeviceNet scanner and select the OK button. Version V1.1 Issue /52

20 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 Select Communications Path to Controller Table 3-6 RSLogix needs a communications path in order to communicate with the controller. This is accomplished by selecting the path. 1. Select the Who Active button beside the Path drop-down box on the RSLogix 5000 window. 2. 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. Version V1.1 Issue /52

21 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 /52

22 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 Create DeviceNet Configuration File Table 3-7 Configure a DeviceNet Configuration File. 1. First select the properties of the DeviceNet Scanner. 2. Select the RSNetWorx tab from the Module Properties window. Version V1.1 Issue /52

23 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 /52

24 3.3.6 Install the Micromaster EDS File Launch the DeviceNet configuration editor. Table 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 /52

25 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. Select the Next button. Version V1.1 Issue /52

26 9. Select the Next button. 10. Select the Next button. 11. Select the Next button. 12. The installation is complete. Version V1.1 Issue /52

27 NOTE 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 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 Select the Online button from the toolbar. 2. A path to the DeviceNet network must be selected. Version V1.1 Issue /52

28 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. 5. The DeviceNet scanner will scan for all 64 nodes on the network. 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 /52

29 3.3.8 Configure and Download DeviceNet Nodes The next step is to configure and download the nodes that the scanner located. Table 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 /52

30 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 /52

31 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 /52

32 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 Scanner s 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 Scanner s 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 /52

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

34 16. RSNetworx automatically prompts for a download when exiting the DeviceNet Scanner s 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 Save and Exit the RSNetworx Save the configuration and exit RSNetworx. Version V1.1 Issue /52

35 Table 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 Manually Set DeviceNet Scanner to Run Table 3-12 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 scanner s memory area of the Controller. 1. The Controller must be placed into Run Mode. To do this, right click the Controller Tags menu item. 2. Select the Monitor Tags menu choice. 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 /52

36 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 /52

37 NOTE 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 Manually Command Motor Once the controller and DeviceNet Scanner are in Run, the MicroMaster drive can be commanded to run the motor. Table 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. 4. 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. 5. 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. Version V1.1 Issue /52

38 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 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 /52

39 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 /52

40 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 Scanner s CommandRegister.Run tag 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 /52

41 Table 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 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 MicroMaster s DeviceNet communication board (CB). The tags are: Version V1.1 Issue /52

42 Name Type Function Read Bool Read request trigger. Write Bool Write command trigger. Table 3-15 ReadRequest Buffer Read request data for reading parameters. ReadResponse Buffer Response from parameter read request. WriteCommand Buffer Write command data for writing parameters. WriteResponse Buffer Response from the write command. ReadParms MESSAGE MSG function instance tag for read requests. WriteParms MESSAGE MSG function instance tag for write commands. 1. To configure tags, select Controller tags. 2. Select the Edit Tags tab at the bottom of the page. 3. Add the tags and then Save the project. 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 /52

43 Create Logic for Reading PKWs The MSG instruction is used to read parameters from the MicroMaster. This section centers around section of the Siemens document DeviceNet Option Module Operating Instructions (6SE6400-5BC00-0BP0). The logic in this section reads parameter r , the firmware version of the MicroMaster. Table 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 /52

44 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 function s 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 /52

45 7. Configure the message communications using the CIP Generic message type. Configure the Service Code, Class, Instance, and Attribute per the requirement of section 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. 8. 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. Version V1.1 Issue /52

46 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 /52

47 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 d ". 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 of the Siemens manual. The actual value is hex "00 d0" which in decimal is 208. This MicroMaster has firmware version 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 /52

48 Create Logic for Writing PKWs Table 3-17 This example for writing MicroMaster parameters is from section of the Siemens manual. Parameter P1203, "Flying Start", will be set to a value of "99". 1. The logic is very similar to the "Read PKW" logic. 2. As defined in section 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 /52

49 4. Write commands are similar to the read commands. The following screen capture shows the write to P1203 example from section 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 Conclusion 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. 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 /52

50 Appendix Flash Animations 4 Flash Animations Appendix 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 Description See... Configure RSLinx Configuring the RSLinx communication software to communicate to the ControlLogix Controller New Program Creation of a new RSLogix5000 project Configure DeviceNet Scanner Set Communications Path Create DeviceNet Config File 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 , Browse Network Browsing the DeviceNet network to locate connected nodes Download Devices Downloading the configuration to DeviceNet nodes Create DeviceNet File Configuration of the DeviceNet nodes SaveAndExit Saving and exiting the DeviceNet network configuration software Set To Run Manually setting the DeviceNet Scanner to Run Mode Command Motor Verify Write Operation Program Run Logic Create Buffer Data Type 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 Create Tags Creating of custom tags for reading and writing PKWs Create Read Logic Create Write Logic 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 Version V1.1 Issue /52

51 Appendix Internet links 5 Internet links Topic \1\ Reference to the entry \2\ Siemens A&D Customer Support \3\ Operating Instructions: MICROMASTER DeviceNet Option Module \4\ Reference to a collection of articles regarding the connection of Rockwell components Title n/ n/ n/ Version V1.1 Issue /52

52 Appendix History 6 History Table 6-1 History Version Date Modification V1.0 24/09/07 First edition V1.1 10/01/09 Adaptation to CS Design Guidelines Version V1.1 Issue /52