Skip to content
Saharsh Engineering Log
Back to projects

CubeSat VLF Lightning Wave Receiver — Rev A

I designed the first electronics revision of a CubeSat receiver intended to detect very-low-frequency electromagnetic signals produced by lightning. Rev A combines a search-coil input, analog amplification and filtering, 12-bit digitisation, event-processing electronics, power and protection, and ground-development interfaces. Reviewing the design made the harder part clear: a sensitive VLF receiver has to distinguish natural signals from aliasing, calibration signals, and electrical noise generated by the spacecraft itself.

CubeSatData AcquisitionEasyEDASchematic DesignSignal ProcessingVLF

Summary

Electronics & PCB Design
Project
In development

Evidence on file

Documentation

My contribution

I drew the Rev A receiver schematic in EasyEDA and reviewed it against what the measurement demands. Alongside the drawing I wrote the receiver architecture, the analog signal path, the acquisition concept, the top-level requirements, the event-detection logic with its pre- and post-trigger capture, the spectral-analysis and calibration concepts, the interference strategy, and the verification method for each mission function.

Rev A is a design-stage schematic. Fabrication and hardware testing are not part of this revision. The review is my assessment of which parts of the receiver the drawing settles and which it does not.

Project overview

01

Why I built this

Lightning radiates a great deal of energy at very low frequencies, and that energy does not stay in the atmosphere. It couples upward into the ionosphere and magnetosphere, and what happens on the way is what the mission asks.

A receiver in orbit can look for the radio pulses lightning produces, for whistlers — pulses stretched in frequency by travelling along magnetic field lines — and for the waveform structure and spectrum of both. A receiver in orbit can sample those signals along a path through the ionosphere and magnetosphere that ground measurements alone cannot reproduce.

02

Mission objective

The intended payload would measure the magnetic component of VLF signals, initially across 3 to 30 kHz, and identify candidate lightning-generated events. For each it would record the waveform and its spectrum, attach UTC time and orbital position, and store it for downlink. Detections would then be compared against independent lightning observations.

This is a receiver mission: the only signal it is meant to generate is a calibration tone injected into its own front end. That is intended behaviour — Rev A is a schematic and demonstrates none of it.

03

What Rev A contains

By subsystem, with designators for anyone following on the drawing.

H1, a two-pin connector. The coil is not on the sheet.
U4, a TLV9062 dual op-amp: preamplifier and conditioning.
Passband and anti-alias conditioning from the network around the op-amp.
U5, an MCP3202 12-bit SPI converter.
U6, a 2.4 GHz MCU module, driving the converter and event processing.
U3, an AP2112K-3.3 regulator, with L1 ferrite between digital and analog supply.
Polyfuse, D1/D2 TVS, D3 on the antenna input, BAT54S clamps.
USB-C, SW1 reset, SW2 boot, status LEDs.
U7, a four-pin OLED / I2C connector.
CID45N65MD8 gallium-nitride and CI02S120C3 silicon-carbide devices, annotated as transmitters. Purpose unresolved.
04

Rev A schematic

EasyEDA Schematic V1.0. The title block identifies the artefact as PAYLOAD11: VLF Wave / Lightning Leakage Monitor, created 13 June 2026 and updated 26 June 2026 — the drawing's dates, not the project's.

Page 1 of the export, rendered as drawn. Open the enlarged view to follow the layout, and the PDF to read it.

05

The receiver signal chain

Magnetic field in at one end, a catalogued event out at the other. The receiver core is on the Rev A sheet; the sensor is external, and the flight subsystems past the processor are requirements the drawing does not settle.

Solid — represented in the Rev A schematicDashed — an external sensor, or a flight-system requirement
    1. VLF magnetic field

      Target band 3 to 30 kHz.

    1. External search coil

      Turns a changing field into a small voltage. Connected at H1; its geometry and sensitivity are not on the sheet.

  1. Represented in Rev A
    1. Analog preamplifier

      U4, lifting a microvolt-level signal to something a converter can read.

    2. Band-limiting and anti-alias filter

      Attenuates what lies above the band, so out-of-band energy cannot fold back in as false signal.

    3. 12-bit ADC

      U5, an MCP3202.

    4. Payload MCU

      U6 runs the acquisition.

    5. Event detection, pre-trigger buffer, spectral processing

      An adaptive threshold, a buffer holding the signal from before the trigger, and the spectra computed from it.

    1. Storage and spacecraft computer

      Science storage with integrity checking, and a flight command and data interface.

    2. Ground processing

      Calibrated waveforms, spectra, event catalogues, correlation with independent lightning records.

The receiver core is drawn. The coil is a physical sensor the schematic can only show as a connector, and timing, storage and the spacecraft interface are flight-system requirements Rev A does not represent.
06

What the design review found

The receiver core is drawn. The review was about the distance between that and an instrument whose measurements would mean something.

The sensor is the first gap. The coil is external and not shown, so its geometry, its sensitivity in volts per tesla and its calibrated response are undefined — and each sits in the relationship between a measured voltage and the field that produced it. A coil mounted near spacecraft wiring measures the spacecraft.

Then the analog path. Gain is unverified against the requirement that 10 microvolts RMS give at least 10 dB SNR, and one fixed setting may not serve weak and strong events alike. The filter must be designed and measured rather than assumed: 3 to 30 kHz flat within 3 dB, 20 dB attenuation above roughly 40 to 45 kHz. The 1.65 V bias and stable 80 to 100 kSPS sampling need checking too.

The flight subsystems are requirements, not parts of the drawing: UTC within a millisecond, storage with 99 per cent integrity, a spacecraft-computer interface. USB-C, the OLED and the MCU's 2.4 GHz path are development conveniences — none is the downlink.

07

Keeping the spacecraft out of the measurement

A VLF receiver is sensitive enough to detect the spacecraft it is bolted to. That is not a nuisance to tidy up at integration; it decides whether the instrument has a noise floor low enough to see anything.

Switching and digital subsystems can radiate or couple energy into the receiver band. The review names them: Wi-Fi, the OLED, the LEDs, switching circuits, unnecessary radios, high-current wiring near the coil. Any can put a line exactly where a natural signal would sit, and a clock harmonic does not look different from lightning once it has been through the same amplifier.

So noisy subsystems are disabled during sensitive measurements rather than trusted, repeated noise frequencies are identified so they can be recognised later, and the coil is mounted away from high-current wiring.

The verification approach is the part worth writing down, because it is the only way to know which subsystem is responsible. Record a baseline with everything off. Enable one subsystem at a time and record what changes. Build an interference database. Then repeat it in the assembled satellite, because a subsystem quiet on a bench is not necessarily quiet beside everything else.

None of it has been carried out.

08

Calibration and the ambiguous transmitter devices

A receiver that cannot check itself produces numbers nobody can defend. The intended calibration system injects a known signal so coil response, gain, filter response, converter accuracy and drift can each be checked against a traceable reference — stable within 5 per cent, and never mistaken for a natural event.

The drawing contains two devices that do not obviously belong to a receiver: CID45N65MD8, annotated as a gallium-nitride transmitter, and CI02S120C3, annotated as silicon carbide. The review's reading is that they might be intended for that calibration role.

I am not going to settle it here. The source says their connections and purpose need clarification, and that is where it stands. Whether they are the injection path or something that should not be on the board is Rev B work.

09

Event capture and timing

What happens when the detector fires. Every figure is a design requirement. Timing matters because detections are meant to be matched against independent records of the same lightning.

  1. 01

    Candidate event detected

    Threshold adapting to measured noise; target 90 per cent detection at 6 dB SNR, under one false trigger per minute.

  2. 02

    Preserve at least 1 second before the trigger

    A circular buffer runs continuously, so the onset is not lost to the time taken to recognise an event.

  3. 03

    Preserve at least 3 seconds after the trigger

    Long enough to carry a dispersed whistler, with the trigger position recorded.

  4. 04

    Attach accurate time and position

    UTC within 1 ms, plus position and operating state. Lost synchronisation is flagged.

  5. 05

    Calculate spectra and spectrograms

    FFT settings recorded in the metadata.

  6. 06

    Store for later downlink

    Waveform, time, position, sample rate, gain, temperature and checksum, against 99 per cent integrity.

10

Critical Rev B priorities

The items that decide whether the next revision is an instrument rather than a receiver-shaped board.

Define geometry, sensitivity, mounting away from noise sources, and calibration.
Validate against the 10 microvolt, 10 dB SNR requirement; add selectable settings if one cannot cover the range.
Verify 3 to 30 kHz within 3 dB, and 20 dB attenuation above roughly 40 to 45 kHz.
Verify the 1.65 V midpoint so neither half of a bipolar waveform clips.
Verify sample rate, timing stability, reference and noise over a long recording.
Add GPS 1-PPS or spacecraft-clock synchronisation for UTC within 1 ms.
Define flight science storage and the 99 per cent integrity strategy.
Define a flight command and data interface.
Science-mode shutdown for noisy subsystems, and a measured interference database.
Clarify the injection path, and what the GaN and SiC devices are for.
Coil and analog temperature monitoring, recorded with each event.
11

Verification plan

Grouped by what each exercises. None has been carried out: there is no hardware, and several need a calibrated magnetic-field source or a thermal chamber.

AreaPlanned verification
Search coilCoil inside a calibrated field-generation coil driven 3 to 30 kHz; sensitivity per frequency, repeated across temperature.
Analog chainCalibrated sine waves at the connector at minimum, nominal and maximum amplitude; gain, clipping and response at every setting.
Filter and ADCSweep from below 1 kHz to above 100 kHz; an out-of-band tone injected to look for false in-band signals; a ten-minute run checked for sample count and FFT accuracy.
Event detectionSimulated lightning and whistler waveforms added to recorded noise and replayed, measuring detection probability and false-trigger rate.
Timing and bufferOne pulse to both converter and timing reference, compared against laboratory equipment; saved files checked for the capture intervals.
EMI and calibrationBaseline with everything off, then each subsystem enabled individually and its contribution measured; calibration run across temperature.
Power, environment and interfaceBus voltage swept with current and ripple measured; forced lockups; vibration, thermal-vacuum and radiation review; a 24-hour emulator test.
12

What I learned

A VLF receiver is not an amplifier connected to a converter. I drew it as though it were, and the review is largely a list of what that assumption left out.

The instrument does not end at the connector. The coil's geometry and sensitivity are part of the measurement chain; the filter decides whether energy from outside the band arrives disguised as signal inside it; the sampling has to be steady enough that a frequency means what it says; the timing has to be good enough to match an event against somebody else's record of the same lightning. Filtering, aliasing, calibration and timing are not support details around the science. They are the science.

The spacecraft also becomes part of the environment being measured — most of the noise the instrument must reject comes from the vehicle carrying it. And two devices labelled as transmitters sat on a mission that receives, which forced a separation I had not made clearly enough: receiving, calibrating and talking to the spacecraft are three different jobs.

Technical notes

The detailed VLF receiver requirements, signal-processing design, event-detection logic, interference strategy, calibration plan, and Rev B review behind this schematic.

Read the technical notes

Evidence

Log entries for this project

Project

I designed the first electronics revision of a CubeSat payload intended to measure small-scale irregularities in ionospheric plasma. Rev A brings together a low-current probe front end, programmable probe bias, high-resolution digitisation, GNSS time and position, onboard storage, magnetic and thermal context sensing, and an RP2040 payload computer. The design review then identified the physical-probe, analog, guarding, bias-range and interference-control work still required before fabrication.

In developmentDocumentationCubeSatData Acquisition
Project

I designed the first electronics revision of a CubeSat photometer intended to measure the brightness of a selected star over several hours and look for the small, repeatable dip caused by a known transiting exoplanet. Rev A combines a BPW34 photodiode, a transimpedance amplifier, a 16-bit ADC, a calibration-light interface, onboard storage, power and development electronics. The design review made the harder problem clear: a transit-like dip can also be produced by pointing error, temperature drift, stray light or electronics drift, so those effects have to be measured well enough to rule them out.

In developmentDocumentationAnalog Front EndCubeSat
Project

I designed the first electronics revision of a CubeSat payload intended to detect gamma-ray bursts and timestamp individual detector pulses precisely enough for comparison with other spacecraft and observatories. Rev A brings together pulse amplification, triggering, pulse-height digitisation, GNSS timing, storage, SiPM bias power, housekeeping, and an STM32 payload computer. Reviewing it exposed the most important remaining gaps: the scintillator and SiPM detector head is not yet present, pulse shaping still has to be added, and the timing path must be calibrated end to end before the timestamps can support scientific comparison.

In developmentDocumentationCubeSatEasyEDA