BetaFPV 65s DSMX Just Don't Wanna Fly!!!

[LuMan]

I'm about ready to chuck the towel in with this one!!

I got myself one of these BetaFPV 65S whoops a few weeks back, so I could FPV my way around the garden (I've mentioned this in other posts). Since getting it, I've bought a new FRSky D8 compatible Tx.. To no avail, as my version is DSMX    and also a multi-protocol unit, which I've now fitted.

The culprit!



The "solution"



Aside of how it looks, the multi-protocol unit is working as intended, and has been set to DSMX mode (No.8 on the selector), as opposed to the SRSky/Spektrum mode (No.5). To be sure, I attempted binding in both modes. It does actually bind in DSMX mode. This much I know.

Within Betaflight, I can see pretty much everything working as it should. However, when I check the controls, the levels don't move smoothly. They jump between the initial/default values and the value I've set. I've tried to capture this in pics, but a vid might be better:

This is where the controls SHOULD be:



But - they're not. They flick between the above and the below every second or so:



It's like the input hasn't been received for a second, then is, then isn't again.

I've tried:
- refreshing the FW with ALL of the available F411 options. No change
- Turned off everything that could use CPU cycles, although, the CPU is only hitting 15% max
- Set the sampling to 2kHz and 0.5kHz for Gyro and PID
- Tried various receiver options, but none of them will bind, except for the Spektrum2048 option.
- Motor tests work fine (this is how I know I've got the right FW loaded).
- Used the suggested CLI dump from the BetaFPV support page for this FC.
- Sacrificed next door's cat while dancing naked around a George Foreman grill in the back garden at last full moon*

Before I stamp on the little f..f...flying thing(!) has anyone got any ideas? If anyone has got a suitable controller I'm willing to post it out so you can test whether the unit does actually work (I'll include return postage too).

Just a bit pee'd off that a simple thing I got to make lockdown more bearable has made me bloody greyer!!

Thanks in advance
Worried Bros fan.. Oh, hang on... wrong forum...

Cheers
LuMan

*I made that bit up. It was a Breville sandwich toaster...

[ched]

You just thought that George Foreman sounded posher didn't you   

Anyway back to the devil quad. This may be a silly suggestion but it might help in diagnosing the issue. I think you are running FlySky on other kit? Set the mutimode to FlySky AFHDS2A and see if it binds to some other rx and see if that works in BF. If it does without any jumping about then the module and it's connection to the tx looks OK.
If it still jumps then either the module is misbehaving or the connection to the tx is iffy.

I think this is the correct pin config for the i6 tx:
 

Double check you have it connected correctly.

Did we come to the conclusion that you couldn't connect an external rx?

[Bad Raven]

I have a FlySky FS-i6 that does std and 2A.  I also have a DX6i DSM2/DSMX, two DSM2 DX7 and a DSM2/DSMX DX9. Also two Horus X12S with multi-modules.

Oh and I have fought a 65X brushless and a HX115 into submission after 24 rounds of bloody noses and total exhaustion.

My local group consider I'm an "expert" in fixing Tiny6/7/8 quads as I have managed to sort quite a few that refused to fly, but then they don't see me blundering around muttering old Greek incantations wielding a highly polished lump hammer while wearing a welding apron and face mask.

OOOPS, gave game away.................

A Singapore based friend gave me several 1960's ENYA glow engines, and I later reported by text that I'd got them all running really well on 25% nitro. His reply was that they were probably too scared NOT to run!!   

Unfortunately I'm in Kent (sister-in-law is in Keyworth but obviously no visiting), but willing to help if you are really really stuck.

PM accordingly.

[LuMan]

@ched - I've set the Tx to both AFHDS and AFHDS2A modes, but no change. I've also soldered the signal lead directly to the PPM-Out pad on the circuit-board (there are a couple of vids on YT about how to do this). I did think about binding to another Rx via the multi-protocol module just after my initial post, but it was getting late and I needed wine....    I also checked that the i6x is working fine by milling my mini 130 around the garden, so I'm happy that the Tx itself is working fine.

I'll try a couple of tests with a couple of other receivers to see if I can rule out an issue with the multi-protocol unit.

@Bad Raven - I've got family in Keyworth, too!    If I still have issues after the next set of tests (and perhaps updating the FW on the multi-prot module) I'll bung you a PM. TBH, sending it down to Kent for you to have a bash at isn't too much of an issue as it's not doing anything at the moment anyway.

Thanks v much for your help, chaps