C-17 Transport

Where is my SDR device when I need it...
I've got hard time figuring out the channels used since there is a lot of bleeding to other channels. The NRF is picking up echo on many channels. I'm running long scans, enough to find out the main channels being used but I'm not sure if I'm missing a channel which could have inteferences with another signal...
Let's see how far I can get.

Impressive how you manage to "puzzle" protocols

Hello. Received my C-17 today. Binds ok with the toy tx it comes with, but unfortunately doesn't bind with my DEVO 10 with latest (8cfcb5d) Nightly Build.
Is it because it is an even newer protocol, or is there something else i must do?

goebish wrote: Probably the newer protocol, Pascal started working on it.

Fastest reply ever Thank you. The C-17 will have to wait then.

The new RX has this reference: GD9001-102RX2. Is that your case?
Pascal

planger wrote: The new RX has this reference: GD9001-102RX2. Is that your case?
Pascal

Where was that written on? If its one the rx, i have glued the battery hatch in place, and it will be damaged if i try to remove it.
Also, the tx is not easy to open too... The sticks are soldered to the lower part, while the opening for the levers on the upper part, is not wide enough to allow the stick ends to pass through. I can not seperate the two parts to have a look at the board. Unless i am missing something...

The reference I gave you was on the RX. One difference that you might remember is the RX antenna. On V1 the antenna is quite big with a dipole at the end (like this abra-electronics.com/images/detailed/142/ANT-21-_1_.jpg ) where the V2 has a simple wire instead.
On V2 I've emulated the bind part but the normal packet mode transmission scheme is extra weird. I will probably look at it again next week.
Pascal

I am sorry, i really can't remember and all i see now is the end of the antenna comming out of a hole in the battery compartment. I can't remember if it is an antenna like the one you showed in the picture, or a simple wire comming out from the rx.

Every time i get a new plane, heli or quad, i take many pictures to see what goes where in case it is needed. This time it was so little efford to assemble the plane that i didn't take any pics... what could go wrong??? (lol).

Ok, I've got the protocol working with only 1 ID for now. I would need other dumps to see if we can figure out a pattern.
Is someone willing to send their TX?

Goebish, do you want to port this work in progress?

Pascal

I need a couple more hours to fully reverse the ID (trial and errors)...
So far I've got some more IDs working with these rules:
- payload xor = rx_tx_addr[0]^rx_tx_addr[1]^rx_tx_addr[2]
- hopping_frequency[0]=0x05+((rx_tx_addr[0]^rx_tx_addr[1]^rx_tx_addr[2]^rx_tx_addr[3])&0x0F);
- hopping_frequency[1]=0x20+hopping_frequency[0];
But there is something more like a check since for some values it doesn't bind at all, for others the hopping frequencies are wrong and others one of the frequency seems wrong.
Enough for tonight in any case...
Pascal

@Fer could you also install the attached build and follow the instructions from this post and post your results here? This could help us in get another address frequency pair to find out the pattern.

edit: you will need to run the scan with 250 kbps.

Moeder wrote: @Fer could you also install the attached build and follow the instructions from this post and post your results here? This could help us in get another address frequency pair to find out the pattern.

edit: you will need to run the scan with 250 kbps.

Going to try it now one my spare DEVO 10. Haven't done this before, and i don't know if it will work, nor if this build is like the nightly builds. I hope i can come back soon with results.

@Fer: have you tried the protocol GD00X, format V2?

Ok, i installed the firmware from the link goebish provided, but in transmitter menu, only goes up to option 5. SCANER, i don't see a 6th option to sellect XNdump or whatever else should have appeared there. Have i done something wrong? Then i copyed again all files (including debug file) on the DEVO and now it is stuck on USB mode. Ahhhh... I am installing firmware again, and i hope to be able to fix it. Sorry, i am trying...

goebish wrote: I just updated the test build in my dropbox folder, it now has GD00X V2 protocol and XN297 Dump.
www.dropbox.com/sh/s0xbf68hkfl5qni/AACNd...HdeIXBiQEXdF5Va?dl=0

Ok, and i managed to get her back in order again. I am downloading this newest firmware, and installing it. Will report soon...