11/6/2019 2:28 PM | |
Joined: 5/3/2017 Last visit: 5/21/2024 Posts: 673 Rating: (217) |
Hi Nikola Hadjinikolov,
I don't know this error. So I can't help you with the. The only advice I can give you is to contact Siemens with a Support Request.
The information to start an trend with the archive values can be found in the manual Advanced Process Library in the section Trend view: Configuration of the trend viewThe trend view can be configured so that archive values are displayed immediately after opening. A prerequisite for this is that archive variables exist. Proceed as follows:
with regards |
11/6/2019 3:13 PM | |
Joined: 2/1/2010 Last visit: 11/12/2024 Posts: 154 Rating: (72) |
HI Nikola 1. I can't fully answer this question, as I don't know that I've specifically seen OSStateMachineX be the reason for slow restart, but in general we don't use the auto download on Server projects as a hold over from a time when OS downloads weren't so stable. As a habit when performing full downloads for any of our customers we normally stop runtime manually on the OS server, perform the full download and restart runtime manually. I know you aren't supposed to have to do this, but it avoids having the ES tied up for that whole time. Don't forget you have to wait for servers to finish syncing after the complete download no matter which method. If you really want to get to the bottom of it instead of just dealing with the problem like we eventually have, then I agree SR is your best bet. 2. +1 for Heisenberg's answer. |
If my post helped you, please rate. Thanks. |
|
Follow us on