Missing Modules:MultiMods

I reflashed devo 10 with original firmware and then reflashed with the latest nightly build 04/10/2016 deviation-devo10-v4.0.1-g32bb7c.zip. This is my hardware file before editing after reflash ;Only useful for transmitters with an after-market vibration motor
;enable-haptic=1
;
;switch_types: 3x2, 3x1, 2x2
;extra-switches=
;
;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
I am now getting error missing modules CYRF6936? I have tried these two hardware files that give me the missing modules multimod error.

ini file #1
;Only useful for transmitters with an after-market vibration motor

;enable-haptic=1
;
;switch_types: 3x2, 3x1, 2x2
;extra-switches=
;
[modules]
; With MultiModule
; there is no need to enable the cyrf6936 module unless
; it is wired to an alternate port. It is Enabled automatically otherwise
; enable-cyrf6936=S0
; has_pa-cyrf6936=1
enable-a7105=S1
has_pa-a7105=1
enable-cc2500=S3
has_pa-cc2500=1
enable-nrf24l01=S402
has_pa-nrf24l01=1
enable-multimod=A13


ini file#2
; 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

Using osh park 1.3v board with nrf24, cc2500, and A7015 chip.

Ini file #1 should have worked. Since it didn't, do you have clear photos of your connections? I get these symptoms when I don't have the right wires at the right solder points. You may need to just change the last line from A13 to A14, but if I can see the wiring I can probably see if there is a problem.

I will definitely do that. I will take the Tx apart tomorrow and send them to you. It's been a long last few weeks or so trying to figure this out. Thanks again for your help it is greatly appreciated.

Arnold wrote:

Deal57 wrote: ...
;enable-cyrf6936=B12
has_pa-cyrf6936=1
...

Just an aside here, Jeff.
You have the cyrf in the tx, but not on the MM, correct?
On the next line your are saying there is a power amp circuit in the cyrf module.
Does that mean you've replaced the standard cyrf module with the "S" version in the tx?
Or does it mean something else? I thought that line about PA in the hardware.ini file was only relevant when using the cyrf module on the MM.

Another question: Why mount a cyrf module on the MM in the first place, since all Devos have one on the board anyway? Maybe 2 is better than 1?

That's correct, he is using the stock CYRF. And that's a reasonable question for which i can only "punt!".

I may have assumed incorrectly, as I've only tested the power functionality on my Devo7e, but I routinely un-comment the line
"has_pa-cyrf6936=1".
In the 7e this enables the use of the power settings for the stock, modified (range mod) CYRF module. Based on searches on this site I cannot tell for certain that it has any effect on the Devos with the "S" version stock CYRF module (6s, 8s, 10e, etc.), but it doesn't seem to hurt on my 6s. When I get a chance I'll check the mA used with and without it.

In any case I don't see that it hurts this situation either way (I could be wrong!). But it brings to mind a question:

@bmw2444: did this multimodule work before you updated your firmware?

I just tried to post two replies with photos but they are not appearing? Did you receive them?

I went back to try and upload photos tried to load one photo and it exceeded the allowable size? Is there another way to upload photos?

I think most users upload their photos on a service like Photobucket or Shutterfly or Google Photos and then include a link to them in their posts here.
I put mine on Mega in New Zealand.

Thanks I will do that.

Here is the link to photos of Transmitter circuit board and multimod. s328.photobucket.com/user/bmw2444/library/ The color code is as follows: 3.3v red to VDD, Gnd black to ground, TCK orange to RSET, TMS yellow to CSN, Mosi purple to Mosi, Miso brown to Miso, SCK white to SCK. I did not use TSV to 5v due to not installing a separate CYRF chip. The NRF24 is not installed to the board but located under the right gimbal using wires to connect it to the board. The color code is as follows if you are looking at the NRF24 chip with the eight terminals at the bottom circuit board facing you. Top left VDD red, next to that TCK orange, beside TCK, Mosi purple. The last pin on top not used. On the bottom row far left Black, ground, next to ground VDD red, then SCK white, and last Miso brown. All of the connections appeared secured and were connected correctly assuming my wiring schematic is correct. I have been able to change the hardware ini to get the deviation to power up but not able to access installed chips with all of them having asterisk besides them.

I have tried different hardware ini and got the devo to load the deviation screen no access to installed chips with asterisk besides them, the missing cyrf message and also missing multimod error message. I have also been able to get the asterisk to appear besides the stock protocols as well? Go figure. Thanks again for everyone's help.

From the photos it looks like things are wired right. I can't see anything that looks like a short But maybe you've got TMS and TCK different. Try this hardware.ini instead.

[modules]
; With MultiModule
; there is no need to enable the cyrf6936 module unless
; it is wired to an alternate port. It is Enabled automatically otherwise
; enable-cyrf6936=S0
; has_pa-cyrf6936=1
enable-a7105=S1
has_pa-a7105=1
enable-cc2500=S3
has_pa-cc2500=1
enable-nrf24l01=S402
has_pa-nrf24l01=1
enable-multimod=A14

Thanks for replying and looking over photos.I input the hardware ini file and still no access to installed chips asterisk besides them.

I have an idea. I will pm later tonight.

Thanks for your help again you are appreciated.

This was in my error file if it helps.

This was the result of my post to the bug tracker. I was informed that it looks like a hardware issue:

This sounds more like a hardware or configuration problem than a deviation error. Protocols with a '*' next to them are not accessible as they module either isn't installed or didn't init properly.

There has been an issue with the CYRF module being reported missing when others are configured but not found.

Some of the devo transmitters have power issues with several extra modules installed that will cause the CYRF to fail to init and show up as missing randomly. That may or may not be the issue here, but it's hard to say which is which.

Please take this issue to the forums. Post the hardware.ini file your transmitter has, information about which transmitter it is, and pictures of your hardware install so that there's enough information for it to be diagnosed. If they decide it's a software issue, report that back here along with a link to the thread. Also, update the bug report to include such information for when there's field for it.

This was MWM developers response. If it's a power source issue could it be the case that I am using the stock AA batteries? I always use alkaline batteries. Or does this even apply due to the out of the Tx?

I was having multi module errors so I installed the devo 10v4.0.1 version and was able to get the a7105 and cc2500 modules to work. The only one that is not is not recognized is the nrf24. I I enabled it but it's not visible as a protocol on the Tx menu screen. Here is the ini
current_model=1
mode=2
[modules]
; 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

[calibrate1]
;Aileron (Mode 1)
max=3813
min=530
zero=2171
[calibrate2]
;Elevator (Mode 1)
max=3549
min=354
zero=1951
[calibrate3]
;Throttle (Mode 1)
max=3698
min=489
zero=2093
[calibrate4]
;Rudder (Mode 1)
max=3867
min=569
zero=2218
[touch]
xscale=197312
yscale=147271
xoffset=-404
yoffset=-20

Is there a way to get the nrf24 recognizable?

Ok that's kinda odd, but whatever works! In any case, you can only use A13 or A14 for one module each. The multimodule connects to both so that it can multiplex between them.

You could try commenting out the lines for the cc2500, just to see if the NRF shows up. They can't both be on A14. Let us know what you find.