@jc0day 2 of #bci! today my goals were to get the hang of using kicad, understand the schematic of openbci's cyton board (which is, along with hackEEG and piEEG, the basis for a lot of our understanding of what exactly happens in EEG boards) and spin up a bill of materials for everything going in our pcb. i got to the first two and didn't do the last one (although i will eventually get to it!), but i had a lot of fun! today was another great day because this is the most fun i've had in a while building shtuff (among other things: deciding who would be who in the openai drama, the f*ckboard, dinner at steve). tomorrow's goal is to spend the whole day just building the actual pcb (and then spend thanksgiving off?) we're building this out in the open so my daily notes are all here: cloud-ckujstd4d-hack-club-bot.vercel.app/0jc_0e4ee6c5e5e546ce910bda3e3ad2ac10.pdf
(this is part of #100-days! join us over there, we're working on cool stuff like #apocalypse and #dallas-day-of-service!)
@jc0day 1 of #bci! i mostly got caught up on a bunch of things today (including, but not limited to: parts of the brain, eeg concepts like the 10-20 system, reading schematics, understanding what exactly we’re doing including the process of actually designing the eeg circuit: electrodes -> ads1299 (including digital to analog converter) -> microcontroller -> computer for extra processing - so many black boxes we’re trying to figure out!) and generally feel like i’m ready to start playing around with kicad/observing tomorrow! today was a great day overall, although we think we could have focused a bit more and it still feels like i don’t know anything. tomorrow’s goal is to build shit which is the easiest way to understand stuff. we're building this out in the open so my daily notes are all here: cloud-6crgvlqrj-hack-club-bot.vercel.app/0jc_e4acbe3e3aff48778866059bb21c78be.pdf
(this is part of #100-days! join us over there, we're working on cool stuff like #nanowrimo and #polyglot-warriors!)
@karmanyaahm0Don't have pictures of the whole thing but I got recruited onto chessbot ig, an electromagnet CNC drags the chess pieces around
@dominic0I made @upsanddowns to act as Jia for #up-vs-down - assigns new members a team, makes sure people count correctly, and resets the game at 100 or -100. this was my first time making a slack bot - slack bots are fun!
on github at mrhappyma/slack-ups-and-downs, or go count in #up-vs-down to see it in action!
@karmanyaahm0Using ROS2's multi device communication to send Intel realsense camera data from a Jetson nano to my laptop@leom0Today I got a drink from this café. Not too many employees around to see…
@msw0Here’s a robot that @ella built drawing art I had chatgpt make for me!@Marios2Worked on the Sinerider Reddit Bot! :)
@karmanyaahm0Restoring Mr Robot with Vex Cortex and ROBOTC milestone (with @Jaxzog)! The master brain is now talking to the follower and successfully sending values over UART!@sporeball0lucy-bot learned about attackers and defenders, which might help her calm down just a bit
@sporeball0lucy-bot learned about captures and checks. now she'll use them to perform a dead-simple evaluation
@karmanyaahm0Installing headers to adapt the ports to a vex cortex brain for Mr. Robot (a Lego technic based humanoid)
@Marios2Another day another Portuguese learning day!
~~ What I did today ~~
Today was pretty chill till the night where I had a lot of issues with the sinerider bot. Thanks @JosiasAurel for helping me.
On the duolingo side I did some very needed revision. And I can proudly say:
@Lucas tem um cachorro!
@rajanagarwal0experimenting with fine-tuning a generative text model for a cool slack bot!
@Scott1700Still not done with my WHW robot (technically). I have finished building my robot but it is not exactly the best design, so I have been thinking about upgrading from micro servos to servos. (It will result in the robot being bigger but also able to handle more of a load)
@RaymondWu-U04JJ3A7G3Z0I'm trying to make a computer vision program that detects tennis balls. There will be a ball picking robot eventually.
@Marios2Day whatever of my life on #scrapbook!
Today I completed the sinerider bot, programmed in the Commodore 65 and played MC with @Odysseus. And also launched an Order Lookup system for Kelp LTD. I also continued my adventure on how current works!
What I didn't like about today:
+ I did ~4 hours of math for an exam. Not fun
@ManikShrivastav-U04GY2NRT5X0Day last of WHW🇳🇵
Finally my project The Gesture Control Robot 🤖 is completed and you can have a look on it. It was a great time working with this project. Hope to participate in future events as well.
By @ManikShrivastav-U04GY2NRT5X .@Marios2Today is the 1st day of what I call, the DM ( Daily Marios ) Didn't do much because I was out of town
~~ The 📜 Changelog of wisdom
1️⃣ I worked on the Sinerider reddit bot
2️⃣ Experimented with the Commodore 64, fascinating stuff!
~~ :future_potato: What is tomorrow? ~~
I want to update my winter hardware wonderland repo and create the pcb. Also experiment more with the C64.
~~ It is :minecraft: time ~~~
Or is it? I didn't have much time today so I didn't play much :(.
@BikashGupta-U04HFDWE7CH0Final video of my Human face following robot 🤖. It is working well tracking my face 😊.@Captain-A.J.0Winter Hardware Wonderland Day 8 #hardware-party
Today, I connected the Pixycam to the RoMeo BLE and ran the test code to make sure everything was working properly... and it was! When the camera sees a “learned” object, the Arduino IDE's serial monitor shows the values seen in the picture. I have also run the line tracking demo code without the camera attached to a chassis, which was also a success! So, next on the agenda: finish the line tracking code to fit my robot's purpose.
TWO DAYS TO GO EVERYONE! Let's keep pushing!
@ShouryaPandey0Started to make a platform for testing the bot and repairing it
@TheScientist1010Day 5 of #hardware-party :
Today I finally got the connectivity and data transfer between the robot and the phone for controls done. I am using Flutter for the app because of its ease of use and cross compatibility. Here’s an image of the joystick below. I need to learn how to parse the data on the robot. I will hopefully work on that today.
I finally got the robot mechanisms worked out. Here is a very rough sketch of the first piece of paper that I stumbled upon. This design should allow the robot to go, forward, backward, left, and right, and even stop with just a single lever, a bunch of gears, and a motor that is continually turning in one direction. Here is how it works:
On the left side, we can see the side view. There are two gears that mesh together on a pivoting bar. Attached to the bottom gear are the wheels. If the lever is pushed all the way to one side, the top gear will touch the drive gear and act as the idler gear, so the bottom gear will travel in the same direction as the drive gear. If the lever is pushed to the other side, then the bottom gear will directly touch the drive gear, and it will travel in the opposite direction. If the lever is put in the middle, then neither the top nor bottom gear will touch the drive gear, and the robot will not move. This is how our robot goes forward, backward, and stops.
On the right side, we can see the front view of the wheel system. Most of our axles are tight square axles that spin with the gears and lock tightly in place, but the axle in our wheels is a loose circle that doesn't turn with the wheel. We can see in this side view that our bottom gear is actually very thick/long, and has 4 rods poking out of either side. This gear will easily be able to slide left and right when the lever is slid left and right. When the lever is slid to the left, the rods interlock with the holes between the spokes of the left wheel, but not the right wheel. When this gear turns, the left wheel will turn, but the right wheel will not. The same applies to the right side. Also when the lever is in the middle, it interlocks with both wheels, allowing the robot to go straight. This is how our robot can turn left and right.
Also, @AaronD'Souza-U04J5CM3T46 and @BrendenD'Souza-U04JC0N6ZC2 uploaded all of our finalized files from Day 1 and Day 2 to the SD card for our printer so they are all readily available to be printed.
We are going on vacation to Florida for 4 days because of a wedding, so we won't get much done then. Hopefully, we can get some CAD files done for the robot when we are sitting in the hotel, but we will be pretty busy and we can't do any printing.
@caleb0i made a… skribbl.io bot that just straight-up draws the word@Scott1700Big Milestone! Day 2 of my WHW project
Really productive day today! I was able to get my torso design done and printed (7 whole hours!) and printing the rest of the legs. Hit a big milestone and got the main structure of the robot done 😄
a few hicups along the way (a few micro servos broke) but I got it done!
@ky2006170Ahhhh! Robotics had me crazy today so I couldn’t sit down and CAD a case.
Regardless, I made this cool pivoting gearbox that has a 400:1 gear ratio.
And it was a clear sky day too!
@Daniel0Winter Wonderland - Back Again for Day 2/10! (#hardware-party)
Today has been a pretty busy day for me, so I didn't get quite as much done as I wanted to. Nevertheless, progress has been made and you're here to see it.
First things first, I went through three different motor mount bracket revisions trying to get the angles just right (a tilted motor would lead to belt wear nightmares down the road).
After getting the motor mount sides printed, I decided to knock out a couple easy tasks, so I mounted the battery to the bike, which was easy to do with the water bottle holes already found standard on the bike frame. I also printed the mount for the speed controller (out of PETG for heat resistance) and gave it a test fit on the bike. While the part looks super pretty and clamped on to the frame well, it didn't have the friction to resist my pushing it down the tube. To solve this problem, I'm thinking of lining the inside of the clamp with electrical tape for its thin but rubbery surface.
One more super exciting thing - I got some of my aluminum plates machined at robotics! All I need now is the motor mount plate, which is a little bit more complex with its partial depth cut wings.
Just like the last post, feel free to message me with any questions or input!
CAD for reference
@Captain-A.J.0Assembling the bot! Plan to upload some code for basic function soon.
@Captain-A.J.0Winter Hardware Wonderland Day 1 :winter-hardware-wonderland: #hardware-party
A.L.F.R.E.D ButlerBot (PR here: github.com/hackclub/winter/blob/main/Captain-AJ.md)
Welcome all to the start of a great adventure! I hope everyone is making great progress on their projects. Personally, I have started building my
Autonomous food delivery bot: A.L.F.R.E.D. Which stands for Advanced, Little, Fit, Robot, Education, Device. Today I've just about finished the wheels of my robot, I had some trouble with the suspension due to screw tightness, but all is fixed now! Tomorrow I plan to make a basic
remote-controlled robot for testing. I am currently learning about Arduino hardware and software and will start learning C and C++. That's all for now!
@GauravBansal-U03M3D6RA1K0WHW 1/10 #hardware-party
I researched some inverse kinematic and FABRIK algorithms for my robotic arm! I decided to use a 3R 3D manipulator with one motor turning on a separate axis. Overall, I’m pretty excited to code in IK for the robot arm (and be able to control the arm through input!)
As a reminder, @AaronD'Souza-U04J5CM3T46 and @BrendenD'Souza-U04JC0N6ZC2, and I are building a mechanically-codable robot. We are going to have to make a revision to our design. Originally we were going to make it read the input from a wheel with gears, but now we are going to make either 1 or 2 levers that control whether the robot is going forward or backward, and also left or right. Once again there is no coding or microprocessors, all the information for how the robot moves and turns are not controlled by the motor, but by the gears and the physical layout of the plastic pieces. We have a general idea of how this going to work, but we need to do a lot more designing.
We had previously done some testing with tolerances in a gear meshing a couple days ago. Not all of our prints are shown (we had a bunch of fails where the tolerance didn't line up, or the printing didn't succeed, or we replaced in favor of a better design), but pictured in white are our latest version of the Gen 1 gears, motor-axle adapter, and axle. These are printed in the PLA given to us in the box in which we received our 3d printer, and are made with just 20 percent lightning infill on the gears.
Our Gen 2 gears, motor-axle adapter, and axle are the ones that are approaching the level of what we are planning to actually use in our robot. As you can see the sizing completely changed. We are using much smaller teeth. In Gen 1 those 2 gears could only manage a 2:1 gear ratio, but now we have a 6:1 gear ratio with slightly smaller gears. Also, these are printed with PLA+ filament and 50% grid infill so they are much stronger and very high quality. Also, our motor-axle adapter is now tighter on the motor and has a smaller and sleeker design. Once again many of our failed or outdated prints are not shown.
In addition, you can see we set up 100% of our electronics. Just a single motor attached to a battery pack.
@AndrewZhao-U04KN759HPA0Day 1/10 of #hardware-party! 16:1 gear reduction now printing! Should theoretically output ~20Nm of holding torque for a robot arm. Gearbox assembly tomorrow!