The engines don't arm. After replacing the ESC. I can't arm the engines.
BT in the [Motor] tab starts the engine in MSP (USB) mode
* In [Ports] tab, UART 1 set to TX1, Reciver and radio are communicating.
The radio turns on the buzzer on TX3 not MSP (USB unplugged).
* In the [Reciver] tab, the gimbals work in accordance with the simulation in BT (throttle set to the bottom).
Taranis vs Reciver communication in mode (Access taranis qx7)
 In the bookmark .
* FC inverted 180` (corrected) in BT. The model behaves like in the simulator.
** What can block engine arming?.
*** CLI command needed to disable all config in [Filsafe] tab. tilt angles, etc.
 You know: no locks because the drone is tilted 90 degrees or something, I need to rule that out first. I think so.

My FPV  https://mechatronikaedu.blogspot.com/202...y-fpv.html

go into betaflight configurator, remove the rotors, plug in a lipo, into cli tab and type in: "status"
copy paste the results inhere.

or watch the video feed while arm, look for the betaflight warning

(15-Aug-2023, 10:25 PM)hugnosed_bat Wrote: go into betaflight configurator, remove the rotors, plug in a lipo, into cli tab and type in: "status"
copy paste the results inhere.

or watch the video feed while arm, look for the betaflight warning
hugnosed_bat 

My alert int the import old present 
First alert 

#status


first alert

second error


a) I replaced the ESC (because one transistor died 4in1 40A), I had to solder the wires, you know.

a) The previously written BT 10.9 configuration was loaded into the freshly flashowange FC (why did I flash?) Well, I was looking for reasons, I was experimenting. Anyway, I uploaded back the BT configurations in version 4.2. But BT 10.9 accepts v 4.4, 4.3. This however went with some slight errors.

b) the previous owner overclocked the ESC BLHeli_S or JESC. So that you could enable Dhot, as for ESC version 32 I have ESC_S

c) Engines start in the engine tab, I can start any engine and its revolutions. Disabled.
I also tried to make my own configuration based on popular (present) starter configurations.

d) I configured the channels in BT (gimbals) and the sticks work in accordance with the simulator on SBUS (AETR1234).

e) Command
CODE: SELECT ALL

status
the only thing that comes back:
CODE: SELECT ALL

SMEs,
you know you have a USB plugged in, ok.

f) I disconnect the USB, connect to drones using Taranis qx7/access . FC seems to be responding. For example, switching the stick to UAUX2. Works properly. Stick enables/disables the buzzer

g) I have the motors set to AUX1. When simulating in MSP (USB) mode, you can see that the stick switches AUX1. The ARM field turns red in ON mode and gray in OF mode.

** I am looking for CLI command => Disable Failsafe. Just turn OFF Failsafe.

Failsafe is for what happens when you lose your control link. This is not the same thing as something keeping you from arming.

Hugnosed asked you to run the STATUS command because that will show us the arming flags. In other words, it will tell us why it is not arming, and allow us to solve your problem.

(16-Aug-2023, 12:05 AM)Lemonyleprosy Wrote: Failsafe is for what happens when you lose your control link. This is not the same thing as something keeping you from arming.

Hugnosed asked you to run the STATUS command because that will show us the arming flags. In other words, it will tell us why it is not arming, and allow us to solve your problem.

I see.
Failsafe blocks the motors in certain situations. Inclination in degrees, etc. yes or no. It can stop the engine from starting. Yes or no?. If my engines do not start and the radio receiver communication exists. Why don't they launch?

No.

Failsafe controls what happens when your rc link is lost- does the quad drop, land, keep its current course, etc.

The angle the quad can be armed at is set in the configuration tab of betaflight.

Right now your arming disable flags are showing rxloss, which means your receiver is not connected to your transmitter.

Take your propellers off of your quad, turn your transmitter on, plug the quad into betaflight again and plug in a battery. Turn on your arm switch, run the status command again, and paste the output here.

Well, let's forget about failsafe. What makes the motors not want to arm after disconnecting the USB?. Please don't make me type #status. I'm about to get -1 again because I want to help a little, not start from the beginning. If there is no CLI, disable failsafe. I understand well. But do you know that if the FC is rotated 180`, the motor will not arm itself?. But let's forget about failsafe. You guys are experienced, you'll solve my problem soon, I'm counting on it.
---
You are the method

a) analysis, fast but difficult
oscarliang.com/quad-arming-issue-fix
b) deduction, slower but effective
I want to go by deductive method. If failsafe can block motors then I want to disable it. Then I will do another procedure. Yes, I want to solve it. The drone has been standing for 40 days and nothing. .

(16-Aug-2023, 12:57 AM)Lemonyleprosy Wrote: No.

Failsafe controls what happens when your rc link is lost- does the quad drop, land, keep its current course, etc.

The angle the quad can be armed at is set in the configuration tab of betaflight.

Right now your arming disable flags are showing rxloss, which means your receiver is not connected to your transmitter.

Take your propellers off of your quad, turn your transmitter on, plug the quad into betaflight again and plug in a battery. Turn on your arm switch, run the status command again, and paste the output here.

https://oscarliang.com/quad-arming-issue-fix/

---

(15-Aug-2023, 10:25 PM)hugnosed_bat Wrote: go into betaflight configurator, remove the rotors, plug in a lipo, into cli tab and type in: "status"
copy paste the results inhere.

or watch the video feed while arm, look for the betaflight warning

https://oscarliang.com/quad-arming-issue-fix/

I’m going to tell you to do what I previously posted, and type status after following my directions.

I’m not going to spend my time continuing to help you. It’s nothing personal, but without that information all I can do is guess. I certainly don’t want any part of helping someone get a quad in the air who is willing to disable all failsafes. They are there for a reason, and that is to keep your quad from being an out of control danger to life and property. This will be my last response to this thread.

Once again, maximum arming angle can be changed in the configuration tab in betaflight. It defaults to a low number, if you change it to 180 it will allow the motors to arm even if it was upside down.

If you had followed directions, we would know if this was your problem because it would show us an “angle” arming flag.

The method that you are describing is not analysis or deduction. It is simply shooting in the dark and seeing what sticks.

Here’s some reading on things that can cause your quad not to arm. Perhaps you’ll eventually find your answer there through enough trial and error:
https://betaflight.com/docs/wiki/archive...And-Safety

(16-Aug-2023, 09:12 PM)Lemonyleprosy Wrote: I’m going to tell you to do what I previously posted, and type status after following my directions.

I’m not going to spend my time continuing to help you. It’s nothing personal, but without that information all I can do is guess. I certainly don’t want any part of helping someone get a quad in the air who is willing to disable all failsafes. They are there for a reason, and that is to keep your quad from being an out of control danger to life and property. This will be my last response to this thread.

Thank you for your time.
I pasted the result of the #status command above.
We managed to solve the problem. The engines start. The throttle was in the wrong range.
* Thanks again for your patience.
I'm currently working on the modes tab. I'll start a next thread about it. I want to add a switch (engine off) to descend safely. He's learning to fly. Returning the throttle to the bottom causes the drone to hit the ground. It's better that it drops by itself from 15 cm.