Window in a window...

We released a new HMI version today that contains a new graphic element. The new element allows for one window to be displayed in another window.

For example, the project requires a collection of 16 LED indicators to be at the top of all windows and to display the same information. Placing all the LEDs in one window, setting the animations and then referring to the window in all other windows would be a better solution than re-creating the LED 'panel' in each window.

"ODBC In" example...

This morning we posted a very simple project that demonstrates a user clicking one of three buttons. Each button reads four cells/values in an Excel spreadsheet. The column and row are the same for each sheet. The sheet name is different for each button. Simulating, each sheet as a different recipe with four ingredients. The values are transferred to a Micrologix 1400.

The data source could have been any database with an ODBC driver (we have not found a database that does not support ODBC).

 Any protocol the HMI supports can be used as the data destination.

More camera support...

Several days ago we added video support for the Trendnet TV-IP600 video camera. It uses the MJPEG 'protocol'. This brings the count to 7 video cameras or video encoders the HMI now supports via native protocols. The HMI does not use any ActiveX or DLL to access the images.

Bitmap editor...

We had an HMI release today. We added a bitmap editor in the graphics editor. This provides a method to edit bitmaps inside the HMI editor.

ODBC data logging update...

We released a new version today that adds a pause feature and the ability to change the logging rate for ODBC data logging at runtime on a per table bases.

The pause was added to halt logging, for example, when the machinery was off-line or logging was only required during certain abnormal conditions.

The logging rate is adjustable from 100 milliseconds to 2 million plus milliseconds in 100 millisecond increments. Under normal operations it might be configured to log every 10 seconds but, under an abnormal condition the desired rate might be 100 milliseconds.

We also added a 'close the calling window' attribute to all graphic mouse 'open window x' commands. (Saves a separate call to close window.)

Also added is a method to test if a tagname in a Logix controller exist at design time.

ODBC data logging...

A new version of the HMI was released yesterday. PeakHMI has been able to read/write data to any database, via ODBC, for the real-time processing of data, for quite some time. This was accomplished by reading/writing the same fields of the database table, via a set frequency or a change of value of the underlying data point.

PeakHMI is also able to log data values to an internal database and then export it to several formats.

PeakHMI can now log data values directly to any database, via ODBC, at a set frequency, user command or scripting command. A new record is added to the end of the table.

The release also included a few minor corrections in the graphics editor. The minor corrections had to do with the visual appearance with one gauge at design time and a mouse down event in the analog and digital grid editors.

We are considering adding support for the 1-Wire protocol from Maxim. Here is a link to a web page.

New release last week...

We completed addition of Mitsubishi 3C protocol driver. The driver supports format 1 with or without checksum and format 4 with or without checksum.

We also added a period of 'hour' to the task scheduler. A task can be configured to execute on 'X' minute of an hour and repeat every 'Y' hours.

Work on an new ODBC feature to allow the logging of data to any database that supports ODBC. Our current ODBC support is used for collecting and exporting current tag values. It repeatedly reads or writes the data to the same table fields. The new feature is a data logging action. It will 'insert' new records, containing tag values, at the end of the table at the configured frequency.