Troubleshooting e Symbol Error in RSLogix 5000: Unable to View Verify Rung Data

Question:

As a hobbyist programmer, I am using RSLogix 5000 (full edition, version V20.01.00) with a 1768-L45 CompactLogix 5345 PLC for a non-life safety project. Recently, I added new rungs in an online edit, but they are showing an error symbol "e" continuously. Despite knowing that this indicates an error, I am unable to identify the issue using the "verify rung" function. The software is being used in a virtual machine, which may be causing the error details to not display properly. The rung in question involves the use of string tags to display the day of the week on an HMI. This is a new experience for me, and I may not fully grasp how to work with string tags. I am seeking assistance in resolving the error indicated by the "e" symbol on the rung. Any insights on what may be wrong with the setup are greatly appreciated.

Top Replies

Is it possible for the MOV instruction to transfer string data on a PLC model? You might need to consider using the COP instruction or one of the available string instructions for this task.

To access errors in the ladder editor, navigate to the view menu and select the option to display errors. This window can be pinned in place for easy reference. If you encounter the error "Missing reference to array element," it may be due to the complexity of working with strings. Ensure you are addressing the array correctly, such as DOW_Tue.DATA[0]. Alternatively, consider using a COP instruction for simplicity, like this code: COP DOW_Tue.DATA[0] Day_of_Week.DATA[0] DOW_Tue.LEN. Additionally, you may need to transfer the length of DOW_Tue to Day_of_Week with this code: MOV DOW_Tue.LEN Day_of_Week.LEN.

Unfortunately, I don't have a PLC at v20 to capture screenshots while online. However, the sequence you are searching for is "accept" -> "test" -> "assemble" (if memory serves me correctly). I am unsure about which version introduced the option to "assemble all" in just one step. Essentially, the "e" rungs have not yet been accepted. Additionally, as per @drbitboy, there was a shift at some point from MOV to COP for STRING data types. In more recent programs/controllers, I have been using COP, whereas I recall using MOV in earlier versions. Your rung could very well be perfectly acceptable. Another suggestion is to navigate to the "View" menu and confirm that the "Errors" window is visible. This feature should provide information on any compilation issues.

Check out this website (DISCLAIMER: this link may not be safe for OkiePC users).

Joseph_e2 recommended checking the "View" menu to ensure the "Errors" window is open, as it can help identify any issues the compiler may have. Despite toggling it on and off, there were no visible errors. Thank you to everyone for the suggestions, I will explore those options shortly.

I sympathize with your situation, working with string tags can indeed be tricky when you're first dipping your toes into it. First off, ensure that the string tag has been correctly declared and formatted. Secondly, check if string commands are used correctly within the rung, as improper usage might be the cause of the error. Also, keep in mind that working on a VM can introduce a certain degree of unpredictability, so errors might not be solely related to your PLC programming. Lastly, I suggest you try running diagnostics with RSLogix itself. It often helps identify more complex issues.

That's an interesting issue you've encountered. Given that you're dealing with string tags, one possible source of the error might be from incorrect string manipulation or parsing. Make sure that you've set up your string tags correctly and also check if your HMI handles string display properly - some may have specific requirements or limitations. The VM environment could potentially be causing some issues, although it's unlikely, but you might want to try running the software directly on a physical machine to cross verify. Lastly, observe the error details carefully, even if they aren't fully displayed, they usually give a clue about the issue. Remember, experimenting and troubleshooting is a part of the learning process!

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. Why am I seeing an error symbol "e" on my rung in RSLogix 5000 despite using the "verify rung" function?

Answer: - The error symbol "e" indicates a problem with the rung, but sometimes the exact issue may not be identified by the software. It's important to carefully review your logic and configuration to troubleshoot the error.

FAQ: 2. Could using RSLogix 5000 in a virtual machine affect error display and troubleshooting?

Answer: - Yes, using RSLogix 5000 in a virtual machine may sometimes lead to display issues with error details. It's recommended to ensure proper settings and compatibility when working with virtual environments.

FAQ: 3. How can I troubleshoot errors related to string tags in RSLogix 5000 rungs?

Answer: - When working with string tags in RSLogix 5000, ensure correct data types, lengths, and configurations are used. Reviewing the logic related to string manipulation and HMI display can help identify potential issues.

FAQ: 4. Any tips for resolving errors indicated by the "e" symbol on rungs in RSLogix 5000?

Answer: - Double-check your logic, verify tag configurations, review any recent changes made, and consider consulting documentation or online resources for troubleshooting tips specific to RSLogix 5000 error symbols like "e".

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  â†’