(26-Dec-2017, 09:51 AM)Tom BD Bad Wrote: I agree, my 1st attempt at a build, initially, went really well, despite the Omnibus brushed FC not coming with any instructions. After everything was soldered and placed on the frame, looking ready to go, however, I struggled to get BetaFlight to recognize the connection to the FC... 

I had done the soldering at my buddy's place, he has a workshop with a nice soldering station, lighting, spare hands etc, all set up and ready to go, whereas I would have to (to use a common South African term) make a plan. So I downloaded the BetaFlight configurator onto his PC, along with driver packs etc. but I couldn't get it to work.

Finally managed to get everything set up on my laptop at home, got the board and configurator communicating, but now I couldn't get the RX to talk to the FC...  With hindsight and a little more experience, I was probably failing to select the proper options for the serial RX... As a human being though, I am prone to expecting the worst, so I re-soldered the RX... 

Thinking back on it,  I might have even seen the tell tail 'smoke trail' of the tiny solder 'missile' that lay, un-exploded, awaiting the 5v trigger that inevitably came with connecting the USB!


Things are looking like they are improving though, (Josh Bardwell's) JB FC is now available, (shipping it out of the US isn't very affordable at the moment though) and I'm sure that there is probably an excess of information in the manual. He has also written the instruction manual for the HolyBro Kakute FC too. Josh has also just announced that he has quit his permanent job to focus on the hobby full time, so he may have more time to offer his writing services to FC manufacturers.

I'd be happy to pay an extra few $ to cover the cost of his service and the printing.

BD, yours is a story I have seen time after time on various forums. I just keep wondering why it has been allowed to go on for so long.

Josh bardwell sounds like he has got the message and perhaps others will soon follow suit. Let us hope so.

Regards,

KK.

Some good news at last.  

After 3 days of poking, prodding, loading and reloading drivers, firmware versions, configurator versions and goodness knows what ever else all of a sudden for no apparent reason that I can discern, the SP Racing F3 suddenly decided to successfully flash the firmware.  


I have been swapping between Betaflight and Cleanflight all to no avail even though I would prefer the Cleanflight version.

However as the Gods will wont, the version flashed successfully was Betaflight and now I am dead scared to reflash with Cleanflight in case I muck things up again.

As I have said many times, why is this quad stuff so hard, so vague? It really makes life tough for dumbos like me.

Anyway, let us see what the next few days bring.


I will start to tune the FC properly and then install it into Wooden It.

Fingers crossed.    

KK

Well along the road to tuning the SP F3 and I find myself wandering down a very familiar path. The same path I wandered down tuning the Hero.


As a result I find myself wondering if there is actually any difference between these two FC or for that matter any of the FC that use the Betaflight Config. From a tuning point of view everything is exactly the same for both FC.   

Anybody care to comment?

Regards,

KK

Yeah, betaflight does pretty much the same.

I don't remember if your hero FC uses an F1 chip... With the F3 you could use higher looptimes and the dynamic notch filters if you flashed firmware 3.2 or later.

(31-Dec-2017, 05:15 PM)fftunes Wrote: Yeah, betaflight does pretty much the same.

I don't remember if your hero FC uses an F1 chip... With the F3 you could use higher looptimes and the dynamic notch filters if you flashed firmware 3.2 or later.

Thanks FF.  My Hero was an F3.

(31-Dec-2017, 03:35 PM)Keyboard Kid Wrote: ... I find myself wondering if there is actually any difference between these two FC or for that matter any of the FC that use the Betaflight Config. From a tuning point of view everything is exactly the same for both FC.   

As far as I know, when you purchase a standalone FC, it will use the default configurator values (PIDs, filters, etc). These days BetaFlight default configuration works so well with most different quads that it's actually quite rare to buy an RTF model that has the FC specifically pre-tuned.

(01-Jan-2018, 07:20 AM)Tom BD Bad Wrote: As far as I know, when you purchase a standalone FC, it will use the default configurator values (PIDs, filters, etc). These days BetaFlight default configuration works so well with most different quads that it's actually quite rare to buy an RTF model that has the FC specifically pre-tuned.

Thanks BD.

I rather suspect the defaults may not apply to Wooden It.

IT is a bit far removed from your standard quad.

Regards,

KK

Howdy Boys,

The pre-tuning on the SP F3 is now finished and it is ready to mount on the quad.

However before I do that I wanted one more try at these misbehaving Heros.

I have two of them. One has never flown and the other is wel flown but stopped communicating with the config some time back.

My mate Snow got both of them communicating with both BF and CF and both communicate perfectly.

However one will work the motors via the Motors Tab in both configs the other will not.

Again both Heros will not drive the motors from the TX.

Is there any setting that I may have overlooked that would account for the motors not working?    

I am near worn out trying to sort these problems out.

I am in a lot of pain at the moment as I am facing a hip replacement op in the next few weeks and I find this stuff a bit tedious at the moment.

I am hoping to test fly the SP F3 before the op but I want to sort these Heros out before putting them away.

I am not sure how long I will be laid up after the op but I will keep in touch as often as possible and I will see if I can remember some more tales from my olden days to keep you lot amused while I am loafing around after the op.

KK  

One trap is the min_check setting. If your throttle channel does not go below min_check, the motors won't start. Not sure if min_check is visible in the GUI, if not you'll find it in CLI. If this was the problem, either increase min_check or lower the throttle endpoint in the tx.

That's just the first thing i could think of... I'm pretty sure you checked that before but this thread grew longer than my short-term memory.

(03-Jan-2018, 04:04 PM)fftunes Wrote: One trap is the min_check setting. If your throttle channel does not go below min_check, the motors won't start. Not sure if min_check is visible in the GUI, if not you'll find it in CLI. If this was the problem, either increase min_check or lower the throttle endpoint in the tx.

That's just the first thing i could think of... I'm pretty sure you checked that before but this thread grew longer than my short-term memory.

Hi F,F my short term memory gave up months ago and  I find myself constantly going back and re-reading distant posts. This thread certainly has grown.

I am not sure if I have ever looked at min_check but there is a min throtlle setting in config which I make sure is exceeded by the throttle travel.

However I will go looking for min_check to see what that is set at.


KK

(03-Jan-2018, 09:51 PM)Keyboard Kid Wrote: Hi F,F my short term memory gave up months ago and  I find myself constantly going back and re-reading distant posts. This thread certainly has grown.

I am not sure if I have ever looked at min_check but there is a min throtlle setting in config which I make sure is exceeded by the throttle travel.

However I will go looking for min_check to see what that is set at.


KK

Hi FF, I entered min_check in CLI (Cleanflight) and it came back "Unknown command".

I re-checked the min throttle commands in config and they were all correct so still no joy.

KK

(03-Jan-2018, 08:19 AM)Keyboard Kid Wrote: I am in a lot of pain at the moment as I am facing a hip replacement op in the next few weeks and I find this stuff a bit tedious at the moment.

Good luck and a speedy recovery KK

(04-Jan-2018, 05:22 AM)Tom BD Bad Wrote: Good luck and a speedy recovery KK

Thanks BD.

I will be thinking of you blokes while I am lounging back in luxurious surroundings being waited on hand and foot by glamorous nurses.   

No more stupid quad stuff just pampering.

I cannot wait!!

KK

(04-Jan-2018, 09:04 AM)Keyboard Kid Wrote: Thanks BD.

I will be thinking of you blokes while I am lounging back in luxurious surroundings being waited on hand and foot by glamorous nurses.   

No more stupid quad stuff just pampering.

I cannot wait!!

KK

Latest quad update.

I put aside the Heros for the time being as I am running out of time. I want to test fly the SP F3 before I go to hospital.


So I installed the SP F3 today and everything thing works well. Comms and motors all work well from both Betaflight and Cleanflight.

HOWEVER the receiver is completely out of whack.    

The only two channels that are controlable from the TX is AUX 1 which is actuated by the Throttle (TX ch 3) and AUX 2 which is actuated by the TX channel 4.

I have checked the RX type and channel map in configuration and I have swapped wires around from the SP 10-1 and 10-2 all to no avail.

I just cannot fathom what on earth is going on.

I have loaded and re-loaded everything I can think of with no success what so ever.

Any ideas out there? PLEASE?

I am definately starting to wear out.

KK

PS Reno I have decided to order a Naza V2 when I get back on my feet. I agree that it will be the best for my application.

I guess you checked settings on the TX?