Script working in sim. but not IRL - Wincc Flex 2008 RT

[rQx]

Hi!

I'm a little lost here. I have made a script in VB that run perfect when I simulate it on my programming machine (Windows 8.1)

But when I run the system on the actual computer (windows 7) it won't work. How do I debug this? There is absolutely no life of the script. I have one more complicated script and one that just copy 8 smarttags to 8 internal tags.

Anyone has this kind of problem? And how do i debug this?

/Tim

 

[Bratt]

You can install a script debugger that will attach upon error but a simple and quick method that i sometimes use is the function system alarm to output debug messages to the screen.

Do you have somewhere to show system alarms?

If not add an alarm window to the template make sure alarm class system and pending alarm is ticked. The time that system alarm popup is shown can be increased in alarm settings --> display duration.

All errors in scripts are output as a system alarm so if you might suspect script errors it is important that you have somewhere to show the system alarms from system alarm class.

But you can also use function ShowSystemAlarm("MY TEXT") to output your own system alarms that can contain values from tags for debug or just to make sure that a certain line is reached. If you have ShowSystemAlarm("TEST") in the first line and have an alarmwindow with system alarm you will get a popup showing TEST whenever the scripts executes.

 

[rQx]

Thanks I will try that and see if the script tries to run at all. It seems like it wont even start.

One script is just:

Smarttag1=smarttag2

But it dont execute

Will be intresting to see what the problem is

 

[sigmadelta]

Try from the File/Project menu Generate -> Rebuild All

 

[JesperMP]

Dou you have the error handling code in your VB script ?

In the start
ON ERROR RESUME NEXT

After each coed section that could have potential problems (anything with i/o):
IF ERR.number <> 0 then
ShowSystemAlarm ERR.number & ": " & ERR.description
ERR.Clear
end if

 

[Bratt]

System alarms are triggered in case of script error even without that piece of code

Your piece of code will allow the script to continue even if there is an error and output the error in a more controlled and elegant manner.

 

[sigmadelta]

Make sure you have the same service pack and hotfix version on your development computer and runtime computer.

 

[JesperMP]

System alarms are triggered in case of script error even without that piece of code

Your piece of code will allow the script to continue even if there is an error and output the error in a more controlled and elegant manner.

Not all VBS errors will trigger a system alarm.

Also, you can place several of the lines with IF ERR.number <> 0 then ShowSystemAlarm ERR.number & ": " & ERR.description.
That can give you more detailed info about where in the code the problem is.

 

[rQx]

Thanks alot for all your help! I think I have now solved the problem.

I had made some debug I/O fields in one screen to see that the HMI actually got the correct values to it.

The script only worked on that screen.

I made a quick google and it appears that all tags are in acqusition mode "cyclic on use" and I have to set it to "cyclic continous" for it to detect my "change value" event that I use to trigger the script.

I haven't tested this yet but it seems that this could be the solution.

/Tim

 

[Bratt]

You are correct cyclic continues is right if you want to connect a script to value changed event