TIAv13,SP1,Upd8 Scripts are not working in Simulated Runtime

Hello all.

I have quite big issue to run any of script in HMI runtime. Always everything (scripts included) is working fine, but once my simulated HMI runtime establishes connection to the PLC (doesn't metter if it is also simulated or real HW), all scripts stops working (only scripts), or they are really lagged. I made one simple script where I'm loading a number to HMI tag and after triggering sometimes I can see reaction in 5mins sometimes I can't see any reaction at all.

I have completely new installation of system (virtual Win7Pro x64, SP1) and TIA v13 SP1 also. Today I installed last update "8", but this also didn't help.

If you will have any idea how to solve it, please give me a shout. I'm desperate. 

Thank you a lot.

Jiri

Hello Jiri,

first we need to know which runtime you use: RT Professional/RT Advanced/Panels?

To me it sounds like your panel is busy.
Multiple scripts on the panel can't run at the same time but one after the other and they can't run if some other function is eating up resources.

What do you do besides using scripts during runtime? Like logging many tags or alarms into archives, communicating with multiple devices, e.g. ...just trying to locate the bottleneck.

Hello H.J.

I have RT Advanced.

Thank you H.J., finally I found it. I was running two scripts together. Is there any way how to run more then one script at once? From my point of view it is very very limiting. On WinCC Flexible 2008 I was able to run more scripts, I know TIA portal is quite new piece of software but I thought that the core is quite same like Flexible 2008.

Do you know if will be possible to run more scripts in future?

Another question is, do you know how to have some HMI internal counter/timer? I was using script for an internal timer and now I need to replace it somehow.

Otherwise thank you again.

Jiri

Hello Jiri,

I don't know very much about this aspect of WinCC Flexible.

Here is an FAQ that describes one possibility to build a kind of timer:

• "How do you implement a wait function (delay) in a Visual Basic script in WinCC flexible?"
  https://support.industry.siemens.com/cs/ww/en/view/26120986
  It's for flexible, but it should work in Advanced, too. Because, as you said, the guts of the software are similar.
  BUT even here it warns, that other scripts will be interrupted:

  "Note that all the scripts of your configuration are interrupted for as long as your script is in the delay loop. The execution of other time-critical tasks can be affected by scripts which last a long time. (See here too the WinCC flexible 2008 System Manual"
  

   The WinCC flexible manual states:

• Processing of scripts in runtime
  

  Principle

  Only one script at a time can be performed in runtime. If several scripts are waiting to be edited, the scripts are lined up in a queue and completed one after another.

  Note A loop in a script therefore blocks the execution of other scripts in the queue even if the scripts are triggered asynchronously.

  WinCC flexible supports a maximum nesting depth of eight scripts. Please note that the nesting depth is not checked.

• If more scripts than can be premarked are activated at one time, during a screen change for example, excess calls are discarded and a system alarm displayed

•  (https://support.industry.siemens.com/cs/ww/en/view/18796010/10671831691)

• In the WinCC Advanced manual it's basically the same, slightly different explanations and a tad more colour. ;) https://support.industry.siemens.com/cs/ww/en/view/109091876/36120419723
  
  

   

  
  

Hello Murof.

You are actually talking about tasks of process and I can understand it very well. If I need to delay a process - for example to delay a pump start-up - I can't use HMI timer, that is clear, but I used this timer for example for monitoring Ethernet connection. As you can know in Coordination area pointer you have LifeBit which is blinking all the time, but if you loose connection to the PLC you can recognize it only by this bit and system alarm message which is not enough for me. I would like to do some other job (let's call it fail-save) base on this and the question is How to trigger this fail-safe job?

Second potentional situation for this timer would be delaying of message resets or triggering of pop-up windows, etc...

From my point of view would be very very very nice to have similiar set of hardware timers in HMI like in all PLCs.

HEY

I am also facing the same problem.

kindly can u tell me the solution.

i have to generate the report on daily basis at 7 am when i download the program to HMI RUNTIME ADVANCED V13 upd 9 on first time report generate but next day it will not working.