Support Forums
VTScada Scripting Language

VTScada language syntax is "C' like, but excludes a lot of the overhead of syntax typing, error trapping and event handling which are automatically done for you to provide a reliable scalable platform for industrial applications. For stability, you can take a variable and divide by zero and it does not blow-up on error ("Invalid" is the result, which you can do things with)! For scalability, there are applications (including drivers, historians, displays, etc.) of over 1 million plus tags running on a single server due to event-driven execution (i.e. if A = B+C, "A" would not calculated, or consume CPU time, unless "B" or "C" changed). It is for this reason that you see some really big and critical infrastructure applications using VTScada when they would have traditionally used a DCS system - but the same software will install and run on a $99 USB computer.

If you are familiar with programming languages, VTScada is easy to learn and use (evidenced by hardware OEM's who had their own HMI products based in other non-industrial languages, switching their HMI's to VTScada).

All this is performed by the product 'engine' which is comprised of over 1.5 millions lines of 'C" and VTScada script - yes VTScada is partially "written in itself" with its own compiler which it enables it to scale and run reliably so well (ask users). It is state-logic based and is in fact classed as a "Reactive Programming Language" which is designed for industrial use versus web displays or word processing. In that regard, it has been used for some real neat applications that traditional languages have problems with, like modelling the neural network of the human heart to understand arrhythmia, a leading cause of sudden cardiac death
See https://www.trihedral.com/vtscada-has-heart

VTScada language syntax is "C' like, but excludes a lot of the overhead of syntax typing, error trapping and event handling which are automatically done for you to provide a reliable scalable platform for industrial applications. For stability, you can take a variable and divide by zero and it does not blow-up on error ("Invalid" is the result, which you can do things with)! For scalability, there are applications (including drivers, historians, displays, etc.) of over 1 million plus tags running on a single server due to event-driven execution (i.e. if A = B+C, "A" would not calculated, or consume CPU time, unless "B" or "C" changed). It is for this reason that you see some really big and critical infrastructure applications using VTScada when they would have traditionally used a DCS system - but the same software will install and run on a $99 USB computer. If you are familiar with programming languages, VTScada is easy to learn and use (evidenced by hardware OEM's who had their own HMI products based in other non-industrial languages, switching their HMI's to VTScada). All this is performed by the product 'engine' which is comprised of over 1.5 millions lines of 'C" and VTScada script - yes VTScada is partially "written in itself" with its own compiler which it enables it to scale and run reliably so well (ask users). It is state-logic based and is in fact classed as a "**Reactive Programming Language"** which is designed for industrial use versus web displays or word processing. In that regard, it has been used for some real neat applications that traditional languages have problems with, like modelling the neural network of the human heart to understand arrhythmia, a leading cause of sudden cardiac death See https://www.trihedral.com/vtscada-has-heart
255
1
2
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft