Manuals / Watlow Electric / Computer Equipment / Network Card

Watlow Electric Gateway & DeviceNet Custom O to T Assembly, Watlow, Bundy Blvd, Winona, MN, 4/08

Models: Gateway & DeviceNet

1 21

Download 21 pages 60.38 Kb

Page 21

Image 21

RUI/Gateway & DeviceNetTM

Configuration & Ladder Logic Example

Using an Allen-Bradley CompactLogix PLC

Custom T to O Assembly

Custom O to T Assembly

Watlow
1241 Bundy Blvd
Winona, MN 55987
Telephone: 507-494-5656
© 2007 Watlow Electric Mfg Co	21	4/08

Page 21

Image 21

Watlow Electric Gateway & DeviceNet Using an Allen-Bradley CompactLogix PLC Custom T to O Assembly, Custom O to T Assembly

Contents

RUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Using an Allen-Bradley CompactLogix PLCConfiguring the RUI/Gateway on DeviceNetTM Using RSNetWorx RUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Using an Allen-Bradley CompactLogix PLCdisplay as shown below. In this particular case, node 7 RUI/Gateway appears with a question mark because it has not yet been registered on the network Using an Allen-Bradley CompactLogix PLC RUI/Gateway & DeviceNetTM Configuration & Ladder Logic ExampleWatlow 1241 Bundy BlvdRUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Using an Allen-Bradley CompactLogix PLC8. When found notice that if there is an icon with the same name the software will register it along with the EDS file. Click next to proceed with the registration RUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Using an Allen-Bradley CompactLogix PLC10. After clicking next above, the software will associate an icon to this device, if there was none found in the previous step it will use a default icon to graphically represent this node. Click next to proceed RUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Using an Allen-Bradley CompactLogix PLC12. The next series of steps involves mapping the available RUI/Gateway input 84 and output 80 bytes via the scanner into the PLC memory. Double click on the scanner module to proceed RUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Using an Allen-Bradley CompactLogix PLC14. After the scanner recognizes the RUI/Gateway on the network it will then appear as an Available Device as shown below. Before clicking on the right arrow to add it in the scanners scan list consider the effect of the Automap on Add check box. If this box is checked and there are other currently existing nodes on the network where they may not be using complete words less than 32 bits the scanner will not consider word boundaries when adding a new node and will attempt to utilize every available bit in the PLC. As an example, if a given device has only 9 bytes of information it will use 2¼ 32 bit words 3 bytes not used in the last word. Now, when adding a new node like the RU/Gateway that utilizes 80 bytes 20- 32 bit words with each being a separate entity, i.e., 32 bit Set Point ¾ of the first word will be placed in the last word of the node mentioned above. The impact of this action would then break up all of the 20 words sent to and received from the RUI/Gateway in a convoluted way. For this reason, it is suggested that this box be unchecked if there are other devices on the network allowing the individual doing the configuration to select the appropriate word boundaries manually RUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Using an Allen-Bradley CompactLogix PLC15. Once the available device RUI/Gateway in this case is moved over to the Scanlist the next step will be to map the RUI/Gateway input and output bytes to PLC addresses first the inputs. In this particular case the Automap on Add box was checked and the result of that now becomes apparent. Since there were no other devices on the network the software simply took all of the available RUI/Gateway input bytes 84 and allocated them to the first available PLC input bytes. Although we can’t see in the graphic below all of the addresses assigned you can trust that what was assigned are addresses 1I.Data0 through 1I.Data20. If there were other devices on the network and the Automap on Add box was not checked the address field below would not be populated. Clicking on the Advanced button would then allow for manual configuration RUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Configuration of the RUI/GatewayUsing an Allen-Bradley CompactLogix PLC The PLC will need to be in the program or remote program mode for this to occur. When written this completes the configuration of the RUI/Gateway using RSNetWorxGateway EnableOffset InstanceRUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Configuring the DeviceNetTM Scanner 1769-SDN Using RSLogixUsing an Allen-Bradley CompactLogix PLC 19. The gateway instance represents the EZ-ZONE control, in this case, PM 1-4. The enableRUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example EZ-ZONE EEPROMUsing an Allen-Bradley CompactLogix PLC 22. Notice too, the slot number, in this case “1”. This is the physical slot in which the scanner resides. After the scanner is configured two tags will be automatically generated reflecting the existence of the scanner in slot 1 of the I/O structure. These tags will be used to move the implicit input and output assemblies more on this to follow to and from the RUI/Gateway and then ultimately to the destination EZ-ZONE PM controls that exist on Standard BusRUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Reading and Writing to/from RUI/Gateway Using RSLogixUsing an Allen-Bradley CompactLogix PLC 24. The rung of logic below when enabled, will execute an explicit message sent to the gateway where it will then be routed out over Standard Bus to the EZ-ZONE PM control defined by the instance oSt prompt. Because the CIP offset is set to 12 for gateway instance 4 this message will be routed to PM4. When done, the destination tag identified under the configuration tab “EEPROM Status” see below will contain the value of either 106 being enabled or 59 being disabledRUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Using an Allen-Bradley CompactLogix PLC25. Notice above that there are screen shots for the configuration and communication tabs. Within the configuration, the programmer will need to specify whether this is a read Get or a write Set operation as well as the class, instance, and attribute CIA of interest. The CIA for all PM controls is 150, 2, 8 respectively. The CIA shown above in hexadecimal represents the Non-Volatile Save parameter for node 4 going through the RUI/Gateway see step 24 for explanation. The communication tab allows the programmer to select a configured I/O module to send or receive the message where the port number and node address need to be identified. Again, as can be seen above the module is defined in the I/O structure as DNetScanner Default Originator to Target O to T Assembly Default Target to Originator T to O AssemblyRUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Using an Allen-Bradley CompactLogix PLCUsing an Allen-Bradley CompactLogix PLC RUI/Gateway & DeviceNetTM Configuration & Ladder Logic ExampleCustom T to O Data Type Custom O to T Data TypeUsing an Allen-Bradley CompactLogix PLC RUI/Gateway & DeviceNetTM Configuration & Ladder Logic ExampleController Tag T to O Controller Tag O to TRUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example AssemblyUsing an Allen-Bradley CompactLogix PLC GatewayCommunications Card RUI/Gateway AddressingDevice Physical AddressRUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Using an Allen-Bradley CompactLogix PLC37. In step 30 it was suggested that the user may want to create user defined data types. Likewise, in step 31 it was also suggested that the user should create controller tags utilizing those same user defined data types. The reasoning for this may become more obvious in the Custom O to T Assembly Using an Allen-Bradley CompactLogix PLC Custom T to O AssemblyRUI/Gateway & DeviceNetTM Configuration & Ladder Logic Example Watlow