3/3/2017 6:17 PM | |
Joined: 3/14/2008 Last visit: 10/15/2024 Posts: 2111 Rating: (942)
|
Hi, Is the AS-OS2 connection named the same like AS-OS1? In Netpro. Is station configurator loaded correctly for the server? Command: PLC->Configure and then PLC->Download? |
If I could help you, you can use the RATE button. Thank you. |
|
3/3/2017 7:45 PM | |
Posts: 3 Rating: (0) |
Hello, yes, the connection is named the same. and the configuration is also downloaded correctly. Do you have other ideas what could be the reasen.
|
3/4/2017 1:00 PM | |
Joined: 3/14/2008 Last visit: 10/15/2024 Posts: 2111 Rating: (942)
|
Hi W_Pavis, What does the connection say? "Is being setup"? I have a few other things you can try, some may not be related directly: - Is the AS station in netpro downloaded as well (or at least the AS-OS connection after creating AS-OS02 connection? - Did you insert a "WinCC Appl. stby" for the redundant server? - Did you configure who the standby server is under the properties of the OS object of the master server? - Are the two servers located in the same project in the multiproject? - Did you use "s7 connections" and not of type: "s7 connection fault tolerant"? - Under "Redundancy" in WinCC Explorer, did you set everything correctly?-> Default master must be your server 1, redundant partner server must be your server 2, Did you set the correct network adapter for the redundancy and did you activate option: "Activate redundancy" at the bottom? - Is the OS compiled through "Named connections" or via ISO protocol? - For all PC stations, the PG/PC interface must be set to: "PC Internal.local1" - Check again if the station configurator is loaded correctly--> a yellow pencil must be shown, indicating the connection is downloaded successfully. If the icon is greyish or even has a red cross for the WinCC appl. stby, then the configuration is not successful. - Make sure the Terminal bus network card is selected in Simatic Shell and that it is on top of the communication settings-->To check: Open Network and sharing center->Change adapter settings, press Alt and click on Advanced in the visible toolbar->Advanced Settings. - Is the redundancy option in Simatic Shell setup correctly for both servers? Simatic Shell settings must be done locally for each PC station. If nothing else works, I suggest you will download your netpro configuration for all stations again, reboot servers+ES station and see if it solves your issue. Let me know the result!! |
Last edited by: Oreca at: 3/4/2017 1:05:16 PMIf I could help you, you can use the RATE button. Thank you. |
|
This contribution was helpful to1 thankful Users |
3/6/2017 5:22 PM | |
Posts: 3 Rating: (0) |
Thanks a lot for your help. The Problem was solved by deleate the hole OS-Project and build it up new. So i think the Project was crashed somewhere inside.
|
3/6/2017 5:50 PM | |
Joined: 2/29/2016 Last visit: 3/12/2024 Posts: 100 Rating: (1) |
Good list! |
6/22/2022 8:14 AM | |
Joined: 5/3/2017 Last visit: 5/21/2024 Posts: 673 Rating: (217) |
Hi mr Gun, if you use an other access point then "PC internal" it works also. But at PCS 7 it is recommended to the set the "S7 online" access point to the "PC internal" interface. In this case all access to the AS – in order to check the module information of an AS or to download S7 programs, for example – is performed via "PC internal". "PC internal" is a centrally configurable interface, which can be loaded with project-specific settings for all stations on the system bus. The settings are made on the ES in the PCS 7 multiproject and downloaded from the ES. The settings you have to made can be found in the manual PCS 7 Compendium Part A - Configuration Guidelines at the section Engineering Station. With regards |
This contribution was helpful to1 thankful Users |
Follow us on