PLC Troubleshooting - RSLogix 500 SLC MicroLogix Mathematical Overflow Fault Code Finding Techniques

แชร์
ฝัง
  • เผยแพร่เมื่อ 13 ม.ค. 2020
  • PLC Troubleshooting - RSLogix 500 SLC MicroLogix Mathematical Overflow Fault Code Finding Techniques
    Visit SolisPLC.com for more Tutorials, Information & to connect with the Community
    The ability to effectively troubleshoot control systems comes from practice. By going through the steps, again and again, an experienced electrician, technician or engineer, will develop an eye for how to fix most problems. By practicing this skill, the individual will take less time on future problems they encounter. That being said, what is an effective starting process? Which steps would we typically take?
    Step 1 - Resetting the Fault
    It's important to note that in production, every minute of downtime is expensive. Therefore, unless a potential problem of doing so is apparent, the first step is often to reset the PLC and set it back to "Run". An intermittent fault may have been caused by a deadlock in the software, an electrical malfunction or a glimpse in the system. These aren't common, but they do occur.
    Step 2 - Using the Error Description Functionality
    Every Programmable Logic Controller that throws a fault will present the user with a certain description. In RSLogix 500, this description may be accessed through the fault menu in the top left corner.
    Once the menu is opened, it's important to take note of the fault. This description will aid in the following steps of the process and may give the programmer a good idea of what the problem is.
    Step 3 - Fault Research
    Fault codes may be typed directly into Google. Chances are, someone has already encountered the same fault you're seeing. The top results within the search engine are very good at resolving the fault of our experience. Note that some of these resources could be from a forum, blog post or another user-created resource. Other times, the fault code along with an extensive troubleshooting guide will be available from an OEM document such as a datasheet. Do not disregard user-generated content as end-users may often encounter faults that aren't always known by the OEMs.
    Step 4 - Technical Support Channels
    If none of the above methods worked, it's time to reach out for professional help. If you have access to paid channels such as Rockwell Tech Connect, it's time to make a phone call. You'll be connected with an expert from the company who should be able to guide you toward a resolution of the problem. If this isn't available to you, it's often possible to obtain help from a local system integration company. If you've purchased equipment from a local distributor, they may be of assistance as well.
    Step 5 - New Fault Documentation
    If you're still stuck, it's advised to post your fault with as many details as possible on an end-user community forum. As mentioned above, it's highly unlikely that you've encountered an issue that has never been seen before. Create a post with as many details as possible on the following forum: SolisPLC Forums
    Full Tutorial:
    solisplc.com/plc-troubleshoot...
    Find us on social media:
    Web: solisplc.com/
    Forum: solisplc.com/forum/
    LinkedIn: / solisplc
    Facebook: / solisplc
    Instagram: / solisplc
    Twitter: / solis_plc
    Other Cool Content:
    PowerFlex 525 VFD Setup - Programming Parameters Wiring Diagram RSLogix Studio 5000 EtherNet IP Address Start Stop
    • PowerFlex 525 VFD Setu...
    PLC Data Types & Structures - Allen Bradley PLC RSLogix 5000 Basics Programming BOOL INT DINT Arrays
    • PLC Data Types & Struc...
    Raspberry Pi Ignition Edge Installation | Industrial SCADA Inductive Automation Tutorial NOOBS IoT
    • Raspberry Pi Ignition ...
    PLC Networking Basics Tutorial | RSLinx Classic Lite EtherNet/IP Driver Configuration User Training
    • PLC Networking Basics ...
    PLC Interview Question - Array FIFO Logic Programming Example Average Rolling Mean RSLogix 5000
    • PLC Interview Question...

ความคิดเห็น • 9

  • @junsiason4501
    @junsiason4501 8 หลายเดือนก่อน

    Fantastic! Very Helpful

  • @cooperalisa
    @cooperalisa 2 ปีที่แล้ว

    Thank you sooo much for your logical explanation. You, Sir, are a rockstar in this world.

  • @valmontdain
    @valmontdain 3 ปีที่แล้ว +1

    Hello sir,
    Thanks for your many wonderful tutorials, you are my very major plug in anything that has to do with PLC Allen Bradley programming.
    Pls, how do you locate the exact rung that the erro is located among the myriads of rungs in a typical PLC program?

  • @mattraymond2935
    @mattraymond2935 4 ปีที่แล้ว +2

    good 1 had this happen at work

  • @arulkumar927
    @arulkumar927 2 ปีที่แล้ว

    Really helpfull bro, thank you for video🥳🥳🥳🥳

  • @kevin00861
    @kevin00861 2 ปีที่แล้ว

    Thank you so much Prof.
    I've a question, please
    Why didn't you look at S1 faults in the fault dialogue ?
    Why did you only examine only the S5 ?

  • @sudhandiramanisundaram4909
    @sudhandiramanisundaram4909 9 หลายเดือนก่อน

    Hi, please advise how to resolve the negative value entered into the timer PRE to avoid error code 34 and stop the CPU. What steps can we take to resolve this issue?

  • @tonycosmas9535
    @tonycosmas9535 2 ปีที่แล้ว +1

    Thanks a lot you're a source of help, how can someone get a hands on training with you?

    • @SolisPLC
      @SolisPLC  2 ปีที่แล้ว

      Hey Tony, glad to hear we could help :) You can find all our training courses on SolisPLC.com
      If you have any technical questions you need help with, make sure to post them on our forum (forum.solisplc.com) and we'll be happy to help.