Ok I will head back into that program.
So that software program essentially even though d shot is checked I just need to uncheck it since my ESCs aren’t dshot capable and just move through it like that is that kind of how it’s working? It’s recognizing my flight controller as a Maytak Even though it’s an orange plus is this normal I just want to confirm before I move forward so I’m not messing anything up on my end and make it more complicated?
Never mind I found the user manual I’ll start reading through it
Welp I worked my way through the configuration tool and it crash. Here is the bin file. I took off nicely then shot up in the air, I was able to decrease the throttle but it was like it didn’t care what the stick inputs i gave it. I am sure you can see all the detail in the bin file though.
Oh? There is nothing to see in that log with the log bitmask you have set.
And it doesn’t look like it was flying at all. At least view the log for yourself before posting it to determine if its of any value.
I am not sure why it didn’t log anything
I told you why. Because you have this.
LOG_BITMASK,524416
Now you should look at your parameter file and see for yourself what is being logged with this bitmask (hint, not much) and you will learn something.
I did review it and didn’t see much but thought that maybe I was missing something. Dave I appreciate you looking into this but I am not looking for a hand out and I am trying my best to figure all this out. I have been following the paths that I have found and its not working out as of yet.
Post a .zip file containing all the files in ArduPilot Methodic Configurator vehicle configuration directory that you created.
My guess is that you did take off prematurely without doing the required steps. But I can only see what happened once you post that zip file.
In the user manual for the configurator it shows red #3 for the flight controller option. I have downloaded the latest version and I missing something? When it shows the “current value” is that what is currently on the flight controller or just generic?
No, that picture is outdated there is no more #3.
Yes that is the current value in the flight controller as explained in the mouse over help text.
Thanks for all your help.
I am backing up and going thru all the basics currently, plus I believe that one of my issues with this build may be out of date ESC’s. I am digging thru the forums to see if I want to go with 4in1 or single for this 1000+mm slow flyer.
No matter what you choose, at the moment you don’t want to buy BLHeli32 ESCs 
As per Dave’s steering I picked up BLHeli32 esc’s, he said it won’t be an issue. They will still communicate with the cube orange flight controller correct?
My comment was a bit tongue-in-cheek. Technically, BLHeli32 are among the best ESCs you can buy, but there is a bit of a situation ongoing with the BLHeli dev, see here. For what it’s worth I do believe that there will be some kind of compromise at some point, but at the moment you won’t be able to upgrade your ESCs, which, depending on the currently flashed version, comes with some (IMO neglectable) risk as there have been a few reports of misbehaving (read: spinning up when they shouldn’t) BLHeli32-driven motors with certain versions.
Right. The last BLHeli_32 ESC’s I have purchased came with 32.9 and until all the hoopla over BLHeli_32 shutting down I had never heard of this problem of unexpected spin up. But, that’s because I haven’t used Betaflight on anything in some years and that seems to be the only connection to this problem. I could be wrong about that but we don’t see it mentioned on the forum here. I have updated all of mine to 32.10, which has been out for awhile, but that’s just because I usually do keep things at the latest level, it wasn’t driven by any perceived problem. I have a very dim view of the “if it aint broke don’t fix it” mentality.
@dkemxr I picked up 8 of those esc’s in case in want to convert it over to X8, I appreciate all the input here in the forum. The only negative reviews on them are “bad/cold solder joints”. I’m assuming like all products there will be a few that slip through QC.
I have had 8 of those flying on 2 quads for quite awhile, they seem to be solid.
Pretty sure the whole thing is getting way over-amplified at the moment because it’s used as argument for why it was a really dumb decision to just shut down the servers. And I get it, if I were selling drones commercially I really wouldn’t want there to be chance of accidentally beheading my clients. But in the end I don’t think it adds much to the inherent risk of the hobby.
1 Like
I wanted to post an update…
I tore my quad back down and ordered some new esc’s to rule out any issues with them.
I closely inspected my motors and found that they had some serious vertical play on the rotating assemblies. It seems that the main shaft had slipped down and created the play. So I decided to order new motors, for the prior reason and it seemed that the bearings also were about to lock up.
Now I just need to get the Bidirectional DSHOT work with the new ESC’s before the new motors come in.
Thanks to everyone on this thread that has assisted me in trouble shooting my issues!!
@amilcarlucas @Oli1 @dkemxr @Tristan_Redish I really appreciate your help!!
2 Likes