I got issues with my new mobula 7 ( my first fpv drone, also my first post here as I lost my hopes to fix it by myself), It was set up at betaflight configurator, it was actually ready for arming for first time, however I left it for a while either with just 1S battery in or connected to PC usb (can’t remember) to change batteries at radio controller. I tired to bind radio again as I found out that this is not connected when I changed batteries. It was not successful, when I opened betaflight configurator I realised that I miss quite a few features I was able to see before- I am not able to calibrate accelerometer ( I can’t see actual position of drone at setup tab- this might have another explanation as I am onboard vessel which is rolling continuously a bit), at “ports” tab I can see only USB VCP, URAT1 and URAT 2 gone. Can’t see battery voltage when connected, additionally can’t bind receiver.

I was hoping to update firmware via beta-flight but there is no response from bootloader. I was trying to trigger flash on connect.

I am getting warning that my version of firmware is newer than newest betaflight release, furthermore when I am trying to get version via CLI I can find out that release of current version have tomorrow date ( more than 24h so it shouldn’t be timezone issue).

# version
# Betaflight / STM32F411 (S411) 4.3.0 Apr 15 2022 / 10:14:38 (9360ab1) MSP API: 1.44
# config: manufacturer_id: HAMO, board_name: CRAZYBEEF4FS, version: a074838b, date: 2021-06-14T21:36:54Z

Is there any hope for my drone, or I just fried electronics somehow? I also consider pushing wrong binding button ( the second button is boot). Thank you for any indication where issue can be.

From what you're saying it almost seems like it flashed and no configurations have been applied.

If it connects to Betaflight then it might be the case to reflash the appropriate firmware and loading the config file on the cli.
Is your Betaflight the on the latest version? For 4.3 it needs to be 1.8.0 (I assume it would be as its new for you, but just checking)

Have you actually tried to flash something already? If not, there are a few videos on youtube showing how to (check Joshua Bardwell and UAV Tech, to name a couple) or check Oscar Liang's site, there is a tutorial there I'm sure (also several posts here showing all the necessary steps.

If you're having trouble getting BetaFlight to recognize the board during the firmware upgrade you might need to install a driver to fix that (assuming you are using Windows). This one has worked well for me "ImpulseRC_Driver_Fixer" (don't have the link on me right now, sorry).

PS: I just recovered from a situation with my whoop as well in which I thought it was gone. The guys here helped a lot and I'm learning that a lot of configuration/firmware issues can be solved with a bit of work.

This might be it, my betaflight is below 1.8.0 as manufacturer manual said it should be 1.4 and not newer, I believe due to some bug which was fixed later. Thank you a lot for your reply, I will try new version in couple hours

No worries dude, hope it helps, if it doesn't be sure to post back with more details so that the community can help you better.

First thing.  Whenever your drone is sat plugged in to a LiPo (and not flying) and/or USB, point a fan at it to simulate the props spinning, to keep the electronics cool.  Things can burn out easily, especially the VTX.  Another thing is to watch your LiPo voltage if it's plugged in for a while.  Whoops seem to eat power and your battery can be at dangerous levels fairly quickly, this won't harm the whoop, but it will harm your battery.

Calibration of the accelerometer.  The only idea I have, since you are on a boat, make a platform and tie it to the ceiling with rope and with a weight below the platform.  The Platform should remain flat no matter how much the boat rocks.  This isn't ideal, but it might work.  In the same vein as a gyroscope or hammock.  I don't think anyone envisaged someone doing drone calibration on a constantly moving object, so YMMV.

Before you do any flashing you need to do a couple of steps in Betaflight CLI.  Follow these steps (posted by IFly4rotors).

IFly4rotors Wrote:Here is what I would suggest and I do this for EVERY new quad or new FC board that I buy.
In fact, I do these things BEFORE a battery is ever connected. This is just a good "safety"
measure and ensures that I can recover should something go sideways.

Make sure that you have the Betaflight configurator installed on a computer (PC) first:

1) Open the Betaflight configurator on the PC.
2) Plug a USB cable {must be a DATA cable} into the quad and into the PC.
3) Click "Connect" in the Configurator.
4) Open the CLI tab.

             For each command:
             CLEAR the screen.
             Type the command press [Enter].
             Save to File {I generally leave the name, but add to the end of it}.

6) DUMP   { I would do this even though it looks like you have the DUMP file}
7) DUMP ALL
8) DIFF
9) DIFF ALL
10) RESOURCE
11) RESOURCE SHOW ALL

Just me , but I also take screen prints of the important stuff just so
that I know what things were from the factory. I like having the visual.

Now, if all of this sounds like "Overkill"...well, maybe it is, but I have all sorts of
backups and information just in case something should go sideways with the
firmware for any reason.

With all of this information, I can recover should I mess something up.  

(14-Jun-2022, 09:41 PM)cst3x6 Wrote: No worries dude, hope it helps, if it doesn't be sure to post back with more details so that the community can help you better.

So, this actually worked, drone beeps at me again, still a lot to configure before first flight but this is huge progress. I was quite sure that drone died

Thanks a lot

(14-Jun-2022, 11:28 PM)Pathfinder075 Wrote: First thing.  Whenever your drone is sat plugged in to a LiPo (and not flying) and/or USB, point a fan at it to simulate the props spinning, to keep the electronics cool.  Things can burn out easily, especially the VTX.  Another thing is to watch your LiPo voltage if it's plugged in for a while.  Whoops seem to eat power and your battery can be at dangerous levels fairly quickly, this won't harm the whoop, but it will harm your battery.

Calibration of the accelerometer.  The only idea I have, since you are on a boat, make a platform and tie it to the ceiling with rope and with a weight below the platform.  The Platform should remain flat no matter how much the boat rocks.  This isn't ideal, but it might work.  In the same vein as a gyroscope or hammock.  I don't think anyone envisaged someone doing drone calibration on a constantly moving object, so YMMV.

Before you do any flashing you need to do a couple of steps in Betaflight CLI.  Follow these steps (posted by IFly4rotors).

So I as understand, the battery gets connected only in order to fly, and we depend on usb 5v when setting up? Does it even make difference? The manufacturer documentation is basically few screenshots from betaflight

(15-Jun-2022, 09:50 AM)Patryk Wrote: So, this actually worked, drone beeps at me again, still a lot to configure before first flight but this is huge progress. I was quite sure that drone died

Thanks a lot

Great, happy this got you in the right direction.

Quote:So I as understand, the battery gets connected only in order to fly, and we depend on usb 5v when setting up? Does it even make difference? The manufacturer documentation is basically few screenshots from betaflight

From the top of my head, the only time you need to plug in a battery when setting things up is for motor related stuff and to load fonts to the vtx from the osd tab.  Flashing firmware and configurations on betaflight can all be done with just the usb cable plugged in..

Additionally, if you didn't backup the original settings at the CLI page, you can probably find that on the manufacturers page for said model. Download that and apply it after flashing the new firmware (make sure to download the CLI file that matches your model, this is very important). Once this is done, do any additional customization you might want and save a new diff all from CLI (Its good practice to always save one before doing any changes and one after changes are made and you're happy with it)

As an update, seems like everything works smooth when both FC and betaflight are updated to newest version, I got back my gyro and basically all lost tabs.

There is new problems as the motors doesn't behave as they are supposed, I am able to arm drone and I was trying to move the throttle slightly ( as I would at drone simliator), but not all of motors will behave the same way- drone will flip upside down.

So I tested all of them on bench, seems that all my engines are in right position ( as betaflight numbers), are installed in right direction, ESC motor protocol as described in manual ( DSHOT600). I have flashed new firmware via Blhelisuite ( S-H-50), it seems to me that this might be a problem, seems to me that drone (and especially manual) was on the shelf for a while and all these manuals are a bit outdated.

Trying to change the ESC firmware was precisely what messed up my whoop the other day. Had to go back to the stock firmware to get everything back to normal.

Assuming there are no problems with the firmware and your ESC, make sure the orientation of the propellers match the orientation the motor is set to on betaflight. From what you described its seems that this could be the problem.

(16-Jun-2022, 12:49 PM)cst3x6 Wrote: Trying to change the ESC firmware was precisely what messed up my whoop the other day.  Had to go back to the stock firmware to get everything back to normal.

Assuming there are no problems with the firmware and your ESC, make sure the orientation of the propellers match the orientation the motor is set to on betaflight.  From what you described its seems that this could be the problem.

Seems to be something different, orientation and motors rotation both good. At this point from betaflight I can test it well, then I will get some power on all motors but it will flip like one motor is not giving same RPM as others, that would be bad as I won't be able to get any spare parts in weeks.

(16-Jun-2022, 02:16 PM)Patryk Wrote: Seems to be something different, orientation and motors rotation both good. At this point from betaflight I can test it well, then I will get some power on all motors but it will flip like one motor is not giving same RPM as others, that would be bad as I won't be able to get any spare parts in weeks.

Could you maybe post screenshots of the motor tab from betaflight and from the settings on BLHeliSuite or esc configurator ?

I was having the same issue you mention, one of the motors wasn't spinning, but it was all because of the wrong ESC firmware I had installed.  Apart from this, some of the power setting in blheli might need to be changed..

Don't order anything yet as it is likely a configuration/firmware issue..

Looking at the the specs for mobula 7 on happymodel page (https://www.happymodel.cn/index.php/2022...oop-drone/) I get this on the esc:
Factory firmware: Z_H_30_REV16_7.HEX
Default protocol: DSHOT300
Support Bluejay firmware
When use Blujay firmware with 48khz, should set startup power to 1100/1200

The firmware you mentioned earlier is not the same. So perhaps try to use the same one as mentioned on factory settings and go from there..

So basically this is my setup, the happymodel website states 20000kv motors however I have kv16000, nevertheless that seems to be right firmware.
I am trying to get bluejay firmware which is bit over 100mb , but that seems difficult to my unstable sattelite internet at the moment, I will try with better weather/coverage

On Betaflight click on the "motor direction is reversed" switch and try lifting again..

Also, check the firmware I mentioned earlier in case it doesn't.