Hello everyone, I have some important insights to share regarding setting up the new OPC UA server, and I believe this information will be of interest to you, JeremyM. Rockwell's documentation on this process is currently limited, but I am actively working on gathering more information through a ticket with Rockwell. I will continue to update my findings as I progress. If you're looking for guidance on configuring the OPC server, take note of the following TechNotes: - QA67230 - Key details on OPC UA in version 36 - QA67231 - Steps to activate OPC server/client - QA67232 - Tutorial on utilizing OPC client Please be aware that my notes mainly focus on the OPC server, as I have not yet delved into the client side. My testing has been conducted on the 1756-L81E and 1756-L82E models. After consulting with tech support, it appears that the 1756-L81E (along with similar models supporting a maximum of 0 OPC nodes) does not fully support OPC, although it does have the OPC CIP object. For connecting to the OPC server, you can refer to the following details: - OPC Discovery URL: http://address:4840 - OPC TCP URL: opc.tcp://address:4840 - Supported Connection Modes: Basic256Sha256 (Sign and Encrypt), None (No encryption or verification, Insecure) Regarding tag addressing, controller tags are stored in namespace 6 and can be referenced by name. For instance, a controller tag named "TEST" will have an OPC address of "ns=6;s=TEST." Program tags are referenced with the prefix "Program:" followed by the program name and tag name, such as "ns=6;s=Program:MainProgram.PROG_TEST." When it comes to OPC server configuration, you will need to send a message to the controller to enable or disable the OPC server. This setting will be retained after a download, and I recommend using the S:FS (First Scan Bit) to initiate the enable message to ensure OPC activation. By default, the OPC server/client is disabled. For more details on setting up the OPC server, including node counts and performance tests, as well as undocumented messages for additional functionality, please refer to my detailed findings above. I hope this information proves beneficial to your understanding of OPC server setup ~ Trevor.
UPDATE: Rockwell has recently revised TechNote QA67231 to address issues with missing Logix import files and broken images. This update ensures that the necessary files are now included and all images are displaying correctly.
Fantastic! Thank you. It is high time for Rockwell to introduce an OPC UA server, which will greatly benefit their users and enhance connectivity. This addition will streamline operations and improve data communication within industrial systems.
Saving this page for future reference when I need to delve into this topic. Thank you!
Update: Rockwell has recently updated QA67232, which includes sample code for the OPC UA Client documentation.
Here are the node counts for popular tags in the system:PID_ENHANCED = 166 Nodes (Wow!)PID = 69 NodesTIMER = 6 NodesCOUNTER = 8 NodesFBD_TIMER = 13 NodesTOTALIZER = 46 NodesDISCRETE_2STATE = 42 NodesDISCRETE_3STATE = 74 NodesIt is worth mentioning that Rockwell Automation has addressed my inquiry regarding the 1756-L81E controller (and other models with 0 nodes support) stating that they currently do not offer any OPC support (both server and client).
Thanks for the detailed information, Trevor! Your findings are incredibly useful, especially considering the lack of comprehensive documentation from Rockwell at the moment. The pointers that you've provided to configure the OPC server are much appreciated. The information about the addressing of tags is particularly helpful, as I used to struggle a bit with it before. I'm eager to see more of your findings, especially regarding the performance tests and the undocumented messages. Keep up the great work!
Trevor, I greatly appreciate your comprehensive rundown on the OPC server setup. Until now, I've had some difficulty understanding all the technicalities involved but your post, along with the TechNotes you've mentioned, has made things quite clear. I completely agree with your suggestion about utilizing the S:FS to initiate the enable message for OPC activation, it does seem inherently reliable. Looking forward to hearing more about your further findings and any potential tips you might share on the client side. Thanks again. ~ JeremyM.
Hey Trevor, your extensive research efforts are commendable! The technical insights you provided are genuinely helpful and typically absent in Rockwell's docs. The CIP object's partial support of OPC in the 1756-L81E model, the connection details, and the method for addressing controller tags are particularly vital tidbits. The setting retention after a download was a game changer for me; I had no idea it functioned that way. Also, the additional information about the First Scan Bit was the icing on the cake! Looking forward to seeing your performance tests and any data you might have regarding node counts. Thanks so much for the valuable info!
Thanks for sharing your insights, Trevor! It's great to see someone diving deep into the OPC UA setup, especially since Rockwell's documentation can be a bit sparse. I appreciate the TechNotes you've highlighted, as they seem like invaluable resources. It’s interesting to hear about the limitations with the 1756-L81E; I’m eager to see how your findings evolve, especially once you get more feedback from Rockwell. Keep us posted on any new details you uncover, especially regarding the client-side issues—those could greatly enhance our understanding of the whole system!
Thanks for sharing these valuable insights, Trevor! It's great to see someone taking the initiative to collate and clarify the OPC UA server setup, especially given the gaps in Rockwell's documentation. I found your notes on the connection modes particularly helpful—it's good to have a clear understanding of the security options available. I'm also eager to hear more about your findings as you get updates from Rockwell. Good luck with your ticket!
✅ 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: - Answer: Some recommended TechNotes include QA67230 for key details on OPC UA, QA67231 for steps to activate OPC server/client, and QA67232 for a tutorial on utilizing OPC client.
Answer: - Answer: The testing has been conducted on the 1756-L81E and 1756-L82E models.
Answer: - Answer: Information on connecting to the OPC server can be found with the OPC Discovery URL, OPC TCP URL, and supported Connection Modes provided.
Answer: - Answer: Controller tags are stored in namespace 6 and can be referenced by name. For example, a controller tag named "TEST" will have an OPC address of "ns=6;s=TEST."
Answer: - Answer: To configure the OPC server, you will need to send a message to the controller to enable or disable the OPC server. It is recommended to use the S:FS (First Scan Bit) to initiate the enable message to ensure OPC activation. By default
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.