{"id":1583,"date":"2018-07-22T15:29:56","date_gmt":"2018-07-22T15:29:56","guid":{"rendered":"http:\/\/bryceautomation.com\/?p=1583"},"modified":"2018-07-22T15:30:38","modified_gmt":"2018-07-22T15:30:38","slug":"troubleshooting-a-controllogix-output","status":"publish","type":"post","link":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/","title":{"rendered":"Troubleshooting a ControlLogix Output"},"content":{"rendered":"<h2>Introduction to Troubleshooting a ControlLogix Output<\/h2>\n<p>The most common problems on a system using ControlLogix are usually field devices.\u00a0 \u00a0Occasionally an I\/O module can fail.\u00a0 Most of the time, however we are using RSLogix\/Studio 5000 to find a failed field device.\u00a0 In this document, we will be troubleshooting a ControlLogix output.\u00a0 We will locate the output in the project.\u00a0 \u00a0Then we will navigate through the project to find the reason why the processor is not calling for an output to energize.\u00a0 One reason the output might not energize is because the processor is not getting an input, such as a limit switch, or a selector switch.<\/p><div id=\"bryce-632382221\" class=\"bryce-afterfirst bryce-entity-placement\"><script async src=\"\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-8316758073402323\" crossorigin=\"anonymous\"><\/script><ins class=\"adsbygoogle\" style=\"display:block;\" data-ad-client=\"ca-pub-8316758073402323\" \ndata-ad-slot=\"7728240895\" \ndata-ad-format=\"auto\"><\/ins>\n<script> \n(adsbygoogle = window.adsbygoogle || []).push({}); \n<\/script>\n<\/div>\n<p>Most of the time, there will be just one field device that we are not getting a signal from.\u00a0 \u00a0In this example, however, we will have multiple field devices that are not made.\u00a0 \u00a0 This will give you a better understanding of how to navigate, and locate the I\/O.<\/p>\n<p>Our goal here is not to change logic or the operation of the equipment in any way, but to use Studio 500 as a tool to locate failed field devices.<\/p>\n<h2>Understanding the Chassis Layout<\/h2>\n<p>When troubleshooting a ControlLogix output, you might first locate the failed output on a schematic.\u00a0 \u00a0Your schematic will show you what chassis the output is connected to, the slot, and the terminal.\u00a0 If you only have one chassis with a processor, we can always start by locating the Local controller tag.\u00a0 \u00a0All tags for all modules where the processor resides will start with the name &#8220;<strong>Local<\/strong>&#8220;.\u00a0 Tags for modules in remote chassis will begin with the name of the <strong>adapter<\/strong> in that chassis.<\/p>\n<p>Consider the following layout:<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1585 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/chassislayoutwithlight.png\" alt=\"Chassis Layout\" width=\"827\" height=\"566\" data-srcset=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/chassislayoutwithlight.png 827w, https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/chassislayoutwithlight-300x205.png 300w, https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/chassislayoutwithlight-768x526.png 768w\" data-sizes=\"(max-width: 827px) 100vw, 827px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 827px; --smush-placeholder-aspect-ratio: 827\/566;\" \/><\/p>\n<p>As we said before, all tags for all modules in the top chassis will begin with the name &#8220;<strong>Local<\/strong>&#8220;.\u00a0 Tags for the modules in the middle chassis will be named &#8220;<strong>remote_asb<\/strong>&#8220;.\u00a0 We can find this name by expanding the I\/O tree under I\/O configuration in the RSLogix\/Studio 500 project.\u00a0 Similarly, we know that all tags for modules in the last chassis will be named &#8220;<strong>remote_aent<\/strong>&#8220;.<\/p>\n<p>The output we will be troubleshooting in this example is shown above.\u00a0 \u00a0This output is in the Local chassis, slot 6, terminal 0.<\/p>\n<p>&nbsp;<\/p>\n<h2>Locating the output in the ControlLogix project.<\/h2>\n<p>Be sure you are online with the processor.\u00a0 This will ensure the data that we are looking at is in real time.\u00a0 Next, go to<strong> Controller Tags<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1587 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/controllertags.png\" alt=\"Controller Tags\" width=\"206\" height=\"98\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 206px; --smush-placeholder-aspect-ratio: 206\/98;\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Now find the local tag for slot 6.\u00a0 Since this is an output module.\u00a0 This will be easy to decipher.\u00a0 We know the chassis name is Local, so find the controller tag for slot 6.\u00a0 We know this is an output module, so expand the Local:6:O tag.\u00a0 Then expand the data component of this tag.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1588 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/Local6.png\" alt=\"Local 6\" width=\"381\" height=\"116\" data-srcset=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/Local6.png 381w, https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/Local6-300x91.png 300w\" data-sizes=\"(max-width: 381px) 100vw, 381px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 381px; --smush-placeholder-aspect-ratio: 381\/116;\" \/><\/p>\n<p>We will cross reference bit 0 of this tag to locate it&#8217;s output in logic.\u00a0 \u00a0Right click to cross reference.\u00a0 \u00a0You cannot left click first, or Studio 5000 will think you want to cut, copy, or paste.\u00a0 Right click only, and choose &#8220;Go to Cross Reference for Local:6:O.Data.0&#8221;.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1589 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/CrossReference.png\" alt=\"Cross Reference\" width=\"345\" height=\"158\" data-srcset=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/CrossReference.png 345w, https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/CrossReference-300x137.png 300w\" data-sizes=\"(max-width: 345px) 100vw, 345px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 345px; --smush-placeholder-aspect-ratio: 345\/158;\" \/><\/p>\n<p>Notice the next window that opens.\u00a0 \u00a0Usually, you will have only one instruction that is destructive.\u00a0 You can look in the destructive column for the &#8220;Y&#8221;.\u00a0 An instruction that is destructive has the ability to change the value of the tag.\u00a0 \u00a0We want to go to this tag to find out why it&#8217;s not turning the bit on.\u00a0 \u00a0In this case, we do have two instructions that are destructive, so we ask ourselves which one will energize the bit.\u00a0 The OTU (Output to Unlatch) will shut the bit off.\u00a0 \u00a0We are wanting to turn the bit on, so we will double click the OTE (Output to Energize) instruction.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1590 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/destructive.png\" alt=\"Destructive\" width=\"633\" height=\"117\" data-srcset=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/destructive.png 633w, https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/destructive-300x55.png 300w\" data-sizes=\"(max-width: 633px) 100vw, 633px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 633px; --smush-placeholder-aspect-ratio: 633\/117;\" \/><\/p>\n<p>This takes us to the output in logic.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1591 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/light0output.png\" alt=\"Light 0 Output\" width=\"506\" height=\"102\" data-srcset=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/light0output.png 506w, https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/light0output-300x60.png 300w\" data-sizes=\"(max-width: 506px) 100vw, 506px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 506px; --smush-placeholder-aspect-ratio: 506\/102;\" \/><\/p>\n<h2>Using Bookmarks<\/h2>\n<p>Studio 5000 has a nice book mark system built in.\u00a0 However, this is normally shut off by default.\u00a0 To turn on the bookmarks, go to View | Toolbars at the top of your project window.\u00a0 Put a check mark next to &#8220;Bookmark Toolbar&#8221;.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1593 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/bookmarks.png\" alt=\"Turn on Bookmarks\" width=\"307\" height=\"301\" data-srcset=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/bookmarks.png 307w, https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/bookmarks-300x294.png 300w\" data-sizes=\"(max-width: 307px) 100vw, 307px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 307px; --smush-placeholder-aspect-ratio: 307\/301;\" \/><\/p>\n<p>Now, you will notice &#8220;flag&#8221; icons have been added to your project.\u00a0 \u00a0The first two icons will let you navigate between previous and next bookmarks.\u00a0 The middle icon (single flag) will toggle a bookmark at this location in logic.\u00a0 \u00a0The third icon (with the x) removes all bookmarks.\u00a0 The last icon allows you to manage all bookmarks individually.\u00a0 \u00a0Here, most of the icons are grey, because we don&#8217;t have any bookmarks yet.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1594 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/bookmarktoolbar.png\" alt=\"bookmark toolbar\" width=\"148\" height=\"39\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 148px; --smush-placeholder-aspect-ratio: 148\/39;\" \/><\/p>\n<p>As a rule of thumb, I will usually bookmark the first rung I come to.\u00a0 This way, if I get totally lost in logic, I can easily get back to the starting point, and start to navigate again.\u00a0 To prevent building up too many bookmarks when navigating logic, I will only bookmark a rung that has more than one condition that I need to trace down.\u00a0 Let&#8217;s put a bookmark on this rung by pressing the middle bookmark icon.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1595 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/bookmarked.png\" alt=\"Rung Bookmarked\" width=\"509\" height=\"85\" data-srcset=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/bookmarked.png 509w, https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/bookmarked-300x50.png 300w\" data-sizes=\"(max-width: 509px) 100vw, 509px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 509px; --smush-placeholder-aspect-ratio: 509\/85;\" \/><\/p>\n<p>You can see the flag underneath the rung number, so we know now that this location is bookmarked.<\/p>\n<h2>Navigating logic<\/h2>\n<p>Let&#8217;s look at the conditions before Local_Light.0\u00a0 You can see the alias information below this tag (Local:6:O.Data.0).\u00a0 You will also notice this is seal-in logic.\u00a0 \u00a0Once bit_array[0] is true, the output will energize, and seal around bit_array[0].\u00a0 \u00a0When bit_array[0] goes false, the output will still remain energized.\u00a0 \u00a0When we see a rung that seals the output, we can ignore that for now.\u00a0 \u00a0This is because we have to take another path to get the light to energize in the first place.<\/p>\n<p>We need to cross reference bit_array[0].\u00a0 \u00a0To cross reference this bit, be sure you are on the tag itself.\u00a0 You cannot cross reference an instruction, or a description.\u00a0 \u00a0We need to right click bit_array[0], and cross reference.\u00a0 Then we will go to the destructive instruction.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1597 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/bitarray0.png\" alt=\"bit array 0\" width=\"629\" height=\"71\" data-srcset=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/bitarray0.png 629w, https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/bitarray0-300x34.png 300w\" data-sizes=\"(max-width: 629px) 100vw, 629px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 629px; --smush-placeholder-aspect-ratio: 629\/71;\" \/><\/p>\n<p>In the following rung, we can see that bit_array[0] is not energized for two reasons.\u00a0 (The ONS will take care of itself).\u00a0 One condition is a real world input.\u00a0 SLC_Switch.15 is an alias to remote_asb:I.Data[1].15.\u00a0 If you look at the chassis layout above, we know this is on the middle chassis, slot 1, bit 15.\u00a0 \u00a0If this was in your plant, you could locate this on your schematic to find the field device wired to this terminal.\u00a0 \u00a0It&#8217;s possible the input is not made because a limit switch is bent or a wire is broken.\u00a0 Somehow, you need to get a voltage to this terminal, and then you will see the bit intensify in logic (the instruction will turn green).\u00a0 Once this problem is solved, we cross reference safetys[7].\u00a0 This is an internal bit, and we need to go to it&#8217;s output.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1598 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/bitzerooutput.png\" alt=\"Bit Zero Output\" width=\"612\" height=\"55\" data-srcset=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/bitzerooutput.png 612w, https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/bitzerooutput-300x27.png 300w\" data-sizes=\"(max-width: 612px) 100vw, 612px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 612px; --smush-placeholder-aspect-ratio: 612\/55;\" \/><\/p>\n<p>Here, we see the output safetys[7] is not is not energized because\u00a0 warnings[31] is not made.\u00a0 Again this is an internal bit.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1599 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/safety7.png\" alt=\"Safety 7\" width=\"664\" height=\"56\" data-srcset=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/safety7.png 664w, https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/safety7-300x25.png 300w\" data-sizes=\"(max-width: 664px) 100vw, 664px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 664px; --smush-placeholder-aspect-ratio: 664\/56;\" \/><\/p>\n<h2>The Final Rung<\/h2>\n<p>Now we can see warnings[31] output\u00a0 The only conditions left to fix are real world inputs now.\u00a0 We need to get a voltage on Slot 0 of the bottom chassis, bit 1 (remote_aent)..\u00a0 We also need a voltage on terminal 12, slot 1 of the SLC chassis (remote_asb).\u00a0 You might need your schematic and your meter, but since those are real world inputs, we need to fix them in the real world.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1600 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/warnings31.png\" alt=\"Warning 31\" width=\"614\" height=\"119\" data-srcset=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/warnings31.png 614w, https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/warnings31-300x58.png 300w\" data-sizes=\"(max-width: 614px) 100vw, 614px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 614px; --smush-placeholder-aspect-ratio: 614\/119;\" \/><\/p>\n<p>Once all problems have been solved, then we can go back to our bookmark (at our original starting rung).\u00a0 We can see the output is now energized.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-1601 lazyload\" data-src=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/problemsolved.png\" alt=\"Problem Solved\" width=\"664\" height=\"103\" data-srcset=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/problemsolved.png 664w, https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/problemsolved-300x47.png 300w\" data-sizes=\"(max-width: 664px) 100vw, 664px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 664px; --smush-placeholder-aspect-ratio: 664\/103;\" \/><\/p>\n<p>Remember bit_array[0] output had the ONS instruction before it, so it was only true for one scan, however, our output stays on because of the seal.<\/p>\n<p>For more information on ControlLogix, visit the <a href=\"https:\/\/bryceautomation.com\/index.php\/category\/controllogix\/\">ControlLogix Category<\/a> page, or simply choose &#8220;ControlLogix&#8221; from the menu bar above.<\/p>\n<p>&nbsp;<\/p>\n<p>&#8211;Ricky Bryce<\/p>\n<div id=\"bryce-4071387171\" class=\"bryce-after-content bryce-entity-placement\"><script async src=\"\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-8316758073402323\" crossorigin=\"anonymous\"><\/script><ins class=\"adsbygoogle\" style=\"display:block;\" data-ad-client=\"ca-pub-8316758073402323\" \ndata-ad-slot=\"4667596182\" \ndata-ad-format=\"auto\"><\/ins>\n<script> \n(adsbygoogle = window.adsbygoogle || []).push({}); \n<\/script>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Introduction to Troubleshooting a ControlLogix Output The most common problems on a system using ControlLogix are usually field devices.\u00a0 \u00a0Occasionally an I\/O module can fail.\u00a0 Most of the time, however we are using RSLogix\/Studio 5000 to find a failed field device.\u00a0 In this document, we will be troubleshooting a ControlLogix output.\u00a0 We will locate the <a class=\"moretag btn btn-primary\" href=\"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/\">Read More \u00bb<\/a><\/p>\n","protected":false},"author":1,"featured_media":1585,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[114,115],"class_list":{"0":"post-1583","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-controllogix","8":"tag-controllogix-troubleshooting","9":"tag-outputs","10":"czr-hentry"},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.3 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Troubleshooting a ControlLogix Output and navigating through logic.<\/title>\n<meta name=\"description\" content=\"How to locate an output in the ControlLogix processor using Studio 5000, and navigate through the project to find failed field devices.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Troubleshooting a ControlLogix Output and navigating through logic.\" \/>\n<meta property=\"og:description\" content=\"How to locate an output in the ControlLogix processor using Studio 5000, and navigate through the project to find failed field devices.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/\" \/>\n<meta property=\"og:site_name\" content=\"Bryce Automation\" \/>\n<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/ricky.bryce.7\" \/>\n<meta property=\"article:published_time\" content=\"2018-07-22T15:29:56+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2018-07-22T15:30:38+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/chassislayoutwithlight.png\" \/>\n\t<meta property=\"og:image:width\" content=\"827\" \/>\n\t<meta property=\"og:image:height\" content=\"566\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Ricky\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/2018\\\/07\\\/22\\\/troubleshooting-a-controllogix-output\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/2018\\\/07\\\/22\\\/troubleshooting-a-controllogix-output\\\/\"},\"author\":{\"name\":\"Ricky\",\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/#\\\/schema\\\/person\\\/5d5b0f6f6ad768f1ee52968338e63af7\"},\"headline\":\"Troubleshooting a ControlLogix Output\",\"datePublished\":\"2018-07-22T15:29:56+00:00\",\"dateModified\":\"2018-07-22T15:30:38+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/2018\\\/07\\\/22\\\/troubleshooting-a-controllogix-output\\\/\"},\"wordCount\":1295,\"commentCount\":2,\"image\":{\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/2018\\\/07\\\/22\\\/troubleshooting-a-controllogix-output\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/bryceautomation.com\\\/wp-content\\\/uploads\\\/2018\\\/07\\\/chassislayoutwithlight.png\",\"keywords\":[\"ControlLogix Troubleshooting\",\"outputs\"],\"articleSection\":[\"ControlLogix\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/2018\\\/07\\\/22\\\/troubleshooting-a-controllogix-output\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/2018\\\/07\\\/22\\\/troubleshooting-a-controllogix-output\\\/\",\"url\":\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/2018\\\/07\\\/22\\\/troubleshooting-a-controllogix-output\\\/\",\"name\":\"Troubleshooting a ControlLogix Output and navigating through logic.\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/2018\\\/07\\\/22\\\/troubleshooting-a-controllogix-output\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/2018\\\/07\\\/22\\\/troubleshooting-a-controllogix-output\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/bryceautomation.com\\\/wp-content\\\/uploads\\\/2018\\\/07\\\/chassislayoutwithlight.png\",\"datePublished\":\"2018-07-22T15:29:56+00:00\",\"dateModified\":\"2018-07-22T15:30:38+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/#\\\/schema\\\/person\\\/5d5b0f6f6ad768f1ee52968338e63af7\"},\"description\":\"How to locate an output in the ControlLogix processor using Studio 5000, and navigate through the project to find failed field devices.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/2018\\\/07\\\/22\\\/troubleshooting-a-controllogix-output\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/2018\\\/07\\\/22\\\/troubleshooting-a-controllogix-output\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/2018\\\/07\\\/22\\\/troubleshooting-a-controllogix-output\\\/#primaryimage\",\"url\":\"https:\\\/\\\/bryceautomation.com\\\/wp-content\\\/uploads\\\/2018\\\/07\\\/chassislayoutwithlight.png\",\"contentUrl\":\"https:\\\/\\\/bryceautomation.com\\\/wp-content\\\/uploads\\\/2018\\\/07\\\/chassislayoutwithlight.png\",\"width\":827,\"height\":566,\"caption\":\"Chassis Layout\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/2018\\\/07\\\/22\\\/troubleshooting-a-controllogix-output\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/bryceautomation.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Troubleshooting a ControlLogix Output\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/#website\",\"url\":\"https:\\\/\\\/bryceautomation.com\\\/\",\"name\":\"Bryce Automation\",\"description\":\"Automating Home and Industry...\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/bryceautomation.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/#\\\/schema\\\/person\\\/5d5b0f6f6ad768f1ee52968338e63af7\",\"name\":\"Ricky\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/bryceautomation.com\\\/wp-content\\\/wphb-cache\\\/gravatar\\\/a8f\\\/a8fe6bf79d292b388ffee281ccb12488x96.jpg\",\"url\":\"https:\\\/\\\/bryceautomation.com\\\/wp-content\\\/wphb-cache\\\/gravatar\\\/a8f\\\/a8fe6bf79d292b388ffee281ccb12488x96.jpg\",\"contentUrl\":\"https:\\\/\\\/bryceautomation.com\\\/wp-content\\\/wphb-cache\\\/gravatar\\\/a8f\\\/a8fe6bf79d292b388ffee281ccb12488x96.jpg\",\"caption\":\"Ricky\"},\"sameAs\":[\"http:\\\/\\\/bryceautomation.com\",\"https:\\\/\\\/www.facebook.com\\\/ricky.bryce.7\",\"https:\\\/\\\/www.linkedin.com\\\/in\\\/ricky-bryce-4367a416\\\/\"],\"url\":\"https:\\\/\\\/bryceautomation.com\\\/index.php\\\/author\\\/ricky\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Troubleshooting a ControlLogix Output and navigating through logic.","description":"How to locate an output in the ControlLogix processor using Studio 5000, and navigate through the project to find failed field devices.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/","og_locale":"en_US","og_type":"article","og_title":"Troubleshooting a ControlLogix Output and navigating through logic.","og_description":"How to locate an output in the ControlLogix processor using Studio 5000, and navigate through the project to find failed field devices.","og_url":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/","og_site_name":"Bryce Automation","article_author":"https:\/\/www.facebook.com\/ricky.bryce.7","article_published_time":"2018-07-22T15:29:56+00:00","article_modified_time":"2018-07-22T15:30:38+00:00","og_image":[{"width":827,"height":566,"url":"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/chassislayoutwithlight.png","type":"image\/png"}],"author":"Ricky","twitter_card":"summary_large_image","schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/#article","isPartOf":{"@id":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/"},"author":{"name":"Ricky","@id":"https:\/\/bryceautomation.com\/#\/schema\/person\/5d5b0f6f6ad768f1ee52968338e63af7"},"headline":"Troubleshooting a ControlLogix Output","datePublished":"2018-07-22T15:29:56+00:00","dateModified":"2018-07-22T15:30:38+00:00","mainEntityOfPage":{"@id":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/"},"wordCount":1295,"commentCount":2,"image":{"@id":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/#primaryimage"},"thumbnailUrl":"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/chassislayoutwithlight.png","keywords":["ControlLogix Troubleshooting","outputs"],"articleSection":["ControlLogix"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/","url":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/","name":"Troubleshooting a ControlLogix Output and navigating through logic.","isPartOf":{"@id":"https:\/\/bryceautomation.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/#primaryimage"},"image":{"@id":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/#primaryimage"},"thumbnailUrl":"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/chassislayoutwithlight.png","datePublished":"2018-07-22T15:29:56+00:00","dateModified":"2018-07-22T15:30:38+00:00","author":{"@id":"https:\/\/bryceautomation.com\/#\/schema\/person\/5d5b0f6f6ad768f1ee52968338e63af7"},"description":"How to locate an output in the ControlLogix processor using Studio 5000, and navigate through the project to find failed field devices.","breadcrumb":{"@id":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/#primaryimage","url":"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/chassislayoutwithlight.png","contentUrl":"https:\/\/bryceautomation.com\/wp-content\/uploads\/2018\/07\/chassislayoutwithlight.png","width":827,"height":566,"caption":"Chassis Layout"},{"@type":"BreadcrumbList","@id":"https:\/\/bryceautomation.com\/index.php\/2018\/07\/22\/troubleshooting-a-controllogix-output\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/bryceautomation.com\/"},{"@type":"ListItem","position":2,"name":"Troubleshooting a ControlLogix Output"}]},{"@type":"WebSite","@id":"https:\/\/bryceautomation.com\/#website","url":"https:\/\/bryceautomation.com\/","name":"Bryce Automation","description":"Automating Home and Industry...","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/bryceautomation.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/bryceautomation.com\/#\/schema\/person\/5d5b0f6f6ad768f1ee52968338e63af7","name":"Ricky","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/bryceautomation.com\/wp-content\/wphb-cache\/gravatar\/a8f\/a8fe6bf79d292b388ffee281ccb12488x96.jpg","url":"https:\/\/bryceautomation.com\/wp-content\/wphb-cache\/gravatar\/a8f\/a8fe6bf79d292b388ffee281ccb12488x96.jpg","contentUrl":"https:\/\/bryceautomation.com\/wp-content\/wphb-cache\/gravatar\/a8f\/a8fe6bf79d292b388ffee281ccb12488x96.jpg","caption":"Ricky"},"sameAs":["http:\/\/bryceautomation.com","https:\/\/www.facebook.com\/ricky.bryce.7","https:\/\/www.linkedin.com\/in\/ricky-bryce-4367a416\/"],"url":"https:\/\/bryceautomation.com\/index.php\/author\/ricky\/"}]}},"_links":{"self":[{"href":"https:\/\/bryceautomation.com\/index.php\/wp-json\/wp\/v2\/posts\/1583","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bryceautomation.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bryceautomation.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bryceautomation.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/bryceautomation.com\/index.php\/wp-json\/wp\/v2\/comments?post=1583"}],"version-history":[{"count":0,"href":"https:\/\/bryceautomation.com\/index.php\/wp-json\/wp\/v2\/posts\/1583\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bryceautomation.com\/index.php\/wp-json\/wp\/v2\/media\/1585"}],"wp:attachment":[{"href":"https:\/\/bryceautomation.com\/index.php\/wp-json\/wp\/v2\/media?parent=1583"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bryceautomation.com\/index.php\/wp-json\/wp\/v2\/categories?post=1583"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bryceautomation.com\/index.php\/wp-json\/wp\/v2\/tags?post=1583"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}