speedybee f7v3 in inav 7.1.2 motor mapping not working

[samsab1]

Hello everyone
I'm running into an extremely annoying problem whose cause I can't determine:
inav 7.1.1, speedybee f7v3 in inav 7.1.2
Flight Controller reversed 180°, engine remapping done correctly I believe, dshoot 300.
almost every time I connect my controller card to INAV, I lose the motor mapping; more precisely, the mapping remains faithful to what I had determined BUT when starting the drone, only 3 motors turn, or only 1 (the one which was not previously turning when the other 3 were turning) or even only the front 2 turn or then only the 2 rears rotate..... in short almost all combinations are possible, while this same flight controller card, with inav 7.1.1 firmware, oriented normally (not inverted therefore) and the standard mapping, does not didn't make that kind of bad joke to me.

Can anyone tell me how to fix this permanently?
I would nevertheless point out that sometimes the 4 motors start working when the drone is armed.....

[samsab1]

I add pictures

[sensei-hacker]

Let's start with this - how are you testing the motors?

[samsab1]

i would say:
with and without prop
batterie connected
throttle : using the inav interface above
i do not know if i give you the right information you are looking for....

[sensei-hacker]

Sorry, I didn't see the pictures you had added. The Outputs tab is indeed the best place to test.

I said you "remapped" the motors. Can you tell me please how you went about doing that?

[samsab1]

I mounted my drone in a classic way respecting the standard assembly of the F7, that is to say arrow of the FC towards the front of the drone.
then I wanted to rearrange this assembly and so I turned the complete stack, already wired with its motors, by 180°. finding that the order of the motors was incorrect, I remapped the FC with the inav utility.

each time I modify another parameter of inav such as the RTH parameters, I take the risk of seeing my motors not all start the next time the motors are armed. I don't understand what can bring about this random aspect, although very present; that being said, as I write, the 4 engines are recognized and functional, but for how long?

under inav 7.1.1 in normal configuration, from the orientation point of view of the fc, I have never had this problem

[aveias100]

Hi samsab1!
I have the same problem... there is a way to resolve the problem?

[sensei-hacker]

Again, what do you mean you "remapped" the motors? There is no such thing in INAV. So what exactly did you do?

From the screenshot, it looks like possibly you ran the mixer wizard?

Do NOT load and apply a default preset after doing that. Loading and applying the default preset will undo what you did with the mixer wizard.

under inav 7.1.1 in normal configuration, from the orientation point of view of the fc, I have never had this problem

FYI the ONLY difference between 7.1.1 and 7.1.2 is the default setting for a baro-related setting:
iNavFlight/inav@7.1.1...7.1.2

[sensei-hacker]

I just re-read and noticed this:

only 3 motors turn, or only 1 (the one which was not previously turning when the other 3 were turning) or even only the front 2 turn or then only the 2 rears rotate

That sounds like a dodgy connection on the plug between the FC and ESC.
INAV cannot change the settings between boots, because the settings are checked by a CRC.
Therefore anything that changes without saving new settings in Configurator is a hardware issue, such a loose connection.

[aveias100]

Motors are in wrong position in inav. It was ok and working in betaflight.. Changing to inav motor mapping is wrong... A domingo, 25/08/2024, 13:47, Sensei ***@***.***> escreveu:

…

I just re-read and noticed this: only 3 motors turn, or only 1 (the one which was not previously turning when the other 3 were turning) or even only the front 2 turn or then only the 2 rears rotate That sounds like a dodgy connection on the plug between the FC and ESC. — Reply to this email directly, view it on GitHub <#2143 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKYTDTXH7DOXCAIEBUOW7SDZTHG55AVCNFSM6AAAAABKWHJ74CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYHAZDANJUGY> . You are receiving this because you commented.Message ID: ***@***.***>