carl9170fw VS rpitx

The carl firmware at https://github.com/chunkeey/carl9170fw should put that argument to rest. That is Wifi firmware source code for the Wifi I currently use.

Easily changed likely means there's a physical knob somewhere that you could accidentially poke as a layperson.

Not that you get a three year CS education, figure out how your distribution packages dependencies, install the correct embedded toolchain (good luck), find out exactly which chip is in your device, fetch the proper firmware source code in the right version, build the thing, figure out how to flash the result onto the chip / read the Linux kernel sources to figure out the filename inside /lib/firmware. That's not easy.

Even if this entire process was packaged (it is--see <https://packages.debian.org/sid/firmware-linux-free>), it probably still doesn't count (or at least shouldn't count) as "easily" changed.

There are some cards with open source firmware, you might be able to modify it to do something like that.

https://github.com/chunkeey/carl9170fw/

As someone with a HackRF PortaPack knockoff I got from ebay, I would agree that SDRs are better and cheaper than ever before. However, I think the average person will struggle with using a HackRF for more complex projects. I've used URH before, and while useful, it can be intimidating for beginners.

Also, while I like the RTL-SDR (and the price tag!), you can't transmit with it. While this isn't a deal breaker to everyone, if you'd like to clone a garage door remote, for example, you need to be able to transmit. While you could use something like a raspberry pi and rpix [0], but I think it is more work than it's worth for many. Also, multiple RTL-SDRs are required for higher bandwidth applications like ASTC TV or trunked radios.

With the flipper, I think the main draw for most is the point-click-done nature. Include the Android/iOS app and it makes it easy to configure on the go without a computer. The expandability is one of the main feature that will increase adoption over time compared to the HackRF+PortaPack which, from what I saw in the past, lacked longer-term support and regular updates and new features.

[0] https://github.com/F5OEO/rpitx

HackRF One is an option. There are a number of others. Legality varies by country/frequency/power level.

Can also make a Raspberry Pi act as a transmitter (https://github.com/F5OEO/rpitx), which could hit the zwave frequency but not the zigbee one. (Also, make sure to put a low pass filter on it.)

The warning at https://github.com/F5OEO/rpitx#hardware suggests a bandpass filter will be needed but has no additional info. https://github.com/F5OEO/rpitx/issues/40 looked promising but is closed.

On a similar path, you might look at: rpitx

RF transmitter for Raspberry Pi With this project you can turn your Raspberry Pi into an RF transmitter with only a filter to avoid interferences.

RPITX is the spiritual successor of your project!

https://github.com/F5OEO/rpitx

And it does work with nearly every RPi.

And unlike only doing FM (97MHz-108MHz), it can emit from an IQ datastream from 10KHz to 1.5GHz.

Hey everyone, I've recently discovered that the Raspberry Pi can act as a radio tranceiver, and am hoping to use it for security research. While projects such as rpitx act as a great tech demo, they don't offer me the modularity/parametrization I was hoping for. Ideally the end state for this would be a cheaper/less effective HackRF.

The RPITX project supposedly can generate signals up to 1.5GHz with an unmodified Pi, though, which is interesting... a true spectrum analyzer needs a receiver end, though.

če si vešč z linuxom (no z GNU-linuxom da ne razjezim folka) pa najdeš en raspberry pi, ti lahk to pomaga https://github.com/F5OEO/rpitx