aFrInaTi0n

Yeeeaaaah, maybe - but I am curious of the outcome of it. Things have to be tested, otherwise we will never know... so please go on :D

Ah ok, then sorry - thought the 1-directional clutching with allowing for free spin would be enough already. But you want to have motors running a main crankshaft for moving the pistons and from that allowing with some kind of rpm-limit driven clutch to move the real drivedrain, if I got it correctly?

@piterx's freespin is smaller and may be helpful here..

"Supply and demand" I guess... unfortunately I can't offer alternatives..

People will kill me for that pin-torturing, which is needed at the front mounting of the wheel to the fork.. Maybe this will be a chance or singularity of all different interest fields and brick people to unite and hunt me down.

Update on @amorti's RC Boxer Sports Motorcycle: Short footage of the first testdrive with working active steering: 🏍🔥

Nice gearbox! Chainlinks can handle more torque when put on inside out. Can be observed here:

Unfortunately not had any time to test those and create some good footage - I hope for being able to do so this or next weekend. Sorry for lagging behind with that..

From the Buwizz mail, the updated UserGuide in Version 1.9 as a PDF: https://buwizz.com/UserGuide_1_9.pdf

Good luck then - what you could also do is opening the case and disconnecting the battery's connector from the PCB socket. But to be clear: with doing so YOU WILL VOID ANY WARRANTY! I just want to mention the possibiliy that there is a plugable connector for the batt of the Buwizz 3 (not sure about the Buwizz 2!).. So please really consider this only if you have the skills to not screw it somehow up and then blame the vendor or me!

Please read the last two pages of this thread, then you may get a clue how to get into the beta program to have a possible long-term fix & also you can reply to Zerobricks, as he asked if their fix is working out for ppl like you and me.. Generally for me it helped to "reset" the buwizz into a useable state by just putting it onto a charger - sometimes it helps for the fast blinking mode to stop.. some times not.

Feedback regarding current limiters: I only had one occurance with a very light motorcycle model with the new beta, so insights may not be that helpful - but the Buwizz operated totally stable over the whole time and there wasn't any recognizable effect like the model starting with some delay or something.

@Toastie you got me wrong. Expert mode and the BT conn info I see as two different things. the conn info shall just be an informative one, reading out the bt functionality of the phone (highest supported bt protocol-version). Without such informative box the only feedback for range issues one may get is "depends on the phone" - which is a very helpful statement getting more details about the 60m range claim being false and what the real limit of the product is..

I am with @amorti in regard of ease-to-use of the product in the default state. But also on the other hand I would like to have more options in kind of an "expert mode" which would allow more detailed configuration for the users who need / want it. As complaining is easy, at least some idea to have it intuitive but maybe working with the calibration for the different types of motors: Give the possibility to select the type of PWM motor in the centered steering module for the calibration and maybe general output to be adjusted to the fitting values for the selected type. Also regard the BT upgrade: Still have a Samsung S20 FE with BT5 stack - so as already pointed out, it would be a nice to have feature to somehow get the information about the connection state between Buwizz and the phone.

Zero, I think nobody is mad at you personally, more like at the vendor Buwizz I reckon. I would hope for at least some good default values for the different PWM motors setups possible with Buwizz.. like "for the angular thingies, this and that needs to be set to x, y, z". Do they have the angulars available at Buwizz HQ for further testing?

Also tested again, outcome is: For me the medium angular motor gets some voltage applied (one can hear the motor do some sounds) but not moving at all at several tries. Then it tells after some time it did its calibration - what it didn't. I can create combined footage of screen recording + the Buwizz being recorded, if helpful.. Edit: @amorti Try to increase the "Centering PVM power" to 80% -> helped out for me. Edit2: Only the calibration seems to work - partially, as the center position is not being hit afterwards... :D & also no steering function in the real controls after "successful" calibration. Edit3: Starting over with a clean and fresh profile helped.. ✔

Thanks for the fast reply to us from within your free time & a happy Easter! I will retry with the angular with a limit set for both sides and report back / edit my above post.

Another question for Zero, if he can answer from his alpha testing experiences: Is the new BT stack giving some additional meters in the total range? I think I may test that this evening for myself.

Nothing there for you? On Android?

App Version on Beta is 3.0.7, Nordic Firmware shall than be updated to version 3.22.

Beta Update is available from the Playstore since this morning, changes are: Observations so far: - 🟨 1st Firmware Update failed on both Buwizz, second attempt with (shutting down and) restarting the App + the Buwizz unit helped - 2nd attempt went through fine. - 🟨 no mixed firmware mode: New App version is forcing updates of any Buwizz with old firmware, before you can use it - 🟩 Profiles are being kept - 🟥 Central Steering: First test with the medium angular motor wasn't working out. It did somehow start to calibrate, but not sure if no "endpoint" as blocker is needed to work correctly - 🟨 Current Limits: For the PU Ports the warning comes with values greater than 2.0 A, for the PF Ports it warns already from the "1.0 A" value - 🟨 UI: Bug of the Currents / Voltage - went away after some reconnects / restarts of the profile (or is 17.6 Volts the new ludicrous mode for BW3? 😂)

@Jundis I think the more and faster we test the update, the earlier.. I would guess the end of april is aimed for the prod version, so ~3 weeks of Beta testing if everything goes well. Its very easy to join, just go to the google playstore and navigate to the Buwizz App, there should be a button to participate at the beta.

Little update with Mk 4.0 and Mk 4.1 of the RC BATPOD: Huge thanks for @efferman and @Jundis for giving me a tiny and sturdy af gearless 1/2 reduction for the servo to do only 45° rotation of the Buwizz as leaning-weight at max! ♥ Unfortunately the weight rolling in instead of being shifting outwards the CoG wasn't as effectful as initially thought, but has been identified to a slightly missalignment from the chassis due to redesign, never the less a nice viewing angle with an offset to the left for the camera (so this is the reason for the left-heavy turning) for the MK 4.0: Finally the Mk 4.1 Testdrive with already better steering / effect of shifting the CoG through some minor adjustments in the geometry of the chassis. And a wonderful Mk 4.1 crash ( Buwizz):

@Jundis the "maybe end of April" Update may include it or not, they didn't state any clearer.. Edit: Another of those "lost range in under 25 meters" scenarios I am experiencing repetitivly... 🤬

Yeah, I had a call on our companies on-call-duty and realized inbetween - but couldnt immedialely edit.. Thanks, this is much more that I could have asked already haha!! ♥ so thanks to both of you. Edit: I forgot about the generic build help thread... next time I hopefully will post there... *note to myself..