New WLToys Protocol V977

I've got IT !!!

My mistake was that i didn't matched the address but the payload with arduino library.... I wrote the functions to access to the nrf24l01 and it's work... i can see the correct binding packet

Thanks a lot for your code and your support

It's work

Hello,

I tried communicating with RCgroups people but I found massive circlejerk instead. People here seems to be much more potent with modding.

I got my personal idea for this project:
Getting into RX(maybe TX?) firmware and make life easier for devo to work.

Has anyone tried interfacing with v977 PCB? Very much possible that it's common PS2 interface(GND, CLK, DIO, 3.3V) Data is bidirectional, start byte at 0.
You can put TX into service mode(flashing possible?), I haven't found out yet if it does the same with RX. I WISH I could have more time to tinker with v977, unfortunately my life

Hello everyone
recently got t v977 bnf from banggood with the nrf module.
The soldering was done ok I would say but for me is still not clear(seen several versions) if from the nrf module the pin5 ground must go to the walkera module pin3 as below or not? This is how I did mine:

I loaded this nigthly build which for me is still a bit of mistery due to missing documentation and I can say that sometimes the bind just gets lost between my devo 10 and the heli. Another issue I have is that I could never get to take off since either the motor doesnt start or when it spools up it suddenly stops(pitch still changes even if motor is stopped). Another issue is that sometimes on startup I got the "program update" logo that the dfuse process gives - without updating anything and also I got some missing module error message.

To be honest much fuss and big chances to fail on the transmitter or loose the bind and heli mid-air...I know also this build is supposed to be unstable but I could never trust glying my 500 heli with this just expecting some binding loss or some restart furing flight. Tried going back to stock firmware but got some strange font error.

Please let me know if my pinout is correct or not, and / or if I am doing something wrong here?
Thanks

Hello. I am using my Devo 10 with Deviation release 4.0.1 with two RF modules installed (NRF24L01 and A7105). I bought V966 BNF microheli and from this forum I found out, that I need to install "nightly build". I am probably doing somethig wrong. I thought I just copy new files into Tx, but I can't still choose KN protocol. How can I check that I have correctly installed new version?

from the main menu select about Deviation I think it should read:
devo10-v4.0.1.
Also check hardware.ini is setup for new Tx modules.

FW version hasn't changed since I am using V4.0.1 from the beginning.
I noticed that I should check hardware.ini file, but I am not sure about its setup. Before upgrade there was only tx.ini in my Tx:

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

Default hardware.ini now shows:

; enable-cyrf6936 = B12
; has_pa-cyrf6936 = 1
; enable-a7105 = A13
; has_pa-a7105 = 1
; enable-cc2500 = A14
; has_pa-cc2500 = 1
; enable-nrf24l01 = A14
; has_pa-nrf24l01 = 1
; enable-multimod = A13

Do I have to remove ";" in specific lines to enable these modules?

Now I noticed that new tx.ini and my old tx.ini have different structure, not only removed module setings. Should I overwrite old tx.ini and recalibrate my transmitter? My Tx performs now like before the upgrade-I can use enabled modules and control my HCP80 microheli with HiSky protocol.

did you use the DFuse program to flash the new firmware.
After you do that, than copy the new files.
To get the extra modules working you have to change the hardware.ini.
There should be no mention of the modules in the new tx.ini.

PS you should recalibrate your sticks and knobs.
Don't forget to save your models, so you can copy them back.

It is strange. Should nightly build include KN protocol? I can't still choose it. Hardware.ini file doesn't enable RF modules in my case. Instead of this transmitter adds module enabling section to tx.ini file itself. I can make modules active only when I enable them in tx.ini file.
What am I doing wrong?

than you did not flash the firmware with DFuse.
your still on 4.0.1.
Not a nightly.

I thought, once the Deviation FW is flashed with DFuse, then you upgrade just by copying files. Am I not right? It is written in manual.

Sorry, No.

for every version you have to flash with DFuse and copy files.
The only thing you can keep are the models and ico directory. Or better save them on harddisk and copy them back when you finished.

OK. But another issue is that DfuSe don't recognize my transmitter. I tried it on 2 different notebooks, one with WIN7 and second with XP. Computer detects only USB device, but DfuSe nothing

Press EXT and power on TX

I know it and I do it every time when I need to connect to PC.

???

pressing ENT and power on is USB mode
pressing EXT and power on is DFU Mode

you know?

Thank you very much! What a stupid mistake. Two different letters make big change!

@Wene001 - that was real customer support magic! To be able to make a hypothesis when customer is sure that he's doing everything right requires insight.

Be sure to use the upgrade button in DFUse Tool (not Update)
then everything is goin smooth.

@victzh - Thanx for the flowers and your great work

I have already a nRF24L01 with build in antenna. Does anybody knows if it is ok? I dont care about range with v977.
it is like this one:
www.ebay.fr/itm/nRF24L01-Wireless-2-4GHz...%26sd%3D131185014323