JScript Data Logging Example - Iconics-genesis32-scripts Typing CST Test
Loading…
JScript Data Logging Example — Iconics-genesis32-scripts Code
A JScript snippet that logs a process value to an external file in Genesis32.
var fso = new ActiveXObject("Scripting.FileSystemObject");
var logFile = fso.OpenTextFile("C:\\Logs\\process_log.txt", 8, true);
var pressure = ThisDisplay.GetVariable("Tank_Pressure");
logFile.WriteLine("Pressure: " + pressure + " at " + new Date());
logFile.Close();Iconics-genesis32-scripts Language Guide
ICONICS GENESIS32 scripting provides a flexible environment to automate, extend, and customize GENESIS32 HMI/SCADA applications. It enables control logic, event handling, alarm management, and dynamic visualization through built-in scripting languages and VBScript/ActiveX support.
Primary Use Cases
- ▸Dynamic tag calculation and monitoring
- ▸Custom alarm management and notifications
- ▸Automated historical data logging and reporting
- ▸HMI screen interactivity and conditional object control
- ▸Integration with PLCs, OPC servers, and SQL databases
Notable Features
- ▸Real-time scripting within HMI/SCADA runtime
- ▸Access and manipulate GENESIS32 tags dynamically
- ▸Event-driven triggers for alarms and I/O changes
- ▸Customizable HMI object behavior via scripts
- ▸Database connectivity for historical and reporting purposes
Origin & Creator
Developed by ICONICS in the late 1980s, GENESIS32 and its scripting framework were designed to provide engineers a programmable way to extend HMI and SCADA functionality beyond pre-built graphics and controls.
Industrial Note
GENESIS32 scripting is crucial for advanced alarm handling, custom visualization, automated reporting, and multi-system integration where built-in configuration objects are insufficient.