Recently completed a new 5"quad.
Kakute F7 stack with Tekko 40amp 4-in-1 ESC, 

Running it on INV 2.3.2
and the latest Kakute F7 update
and I chose a 'Preset' to make things easy. In the Preset Inav chose MultiShot.

Flew it about 6-8 times just cruising along watching how it flys on Multi-Shot. All went well until today

I watched an INAV vid with Pawel (one of the INAV developers) recorded in NOV or DEC and he stated that it would
be fine to use DShot 1200 on INAV.
I wanted ESC telemetry so I switched it over to DShot1200.
I went back out to do some flying to get my 'heading' set correctly in GPS.  Thankfully I was still just cruising and only about 6' off the ground because the
quad did a left roll and hit the dirt.
So I thought well maybe 1200 is a bit to much so I chose Dshot 600...same results, Dshot 150...same results...
By the way it always seemed do a left roll and it would fly for about 1 to 1.5 minutes before takin' a dive.
I slowed down the video and motors 2 & 4 seemed to still be spinning when it hit and there were no warning
message(s) on the OSD.



Went back to Mulitshot and the quads flies fine.
     
Anyone experience this? Or have an answer as to why?    INAV gives a warning when you choose DShot 600 or 1200.
I would really like to get the amperage reading in the OSD but ....

Thanks
Roger

I know there is issue with iNav and Dshot. This is a while back but I don't think iNav has Dshot working well yet. Snow even mentioned this the other day.

https://github.com/iNavFlight/inav/issues/4601

Even the release note for 2.1 mentioned caution.

https://github.com/iNavFlight/inav/wiki/...ease-Notes

The reason that DShot is flaky in iNav is because the developers only implemented it due to public demand and pressure. They didn't really want to include it in the first place because their argument is (was) that Multishot and Oneshot are better protocols. I can't say whether that is the case or not because in Betaflight I've never seen any reason to use anything other than DShot. As a result, the implementation of DShot in iNav wasn't done in the same way as it was in Betaflight (I think it was probably just cobbled in), and because of that it seems to have some reliability issues. This is no disrespect to the iNav developers because they spend their own spare time doing a great job providing flight controller firmware to the masses for free, so it just is what it is.

That said, in the upcoming iNav 2.4 release (due out around the end of February), they have implemented the ability to use RPM filtering which needs to make use of telemetry data that comes into the FC from the telemetry signal connection, so for that so be reliable I would expect them to have bolstered up DShot implementation in some way. So when iNav 2.4 drops I would give that a go with DShot and see if it then works more reliably. No guarantee, but certainly worth a try.

(29-Jan-2020, 06:07 AM)voodoo614 Wrote: I know there is issue with iNav and Dshot. This is a while back but I don't think iNav has Dshot working well yet. Snow even mentioned this the other day.

https://github.com/iNavFlight/inav/issues/4601

Even the release note for 2.1 mentioned caution.

https://github.com/iNavFlight/inav/wiki/...ease-Notes

Yea, I was aware going in that Inav didnt use Dshot. In the Release note 2.1 link it says  Dshot is supported but l not fully tested. In his videdo the developer Pawel
said it is OK to use any Dshot protocol. 



I have Blackbox logs but I have no experience in using them. I will edit the post and add the logs, possibly someone could take a look.

Thanks

(29-Jan-2020, 01:45 PM)SnowLeopardFPV Wrote: The reason that DShot is flaky in iNav is because the developers only implemented it due to public demand and pressure. They didn't really want to include it in the first place because their argument is (was) that Multishot and Oneshot are better protocols. I can't say whether that is the case or not because in Betaflight, I've never seen any reason to use anything other than DShot. As a result, the implementation of DShot in iNav wasn't been done in the same way as it was in Betaflight (I think it was probably just cobbled in), and because of that it seems to have some reliability issues. This is no disrespect to the iNav developers because they spend their own spare time doing a great job providing flight controller firmware to the masses for free, so it just is what it is.

That said, in the upcoming iNav 2.4 release (due out around the end of February), they have implemented the ability to use RPM filtering which needs to make use of telemetry data that comes into the FC from the telemetry signal connection, so for that so be reliable I would expect them to have bolstered up DShot implementation in some way. So when iNav 2.4 drops I would give that a go with DShot and see if it then works more reliably. No guarantee, but certainly worth a try.

Yes, all due respect the the developers. I am going to add the BB logs to my post in hopes someone with experience can tell me what exactly caused
it to drop, i'm curious that i did not get a warning before, during, or after that something was/is wrong. I looked at them, but with no experience in BB logs I wouldnt know a good log from a bad one.
 Possibly 2.4 will have a fix.
Thanks for the info.