I was about to say, “coolnamesalltaken already has a pretty small one,” but you are them! I’m definitely excited by this project, I have something I wanted to add ADS-B integration to and this looks like an even better option!
As for a question, how do you balance low power with performance? Is there a target range or use case to decide the performance envelope?
Ha, it's very fun to see that people know about the project!
ADSBee 1421's very low power consumption is determined by its architecture. Where ADSBee 1090 has a discrete RF frontend with multiple power hungry LNAs and a power detector chip, plus a dual core RP2040, an ESP32 S3 module, and a CC1312, ADSBee 1421 just has an LR2021 chip and a CC1314. A single LNA on the ADSBee 1090's RF frontend actually draws about as much power as the whole m1421!
The tradeoff is that we have fewer CPU cycles available for crunching packets compared to the ADSBee 1090, and the LR2021 has some quirks that result in it only being able to receive ADS-B packets in its maximum dynamic range configuration (so we support Mode S DF17 only, no squitter packets or altitude / surveillance replies like you get with DF4/5/11). That said, this has been plenty for customers who are looking for an aircraft detect and avoid solution plus UAT traffic / weather.
Based on our testing so far, ADSBee m1421 is well suited to general aviation applications (portable flight bag / cockpit avionics), drone flight controllers (aircraft detect and avoid), and anything that needs to be low cost or easy to run off a solar panel or little battery.
For customers looking to build something like an airport ground station, where they want all squitter and extended squitter packet formats and a higher max packet rate, we still recommend the ADSBee 1090 three-MCU architecture.
We're focusing on embedded applications with ADSBee m1421 applications right now but it's definitely tempting to roll m1421 into a smaller flight bag device. It's something we might get back around to once we have Winglet off the ground.
As for a question, how do you balance low power with performance? Is there a target range or use case to decide the performance envelope?
ADSBee 1421's very low power consumption is determined by its architecture. Where ADSBee 1090 has a discrete RF frontend with multiple power hungry LNAs and a power detector chip, plus a dual core RP2040, an ESP32 S3 module, and a CC1312, ADSBee 1421 just has an LR2021 chip and a CC1314. A single LNA on the ADSBee 1090's RF frontend actually draws about as much power as the whole m1421!
The tradeoff is that we have fewer CPU cycles available for crunching packets compared to the ADSBee 1090, and the LR2021 has some quirks that result in it only being able to receive ADS-B packets in its maximum dynamic range configuration (so we support Mode S DF17 only, no squitter packets or altitude / surveillance replies like you get with DF4/5/11). That said, this has been plenty for customers who are looking for an aircraft detect and avoid solution plus UAT traffic / weather.
Based on our testing so far, ADSBee m1421 is well suited to general aviation applications (portable flight bag / cockpit avionics), drone flight controllers (aircraft detect and avoid), and anything that needs to be low cost or easy to run off a solar panel or little battery.
For customers looking to build something like an airport ground station, where they want all squitter and extended squitter packet formats and a higher max packet rate, we still recommend the ADSBee 1090 three-MCU architecture.
A normal non ADS-B iPad GPS flight module is almost 10% the price of the Sentry
https://www.garmin.com/p/645104/
We're focusing on embedded applications with ADSBee m1421 applications right now but it's definitely tempting to roll m1421 into a smaller flight bag device. It's something we might get back around to once we have Winglet off the ground.