1-ON-1 TROUBLESHOOT: Jacob Ursua Aux channels don't go to 1000 | SOLVED 

When I worked for IBM we would occasionally have mystery fixes like this. In the machine history we would write "FWT squared" which stood for F**k With This, F**k With That. ;)

This call in thingy was a good idea. Will make for a nice long term series.

Thanks again for this opportunity Joshua! The video turned out great!

Thanks Josh... you really are a decent guy. I mean WHO DOES THIS??? this is amazingly kind and helpful. Good man!

5:45 "oh yea, put it there" quote of the year

one of the BEST Support for DRONE Community...

Thanks so much. My quad had the problem where I was not able to see the Aux channels moving at all. I just applied the setting "Channel forwarding" in configuration and it now works.

Throw back to the video were you slow motioned "rubbing on these nuts". You rock josh

Good info man!! This will help a lot of people👍👍

Lack of a possible full chip erase came to my mind during this session also. Earlier this year is updated from 3.1.7 to a pre-RC 3.2 without doing a chip erase. All seemed fine at first but when punching the quad it got wild and erratic when airborne. I suspected bugs in 3.2 but by doing it all over again, with a full chip erase, it worked just perfectly.

A couple weeks ago a buddy of mine had this happen to a new FC he'd insatlled on his quad. We were at the field when he showed me the problem. So played around with the channel settings on his Tarranis X9D.. I copied the affected switch channel and created the missing switch setting position that was needed to get the full range on the Aux channel switches. For some reason it wouldn't show the lower switch setting until we reprogrammed it into the reciever... It's a work around that worked... Not sure why but is a way to get around it if you can reprogram your receiver channel switchs. And don't have access to a computer for a download in the field....

Josh...ive been a long time fan of your videos. Ive been a long time fan of the fact that you enjoy helping out the rc community. Now, I find that you are doing 1 on 1 "help" videos....that's incredible! Two thumbs up for you, man! This scenario was quite interesting and I'm happy to see that the problem was solved.

I love this new idea helping out people like this and then sharing it , i might have to hit you up myself . I have been flying for about a year and still have no idea how to properly use BataFlight .

That’s awesome of you to help this guy out, his minimum throttle was at 1040 and when it was working it was at 1050😎🎮🤙🏻

Joshua, first off let me say that your helping many with your instruction. Your easy to follow and make even frustrating things like this a little less stressful. I am having the very same problem as shown in the video. I have reflashed the board (CrazyBeef4dx) firmware (CrazyBeef4dx 4.1.1) on my Mobula7HD V2 using 10.4.0 Betaflight as advised in the setup instructions several times and the problem persists. All of my Aux channels start out at 1500 and range up to the low 1800's and never up to 2000. 3 position switches act like a 2 position starting at 1500 then into the 1800's and back to 1500 on the 3rd position. My radio is a Taranis QX7s running OpenTX 2.2.4 with a IRangeX module bound on Multi DSM X 11ms, have also bound in DSM 2 11ms. The model binds great, flies well but the Aux channels are just not cooperating. I did try my old DX7i but still having the issue. I am out of ideas on solving this issue. Any ideas? Is there a way that a CLI command would fix the aux channels like rxrange command does for channels 0-3? It's all a big learning experience for an old dog, that started out on control line back in the 1960's and all the way up till now. Getting back into Quad's, it's advanced a long, long way from the old AeroQuad Arduino boards .

Bardwell is on it. Looking forward to more videos

Good find! The re-flash did the trick! Thanks for posting! Happy New Year, JB!

I've been flying the Xhover Stingy since it came out and I freaking love it. Great choice for a frame!

This is an awesome idea with this type of video. I'm still rather new to quads and was able to pick up on some of the small common details that are "understood" by most. Thank you for this!

Very nice video J.B.

Had the same sort of problem when I built my FT gremlin, but instead of aux channels my control channels were messed up. Spent 2 days trying to get it working. Ended up with the same solution, no clue what fixed it but it worked after reflashing the umpteenth time. Makes things feel a bit better knowing these things just don't happen to one person!

Live help ,that’s great to see, setting these things up can be so frustrating sometimes,,great work Joshua 👍

Fantastic interaction and this technique is a great learning tool whether I have that particular problem or no.

Joshua man!!! You are rocking it!! So proud and envious of you. But you've definitely put in the hours. You deserve it. Love your work.

Nice job Joshua

Sweet, cool video archetype. Theres always been a love/hate relationship with troubleshooting. Thats about the only thing you could have done.

You had it on the new model when you reflashed it...that did the trick.

If I'm not mistaken there's a DYS F4 target in the firmware flasher. When you asked him to reflash, he loaded the Omnibus F4 target... I own an DYS F4 and it gets buggy every so often.

i speculate that you are correct that there was something in the modes... just the other night on my nephews babyhawk he was flying just fine. i connected it to BF and adjusted just his rates and when he went to fly it again some how the modes got jacked up and channels got reassigned. also when i first bound it only 1-8 of the aux channels of 16 would work. after changing the aux's back and getting it out of turtle mode (arm and turtle mode got assigned to the same switch) and fixing prearm it now flys like a dream but the fact that the new BF (standalone) did that i think it might be a bug in the standalone

Man had same problem with the dys f4 board except on the controls pitch roll yaw wouldn't go below 1500 I gave up and got a new one about to find my old board and reflash again see what happens

It might have been by using the *new configurator* to flash FROM the *old firmware* to the new created a *bug* . Once it had the new firmware on the FC and flashing it again, the new configuration was able to flash without creating that bug.

Joshua, I'm happy that you have found your niche. Would you consider this to be your number 1 passion? And how long have you been considering making this a full time love affair?

lololol.... first up good on you for trying to troubleshoot a flysky i6x, secondly i joke about opening electronics and looking at it sternly and somehow that fixed it hehe.. i also joke about my upgraded i6 having a haunted model number, no.2 ps. goodness knows what kinda editing nightmare this was to put together. good work josh and jacob

I think I have the same FC board and transmitter. Be careful to flash the correct version of betaflight for the FC. My Omnibus F4 is "OmnibusF4SD" for flashing in BF, not sure if just using OmnibusF4 as in this video, could screw things up. I've never had that issue with my F4 and I6X. Creating a new model and re-flashing Betaflight is a good thing to try, when having setup issues. Nice troubleshooting video !

Great vid JB, every days a school day. Nice to get a fix on this one, getting another pilot in the air. Great job, love your work, that's why I'm a patron of yours and always will be.

Can’t the rxrange command cli command let you play with individual channel endpoints? Perhaps he played with those or the data behind that command was not erased when he flashed

Brilliant..ive got the flysky ia6 and with 2 omnibus f3 boards and a sp racing f3 board i am getting the no lines or channels showing at all..tho its deffo bound and i got the ibus/ serial and correct uarts set..also flashed most recent update it is driving me mad..done all the builds on 3 copters and only 1 shows correct receiver response..

That was very strange that it made the beep like it just bound to the receiver when he started moving the sticks. I wonder what RX he has in there? A8S?

Is it possible that he needed to have his transmitter on when flashing and dint have it on the fist time? Just asking and trying to learn. I will be setting up my second quad soon and struggled with my first but finally figured it out. Thanks for the great info and making yourself available. Much appreciated

Excellent video man!!! 1 on 1 trouble shooting!!! So useful for all of us!!!

I have seen this more and more since 3.2 and configurator 10.x

: o in my taranis didnt moved at all any aux in the monitor channel

Nice work one of your best videos

Interesting .....I think that new stand-alone has something to do with it. When I went to the stand alone my board orientation changed. My boards are both turned 90 degrees. When I started using the stand alone i had to change board orientation in betaflight to 180 but nothing was physically changed on the quads. I will try to reflash with the stand alone after seeing this.

Very nice Video, had the same problem and reflashed it and everything worked fine :)

Thanks! Loved this one, a nice reminder that sometimes things don't make sense and when things don't act/work like they suppose to I should try a 9th time before going crazy

I am trying to solve the same issue, but when i flash the board i get "Failed to open serial port" error, in betaflight. Powering up while holding boot button doesn't seem to make a difference. Any idea what could be not correct?

My receiver is bound to my controller but all my channels in the receiver tab on betaflight do not move, I move the sticks/throttles but nothing responds in betaflight therefore I cannot set my switches. Any help?

All my channels always go from 1100 to 1900. I have tried to fix it, but the quads go crazy. Flies fine with the weird endpoints, so I just leave it.

‘Giggity’.. you better be a family guy fan josh! :P I seriously say this too much.

I’m wondering if this isn’t some kind of bug in 3.2.#? I had same problem on two of my crafts I was working on. Except with mine it was like it wasn’t seeing receiver at all. Two different radios also, one taranis and One turnigy evolution. And when I reflashed it fixed itself same as this. Was using chrome configurator on both.

I watched all your videos I got it to arm then now the need day my receiver tabs not moving what the fffff

I have got a question: can I use a 7500 mAh 2s lipo as a ''power supply'' for my isdt q6 plus for charging 1300 mAh 4s lipos on the field? Just wondering because input voltage is lower than output voltage....

Hi Joshua hope all is good. Man i have a problem i only pick up 4 aux channels what chould be the problem.

interesting issue. who is next? I am seeing a long queue. to drone doctor Joshua Bardwell! thumb-up

You are a rock star!!!!

Nice like that not had the problem myself but good to see you work through it.

hi Joshua thank you for all the video you made so far!!! i have a issue with my new taranis i update to open tx 2.2 and when i go to betaflight in the receiver ,none of my channel move,i'am using a micro tbs crossfire and it all binded i have solid green light on both device do you now why? by the way sorry my english is not perfect hihi!! thank you!!!

i need help to :( my tango 2 pro is bind to my TBS Crossfire Micro Receiver V2. everything work in betaflight. but the secend i put my battery in the drone the reciver wont show input :( it still show green light `bindet` but no respons on betaflight. if i unplugg the battery, everything works agein.

instructions say:defaults, flash, defaults and then setup no restore between majon upgrades.

Wouldn't a diff been a thing to do to take a look at what was changed? I've had a number of weird issues after no change that a full chip erase has fixed. Most recently an RX that was bound with the RX before a board change would not work (register anything in the RX tab) after swapping a dead FC with a new copy of the same model FC. Pasted in old settings to the FC RX didn't work. Eventually full erase reflashed and the same pasted in settings worked. The only thing that could have been different were the contents of the flash. I think the flash needs to be checksummed and checked on boot if it is not already it seems to me that the flash gets corrupted (or not written correctly) sometimes. A checksum on boot (and on write) should at least catch the corruption.

This is so much like Amiga's in the 90's you had to turn them off just a reset never got rid of old stuff in ram.

I have 2 FC board one omnibus f3 with integrated OSD and the other one omnibus f4 with OSD as well got strange behaviour where on hover angle mode after 30 or 40 sec the micro quad drift to the left so badly that even if I apply trim will not stop to the point I run out of trim and I have to land both board got this issue I tried everything like soft mounting the boards flashing the beta flight with no joy both fc worked fine for me I don't know what to do so any help or advise will be appreciated. Cheers,

If he dump the old settings or using diff. He can compare the difference between the actual settings and the backup one.

It makes no sense but this was an issue when I flashed to the bee 10.0 configurator... I had to reflash 6 times!!! I was so mad!!!

I just plugged my Eachine X220 into betaflight to turn motor stop off, but after removing it it seems my esc isn't connecting to my flight controller properly. I plugged it back into betaflight to see if I could find the problem. All the aux channels are on 0 and flicking the arm and flight mode switches won't do anything. Do you know what the cause could be? Thanks, Ben

I would watch more videos like this. 🙂

nice ifo again .here is one for you I have a taranis plus and a qx7 ,can I bind them both to one receiver ,so if one stops working on the filed I can just tern the other one on and its allread bind ?

HI JB, do you use a 3D printer? If you do would you think about doing a vid on it? 👍🏻👏👍

I joshua do you think it maybe be a COM PORT error?

Mine aren’t moving at all I don’t know what to do 🤦🏽‍♂️

Weird!? Well, good it's fixed now :-) However I suggest next time to get the CLI-output of "diff" or even "dump" before and after fixing the problem. That would have gave you the chance to compare the configs and figure out what made the issue ;-)

Hey Josh great vid. Can you help me get my DShot beeper working on a stubborn quad? I have it turned on in CLI DShot Beeper fequency and volume set to 3. I also have set in modes on the third flight mode switch with turtle mode. I am using the same FC that is on another quad and the beeper works perfect with DShot but this one will not beep. Any ideas 💡?? Thanks bro

Yeah I had to use DFU with 3.2.3 bl didn't work

U mentioned that there was no movement in the receiver, dont show anything as if its not connected

Awesome - conversation content!!

How about paste in the config one line at a time until it screws up again? Would like to know what actually happened!

My DYS F4 just started making that beeping sound this morning out of nowhere just like his. I haven't had it connected to betaflight in weeks, any ideas? Is this normal? It has never made that sound before now. The beeping sound is at 11:55

Hi Joshua, Now that your doing this full time I believe you will need to widen the scope of topics to continue growing your fan base. I am one of a few that have been strugling to perfect VTOL craft for 3 plus years. The only truely useful controller serving this space is the KK1 with David's (happysunday) code "openaerovtol" unfortunately this controller is insufficient. We need code ported to or written for the current series of controllers you are familiar with. How about exploring/promoting this area of development?

Nice video I took was a great help. I was wondering if you've been hearing of an issue with HGLRC F428 V2 FC ..after flashing to 3.2.3 the accelerometer dies and there is no CPU load but board lights up normally..

I had the same problem on Betaflight 3.2.1 lol... I reflashed it and the problem was away...weird...I will flash 3.2.3 tomorrow and see what happens :D

Josh , hope you can help, just got ET100 and soon as I plug usb in to FC laptop dies like it's pulling down power for USB ports. Disconnected FC from ESC board , same thing. Acts like something in the FC PCB is shorted. Update: I made a data only USB cable that works fine on ET125 with batt plugged in and connects to betaflight, but when USB data only cable is plugged into ET100 and batt plugged in , computer does not die ( which is good) but will not connect. I guess I got a dud.

Why don't you compare the two dumps (backup from before vs. the fresh, reconfigured version) with a diff tool like diffchecker.com to see which settings are different ? That's what I do when I upgrade to make sure I didn't miss a new command or an old one is not compatible anymore

Good on e Joshua for helping that guy, you da man. It was a strange one as I watched I was thinking why the hell is this happening. Funny thing just like a lot of app's if they go wrong reinstall and they work again ( Gremlins lol )

when is your esc coming out through racedayquads,,,, waiting tic tic tic tic,,,,

Joshua Bardwell is a gangster... you've helped me so much Man U deserve 100k subs absolutely #gettingoverminiquadhump YOU CAN DO IT

I'm trying to use AUX5, I put it on inputs but on my Betaflight it doesn't work, what can I do?

I have the problem that the aux channels aren’t moving at all but all the stick movements work. Does someone know a fix?

I am sitting here thinking you guys should be checking the modes page first. I am watching to see what's going on though.

Dr. J. Bardwell, F.P.V., M.D

heya, maybe ill be the next lucky winner:) my aomway commanders are constantly a grey screen. no matter what channel or band i go to on them, they are always grey. its pretty frustrating when i want to fly but... oh wait, my googles aren't working. thanks

I can’t get my ,orx r620x v2, rx to talk to my JB F4 FC ??

telecoms is awesome. I was having this problem and was just wondering if I could ask you this. my roll won't go to 1500. it bounces from 1501to 1500. tx is evolution.

Copying old setup to new version isn't good idea. When You flash FC to new betaflight version always build your configuration from scratch. NEVER PASTE OLD CONFIG

With my Holybro Kakute F4 FC I have activated gyro 32 kHz sampling mode, 16kHz Gyro Update frequency and 8kHz PID loop frequency. CPU load is at 16%. Want to try it today.... Am I at risk? ....Specifying 32kHz Gyro Update frequency and 32kHz PID loop frequency resulted in a CPU load of 100%. I didn't risk to fly with that CPU load... 16kHz Gyro Update frequeny and 16kHz PID loop frequency led to CPU load of 67%. Didn't want to fly with that either. Think we need F7 processors...

i cant fly my drone its stuck in angle mode

I have a furious Fpv radiance sabot version that when I go to the reciever tabs it doesn’t show any movement in the sticks or switches but I can put the receiver on another fc and it works fine I even put another receiver on the furious Fpv fc and it works fine just it will not work with my xm+ that I was using on a 3 inch build any clue as to why that happens

Joshua, what about you made JB branded googles with OLED display? You will be first who made googles with OLED display 😉

I have an XM plus a betaflight OSD an Omnibus F4 flight controller I cannot figure out RSSI it seems really easy but I can't find it anywhere can you please help me please please please please please please please please please please please please and thanks

Spoiler : ......... in the end they dont have any idea why it was fixed :) . Really enjoy your videos but waiting 18 mins for this seems too much . It would be OK if those 18 mins would had boiled down to a reason but just "fate" doesnt justify it. Happy new year