User: ptonsparky, Location: NE (9.06 miles @5.9 Degrees from Winged Horses)
Asked on: Saturday, November 9, 2024 at 7:31 am EST
Answered on: Thursday, March 6, 2025 at 5:02 am EST
Question: I have a customer with an AB 1400 I put in many years ago. I've had to reset it twice, I think, going on line with it. Power reset doesn't work.Retired now and currently 11 hours away, I get the SOS call. My former employee and his new boss did a physical work around.What is the bit number I could use to do the reset via its HMI?IDK why I finally thought of it and maybe its not possible.
Okay, let's break down the situation and explore options for remotely resetting an Allen-Bradley MicroLogix 1400 PLC via its HMI, given your retired status and the distance involved.
Understanding the Problem
MicroLogix 1400 Lock-Up
The fact that power cycling doesn't resolve the issue suggests a deeper problem than just a program crash. It's likely a processor fault, a software glitch, or corrupted memory.
Physical Workaround
The "physical workaround" your former employee and his boss implemented is a major concern. It likely means they manually cleared memory, which could mean the loss of program, force, and other data.
Remote Reset Goal
You want a way to remotely trigger a PLC reset without physically interacting with the PLC. This is valuable to avoid on-site visits and potentially recover from less severe lock-ups.
The HMI Reset Approach (and its Limitations)
The core idea is to write logic in the PLC program that, when triggered by a button (or other input) on the HMI, will effectively reset the PLC. While it's technically possible, it has important limitations:1.
PLC Must Be Partially Functional
The PLC must be in a state where it can still execute some logic, even if it's locked up or behaving erratically. If the processor is completely frozen, this approach will fail.2.
HMI Must Be Able to Communicate
The HMI must still be able to communicate with the PLC to write to the tag that triggers the reset logic. If communication is lost, this won't work.3.
Program Access Required
You need to access the PLC program to implement the reset logic, compile, and download it. You may need to use RSLogix500 or a similar Rockwell Automation software
How to Implement an HMI-Triggered Reset (if possible)
Here's the general approach to implement in the PLC code:1.
Create a Reset Bit
Define a Boolean tag (a bit) in your PLC program. This will be the "reset command" from the HMI. Let's call this tag `HMI_Reset_Command`.2.
Reset Logic (Ladder Logic Example)
The core logic will use `HMI_Reset_Command` to trigger a series of actions to reset the PLC, in a way that is as close as possible to a software reset.
Important
The reliability of this depends entirely on the nature of the lock-up. It's not guaranteed to work in all cases.ladder// rung 1: HMI Reset Command to Initiate Sequence---[ HMI_Reset_Command ]---------------------(OTE HMI_Reset_Running )---// rung 2: One shot HMI Reset Running---[HMI_Reset_Running]---[ONS ONE_SHOT_RESET]---------------------(OTE HMI_Reset_One_Shot )---// Rung 3:---[HMI_Reset_Running]---[Timer Reset]----------------------------------------------------------- (RES T4:0)---// Rung 4: Clear memory, force, reset---[HMI_Reset_One_Shot ]---[MCR Master Control Reset]-----------------------------------------(MCR Z:0)------[MOV 0 V30]---------------[/MCR]// rung 5: Disable Reset Command After completion or timeout---[Timer DN]----------------------------------------------------------- (OTL HMI_Reset_Running)---
`HMI_Reset_Command`
Boolean tag controlled by the HMI. When set to 1, it starts the reset sequence.
`HMI_Reset_Running`
A retentive bit that signals the reset sequence is in progress. This prevents retriggering while the reset is happening.
`ONE_SHOT_RESET`
One Shot. Only triggers one time when HMI_Reset_Running changes state
`T4:0`
Timer.
`V30`
File V30 is defined as integer.
`MCR Z:0`
Z is the number of files for the master control reset.3.
HMI Configuration
On your HMI, add a button or other control. Configure this control to write to the `HMI_Reset_Command` tag in the PLC. When the button is pressed, `HMI_Reset_Command` should be set to 1 (or toggled). When the button is released `HMI_Reset_Command` should be set to 0 (or toggled).
Important Considerations and Warnings
Data Loss
Implementing a reset this way will likely cause data loss. Any data stored in the PLC's memory will be cleared. This could include recipes, production counts, running totals, etc. Make sure the customer is aware of this risk. Backups are crucial! Unintended Consequences
A poorly designed reset sequence could leave the PLC in an unstable or unusable state. Thoroughly test the logic in a safe environment before deploying it in a production system.
Alternative Reset Methods
Before resorting to a software reset, consider other remote troubleshooting steps:
Check PLC Status
If the HMI can read any data from the PLC, try to read status words or diagnostic flags. This might give you a clue as to the cause of the lock-up.
Review Recent Changes
Ask the customer or your former employee about any recent changes to the PLC program, HMI configuration, or connected devices. This can often point to the source of the problem.
Why the Physical Workaround Was Problematic
Without knowing exactly what the "physical workaround" was, I can assume that, at the very least, they may have manually cleared memory, which could mean the loss of program, force, and other data.
Recommendation
Gather More Information
Try to get as much detail as possible about the nature of the lock-up, the "physical workaround" that was used, and any recent changes to the system.2.
Assess Communication
Can the HMI still read any data from the PLC? This is critical for the HMI-triggered reset approach to work.3.
Backup
If possible (and if the PLC isn't completely bricked), try to get a backup of the PLC program before making any changes. This is essential for recovery if things go wrong.4.
Remote Connection
If there is a remote connection to the PLC, consider connecting to the PLC remotely and looking at the status and error codes. It may be that a remote force of the output, if possible, will fix the issue.5.
Caution
Explain the risks of data loss and potential instability to the customer before implementing any remote reset solution. The physical workaround implemented may have damaged the MicroLogix or program.
Important Disclaimer: I am an AI chatbot and cannot provide definitive troubleshooting advice for industrial control systems. Always consult with a qualified automation professional when working with PLCs and HMIs. The information provided here is for informational purposes only. Flag for review