a A7105 module defective?

yes i use deviation 4.0.1. presently the module is not in the radio.
i will do the test you propose not before next week end.
i succeded in binding a walkera mini cp.
by the way i think "we" should create a place on the site which would gather all the *.ini model files,for example in the sub menu "supported models".

I am having the same problem with my Devo 10. I am using the 4.0.1 version of Deviation and when I power up using the Hubsan protocol I get a blank white screen. I turn off the power and usually after another minute or two the TX will turn off. I get this several times before it will start up without having the problem. If I set it to start with a flysky model (I am using a 7105 chip from a V911 TX) it is fine.

I believe it has something to do with the automatic reinit upon startup that it does when it is set to the Hubsan protocol. Is there any way to disable the automatic reinit? I would like to try this and then manually go to reinit and see if I still have the problem.

If I start the TX and it is on any protocol but Hubsan, it is just fine. Often, though, when I go to load a Hubsan model it will freeze on the load screen when I select the model. Again I can turn the power off, but it will take a minute or two before the TX shuts down.

I used the exact wiring method from here: www.deviationtx.com/forum/how-to/1144-fl...on-devo-10-with-pics

Again - this is only a problem when using the Hubsan protocol.

I should add that I recently upgraded from the version 2.1.0 of Deviation. with that version the TX would reset itself every few seconds when set to the Hubsan protocol - only if not bound to a model. Once bound it would be OK. If I started up the TX and it was set to Hubsan I only had four or five seconds to switch to another model before it would reset back to the start screen for my Hubsan X4, for example.

AirPatoine wrote: I am having the same problem with my Devo 10. I am using the 4.0.1 version of Deviation and when I power up using the Hubsan protocol I get a blank white screen. I turn off the power and usually after another minute or two the TX will turn off. I get this several times before it will start up without having the problem. If I set it to start with a flysky model (I am using a 7105 chip from a V911 TX) it is fine.

I believe it has something to do with the automatic reinit upon startup that it does when it is set to the Hubsan protocol. Is there any way to disable the automatic reinit? I would like to try this and then manually go to reinit and see if I still have the problem.

If I start the TX and it is on any protocol but Hubsan, it is just fine. Often, though, when I go to load a Hubsan model it will freeze on the load screen when I select the model. Again I can turn the power off, but it will take a minute or two before the TX shuts down.

I used the exact wiring method from here: www.deviationtx.com/forum/how-to/1144-fl...on-devo-10-with-pics

Again - this is only a problem when using the Hubsan protocol.

I should add that I recently upgraded from the version 2.1.0 of Deviation. with that version the TX would reset itself every few seconds when set to the Hubsan protocol - only if not bound to a model. Once bound it would be OK. If I started up the TX and it was set to Hubsan I only had four or five seconds to switch to another model before it would reset back to the start screen for my Hubsan X4, for example.

I had the same problem on my 7e devo and I solved changing the v911 module of this

That's what I was planning on trying next. So you don't have any issues at all after changing to the 7100-500m module?

AirPatoine wrote: That's what I was planning on trying next. So you don't have any issues at all after changing to the 7100-500m module?

No problem dovetails nicely every time I turn the TX and again and not have the blank screen.
I advise you to buy an armored like the link module

Excuse my English translator

I just ordered one from Ebay. Will install it and report back. Thanks.

Ok use this wiring

Installed the new 500m module. Everything is working great. Instantly binds and I have telemetry with my Proto X and Hubsan X4. No more freezing screen on startup. Thanks for your help.

the first module i bought was really defective because i bought another one on
banggood and soldered it this afternoon. And this one works!!!
it's a pleasure to fly my x4!
now i want to bind a trex 100X but i don't find any config file.

Is there a way to tell if the A7105-D03-PA is defective, other than just getting a failure on power-up or when we try to use a supported protocol?

I replaced my A7105 and it worked for about a week, then once, upon power-on it gave me the "Missing Modules: MultiMod" error. I quickly powered off and powered it back on, and that error didn't reappear... well for about another week, during which I spent a good deal of time flying using that radio. I have an NRF module installed too, and it is working perfectly. If I power on with a protocol on the NRF or CYRF modules things work as normal.

Now I get the "Missing Modules: MultiMod" error any time I power on with one of the A7105 protocols selected. I also have the "*" in front of the protocol names; it's pretty clear the module isn't working. I have checked the wiring for breaks or problems on the 7e board; when I installed the boards I wanted to be sure that if there was an issue I could avoid soldering on the 7e board, so I soldered just one wire to the 7e board, and the wiring from each module is joined to the appropriate connection (I've spent most of my career in network systems, so I'm pretty good at spotting wiring issues). On the A7105 module I have voltage at Vcc (3.23v), and SCS (3.23v). I also checked GIO1, GIO2, RXEN and TXEN and found 3.23v on each of them.

This is my hardware.ini:
[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-nrf24l01 = A13
has_pa-nrf24l01 = 1
enable-a7105 = A14
has_pa-a7105 = 1
; enable-cc2500 = A14
; has_pa-cc2500 = 1
; enable-multimod = A13

If I put the semi-colon in front of the A7105 lines, the error doesn't show up, but of course the protocols are not available.

For the photo I have removed the heat shrink tube that I put around the module, along with a bit of hot glue to keep the wires immobilized.

Any ideas? Thanks!

Old wiring for Deviation 4.01.....for testing..
Release wires at GO1 and GO2.
Then bind pin 9 to pin 1 (Vcc) and pin 8 to pin 3 (GND).
If this does not work, the module is dead.

Both wirings work with the nightly, but this will not bring the A7105 to sleepstate when using other modules.

Darn. It doesn't work that way either.

I hate to invest in another one if the problem is my 7e... I replaced my original A7105 because it gave me the missing modules: Multimod error after about two months use. I have a v911 controller I can harvest, but I may just build the multimodule, since I know I will have a Devo 10 in a few months.

Has anyone installed the multimodule in a Devo 7e? It looks like it may not fit in that little case.

...Thanks for your thoughts.

If it were due 7e hardware problems your other module would not work either
or A14 is not working anymore.....
Change to A13 and the other module to A14 and don`t forget to change your hardware.ini that way.

Another job could be done with messuring the currend of the whole TX while switching between the modules.

The CYRF 6936 should draw round about 110-115mA at 10mW, the NRF24L01 below 100mA and the A7105-D03 nearly 170ma.

With the old wiring you will see 220mA with CYRF (and A7105.. .. because it it not powered down)

Do it, you will have a starting point for more investigation.

The multimodul will not really fit into 7e, to big.

Thanks for the info on current... I remember a discussion about that some time ago, and that's where I'm going. I can put off the MM but I was looking forward to more hardware fun, which was long ago a big part of my work.

In any case, I'm pretty sure that learning something new everyday is a requirement for this hobby!

Deal57 wrote: ............. I can put off the MM but I was looking forward to more hardware fun, which was long ago a big part of my work.

Oh dear, looking a second time at your pictures, I noticed a wire at RES. But your hardware.ini does not give a hint for an aktive MM.
Did you solder the modules to a MM? At that point i would be out, having no experience with this mod.

I looked again and the photo is misleading and no, I don't have the MM.

I have soldered my leads to the tms, tck, gnd and vcc connections on the board, and the 2,3 and 4 pins on the CYRF. TMS (A13) is connected to my NRF24L01 module, along with the other appropriate lines. TCK (A14) is connected to the A7105. I hope to check the current consumption today.