4/27/2016 3:54 PM | |
Posts: 30 Rating: (1) |
Dear Oreca, Yes the OCM is checked. but problem still same. |
4/29/2016 6:25 PM | |
Joined: 6/23/2008 Last visit: 10/5/2024 Posts: 1168 Rating: (282)
|
Hello CKO, now I'm relativ sure that the 'block jump problem' is not releated to the language issue (this is sometimes the case when people add a new language to the project). The block jumps work via a text-reference wich refer to the entry for the specific jump in the textlibrary. You may have seen those entries in the textlibrary(Serverprefix::Chartname\Blockname). And with the Serverprefix, I think, your problem comes.... The path to the target OS in the object properties of the OS (tab 'Target OS and Standby OS Computer') is part of the 'Serverdata'.... On the real server the path, where the Serverprefix is pointing to, is the own computer, but in runtime on your ES it is pointing to the server computer. This is also the reason why you see something like 'Server down' in the message line in runtime on ES when you didn't delete the path... Try the following:
Before you ever download the real servers or a client again, put the correct path and generate server data.
Independent from your topic I would recommend to perform the steps from this FAQ, whenever the OS-Project had been in runtime on the ES, before downloading to the real target computer. To prevent the need of performing of the steps from previously mentioned FAQ, Siemens invented the function OS-Simulation. Unfortunately the block jumps don't work in a simulated OS-Server-project, either... Please let us know if it worked.... Best regards... |
Last edited by: mark1507 at: 06/02/2021 21:01:27"Expert" does not necessarily mean Siemens employee. Please cross-check your requirements always with official Siemens documentation. Also "Experts" are pleased about feedback. Please don't send support requests as PM. Questioners who don't follow up their thread will be put to my list of users to be ignored. |
|
This contribution was helpful to3 thankful Users |
3/20/2017 7:12 AM | |
Joined: 9/9/2015 Last visit: 10/8/2024 Posts: 727 Rating: (278) |
I was facing the same problem as well in my local station. The #jump is not working. After troubleshoot, it was caused by the server data issue. My solution is , in the wincc explorer of the client station, right click on the server data, and select standard server. Default will be no standard server. I changed the SSM and Tags to server1(my server symbolic name) , restart runtime, and the interlock block can jump to another faceplate now. Thank you so much guys~~ |
Please give me 5 stars Rating if my post is helpful for you. :) |
|
This contribution was helpful to1 thankful Users |
3/7/2018 10:59 AM | |
Joined: 9/15/2015 Last visit: 7/1/2024 Posts: 67 Rating: (6) |
Hi mark1507, Oreca, I've got many problem when I changed language in runtime (Computer in WinCC Explorer-> Computer->Properties-> Parameters), that affects to Text Library. The problem is when I create some texts (OS additional text, Identifier,...in Interlock, Permit,.. Selfp1...) in the previous language setting, the ID texts for them were respectively created in Text Library for the previous language. When I made a change to new language of WinCC Runtime, the texts for previous language were not copied to new language in Text Library. That is the cause of many error or missing text in Runtime. I manually copy all text defined by Text ID from previous to the new language. Anyhow, then I tried the following:
But it does not work completely. Please give me some advice. Thanks!! I thought this relates to many topics: https://support.industry.siemens.com/tf/ww/en/posts/faceplate-motor-valve-showing-text-error-on-under-command/135522/?page=0&pageSize=10 https://support.industry.siemens.com/tf/WW/en/posts/text-error-in-runtime/138511?page=0&pageSize=10
|
Follow us on