All changes from the previous releases are included in the newest version.

Version 3.6.5
14.03.2013
Improvement to avoid measurement failures caused by electromagnetic distortions.



Version 3.6.4
26.03.2012
Bug fixes:
- Fixed error in memory management that could occur under some circumstances and that led to loss
  of all data on the device.



Version 3.6.3
25.01.2012
Improvements for quality management reporting



Version 3.6.2
15.04.2011
Bug fixes:
- Fixed error in calibration check option.



Version 3.6.0
28.09.2010
New functions:
- Number of templates increased. It is now possible to store 255 templates for each configuration
  type on Detector.
- It is now possible to delete measured data for one measurement point, a machine, a plant or for
  all data. This applies only for the type of configuration currently selected. It can also be
  applied for free measurements.
- In the memory manager (system menu) it is now possible not only to delete all data stored on
  Detector (including configurations and templates), but also to delete only all measured data
  (configurations and templates will retain).
- It is now possible to delete a specific measurement for a cm measurement point.
- It is now possible not only to select a comment defined in Trendline, but also to enter a comment
  manually after a measurement.
- It is possible to configure for cm measurements that a comment is mandatory.
- It is now possible to view a trend for the characteristic values of a cm measurement on Detector.
- CM measurements can be done with a speed signal that has several pulses per rotation.
- New type of characteristic value: universal value (entered manually)


New features:
- A Warning is displayed if a default template could not be created due to insufficient memory.
- For cm configurations, some statistic facts are shown (number of measured configurations, total
  number of configurations and percentage)
- Serial number of RFID reader is displayed in the RFID settings menu.
- All measurements stored for a cm measuringpoint can be reviewed on Detector now.
- Proposal for trial weight has been improved.
- Alarm status of all characteristic values is displayed in an additional line in the summary shown
  after a condition monitoring measurement (except ISO 10816 single measurement).
- Automatic power down time which turns off Detector after 2 minutes in idle mode can now be set by
  the user between 1 and 99 minutes. It is also possible to disable the automatic power down
  function.
- Automatic power down is activated in balancing measure points when Detector starts in the same
  menu where it was switched off.
- For cm measurements, the rotational speed can be used even if it is instable, but a warning is
  displayed that must be acknowledged by the user.
- All internal voltages are written into header of logfile.
- For some hardware errors, additional information is stored in the logfile.
- Bias voltages for ICP sensors can be viewed in the settings and modified for free measurements.
- Bias voltages for ICP sensor used during single measurements can be modified.
- Resonance frequency bands can be reviewed for balancing configurations.
- Number of vibration averages can be reviewed for balancing and amplitude/phase measurements. For
  free measurements of these types this number can even be changed.
- For free balancing measurements, some parameters can be adjusted even after completing the
  reference run.
- During run up/coast down measurements, all values are discarded if rotational speed is below
  300 RPM.
- Dates are now displayed according to ISO 8601 (YYYY-MM-DD instead of DD.MM.YYYY).
- Speed measurements where the speed can be changed for an amplitude/phase measurement are only
  done when there are no measuring points or no measuring values for the measuring points.
- Single speed measurement can be done with a signal that has several pulses per rotation.
- Moving through the menus when canceling an action for a free measurement has been modified.
- During balancing proposed weights are saved now an can be reviewed in the steps shown in the
  "Previous Steps" list.
- When using discrete weight positions during balancing, the discrete weights entered are now
  stored.
- It is now possible to save time signals during a cm measurement if only a pre alarm has occured.
- Remaining imbalance is send to Trendline when a balancing job is fetched.
- Negative weights can be used for balancing.
- Calibration information displayed in a separate calibration menu.
- Calibration check can be performed.
- Added a characteristic value for the demodulation signal in the ISO 10816 single measurement.
- Faster digital filters for 200 Hz measurement (only for old hardware) and 500 Hz measurement (for
  all devices).
- The minimum number of discrete weight positions for balancing is now 3 instead of 4. This change
  applies also to the vector calculator that can be accessed from each balancing configuration.


Bug fixes:
- When selecting a measuringpoint by RFID, wrong cursor positions were stored for machine selection
  menu and measuringpoint selection menu.
- Wrong checksum was stored for free cm configurations when vibration sensor or trigger sensor
  settings were adjusted. This has been corrected.
- Display of long measuring point names could cause display errors under some circumstances. This
  has been fixed.
- Only 255 measurements can be saved for one cm configuration at the same time on Detector.
- When choosing what to do with a repeated cm measurement (overwrite, save extra or discard) the
  ESC-button is now ignored.
- Unused memory allocated for run up/coast down data is now freed.
- Altough not intended, it was possible to complete the speed measurement even when speed was above
  the maximum allowed value (9999 RPM) or speed was instable. This is no longer possible.
- Number of digits behind the decimal point were calculated incorrectly in some cases. This has
  been fixed.
- When using a different speed for balancing or amplitude/phase measurements than that configured
  the speed delta is adjusted if it exceeds 10% of the new nominal speed.
- The minimum frequencies for velocity characteristic values could be too small for free
  measurements. This has been corrected.
- In some menus characters remained when the display scrolled. This has been corrected.
- Long comments are now displayed correctly in the summary after a cm measurement and can be
  scrolled to read the whole text.
- Error message is displayed if measured speed is below minimum.
- DC offset is no longer removed from acceleration and velocity time signals when using a passive
  sensor with DC coupling.
- Sign of acceleration and velocity time signal samples is corrected (was inverted).
- Fixed problem that overrange was not detected in some cases when using amplification factors from
  a previous measurement that are now too high.
- In some places it could occur that no communication was possible directly after switching the
  device on. This has been fixed.
- Nominal speed for every amplitude/phase configuration is adjusted if the measuring points
  received from Trendline have speed values that are not inside the speed band of the configuration.
- Flags indicating whether time signals have been saved for a configuration are now set correclty
  to prevent logfile entries in Trendline.



Version 3.4.5
09.03.2010
Bug fixes:
- Support for serial number with a character as year (A-F)



Version 3.4.4
04.01.2010
New features:
- Support for new hardware revision (SN xxxxxx/F4).



Version 3.4.3
26.02.2009
Bug fixes:
- On some devices HW6 appeared after starting the system when using a very full battery (i.e. with
  high voltage) although the voltage responsible for HW6 was ok. This has been corrected.
- Under specific circumstances it could occur that all memory content was erased. This has been
  fixed.



Version 3.4.2
26.09.2008
Bug fixes:
- Length of strings in amplitude/phase menu corrected.
- Correct free measurement is selected for CM configurations now.
- CRC error doesn't occur any longer after deleting measurement values of measuring points of
  amplitude/phase configurations.
- Key description while entering weights during balancing was sometimes confusing. This has been
  modified.
- In some cases it could happen during a balancing or amplitude/phase measurement that no measured
  values were displayed due to an occured error, but the matching error message wasn't displayed.
  This has been fixed.
- Automatic power-off functionality (Detector turns off after two minutes without user actions)
  re-enabled when leaving a balancing configuration by pressing the HOME button.
- Automatic power-off functionality re-enabled when a run up/coast down measurement is aborted due
  to insufficient memory or maximum number of measurements reached.
- Automatic power-off functionality re-enabled after an amplitude/phase measurement has been done.
- After a trim run, the user can choose whether ha wants to make another trim run or a test run. It
  is now possible to alter this decision even after selecting one of the menu entries like 
  "Proposed weights".
- Very big weight proposals could not be displayed properly due to limitations of the display. They
  are now displayed in a bigger mass unit.
- If a cm configuration is measured a second time, the user can choose at the end if he wants to
  overwrite the first measurement, discard the second measurement or save it as an extra
  measurement. The automatic power-off functionality is disabled in this screen to prevent a loss
  of measurement data.
- Pressing HOME (button 1) or starting communication in some menus shouldn't have any effect, but
  in some cases the menu was left by doing so. This has been corrected.
- The warning after communication that passive sensors are configured appears only if there really
  is a configuration or template with a passive sensor.
- The warning that configurations with passive sensors are available on the system while the sensor
  is powered continuously was displayed only after communication. It is now also displayed when
  Detector is switched on and when the continuous sensor power supply is activated.
- Sensor initialisation before a measurement with activated contiuous sensor power supply is now
  stricter concerning oscillation of bias voltage to prevent influence on measurement.
- The same RFID number can no longer be assigned to several amplitude/phase configurations.
- Weight proposals for a balancing test run were too small when using peak or rms setting. This has
  been corrected.
- Maximum balancing limit ("Bal. OK at") is now 9999.0 instead of 9999.99999 because only four
  digits can be displayed and the old limit was rounded to 10000.
- Detector warns if coefficients seem to fit no longer.
- Position of trial weight corrected.
- During balancing with 2 planes, a CRC error could occur after trial run 1 if the trial weight was
  removed. This has been corrected.
- The angle in graphic displays for masses shown during balancing were counted in direction of
  rotation, but they must be counted against the direction of rotation.
- Number of samples for a time signal of a cm configuration were too small. Detector transfered
  only 4095 instead of 4096 and 8191 instead of 8192 respectively. This has been corrected.
- A CRC error could occur when a configuration with 2 balancing planes is changed to a free
  balancing configuration with only one plane. This has been fixed.
- In some cases it could occur that the top of a high positive peak in a time signal was reflected
  with respect to the time axis. This has been corrected.
- The calculation of memory size displayed in the memory manager for free run up/coast down
  configurations has been corrected.
- If remaining memory is insufficient for a free configuration, the template lists are no longer
  shown.
- A free run up/coast down configuration can only be created if there is also enough memory for the
  first block of measured data.
- A free amplitude/phase configuration can only be created if there is also enough memory for at
  least five measuring points.
- Key description during amplitude/phase measurement corrected.
- Improved communication with USB<->Serial converters.



Version 3.4.1
06.06.2008

New functions:
- The plant, machine and measuring point names of each configuration can now be up to 30 characters
  long.
- New measurement type: amplitude/phase
- Alphanumerical keyboard
- New single measurement: ISO 10816 class 1 to 4.


New features:
- A warning is displayed if coefficients send by Trendline can't be used due to a different
  rotational speed.
- Detector proposes a trial weight before every trial run.
- Detector starts in the same menu where it was when it was switched off. This feature can be
  deactivated in the settings menu.
- Detector displays and sends to Trendline an error message if the number of configurations, units
  or comments sent from Trendline don't matches with the number announced by Trendline before.
- Previous balancing steps can be reviewed now.
- Settings of a cm configuration can be reviewed now on Detector. Settings of a free cm measurement
  can not only be reviewed, but can also be edited.
- A default template is created for each configuration type for which no template has been sent
  from Trendline.
- Detector displays a warning if change of imbalance caused by trial weight is too small and allows
  the user to restart the trial run with a different weight.
- The vibration sensor can be powered continuously to skip the sensor initialisation when doing
  several measurements with the same sensor.
- A new vector calculator allows the user to define two weights, for which the angles are
  calculated.
- Leaving the summary shown after each balancing step by pressing <ESC> must be confirmed by the
  user.
- Rotational speeds shown in the general settings menus for cm, balancing and run up/coast down are
  displayed now in the configured speed unit and not in RPM. In addition, the speed unit is
  inserted as a new entry in these settings menus.
- The expected vibration levels for each sensor are displayed after the weights have been entered
  before a trim run.
- Sensor positions are displayed in a sensor chart before a balancing run and in the balancing
  settings.
- Weight positions for weights that should be attached can be viewed in a chart before a trial and
  trim run.
- Free cm measurements are handled now like cm configurations, i.e. they can be reviewed and
  measured several times.
- Error message shown after startup when a hardware error occured can now also be quit by pressing
  the ESC button.
- A warning is displayed if the calculated weights exceed 3 times the trial weights.
- After the trial run for plane 1 Detector checks whether the configured number of planes is ok.
  Otherwise a warning is displayed and the user can change the number of planes (changed
  configuration becomes free measurement).
- Logfile available on Detector.
- Numbers entered in settings menus for all configuration types can now have positions after the
  decimal point (only where it makes sense!).
- Pre-alarm limit for characteristic values of a cm measurement can be reviewed in the settings
  menu for characteristic values of a cm configuration and edited for free measurements.
- Display a smiley in front of each characteristic value in the overview after a cm measurement
  indicating its alarm status (:-) = no alarm, :-| = pre-alarm, :-( = main alarm).
- New language available: Polish


Bug fixes:
- Error message displayed when too many configs are sent to Detector is now "Too many configs" and
  not "Buffer overflow".
- The 5V supply for trigger sensor is now activated during single speed measurements. In previous
  versions, only the 12V supply had been activated.
- Detector remembers now the position in the run up/coast down menu.
- Display a warning when the maximum number of measurements for a run up/coast down configuration
  has been reached.
- When the memory is not sufficient for a new run up/coast down measurement, the last measurement
  for this configuration is no longer deleted erroneous.
- Prevent displaying too many entries in the list of plants, machines or measuring points for cm
  configurations (maximum number allowed is 256).
- Check whether RFID is available is performed up to five times on startup. Keyboard is deactivated
  during this check to prevent errors caused by pressing keys during this process.
- Time is now displayed correctly even if hour is greater than 18.


Known bugs:
- If a free cm measurement is repeated and the results are saved in addition to the first results,
  free measurements created afterwards can not be reselected in the "Previous Data" menu.



Version 3.2.4
09.11.2007
Bug fixes:
- When communicating with the Detector directly after a flashupdate and not sending configurations,
  the Detector crashed during startup. This has been corrected.
- When reviewing a FFT spectrum with 3200 lines of a cm measurement, a second measurement for the 
  same configuration done afterwards had wrong results. This has been fixed.
- Keyboard is disabled during communication except for On/Off and backlight button.
- Maximum order for run up/coast down measurements is now 10 instead of 4.



Version 3.2.3 
25.09.2007
Bug fixes:
- Corrected a bug which leads to problems in the tree when using more than 37 configurations, e.g.
  measuring points don't appear in the tree or plants appear twice in the tree.
- Minimum speed for automatic stop in free run up/coast down configurations has been changed 
  from 0.5 Hz (30 RPM) to 5 Hz (300 RPM), like in Trendline.
- Settings of free run up/coast down configurations can't be edited anymore after a measurement has
  been saved.
- Free run up/coast down measurements don't have crc errors any longer when Detector is switched 
  off during creation of the free measurement.
- The number of balancing steps that can be done by the user is limited to 255 to prevent a memory
  overflow.
- When decreasing the rotational speed in a free balancing configuration, the speed delta is 
  automatically decreased, when it is higher than 10% of the rotational speed.
- When sending too many time signals, the Detector could show CRC-errors when switched on or during
  communication. This has been corrected.
- Under certain conditions, the single temperature measurement didn't function correctly (Detector
  switched off when the measuring values should be shown or no values were displayed). This has 
  been corrected.



Version 3.2.2
17.07.2007

Bug fixes:
- Because of an error in the offset calculation, characteristic demodulation values for frequency 
  bands with small signal components are calculated wrong or become 0. This has been fixed.
- The frequency limits for selective characteristic values were rounded mathematically to the 
  nearest FFT line, which could lead to differences between the shown and the calculated frequency 
  band. Now the Detector only uses the FFT lines within the defined band, i.e. Frequency min. is 
  rounded up to the next FFT line, Frequency max. is rounded down.



Version 3.2.1
10.05.2007

New functions:
- RFID-handling
- Run up/coast down measurements

New features:
- Added calculations for using more sensor positions (up to 4) than balancing planes.
- The user can select a comment from a list created in Trendline after a CM measurement, after each
  balancing step and after a run up/coast down measurement.
- During the speed measurement for a balancing configuration, the Detector checks for resonance
  frequencies defined in the Trendline software.
- In the single measurements menu, the user can now use a ICP sensor tester.
- Added stability indicator for balancing measurements.
- The user can now reset the averaging buffer during balancing measurements by pressing the F-key.
- In the settings menu, the user can reset all balancing data, when at least the speed has been 
  measured.
- Added contrast settings menu.
- After the last trial run, the user can select which trial weight should be removed. The Detector 
  then shows online the resulting balancing weights.
- When speed is measured for a CM measurement, then the measured or enterred speed value is 
  shown with the resulting characteristic values.
- When using discrete positions, the user can now enter two trial weights for every plane.
- The user can now see and (in a free measurement) change the balancing limit in the settings menu.
- At startup the Detector executes a selftest and displays the errors, if something is not OK.
- In the Detector info menu the calibration date is shown.
- The Detector informs the user, when the sensor sensitivity changed from last measurement.
- The coefficients are now calculated after the measurement of every trial run. They now are also 
  stored in the trial run.
- When a trial weight 1 is not removed, it is also shown in plane 1 for the trial run 2.
- In the balancing sensor settings, the user can now also change the connector settings, when using
  balancing templates.

Bug fixes:
- Weights exceeding 1000gr are now shown in kg (accordingly for US weight units).
- It is now allowed to add a corrective weight of 0gr.
- Detector doesn't hang up during communication if Trendline chrashed and locked serial port but 
  ends communication after a few seconds if he can't send data any more.
- When enterring weights for discrete positions, the statusbar now shows "position" instead of 
  "angle".
- Frequencies on FFT diagram are displayed correct now (all in kHz if highest frequency is greater
  than 1000 Hz)
- The time signal viewer doesn't overwrite the title bar anymore.
- The memory size for CM and balancing configurations in the memory manager now includes free
  measurements
- The title shown in general balancing settings and balancing plane settings is corrected.
- During a balancing job with 2 planes when applying the computed weights, the number of discrete 
  positions (0 for continuous) for plane 2 were taken from plane 1 instead of plane 2. This has 
  been fixed.
- When the lowpass for the acceleration or demodulation signal of a CM measurement is set to 
  200Hz in combination with 3200 FFT lines, the velocity time signal shows incorrect values for 
  the first 70 measure points. This has been fixed. This bug didn't affect the characteristic 
  values!
- Pressing the backlight key during a balancing run doesn't change the measured value anymore.
- During a balancing run (reference run, trial run or trim run) it could rarely happen that the RPM 
  value shown in the summary at the end of the run was 60 times too big. This has been fixed.
- In the balancing menu the user could move the cursor onto a disabled menu item under some
  conditions. This has been corrected.
- The imbalance calculation used during balancing and run up / coast down is now more accurate.
- The warning "No RPM signal!" during a balancing run is now displayed in the center of the screen 
  and doesn't flicker any more (only updated if status has changed).
- The balancing limit for free balancing measurements is set to zero if the vibration unit is 
  changed.
- Dropdown menu for discrete positions ("Yes" or "No") in the balancing planes settings menu for 
  plane 2 of free measurements has been moved a bit to the left so that it is now displayed 
  completely.
- When accessing the "Apply Weights" menu during balancing right after the refernce run (only 
  possible if Trendline sent coefficients from previous balancing job), Detector hung up. This has
  been fixed.
- Above and below the dropdown menu is now only one line cleared and not 3 or 4 lines.
- When using a lowpass of 200Hz or 500Hz in combination with 3200 FFT-lines, some values at the end
  of the time signals were wrong. This has been fixed. This bug did affect the characteristic 
  values!
- Values are now displayed and saved correctly on Detector when using anglo-american units.



Version 3.0.4
31.01.2007

General bug fixes:
- Several corrections in Spanish texts
- Corrected several errors in the Slowene translation.
- When pressing enter very quickly after starting the speed measurement, the Detector sometimes
  stored 0RPM. This has now been disabled.
- When a configuration has a checksum error, sometimes all other configurations of the same type 
  (i.e. CM or balancing) were not read by the Trendline. This has been corrected.
- Some ICP sensors take very long the initialize. The Detector now not only checks the amplitude of
  the bias voltage, but also waits until it is stable.
- Reading internal voltages (e.g. sensor bias voltage) now always works correctly, fixing problems
  with random sensor errors.
- Random keyboard lockups have been fixed.
- During balancing and CM measurements, the Detector not only finds loss of sensor power or short 
  circuit, but also a broken cable or removed sensor.
- Reprogrammed speed measurement menus and corrected some smaller cosmetic bugs.


CM bug fixing:
- When the lowpass for the acceleration or demodulation signal of a CM measurement is set to 
  200Hz in combination with 3200 FFT lines, the velocity time signal shows incorrect values for 
  the first 70 measure points. This has beend fixed. This bug didn't affect the characteristic 
  values!
- The velocity and acceleration time signals are stored without an offset.
- Viewing free cm measurements on the Detector didn't work correctly (wrong or no measurement was 
  shown). This bug has been fixed.
- Improved speed of the hanning window calculation.


Balancing bug fixes
- Pressing any key except <Enter>, <ESC> or <Backlight> during a balancing run (reference run, 
  trial run or trim run) stopped the balancing measurement and no new values were calculated.
  This has been corrected.
- Pressing the backlight key during a balancing run doesn't change the measured value anymore.
- Changing the trigger sensor settings in a free balancing measurement could lead to checksum 
  errors during communication.
- In the balancing menu the user could move the cursor onto a disabled menu item under some 
  conditions. This has been corrected.
- In Vector_Calculator_Split_Angles, the user could enter 2 equal phases, which showed weight
  values of NaN.
- In Vector_Calculator_Split_Angles, the calculations now always search for the smaller angle
  between Phase1 and Phase2 to define the allowed range.
- In all vector calculators all weights now have 2 decimal digits. 
- In the split angles vector calculator, the user can now only enter a weights phase between 
  phase 1 and 2. Other values would result in negative weight values.
- Increased the number of balancing averages from 5 to 20
- Pressing any key during balancing measurements now doesn't change the displayed values anymore.
- Improved accuracy of the balancing calculations.
- When reading data from free balancing measurements, all measurements got the steps of the first 
  measurement. This has now been corrected.

