Greetings!

If any of the info on this website was useful for your projects or made your head spin with creative ideas, and you would like to share a token of your appreciation- a donation would be massively appreciated!

Your donation will go to my Robotics Fund, straight towards more sensors, actuators, books, and journeys. It takes a lot to continue building these robots, and I’m really thankful of everyone who helps encourage me along the way.


USD


CAD

“A wise robot once said to me through Serial.println- that robots teach us about ourselves.”

All posts tagged Processing

Flexure Mech Prototype, Points in Antimony

Just finished a week of Fab Academy where I learned a lot of info and tried new things! There were some interesting fails and challenges along the way. The first half was creating a flexure mechanism, and the second half was learning a little about function representations and importing points into Antimony.

Here are the highlights, if you want to read all of the details please see my Fab Academy page!

To continue working on the robot project, I created the first test of a flexure mechanism. It is based on Flex-16.

3D printed in PLA. Uses a micro servo and a paper clip linkage:

flexure_mech_prototype_2

Here you can see the flexibility of it (though this was in ABS):

flexure_design_prints_2

There is too much movement in the z axis to make it useful in the robot idea (see vine video above). Have an idea on how to make the next one. Flexure mechanisms are pretty cool, I’m excited to try to build a robot with them.

For the scanning aspect, I wanted to be able to display slices of a 3d model in Antimony and maybe blend two models together.

Here was a first attempt that failed:

tri top view

Went to the idea of just displaying shapes where the points are. It sort of resembles the Stanford Bunny:

bunny view

Created a node for Antimony that reads in the points. 3 of them in action to display the pieces of the Fab Lab logo:

fab logo reading node

More info about these is on my Fab Academy page.

Lots of electronics coming up next. In the lecture, I can’t believe people used to use tape to make circuit boards by hand! The fab modules has an EDA tool where you can make the board by typing commands. It will be interesting to try it out compared to my previous gEDA experiments.

Clyde : Winter

Happy winter everyone and everybot! It’s a great season to enjoy many activities. For a robot, this is not just limited to being a robot snowplow. In this hack, we will be making Clyde into a winter themed connected cheerlights device! Watch the vid!

Check out all of the information over on Fabule’s blog. It goes through every step, from 3d printing the snowflakes, to the Processing sketch, and more. So go check it out!

clyde_winter_13

Hope you enjoyed this last Clyde hack! It turned out to be quite a long hack, but the end result makes a great appearance with all of the blinking snowflakes and internet controlled eye.

It has been a blast creating these and evolving the creativity for each one. Thank you to Fabule for sponsoring this video series!

Happy hacking and happy winter :)

Promulgate

promulgate_icon

Promulgate is an Arduino library with a very simple protocol to allow communication from Arduino to other devices.

Check out the video to see it in action!

The library was designed so that you can add Promulgate quickly to a project. It is very simple to parse and transmit messages.

To get started, go to RoboBrrd.com/promulgate. There is an example and boilerplate code for Arduino and Processing.

The code is available in this repository.

If something breaks in the library or could be improved, feel free to let us know. We’re constantly learning, so if it’s wrong, we might not have even realised this.

You can also see our post about our two Promulgate + iOS demos.

We were looking back at our log notes for the entire project last night. It took 23 days to create Promulgate, spanning across 40 days. Each day was 1 hour (give or take) of total focus. This includes the library, two iOS demos, Xbee demo, and documentation.

Just thought we would share this info about the development time. It’s actually a little personal to us, since we aren’t exactly lightning fast (we need to improve our pace). Though, it brings up an interesting point in evaluating success of a project. Do any other makers think about this beforehand?

For Promulgate we had a few factors in mind that would make it a success (to us). Most importantly, completing the project to our best quality, and our meticulous documentation so that it will be easy to make a quick demo even if we have not looked at the code in 3 months.

Making a good demo video of it in action was also important to us, because we are lucky enough to have the support of our Robo-Patron backers on Patreon. Our original video of this project was very monotone and not as fun, so we entirely scrapped it and started over.

Sharing it with others, hopefully seeing it be used in some projects, and learning about improvements from the community are also factors. These ones are tricky though, as it can really depend on the project if people enjoy it or not. It is nice when they do, though.

Evaluating the success of a project depends on a myriad of factors. The best part is that it is done now… so on to the more fun apps. “If hardware is the heart of a project, then software is its soul”.


This work was supported by our great Robo-Patrons. Consider backing us on Patreon to help us make more projects!

patreon_robotgrrl_800