The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
Debugging VBScript in InduSoft Web Studio Projects
4. Established in US in 1997
Since Sep, 2013: an Invensys Company!
Pioneer in industry:
First HMI/SCADA package for Microsoft Windows CE
Web solution and XML integration in HMI/SCADA
Patent for database connectivity
Multi-touch support and HTML5 integration
Certifications:
7. Brief Intro
Why VBScript?:
It is a quite well known high-level programming language
Simple, Flexible and Standard
Runs on Windows Embedded OS and Internet Explorer
It is similar to VBA, which is also used on other MS Applications such as the
MS-Office suite
Which IWS interfaces support VBScript?:
Script Task, Global Procedures, Startup Script, Screen Script, Graphics
Script, Command animation property, ActiveX and .Net controls Methods
Support to Built-in IWS functions and tags on VBScript Environment
8. VBScript Cool Features!:
Use of Variables on the Script!
Save on tag count!!!
Intellisense: auto-complete
(less typing, more doing)
Create your own Functions and
Sub-routines
Find on the Internet scripts with
examples on how to do things that
you are not sure how to do!
http://www.w3schools.com/vbscript/
10. Database Spy:
It works to debug project running on the local machine or in remote
ones
Used to see and load values into tags
It can also execute Built-in Functions or call VBScript procedures
Sub-routines
NEW!!! Support to seeing VBScript variables values and functions
status
11. Output Window / LogWin:
Helps to debug almost all IWS tasks, such as Comm Drivers, OPC
messages, Database transactions, Screens load time, Log tag changes, and
so forth
Like the DBSpy, it works for both Local and Remote projects
TRACE messages has been the biggest friend on debugging scripts until
now
It can save Log Files
13. What can be debugged?
Global Procedures
Graphics Script
Scripts from the Script task and Startup Script
Screen Script and Graphics Script
What is not supported yet?
Command Properties on screen objects
ActiveX and .Net Controls Methods
14. The new DEBUG tab
It only appears when a supported VBScript interface is open
Allows the user to select between Debugging the Viewer module or the
Background tasks
It is where the user controls the debug execution by starting, stopping, going to
the break points, Stepping Into a function, Over and Out as well.
15. Break Points
Used to identify important sections
that you want to focus your debugging
process
Temporarily suspends the script
execution on that point
During that break time, the user can
check variable values, execution states,
and be prepared for the next steps
16. Stepping through
Once the execution in in Break mode, the
user can:
Step Into: advances a single step
forward
Step Over: advances a step on the main
Script, not stepping into function calls
Step Out: if the main script called a
function and is debugging there, this
command will finish the execution and
return to the main script
17. Database Spy
Once the execution in in Break mode, the Database Spy can help the user see:
Locals: Local Variables values
Stack Frame: Shows which VBScript interfaces are currently under Debug
mode
Tasks Frame: shows the Runtime tasks states during the Break