WLToys Q282G micro hexa 5.8G FPV

Lynxie wrote: Thanks with new v686g works well. But i dont found X and Y calibration.
5 - lights
6 - flips
7 - photo
8 - video
9 - headless
10 - RTH

Thanks for the report. How is calibration done? If it's stick commands they may work. Otherwise we'd need SPI captures.

hexfet wrote: I added the updated CX10 protocol to the protocol_combo test build. You're welcome

Hi Hexfet,
Combo build works fine,thank you very much!

hexfet wrote: Thanks for the report. How is calibration done? If it's stick commands they may work. Otherwise we'd need SPI captures.

Calibration made by long press on button. I will try make dump at evening.

Just tested on my Q282J and it's working perfectly
I tested also the blue-A option on the CX-10C .. working well but no camera triggering ...
I guess we need SPI data to add these specific flg ?

Actually I was a little liberal and the new code sends the DM007 control bits for the Green and Blue-A modes also. From the reports of success it seems they don't interfere, but I'll clean that up before a pull request Still would like to hear from a DM007 owner.

So it seems the CX-10C doesn't respond to the DM007 camera controls. We'd need a capture.

Lynxie wrote:

hexfet wrote: Thanks for the report. How is calibration done? If it's stick commands they may work. Otherwise we'd need SPI captures.

Calibration made by long press on button. I will try make dump at evening.

I tried make dump with open logic sniffer, but it can capture only 0.3 sec Maybe I will write some utility to stm32discovery for capture this data.

I managed to find saleae X and Y calibration dump www.dropbox.com/s/44rkdl9kiszpze4/v686rev2_calibration.zip?dl=0

Can you list the steps of how calibration is done? What I see in the captures is the X calibration bit being set, and in the Y capture that bit is still set when another bit also changes to 1. If that happens just by holding down one button, if you want the same behavior you'll need to emulate it with mixers.

I put the X calibration bit on channel 11, and the Y bit on 12. The q282 test build is updated.

Your tx also uses the same RF channels as the q282, but a different txid. So in this build the txid is set randomly. Let me know if you see any issues with binding.

Enable is on channel 3 in the SPI captures.

In both these and the q282 captures the MISO data is all zeroes. But it's not used anyway

hexfet wrote: Can you list the steps of how calibration is done? What I see in the captures is the X calibration bit being set, and in the Y capture that bit is still set when another bit also changes to 1. If that happens just by holding down one button, if you want the same behavior you'll need to emulate it with mixers.

I put the X calibration bit on channel 11, and the Y bit on 12. The q282 test build is updated.

Your tx also uses the same RF channels as the q282, but a different txid. So in this build the txid is set randomly. Let me know if you see any issues with binding.

Enable is on channel 3 in the SPI captures.

In both these and the q282 captures the MISO data is all zeroes. But it's not used anyway

Its awesome, all work very well:) Calibration starts each time when I change channel state, for example: if I change 11 channel from -100 to 100, calibration start, and when I change back from 100 to -100 its start again. And same for 12 channel. Now I'm waiting for combo protocol build Thanks

Thanks for testing I've updated the combo test build.