Software-defined radio and instrument-grade measurement grew up in different rooms. The open ecosystem gives an engineer every sample and no absolute reference; the instrument gives an absolute reference and, usually, no way in. This handbook is about the boundary between them.
It sets out what a software-defined receiver is and where its programmable edge falls, derives what real-time analysis guarantees that a swept receiver cannot, documents the SoapySDR hardware abstraction layer in enough detail to write acquisition code from, reviews the ICX-FieldHawk against seven requirements derived before any product is named, and then walks six signal chains built in GNU Radio against a calibrated front end. It closes with the practice, the troubleshooting and the quick reference a working engineer needs on the bench.
What is in it
Part I. The field
- 2. Why software-defined radio arrived in measurement
- 3. Anatomy of a software-defined receiver
- 4. Where the conversion happens: receiver architectures
- 5. What separates a reading from a measurement
- 6. Real-time analysis, and what gap-free actually guarantees
- 7. SoapySDR in depth
- 8. What the abstraction deliberately leaves out
Part II. The ICX-FieldHawk, reviewed
- 9. The family: form factors and frequency tiers
- 10. The front end and the published performance
- 11. From IF to samples: conversion and digital processing
- 12. The real-time engine
- 13. IQ capture, streaming and triggering
- 14. The measurement set, and what it costs
- 15. Reference and timing
- 16. Where this instrument is not the answer
Part III. Building on it: GNU Radio
- 17. How a flowgraph actually works
- 18. The source block, parameter by parameter
- 19. Getting the environment right
- 20. Six chains, drawn and explained
- 21. The arithmetic that has to close
- 22. Making a flowgraph produce a defensible number
Part IV. Applications
- 23. Ten applications, reviewed
- 24. Conclusion
Part V. Practice and reference
- 25. Measurement practice
- 26. Troubleshooting
- 27. Proving the amplitude path, and a reproducibility checklist
- 28. Quick reference
- 29. Definitions, symbols and further reading
Who it is for
RF and systems engineers building measurement or monitoring systems on open software. Researchers and teaching staff who need a result that survives peer review rather than a demonstration. Product architects deciding how much of a receiver to build. Test engineers who already own an analyzer and want to reach the samples underneath it.