Aerospace & Space-Grade ADCs for Radiation and Wide-Temp Designs
← Back to:Analog-to-Digital Converters (ADCs)
Aerospace / space-grade ADC design is an evidence-driven engineering workflow: translate mission constraints (radiation, temperature, supply chain) into bounded risks, add explicit mitigation and recovery hooks, then verify with pass/fail criteria. The goal is not the “best ADC,” but a measurement chain that remains accurate, recoverable, and traceable throughout the mission life.
What is an Aerospace / Space-Grade ADC?
A space-grade ADC is not defined by a single “best” performance number. It is defined by evidence: the measurement chain must remain predictable and recoverable under radiation exposure, extreme environments, and mission-grade supply-chain controls over the intended lifetime.
In practice, “space-grade” means three constraint sets must be satisfied together: Radiation (TID / SEE behavior and test conditions), Environment (wide temperature and mechanical/vacuum stresses), and Supply-chain (traceability, screening/qualification, and controlled changes).
Radiation constraints (TID / SEE)
- TID: long-term parameter drift under dose; treat offset/gain/drift as lifetime budget items.
- SEE: single-event behavior mapped to system risk: SEL (over-current / destructive risk), SEU (state/config flips), SET (transient errors / spikes).
- Test context matters: bias, dose-rate/conditions, and recovery assumptions must match the mission envelope.
Environmental constraints (wide-temp / vacuum / shock)
- Wide temperature: accuracy and linearity must remain inside budget across range and gradients, not just at one point.
- Thermal cycling: packaging and assembly stresses can change drift and long-term stability.
- Vacuum / outgassing and vibration/shock: system-level material and interconnect reliability constraints.
Supply-chain constraints (traceability / screening / PCN)
- Traceability: lot-level lineage and records to bound anomalies to known batches.
- Screening / qualification flow: mission-grade screening evidence, not just production test.
- Controlled change: PCN discipline for process/material/test-flow changes across the program lifetime.
A practical definition is therefore evidence-based: the chain is selected, documented, and verified against radiation behavior, environmental envelopes, and controlled sourcing, instead of relying on a single headline spec.
Why ADC and analog measurement chains fail more easily in space
Space environments push the measurement chain into failure modes that are easy to underestimate in lab conditions. The dominant risks are not only “noise” or “spec margin” but lifetime drift, rare high-impact events, and temperature-driven error reallocation. These effects must be translated into observable symptoms and system-level risks to define what should be protected, detected, and verified.
The following map keeps the discussion engineering-focused: each input stress (TID / SEE / wide temperature) is linked to what changes inside the chain, what can be measured at the outputs, and what system decisions can be corrupted.
TID → drift-type degradation
Bias/threshold shifts and increased leakage re-shape offset, gain, and drift over mission life. The risk is not just worse initial specs, but a changing error budget that can silently invalidate calibration and thresholds.
SEE → transient / functional events
Single-event effects are “rare but high impact”. SEL is a destructive over-current risk, SEU flips configuration/state bits (often a silent error), and SET injects short spikes that can trip triggers or corrupt samples.
Wide temperature → error budget reshuffle
Temperature changes shift which block dominates error: reference behavior, front-end amplifier offsets/noise, sampling leakage, and clock/jitter allocation can all move. A design that “passes at room temperature” can fail at extremes or during transitions.
Treat these as different classes of risk: TID changes long-term accuracy, SEE produces sparse but high-impact events, and wide temperature shifts which block dominates the error budget. A robust space-grade chain is built around predictable bounds, detectability, and recoverability.
System architecture strategies for space-grade ADC designs
A space-grade measurement chain is chosen as a system strategy, not as a single converter part number. Radiation events and wide-temperature drift are managed by selecting an overall path that defines how much risk is absorbed by the device itself versus by detection, recovery, and verification at the system level.
Three practical strategies cover most programs: (A) a space-grade / rad-hard ADC with the clearest qualification evidence, (B) a rad-tolerant ADC with explicit system-level fault tolerance, and (C) a COTS approach that relies on shielding, redundancy, and derating under a mission profile.
Strategy A: Space-grade / rad-hard ADC
- Benefit: clearest radiation behavior and qualification path for mission assurance.
- Trade-off: performance/power options may be limited; cost and lead time are typically higher.
- Still required: configuration integrity and wide-temp drift verification remain mandatory at system level.
Strategy B: Rad-tolerant ADC + system-level fault tolerance
- Key idea: treat SEE as events that must be detected and recovered from, rather than ignored.
- Must-haves: SEL protection (current limiting + power cycling), register/coeff refresh, and periodic self-check.
- Data integrity: CRC/sequence checks, frame-loss handling, and timeout recovery.
Strategy C: COTS + shielding + redundancy + derating
- Use when: mission level allows graceful degradation, and redundancy/verification effort is acceptable.
- Decision drivers: cost/lead time, availability, and the ability to validate batches under the mission profile.
- Engineering requirement: redundancy and derating must convert uncertainty into bounded risk.
Mandatory engineering actions (interface-level checkpoints)
- Critical registers & calibration coefficients: load on boot, verify periodically, refresh/rollback on mismatch.
- SEL protection path: current-limit sensing, controlled power-cycle, and thermal monitoring hooks for recovery.
- Data-link robustness: CRC + frame sequencing, frame-loss detection, and timeout recovery to a known-safe state.
A robust program selects one strategy early and then builds verification around it: drift budgets for TID and temperature, event handling for SEE, and repeatable recovery for critical faults. Interface-level hooks (power control, health signals, and integrity checks) ensure the chain can be forced back to a known state.
Isolation front-ends and wide-temperature packaging
In space and high-reliability aerospace systems, isolation is rarely “optional”. It is often the only practical way to keep a low-voltage measurement and control domain stable when the sensed domain contains high voltage, high dv/dt switching, or long harnesses that inject common-mode disturbances.
This section focuses on selection-critical parameters and system risks. It does not dive into isolator internal architectures. The goal is to map isolation choices and packaging realities to observable errors, timing uncertainty, and long-term reliability under wide temperature and mechanical stress.
Typical space scenarios that drive isolation needs
- High-voltage power: bus monitoring, converters, and protection thresholds under fast common-mode transients.
- Solar array / EP / motor drives: switching edges and ground bounce coupled into sensing and control.
- Long harnesses: common-mode pickup, ground loops, and surge/ESD stress on remote sensing lines.
Isolation selection fields (field → risk it controls)
- Isolation rating: defines fault boundary across domains under HV and transient stress.
- CMTI: determines susceptibility to dv/dt-driven false events, glitches, and mis-sampling.
- Barrier capacitance: controls common-mode current injection across the barrier (noise/EMI coupling).
- Propagation delay & jitter: sets timing uncertainty for synchronization and control-loop stability.
- Drift vs temperature: governs long-term accuracy and cross-temperature repeatability of the chain.
- Operating temperature range: ensures function and bounded error at extremes and during transitions.
- Package / outgassing grade (if required): aligns materials and assembly with vacuum and contamination limits.
Wide-temperature packaging and assembly risks (where drift becomes unpredictable)
- Ceramic vs plastic packages: stress behavior under thermal cycling affects long-term stability and repeatability.
- Thermal cycling: solder and interconnect fatigue can create intermittent faults that look like random noise.
- Coating & cleaning: residues and contamination can increase leakage and bias drift across temperature.
- Connectors & cables: harness motion and coupling can reintroduce common-mode injection even with isolation.
A good isolation design makes common-mode behavior and recovery predictable: bounded injection across the barrier, stable timing, and repeatable drift across temperature and cycling. Packaging and assembly choices must support that predictability over the mission profile.
Mission and payload mappings: requirements to solution strategy
Space-grade ADC requirements are best defined from the real measurement chain, not from a generic specification list. Each mission class has a dominant set of risks (drift, dv/dt injection, timing uncertainty, data integrity, or silent configuration errors). The mappings below translate typical payload needs into the key metrics to prioritize, the pitfalls to avoid, and the most natural system strategy (A/B/C).
Power and propulsion measurement (current / voltage / bus ripple)
Prioritize: CMTI, barrier capacitance, delay consistency, drift over temperature and dose. Pitfalls: false protection trips, dv/dt-driven glitches, dropout without recovery. Typical strategy: A or B, often with isolation front-ends.
Attitude control and actuators (IMU / gyros / motor feedback)
Prioritize: latency and timing stability, drift, configuration integrity. Pitfalls: silent mode/scale flips (SEU), transient outliers destabilizing a control loop. Typical strategy: B with strong integrity checks; A for highest assurance.
Communications and telemetry (IF/RF sampling chains)
Prioritize: clock/jitter budget ownership, link integrity and recovery behavior. Pitfalls: jitter underestimation, event-driven link dropouts and slow recovery. Typical strategy: A or B; RF/IF implementation details belong in the RF/IF pages.
Science payloads (low-frequency precision / imaging)
Prioritize: drift and repeatability across temperature and dose, calibration coefficient stability. Pitfalls: “passes at room temperature” but fails across temperature transitions or over mission life. Typical strategy: A for highest stability; B/C require tighter verification windows and derating.
These mappings keep the selection vertical and chain-based: choose the mission row, prioritize the dominant metrics, then pick the strategy that provides the required level of evidence and recoverability. Detailed RF/IF implementation and interface specifics should be handled in the dedicated RF/IF and interfaces pages.
Engineering checklist for aerospace / space-grade ADC chains
Space-grade designs succeed when requirements are translated into bounded risks, then into explicit mitigation hooks, and finally into verification with pass/fail criteria. The checklist below is written to be executable: each block defines the inputs required, the decisions to make, the engineering actions to implement, and the evidence to collect.
1) Mission profile (inputs that drive architecture)
- Inputs: orbit/environment class, mission life, maintenance/repair capability, acceptable degradation mode, shielding mass budget, power/volume constraints.
- Decision: select Strategy A/B/C and define what must remain correct under faults (control stability, protection thresholds, data availability).
- Evidence: one-page mission profile + assumptions list (documented margins and exclusions).
2) Radiation targets (TID + SEE as verifiable requirements)
- Inputs: TID target, SEE tolerance by class (SEL/SEU/SET), test conditions, and margin model.
- Risk model: drift over life (TID) + event-driven faults (SEE) with detectability and recoverability.
- Actions: SEL protection hook; SEU detection (config integrity); SET containment (outlier windows / trigger hardening).
- Pass/Fail: SEL is contained and recoverable; SEU is detectable and correctable; SET does not cause unsafe decisions.
3) Temperature profile (wide-temp operation + cycling)
- Inputs: operating and storage ranges, thermal cycling envelope, expected transitions, self-heating assumptions.
- Budgeting: allocate drift budget across reference, AFE, sampling/leakage, isolation timing, and ADC behavior.
- Pass/Fail: accuracy stays within budget across temperature points and transitions; no intermittent behavior under cycling.
4) Power and protection (recovery paths must exist)
- Inputs: power tree, controllable rails, sensing points (current/temperature/PG), reset topology, watchdog availability.
- Actions: SEL current limiting, controlled power-cycle, over-temperature response, watchdog + deterministic re-init sequence.
- Pass/Fail: protection response time and thresholds meet safety needs; recovery returns to a known-good state repeatedly.
5) Configuration integrity (SEU-resistant operation)
- Actions: register mirroring, periodic scrub, coefficient/version tagging, mismatch detection and rollback strategy.
- Evidence: golden configuration table, scrub schedule, and exception handling rules.
- Pass/Fail: any deviation is detected; correction restores intended modes without destabilizing the system.
6) Test and qualification (matrix + acceptance criteria)
- Matrix: temperature points × dose steps × operating modes (rate, gain, filter, interface state).
- Batch control: define key metrics for lot-to-lot stability and acceptance sampling plan.
- Pass/Fail: drift stays within budget; event handling meets recovery requirements; data integrity meets the project’s thresholds.
The most common failure mode in space programs is not missing a feature, but missing a recovery path or an acceptance criterion. Lock the mission profile early, define bounded risks, implement explicit mitigation hooks, and verify with a test matrix that includes temperature transitions, event handling, and repeatability across batches.
IC selection logic: fields → risk mapping → RFQ template
Space-grade ADC selection is a documentation-driven process. Selection fields must map to failure modes (TID drift, SEL latch-up, SEU silent corruption, SET transients), and the RFQ must require the evidence package (radiation reports, screening flow, traceability, PCN control, and life data). The structure below is designed for direct vendor comparison and acceptance criteria definition.
(1) Parameter fields (grouped for RFQ and acceptance)
- TID rating: stated limit and test conditions; drift expectations over life.
- SEL: latch-up immunity/threshold and test conditions (LET, temperature); recovery behavior.
- SEU: sensitivity/rate for configuration, calibration, and state retention.
- SET: transient susceptibility on data/trigger paths (glitch behavior).
- Screening level and qualification flow: documented steps, yield expectations, and exclusions.
- Traceability: lot/date code, serialization (if applicable), and documentation deliverables.
- Life / FIT data: conditions, assumptions, and evidence for mission duration.
- PCN control: notification policy, change categories, and re-qualification triggers.
- SNR / ENOB, SFDR: performance under the intended input profile and clock plan.
- INL / DNL: linearity for measurement validity over life.
- Offset/gain drift: across temperature and expected TID margin.
- 0.1–10 Hz noise (only when low-frequency precision dominates the payload).
- Temperature range: operating and storage; behavior during transitions/cycling.
- Package type: ceramic/plastic options, thermal resistance, and assembly constraints.
- Materials/outgassing: required declarations when mission standards demand it.
- Interface: supported modes and reset/recovery behavior (avoid protocol details here).
- Clock requirements: constraints that drive jitter budget and distribution.
- Synchronization: triggers, alignment options, and deterministic startup behavior.
- Power: consumption under temperature extremes and implications for thermal design.
(2) Risk mapping (field → failure mode → required system action → verification)
| Field | Failure mode | Required action | Verification evidence |
|---|---|---|---|
| SEL threshold / immunity | Latch-up overcurrent → thermal damage or reset storms | Current limit + fast detect + controlled power-cycle + thermal monitoring | SEL report + board-level containment test + recovery time record |
| TID rating / drift margin | Long-life drift exceeds error budget; calibration no longer valid | Increase margin, derate, and define calibration cadence / re-trim strategy | TID report + cross-temperature drift data + budget sign-off |
| SEU sensitivity | Silent configuration corruption (gain/mode/filter/coefficients) | Register mirror + CRC/version tag + periodic scrub + rollback rules | SEU data (or assumption) + scrub verification + fault injection log |
| SET characterization | Transient spikes → false triggers, false alarms, data outliers | Outlier windowing + trigger debouncing + safety gating on decisions | Transient stress tests + system-level decision robustness test |
| Temp range / packaging | Thermal cycling causes drift shift, intermittents, or assembly fatigue | Thermal budget allocation + assembly controls + burn-in (if applicable) | Temperature matrix + cycling logs + repeatability across transitions |
| Interface / reset behavior | Dropout / stuck state → data loss without deterministic recovery | Timeout + retry + deterministic re-init + error counters / telemetry | Link recovery test + brownout/reset sequencing validation |
A field that does not map to a failure mode should not be used to drive selection. A failure mode that does not map to a mitigation hook is a design gap.
(3) RFQ template (copy/paste to distributor or manufacturer)
Provide the requested information as a single evidence package. Missing reports should be explicitly stated with a proposed alternative.
Subject: RFQ – Aerospace/Space-Grade ADC (evidence package required)
Mission profile (one line):
- Orbit / environment class:
- Mission life:
- Maintenance/repair capability:
- Shielding mass budget:
- Operating/storage temperature range:
Target part(s) / alternatives:
- Primary candidate:
- Acceptable alternates:
Required fields (please fill or attach):
Radiation:
- TID rating and test conditions (including temperature):
- SEL immunity/threshold and conditions (LET, temperature), recovery notes:
- SEU sensitivity/rate for configuration/state (what is covered):
- SET characterization (data/trigger path behavior, if available):
Screening / qualification / reliability:
- Screening level and qualification flow description:
- Lot/date code traceability and delivered documentation:
- Life/FIT data and assumptions:
- PCN policy and change control procedure:
Electrical / system:
- Key performance summary (SNR/ENOB, SFDR, INL, drift):
- Interface modes and deterministic reset/re-init behavior:
- Clock requirements and any stated jitter sensitivity:
- Power consumption across temperature extremes:
Requested attachments:
- TID/SEE reports (or latest available radiation & reliability reports)
- Screening/qualification flow document
- Traceability statement and example CoC/lot documentation
- PCN policy document and last 12-month change history (if available)
Example part-number shortlist (starting points, evidence still required)
- TI ADC168M102R-SEP — radiation-tolerant, 8-channel, 1MSPS, 16-bit simultaneous-sampling SAR ADC.
- TI ADC128S102-SEP — radiation-tolerant, 8-channel, 50kSPS–1MSPS, 12-bit SAR ADC.
- Renesas ISL73141SEH — radiation-hardened, 14-bit, 1MSPS SAR ADC.
- ST RHFAD128 — rad-hard, 8-channel, 12-bit, 50kSPS–1MSPS ADC.
- TI ADS1278-SP — radiation-hardened, 24-bit, 8-channel simultaneous-sampling delta-sigma ADC.
- Teledyne e2v EV12AQ600 — high-speed space-qualified ADC family (up to multi-GSPS aggregate sampling).
- Microchip MCP37D31-RT200 — 200MSPS, 16-bit rad-tolerant ADC with 8-channel MUX (check current lifecycle status during RFQ).
The shortlist is only a starting point. Final selection should be driven by the evidence package: radiation reports, screening/qualification flow, traceability, PCN control, and acceptance criteria aligned to mission risk.
Request a Quote
FAQ: Aerospace / space-grade ADC design and selection
These questions focus on space-grade concerns: radiation drift and events (TID/SEL/SEU/SET), wide-temperature behavior, recoverability, evidence packages, and acceptance testing. No images are used in this section by design.
