Yesterday we released a new version of the HMI that added
support for PDF output.
Reports, screen captures, window captures, DMCP plots and
trend plots now all support PDF as an output option.
Friday, June 13, 2014
Monday, June 2, 2014
CFR 21 Part 11...
Yesterday we released a new version of the HMI to support CFR
21 Part 11 user/password control. The HMI has always provided a user/password system
to control and monitor access to the HMI. The HMI now provides more options for
passwords.
Thursday, February 27, 2014
New protocol added...
Today a new version of the HMI was released that supports
the Saia-Burgess Serial-S-Bus (RS232/485) and Ether-S-Bus protocols.
Boolean, integer, float and string data types are supported.
Registers, counters, timers, flags, inputs, outputs and data blocks are
supported.
Boolean, integer, float and string data types are supported.
Thursday, January 30, 2014
Graphics addition...
From the release of the HMI the option to set a graphic
element to transparent or opaque has been present. This allowed the selected
brush style to be applied to the graphic element and the “background” (whatever
is behind) to show thru the graphic element.
Yesterday we released the latest version with an “Opacity” setting. This allows for the background to show through graphic elements with a “blend” of the foreground and background. A setting of 0 (zero) is totally transparent and a setting of 255 is totally opaque.
Here is a sample.
Saturday, December 28, 2013
HMI update 12/28/2013
In the last HMI update for 2013, we realigned the alarm ‘blocking’
logic to maintain continuity between configuration settings and runtime
actions.
Alarm logic can be blocked / unblocked at runtime to temporarily disable and then enable the alarm logic processing for a point.
Alarm blocks are designed to be a temporary solution, when for example, a transmitter fails and the configured alarm needs to be 'blocked' so as not to provide false information.
The alarm configuration should be altered if the 'block' is used as a permanent or long term solution.
Also the SetAlarmSetpoints has a new flag to disable the alarm check when the function is called. This really should only be called with ‘false’ at runtime start, via the runtime start script, when the data from external devices has not yet been collected.
Happy New Year
The SetAlarmEnables function is still present but, will be
removed in a future release. See SetAlarmBlocks.
Alarms are enabled / disabled, at runtime start, as determined by
project configuration.
Alarm logic can be blocked / unblocked at runtime to temporarily disable and then enable the alarm logic processing for a point.
Alarm blocks are designed to be a temporary solution, when for example, a transmitter fails and the configured alarm needs to be 'blocked' so as not to provide false information.
The alarm configuration should be altered if the 'block' is used as a permanent or long term solution.
Also the SetAlarmSetpoints has a new flag to disable the alarm check when the function is called. This really should only be called with ‘false’ at runtime start, via the runtime start script, when the data from external devices has not yet been collected.
Happy New Year
Sunday, December 1, 2013
HMI update 12/1/2013
Yesterday, a new version of the HMI was released that
includes three new script functions.
ODBCDataLoggerDelete
This function is used to delete all the records of the table. The data logger appends a record to the table when the preset timer expires or a “log” command is called. The table can become very large. This allows the table to be emptied on command.
AcknowledgePointAlarm
The HMI has a global “Acknowledge” command. Also, the alarm panel graphic has a “Page Acknowledge” button. Now a single point alarm can be acknowledged via scripting. When an alarm row is selected, via the alarm panel, the point tagname and alarm type are now available to the scripting engine, allowing actions to be programmed based on the point tagname and/or the alarm type.
SetAlarmPoints
This function provides for “set points” of the analog point alarms, to be altered at runtime. Two methods are provided to alter a "setpoint". The HMI can be instructed to use the value of another point or via a value defined by the user.
Earlier this month we released an 800+ page manual for the HMI. The link to download the manual is on our website.
ODBCDataLoggerDelete
This function is used to delete all the records of the table. The data logger appends a record to the table when the preset timer expires or a “log” command is called. The table can become very large. This allows the table to be emptied on command.
AcknowledgePointAlarm
The HMI has a global “Acknowledge” command. Also, the alarm panel graphic has a “Page Acknowledge” button. Now a single point alarm can be acknowledged via scripting. When an alarm row is selected, via the alarm panel, the point tagname and alarm type are now available to the scripting engine, allowing actions to be programmed based on the point tagname and/or the alarm type.
SetAlarmPoints
This function provides for “set points” of the analog point alarms, to be altered at runtime. Two methods are provided to alter a "setpoint". The HMI can be instructed to use the value of another point or via a value defined by the user.
Earlier this month we released an 800+ page manual for the HMI. The link to download the manual is on our website.
Wednesday, October 16, 2013
HMI release...
Today a new version of the HMI was released. The release
has several new features in preparation for a new feature to allow the
attachment of files to Emails sent from the HMI.
CaptureScreen, CaptureWindow, TrendSavePlotPictureToFile
An Email generated via notifications has been available in the HMI for some time. The new Email feature will be under script control and allow the attachment of files, along with the normal message and subject fields. A user generated Email will also be available. It will be much like the SMS user generated message entry.
If you have any requirements, wants or needs for the forthcoming Email feature, contact support for more data.
Several new script commands have been added.
ExportAlarmLog, ExportEventLog
These new commands provide the ability to convert a log
file, at runtime, from the internal format to a ‘CSV’ (comma separated values)
file. The current log file (today), yesterday’s log file or a log file selected
by day/month/year can be converted. The first two options provide an easy
method to run a task at for example, 3:00 AM and email or FTP yesterday’s log
file without user interaction.
CaptureScreen, CaptureWindow, TrendSavePlotPictureToFile
These new commands provide the ability to capture the
complete monitor(s) image, a specified user window, the foreground window or a
trend plot picture to a specified file. The file can be sent via email or FTP
without user interaction at a specified time or via a triggered event. The
print screen features remain without change.
An Email generated via notifications has been available in the HMI for some time. The new Email feature will be under script control and allow the attachment of files, along with the normal message and subject fields. A user generated Email will also be available. It will be much like the SMS user generated message entry.
If you have any requirements, wants or needs for the forthcoming Email feature, contact support for more data.
Subscribe to:
Posts (Atom)