FQ777-124 Pocket Drone

Does anyone know if the FQ777-124 Pocket Drone is supported in Deviation? Here is a link to the quad.

www.banggood.com/FQ777-124-Pocket-Drone-...er-RTF-p-977881.html

I just got mine today. It's like a Cheerson CX-10 clone with way more power. It looks like it has enough power to handle some wind. It also has headless mode and return to home.

I haven't seen anything on here about it being Deviation compatible but...
This review says the FQ777-124 has "CX-10" printed on the green circuit board.
He tried the Deviation CX-10 protocols, with no luck.
Maybe it wouldn't be that difficult for somebody to mod the CX-10 green protocol.
www.rcgroups.com/forums/showthread.php?t=2432513

I hope somebody gets a protocol working for it. I love flying my CX-10 with my Devo 8S, and this one looks like it could be twice as fun.

This one does seem like it will be a very nice flier once Deviated.

The included transmitter is pretty bad, as usual.

I've checked the protocol - does not match with anything found in deviation yet,
which means this needs a new protocol, not an option to an existing one.
Uses NRF, 4 channel fixed hopping (4D, 43, 27, 07), bind Address E7 E7 E7 E7 67,
sends 8 byte packets every 0.002 s (gosh, that would be 500 Hz, have to recheck that one).
20 xx xx xx ID ID ID CS on bind
then switches TX ID to ' ID ID ID E7 67'
and data packets are
00 AA BB CC DD EE 00 CS
center values are 0x32 (50) for AA-CC, did not check any further yet.
Very simple protocol, I'll need to hook up my MM to Devo and give it a try ...

Great news! btoschi, thanks for taking the time to tackle this protocol. I'm sure many will be grateful for your effort.

It would be so nice to fly this little hot rod Deviated! And many thanks to all Deviation developers.

Yes. I picked one up because the reviews were good. Seems like a very nice flier. The stock transmitter is crap, as expected. (Kind of ruins the whole pocket-able thing.) So she sits and waits for her Deviation. Otherwise she will likely be prematurely crashed and destroyed.

Why don't the reviewers mention how crappy the transmitters are? If they did perhaps the manufacturers would start making better ones.

Just a short update on this:
I have create a simply protocol which replays the init from SPI trace (well, the known parts, see below),
but it does not work yet.

It seems that I have a completely different FC and RF chip on my FQ777 "Pocket drone" than what SeByDocky has in his pictures:
www.drone-maniac.com/fq777-124-pocket-drone/

My Transmitter has "SJ-SF121T2.4G V1.1" "20150327" printed on the backside of the PCB,
layout slightly differs, the RF daughter board is different. No way to look at RF chip w/o breaking it up.

Then I opened up my quad and peeled off the white stuff which holds the quartz down to the RF chip.
The marking reads:
"SV7241A"
"SOA5m" (not 100% sure about the 'm' here)
"S592"

This seems to be SSV7241 2.4 GHZ GFSK TRANSCEIVER from South Silicon Valley Microelectronics.

Note that the Quad's PCB is red (which can be seen from outside), contrary to the green board found in others.

As I have sniffed SPI on the transmitter side I can confirm that this chip
must be a nRF24 clone, but it uses yet unknown registers.
Only programming the known ones on nRF24 does not work out ...

Here's the init sequence with first (bind) packet.
1F xx seems to switch register banks, a datasheet should help out here.

Anyone else who can see a glimpse of red on his quadcopter's PCB,
so further investigation is of some use ?

I have ordered mine from banggood in july 2015 (red canopy).

Edit:
Found that the Nuvoton M452 Quad Copter Dev board uses the SSV7241, source code available at nuvotons site.
Unknown registers mostly matches what their 'Initial_Reg_Array' (simplified) does.
No docs, so still I need the datasheet to understand if that can be nRF24 compatible, or not.

btoschi wrote: ....Anyone else who can see a glimpse of red on his quadcopter's PCB,
so further investigation is of some use ?....
.

I ordered mine from Banggood in Sept 2015. It has a red pcb in the quad. It's also the red canopy version.

Wonder if there is any progress on the FQ777 protocol

btoschi wrote: Anyone else who can see a glimpse of red on his quadcopter's PCB,
so further investigation is of some use ?

I have the red PCB one, and can do some sniffing if necessary with the logic analyzer.

BTW would this datasheet help?
www.51wendang.com/doc/17acf0aab9524ce68d2de3cc

Download doesn't work, but the document can be browsed online.

pawelsky wrote: Wonder if there is any progress on the FQ777 protocol
...
I have the red PCB one, and can do some sniffing if necessary with the logic analyzer.

Init and bind sequence of another copter could be helpful, even though I still had no good idea how to make this work.
Currently thinking of using arduino and TX's RF chip for further testing, but mainly I'm missing a tool to sniff data on the air
to understand what's going wrong there ... ideas on how to do this w/o too much hassle are welcome

btoschi wrote: Init and bind sequence of another copter could be helpful, even though I still had no good idea how to make this work.

If the datasheet I've linked in my previous post won't help I can record the init/bind sequence, but would you mind sharing some picture of where the SPI lines are to connect the analyzer to?

Sorry for non-answer. I was inattentive to the previous discussion.

No, this datasheet is not a real datasheet, but a brief description. It does not describe radio well enough. So either SDR is needed, or some other sniffer based on nRF24 can be used.

victzh wrote: No, this datasheet is not a real datasheet, but a brief description. It does not describe radio well enough.

Hmmm, 34 pages of brief description? It looked pretty detailed, but I guess pictures are missing when you browse it online.

Anyway - if I can help somehow - let me know.

EDIT: I wanted to try this downconverter before, so I think I'm gonna give it a go. Ordered...
blog.cyberexplorer.me/2014/01/sniffing-a...ng-nrf24l01-and.html

The downconverter has arrived and I can see some communication going on when I turn on the FQ777. Need to find some time to look deeper into that.

Will the PDF version of the short datasheet be of any help or are the undocumented reserved registers (0x19, 0x1A, 0x1B, and 0x1F) the ones that need to be known?

drive.google.com/open?id=0B4toKKKJwI9jWn...SGY4dEMtdkN1bXEwNWFj

If this thing gets deviated i am pretty sure tears of happiness will come out of my eyes. I love this little thing but hate the transmitter big time.

The only problem is that it seems there is two boards and I am not sure if both are on the same protocol

Same here. The small quad been sitting on my desk for a while now.

Some updates on this topic - not too good news, though.
Need to dig into the dirty details on FM Transmission now ...

I have my own code on Devo 8S running protocol following SPI Traces (with some unknown registers) and the original Transmitter running,
sniffed both using SDR# (on linux with mono 4.2), tuned to NRF Channel 7 (MMDS LO Freq is 1998Mhz) and zoomed up to same details.

Original Transmitter:


Devo witt NRF:


One can easily spot that these signals are no way tuned to the very same frequency,
and they clearly do not look anywhere like the captures on the NRF24 sniffing page .

Someone with RF knowledge can help me out here ?
Both signals should be GFSK, but I cannot identify it at all ...

Just as a side note: the nrf24-btle-decoder cannot identify any meaningful frames (prints random garbage) - even with my Devo code.

I kinda figured this was the case. I have been playing around with a few nrf24l01+ modules and one ssv7241 extracted from a tx. I modified the nrf24_multipro code to also be a receiver (for bayang protocol) and was able to receive bind packets from an H101 tx with the ssv7241. But as soon as the channel changes nothing comes in (I did not modify the reserved registers in this case).

I also implemented the nrf24l01 "promiscuous" mode to try and sniff packets but when I use this code with the ssv7241 it doesn't seem to receive many and they all seem like garbage.