Radio Frequency (RF) & Wireless Design

In my previous post I categorized many forms of wireless technologies that were available for the embedded CPU Raspberry Pi 'hat' add-on boards.

In this post I have decided to focus on just one form of RF and Wireless add-on mezzanine Arduino 'Shield' boards from QRP (ham radio term meaning low power) Labs.

https://www.qrp-labs.com/uarduino.html

The reason is that I found there are just as many shield add-on boards that use RF and Wireless technologies for Arduino as there are for Raspberry Pi, so if you are looking for a RADAR version for Arduino its more than likely to be out there. https://www.fierceelectronics.com/components/arduino-gets-its-first-radar-shield-board

The major consideration for choosing a particular platform is the bandwidth in Mega-bits-per-second (Mbps or Mb/s) that you will need. For example if you only need low speed USB at 1.1 Mbps then Arduino will work fine. However if you need High Speed USB2.0 at 480 Mbps then Raspberry Pi is your better choice.

Another consideration is what programming language that you prefer to use. With Arduino it most certainly is C and possibly BASIC, but don't expect Java. This will require an embedded CPU such as the Raspberry Pi. Now there are exceptions like Python, but only one for Arduino, so don't expect many choices for the embedded MCU Arduino as operating systems go.

Another consideration is graphics. For Arduino you will be limited to very small graphic displays with their own embedded graphic MCU or character type displays. If you want full resolution computer style graphics, then you will be pushed to go to Raspberry Pi again.

So why Arduino at all ? Well power consumption for one. Raspberry Pi is not known for its low power modes. So if you are looking for something that is portable and battery operated, then Arduino fills the bill better.

Another reason is simplicity for learning. Arduino is much easier to learn and is a better starting choice for the beginner to embedded programming as a node. Moreover knowing how embedded MCUs work is a better stepping stone for understanding from the bottom up design approach. With an understanding of the smaller elements in a system, System Architecture for larger designs later is much easier.

So although this article is not as focused on the Wireless and RF side of things, I hope that it has been helpful in understanding why each platform has specific uses and merits. And that choosing the right platform as embedded MCU or embedded CPU can make your Wireless and RF project development less stressful.

Any interest in these Shield mezzanine boards ? Please comment below !