Doua

Definitely do not use the 3.3v output from the microcontroller to power the servos. They will take in way more amps than the rated current on the pico output (you should be able to find the rated current on the pico spec sheet, usually its 20-100mA while servos can take 100s of mA each). You need to run the raw voltage from your batteries to a rail that can power your pico and your servos separately (in parallel).

Hi, I've built this today, it's really awesome! Plenty of power in low and enough speed in high. It's the most capable and robust built off-roader I've built for sure. Thanks for the instructions and keep the models coming, you rock at Technic :D (Don't have the tapered panels for doors, I'll need to fix something up to protect the battery and motors) I think this is around my favourite scale for Lego RC cars, light so it's nimble and doesn't stress parts too much, 2 Buwizz motors for plenty of power at this weight and again, not too much stress on parts. And low part count makes it a good "one evening build" and also easy to disassemble with no remorse :D The weakest point I found was the vertical bracing of the steering (the two 6L thin liftarms placed vertically). They tended to pop out quite easily in a front collision :x, but also looks like the steering motor was able to push it loose under heavy steering and acceleration. I've reduced the pwm of the steering motor a bit which helps, but I've also reinforced with a T piece in front of everything, which also serves as a central bumper of sorts. The steering is strong and responsive, no issues at all otherwise. Instructions are very good and clear. A couple notes below for "easy wins" if you ever care to change them: Step 7: should be viewed from the other side (rotated 180 deg) Step 10: the black pin should be placed at an earlier or later step (eg step 16) (can't see placement on step 10) Step 11: should be viewed from the other side Thanks again!

I can't help but see similarities between Lego's marketing/target audience shift in the past 10/15 years, and that of Magic the Gathering (MtG). MtG releases sets of cards a few times a year. That used to be it until a couple years ago. Now the number of sets they release has exploded in number, a ton of MtG fans are complaining that they now can't "keep up" and get all the releases, from my experience it's absolutely true. There's now licensed sets in MtG, collectors editions etc... And a ton more cards released each year. It looks like MtG has expanded their target audience to now include, say, LOTR fans, rare cards collectors, card art fans, etc etc... They even state it officially with things like "[this particular set/product] is not made for [this audience]. To me it seems like Lego is doing similar, the number of sets per year has grown a fair bit in the last 15 years or so, and now they target a whole bunch of audiences from young kids to expensive display pieces collectors, specific license collectors etc. The similarities between Lego and MtG shifts in production/releases is striking (granted I only have come back to Lego recently).

OK thanks, so you set the power curve so the motor stalls once the gear is in? Thanks for the quick reply!

Question about the gearbox mechanism. From what I understand the WeDo motor doesn't have encoder. And from what I could see in Studio the gearbox doesn't use any kind of clutch. Do you operate the gearbox "manually" that is, run/stop the motor manually once the gear changed? Or can the buwizz app gearbox module operate with "dumb" motors? Asking because this motor is actually quite expensive here in Australia (40-60$!) and I'm very tempted to go 3rd party for these... An M motor with PU connection would be useful to have either way. Thanks!

Thanks for this, it looks awesome and very sturdy! I will definitely build this in the future; need to get my hands on a second hand Zetros since it seems to have most of the rarer parts needed (hubs, tyres, Wedo motor, some gearbox parts). I have created the parts list on rebrickable which I'm happy to share: https://rebrickable.com/users/Doua/lists/250912/ I have manually added : - 4x red 6.5 shocks hard - 3x 20 tooth bevelled tan gears - 1x steering yoke List doesn't include the Buwizz 3.0 or the 2x Buwizz motors. It may be easier to build in black since the red tapered panels for the doors are quite rare in red; the flat panels are also a bit more common in black.

Hi all, I'm having what I think is a firmware issue with Buwizz 3. I have messaged support, but figured I could also ask here. I received my Buwizz 3 yesterday, let it charge and tested it by swapping the Control+ battery box of my 42099. Everything worked perfectly, easy to set up controls etc. All super. Knowing there's a beta version of the app that allows you to use Xbox controllers, this morning I opted in to the beta in the Play store, downloaded and installed the beta version on the app. On starting the app it told me the Buwizz unit needed a firmware update, fair enough. The update failed a couple times. I restarted the Buwizz and app to try and fix it as suggested in the app, to no avail. After a couple tries, the app was able to see and connect to the Buwizz; however, I cannot run the motors anymore or do anything really (change LED colors etc.). When going into the "Manager" on the app, and selecting my Buwizz, at the bottom it shows "checking device firmware" for a long time (1 minute), then shows this: If I click "update firmware", it fails at the step where it checks Buwizz battery (saying battery is too low, and cancelling the update). If I load a profile, it does the same thing "checking device firmware" for 1-2 minutes, then shows the Buwizz connected but I cannot drive motors / change LEDs etc. To me that seems like something's wrong with the Tajnik firmware, as a result I can't read battery status, and so can't update the firmware. Nordic firmware seems fine which is why I can see and connect to the unit. Any help appreciated! EDIT: With Brickcontroller2 everything is fine, I am able to use Buwizz to control PU motors. EDIT 2: fixed it by deleting all app data and cache, uninstalling / resinstalling the app (beta version). Now everything works perfectly. Off to made cool RC lego cars now :D