Release Notes for eDAQ firmware v3.13.C

September 14, 2009

Special Notes for Version 3.13.x

Starting with v3.13, the eDAQ supports automatically updating all firmware in one step. Please see the eDAQ Firmware installation instructions for more information.

Releases since v3.11 support using SIE from TCE. Customers are strongly encouraged to start using SIE if possible. SIE has fundamental reliability advantages over SIF, and all future development efforts will go towards SIE. The choice of data format is now made in the TCE "Test ID / Network Setup" window, rather than the eDAQ's Data web page. The SIE workflow can be made identical to SIF by selecting the "SIE (delete old SIE files on test init)" data option; use of the web interface to manage SIE files is not required.

To get v3.13-compatible firmware and software, visit the SoMat v3.13 resource center at http://www.somat.com/resource_center/edaq_313.html.

Bug Fixes

  1. Reliability problems with ELTCB boards have been fixed. Under certain circumstances, ELTCB boards were causing eDAQs to reset with a CardException. This should no longer happen.
  2. Several firmware updater problems have been fixed.

Release Notes for eDAQ firmware v3.13.B and TCE v3.13.0

August 20, 2009

New Features

  1. The eDAQ firmware updater can now update all boards in one step. Please see the eDAQ Firmware installation instructions for more information.
  2. The eDAQ now supports an "alternate HTTP port." The alternate port must first be set on the eDAQ's network setup web page. This is intended for use with customers unable to contact their eDAQs on port 80, for instance, when using a RavenX cellular modem. TCE can use the alternate port by adding "edaq:port" to the TCE communications preferences; for example, "myedaq.eairlink.com:8000".
  3. The ELCOM board is now supported.
  4. Improvements to eDAQ battery monitoring. TCE now has a battery meter in the Test Status display, and both it and the eDAQ's battery monitor now detect and report certain conditions indicating battery failure. In addition, a new battery interlock on test start is now supported to ensure a test does not start on an eDAQ with a battery with insufficient charge.
  5. A new feature which can estimate the lead wire resistance of non-six-wire bridges has been added. This is not supported on LLB channels.
  6. TCE now supports modifying and creating from scratch eDAQ hardware configurations. This can be used to build a test with no eDAQ hardware connected.
  7. TCE now supports entering mV/V sensitivity for channel calibrations.
  8. The eDAQ manual is now included with TCE. It is accessible from the Help menu.
  9. The eDAQ can now detect and generate databases for cDAQ ITC modules. This functionality is available under the "cDAQ CAN Database Generator" link in the Vehicle Bus page under the Hardware tab on the eDAQ web interface.
  10. The GPS type connected to the COM board GPS port is autodetected on bootup. Do not unplug the GPS while the system is powered on! Voltage levels are decided upon bootup that may damage other GPS modules!

Bug Fixes

  1. The _utc_day_week and _local_day_week Desk Calculator functions have been fixed. Previously, they were not returning the day of week as documented. Now they correctly return 1 for Monday through 7 for Sunday.
  2. A bug which caused eDAQ failures with MPB pulse counter channels at low sample rates has been fixed.
  3. DVMs of low sample rate channels in TCE are now more responsive.
  4. Incorrect behavior on reading Smart Modules with invalid pass-through parameters has been fixed.
  5. A bug causing SIE files to be unable to be deleted when they otherwise should have been has been fixed.

Known Bugs

  1. The eDAQ may error reset when stopping a test that uses active query on the J1708 VBM. The eDAQ Logbook will contain a "Dropped VBM Packet" message and a CardException error if this occurs. This issue will be addressed in a future release.
  2. TCE always retrieves the SIE file with the latest date. If the eDAQ's clock is reset incorrectly or loses time, this may result in the SIE file for another test being fetched instead of the currently initialized test. If this happens, the web interface can be used to retrieve the correct file; to do this, click the "Manage SIE Files" button in TCE, or go to the eDAQ's Data tab in its web interface.

New or Revised Operational Notes

None.

Previously Issued Operational Notes

See the TCE help "Operational Notes" for previously released operational notes that may be helpful in using TCE and the eDAQ.