7e NRF24L01 instalation failed "Missing modules"

Hello.

So I installed this www.banggood.com/DEVO-Transmitter-Tuner-...ys-V922-p-89812.html following this www.hacksmods.com/2013/05/nrf24l01-devo7e-pinout/

then went to hardware and erased the semicolons and I have this:

;Only useful for transmitters with an after-market vibration motor
;enable-haptic=1
;
;switch_types: 3x2, 3x1, 2x2
;extra-switches=
;
[modules]
; there is no need to enable the cyrf6936 module unless
; it is wired to an alternate port. It is Enabled automatically otherwise
; enable-cyrf6936 = B12
has_pa-cyrf6936 = 0
; enable-a7105 = A13
; has_pa-a7105 = 1
; enable-cc2500 = A14
; has_pa-cc2500 = 1
enable-nrf24l01 = A13 has_pa-nrf24l01 = 1
; enable-multimod = A13
I turn on the transmitter and get modules missing: NRF24101 at start up

I have rechecked all the wiring, everything is connected like in the pictures from the link. So I have no idea what is going on. Hope you can guide me to discover the problem or if this something that happens often and there is a fix.

thank you

now I have this in hardware

;Only useful for transmitters with an after-market vibration motor
;enable-haptic=1
;
;switch_types: 3x2, 3x1, 2x2
;extra-switches=
;
[modules]
; there is no need to enable the cyrf6936 module unless
; it is wired to an alternate port. It is Enabled automatically otherwise
; enable-cyrf6936 = B12
has_pa-cyrf6936 = 0
; enable-a7105 = A13
; has_pa-a7105 = 1
; enable-cc2500 = A14
; has_pa-cc2500 = 1
enable-nrf24l01 = A14 has_pa-nrf24l01 = 1
; enable-multimod = A13


I changed the A13 to A14 but still it says module missing

Multirotor Go wrote: ...
enable-nrf24l01 = A13 has_pa-nrf24l01 = 1 ...

I'm probably the last guy on this forum to be offering advice, but here's what I see:
The portion of your quote (above) that reads, "has_pa-nrf24l01 = 1" should be on a line by itself, I believe, rather than tagged onto the end of the previous line. See if changing that helps.

thank you

well I don't think that matters, since actually in my editor I see everything on a single line. And I see here that it is shown as I see it on my editor at 15:15

I went back to A13 . I got confused. A13 is the correct one. still missing.

Multirotor Go wrote: ...l I don't think that matters, since actually in my editor I see everything on a single line...

Ah, yeah, OK. Took my best shot, now I'm out of ammo

Multirotor Go wrote: thank you

well I don't think that matters, since actually in my editor I see everything on a single line. And I see here that it is shown as I see it on my editor at 15:15

It does matter how you edit ini file!

What you using to edit ini?

the default program that window 8 uses, the sames as in the video I posted.

www.pnotepad.org

Start again with a fresh copy of ini.

Sure coders will give correct answer as to why it matter but to rest of us looking right don't make it so

Now still may not work....
Just reflux all solder joints and reflow solder. Looking for nice and bright solder.

I replaced the hardware ini with one from a friend that has his devo 7e working with this modules and still is doe's not work. Maybe banggood send to me a bad one

That would mean to me like 2 more month to have a new one here. How can I know if the module is working ?

Unfortunately module's can be doa but check install and solder joints..dry joints are just as likely as doa module!

No easy way to test modules.

Would taking module out of the working tx an option? Or did you get bind and fly... Could get you going till replacement arrives.

Nah to complicated to me. solder joint look ok, well they are far from perfect but still not that bad to the point were thing could not be recognized. I will re, re, recheck the thing and redo everything again it seems I don't have another option

Take break, kick the cat.... Only joking
Honestly dry joints get everyone

I had the exact same problem installing the nrf in a devo12 and no matter what was tried it would not work...i took the module out and put it in my devo8 and it worked fine i rechecked and rechecked and rechecked but it would never work and to this day it still does not work in my devo12....i bought a 12s and put the same module in it and it works perfect....never did figure out why the 12 would not accept the module...only thing i could figure is it is one of the early production devo12 models and there is something different about it versus the 12s...so i gave up on it and accepted defeat... but the module is still working perfect in my 12s..

EDIT: Heads up you don't have to wait months to get a new module they are available here in the U.S i bought 2 off Ebay and they both work great....have one in my 12s and the other in my 8..

Well I am not from US and around here this exact module is not available. I have the 7e not the devo 12 mmm l will try to redo everything and in the mean time order another module

Instead of trusting a 2 year old article on the hardware install, you might check the official documentation, which is updated regularly as the software changes: bitbucket.org/PhracturedBlue/deviation/wiki/ModuleInstallation

In particular, the module wiring he use dates back to the 4.0.1 release, which doesn't use hardware.ini. It's been over a year since that was correct for the nightly build. While it can work with the old wiring, the exact behavior will depend on the protocol, and some have reception problems, possibly bad enough to cause binding issues.

as far as i know the wiring for the nrf module hasn't changed.

Multirotor Go wrote: the default program that window 8 uses, the sames as in the video I posted.

You can do a lot better than notepad.exe that comes with Windows, even though you are probably 100% correct with your changes. I found Notepad++, an open source editor that really works well for things like config files.

I installed the same module using the same directions into my 7e sometime during the Spring of this year. It worked without any problems with the nightly builds available at the time. Some weeks or months later, I added an A7105 module (correct no. ??) and it gave me an indication similar to what you have. I checked it over and over, and all of the wiring was correct. Out of desperation, I changed the module position, A13/A14, by moving the wires at the CYRF module. After that it worked, and has continued through the current nightly builds.

I don't have a clue whether there was an problem I corrected by moving the two wires, or if there was a conflict with the nightly builds. It is probably a long shot, but possibly worth trying before you do something major.