Release 1.772

Release 1.772

Code added to ensure that the QA350 application cannot reflash a QA351 device.

Release 1.771

Still tracking down the reflash issue. This version checks version immediately upon connection and then prohibits further interaction with the device until the flash version is corrected via reflash.

DO NOT TRY TO FLASH A QA351 with QA350 software or you may brick the device!

Release 1.77

Release 1.77
Tracking down issue with re-flash of device. This release has changes to USB timing when entering bootloader. If you aren't having problems, there's not reason to upgrade to this version.

Release 1.76

1.76 (May 2019)

• Added QA350 CPU temp display in status bar and also in logging. Temp accuracy will bounce around +/- 1 degree. You should see the temp rise inside the QA350 about 1-2 degrees over ambient.
• Firmware version must match release, otherwise a reminder is shown at launch
• This requires FW release 12. When you run the 1.76 release, you'll see a messaging indicated the FW doesn't match. To update, pick Tools->Update Flash from the menu and selection the image named QA350.boot when prompted. After flashing, re-start app and re-plug QA350. You should see the new FW version indicated as '12' in the lower left.

Below is screen capture of measured voltage over time (813 seconds). Image 1 (external 10V reference) is showing well under +/-10 PPM and Image 2 (internal 2.5V reference) is showing about +/- 1 PPM stability. Verify you are also measuring this level of stability on your QA350 and contact us if not. In particular, notice the standard deviation reported for both--these are expected values and represent about +/- 1 LSb of noise from the converter. Make sure you don't have a phone nearby when doing these measurements as phone transmission can move the reading a few PPM.

Release 1.75

1.75 (May 2019)

• Fixed bug where axis settings wasn't persisting correctly
• Added ability to log at arbitrary intervals. This was for user DM, who needs the ability to log for days at a time
• NOTE: There is a voltage offset of ~20 uV present when switching between fast and slow modes, and the cause hasn't yet been determined. The solution here is to restart the application if you want to revert to slow sampling after fast sampling.

Release 1.721

1.721 (Oct 2018)

• Fixed bug where there were problems with cal data being used before it was created
• Added a 'secret' key sequence that would allow you to enter factory mode so that virgin devices could be flashed from retail builds
• Added status update on flash progress. This will appear in the lower left on the status bar

RMS added

[The firmware for this release is the default firmware shipping in new QA350. If you ordered your QA350 the week of July 30th or after, then your QA350 was shipped with firmware release 11 and needs release 1.7_Preview to run. If you encounter issues, let us know and we'll help you roll back to a prior release.]

This release builds on the fast logging (1 KHz) release as they are intertwined somewhat. The RMS mode uses a 15 KHz sample rate, and computes true RMS by integrating over 16384 samples, giving an update rate of just over 1 Hz. The math is all 64 bit.

On the ADS1256, the 15 KHz sample rate should yield a 4807 Hz 3 dB bandwidth (see table 12 in spec).

The ADS1256 input impedance changes quite a bit based on sample rate. The QA350 was never intended to do AC/true RMS measurements, but as we've become more familiar with the hardware abilities, true RMS is just too good to pass up. This does require a fudge-factor to account for the lowered input impedance. We don't know the full unit-to-unit variation yet on this. As a first test, the 2.5V reference should read precisely 2.500000 in slow DC mode. But might measure a bit higher or lower in RMS mode, depending on the unit. Long term we'll add a means to calibrate this out.

On the hardware, the input Z should measure about 0.996 Mohms in DC mode, and will drop to about 0.971 Mohms in RMS mode. This is due to the input Z of the ADS1256 dropping at the higher sample rate. This is just under a 3% change.

Release 1.701 was released just after 1.700 to correct an exception on startup that occurred if the QA350 wasn't connected.

Release 1.702 adds text logging (1.701 offered only binary)

1.60 Alpha

ALERT! This release isn't for production use! This release is for developers working on fast logging. For general release, see release 1.5 below.

This is first-checkin of code with fast logging to disk. 1Ksps verified in release mode without any drops. This release (and future releases) will require a hardware modification to work.

If you are able to solder, you can easily make the modification yourself. First you need to remove the top lid from the QA350. This requires you to remove the top two hex head screws on the front panel. Notice the front panel has 4 head head screws at located at the corners. The upper left and upper right can be unscrewed with a 2 mm hex bit.

After removing the two front-panel screws, then using a small Philips screwdriver remove the 6 flat-head screws on the left side of the case, and then the 6 flat head screws on the right side of the case. The top case should lift off at that point. When you re-assemble, be gentle and make sure the screw is perpendicular to the case as its easy for the tiny screws to strip out the threads on the case if you turn too hard or if they feed in crooked.

On the P3 PCB (most recent), there is a header marked J204 on the left side of the board. Pin 1 is marked with a round solder pad, while the other pins have square solder pads. The pad numbering is as follows:

1 2
3 4
5 6
7 8
<etc>

Pins 5 and 6 need to be shorted together with a small drop of solder or other means. In the picture below, you can see the numbering for pin 1 (round pad) and 2, and also 5 and 6. What is shown is a 0 ohm resistor jumper from pin 5 to pin 6. You can also use a short length of wire. In the picture there is a blob of solder on pin 3. That isn't needed and was just the byproduct of messy work.

Once pins 5 and 6 are connected, double check your work and then close-up the QA350.

You will need to update your QA350 flash when running for the first time. This release requires firmware version 10 or later. If you try this release and update your firmware to version 10 or later, then you will need to downgrade your firmware back to version 6 when running 1.50.

1.50

This release is for production use. If you have experimented with Release 1.6, then you will need to downgrade your firmware. This release requires firmware version 6.

• Updated version to fix issue with tag on last release.
• Enabled the ability to re-flash MSP430 code.
• Minor changes and bugfixes.

Release 1.4

General cleanup, fixed bug related to REL offset.