Basics of RF Emissions Debugging
How to fix a failed test
Presented by Alex Whittemore for the Hackaday Remoticon 2020 workshop series�https://hackaday.io/project/175080-remoticon-basics-of-rf-emissions-debugging�alex@alexw.io https://www.alexwhittemore.com
These slides: https://docs.google.com/presentation/d/1QJ2Pu3y-F7zJg2ZN3TOdezDzjAVtaXPsHZbvoPqMlZ8/edit?usp=sharing
Background info
Software setup instructions/background are at https://hackaday.io/project/175080-remoticon-basics-of-rf-emissions-debugging/log/185818-software-setup-notes
We’ll need to install/set up:
Workbench Materials
Your workbench should include the following:
Software setup: SDR
We’ll make use of the following SDR software:
DragonOS LTS includes these out of the box; here’s a VirtualBox VM �ready to go.
VirtualBox performance is marginal: If you can, import this VM into�Parallels Desktop (on Mac) or VMWare Workstation.
Software setup: TinyFPGA
TinyFPGA tooling setup is (relatively) painless.
What is RF Compliance?
Electronic devices emit signals, intentionally or unintentionally, that may interfere with other devices:
FCC part 15 Subpart B governs “Unintentional Radiators” - Electronic devices that may cause accidental interference. ��FCC part 15 Subpart C governs “Intentional Radiators” - devices that �specifically implement wireless radios to broadcast RF energy.
How does testing work?
And then?
Whoops, you failed.
And then?
Whoops, you failed.
And then?
… Or did you?
And then?
Well, not this mode, anyway.
So what do we do about it?
Near Field Probing (magic wand method)
(This is what we’ll be doing)
Near Field Probing (Expensive toys method)
Demo: Using expensive gear
Demo: Building a probe and using cheap gear