I just recently added search to Circuit Dojo but it was not as straight forward as I had hoped. There was plenty of people who had done it but there were some important details that were left out. So, like anyone else in this situation, I hacked on it a bit to understand how things work under the hood. Here’s the process from beginning to end on how to get it done using a Gulpfile, and some Hugo templates generated on compile time.
In my previous article, I went into detail about the short range possibilities for connecting a device to the outside world. But sometimes you need to go the distance; and when I’m talking about distance, i’m talking about 1-12 miles line of sight! In this article, I go into the details about the different types of long-distance embedded communication. These are the types of protocols that get your sensor data to the cloud so they can be consumed by your service and transformed into something useful for the end customer.
It’s been a while since i’ve played with Bluetooth and I’ve been researching every connectivity technology that exists to create a IoT. After some laborious searching reading and chatting industry experts, I realized that there were too many to count! In this short series i’m going to deconstruct the biggest players in the arena and tell you the benefits and where they should be used in an end application.
Over my past few posts there has been a common theme of “using things that already exist.” This stems from a mindset of building things from scratch whether or not they’re actually warranted or needed. For instance, you may work with a fussy firmware engineer who finds the provided vendor code just deplorable to use. That person then takes extra time to go about writing their own platform or system that replaces the vendor code.
It’s stressful to be on the front lines of a pre-production effort. It’s even more stressful when you are the only person that is responsible for the majority of the design, component selection and procurement. In this post, I’m going to dive in some of the ways you can leverage distribution partners and your factory to manage your bill of materials for you. That way you can stay ahead of the game and focus on what really matters.
In order to get interactive with your now serial enabled Raspberry Pi we need a framework that will provide the ability to communicate in real time over the web. For example, if you press a button in a web browser on your Mac it enables a GPIO on your Raspberry Pi/Arduino which subsequently enables a relay connected to a light in your house. Before we get started: since creating this post back in 2014, much has changed in the landscape of Node.
Prototyping can open your eyes to the possibilities or the constraints that you now have to create a product. For instance if you 3D print a prototype and find that it’s darn near impossible to hold for people with smaller hands (or large hands for that matter), you should modify the design so it works for your intended demographic. Especially if your demographic is filled with people who have large hands!
There are many techniques to prototype the products you want to create in the future. I have had the chance to work with some of the most talented people in the San Francisco Bay Area. Through their inspiration, I wanted to share some of the tricks of the trade making something from nothing. Here are their and my favorite ways to prototype: Note: this post is lengthy. If you are particularly interested in a certain technique see the list of links below:
The delivery of static files from a web server to your browser can be blazing fast. That is one of the advantages of using Jekyll vs. other dynamic web content systems like Wordpress. One of the drawbacks, unfortunately, is that Jekyll requires much more knowledge about the intricacies of how all the pieces work together. (i.e. fix things when they break in Ruby, install or bake your own plugins, etc.
Remember when static websites were the only things that were served on the internet? I don’t know about you but I definitely remember the pain of uploading all my sources files via FTP to a web server only to realize there was a mistake in one of the HTML files. Shnit! Nowadays, while web has become significantly more complex, there are companies, mom and pop shops and individuals looking to make it simpler.