MaxQData MQ Software 3.4d
Release Notes
Release date: December 10, 2009

First release officially supporting Windows 7

Chart
-----
- changes to Power Report, including manual postprocessing adjustment for weight and LongG vs Speed

Flight
------
- support for Pegasus Imaging MJPEG codec; if "Morgan Multimedia M-JPEG V3
codec" is not found, Flight will look for "PICVideo M-JPEG 4 32-bit VfW Codec";
please note that the current version of Windows Media Player under Windows 7
does not appear to play back MJPEG ASF files correctly (audio stretching,
frame interleaving problems) if the video frame size is 640x320 or larger,
however these files will play correctly under Windows XP if the correct codec
is installed
- new AudioBufferLengthWMV, AudioBufferLengthMJPEG,
AudioBufferLengthUncompressed registry values
- AudioBufferLength chosen based on video encoding type
- new AudioBufferWindow, VideoBufferWindow registry values
- "netsh wlan connect name=<profile>" on Flight launch under Win32 if <profile>
(usually SSID) is present in GPS Port setting in Settings
- GPS Road Power calculation cleaned up for Quantum 20 Hz
- fix TSLH to properly handle 20 Hz sampling

Settings
--------
- added "Enable precapture buffer" checkbox to Camera Capture Settings dialog; unchecking this box can
eliminate audio/video synchronization problems, but then the precapture buffer will not be used,
so for autocrossing it is important to use the LongG threshold on the Flight Recording Trigger
or manual start
-  To have Flight cause a connection to specific network, append the profile
name to Settings > Serial Port Settings > GPS Port by typing a semicolon (';')
at the end of the IP address and then the profile name, e.g.
"169.254.1.1:2000;MaxQDataQuantum", where "MaxQDataQuantum" is the name shown
in the Windows Wireless Manager for the network used to connect to the Quantum



MaxQData MQ Software 3.4c
Release Notes
Release date: October 19, 2009

All
---
- restored correct resource files corrupted by Visual Studio during update of version number



MaxQData MQ Software 3.4b
Release Notes
Release date: October 12, 2009

Chart
-----
- fixed issue where Align B to A might not work correctly if the alignment
point was more than 45 seconds from the beginning of the file

Flight
------
- added support for GT-750F GPS module
- added support for Quantum WiFi Edition v15 firmware
- completed support for Quantum WiFi Edition for Windows Mobile
- fixed GPS Lap Time issue resulting in accumulated lap time rather than per-lap time
- reduced periodic "tick" sound when capturing audio and video using Morgan MJPEG codec
- added new CameraCaptureSetup\AudioBufferLength value



MaxQData MQ Software 3.4a
Release Notes
Release date: August 31, 2009

Chart
-----
- resolved problem causing Chart to crash with error 0xc0000005 at offset 0x000521c6
when two video files are loaded, one video window is then closed, and Play is
pressed in the remaining window

Flight
------
- fixed problem where sequence number was still added when filename prefix included
MMDD HHMM
- fixed problem causing extremely long delays at FRT start and stop when processing
TXT files
- fixed certain problems connecting to MQ200
- completed support for Quantum WiFi Edition for Win32



MaxQData MQ Software 3.3a
Release Notes
Release date: July 18, 2009

All
---
- Please uninstall all earlier versions of the MaxQData software before
upgrading to version 3.3a.  If your uninstall fails, you should at least
delete any Start Menu or Desktop shortcuts you may have for MaxQData Setup.
- Support for Vista and 7 User Account Control application security model.
Please note that the unlock challenge and response codes will both change
when installing 3.3a.  Also, the current calibration will be reset, so users
are advised to backup their current calibration before installing and then restore
it after installation.
- Video features now support the Morgan Multimedia MJPEG V3 codec.  This codec provides
significantly improved video capture performance, allowing larger frame sizes and
higher frame rates than when using WMV encoding at the expense of larger video
files.  There is also an option to recompress to WMV after capture.

In order to take advantage of these performance improvements, the user must install
the Morgan Multimedia MJPEG V3 codec, which can be found here:

http://www.morgan-multimedia.com/technicalsV3.htm

Please note that the Morgan Multimedia MJPEG V3 codec is not free software, though it
is inexpensive and the download is a 60-day free trial.  If you did not receive this
codec bundled with your MaxQData system, you will need to purchase it from the publisher.
See the link above for more details.  MaxQData does not warrantee the performance of
the Morgan codec or other third party software.

Installing this codec causes a red googly-eyed smiley face to appear in the system tray.
Users can adjust the codec properties by clicking this smiley face and choosing "Codec
properties".  The default settings are good for general-purpose use.  The user can
trade off file size for image quality by checking the "Forced quality" checkbox
and adjusting the slider setting.  The recommended setting is 75 (be sure the
checkbox is checked).  This results in file sizes of about 1.2 MB per second (when
"Bitrate control" is checked).  Reducing quality to 25 cuts the file size in half
with a noticeable but not severe reduction in video quality.

- At the time of this release there is no support for the Windows 7 Release Candidate,
but the software has been tested on it.  There are three Known Issues at this time:
1) CPU utilization is higher during video capture and this may result in lower frame
rates; 2) Videos encoded with the Morgan MJPEG encoder may not play back at the correct
speed in Windows Media Player; 3) Clicking the play button in a video window in Chart
results in an application crash.  The workaround is to enable post-capture transcoding
to WMV so that the MJPEG encoding is changed to WMV encoding before the video is used
with Chart.

Chart
-----
- fixed issue preventing Qview export from comparing one file to a different file
- when displaying two video windows, pressing the Play button in either window now starts
both video windows playing, unless the offset lock is unchecked for the other file
- resolved crash on exit from Chart due to main window being destroyed before video windows
- minimum window size for video windows is now smaller to better support netbook screen sizes
- Unlock code response code in File > Advanced is now read-only; please use MaxQData Settings
to enter your unlock code.
- new 0-75 MPH, 0-120 KPH ranges for MPH for autocross support

Flight
------
- file sequence suffix number now starts at 001 instead of 000
- new 0-75 MPH, 0-120 KPH ranges for MPH for autocross support
- Flight Config > Sensors > Standard now adds VertG, Roll Rate, Pitch Rate, Yaw Rate,
Lean Angle, Roll Angle, Pitch Angle, and Drift sensors to the Standard list if enabled
- resolved issue where Flight would process a TXT file containing multiple sessions ad
infinitum, endlessly creating MQD files for only the first session

Settings
--------
- name changed from "Setup" to "Settings"
- removed Lagarith encoding option
- added MJPEG encoding option
- compress/transcode to WMV after capture is now allowed for both MJPEG and Uncompressed encoding
- default value of PhaseShift calibration point for Video Sync sensor changed to -1200
to better synchronize data and video when using MQGPS-Quantum
- changed unlock code scheme

Installer
---------
- The installer no longer contains the Prism video transcoding software.  Customers who need
video transcoding software (e.g. if they are using their own camera rather than a VeQtr
system) can download the free version of Prism here:

http://www.nchsoftware.com/prism/index.html

The Chart application will use Prism for transcoding files to WMV if Prism is installed
on the user's system.
- You must run the installer as an administrator under Windows Vista and Windows 7.



MaxQData MQ Software 3.2a
Release Notes
Release date: July 3, 2009

Chart
-----
- resolved problem causing some computers to fail to load a file when File > Load was used
- Qview screen plot is revised to give a cleaner appearance and support the new yaw rate-
based Heading and Drift measurments
- resolved issue where some video files, when played back in Chart, would "hang" the UI
until the end of the video

Flight
------
- reliability improvements to help resolve "hanging" 22 KB file issue, video but no data issue,
bomb on stop logging
- set WMV encoder complexity to 0, new CameraCaptureSetup\Complexity registry setting

Sensor Drivers
--------------
- new drivers for MQGPS-Quantum when equipped with gyro cluster: "Roll rate", "Pitch rate",
"Yaw rate", "Roll angle", "Pitch angle", "Heading", and "Drift"

Software Installer
------------------
- Installer no longer resets System Type to MQGPS or resets sysetm options to GPS only


MaxQData MQ Software 3.1i
Release Notes
Release date: 6/11/09

Flight
------
- support for MQ1604 module

Setup
------
- support for MQ1604 module



MaxQData MQ Software 3.1hR2
Release Notes
Release date: 6/3/09

Flight
------
- On Pocket PC, the timeout for resetting the Bluetooth connection was the same as the time
it took for the MQGPS-HiDef to start tranmitting data, resulting in barely any data getting
through and a very low sample rate.  This has been resolved.


MaxQData MQ Software 3.1h
Release Notes
Release date: 5/28/09

All
------
- fixed the version number


MaxQData MQ Software 3.1g
Release Notes
Release date: 5/27/09

Flight
------
- adjusted GPS Time Since Last Here so it works at the 20 Hz sample rate of the Quantum


MaxQData MQ Software 3.1f
Release Notes
Release date: 5/27/09

Flight
------
- fix for problem where Flight, when processing a Quantum TXT file, misses the rising edge of the Flight
Recording Trigger


MaxQData MQ Software 3.1e
Release Notes
Release date: 5/27/09

Chart
-----
- new feature: multi-file select during File > Load (Win32 only)
- new feature: multi-file select during File > Unload
- new feature: align B to A


Flight
------
- corrected processing of TXT files to prevent lockup on PCs with single-core CPUs
- If the destination drive ("Set filename prefix...") runs low on free space, Flight
will run but will not allow a flight recording to be recorded and will stop any
current datalogging.  It will also display the message "Out of disk space".

Setup
-----
- auto placement of second and third PiP secondary cameras now goes to different corners


MaxQData MQ Software 3.1d
Release Notes
Release date: 5/20/09

Chart
-----
- fixed Play 0.5x, Play 0.2x, Play 0.1x playback rates

Flight
------
- new Roll Rate, Pitch Rate, Yaw Rate, and Lean Angle sensor drivers for MQGPS-Quantum
- improvements to Bluetooth reconnect process
- fixed rare occurrence of sudden large jump forward in time when using MQGPS-Quantum

Setup
-----
- now supports optional Roll, Pitch, and Yaw rate sensors for MQGPS-Quantum


MaxQData MQ Software 3.1c
Release Notes
Release date: April 14, 2009

Chart
-----
- fixed problem where scrolling with the arrow keys was disabled once any parameter
checkbox has been unchecked or some other UI elements have been clicked

Flight
------
- Fixed problem during video capture where audio would become dissynchronized (advancing
relative to the video), distorted, and lower in pitch when CaptureBufferDuration was > 0.
Note that the new precapture buffer duration maximum is now 2 seconds.  This means that
users who race from a standing start using the Flight Recording Trigger must configure the
FRT to trigger no more than two seconds into their run, e.g. by setting the Start Speed to
a low value or enabling the new LongG threshold.
- Fixed problem where video would start writing to disk immediately, regardless of FRT
state, when CaptureBufferDuration was 0.
- Fixed glitch causing two simulated NMEA sentences to be read before Quantum TXT file
processing starts.
- Improved time-to-connect for Bluetooth, reducing pseudo-hangs of the UI.
- Fixed problem where Flight does not turn on Bluetooth on Windows Mobile devices with
the Microsoft Bluetooth stack
- Enabled using MQGPS-Quantum with MQ200; set System Type to "Hybrid" (MQ175 and earlier
are not supported when using the MQGPS-Quantum).
- Fixed problem where Speak Lap Time would continually repeat the time

Setup
-----
- new option to have FRT trigger based on LongG when under StartSpeed


MaxQData MQ Software 3.1b
Release Notes
Release date: March 22, 2009

Flight
------
- resolved problem under Windows Mobile where Flight would not reconnect to the MQGPS
after reconfiguring sensors unless "Is Bluetooth" was unchecked
- added support for Open Road racing type including revised Dashboard display
- resolved "An invalid argument was encountered" error when loading an MQGPS-Quantum text file
- when processing a Quantum TXT file, Flight now uses the name of the text file as the
basis for the MQD filename, and places the MQD file in the same folder as the TXT file
- On a PC, Flight will attempt to terminate if the destination volume goes below
64 MB of free disk space.
- resolved problem causing poor initial Bluetooth connection performance with
MQGPS-Quantum; please note that the Quantum will not connect and no data will
be shown on the screen until a sufficient number of satellites have become
visible

Setup
-----
- Added two new sensors: GPS Elapsed Time and GPS Average Speed.  GPS Elapsed Time is the time
since GPS Distance became non-zero (i.e. when the car started moving).  GPS Average Speed
is GPS Distance divided by GPS Elapsed Time.


MaxQData MQ Software 3.1a
Release Notes
Release date: March 11, 2009

Chart
-----
- new Power Report
- new slow speed Play options

Flight
------
- adjusted timeouts to allow for long camera initializations, avoid problem
where MQ200 does not connect if MQGPS present
- new camera preview option
- adjusted decel threshold on Speak MPH
- corrected repeated Speak MPH (minimum time between MPH announcements is now 10 seconds)
- adjusted Speak LatG algorithm
- saving beacon files now adds MQB to filename if user does not
- If GPS COM port is set to TXT in Setup, and the NMEAInputFile registry
key is not present or has zero length, then Flight presents a dialog box
allowing the user to specify a text file.  This file must contain NMEA
sentences.  This is how a user opens a file captured by an MQGPS-Quantum
or other GPS modules with NMEA logging.
- support for processing the new MQGGA, MQVTG, and MQGGG sentences produced by the Quantum
- fixed problem where Flight hangs after sensor pick
- When Flight runs, if no sensors have been selected, Flight picks a standard list of sensors.

TraQr Manager
-------------
- speed threshold now does increments of 0.1 MPH to support BT-Q1000X which cannot do 5 Hz at a speed threshold of 0

Setup
-----
- saving calibration files now adds MQS to filename if user does not
- auto-placement of second and third secondary cameras fixed



MaxQData MQ Software 3.0c
Release Notes
Release date: January 24, 2009

Chart
-----
- improved support for HD video and 16:9 video
- new "HQ Preprocess" option for overlay export
- new bitrate options for overlay export
- Video overlay shows speed in KPH if Metric Locale is set in Setup
- fixed problem where video export did not work on a clean install if Setup was not run first to enter unlock code
- when using non-WMV/ASF files, Chart now creates a WMV file first (using Prism) and names it with
the name of the MQD file
- Qview and numeric plot scaling for large frame sizes fixed in data overlay
- KML export speed-based coloring fixed
- fixed problem where in some cases it was not possible to use t..tA/tB video export if the tA/tB mark was set
at the beginning of the file and the video was captured with Flight
- fixed problem where Chart would crash when displaying Qview or producing a video overlay if
Chart had never shut down successfully before at least once
- Please note: In order to enter an unlock code in Chart when running under Windows Vista, you must use
Run As Administrator, otherwise the unlock code will not be saved.

Flight
------
- resolved data vs. video phase shift with calibratable delay parameter on "Video Sync"
- fixed MQ200 compatibility issue causing Flight to exit when using MQGPS-HiDef
- Video overlay shows speed in KPH if Metric Locale is set in Setup
- Dashboard display shows speed in KPH and altitude in m if Metric Locale is set in Setup
- External display shows speed in KPH and altitude in m if Metric Locale is set in Setup
- Voice readout of peak speed reads in KPH if Metric Locale is set in Setup
- LongG threshold on voice readout of peak speed lowered to -0.3g

Setup
-----
- messagebox informing user that "Camera" box is unchecked on exit from Camera Capture Settings
- new "metric locale" option under Settings > Advanced



MaxQData MQ Software 3.0b
Release Notes
Release date: January 7, 2009

Setup
-----
- fixed "Load calibration backup..." greyed out



MaxQData MQ Software 3.0a
Release Notes
Release date: December 30, 2008

Please note that version 3.0a uses new unlock codes which are not compatible with earlier
codes.  You will need to enter a new unlock code after you upgrade to 3.0a from previous
versions.  Contact MaxQData for details.  No unlock code is necessary for Chart, unless
you intend to use the video post processing features.  No unlock code is necessary for
MQ100-MQ200 users unless you are also using an MQGPS in parallel.

Chart
-----
- new video overlay export feature
- new YouTube upload feature
- new LoadCSV feature supports loading of data files from other data acquisition systems for video export
or direct comparison; please note that successful import of a CSV file generated depends on the
precise use of parse expressions; the default parse expression will read basic data from a Trackvision export;
consult the user manual or MaxQData support forums for explanations and information on supporting other
CSV export types
- new KML (Google Earth) file export option replaces GPX export option
- keyboard arrow keys in Chart now scroll the data left and right
- left/right scrolling with arrow keys or D-pad now starts with fine movement
and accelerates if you hold it down
- scrolling buttons are now flipped (right arrow moves forward in time)
- (PC) Beacon menus are now accessible from the main menu
- new racing type "The Ring" supports Nurburgring and other open-course events such as the Silver
State Classic; set Racing Type to "The Ring", then set up beacons so that there is a beacon at
the start line (flying start) and a beacon at the finish line with optional intermediate beacons,
and set Beacons Per Lap to be the total number of beacons added
- Chart now has an unlock code (for video post processing features) which can be entered
using File > Advanced.
- Video post processing uses NCH Software "Prism" freeware to perform automatic video file
conversions.  Prism is a separate download.  It is not required for VeQtr-X users.

Flight
------
- new video capture feature with multi-camera support, Picture-In-Picture, and Data Overlay
- new voice feature speaks lap and segment times, g's, and MPH
- action button adds a beacon when RacingType is set to Autocross, otherwise it
displays the best lap time when using the lap time display
- added internal GPS Hz monitor	to reprogram GPS module if it self-resets
- improved synchronization with Flight Recording Trigger when processing TraQr BIN files
- improved speed of processing TraQr BIN files
- improved handling for LogFileQueue buffer overflow condition
- GPS Lap Time behavior has changed: this now shows cumulative lap time since the start of the current lap,
updated at each beacon position (to support Nurburgring, Silver State Classic, and other open-course events)
- GPS Road Power has been updated to include aerodynamic drag and rolling resistance estimates, resulting in
an estimate for actual drive wheel horsepower in order to better correlate with chassis dyno testing;
to negate this, set CdA and Crr to 0.0

Tracker
-------
- fixed Bluetooth write timeout issue causing download error on Pocket PC

Setup
-----
- new camera capture setup dialog
- calibration points are now editable on Smartphone devices
- new racing type "The Ring"
- If MQPort = NONE and GPS Port = TXT, then Flight will simulate a stationary GPS module.
This allows use of the software (including video capture) without connecting to an MQGPS
or MQ200.



MaxQData MQ Software 2.9a
Release Notes
Release date:

All
---
- non-touchscreen Smartphones now supported

Chart
-----
- fixed issue where lap time computation could be off by one sample period


Flight
------
- resolved certain performance issues while in debug mode



MaxQData MQ Software 2.8c
Release Notes
Release date: May 8, 2008

Setup
-----
- MQ Module Configuration is now written to the registry unconditionally

Tracker
-------
- default MQSystemOptions =  MQOptionMaskGPS

Sensor Drivers
--------------
- fixed new RMSPitchRate, etc. drivers so they are only activated if the
correct MQ Module Configuration is enabled

                                                  

MaxQData MQ Software 2.8b
Release Notes
Release date: April 30, 2008

Chart
-----
- fixed comparison PNG folder target when comparing two different files
during a Qview export
- registry entries for changing Qview LatG/LongG/Velocity delta scaling



MaxQData MQ Software 2.8a
Release Notes
Release date: April 24, 2008

Chart
-----
- fixed unhandled exception when adding a beacon and no GPS Track made good
information present in file
- added more output fields for Trackvision support

Flight
------
- action button now adds a beacon when logging a flight recording for more
convenient course walking
- MQGPS-HiDef reconfiguration for improved 10 Hz operation

Sensors
-------
- added the following MQ200 sensor drivers: Pitch Acceleration, RMS Pitch Rate,
RMS Pitch Acceleration, RMS VertG

Setup
-----
- checkbox for Instructor Mode

MQGPS-TraQr Manager
---------------------
- added new application to support the MQGPS-TraQr product



MaxQData MQ Software 2.7b
Release Notes
Release date:  February 26, 2008

Flight
------
- fixed problem calculating real-time lap/segment times (Latitude and
Longitude were swapped when importing beacon file into calibration)
- added IP address to timing and MQD emails
- "Screen tap" now defaults to unchecked
- "MMDD HHMM" in the flight recording file name now uses the time the flight
recording was triggered rather than the time the flight recording was closed
- the Lap Time display mode now shows current GPS MPH in the upper left corner
- Using the "Add beacon" feature, you can now add cone markers while walking
the course.  These markers can be viewed in Chart plotted against the course
map.  To use, first manually start a flight recording.  Then walk the course,
stopping at each cone of interest.  It is recommended that you have your MQGPS
on your head while walking the course (e.g. under a baseball cap).  Put the
MQGPS over each cone position (e.g. by standing over each cone) and tap 
Config > Add beacon.  Then walk to the next cone of interest and repeat.
When you are finished, stop the flight recording.  You may wish to give the
.MQD file a special name, such as "NatsNorthCones.mqd".  You can then load
this file in Chart using File > Load cones.


Chart
-----
- fixed plot wrap-around problem at large zoom values and large window sizes
- New cone plotting feature File > Load cones.  This is especially useful
for autocrossing.  See above for how to create a cone file while walking the
course.  Use the File > Load cones menu option to load a file specifically
as a cone file (if you use File > Load instead, the file will load like a
normal flight recording file).  When you are displaying other flight
recordings, the cone positions will be marked with orange squares on the
trackmap.  Please note that GPS drift throughout the day may alter the
relative position of the trackmaps for each run compared to the cone
positions.  Use care when interpreting the results.

Codes
-----
- added Codes.txt file to installer

Setup
-----
- fixed problem importing beacons where Latitude and Longitude were swapped
- when GPSHz not set to Default and 5 Hz license, GPS sample rate configuration
commands will be sent (for legacy MQGPS-USB and MQGPS-RS232 support)
- When installing over old versions, the value for the old and now unused
"Repeated fields are zero length" is ignored to avoid file read performance
problems
- Flight Recording Trigger StartSpeed default is now 20 MPH, StopSpeed is 15 MPH



MaxQData MQ Software 2.7a
Release Notes
Release date: October 25, 2007

General
-------
- release number bumped to 2.7a in light of extensive changes since last
non-beta release

Flight
------
- fixed problem where dashboard display might show GPS Jerk when not enabled
- GPS modules are reset down to 2 Hz, GPGSA and GPGSV enabled, and other
navigation parameters are reset on exit to support third party software
(only when using a 10 Hz license and GPS Hz is set to > 5 Hz)

Chart
-----
- fixed error generating timeslip when GPS Jerk is recorded but GPS LongG is
not
- export to XLS, CSV, and TXT now exports Lap Time and Segment time in m:s
format correctly
- export to TrackVision now adds MAP columns



MaxQData MQ Software 2.6f
Release Notes
Release date: October, 2007 (beta only, no official release)

Flight
------
- new feature: Directional GPS Beacons (see notes for Chart)
- new feature: Log > Add beacon.  Use this while walking an autocross course
to add beacons to the flight recording during the course walk.  We recommend
wearing the MQGPS on your head or carrying it in your outstretched hand for
best accuracy while walking the course.
- support for Lite version
- fixed problem where beacon count was one less than the actual # of beacons
inserted when using real-time beaconing
- improved filtering on GPS LatG to support 10 Hz operation
- Dashboard display now shows tent of a MPH for speed and hundredths of a g
for LatG and LongG.  Also, if "GPS Jerk" is present, it will be displayed
in place of GPS LatG.
- fixed problem where LatG and LongG dashboard values might not be displayed
due to uninitialized handles
- fixed problem where only positive max values for LatG and LongG were shown
on the dashboard
- if GPSHz is set to > 4, on exiting Flight, GSV will be reenabled and the
sample rate set to 4 Hz on exit to support navigation software and other
third party applications that are unable to work at high sample rates

Chart
-----
- new feature: Map > Slide map B allows you to slide the B map around with the
stylus to adjust for GPS drift when comparing files.  The slide distance is
not permanently recorded in the flight recording.
- new feature: Directional GPS Beacons.  When adding GPS beacon points, Chart
now takes into account the direction the car is heading as it passes a beacon
point.  When exporting beacons, the Heading of the car is recorded along with
the Latitude and Longitude of the Beacon point.  When importing beacons (or
when manually using "Add beacon each lap..."), the beacon is triggered only if
the vehicle passes close enough to the beacon Latitude/Longitude and is heading
within +- 45 degrees of the heading recorded with the beacon.  This allows
beacons to be placed at locations where the track bends back tightly on itself
or crosses over itself.  Please note that your old beacon files will still work,
but since they do not contain directional information, the beacons will not
be directional.  You will need to create new beacon files to take advantage of
this new feature.  You can create a new beacon file from any flight recording
so long as it contains the "GPS Latitude", "GPS Longitude", and "GPS Track made
good" sensor values.
- GPS beacon position is now interpolated to improve alignment of beacon "X"
marks between different files/laps
- Please note: When adding a beacon manually to a flight recording, the beacon
is actually marked by the time of the current sample, therefore segment times for
this file will be multiples of the base sample frequency (e.g. 0.200 second
for 5 Hz sampling).  This does not mean that the segment times are only accurate
to the nearest 0.200 second.  The segment time is exact.  In effect, it means
that the *beacon position* is adjusted so that the segment time is precisely a
multiple of 0.200.  When exporting the beacon to a file, the beacon Latitude and
Longitude are taken from this sample and placed in the beacon file.  When
this beacon is imported into a *new* file, the Latitude/Longitude samples will
not be the same Latitude/Longitude samples as recorded for the first file.
So the beacon times are interpolated based on the closest that the car comes
to the original beacon Latitude/Longitude, in order to preserve 0.001 second
precision.  This is why the segment times for the new file are not multiples of
0.200.
- support for Lite version
- When generating timeslips, if GPS Jerk and GPS LongG are present and there
is a rolling start, a standing start timeslip is calculated.  The time to go
from 0 to the rolling start speed is estimated based on the acceleration of
the vehicle immediately after the initial Jerk spike.  The total 0-to-whatever
time is therefore the estimated 0-to-rolling start time plus the actual
rolling start-to-whatever time.  This is good for measuring boat acceleration
(since it is hard to get a boat completely stopped in the water) and also car
acceleration if there is some initial roll due to slope in the road at the start
line or GPS speed drift.  For most accurate results, keep the rolling start speed
low, e.g. under 5-6 MPH for a boat, under 1-2 MPH for a car.  (In a car,
especially one with a clutch, the jerk phase of a rolling launch will
not resemble that of a standing launch if the car is already rolling so fast
that a drop-clutch engagement or sudden WOT produces little or no momentum
transfer from the rotating mass of the engine to the forward momentum of the
car.)



Setup
-----
- new feature: Directional GPS Beacons (see notes for Chart)
- support for Lite version
- added new Jerk and GPS Jerk sensor values (Jerk is the rate of change of
LongG over time)




MaxQData MQ Software 2.6e
Release Notes
Release date: September, 2007 (beta only, no official release)

Flight
------
- Please note: in the current implementation, the real time lap time calculation
is the sum of the previous one lap of beacons, which means that the reported lap
time may change at each beacon.  This is a feature, not a bug.  Lap times calculated
in Chart are based off the location of the first beacon encountered and do not
change at successive beacons.
- There is now no user interface delay when between switching drivers.
- You can now add "MMDD" and/or "HHMM" to the prefix in File > Set name prefix.
When each flight recording is closed, the month and day are substituted for
"MMDD" and the hour and minute are substituted for "HHMM".  Please note that
if "HHMM" is used, the trailing numeric suffix (000, 001, etc.) is not added
to the filename, unless more than one flight recording is created within the
same minute.  The "MMDD" and "HHMM" may appear anywhere in the prefix, but
only the first occurrence of each is replaced.  The letters must be capitalized.
- simplified the main menu
- timespan for strip chart plot and min/max values is now fixed at 10 seconds
and is no longer user-configurable for simplicity
- added GPS Altitude to Standard sensor list
- removed Grey color scheme option
- corrected filtering on GPS LongG
- added new "Dashboard" display option under "Config" menu
- now supports logging debug data to "\SD-MMC card\"

Chart
-----
- relative HTML links now for Qview export
- trip point for beacon import is now 50 feet (three car lengths) in Autocross mode
- fixed error after Qview export when timing details are displayed
- under the Map menu there is now a "Rotate Zoom" option; when checked, the
Zoom/Qview display rotates with the car so that the top of the screen is always
where the car is heading; when unchecked, the top of the screen is always North
- miscellaneous improvements to Qview export, including horsepower plot

Setup
-----
- support for COM ports above COM9 under Win32 (use "\\.\COM10" format)
- improved support for 10 Hz Bluetooth GPS modules (uBlox ANTARIS 4 chipset only)



MaxQData MQ Software 2.6d
Release Notes
Release date: June 24, 2007

Installation
------------

- fixed problem where buttons at bottom of screen were not visible during
installation in landscape mode

- fixed problem where file assosication was not set correctly on PPC,
resulting in "that is not a valid log file" message when opening the file
by tapping on it in File Explorer

- Unlock code (and challenge code) are preserved during upgrade if the
earlier version is not manually uninstalled.  However, it is recommended
that users write down their unlock code before upgrading in case there is
a problem.

Flight
------

- fixed problem preventing attachment of flight recordings to outgoing email
(email sent without attachment, attachment name has '"' at the end)

- fixed problem where MQGPS-USB and MQGPS-RS232 would get stuck on $GPVTG
sentence and no more data would be processed

- "Force recording" now causes Flight Recording Trigger to be ignored

- manually starting a flight recording causes Flight Recording Trigger
to be ignored until the flight recording is stopped manually

- 10 Hz GPS support

- fixed problem automatically loading timeslips in Pocket Internet Explorer

- fixed problem where automatic Timeslip generation was not working
correctly

Chart
-----

- Export to "Qview report" now supported on Pocket PC

- now supports 240x240 square screen correctly when turning on/off Show
Numerics

- default to full track display for Autocross

- fixed Show Timing displaying one too many segment times

- fixed problem where Qview export did not export in the release build

- fixed problem where Chart would sometimes bomb after exporting a Qview
report

- fixed problem where Trackvision export would stall if initial GPS
Longitude was 0

- 10 Hz GPS support

Setup
-----
- for MQ200 Speed sensor, calibration point SpeedSignalSource default is now
3 (GPS) to avoid erratic operation when user does not set this after
installation



MaxQData MQ Software 2.6c
Release Notes
Release date: May 30, 2007

This release is only for the PC version of Chart.

Chart
-----
- New feature: Export to "Qview report".  This creates a series of segment-
by-segment Qview comparisons between two flight recordings (or within the
same Flight recording).  The comparisons are saved as Web pages which can
be viewed in a Web browser.  If desired, you can print these comparisons
from the browser.



MaxQData MQ Software 2.6b
Release Notes
Release date: April 11, 2007 

NOTE: PLEASE READ THE RELEASE NOTES FOR 2.6A BELOW.

Flight
------

- New SMS lap/segment time feature for Pocket PC Phone Edition users.  SMS
messages can be sent automatically at the end of each lap/segment to a list
of phone numbers.  Each message contains lap and segment time information.
Use Setup to configure this feature, and be sure to flight record "GPS
Beacon timestamp", "GPS Lap count", "GPS Lap time", "GPS Segment count", and
"GPS Segment time" (or the equivalent non-GPS values).  Do not use "GPS Time
Since Last Here" unless you are willing to send/receive a large number of
SMS messages as this value changes.  Please note that your cellular provider
may charge you for each outgoing and incoming SMS message.  You will
increase the number of messages sent as the number of beacons per lap
increases.  This feature can quickly use up the SMS message limit on some
phone plans, so use it carefully.  SMS messages will only be sent while
logging a flight recording.

- Data file format change for more efficient storage.  Large files are now
approximately half the file size of earlier formats.  As a rule of thumb, a
typical MQGPS setup will consume about 25 KB per minute.  A Pocket PC with
32 MB free storage memory would be able to record for over 20 hours
straight.  We continue to support independent software development via our
flight recording parser API (contact MaxQData for details).

- Improved startup time for devices using the Widcomm Bluetooth stack.

- Fixed problem where timestamp would not update with a direct-connect GPS
and GPRGH disabled.


Chart
-----

- Changed unlock code implementation.  MQGPS users of 2.6a may need a new
unlock code (contact Info@MaxQData.com for instructions).  All MQGPS users
will need an unlock code if they do not already have one.  Be sure to read
the release notes for 2.6a.

- When selecting files to view in either the A) or B) section, the filenames
are displayed differently (filename first, then full pathname) to make it
easier to distinguish between them.  In Autocross mode, if a lap time is
available, it will be shown between the filename and the pathname.

- improved visibility of lap and segment time overlay

- increased maximum loaded file count to 100, subject to available memory

- Play timing accuracy improved

- support for new compressed file format

- fixed scaling of full track map plot relative to the size of the plot area

- fixed screen layout issues for 640x480 and 480x640 devices


Setup
-----

- eliminated "Repeated fields are zero length" option

- moved unlock code input field to top of "Settings > Advanced" dialog box

- new "MaxDistanceToBeacon" setting under "GPS Beacon timestamp" allows
tuning the beacon distance sensitivity for different track sizes and
configurations

- real-time beacons must be placed at least 5 seconds apart (previous
threshold was 10 seconds)

- new configuration dialog for new SMS feature (see above)

- defaults for a clean installation are now for an MQGPS-Bluetooth on COM7,
RacingType = Autocross


Sensors
-------

- fixed problem with real-time GPS beacon timestamping sometimes causing two
beacons to be placed one right after the other



MaxQData MQ Software 2.6a
Release Notes
Release date: not officially released - beta only


Flight
------

- IMPORTANT: ALL MQGPS USERS MUST CONTACT MAXQDATA TO RECEIVE AN UNLOCK CODE
IN ORDER TO ENABLE 5 HZ OPERATION.  WITHOUT THE UNLOCK CODE, THE SOFTWARE
WILL ONLY LOG GPS DATA AT 1 HZ.  ALL ORIGINAL PURCHASERS ON RECORD MAY
RECEIVE AN UNLOCK CODE AT NO CHARGE.  CONTACT INFO@MAXQDATA.COM. SEE THE
"SETUP" SECTION BELOW FOR MORE DETAILS.  MQ200 USERS DO NOT NEED AN UNLOCK
CODE.

- PLEASE NOTE: Some Pocket PC models will automatically disable Bluetooth if
you turn off the Pocket PC while Flight is running and the MQGPS-Bluetooth
is connected.  When you next power on the Pocket PC, you will no longer see
the Bluetooth LED flash, and Flight will not reconnect to the MQGPS-
Bluetooth, even after you wait a while.  You will have to exit Flight, then
manually reenable Bluetooth.  This appears to be a problem in the Bluetooth
stack.  If your Pocket PC behaves in this manner, you should File > Exit
from Flight before turning the Pocket PC off (do not use the 'X' in the
upper right corner of the screen).  Although Flight will attempt to turn on
Bluetooth if it is turned off, some Bluetooth implementations may not
respond as expected.  Be sure to test this before relying on the ability
to turn off your Pocket PC while Flight is running.  On the other hand,
some Pocket PCs do not exhibit this behavior.

- It is no longer necessary to turn on the MQGPS or MQ200 before starting
Flight.  You can start Flight before or after.

- Recommendation for preserving battery life:  Start your race weekend with
a fully charged Pocket PC and MQGPS-Bluetooth.  Leave the MQGPS turned on
all weekend (or at least during the day), but turn off the Pocket PC via the
power button between runs.  On many Pocket PCs it is not necessary to exit
Flight before turning off the Pocket PC, but see the caution note above.
When Flight is not running, the MQGPS will go dormant and conserve battery
power automatically.  Power on the Pocket PC before you head back to the
grid for each new session.  Depending on how much you use your Pocket PC,
you will probably make it all the way through the race weekend without
having to recharge either the Pocket PC or the MQGPS-Bluetooth.

- Improved reliability for real-time GPS Lap Time and GPS Segment Time.  Be
sure to place beacons more than ten seconds apart in time and more than 100
feet apart in distance when using GPS Lap and Segment time.  Also note that
the vehicle must be moving at least 12 MPH in order to trigger a GPS beacon.
If the vehicle passes a beacon point which was not the next one in sequence,
additional beacons will be added immediately after that point to
resynchronize the lap and segment counts, but these will have to be manually
edited afterwards.  This can happen if, for example, the first beacon
encountered is not the first beacon that was placed on a lap, or if a beacon
was not triggered.

- Improved Bluetooth reset/reconnect

- Fixed problem where Bluetooth might not connect immediately after power-on
when Flight assigned to a button

- Improved MQGPS-Bluetooth start-up times.

- New feature: multi-driver support.  Set filename prefix as before, default
is still "Run".  New "File > Set driver list" feature allows you add a list
of drivers (or a list of courses, or whatever), e.g. "Rick;Tony;Sue" or
"TomNorth;KenNorth;TomSouth;KenSouth".  The actual filename will be <prefix>
<driver><XXX>.mqd, e.g. "RunTomNorth000.mqd".  When a driver list is in use,
the current driver name is printed in light grey letters in the background
of the Flight display (except on the Lap Time screen).  You must switch
between drivers by using the up and down keyboard arrows or d-pad buttons or
jog wheel.

- fixed problem with MQGPS v.1 units where sometimes Flight would get out of
sync with the GPS data and data would drop out

- Clarification of the Lap Time Display feature:  This will display one of
three possible lap time measurements: 1) GPS Time Since Last Here, 2) Beacon
lap time, or 3) GPS Lap Time, in that order of preference.  For example, if
you have both GPS TSLH and GPS Lap Time set to record in the sensor
configuration, the lap time display will show GPS TSLH.

- Changed "Standard" list of sensors.  This list is now "Flight recording
trigger", "GPS Latitude", "GPS Longitude", "GPS Satellite count", "GPS
Vehicle speed", "GPS Distance", "GPS LatG", "GPS LongG", "GPS Track made
good", "GPS HDOP", and "GPS Seconds past midnight UTC".  If using an system
other than an MQGPS, "Internal LatG" and "Internal LongG" are added as well.

- fixed a mutex problem possibly causing type 1 records to not be acquired
in rare cases

- When Racing Type is set to "Drag Race" (see notes on Setup and Chart,
below), you can enable Timeslip generation as before.  When Racing Type is
set to any other type, the Timeslip option becomes "Launch Chart". When
enabled, each new flight recording is automatically loaded into Chart.  If
"Display Report" is enabled, Chart will remain in view while Flight
continues to run in the background.


Chart
-----

- Play now automatically loops back to the beginning of the flight recording

- Friction circle plot now uses "Internal LatG" and "Internal LongG" (if
present) in preference to "GPS LatG" and "GPS LongG"

- Improved Qview(tm) display:  faster/slower depiction.  In order to see
this, the A) and B) files must be approximately synced (within roughly five
seconds) and QView must be enabled.  The A) car is then the "reference" car.
The QView blocks are outlined in gray.  The B) file is compared to the A)
file and the outline color of each block is chosen based on whether the B)
car was faster or slower at that point on the track.  If the outline color
is green, the B) car was faster at that point. If the outline color is
yellow, the B) car was slower at that point.

- improved lap and segment time precision for MQGPS-based systems

- increased font size for "Show timing" values

- fixed Trackvision export problem with Power value

- Chart will now load up to 20 flight recordings at the same time, available
memory permitting

- New feature: "File > Racing Type".  Users should set the racing type
(Autocross, Circle Track, Drag Racing, Other, Rally, or Road Racing)
appropriate to the data files they open.  This establishes certain
assumptions about how to interpret the data.  In this version, "Autocross",
"Drag Racing", and "Rally" are treated differently than the other options in
that "laps" are open-ended, and the "lap" begins at the last time Distance =
0 before the top speed in the file.  In other words, no beacon is placed at
the start of the lap; it is inferred by where the car starts moving.  Thus,
to time a lap, one need only place a single beacon at the finish line.  "Add
beacon each lap" is disabled (there is only one "lap"); instead, simply use
"Add beacon".  With each new beacon, BeaconsPerLap is incremented.  Also, it
is no longer necessary to set BeaconsPerLap to one less than the number of
beacons placed in order to compute lap time.  For "Circle Track", "Other",
and "Road Racing", laps are assumed to be closed.  Lap 1 begins at the first
beacon, not where the car starts moving.  It is necessary to use "Add beacon
each lap".  "Add beacon" does not increment BeaconsPerLap.

- When Racing Type is Autocross, Drag Racing, or Rally, the Timing Details
display is simplified to show total elapsed time and individual segment
times.

- Each new file loaded after the first is automatically placed in the B)
section (previously, the third and successive files loaded would only be
loaded and would not be placed in either the A) or B) section for viewing)

- Once Chart is opened, tapping a flight recording in File Explorer will now
bring Chart to the top and automatically load the flight recording.
Previously, on Win32 it would start a new instance of Chart before loading
the file, and on WinCE it would have no effect.

- When exporting or importing beacons, the user is given the option to
automatically re-import the beacon file for each new flight recording
loaded.  If the user chooses "Yes", every time a new file is loaded, any
beacons in that file will be erased and replaced with the beacons from the
specified beacon file.  This continues until the user does another import or
export and answers "No", or until the user exits Chart.

- Cleaned up screen redraw on orientation change so fragments of previous
display weren't still visible on Pocket PC.

- New feature for Pocket PC: "Chart > Show numerics".  Unchecking this
removes the bottom three lines of the display (the ones that show the
numeric values of the data traces) and expands the plot area, making the
plot area much easier to see in landscape orientation.

- improved full track map scaling to use more of the display area

- Zoom mode track map (including Qview) is now plotted so that "forward" is
always straight up on the display, in other words it is oriented along the
driver's perspective looking ahead; this keeps the two track maps better
separated on the screen


Setup
-----

- IMPORTANT: MQGPS 5 HZ UNLOCK CODE NEW FOR THIS RELEASE.  Under Settings >
Advanced..., you will see "Unlock code", followed by a number, followed by
an area to enter a second number.  You must provide the first number (which
is unique to every installation) to MaxQData in order to receive the unlock
code.  You then enter the unlock code in the area for the second number.
Original purchasers on record may obtain an unlock code at no charge.
Unrecorded users may be required to pay a license fee.  If you install the
software on another device, or if you hard reset your system and reinstall
the software, you will need to contact MaxQData for a new unlock code. Users
will have to reenter the unlock code when installing upgraded software. THE
UNLOCK CODE DOES NOT AFFECT MQ200/MQ175/MQ125/MQ100 USERS.  ENTERING AN
UNLOCK CODE OR NOT ENTERING A CODE HAS NO EFFECT ON THOSE SYSTEMS - THEY
WILL CONTINUE TO OPERATE AS BEFORE WITH FULL FUNCTIONALITY.

- "Delay Bluetooth Init" is no longer recommended.  Unchecking this option
will speed start-up.  Use this option only if you are having problems making
a Bluetooth connection immediately after power on.  If you are using an
MQGPS-Bluetooth v.2 module, please select "Default" for "GPS Hz", which will
also quicken start-up.

- Settings > Advanced... Menu now includes "Racing Type" selection.  This is
the same setting as in Chart.


Sensors
-------

- Added new ECT (Engine Coolant Temperature) and IAT (Intake Air
Temperature) sensor drivers for direct-wired sensors. Please note that these
are currently simple linear models.  Many temperature sensors will output a
non-linear voltage as a function of temperature.  You should choose
calibration points that are near the expected operating temperature (e.g.
20C below normal temp and at the normal temp).  This will preserve accuracy
near the operating point, but note that the farther away from this point you
get, the more inaccurate the measurement will be.



MaxQData MQ Software 2.5c
Release Notes
Release date: October 24, 2006

Chart
-----
- smoother plots at small time scales
- fixed problem where correct scale factor did not always appear for parameter 2 on PC Chart



MaxQData MQ Software 2.5b
Release Notes
Release date: October 7, 2006

Flight
------
- improved dynamic response configuration for MQGPS (reduces likelihood of dropped samples in hard cornering)
- added Power Ratio sensor driver
- corrected CAN OBD-II communications issues
- new calibration option to turn off automatic Distance zeroing at zero speed

Chart
-----
- added new horsepower report
- segment times now show speed at beacon and maximum segment speed
- added TrackVision export option
- QView is based on GPS for MQ200 (easier to see than if based on internal accelerometer)



MaxQData MQ Software 2.5a
Release Notes
Release date: July 28, 2006

Flight
------
- added Send Via Email feature (see Setup) to send data file to email recipients
- performance optimization for writing data buffers to disk
- GPS Seconds Past Midnight does not freeze when Satellite Count drops to zero but satellites are actually visible
- new full screen lap time and lap count display under Config menu; must be recording GPS Lap time/Beacon lap time/GPS
Time Since Last Here and/or GPS Lap count/Beacon lap counter; press action button or left/right/up/down button
best lap time
- Lap time and segment time display in Minutes:Seconds
- resolved problem on some MQGPS-Bluetooth modules causing out-of-order data
- removed Window size options 1, 2, 5 seconds from Config menu

Chart
-----
- added new Export option: GPX (popular XML format for GPS data), compatible with GPSVisualizer.com and others
- align to start of run on load only for data files less than 5 minutes long
- new Import beacon feature (add each lap on the basis of previously exported .mqb file)
- In addition to minutes:seconds display of lap/segment times under lap/time summary already supported, the
parameter value field will also show minutes:seconds if the flight recording was made with 2.5a or later

Setup
-----
- added new "Settings > Email..." for configuring Send Via Email feature; note, immediate email send trigger
only available on Windows Mobile 5.0 devices (use scheduled send/receive for WM2003 devices)
- added new "Max Record Time" calibration value for Flight Recording Trigger; controls maximum file size
- added configurable GPS sample rate under "Settings > Serial Port Settings..." (only for MQGPS)



MaxQData MQ Software 2.0m
Release Notes
Release date: July 6, 2006

Flight
------
- when creating MQDebugLog files, Flight on Pocket PC will first attempt to create the file
in "\Storage Card\" (not localized).  If it is unable to create the file there, it will attempt
to create the file in "\My Documents" (localized).  Note that not all Pocket PCs name their
storage cards "\Storage Card".  On PC, Flight will create the file in "\My Documents" (localized).
- fixed problem where flight recording prebuffer was not written out when the time between
starting Flight and starting a flight recording was short
- resolved issue with GPS Time Since Last Here which was not producing a value

Chart
-----
- added "View > Set zero time" feature which zeros the time at the current view position
- when loading a file that is less than one hour in length, Chart now automatically does an
"Align to start of run" and a "Set zero time"
- cleaned up Sensor Configuration dialog on PC



MaxQData MQ Software 2.0l
Release Notes
Release date: June 26, 2006

Flight
------
- fix for problem when GPS time jumps by one day

Chart
-----
- Align to Start of Run fixed, automatically aligns runs when loaded



MaxQData MQ Software 2.0k
Release Notes
Release date: June 4, 2006

Flight
------
- eliminated redundant processing of RMC sentence when GPRGH is selected
- It appears that the 4 Hz/5 Hz GPS modules will sometimes report Satellite Count as zero even
though the module continues to report valid GPS position/velocity solutions.  This is often the case right around
times when there are 12 satellites visible.  The result is unnecessary data dropouts.  Previously, Flight
would ignore incoming data when the satellite count was zero.  However, now Flight will only ignore incoming
data when the "GPS Fix Quality" value is zero (indicating no fix or an invalid fix).  If Satellite Count is
reported by the GPS module as zero, but GPS Fix Quality is not zero, then Satellite Count will be set to 20
to indicate this condition.  Users may wish to flight record the GPS Fix Quality and GPS HDOP values as
an additional check on GPS data validity.
- range for GPS Satellite count changed to [0, 20]
- Flight Recording Trigger range corrected (this caused Flight to terminate abnormally due to a divide-by-zero
error when Flight recording trigger was a selected value and the display was set to strip chart mode)

Chart
-----
- track map will plot data points where the satellite count was zero as long as fix quality was not zero



MaxQData MQ Software 2.0j
Release Notes
Release date: May 16, 2006 

Chart
-----
- QView(tm) will use GPS LatG/GPS LongG if available.  If not available, it will use Internal LatG/Internal LongG.
- fixed Full Track Map overlaid file alignment problem
- fixed regression error where Timeslips could not be generated on the Pocket PC
- fixed problem where MPH-MPH times in Timeslip would not be generated if start speed was above 0 MPH



MaxQData MQ Software 2.0i
Release Notes
Release date:

Flight
------
- added suppport for 5 Hz MQGPS (users of 4 Hz MQGPS-Bluetooth modules should remove the rechargeable battery
for 5 seconds, reinsert, turn on, wait for satellite lock, and run Flight in order to reprogram the module for
5 Hz operation; if no data shows within 30 seconds, File > Exit from Flight and run Flight again; users of
MQGPS-RS232 and MQ200 4 Hz GPS modules should contact MaxQData for info on reprogramming)
- added spurious value rejection and filtering on GPS LatG and GPS LongG
- added InitISO9141d2 registry value
- eliminated filtering of displayed value for MQGPS
- removed 50 second Min/Max window option for consistency with MQGPS prebuffer size
- fixed millisecond roundoff error issue with GPS-based timestamps
- MQGPS prebuffer size is now 25 seconds at 5 Hz



MaxQData MQ Software 2.0h
Release Notes
Release date: May 5, 2006

Chart
-----
- switched back to 240x320 for 240x240 displays (better to let user scroll than to squish the plot)
- added half-speed playback option
- added "Chart > Align to start of run" feature (finds maximum speed in flight recording then
scans backwards for Distance = 0 or beginning of run, whichever comes first; only for flight
recordings less than one hour long)
- eliminated View > Grey option
- Full GPS Map scaling for file B) is now the same as A) even if the extent is larger
- enabled g-g plot for GPS LatG/GPS LongG
- sign change on GPS LatG (right turn should be positive)
- sign change on Internal LatG when Orientation = 0 or 2 (right turn should be positive)
- sign change on Internal LongG when Orientation = 1 or 3 (acceleration should be positive)

             
Flight
------
- reduced display filtering causing excessive delays in screen value updates for GPS-based systems
- GPS Distance now resets to zero automatically at zero speed (when already moving slowly)
- changed "Standard" sensor selections
- check to make sure MQGPS is at 4 Hz and reconfigure if it isn't
- fixed strip chart plot (regression error)
- changed prebuffer sizing (MQGPS is about 20 seconds; MQ100-MQ200 are 2500/(sample rate) seconds)

Setup
-----
- Fixed problem setting Mass calibration for GPS Road Power in PC version



MaxQData MQ Software 2.0g
Release Notes
Release date: April 9, 2006

Chart
-----
- Pocket PC screen sizes now supported: 240x240, 240x320, 320x240, 480x640, 640x480
- fixed problem causing abnormal termination when dragging plot area on Pocket PC
- fixed side-by-side Qview
- fixed plot area drag not in sync with stylus

Flight
------
- Pocket PC screen sizes now supported: 240x240, 240x320, 320x240, 480x640, 640x480

Setup
-----
- Pocket PC screen sizes now supported: 240x240, 240x320, 320x240, 480x640, 640x480



MaxQData MQ Software 2.0f
Release Notes
Release date: April 4, 2006

Chart
-----
- added Play feature
- corrected File Load bug on Pocket PC version
- fixed Lap Time Copy under Windows XP

Flight
------
- corrected PWM driver logic, improved support for MQ200-MAX

Setup
-----
- re-added OK buttons for dialog boxes



MaxQData MQ Software 2.0e
Release Notes
Release date: March 26, 2006

Chart
-----
- improved file-to-file sync when scrolling the plot in Plot-By-Distance mode

Setup
-----
- enabled 115200 baud rate selection in PC version of Setup



MaxQData MQ Software 2.0d
Release Notes
Release date: February 9, 2006

Flight
------
- disabled Sensor Reset on Flight Recording Trigger
- gauge configuration Save on Exit issue resolved
- tickcount and timestamp no longer reset to zero with each successive data stream restart (BT support)
- if GPS time goes backwards, timestamp in file will not increment by one day

Chart
-----
- fixed problem reading portions of engineering conversion information section in header of .mqd file



MaxQData MQ Software 2.0c
Release Notes
Release date: December 29, 2005

General
-------
- IC Period now displayed to 3 digits after the decimal point
- added Vbat sensor driver for MQ200


Flight
------
- fixed issue where Pocket PC might hang after stopping a flight recording
- fixed MQ200 high speed sample rate issues



MaxQData MQ Software 2.0b
Release Notes
Release date: December 21, 2005

General
-------
- support for MQ200
- consolidation of all sensor drivers into one .DLL file


Sensors
-------
- fixed problem where "MQTemp" units were calculated as "C" but shown as "F" (number was correct, unit was wrong)
- fixed GPS LatG so sign agrees with Internal LatG
- added meters unit for Distance


Chart
-----
- previous sensor selections are now remembered between Chart sessions
- some other values now persist between Chart sessions
- new color-coding of LatG/LongG along trackmap in GPS Zoom mode
- fixed bug where plot-by-GPS Distance was not available
- fixed problem where Chart would not load a file or would crash when activated by File Explorer
- added per-channel time markers and max/avg/min calculations, accessible through context menu
- added background grid (View > Show grid)


Setup
-----
- New module configuration page supports MQGPS, MQ100, MQ125, MQ200; allows selective deactivation of certain groups of sensors



MaxQData MQ Software 1.9f
Release Notes
Release date:  September 6, 2005

Chart
-----
- new feature: export to .CSV/.TXT will optionally split every 65000 lines
- fixed display wraparound at 4200 seconds problem



MaxQData MQ Software 1.9e
Release Notes
Release date:  August 27, 2005

General
-------
- added support for parsing GPS NMEA RMC sentence in addition to VTG sentence

Chart
-----
- resolved issue where sensor values using degrees symbol would not load under Windows 98
- fixed cache problem causing strange track maps to be drawn when one flight recording
is unloaded and then a different flight recording is loaded
- fixed problem generating .CSV/.TXT files where "%c" is shown instead of data

Sensors
-------
- changed degrees symbol to the character 'd' to avoid W95/W98 related Unicode problems
- added GPS Turn Radius


Flight
------
- added optional 10 second delay before Bluetooth connect (to allow BT stack sufficient
time to set up; enable in Setup Settings > Serial Port Settings...
- improved Bluetooth reconnect capability when Bluetooth goes out of range



MaxQData MQ Software 1.9d
Release Notes
Release date: May 30, 2005

Flight
-------
- fixed Dell Axim X50v slow screen update issue

Chart
-------
- fixed Dell Axim X50v slow screen update issue



MaxQData MQ Software 1.9c
Release Notes
Release date: May 7, 2005

General
-------
- added GPS LongG and GPS LatG to MQ175 and MQ125 builds
- fixed "Copy t..T" problem on PC Chart (where Paste would yield garbage characters)
- added deceleration results to timeslip
- added graph of HP and LongG by MPH to timeslip (good for generating power curves)



MaxQData MQ Software 1.9b
Release Notes
Release date: April 18, 2005

General
-------
- support for MQ-GPS
- support for 4Hz GPS module
- improved Timeslips (0.01s precision, 1 foot rollout, improved logic for detecting
start and end of 1/4 mile run)
- minor UI tweaks
- PC versions of Flight, Setup, Codes
- new .MQD flight recording file format with constant-length beacon section
- fixed 2.4% error on RPM calculation using pulse input channel



MaxQData MQ Software 1.8c
Release Notes
Release date: October 24, 2004

Chart
-----
- minor UI tweaks

Flight
------
- fixed bug where "File Save As" did not "take" immediately

Other
-----
The calibration for Internal LatG and Internal LongG has been changed slightly
for MQ175 modules in order to recitfy certain inconsistencies between the Orientation
setting and how the "X1gT35", "X-1gT35", "Y1gT35", and "Y-1gT35" calibration points
were interpreted.  MQ175 modules with serial numbers 0107 and lower may have one or
both axes "inverted" after installing 1.8c.  Users are advised to sanity check the
Internal LatG and Internal LongG readings after upgrading to 1.8c and reloading
their calibration backup.  If it is discovered that an axis is inverted, follow
this procedure:

a. Determine whether the major or minor axis measurement, meaning the
lengthwise or widthwise axis of the MQ175, is inverted.  For example, if the module
is installed in Orientation 0, and Internal LatG is inverted, then the lengthwise
"major" axis of the MQ175 is the one that is inverted.  The minor axis is called
the "X" axis and the major axis is called the "Y" axis.

b. Find the "1gT35" and "-1gT35" sensitivity calibration points under the Internal LatG
calibration in Setup corresponding to the inverted axis (e.g. "X1gT35" and "X-1gT35"
are the minor axis sensitivity calibration points).  Invert the sign of both calibration
points (e.g. 512.0 would become -512.0).  Save to a new calibration backup file.

c. Run Flight and check to make sure that the axis is no longer inverted.

d. Also check against gravity for a symmetrical swing about 0g.  For example,
if you stand the box perfectly vertical on one end and it reads "1.05g", and you
stand it perfectly vertical on the opposite end and it reads "0.95g", but it reads
very nearly zero when level, then the reading is not symmetrical.
To try to correct for this, swap the "1gT35" and "-1gT35" calibration points
corresponding to that axis.  Some MQ175s may have identical or nearly identical
values for the "1gT35" and "-1gT35" calibration points, in which case you can
leave them as they are or attempt to tweak the values manually.




MaxQData MQ Software 1.8b
Release Notes
Release date: September 27, 2004

Chart
-----
- adjustable smoothing of data traces
- fixed lap/segment timing copy to clipboard
- enabled minutes:seconds display of lap/segment times
- calculates theoretical best lap from minimum segment times
- easy jump to lap # via lap times
- minor color scheme improvements

Flight
------
- one-button pick minimum recommended sensor set
- optional disable of flight recording pre-open (allows storage card swap during pit stop)
- Flight Recording Trigger: must now exceed Stop Speed before speed < Stop Speed stops flight recording
- if flight recording cannot be created in target folder, tries \My Documents as a fallback



MaxQData MQ Software 1.8a
Release Notes
Release date: September 11, 2004

General
-------
- fixed problem where "ISO is 14230" setting was ignored
- updated MQ100 support
- various stability improvements



MaxQData MQ Software 1.7g
Release Notes
Release date: August 6, 2004


General
-------
- improved support for Bluetooth connections (in MaxQData Setup->Advanced..., check "Is Bluetooth" for COM ports that are BT)

Flight
------
- GPS Distance computed from Doppler-based GPS Speed using $GPRGH for greater accuracy
- fixed Road Power sensor driver
- new GPS + LongG option for Speed
- added yaw rate trace to Timeslip graph
- new GPS-based beaconing/lap times/segment times
- fixed problem where power cycle would cause Flight to cease collecting data
- fixed problem where starting a second flight recording without exiting Flight first could cause lockup
- added new "OBD2 Generic PID", supporting J2190 Enhanced PIDs on some vehicles
- Flight will prevent automatic Pocket PC suspend while running

Setup
-----
- improved debug log capability
- specify OBD-II bus explicitly or autosense
- adjust ISO initialization timeout for non-standard vehicles
- support for new 1.000ms timebase on MQ175
- added ability to manually tweak null adjustment value for Yaw Rate to account for drift

Chart
-----
- corrected BIFF5 maximum row count problem when exporting to .XLS (now 16000 rows before wraparound)
- fixed certain errors with misplaced GPS crosshairs
- fixed problem exporting negative numbers
- NOTE: as before, opening an .XLS file by double-clicking on it in File Explorer on
a PC may not cleanly open the file (cell formatting can be messy); instead, open Excel first and then
drag and drop the file into Excel
- fixed plot-by-distance synchronization errors due to quantization



MaxQData MQ175 DAQ Software 1.7f
Release Notes
Release date: June 8, 2004


General
-------
- support for "$GPRGH" message
- removed less commonly used sensors for clarity


MaxQData MQ175 DAQ Software 1.7e
Release Notes
Release date: April 7, 2004


General
-------
- support for MQ175


MaxQData MQ25/MQ75/MQ100/MQ125 DAQ Software 1.7d
Release Notes
Release date: March 10, 2004


General
-------
- removed registration code
- MQDebugLog files now go into \My Documents
- miscellaneous changes



MaxQData MQ25/MQ75/MQ100/MQ125 DAQ Software 1.7c
Release Notes
Release date: February 24, 2004


Setup
-----
- advanced settings for COM port, OBD2 debug logging, ISO14230
- Use "ISO is 14230" switch in Setup under Advanced Settings to enable ISO 14230 support (disables ISO9141-2 support)
- fixed problem with setting GPS baud rate


Flight
------
- flight recording trigger now starts on >, not >=, and stops on <, not <=
- fixed problem with setting sample rate
- improved restart/reinitialize performance when cable disconnected or power cycled
- added OBD2 sensor driver for "Calculated Load Value"
- fixed problem where flight recording trigger on LongG stops immediately after starting



MaxQData MQ25/MQ75/MQ100/MQ125 DAQ Software 1.7b
Release Notes
Release date:  December 3, 2003


General
-------
- support added for MQ25 and MQ125-Multi to speak ISO 14230 (Keyword 2000)
- Use "ISO is 14230" switch in Setup under Advanced Settings to enable ISO 14230 support (disables ISO9141-2 support)
- fixed miscellaneous problems for backward compatibility with MQ-100


Flight
------
- improved power cycle recovery
- added sensor driver for OBD2 Calculated Load Value




MaxQData MQ25/MQ75/MQ100/MQ125 DAQ Software 1.7a
Release Notes
Release date:  September 26, 2003


General
-------
- Fixed: Pocket PC 2003 compatibility issues; PPC2K3-specific install is recommended
- MQ125 firmware now includes "GPS passthrough mode", allowing the Pocket PC to be used with GPS navigation software while the MQ125 is installed.  When the MQ125 is not being used, GPS data sent from a GPS module connected to the MQ125 is passed through to the Pocket PC.  The baud rate going into the Pocket PC is 38400 baud.  The baud rate for the GPS module is whatever it was the last time the MQ125 was used, unless power to the MQ125 is dropped, in which case the baud rate defaults to 4800 baud on power up.


gCal
----
- gCal is no longer needed for the MQ75/MQ125 as they are calibrated at the factory.  A separate calibration file is provided with each unit.


Flight
------
- New feature: Flight for MQ125 can now take input from a GPS unit connected directly to the Pocket PC, e.g. a Bluetooth GPS module.
- Change: smaller flight recording files (see Setup below)
- Change: preopened temporary file is now named "~FlightTempxxxxxxxx.mqd".  This avoids confusion when copying files or opening flight recordings while Flight is running.
- Change: Flight Recording Trigger Start trigger is now when Speed > Trigger (before it was Speed >= Trigger), and Stop trigger is Speed < Trigger (not Speed <= Trigger)
- Change: Flight monitors remaining space where the flight recording is being stored; when available free space drops below about 256K, new data is not logged to the file
- Change: better handling of timestamping during loss of power
- Fixed: Sample Rate may not be changeable from 10Hz
- Known issue: After changing the list of selected parameters, OBD2 values may not update.  Workaround: Exit and restart Flight.


Chart
-----
- Fixed: not always exporting to the selected file type.
- New feature: export beacon positions


Codes
-----
- Fixed: not recognizing serial number format for MQ75/MQ125 and thus not connecting


Setup
-----
- New feature: User can now specify a COM port for a directly-connected GPS module, or leave blank for a GPS module connected through the MQ module.
- New feature: Advanced settings allow reduction in file size by eliminating excessive data (Type 1 records only, blank duplicate values)
- New debugging feature: Advanced setting to log OBD-II traffic (not recommended for normal use)
- Change: User can now input the MQ COM port as a text string, supporting any available COM port.
- Change: GPS baud rates of 4800, 9600, 19200, and 38400 are now supported for MQ-connected GPS; for direct-connect GPS, all these plus 57600 and 115200


Miscellaneous
-------------
- New feature: MQ75/MQ125 have temperature-compensated yaw rate sensor
- New feature: MQ75/MQ125 accelerometer driver allows for calibratable roll and pitch compensation
- New feature: MQ75/MQ125 accelerometer and yaw rate sensor are temperature-compensated





MaxQData MQ050/MQ100 DAQ Pack 1.6
Release Notes
Release date: May 12, 2003


Codes
-----
- Fixed: New install doesn't install incorrect CPU build on StrongARM Pocket PCs.


gCal
----
- Fixed: gCal now attempts to talk to the MQ module based on the COM port setting in MQSetup rather than assuming COM1:.


Flight
------
- New feature: There are now two numeric summary screens in addition to the six plot screens.  The three "A" plot screens (Bar graph A, Strip chart A, X vs. Y A) are summarized on the first numeric summary screen, and the three "B" plot screens are summarized on the second numeric summary screen.
- Change: the numeric "current value" is now more filtered and updated a bit more slowly to make it easier to read.
- Fixed: problem where occasionally Flight did not connect with the MQ module. 


Chart
-----
- New feature: the g-g plot now shows a dotted outline of the friction circle, cumulative across the entire file.
- Fixed: problem where unloading the second file after loading two bombs Chart.
- Fixed: problem in desktop Chart where GPS map wasn't always shown on initial file load.
- Fixed: problem where full GPS track map would not draw under W98.
- Fixed: problem where sometimes it became impossible to load two flight recordings at once.
- Fixed: "Set tA" and "Set tB" now enable the tA and tB markers.


Setup
-----
- Change: Registration key now required to avoid pop-up message when creating a flight recording.  All MQ050/MQ100 customers can receive a free registration key by contacting Info@MaxQData.com
- Change: While there are new menu selections to set the GPS baud rate, they have no effect on an MQ100 system.  The MQ100 still only supports GPS at 4800 baud.  The higher baud rates only apply to the MQ125.
- Change: Firmware version is now reported slightly differently.


Miscellaneous
-------------
- New feature: new MQ100 User's Manual in Adobe Acrobat format is available (but due to size is not included with the web-base install).
- New feature: "GPS Distance", "GPS Road power", and "GPS LongG" drivers
- New feature: GPS Latitude, Longitude, and Altitude measurements that don't have sufficiently low HDOP, or enough satellites, or a proper GPS fix are now ignored (the previous good value is substituted), which avoids GPS maps that veer suddenly.
- New feature: "OBD2 Distance", "OBD2 Road power", and "OBD2 LongG" drivers
- Change: Timeslip generation will now generate an error page if the right sensor values aren't available.




MaxQData MQ050/MQ100 DAQ Pack 1.5
Release Notes
Release date: August 2, 2002


Codes
-----
- This time for sure Codes launches successfully on all Pocket PCs.


Flight
------
- Fixed: bug causing Flight to hang after ~45 minutes of running if a strip chart or X-Y display was being continuously displayed.



Release date: July 28, 2002

Note: Please uninstall any earlier version from both the Pocket PC and the desktop before installing this software.  You may wish to create a backup calibration file in Setup on the Pocket PC first so you can reload it after installing the new software.


Codes
-----
- Codes now launches successfully on all Pocket PCs.


Timeslip generation
-------------------
- New feature: Added plot of entire run vs. time
- New feature: Added table of 0-5, 5-10, 10-15 time deltas; this assists in picking optimal shift points
- New feature: Now supports rolling starts so you can do single-gear measurements (e.g. dyno pulls).  Rolling starts do not generate 1/4 mile time-to-distance and speed-at-distance values.
- Distances are now reported in feet, not yards.
- Various cosmetic changes have been made, including changing vertical axis scaling on the graphic plots
- For the tab-delimited text file, a short report of the sensors used is appended.

                                               
Chart
-----
- .MQD files are now associated with the Shell.  This may not become apparent until the next system reboot.
- The first file loaded is automatically selected into both the A) and B) sides, and the full GPS map is enabled.
- Minor cosmetic changes


Flight
------
- The flight recording prebuffer has been eliminated.  Previously, a rolling record of 30-90 seconds (depending on sample rate) was maintained and was written to disk at the beginning of each flight recording.  This allowed the user to view the data that was collected shortly before the flight recording was begun.  However, this caused problems in generating timeslips, as it was difficult to tell where the "true" beginning of the run was.  Also, this prebuffer was a non-intuitive feature that was confusing new users.  With this new release, flight recording files do not contain data recorded before the trigger (manaul or automatic).
- Fixed bug where Flight would jump to Pocket Internet Explorer at the end of a run if "Display Timeslip" was selected but "Generate Timeslip" was not.


Sensors
-------
- "Time since last here (GPS)" has been fixed.  This sensor gives you "continuous lap time" based solely on GPS.  Testing has shown accuracy comparable to a stopwatch to a tenth of a second precision.  The value represents how long it has been since one lap ago at the current track position, therefore you don't have to wait until the end of a lap to see if you've gained or lost time.  Because no two laps are exactly the same, this value will wander slightly as the car goes around the course.  Drivers who wish to watch this value while driving are advised to look at it only once or twice per lap, and always at the same point on the track (thus simulating a "beacon lap time"), until they become familiar with how it works.  As with all GPS-based values, accuracy will vary depending on whether or not there is a clear view of the sky and on the degradation of the GPS signal due to atmospheric conditions or Selective Availability.
- "GPS Vehicle speed" would drop to zero or a low value every sixty seconds, while Seconds Past Midnight would increase rapidly.  Also, "GPS Vehicle speed" worked erratically, depending on the time of day.  These issues have been fixed.
- Because of the new Timeslip feature, the 0-60MPH, 60' time, Eighth mile time, and Quarter mile time sensors were deemed redundant and have been eliminated.
- The "RPM (injector)" sensor would sometimes drop to zero or a low value and stay there, usually during a fast shift.  This has been fixed, but the user will still have to interpret this value.  Injectors will shut off frequently during normal operation (usually at lift throttle to save fuel), or they will open only for a partial cycle (on tip-in), causing momentary sharp spikes or dips in the computed RPM value.


Information and Known Issues
----------------------------
- 0% and 100% duty cycle are not always properly recognized for the P0-P5 inputs.  When measuring the duty cycle of a signal, make sure the signal switches at least once every 0.25 seconds.
- Users are advised that, occasionally, GPS values reported by the GPS receiver may become erratic due to not having a clear view of the sky or for some other reason.  This can show up in Chart as straight-line movement over several seconds, or no movement.  Always ensure that your GPS unit has a clear view of the sky for best results.  Ideally, your GPS receiver should be mounted externally on the roof or rear deck lid for best reception.  If an interior mounting point is used (e.g. dashboard), make sure the receiver sees as much of the sky as possible.
- Users of the Garmin eTrex handheld GPS units may find that GPS values are not sent to the MaxQData system when the eTrex is switched on, even though RS-232 output has been enabled, until the RS-232 cable is unplugged from the eTrex and plugged back in.  So long as the eTrex stays on, this problem does not appear to recur.  Always check "GPS Seconds past midnight" and/or "GPS Satellite count" to make sure that the GPS is working before going out on the track.
- Note that there may be discrepancies between RPM as reported through the MaxQData system and the OEM tachometer.  In practice, it has been found that the RPM measurements from the MaxQData system can often be more accurate than the OEM tach.  If an error is suspected, a good reference is OBD2 RPM, which is the best indicator of what the ECU thinks engine speed really is.  If there is an error in the OEM tach, it is likely that the tach will read differently than OBD2 RPM.






MaxQData MQ050/MQ100 DAQ Pack 1.5
Release Notes
Release date: July 11, 2002

Note: Please uninstall any earlier version from both the Pocket PC and the desktop before installing this software.  You may wish to create a backup calibration file in Setup on the Pocket PC first so you can reload it after installing the new software.


Codes
-----
- Codes is a new application that reads and clears codes from OBD-II vehicles.
- Reading codes: Diagnostic Trouble Codes are reported by number, e.g. "P0100".  There is a file named "Codes.txt" in the \Program Files\MaxQData directory which contains text explanations of all of the standard codes.  The Codes application will look up each code by number in this file and show the associated explanation.  There are many manufacturer-specific codes in addition to the standard codes.  If you get a manufacturer-specific code, the Codes application will report it by number but will not find an explanation in "Codes.txt".  You may find these manufacturer-specific codes documented on the Web.  You can edit the "Codes.txt" file yourself using Pocket Word or a text editor to add explanations for manufacturer-specific trouble codes for your specific vehicle.
- Clearing codes:  This is achieved by the standard OBD-II "Clear all codes" mode command.  There is no ability to clear individual codes.


Chart
-----
- New feature: Export to Timeslip.  See the notes below on "Flight" for information on Timeslips.
- New black background color scheme and revised greyscale color schemes.
- Fixed plot-by-distance so that the plot traces are now aligned correctly.  Note: while plot-by-distance does indeed plot according to distance, your distance sensor (usually derived from a speed sensor) may not be an accurate way to measure distance traveled.  This is often due to tire slip.
- Fixed problem so information for field three under data file "A" now shows up.


Flight
------
- New feature: Timeslip generation.  This is enabled under "Log" on the main menu.  Timeslip generation is useful for doing straight-line acceleration runs.  When enabled, a timeslip is automatically generated each time a flight recording is created.  The timeslip contains information like 0-60 time, 60 ft and 1/4 mile time, plus a detailed graph of the first few seconds of the run for analyzing launch technique.  If you enable "Display Timeslip", this information will automatically be displayed in Pocket Internet Explorer at the end of your run, with links to previous runs and to data files.  The timeslip graphic is a single ".PNG" file (similar to .GIF, but in a non-proprietary format) which can be emailed and posted to discussion lists.  You also get an HTML file that can be placed on a website.  In addition both tab-delimited text and Excel files are generated.    If you do not automatically generate timeslips from Flight, you can still use the "Export to Timeslip" feature in Chart after the fact.
This feature works by reading the data file for the top recorded speed, then working backward to either the beginning of the file or zero speed, whichever comes first.  Thus, you do not have to do standing starts to use the Timeslip feature, and you don't have to worry about confusing it with burnouts or moving the car into position.
The timeslip values are computed on the basis of the speed sensor in use.  Note that there can be surprising delays between when the car physically starts accelerating and when speed changes from 0 MPH.  The most accurate measurements would be when starting from a standstill and using Internal LongG as the basis for Speed; however, this is not always practical and is subject to error from the slope of the road.  The next best is TransSpeed, followed by OBD2, followed by GPS.  This is usually only an issue with standing starts.  The data is still very useful, especially for comparisons on the same road, but may not agree exactly with measurements taken at a drag strip.  
- New feature: "No Data" is displayed on the screen if the connection to the MQ050/MQ100 is broken.  Flight continues automatically when reconnected.
- Improved: the visual delay before a flight recording begins has been shortened.
- The Road Power computation has been greatly improved.  It is recommended that the "LongG" sensor be configured to "Internal LongG".  Using OBD-II as the basis for LongG does not work well due to the slow rate at which OBD-II data comes in and other issues.  Note that the slope of the road makes a big difference in the computation.  This sensor is best used for comparing different runs on the same road.  Also, the "Mass" calibration point for "Road Power" was incorrectly converting pounds to kilograms behind the scenes.  This has been fixed.
- Fixed problem where the first few values in a flight recording for GPS and several other sensors were off by a factor of two or were illogical.  This caused GPS track maps to look wrong in some cases.
- Fixed problem where some GPS receivers (e.g. Garmin eTrex) were not understood due to differences in their NMEA-0183 output format.
- GPS values are no longer zeroed when HDOP exceeds an arbitrary limit.
- Some slower Pocket PCs (e.g. Aero 1550) had a difficult time bringing up the flight recording ready screen.  This has been improved.
- When reading OBD-II information, if a sensor value was configured that was not actually supported by the car, there would be long timeout delays while Flight retried the value.  This greatly reduced the sample rate over OBD-II in this condition.  Now it skips on to the next value to read immediately.  You still don't want to bother flight recording sensor values that are not supported by OBD-II on your car.
- Fixed problem where Flight stopped displaying data immediately after the sampling rate was changed.
- The computation of LongG from TransSpeed is now improved.
- Known issue: it's not possible to sample at 60Hz with GPS sensors enabled.  The MQ100 will lock up due to an internal buffer overrun and require a power cycle to come back to life.  A fix is planned that will require a field upgrade to the firmware inside the MQ050/MQ100.  Also, some slower Pocket PCs may not be able to sample at the higher sample rates when many sensors are enabled.


Setup
-----
- Sensor list now sorted by name.
- Pulse inputs now labeled "P0", etc. instead of "IC0".
- Fixed problem where some sensor calibration points would not accept "0" as a valid calibration value.


MQSensorInternal
----------------
- New MAP sensor driver allows for direct reading of MAP sensors with 0-5V output.
- New TPS (Throttle Position Sensor) driver allows for direct reading of TPS sensors with 0-5V output.
- Fixed problem where "quarter mile %" was off by a factor of 100.


MQSensorInjector
----------------
- fixed problem in Injector Pulse Width computation





MaxQData MQ050/MQ100 DAQ Pack 1.0
Release Notes
Release date: May 6, 2002


Note: Please uninstall any earlier version from both the Pocket PC and the desktop before installing this software.


Chart
-----
- New feature: Chart now comes in two versions, one for the Pocket PC and one for desktops/laptops running W95/W98/WME/WNT/W2K/WXP.  The desktop version has the same functionality as the Pocket PC version, but it uses a somewhat different, larger user interface that is also resizable.
- New feature: Export a flight recording to .XLS (Microsoft Excel 5.0/95 workbook), .CSV, and .TXT files.  To use, first load a flight recording (flight recording files end with ".MQD"), then choose "Export..." from the "File" menu.  Note: the .XLS option takes longer and uses more memory.  The .CSV export option is normally recommended, since Microsoft Excel can import .CSV files directly.  However, .XLS is useful when exporting files that can be immediately viewed in Microsoft Pocket Excel on the Pocket PC (Microsoft Pocket Excel for the Pocket PC cannot import .CSV or .TXT files).  The resultant file is placed in the same folder as the original .MQD file.  The exported file is a time-ordered table of sensor values.  At this time, a separate table of beacon times is not exported.  However, if you are using a real beacon system (as opposed to manually adding beacons based on GPS position), you can still see the beacon time sensor value in the table.
- New feature: when no files are selected into the display, the first file selected (in either the A or B section) is automatically loaded into both sections.
- The color scheme has been totally revamped for better outdoor visibility and better discrimination between sensor values when more than one is displayed at a time.
- Fixed problems where occasionally the track map doesn't get redrawn when it should.
- Time marker "tB" now shows up on the screen when enabled.
- The time interval display, which showed either "t-t1=" or "t-t2=", now displays "t-tA=" or "t-tB=" to be consistent with the naming of the "A" and "B" file slots.
- File slots A and B are now noted with the prefix "A) " or "B) " before the filename.
- Known issue: Chart on the Pocket PC does not display the "degrees" sign correctly for Latitude, Longitude, and Spark Advance.  Also, the "degrees" sign is exported as a question mark.  This is under investigation.  This problem has not been observed in the version of Chart for the desktop.


Flight
------
- New colors for the "B" gauge sets.
- Gauge timespan = 20s now works correctly instead of only showing half a screen of data.
- Known issue: 60Hz sampling may not work with GPS and/or OBD2 sensors enabled.  This is under investigation.


MQSensorInternal
----------------
- "Raw ICx" channels are now called "Px" to be consistent with external box markings (e.g. "Raw IC0 period" is now "P0 period").
- "Raw ADx" channels are now called "Ax" to be consistent with external box markings (e.g. "Raw AD0 voltage" is now "A0 voltage").
- "Px duty cycle" (formerly "ICx duty cycle") now have a an "InvertFlag" calibration which inverts the reported duty
cycle when set to "1" (100% becomes 0%, 0% becomes 100%).


MQSensorGPS
-----------
- Implemented a fix for the condition where sometimes GPS initial position (Latitude, Longitude, and Altitude) are way off the map.
- Known issue: The "GPS Time since last here" sensor has been observed not working.  If you wish to use this sensor, make sure you are also logging every other sensor beginning with "GPS".  This is under investigation.  Also, this sensor is still a bit of an experiment; please interpret its values with caution while we make improvements.


Build numbers
-------------
MQChart.exe:        1530
MQgCal.exe:         1095
MQFlight.exe:       1134
MQSetup.exe:        1098
MQBiff.dll:         1095
MQLogFile.dll:      1258
MQComm.dll:         1192
MQSensorBeacon:     1097
MQSensorGPS:        1093
MQSensorInjector:   1113
MQSensorInternal:   1144
MQSensorOBD2:       1095
MQSensorTransSpeed: 1099




MaxQData MQ050/MQ100 DAQ Pack 1.0
Release Notes
Release date: April 15, 2002


Flight (build 1129)
------
- Added Log menu option for turning off screen tap to begin flight recording
- Added Log menu option for getting to the flight recording ready screen


MQSensorInjector
----------------
- Fixed bug that disallowed channel 0


MQSensorInternal
----------------
- Fixed bugs that interfered with changes to LongGSignalSource, RPMSignalSource, RPM (IC) Signal Source, SpeedSignalSource
- Fixed bug that bombed Flight when logging LongG and some other sensors
- Adjusted filter on TransSpeed for better performance


MQSensorOBD2
------------
- Fixed bug where LongG could not be derived from OBD2 Vehicle Speed