ECSS AIT — Element Electromagnetic Compatibility Tests (space-systems/ecss/e1003-el-emc)
Use when the task is the electromagnetic compatibility assessment of a space
element under ECSS-E-ST-10-03C §6.5.5, covering auto-compatibility verification,
passive intermodulation (PIM) evaluation for RF-carrying elements, residual
magnetic dipole moment measurement, and selection of stand-alone versus embedded
test mode per §6.5.5.2.
Domain quick reference
- §6.5.5 groups element EMC tests into four categories: auto-compatibility
(internal emitter vs. internal receiver), passive intermodulation (two carriers
mixing in passive components to produce unwanted products), magnetic field
measurement (residual dipole moment), and the general EMC conducted/radiated
emission and susceptibility suite.
- §6.5.5.2 separates tests into two modes. Stand-alone mode applies to every
element: the element is powered and exercised in isolation under representative
electrical boundary conditions. Embedded mode supplements stand-alone when
the element is available assembled into its higher-level unit; conducted and
radiated susceptibility are the primary candidates for embedded re-check
because the higher-level assembly provides realistic cable harness and grounding
that cannot be fully replicated stand-alone.
- Auto-compatibility: a finding occurs when an internal emitter frequency falls
inside an internal receive band and the measured isolation margin is below the
required minimum. An emitter whose frequency sits outside all internal receive
bands requires no margin check against those bands.
- PIM: applies only to elements with RF transmission paths through passive
components (connectors, cables, waveguides, filters, antennas). For each pair
of carrier frequencies, odd-order intermodulation products (3rd, 5th, 7th, ...)
are computed as m·f1 − n·f2 (and m·f2 − n·f1) where m + n equals the order.
A product that falls within the element's receive band is a finding.
- Magnetic field: the element's residual magnetic dipole moment is measured in
three orthogonal axes and the vector magnitude is compared against the
element-level magnetic budget. Exceeding the budget is a finding.
Workflow
- Obtain the element's internal frequency plan (all emitter center frequencies
and all receive band definitions) and the EMC requirements (isolation margin
per emitter–receiver pair, magnetic dipole budget, PIM-free receive band).
Reject an assessment that lacks a frequency plan or magnetic budget.
- For auto-compatibility, iterate every emitter–receiver pair: if the emitter
frequency lies within the receiver's band, check that the measured isolation
margin meets or exceeds the required margin; flag any pair where it does not.
Emitter frequencies outside all receive bands are out-of-scope for margin
checking and are recorded as not applicable.
- If the element carries RF paths through passive components, list every pair
of simultaneous carrier frequencies. For each pair, compute odd-order PIM
products up to at least the 9th order; flag any product that falls within a
receive band.
- Measure the element's residual magnetic dipole moment (three axes) and
compare the vector magnitude against the budget. Record a finding if the
budget is exceeded.
- Assign the test mode for each test type per §6.5.5.2: stand-alone is
mandatory for the full suite; if the element is available in its assembled
higher-level unit, schedule conducted and radiated susceptibility re-checks
in embedded mode as a supplement.
- Aggregate all findings. The element is compliant for EMC when the
auto-compatibility list, the PIM list, and the magnetic finding are all clear.
Pitfalls
- Skipping PIM evaluation because no active mixing occurs — PIM arises from
non-linearity in passive junctions (connector interfaces, cable ferrite
material, oxidised contacts) and must be assessed for any element with RF
transmission paths, regardless of whether it contains an active mixer.
- Treating the embedded-mode susceptibility re-check as optional when the
element is available assembled — §6.5.5.2 makes the embedded supplement
mandatory for susceptibility once the higher-level assembly exists; skipping
it leaves the realistic harness/grounding environment unverified.
- Accepting a zero-margin auto-compatibility result as a pass — the required
margin is a positive value set in the EMC requirements; a measured margin of
exactly 0 dB is only acceptable if the requirement explicitly allows it.
- Omitting the magnetic measurement for elements that appear non-magnetic —
residual ferromagnetic content in structure, connectors, and PCB materials can
produce non-trivial dipoles; the check is mandatory for all elements in the
§6.5.5 scope, not limited to elements with obvious magnetic components.
Behavior contract (gate 3)
The auto-compatibility, PIM, magnetic-field, and test-mode-selection logic is
exercised by the gate 3 contract test:
scripts/test_e1003_el_emc.py against scripts/e1003_el_emc_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e1003_el_emc.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1003-el-emc3description: "Use when running element electromagnetic compatibility tests under ECSS-E-ST-10-03C §6.5.5: determine auto-compatibility by verifying that each internal emitter's frequency has sufficient isolation margin against every internal receive band, evaluate passive intermodulation (PIM) products for RF-bearing elements to confirm no odd-order products fall within the receive band, perform residual magnetic dipole moment checks against the element magnetic budget, and identify the correct test mode—stand-alone or embedded—per §6.5.5.2 for each applicable test category. Trigger: ecss, e-st-10-03c, emc, electromagnetic-compatibility, pim, passive-intermodulation, magnetic-field, auto-compatibility, stand-alone, embedded."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/e1003-el-emc15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-03c, emc, electromagnetic-compatibility, pim, passive-intermodulation, magnetic-field, auto-compatibility]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS AIT — Element Electromagnetic Compatibility Tests (space-systems/ecss/e1003-el-emc)2324Use when the task is the electromagnetic compatibility assessment of a space25element under ECSS-E-ST-10-03C §6.5.5, covering auto-compatibility verification,26passive intermodulation (PIM) evaluation for RF-carrying elements, residual27magnetic dipole moment measurement, and selection of stand-alone versus embedded28test mode per §6.5.5.2.2930## Domain quick reference3132- §6.5.5 groups element EMC tests into four categories: auto-compatibility33 (internal emitter vs. internal receiver), passive intermodulation (two carriers34 mixing in passive components to produce unwanted products), magnetic field35 measurement (residual dipole moment), and the general EMC conducted/radiated36 emission and susceptibility suite.37- §6.5.5.2 separates tests into two modes. Stand-alone mode applies to every38 element: the element is powered and exercised in isolation under representative39 electrical boundary conditions. Embedded mode supplements stand-alone when40 the element is available assembled into its higher-level unit; conducted and41 radiated susceptibility are the primary candidates for embedded re-check42 because the higher-level assembly provides realistic cable harness and grounding43 that cannot be fully replicated stand-alone.44- Auto-compatibility: a finding occurs when an internal emitter frequency falls45 inside an internal receive band and the measured isolation margin is below the46 required minimum. An emitter whose frequency sits outside all internal receive47 bands requires no margin check against those bands.48- PIM: applies only to elements with RF transmission paths through passive49 components (connectors, cables, waveguides, filters, antennas). For each pair50 of carrier frequencies, odd-order intermodulation products (3rd, 5th, 7th, ...)51 are computed as m·f1 − n·f2 (and m·f2 − n·f1) where m + n equals the order.52 A product that falls within the element's receive band is a finding.53- Magnetic field: the element's residual magnetic dipole moment is measured in54 three orthogonal axes and the vector magnitude is compared against the55 element-level magnetic budget. Exceeding the budget is a finding.5657## Workflow58591. Obtain the element's internal frequency plan (all emitter center frequencies60 and all receive band definitions) and the EMC requirements (isolation margin61 per emitter–receiver pair, magnetic dipole budget, PIM-free receive band).62 Reject an assessment that lacks a frequency plan or magnetic budget.632. For auto-compatibility, iterate every emitter–receiver pair: if the emitter64 frequency lies within the receiver's band, check that the measured isolation65 margin meets or exceeds the required margin; flag any pair where it does not.66 Emitter frequencies outside all receive bands are out-of-scope for margin67 checking and are recorded as not applicable.683. If the element carries RF paths through passive components, list every pair69 of simultaneous carrier frequencies. For each pair, compute odd-order PIM70 products up to at least the 9th order; flag any product that falls within a71 receive band.724. Measure the element's residual magnetic dipole moment (three axes) and73 compare the vector magnitude against the budget. Record a finding if the74 budget is exceeded.755. Assign the test mode for each test type per §6.5.5.2: stand-alone is76 mandatory for the full suite; if the element is available in its assembled77 higher-level unit, schedule conducted and radiated susceptibility re-checks78 in embedded mode as a supplement.796. Aggregate all findings. The element is compliant for EMC when the80 auto-compatibility list, the PIM list, and the magnetic finding are all clear.8182## Pitfalls8384- Skipping PIM evaluation because no active mixing occurs — PIM arises from85 non-linearity in passive junctions (connector interfaces, cable ferrite86 material, oxidised contacts) and must be assessed for any element with RF87 transmission paths, regardless of whether it contains an active mixer.88- Treating the embedded-mode susceptibility re-check as optional when the89 element is available assembled — §6.5.5.2 makes the embedded supplement90 mandatory for susceptibility once the higher-level assembly exists; skipping91 it leaves the realistic harness/grounding environment unverified.92- Accepting a zero-margin auto-compatibility result as a pass — the required93 margin is a positive value set in the EMC requirements; a measured margin of94 exactly 0 dB is only acceptable if the requirement explicitly allows it.95- Omitting the magnetic measurement for elements that appear non-magnetic —96 residual ferromagnetic content in structure, connectors, and PCB materials can97 produce non-trivial dipoles; the check is mandatory for all elements in the98 §6.5.5 scope, not limited to elements with obvious magnetic components.99100## Behavior contract (gate 3)101102The auto-compatibility, PIM, magnetic-field, and test-mode-selection logic is103exercised by the gate 3 contract test:104scripts/test_e1003_el_emc.py against scripts/e1003_el_emc_logic.py105(stdlib unittest, offline). Run:106python3 scripts/test_e1003_el_emc.py107108## Compliance109110- ECSS standards are freely downloadable (ESA); cite the source and111 paraphrase per standards-map.yaml.112- compliance: STANDARDS-REF, gated: false.