JJrc345 drones as gift in return for protocol.

Seems to be same results. Binds and takes off fine. Aileron seems to activate flip but also flips on its own.

I'm thinking about trying a model ini like E010 where channels 5 and 6 are already configured for flip and d/r. I'm not sure if that's related but I am trying to figure it out with what I can do. While I await your latesr response

Thank you for your time

Will try. Are there any dumps that I can redo that will help you so deep erratic flip. Please let me know I am willing.

It sounds like a great option. I will try your test build soon. Thank you. Chris

I tried the latest build. The results remain the same. Channels respond correctly but erratic flipping still remains. I suspect this is fixable and will check back soon to see how I can help. Thank you. Chris

Hi Chris,

attached is another special non-modular dumping build for your 7e (it doesn't contain goebish's protocol). It has the updated XN297DUMP protocol which will allow dumping to the file "datalog.bin" on the devo's filesystem. Since I made some changes to the interface here is the instructions on how to use it:

1. Choose a free model file for the dumping (already did that previously)
2. Go to protocol options, set "Bitrate" to 1 Mbps, "Address" to 5 byte and "Scrambled" to yes
3. Enter XN297 Dump in the Transmitter Menu
4. Bind the JJRC tx.
5. Set "Off" to "Scan" (Press right twice) and then press ENT to start scanning. It will stop scanning on a valid channel just as before
6. Now move the Mode selector from "Scan" to "Man" (press left once) and push ENT again. This will start recording.
7. Move each individual stick on the jjrx tx independently slowly from min to max. Make a little pause between the sticks. Also record the buttons just as you would use them with the quad (as in doing flips, setting different rates etc.) Please write down the order in which you recorded all the stick transitions and other states.
8. When finished, press ENT again on your devo, connect to the devo USB drive and copy the datalog.bin and paste its contents here or attach it together with the description of what you actually recorded in it (you will have to rename datalog to .txt or the forum won't allow uploading it).

Please note that recording space in datalog.bin is somewhat limited, so you might have to split it up in two sessions.

Looking forward to finishing the protocol work, please bear with us.

Hello, any updates? I have also basic MX5323 transmitter and would like use my DEVO 7E instead

Hi,
this protocol uses a lot of toys.
Specifically, the micro car Velocis 1:32.
Pascal Langer has this hardware at his disposal and his statement was
"Looking over the air the TX transmits 3105 bits which is 389 bytes! There must be some correction encoding in place or special encoding which none of the components will emulate".
George

Stanek wrote: Hi,
this protocol uses a lot of toys.
George

Yes, but anybody has SPI trace or dump? how to understand and emulate protocol?

There is no trace, this transceiver contains an MCU inside the RF. Only data transmitted and captured by air. Anyone who owns a 2.4Ghz SDR can analyze this data.

Stanek wrote: Only data transmitted and captured by air. Anyone who owns a 2.4Ghz SDR can analyze this data.

For SDR you need some software decoder, its not so easy to analyze raw signals.

I see special firmware for DEVO7e above, us I understand it can help obtain dump or not?

I've seen such a nice decoder at Goebish for XN297

https://github.com/goebish/XN297_dumper

More easy way use Arduino + NRF24L01 + MULTI-Module code github.com/pascallanger/DIY-Multiprotoco...er/docs/Compiling.md
XN297 dumper mode included in firmware github.com/pascallanger/DIY-Multiprotoco...vanced_XN297Ldump.md

As I understand MX5323 chip has embedded XN297 radio.