Devo10 ESky protocol draft

good news

we are two interested now... i'm sure that will be others...

Make that 3 interested persons

I would like to be able to fly my HoneyBee V2 with the devo7e

OK, I heard you.

Please try and report success/failure for the attached builds for Devo 10 and Devo 7E.

hi victzh

i've tried the version 7E and it Power On but i don't have Main Menu... nothing appears...

Hi Victzh,
after installing the 7e files, the 7e will power up but the same problem as dremaer, hit ENT button and devo goes to the main menu which is blank, if I hit ENT again the 7e appears to turn off

Yea, I saw it myself. Strange, Devo10 did not do this. Can you check nightly build, does it behaves strange as well.

And do not test deviation-devo7e-v4.0.1-bd281d2.zip, it can be OK. I'm interested in the next one (when it appears). It can have name deviation-devo7e-v4.0.1-e1e910c.zip.

Scratch all that.

Take last nightly at www.deviationtx.com/repository/func-startdown/1707/

Copy 'media' directory from it to your Devo 7E. It should fix the menu problem.

Copy 'protocol' from mine zip file and Upgrade from it also.

It would help if you copy 'layout' also.

installed and at first sight works well. however i can't go further because i'm waiting my NRF module.
a question: it's the Esky150 protocol that i should take for my belt cp right?

dremaer wrote: installed and at first sight works well. however i can't go further because i'm waiting my NRF module.
a question: it's the Esky150 protocol that i should take for my belt cp right?

And i almost forgot to tell...
Thank you...

dremaer wrote: installed and at first sight works well. however i can't go further because i'm waiting my NRF module.
a question: it's the Esky150 protocol that i should take for my belt cp right?

No the ESKY150 is corresponding to the new ESKY protocol. Please download the beta version from the Victzh msg

well

after this update i tried to bind with my v911 but it won't work... i went to "Model Setup" and *FlySky had a star before means i think "module not installed". I went to TX file and i have the module activated.


[modules]
enable-cyrf6936=B12
has_pa-cyrf6936=1
enable-a7105=A13
has_pa-a7105=1
enable-cc2500=None
has_pa-cc2500=0
enable-nrf24l01=None
has_pa-nrf24l01=0

what could it be?

If you are using the nightly build, the parameters have moved to the hardware.ini file. So set them there and it should work.

dremaer wrote: well

after this update i tried to bind with my v911 but it won't work... i went to "Model Setup" and *FlySky had a star before means i think "module not installed". I went to TX file and i have the module activated.


[modules]
enable-cyrf6936=B12
has_pa-cyrf6936=1
enable-a7105=A13
has_pa-a7105=1
enable-cc2500=None
has_pa-cc2500=0
enable-nrf24l01=None
has_pa-nrf24l01=0

what could it be?

You are right .... There is a bug for my Devo 7E to bind the Esky150 (missing module). It's working with my Devo10. I am using the 15 june NB ....

Of course I tested other protocol nRF24L01 based such as V2x2 or Sky Wlaker and it's working with my Devo7E...

SeByDocKy wrote:

dremaer wrote: well

after this update i tried to bind with my v911 but it won't work... i went to "Model Setup" and *FlySky had a star before means i think "module not installed". I went to TX file and i have the module activated.


[modules]
enable-cyrf6936=B12
has_pa-cyrf6936=1
enable-a7105=A13
has_pa-a7105=1
enable-cc2500=None
has_pa-cc2500=0
enable-nrf24l01=None
has_pa-nrf24l01=0

what could it be?

You are right .... There is a bug for my Devo 7E to bind the Esky150 (missing module). It's working with my Devo10. I am using the 15 june NB ....

Of course I tested other protocol nRF24L01 based such as V2x2 or Sky Wlaker and it's working with my Devo7E...

i have 2 files from this date...1126.0kb and 773.3kb. wich?

forget my question...

since a while i try to solve this but i can't. my A7105 don't want to be reconized. however with 4.0.1 version it works fine.

OK, did anyone have success with my builds for ESky protocol? Once again - take 'media' directory from the nightly build, 'protocol' and dfu from my zip.

hi victzh

i've tried just like you said on my Devo 7E and no major issues. however i can't bind my v911. i checked .ini file it's ok, and in model setup, the A7105 protocols have a "*" after the name like "*Flysky", "*Hubsan4", "*V202". it's normal?
but if i retrograde to 4.0.1 version my v911 binds and the "*" disappears.

Did you modify hardware.ini accordingly? Nightly build differs from 4.0.1 in this, the section about modules moved from tx.ini to hardware.ini.