To Join the Telephone Conference… Dial 866-774-1453 Please - PowerPoint Presentation

To Join the Telephone Conference… Dial 866-774-1453Please specify conference ID 89292105 We will send a link to a recording of this broadcast following the WebEx session. 1

June 2012 TechConnectSM Support Genius Webinar Kathy Mathews, Technical Support Engineer

Agenda Creating and Scheduling a Scan List on ControlNet Using Recommended StepsImplementing and Using the ControlNet Diagnostic Faceplate 3

Agenda Creating and Scheduling a Scan List on ControlNet Using Recommended StepsImplementing and Using the ControlNet Diagnostic Faceplate 4

What are the steps to get ControlNet running?Physically wire the ControlNet trunk line. Add repeaters, if necessary.Set the ControlNet node numbers (addresses), connect the ControlNet taps, and power up the devices.Set the network and media parameters in RSNetWorx . Create the scan lists. Schedule the network with RSNetWorx . Resolve any keeper signature mismatches. Upload all controller projects to get the scanner signatures. Make a backup copy of your ControlNet configuration (.xc file). 5

Kathy’s Recommended Steps Set the network and media parameters in RSNetWorx. Resolve any keeper signature mismatches. Upload all controller projects to get the scanner signatures. Make a backup copy of your ControlNet configuration (.xc file). 6

What are the basic steps? The first 3 steps are . . . Physically wire the ControlNet trunk line.Add repeaters if necessary.Set the ControlNet node numbers (addresses), connect the ControlNet taps and power up the devices. repeater 7

Step 4: Set the network parameters and specify physical media in RSNetWorx Network Update Time ( NUT) is the base rate at which communication repeats . It can be a value from 2 to 100 msec. It is the fastest rate at which two devices can communicate. Max Scheduled Address is a value from 1 to 99. Any node with an address above Max Scheduled Address may not communicate during the scheduled portion of the NUT . Max Unscheduled Address is a value from 1 to 99. Any node with an address above Max Unscheduled Address may not communicate during the unscheduled portion of the NUT. Media Redundancy : t he user defines if they are using the A Ch Coax connector, B Ch Coax connector or both coax connectors. RSNetWorx for ControlNet Network Parameters Dialog 8

Step 4 continued: Specify the Media You must configure the number of repeaters and amount of cable used in your network to ensure that no data collisions occur on the wire due to propagation delay. Collisions cause additional and unnecessary traffic on the wire. Collisions will also cause false positive for bad ControlNet media, meaning that you will see flashing ControlNet media LEDs and start to troubleshoot media component issues that don’t exist . view video (2 min) Drag items from left to right RSNetWorx for ControlNet Media Configuration Dialog 9

Steps 5 & 6 are required to configure & schedule your ControlNet I/O Create the scan list for each of the scanners, i.e., what controller will control what I/O device and how often they should exchange data. For Logix, you do this using RSLogix 5000.Schedule the scan list (network) using RSNetWorx for ControlNet 10

Step 5 & 6: Create & schedule a scan list for L63 to control FLEX I/O view video (6.5 min) RSNetWorx for ControlNet Graphical View of the Network 11

Steps 7 & 8: Ensure that scheduled I/O keeps working during a controller download or system power cycle Check and resolve any Keeper Signature mismatches Go online and upload all the controller projects with ControlNet scanner signatures 12

Steps 7 & 8: Ensure that scheduled I/O keeps working during a controller download or system power cycle May I see your invitation to the Scheduled I/O Party? Let me see if you are on my list! Check and resolve any Keeper Signature mismatches Go online and upload all the controller projects with ControlNet scanner signatures 13

ControlNet Keeper: Keeps unauthorized scheduled I/O off the network You can only control ControlNet scheduled I/O if you are on the Keeper’s list and your scanner signature matches the scanner signature found on the keeper’s list. The keeper gets its list of all the scanner signatures when the network is scheduled with RSNetWorx . When a keeper has this information, we call it a valid keeper . Individual scanners get their scanner signature when the network is scheduled. We call that the scanner signature . Keeper with the list of what scanners are allowed on the network Multiple Scanners waiting for permission to connect to its I/O defined in the scan list 14

How do we “resolve keeper signature mismatches”? And why? Any ControlNet scanner on the network can be a keeper . The keeper cable device working as the keeper is called the active keeper . The keeper cable devices not working as the keeper are called back-up keepers. If a keeper has a(n) Old signature = invalid keeper Current signature = valid keeper No signature = unconfigured keeper Any device that is or may become an active keeper needs the correct keeper signature (party list ), so the right folks are admitted to the I/O party. Otherwise I/O stops!15

We want all keepers to be valid keepers… otherwise if that invalid keeper becomes the active keeper, then the CNet I/O stops! But it is possible for a keeper-capable device to have the wrong keeper signature because: t he device was off the network when the keeper signature was sent down by RSNetWorx . s omeone replaced the device after the signature was sent down by RSNetWorx . t he device was too busy to accept the signature when it was sent down by RSNetWorx . Any device that is or may become an active keeper needs the correct keeper signature (party list ), so the right folks are admitted to the I/O party. Otherwise I/O stops!16

Step 7: After every RSNetWorx scheduling, review and resolve any Keeper Signature mismatches Go on line with RSNetWorx and select Network>Keeper Status.In the Keeper Status Dialog, make sure all the signatures match.If a signature does not match, then select that node and hit the Update Keeper button.Repeat for all nodes where the signature does not match. view video (1 min) RSNetWorx for ControlNet Keeper Status Dialog All are equal . That is what you want. 17

Step 8: Upload and save the scanner signature with the controller project Open the project offline. Use the pull down and select Upload twice. This ensures that your ControlNet scheduled I/O will work after a download of the controller project without rescheduling the network with RSNetWorx . RSLogix 5000 Upload Dialog 18

Step 9: Back up your work! Make a back up copy of the ControlNet configuration file or .xc file Just use the copy and rename commands in Windows! 19

Summary: What are the steps to get ControlNet running? Physically wire the ControlNet trunk line. Add repeaters, if necessary.Set the ControlNet node numbers (addresses), connect the ControlNet taps, and power up the devices.Set the network and media parameters in RSNetWorx . Create the scan lists. Schedule the network with RSNetWorx . Resolve any keeper signature mismatches. Upload all controller projects to get the scanner signatures. Make a backup copy of your ControlNet configuration (.xc file ). 20

Agenda Creating and Scheduling a Scan List on ControlNet Using Recommended StepsImplementing and Using the ControlNet Diagnostic Faceplate 21

So what happens if you forget some of the steps?Incorrect media configuration can cause a false positive for bad media (flashing green media LED), causing unnecessary work looking for a bad connector or bad piece of cable when nothing is wrong except a software configuration value 22

So what happens if you forget some of the steps?A bad keeper signature could prevent some or all of your ControlNet I/O from starting up. This will prevent the machine or system from running correctly and could happen when a module is replaced or if the module is powered down during a network download. RSLogix 5000 Module Properties Connection Dialog Attention Icon next to a module in I/O Configuration 23

So what happens if you forget some of the steps?Downloading a project with bad scanner signatures (presented to the keeper when the I/O connection is opened) will prevent some or all of your ControlNet I/O connections from starting up. This will prevent the machine or system from running correctly. RSLogix 5000 Module Properties Connection Dialog Attention Icon next to a module in I/O Configuration 24

ControlNet Diagnostic Faceplate helps with two common issues Whether or not the media configuration has been changed from default Not configuring media correctly can result in blinking media LEDs that indicate a false positive for bad media. This could cause an unnecessary search for bad connectors or bad sections of cable.Which nodes have invalid keeper signatures If a keeper with a bad signature becomes the active keeper, then I/O could be prevented from starting. This can cause the machine or the system not to function correctly. 25

How do we Implement ControlNet Diag FP? In RSLogix 5000: View Video (starts with a new empty application already created) Add in a subroutine, CNet_KPR_Table , & call to that subroutine by importing two .L5X files Define the path to the lowest node-numbered keeper. It must be a valid, active keeper for the code to work. Note that the code was written for one ControlNet network. The code was written to minimize code execution time. The code was written to minimize the number of ControlNet unconnected buffers used. In FTView Studio Machine Edition: View Video (starts with a new empty application already created) Import a display and its associated parameter file Modify the parameter file to use the correct controller device shortcut nameIf you are unfamiliar with creating a new FTView Studio ME project, view this video 26

How do we use ControlNet Diag FP? Monitor the FP Alarm page on a regular basis. If the Network Valid Signature is red, then monitor the Network Node Table display to determine which keepers have bad signatures. Go on line with RSNetWorx and resolve any keeper signature mismatches in the Keeper Status dialog box. Use the FP help text to guide your actions. If you have complaints about the CNet media LED blinking, then check the Media Config Default status on the Network Status display. Verify your media configuration settings against your network drawings. View Video FTView Studio ME displays 27

ControlNet Diagnostic Faceplate SummaryTo provide standard HMI displays to our customers, system integrators and OEMs to make our products easier to use and systems easier to maintain. ControlNet is the network used by our process industry customers, as it supports redundant media, redundant processors and adding of I/O online. Having standard HMI displays with diagnostics is expected. Now, we have it. 28

Where do we find Faceplates? Go to www.ab.com/go/iatools/ Navigate to the sample code w ebsite Using the drop-down menu for Technologies & Functionalities, select Face Plates & hit Search Download the files you want 29

Final Summary Physically wire the ControlNet trunk line. Add repeaters if necessary.Set the ControlNet node numbers (addresses), connect the ControlNet taps, and power up the devices. Set the network and media parameters in RSNetWorx . Create the scan lists. Schedule the network with RSNetWorx Resolve any keeper signature mismatches. Upload all controller projects to get the scanner signatures. Make a backup copy of your ControlNet configuration (.xc file ). Consider using the ControlNet Diagnostic Faceplate to help with steps 4 and 7. 30

Final Summary: Why we follow the steps When you follow these steps, then your ControlNet I/O will work properly:without false positive bad media indicatorsno matter which devices are powered up and downwithout having to reschedule ControlNet after downloading to the controller (provided the scan list did not change) because your scanner signature is badyou’ll have a back up copy of ControlNet configuration in case you ever need it 31

Thank You! Want to know more?Any questions? 32

June 2012 TechConnectSM Support Genius Webinar Kathy Mathews, Technical Support Engineer