Troubleshooting Unexpected Bit Activation in PLC Programming

Question:

For 7 years, I have intermittently engaged in PLC programming with AB, Siemens, and Automation Direct. While I usually excel in this area, I recently encountered a challenge starting a new AB program from scratch. It seems that some memory bits are activating unexpectedly, potentially due to a setup error or sequencing issue. This issue reminds me of a similar situation I faced when working on a Siemens PLC project, likely caused by referencing the same memory address using different data types. In the TIA portal, there was a helpful feature that displayed all address locations and their uses. I wonder if RSLogix 5000 offers a similar tool. I suspect there may be a simple mistake in my setup. Even when I create a basic program, I encounter bits that latch and do not release, even without using any latching commands. Any assistance or advice on this matter would be greatly appreciated. Thank you.

Top Replies

To enable homing, utilize one-shot (ONS) tags with matching tag names to activate the homing bit. Be sure to review and avoid using redundant tag names.

Execute the verify controller function and address any warnings that may arise during the process. This will help ensure that your system is running smoothly and efficiently.

It is essential that each Object Name Server (ONS) is assigned a unique tag name to avoid conflicts with other instructions. It is not recommended to use the same tag for the ONS, Object List (OTL), and Object Unit (OTU) as this can cause issues. The OTL and OTU can share the same tag, but the ONS must have a distinct tag. As highlighted by Scottryan, it is important to address any warnings that may arise. Furthermore, each Program in your project can have its own designated set of Program Tags. For example, you can assign a "HOMING" tag in Program ST1 and create another "HOMING" tag in Program ST2. However, it is worth noting that Controller Tags are global and apply across all Programs within the project.

The way ONS functions in AB seems different from what I'm familiar with. I was under the impression that each time I enable or latch my homing bit, all homing ONS should activate for a single scan. If this is not the case, how can I achieve that?

This method is effective. The ONS needs a distinctive tag that stands out.

It sounds like you're dealing with a tricky issue! In RSLogix 5000, there isn’t a direct equivalent to the TIA Portal's feature, but you can use the “Monitor” tool to keep an eye on your memory addresses and their states, which might help you identify any unexpected behavior. Make sure to double-check your tag configuration and the data types you’re using; sometimes, a simple mismatch can lead to weird latching issues. Also, reviewing your project's execution order and ensuring there are no unintended loops or conditions can be a good place to catch those hidden pitfalls. Good luck, and don't hesitate to reach out with updates!

It sounds like you're dealing with a frustrating issue! In RSLogix 5000, one helpful tool you could try is the 'Cross Reference' feature, which allows you to see where and how your tags are being used throughout your program—similar to what you found in TIA Portal. It can definitely help identify if something is inadvertently referencing the same memory or if there's a logic loop causing the latching behavior. Also, double-check your program's initial conditions; sometimes a simple oversight in how bits are being initialized can lead to unexpected results. If all else fails, incrementally disable logic sections to isolate the problem bit. Good luck!

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

âś…   Work Order Management

âś…   Asset Tracking

âś…   Preventive Maintenance

âś…   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

To add a comment, please sign in or register if you haven't already..   

Frequently Asked Questions (FAQ)

FAQ: 1. What could be causing unexpected bit activation in PLC programming?

Answer: - Answer: Unexpected bit activation in PLC programming could be caused by setup errors, sequencing issues, referencing the same memory address with different data types, or unintentional latching of bits without explicit latching commands.

FAQ: 2. How can I troubleshoot unexpected bit activation in an Allen Bradley (AB) PLC program created from scratch?

Answer: - Answer: To troubleshoot unexpected bit activation in an AB PLC program, you can check for setup errors, review the sequencing of your program, ensure consistent data type usage for memory addresses, and look for any unintended latching behavior in your logic.

FAQ: 3. Does RSLogix 5000 offer a tool similar to the TIA portal's feature that displays all address locations and their uses?

Answer: - Answer: RSLogix 5000 may offer tools or features that allow users to view address locations and their corresponding uses within the program. Users can explore the software's documentation or seek guidance from the manufacturer's support resources for more information on accessing such tools.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  â†’