Closed Slodrein closed 1 year ago
Please try MAMBAH743
Please try
MAMBAH743
Yes, except that this is not the target that the manufacturer tells us. I don't risk having problems going through this target?
I've tried MAMBAH743 target instead of auto detected MAMBAH743_2022B and I've got vtx disabling on arm. How can I fix that?
The two targets are not interchangeable and has been added to 4.4.0 last week: https://github.com/betaflight/unified-targets/pull/981
The 4.5.0 version is not yet available.
Did you ever get the firmware? im in the same boat, shows nothing in the drop down.
@Newtothegrounds I've tried to search for old versions of firmware, but I couldn't find any. Now I'm waiting for merging this https://github.com/betaflight/betaflight/pull/12718
@Newtothegrounds I've tried to use settings from https://github.com/betaflight/unified-targets/pull/981/files after flashing 4.4.1 for MAMBAH743 and it solved my problem. Everything seems working
I have the Mamba H743 v2 dual gyro, flashed to 4.4.1 using DFU mode. Prior to the update the board had life, soon as i updated it 4.4.1 it was stone dead except some life in the 3.3v LED. I could not reconnect to BF at all, i eventually contacted Diatone and they gave me 4.3.1 and the config for that which got life back into the FC. Diatone said that there will be support for the board in BF4.5. How to true is all this as i see above some have the board working. Any help will be greatly appreciated. Is there maybe something i have missed in the whole flashing process? Many thanks in advance.
For now stay on 4.4.0 or use 4.5.0:
Many thanks for responding, i will give those a go
I you give me a support ID from 4.4.0 build I can create a 4.4.2 test build. Or click Show log and paste the URL here.
ok let me fiddle, im coming from KISS back to BF on a build, its been a few years since i last used BF. I need to find my feet Apologies:-)
The issue i hade updating to newer is the FC does not want to connect to BF again until i flash something the FC is happy with. I game to try anything to be honest, its a nice learning curve for me
Use boot button instead - or replug flight controller or restart configurator / computer.
Checkout documentation for refreshing memory Also highly recommend using nightly configurator
Id: "7a7db705-9ffd-4d11-b034-fdb09c3d01cb"
I managed to get 4.4.0 on to the FC, dead as usual but then loaded the Diff, i got a few error messages as i believe the config is from 4.3.1. This board gets quite toasty
Yeah Diatone has the 2022B in the documentation for the board.
Does the F7 vs H7 make a difference with the Hex file?
Oo - fixed: betaflight_4.4.2_STM32H743.zip
make STM32H743 EXTRA_FLAGS="-D'BOARD_NAME=MAMBAH743_2022B' -D'MANUFACTURER_ID=DIAT' -DCLOUD_BUILD -DUSE_ACC -DUSE_ACC_SPI_MPU6000 -DUSE_BARO -DUSE_BARO_DPS310 -DUSE_DSHOT -DUSE_GPS -DUSE_GPS_PLUS_CODES -DUSE_GYRO -DUSE_GYRO_SPI_MPU6000 -DUSE_ACCGYRO_BMI270 -DUSE_ACC_SPI_ICM42688P -DUSE_GYRO_SPI_ICM42688P -DUSE_FLASH -DUSE_FLASH_W25N01G -DUSE_LED_STRIP -DUSE_OSD -DUSE_OSD_HD -DUSE_OSD_SD -DUSE_VTX -DUSE_MAX7456 -DUSE_PINIO -DUSE_SERIALRX -DUSE_SERIALRX_CRSF -DUSE_TELEMETRY -DUSE_TELEMETRY_CRSF"
Haha thank you for this, i will flash it shortly
I get the above errors if you loading that config file. Im a little useless at this. It works on the bench with the errors just not sure the impact..
Just ignore them :see_no_evil: This is a local build - as cloud build would remove it afaik
I also have this H743 board. On Discord I was able to talk to another user, F_Bee, with the same Diatone H743_2022B. He was able to guide me to use the v1 configuration. As he was able to make his 7" fly with it.
Save a back up from 4.3
and then added the following command:
resource ADC_RSSI 1 NONE resource PINIO 1 C02 resource PINIO 2 C05 set pinio_config = 129,129,1,1 set pinio_box = 0,40,255,255 save and then import the 4.3 settings
There might be a change in the Gyro heading setting for BOTH gyros, just make sure it's set to the right directions
I verified that it works, as I was able to fly with my 5" Mark5
Soooo i decided to have a look at 4.5 zulu and there isn't much in the cli when running diff. Just a few commands if that's the correct term. Yet my fc is alive and working. If i run any other version the fc is dead until i load the saved diff files with tons of info and errors, how does that work and should i carry on using 4.5?
I would also like to thank all of you for jumping in and helping out. I have been away for work so now back to fiddling with this board.
I will go back to the 4.4.2 version and add the above into the cli, I'm just not sure on how to set gyro directions
"c824969b-58e9-472a-9d96-2001b5601eed" ID for log if someone wants to look. Im back on 4.4.2 as provided, i just wanted to see what 4.5 showed under config and i t was not much :-)
I will go back to the 4.4.2 version and add the above into the cli, I'm just not sure on how to set gyro directions
The gyro is in the configuration tab, under the heading Board and Sensor Alignment. You should always check this part on a new build anyway. But for me the FC is mounted "due north" where the board arrow is pointing straight/front (0 Degree), but after changing to the mamba version 1 configuration it was set 90 CW.
This is what i see for gyro
Default | MAMBAH743 | MAMBAH743_2022B |
---|---|---|
set gyro_1_sensor_align | CW180 | CW0 |
set gyro_1_align_yaw | 1800 | 0 |
set gyro_2_sensor_align | CW270 | CW270 |
set gyro_2_align_yaw | 2700 | 2700 |
ahh so its correct
Sooooo, im back at this board, only really get time on weekends to fiddle. Anyone know why nothing is saving to the FC, serial rx, presets etc...nothing i select stays selected after save and reboot. Messages say that if nothing is there after it's saved and rebooted that its not supported...i know this FC can take an RX and a GPS as well as a DJI or Vista AU....
yes I have a M10 GPS with the FC and it works fine no problem with saving either. On Friday, May 19, 2023 at 04:11:11 PM CDT, GootyS @.***> wrote:
Sooooo, im back at this board, only really get time on weekends to fiddle. Anyone know why nothing is saving to the FC, serial rx, presets etc...nothing i select stays selected after save and reboot. Messages say that if nothing is there after it's saved and rebooted that its not supported...i know this FC can take an RX and a GPS as well as a DJI or Vista AU....
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
so weird that i cant save and reboot and the fc keep my settings. ALso have the M10 connected
Closing as fixed in 4.4.2 release.
still not seeing 4.4.2 for mambah743_2022B....
Do I need to do something to refresh it? or this PR still?
On Thursday, June 1, 2023 at 10:12:09 AM CDT, Mark Haslinghuis ***@***.***> wrote:
Closed #12668 as completed.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
guess my email with the screenshot didn't come through h...
@blckmn can you add the 4.4.2 release version to cloud build ?
same on this end as of 20:32 UK time, only shows old versions. Will be amazing if there is a release for this FC, It has been fun tinkering. Who can i chat to about OSD? I have a small issue in the DJI v2 goggles
You could join our discord server
im on the Discord, did a search for OSD, seems a few have issues but no solve that i can find. Maybe there needs to be a "#"OSD section
I was able to load 4.4.2 via BetaFlight Configurator. Looks like it's all good now. Also was able to fly. probably can close this.
Index updated.
Describe the bug
When I use automatic detection to flash my stack, betaflight does not find any official target of my version whereas a few weeks ago the version was offered to me
To Reproduce
Connect my stack and use automatic detection
Expected behavior
Have an official version of my stack again
Support ID
Flight controller
Mamba MK4 H743 V2
Other components
No response
How are the different components wired up (including port information)
No response
Add any other context about the problem that you think might be relevant here
No response