Skip to main content

Module rdas

Module rdas 

Source
Expand description

AED Electronics’ R-DAS flight computer’s raw data, as its Windows software exports a flight to text: a *** Configuration *** section, then *** Raw data *** and a table of the converters’ counts.

The R-DAS records its accelerometer and its barometer, and as its owner chooses its four digital inputs and six analog inputs from an expansion port, each through a 10-bit converter over 0 to 5 V, at up to 200 samples a second (R-DAS User Manual, V1.5, AED Electronics, 2001, p. 7, p. 14). It keeps the 2 s before liftoff and stores from there (p. 6). Its Windows software exports a downloaded flight as text, either raw or converted with the calibration values set in the software; the raw file’s header “contains a summary of the measurement configuration”, and its values are “measured ADC-values”, each step 5 V / 1,024 = 4.883 mV, for the reader to convert with the calibration values (p. 14). The manual shows no file and names no column. The sample logs hold the raw export only, 54 files from a college course’s flights in 2008: 28 recorded on board at 200 Hz, and 26 at 10 Hz, by their names the course’s telemetry records of the same flights, in the same layout but for a configuration whose Trigger: line is blank and which names no firmware.

Recognition. The first line that isn’t blank is *** Configuration ***, and a line *** Raw data *** comes within the file’s first 200 lines; no other layout HPR Sim reads opens so.

The configuration. Two of its lines are needed, and a file without either is refused (LogError::Unit): Data is sampled at N Hz., which the clock is checked against, and Inputs that were sampled: …, which says what the table’s columns hold: Acceleration is Acc, Pressure is Prs, the digital inputs is Dig, and ADC0 to ADC5 are themselves. The table’s header, after Time, must name those columns in that order, and a list naming an input the reader doesn’t know, or one twice, is refused (LogError::Syntax). A line holding with firmware version N gives FlightLog::firmware, the last if several do. Every line of the configuration that isn’t blank, its trigger and recovery settings among them, is kept in a note as written, at most 40 lines of 200 characters.

Columns. The file states no calibration, and the manual leaves the conversions to values set in the software, which the file doesn’t hold, so no column is converted:

ColumnQuantityAs read
Timethe clock, sfrom liftoff: checked against the stated rate (below)
Acc, Prs, ADC0 … ADC5Quantity::Unrecognizedthe converter’s counts, whole numbers 0 to 1,023, as written
DigQuantity::Numbera hexadecimal word, kept as its number

Acc is the accelerometer, an Analog Devices ADXL150 for ±50 g, and Prs the barometer, a Motorola MPXS4100A for 20 to 105 kPa, in the manual’s R-DAS (p. 7); but the file states neither the calibration values nor which board and sensors wrote it, and others have been fitted to the R-DAS (a college course’s pressure lab names an MPXH6115A on its R-DAS: E80 Pressure and Temperature Lab, Harvey Mudd College, https://pages.hmc.edu/spjut/NewE80/PresTempLab.html, section 2), so the counts aren’t taken through that sensor’s data sheet. The manual says the digital byte holds the four digital inputs and, in its other four bits, the flight’s phase: before liftoff, flight, drogue and main (p. 14), and, of firmware 2.2, that “bit 3 is set when timed recovery was used” (p. 22); it gives no other bit. The files write a word of four hexadecimal digits, not a byte, and never set bit 3 of either byte: they set 0x80 and 0x8000. In 27 of the 28 on-board sample files the word reads 0000 from the first row, 0010 from within 0.25 s after the zero, then 0020, 0030 and, near the file’s end, 8030; the 28th writes 00B0 and 80B0 in place of the last two. The low byte’s high bits look like the phases in order, but that rests on the files, not a document, so the word is kept as written and no event is taken from it.

The clock. Time counts from liftoff, t = 0 in the manual’s figure 2.2, the g-switch, 2.5 g held for 0.25 s, firing at 0.25 s (p. 10, p. 11): every sample file’s first row is at −2.000, the 2 s before liftoff the manual says it keeps. That it counts seconds rests on the stated rate: the clock’s average step, from the first row to the last, must be the stated rate’s interval within 1%, or the file is refused (LogError::Unit); a note gives both. In every sample file the step is the interval exactly, 0.005 s at 200 Hz and 0.1 s at 10 Hz. A step under half the interval or over one and a half of it is counted in the note.

The primary track. The file holds counts and no altitude, so FlightLog::time_s and FlightLog::altitude_m are empty, as for the Raven’s raw .FIPa, and every column is a channel on the file’s clock.

Cells. Every row must hold as many cells as the header names, its Time a number greater than the row before’s, and every count that is a number a whole one from 0 to 1,023, which keeps a file of converted values from passing for counts; otherwise the file is refused, naming the line. Any other cell that isn’t a number, or for Dig a word of hexadecimal digits, is a gap (NaN), counted in a note. Lines may end in LF or CR LF; a file whose lines end in a lone CR isn’t recognized.

An invented file, in the layout the sample files share:

*** Configuration ***

Trigger: G-switch.
Data is sampled at 200 Hz.
Inputs that were sampled: Acceleration, Pressure, the digital inputs, ADC0, ADC1.

This data was generated with version 4.1 of the RDAS windows software,
and downloaded from an RDAS board with firmware version 4.1


*** Raw data ***

   Time  Acc  Prs  Dig ADC0 ADC1
 -2.000  510  800 0000  500  250
 -1.995  511  800 0000  501  250

Constants§

ALTITUDE_STEP_M
The barometer’s step, as the format’s resolution (LogFormat::altitude_resolution_m): the file writes no altitude, but its pressure moves by the barometer’s count, 0.09 kPa in the manual’s R-DAS (p. 7), 7.5 m near sea level (Δh = Δp / (ρ₀ g₀), as LogFormat::altitude_resolution_m takes it). A board with another sensor steps otherwise.

Functions§

read
Reads a log in this layout.
recognizes
Whether a file’s text is in this layout: its first line that isn’t blank is *** Configuration ***, and a *** Raw data *** line comes within its first 200 lines.