ORIGINAL CONTENT! The All-Around Robot Update: Roll Cake Rises Again; Dragon Con 2017 & Uberclocker

Whoa, what happened to this place? Everything’s so dusty and gross. Why is there a pile of circuit boards on the bench??

*trips over Chibikart on the ground and dies*

Hey, remember: whenever I disappear for an unexplained period of time, it’s always because I’m working on something hilarious. This time it’s extra hilarious, I promise! Obviously I’m always itching to keep everything updated here on my latest, but just like the first BattleBots build season, externalities which if broken would make other people look like assholes prevent me from saying anything at the moment. See, I don’t mind me alone looking like an asshole…

Anyways, backing up a little in life, I decided to redesign Roll Cake from the ground up following my hub drive experiments earlier. MomoCon came and went, but the Hobbyking orders kept stacking up, so I decided to roll it all in with Überclocker’s changes for Dragon Con!

roll cake

It all begins with a wheel.

Doing the drive test with the SimonK ESCs and the Multistar 460kv motors convinced me that the hub motor direct drive would work out, at least better than the previous BS I tried to do. I went shopping for high pole-count, low Kv drone motors since they’re pancakey. The plan was just to approximate wrapping an O-ring as close as I could to the motor. I ordered a few of these AX4006 motors for their combination of weight, low Kv, and high pole count.

Roll Cake is a bot which faces some packaging difficulties, since the middle of the bot has to be left pretty open for the flipper linkage. It would actually be easier in a 12 or 30lb design, since ‘noise floor’ of part sizes is much smaller compared to the bot size. If I scaled this design up to a 30lber right now, those would basically be 6″ hub motors, which is unnecessarily large.

There’s other architectures and shapes for the bot which might alleviate this, but for the time being I decided to try and keep the cheese wedge shape but  make it a little more…

…round. Remember that the flat sided shape was just an attempt at vomiting my vision of a bot that I’ve had for a while now, not making sure it works. When you ditch the need for 6WD, things get a little simpler! Even this is technically unoptimal packaging since there will be a lot of wasted space in the narrower parts of the cheese wedge. I’m basically just reskinning Roll Cake v1 and using all the same parts, since the goal is to get it driving and flipping things reliably, albeit not spectacularly, before deciding what aspect of the design to improve.

Once I had the parts placed reasonably, I started generating frame features to accommodate, such as wheel cutouts and future bearing blocks. The chassis will no longer split in the middle – that required so much extra effort to get everything to line up. Instead, I’ll be splitting the rounded caps next to the bearings off as its own print in the future.

The previous image showed the old linear slider trigger, but packaging necessitated switching to a swinging style. This means Roll Cake won’t fire when upside-down with the drum running in reverse – I’d still have to ‘self right’ so to speak. That’s fine, since I’m also ditching the double-sided linkage due to it taking up the entire center of the bot from swing space. At least keeping the flipper single-sided lets it still have structure in the middle!

The chassis is now taking shape pretty well, showing the swing trigger’s backing and “drilled” bearing cap holes and the like. I’m designing this to print ‘upside down’ on the flat top face.

After defining critical part anchor locations, I hollowed things out to accommodate the flipper linkage and irritatingly rectillinear things like batteries. Seriously, if there’s one thing this design is sorely lacking, it’s a battery worth having. I much prefer this to be 4S, but can only fit a 3S pack of adequate capacity for now.

As I model the body, I can give components final homes constrained by mounting holes and then adjust the cutouts and spacings to fit. So there was a fair amount of tuning going on at this point, including a change of wheel size to be smaller in order to shift the wheels more rearward (to give me battery space!)

After that, the fun part became linkage design. The goal is to get a linkage design which travels as far up as I can manage using the roughly 1″ throw of the cam ring, and generally has no linkage interacting at more than 45 degrees starting angle.

My insistence on a “pull” action on the main cam linkage means I have to transform the motion through a bell crank (the bottom and right side short line) to become an upward motion. Strictly speaking, I could potentially accept a push action from the cam linkage and that can directly interface with the flipper arm and move it upwards, but it would need to be designed much more heavy to stand the compressive force instead of tension (pulling) force.

 

This bell crank itself went through a few revisions in order to minimize the impact it has on the middle of the bot, the large bulkhead that runs across the two sides.

Here, I’m comparing designed linkage travel with actual part placement, seeing how much of the middle of the bot has to be cut out. The bell crank center distances and topology have also changed. The previous design intruded on the center of the bot with its full height, whereas this “T” design means only the short leg of the T pokes through the center bulkhead.

Then I decided to wrap the bulkhead around the bell crank instead of hollowing it out pre-emptively. It’s all going to be 3D printed in 50% density anyway, so no need to pre-emptively deny myself cross sectional area (which is very important to 3D printed parts)

After I was satisfied with the bell crank geometry, I made a crude flipper arm model to start out with.

The linkages will have to fold into themselves a fair amount, so I pre-emptively carved space for them before doing anything else.

The intermediate linkage is a bit of an awkward shape – here it is taking form. It has to adapt the narrow bell crank to the wide flipper linkage. I decided to do it here, and reinforce the middle of this linkage with a big flange, instead of trying to flare the end of the bell crank wider due to my desire to print it flat and have fully un-interrupted perimeters to maximize strength.

Here, see the aforementioned flange in the center of the intermediate linkage. I’ve now hollowed the flipper arm, which will be top-skinned with hardened spring steel.

The armor for this bot is quite simple – primarily Onyx in massive hollow-ish sections for the crumple zone effect, and blue-temper spring steel covering the important parts and providing access hatches.

I added a little feeder leg next to a region with unused material thickness. This will be a machined piece which is captured with nuts and flat-headed screws.

Finished and ready for printing!

I had to split the geometry first into the printable sections. I extracted the bearing cap by making a 5-sided surface box in Inventor and using a split body by surface function. Only one was needed – the other was disposed of. Other sections such as the mostly empty tail were cut off also in order to reach the print volume, and they were designed to be bolted back on.

A day later… Her’s the frame finished, printed in 3-perimeter 50% density Onyx. Ought to be plenty!  You can see where I cut the end of the wedge off and have modeled in a few tappable holes to hold them on.

Here’s a pretend-o-bot to make sure the dimensions all fit. The bearing cap was something I was particularly nervous about. I didn’t design clearances into the linkage parts to save design effort (read: I’m too lazy to make proper constraints) so some filing was needed to get them sliding freely.

Hardware installation time! I made sure to make little access ports for the motor wires, because wouldn’t that be embarrassing?

We move now to my old high school workbench down in Atlanta, which is somehow still there and in operation (maybe being 16 feet long has something to do with it). I got all the mechanical hardware installed before leaving, and decided to save the wiring for the Dirty South.

Pictured in the foreground is my new best friend: the itty-bitty-baby-offset-screwdriver-bit-ratchet. It’s McMaster part number 52725A31, and it’s positively adorable AND the only way some screws on Roll Cake are accessible at all. I designed it this way, so it’s legit, right!?

 

As usual with this thing, wiring is a disaster. The ESCs of choice are the Afro 30 Race with SimonK set up to do reversing with my usual tricks. They’re small, but not THAT small. I decided to keep the ESCs on the same side of the bot as their motors in order to reduce the amount of long wiring runs, so there’s two on the right side of the bot and one on the left.

All the motor connections have now been made, and I left one task for last before I soldered the 3-pin signal wires to the receiver….

I had to program the SimonK firmware to activate reversing and braking and my preferred goodies. I planned ahead and made this servo to tiny-clippy-jiggle breakout cable which I’ve termed “The Simonator 2.0” in order to grip the signal wires of the ESCs. While I could have programmed them all beforehand when the servo conectors were all still there, I decided I needed this cable regardless just in case I had to change something in the field, post-installation.

I brought the finished bot to one of the robot panels at Dragon Con. Sadly this year I fell off the bus and did not host any panels, but I’ll make sure that changes next time! I’m glad that recently, my Makers presentation hasn’t really been needed – in the most recent years I delivered it, the percentage of the audience who’ve experienced CAD or soldering LEDs together, etc. has grown immensely, in my opinion greater than the rate of self-selection for these things.

Here’s the linkage fully opened! Note the preponderence of little shoulder screws forming the joint pins – I standardized all of these to the same length to save myself from my historic habit of making my robots all shoulder screw nightmares.

….and now announcing my new 6lb multibot entry??? This is the head of Lucy‘s Mei cosplay, the freeze-ray dispensing Snowball. overwatch has ruined my life run away now

I’ll post some of the test videos of Roll Cake soon – I was happy enough with its performance in the garage in terms of drivability and flipping, even if it won’t prove that impressive in the box due to being repackaged test rig parts.

überclocker

We now move onto good ol’ Clocker, which has looked like this since Motorama…

Pretty depressing, eh? In the final rumble of the 30lbers, I burned out one of the SK3 4240 drive motors, so I was on the hunt for replacements, and Hobbyking didn’t have stock in that size at the time.

What they did have is a sale on their new NTM line, which had a similar size motor:

So I scored a couple of these – they were physically the same dimension, but unfortunately these motors were slightly faster again, so I was facing the very real prospect of Clocker hitting 25mph without much provocation, which could be a liability on the Dragon Con stage.

I emptied the bag of Clocker remnants to see what I could salvage and what I’d have to remachine – the answer was really basically everything minus the motor output gear :p

Good thing Clocker is legal in the new 30lb Sportsman’s Class rules enacted FRESH AND NEW this year for the Franklin Institute event in 3 weeks!

To extricate the motors, I had to disassemble the frame, which proved a little…. challenging after Glasgow Kiss gave it a once-over. There were some special extraction techniques I had to use here on this machined corner!

From the spare Clocker parts bin I extracted another section of the 1/2″-10 leadscrew and flanged bronze nut that fit it. I’d bought a few spares last year in anticipation of needing to machine them eventually, and here we are.

The bronze nut gets machined all the way down to be smashed into the bore of the modified Vex Pro spur gear. When the gear spins, the leadscrew gets sucked in and out of the nut, and its own reaction forces are taken up by the bronze bushings surrounding it. All solid, all friction, all the time, but it gets the job done.

I’d like to eventually rebuild Overhaul’s actuator in this way, except with preloaded tapered roller bearings, for #season3 whenever it ends up being :'(

 

Mate this up with new waterjetted plates that I drilled and tapped and we have a new actuator. The drill gearbox was reassembled from stock pieces from my giant decade-old (…) bag of Chinese cordless drill parts, using the original shaft which was not damaged in the fight. I have enough pieces now to straight up make two whole actuators, which is nice.

After that, I repaired the bottom plate of the bot by stitching new holes in between the hole ones. I’m not sure if I’d use #4 screws like this anywhere in a loadbearing path (which the top and bottom plates do count as) if I redesigned Clocker again, since the indirect shock loads from the 30lb Featherweight class alone (in the form of getting socked by a spinning weapon) is much higher than Sportsmans. One of the corner hits from Glasgow Kiss sheared off a half dozen of my bottom plate screws just by momentarily bowing out the frame enough.

 

While I was in there, I swapped in the spare wheels made from 60A Mystery McMaster Urethane (actually OEM’d by Forsch Polymer, the most 1997 company extant in 2017). The white Smooth-on Simpact wheels had worked well enough, so I wanted to see how these would do.

Well, everything is technically ready for reassembly!

I rememberd a much better way of taking the entire top off Clocker. Previously, it involved trying to drive the center lift shaft out through ALL of the components that were shaft collar’d onto it. This was patently painful. Unlike Overhaul’s unboltable lift towers, Clocker has solid ones built into the frame rails. It turns out if I just unbolt the outer and inner frame rail on one side as a unit (9 screws), there’s enough room to wiggle the shaft out of the bearings and pop the whole thing off.

 

Clocker was the last thing I wanted to put the Brushless Rage test units in before shipping them off for production. The severely under-geared high-Kv motors will be a good stress test for the architecture, since on the Dragon Con stage I’ll mostly be driving at low speeds and turning/reversing often.

Check out that little Onyx bracket I made to hold the units. I wanted to place them flat against the frame rail behind them here, but this arrangement kept the wiring cleaner and away from the outrunner motors.

A new waterjet-cut gear and some quality Taki-time later, and everything is now back together. I did some drive testing outside, which showed me that the Brushless Rages were working great even under duress – the gearing on the motors is low enough that the bot has trouble turning in place on a high traction floor. So here I was hoping that it would be even able to turn at all on the Dragon Con stage carpet! But once it takes off… boy does it want to keep going.

the charles and the dragon con

Welcome to Dragon Con! Have a van.

I would have loved to bring VANTRUCK instead this year, as it has been now impeccably reliable after its lobotomy and subsequent headcrab installation, but could not even begin to justify the 9 miles per gallon each way. It’s beginning to dawn on me that the kind of person who would have bought one of these things new, never ever thought about the cost of fueling and ownership. I’m not quite to that level in life yet.

Overall, this con worked out a lot differently than some of my past Dragon Cons. See, I wasn’t scrambling to finish a robot every day for once – Roll Cake’s finishing work and testing occurred before the con started. Instead of trucking around a giant transforming mechanical prop, Cynthia instead prepared a bunch of pieces for the Dragon Con art show (which as I found out was nontrivial to get into)

On top of that, it’s become more of a yearly reunion for some of the BattleBots competitors and friends who have moved around the country & world. For example, I found Lisa Winter!

The cotton candy committee has arrived.

I attempted to replicate her tattoos in the middle of talking at a panel. Nailed it!?!

And for the first time in probably over 10 years, I actually played in a gaming tournament. There was an Overwatch ruined my life run away now tournament being hosted at the convention gaming center, and a few of us essentially set up #BattleBotsPlaysOverwatch.

The house equipment was sub-par, though, so we didnt’ do too well – people who have clearly been to more than one tournament brought their own mice, keyboards, headsets, and pillows and stuff. Now that’s pro.

 

HELLO FOR I AM MECHANICALLY THEMED VIDEO GAME GANDER AT MY CURATED ARRANGEMENT OF MECHANICALLY THEMED ITEMS

Alright, you know how Dragon Con goes down. Let me spare you the details and get to some robots!

MicroBattles has grown to the point where it has to be single eliminations only and running across two arenas to keep up. I’m glad that it’s a good problem to have! However, it does mean you’re pretty much one-and-done.

There wasn’t much to do with Roll Cake beforehand except get some driving in. I decided to move the tail on the flipper downwards one mounting bolt such that it was more likely to rest on the floor – otherwise, the bot tipped abouts its wheels a little. However, it kept weight on the feeder wedge, so that was a plus.

Robot Battles features mostly local builders who kind of keep to that series of events around the Southeast. It’s refreshing to see bots which haven’t been forced to become the small monolithic dense bricks that most competitions have forced them into being. These two, for instance, are hand-bent sheet metal from Home Depot, with a hand-soldered custom motor driver inside. I honestly miss these kinds of builds.

Pool noodle wheels were fully in fashion this year, made popular by the Dale robot Noodles. Hey, they’re totally not entanglement devices. The wheels aren’t supposed to come off, just incidentally if you hit them with your spinning thing! Wink wink. I suspect this kind of thing might get roundabout-banned somehow, but on the other hand, it’s 2017 – get a reversible ESC on your weapon already!

Sheet metal everything, down to the weapon! Now this is robot fighting.

Other builders who had too much time on their hands chose to adorn their robots in….. creative ways. That’s hand trimmed and applied fake wood veneer vinyl on Margin of Safety here…

I was pretty eager to fight Noodles since it’s high ground clearance and invertibility would have made for a whole match of flips with Roll Cake.

Besides the wacky builds, you had your usual array of kit-bots and modified kit-bots.

Roll Cake was matched with Margin of Safety first, obviously a fight that I was hard pressed to win. Aaron put on the miniature vertical drum module for the match, so we went head to head trading blows. Margins having the the smaller drum advantage,  Roll Cake got flipped over and I spent a while trying to self-right, but at the time didn’t have any skids on top of the bot, so I trundled it around a few times trying to get him to flip me back over.

See the two little hex nuts sticking up from the top? That was added after this match so I could get flipped over in the rumble and maybe get back up. With the drum bouncing off the ground, it wasn’t going to get enough momentum to roll it self back over, so after a while of trying, I decided to save the effort for the rumble.

In said rumble, the drum promptly threw the rubber o-ring belt and jammed as soon as it started. Well bugger me with a #1/2-20 tap, that sure didn’t come up in testing! So I spent the whole time running around like an idiot.

I suspect that spinning up quickly made the belt stretch enough (since rubber cord doesn’t have a tension element in the middle like fibers) to jump out out of the pulley enough to get grabbed by the drum. In Roll Cake 1, the pulley spacing was far enough apart that it would have just fallen off, but this time I had to move the drum closer and so there is a lot of overlap with the drum iself.

Hey, all things considered, I walked out with a working bot. It’s now time to get serious with Roll Cake. I’m extremely confident in the mechanism now, and so it’s time for it to stop being a test jig on wheels. The weapon motor is severely undersized – if there was one design which should have a motor-in-drum setup, it’s this one! And, furthermore, freeing up the space occupied by the weapon motor might mean I could use more conventional drive motors. The hub drive worked well enough, but I still prefer the positive feel of a geared motor.

And now it’s Monday!

 

With the return of all the robotty TV shows, we’ve seen a serious and sustained rise in the audience count. The room filled up to this level well before matches began, and the line continued out the door the entire day.

An entry being finished in the pit area before matches begin! How quaint.

Lisa brought itty-bitty Tento, weighing about 8 pounds, and entered it in the 12lb class for fun. This thing was built as a “how to build a robot” demo piece. Unfortunately, it suffered a gearbox failure literally right before matches began and it was of a type that nobody else was using, so spares couldn’t be located. Sad day – maybe next time!

Clocker just needed battery charging (and the replacement of a chain tensioner block) this whole event, so I’m quite pleased.

I only ended up having two matches – one against this giant purple thing (which had radio problems at the end – notice us both running onstage to disarm it), and the second against Dale’s Pushy Grabber. This thing has been sweeping RB events (literally) with the lynchpin strategy of wiggling under your bot almost no matter what. Now, normally I offer at least some resistance to Dale, but this thing I had to approach either at a very specific angle or risk getting plowed off the stage almost instantaneously. We had 4 total matchups, in the middle of which Dale had to reattach one of the rollers and I had to replace a chain tensioner block which finally decided to wear through and fall off.

This event really showed that, much like my arena-optimzed Test Bot v4 days in the Late Aughties, wide ground-hugging wedge surfaces really are more of a liability on the stage than an asset. Notice how in the final Pushy Grabber matchup, I tried executing the same strategy, but got hung up on the edge just long enough to become vulnetable. The only weakness of Pushy Grabber right now is a long-reach forked robot like Nyx with the lifter attachment – Clocker did not have enough “stickout” to really get a good handle on it – nor did it really on other bots.

Unlike version 2 and 3 where the clamp arm reached all the way to the end of the forks, this one for the sake of looking more like Overhaul has the ‘grab point’ more inwards, so I had a harder time getting opponents into the clamp in the first place unless I took a straight run at them with some velocity – upon which I would often run into the stage edges.

I stuck around for Rumble #1 which I won by virtue of trying to get around the damn stage and mostly ignoring opponents…. and in Rumble #2, I just took the wedges off and ran around like an idiot some more, accidentally handing the win to the purple thing after doing some kind of J-turn rocket jump off the stage. Oops.

This event was also the final straw for me in terms of gearing down the drive motors more. I’ve been threatening to go to 2-stage gearboxes for the drive, and now it’s more necessary than ever. Clocker v3 was geared for 19mph and was already a rocket, and there was barely any need for it on the stage. I’ll probably move to 11:1 2-stage P60s and use smaller 35mm drive motors.

Yes, this kind of thing is legal here, with a catch: It doesn’t exceed either 500 RPM, or 20 ft/s edge speed.  It’s driven by a geared motor, so it will more lift your bot up and chew at it.

 

Replicas of BattleBots entries are the in thing right now! This is Tuskin Raider, a 12lb Razorback-alike that Jamison built. It got all the way to the 12lb finals.

This is a 12lb shell spinner.

And here we have the assembled Power Rangers shot of all the scale models. Hey, we can film #season3 right now if we just get all the cameras up really close. I keep bugging Jamison about why he didn’t make Tuskin a 30lber instead of a 12lber.

So that’s it for Dragon Con! Two working robots remaining, shenigans abound, and…. no van adventures. Wow, when did my life become routine? Obviously it’s time for another all-vans update soon….

Brushless Hipsterism Intensifies: Returning to Brushless Rage. Brushless Mini-Rage!? And Trying Hub Motor Drive in a Beetleweight

Oh, Brushless Rage… how far you’ve fallen. It’s been standing idle since late last year when I got the first version running. Thereafter, it began having some rather obdurate power supply problems that I couldn’t resolve with a few different attempts, and with #season3 still unknown (TO. THIS. DAY. UUUUUUGGGGGGGGGGGH.) and having to pick up and move shops, I lost motivation. Now, with the spring and summer silly go-kart season coming up, me really wanting to pregame getting Overhaul back in shape ( *cries deeply* ), and my comrades over at Robot Wars screaming for assistance, it’s time to put my robes and wizard hat again.

The last time I really worked on Brushless Rage was in October. After tuning out the first one, I went ahead and made a 2nd one. I wanted to get Sadbot running on them for a few test drives.

Here’s my innovative housing for the two controller! Bolted back-to-back with drilled holes in the Ragebridge shipping box.

And that was all! It was retained by a few zip ties running through the bottom ‘breadboard’ baseplate. I didn’t take much test video of Sadbot running on them, unfortunately;really the only one that exists within easy reach is, uhh, this one. While it doesn’t show them getting whipped, they definitely don’t not work! Yay!

But not for long. I soon lost both of the units in further off-bot tuning of settings. They didn’t blow up, but simply failed to ever power on, with the LM5017 regulator simply sitting there getting hot. The only “fix” was replacing the regulator, and I say “fix” because that really didn’t fix anything, and they would die again within minutes or even seconds.

No problem… maybe it’s just an issue with the two boards. I’ll just try another one of the five total I ended up making….

Nope. Nothing. They died one by one, all to the same symptom. I tried redoing my math for the regulator for the 4th time, thinking maybe  I made a mistake somewhere. I even tried mimicking the reference design to try and get something running. I literally never do that.

At this point, I figured it must have been something incredibly dumb and simple I missed. But why would the first two have worked at all, even for a little while?! Convinced the solution might just suddenly invent itself, I stopped thinking about it.

And so here we are, a few weeks ago, when I’m slowly building up a new rev of the logic board that fixes up some trace routing problems and Little Blue Wire problems. Again, the logic regulators kept exploding, some times dramatically taking out the input trace like seen above. The little light is strapped across the 15V gate drive supply to give me a visual indication of it being on.

What is with me and being unable to use switching regulators!? I recalled the Ragebridge Diode Debacle of 2015, and decided to take one last Hail Mary run through the datasheet along with friends to carefully cross-check each other for boneheaded mistakes and…….

TI, you assholes.

So here’s what’s going on. The Vcc pin of this chip allows you to power it from its own output voltage, which is often fairly low, so it prevents a lot of heat dissipation in the chip since otherwise it would have to derive its own power from the voltage input (up to 95V). But what I missed is this only works up to 13 volts. My gate drive supplies were 15 volts by design.

Beyond that? Who knows?! It might work, it might not. I’m guessing my first two were just high enough in manufacturing overhead that they worked for a little while. Subsequent statistics were not on my side.

Okay, whatever. I cut off the 11.3kohm feedback resistor and threw on a 9.1kohm to drop the voltage from 15V to about 12.5V and let’s see what happens.

Ah, it wakes right up.

Of course it does.

So I decided to respec the gate drive for 12.5V. Why do this instead of go for the full 15+ volts? Because I’m really aiming to make this design work at high-for-robots voltages of 36-48v, possibly up to 60V nominal with a different power stage, so I’d like to save the power dissipation in the chip’s onboard logic power supply.

The change in drive voltage will slightly affect the drive characteristics and switching time. For now, I’ll keep all the power stage parts unchanged, but I’ll probably tune the gate resistor values later.

 

To get rid of the noisy ripples on the feedback network and to stabilize the switching frequency, I added some more bypass capacitance to the chip. This was not included in the design at first, since I figured my large ceramic input and output caps were nearby, but it really really wants its own little private capacitor on Vcc. Gee, I thought I was a princess at times.

So now this thing is pretty much bombproof. Here’s a video of it throwing around one of the 30-pound old MIT CityCar prototype motors (which I inherited 4 of after the project was dismantled):

In that video, it’s running from 36 volts. I tested it with a smaller motor all the way up to 50V input before getting too scared for my power supply’s life; I’ll need to try it on a larger high-for-robots voltage power system later, but nothing smelled imminently unhappy!

With the regulator death issue apparently behind me (again) I decided to push another board revision. This time, I added all the necessary bypass caps and changed the layout of the logic power supply, as well as take out some parts I decided were superfluous.

The logic power supply got a little smaller and more electrically optimal. The whole thing is just less messy now. I like it – it takes up around 1/3rd square inch of PCB space on one side. At the behest of a professional PCB engineer friend, I turned the inductor 90 degrees and joined it with the LM5017’s switching node with a small trace instead of a larger groundplane. This would prevent the switching node (a source of huge voltage swings in microsecond timescales) from broadcasting as much noise.

Besides some other minor trace chasing, what’s going on down below on the board is also something experimental:

That there is a bidirectional optoisoated I2C bus for transmitting data between two microcontrollers which should never meet directly. I had a single-direction opto input on the board revisions so far, but this prevents updating of settings via the SimonK/BLHeli type bootloaders. That means tuning the settings require busting out my chip socket every time, which is annoying. I reviewed a couple of bidirectionally isolated bus schematics and decided to try this one out first, since it involved diodes only, not transistors.

The problem is, the I2C bus is a open-drain configuration with pullup resistors and ‘1’ bits transmitted by pulling the line down to 0v. I kind of wanted to try keeping the opposite polarity, so to speak (even though SimonK supports an inverted input setting) just because I’m used to thinking about things this way. So I tried flipping the circuit over…. pullup resistors became pulldowns, and common-emitter became common-collector, and so on.

It makes sense in my head, but I’m sure excited to see this work!

On the board, this is the layout. It doesn’t consume much more space than my previous 1-direction optocoupler setup, and can be bypassed for testing with 2 wires if needed. That’s the nice thing about keeping things upright signal-wise.

So before I sent this board revision out, I stopped for a moment to think who would really be wanting to use Brushless Rage. I’d designed the 12-FET board to effectively replace Overhaul’s 250A DLUX controllers (with more realistic ratings, mind you). I’d say the majority of people who would buy such a thing won’t be running motors that big.

Recently, the thought of a “Half-Rage” has been coming up in my mind as something worth pursuing. This would be a board with about half the footprint of a RageBridge 2 and supporting about 1/2 of the amperage. As some curious question-askers had innocently drilled into my mind, this would be an Actually More 30lber-Sized controller.

> mfw "When are you going to make a 30lber/12lber version of RageBridge?

 

With this in mind, I decided to make a copy of the power stage and began downsizing the hell out of it.

Step 1: Reap what I sow when it comes to the sheer number of vias I deposited under the FETs.

After bunching the FETs together, I referenced one of the earlier abandoned Brushless Rage layout ideas for the output wires. This board is now short enough that I’m comfortable pulling the phase outputs all the way to the right with the power. Keeping all my wires on one side is something I prefer.

Somewhat final routing of the fat bus traces here. I had to move a few gate drive traces, as there was no longer an opportunity to swap sides in the middle of the FET bank. Power+ runs straight from the bottom right corner, through the bus capacitors, into the high-side FET. Power- emerges from the current shunts and then has 3 paths to return to the buscaps before being slurped up by by the wire hole on the upper right.

Here’s an overlay of the signal board design on the power stage, showing roughly the size of things. The final power stage is 2″ x 2.75″. Not the tiniest thing, but I have more capacitors than you!

This board shares a lot of thermal characteristics with RageBridge, so I’m pretty comfortable calling this a 50A continuous class controller. 50 real under-partial-throttle amps, so that’s what, like 1,200 Hobbyking Amps?

In all likelihood, this controller will be able to handle an average 63mm SK3 motor in continuous duty applications like a silly go-kart. Robot-wise, it will probably be stressed handling the same in bidirectional drive mode.

Fast forward a few days and….

OhmygoditssocuteIjustwanttohugit and then make it run a 80mm outrunner on 12S violently. I’ve ordered parts to make a handful of these, and two are going on Sadbot ASAP to be driven until something blows up!

Direct Outrunner Hub Drive for Your Little Bot

Next up, something even smaller!

So I’ve long been a connoisseur of fine handcrafted hub motors. I got curious recently on using direct-drive small outrunner motors in an ant or beetle after thinking a while on the redesign of Roll Cake. Version 1 of Roll Cake was honestly just a braindump of a vision I’ve had for years for the shape of the bot, and everythng else came second to that. On the beetle scale, the multi-pulley serpentine pulley drivetrain simply had too much friction for the Fingertech motors (which were severely underpowered for the task) to overcome.

For the next version, I’m ditching the triangular cheese wedge shape for something more straightfoward. The cheese wedge will be back for a heavier weight class. Roll Cake’s design really wants to have the middle of the bot kept clear for the flipper linkage. I’m sure I could work around it with low-mounted drive motors and similar, but this was an excuse to play with brushless things!

I based my thoughts off Jamison’s mini-gimbalbot which used camera gimbal motors for drive with a small Hobbyking R/C car ESC. It drove “okay”, certainly capable of a weapon delivery platform. So naturally, I wanted to put some SimonK-capable controllers on it and see how the handling would change. I got a small selection of motors: A pair of DYS and Quanum 28mm motors as well as a pair of Multistar “HV” 460kv motors. 460 RPM/V is reeeeeally slow for that size of motor that isn’t a gimbal motor, so I was quite interested in them.

These are the gimbal motors. I like them for their pancakeyness – the Quanum motor is more 30mm and has a bigger stator.

Playing around in the CAD model a little for component placement. At this point was when I realized Roll Cake in this incarnation might end up looking a lot like The Dentist :P

I designed up a few hubs that bolt to the face of the motors and have a tapped middle hole to sandwich a wheel. The wheels are spare 1.625″ BaneBots wheels that I originally bought for Candy Paint & Gold Teeth.

Shown with those motors is a ZTW Spider 18A controller. My typical SimonK ESCs, the Afro series, were out of stock when I placed this order, so I took recommendations from people on what I should use. The Spider series are fairly popular these days among small bot folks.

The issue is, they come with BLHeli firmware, the other other open source drone racing / vaping rig development path. It’s a newer effor than SimonK and has a more polished interface. I’d read about it before, but not worked with personally. Other builders have said it doesn’t run robot drivetrains as well due to being much more optimized for propellers. So hell, why not – this was a chance to explore that side of things.

Here’s some real life CAD layout, featuring the Multistar motors.

I really wanted to use the gimbal motors, but they disappointed me in bench testing sufficiently that I didn’t even end up installing them. Basically, they can’t draw enough current to make torque at typicall little-bot voltages. With phase resistances of 10-20 ohms, they can really only draw ~ 1amp or so. I mounted one in a vise and could stop the motor with my pinky finger at full radio stick input.

These motors might be better at 6S and up, but for the time being, since all of my small-bot batteries are 3S, I decided to pursue making a test platform using the Multistar 460kv motors.

 

The platform of choice was…… one of Candy Paint’s spare weapon pulleys. I literally spilled my “preformed robot spares” bin on the ground and tried to see what was good to use as a base. Hey, it’s round and has convenient wheel holes in it already! All I needed to do was quickly whip up some motor mounts (3D printed) and I was in business.

 

Here’s everything hooked up. That nut is for a counterweight on the front to add some friction against the ground while turning. Otherwise, it had a tendency to keep spinning and spinning if you even thought about turning.

Communicating with the ZTW Spiders was a hell of an adventure in its own right, and I am putting this post under Reference Posts because I’m 99% I will need it again or someone else will randomly find it while needing the information. If there was any industry that continually pisses me off with how undocumented and tribal-knowledge focused it is, it’s the R/C anything industry.

So, here’s how everything went down. I lost my AfroESC USB communicator, so I purchased the Spider SPLinker advertised as working with the controllers. I also bought one of these stupid things:

That’s a “SimonK/BLHeli compatible” dongle called the ESCLinker. It allegedly can talk to either kind of ESC, but there was nothing remotely resembling a manual or operating guide; all of the search results for this brilliant device were people complaining that there was no manual.

So I’m writing the manual now: This thing does not want to talk to KKMulticopter Tool (my go-to for flashing SimonK ESCs). It will only talk to BLHeli Suite. As a matter of fact, I couldn’t get the Spider SPLinker to talk to ANYTHING. For all of my tuning here on, I used the ESCLinker tool.

Here is BLHeli Suite, which is hosted on the sketchiest possible website that is one tier above compiling it from the Git repository yourself.

Notice how I’m connected to the ZTW Spider now. The ESCLinker (and SPLinker) install as virtual COM ports.  The necessary baud rate is 38400 baud, not 19200 (Afro/Turnigy USB dongles, to my knowledge)

By the way, once I realized this, I tried to talk to the SPLinker and ESCLinker on KKMulticopter Tool again using 38400 baud; no dice.

Further investigation revealed that the ESCLinker needs these options to communicate to the ESC – both options 2 and 3 will work. So if you’re listening, people mystified by the ESCLinker: Talk to it on 38400 Baud and ask it to communicate to your ESCs with BLHeli/SimonK 4-way-if bootlader.

Ugh. One of my selfish reasons for wanting Brushless Rage is so it’s one known quantity and I never have to dick around with other people’s open-source bullshit again.

So with all that behind me, I decided to try out BLHeli drive on the little pulleybot. I went with intuitive settings based on my SimonK advice, which included “Damped Light” mode, a fancy euphemism for synchronous rectification/complementary PWM, medium to low timing and maximum start power. BLHeli also has a “demag compensation” feature which appears to delay commutation to compensate for current decay in the windings. Who knows!? I wasn’t given the imprssion that its users actually understood what it meant, nor does the manual really say anything useful.

I found that Demag Compensation turned all the way up gave the best performance, along with maximum start power. However’ it still couldn’t compare with my SimonK experience. It seems like even maximum start power is much weaker than what SimonK permits you to do.

Here’s the final test drive I made with the BLHeli Spider ZTWs:

I’m honestly not very impressed. I think BLheli is very much optimized towards multirotors and helicopters (hmm, maybe it’s even called BrushLessHeli for a reason!) and the settings are more high-level and mask the underlying mechanicals of the firmware. I think this makes it much more accessible to hobbyists, though. In the end, I’m not very enamored by it.

These were my final settings:

For a direct comparison, I decided to replace the ESCs with my old SimonK Afro 30 amp units. These have been on quite a few bots now, starting with the original Stance Stance Revolution, and they were completely beat up. But they still worked!

A direct replacement into the existing wiring harness later… we have SimonK!

I found myself in the awkward position of using KKMulticopter Tool to compile a customized SimonK formware, then uploading it via BLHeli Suite because my USB dongles didn’t talk to KKMulticopter Tool; I’d lost my AfroESC USB dongle a long time ago.  BLHeliSuite doesn’t seem to have a firmware editor window that I’ve found yet.

Here it is. I found the SimonK version so much more responsive that I actually needed more counterweight on the front. So, a non-fitting bolt gets zip tied to the nut! Now the bot’s a lot more controllable:

I like it a lot. It might even be worth doing 4WD to give me more yaw damping, or I’d have to design the bot to be well balanced enough on front skids, or something. I used my typical SimonK parameters: complementary PWM, maximum braking power, maximum braking ramp speed, and adjusted start PWM limits to something like 50%.

I’m aiming to get Roll Cake and maybe Colsonbot running for this year’s MomoCon in a couple of weeks, so hopefully I’ll post up some design news soon!