#Arming Issue

146 messages · Page 1 of 1 (latest)

digital fiber
#

use the screenshot app 😭

sly star
#

How many poles does a tinywhoop motor have again?

#

Did you apply defaults after flashing bf?

digital fiber
#

you should honestly just

#

reflash it

#

and when you connect it'll prompt you to apply defaults

#

apply them

#

do diff all in CLI first and send it here

#

yeah just reflash it now

#

probably with reboot sequence

#

unless you're already in DFU by having held the button

sly star
#

it needs to be a full dump to show resources

digital fiber
#

yeah just doing diff because they're reflashing

sly star
#

but i agree, full reflash is probably best

digital fiber
#

no just reflash

sly star
#

I'm leaving to pick up food, but incase yall need it this is the motor mapping for a betafpv 5a aio

#

resource MOTOR 1 B06
resource MOTOR 2 B07
resource MOTOR 3 B04
resource MOTOR 4 B05

digital fiber
#

thank you

#

now when you connecyt

#

press the apply defaults button

#

well that's weird

#

apparently it does that by default now

#

without prompting you

#

so you're good I guess

#

just copy your diff into the cli

#

and then copy this into the cli

# 
resource MOTOR 1 B06
resource MOTOR 2 B07
resource MOTOR 3 B04
resource MOTOR 4 B05
save
#

yeah

#

why not

#

press save?

#

you copied the entire diff into the cli right?

#

and then it reboots?

digital fiber
sly star
#

The diff has save at the bottom

digital fiber
#

what error are you getting?...

# 
set dshot_burst = AUTO
set dshot_bidir = ON
set dshot_bitbang = OFF
set dshot_bitbang_timer = AUTO
save
#

can you just

#

try that

#

see what goes on

#

I'm confused at this point

#

bitbang on = no gyro... bitbang off = wrong mixer

#

what even

digital fiber
digital fiber
# 
set dshot_bidir = OFF
set dshot_bitbang = ON
set dshot_bitbang_timer = AUTO
save```
#

try this

#

and otherwise just wait for someone to post a dump i guess

#

no it is not your fault

#

if it was your fault

#

I would say

#

"this is your fault"

sly star
#

What does your configuration page look like?

#

Alright

#

The dma thing with these fcs is pretty unique, i havent ran into it with any other fc

#

No just a bad combination of settings

#

You werent holding it in your hand while trying to calibrate, were you?

#

Does the fc say v2.1 on the bottom?

#

The slow gyro issue is related to how the fc was designed, it needs bitbang to function properly on later revisions

#

Yeah because too many resources being used, so i wanted to know what your settings were

sly star
#

But i need you to confirm yours is this generation

#

Ill send you a dump in a bit, im watching tv with my wife rn

sly star
#

same way you updated, just select 4.3.0 as the version

#

setup as normal

#

If everything is good we can consider updating to 4.5 later

#

I probably wont be up for much longer, just doing a quick led repair before bed

#

kew

sly star
#

Nah 4.3 just came out i swear

sly star
#

Just look at the photo

#

Up left with left stick, down center with right for gyro

#

Yeah, i didnt say to try to arm it with stick commands

#

I dont even know if that one works anymore

#

If you do right stick up and left stick left it should open the osd menu

#

Use that to goto hardware i think and run the calibrations in there

#

Is your radio bound to the quad?

#

And is the quad powered on with a lipo?

#

You need to do this with your goggles

#

Somethings probably fucked then

#

You do stick commands before trying to arm

#

You werent trying to arm first, right?

#

Is led strip enabled in betaflight?

#

In the configuration tab it's unchecked?

#

I have a sus idea

#

If you put "get moron_threshold" in cli what does it return?

#

Oh they changed it "get gyro_calib_noise_limit"

#

"set gyro_calib_noise_limit = 100"

#

Yeah

#

It should already be on from the factory dump i sent

#

You pasted the entire dump into cli after flashing 4.3, right?

#

Did you type save after?

#

I did forget to specify, you need to save after any cli commands. Including the gyro one you just did

#

If you have been saving you can try to set gyro_calib_noise_limit to 200, and if that doesnt work your gyro is probably cooked

#

So you didnt save after pasting the dump then

digital fiber
sly star
#

The dump included turning on bitbang

#

Yeah its a factory dump of all settings

#

Doing it now will wipe any changes you made since flashing 4.3

#

So you now need to make a diff, then put the dump in and save, then put the diff back in and save

#

All motors work?

#

Does it twitch?

#

It might be incorrect motor mapping

sly star
#

Normally when a motor or esc dies its only one phase, and this causes the motor to twitch

#

If you plug it into betaflight and open the motors tab and plug in a battery does the non functional motor show an error?

#

Try a different motor then

#

I do it by feel with the props off, gently touch the side of the bell as its spinning

sly star
#

Nice

#

It was probably because you flashed 4.3, but didnt apply the dump

#

You could try it

sly star
#

You are set to props out, right?

#

All 4 motors work now?

#

Is the gyro_calib_noise_limit still 100?

#

We should probably put that back to what it was

#

Yeah

#

And also goto your receiver tab and make sure all your stick inputs match the bars moving on the left

#

Yaw moves yaw, throttle moves throttle, etc

#

If it arms at 48 then you dont need to make it 100

#

Have we done any esc settings yet? I cant remember

#

I have a thread in #1144565832828072080 about setting up bluejay, do that with the most recent stable release of bluejay

#

And after going through all the steps, before disconnecting the quad, send a screenshot of the settings page

#

And tag me

#

There you go

#

Youll get better battery life, but if it works now just go enjoy it until you feel like tinkering

#

The big thing to remember is bitbang, any time you update the default settings will turn it off

#

Make a diff before updating, paste into cli after, dont forget to save

#

If it throws errors you can save again to force it without the error commands. Some commands change with bf versions

#

I try not to bring pid settings across betaflight versions using a diff, i prefer to just use a preset after updating

sly star
#

Why did you update if it was flying well?

#

Can you plug it into bf while holding the boot button on the fc? You might need to use a pen or something

livid drum
#

Alright so we've established that LQ is showing you the transmit mode, not transmit channel (not a thing in ELRS)

#

So LQ 7:xx or LQ 13:xx in your OSD

#

Ugh that video is so old

#

BADRX means the FC is detecting something wrong with the signal that the receiver is giving it

#

Go to your Receiver tab in BF Configurator and make sure that all of the correct channels are moving when you move a stick or switch on your radio

#

Yes I know

#

That's why you need to check your channel map in the Receiver tab

#

Do you get BADRX only after arming and only after raising the throttle?

#

Have you put the RSSI dBm on the OSD as well as LQ?

#

What does that value say?

#

Have you done the ELRS bench test?

fast stump
#

What FC do you have again?