I recently posted a problem with a devo 10 install of a 4 in 1 module that displayed a missing NRF24L01 module. After several hours I located a posting that helped somewhat allowing the NRF24L01 be recognized. My original hardware file looked like this when uploaded from the 5.0.0 build.
;Only useful for transmitters with an after-market vibration motor
;enable-haptic=1
;
;switch_types: 3x2, 3x1, 2x2
;extra-switches=
;
;Audio player connected to UART (Devo12/S internally, others via trainer port): audiofx, dfplayer
;voice=
;
;Enable if audio device is wired to uart5 instead of ppm on devo7e-256
;voice-uart5=1
;
;button_types: trim-all, trim-(left|right)-(up|down|both)
;May occur more than once if necessary.
;extra-buttons=
;
[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 = 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
The fix? I guess that allowed the module to be recognized was due to the enable-nrf24l01 = A14 being incorrect? The post that I found on deviation said it should be enable-nrf24l01 = B7. The devo can recognize the NRF24L01 and bind to models but has trouble staying bound and the models fly in a uncontrollable cirular motion rendering them unsafe. Have no idea why. Any help is greatly appreciated.
