pankov

I thought about this too but on all BW3 devices I have this function disabled so I presume it shouldn't be the cause of the issue ... or can I be wrong here?

Great, now it worked and here is the ticket number: 13844 May be you should tell the person responsible for the website to remove the non-working web page because it definitely causes confusion and misleads the customers that they'll get support.

Good question ... but how would I know that? I never did receive any response or email from support (it was just a "Thanks for contacting us" on the web page itself) and since I wasn't sure I should have received something I never thought to ask again. Should I have received anything on my mail when I posted the issue on the BuWizz dedicated support page? btw how is https://buwizz.com/contact-2/ different from https://buwizz.com/contact-support/ and should I have used the first one instead of the second one that you posted about here?

@Zerobricks, sorry to bother you again with this but is there any chance you can push support to respond? It's been around two weeks since I sent the support ticket and I still don't have any response. Also could it be that your system didn't even store the support request?

@Zerobricks, Any news on the app update that will include the option to the BuWizz3 in deep sleep mode? Or on how exactly we can do the same ourselves via the options in nRF? And finally - does anyone know how to send a ticket to BuWizz support?

I'm a bit ashamed to admit it but how do I send a support ticket?

@imurvai, are you aware of the 0xA1 Activate shelf mode command for the BuWizz 3 controller mentioned here Is there any chance you can add an option to invoke/enable it in BrickController2?

@Zerobricks, Is that BLE function ... and others ... publicly documented somewhere? I tried nRF bit to be honest I got a bit lost there. Can you help me a bit? Here is a screenshot from the app with all available functions. Is the shelf mode one at all visible? For example I tried changing the name of the device via 0x2A00 and despite nRF showing success in writing the value the BuWizz app kept on showing the old one... Does anyone have any idea what I might be doing wrong?

I wish you speedy recovery and hoping that everything is and will be fine. Is there any chance we can get this information from somewhere else? Do you know if the official support can/will be willing to help if I contact them? hmm ... this sounds interesting. To be honest I've never heard of such a thing but I'm in no way expert on the subject so might definitely be a possibility.

Sadly I think you misunderstood my post. It's only the brand new (untouched) BuWizz 3.0 Pro that I bought an year ago and never had the chance to even turn on once that started working after "waking it up" by plugging in the charger. The other two BW3.0 simply don't work which made me believe that there is a "hidden" storage state that BuWizz/Fortonik is using for shipping their products which successfully preserves the batteries for long periods. Btw I also have one BuWizz 2.0 that was left in this semi-charged state as the two failed BW3.0s at exactly the same time more than 6 months ago and it is working just fine - it turns on and holds charge without any issues ... so it must be something in the BW3s that's different. @Zerobricks, from your knowledge and experience is there anything we can do to stop this depleting of the batteries of the BW3.0 bricks in the "off" state? Is there any secret command/combination that we can put them in "deep-off" state?

@Toastie, thanks for the link and the reasonable explanation what could be causing the depleting of the batteries and the link to the possible revival procedure for LiPo batteries. It all makes a lot of sense now that you've laid it out like that and you got me thinking on how exactly are these BuWizzes stored originally ... or shipped in general ... because I had just opened a brand new one bought almost an year ago that I never managed to finish the build I bought it for and it behaved a bit differently. I couldn't turn it on using the button ... so obviously the controller inside wasn't listening to it ... and only when I plugged in the charger it blinked and was brought back to life. Interestingly it was almost fully charged - the status leds were blinking green and after a very short charging cycle it was fully charged. So somehow this BuWizz was put in some kind of storage state where it wouldn't kill its battery. Does anyone know how this can be achieved? Going back on the topic of reviving the dead batteries I was wondering if someone knows the pinout of the breakout cable of the battery? There are six cables (3 red and 3 black) which I can only presume are divided in 4 that belong to the balance port (after all it's a 3s battery) and 2 for the main current ... but having them all at the same gauge/thickness makes me doubt that logic so I'd be glad if someone can shed some light on that.

Hi I've purchased 4 BuWizz controllers in the last couple of years and after the initial excitement lately I haven't been able to use them and was surprised to find 2 of them dead ... and seemingly unrevivable (not turning on and after attaching to the charger I get the spinning red pattern on all ports). I did carefully leave them a few months ago in neither fully charger nor depleted state (battery status showed medium) which is similar to the storage state for all other lipo batteries I use for dedicated RC (non-Lego) models and was wondering what I could have done wrong here. Is is possible that there is phantom drainage of the battery from controller itself? Is there a dedicated "storage" mode that I can active somehow to preserve the batteries better? ... and finally - what are my options for changing the batteries? Did someone manage to find ones that fit somewhere online? I still haven't contacted Fortonik/BuWizz themselves but I'm afraid what their answer might be so what's the community advice on this matter - should I try this or don't even bother?

Aurorasaurus, Can you share which no OG Lego servos with proportional control are you referring to? Any available right now?

@Zerobricks or someone else, did you manage to replicate/confirm these or is it something that I'm doing wrong on my end?

I just found out that there's already such an option and together with the controls opacity configuration it's almost perfect 😊