A7105 wiring of GIO pins

Devo 7e + Latest Nightly + Flysky protocol

Can I wire the A7105 module?
RxEn - GIO2
TxEn - GIO1

Or should I use old wiring;
RxEn - Gnd
TxEn - 3v3

Ok thanks I'll leave that way!

I was wondering if it was working, as humming is much less, so this mean much less power consumption from the module, more efficient.

Not measured range or Ma yet.

Currently seem that CC2500, draw most power.

Will the nightly builds not work with the "old" method above (I just finished soldering my A7105!)?

I suppose they will, if in slightly suboptimal manner. Some protocols with feedback would benefit from turning PA off / LNA on when receiving, which is implemented by nightly builds and new wiring.

I have A7105 soldered in an old manner and it works OK.

Thanks, it's not installed yet so I could change if it's best...

I attached two files that I think show the way an XL7105 module is suppose to be wired if using the nightly downloads or any Deviation 4.0.1 or newer. What I'm looking for is verification that it right. And I hope that whoever created these files won't be upset by my modifying them.

Tim

I think for 4.0.1 you would use the old method, it's anything newer than that you would use the new method for (IE nightly builds).

The diagram is how I understand it needs to be done, I just have another issue preventing me using the nightly build so my module is yet to be installed.

As a regular dumb end user who has prep'd his A7105 with the old wiring for his devo 10, help me to acquire more context about this change. The intended application for mt A7105 is just common sport flying hubsan protocol:

-I don't know when to expect a new deviation non-nightly release. When would this change make it to the other channel for a major release?

-What differences would I observe on 4.0.1 with old wiring vs nightly with new wiring. The only reference I can find to this is related to noise/hum, but what does that mean to the end user?

I.E. If I complete the mod the old way on 4.0.1, would it be worth redoing it later. I don't mind fetching another module to try the other, but I want to understand the differences first.

Are the current nightlies working? I just changed the wiring of the 7105 module to the GIO pins and upgraded to the latest nightly (16 March), but I can't get my hubsan h107c to bind. It worked fine with the previous wiring and deviation 4.0.1

did you edit the hardware.ini file?

wian wrote: Are the current nightlies working? I just changed the wiring of the 7105 module to the GIO pins and upgraded to the latest nightly (16 March), but I can't get my hubsan h107c to bind. It worked fine with the previous wiring and deviation 4.0.1

I am using the latest nightly with my A7105 and GIO wiring without any problem.
I remember one user about 2 months ago, that never could use GIO pins. Probably faulty A7105 module. The module from these user worked without problems with the old style wiring (as your module).

Check this thread:
deviationtx.com/forum/6-general-discussi...7105-and-new-wriring

Thank you very much for the suggestions! The good news is that it is working now, the bad news is, I don't know what fixed it.

I formatted my devo 7e, reflashed the 16 March nightly DFU, copied over all folders from the nightly, copied the hubsan models.ini and made only the following changes to hardware.ini:
has_pa-cyrf6936 = 0
enable-a7105 = A13
has_pa-a7105 = 1

But before testing, also I also resoldered VCC (wire was skewed, but seemed fine otherwise) and scratched between the GIO1 and GIO2 because there were some tiny specs of solder that might have been causing trouble.

Now it is working fine.

What I did before when it was not working is that I copied back known working files from from deviation 4.0.1 , e.g. tx.ini and hardware.ini and copied and pasted all settings from tx.ini to hardware.ini (including the settings above). I may have also copied known good hubsan4.mod to the protocol folder. I suspect copying these deviation 4.0.1 files to the devo 7e with nightly installed caused the problem, rather than the scratching or resoldering.

Anyway, thanks for the replies and I hope this is useful for someone running into similar problems.

Hi guys, I am running devo7e-v4.0.1-dd446f70 nightly and having issues getting the XL-a7105-d03 working.
I am confused as I see a few different wiring diagrams published, so I am unclear if I have wired correctly.

On this page, it indicates "*4.0.1 and earlier: Connect 8->GND and 9->3.3V. Leave 6 and 7 floating " (what does floating mean?)
bitbucket.org/PhracturedBlue/deviation/wiki/ModuleList

Does this mean RXEN ( gets connected to GND (3) and VCC (1) and TXEN (9) get connected together?

On the same page listed above it says "Connect 6->9 and 7->8 (*)"
So according to that do I connect 6-9 and 7-8?

Which is correct? Do I keep the loops between 6-9 and 7-8 as well as connect 8 to GND and 9 to 1?
Thanks!

Currently I have it wired like this and its not finding the module, edited hardware.ini and checked everything with dmm etc:
4.bp.blogspot.com/-xkOUPc1CsSA/VQBfn72G_...w/s1600/A7105-7E.jpg

...for nightly builds..
www.deviationtx.com/forum/6-general-disc...0-for-frsky-rx#28027

I agree with aMax.
For nightly builds, much better the new style wiring (AKA 6-9, 7-8 bridges).
Low power consumption when not in use the A7105 module, and don't loose Telemetry under supported protocols (Hubsan protocol for ex.)

okay so I'm close, I also see SCK wired to ground, is that correct?

as far as wiring to the TX board (adding the loops back and grounding SCK, the Rx side is the same as this ?
4.bp.blogspot.com/-xkOUPc1CsSA/VQBfn72G_...w/s1600/A7105-7E.jpg

thanks so much for your help guys! I have the NRF module working great, just want to get this a7105 working now

No, SCK don't need to be wired to ground.
Your schematic at your first post is OK. You only need to change the bridges for RXEN and TXEN.
TXEN to GIO1(6 - 9) and RXEN to GIO2 (7 - 8 ), and be sure you configure your module at Hardware.ini to point TMS signal (a13)