Podcasts about arduinos

In this episode, we are joined by Everson Siqueira of Geek Detour. Brought to you by PCBWay (https://jle.vi/pcbway) and OctoEverywhere (https://octoeverywhere.com/welcome?id=podcast).Everson's career is a fascinating blend of creativity, innovation, and technology. Starting his journey in Electronics and Advertising, he worked as a Web Designer and Programmer for tech giants like AOL and Yahoo! in Brazil, creating CD-ROMs, Flash games, and iOS apps.After relocating to Spain, Everson pursued a Master's in 3D Game Design, marking a turning point that deepened his love for creative technology. This passion inspired the launch of his original YouTube channel, "YouHaveAniPad," which later transformed into "Geek Detour." Today, "Geek Detour" focuses on the incredible world of 3D printing, Arduinos, and maker culture, showcasing Everson's journey as a tech enthusiast and innovator.In this episode, Everson shares his unique career path, insights into 3D printing and Arduino projects, and how his background in game design influences his maker mindset.

Today on Elixir Wizards, indie developer Lucas Sifoni shares his experience prototyping a remote-controlled terrestrial telescope using Elixir, Nerves, Rust, and various hardware components. Lucas explains the basic components of a telescope, the challenges he faced during the development process, and the benefits of using Elixir and Nerves for hardware projects. Lucas emphasizes the importance of simulating hardware components and testing assumptions before working with physical devices, as well as the value of literate programming and executable blog posts for documenting and sharing the process. Lucas encourages listeners to explore Nerves and build their own hardware projects. He also gives a shout-out to the Nerves core team for their incredible work. Topics discussed in this episode: Challenges in optimizing wiring and PCB design for the prototype Benefits of Elixir and Nerves for hardware projects Communicating with Arduinos using serial connections and pattern matching Leveraging binary pattern matching and construction in Elixir for hardware Balancing educational value and real-world usability Learning CID software and parametric design for 3D printing components Growing interest in Nerves and hardware projects within the Elixir community Simulating hardware components and testing assumptions before physical implementation Literate programming and executable blog posts for documenting hardware projects Using Elixir's interoperability with Rust for performance-critical tasks Elixir's low fragmentation and high-quality libraries for various domains Potential for using Livebook in hardware projects, with some limitations Encouraging listeners to explore Nerves and build their own hardware projects Links mentioned https://lucassifoni.info/ https://www.rust-lang.org/ https://go.dev/ https://lisp-lang.org/ https://ubuntu.com/ https://hexdocs.pm/iex/IEx.html https://nerves-project.org/ https://lucassifoni.info/blog/prototyping-elixir-telescope-code-beam/ https://github.com/Lucassifoni/oiseaux https://hexdocs.pm/phoenixliveview/Phoenix.LiveView.html https://www.raspberrypi.com/ https://mangopi.org/ https://store.arduino.cc/products/arduino-nano https://elixir-circuits.github.io/ https://www.erlang.org/doc/apps/runtimetools/scheduler.html Binary pattern matching in Elixir with PNG parsing example https://zohaib.me/binary-pattern-matching-in-elixir/ Lucas' Code Beam Talk: https://www.youtube.com/watch?v=q7bleFzA11c https://github.com/membraneframework-labs https://github.com/talklittle/ffmpex https://studio.blender.org/training/3d-printing/ https://www.autodesk.com/products/fusion-360/personal https://en.wikipedia.org/wiki/Parametricdesign https://www.exem.fr/ https://www.kikk.be/exhibitions/collectif-lab212-nicolas-guichard-beatrice-lartigue/ https://livebook.dev/ https://github.com/elixir-nx/bumblebee https://github.com/rusterlium/rustlerhttps://www.youtube.com/watch?v=q7bleFzA11c Special Guest: Lucas Sifoni.

This week's Electromaker Show is now available on YouTube and everywhere you get your podcasts! Welcome to the Electromaker Show episode 158! This week we dive into uncharted Raspberry Pi hardware territory, get giddy over the M5Stack Cardputer ESP32 devkit, Stretch our imaginations with two deformable PCB projects, explore solderless pcb prototyping and much more! Tune in for the latest maker, tech, DIY, IoT, embedded, and crowdfunding news stories from the week.   Watch the show! We publish a new show every week. Subscribe here: https://www.youtube.com/channel/UCiMO2NHYWNiVTzyGsPYn4DA?sub_confirmation=1 We stock the latest products from Adafruit, Seeed Studio, Pimoroni, Sparkfun, and many more! Browse our shop: https://www.electromaker.io/shop Join us on Discord! https://discord.com/invite/w8d7mkCkxj​ Follow us on Twitter: https://twitter.com/ElectromakerIO Like us on Facebook: https://www.facebook.com/electromaker.io/ Follow us on Instagram: https://www.instagram.com/electromaker_io/ Featured in this show: Faboratory at Yale stretchable Arduinos embedded in soft robots CNLohr PolyLMN testing Raspberry Pi 500 coming soon? New Pimoroni Pico Plus 2 W features as-yet-unannounced RM2 wifi module Arduino Alvik Giveaway winner announced! M5Stack Cardputer: The Hacker's Dream Jumperless V5 Update ESP32 Rainbow ZX Spectrum on Crowd Supply Solder Free PCB prototyping Opulo website for Lumen Pnp Jeff Geerling's voice cloned by Elecrow

In this episode we meet Pat Hensley, W5WTH, a prolific designer and project builder.  Pat has made several intersting radio and non-radio related electronic projects and he features them on his blog site WhiskeyTangoHotel.Com Some of Pat's projects are very useful and some are just plain fun.  Many projects are a blend of hardware (Arduinos, Raspberry Pis, etc) and software (c, Python, etc).  Pat publishes all of his source code for us all to learn from.  If you want to be inspired to build your first project you have come to the right place. 

This week's Electromaker Show is now available on YouTube and everywhere you get your podcasts! Welcome to the Electromaker Show episode 153! Retro Trolley racing, Arduino Plug and Make Giveaway, more RP2350 goodness and hacking terrible but good Walmart LED panels! We also announce the winner of our ongoing Blues LoRaWAN Starter Kit competition! Tune in for the latest maker, tech, DIY, IoT, embedded, and crowdfunding news stories from the week.   Watch the show! We publish a new show every week. Subscribe here: https://www.youtube.com/channel/UCiMO2NHYWNiVTzyGsPYn4DA?sub_confirmation=1 We stock the latest products from Adafruit, Seeed Studio, Pimoroni, Sparkfun, and many more! Browse our shop: https://www.electromaker.io/shop Join us on Discord! https://discord.com/invite/w8d7mkCkxj​ Follow us on Twitter: https://twitter.com/ElectromakerIO Like us on Facebook: https://www.facebook.com/electromaker.io/ Follow us on Instagram: https://www.instagram.com/electromaker_io/ Featured in this show: TURFPTAx Hacking a Walmart LED Panel using an ESP32 C3 Xiao Open Muscle Project Checkout Challenge - Custom Game for Adafruit PyBadge Blues LoRaWAN Starter Kit Winner Announced! Electromaker Product of the Week: Arduino Plug and Make Kit! Enter the #plugandmake giveaway under the Product of the Week video New Seeed Xiao RA4M1 board! Flexduino: Arduino Uno Clone with a Flexible PCB RP2350 Rundown with Scott from Adafruit Adafruit Feather/Metro boards with the HSTX connectors An update from Don/Novaspirit Tech

MLOps Coffee Sessions #162 with Soham Chatterjee, From LLMs to TinyML: The Dynamic Spectrum of MLOps co-hosted by Abi Aryan. // Abstract Explore the spectrum of MLOps from large language models (LLMs) to TinyML. Soham highlights the difficulties of scaling machine learning models and cautions against relying exclusively on open AI's API due to its limitations. Soham is particularly interested in the effective deployment of models and the integration of IoT with deep learning. He offers insights into the challenges and strategies involved in deploying models in constrained environments, such as remote areas with limited power and utilizing small devices like Arduino Nano. // Bio Soham leads the machine learning team at Sleek, where he builds tools for automated accounting and back-office management. As an electrical engineer, Soham has a passion for the intersection of machine learning and electronics, specifically TinyML/Edge Computing. He has several courses on MLOps and TinyMLOps available on Udacity and LinkedIn, with more courses in the works. // MLOps Jobs board https://mlops.pallet.xyz/jobs // MLOps Swag/Merch https://mlops-community.myshopify.com/ // Related Links --------------- ✌️Connect With Us ✌️ ------------- Join our slack community: https://go.mlops.community/slack Follow us on Twitter: @mlopscommunity Sign up for the next meetup: https://go.mlops.community/register Catch all episodes, blogs, newsletters, and more: https://mlops.community/ Connect with Demetrios on LinkedIn: https://www.linkedin.com/in/dpbrinkm/ Connect with Abi on LinkedIn: https://www.linkedin.com/in/goabiaryan/ Connect with Soham on LinkedIn: https://www.linkedin.com/in/soham-chatterjee

Nick O'Leary from FlowForgeNick is the CTO and Founder of FlowForge Inc, where he is leading the OpenJS Node-RED project and building a low-code development platform. Before starting FlowForge, he was at IBM for over 19 years working across a wide range of technologies. He spends his time playing with IoT technologies, having worked on projects ranging from smart meter energy monitoring to retrofitting sensors to industrial manufacturing lines with Raspberry Pis and Arduinos. With a background in pervasive messaging, he contributes to the Eclipse Paho project and sits on the OASIS MQTT Technical Committee and the OpenJS Cross Project Council.Nick O'Leary created Node-RED and now, 10 years later is helping to industrialize that same tool!Join us as we talk about the creation of Node-RED, and how it's been used across the world. We'll as NIck what problem his new venture Flow Forge aims to solve. Along the way, we'll talk about a variety of Efficient Engineering tools that have been long used in software development and how they can transition into the industrial space.A special thank you to Siemens for sponsoring this theme and your continued support of Manufacturing Hub and the community. Connect with Us Nick O'Leary Vlad Romanov Dave Griffith Manufacturing Hub SolisPLC #manufacturing #automation #Industry40 #engineering #digitaltransformaiton

Lex Neva, Staff Site Reliability Engineer at Honeycomb and Curator of SRE Weekly, joins Corey on Screaming in the Cloud to discuss reliability and the life of a newsletter curator. Lex shares some interesting insights on how he keeps his hobbies and side projects separate, as well as the intrusion that open-source projects can have on your time. Lex and Corey also discuss the phenomenon of newsletter curators being much more demanding of themselves than their audience typically is. Lex also shares his views on how far reliability has come, as well as how far we have to go, and the critical implications reliability has on our day-to-day lives. About LexLex Neva is interested in all things related to running large, massively multiuser online services.  He has years of SRE,  Systems Engineering, tinkering, and troubleshooting experience and perhaps loves incident response more than he ought to.  He's previously worked for Linden Lab, DeviantArt, Heroku, and Fastly, and currently works as an SRE at Honeycomb while also curating the SRE Weekly newsletter on the side.Lex lives in Massachusetts with his family including 3 adorable children, 3 ridiculous cats, and assorted other awesome humans and animals.  In his copious spare time he likes to garden, play tournament poker, tinker with machine embroidery, and mess around with Arduinos.Links Referenced: SRE Weekly: https://sreweekly.com/ Honeycomb: https://www.honeycomb.io/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by our friends at Chronosphere. Tired of observability costs going up every year without getting additional value? Or being locked into a vendor due to proprietary data collection, querying, and visualization? Modern-day, containerized environments require a new kind of observability technology that accounts for the massive increase in scale and attendant cost of data. With Chronosphere, choose where and how your data is routed and stored, query it easily, and get better context and control. 100% open-source compatibility means that no matter what your setup is, they can help. Learn how Chronosphere provides complete and real-time insight into ECS, EKS, and your microservices, wherever they may be at snark.cloud/chronosphere that's snark.cloud/chronosphere.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Once upon a time, I decided to start writing an email newsletter, and well, many things happened afterwards, some of them quite quickly. But before that, I was reading a number of email newsletters in the space. One that I'd been reading for a year at the time, was called SRE Weekly. It still comes out. I still wind up reading it most weeks.And it's written by Lex Neva, who is not only my guest today but also a staff site reliability engineer at Honeycomb. Lex, it is so good to finally talk to you, other than reading emails that we send to the entire world that pass each other like ships in the night.Lex: Yeah. I feel like we should have had some kind of meeting before now. But yeah, it's really good to [laugh] finally meet you.Corey: It was one of the inspirations that I had. And to be clear, when I signed up for your newsletter originally—I was there for issue 15, which is many, many years ago—I was also running a small-scale SRE team at the time. It was, I found as useful as a part of doing my job and keeping abreast of what was going on in the ecosystem. And I found myself, once I went independent, wishing that your newsletter and a few others had a whole bunch more AWS content. Well, why doesn't it?And the answer is because you are, you know, a reasonable person who understands that mental health is important and boundaries exist for a reason. No one sensible is going to care that much about one cloud provider all the time [sigh]. If only we were all that wise.Lex: Right? Well, [laugh] well, first of all, I love your newsletter, and also the content that you write that—I mean, I would be nowhere without content to link to. And I'm glad you took on the AWS thing because, much like how I haven't written Security Weekly, I also didn't write any kind of AWS Weekly because there's just too much. So, thanks for falling on that sword.Corey: I fell on another one about two years ago and started the Thursdays, which are Last Week in AWS Security. But I took a different bent on it because there are a whole bunch of security newsletters that litter the landscape and most of them are very good—except for the ones that seem to be entirely too vendor-captured—but the problem is, is that they lacked both a significant cloud focus, as well as an understanding that there's a universe of people out here who care about security—or at least should—but don't have the word security baked into their job title. So, it was very insular, using acronyms they assume that everyone knows, or it's totally vendor-captured and it's trying to the whole fear, uncertainty, and doubt thing, “And that's why you should buy this widget.” “Will it solve problems?” “Well, it'll solve our revenue problems at our company that sells the widgets, but other than that, not really.” And it just became such an almost incestuous ecosystem. I wanted something different.Lex: Yeah. And the snark is also very useful [laugh] in order to show us that you're not in their pocket. So yeah, nice work.Corey: Well, I'll let you in on a secret, now that we are—what, I'm somewhat like 300 and change issues in, which means I've been doing this for far too long, the snark is a byproduct of what I needed to do to write it myself. Because let's face it, this stuff is incredibly boring. I needed to keep myself interested as I started down that path. And how can I continually keep it fresh and funny and interesting, but not go too far? That's a fun game, whereas copying and pasting some announcement was never fun.Lex: Yeah, that's not—I hear you on trying to make it interesting.Corey: One regret that I've had, and I'm curious if you've ever encountered this yourself because most people don't get to see any of this. They see the finished product that lands in their inbox every Monday, and—in my case, Monday; I forget the exact day that yours comes out. I collect them and read through them for them all at once—but I find that I have often had caused a look back and regret the implicit commitment in Last Week in AWS as a name because it would be nice to skip a week here and there, just because either I don't particularly feel like it, or wow, there was not a lot of news worth talking about that came out last week. But it feels like I've forced myself onto a very particular treadmill schedule.Lex: Yeah. Yeah, it comes with, like, calling it SRE Weekly. I just followed suit for some of the other weeklies. But yeah, that can be hard. And I do give myself permission to take a week off here and there, but you know, I'll let you in on a secret.What I do is I try to target eight to ten articles a week. And if I have more than that, I save some of them. And then when it comes time to put out an issue, I'll go look at what's in that ready queue and swap some of those in and swap some of the current ones out just so I keep things fresh. And then if I need a week off, I'll just fill it from that queue, you know, if it's got enough in it. So, that lets me take vacations and whatnot. Without that, I think I would have had a lot harder of a time sticking with this, or there just would have been more gaps. So yeah.Corey: You're fortunate in that you have what appears to be a single category of content when you construct your newsletter, whereas I have three that are distinct: AWS releases and announcements and news and things to make fun of for the past week; the things from the larger community folks who do not work there, but are talking about interesting approaches or news that is germane; and then ideally a tip or a tool of the week. And I found, at least lately, that I've been able to build out the tools portion of it significantly far in advance. Because a tool that makes working with AWS easier this week is probably still going to be fairly helpful a month from now.Lex: Yeah, that's fair. Definitely.Corey: But putting some of the news out late has been something of a challenge. I've also learned—by getting it wrong—that I'm holding myself to a tighter expectation of turnaround time than any part of the audience is. The Thursday news is all written the week before, almost a full week beforehand and no one complains about that. I have put out the newsletter a couple of times an hour or two after its usual 7:30 pacific time slot that it goes out in; not a single person has complained. In one case, I moved it by a day to accommodate an announcement but didn't explain why; not a single person emailed in. So, okay. That's good to know.Lex: Yeah, I've definitely gotten to, like, Monday morning, like, a couple of times. Not much, not many times, but a couple of times, I've gotten a Monday morning be like, “Oh, hey. I didn't do that thing yesterday.” And then I just release it in the morning. And I've never had a complaint.I've cancelled last minute because life interfered. The most I've ever had was somebody emailing me and be like, you know, “Hope you feel better soon,” like when I had Covid, and stuff like that. So, [laugh] yeah, sometimes maybe we do hold ourselves to a little bit of a higher standard than is necessary. I mean, there was a point where I got—I had major eye surgery and I had to take a month off of everything and took a month off the newsletter. And yeah, I didn't lose any subscribers. I didn't have any complaints. So people, I think, appreciate it when it's there. And, you know, if it's not there, just wait till it comes out.Corey: I think that there is an additional challenge that I started feeling as soon as I started picking up sponsors for it because it's well, but at this point, I have a contractual obligation to put things out. And again, life happens, but you also don't want to have to reach out on apology tours every third week or whatnot. And I think that's in part due to the fact that I have multiple sponsors per issue and that becomes a bit of a juggling dance logistically on this end.Lex: Yeah. When I started, I really didn't think I necessarily wanted to have sponsors because, you know, it's like, I have a job. This is just for fun. It got to the point where it's like, you know, I'll probably stop this if there's not some kind of monetary advantage [laugh]. And having a sponsor has been really helpful.But I have been really careful. Like, I have always had only a single sponsor because I don't want that many people to apologize to. And that meant I took in maybe less money than I then I could have, but that's okay. And I also was very clear, you know, even from the start having a contract that I may miss a week without notice. And yes, they're paying in advance, but it's not for a specific range of time, it's for a specific number of issues, whenever those come out. That definitely helped to reduce the stress a little bit. And I think without that, you know, having that much over my head would make it hard to do this, you know? It has to stay fun, right?Corey: That's part of the things that kept me from, honestly, getting into tech for the first part of my 20s. It was the fear that I would be taking a hobby, something that I love, and turning it into something that I hated.Lex: Yeah, there is that.Corey: It's almost 20 years now and I'm still wondering whether I actually succeeded or not in avoiding hating this.Lex: Well, okay. But I mean, are you, you know, are you depressed [unintelligible 00:09:16] so there's this other thing, there's this thing that people like to say, which is like, “You should only do a job that you really love.” And I used to think that. And I don't actually think that anymore. I think that it is important to have a job that you can do and not hate day-to-day, but there's no shame in not being passionate about your work and I don't think that we should require passion from anyone when we're hiring. And I think to do so is even, like, privilege. So, you know, I think that it's totally fine to just do something because it pays the bills.Corey: Oh, absolutely. I find it annoying as hell when I'm talking to folks who are looking to hire for roles and, “Well, include a link to your GitHub profile,” is a mandatory field. It's, well, great. What about people who work in places where they're not working on open-source projects as a result, and they can't really disclose what they're doing? And the expectation that oh, well outside of work, you should be doing public stuff, too.It's, I used to do a lot of public open-source style work on GitHub, but I got yelled at all the time for random, unrelated reasons and it's, I don't want to put something out there that I have to support and people start to ask me questions about. It feels like impromptu unasked-for code review. No, thanks. So, my GitHub profile looks fairly barren.Lex: You mean like yelling at you, like, “Oh, you're not contributing enough.” Or, you know, “We need this free thing you're doing, like, immediately,” or that kind of thing?Corey: Worse than that. The worst example I've ever had for this was when I was giving a talk called “Terrible Ideas in Git,” and because I wanted to give some hilariously contrived demos that took a fair bit of work to set up, I got them ready to go inside of a Docker container because I didn't trust that my laptop would always work, I'm might have to borrow someone else's, I pushed that image called “Terrible Ideas” up to Docker Hub. And I wound up with people asking questions about it. Like, “Is this vulnerable to ShellCheck.” And it's, “You do realize that this is intentionally designed to be awful? It is only for giving a very specific version of a very specific talk. It's in public, just because I didn't bother to make it private. What are you doing? Please tell me you're not running this in production at a bank?” “No comment.” Right. I don't want that responsibility of people yelling at me for things I didn't do on purpose. I want to get yelled at for the things I did intentionally.Lex: Exactly. It's funny that sometimes people expect more out of you when you're giving them something free versus when they're paying you for it. It's an interesting quirk of psychology that I'm sure that professionals could tell me all about. Maybe there's been research on it, I don't know. But yeah, that can be difficult.Corey: Oh, absolutely. I used to work at a web hosting company and the customer spending thousands a month with us were uniformly great. But there was always the lowest tier customer of the cheapest thing that we offered that seemed to expect that that entitle them to 80 hours a month of support from engineering problems and whatnot. And it was not profitable to service some of those folks. I've also found that there's a real transitive barrier that begins as soon as you find a way to charge someone a dollar for something.There's a bit of a litmus test of can you transfer a dollar from your bank account to mine? And suddenly, the entire tenor of the conversations with people who have crossed that boundary change. I have toyed, on some level, with the idea of launching a version of this newsletter—or wondering if I retcon the whole thing—do I charge people to subscribe to this? And the answer I keep coming away with is not at all because it started in many respects is marketing for AWS bill consulting and I want the audience as fast as possible. Artificially limiting its distribution via a pay-for model just seemed a little on the strange side.Lex: Yeah. And then you're beholden to a very many people and there's that disproportionality. So, years ago, before I even started in my career in I guess, you know, things that were SRE before SRE was cool, I worked for a living in Second Life. Are you familiar with Second Life?Corey: Oh, yes. I'm very familiar with that. Linden Labs.Lex: Yep. So, I worked for Linden Lab years later, but before I worked for them, I sort of spent a lot of my time living in Second Life. And I had a product that I sold for two or three dollars. And actually, it's still in there; you could still buy it. It's interesting. I don't know if it's because the purchase price was 800 Linden dollars, which equates to, like, $2.16, or something like that, but—Corey: The original cryptocurrency.Lex: Right, exactly. Except there's no crypto involved.Corey: [laugh].Lex: But people seem to have a disproportionate amount of, like, how much of my time they expected for support. You know, I'm going to support them a little bit. You have to recognize at some point, I actually can't come give you a tutorial on using this product because you're one of 500 customers for this month. And you give me two dollars and I don't have ten hours to give you. You know, like, sorry [laugh]. Yeah, so that can be really tough.Corey: And on some level, you need to find a way to either charge more or charge for support on top of it, or ideally—it I wish more open-source projects would take this approach—“Huh. We've had 500 people asking us the exact same question. Should we improve our docs? No, of course not. They're the ones who are wrong. It's the children who are getting it wrong.”I don't find that approach [laugh] to be particularly useful, but it bothers me to no end when I keep running into the same problem onboarding with something new and I ask about it, and, “Oh, yeah, everyone runs into that problem. Here's how you get around it.” This would have been useful to mention in the documentation. I try not to ask questions without reading the manual first.Lex: Well, so there's a couple different directions. I could go with this. First of all, there's a really interesting thing that happened with the core-js project that I recommend people check out. Another thing that I think the direction I'll go at the moment—we can bookmark that other one, but I have an open-source project on the side that I kind of did for my own fun, which is a program for creating designs that can be processed by computer-controlled embroidery machines. So, this is sewing machines that can plot stitches in the x-y plane based on a program that you give it.And there really wasn't much in the way of open-source software available that could help you create these designs and so I just sort of hack something together and started hacking with Python for my own fun, and then put it out there and open-sourced. And it's kind of taken off, kind of like gotten a life of its own. But of course, I've got a newsletter, I've got three kids, I've got a family, and a day job, and I definitely hear you on the, like, you know, yeah, we should put this FAQ in the docs, but there can be so little time to even do that. And I'm finding that there's, like—you know, people talk about work-life balance, there's, like, work slash life slash open-source balance that you really—you know, you have to, like, balance all three of them.And a lot of weeks, I don't have any time to spend on the project. But you know what, it's still kicks along and people just kind of, they use my terrible little project [laugh] as best they can, even though it has a ton of rough edges. I'm sorry, everyone, I'm so sorry. I know it has a t—the UI is terrible. But yeah, it's interesting how these things sometimes take on a life of their own and you can feel dragged along by your own open-source work, you know?Corey: It always bothers me—I think this might tie back to the core-js issue you talked about a second ago—where there are people who are building and supporting open-source tools or libraries that they originally constructed to scratch an itch and now they are core dependencies of basically half the internet. And these people are still wondering on some level, how do I put food on the table this month? It's wild to me. If there were justice in the world, you'd start to think these people would wind up in never-have-to-work-again-if-they-don't-want-to positions. But in many cases, it's exactly the opposite.Lex: Well, that's the really interesting thing. So, first of all, I'm hugely privileged to have any time to get to work on open-source. There's plenty of people that don't, and yeah, so requiring people to have a GitHub link to show their open-source contributions is inherently unfair and biased and discriminatory. That aside, people have asked all along, like, “Lex, this is decent software, you could sell this. You could charge money for this thing and you could probably make a, you know, a decent living at this.”And I categorically refuse to accept money for that project because I don't want to have to support it on a commercial level like that. If I take your money, then you have an expectation that—especially if I charge what one would expect—so this software, part of the reason I decided to write my own is because it starts at two-hundred-some-off dollars for the competitors that are commercial and goes up into the five, ten-thousand dollars. For a software package. Mine is free. If I started charging money, then yeah, I'm going to have to build a support department and we're going to have a knowledge base, I'm going to have to incorporate. I don't want to do that for something I'm doing for fun, you know? So yeah, I'm going to keep it free and terrible [laugh].Corey: It becomes something you love, turns into something you hate without even noticing that it happens. Or at least something that you start to resent.Lex: Yeah. I don't think I would necessarily hate machine embroidery because I love it. It's an amazingly fun little quirky hobby, but I think it would definitely take away some of the magic for me. Where there's no stress at all, I can spend months noodling on an algorithm getting it right, whereas it'd be, you know, if I start having to have deliverables, it changes it entirely. Yeah.Corey: It's odd, it seems, on some level too, that the open-source world that I got started with has evolved in a whole bunch of different ways. Whereas it used to be write a quick fix for something and it would get merged, in many cases by the time you got back from lunch. And these days, it seems like it takes multiple weeks, especially with a corporate-controlled open-source project, and there's so much back and forth. And even getting the boilerplate, like the CLI—the Contributor License Agreement—aside and winding up getting other people to sign off on it, then there's back and forth, in some cases for weeks about, well, the right kind of test coverage and how to look at this and the right holistic framework. And I appreciate that there is validity and value to these things, but is that the bulk of the effort should be going when there's a pull request ready to go that solves a breaking customer problem?But the test coverage isn't right so we're going to delay it for two or three releases. It's what are you doing there? Someone lost the plot somewhere. And I'm sure there are reasons that makes sense, given the framework people are operating within. I just find it maddening from the side of having to [laugh] deal with this as a human.Lex: Yeah, I hear you. And it sometimes can go even beyond test coverage to something like code style, you know? It's like, “Oh, that's not really in the style of this project,” or, “You know, I would have written it this way.” And one thing I've had to really work on, on this project is to make it as inviting to developers as possible. I have to sometimes look at things and be like, yeah, I might do that a different way. But does that actually matter? Like, do I have a reason for that that really matters or is it just my style? And maybe because it's a group project I should just be like, no, that's good as it is.[midroll 00:20:23]Corey: So, you've had an interesting career. And clearly you have opinions about SRE as a result. When I started seeing that you were the author of SRE Weekly, years ago, I just assumed something that I don't believe is true. Is it possible that you have been contributing to the community around SRE, but somehow have never worked at Google?Lex: I have never worked at Google. I have never worked at Netflix. I've never worked at any of those big companies. The biggest company I've worked for is Salesforce. Although I worked for Heroku who had been bought by Salesforce a couple of years prior, and so it was kind of like working for a startup inside a big company. And here's the other thing. I created that newsletter two months after starting my first job where I had a—like, the first job in which I was titled ‘SRE.' So, that's possibly contentious right there.Corey: You know, I hadn't thought of it this way, but you're right. I did almost the exact same thing. I was no expert in AWS when I started these things. It came out of an effort that I needed to do of keeping touch with everything that came out that had potential economic impact, which it turns out are most things when you understand architecture and cost are the same thing when it comes to cloud. But I was more or less gathering what smart people were saying.And somehow there's been this osmotic effect, where people start to view me as the wise old sage of the mountain when it comes to AWS. And no, no, no, I'm just old and grumpy. That looks alike. Don't mistake it for wisdom. But people will now seek me out to get my opinion on things and I have no idea what the answer looks like for most of the stuff.But that's the old SRE model—or sysadmin model that I've followed, which is when you don't know the answer, well, how do you get to a place where you can find the answer? How do you troubleshoot this? Click the button. It doesn't work? Well, time to start taking the button apart to figure out why.Lex: Yeah, definitely. I hear you on people. So, first of all, thanks to everyone who writes the articles that I include. I would be nothing without—I mean—literally, that I could not have a newsletter without content creators. I also kind of started the newsletter as an exploration of this new career title.I mean, I've been doing things that basically fit along with SRE for a long time, but also, I think my view of SRE might be not really the same as a lot of folks, or, like, that Google passed down from the [Google Book Model 00:22:46]. I don't—I'm going to be a little heretical here—I don't necessarily a hundred percent believe in the SLI SLO SLA error budget model. I don't think that that necessarily fits everyone, I'm not sure even suits the bigger companies as well as they think it does. I think that there's a certain point to which you can't actually predict failure and just slowing down on your deploys. And it likes to cause there to be fewer incidents so that you can get—your you know, you can go back to passing in your error budget, to passing your SLO, I'm not sure that actually makes sense or is realistic and works in the real world.Corey: I've been left with the distinct impression that it's something of a framework for how to think about a lot of those things. And it's for folks on a certain point of their development along whatever maturity model or maturity curve you want to talk about, it becomes extraordinarily useful. And at some point, it feels like the path that a given company is on will deviate from that. And, on some level, if you don't wind up addressing it, it turns into what it seems like Agile did, where you wind up with the Cult of Agile around it and the entire purpose of it is to perpetuate the Cult of Agile.And I don't know that I'm necessarily willing to go so far as to say that's where SLOs are headed right now, but I'm starting to get the same sort of feeling around the early days of the formalization of frameworks like that, and the ex cathedra proclamation that this is right for everyone. So, I'm starting to wonder whether there's a reckoning, in that sense, coming down the road. I'm fortunate that I don't run anything that's production-facing, so for me, it's, I don't have to care about these things. Mostly.Lex: Yeah. I mean, we are in… we're in 2023. Things have come so much further than when I was a kid. I have a little computer in my pocket. Yeah, you know, “Hey, math teacher, turns out yeah, we do carry calculators around with us wherever we go.” We've built all these huge, complicated systems online and built our entire society around them.We're still in our infancy. We still don't know what we're doing. We're still feeling out what SRE even is, if it even makes sense, and I think there's—yeah, there's going to be more evolution. I mean, there's been the, like, what is DevOps and people coining the term DevOps and then getting, you know, almost immediately subsumed or turned into whatever other people want. Same thing for observability.I think same thing for SRE. So honestly, I'm feeling it out as I go and I think we all are. And I don't think anyone really knows what we're doing. And I think that the moment we feel like we do is probably where we're in trouble. Because this is all just so new. Look where we were even 40 years, 30, even 20 years ago. We've come really far.Corey: For me, one of the things that concerns slash scares me has been that once someone learns something and it becomes rote, it sort of crystallizes in amber within their worldview, and they don't go back and figure out, “Okay, is this still the right approach?” Or, “Has the thing that I know changed?” And I see this on a constant basis just because I'm working with AWS so often. And there are restrictions and things you cannot do and constraints that the cloud provider imposes on you. Until one day, that thing that was impossible is now possible and supported.But people don't keep up with that so they still operate under the model of what used to be. I still remember a year or so after they raised the global per-resource tag limit to 50, I was seeing references to only ten tags being allowed per resource in the AWS console because not even internal service teams are allowed to talk to each other over there, apparently. And if they can't keep it straight internally, what hope to the rest of us have? It's the same problem of once you get this knowledge solidified, it's hard to keep current and adapt to things that are progressing. Especially in tech where things are advancing so rapidly and so quickly.Lex: Yeah, I gather things are a little feudalistic over inside AWS, although I've never worked there, so I don't know. But it's also just so big. I mean, there's just—like, do you even know all of the—like, I challenge you to go through the list of services. I bet you're going to find when you don't know about. You know, the AWS services. Maybe that's a challenge I would lose, but it's so hard to keep track of all this stuff with how fast it's changing that I don't blame people for not getting that.Corey: I would agree. We've long since passed the point where I can talk incredibly convincingly about AWS services that do not exist and not get called out on it by AWS employees. Because who would just go and make something up like that? That would be psychotic. No one in the right mind would do it.“Hi, I'm Corey, we haven't met yet. But you're going to remember this, whether I want you to or not because I make an impression on people. Oops.”Lex: Yeah. Mr. AWS Snark. You're exactly who I would expect to do that. And then there was Hunter, what's his name? The guy who made the—[singing] these are the many services of AWS—song. That was pretty great, too.Corey: Oh, yeah. Forrest Brazeal. He was great. I loved having him in the AWS community. And then he took a job, head of content over at Google Cloud. It's, well, suddenly, you can't very well make fun of AWS anymore, not without it taking a very different tone. So, I feel like that's our collective loss.Lex: Yeah, definitely. But yeah, I feel like we've done amazing things as a society, but the problem is that we're still, like, at the level of, we don't know how to program the VCR as far as, like, trying to run reliable services. It's really hard to build a complex system that, by its nature of being useful for customers, it must increase in complexity. Trying to run that reliably is hugely difficult and trying to do so profitably is almost impossible.And then I look at how hard that is and then I look at people trying to make self-driving cars. And I think that I will never set foot in one of those things until I see us getting good at running reliable services. Because if we can't do this with all of these people involved, how do I expect that a little car is going to be—that they're going to be able to produce a car that can drive and understand the complexities of navigating around and all the hazards that are involved to keep me safe.Corey: It's wild to me. The more I learned about the internet, the more surprised I am that any of it works at all. It's like, “Well, at least you're only using it for ridiculous things like cat pictures, right?” “Oh, no, no, no. We do emergency services and banking and insurance on top of that, too.” “Oh, good. I'm sure that won't end horribly one day.”Lex: Right? Yeah. I mean, you look at, like—you look at how much of a concerted effort towards safety they've had to put in, in the aviation industry to go from where they were in the '70s and '80s to where we are now where it's so incredibly safe. We haven't made that kind of full industry push toward reliability and safety. And it's going to have to happen soon as more and more of the services we're building are, exactly as you say, life-critical.Corey: Yeah, the idea of having this stuff be life-critical means you have to take a very different approach to it than you do when you're running, I don't know, Twitter for Pets. Though, I probably need a new fake reference startup now that Twitter for reality is becoming more bizarre than anything I can make up. But the idea that, “Well, our ad network needs to have the same rigor and discipline applied to it as the life support system,” maybe that's the wrong framing.Lex: Or maybe it's not. I keep finding instances of situations—maybe not necessarily ad networks, although I wouldn't put it past them—but situations where a system that we're dealing with becomes life-critical when we had no idea that it could possibly do. So, for example, a couple companies back, there was this billing situation where a vendor of ours accidentally nilled our customers incorrectly and wiped bank accounts, and real people were unable to make their mortgage payments and unable to, like, their bank accounts were empty, so they couldn't buy food. Like, that's starting to become life-critical and it all came down to a single, like, this could have been any outage at any company. And that's going to happen more and more, I think.Corey: I really want to thank you for taking time to speak with me. If people want to learn more, where's the best place for them to find you?Lex: sreweekly.com. You can subscribe there. Thank you so much for having me on. It has been a real treat.Corey: It really has. You'll have to come back and we'll find other topics to talk about, I'm sure, in the very near future. Thank you so much for your time. I appreciate it.Lex: Thanks.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

Playing with Arduinos, a 1337 h4x0r tool, ChromeOS Flex, a proprietary software win, whether open-sourcing AI makes sense, and more.   Discoveries Tauno Serial Plotter kdb-audio ChromeOS Flex is now generally available   Discussion Open source isn't working for AI       Kolide Kolide believes that maintaining endpoint security shouldn't mean compromising employee privacy.... Read More

Playing with Arduinos, a 1337 h4x0r tool, ChromeOS Flex, a proprietary software win, whether open-sourcing AI makes sense, and more.   Discoveries Tauno Serial Plotter kdb-audio ChromeOS Flex is now generally available   Discussion Open source isn't working for AI       Kolide Kolide believes that maintaining endpoint security shouldn't mean compromising employee privacy.... Read More

In this edition of SMBCP, Host Karl sits down with Robert Sawyer and Daniel Daraban to discuss Bitdefender's GravityZone XDR (extended detection and response).  Find out what GravityZone XDR can do for your MSP business.  Robert Sawyer is the director of product marketing for cloud workload security and managed detection and response at Bitdefender. Prior to Bitdefender, he led product marketing for integration and applications at IBM as part of its newly launched automation division. He also led teams in hybrid cloud, tracing his roots back through BPM and SOA, and worked at Rackspace Technology, helping lead marketing for a newly launched managed security service offering. He's been in the IT space for over 20 years and started his career in software development, working on industry solutions in healthcare and life sciences and media and entertainment. As a Director of Product Management at Bitdefender, Daniel Daraban manages the Bitdefender Business Solutions Group flagship product lines: EDR and XDR. Together with his team, they are on a mission to solve real-world customer encountered issues. Eager to understand day-to-day workflows and how that is impacting the products he manages, Daniel enjoys interacting with customers, prospects and industry analysts to gain valuable feedback. Outside of work you will find him in his tool shed working on various DYI projects, playing around with Arduinos, or riding some of the world's craziest rollercoasters. Resources and Links: XDR for MSPs Datasheet: https://www.bitdefender.com/content/dam/bitdefender/business/products/msp/Bitdefender-XDR-for-MSP-Datasheet-en.pdf  XDR for MSP launch blog: https://businessinsights.bitdefender.com/how-xdr-can-transform-msp-cybersecurity   Sponsor Memo: PCMatic  PC Matic — Endpoint Security built on a zero trust/default deny foundation Finally - a light weight, simple to deploy & easy to manage approach to application allowlisting. The perfect compliment to your current security stack. No minimums and no annual contracts. Find out more about PC Matic by  visiting PCMatic.com/MSP today.      :-)    

What are you going to print? Head straight downtown to the 3D statue-filled intersection of “Fun Street” and “Technology Avenue” with this Data Center Therapy podcast!  Your hosts Mr. Matt “What can't you do with a Pi?” Yette and Mr. Matt “Printable Log Cabin” Cozzolino welcome you, our loyal listeners, into their virtual garages for an entertaining introduction to 3D printing, sans the resin fumes.  If you're wondering what the heck a “PEI magnetic build plate” is, give this episode a listen! In this quick but enjoyable 30-minute dash, you'll get a handle on: Which 3D printers are the “Ford F-150s” of the market; trustable industry standards to get started with and to modify when you're ready. The difference between Filament-based and Resin-based 3D printers, how they function, and which ones are more hazardous and need special consideration. And tips and tricks that the Matts share to keep your 3D prints extruding well, staying sharp and functionally strong (and the reason why Yette owns a grow tent!). You'll get a little background on the common things some of the gaming-minded folks print (hint: Final Fantasy VII, Warhammer, and Day of the Tentacle come into the discussion) and you'll also find out where things like ESP32 and Arduinos (nifty pieces of technology in their own right) mesh with 3D printing.   If you loved this episode, please be sure to like, share and subscribe wherever you quality podcasts are found.  Be sure keep those printer beds warm, keep those filament spools spooling, and tune in again for another fun episode of Data Center Therapy.  Thanks everybody!

Microsoft compra Activision Blizzard / Más de 500 millones de abonados a música en streaming / YouTube cierra Originals / El CEO de Airbnb "se va de Airbnb" / Intel presenta un minero de Bitcoin / AdBlock Plus gana el juicio / Primera candidata real de exoluna Patrocinador: Cuidado con las Macros Ocultas https://www.cuidadoconlasmacrosocultas.com/ es un podcast de divulgación tecnológica para empresas impulsado por Cuatroochenta que responde a preguntas clave de nuestra época en cada episodio: ¿Cómo es un ciberataque desde dentro?, ¿cuál es el impacto medioambiental de la nube?, ¿qué cambiará realmente la IA? — Suscríbete en Spotify https://open.spotify.com/episode/1IyJTLfo2XlrwNwwm0q2gp?si=2gOAVIqdR3yDHLlRU3CX5g, Apple https://podcasts.apple.com/es/podcast/cuidado-con-las-macros-ocultas/id1582767310?i=1000547511042, Ivoox https://www.ivoox.com/m05-automatismos-robots-avatares-el-nuevo-digital-audios-mp3_rf_80668395_1.html, Google https://podcasts.google.com/feed/aHR0cHM6Ly9vbW55LmZtL3Nob3dzL2N1aWRhZG8tY29uLWxhcy1tYWNyb3Mtb2N1bHRhcy9wbGF5bGlzdHMvcG9kY2FzdC5yc3M/episode/ZjgxYjg5MDQtODAyYi00MjI5LTk3Y2ItYWUwODAwOTdhZWVi?ep=14, etc. Microsoft compra Activision Blizzard / Más de 500 millones de abonados a música en streaming / YouTube cierra Originals / El CEO de Airbnb "se va de Airbnb" / Intel presenta un minero de Bitcoin / AdBlock Plus gana el juicio / Primera candidata real de exoluna

The element of marketing that occupies the largest chunk of our time and energy is the collection of software tools that we use. We usually termed it as our technology stack. Some people have seen enough things done with tech stacks, they can spot the do's and don'ts that marketers should follow. I brought somebody on who I think is really good at this.  Dave Hicks is a front end digital marketing strategist, photographer and designer whose tools of choice are Adobe Photoshop and Illustrator.  He's also a backend developer who knows JavaScript, Jquery, Node.JS, Ruby and PHP. But what he's especially good at is making sure that the tech stack a company uses conforms to the marketing objective that the strategy calls for.  I met Dave through some of his community minded pursuits including his organization of live meet ups for social media and marketing folks in Ottawa. I also enjoy gawking at the creations he makes out of Arduinos and Raspberry Pi's as a hobby. After doing a lot of moving around in his youth, he settled in Ottawa, where he lives and works on cool projects as a freelance marketer. People/Products/Concepts Mentioned in Show Single point of failure COTS vs Custom-coded software: Here's one view and here's another. Development vs Staging vs Production sites Corel K.I.S.S. Principle Dave's twitter account, which has over 200K tweets Dave can be reached via email Episode Reboot. You can't automate everything. For more details, please visit https://funnelreboot.com/episode-63-marketing-stack-dos-and-donts-with-dave-hicks/

Jim Grisanzio from Oracle Developer Relations talks with Gabriele Provinciali, an engineer and solutions architect at Oracle in Rome, about smart and safe city models built with Lego Bricks, Arduinos, Raspberry Pis, and a variety of IoT edge sensors all connected to the Oracle Cloud. Twitter Thread. Video on YouTube. Oracle News Connect Article Little towns, big ideas: How scale models can imagine smarter and safer cities Gabriele Provinciali, Solution Architect, Oracle Cloud Infrastructure https://www.linkedin.com/in/gabriele/ https://twitter.com/GabbaPro ProximaSafe: Joining the Dots in OCI to build a Stream Analysis Lab Part 1: Setting up the event-driven OCI components Part 2: From Edge to Serverless Part 3: Sensors, Pipelines and back to Edge YouTube Video: Oracle Proxima City Jim Grisanzio, Oracle Developer Relations https://twitter.com/jimgris https://www.linkedin.com/in/jimgris/ https://developer.oracle.com/team/ https://oraclegroundbreakers.libsyn.com/

What do Elon Musk, dinosaur-shaped Arduinos, and the largest network of HS coders have in common? Zach Latta brings us through his journey dropping out and moving to SF at 16 to founding Hack Club.“To Meet Interesting People, You Have to Work on Interesting Things.”At age 7, Zach took apart his parents computer, then created top chart games and apps used by 5 million people at 16 after moving away alone to SF. In doing the unconventional, Zach set himself on a path to doing interesting things - and meeting and working with interesting people, including Elon Musk and Tom Preston-Werner.In this episode, you'll hear about how to get in rooms with interesting people, why you need to prioritize actually helping people, and getting backed/raising money to support your causes.______________________________GuestZach LattaOn Linkedin

This week's guest is South Africa's own Faffa! Faffa is a teacher in South Africa's oldest technical school, Daniel Pienaar Technical Highschool, teaching electronics and digital circuits, and is starting up a robotics program using Arduinos and all sorts of awesome gadgetry! I strongly recommend you check out his YouTube channel and subscribe! Check him out here: https://www.youtube.com/channel/UC1cvH4fNvsfkN12EpXTVrZA https://www.youtube.com/channel/UC_kGc0FI5CCKYGiEmPaUDsg https://instagram.com/tiere_dp_?r=nametag https://www.facebook.com/www.danielpienaar.co.za/ https://www.danielpienaar.co.za

En este nuevo capítulo explico cómo comunicar dos Arduinos mediante radiofrecuencia utilizando módulos RF433 MHz.Más información en https://programarfacil.com/blog/arduino-blog/rf-433-mhz-arduino-fs1000a/

Mike is joined by Cara Lesser. CEO and Founder of the KID Museum in Bethesda, Maryland. Cara starts by describing how she transitioned from working on healthcare policy to growing interested in education as her children entered school. Inspired by the Children’s Museum of Pittsburgh, she sought to create an institution dedicated to what she felt was lacking in her children’s education: creative, hands-on problem-solving. The KID museum features flexible workspaces, many digital items for kids to explore, as well as more traditional technologies. (Some of the educational technologies Cara mentions: 3D printers, CNC routers, micro:bits, Arduinos.) Cara partners closely with educators and administrators to provide compelling and effective pedagogy.   The pandemic accelerated the move into the virtual space, and even into VR. While the focus is on K-8, KID Museum partners with Amazon Future Engineer to allow kids to explore career pathways. KID Museum also encourages education across traditional siloed subjects. This can be called “maker education,” or “invention education”. Cara cites research from the George Lucas Foundation on the efficacy of project-based learning. Mike and Cara finish up by discussing how KID Museum might be a model for other initiatives. Join them both for this compelling look into the creative mind of maker learning. If you like what you're hearing subscribe to Trending in Education wherever you get your podcasts and check us out at TrendinginEducation.com.

Cy Keener spoke with us about sensors, Arduinos, ice, and the crossover between art and science. You can see some of his field work and gallery installations at his site: cykeener.com and on his vimeo channel. Cy is an art professor at the University of Maryland (bio, youtube) Cy’s advisor at Stanford was Paul DeMarinis (pauldemarinis.org, Stanford page). Arduiniana: a blog of useful Arduino libraries We also talked about some custom sensors by Lovro Valcic of Bruncin (bruncin.com).

Welcome to the Electromaker Show, episode 36! This week saw the Arduino IDE 2.0 beta released, DietPi added Docker and Steam support, the ESP32-M1 seeks crowdfunding, and there’s an early hands-on look at the ESP32-S3! Check out these top maker, tech, DIY, IoT, embedded, and crowdfunding news stories from the week! We publish a new show every week. Subscribe here. Read the article! Don't have time to watch the show? Listen to the Electromaker Show in podcast format!  Super Early hands-on look at ESP32-S3 with Unexpected Maker Using Raspberry Pi GPIO pins as radio transmitters "The Thresher" A personal grooming device from JoelCreates you'd never want to use Bitluni 3d Printed Holographic Displays Zack Freedman talks about "Disgusting Secrets of Real Hardware" ESP32-M1 Reach Out - long-range Wi-Fi board Binary Decoder SMD soldering kit Simple Calculator Through Hole Kit Arduino IDE 2.0 hits Beta Arduino Day 2021 Free RISC-V training classes from Linux Foundation and RISC-V International Embedded World Closing Report DietPi 7.0 now has Docker and Steam support

Greg and Anto talk about the tiny world of Arduinos, Raspberry Pis, sensors, and mishaps with low-voltage electricity as they relive their hack day building an Arduino theremin. Learn about breadboards, prototyping your own project, and tools you need to get started.

In this episode of Gadget talk Chad "Bounce Bounce" and Derek "Baker6Clan" talk to Dave "DJW House" about the Arduino world, and some suggestions on how to get into that world.  This is review of what Arduinos are and what they can do.     If you have any questions email us at gadgettalkpodcast@gmail.com

Quieres unirte al club y ser un EEYMUCQUER te dejo el Whatsapphttps://wa.me/573128329992?text=HolaEn el Episodio de Hoy respondo una pregunta relacionada con el IIOT y la posibilidad de usar Arduinos en implementaciones para estas tecnologíashttps://www.eeymuc.co/159-arduinos-y-el-iiot/

Quieres unirte al club y ser un EEYMUCQUER te dejo el Whatsapphttps://wa.me/573128329992?text=HolaEn el Episodio de Hoy respondo una pregunta relacionada con el IIOT y la posibilidad de usar Arduinos en implementaciones para estas tecnologíashttps://www.eeymuc.co/159-arduinos-y-el-iiot/

Our Online Puzzle Games: https://www.fortescapegames.com/games KSGR Soldering Iron:https://usa.banggood.com/V2_1S-T12-Digital-Temperature-Controller-Soldering-Station-Electric-Soldering-Iron-Tips-T12-K-907-Handle-p-1338117.html?rmmds=myorder&cur_warehouse=USACompatible KSGR Soldering Iron Tips: https://usa.banggood.com/Drillpro-10pcs-T12-Soldering-Iron-Tips-Set-for-HAKKO-FX951-FX952-p-1191594.html?rmmds=myorder&cur_warehouse=CNWhite Desk Lamp: https://amzn.to/3dF5g6O Circuit Board Holder: https://amzn.to/2BLzcjG Ryobi 18V Soldering Iron: https://amzn.to/2XGFklQ Ryobi 18V Hot Glue Gun: https://amzn.to/2zeSbCl Heat Gun: https://amzn.to/2Yk7pyy Butt End Connectors with Solder Sleeve: https://amzn.to/2AOFSx2 WAGO Clips: https://amzn.to/3f0h6su Arduino Uno: https://amzn.to/2UmVvTcMicrocenter Arduino: https://www.microcenter.com/product/486544/inland-uno-r3-mainboardWAVGAT Arduino (not recommended): https://www.aliexpress.com/item/4000587244657.html?spm=a2g0o.productlist.0.0.56675cb7UBeuO0&algo_pvid=7a39cf9e-4e18-4824-8e54-0545dc6235db&algo_expid=7a39cf9e-4e18-4824-8e54-0545dc6235db-2&btsid=0ab50f4415916310697714232e56ce&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_Arduino Shield: https://amzn.to/2A7ffU6

Ingeniería inversa, programación en Android, programación en Arduino, conectarse a la centralita de la moto con un conector hecho con una impresora 3D. Nos va a explotar la cabeza!! Fran Segovia, alma matter de www.motomedialink.site, nos explica en qué consiste la aplicación Android y los diferentes dispositivos que ha diseñado para controlarla con la electrónica de la moto. En la segunda parte del programa, tres amigos del grupo de Telegram de El Internet de las Motos, nos ayudan a hacer un nuevo consultorio frikie, en el que hablamos de noticias e innovaciones sobre cascos, además de algún gadget innecesario, claro está. Todo esto acompañado de un poco de música y muchas ganas de aprender cosas nuevas. Links a las noticias: https://wowmotosnoticias.com/camara-de-accion-disenada-para-y-por-cascos-hjc-hjc-smart-10a/ https://www.canariasenmoto.com/noticias/en-peligro-el-futuro-de-los-cascos-modulares-y-los-intercomunicadores-22453.html https://www.lightmodehelmets.com/neutron-s-kit/2x-grid Email: elinternetdelasmotos@viajoenmoto.com --- Send in a voice message: https://podcasters.spotify.com/pod/show/el-internet-de-las-motos/message

Eigentlich sollte es nur eine kurze Ankündigung werden, aber nach kurzer Zeit diskutieren Julian und Nils schon direkt über Themen, wie 3D-Druck und Arduinos. Davon wird es in Zukunft wohl mehr geben.

As we head towards week 4 of lockdown in the UK, Chris and Martin reflect on the personal changes in their daily routines, as well as the implications on businesses. This has been a time for dusting off old skills (like DNS/DHCP configurations) and finding new uses for Raspberry Pis and Arduinos. Working from home […] The post #153 – Post Pandemic Storage Efficiencies appeared first on Storage Unpacked Podcast.

Building ventilators to help COVID-19 patients could be much easier than we think. Dr. Sem Lampotang is a Professor of Anesthesiology and the Director of the Center for Safety, Simulation and Advanced Learning Technologies at the University of Florida. Based on a design Lampotang helped create 30 years ago, simple “crisis” ventilators can be built with parts from Home Depot, Ace or Lowe’s hardware stores for less than $300. The “open-architecture” design can be downloaded anywhere and allows anyone to use locally-available parts if traditional parts can not be sourced. Doctors and engineers in Mauritius, Lampotang’s native country, have already produced ventilators using his design. TRANSCRIPT: Intro: 0:00 Welcome to a special two-part edition of Radio Cade . We’ll be discussing COVID-19 and ventilators. In part one, we visit with Dr. Sem Lampotang and in part two, we visit with Dr. Richard Melker. We hope you enjoy the program. Inventors and their inventions. Welcome to Radio Cade a podcast from the Cade Museum for Creativity and Invention in Gainesville, Florida. The museum is named after James Robert Cade , who invented Gatorade in 1965. My name is Richard Miles. We’ll introduce you to inventors and the things that motivate them, we’ll learn about their personal stories, how their inventions work and how their ideas get from the laboratory to the marketplace. James Di Virgilio: 0:53 Welcome to a special episode of Radio Cade . I’m your host, James Di Virgilio. Today we’re going to be covering mechanical ventilation and its effect on the COVID-19 crisis. Mechanical ventilation is a lifesaving therapy that is used extensively and modern intensive care units. The origins of modern mechanical ventilation can be traced back five centuries ago to the seminal work of Andreas Vasilis, really the founder of modern human anatomy. My guest today is Dr. Sem Lampotang. He is the Joachim S. Gravenstein professor of anesthesiology at UF Health and the Director of the Center for Safety Simulation and Advanced Learning Technologies. Dr. Lampotang, welcome to the show. Dr. Sem Lampotang: 1:33 Thank you. James Di Virgilio: 1:35 Now your background is extensive. You have a PhD in engineering. You spent a lot of time dealing with patient safety, especially on the anesthesiology side, but today you’ve been working extensively on a mechanical ventilator. That is interesting for a lot of reasons. Tell us a bit about how this project came to be. Dr. Sem Lampotang: 1:54 If you go way back, like 30 years ago, what we are building today, I actually designed 30 years ago together with two respiratory therapists, Michael Bonner and Paul Blanche at the University of Florida and our design was actually commercialized and used on patients in the United States by a Swiss company. The ventilator was called Hamilton Max. And what we’re building today is essentially the Hamilton’s Max, but we’ve paused from hardware stores. The reason we decided to use hardware store parts from my work 3 decades ago, with ventilated companies , we still have insider information being a good way about what’s going on. So three, four weeks ago, before everybody else knew, we already knew that there would be no parts traditionally use to build ventilators. That’s a problem GM is facing right now as they’re trying to build ventilators. So when we were approached to design one to address that expected shortfall of ventilators, if we truly need a million, then the design style that we have , how do you build it? If your traditional supply chain is no longer available. And that’s when the idea of going to home Depot and ACE and Lowes came into being. James Di Virgilio: 3:05 And your ventilator itself is an interesting concept. You are open sourcing it. What essentially means you put the design out there into the public arena. And anyone is able to take a look at this and improve it as necessary. We often see this done in the internet and things like that. How often is something open sourced in the medical community? Dr. Sem Lampotang: 3:25 It is quite common today with the COVID-19. So there are a lot of open source ventilator projects going on. So we were among the first day , a lot of open source efforts, spontaneously sprang up around the country. And also I think in the UK, I don’t know whether it was common before that, but I can tell you now, currently in this crisis, it’s quite common. James Di Virgilio: 3:47 No, I’ve seen a lot of studies back in the mid two thousands that had suggested that we did not have enough ventilators in the case of a surge event, which COVID-19 certainly is a surge event. However, those same studies argued that the $40,000- $50,000 ventilators that exist in the ICU would not be appropriate to basically hold on reserve based upon daily usage. But instead they suggested a combination of something more like you were creating or something that could be utilized. Why is it that those academic studies just went unheated that in reality, we really didn’t attempt to address maybe a middle ground, a less intensive ventilator. Why do you think it is that that’s been the case? Dr. Sem Lampotang: 4:28 Well, it’s a lot of it is mission Creek. And also a lot of it is there’s a tendency to treat to the highest need. So when you order a ventilator, you want to make sure it will need those patients who have really, really dire needs. So that’s a tendency. It’s just like, why do we not drive small cars? Why do we drive bigger cars? Because we can. And so if hospitals also want to make sure they can treat the sickest patient, so they usually order the Cadillacs instead of the base models. James Di Virgilio: 5:01 That’s one reason, right? And obviously it would be cost inefficient to stockpile, a lot of $50,000 ventilators that may not get used, but there is this other side we’re in now where we know that a virus could happen, that causes this situation and you and I, before the show, we’re talking about something, that’s very interesting. So your design has been working now for a week straight. Your ventilator has been working as you wanted it to for one week straight, right? But you were telling me that’s not enough yet. And why is that? Dr. Sem Lampotang: 5:30 The reason is not enough at the one week nonstop running, it’s going an endurance testing is the data from Italy. And China indicates that worst case scenario, a patient needs ventilatory support, meaning they need to be on a ventilator for up to three weeks nonstop. So, currently all I can say with confidence is that this ventilator will run for a week nonstop because I have not run it for another two weeks, but my dilemma and my ethical dilemma as an engineer, a professional engineer is, if let’s say in a week from now, when I’m two weeks into endurance testing, and by the way, there’s more than one ventilator . So I have three ventilators undergoing endurance testing right now, but even two weeks from now, two weeks of endurance testing, but I’ve not completed my three weeks. And the doctors are being faced with a stock choice of you have the ventilator you don’t then do we start building and giving them to the doctors and say, trust us, even though we have not finished the testing, because the proper engineering practice is to finish the testing costs and then deliver. One of the benefits of working at the University of Florida, is it has a lot of faculty with expertise. So I talk to an ethicist when I was faced with that dilemma, I called an ethicist who I know, and I said, this is my dilemma. And it was very helpful because he told me, in his opinion, if in a week from now, we have not finished, but the need is there. You have defensible ethical ground to release, even though your testing is not finished, because at least you did some. James Di Virgilio: 7:05 Right. And what’s the alternative? Patient X,Y, Z, you have no ventilator at all. We’re going to have to now make a triage decision to let someone else on this ventilator. And you don’t get one versus your solution, which is, this may not work for three weeks, but also it may work for three weeks. Dr. Sem Lampotang: 7:19 Correct. But at that point would know it’s been working for two weeks. So that’s why then ethically each its a bit more defensible because we did as much as we could until the virus overtook our testing, right? James Di Virgilio: 7:32 Creating an emergency situation where then innovation in this case allows for at least an opportunity as you’re mentioning to improve it. Now, the FDA gets talked about a lot in crisis like these, are they helpful? Are they harmful? As far as what the FDA has been doing? Again, you mentioned before the show, they’ve been relaxing, some restrictions we’ve seen this in the news. Do we feel like we’re in a spot where, what you said would be possible where the FDA would allow an emergent situation, people to have to try some of these ventilators that have been obviously operating for a while, or do we think that they wouldn’t be allowed into the system in an event like that? Dr. Sem Lampotang: 8:06 The FDA has been flexible, my understanding, but this is third hand. I have no way to know whether it’s true or not. They have been approving devices that are specific to the in crisis already. So some devices have already been approved under the what’s called the EUA (Emergency Use Authorization), which has a reduced set of requirements. And the FDA has been also flexible in this sense. So they’ve relaxed the rules. And now if our ventilator becomes approved, we intend to file in a week from now. So around April 10th, if we’re approved, the approval is only while the crisis lasts. The moment of the COVID-19 is no longer a pandemic, our approval from FDA would lapse immediately. So I thought that was also very creative from the FDA. And so they’ve been flexible and it’s also helped us to do due diligence on our testing because by following the FDA standards, we can make sure, A: whether they are relevant to this situation and B: how to meet them and then give ourselves an added measure of confidence that we are producing a safe design. James Di Virgilio: 9:17 Now let’s talk about your design in general. So it seems like ventilators range from as cheap as $5,000 to as expensive as $50,000. One of the issues with the Cadillac ventilators, as you mentioned, is that you have staffing concerns as well, only so many people are trained to operate those. I’m imagining that your ventilator does not require extensive training to have someone operated. Is that correct? Dr. Sem Lampotang: 9:40 That is correct. There’s only three settings. So it will not be complicated. One setting is we call it, title volume. How much gas do you want to flow into the patient’s lungs with each breath, a small breath, or a big breath or something in between the second one is what we call the breathing frequency. How often do you want this patient to breathe? 10 times a minute, 15, 20, 25, 30. And then the next one is how long, how much longer is exhalation compared to the inhalation? And it’s a ratio. So it is one to two, one to one or one to three. And that’s it. That’s the ventilator. James Di Virgilio: 10:20 And so it’s much simpler. To give me a difference someone who knows really nothing about ventilators, how much less effective would this be in a serious case someone’s in the ICU, they have a serious case. Would your ventilator be able to get 60%, 80% of the way towards the Cadillac one? Or is there a big, big gap between what both of them do? Dr. Sem Lampotang: 10:38 I think it would get to 60% and I’m guessing and what it would not do, you may have heard this term when reading about ventilators , it’s called weaning . Just like you wean a baby from breast milk, to something else. So weaning means if a patient has been on the ventilator a long time, they may become dependent and now you have to slowly wean them from the ventilator. So our ventilator will not have weaning capabilities. That’s what the big Cadillac ventilators have. So instead of forcing the lung each time into the patient, because they can’t breathe, then they start saying, okay, I’m going to wait a bit lets see whether the patient can take a breath on his own or her own . And then if they can the gradually step back and let the patient do more and more spontaneous breaths until finally the patient is breathing on their own. And then they get removed off the ventilator. We don’t have that capability. James Di Virgilio: 11:35 Okay. And that’s probably needed in the most serious cases, right? So in a mid level case, yours would be able to be sufficient. But if you get a really serious one, maybe not so much, and that allows then the hospital to get some flexibility with how they’re treating patients. It gives them scalability with who gets what. Dr. Sem Lampotang: 11:50 Right. So our ventilator is a crisis ventilator to be clear. So it’s really a survival. We’re not trying to win people. We’re trying to prevent them from dying because there’s no ventilator. James Di Virgilio: 12:03 And how difficult was it to build something like this? I know you’re using like Lowe’s and home Depot and normal parts that I could go and purchase right now to do this. How difficult was it to create this design? Because you did it so quickly. Dr. Sem Lampotang: 12:16 The design was a paper design until our lead engineer, David Lizdas in our lab, did they run on a Saturday, which was five days into the project because we were doing a lot of paper designs, lining up things. And then he ran to Home Depot and acquired a lot of parts and then went back to his garage and put something together. And then he FaceTimed me. I look at it, I asked him to do some adjustments, and then I was satisfied at work. And we put it up on the web immediately. Like an hour later, it was on the web. And when we put it on the web, a lot of people saw it. And then we were able to convince a colleague of mine who was initially a bit skeptical. And that’s Dr. Gimme , he’s an anesthesiologist who is retired, but also an electrical engineer. And again, that’s an open source concept. He’s also a ham radio operator. So he brought in all his ham radio buddies, and they’ve been tremendously helpful with the electronics and the software. And one of them was actually the ham operator person is a genius from Bangalore, India. So he’s been tremendously helpful. And now we’re happy that our design is helping him start creating ventilators in India for each country. James Di Virgilio: 13:30 And that’s something to think about in life, I like to think about doing unto others as you would have them do unto you. And how do we love our neighbors? And obviously in the U.S. we’re a very wealthy country. We’re fortunate to be able to have the medical resources we have at the top end. And if you’re looking at a lot of developing countries, they don’t have a lot of those Cadillac ventilators. They don’t have a lot of ventilators at all. Your solution, as you just mentioned, is something that can be downloaded on the internet with the open source. Someone can take that. They can build that. They can use that. How expensive is it for someone to build your ventilator? I see this on the internet and I live in India. What does it cost me to build one of these ventilators? Dr. Sem Lampotang: 14:07 So I mentioned earlier, our design, it’s actually a very specific meaning. It’s called open architecture. Open architecture means speed site design that people can alter, because we don’t know that the part from Home Depot we use in Gainesville, he’s available in India, or for that matter in New York, a gentleman in New York is worried about his state. He’s building one. He went to Home Depot. He couldn’t find some of the parts . So then the idea is, as long as we specify the pod , very clearly, then you should be able to find a substitute. And that’s what happened actually in Mauritius yesterday, Mauritius is where I was born and grew up in the Indian ocean. And they already have a ventilator built with the parts that were available locally. And one of the other ways that this ventilator was designed, it was designed on the assumption that transportation would come to a grind that would be no transportation because of the pandemic . And I was reminded of that because I was texting the engineer and Mauritius building. He said, we don’t have Arduinos , which is the computer running our ventilator. I said, well, you can order it readily on Amazon or Alibaba. And he goes there are no flights come in. The Island is on lockdown for two weeks. And that was exactly how we designed it, that we designed A: that traditional parts would not be available and B: transportation would be disrupted. So then he did what he’s supposed to do. He went and looked for a local equivalent that was available, substituted it. And then today he uploaded a video on our website and you can see the ventilator from Mauritius on it. James Di Virgilio: 15:44 That’s an amazing story. You’ve talked during your creation story about how many people, how many innovators and creative people it takes to have this idea, the power of what you just mentioned of opening your idea to others so that it can be quickly and nimbly changed and altered depending on the environment, the foresight that you had to recognize that if this surge event does happen, people aren’t going to be able to acquire things in the normal means. You just mentioned. So the person you just spoke of, what did it cost them to build this ventilator? Is this $2000 or $3,000 venture? Is it a $30 venture? What does it cost to get one of these up and running? Dr. Sem Lampotang: 16:16 I don’t know. I look at their design, they need a teflon. So I just talked to my lead engineer this morning. So that’s long is a piece of instrument that simulates among all the patients . And that’s how you’re able to test that your ventilator is built to spec, but they don’t have it in Mauritius and probably in India. So I just put something and it’s being uploaded to the web so that everybody can say, okay, we’re going to do not on these ventilator. We’re going to home build a Tessalon so that we can test that our ventilator is built to specifications. James Di Virgilio: 16:49 Okay. And the cost here in Gainesville, when you’re making one of these, what does it cost you to do it here? Dr. Sem Lampotang: 16:54 It’s less than $300. And actually our thinking now has evolved as we’re getting ready to go through the FDA, so that we don’t have to meet all of FDA’s requirement for contamination, from one patient to the patient that uses the ventilator next, the disposable pod is $98 from home Depot total. So the idea is off the patient has used it for up to three weeks, rather than probably to we sterilize it and need the FDA requirements what designed , pushed the realization. We would just throw the whole thing away and bring another one in, because that’s $98. That’s like an expensive meal, right? James Di Virgilio: 17:30 Right. No, it’s remarkable. We anchor this show on the $30,000 to $50,000 ventilator. You had mentioned, you get just a guess somewhere around 60% of the operational capacity, and you’re doing it for 300 or so dollars here in the U.S. that’s remarkable. And that is the productivity of creation, innovation, especially during a crisis time. It’s something that makes innovation. I think so powerful. Obviously what you’re doing is so impactful, not just here but abroad. I mean, imagining that these countries can now give themselves access to a possibly functioning solution during a crisis like this or something that is affordable, that is not going to bankrupt them. That is why the usable is amazing. And of course, this is not the first time this has happened right? Throughout human history. This is the response to crisis is when people are allowed to be able to think creatively and put their solutions together. And what you’re doing is simply remarkable. And to me, it’s just further proof of the power of people working together, working together quickly and producing something that again is just to me , incredible to think of the costs that you’re producing this unit for given to the functionality that it has so far. Just really remarkable. Dr. Sem Lampotang: 18:35 I want to clarify though , the whole team behind us, and also I would be remiss if I didn’t mention the University of Florida. So for example, in open source, you probably understand that the University of Florida has a lot of intellectual property, like Gatorade that funds the university. So generally the university owns everything. The faculty member like me designs. So I have a very good working relationship with the Office of Technology Licensing of the University of Florida because I have multiple patents. So very early I involved Office of Technology. I said, are you okay with this being open source? Because it goes against everything belongs to UF. So UF was also very supportive, they said, run with it. We need this. We are not going to worry because if we had said, oh, if you partner with us, UF has to have X percent of whatever this project would not happen. And I think my technology manager at UF [inaudible] was very supportive, particularly at it. And he said, yes, you have authorization to run with it. Even though what you’re doing is technically against the university’s rules, that they own everything that a faculty member designs. James Di Virgilio: 19:47 And so that’s a further example of flexibility. You mentioned the FDA, you mentioned UF, they’re sort of relaxing the rules in a crisis, which is allowing for this innovation. And obviously here being at the Cade, and we’re very familiar with, with what happens when universities are obviously working closely with inventors and employees, and a question that comes to mind, Dr. Lampotang is, why do this? Why wouldn’t you heard about this crisis set aside what you’re normally working on and do this? I’m certainly assuming it was not to make money, but rather to save lives. But what was your motivation to put aside everything else? And to begin working on this? Dr. Sem Lampotang: 20:21 Many things, first of all, like I told you, building a ventilator is not a challenge for me because I built one, I was a graduate student at UF, so that was none of that can I do it? I knew I could do it. And then when, you know, you can do it and you know, there’s going to be a shortfall , depending on what news outlet you read. We have either 40, 60, or 80 thousand ventilators in the U.S. and the projected need is 1 million. And it almost seems that my path, my journey through life, brought me to this where I was like, you really need to do this because you know how to do this. And you can just stand on the sidelines. And the other thing is on a personal note, I’m a prostate cancer survivor. So I have been in a close shave, and luckily I believe I’m cured. So it is also, when you get a second chance at life, you sort of also say, why was I given that second chance? And you try to get some meaning, to that second chance you were given. James Di Virgilio: 21:17 That’s, that’s powerful. And obviously I think myself on behalf of everyone, listening to this podcast is thankful for people like you that have the expertise to create these things, to save lives. And like you mentioned, I heard you say before, hopefully this is not something that’s even needed, right? Hopefully we don’t reach that level of surge. But if we do, obviously those and others working around the world to find these solutions is what allows us to save lives. And that’s rather remarkable. One last question here, it’s been a great discussion so far, this gets asked more than all the other questions. So we have to ask it looking back. Is there something we could have done to have been more prepared for this situation, with regards to ventilators specifically? Should we have been stockpiling them? Should we have been developing what you’re developing now 10 years ago? Or was this something that we had to go through to then ramp up our efforts to create these ventilators? Dr. Sem Lampotang: 22:09 Yeah, that’s a difficult question. My approach to this is we are where we are . There’s no point in looking back because that is not helpful at this juncture. I would say yes, we could have been better prepared, but we are where we are and we have a shortfall. The thing that’s been uplifting easily, the outpouring of support from all over the U.S. and the world and people volunteering to build and to build them out of their own funds and take it to the local hospitals. Now, the main thing we need to do is clear the regulatory hurdles, but there’s one more twist to this that I want to make sure people understand if it comes to where those ventilators are needed and the FDA approval is not recieved. Some hospitals are going to basically have a consent form that will tell the patient. This is a ventilator that has not been fully tested. Some testing has occurred, but it was not completed. Do you want to go on this ventilator? Do you consent to be put on that ventilator? And that’s false under compassionate use. And it’s a relief to know that because to get FDA clearance takes time, and that’s the alternative path. If really our development effort and our FDA regulatory effort gets overtaken by events , that’s the fall back position. And then one last thing from my part is when this crisis is over, there are a lot of under developed countries who lack ventilators, perennially, and the whole design. This design being open source would be continued to be used and maybe improved so that low resource countries can build their own ventilators and safely. James Di Virgilio: 23:56 And thank you so much for the time that you’ve given us and for the message you just put out there, right? I think that’s the goal. Definitely moving forward. As you said, I agree. We can look back into history and take lessons to learn, to improve the future. And what you just said, right there is certainly improving the future. How can we give ventilator access to people across the world? Because I’m sure this won’t be the last virus or surge event we deal with that deals with the respiratory system. And certainly the work that you have done thus far in the work of others than something being open source consistently able to be looked at and improved and tweaked and tested and changed very quickly because of its open source nature will allow for the fastest adaptation of getting to the best result. And I applaud you for your time for your efforts, for what you and your team have done through the University of Florida, through all of your colleagues, putting time aside to do this. It certainly is again, the power I think of individuals getting together and creating solutions to very complicated and difficult problems. I’ve enjoyed our discussion today, Dr. Lampotang, thank you so much for being with us. Dr. Sem Lampotang: 24:53 Same here . Thank you so much. Stay well James Di Virgilio: 24:55 For Radio Cade, I’m James Di Virgilio. Outro: 24:58 Radio Cade is produced by the Cade Museum for Creativity and Invention located in Gainesville, Florida. This podcast episodes host was James Di Virgilio and Ellie Thom coordinates, inventor interviews, podcasts are recorded at Hardwood Soundstage, and edited and mixed by Bob McPeak. The Radio Cade theme song was produced and performed by Tracy Collins and features violinist, Jacob Lawson.

Andrew Quitmeyer lives in Gamboa, Panama running DinaLab, a center for Digital Naturalism. He works to change the way researchers interact with their data collecting by moving the lab to the floor of the rainforest. The implications of his ideas go way beyond scientific study, it seems similar to Francisco Varela's "Embodied Cognition" only with Arduinos, LED's, and laser cutters. Confused? Good, that is a good state of mind to begin this podcast.

Gabi Ferrara and Jon Foust are joined today by fellow Googler Zack Akil to discuss machine learning and AI advances at Google. First up, Zack explains some of the ways AutoML Vision and Video can be used to make life easier. One example is how Google Photos are automatically tagged, allowing them to be searchable thanks to AutoML. Developers can also train their own AutoML to detect specific scenarios, such as laughing in a video. We also talk Cloud Next 2019 and learn how Zack comes up with ideas for his cool demos. His goal is to inspire people to incorporate machine learning into their projects, so he tries to combine hardware and exciting technology to think of fun, creative ways developers can use ML. Recently, he made a smart AI bicycle that alerts riders of possible danger behind them through a system of lights and a project to track and photograph balls as they fly through the air after being kicked. To wrap it all up, Zack tells us about some cool projects he’s heard people use AutoML for (like bleeping out tv show spoilers in online videos!) and the future of the software. Zack Akil When he’s not teaching machine learning at Google, Zack likes to teach machine learning at his hands-on data science meetup, Central London Data Science Project Nights. Although he works in the cloud, most of his hobby projects look at different ways you can embed machine learning into low-power devices like Raspberry Pis and Arduinos. He also likes to have a bit of banter with his mixed tag rugby teams. Cool things of the week Stackdriver Logging comes to Cloud Code in Visual Studio Code blog Open Match v0.8 was released last month site Cloud Spanner now supports the WITH clause blog Interview Zack’s Website site Cloud AutoML site AutoML Video docs AutoML Vision site AutoML Vision Object Detection docs Coral site TensorFlow.js site Central London Data Science Meetup site Question of the week How do I run Cloud Functions in a local environment? Where can you find us next? Zack will be at DevRelCon. Gabi will be taking time to recharge after conference season, then visiting family. Jon will be attending several baby showers. Sound Effect Attribution “Small Group Laugh 4, 5 & 6” by Tim.Kahn of Freesound.org “Sparkling Effect A” by CetSoundCrew of Freesound.org

Programming doesn't have to be so hard. Computer Science teacher, Michael Backus, gives us advice to help make programming easier. www.coolcatteacher.com/e567   Michael Backus - Bio As Submitted Michael Backus teaches computer literacy and computer science at Teeland Middle School in Wasilla, Alaska. As the creator of the https://www.akrobotnerd.com, he has shared many projects that he has developed over the years, the most famous being his Artificial Intelligence with Arduinos curriculum. His most recent project is Build and Program Games with Arduino, a curriculum that introduces students to Arduino by walking them through how to make an electronic Tug-o-War and Simon Says game. In addition to creating curriculum, Michael also writes software to make life easier for teachers. His most recent work is a trio of G Suite add-ons (Document Evaluator, Slideshow Evaluator, and Spreadsheet Evaluator) that make communicating assignment requirements, managing peer evaluations and grading much faster and easier.

Michael Backus had a problem as he was teaching in Google Classroom. So, he programmed add-ons to solve the problem of needing checklists attached to his Google Classroom assignments. He saw a problem and programmed a solution, first by creating an add-on for just within his district. Many people don't know that this is possible or that add on's can be just within a district. We also discuss a "make your own extension" resource by Wanda Terral. Learn about Google Classroom teaching practices as well as a problem-solving attitude that you can bring to your own school. www.coolcatteacher.com/e557 Today's Challenge As I mentioned in the show, I was in Memphis this summer, Wanda Terral had a mini class on programming an extension for your district. There are teachers creating add ons and extensions inside their district. So, your challenge today is to explore and look at the add ons inside your favorite Google App and to find at least one time-saving add on or browser extension. After you find it, or if you already have one – share it to #edtechfind on the social media of your choice.    Resources Document Evaluator: https://chrome.google.com/webstore/detail/document-evaluator/dnjkieiolpkkdgabfmneenjoccdlkggg?authuser=0 Slideshow Evaluator: https://chrome.google.com/webstore/detail/slideshow-evaluator/iafonlflbncinmmdcbcdpohmbmnpnfpi?authuser=0 Spreadsheet Evaluator: https://chrome.google.com/webstore/detail/spreadsheet-evaluator/bcjhagclodbbgjajonpknhmkkilckalo?authuser=0 Wanda Terral's - Program Your Own Chrome Extension Michael Backus - Bio as Submitted Michael Backus teaches computer literacy and computer science at Teeland Middle School in Wasilla, Alaska. As the creator of the https://www.akrobotnerd.com, he has shared many projects that he has developed over the years, the most famous being his Artificial Intelligence with Arduinos curriculum. His most recent project is Build and Program Games with Arduino, a curriculum that introduces students to Arduino by walking them through how to make an electronic Tug-o-War and Simon Says game. In addition to creating curriculum, Michael also writes software to make life easier for teachers. His most recent work is a trio of G Suite add-ons (Document Evaluator, Slideshow Evaluator, and Spreadsheet Evaluator) that make communicating assignment requirements, managing peer evaluations, and grading much faster and easier. Blog: https://learn.akrobotnerd.com  

Muy buenas a todos, espero que hayáis tenido una Semana Santa estupenda y una vez más nos vemos por aquí con las pilas cargadas y muchas ganas de meterle mano a nuestros Arduinos.Hoy contamos con la presencia de Germán Martín y José Manuel Galileo, que, aunque parezca mentira casi desde navidades que no estamos los tres juntos en el podcast.Vamos a hablar de qué es un servidor VPS y cual he escogido para meterle mano durante estos meses, además de la nueva actualización de nuestro querido Node-RED, a la esperada versión 1.0, con muchas novedades.Además, hablaremos de un proyecto Open Source muy interesante de la mano de Julián Martínez, un chico de 16 años que quiere mandar satélites al espacio de forma económica y libre.Finalmente hablaremos de mi nuevo ‘juguete' para poder medir consumos en nuestros proyectos a otro nivel y del último proyecto de Germán, el EnigmaIot.Dicho esto, no te entretengo más, ponte los cascos, sube bien en volumen, abre la lata de cerveza (o lo que estés tomando) que te espera un episodio con muchas, muchas novedades interesantes.Comenzamos :)Más información en https://programarfacil.com/podcast/noticias-proyectos-dispositivos-makers-open-source/

The Golden Integrated CircuitParkerPropeller Development Stick Type-C Addition Found the BQ24165RGET to handle the lithium battery power management New battery management IC handles dual inputs thus replacing the TPS2113ADRBR power mux and p-channel mosfet Wagon Tach Project Signal is a 50V pulse from the distributor Arduinos do not like 50V Wagon Powered Mirror PCB Installed! 3D printed a bracket and installed into the door Tag Connect Probe Ends Will give a full report on how well they workStephenMacro Amp Milling the top panel Transformers mounted - check! PCB mounting needs fasteners ordered J-Fet buffer for the NuTubes Riaa filter with gain options for MM and MC type A series of filter specifications for recording If the record is cut with lower bass then the cut width can be smaller allowing for more info to be cut on to the record - More music playing time Two poles and one zero R.F.O.Gain ultra-high power density for 100-W USB Power Delivery adapters Texas Instruments application document for a very dense, high power AC to DC power supply Designed around providing the power for a 100W USB Type-C charger Complete 5-Watt Power Supply in IEC Main Filter Case Combines a IEC60320 (C13 coupler) connector with EMI filtering and a AC to DC power supply Greatly simplifies product design Due to cost Parker only sees this used in low volume / high margin products and one off art installations TI Claims Breakthrough BAW Technology Bulk Acoustic Wave (BAW) resonator technology though should it be BAWRT? Will reduce BoM cost and PCB size Discussion on how to store parts Part bins, boxes for projects, and proper tool storage Parker's fasteners drawer is getting out of hand How do you organize your parts?Announcements!KiCon 2019 is a user conference for the popular open source CAD program KiCad. Happening April 26th and 27th 2019 in Chicago IL, this is the first and largest gathering of hardware developers using KiCad. Talks at the conference will span hardware design, revision control, scripting, manufacturing considerations, proper library management and getting started developing the underlying tools. All announced talks have been listed on the conference site.Visit our Public Slack Channel and join the conversation in between episodes!

Akbar Agha earned an Bachelor of Science degree in Mechanical Engineering from the University of Illinois and is a Statistical Analyst at Grainger. Akbar enjoys amateur car road racing, doing do it yourself projects with Arduinos and enjoys Salsa dancing. He has changed careers three times since he graduated in 2014 but his mechanical engineering degree has empowered him to pretty much do anything he wanted. For statistical analysis you need to know how to apply math and he had to do some self education beyond the mechanical engineering degree to be qualified. If he had to go back to college knowing what he knows now he would have leaned towards electrical or computer science. He recommends getting some programming experience in high school and in college figure out how to work well with people. Best advice is that everyone’s advice is biased to their own situation, there is no right answer, listen to what they have to say and pick it apart and apply it to your situation and a personal habit for success is exercise and a healthy diet. H Recommends Evernote for note taking and the book he recommends is “Dreams of My Father” by former President Barack Obama. Parting guidance is don’t define your goals by what others around you expect of you define them as what makes the most sense to you. You can get a free book from Audible at www.stemonfirebook.com and can cancel within 30 days and keep the book of your choice with no cost. Free Audio Book from Audible.

Al Williams and the Field Programmable Gate ArraysFPGA Mega Podcast with Al Williams: What is an FPGA? Field-programmable gate array Bunch of logic gates and sea of gates, we tell them what to do Writing hardware description of what it will do - writing requirements language, You’re describing requirements Using VHDL or veralog, syntax is close to the C programming language Why not a microcontroller? Advantage with FPGA = parallel hardware, not a brain with steps and time running out People use FPGAs to get fixed deadline on when processes get finished 100 arduinos on an FPGA - next HackADay Article Mike “Hamster” Field Do you need hardware? No, you can do things via simulation. EDA Playground Can play around for free and don’t have to create login IceStick/IceStorm IceStick is a Lattice FPGA dev board: good starter tool IceStorm is an open source development tool chain HackADay Learning FPGA Links Learning Verilog for FPGAs: The Tools and Building an Adder Learning Verilog for FPGAs: Hardware at Last! YouTube series Visit our Slack Channel and join the conversation in between episodes!Tags: 100 Arduinos, Al Williams, EDA Playground, electronics podcast, Field Programmable Gate Arrays, FPGA, IceStick, IceStorm, MacroFab, macrofab engineering podcast, MEP, Podcast

FallCue 2017 and the Podfather Thursday 10/26 Need you to present right now! (Audio in the Classroom) Sketch 50 w/ Misty Kluesner & Cate Tolnai https://fallcue2017.sched.com/event/CBKO/sketch50-lean-into-your-growth-mindset No room for you! Friday 10/27 Playtime in the STEAMpunk Playground https://fallcue2017.sched.com/event/CBOx/cue-steampunk-playground Ozobots and Spheros Helping to set-up, more than willing... Digital Breakout Edu with Microsoft OneNote http://fall.cue.org/event/CBKl/breakout-with-onenote with Maria Turner & Melinda Richwine https://fallcue2017.sched.com/event/CBKl/breakout-with-onenote Circuit Studies with Makey-Makeys with Rick Phelan https://fallcue2017.sched.com/event/CBPI/circuit-studies-with-makey-makeys Better Together Learning Network https://fallcue2017.sched.com/event/Cbf7/better-together-learning-playground https://docs.google.com/drawings/d/15FKahYvTdu4_IjeZ6Ge9km10Gn1UB1Eno8saNrgCHfY/edit Aurdino: What is it what do I do with it? with David Platt, Heidi Baynes and special guest Roger Wagner of Hyperduino and Hyperstudio https://fallcue2017.sched.com/event/CBPf/arduino-what-is-it-what-do-i-do-with-it Saturday 10/28 Tried to get into Lesson Builder's Fair session with Jon Corippo and Lindsey Blass http://fall.cue.org/event/CBQH/lesson-builders-fair-a-bold-approach-to-lesson-design Absolutely packed, next time. Went to http://fall.cue.org/event/CBQ7/why-the-maker-movement-matters-in-education-exploring-the-new-steam-power with David Thornburg and his wife Norma -STEAM curriculum areas with 3D printers, Arduinos, micro:bits and other new tools for the K-12 classroom. http://fall.cue.org/event/CBQp/tubes-tape-and-imagination-starting-and-sustaining-a-future-ready-lab with Jennifer Harrison Principal, Tustin Unified School District and Traci DiLellio Teacher Grades 3/4, Tustin Unified School District http://fall.cue.org/event/CBRT/tech-out-that-open-house with Monica Bennett and Valerie Sun Finally, http://fall.cue.org/event/CBRx/makerspaces-nuts-and-bolts with Heidi Baynes TOSA-Instructional Technology, San Jacinto Unified School District, Gabrielle Henderson, Denise Leonard, Mark Synnott, Joseph Williams and again special guest Roger Wagner. Sunday 10/29 Podfather Leo Laporte https://twit.tv/shows/the-tech-guy/episodes/1435?autostart=false check out about the hour and fifteen minute mark to see us in the studio, and a sticker of ours on Leo's Desk.

This week Michael sits down with electrical engineer and entrepreneur Ken Burns. Ken is the founder of TinyCircuits, a company that designs and builds tiny open source electronics for makers and hobbyists. Ken talks about the inspiration behind his invention, ‘TinyDuino’ ,an Arduino compatible board that’s less than the size of a quarter (3:50), why he chose to manufacture all his own electronics in-house (10:35), and how he came up with the idea for ‘Tiny Arcade’, a miniature Arduino that you can play games on (25:35).

This week we look at where Arduinos are proving useful for makers and scientists alike.

If you ever have a project using two or more Arduinos, it's likely you'll want them to work together. Say for example you have one Arduino connected to an LCD shield, and another Arduino controlling an LED matrix.  You want both to do something when you press a single button - how can this be done? It turns out to be extremely easy.  This video will describe in detail how to trigger multiple Arduinos with a single input. CODE: /* Button Turns on and off a light emitting diode(LED) connected to digital pin 13, when pressing a pushbutton attached to pin 2. The circuit: * LED attached from pin 13 to ground * pushbutton attached to GND through pin 2 on two (or more) Arduino's * Note: on most Arduinos there is already an LED on the board attached to pin 13. created 2005 by DojoDave modified 30 Aug 2011 by Tom Igoe Modified 16 APR 2015 by Michael James https://programmingelectronics.com/using-the-same-input-to-trigger-multiple-arduinos/ This example code is in the public domain. http://www.arduino.cc/en/Tutorial/Button */ // constants won't change. They're used here to // set pin numbers: const int buttonPin = 2; // the number of the pushbutton pin const int ledPin = 13; // the number of the LED pin // variables will change: int buttonState = 0; // variable for reading the pushbutton status void setup() { // initialize the LED pin as an output: pinMode(ledPin, OUTPUT); // initialize the pushbutton pin as an input: pinMode(buttonPin, INPUT_PULLUP); } void loop() { // read the state of the pushbutton value: buttonState = digitalRead(buttonPin); // check if the pushbutton is pressed. // if it is, the buttonState is HIGH: if (buttonState == LOW) { // turn LED on: digitalWrite(ledPin, HIGH); } else { // turn LED off: digitalWrite(ledPin, LOW); } }   Breadboard Layout:   Downloads: Schematic Fritzing File.fzz   If you like this tutorial, check out some of out very best by signing up for our free Arduino Crash Course below.

Do you have an application where you want multiple buttons for different user inputs?  Maybe you have a timer and you want one button for minutes and another for hours. But there is a problem – you only have room for one button! In this tutorial, we are going to use Arduino to explore how to make one button have the functionality of two or more. Click here to join our 12-part HD Video Course.   You Will Need: (1) Momentary push button (5) Jumper wires (1) Solderless breadboard (2) LEDs (2) 220 Ohm resistors Set Up The Circuit: To demonstrate making one button have the functionality of two or more, we will set up a simple circuit with 2 LEDs and a button.  Based on how we press the button, different LEDs will illuminate. Follow the instructions and schematic below to get the circuit set up before we dive into the mechanics of the Arduino code. Using a jumper wire, connect any GND pin from the Arduino, to the ground rail on your breadboard. Place an LED on your breadboard, make sure to note which way the long leg is facing. Using a jumper wire, connect pin 13 from your Arduino to the breadboard in the same channel where you have the long leg of the LED attached. Now connect one side of the 220 Ohm resistor to the short leg of the LED, and connect the other leg to the ground rail on the breadboard.  The orientation of the resistor doesn’t matter. Repeat this using pin 12, and another LED and resistor. Finally, place your push button on the breadboard.  Depending on the style of your pushbutton, they often fit well straddling the long trench that goes through the breadboard. Connect a jumper wire from one side of the button to pin 2 on the Arduino. Connect a jumper wire from the other side of the button to the ground rail on the breadboard. That's it for the circuit setup.  Now, when you press the push button (which will electrically connect both sides of the button), pin 2 to will have ground voltage applied.  We will use this ground voltage input to trigger our different functions. Examine the Sketch: There are couple ways to implement the multi-function button press using Arduino. One way is to have the number of presses determine the output.  For example, a single click might highlight the “hour” field of an LCD timer and a double click might highlight the “minute” field of the display. Another way that we can implement multiple functions with one button is for the user to hold down the button for different lengths of time with the length of the hold determining the output. For example, if the user holds the button for half a second and releases, something happens.  If she holds it for 2 seconds, something different happens. This latter method of using button hold length time to determine separate functions is the strategy we will learn here. Before I go any further though, I would like to thank Steve for creating the base Arduino code that we will be using.  Steve is a member of the Premium Arduino course (a couple of months ago, he was new to Arduino). While creating a home automation project, he was in need of using a single button to do multiple things, and came up with a very simple way to make it happen.  Thanks Steve! Here is the complete sketch, I recommend looking it over first, and then we will discuss it piece by piece below. /*Using a Single Button, create mutliple options based on how long the button is pressed The circuit: * LED attached from pin 13 to ground through a 220 ohm resistor * LED attached from pin 12 to ground through a 220 ohm resistor * one side of momentary pushbutton attached to pin 2 * other side of momentary pushbutton attached to Ground * Note 1: on most Arduinos there is already an LED on the board attached to pin 13. * Note 2: In this circuit, when the button is pressed, Ground Voltage is what will be applied. Created DEC 2014 by Scuba Steve Modified JAN 2015 by Michael James Both members of https://programmingelectronics.com This code is in the public domain */ /////////Declare and Initialize Variables//////////////////////////// //We need to track how long the momentary pushbutton is held in order to execute different commands //This value will be recorded in seconds float pressLength_milliSeconds = 0; // Define the *minimum* length of time, in milli-seconds, that the button must be pressed for a particular option to occur int optionOne_milliSeconds = 100; int optionTwo_milliSeconds = 2000; //The Pin your button is attached to int buttonPin = 2; //Pin your LEDs are attached to int ledPin_Option_1 = 13; int ledPin_Option_2 = 12; void setup(){ // Initialize the pushbutton pin as an input pullup // Keep in mind, when pin 2 has ground voltage applied, we know the button is being pressed pinMode(buttonPin, INPUT_PULLUP); //set the LEDs pins as outputs pinMode(ledPin_Option_1, OUTPUT); pinMode(ledPin_Option_2, OUTPUT); //Start serial communication - for debugging purposes only Serial.begin(9600); } // close setup void loop() { //Record *roughly* the tenths of seconds the button in being held down while (digitalRead(buttonPin) == LOW ){ delay(100); //if you want more resolution, lower this number pressLength_milliSeconds = pressLength_milliSeconds + 100; //display how long button is has been held Serial.print("ms = "); Serial.println(pressLength_milliSeconds); }//close while //Different if-else conditions are triggered based on the length of the button press //Start with the longest time option first //Option 2 - Execute the second option if the button is held for the correct amount of time if (pressLength_milliSeconds >= optionTwo_milliSeconds){ digitalWrite(ledPin_Option_2, HIGH); } //option 1 - Execute the first option if the button is held for the correct amount of time else if(pressLength_milliSeconds >= optionOne_milliSeconds){ digitalWrite(ledPin_Option_1, HIGH); }//close if options //every time through the loop, we need to reset the pressLength_Seconds counter pressLength_milliSeconds = 0; } // close void loop Comments: At the top of the sketch, we find the comments.  You should make it a habit to read the comments in a sketch before jumping into the mechanics of the code.  The comments should lay the groundwork for what is going to happen in the program and will help you interpret the intent of the code as you begin to analyze it. Declare and Initialize Variables: After the comments, we start initializing and declaring variables.  Since, we are going to be tracking time, we need to have a variable to record the length of time a button is being held.  We do that with the pressLength_milliSeconds variable: //We need to track how long the momentary pushbutton is held in order to execute different commands //This value will be recorded in seconds float pressLength_Seconds = 0; Now, you might think that the variable name is really long and annoying.  And I wouldn’t particularly argue with you – I mean, why would I include milliSeconds in the name of the variable? The reason I do this is because I think including the unit of measurement in the variable name is helpful when other people are trying to read your code.  Writing code that other people can read is not only good for other people, but also future versions of yourself who forget what the heck you were thinking when you wrote the code! [End Rant] The next thing we need to set up are the parameters for when options will get executed.  In this example, I have two variables for two options: // Define the *minimum* length of time, in milli-seconds, that the button must be pressed for a particular option to occur int optionOne_milliSeconds = 100; int optionTwo_milliSeconds = 2000; Each option is defined by the number of milliseconds that the button must be held for that specific option to get executed.  In order to get my first option to happen, I have to hold the button for at least 100 milliseconds which is pretty much a short tap on the button. If I want the second option to happen, then I have to hold the button for at least 2000 milliseconds aka 2 seconds. If you wanted more options, you would add more variables here with their corresponding hold times. Our final initializations will be to specify pin numbers for our button and LEDs. //The Pin your button is attached to int buttonPin = 2; //Pin your LEDs are attached to int ledPin_Option_1 = 13; int ledPin_Option_2 = 12; Setup() the Sketch: The setup() for this sketch is pretty straight forward (if it’s not straight forward to you, make sure to check out our free 12-part Arduino Course, after which this setup will be very familiar to you). We want to make sure that the pin our push button is connected to is set as an INPUT_PULLUP: // Initialize the pushbutton pin as an input pullup // Keep in mind, when pin 2 has ground voltage applied, we know the button is being pressed pinMode(buttonPin, INPUT_PULLUP); We do this to make sure that the button pin is not floating (if you are wondering what the heck that means, you can read more on that here – but if you just roll with me until we get through this tutorial, you should be fine ). We also want to specify the pins that our LEDs are attached to as OUTPUTs, because we will be applying voltages to these pins in order to illuminate them: //set the LEDs pins as outputs pinMode(ledPin_Option_1, OUTPUT); pinMode(ledPin_Option_2, OUTPUT); Finally, it never hurts to start serial communications for debugging purposes. //Start serial communication - for debugging purposes only Serial.begin(9600); With setup() complete, now we can jump into the main loop of our sketch… The Main Loop(): We know we are going to have to measure the length of time the button is pressed, and then record it. To do this, we use a while statement whose condition requires the button pin to be in a LOW state (remember, when we push the button, pin 2 will have a ground voltage applied). //Record *roughly* the tenths of seconds the button in being held down while (digitalRead(buttonPin) == LOW ){ Once the button is pressed and held, the while statement starts executing.  The first thing we do in the while statement is to delay 100 milliseconds, and then record that into our time tracking variable: delay(100); //if you want more resolution, lower this number pressLength_milliSeconds = pressLength_milliSeconds + 100; Keep in mind the first time through the loop, pressLength_milliSeconds will be equal to 0, so we are just adding 100 to the variable. It can be handy to know how long the button has been pressed as you add options. To make this easy, we want to print the current value of the pressLength_milliSeconds variable to the serial monitor window: //display how long button is has been held Serial.print("ms = "); Serial.println(pressLength_milliSeconds); Let’s ignore the rest of the code for a second, and imagine what happens if we keep holding the button. The first time through the while loop, we add 100 milliseconds to the time tracking variable and we print that value to the serial port.  The next time through loop, we add another 100 milliseconds to the timer counter variable, and print this new value to the serial monitor. As long as the button is being held down, then we keep adding time to the pressLength_milliSeconds variable – this is the crux of the program. When we release the button, the while statement stops, because the condition is no longer met, and we stop adding time to pressLength_milliSeconds. So let’s pretend we held the button for three seconds, and then let go - what happens? Well, as we discussed, the while statement ends and the next line of code we encounter is an if statement. //Option 2 - Execute the second option if the button is held for the correct amount of time if (pressLength_milliSeconds >= optionTwo_milliSeconds){ digitalWrite(ledPin_Option_2, HIGH); } The condition of the if statement requires that the time we held the button be longer than or equal to the time we set for option number two. If you recall, option number two was set to occur with at least 2 seconds of button press time. Since we held the button for three seconds, this if statement will get executed. And all we do is write HIGH voltage to our “option 2” LED, making it illuminate. What if we had only held the button for one second – then what would happen? If this were case, then the first if statement condition would not have been met, but a subsequent else-if statement only requires the button hold time be 100 milliseconds or more – so the second else-if statement would get executed, which turns on the “option 1” LED. //option 1 - Execute the first option if the button is held for the correct amount of time else if(pressLength_milliSeconds >= optionOne_milliSeconds){ digitalWrite(ledPin_Option_1, HIGH); }//close if options Basically, if we hold the button a long time, the second option gets executed.  If we hold the button a short time, the first option gets executed. If we wanted to add more options, we add the longer hold options at the top, and the shorter hold options at the bottom. I wouldn’t try to squeeze too many options in a small span of time or it might drive the end user crazy trying figure out the timing. Nor would I try to add more than three options for a single button within a given context, or else you chance making your potential end user want to beat you up. To finish up the sketch, we reset our button press timing variable to zero.  This ensures that next time the button is pressed and held, we will start from time zero again. Try On Your Own Challenge: Add another option, which turns off both LEDs.  Try adding it before the first option (you will have to adjust the timing) and then after each option. How tight can you squeeze the option time together?  Experiment and determine what is a good rule of thumb. Download: PDF of this Arduino Tutorial

This is the Pilot episode of our new series looking at the Abilitynet Tech4Good Awards. (http://www.tech4goodawards.com/) Bex (@rebeccawho) from Reason Digital’s (http://reasondigital.com/) Tech for Good Live team (http://www.techforgood.live/) and Producer Paul (@paul_yakabovski) join forces with Mark Walker (@scipmark) from Abilitynet (https://www.abilitynet.org.uk/) who has been running the awards since 2011.We gather together nominees, sponsors, winners, judges and friends of the awards to tell their stories and talk about the latest developments in the sector. In the pilot episode, we brought in Judge, Gareth Ford Williams, (@garethfw) Head of Accessibility, User Experience & Design at BBC Design and EngineeringWe also have previous winner Rachael Moat (@rachaelmoat) who worked on a project using Arduinos to control sound using liquid to make music for youth with autismGive us a shoutout on Twitter @techforgoodlive and @tech4goodawards

Two cyborgs chat about the most important part of any intelligent system-- the brain. In our electronic augmentations, this role is most often filled by a microcontroller. Listen in as we discuss this key component to any simple electronic device.

Podcast Notes First podcast and the first recording in the "Bomb Shelter" (name pending). See Figure 1. Parker is working on an adjustable fixture to work along with the Jig Of Destiny that is currently being used. It will have an adjustable slide to fit multiple panel sizes. The Macro_Duino has been fixed. Parker tied the FT230X's VCCIO to the 3.3V output on the FT230X which is the standard way to do it. The I/O on the FT230X is 5V tolerant so this should be good. The 3.3V regulator on the chip can supply 50mA if you are daring enough to hook some external circuits up to it. Parker's AVR Tag Connect article came out. Go check it out. Stephen has continued his work on his "Synth Engine" that he started while his wife was in surgery last week. Arduino stuff is working well! However the Arduino wasn't working to well for getting high speed frequencies so Stephen moved to the AD9833 - a 28 bit frequency divider. He put a 1Mhz clock generator (ECS-2100AX-1.0MHZ) and can get up to 0.004Hz resolution. See Figure 2. Cadsoft Released Eagle 7.7 which is the first version since the AutoDesk acquisition. Check out the Patch notes. Interesting things are the new licensing options and the signal names on the traces in the layout editor. Arduino V. Arduino – Arduino LLC and Arduino SRL are battling for the Arduino trademark. Has Arduino.cc and Arduino.org settled things once and for all? Thats a lot of Arduinos in the last couple sentences. Yup more Arduinos. They are running a kickstarter called the ESLOV IoT Invention Kit. Why does an established company need to run a kickstarter? IoT devices take over the internet with botnets! 150,000 IoT devices are behind the 1Tbps DDoS attack on OVH Hosting. Most are security IP cameras. IP cameras have been around a lot longer then the buzz term IoT. Special thanks to whixr over at Tymkrs for the intro and outro!

¿Por qué queremos conectar dos Arduinos? Puede haber varias razones para conectar dos o más Arduinos entre si, ampliar las entradas/salidas analógicas y/o digitales, dar más funcionalidad a nuestro proyecto pero quizás, la más interesante sea poder utilizar Arduino MKR1000 como enlace WiFi. Todo esto lo podemos hacer mediante el protocolo I2C de una manera muy sencilla.Esta semana me ha llegado una pregunta de un oyente y alumno del Campus, Javier Tallón. Me preguntaba cómo conectar un Arduino MEGA a una red WiFi. El había adquirido un módulo ESP8266 pero no encontraba la manera de poder conectar estos dos dispositivos por su dificultad. Su idea es poder controlar varias líneas de media potencia de su casa. El problema es que no tiene mucha experiencia en programación y, en cuanto nos salimos de tecnologías plug and play como Arduino, es cuando empezamos a sufrir.No me malinterpretes, el módulo ESP8266 es un dispositivo muy bueno, barato y que nos da un rendimiento y funcionalidad excelente. La pega es que hay que tener conocimientos medios de programación, comunicación y electrónica.Por lo tanto mi respuesta fue clara, si realmente quieres hacerlo sin dolores de cabeza, compra un Arduino MKR1000. Esto si que es tecnología plug and play, solo tienes que ver el curso donde explico cómo lo puedes configurar, con solo dos lecciones está listo para usar.La otra cuestión es cómo comunicar un Arduino MKR1000 con un MEGA. Esto lo podemos hacer muy fácilmente gracias al protocolo de comunicación I2C, pero esto lo veremos más adelante.Ahora lo que veremos es una comparativa extraída del blog Pensando con Lógica de Jorge Aranda. Hace tiempo escribió un artículo donde explica las diferencias técnicas técnicas entre estos dos dispositivos cuando trabajan de manera autónoma es decir, sin conectar el ESP a una placa de Arduino. Aquí te voy a hacer un resumen:PrecioESP: aprox 6€MKR1000: 31€TamañoEl Arduino MKR1000 es 3 veces mayor que un módulo ESP. Ojo con esto si queremos hacer un proyecto final pequeño.AlimentaciónESP: 3,3V - 12 mAMKR1000: 5V - 7 mAFrecuencia del reloj (importante para la velocidad de procesado del código)ESP: 80 MHzMKR1000: 48 MHzMemorias Flash / SRAM / EEPROMESP: 512 Kb / 64 Kb / No tieneMKR1000: 256 kB / 32 Kb / No tienePines digitales/analógicosESP: 11 Digitales (11 PWM) + 1 analógicoMKR1000: 8 Digitales (4 PWM) + 7 analógicosProgramaciónESP: es más complicado de programar, necesitamos conectar a un puerto USB/Serie a través de otros componentes, necesita alimentación y configurar el entorno de desarrollo.MKR1000: a través del IDE de Arduino configurándolo y con el lenguaje nativo de Arduino.Yo no voy a entrar en el debate de si uno es mejor que otro, dependerá de los requisitos técnicos de nuestro proyecto. Si que puedo decir que es recomendable tener conocimientos medios de electrónica, programación y comunicación para enfrentarse a un módulo ESP.Si lo que queremos hacer es que el módulo ESP se utilice como enlace para conectar a la red WiFi, lo podemos hacer a través del monitor serie, haciendo las conexiones pertinentes y con comandos AT.La solución propuesta a Javier es utilizar el Arduino MKR1000 como un enlace WiFi. Para ello tenemos que conectar los dos Arduinos mediante el protocolo de comunicaciones estándar I2C, del cual ya te he hablado en el artículo donde explico como hacerlo.Gracias a este protocolo no solo podemos conectar uno o varios Arduinos, también podemos añadir al bus de comunicación sensores y otros dispositivos como una pantalla LCD.Recurso del oyenteEl recurso del oyente nos lo ha enviado Javier Tallón. Se trata de un sistema para gestionar nuestros dispositivos domóticos, Domoticz. Es un software de código abierto escrito en C++, muy ligero y multiplataforma, se puede ejecutar en Raspberry Pi, Windows, Linux, Mac OS X e incluso en un servidor NAS de Synology.El core o corazón trabaja con un proceso en background. No nos enteramos ni que está instalado. Para acceder lo haremos a través de una interfaz basada en la web y escrita en HTML5 y CSS3.Este sistema nos sirve para configurara y supervisar dispositivos cómo luces, interruptores, sensores de temperatura, lluvia, viento, ultravioleta y un largo etc...Dispone de un sistema de notificaciones a cualquier dispositivo móvil. Como dicen ellos, es totalmente gratis, solo tienes que invertir en hardware.Soporta una larga lista de protocolos entre los que destacan X10, Z-Wave, Apple Homekit con soporte para Siri y Bluetooth Audio.Y hasta aquí el programa de hoy, recuerda que nos puedes valorar en las diferentes plataformas de podcast iVoox, iTunes y en Spreaker, nos harás un gran favor y así podremos llegar a más gente.

Hoy vamos a hablar del Arduino Day y del protocolo de comunicaciones Firmata. El Arduino Day es la celebración en todo el mundo del cumpleaños de Arduino y Genuino, te recuerdo que por problemas de marca Arduino se llama Genuino fuera de USA. Es un evento durante 24 horas que se celebra el 2 de abril de cada año. Los diferentes eventos pueden ser organizados por la comunidad o por los fundadores, donde las personas interesadas en Arduino se reúnen, comparten sus experiencias y aprenden cosas nuevas.En el campus de programarfacil, hay un nuevo curso que estamos preparando, si quieres mantenerte informado y que te avisemos cuando esté preparado date de alta accediendo al formulario.Este año han sido 331 eventos en 68 países de todo el mundo, en España han sido 29 repartidos por toda la geografía. Este año ha sido imposible organizar algún evento en nuestra ciudad, Alicante, pero te prometemos que el año que viene seremos parte del Arduino Day organizando nuestro propio evento al que esperamos que asistas.Podías seguir dicho evento a través de las redes sociales, estuvieron muy activas, con fotos, vídeos y artículos, todo centrado en este día especial para Arduino. Si quieres ver los diferentes eventos, puedes ir a la web oficial de Arduino Day.Además de los eventos repartidos por todo el mundo, este día aprovechan para hacer presentaciones de nuevos productos y diferentes anuncios relacionados con Arduino. En esta ocasión hay tres noticias importantes.Por un lado han puesto a la venta la tan esperada placa MKR1000 con un precio de 30,99 €, de la cuál hemos hablado en diferentes ocasiones y a la que dedicaremos bastante tiempo. Es una placa orientada principalmente al IoT.También se ha presentado el Arduino Project Hub, una nueva plataforma donde compartir experiencias y proyectos para toda la comunidad. Arduino es el referente en los microcontroladores de todo el mundo, uno de sus puntos fuertes es la cantidad de información que podemos encontrar en Internet alrededor de esta placa. Hay multitud de proyectos y tutoriales al respecto pero, Arduino a ido más allá. A presentado Arduino Project Hub, la plataforma de tutoriales alimentado por la más que conocida comunidad hackster.io. Esto abre un mundo infinito al mundo maker y lo más importante, lo recoge todo en una única plataforma donde poder consultar en tiempo real cualquier manual o tutorial paso a paso y pone en contacto a miles de usuarios con el apoyo oficial de Arduino.Dentro de esta plataforma también encontramos el nuevo IDE oficial, Arduino Create, del cuál ya hemos hablado en el capítulo Arduino basado en la web y que por el momento esta en fase beta.Y por ultimo y quizás la más importante, a mi modo de ver, se ha publicado el Manifiesto IoT donde se habla del cambio que se nos viene encima gracias a este movimiento. Los fundadores de Arduino creen que el IoT puede cambiar la manera en que los ciudadanos viven en las ciudades y apuestan por hacer crecer este entorno con plataformas de hardware y software libre. Proponen que los dispositivos conectado deben ser:Abiertos: el código y el hardware abierto es la mejor manera para fomentar la innovaciónSostenibles: en contra de los productos de consumo rápidos.Justos: que cada usuario tenga el control de sus datos, sin intermediarios.No cabe duda que la era del IoT ha entrado en Arduino para quedarse, dando un puñetazo en la mesa a todos aquellos que, de alguna manera, quieren apoderarse tanto del mercado que lo rodea, como de la mina de diamantes que puede generar los datos producidos por estos dispositivos.Protocolo FirmataEl protocolo Firmata es un protocolo para comunicar con microcontroladores desde cualquier software o cualquier ordenador conectado. El objetivo primordial de este protocolo es hacer que el microcontrolador sea una extensión de nuestro entorno de desarrollo. Fue diseñado para ser abierto y flexible para que pueda ser soportado por cualquier lenguaje de programación, también debe ser simple de implementar en el microcontrolador y en el ordenador.La implementación de referencia es la librería para Arduino/Wiring la cual está incluida en el entorno de desarrollo oficial de Arduino a partir de la versión 0012.Firmata fue creado en el 2006 como una demo para Arduino por Hans-Chistoph Steiner. Se le ocurrió mientras estaba trabajando en un proyecto musical con dispositivos Eroktronix MIDItron conectados a varios Arduinos con varios sensores conectados. Cuando tenía que hacer una modificación en el código, debía replicarlos en todos los Arduinos.Cuando se trabaja con microcontroladores, siempre es necesario disponer de un ordenador y un cable para comunicación serie con los microcontroladores. Estos son utilizados para capturar información a través de los sensores y actuar en consecuencia con los dispositivos conectados. En este caso se hace necesario un protocolo serie que permita comunicar el microcontrolador y el ordenador. Debido a que este tipo de proyectos utilizan un único ambiente de programación, se hace evidente que los microcontroladores deberían ser una extensión del entorno de desarrollo en lugar de un dispositivo ajeno al proyecto, con su propio lenguaje de programación.El desarrollo inicial de Firmata se centró en la placa de Arduino y en la actualidad sigue siendo el foco principal. La librería ha sido portada a toda la familia de Arduino y a Wiring. Cualquier placa compatible puede utilizar el protocolo Firmata o la librería asociada.Pero no solo existe Firmata como protocolo de comunicaciones, también hay otros tipos de protocolos, protocolos ASCII, Open Sound Control, Gainer, USB HID, MIDI, SLIP etc... y precisamente Hans-Chistoph se basó en todos ellos para crear un protocolo estándar y principalmente en el protocolo MIDI.El protocolo Firmata se basa en la representación de la API de Arduino (comandos del lenguaje) y los tipos de datos que se transfieren entre la placa y el ordenador. Está enfocado en la facilidad de uso aunque esto conlleve un peor rendimiento. El protocolo MIDI fue elegido como el núcleo central de Firmata debido a su eficiencia, su facilidad y por la gran cantidad de implementaciones existentes de libre acceso. Firmata implementa solo el formato de mensajes de MIDI.MIDI (Musical Instrument Digital Interface) es un protocolo, interfaz digital y conectores que se utilizan para comunicar y conectar ordenadores, instrumentos musicales eléctricos y otros dispositivos entre si.El protocolo MIDI utiliza unos mensajes estándar para la comunicación. En el caso de Firmata estos mensajes han sido sustituidos y se creó un nuevo conjunto de mensajes tanto para los tipos de datos (analógicos y digitales) como para los mensajes de control (pinMode, digitalWrite, etc...). Esto hace posible representar la API de Arduino usando mensajes de Firmata además, da soporte a más de 16 pins analógicos con una resolución de 14 bits y más de 128 pines digitales.Gracias a su condición de código abierto, se han implementado diferentes versiones que dan soportes a multitud de funcionalidades de los microcontroladores. La versión original es la Standard_Firmata que viene se incluye dentro de las versiones del entorno oficial de Arduino y Wiring. Hay que recordar que el entorno de desarrollo de Arduino se basa en la plataforma Wiring. Esta versión incluye soporte para las siguientes características:Entradas y salidas analógicasEntradas analógicasSalidas PWMConmutación entre entradas y salidas analógicasServomotoresMatrices de LEDsI2CAdemás de las funcionalidades a las que tenemos acceso, también hay que destacar que es compatible con multitud de lenguajes de programación y es multiplataforma. Solo tenemos que buscar en los repositorios como GitHub y encontraremos infinidad de implementaciones de este protocolo. A continuación mostraremos unos cuantos pero puedes encontrar muchos más en la web oficial.Pyduino (Python)ProcessingC++/openFrameworksSolid Soils (C#)Sharpduino (C#)4ntoine (Java)Johnny-five (JavaScript / node.js)Hardbap (Ruby)Carica-firmata (PHP)Volviendo hacer mención a lo que dice el creador de Firmata Hans-Chistoph, es muy buena idea hacer que Arduino sea una extensión de el entorno o plataforma de programación que utilices pero, hay que tener en cuenta que tiene limitaciones, no va a servir para todos los casos que queramos.Sin duda alguna nos abre las puertas a otros lenguajes de programación con el que nos sintamos más cómodos, como menciona en alguno de sus capítulos Gabriel Viso en el podcast Pitando, la programación física puede ser más divertida con lenguajes como Python.A continuación te dejamos unos ejemplos donde hemos utilizado Firmata con C# y con JavaScript.Control Arduino motor 28BYJ-48 con una aplicación WPFRecurso del díaVisualinoVisualino es un entorno de programación para Arduino. Está basado en la plataforma Google Blockly, el editor visual que permite crear entornos de desarrollo de lenguajes visuales. Es muy fácil de usar gracias a su entorno intuitivo y a que se encuentra en múltiples idiomas. Al contrario de plataformas como S4A, genera el código nativo de Arduino a partir de la programación por bloques, lo que permite la ejecución de programas independientemente del ordenador. Es un software libre y puede ser modificado.Muchas gracias a todos por los comentarios y valoraciones que nos hacéis en iVoox, iTunes y en Spreaker, nos dan mucho ánimo para seguir con este proyecto.

Scott sits down and talks with Lyza Gardner, CTO of Cloud Four and long-time web expert, about her recent explorations into hardware using the Johnny-Five Framework. You can control Arduinos and other devices and make robots with brains written with Node.js and JavaScript! Is this the framework we've been waiting for?

Simone Giertz is a Maker, a robotics enthusiast and surprisingly (her words!) a non-engineer. She's become somewhat of an expert in sh*tty robots and we love her for it. Also, she happens to be Swedish but sounds totally American just to confuse us. Scott talks about how she gets her inspiration and how she got started!

Jeremy Sarachan OF St. John Fisher College presents "Find an Art Gallery and Show Off Student Work" at the 2015 NMC Summer Conference in Washington, D.C. By coordinating a class with a student-run art show, students were able to invent creative installations with Processing, Arduinos, and Makey-Makeys. The class, “Algorithmic and Data Art,” covers new media art theory and the creation of physical computing interfaces while fulfilling an arts requirement for the college core.

Primer capítulo de la serie que os iremos presentando donde veremos como crear un proyecto con Arduino y tecnología web, en este capítulo, Arduino entradas y salidas, os explicaremos como podemos conectar dispositivos al Arduino a través de las entradas y salidas.Pero como siempre ya sabéis, si queréis contactar con nosotros lo podéis hacer a través del formulario de contacto o de Twitter @programarfacilc. También tenéis una lista de distribución a vuestra disposición para que os suscribáis.En el Arduino UNO existen entradas y salidas analógicas (6) y digitales (16). Por un lado las analógicas son utilizadas, generalmente, para dispositivos de entrada y nos permiten leer un rango de valores. En cambio las digitales pueden tener a la entrada o a la salida 0V o 5V, esto nos indica que ese pin está en estado alto (High) o bajo (Low).Entradas/salidas digitalesSe trata de pines donde el usuario puede activar (poner tensión) o desactivar (quitar tensión). Es similar a escribir 0 y 1, como ya hemos dicho 0V y 5V respectivamente.Los pines 0 (Serial In RX) y 1(Serial Out TX), puerto serie, se usan para comunicación entre dispositivos. La característica principal de los puertos serie es que envían la información bit a bit, enviando un bit cada vez. La versión avanzada de este puerto sería el paralelo que nos permite enviar información en paralelo. Para que se pueda entender imaginaros un tanque lleno de agua, si de ese tanque sacamos un grifo para llenar botellas una a una éste sería nuestro puerto serie, ahora bien, si de ese tanque sacamos cuatro grifos para llenar cuatro botellas a la vez, este sería el ejemplo de un puerto paralelo. En ordenadores, el puerto serie, se usa y se sigue usando para conectar un ordenador con módems, ratones, teclados y muchos más periféricos. En el caso concreto del Arduino UNO, el puerto 0 (RX) sería el puerto serie de entrada y el puerto 1 (TX) sería el puerto serie de salida.Los pines 2 y 3 nos permiten interrumpir el funcionamiento del bucle "loop". Ya hablaremos de este bucle más adelante en otro artículo, pero quedaros con la idea de que es lo que se ejecuta continuamente dentro del código de Arduino. Imaginaros que queremos leer un sensor cada segundo. No hace falta escribir el código infinitas veces, en Arduino existe este bloque que repite todo lo que se encuentre dentro de él indefinidamente. Estos pines paran precisamente ese bucle y obligan a ejecutar un código asignado a cada pin.Los pines 3, 5, 6, 9, 10 y 11 que están marcados con el símbolo ˜, son entradas y salidas especiales ya que aunque son digitales y se pueden utilizar como tal, también se pueden utilizar para la comunicación PWM (Pulse-Width Modulation) modulación por ancho de pulsos. Se trata de una técnica que nos permite transferir información o energía a un dispositivo con una señal cuadrada. Como ya hemos dicho, los pines digitales solo atienden a dos estados, bajo (0V) y alto (5V). Si somos capaces de cambiar el estado alto y bajo controlando el tiempo que está en alto y el tiempo que está en bajo, conseguimos tener una onda cuadrada donde el tiempo que esté en estado alto (5V) será el ancho de pulso. La relación que existe entre estos dos tiempos se llama ciclo de trabajo y se expresa en tanto por ciento (%). Nos indica el tiempo que la señal está en alto en comparación con la que está en bajo. Lo podemos ver con el siguiente ejemplo.pwmEn Arduino existe una función que permite utilizar estos puertos, se llama analogWrite. No podemos utilizar cualquier rango de valores, esta función solo admite valores entre 0 y 255 (8 bits). Por lo tanto y con el ejemplo de ciclos de trabajo que tenemos arriba, podemos definir una tabla donde nos diga el valor correspondiente para introducir en la función analogWrite y la salida en volitios que tendríamos.Ciclo trabajo (%)analogWrite (0 - 255)Salida (Voltios)00025641.25501272.5751913.751002555Si por ejemplo tenemos conectado un led a alguna de estas salidas es fácil imaginar que pasará, cuando esté al 25%, el led tendrá una intensidad del 25 % y así sucesivamente.Los pines 10, 11, 12 y 13 son utilizados para conectar varios dispositivos entre sí, por ejemplo varios Arduinos. Son los pines SPI (Serial Peripheral Interface) ya que precisamente utilizan este estándar de comunicación, definido para comunicar circuitos integrados con comunicación serie a través de un bus de comunicación. El pin 10 es el SS (Slave Select) es el puerto esclavo (Slave). Permite seleccionar el Slave desde el Master o para que el Master active el Slave, si es el esclavo. El pin 11 es el MOSI (Master Output Slave Input). Se usa como entrada de datos del Master y la salida de datos del Slave. El pin 12 es el MISO (Master Input Slave Output) es el contrario del pin 11, permite entrada de datos del Master y salida de datos del Slave. Por último el pin 13 SCK (Select Clock) nos sirve de señal de reloj. Se trata de un pulso, como el visto en los pines PWM, que marca la sincronización entre los dispositivos conectados. Cada pulso de ese reloj se envía o se lee un bit.Entradas/salidas analógicasEn el Arduino UNO tenemos 6 entradas analógicas que van marcadas con una A delante. Aunque pueden ser utilizadas como salida, su uso más común es la lectura de datos de dispositivos analógicos. Tiene una resolución de 10 bits lo que implica que tenemos 1024 valores diferentes, es decir, podemos leer un rango de tensiones desde 0V hasta 5V detectando cambios de voltaje de 0.004V (5/1024).Los pines 4 y 5 soportan la comunicación I2C (Inter-Integrated Circuit), muy parecida al bus de comunicación SPI y sirve para conectar varios dispositivos. En este tipo de comunicación cada dispositivo tiene una dirección única y cada dispositivo puede funcionar como maestro (Master) o esclavo (Slave). El pin 4 es el SDA (Serial Data Line) y se utiliza para la transmisión de datos en serie. El pin 5 es el SCL (Serial Clock Line) suministra la señal de reloj para mantener a todos los dispositivos conectados sincronizados.Otras entradas/salidasAdemás de los pines digitales y analógicos ya explicados existen otros pines que nos dan diferentes funcionalidades.GND (Ground) es la toma de tierra, 0V.AREF (Analog Reference) es el pin que nos suministra la tensión para el rango máximo de los puertos analógicos, normalmente 5V.Vin es la entrada de alimentación de la placa Arduino. Esta entrada no está protegida y por lo tanto hay que tener un especial cuidado con el voltaje que suministramos ya que podemos quemar la placa. Se recomienda una alimentación por USB en el periodo de pruebas.5V y 3.3 V suministra una tensión de 5V y 3.3V respectivamente.RESET sirve para resetear el Arduino si aplicamos la tensión máxima posible (IOREF). Reinicia el Arduino volviendo a ejecutar el Bootloader y el programa que tengamos cargado. Importante, esta función no borra el programa que tengamos cargado en la memoria del Arduino.IOREF (Input Output Reference) es el pin que nos suministra la tensión para el estado alto de los pines digitales. Por norma general si conectamos el Arduino a 5V este pin nos dará 5V, en caso contrario serán 3.3V.Pues hasta aquí el programa de hoy, hemos visto todo lo necesario para poder conectar a nuestro Arduino diferentes tipos de dispositivos. Os esperamos en el siguiente capítulo donde veremos más cosas interesantes sobre Arduino.Recurso del día123d.circuits.ioOs presentamos una aplicación on-line muy interesante. Se trata de una web donde podemos crear nuestros propios diseños con Arduino, se llama 123d circuits y es de la casa Autodesk, los creadores de Pixelr, la aplicación web de retoque fotográfico que ya comentamos el capítulo 9.Además del laboratorio de electrónica donde prototipar, también puedes diseñar tu propia placa de circuito impreso PCB (Printed Circuit Board).Lo mejor de todo es que es gratuito, tienes multitud de componentes y entre ellos un Arduino UNO y un Arduino Micro, resistencias, potenciómetros, servos, leds, protoboard, pulsadores y muchos componentes más, aunque tiene ciertas limitaciones. No nos permite usar sus modelos 3D para uso comercial, tenemos acceso a aplicaciones 3D de diseño, acceso ilimitado a los componentes básicos, acceso a 10 modelos premium, espacio de alojamiento ilimitado en la nube e ilimitados proyectos, tutoriales y acceso a foros.Si quieres empezar con Arduino sin comprar uno, esta es la mejor opción para que te adentres en este mundo.Muchas gracias por todos los comentarios y valoraciones que recibimos a través de las plataformas de podcast ivoox, iTunes y Spreaker.

Manolis Nikiforakis and his team (Dimitris Karagiannis and Thanasis Daglis) set out to create a multiplayer reactive game, using mostly Arduinos and Particle (Spark) Cores, where the losers’ money would automatically be donated to charity! Well, that was the main idea, but -unfortunately- time was not enough for them to fully implement it during the 24-hour duration of BattleHack. Nevertheless, Manolis (a seasoned researcher and developer with 12+ years of experience), confessed to us that he loves taking part in hackathons… just for the fun of it. And, surely enough, we also talked a lot about the opportunities arising all the time, as technology evolves, for example in the relatively new field of IoT. Interviewed by Yannis Rizopoulos for Tech Talks Central.

In this episode of the podcast, I talk with local digital artist and educator Rachel Hooper about how she got started learning and teaching how to make stuff with arduinos. Hooper discussed her background in teaching both students and adults how to construct projects using the tiny microcontrollers, her journey from arduino-learner to educator, then schooled me on gender essentialism* in tech-based learning. And did I mention we were locked in a bathroom at the Generator? (Never let your travel microphones out of your sight, people. Never. Do it.)

Connectivity and ubiquity will play a huge role in how web development for connected devices evolves. The rise of makers & builders in the development community is sparking innovation as well as curiosity in the business world. From connected cars & living spaces to fashion and novelty, The Internet of Things (#IoT) stretches far and wide. We are seeing more and more that our clients and users are demanding applications that integrate seamlessly not just w/ their phones, tablets, and computers but with their tv's, security systems. Many companies are now seeing the viability & market for connected IoT. Many of these companies want to unify product experiences and blur the lines between the physical and digital worlds. With that said, how can we start building our skills and becoming the experts in this development arena?   Whether you are interested in building assembly line robotics, medical technology solutions, or even a simple product with blinking LED's, developers will need to know many things. The security, product development cycles, how to connect devices to together, & how to share and assimilate firmware & software packages are very important. Standardization and assimilation of devices in a secure manner is critical for businesses.   JavaScript's ubiquity & evented I/O model lends itself well to easily build IoT devices. Other languages are just as viable and debatably better at many aspects of IoT but JavaScript makes it easier, approachable, and portable.   NPM (@npmjs), the Node Package Manager, is used across the world as the standard JavaScript package manager for Node.js JavaScript primarily for the web. NPM, Inc. aims to change that and be more than a web tool. I aims to be the JavaScript ecosystem package manager for all development platforms from front end development to IoT and more. Raquel Velez (@rockbot), Software Engineer at NPM, Inc., speaks to this, the impact of NodeBots on the development community, education of IoT, and robotics & web technologies in IoT.Chris Matthieu (@chrismatthieu), Co-founder & CTO of Octoblu (@Octoblu), discusses Octoblu's platform and specifically #MeshBlu (AKA SkyNet.im), the scalable & universal cloud-based MQTT & CoAP-powered network for smart devices, sensors, cloud resources, drones, Arduinos, Raspberry Pis, and more.   Mike Schwartz(@nynymike), CEO of Gluu, shares his feelings on IoT security, open security standards, development practices and the pitfalls of a connected platform for IoT devices.     Kenal Shah (@KenalShah), Product Manager at 3Pillar Global, talks to the product side of IoT and how the business side of developing for connected devices impacts the development practices.   Standards are constantly debated and the rise of the machines is upon us. We need to decide as a community what these standards are so our clients can trust us to develop their IoT integration products. It is “The Wild Wild West” of IoT yet production and shipping capablities are here with tools like Node.js, NPM, and Octoblu. Once we solidify the standards, will you be ready to deliver?   https://twitter.com/chrismatthieu/status/458381648816377857   Upcoming Related Events http://hangouts.readthesource.io/hangouts/octoblu-meshblu/   Resources http://www.smartthings.com/ http://openinterconnect.org/ http://2014.robotsconf.com/ https://www.docker.com/ http://iot.sys-con.com/node/3178979 http://webrtc.sys-con.com/node/3123286 https://allseenalliance.org/sites/default/files/AllSeen-Alliance-DataSheet-09092014-8x11.pdf https://allseenalliance.org/developer-resources/alljoyn-open-source-project https://localmotors.com/awest/connected-car-project-internet-of-things/ http://javascriptjabber.com/103-jsj-robots-with-raquel-velez/ https://www.spark.io/ https://tessel.io/ http://www.arduino.cc/ http://www.raspberrypi.org/ http://www.intel.com/content/www/us/en/intelligent-systems/alliance-overview.html http://nodebots.io/ http://www.3pillarglobal.com/   All Seen Alliance https://allseenalliance.org/   NPM http://rckbt.me/ https://twitter.com/rockbot https://www.npmjs.org/   Octoblu http://chrismatthieu.com https://twitter.com/chrismatthieu https://github.com/chrismatthieu http://www.octoblu.com/ https://twitter.com/octoblu https://github.com/octoblu https://developer.octoblu.com/ https://plus.google.com/u/0/+ChrisMatthieu https://github.com/octoblu/meshblu https://itunes.apple.com/us/app/mobiblu/id915566405?mt=8   Gluu http://www.gluu.org/blog/ http://www.gluu.org/blog/nstic-announce/ http://www.gluu.org/gluu-server/overview/  

This episode Greg and Ayori talk with Dr. Andrew Williams (Marquette University) and Dawn C. Hayes (Founder of Coollabs http://www.coollabs.org) about Robots, Spelbots, Raspberry Pi's, Arduinos and much more hardware goodness. Follow Dr. Williams: @outofthebox1Follow Dawn C. Hayes: @cool_labs

This episode Greg and Ayori talk with Dr. Andrew Williams (Marquette University) and Dawn C. Hayes (Founder of Coollabs http://www.coollabs.org) about Robots, Spelbots, Raspberry Pi's, Arduinos and much more hardware goodness. Follow Dr. Williams: @outofthebox1 Follow Dawn C. Hayes: @cool_labs

Panel Jaim Zuber (twitter Sharp Five Software) Pete Hodgson (twitter github blog) Ben Scheirman (twitter github blog NSSreencast) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 00:59 - Language Backgrounds 05:23 - Other Languages vs Objective-C Static Typing Go LINQ Semicolons First-Class Functions 18:46 - Benefits of Using Objective-C RubyMotion 25:44 - Building Apps Not Using Objective-C 29:36 - Xamarin 33:03 - Calatrava 33:39 - Appcelerator Titanium 38:01 - PhoneGap Picks Get an HD Antenna (Ben) FizzBuzzEnterpriseEdition (Jaim) Forecast (Pete) Stranger in a Strange Land by Robert A. Heinlein (Pete) MadTree Identity Crisis: A Black IPA from Cincinnati (Pete) The Walking Dead (Chuck) Duct Tape Marketing Revised & Updated: The World's Most Practical Small Business Marketing Guide by John Jantsch (Chuck) Next Week MVC Transcript CHUCK:  Hey everybody and welcome to episode 36 of the iPhreaks Show. This week on our panel, we have Jaim Zuber. JAIM:  Hello from Minneapolis. CHUCK:  Pete Hodgson. PETE:  Hello from San Francisco. CHUCK:  Ben Scheirman’s going to be joining us in a few. This is a weird Christmas episode that we’re recording a little bit early. I’m Charles Max Wood from DevChat.tv and I just want to announce really quickly that if you go to RailsRampUp.com and you sign up before the end of the year, the 31st basically, actually I’m going to give you a few extra days. If you sign up by the 4th, then you can get 30 percent off if you want to learn Ruby on Rails, which is a handy thing for backend stuff. Anyway, this week we’re going to talk about some of the differences between some of our language backgrounds that we have. Some of us come from more enterprise languages like .NET or Java and some of us come from the hippie languages like Ruby, so should be an interesting discussion. JAIM:  I think so. CHUCK:  So real quickly, besides Objective-C, what are your languages that come out of your tool bag when you need to do something different? JAIM:  Well for a long time, I did C# and .NET. Even before that, it was C and C++, embedded stuff, thick client stuff. So I can write C in any language, pretty much. [Chuckles] But things that I like with Objective-C is I’m getting more familiar with how a dynamic language really helps us out, especially with testing and being able to be more fluid with our development. So I like that. But I definitely do come from a static language background. I don’t know. What about you guys? PETE:  So I guess I’ve been all over the place. I started off my career in C++. So when I first started doing iOS development, that actually felt quite familiar in some ways, doing manual memory management and all that fun stuff. And then I bounced around a bunch. I did some C#. I did a fair amount of Ruby. I still do quite a lot of Ruby. I do a lot of JavaScript. I do my current project, I’m writing Scala. I’m doing embedded C++ development in my spare time at the moment with Arduinos. So I guess I’ve been all over the place. But my main, my language I reach for the most is probably Ruby, still. And yeah, it’s interesting. I guess I’ve come to my journey into Objective-C is the opposite where I’m coming more from a dynamic place and seeing how it’s actually quite nice to have a type system sometimes, or have a static type system sometimes, and annoying as well. CHUCK:  Very nice. BEN:  It was a good fight we have right now. [Laughter] PETE:  You know what? If you ever want to play with a strong type system, do some Scala development and you’ll either fall in love with type safety or you’ll absolutely hate it. It’s been driving me a little bit crazy but it’s also pretty cool. But anyway, that’s I guess a different podcast. CHUCK:  Yeah. My background, I did Java and C++ in college but didn’t really take it seriously.

Panel Jaim Zuber (twitter Sharp Five Software) Pete Hodgson (twitter github blog) Ben Scheirman (twitter github blog NSSreencast) Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up) Discussion 00:59 - Language Backgrounds 05:23 - Other Languages vs Objective-C Static Typing Go LINQ Semicolons First-Class Functions 18:46 - Benefits of Using Objective-C RubyMotion 25:44 - Building Apps Not Using Objective-C 29:36 - Xamarin 33:03 - Calatrava 33:39 - Appcelerator Titanium 38:01 - PhoneGap Picks Get an HD Antenna (Ben) FizzBuzzEnterpriseEdition (Jaim) Forecast (Pete) Stranger in a Strange Land by Robert A. Heinlein (Pete) MadTree Identity Crisis: A Black IPA from Cincinnati (Pete) The Walking Dead (Chuck) Duct Tape Marketing Revised & Updated: The World's Most Practical Small Business Marketing Guide by John Jantsch (Chuck) Next Week MVC Transcript CHUCK:  Hey everybody and welcome to episode 36 of the iPhreaks Show. This week on our panel, we have Jaim Zuber. JAIM:  Hello from Minneapolis. CHUCK:  Pete Hodgson. PETE:  Hello from San Francisco. CHUCK:  Ben Scheirman's going to be joining us in a few. This is a weird Christmas episode that we're recording a little bit early. I'm Charles Max Wood from DevChat.tv and I just want to announce really quickly that if you go to RailsRampUp.com and you sign up before the end of the year, the 31st basically, actually I'm going to give you a few extra days. If you sign up by the 4th, then you can get 30 percent off if you want to learn Ruby on Rails, which is a handy thing for backend stuff. Anyway, this week we're going to talk about some of the differences between some of our language backgrounds that we have. Some of us come from more enterprise languages like .NET or Java and some of us come from the hippie languages like Ruby, so should be an interesting discussion. JAIM:  I think so. CHUCK:  So real quickly, besides Objective-C, what are your languages that come out of your tool bag when you need to do something different? JAIM:  Well for a long time, I did C# and .NET. Even before that, it was C and C++, embedded stuff, thick client stuff. So I can write C in any language, pretty much. [Chuckles] But things that I like with Objective-C is I'm getting more familiar with how a dynamic language really helps us out, especially with testing and being able to be more fluid with our development. So I like that. But I definitely do come from a static language background. I don't know. What about you guys? PETE:  So I guess I've been all over the place. I started off my career in C++. So when I first started doing iOS development, that actually felt quite familiar in some ways, doing manual memory management and all that fun stuff. And then I bounced around a bunch. I did some C#. I did a fair amount of Ruby. I still do quite a lot of Ruby. I do a lot of JavaScript. I do my current project, I'm writing Scala. I'm doing embedded C++ development in my spare time at the moment with Arduinos. So I guess I've been all over the place. But my main, my language I reach for the most is probably Ruby, still. And yeah, it's interesting. I guess I've come to my journey into Objective-C is the opposite where I'm coming more from a dynamic place and seeing how it's actually quite nice to have a type system sometimes, or have a static type system sometimes, and annoying as well. CHUCK:  Very nice. BEN:  It was a good fight we have right now. [Laughter] PETE:  You know what? If you ever want to play with a strong type system, do some Scala development and you'll either fall in love with type safety or you'll absolutely hate it. It's been driving me a little bit crazy but it's also pretty cool. But anyway, that's I guess a different podcast. CHUCK:  Yeah. My background, I did Java and C++ in college but didn't really take it seriously.

Es erwartet euch wie immer der neueste heiße Sch* rund um Robotik: Von diversen Robotern, Arduinos, Mikrokoptern, Events über Kleidung, einigen Tool-Tipps bis zum echt-unheimlich-nützlichen-Megafon™.

Stacey returns to the podcast to chat about making stuff with Raspberry Pi and Arduinos, and gives us the story behind the hugely popular open letter at futurewomanintech.com Follow us on twitter : @seb_ly @iainlobb @bitchwhocodes