6 ms·
The Adafruit Feather and FeatherWing System
- polishdude20 5y agoThe adafruit documentation is top notch! I've been working on a project for a thrust vectoring rocket using the same chip that's on the feather m4 (the SAMD 51) https://github.com/AdamMarciniak/CygnusX1 https://github.com/AdamMarciniak/CygnusX1 The schematics on the adafruit site helped me design my board and wire it all up properly!
- Bluestein 5y ago"Wouldn't it be great if, instead of collecting shields, HATs, PMODs, Clicks, Booster Packs, Props... you could have a cross-compatible platform? Something that doesn't force you into one chipset? and allows you to mix-and-match the microcontroller, wireless protocol, and functional extensions? Yeah, me too! That's why I created Feather. Feather is a flexible and powerful family of microcontroller main-boards (Feathers) and daughter-boards (Wings) with a wide range of capabilities."
- bestouff 5y agoObligatory: https://xkcd.com/927/ https://xkcd.com/927/
- BoorishBears 5y agoI've never gotten the obsession with prescribing form factors to breakout boards. What do I lose buying a generic breakout board for half the price of a branded shield/hat/wing and hooking it up on a $2 piece of protoboard or with some jumpers?
- dimatura 5y agoTime and effort?
- wdfx 5y agoYou haven't lost anything. It's about what others can gain. Meaning, those who don't (yet) know how to make their own boards or dont care how the interfaces work can still plug a couple of boards together and make a working system. The reductio ad adsurbum on this would compare these boards to PCI cards for your PC - you wouldn't expect the majority of PC users to have to hand assemble their GPU would you?
- skybrian 5y agoActually there are more beginner-friendly standards in the hobbyist electronic space. Using an i2c plug standard like Sparkfun’s Qwiic QT / Adafruit’s STEMMA QT (which are mostly compatible) avoids soldering, but you’re limited to the i2c parts that they have breakout boards for. https://learn.adafruit.com/introducing-adafruit-stemma-qt/sparkfun-qwiic https://learn.adafruit.com/introducing-adafruit-stemma-qt/sp...
- BoorishBears 5y agoSounds like you misunderstand what a breakout board is? Like it's literally the shield minus a set form factor. It takes 0 more knowledge. It's still plugging boards together, still runs the same code. Just not in a shape that will cover up every single pin you have. Which is something that makes things harder for beginners if anything.
- dimatura 5y agoI don't think it takes "0" more knowledge. Maybe 2-5% more knowledge? (In some made-up subjective scale). If you buy a feather and a wing you know they'll work together (I haven't looked up every feather-wing combination, but the only exception I've seen is large OLEDs which technically work with low-powered feathers, but not very well - and they spell this out clearly in the product description). Not necessarily the case for a random MCU and breakout board, and figuring out needs at least a little bit of knowledge. Same for connecting the boards. There's pretty much one way to connect a feather and a wing so you don't have to think about 5V/3V, SPI pins, RX/TX, etc. Or weird small connectors. Again, not super hard to figure out with arbitrary breakouts, but requires more than 0 knowledge.
- skybrian 5y agoForm factors matter for electronics that need to fit into small spaces. It’s a tradeoff between size and ease of assembly. Also, vendors want to make their microcontroller boards compatible with their breakout boards, which means supporting MxN combinations without having to do testing and write documentation for all of them.
- BoorishBears 5y agoYou're actually making my point Right now I can get the M0 mentioned in the article in any size from "a little bigger than my thumb" to the size of my hand. The breakouts are almost universally smaller than those common denominator shields since they don't have to cover up every pin on the board. But I don't follow your second sentence. You still need the same amount of testing and documentation with the above approach. All you've changed is the connection style from "jumpers into headers" to "pins into headers". The most you save is "plug wire X into pin Y", but in exchange you had to add 15 odd extra pins to the breakout to satisfy the packaging requirements. Not exactly saving effort there...
- daly 5y agoWouldn't it be great if feathers, PMODs, etc. all used ROS2 to provide publish/subscribe and services so that anything could "just work"?
- qbasic_forever 5y agoFeathers are primarily microcontrollers--Atmel AVR, ARM Cortex M0/M4, ESP32, etc. Stuff with kilobytes of memory and low megahertz of speed. None of them can run ROS or any Linux-based OS/RTOS hybrid.
- voxadam 5y agomicro-ROS[1] is an option for resource constrained devices. [1] https://micro.ros.org/ https://micro.ros.org/
- Robotbeat 5y agoROS2 isn’t exactly lightweight.
- Brian_K_White 5y agogod no
- Brian_K_White 5y agoI love it. https://github.com/bkw777/MounT https://github.com/bkw777/MounT
- kens 5y agoFeather is cool but note that this is from 2017.
- Bluestein 5y agoNoted. Should have titled as such ... :(
- neur4lnet 5y agoIs there a reason that the main board is a feather and the daughter boards are wings? I would have expected 1 wing to have many feathers, not the other way around.
- ubertaco 5y ago"Featherwing" is a bit more unambiguous to google than "Wingfeather"[0] at this point. [0] https://en.wikipedia.org/wiki/The_Wingfeather_Saga https://en.wikipedia.org/wiki/The_Wingfeather_Saga
- Bluestein 5y ago... That ... confused me too, must confess.-
- cjdaly 5y agoif you want to be extra confused, look at the HalloWing: https://www.adafruit.com/product/3900 https://www.adafruit.com/product/3900 https://www.adafruit.com/product/4300 https://www.adafruit.com/product/4300 it's a feather mainboard, but with the 'wing' nomenclature.
- igneo676 5y agoThey've had the feather boards for a while but not the wings. After they needed to expand the brand, they were probably a bit limited in choices by the original name
- stronglikedan 5y agoAnd "vane" and "barb" just don't sound as nice as "wing".
- detritus 5y agoScanning quickly down the page to the first schematics as I did, I thought "but this thing's tiny? and so arbitraily-sized!", so scrolled back up a wee bit. Ah, of course. Inches. Stuff this scale should be drawn in millimetres, imho. Keep inches for tables and chairs.
- powerpiglet 5y agoIt's meant to be breadboard-compatible, and breadboard pin sockets are normally spaced at 0.1 inch. You can see in the first schematic that it's 0.9" by 2.0", which gives you 9x20 hole positions.
- nazrulmum10 5y agoAre you interested in making something that works with the Adafruit Feather & FeatherWing system?
- chasd00 5y agoI’m have the stm32 Feather on my desk right now. I use Micropython and it works out just fine. I prefer a raspberry pie zero w though honestly. I can ssh right to it and edit python with vim right on the device. I know the pi isn’t “hard real time” but the servos and sensors I’m using on a rocket don’t seem to care.
- krastanov 5y agoPower consumption and sleep capabilities are also drastically different, not just the hard-realtime. After all the RPi Zero W runs a complete "desktop" OS, while the feathers run a single compiled executable directly on the hardware.
- Ardon 5y agoFirst time I ever saw one of these was in this neat little project: https://github.com/joeycastillo/The-Open-Book https://github.com/joeycastillo/The-Open-Book I'm always delighted to see new open hardware projects, they always feel rare to me, and I'm stoked there are things like the feather making it marginally easier.
- deregulateMed 5y agoI give my EE friends a weird look when I see they bought stuff from Adafruit. I understand if you are a casual trying to do embedded for the first time, but these people know what pins are. They know what MCUs are. They know what power and ground are.. Not sure how they come to the conclusion to spend 10x more.
- psychomugs 5y agoThis is tantamount to saying that every degree-holding MechE should do all of their car maintenance and home improvement and design their own products. Genuine passion for engineering and a healthy dash of imposter syndrome impel me to handle as much of this as I can, but I don't hold it against others who don't.
- tonyarkles 5y agoI'm not sure why you're being downvoted. You're misguided, but have reasonable questions! Here's the deal for me, cost-wise. I can go on Sparkfun, Adafruit, Digikey, Arrow, etc and get these known compatible pieces of essentially Lego that already have firmware support/libraries ready to go. Digikey (who stocks both Adafruit and Sparkfun parts) will have them on my doorstep tomorrow morning. Using the existing libraries, I'll have the a skeleton of a system up and running by tomorrow afternoon. I'll have the prototype up and running in 3 days. Then, if everything seems to look like it's going to work well and I want to pursue the project further, I'll fire up Eagle or CircuitStudio and lay out a board. Upload it to Macrofab and wait 3 weeks for my fully assembled boards to arrive. And then port the firmware from my prototype over to the assembled boards. Or rewrite the firmware, depending on the quality of the specific sensor libraries. It's all about bootstrapping the process. When I get a board from Adafruit or Sparkfun, I've got a pretty good belief that it's going to be high quality and fit well within their existing ecosystem of parts and libraries. Building a prototype out of those parts helps de-risk the project and accelerate the project by cutting out most of the up-front dicking around to get it working. Plus, the vast majority of these boards also have schematics and part numbers provided. When I go to design a real board, I'll use those as references.
- zeta0134 5y agoCould it be curation? I'm still a novice myself so this comes from a place of genuine ignorance, but I find most of the channels for parts and whatnot to be overwhelmingly complex. Adafruit is dead simple to search.