ECSS Structures — Micro-vibration / Noise Disturbance Test (space-systems/ecss/microvibration-test)
Use when the task is to evaluate micro-vibration, microgravity, or noise
disturbance test compliance for spacecraft equipment under ECSS-E-ST-32C
clause 4.6.3.12 — categorizing each disturbance source, verifying frequency
coverage, comparing measured amplitudes against allocated budgets, and
producing a pass/fail determination for each source and for the assessment
as a whole.
Domain quick reference
- Clause 4.6.3.12 governs tests for equipment whose operation generates
mechanical disturbances (reaction wheels, control moment gyroscopes,
cryo-coolers, stepper motors, shutter mechanisms) that can degrade the
performance of co-located sensitive payloads or instruments.
- Each disturbance source is placed into exactly one category before
testing: tonal (discrete spectral line, e.g. a wheel at its spin
frequency and harmonics), broadband (spectrally distributed random
disturbance, e.g. bearing noise), or transient (impulse or short-duration
event, e.g. a latch firing). Placement drives the measurement approach.
- The test measurement frequency range must cover the full required band
stated in the equipment specification. A measurement that starts above
the lower required frequency or ends below the upper required frequency
is a gap, not a pass.
- Force and torque amplitudes are measured on a stiff force-measuring
platform (or equivalent load cell / accelerometer chain with known
transfer function). The measured amplitude at each frequency of interest
is compared against the disturbance budget allocated to that source.
Positive margin (budget minus measured ≥ 0) is required; zero margin is
treated as marginal but compliant.
- A source that exceeds its budget at any frequency, or whose measurement
does not cover the required band, is flagged as a finding. The overall
assessment does not pass until every source clears both checks.
Workflow
- Inventory every disturbance-generating equipment item and categorize
each as tonal, broadband, or transient. Reject any source whose type
cannot be placed into one of these three categories before it enters
the test matrix.
- For each source confirm the test measurement frequency band: the band
must span at least from the lower to the upper boundary stated in the
equipment disturbance specification. Record any gap at the lower or
upper bound as a finding.
- Measure force and torque amplitudes on a force-measuring platform (or
an approved equivalent fixture). Record the measured amplitude for
each source at the frequency or band of interest.
- Compare each measured amplitude against the disturbance budget allocated
to that source. Compute the margin as budget minus measured amplitude.
A negative margin is an exceedance; record it as a finding with the
magnitude of the shortfall.
- Aggregate findings per source: a source passes only when margin ≥ 0
and frequency coverage has no gaps. A source with any finding is
flagged.
- Declare the assessment outcome: overall pass requires every source to
pass. Report the count of failing sources and list all findings.
Pitfalls
- Applying a tonal budget to a broadband source (or vice versa) invalidates
the comparison — the budget and measurement must share the same spectral
interpretation before any margin is meaningful.
- Reading a partial frequency measurement as coverage — if the measured
range starts at 5 Hz and the specification requires from 1 Hz, the
1–5 Hz band is uncovered and must be flagged, not treated as conservative.
- Treating zero margin as a failure — the convention for this assessment is
margin ≥ 0, so zero is marginal but compliant. Recording it as a failure
overstates the finding.
- Omitting a source from the test matrix because its amplitude is expected
to be low — the budget check is the evidence; excluding sources before
measurement introduces an unverified assumption that is itself a gap.
Behavior contract (gate 3)
The source categorization, frequency coverage, margin computation, and
overall assessment logic is exercised by the gate 3 contract test:
scripts/test_microvibration_test.py against
scripts/microvibration_test_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_microvibration_test.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: microvibration-test3description: "Use when evaluate micro-vibration, microgravity, or noise disturbance test compliance for spacecraft equipment under ECSS-E-ST-32C clause 4.6.3.12: categorize each disturbance source as tonal, broadband, or transient, verify that the test measurement frequency band fully covers the required range, compute force and torque disturbance amplitudes using a force-measuring platform or equivalent fixture, compare each measured amplitude against the allocated disturbance budget, and flag any source whose amplitude exceeds the budget or whose frequency coverage is insufficient. Apply this skill when establishing or reviewing the test configuration, measurement chain, and pass/fail criteria for micro-vibration qualification or acceptance testing of rotating or oscillating equipment. Trigger: ecss, e-st-32-structures-scope, microvibration, micro-vibration, noise-disturbance, disturbance-budget, tonal-disturbance, broadband-disturbance, force-platform."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/microvibration-test15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-32-structures-scope, microvibration, noise-disturbance, disturbance-budget, tonal, broadband, force-platform]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Structures — Micro-vibration / Noise Disturbance Test (space-systems/ecss/microvibration-test)2324Use when the task is to evaluate micro-vibration, microgravity, or noise25disturbance test compliance for spacecraft equipment under ECSS-E-ST-32C26clause 4.6.3.12 — categorizing each disturbance source, verifying frequency27coverage, comparing measured amplitudes against allocated budgets, and28producing a pass/fail determination for each source and for the assessment29as a whole.3031## Domain quick reference3233- Clause 4.6.3.12 governs tests for equipment whose operation generates34 mechanical disturbances (reaction wheels, control moment gyroscopes,35 cryo-coolers, stepper motors, shutter mechanisms) that can degrade the36 performance of co-located sensitive payloads or instruments.37- Each disturbance source is placed into exactly one category before38 testing: tonal (discrete spectral line, e.g. a wheel at its spin39 frequency and harmonics), broadband (spectrally distributed random40 disturbance, e.g. bearing noise), or transient (impulse or short-duration41 event, e.g. a latch firing). Placement drives the measurement approach.42- The test measurement frequency range must cover the full required band43 stated in the equipment specification. A measurement that starts above44 the lower required frequency or ends below the upper required frequency45 is a gap, not a pass.46- Force and torque amplitudes are measured on a stiff force-measuring47 platform (or equivalent load cell / accelerometer chain with known48 transfer function). The measured amplitude at each frequency of interest49 is compared against the disturbance budget allocated to that source.50 Positive margin (budget minus measured ≥ 0) is required; zero margin is51 treated as marginal but compliant.52- A source that exceeds its budget at any frequency, or whose measurement53 does not cover the required band, is flagged as a finding. The overall54 assessment does not pass until every source clears both checks.5556## Workflow57581. Inventory every disturbance-generating equipment item and categorize59 each as tonal, broadband, or transient. Reject any source whose type60 cannot be placed into one of these three categories before it enters61 the test matrix.622. For each source confirm the test measurement frequency band: the band63 must span at least from the lower to the upper boundary stated in the64 equipment disturbance specification. Record any gap at the lower or65 upper bound as a finding.663. Measure force and torque amplitudes on a force-measuring platform (or67 an approved equivalent fixture). Record the measured amplitude for68 each source at the frequency or band of interest.694. Compare each measured amplitude against the disturbance budget allocated70 to that source. Compute the margin as budget minus measured amplitude.71 A negative margin is an exceedance; record it as a finding with the72 magnitude of the shortfall.735. Aggregate findings per source: a source passes only when margin ≥ 074 and frequency coverage has no gaps. A source with any finding is75 flagged.766. Declare the assessment outcome: overall pass requires every source to77 pass. Report the count of failing sources and list all findings.7879## Pitfalls8081- Applying a tonal budget to a broadband source (or vice versa) invalidates82 the comparison — the budget and measurement must share the same spectral83 interpretation before any margin is meaningful.84- Reading a partial frequency measurement as coverage — if the measured85 range starts at 5 Hz and the specification requires from 1 Hz, the86 1–5 Hz band is uncovered and must be flagged, not treated as conservative.87- Treating zero margin as a failure — the convention for this assessment is88 margin ≥ 0, so zero is marginal but compliant. Recording it as a failure89 overstates the finding.90- Omitting a source from the test matrix because its amplitude is expected91 to be low — the budget check is the evidence; excluding sources before92 measurement introduces an unverified assumption that is itself a gap.9394## Behavior contract (gate 3)9596The source categorization, frequency coverage, margin computation, and97overall assessment logic is exercised by the gate 3 contract test:98scripts/test_microvibration_test.py against99scripts/microvibration_test_logic.py (stdlib unittest, offline). Run:100101```102python3 scripts/test_microvibration_test.py103```104105## Compliance106107- ECSS standards are freely downloadable (ESA); cite the source and108 paraphrase per standards-map.yaml.109- compliance: STANDARDS-REF, gated: false.