R2UK 2019

Back home now after R2UK 2019, and it was such an amazing weekend.

Three days of astromech fun, from talks about their use in the films, to weathering techniques. Driving accuracy course, to mini egg droid wacky races.

Was a bit anxious on the build up to the event, as I’d taken on the task of upgrading all the electronics in the driving course to make scoring automatic, along with registration via RFID. Thankfully however, once I’d done a little tweaking it all seemed to work fairly smoothly.

R2 not to scale! 😉 This is the DeAgostini scale model, done out in R2-KT colours by Paul Whitrow of TRamp

Lots of improvements to be made to it, and repairs after some droids didn’t seem to be avoiding the sensors that they *shouldn’t* be hitting! The actual metalwork took quite a bashing too as some droids thought it was more like a pinball machine.

This weekend is the must do event of the year for me. Its such great fun to hang around with a fantastic group of people. Everyone has something to contribute, and everyone will listen. Lots of advice was both given and received over the weekend, and I dare say motivation for building droids is at an all time high in the UK.

If you want to learn more about the driving course and the automated system I’ve done for it, its all in the git hub repository.

Power Tracking

One of the things I’m quite interested in keeping an eye on (and wish I’d started making notes a lot earlier) is how much battery power I consume at an event.

R2 is quite a heavy droid, with lots of gadgets, and is generally very active at events. I like to drive round and entertain rather than staying in one place. I also may have gone overkill on the battery, tho that being said by never fully depleting the cells I’ll probably get a lot more life out of the packs.

So, I have started a spreadsheet to keep track of how much actual power I use in a given event, to hopefully get some meaningful stats for my droid(s).

Besides standard stuff like the event name and date, I’ll be logging the amount of power put back into the droid after the event, as measured by the charger I’m using. I’ll also log approximate hours the droid was powered up, along with how much of that time he was actually active and moving around.

The spreadsheet will be public, as it may help other builders:


I just have to remember to keep it updated now! 😀

One droid is never enough

The time has come….

R2 needs a friend.

I’ve actually started collecting bits to make my next droid. I’ll be picking up the bulk of the droid in a couple of weeks at R2UK. I’ve already got the motors, speed controller, Pi, and a few other little bits. Most of the other electronics are on order too.

Not 100% certain on what type of dome the droid will have, nor the colour scheme that I’ll use. That can all come later.

What I do know:

  • Brushless Q85 motors (e-bike hub motors).
  • ODrive controller for the motors (a lot cheaper than the Roboteq most people use).
  • Will use r2_control (of course), but be able to swap out to standard RC quickly.
  • Same battery as R2, so I’ll have two identical ones.
  • All electronics will be on a removable board so that I can pull them out to work on outside of the droid.
  • Dome will be wireless with its own (small) battery.
  • Cheaper than R2 (much cheaper!)

I’ll probably also use steel feet to keep the center of gravity nice and low for stability.

So, it will mean a fair bit to do. I’ve never really worked with styrene before and with using both wireless comms for the dome and an ODrive there will be a fair amount of coding work to do on r2_control.

I’m going to try and keep a better build log for this one, with more work in progress pictures.