Mike, just to be clear, the Exceed/Flysky is only blocking one DSM2 channel (2.432 Ghz), not both. So this is exactly the same test you ran with an AV transmitter, except my DIY did not change the channel to avoid the conflict (2.432 Ghz). Is your module one of the beta test samples? If so, I've seen lots of posts on RCG indicating the beta units did indeed change to a different channel to avoid a conflict. But I've seen zero posts to date that a factory production unit like mine will ever select anything other than the two default DSM2 channels. According to Lemon the two default channels are selected by an algorithm that uses the unique ID of the transmitter module. I'm being told by Lemon that the transmitter modules scan the band to look for the quietest channels, and then select two of those for DSM2. The video proves that this is simply not true for this particular DIY module, and it's not true for any of the other five production version modules that I have. Each of the six modules happened to end up with different default DSM2 channels, but each module always chooses the same two default DSM2 channels, no matter what.Mike_K wrote: ↑29 May 2021, 08:02 Hi Dave
You have virtually repeated my earlier experiment, except I used a 2.4GHz analogue FPV AV transmitter to select a single channel to block, not block both channels. Mine succeeded in moving the channel being blocked by the AV signal (but the other remained the same).
I know the Exceed/FlySky FS-CT6A transmitter does not use DSM2, but I do not know what protocol it uses.Mike_K wrote: ↑29 May 2021, 08:02I can't dispute what you're finding, but what does trouble me is that the FlySky should only be actually transmitting for a short period of each frame, typically a millisecond or two every 20mS or so and also the LemonRx will only be transmitting for 1.4mS every 22mS, so even if they happen to be on the same channels, the chances of the packets actually conflicting is still small. What protocol does the FlySky use, it isn't DSM2 is it?
But to me the issue isn't that time sharing of the packets aren't able to cope with the channel conflict.
To me the real issue is that the production versions of the Lemon modules are ignoring the maximum possibility of RF interference by selecting one of it's two DSM2 channels on the exact same channel as the FlySky, even when the rest of the band was clear. In this case, the maximum possibility of channel interference was on 2.432 Ghz, and yet the DIY module selected 2.432 Ghz anyway as one of it's two DSM2 channels.
This sums up everything that I have been asking for from the beginning.
Thank you very much for your reply!