An open-source educational robotics project that inspires elementary and middle school kids to invent through building their own robot
To make the experience fit your profile, pick a username and tell us what interests you.
Solidswork files for 3-D printable Barnabas-Bot. Version 2.2.
x-zip-compressed - 13.12 MB - 01/29/2017 at 01:56
EAGLE file for Barnabas Noggin daughter board for Arduino Nano -- REV C Created by Vincent Kok.
x-zip-compressed - 1.43 MB - 01/29/2017 at 01:54
Sample engineering notebook for Barnabas-Bot Class
document - 4.19 MB - 01/29/2017 at 01:52
I got the board working;
For the most part at least. The board gets power, can communicate via usb, accept code, and power components such as motors. However there is still a problem. That being the board's inability to receive power from USB. I think that the reason for that is a fundamental misunderstanding of p-mosfets.
I am well aware that p-fets act as inverters, only turning the channel on if the gate is low. However when routing the board I forgot that current only flows from source to drain in a p-fet. Thus the power management subsystem that allows the board to receive power via USB is essentially backwards.
So I need to Mcgyver the board in a way that allows me to verify this. You will probably be hearing from me again soon.
Till next time,
Quick update on the Barnabas noggin. I finished soldering it together today and, surprise surprise, it doesn't work. Not "I can't put code on it", more like "It doesn't receive power whatsoever". But, after a few hours of debugging I found the culprit;
This barrel jack was wired in the way above because I assumed pin 3 was internally connected to pin 2, AND NOTHING ELSE. In other words, I assumed the following schematic was an accurate representation of the barrel jack;
As it turns out, pin 3 is also internally connected to pin 1 in some way. So the layout is shorting the power source completely. After chopping off pin 3 on another jack and placing it onto the board, I confirmed that to be the case.
In addition to that problem there was some poor soldering that I am in the process of touching up. I'll keep you guys in the loop.
Till next time,
Long time no see guys. I just thought I'd give you an update.
Since I last checked in there have been a few changes. First being the serial chip that we were using in the prototype, an FTDI chip, was replaced by a ch340ser chip, mostly due to reduced cost. However this lead to a pretty stupid mistake on my part which ended up halting progress for a couple weeks. I had decided to use the 340t version of the chip, but for whatever reason I used the 340g pinout when editing the schematic. Essentially, my schematic includes a part which doesn't exist.
We have since fixed this in the schematic/PCB and have new boards on the way, but That is not the only change I have made. In addition I have removed the diode that was previously between the external reset pin and the reset pin on the atmega328p. For some reason that diode was making the process of burning the bootloader onto the atmega chip very difficult. My guess is that the voltage drop from the diode was causing the reset to not trigger on the chip, but I could be wrong.
You can see where the diode was removed in the schematic above.
I don't want to speak too soon but I've got a good feeling about the new version of the board. Hopefully next time you hear from me I'll be bringing good news.
Till next time,
As you know the Design Lab residency has officially ended, and as of last week I was scrambling to get the noggin I have been working on for the past four months fully functional.
Luckily on Friday, literally the last day of the residency, Ed and I were able to get the Barnabas noggin to function as intended. The two issues from last week, not getting power from the barrel jack and the board not being recognized by Arduino (or my laptop in general), have been fixed.
Like I suspected, the board was not getting power from the barrel jack due to a burnt out diode. As soon as that was replaced the board received power as expected. The other issue it turns out was due to a very silly mistake on my part. I had linked the Tx of each chip to each other and the Rx of each chip to each other when they should be swapped. Luckily some McGyvering let us remedy the situation;
So what comes next? Well I don't intend to stop giving updates any time soon, as there's a lot that still needs to be done before this board is truly ready for production.
So until next time,
A lot has happened since I left you guys last. Some bad, mostly good. First and for most the board has been completely soldered;
....and it looks beautiful. As far as the functionality of the board goes, it's not all sunshine and rainbows. I can't power the board from the barrel jack and my computer will not recognize the board, so I do have some things to troubleshoot. However, I have successfully burned a bootloader to the board and managed to download code to it in a round about way. I also can power it externally or via the USB jack. So without further to do, here is the culmination of my success;
I know it doesn't seem like much BUT IT WAS HARD FOR ME SO BACK OFF!
In addition to this I have continued to make revisions to the next version of this board, including ascetic changes (I did not care about how the last version looked at all). That mostly just means actually numbering pins, putting our name/website/slogan on the board, check it out;
If you look in the upper right hand corner, you can see we even fit our logo on it;
So I'm gonna keep working on it, hopefully by next week I'll have most of the problems ironed out.
Till next time
My first PCBs have arrived!
So I should be excited, right? Well, hold on. Here is the back side of the board;
........... Not my finest moment, that's for sure. So I'm left with with the task of McGyvering a way to solder a cap, and then a voltage reg. on top of it. Afterwards HOPEFULLY it just works.
In addition to that I am working on the next iteration of the board. I'm considering all of the problems the current board has, coming from the obvious ones (see above), the mechanical ones that will make it difficult to combine this board with the body Ryan is developing (current one fits but could stand to be .5mm to 1mm wider), and the manufacturing minded ones that will inflate the price of the board (such as having components on both sides of the board as opposed to one).
Till next time
Last time I talked to you I was struggling to burn a bootloader onto a blank atmega328p-au chip. My guess was that the connections on the FR1 board that I had milled out were bad, particularly the ones on the crystal. I tested this hypothesis this week by creating the same circuit on a breadboard, using a through hole version of the crystal I was previously using and a FR4 version of a tqfp32 breakout ( I keep destroying the traces on the FR1 boards when I solder). The whole situation ended up looking something like this;
So, in the end, I finally did get the bootloader onto the blank chip. This would seem to support the idea that the previous problems were related to poor soldering on my part rather than poor engineering on my part, what a relief.
With that, I felt confident enough in my design to finally order boards from OSHPark, which should arrive next week!
Till Next Time,
Since I last talked to you I have still been trying to troubleshoot the ATmega328p, in particular burning a bootloader onto it. I successfully burned a bootloader onto another uno using an uno, which I just did as a sanity check to make sure I actually knew how to do that.
I also made a "breakout board" that essentially just had the bare minimum needed to burn the bootlosder onto the chip;
Unfortunately this did not work either. I suspect that the crystal is not properly soldered on to the board (it is an incredibly small component). Next week I need to thoroughly probe the traces to be absolutely sure that the issue is not there.
I have also ordered additional resonators to see if that may be the issue. One is essentially the same crystal I am using but is a through hole component, which will allow me to take the variable of soldering out of the equation. If I can successfully burn a bootloader using that crystal it will tell me that my current issues lie with the soldering. Whether I am damaging the component when I solder or am simply creating shorts, I am unsure. Hopefully the additional probing will give me additional insight.
Till next time,
Hello people of the internet and ....
Today we will talk about the state of the body. Unfortunately, due to personal issues like school. i was unable to reach that tooling stage of the body that i wanted but fear not. I have fixed the issue of that pin issues fitting with the rest of the body. The crazy solution that i came up with is the same as the bottom part. I created in indent so that the pins on the top part of the PCB will no longer be hitting it. Allowing free movement to the desired places.
Additionally, it is time to let our body go on a fat reduction. Meaning, we need to make the printing process of our robot much faster since it takes so long to print already.
We may never find out if this will work by keeping its integrity but hey, until next time.
Hello friends of the inter webs and...
This week i want to show you the amazing powers that i have from becoming a kung fusion 360 MASTER.
Yes, what you see here is the integrated Rev C of the board on to the new body. The reason why this is so important is because all the boards that any of the customers who bought it before we go into injections molding is going to be able to use the new bodies if they chose to do so. The entire thing is flush and will be moving on to the form labs. Additionally, this is the last part that will prevent me from making a tool for the injection molding! I'm excited to work on that next since there are little bits of tweaking that i need to finish.
Until next time
1: Designing Your Robot
In this step you will design your robot and learn a little about computer aided design (CAD) while you're at it. After you finish the design, you will send the robot desing file to our factory via email so that we can start putting together your one-of-a-kind robot. If you already have your robot, you can skip to STEP 3.
See below to watch one of our instructors demonsrate the entire process.
We will be using OnShape. It is free cloud-based CAD software. This will allow you to view and modify our files for 3D printing.
Here are a few tips on how to move stuff around in OnShape.
This is where you will put all your robot's body parts together and create the final file that you will share with us.
This step is necessary if you would like us to 3-D print your robot for you.
Once you share it with us, we will provide a confirmation within 24 hrs. Now just sit back and relax as we start putting your robot kit together!
We have provided the contents of our kit below so that inventors all over the world can make their own DIY version of this simple robot kit.
Once you get your kit, go ahead and first decorate your robot! We typically use acrylic paints, but we have also used metallic paints as well as Sharpies. See below for some cool examples!
Become a member to follow this project and never miss any updates