Joe E.

MrPLC Member
  • Content count

    1586
  • Joined

  • Last visited

Posts posted by Joe E.


  1. I think you're going to have trouble with that distance. Just as a reference, I pulled up the guidelines for Rockwell drives (because they're handy) and the max distance they support with filtering varies by size and series of drive but maxes out at 365m or so.
    https://literature.rockwellautomation.com/idc/groups/literature/documents/in/drives-in001_-en-p.pdf
     

    Your distance is almost 6 times longer than that. Definitely reach out to your drive manufacturer for guidance. You may end up having to build an enclosure near the pond for the drive.

    1 person likes this

  2. We ordered 9324-RLDMLPE, the Multi-language pack that licenses use of ST, FBD, and SFC. It's an add-on to the standard edition license that lets us use the other programming languages. There may be something you can order to just get ST, but I'd probably just get the multi-pack. You'd have to reach out to your local distributor to find out. You'll need to talk to them for pricing anyway, and AB's licensing system is messy enough you'll want expert assistance getting the right thing.


  3. The manual itself doesn't provide much info but it links to an Excel spreadsheet with a little more info:
    https://literature.rockwellautomation.com/idc/groups/literature/documents/rd/2198-rd005_-en-p.xlsx

    For "NODE FLT 02 – PROC WATCHDOG nn", the spreadsheet says:
     

    Quote

    Fault:
    Processor Watchdog Fault
    The processor on the power board or control board failed to update in a certain amount of time.
    The Possible Solutions are the same for all nn sub-codes.

    Action:
    •     Cycle control power
    •     Return drive for repair if fault continues

    Did you find this tech note (access level: TechConnect):
    https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/635513/loc/en_US#__highlight

    It adds another possible fix:
     

    Quote

    Upgrade firmware, or reflash drive with current firmware

     

    1 person likes this

  4. Some faults will cause the PLC to erase the program in memory. Without going online with the software while the fault is active, it's hard to be more specific.

    The 1400 has an LCD screen where you can navigate to "Monitoring" and select file #2, which is processor status.  You can then look at individual words. Word s:6 is your major error code. I've never used the LCD to diagnose an issue since it's easier with the software so I don't know if the LCD still works when the processor is faulted, but that's where I would go if I didn't have a license.

    1 person likes this

  5. I found a comparison tech note (access level: everyone) that compares them:
    https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1032455/loc/en_US#__highlight
    It doesn't show a difference that should affect trending, but there could be other things different.

    There's another more detailed comparison document here:
    https://literature.rockwellautomation.com/idc/groups/literature/documents/sp/2711p-sp011_-en-p.pdf
    That one also doesn't mention trending or datalogs.


  6. I've worked on machines with the Banner safety controllers and have done upgrades on machines where we used Keyence. In general I prefer Keyence over Banner but I wouldn't be upset to work with either. We have other machines with Schmersal and ABB/Jokab controllers. The Jokab are ok but the Schmersal are kind of a pain, especially if you're not absolutely fanatical about keeping up with your source files. You can upload out of them but only a compiled runtime to transfer back into another controller. To monitor/edit you need the matching source file. In the AB world, they also have the 440C-CR30-... controller that's programmed in CCW (free) or can be embedded in a Logix project. I found them to be useful but their IO is very limited for the price and can't be expanded (with safety IO).


  7. That's what I suspected would happen but I haven't used ADC before (heard "horror stories" from a colleague about the firmware versions having to be perfectly aligned and we very rarely had to replace one, so didn't seem worth it). I guess I expected that ADC would be contained fully within the Logix controller and wouldn't affect a disconnected drive at all, which seems to be what you found as well with your experiment.

    So basically, with the network unplugged, the drive parameters set to factory default, the STO satisfied, and all inputs disconnected except input 1....the drive should respond to HIM keypad control. I would think, at least...


  8. So, F059 is "Safety Open". Terminal 4 is a DC Common. It's probable that the system is using an external 24V supply and the drive's terminal 4 is connected to the system's 0V so S1 and S2 can use the system's 24V source. Lifting the wire on terminal 4 causes S1/S2 to lose their 0V reference and show open.

    Btw, that confirms that the STO function is not what's keeping your drive from running via the keypad.

    Have you tried to set P046-P051 back to their default values and t062-t068 to 0 "Not Used"?