Devo 7E and esky 150

I cannt bind the esky 150 even if I installed the nRF24L01+PA+LNA chip. Will there be an update for Devo 7E to bind it correctly? I'm a mode 1 flyer, totally cannt fly mode 2 default transmitter:(

Tried to switch the stock tx to mode1? Should,be possible!

Yes there is a small bug for the Devo7E ... Victzh who did the hack seems to involve in different projects now ....
What is strange it's working for a devo10 not for the 7E ....

It's hard to debug - I don't have nRF24L01 installed in my Devo 7E yet, and, mainly, I don't have Esky 150!

What specifically does not work?

victzh wrote: It's hard to debug - I don't have nRF24L01 installed in my Devo 7E yet, and, mainly, I don't have Esky 150!

What specifically does not work?

Not binding ....

The Esky 150 protocol works for the Devo 10 radio. Binds fine.

But the Devo 7e won't bind when using that same protocol.

I thought this thread is dead

Thanks for all the reply. Yes, it doest not bind the heli. Try Fix ID and None also doesn't work.

Disassemble the default TX, if want to mod from mode 2 to mode 1 there will be lot of works. Need to shit whole left stick to right involve soldering and some wiring.

Concerning the Devo7E problem, ... I can feel it's a syncrho problem.
I mean maybe by increasing/decreasing some time delay used during the protocol setup....

sonyv12002 wrote: I thought this thread is dead

Thanks for all the reply. Yes, it doest not bind the heli. Try Fix ID and None also doesn't work.

Disassemble the default TX, if want to mod from mode 2 to mode 1 there will be lot of works. Need to shit whole left stick to right involve soldering and some wiring.

Actually, maybe not. Check that you can't just move the spring which keeps the stick in the middle position from the right stick to the left.

SeByDocKy wrote: Concerning the Devo7E problem, ... I can feel it's a syncrho problem.
I mean maybe by increasing/decreasing some time delay used during the protocol setup....

Funny, no other protocol has this problem. As I don't have the heli, even the receiver board, I can't check it. I was amazed that our distance debugging worked for the protocol reverse engineering, but this case seems to be harder. You'll need to get traces from Devo 10 and Devo 7E and we'll need to compare them and find the difference.

sonyv12002 wrote: I thought this thread is dead

Thanks for all the reply. Yes, it doest not bind the heli. Try Fix ID and None also doesn't work.

Disassemble the default TX, if want to mod from mode 2 to mode 1 there will be lot of works. Need to shit whole left stick to right involve soldering and some wiring.

Check this thread - it's couple of screws:
www.helifreak.com/showthread.php?t=554545
and it's actually in Devo 7E manual

victzh wrote:

SeByDocKy wrote: Concerning the Devo7E problem, ... I can feel it's a syncrho problem.
I mean maybe by increasing/decreasing some time delay used during the protocol setup....

Funny, no other protocol has this problem. As I don't have the heli, even the receiver board, I can't check it. I was amazed that our distance debugging worked for the protocol reverse engineering, but this case seems to be harder. You'll need to get traces from Devo 10 and Devo 7E and we'll need to compare them and find the difference.

How to get traces ? In debug mode ?

victzh wrote:

sonyv12002 wrote: I thought this thread is dead

Thanks for all the reply. Yes, it doest not bind the heli. Try Fix ID and None also doesn't work.

Disassemble the default TX, if want to mod from mode 2 to mode 1 there will be lot of works. Need to shit whole left stick to right involve soldering and some wiring.

Check this thread - it's couple of screws:
www.helifreak.com/showthread.php?t=554545
and it's actually in Devo 7E manual

Sorry I mean the stock TX from Esky.




I love the 7E, but thinking to upgrade to devo 10. Have a spare is not a bad idea.

I recently received the ESKY F300BL for reviewing and they change the protocol even based on the RFchip. I am sure, they just changed some Id packets, basic stuff like this.

Victzh, I can sniff SPI data in case ?

Hi SeBy, sorry for reopening this thread so late.
Are you still able to capture SPI data from ESKY F300BL and pass them to Victzh so he can also implement this protocol small variation ?
Thank you so much.