Other

技术解读

以下内容由 GitRead 中文社区 编辑团队基于项目 README 与官方资料整理, 结合中文开发者的常见使用场景补充技术选型建议。具体以项目官方文档为准。

AERIS-10:用开源硬件把 X 波段相控阵雷达从实验室里拽出来

项目背景与痛点

相控阵雷达长期是"高墙内"的技术:一台 X 波段有源相控阵,动辄百万级预算、金属波导缝隙阵、液冷机柜、专用信号处理机。学术界想验证一个波束形成算法,往往卡在"没有硬件"这一步;无人机团队想给飞机加一双"毫米波之外的眼睛",要么买工业雷达模组被封闭固件锁死,要么自己从射频前端啃起。

AERIS-10 切的就是这个缝隙。它把 10.5 GHz 脉冲线性调频(LFM)相控阵做成一套低成本的开放式系统,并且直接给出 3 km 与 20 km 两个量级。这里藏着一个很硬的工程事实:按雷达方程,最大作用距离的四次方正比于平均功率、发射增益、有效孔径与相干积累时间的乘积。从 3 km 推到 20 km,距离变为 6.67 倍,意味着能量—孔径积要提升近 2000 倍。所以两个版本绝不是"换个功放管"的关系,而是天线口径、阵元规模、收发通道、脉冲积累策略乃至数据率的一整套重构。理解这一点,才理解这个项目真正的分量:它同时提供了"教学级小孔径"和"实用级大孔径"两个参照系。

核心技术揭秘

从架构上看,AERIS-10 走的是典型的"数字化波形 + 模拟波束形成 + 软件后处理"路线,这与动辄全数字 DBF 的豪华方案是两条路。全数字阵每元一套收发链路加 ADC,成本随阵元数线性爆炸;而用移相器在射频端合成波束,只需要一路(或少数几路)下变频与采样链路,把成本压到了可接受范围。

信号链大致如下:

graph TD A[LFM chirp 波形生成] --> B[10.5 GHz 上变频] B --> C[功分馈电网络] C --> D[移相器阵列-波束赋形] D --> E[T/R 收发前端] E --> F[目标回波] F --> G[下变频与 ADC 采样] G --> H[脉冲压缩-匹配滤波] H --> I[多普勒 FFT 与相参积累] I --> J{"CFAR 检测门限"} J -->|"超过门限"| K[点云输出] J -->|"未过门限"| L[作为噪声丢弃] K --> M[上位机可视化与航迹跟踪]

几个真正决定成败的技术点:

其一是脉间相参性。 LFM 脉冲压缩能拿到时宽带宽积量级的增益,把距离分辨率拉到 c/2B;但要做多普勒测速,就必须保证每个 chirp 的起始相位严格相参,本振与波形发生器共用同一时基。低成本方案最容易在这里翻车——时钟抖动与 PLL 锁定时序一旦松散,动目标就像被"抹掉"了一样。

其二是通道幅相一致性。 波束指向精度与旁瓣电平,直接取决于各通道的相位误差。10.5 GHz 对应波长约 28.6 mm,半波长阵元间距 14.3 mm,此时 1° 的相位误差约等于 0.08 mm 的电长度偏差。PCB 走线不等长、器件离散性、温漂都会引入误差,因此必然存在一张出厂标定的幅相校准表,且需要在工作温度区间内做补偿。这也是所有开源相控阵项目里最"不外传"的部分——AERIS-10 若把这套校准流程也开放了,价值甚至高于硬件本身。

其三是栅瓣与扫描角。 间距超过 λ/2 就会在大角度扫描时冒出栅瓣,把能量打到错误方向。阵元排布一旦定为半波长,扫描范围就基本被锁死在 ±60° 以内,这是物理约束,不是软件能补的。

其四是数据吞吐。 若把原始 I/Q 全推给主机,20 km 版本的采样率与通道数会瞬间打满 USB 或以太网。合理做法是在 FPGA 侧完成脉冲压缩与抽取,只上传压缩后的距离—多普勒矩阵。这一取舍决定系统能不能实时跑。

功能亮点与差异

第一,没有机械云台。电扫描意味着微秒级波束切换,可以做到边扫描边跟踪、多波束分时驻留,这是舵机云台雷达根本做不到的。

第二,波形可编程。LFM 的带宽、时宽、调频率、PRF 都暴露给用户,等于把"距离分辨率 vs 探测距离 vs 无模糊测速范围"的三角权衡交给开发者自己调。这对研究者远比一个封装好的 API 有价值。

第三,双档位形成梯度。3 km 版本适合桌面验证与算法原型,20 km 版本才谈得上外场试验。同一套软件栈跨两档硬件,代码复用率高。

第四,面向无人机开发者。这个定位很务实:无人机避障与地形感知要的是轻、便宜、无运动部件,而不是实验室级精度。

应用场景与落地建议

最现实的场景是高校实验室的教学与研究平台:波束形成、CFAR、微多普勒特征提取,都能在上面跑通闭环。其次是无人机感知原型、地面微动监测(桥梁、边坡)、以及低成本防撞。

上生产前必须过几道坎:

  • 合规优先。 10.5 GHz 属于 X 波段,与射电天文、无线电导航等业务存在频率划分重叠。任何外场辐射试验都应先在屏蔽室或暗室完成,外场需按当地无线电管理规定申请,不可默认"开源即可随意发射"。
  • 校准流程制度化。 上电预热、温度变化后重跑幅相校准,否则波束指向会漂。
  • PRF 与模糊折衷。 高 PRF 测速无模糊但距离模糊,低 PRF 反之,需按任务场景选定并做多 PRF 解模糊。
  • 算力前移。 把压缩、积累放到边缘端,主机只做点云与跟踪。

综合评价

优点:把 X 波段相控阵的成本拉到个人与小组可承受的区间;波形与处理链开放,具备真正的科研价值;电扫描带来的跟踪敏捷性是结构性优势;双档位设计让学习曲线平滑。

不足:模拟移相方案的天花板明确——波束数与多波束能力受限,无法像全数字阵那样做自适应零陷;幅相校准与热管理是隐性工作量,README 之外的"坑"不少;20 km 档对电源、散热、电磁兼容的要求会指数级上升;开源硬件项目的通病——文档与批次一致性往往跟不上硬件迭代。

一句话总结:它不是一件能开箱即用的商品,而是一副足够便宜的梯子。愿意花时间做校准、啃时序、调波形的人,能靠它真正摸到相控阵的门道;想插电就出点云的人,会被它的细节劝退。

关于

GitHub 原始描述(英文)

AERIS-10 is an open-source, low-cost 10.5 GHz phased array radar system featuring Pulse Linear Frequency Modulated (LFM) modulation. Available in two versions (3km and 20km range), it's designed for researchers, drone developers, and serious SDR enthusiasts who want to explore and experiment with phased array radar technology.

描述取自 GitHub 官方 API,保持仓库作者书写的原文。

简要分析

热度分
271
价值分
115
活跃状态
活跃
暂无主题

语言占比

Ada
C
C++
MATLAB
Makefile
PLSQL
Python
SMT
Shell
Tcl
TypeSpec
Verilog

贡献者

README

AERIS-10: Open Source Pulse Linear Frequency Modulated Phased Array Radar

Hardware: CERN-OHL-P Software: MIT Status: Alpha Features: Work in Progress Frequency: 10.5GHz PRs Welcome

AERIS-10 Radar System

AERIS-10 is an open-source, low-cost 10.5 GHz phased array radar system featuring Pulse Linear Frequency Modulated (LFM) modulation. Available in two versions (3km and 20km range), it’s designed for researchers, drone developers, and serious SDR enthusiasts who want to explore and experiment with phased array radar technology.

AERIS-10 Antenna Array

📡 Overview

The AERIS-10 project aims to democratize radar technology by providing a fully open-source, modular, and hackable radar system. Whether you’re a university researcher, a drone startup, or an advanced maker, AERIS-10 offers a platform for experimenting with beamforming, pulse compression, Doppler processing, and target tracking.

🔬 Key Features

  • Open Source Hardware & Software - Complete schematics, PCB layouts, firmware, and software available
  • Dual Version Availability:
    • AERIS-10N (Nexus): 3km range with 8x16 patch antenna array
    • AERIS-10E (Extended): 20km range with 32x16 dielectric-filled slotted waveguide array
  • Full Electronic Beam Steering - ±45° electronic steering in elevation and azimuth
  • Advanced Signal Processing - On-board FPGA handles pulse compression, Doppler FFT, MTI, and CFAR
  • Python GUI - User-friendly interface with map integration
  • GPS/IMU Integration - Real-time position and attitude correction
  • Modular Design - Separate power management, frequency synthesis, and RF boards

🏗️ System Architecture

AERIS-10 System Diagram

Hardware Components

The AERIS-10 main sub-systems are:

  • Power Management Board - Supplies all necessary voltage levels to the electronics components with proper filtering and sequencing (sequencing ensured by the microcontroller)

  • Frequency Synthesizer Board - Uses a high-performance Low Jitter Clock Generator (AD9523-1) that supplies phase-aligned clock references for:

    • RX and TX Frequency Synthesizers (ADF4382)
    • DAC
    • ADC
    • FPGA
  • Main Board containing:

    • DAC - Generates the RADAR Chirps
    • 2x Microwave Mixers (LTC5552) - For up-conversion and IF-down-conversion
    • 4x 4-Channel Phase Shifters (ADAR1000) - For RX and TX chain beamforming
    • 16x Front End Chips (ADTR1107) - Used for both Low Noise Amplifying (RX) and Power Amplifying (TX) stages
    • XC7A50T FPGA - Handles RADAR Signal Processing on the upstream FTG256 board:
      • PLFM Chirps generation via the DAC
      • Raw ADC data read
      • Hybrid Automatic Gain Control (AGC) — cross-layer FPGA/STM32/GUI loop
      • I/Q Baseband Down-Conversion
      • Decimation
      • Filtering
      • Forward FFT
      • Pulse Compression
      • Doppler, MTI and CFAR processing
      • USB Interface
    • STM32F746xx Microcontroller - Used for:
      • Power-up and power-down sequencing (see Power Management Excel File)
      • FPGA communication
      • Setup and Interface with:
        • Clock Generator (AD9523-1)
        • 2x Frequency Synthesizers (ADF4382)
        • 4x 4-Channel Phase Shifters (ADAR1000) for RADAR pulse sequencing
        • 2x ADS7830 8-channel I²C ADCs (Main Board, U88 @ 0x48 / U89 @ 0x4A) for 16x Idq measurement, one per PA channel, each sensed through a 5 mΩ shunt on the PA board and an INA241A3 current-sense amplifier (x50) on the Main Board
        • 2x DAC5578 8-channel I²C DACs (Main Board, U7 @ 0x48 / U69 @ 0x49) for 16x Vg control, one per PA channel; closed-loop calibrated at boot to the target Idq
        • GPS module (UM982) for GUI map centering and per-detection position tagging
        • GY-85 IMU for pitch/roll correction of target coordinates
        • BMP180 Barometer
        • Stepper Motor
        • 1x ADS7830 8-channel I²C ADC (Main Board, U10) reading 8 thermistors for thermal monitoring; a single GPIO (EN_DIS_COOLING) switches the cooling fans on when any channel exceeds the threshold
        • RF switches
  • 16x Power Amplifier Boards - Used only for AERIS-10E version, featuring 10Watt QPA2962 GaN amplifier for extended range

  • Antenna Arrays:

    • AERIS-10N (Nexus) - 8x16 patch antenna array
    • AERIS-10X (Extended) - 32x16 dielectric-filled slotted waveguide antenna array
  • Miscellaneous Components:

    • Slip-Ring
    • Stepper Motor and drivers
    • Cooling Fans
    • Enclosure

Processing Pipeline

  1. Waveform Generation - DAC creates LFM chirps
  2. Up/Down Conversion - LTC5552 mixers handle frequency translation
  3. Beam Steering - ADAR1000 phase shifters control 16 elements
  4. Signal Processing (FPGA):
    • Raw ADC data capture
    • I/Q baseband down-conversion
    • Decimation & filtering (CIC/FIR)
    • Pulse compression
    • Doppler FFT processing
    • MTI & CFAR detection
  5. System Management (STM32):
    • Power sequencing
    • Peripheral configuration
    • GPS/IMU integration
    • Stepper motor control
  6. Visualization (Python GUI):
    • Real-time target plotting
    • Map integration
    • Radar control interface

AERIS-10 Dashboard

📊 Technical Specifications

Parameter AERIS-10N (Nexus) AERIS-10X (Extended)
Frequency 10.5 GHz 10.5 GHz
Max Range 3 km 20 km
Antenna 8x16 Patch Array 32x16 Slotted Waveguide
Beam Steering Electronic (±45°) Electronic (±45°)
Mechanical Scan 360° (stepper motor) 360° (stepper motor)
Output Power ~1W×16 10W×16 (GaN amplifier)
Processing FPGA + STM32 FPGA + STM32

🚀 Getting Started

🧹 Repository File Placement Policy

To keep the repository root clean and make artifacts easy to find, place generated files in the following locations:

  • Published reports (tracked, GitHub Pages): docs/
    • Example: docs/AERIS_Simulation_Report_v2.pdf
  • Simulation-generated outputs (local, gitignored): 5_Simulations/generated/
    • Plots, scenario outputs, temporary analysis directories
  • FPGA/Vivado generated artifacts (local, gitignored): 9_Firmware/9_2_FPGA/reports/
    • VCD/VVP dumps, temporary CSVs, local report snapshots
  • Reusable FPGA automation scripts (tracked): 9_Firmware/9_2_FPGA/scripts/
    • TCL flows, helper scripts used by build/bring-up

Do not leave generated artifacts in the repository root.

Prerequisites

  • Basic understanding of radar principles
  • Experience with PCB assembly (for hardware build)
  • Python 3.8+ for the GUI software
  • FPGA development tools (Vivado) for signal processing modifications

Hardware Assembly

  1. Order PCBs: Production outputs are under /4_Schematics and Boards Layout/4_7_Production Files
  2. Source Components: BOM/CPL files are co-located under /4_Schematics and Boards Layout/4_7_Production Files
  3. Assembly: Use the schematics in /4_Schematics and Boards Layout/4_6_Schematics together with the production outputs above; a standalone assembly guide is not currently tracked
  4. Antenna: Choose appropriate array files for your target variant
  5. Enclosure: Mechanical drawings currently live in /8_Utils/Mechanical_Drawings

📜 License

This project is open-source but uses different licenses for hardware and software to ensure proper legal coverage.

Hardware Documentation

The hardware design files—including:

  • Schematics and PCB layouts (in /4_Schematics and Boards Layout)
  • Bill of Materials (BOM) files
  • Gerber files and manufacturing outputs
  • Mechanical drawings and enclosure designs

are licensed under the CERN Open Hardware Licence Version 2 – Permissive (CERN-OHL-P) .

This is a hardware-specific license that:

  • ✅ Clearly defines “Hardware,” “Documentation,” and “Products”
  • ✅ Includes explicit patent protection for contributors and users
  • ✅ Provides stronger liability limitations (important for high-power RF)
  • ✅ Aligns with professional open-hardware standards (CERN, OSHWA)

You may use, modify, and sell products based on these designs, provided you:

  • Maintain the original copyright notices
  • Distribute any modified designs under the same license
  • Make your modifications available in Source format

Software and Firmware

The software components—including:

  • FPGA code (VHDL/Verilog in /9_Firmware)
  • Microcontroller firmware (STM32)
  • Python GUI and utilities

remain under the MIT License for maximum flexibility.

Full License Texts

  • The complete CERN-OHL-P license text is in the LICENSE file
  • MIT license terms apply to software where not otherwise specified

Why This Change?

Originally, the entire project used the MIT license. The community (special thanks to gmaynez!) pointed out that MIT lacks legal protections needed for physical hardware. The switch to CERN-OHL-P ensures the project is properly protected while maintaining the same permissive spirit.

Note: This is an active development project. Some features are still in progress. Check the issues page for known limitations and upcoming features.

评论

暂无评论