Mamba F405 Mk2 and Dronin

This site is best viewed in a modern browser with JavaScript enabled.

Mamba F405 Mk2 and Dronin

WyreUK

Hi folks I've been searching for two days now how to set up a tricopter on a diatone mamba F405 mk2 flight controller. Is there a firmware for dronin on this fc? It's the last piece of the puzzle to get this into the air.

Also how do I setup the servo on this fc?

Thanks for any help in advance.

Wyrefpv

LitterBug

WyreUK,
I'm not familiar with that FC and am not sure it is supported. If it is supported by dRonin, it may not be sorted by the TriFlight branch.

LitterBug

adamjcooney

I could get the MK2 to work. I had to find the original version of the F405 mini.

WyreUK

Hi Adam,

Thanks for the reply, what would be the target for the mk2? I've been trying with betaflight and it just keeps spinning out when I go to hover. I'm about to give up and just get a quad frame lol

ehrans

standard mamba and mk2 releases shares target on betaflight. i have all of those combinations (normal size/mini/mk1/mk2), i already make it fly, but things like beeper/osd if turned on, becomes in an endelss bootloop until rescue and erase settings partition

btw i tried with dronin revolution target only.

also betaflight target is Furyf4OSD

WyreUK

Hi Ehrans,

So if I flash it with the revolution target I should get it to work?

I've been trying to get it to work with betaflight and every time I try to hover it just spins out. I've got a post on rcgroups and people have been trying to help me but no one can figure out what's going on.

ehrans

WyreUK you have to remap motor order btw. be careful with order and rotation direction

you also have to check and modify the gyro rotation, as far as i can remember is -90º yaw (same as +270 yaw)

double check after a reboot the mimic drone at the telemetry page is moving the same of the real one by hand.
using the mamba f405 is posible but is not plug and play, and remember to NOT activate OSD or Buzzer, will endelss bootloop until reflash or format settings partition.

yds

The dRonin Revolution target is the catch-all for may different betaFlight targets such as:

REVO
OMNIBUSF4
OMNIBUSF4SD
FRSKYF4

and from this thread I now learned the FuryF4OSD target as well..

The Deals & Sales thread lists lots of FCs known to work with dRonin Revolution target. Some, like the HGLRC clones, work other than the Buzzer and LEDs are inverted.

I found betaFlight's FRSKYF4 target.h cleanest and easiest to read.. dRonin's Revolution target works 100% on the XSRF4O. which makes the FRSKYF4 target.h a good one to compare other betaFlight target.h files to see if they are likely to run dRonin's Revolution target.

ehrans

yds i know development is on stand by mode right now. but what i seriusly lack of the actual revolution target, is the posibility to select normal (inverted) sbus on any port. some omnibusf4sd v3 comes with standard sbus (inverted) at rx6, but Dronin only let me select Non-inverted sbus in a diferent port than Main (rx1), i have a lot of 20x20 fc with no posibilities of use other standard sbus port than rx6 and uninverted hack is not public yet on r9mm receivers to pick an uninverted sbus signal. (anyways those mini boards have not another rx pad. just tx3 and tx1 for smartaudio and frsky telemetry)

Is this realy so hard to add the same logic options to any port?

yds

ehrans I'm not a dev. That said, I've had some luck getting S.Bus to work on RX6 with some OmnibusF4SDs by just picking the only available option. I did run into a 20x20 iFlight stack where I had to hack both a non-inverted S.Bus and a non-inverted S.Port. worked out fine with a R-XSR which had solder pads for both non-inverted signals.

ehrans

yds i'm talking about r9mm 866-915mhz receivers, not public know of the uninverted sbus point

LitterBug

Ufortunately, the F4 is not inversion friendly out of the box. It is older than the F3 and F7 which support inversion natively. This is a hardware limitation of the F4, not of the firmware. Manufacturers had to add inverters to their F4 FCs to allow for the use of inverted sbus and s.port. This is the spec for those protocols. dRonin doesn't have the massive target creep of *flight. So you need to find FCs that the mappings match the handful of FCs that are supported. There are ways to externally hack the inversion so it can be used on other ports. https://www.readytoflyquads.com/rtf-sbus-inverter for example. Oscar Liang has some other options here https://oscarliang.com/sbus-smartport-telemetry-naze32/ . Some FrSky RXes support univerted pads that can be used. (R-XSR, and R9 MM for example). With development completely stalled, the best option is to stick with known working FCs.

ehrans

LitterBug r9mm? do you know wich pad/pin/ic leg is the uninverted sbus signal? because i can't find it on internet, what it have is a uninverted smart port pin as far as i know

yds

ehrans https://OscarLiang.com/uninverted-sbus-smart-port-frsky-receivers/

ehrans

yds yeah. i saw that post thouthands of times, i still can't see any uninverted sbus pin of the r9mm receiver

LitterBug

Ah. I was thinking of the S.port. Usually just need one univerted signal since most FCs have an inversion capable port on them.