8/2/2019 6:34 PM | |
Joined: 9/9/2015 Last visit: 9/15/2024 Posts: 727 Rating: (278) |
Dear niksss, I would like to know more, wish I could help too. Let me clarify something first. Your existing system 1 ES with CP1623 for plant bus, one NIC (normal LAN port) for Terminal Bus. Reference OS means? WinCC Application Ref ? or WinCC Application Client Ref? How come seem like you have so many CP1623? CP1623 is just for Plant bus. Normally we used it in ES, OS Server (WinCC Application) only. Normal NIC/LAN Port is for Terminal Bus. To have WinCC Runtime, we use WinCC application Client with only normal NIC / LAN port is enough. No CP1623 is needed. CP 1623 is for S7 communication and Time synchronization. Not related to FH or not FH system. For the Laptop that you mentioned, is it a WinCC Application Client Ref (OS Client)? Second Engineering Station? or WinCC Application (OS Server)? |
Please give me 5 stars Rating if my post is helpful for you. :) |
|
8/4/2019 6:57 AM | |
Joined: 9/9/2015 Last visit: 9/15/2024 Posts: 727 Rating: (278) |
Dear niksss, Now I understood. You are having multiple Single OS station. Let me share my little opinions. First Method In that case, you can use WinCC Application instead of WinCC Application Ref on the Laptop Station. Just refer back the main WinCC Application settings and put it in the third station. Then you can configure different connections (Industrial Ethernet) (purchase Softnet IE-S7). This will be the first solution. Second Method The second will be, instead of choosing the Laptop, buy another identical station with the main OS, then you can continue to use WinCC Application Ref. Third Method The third one is to convert it to WinCC Server Client Licenses. Since you have two OS single stations, contact Siemens to upgrade them to OS server - OS Standby Architecture. Then your laptop can be one of the OS Client stations without the need of using cp 1623. And you don't need to purchase another OS RT PO for the third station as well since you are displaying the same S7 program folder (the same AS station). I never tried on multiple single OS stations before. I think it will be better to change it to OS Server-Client Architecture, so it will be expandable, and you have the options to have a lot of OS Clients in the plant in the future. Maybe this is something you could propose to end-user. AttachmentMultipleSingleOS.pdf (158 Downloads) |
Last edited by: JazTai at: 08/04/2019 07:01:34Please give me 5 stars Rating if my post is helpful for you. :) |
|
This contribution was helpful to1 thankful Users |
Follow us on