菜单
Use when the user wants to receive or demodulate a specific signal — build, validate, run, and verify a receiver pipeline, then save it as a reusable, GRC-openable flowgraph.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a receiver runs but produces no output, noise, or the wrong result — systematically locate the fault instead of guessing, using render and measure to see the problem.
Use ONLY as a last resort when no Marconi tool or vocabulary block can express the task — write a Python script against the marconi library, run it, and report the capability gap.
Use when the user wants a test signal or a simulated RF environment with no hardware — translate intent into a scene and register it as a persistent simulated device.
Use when the user wants to know what signals are present — characterize a capture or a simulated device's spectrum (PSD, signal detection, spectrogram) and summarize what's on the air.
Use when the user wants a closed-loop transmit-then-receive experiment in simulation — transmit a capture into a simulated device's scene and receive it back to confirm the link.
| name | build-receiver |
| description | Use when the user wants to receive or demodulate a specific signal — build, validate, run, and verify a receiver pipeline, then save it as a reusable, GRC-openable flowgraph. |
Turn a target signal into a working receiver. The method below is general; FM voice and an unmodulated carrier are shown as two worked examples so the shape transfers to modulations the demo doesn't cover.
measure. Compute the offset from the capture's center: center_offset = target_freq − capture_center_freq.list_blocks. Compose only from these types; check each block's input/output dtype ('c' complex, 'f' float) so connections match.freq_xlating_lowpass to shift the target to baseband and decimate. Choose decimation so the post-decimation rate is ~2–3× the signal bandwidth; set cutoff ≈ signal_bandwidth and transition ≈ cutoff/2.validate_pipeline(pipeline) and fix every issue (each names the block and field) before running.run_pipeline(pipeline); check status == "ok".save_pipeline(pipeline) and export_grc(pipeline) so the user keeps a reusable receiver they can open in GNU Radio Companion.Channelize so the post-decimation rate equals the FM quad rate (a multiple of the audio rate), then demodulate to a WAV:
freq_xlating_lowpass (decimation chosen so e.g. 2 MHz / 20 = 100 kHz = quad_rate; cutoff ≈ 8 kHz, transition ≈ 4 kHz)nbfm_rx with audio_rate=25000, quad_rate=100000 (quad_rate must be an integer multiple of audio_rate)wav_sink (sample_rate=25000)Connections: src → chan → demod → audio.
There is no demodulator here — receiving a carrier means channelizing it to baseband and confirming it:
freq_xlating_lowpass (narrow cutoff, e.g. a few kHz) → file_sink (give the sink a path ending in .cf32).run_pipeline, then bridge the raw output into an analyzable capture: take the sink path from the run's artifacts[0] and call load_capture(path, sample_rate=<post-decimation rate>, center_freq=<target_freq>) (raw .cf32 needs the sample rate supplied).measure(capture_path, center_freq=<target_freq>) (or render a spectrogram) to confirm the carrier sits where expected with the predicted SNR.This proves the channelizer/offset logic independently of any demodulator — the same skeleton as example A with the demod stage removed. The run → load_capture → analyze bridge is general: that's how you inspect any pipeline's file output.
AM, SSB, and digital (OOK/PPM/FSK) demodulators are not in the v1.0 vocabulary. If the target needs one, report the gap and switch to the escape-hatch skill — do not force an FM demodulator onto a non-FM signal.
measure or spectrogram the channelized output and confirm the carrier/structure is where you expect.