The RageBridge Breeding Program: Alpha Tester Application & Other Stuff

They’re done!

After my Digikey and Avnet shipments arrived, I could finally finish out the 8 remaining RageBridge2 boards in the panel. Using my handy dandy hot-swap test rig, I’ve determined that they at least power on right now without exploding, which is a good start.

Before I upload running code, I’m planning on adding a mix option to the firmware which can be activated by soldering a little jumper wire (a future board rev will add a header that can be used to select it). This way, the controller can be used with non-mixing radios (like 2 channel pistol grips) to let one channel control steering (differential) and the other speed (magnitude).

Update 16 October! The mixing firmware has been implemented.

The two RageBridge2 boards I assembled last time have been tested in real-life driving already. First, I installed it in Null Hypothesis in place of the RageBridge v1:

Then I gave board serial #2 to Adam and had him install it in his pre-Dragon*Con speedballed robot Blitz.

And then, we faced off at the Somerville mini Maker Faire:

Basically what it reduces to is two somewhat gimpy bots driven by two out-of-practice drivers. The motor that smoked in Blitz was on the front lifting tines, and it was being driven by a Victor 883.

But despite my best efforts to test these boards out in a strenuous condition, Blitz and NH are kind of… the same. They both run 4 overvolted drill motors (and keep breaking them… clearly these things have gone totally to shit) coupled to 4 inch wheels, and while NH has a higher top speed due to my more overvolting, the RageBridge boards limit the  motor current such that the motors kind of behave the same anyway.

I need more data points before declaring the RageBridge Certified Legit™. That is why I will now officially announce the….

ragebridge breeding program

These 8 boards will be released “into the wild” as much as possible such that I am not in control of their use and installation save for a short user manual page. I’m therefore going to put the call out for participants.

You may qualify for the RageBridge Breeding Program if…

  • You have a load, such as a robot, vehicle, grain thresher, etc. which runs between 18 and 36 volts, has 2 DC motors, and would like about 40-50A, but can live with 60 amps at most. This is because the RageBridge has intelligent constant-current limiting set to 60A. So if you don’t mind a little… anemic acceleration on your twin Magmotor mountainboard, that will work just fine. At this time, the 2 output channels cannot be combined into a single high-current channel.  The 36 and 24v boards are currently not the same in order to test out different components, but the production version will run the whole range of voltages.
  • It exists right now and you can swap RageBridge into it. Sorry, projects which will be finished Real Soon Now cannot qualify.
  • It uses an R/C radio as an interface. RB currently cannot take analog inputs (e.g. throttle pedals) or TTL serial commands. “Vehicle firmware” which does take these inputs is one of the things I intend to work on as soon as possible, and serial commands is also on the list of things to add. The firmware is easily flashable in the field for when that happens; you will need an FTDI cable. After all, I do write the firmware for this controller in Arduino…
  • You are willing to send $50 USD to help me offset the cost of boards and parts. If it works great for you, then awesome – 36V dual motor controller for $50, and I’m not gonna ask for it back! But…
  • You understand that you are not receiving a finished product and there is no warranty on functionality or reliability. Do not use this to hoist people up elevator shafts or to run your heart-lung machine, for instance. Would you even use an Arduino to run a critical medical device like that?! Each RB board will be tested before it ships out and I can only take “returns” for DOA.
  • You are willing to send me video, pictures, and/or test data showing the board working in your environment.

If you agree with the conditions, send me an email (charlesg@ this 3-lettered university name .edu) with the subject “RAAAGE” (that’s 3 A’s) and the following information:

  • Your load details – what it is, and what voltage it runs, so I know which board type to send you.
  • How soon you intend to install and test the RB board
  • How you intend to mount the board in your load (via its mounting screw, heat shrunk, above a fan, on a boat with a goat, etc.)

Because there are only 8 boards available, I clearly cannot take everyone. I’m seeking “diversity of loads” here – vehicles, robots, elaborate dentistry tools, etc. I will set a deadline for “applications” of MIDNIGHT on Wednesday, October 17th (that means as soon as the clock turns to 12:00 and it becomes the 17th). Eastern Standard Time. I’ll notify both accepted and rejected parties then. They’ll ship during the week.

Preliminary specifications:

  • 18 to 36v nominal operation
    • Absolute maximum voltage for “24v” boards is 37v, absolute maximum voltage for “36v” boards is 57v.
  • 40A continuous at room temperature with no additional convection or insulation.
  • Constant-current region above 60A (your load will see a maximum of 60A, plus or minus a bit of ripple).
  • R/C servo pulsewidth range of 1900us to 1100us with 1500us center. +/- 20us deadband.
  • 5V power available for receivers
  • 4.5″ x 2″ outer footprint
  • 1.7″ x 1.7″ hole pattern for mounting, sized for #4 screws.

the ragebridge fundraising program

I intend to send out one more board revision before releasing the design to manufacturing. This new revision will wrap up some of the hardware loose ends like component placement, manufacturability, trace routing optimizations, and like, making the RESET button actually reachable with an average finger.

Boards and parts (especially parts for 10…) are still really expensive, especially in low test quantities where I can’t take advantage of price breaks.

If you like the RageBridge and its new addition of a constant current output mode to the small- and medium sized robot/vehicle controller world, and want to support its development, then please let me direct you to my donations page. There is no suggested donation, and contributing does not constitute a pre-order for any product!

The whole mission of the RageBridge project is to try and make a compact, reliable dual channel high-powered motor driver using 21st century designs and parts, with no “fanciness” like dual encoder inputs, built-in PID controls, 8 different ways of taking commands, etc. in one unit. It is a rebellion against the new trend in robot controllers to integrate all of these functions and charge more money for it while not really being that good at, you know, driving motors. Basically, I want to give the venerable Vantec series and Victor 88x series of controllers a this-decade equivalent. Raw, simple power for applications which demand it, and nothing more.

the ragebridge kickstarter

Support us on Kickstarter! The link to RageBridge’s campaign is…

Not yet. I fully intend to pitch this sucker up on Kickstarter when I have a demonstrably working device. No promises and renderings here – I’m fully intending to use KS to gauge the initial market and to tell me how many times to hit the button. So if you’re just totally into a public fundraising campaign or find paypal links repulsive, hang tight!

Some more 3D printing shenanigans: The Up!

Scheduled plug: I’ve added a pile of new things to the Stuff for Sale page! Go check it out.

An exciting new thing came for me in the mail right after Maker Faire, and I think I’ve gotten finished playing with it enough to post.

Back in June, I wrote up the Democratic People’s Republic of Chibikart for Instructables and entered the Make It Real contest. It won one of the first prizes, which is an Up! Plus 3d printer, to add to my flock of 3D printers.

That was in July. I just got it a week ago, due to Instructable’s famed lack of shipping organization. That said, I was greeted with this in the shop last week:

Shiny. Let’s open it up!

I see the thing…

Very shiny (looks like glossy enamel) indeed. And orange, I guess because this was an Instructables-commissioned machine.

The Up is a pretty simple machine. It uses the ‘overhung arm’ architecture where the table is mounted on one moving axis and the head is mounted on another traveling, perpendicular axis. Now, I actually think this is the worst design for 3D printers because not only do you have issues stemming from workpiece acceleration (it’s moving), but the axis inertias are also mismatched.

Furthermore, the arm that sticks out is really flexible – it seems to be only mounted by one flap of sheet metal. It The X movement of the extruder is transmitted as vibration into the arm, and the end can resonate a fair amount – at least 3 or 4 mm of wobble at the end! Luckily the printing occurs very close to the arm’s support, so it seems to retain resolution accuracy. But still, it makes the machine design side of me cry a little. The new Up! Mini addresses this with a dual-rail axis design.

It also has a really really loud buzzer that makes it sound like an overly enthusiastic microwave oven whenever it starts, warms up, and begins/ends a print.

It also comes with a fairly extensive toolkit. Fairly typical 3d printer diddling tools like tweezers and a paint scraper are included, as are build platforms, mounting screws, and a nozzle wrench (but no replacement nozzle). I also got a pair of fabulously pink work gloves, but I’m not sure how they’re supposed to be used (are you supposed to grab the nozzle while hot?)

After I made a klein bottle as the printer’s first test, I let it run overnight on this compound of 5 cubes.

I’ll take a moment mention the UP! software. As far as I can tell, it’s closed source. It offers the usual array of tunable features – layer thickness, speed (just fast, medium, or fine), and infill (loose, dense, solid, hollow…), but only generates a square mesh (while Replicator can generate hexagonal meshes or just line scribble). It also slices way faster than ReplicatorG, but the user interface is a little strange with its button press sequence to do a common task like scaling or rotating, but that is a minor complaint.

What is REALLY nice about it, though, is how it generates the support lattice. This is the one place where I think it beats everything for intelligence, because alot of planning has to go into making a homogenous-material (i.e. not dissolvable or something) support that just falls away when done. If you’re a Stratasys printer, you can just puke support material everywhere because the intention is for said support to be dissolved away in the bubbling cauldron of lye. This is a very different, controlled kind of puking.

That entire cocoon for my cube thing came off in one piece, with absolutely no knifing or prying. Same deal with the “raft” layer. Contrast this with the amount of scraping and filing I have to do to the average Replicator(G) print and it seemed almost magical. I’m not sure how it is able to do this -it doesn’t seem to pause for a temperature change when moving between supports and part, so I think it must just be very careful extruder control to make sure the parts just barely come into contact.

It generates several different types of support – there’s the loose lattice that is used to build up the bulk of the support, then a very fine and nearly solid layer that is the one which makes contact with the part (which makes the near trivial breakaway even more amazing). There’s also a “cross hatch” like option which is used only for the loose layers.

Either way, seriously, what? I wouldn’t mind seeing a more robust support generation scheme for Replicator. Or, even better, maybe I should try hybridizing this guy with our Replicator 1 and make an Uplicator. I’d love to combine the high speed-capable gantry head of the Replicator with the Up’s slicing engine and controls.

There’s also one more thing I like, which isn’t Up-specific but I have not seen it until now: perfboard build plate. I am a definite fan of this. On that giant 4.25″ wide print, there was less than 1mm of lift on one corner of the hexagonal base. In ABS! As far as I can tell, the little holes in the perfboard cause the molten ABS to flow into them and hence achieve a mechanical interlock, way better than counting on the strong force interaction or something with a smooth tape. The Up came with 3 pieces of 2mm-space perfboard. I’m tempted to go buy a 6 x 8 panel from Radioshack and check out how it works with our Replicator.

I did a little more research into it and found that perfboard is now a common build surface, especially in conjunction with “ABS juice” that is made of ABS bits dissolved in acetone and painted on the platform.

The more you know…

After experimenting with the Up, I was determined to tune our Replicator to achieve similar qualities. Most of all, I was out to play with the support generation to see if I can achieve a less tenaciously integrated support lattice. I had been opposed to messing with before since technically it’s not “my” Replicator, but belongs to our research group, but I have literally not seen anyone else use it except me, so who’s gonna complain!?

I began by turning down the support flow rate ratio in Skeinforge way down. I had noticed before that the support material was almost as thick as my part lines, which seemed unnecessary. Next, I increased the density of the interface layers (which seems to drive the density of the support layers) so there was more ‘support resolution’. This did involve figuring out a better system so I could get the raft off the part easier (the denser interface layers appeared to want to stick to the part more than anything else). One more parameter I messed with was turning up the “support gap” ratio, which caused the lattice to be spaced further away – this was increased from its native 0.005 (meaning pretty much touching) to as far as 0.1.

I tested these settings by printing a few overhang dongles using full support and rafts, then when I thought I was at a good location, by test printing a difficult object which required full supports: this figurine on Thingiverse.

I think it turned out pretty damn great. Full disclosure: I tried this on the Up! and it got about 3/4 of the way up before the wiggling of the build plate caused the nozzle to bump the whole print off the machine. Oops. That’s what you get for being non-gantry, I guess.

Chunking off the support was pretty easy, but there were definitely lots of areas where I had to knife pretty hard. It looks like I’m the first person on Thingiverse to even try this print, too.

Additionally, one thing I noticed was that the long runs of very thin support lattice (seen in the first picture of the print) tended to warp and buckle much easier than a thin walled part would, probably because the flow rate is modified so much. On smaller prints it was okay, but I’ve definitely had support detatch from itself and curl up before. Once that happens (it seemed to happen at the base of the model), it is generally very hard for it to pick itself up again.

So I decided to try turning on the “crosshatch” option, which normally in RepG makes a pretty damn solid lattice that is utterly impossible to do anything with, but turning the flow rate down even further. The result is what I will call “point cloud” support. The string of plastic breaks between intersections (or leaves very very fine threads) and basically forms a coarse-, open cell, layer-by-layer deposited foam:

 

The “point cloud” is supported by the interaction of all those fine drool threads  and is remarkably solid if you push on it, but it falls away in huge chunks and the remainder is easier to scrape off. Still not Up! class, but a pretty awesome departure away from having to chisel your part out of its own pupa.

 

I next tried this method on the ultimate test: something I 3d scanned, so is not going to be remotely clean or easy anywhere.

 

The model in question is a Hatsune Miku mini-Nendoroid figure that I own. Now, if you know me, you know that just about the only thing I can be considered a ‘fan’ of is Miku and the Vocaloid media franchise and user community. It’s difficult to explain what it is without sounding like an internet startup guy, hipster and open-source advocate at the same time. In short it’s crowdsourced user-supported synthesized music you’ve never heard of.

Hey, when did I get a 3D scanner?!

It’s not mine, per se, but the IDC lab space has been getting some new toys since the last semester, partially in support of MAS.863, the renowned MIT Media Lab class that teaches fabrication and design skills (which Mechanical Engineering doesn’t have an equal to, by the way). This NextEngine triangulating laser scanner is one of them.

Since this was pretty much my first stab at 3D scanning, I neglected to take more than a few orientation scans (which meant the model had a ton of uncloseable holes in it) and then tried to save it at full resolution into an STL. The result was a 130 megabyte STL file that nothing could open or slice. I had to go back and greatly simplify the polygon count in order for ReplicatorG to even think about working with it.

While the STL just had too many gaps and errors for Replicator to generate a successful tool path (there’s some places that are just totally missing or filled with garbage), the “point cloud” support worked as intended. It looks really messy and disgusting on the outside, but the interior is a regular grid of very fine blobs and lines.

Since the whole point of this exercise is really just to get me a Miku figure clone, I tried it on the venerable Up. It handled the errorful STL wonderfully, though it pointed out to me where each and every one of the missing faces was. This was once again an overnight job…

Miku ended up being 4 discrete solids because of the holes in my model – the scanner couldn’t really capture the detail of the hair joint in the orientations I had it, so the point/mesh cleanup routine chopped them off. And no matter how removable the Up support is, it was still made out of the same ABS and so I had to cut part of her loop antenna structure off to remove the internal support, then reglue it back on.

Her legs are also… uhh, detachable?

But some hot glue fixes both problems.

I’m going to sacrifice this figure by supergluing the joints together so it can stay in one pose, long enough for me to scan it from every orientation. Then maybe I can get a higher resolution and fully one-shot printable model up on Thingiverse.

The bigger lesson here, though, is that I really like the “point cloud” support method. I’ve made so many changes to my Skeinforge settings that it’s not really worth trying to narrate them all here. So I’m just going to upload my slicing settings here (stuff the whole folder into your .replicatorg/sf_50_profiles directory and it should automatically recognize from within Skeinforge.

I’m actually kind of serious about trying an Uplicator hybrid. Pretty much all 3D printers are just a few steppers and a heater or two, so I don’t see much difficulty. They even sell the control board for the Up, but sell the CPU separately…for one hell of a sum. I wonder if that’s just an ATMega chip on a breakout board.

The only issue I see right now is that the Up homes differently than the Replicator – the former homes at “Z maximum” and the latter at Z minimum, necessitating different limit switch placement. In the mean time, Up!

but there’s a catch

With two competent hobby-class 3D printers sitting next to me, there’s something that has been a little forgotten which I will now finally decommission.

Poor Make-a-Bot.

The last time I turned this thing on was in late March some time. Ever since then, it’s been sitting quietly on a table, gathering MITERS grunge. The hardware, Makerbot’s Gen3 boards, and the extruder (a stepper chopped MK5), are generations behind. It was really never meant to be a 3D printer – too beefy and solid, but with my extra-stiff axes and much larger stepper motors I could still hold good resolution even at moderate (50-60mm/s) speeds. It’s really better off as a PCB router or very small mill.

Make-a-Bot isn’t being dismantled. Instead,

I’ve sold it to a hopefully loving new home that will turn it into something else awesome. Bye Make-a-Bot :(