Hello everyone, I hope you're all doing well. Currently, I am working on a project involving AOI and encountering some issues with online edits... haha. My problem arises when utilizing a UDT that includes a Counter[3] element. These counters are utilized within the AOI but appear to be malfunctioning. They display erratic values that seem like incorrect data. Interestingly, these counters are solely used within the UDT as an In/Out parameter in the AOI. Have any of you encountered similar issues with AOIs? Any suggestions or solutions would be greatly appreciated. Thank you in advance. - Jesus
The unique identifier of the UDT type may be utilized in various locations. It is important to cross-reference this identifier at both the input and output interfaces.
If you are experiencing issues with your SWAG implementation, it could be due to a COP (such as COP MyCounter[2] AOI.Counter[2]) having a length that is not equal to 1. This could result in "junk" data being copied from the memory beyond "MyCounter[2]" into registers beyond AOI.Counter[2] and eventually into Counter[3]. However, without seeing your code, it is hard to provide a precise solution. It is recommended to review your code to identify any discrepancies.
Hi Jesus, it sounds like you've got quite an issue on your hands. I've encountered similar problems in the past and usually, it's caused by mismatched data types or a timing conflict between the AOI and the PLC cycle. You should consider checking how the AOI handles its inputs, specifically the counters. Make sure that the data types are consistent throughout the logic. If this doesn't clear up the problem, you might want to check the timing and ordering of your PLCs cycle. It's possible that your counter updates are being overruled or skipped entirely due to poor timing. Hope this helps!
Hey Jesus, I've experienced a few similar issues with AOIs in the past. I've found that sometimes it's a matter of synchronization within the program. Make sure you properly update and sync your UDT and AOI, and that you aren't overwriting the counter value somewhere else in your code unintentionally. Remember that UDTs are global and if used in another section of code, it might be causing the erratic behavior you've noticed. Check for unnoticed data overlaps as well. I hope this helps a bit, keep us posted.
Hi Jesus! I can relate to your frustrations with AOIs—sometimes they really seem to have a mind of their own! Have you double-checked the initialization of your counters within the UDT? Sometimes, erratic behavior can occur if they aren't properly reset or if there's an unexpected interaction with other parts of the code. Also, consider whether you're inadvertently trying to read or modify the counters simultaneously in different AOIs, which could lead to conflicts. It might help to add some debugging around those counter elements to get more insight into what's happening. Good luck, and I hope you get it sorted soon!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Erratic data in AOI In/Out Counters could be caused by issues such as incorrect data handling, improper initialization, or conflicting logic within the program.
Answer: To troubleshoot AOI In/Out Counters displaying incorrect values, you can check the UDT configuration, verify the logic within the AOI, ensure proper data handling, and review the online edits for any potential errors.
Answer: Common solutions for resolving malfunctioning AOI In/Out Counters include checking for data integrity issues, verifying UDT configurations, reviewing the AOI logic for errors, and ensuring proper initialization of the counters.
Answer: To prevent erratic values in AOI In/Out Counters within a UDT, it is important to properly handle data, ensure correct initialization, validate the logic within the AOI, and conduct thorough testing before deployment.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.