Hello experts, I trust you are all having a splendid day. I am facing issues with establishing communication between my CompactLogix 1769-L24ER and my InTouch application. Below are the details along with screenshots of the setup.
My controller is currently operating on firmware version 34.012. Within the PLC program, I have created a local BOOL tag named PB1From SMC (OCMC 2023). I have configured an ABCIP OI server on my local node with the controller's IP address, which I can successfully ping. The "ethernet port on CPU module" box has been checked. In the [Device Groups] tab, I have specified my topic as: LOGIX_1
In InTouch WindowMaker (version 20.0.000, c2020), running on the same local node, I have set the access name to:AN: OIServer1Node Name:
To optimize your PLC programming, consider changing the scope of your tags to controller level rather than program level. By using controller scope for your tags, ABCIP and the WW item name will be able to access locally scoped tags in the MainRoutine. It is recommended to keep HMI tags at the controller scope for easier management.
Welcome to the forum! While I'm still new to Wonderware, I have a hunch that your issue might be related to the scope of the tag. When dealing with tags like PB1, it's important to consider whether it is program scoped or controller scoped. By making PB1 a controller scoped tag, you can simplify the process and avoid confusion between different programs. Once you have it working, you can then update the Wonderware tag to specify the program-scoped tag. This usually involves using a notation like [MainProgram]PB1 or MainProgram\PB1. I personally prefer using global scoped tags over program scoped tags, especially for SCADA interfaces. Remember, simplicity often wins in these situations!
Thank you @robertmee for your response. I have created a new tag scoped to the controller (refer to the attached image). I have also edited the "item name" in the tagname dictionary for my previous intouch tag to be PB99. Despite launching WV, the issue still remains unresolved. Any suggestions? (Link to image provided: https://i.imgur.com/bvuCD0k.png) EDIT: Thank you @ASF for your response as well. Despite creating a controller scoped tag, the issue persists. Any further advice?
Outpizza replied to @robertmee's message and thanked him for his response. He created a new tag that is scoped to the controller (refer to the image provided). In the dictionary of tag names, he modified the "item name" of his previous Intouch tag to be PB99. Despite launching WV, the issue persists. Any suggestions? In addition, he addressed @ASF's response and mentioned that he had created a controller-scoped tag, but the problem still remains. It is recommended to stop and restart the ABCIP driver in SMC after making any changes to the PLC tags. Also, it would be helpful to check the SMC local log for any relevant information. Is the PB99 tag visible under Diagnostics/Messages in the log? Please include an image of the Logix CPLX_000 leftmost tag and the device groups tag.
It appears that the Input/Output server is not currently operational on the picture.
It sounds like you've done a thorough job setting everything up, but that "data quality" warning often points to a communication issue between the InTouch application and the PLC. Have you checked the diagnostics or status of the ABCIP OI server to ensure it's properly connected and that the PB1 tag is correctly defined? Sometimes enabling "auto-report" for tags can help establish better communication. Additionally, double-check the tag's access rights and ensure that you’ve configured the read/write permissions correctly. It might also be worth restarting both the PLC and InTouch to reset any transient connection issues. Good luck, and I hope you get it sorted out soon!
It sounds like you're really close to getting everything set up correctly! One thing to double-check is the data type compatibility between your InTouch tag and the PLC BOOL tag. Sometimes, even if everything is correctly configured, data quality issues can arise if the expected data type doesn't match exactly. Also, ensure that your InTouch application has the necessary permissions to write to the PLC and that you've set the refresh properties appropriately to ensure live data is being read. Lastly, try restarting both your PLC and the InTouch application after making changes to see if that resolves the communication issue. Good luck, you're on the right track!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.