Table of Contents

A/D Converter

Problem

During the November 22, 2011 and December 21, 2011 spike many of the A/D measurements had spikes in the data, for example, the Nevzorov measurements on December 21, 2011.

Above shows the spikes in the data

Cause

During December 27, 2011 ground testing, moving the wires on the A/D board did cause jumps in the Attack and Side Slip pressure measurements (first two measured channels). Hence, the tips are a problem for these measurements. Look at the wires, you can see how they been partly broken where the tips connect.

Solution

Removing the tips and going directly into the A/D for all connections.

Problem

When getting the A/D back from the Sikorsky project in September 2005, the A/D board was not working.

Cause

SEAADC had a few pins busted on the high speed analog board.

Solution

Sent the borad to SEA in April of 2008.

The SEAADC had a few pins busted on the high speed analog board and some other pins needed replacement.

The SEAADC was calibrated. The calibration certificate is in the box with the SEAADC.

Problem

On board #1 channel #20 (starting with 0) gave incorrect voltage reading on the M200 display compared to a volt meter. On board #1 channel #4 (starting with 0) would result in spikes so the pitot static wing measurement was moved to channel #0 during MPACE (Fall 2004) which result in no spikes or problems with the measurement

Cause

Something is wrong with some of the channels on the Analog to Digital Converter.

Solution

Board #1 was sent to SEA, Inc. for calibration in June 2005. At this time the board #2 was replaced with a new Analog to Digital Converter box since the one that was being used since August 2004 was only on temporal until a new box could be built.

Problem

Several of the channels were not working on the recently calibrated board #1. These channels were the same channels that did not work on board #2.

Cause

One of the channels was incorrectly reffering to another channel's formula in the fml.300 table

The rest of the channels were incorrectly labeled in the buf.300 table.

Solution

Change the formula for the one channel to the correct formula.

Change the names of the channels in the buff.300 table to match the names in the acq.300 table.