An educator-turned-developer, Daniel got his start in the software industry testing embedded automotive infotainment systems for Johnson Controls in 2014. While he was there, Daniel created new components for and maintained the company’s Python automated testing framework. Daniel held other QA-related roles until becoming a Software Engineer at Blue Medora in 2016. While at Blue Medora, he served as a project lead, a platform extensions software engineer, and a recruitment and outreach advocate. In 2017, Daniel joined Spantree, where he worked on planning and optimization problems, data pipelines, and search solutions. As a Senior Software Engineer at Very, Dan works with clients to build IoT-enabled solutions.View the profile
About the talk
Internet of Things projects are challenging because they contain comical exaggerations of the pitfalls you find in distributed systems. In the case of developing a Solar Microgrid Controller, like I did, you’ll face bonus challenges like, “When will the internet be in town?”, “How do I create clean architecture when the hardware is shifting under my feet?”, and “How do I quickly pivot to a different peripheral?”
In this talk, I’ll share some of the ways our team leveraged Elixir, Nerves, and NervesHub to build robust Solar Microgrid Controller firmware. I’ll also share development patterns and practices that you can take back to your next firmware project.
Because micro grids can be deployed in remote locations without reliable Internet access, data minimization is a must. We’ll talk about the tools you can use to provide full utility data when low bandwidth internet might not be in town until next month.
Next, we’ll look at a couple of different ways Nerves and Elixir can keep our software tidy by decoupling the firmware from the hardware.
We’ll wrap up by looking at hardware. While commodity hardware like BeagleBone or Raspberry Pi are great for prototyping, they’re far too expensive for mass production. For this project, we built our own custom hardware and ported Nerves to it. We’ll take a look at some of the considerations you might make if you develop for novel hardware, and what you might do to bring your next project to life with Nerves.
That in there. So if you're joining me, this is a talk on how to short-circuit iot development time is going to be a lot of lessons that you probably already know. I'm so if you walk away a little bit disappointed that you already knew a bunch of the stuff then I've done my job. Who am I my name is Dan Lindeman. I am a senior software engineer at Berry if you feel so compelled to follow me either on Twitter or check out, you know things that I'm doing a good Hub others are my two handles by the end of this talk. You don't have any other thing further questions. You can always talk to
me about prog-rock my dog Bowie or renewable energy. So originally we had Set the stock up kind of as a battle ground or at you know, Frontline. What is it like to work on iot projects particularly in the renewable energy space but I realized that this project was just full of lessons. For development patterns. So that's kind of power. It's going to be set up. So I need to make a couple of stops on options about you. The first one is that you probably have an interest in iot. So Internet of Things applications,
maybe you've got a Dusty pie somewhere hanging around and you'd like to get it off the shelf and just kind of looking for some inspiration. The other thing that you might have brought you into the dark today is that you have some kind of interest in you know, Sun Beams or renewable energy. So if that's something that you identify with this talk is for you. We do go a little bit into the weeds and I'd and I did definitely want to make sure that we get into some deep technical content. But even if you are, you know, somebody who identifies as you know, I'm just a webdav all the way up to the
Buy this talk
Buy this video
With ConferenceCast.tv, you get access to our library of the world's best conference talks.