Posts: 12 Threads: 2 Likes Received: 1 in 1 posts Likes Given: 1 Joined: Nov 2022 Reputation: 0 I have MAMBA F405 MINI DJI Flight Controller and DJI O3 unit. Should be plug and play.. I did connect the unit and I got DJI remote working but not the OSD.. ![[Image: 52534212933_aa22ffa4ed_k.jpg]](https://live.staticflickr.com/65535/52534212933_aa22ffa4ed_k.jpg) So I have decided to update betaflight to the latest 4.3.2 and saved only DIFF before doing that. Code: #
# diff
# version
# Betaflight / MAMBAF405US (MBF4) 4.1.2 Dec 28 2019 / 15:49:00 (89051e256) MSP API: 1.42
# start the command batch
batch start
board_name FURYF4OSD
# name: 03
# feature
feature -AIRMODE
feature LED_STRIP
# beacon
beacon RX_LOST
beacon RX_SET
# led
led 0 14,12::C:1
led 1 15,12::C:1
led 2 14,13::C:1
led 3 15,13::C:1
led 4 14,14::C:1
led 5 15,14::C:1
led 6 14,15::C:1
led 7 15,15::C:1
# aux
aux 0 0 3 1700 2100 0 0
aux 1 1 0 900 1350 0 0
aux 2 2 0 1300 1700 0 0
aux 3 13 1 1700 2100 0 0
aux 4 28 0 1300 2100 0 0
aux 5 35 1 900 1300 0 0
# master
set acc_calibration = 26,36,-81
set motor_pwm_protocol = DSHOT600
set failsafe_delay = 9
set small_angle = 90
set osd_flymode_pos = 2114
set osd_warnings_pos = 14762
set name = 03
profile 0
rateprofile 0
# end the command batch
batch end
#
Well, the update erased all soft serial config and diff did not save softserial config! After update it looks like this. Code: # resource
resource BEEPER 1 A08
resource MOTOR 1 A03
resource MOTOR 2 B00
resource MOTOR 3 B01
resource MOTOR 4 A02
resource PPM 1 C09
resource LED_STRIP 1 A00
resource SERIAL_TX 1 A09
resource SERIAL_TX 3 B10
resource SERIAL_TX 6 C06
resource SERIAL_RX 1 A10
resource SERIAL_RX 3 B11
resource SERIAL_RX 6 C07
resource INVERTER 1 C00
resource I2C_SCL 1 B06
resource I2C_SDA 1 B07
resource LED 1 B05
resource LED 2 B04
resource SPI_SCK 1 A05
resource SPI_SCK 2 B13
resource SPI_SCK 3 C10
resource SPI_MISO 1 A06
resource SPI_MISO 2 B14
resource SPI_MISO 3 C11
resource SPI_MOSI 1 A07
resource SPI_MOSI 2 B15
resource SPI_MOSI 3 C12
resource ESCSERIAL 1 C09
resource CAMERA_CONTROL 1 B09
resource ADC_BATT 1 C01
resource ADC_RSSI 1 C02
resource ADC_CURR 1 C03
resource FLASH_CS 1 B03
resource OSD_CS 1 B12
resource GYRO_EXTI 1 C04
resource GYRO_CS 1 A04
resource USB_DETECT 1 C05
So I'm looking to find the default CLI dump for the Mamba F405 DJI Mini or resource map. All I could find is just diagram with no resource names on the Diatone's website. ![[Image: 52534212963_1cf42bc834_o.jpg]](https://live.staticflickr.com/65535/52534212963_1cf42bc834_o.jpg) Though the diagram might explain why the OSD was not working.. it has been set on UART4 by default but probably should have been on UART2 according to the diagram. Anyway, there is no UART 2 or UART 4 after the update.. as both there soft serials. So I'm looking how to set those ports back. The whole reason I put this controller is the plug and play DJI connector. ![[-]](https://intofpv.com/images/collapse.png) • Posts: 120 Threads: 17 Likes Received: 58 in 41 posts Likes Given: 20 Joined: Oct 2022 Reputation: 2 I don't think you need softserial with the DJI plug n play. • Posts: 12 Threads: 2 Likes Received: 1 in 1 posts Likes Given: 1 Joined: Nov 2022 Reputation: 0 30-Nov-2022, 04:59 PM (This post was last modified: 30-Nov-2022, 05:00 PM by Original.) (30-Nov-2022, 04:41 PM)Fiveflat Wrote: I don't think you need softserial with the DJI plug n play. Well, this is how it looks after the update. ![[Image: 52533749856_5a68fdbffa_h.jpg]](https://live.staticflickr.com/65535/52533749856_5a68fdbffa_h.jpg) No UART2 or UART4.. and according to the diagram DJI is connected to the UART2. Or how it was set before the update UART4. Again, both UARTs are missing now. Even UART1 does not seem to work anymore. Even the DJI remote has been working on UART 1 before the update. All receiver settings are exactly the same. • Posts: 120 Threads: 17 Likes Received: 58 in 41 posts Likes Given: 20 Joined: Oct 2022 Reputation: 2 30-Nov-2022, 05:38 PM (This post was last modified: 30-Nov-2022, 05:40 PM by Fiveflat.) According to your photo your firmware is 4.1.4 (not 4.3.2) Try to roll back firmware to 4.1.2 as shown in your first post then? Diatone has their firware and config files for download on their support page also. Here is the .rar file Posts: 12 Threads: 2 Likes Received: 1 in 1 posts Likes Given: 1 Joined: Nov 2022 Reputation: 0 (30-Nov-2022, 05:38 PM)Fiveflat Wrote: According to your photo your firmware is 4.1.4 (not 4.3.2)
Try to roll back firmware to 4.1.2 as shown in your first post then?
Diatone has their firware and config files for download on their support page also. Here is the .rar file Thanks! I have found the issue. Betaflight detects this FC as FuryF4OSD.. but OSD is the analog version. I just needed to reflash the correct target for DJI version MambaF405US and all UART ports are back!  I have switched DJI to UART2 and OSD is working on the latest Betaflight too ![[Image: 52533400292_aac41a8b1c_h.jpg]](https://live.staticflickr.com/65535/52533400292_aac41a8b1c_h.jpg) • Posts: 12 Threads: 2 Likes Received: 1 in 1 posts Likes Given: 1 Joined: Nov 2022 Reputation: 0 My Mamba F405 DJI Mini has died in a crash.. so I've put an old Mamba F405 Mini V1 instead. I'm confused now. It's not possible to flash this board above 4.1.7? As I can't see any later FW in betaflight or Diatone website. ![[Image: 52872486673_5351c64ea3_b.jpg]](https://live.staticflickr.com/65535/52872486673_5351c64ea3_b.jpg) • Posts: 21,174 Threads: 581 Likes Received: 8,920 in 6,599 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 Make sure you are using the latest 10.9.0 version of Betaflight Configurator and then in the Firmware Flasher tab just select FURYF4OSD from the board type dropdown list and it should aultomatically pre-populate the firmware version box with 4.4.1. Then flash it as per normal. • Posts: 12 Threads: 2 Likes Received: 1 in 1 posts Likes Given: 1 Joined: Nov 2022 Reputation: 0 05-May-2023, 02:49 PM (This post was last modified: 05-May-2023, 02:57 PM by Original.) Current version on FC Code: # version
# Betaflight / FURYF4OSD (FY4O) 4.1.7 Sep 26 2020 / 16:25:01 (8acc32f41) MSP API: 1.42
Betaflight shows the latest version but it's build for different MCU. ![[Image: 52872703963_e2fb3eada3_h.jpg]](https://live.staticflickr.com/65535/52872703963_e2fb3eada3_h.jpg) And I did flash to betaflights 4.4.1 version it does not work, no gyro and etc.. so I have downloaded 4.1.7 the latest I could find on Diatones page for the correct MCU FuryF4OSD. • Posts: 21,174 Threads: 581 Likes Received: 8,920 in 6,599 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 The Diatone Mamba F405 Mini V1 FC does have an STM32F405 MCU on the board. That is why F405 is in the name of the FC. So it's the correct target.
Betaflight 4.4.x uses the new cloud build system which still has some teething problems so it might not be including the correct gyro drivers for your particular board. You can usually fix that by specifying a custom define statement for the required gyro.
With Betaflight 4.1.7 installed and the gyro confirmed to be working, run the "status" command in the CLI and post the results back here. • Posts: 12 Threads: 2 Likes Received: 1 in 1 posts Likes Given: 1 Joined: Nov 2022 Reputation: 0 05-May-2023, 09:54 PM (This post was last modified: 05-May-2023, 10:19 PM by Original.) Ok, I see, I have MPU6000. Code: # status
MCU F40X Clock=168MHz (PLLP-HSE), Vref=2.90V, Core temp=35degC
Stack size: 2048, Stack address: 0x1000fff0
Config size: 3587, Max available config: 16384
GYRO=MPU6000, ACC=MPU6000
System Uptime: 56 seconds, Current Time: 2023-05-05T20:51:38.756+00:00
CPU:9%, cycle time: 127, GYRO rate: 7874, RX rate: 33, System rate: 9
Voltage: 137 * 0.01V (0S battery - NOT PRESENT)
I2C Errors: 0
Arming disable flags: RXLOSS CLI MSP
and after flashing 4.4.1 and loading config from diatone, there are some errors in CLI. Code: # resource PPM 1 C09
###ERROR IN resource: INVALID RESOURCE NAME: 'PPM'###
# resource CAMERA_CONTROL 1 B09
###ERROR IN resource: INVALID RESOURCE NAME: 'CAMERA_CONTROL'###
# set mag_hardware = NONE
###ERROR IN set: INVALID NAME: mag_hardware = NONE###
# set baro_hardware = NONE
###ERROR IN set: INVALID NAME: baro_hardware = NONE###
# set dashboard_i2c_bus = 1
###ERROR IN set: INVALID NAME: dashboard_i2c_bus = 1###
when I have loaded my saved diff and gyro still not working Code: # status
MCU F40X Clock=168MHz (PLLP-HSE), Vref=2.95V, Core temp=43degC
Stack size: 2048, Stack address: 0x1000fff0
Configuration: CONFIGURED, size: 3626, max available: 16384
Devices detected: SPI:0, I2C:0
Gyros detected: gyro 1 locked
OSD: MSP (30 x 13)
BUILD KEY: 814cf907b3b04f00b75bab6ebfb381f6 (4.4.1)
System Uptime: 26 seconds, Current Time: 2023-05-05T21:05:50.876+00:00
CPU:0%, cycle time: 0, GYRO rate: 0, RX rate: 0, System rate: 9
Voltage: 138 * 0.01V (0S battery - NOT PRESENT)
I2C Errors: 0
FLASH: JEDEC ID=0x00ef4018 16M
Arming disable flags: NOGYRO BOOTGRACE CLI MSP
it's actually random, without changing any settings and just rebooting, sometimes gyro will work.. and sometimes it's not found. Code: #
# Building AutoComplete Cache ... Done!
#
# status
MCU F40X Clock=168MHz (PLLP-HSE), Vref=2.92V, Core temp=45degC
Stack size: 2048, Stack address: 0x1000fff0
Configuration: CONFIGURED, size: 3626, max available: 16384
Devices detected: SPI:1, I2C:0
Gyros detected: gyro 1 locked dma
GYRO=MPU6000, ACC=MPU6000
OSD: MSP (30 x 13)
BUILD KEY: 814cf907b3b04f00b75bab6ebfb381f6 (4.4.1)
System Uptime: 14 seconds, Current Time: 2023-05-05T21:15:18.736+00:00
CPU:44%, cycle time: 125, GYRO rate: 8000, RX rate: 15, System rate: 9
Voltage: 138 * 0.01V (0S battery - NOT PRESENT)
I2C Errors: 0
FLASH: JEDEC ID=0x00ef4018 16M
Arming disable flags: RXLOSS CLI MSP
• Posts: 21,174 Threads: 581 Likes Received: 8,920 in 6,599 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 The default configuration for the FURYF4OSD unified target does already have the MPU6000 specified as a custom define (see the top of the config file HERE), so the drivers for that gyro will be getting included in the cloud build firmware for that Betaflight target. Try flashing Betaflight 4.3.2 to the FC which still uses the old pre-compiled firmware files (not an on-the-fly cloud build of the firmware) and see if the gyro is always detected on every boot with that version. If it is, that then points the finger at some kind of issue/bug in Betaflight 4.4.x in which case I suggest you raise a GitHub issue for your problem using the link below so that a Betaflight developer can look into it... https://github.com/betaflight/betaflight/issues • Posts: 12 Threads: 2 Likes Received: 1 in 1 posts Likes Given: 1 Joined: Nov 2022 Reputation: 0 I have tested it flying and it works perfect every time.. so that's all I care. • Posts: 12 Threads: 2 Likes Received: 1 in 1 posts Likes Given: 1 Joined: Nov 2022 Reputation: 0 27-May-2023, 12:38 PM (This post was last modified: 27-May-2023, 02:27 PM by Original.) I'm reverting betaflight I do not want to be beta tester... The drone did arm everytime.. but I brought it for the first actual flight today. It did fly for a minute and suddenly decided to do a full throttle punch out. Armed it second time, lifted of the ground and it went to a full throttle again. It seems the fault is exactly with the FC.. Radio works fine with the other DJI O3 build. Update: yes, after downgrading to betaflight 4.2.9, it does fly normal again. And I even have a nice tune from smart35 for this version as DJI O3 works with OSD.. so literally, no point going higher. • |
