In my current project, I am tasked with creating a visualization screen using WinCC TIA Portal v16, which will be accessible through LAN within the company. Any computer connected to this network should be able to view the screens by simply entering the IP address in the address bar of a web browser such as Chrome or Firefox. For visualization, I have the following hardware and software: 1. TP700 Comfort Panel 2. TIA Portal v16 with WinCC Basic/Comfort/Advanced/Unified. After researching, I have identified the following options: 1. Create and download the project in TP700 Comfort Panel, utilizing its smart server. However, Chrome and Firefox may not be compatible for this purpose. 2. Repeat the previous step, but use smartclient.exe, requiring installation of sm@rtclient on each computer in the plant that needs HMI access. This may not be practical. 3. Create a WinCC Unified PC project on a computer instead of using an HMI panel, allowing easy access to the runtime screens through Chrome or Firefox. Option 3 appears to be the most feasible, although it would mean sacrificing the use of an HMI panel and installing TIA Portal v16 in at least one PC, which would act as a server at the plant. I am open to feedback on these options and am wondering if there are any alternative solutions considering the available hardware and software. Additionally, I am curious if the server (PC or HMI) and clients need to be in the same subnet/network for access, or if remote access via WAN is possible.
In a recent discussion by user aamirawan91, several options were explored for accessing and managing projects on TP700 comfort panels. One suggestion was to create and download the project, then utilize the smart server for access, although it was noted that Chrome and Firefox may not be compatible for this purpose. Another alternative mentioned was to use smartclient.exe, but this would require installing sm@rtclient on each computer in the plant, which may not be practical. Alternatively, creating a WinCC Unified PC project on a computer was considered, allowing easy access to runtime screens with Chrome or Firefox. When it comes to remote access, it was questioned whether the server and clients needed to be on the same subnet or network. Options 1 and 2 were deemed to be functional but cumbersome, as they essentially mirror the screens on the physical device, limiting simultaneous interactions. Smartclient, whether accessed through an activeX control in IE or a dedicated app, offers more flexibility and can be any VNC client that supports the required settings. Option 3 was seen as the most viable, with Unified V19 being recommended over V16 due to improvements in performance and functionality. It was noted that a runtime license is required for the PC-based HMI, with additional licenses needed for multiple remote clients. Remote access does not necessarily require the same subnet, as long as standard networking components like routers, NAT, and VPN are in place.
In a discussion, MK42 pointed out that Options 1 & 2 may work but are cumbersome. These options involve mirroring screens on physical devices, essentially resulting in direct screen sharing. This setup limits remote users to seeing the same screen and allows only one person to click at a time. Additionally, conflicts may arise if the Human-Machine Interface (HMI) is not dedicated specifically for remote access. Smartclient can function as either an ActiveX control in Internet Explorer (deprecated) or as a dedicated app. It's worth noting that the Smartclient app from Siemens is not obligatory; any VNC client supporting the required settings can be used. Option 3, although seemingly the most practical, has its challenges. Unified V16, the initial release, is considered quite raw in comparison to Unified V19, which boasts significant improvements. It's highly recommended to upgrade to the latest version for a smoother experience. For PLC/Comfort HMI, V16 is adequate. A runtime license based on the tag count is necessary for PC-based HMI, with one free remote client included. Additional licenses are required for multiple simultaneous users. Regarding the bonus question, these options do not need to be on the same subnet as long as standard networking elements (routers, NAT, VPN, etc.) are in place. MK42 emphasized the complexity of tasks like remote access with Siemens systems, despite having a fondness for the brand.
In a discussion with aamirawan91, they mentioned their love for Siemens systems but also pointed out the complexity of tasks like remote access. This is especially true for older systems that lack modern remote access capabilities. However, the newer Unified system offers more streamlined remote access as everything is accessible through HTML pages. The only downside is the cost associated with upgrading to a Unified panel or a PC based runtime for remote access.
I've worked on a similar project where we had to decide between using an HMI panel and a PC with TIA Portal v16. We opted for the PC setup, as your Option 3 suggests, primarily for ease of access across the company. The downside is, indeed, investing in a dedicated PC. It's also essential to ensure that this PC is robust enough to avoid runtime issues. To answer the question about the subnet/network, typically all devices need to be in the same network to ensure seamless communication. If you need remote access via WAN, that is entirely possible, but that usually requires setting up a VPN or some form of secure network connection to ensure the security of your control system.
From your description, it seems like you've done a fine job of outlining the potential paths for this project. That being said, I'm leaning towards voicing support for your third option. Although it does require the sacrifice of the HMI panel, the accessibility and ease of use provided by allowing access through Chrome or Firefox might outweigh this loss. As for your question about the server and network, generally, they should be on the same subnet for smoother operation. However, remote access via WAN is possible with some additional network configurations and appropriate security measures. Remember, security is of paramount importance here due to the potential risks associated with allowing remote access.
Great analysis on your options! Given your hardware and software, I agree that option 3 seems to be the most feasible in your situation. As you rightly pointed out, it will circumvent browser compatibility issues and cater for a wider range of devices within your LAN. The sacrifice of not using the HMI panel might be outweighed by the flexibility of ubiquity. It also avoids the potential bottleneck of having to install sm@rtclient on each computer. Regarding your network concerns, both the server (PC or HMI) and the clients will typically need to be in the same subnet for efficient communication and to prevent network traffic leaks from propagating into other subnets. However, with appropriate routing and security measures, it is possible to achieve remote access via WAN. You'll need to ensure secure and encrypted connections to maintain network integrity, given the rise in cyber threats.
It sounds like you’ve done a solid job weighing your options! Option 3 does seem like the best fit if you want to provide easy access through browsers without needing additional software on each client machine. I could also recommend considering a cloud-based solution if that's feasible for your project, as it can simplify remote access. As for network requirements, generally, all devices need to be on the same subnet for local access, but with proper VPN setups or port forwarding, remote access via WAN is definitely possible—just ensure you have proper security measures in place! Good luck with your project!
✅ 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: The options include utilizing the smart server on the TP700 Comfort Panel, using smartclient.exe with sm@rtclient installation on each computer, or creating a WinCC Unified PC project on a computer acting as a server.
Answer: Answer: Option 3, creating a WinCC Unified PC project on a computer acting as a server, is deemed the most feasible solution, despite sacrificing the use of an HMI panel.
Answer: Answer: Yes, typically the server and clients need to be in the same subnet/network for access within the LAN environment.
Answer: Answer: Remote access via WAN is a possibility, but it may require additional configurations and considerations to ensure security and proper functionality.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.