Stop breadboarding and soldering – start making immediately! Adafruit’s Circuit Playground is jam-packed with LEDs, sensors, buttons, alligator clip pads and more. Build projects with Circuit Playground in a few minutes with the drag-and-drop MakeCode programming site, learn computer science using the CS Discoveries class on code.org, jump into CircuitPython to learn Python and hardware together, or even use Arduino IDE. Circuit Playground Express is the newest and best Circuit Playground board, with support for MakeCode, CircuitPython, and Arduino. It has a powerful processor, 10 NeoPixels, mini speaker, InfraRed receive and transmit, two buttons, a switch, 14 alligator clip pads, and lots of sensors: capacitive touch, IR proximity, temperature, light, motion and sound. A whole wide world of electronics and coding is waiting for you, and it fits in the palm of your hand.
Get the only spam-free daily newsletter about wearables, running a "maker business", electronic tips and more! Subscribe at AdafruitDaily.com !
Nice to see Dave finally come around to Open Source Hardware.
@alan – we’re pretty sure the EEVblog (dave) has consistently spoke highly of OSHW (and so has amp hour with chris).
@Alan I’ve always been a fan of OSHW. In fact, I was publishing open hardware designs 20 years ago, long before the term was even coined.
BTW, the Pinguino project is what prompted me to do the video. http://pinguino.cc/
They claim it’s OSHW, and use the logos and even link to the definition. But they don’t let you download the original CAD files. Just a PDF of the schematic.
Muy buen vídeo, ideal para la difusión del hardware libre y todo este movimiento que cada día toma más impulso. Saludos desde Argentina.
@dave, good to see you here!
yah – while CAD files are great some folks do not always include them. a pdf of the schematic is sorta “ok”, sometimes, but not really 🙁 — board files always better of course. since pinguino is playing in the OSHW arduino world and practically using the name arduino they should do what the arduino team does at the minimum. that’s the “spirit” as you said in your vid, that’s what most do. pinguino should too.
that said, maybe they just didn’t get to it yet, but it’s been a few months huh? even sometimes we forget to upload things but someone always reminds us 🙂 having github for each product is making things easier (and our new site features). we’ve made it clear everything we do is OSHW so it’s not “if”, only when if something isn’t posted immediately for us. usually it’s within a few hours of launch now.
we see you asked them, so they should (hopefully) reply!
if they don’t, they’re likely going to make a lot of people angry with them who do OSHW or customers who buy this because it’s advertised as OSHW.
they say “Pinguino is an Open Source and Open Hardware Project.”
I’ve read several of the OSHW definitions but don’t understand the distinction between electronic “hardware” and hardware like say an open source pair of pliers. Are they both incorporated in the OSHW definition? If so where do non-electronic tools and mechanisms go? Thanks.
@josh, 3d printed items and mechanical files are likely going to be debated a lot as OSHW evolves. at this time since there isn’t open source pliers we don’t have ways to test this.
we think right now it’s possible to release OSHW pliers, you could put the files up on thingiverse under a license that is OSHW compliant, allow others to make and sell them, and share back/credit.
what isn’t quite clear yet is if and how the materials used matter. if our pliers are made from metal it’s not clear how that process will be “open sourced” or if it matters, it might not.
I completely agree with what Dave said. I’m getting ready to sell some kits and call them open hardware, and with that will be the "real" schematic, cad, and firmware files. I have thought very carefully about this and I’m sold. I strongly agree that you need to follow the definitions of OSHW if you are going to label your stuff with the logo. My 2 cents here: http://thecustomgeek.com/?p=135
@jeremy and @dave – phil emailed the pingduino folks asking what’s up, hopefully they’ll do an update to the site(s) soon!
btw, the chipkit32 folks *do* OSHW nicely 🙂
Open source EAGLE project for the chipKIT Uno32. Created in EAGLE v5.11
Thanks for the response. I am really interested in reviving old patents specifically small tools and larger devices like mechanical duplicators and such. Most of these could be 3D printed and “lost plastic” cast. I’ll look into it more, sometimes us less electronic/computer types feel alienated from the OS world. Thanks Josh @Protobotind
@dave – olimex emailed me, the files will be posted soon.
we are on vacation now, next monday i’ll be in office and we tell out it stuff to upload our web with the eagle files
this is very new product and our web pages are still not complete 🙂
> even sometimes we forget to upload things but someone always reminds us 🙂
It would be great if you find the time to upload the design files for your OLED display board
Excellent, thanks Phil.
And thanks to Olimex for playing by the rules, well done.
I’m really interested in seeing what happens with non-electronic physical hardware, like the above-mentioned pliers.
There doesn’t seem to be any “good” format for sharing that kind of stuff, because there are so many formats, and the manufacturing has so many (varied) iterations.
For example, I have a little model steam engine I designed and built, and which I’d like to release as open-source hardware. I worked mainly from 2-D working drawings (autocad DWG). A few of the pieces were, in whole or in part, CNC machined, but not all of them. I could release the g-code for said parts, but they wouldn’t get anybody very far, because without the context of the entire project, they are useless. With the exception of 4 mounting screws and a bearing, the whole thing is custom-made, so a BOM on its own would be meaningless as well.
I’m hoping that this topic is discussed at the OHW summit, because I’m currently a bit lost as to how to share such a project.
@Markus Gritsch – these are all located on github:
Glad to hear another voice. I looked at Thingiverse per Adafruit and didn’t see an applicable format for organizing mechanical components or assy’s. Having come from the aircraft world my gut says organize along patent office codes and then projects with part and assy #’s with .STL’s and another in some editable format. I’d be glad to co-write the convention… I would probably even go as far as to link prior art, assy dwgs.etc. I have no idea how to publish or disseminate this info. It seems like Thingiverse, Ponoko and Materialise have a Bias towards their own manufacturing methods.
There is now some debate over at the EEVblog over whether or not it is compulsory to use a “share-alike” (Copy left) license under the OSHW definition?: