Download EMONITOR Odyssey™ Version 1.2 New Features and Enhancements

ENTEK IRD PRODUCT RELEASE NOTES
P/N 44488
EMONITOR Odyssey™ Version 1.2
New Features and Enhancements
These notes cover the following areas:

New features and changes between EMONITOR Odyssey version 1.1 and EMONITOR Odyssey 1.2.

Information about new drivers or improvements to current drivers. See “Driver Notes and Information” on page 2.

Omissions and Errata for this release. Refer to “Omissions and Errata” on page 4.

Important problem reporting information at the end of this document. Refer to “Problem Reporting” on page 5.
Improvements in Version 1.2
Support for Spanish Language Product-Wide
Odyssey Version 1.2 offers a Spanish language EMONITOR Odyssey. All display information is in Spanish, including
the database.
Support for French Language Product-Wide
Odyssey Version 1.2 also offers a French language EMONITOR Odyssey. All display information is in French,
including the database.
Support for Italian Language Product-Wide
Odyssey Version 1.2 also offers an Italian language EMONITOR Odyssey. All display information is in Italian,
including the database.
Full MIMOSA-Compliant Interface
ENTEK IRD is a charter sponsor of MIMOSA and is committed to supplying customers with MIMOSA-compliant
products as the specifications are officially approved for production use. EMONITOR Odyssey V1.2 includes the
following certified MIMOSA-compliant interfaces:
TREND-File Import & Export for Service Segments V1.1
#1110111 and #1120111
VIB-File Import & Export for Service Segments V1.1
#1110211 and #1120211
TREND-SQL Server for Service Segments V1.1
#1320111
VIB-SQL Server for Service Segments V1.1
#1320211
For more information on MIMOSA, visit the MIMOSA web site at http://www.mimosa.org.
You can also use SQL Snapshot protocol for MIMOSA-compliant procedures. To use SQL Snapshot, you must run a
script on your database. The script files are located in your Odyssey program directory. The default program
directory is C:\Program Files\Entek IRD\Odyssey. Select the correct script for your database server.
Script File
Database Server
snapshot.wts
Centura
snapshot.msq
MS SQL Server
snapshot.ora
Oracle
snapshot.syb
Sybase
page 1
Driver Notes and Improvements in Version 1.2
Please be aware that data collector driver .INI files will be overwritten during the install or update procedure.
This is done in order to be certain that the latest .INI files are installed on your system. If you have modified
your data collector .INI files, you may want to copy them for backup purposes.
dataPAC Driver Improvements
Several parts of the dataPAC driver have been corrected in this release of the Odyssey product. These corrections
include the following items.




Corrected a number of lines problem when combining a magnitude measurement followed by a spectrum
measurement. The driver would incorrectly use the lines of the magnitude measurement. The correction now
uses the correct number of lines for the combination.
Modified support of measurements with an orders frequency range. Previously this type of measurement would
be set up as an orders-based measurement, if the collector supported it. However, orders based measurements
have a maximum frequency limitation of 5,000 Hz. So, to alleviate possible measurement errors, orders based
measurements are only set up and loaded if the maximum frequency estimation (location RPM multiplied by
orders range requested) is less than or equal to 5000 Hz. This modification only affects the dataPAC1500 v4
and above.
Corrected problem involving unloading multiple data sets with improper frequency range (and other
measurement overrides). This correction only affects the dataPAC1500 v4 and above.
Corrected problem with mapping in window alarms. Earlier dataPAC drivers improperly map in window to above
upper threshold instead of above lower threshold.
This table shows the alarm set up in EMONITOR Odyssey, followed by how the dataPAC interprets the alarm.
EMONITOR
Odyssey alarm(s)
Diagram for
EMONITOR
Odyssey
dataPAC interprets
alarm as:
Diagram for
dataPAC
Notes
Mag in Window
(0.1 to 0.2)
Alarm Above 0.1
This interpretation has
changed from the previous
version.
Mag Above 0.2
Mag Below 0.1
Alarm Above 0.2
OR
Alarm Below 0.1
Alarms are the same in
EMONITOR Odyssey and the
dataPAC.
Mag Below 0.2
Mag Above 0.1
Alarm Below 0.2
OR
Alarm Above 0.1
Because the dataPAC driver
combines these alarms with
an OR statement, all values
are in alarm.
dataline Driver Improvements

The dataline driver has been fixed so that band constant alarms with trigger set to yes do not cause a floating
point exception to occur.

The dataline driver has been improved to better handle communications when using a DELL Optiplex computer.
880/885/FastTrack Improvements

This driver has been fixed so that band constant alarms with trigger set to yes do not cause a floating point
exception to occur.

This driver corrects a problem with serial communications during unload involving DELL Optiplex computers.
TEC Driver Improvements
The TEC driver has been corrected to fix a problem with order normalized time waveform measurements, which
were off by the square of the running speed. This version of the driver corrects this problem.
CSI Driver Improvements
The CSI driver has been corrected to fix a problem where unscheduled measurements were not unloaded. This
version of the driver corrects this problem.
page 2
Omissions and Errata
Odyssey version 1.2, March, 1999
ID Number
12309800
09109807
09019804
09019803
08319801
03169901
03069802
02159900
01289900
01259900
01219901
01159900
01139900
Description
Previously, if you would view many plots one after another, you could experience memory
errors due to a memory leak. This problem has been corrected in version 1.2.
The report condition "latest severity" would not save properly so the condition was not
applied. This bug has been fixed in version 1.2.
The exception report had a blank condition field. This has been corrected in version 1.2.
The problem with printer deletion causing an application error on start up has been corrected
in this version. Previously, if you deleted your default printer in Windows and tried to start
EMONITOR Odyssey, the program would fail. Also, if your default printer was a LAN printer
there were problems on start up. Both printer problems have been corrected in version 1.2.
Context-sensitive (F1) help was not working correctly for SE dialog boxes. This bug has been
fixed in version 1.2.
If you imported an image file into an image measurement definition, the date/time stamp was
not accurate. This has been corrected in version 1.2.
The maximum resolution possible for time waveforms is 8192 for Windows 95 systems.
Windows 95 has a limitation of 16000 data points for drawing operations disabling 16384
and 32768 time sample waveforms.
The security key check no longer forces key and database brand to be exactly the same. If
there is a security key attached to the computer, it will force the database to recognize it.
This should avoid security key error messages.
When unloading transient data from a 6600 monitor, an application error would occur. This
bug has been fixed in version 1.2.
The operator level had the ability to generate statistical alarms in the previous version. That
level of rights is reserved for supervisor or higher in version 1.2.
If you added a Percent Change column to a Magnitude Exception report, the report would
display data that is not in exception. This has been corrected in version 1.2.
Frequency items no longer take only the first item in the list for input.
Previously, when you tried to change a measurement's storage flag to Baseline instead of
Archive, EMONITOR Odyssey would fail. This version corrects this problem, allowing you to
change any measurement's storage flag to Baseline.
Previously, when you set the schedule for instrument unload in Unload Station Manager, the
start time had to be before the current time in the computer. This bug has been fixed in
version 1.2. Now you can set the schedule to the current time, or a time in the future and
Unload Station Manager will operate correctly.
Severity Updater previously required you to log in when a SQL error occurred. This bug has
been fixed in version 1.2.
Scheduler has been altered to allow it to run even if the database server is not available.
Export16, the utility used for exporting 16-bit Gupta databases, has been updated so that it
now exports certain data such as plot notes correctly. Previously, the notes would have been
attached to a single plot instead of being spread out across different plots as originally
intended.
page 3
Problem Reporting
With this release of Odyssey some new steps have been taken to facilitate more timely Support response. There are
two things you can do to help us solve any problems you encounter. The first is to note any information that occurs in
the unlikely event of Odyssey system halt, described below under “Reporting error messages”. The second is to
copy the form on the next page. Please fill out this form, and either have it with you when you call Entek IRD
Customer Support, or fax it to Entek IRD Customer Support.
Reporting error messages
Should you encounter a problem, the information below should be reported to your Entek IRD Support contact. By
providing it to Support Engineering, this information will facilitate more accurate and timely fixes to the problem.
For any system we will need to know the version of the software. Note that since Windows NT and Windows 95
machines behave slightly differently you will see one of the following depending on your Operating system.

For WinNT:
If a system halt occurs, a dialog will pop up with the application name at the top, usually followed by the words
Application Error. In the dialog you will see a message similar to the following:
The instruction at “0x00401171” referenced memory at “0x00000000”. The memory could not be “written”.

For Win95:
If a system halt occurs, a dialog will pop up with the application name at the top. The message in the dialog will
state that the program has performed and illegal action and will be shut down. There will be a Details button in
the dialog. Choose Details and you will see a message similar to the one below appear in the message box:
EPM caused an invalid page fault in module EPM.EXE at 0137:00401171
Please write down or copy the entire error message in the dialog, as well as any other information concerning what
you were doing at the time of the crash.
page 4
Entek IRD Customer Support Information Form
Phone: 1-800-EntekIRD / (513) 576-6121 Fax (513) 576-4213 www.entekird.com/support
To help us serve you better, please:
1. Fill out the form below with your product and problem information.
2. Call, fax or visit our website and use the information you gathered to help get your call into our support system
as quickly as possible.
ESAFE Contract Number:
Security Key #:
Contact Name:
Company Name:
Phone Number:
Fax Number:
Email Address:
Product Type:
EMONITOR Odyssey
EMONITOR Odyssey Online
Version:
Data Collector:
dataline
dataPAC
Other :___________
Operating Sys:
Driver Version:
PC Platform:
Network:
Database Type:
Problem Area:
Windows 95/98
Windows NT 4.x/5.x
NT networking
NetWare 3.x
NetWare 4.x
Gupta/Centura Single User
Gupta/Centura Multi-User
Oracle
Sybase
MS SQL Server
Archive Filter
Archive Pane
Band Filter
Band Sets
Button Bar
Categories
Collections
Data Collector
Define Columns
Drivers
Dialog Boxes
Find / Replace
Frequency Pane
Generate Statistics
Help Window
Hierarchy Pane
Install / Update
Lists
Load / Unload
Location Pane
Measurement Pane
Notebook
Use this space for any questions you have and/or a description of the problem.
Please list any relevant errors or steps required to reproduce the problem.
Please copy this form as needed
Pane Controls
Plots
Reports
Saving Views
Storage
Templates
Other