ePLC

MrPLC Member
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ePLC

  • Rank
    Newbie

Profile Information

  • Country Sudan
  1. Yes will do so. Thanks
  2. Hey, So I finally got time for troubleshooting this and got the problem fixed as well. I wasn't sure of how to follow your method mentioned above (because I am a noob) but I found an alternative. I found the problem was resulting from an 'electronic key mismatch' (error 73) so I unchecked the electronic keying boxes in the scan list (Found in the properties of the scanner) and applied the changes. Now the scanning process completes successfully and the drive is communicating with the PLC. I will still investigate further the method you mentioned above as well as learn whats the need for electronic key. Thanks for the help though
  3. Hi, I'm quiet fresh in my career and still new to the PLC world. Currently at my plant we have Allen Bradley PLC's (ControlLogix, PLC 5/30, PLC 2/30). This past year I have understood a little from troubleshooting various problems. But I want to learn in depth. I'm just challenged to find the time to do so. I want to start by learning the basics, interpreting ladder logic, editing, programming, how communication between controllers and field devices takes place etc. Please guide me if you do know any resources, materials, softwares, websites etc. that can help me start learning Greatly appreciate your guidance!
  4. Thanks. I will let you know the results once I get some time to test the above.
  5. Thanks for your welcoming! It is communicating through DeviceNet.
  6. Hi all, I would would greatly appreciate your assistance with the following. Currently I have a powerflex 70 AC drive (Firmware ver. 2.003), connected to ControlLogix (L55), that is frequently tripping due to over heating. I suspected the heat sink fans are not operating so I have made some modifications and placed two small external fans above and below the drive for cooling purposes. Further on I interchanged the existing drive with a similar spare one, which is when I encountered a problem. The spare drive seems to be working normal but the MOD LED is constantly blinking green which indicates the drive is not transferring I/O data. Further on I also noticed the spare drive firmware version is 2.009 which is different from the existing drive firmware version. Can the firmware be causing this problem? If not can someone please direct me in troubleshooting this? I need to resolve this to have a peace of mind in case any problem occurs with the existing drive. Thanks