It is pretty straightforward as on Siemens example.
First you need to give certain name or different numbers to every script which is printed to output window.
(If you use error number on scripts, give for every script different error number, so it is easier to look which script makes error.)
I maded two different buttons, another is with C and other with VBS.
C-code:
#include "apdefap.h"
void OnLButtonDown(char* lpszPictureName, char* lpszObjectName, char* lpszPropertyName, UINT nFlags, int x, int y)
{
printf("\r\n");
printf("This is a my script (Button1, C-code");
printf("\r\n");
SetTagBit("test_bit",1); //Return-Type :BOOL
}
and VBS-code
Sub OnLButtonDown(ByVal Item, ByVal Flags, ByVal x, ByVal y)
HMIRuntime.Trace vbNewLine
HMIRuntime.Trace "this is my script (Button2, VBS-code)"
HMIRuntime.Trace vbNewLine
HMIRuntime.Tags("test_bit").Write 0
End Sub
Then start WinCC runtime.
On WinCC installation folder should be folder name uTools and inside folder apdiag.exe
When runtime have started, open apdiag.exe
On apdiag.exe select output window, there should open grey box which prints all errors etc. fron WinCC's active page.
If you now open page or picture window on WinCC, there maybe is showed some erros if not then everthing good still on WinCC.
Next if you push buttons then output window should print your text and execute other commands of script behind.
You should see your script text as soon as you push buttons.
If there is delay, something is hanging behind on WinCC and affecting to scripts and you should fix that error(s)
When you have examined everything of script and everything is OK, comment all printf and HMIruntime.trace commands out from scripts.
Otherwise they also are saved to WinCC TXT logs and logs are hard to read afterwards
Same also for global scripts, if you make printf/trace commands to global scripts, the are printed to output window when executed with triggers.
First you need to give certain name or different numbers to every script which is printed to output window.
(If you use error number on scripts, give for every script different error number, so it is easier to look which script makes error.)
I maded two different buttons, another is with C and other with VBS.
C-code:
#include "apdefap.h"
void OnLButtonDown(char* lpszPictureName, char* lpszObjectName, char* lpszPropertyName, UINT nFlags, int x, int y)
{
printf("\r\n");
printf("This is a my script (Button1, C-code");
printf("\r\n");
SetTagBit("test_bit",1); //Return-Type :BOOL
}
and VBS-code
Sub OnLButtonDown(ByVal Item, ByVal Flags, ByVal x, ByVal y)
HMIRuntime.Trace vbNewLine
HMIRuntime.Trace "this is my script (Button2, VBS-code)"
HMIRuntime.Trace vbNewLine
HMIRuntime.Tags("test_bit").Write 0
End Sub
Then start WinCC runtime.
On WinCC installation folder should be folder name uTools and inside folder apdiag.exe
When runtime have started, open apdiag.exe
On apdiag.exe select output window, there should open grey box which prints all errors etc. fron WinCC's active page.
If you now open page or picture window on WinCC, there maybe is showed some erros if not then everthing good still on WinCC.
Next if you push buttons then output window should print your text and execute other commands of script behind.
You should see your script text as soon as you push buttons.
If there is delay, something is hanging behind on WinCC and affecting to scripts and you should fix that error(s)
When you have examined everything of script and everything is OK, comment all printf and HMIruntime.trace commands out from scripts.
Otherwise they also are saved to WinCC TXT logs and logs are hard to read afterwards
Same also for global scripts, if you make printf/trace commands to global scripts, the are printed to output window when executed with triggers.
