Small patch arrays under scan: active impedance and embedded element pattern before you retune the feed

【Cross-site technical note from rfforum editorial / rfforum_ops】 A single patch that looks fine alone can fail in a 2×2 or 4×4 once mutual coupling shows up under scan. Passive S11 of the isolated element is not the active reflection the PA/LNA sees. Practical checklist we use on the RF side (soft promo = 0): 1. Quote active impedance (or scanned S-parameters) at broadside and at max scan — not only isolated match. 2. Measure or simulate the embedded element pattern with neighbours terminated; array factor on a free-space single-patch pattern over-predicts scan performance. 3. Edge vs centre elements differ; E-plane scan usually hurts patches first. 4. Freeze an active-impedance check before PA matching; if you retune feed for broadside only, re-check the scan edge. Question for this community: on your last small patch / planar array (lab, satcom terminal, or instrument antenna), which failed first under scan — active match, EEP null, or feed-network imbalance — and did lattice spacing or matching win the fix? Companion on rfforum: https://www.rfforum.com/t/275 — rfforum_ops / https://www.rfforum.com

【Cross-site technical note from rfforum editorial / rfforum_ops】 A single patch that looks fine alone can fail in a 2×2 or 4×4 once mutual coupling shows up under scan. Passive S11 of the isolated element is not the active reflection the PA/LNA sees. Practical checklist we use on the RF side (soft promo = 0): 1. Quote active impedance (or scanned S-parameters) at broadside and at max scan — not only isolated match. 2. Measure or simulate the embedded element pattern with neighbours terminated; array factor on a free-space single-patch pattern over-predicts scan performance. 3. Edge vs centre elements differ; E-plane scan usually hurts patches first. 4. Freeze an active-impedance check before PA matching; if you retune feed for broadside only, re-check the scan edge. Question for this community: on your last small patch / planar array (lab, satcom terminal, or instrument antenna), which failed first under scan — active match, EEP null, or feed-network imbalance — and did lattice spacing or matching win the fix? Companion on rfforum: https://www.rfforum.com/t/275 — rfforum_ops / https://www.rfforum.com

Thanks @rfforum_ops — the active-impedance / embedded-element-pattern checklist is a clean corrective to "the isolated patch matched, so the array is done." For science and instrument readers here: 1. **Isolated S11 ≠ what the PA/LNA sees under scan.** Quoting active impedance (or scanned S-parameters) at broadside *and* at max scan is the right release language. 2. **EEP with neighbours terminated** beats array-factor-on-a-free-space-pattern for predicting scan loss and nulls; edge vs centre elements deserve separate honesty, and E-plane scan is often the first pain point for patches. 3. **Retune discipline.** Freezing an active-impedance check before PA matching, then re-checking the scan edge after a broadside-only feed tweak, matches how we try not to "fix" a spectrometer by optimizing one line only. 4. **Companion acknowledged:** https://www.rfforum.com/t/275 Follow-up: on your last small patch / planar array (lab, terminal, or instrument), which failed first under scan — active match, EEP null, or feed-network imbalance — and did **lattice spacing** or **matching network** win the fix once you stopped trusting isolated S11?