4/5/2019 10:32 AM | |
Joined: 9/9/2015 Last visit: 9/15/2024 Posts: 727 Rating: (278) |
Dear arunvt1992, what you saw on the network place is a shared folder in the other stations. It is a standard way of doing PCS 7 project, to share the wincc projects in the clients and server in the network places. Can you give some screenshots? slightly hard to imagine. By the way, you should have the latest project in your ES (which is running OS runtime now). Deactivate the runtime in ES, then you may do your OS engineering in the ES and replaced the graphics in OS server later on. |
Please give me 5 stars Rating if my post is helpful for you. :) |
|
4/6/2019 8:21 AM | |
Joined: 10/5/2016 Last visit: 8/15/2024 Posts: 85 Rating: (0) |
Dear Jaztai, Thanks for your reply .. Yes for the runtime i have the latest one from the multiproject.. Kindly find attached screenshots of my system and queries. "Deactivate the runtime in ES, then you may do your OS engineering in the ES and replaced the graphics in OS server later on." When activating os3 again will there not be any error if i replace the graphics in OS server later on." In the simatic shell i could see ES1,OS2,SERVERA,SERVERB. Can you explain the server client config of my existing system from the screenshots. Thanking you, AttachmentSERVER CLIENT.pdf (158 Downloads) |
Last edited by: arunvt1992 at: 4/6/2019 8:23:19 AMLast edited by: arunvt1992 at: 4/6/2019 8:40:17 AM |
|
4/6/2019 5:03 PM | |
Joined: 9/9/2015 Last visit: 9/15/2024 Posts: 727 Rating: (278) |
Dear arunvt1992, Okay, let's sort it out one by one. Since you are going to add some screens, you must identify some of the items and understand the architecture well. 1. You have 5 OS Clients in your project settings named as OS1-> OS5. WinCC60_Project_OS# on Central Engineering Station (Es1) belong to the D drive of ES. 2. Your Runtime is working normally now. So the OS Clients should be correctly set up and getting the server data from correct stations. For your redundant OS. You can do a quick check to try swapping OS if you want. 3. Your network places seem like a mess. The reason should be confusing Server data and Confusing Network Folder Sharing Name. TO UNDERSTAND THE NETWORK PLACE SHARING NAME 1. Now, on your Actual MultiProject, you can go to the correct folder, at the user project folder name level , right click on the properties->Sharing->Sharing Name. For Example, your actual Simatic Manager Multiproject name is C:\Program Files(x86)\SIEMENS\STEP7\S7Proj\XXX_MP\ At this level, you should have all the user projects name. Right click on them to see the sharing name. Then you will be able to identify the folder in your ES. Then, at your SERVERA, at the project folder, Right click on the folder->Properties->Sharing->Sharing Name, you will understand the sharing directories name. TakeNote: Network Places cannot have two identicals folder Name. If two multi projects retrieved in ES, having the same share name, window explorer will automatically add "_2"/"_3"/"_4" behind the folder at the network place. Extra Care: Since you have confusing Server data, be careful. OS_SERVER_A_Stby does mean it is SERVERA. We usually just named it as OS or SERVER. In your case, don't let it confuse you. To Answer Your Questions 1. WHY IS THIS SERVER DATA LOCATION POINTING TO A ES LOCATION RATHER THAN A OS SERVER LOCATION. HOW THE CLIENT GETS DATA FROM SERVER. [Jaz]: Can you do a quick check on the other clients? OS1,OS2,OS4. Then you could do a comparison. And the setup in ES. At the ES, under the OS3, you may right-click on the "OS", select "Assign Server data" to check any error there. 2. BASICALLY I AM HAVING DOUBTS ON HOW THIS CLIENT AND SERVER CONFIG WORKS.CAN EXPLAIN ME BRIEFLY about my existing system. Also in OS3 project properties ,es is mentioned as client?? [Jaz]: When you assign ES as Client, it means you can open a runtime in ES. ES is just a workstation with Step 7 installed in the system for you to do AS engineering work and central configuration. ES sometimes can be an OS server also, depending on project budget and preferences. Can you let me know your ES computer name? 3. ALSO I WANT TO ADD SOME SCREENS ,AND HAVE TO TAKE BACKUP OF THIS PROJECT.SO WHEN I ADD SCREENS SHOULD I AGAIN CONFIGURE OS CLIENT and link to the server. [Jaz]: Add a screen; you have to identify where you would like to add the screen. Are you going to add the screen in a new picture tree at overview button? Then how the architecture was done, is the picture tree auto-generated based on plant hierarchy? Or they add the pictures manually in WinCC explorer? Do you need to add any new tags? If yes, you would need to do OS compilations and download OS to the SERVERA and SERVERB. Adding new screens, you do not need to touch the OS Client configuration at all. Just OS SERVERA and SERVERB will do. 4. “You may do your OS engineering in the ES and replaced the graphics in OS server later on. “ Do you mean that I could just add screens and compile later. [Jaz]: to compile or not, it depends whether you need to add any new tags or messages or archive or not. If you are using Auto-Generated Picture tree, then you would need to add new folders in Plant Hierarchy and pictures in those folders. If you are using manual creation picture tree, you need to right-click on the SERVERA OS and open the wincc explorer in the ES, modify the picture tree and do an OS download. (if you do not have confidence in doing the OS download, you can quickly edit the picture tree in the local OS SERVERA and SERVERB station) Here are some guidelines for PCS 7. It will be better to read through first before you do any engineering work in those stations. |
Last edited by: JazTai at: 4/6/2019 5:12:04 PMPlease give me 5 stars Rating if my post is helpful for you. :) |
|
4/7/2019 4:25 AM | |
Joined: 9/9/2015 Last visit: 9/15/2024 Posts: 727 Rating: (278) |
Dear Arun, Hope the below answer is helpful for your troubleshooting.
[Jaz] : "One workstation" which is the one you are using now. Lets name is as ES1. We can forget the OS client name in ES1 as it is not significant. If I'm not wrong OS3 = ES1 (Computer name), correct? If yes, then you are right. ES/OS client with redundant OS Server. From the Overview in your pdf, I saw OS1->OS5. There should be other OS in the plant, right? Like Touchscreen on a cabinet? I seldom open .mcp file (WinCC) remotely via network place. Only locally. If you want to open remotely, you can use Real VNC (some of them use a remote desktop connection which is not recommended by Siemens) to open or connect up the monitor, keyboard and mouse on the workstation to have the screen in the stations. The error you facing might due to Security / Network / User right issue (You must have the same user login in both stations). You may try Ping the station via Computer Name. For eg. -> In cmd -> Ping \\SERVERA . (PCS 7 ways of doing things, we must ping stations via Station Name which we configure in the system32 host file.) ___________________________________________________________________________
[Jaz] : Noted and Closed. ___________________________________________________________________________
[Jaz] : Then you would need to understand the concept of the plant hierarchy design. Is it a station specific or project specific setup? Station specific means, they put one CPU/AS in one user project, OS station in another project. In this setup, when you switch to plant view, you will have two sets of hierarchy folder in each individual user project. Make sure you create the "REAL" folder in either one of the projects and use "Update in Multiproject" (right click on hierarchy folder, hierarchy folder-> update in multiproject) to synchronize the folder to another user project. It will create the Shortcut Plant Hierarchy folder for you to insert Chart / Pictures. ___________________________________________________________________________
[Jaz] : Study how the previous project was done. Just follow the same rules of inserting the pictures. ___________________________________________________________________________
[Jaz]: You may bring the monitor/keyboard/mouse to see what happened there. Or Real VNC Or Remote desktop Connection (Not recommended, but this is what I usually do). |
Please give me 5 stars Rating if my post is helpful for you. :) |
|
4/7/2019 11:22 AM | |
Joined: 9/9/2015 Last visit: 9/15/2024 Posts: 727 Rating: (278) |
Welcome. Post again if you have any issue. Hope my answer is helpful for you. |
Please give me 5 stars Rating if my post is helpful for you. :) |
|
5/7/2019 9:00 PM | |
Joined: 10/5/2016 Last visit: 8/15/2024 Posts: 85 Rating: (0) |
Dear Jaztai,
I added some screens to the existing os and compiled/downloaded to the server which is working fine. Now I want to show a value on the pcs7 screen from a db in step7. I enabled the monitoring and control attribute in the db > rmc > object properties and db > rmc > special object properties and also added the attribute S7_m_c=true; for the variable inside the db. After compiling changes to the OS , I got the tag under the tag management inside wincc explorer but when I connect it to an IO field I can see only a blank screen and value is not visible .. Am I missing some settings here to connect the wincc tags from step7.. How to check the remaining license for os and as in pcs7 v6.1 AttachmentPCS7 tag error.docx (150 Downloads) |
Last edited by: arunvt1992 at: 05/07/2019 21:36:35Last edited by: arunvt1992 at: 05/08/2019 08:24:22 |
|
5/8/2019 12:38 PM | |
Joined: 9/9/2015 Last visit: 9/15/2024 Posts: 727 Rating: (278) |
Dear arunvt1992, Erm...not that understand. You should have a tag name = chart/block.TEST as your tags right? Or you use plc to wincc linking? Then you configure the tag using DB address instead? |
Please give me 5 stars Rating if my post is helpful for you. :) |
|
5/8/2019 5:24 PM | |
Joined: 5/3/2017 Last visit: 5/21/2024 Posts: 673 Rating: (217) |
Hello arunvt1992, with an OS compile you will only generate the OS relevant data that are implemented in an CFC chart. A simple way to generate the OS tag is with the block DigMon or MEAS_MON from the PCS 7 Library. There you also get an blockicon and faceplate. With regards |
Follow us on