Motors tab just glitched out across the board

[Redazu]

I'm using the Piko Blx and this is like my 7th time building a micro with one of these and I always do the dshot mod to it by wiring the ppm to motor 4 pad and then entering the cli commands to remap it. Never had a problem before but all the other times, all I typed was..


resource ppm none
resource motor 1 A07
save

This time however I went to a different place to copy paste it from and they had

resource ppm none
resource motor 1 A07
resource motor 5 none
resource motor 6 none
resource motor 7 none
resource motor 8 none
save

Which I figured ehh ok not like I'm using those motors anyway so won't matter right?  Wrong I guess because I pasted that and hit enter and after the reboot the motors tab is showing 0 on the first 4 motors instead of 1000 like usual and the "I accept blah blah" button is always already slide to enabled even after rebooting. It won't let me move any of the motor sliders at all no matter what. I tried reflashing to multiple different versions with full chip erase and nothing would change it. Sometimes it would show all 4 motors completely full orange like they were maxed out or something but still showing 0 in the middle.

Now here's where I'm just like... mind blown...   I figured ok.. maybe i screwed this board up, maybe a driver on the computer messed up I mean anything no telling... So... I got on another computer...my laptop that I use occasionally to change settings on the go. I got another usb cable, I got another flight controller board that I know works fine, and hooked it all up.. boom.. same shit.... I even got my tinywhoop out and hooked it up and SAME THING! WTF? I know my tinywhoop works perfect, I was flying it yesterday and haven't touched it. I tried hooking the battery up on tinywhoop and it INSTANTLY went full blast. I literally don't know wtf is going on. I have betaflight 3.1.2 configurator on both computers. The motors tab and motors were working just fine right before I did the CLI commands and rebooted ( except motor #4 of course cause dshot was enabled ). Was there some kind of configurator update that went out and got installed in the middle of that? I even tried cleanflight and get the same thing on everything...

[fftunes]

Betaflight configurator 3.1.2 was pushed on chrome store by mistake - it's not working with earlier versions of firmwares (or let's say actual versions, since there are no releases at all for 3.2 yet).

You can download configurator 3.1.1 from github, and apparently there's also a configurator version 3.1.3 already which probably contains fixes for firmwares 3.1.x.

You'll have to manually install them as chrome extension (download/unpack, then add them in chrome). Here's the download page: https://github.com/betaflight/betaflight...r/releases

[Redazu]

I freaking love you... Thanks!! This was driving me insane was up all night xD