Skip to main content

Module rrc3_rff

Module rrc3_rff 

Source
Expand description

Missile Works’ RRC3 raw flight files, .rff: what its mDACS software saves when it downloads a flight from the altimeter, before any export.

The RRC3 records its pressure at 20 Hz, and its temperature and battery voltage at 1 Hz (RRC3+ / RRC3 User Manual v1.71, p. 23). mDACS keeps the download as a .NET BinaryFormatter stream, the layout Microsoft publishes as MS-NRBF ([MS-NRBF]: .NET Remoting: Binary Format Data Structure, revision 13.0, 2024-11-19): a serialized mDACS.AnalysisSupport+FlightRecord whose flight data is a List<Int16>, the altimeter’s memory as it came off the board, one 16-bit word a slot. The stream has no columns and no times:

  • a word below 0x4000 is a pressure, in tenths of a millibar (10 Pa): 0x4000 is 1,638.4 mbar, above the 1,200 mbar at which the RRC3 itself reports a pressure sensor fault (p. 9), so no reading reaches it;
  • a word at or above 0x4000 is an auxiliary word, written in pairs once a second, presumably the temperature and battery voltage the manual names, in counts: Debrief found mDACS’s export’s temperature and voltage tracking them, though not linearly. The file holds no calibration for them, and they are kept as written (Quantity::Unrecognized), in the order the file writes them. A few stand alone, not in a pair (in each sample file, three: one near apogee, one later, and a last 0xFFFF); the first two fall where the manual’s low-voltage samples taken as the drogue and the main fire would (p. 23), but that is a guess, and they are kept as written in a channel of their own. Three or more auxiliary words in a row, which no sample file holds, are read as pairs from the first, with an odd last one kept alone;
  • the readings start at the first word, among the first eight, that a pressure on a launch pad can be, at least 500 mbar (5,570 m in the standard atmosphere, above any launch site): the words before it are kept, as written, in a note;
  • a zero word ends the log: the list’s slots after it are unwritten.

Times. The stream has none, so the pressure’s clock is the RRC3’s 20 Hz, from the manual, the nth reading at n / 20 s, and the auxiliary pairs’ times are the time of the reading before them. Two checks stand behind it: the pairs, one a second, must count the same seconds as the readings do at 20 a second, within 10% and two pairs, or the file is refused; and wherever the project’s sample logs hold mDACS’s export of the same flight, its pressures match the raw readings one for one, and its Time column is this 20 Hz clock as mDACS keeps it: 0.05 s summed in single precision, so that it runs a hundredth of a second ahead late in a long log (cargo xtask logs counts the pairs and compares them).

The record. One Quantity::Pressure channel, Pressure, and the three auxiliary channels. The primary track is empty, with a note: the file holds no altitude, and working one out of the pressure is a reading, not this reader’s to make (milestone M7.2, the readings, takes it), as mDACS’s export’s Altitude is mDACS’s.

Refused, naming the byte: a stream with no List<Int16> of the flight record’s, or more than one candidate for it; a list whose slots run past the file’s end; readings that don’t start among the first eight words; a word other than a zero after the zero that ends the log; fewer than two seconds of readings; and a clock check that fails.

Where this comes from. The layout, the 0x4000 threshold, the 500 mbar floor, the preamble’s length and the clock check follow the reader in Debrief (lib/parsers/missileworksRff.ts, MIT, the project owner’s own; see THIRD-PARTY-NOTICES.md), which was worked out from a raw file and mDACS’s export of the same flight; the record types and their fields are MS-NRBF’s (§2.4.3.3 ArraySinglePrimitive, §2.5.3 MemberReference, §2.6.1 SerializationHeaderRecord). Where this reader departs from Debrief’s: it keeps the auxiliary words, paired and single, and the preamble where Debrief drops them; it refuses a stream with two candidate lists where Debrief takes the longer; and it refuses data after the zero that ends the log where Debrief stops reading.

Functions§

read
Reads an RRC3 .rff file.