Download E3 Release Notes - Elipse Software

The digital certification used for installers and other binary files (EXE, OCX, DLL,
etc.) in E3 was updated. It is now valid until September 13th, 2010.
E3 version 3.2 brings Elipse Event Logs new version, 3.0. It has been greatly
improved, especially concerning graphical interface usability:
Elipse Event Log Viewer: allows you to insert bookmarks in events, sort
events out per fields, and save filter configurations of each log file.
Furthermore, date visualization is now always on the time zone of the place
where the file was generated
Elipse Event Log Export: you can now choose event fields to be decoded
during export
5.2 Bugs Fixed
Alarm Server / Alarm Configuration
Fixed a bug when closing the Domain or deactivating the Alarm Server, which
eventually lead to losing some alarm messages (up to 99) that had not been
recorded in the database yet. {active since v1.00.018 Build 147 (or previous)}
For further information, please refer to http://kb.elipse.com.br/en-us/
questions/1919
Fixed a bug that could cause Viewer script errors after Deactivate method
call, in reference to an AlarmServer object. {active since v1.00.021 Build 96}
For further information, please refer to http://kb.elipse.com.br/en-us/
questions/1928
Fixed Alarm Summary's behavior when the Domain stops. Previously, the
Summary was erased whenever the Domain stopped (without closing it). Now,
Summary messages are only erased if the Domain is closed. {active since
v1.00.021 Build 96} For further information, please refer to http://
kb.elipse.com.br/en-us/questions/1929
Now, when deactivating and then reactivating the AlarmServer at run time,
the Alarm Summary hides (when deactivating) and reappears (when
reactivating). No message will be logged to the database during this process.
{active since v1.00.018 Build 147} For further information, please refer to
http://kb.elipse.com.br/en-us/questions/1947
Fixed E3 Alarm's behavior, which allowed an alarm message to remain active
in the Summary if the related AlarmSource was disabled (AlarmVerify =
False) via Studio, and later the Domain was updated. Now,when updating the
Domain, this message is removed from the Summary, and a message with
Enabled = 0 is logged to the database. {active since v1.00.021 Build 96} For
further information, please refer to http://kb.elipse.com.br/en-us/
questions/1948
Now alarms are only checked after AlarmConfig's complete activation, which
Version 3.2
71