[Devo 7e] Problem changing output power AFHDS-2A

More
27 Sep 2017 20:43 - 28 Sep 2017 10:50 #64697 by quad450
Hi everyone,

I have a Devo7e with diode mod, nrf24l01+pa+lna and A7105-500m module running deviation-devo7e-v5.0.0-b785c8a.

I have the following settings on my hardware.ini:
has_pa-cyrf6936 = 1
enable-a7105    = A13
has_pa-a7105    = 1
enable-nrf24l01 = A14
has_pa-nrf24l01 = 1

I am experiencing a problem with the A7105 module: I can bind correctly to the receiver using AFHDS-2A protocol, but it seems that changing TX output power is not working (even if I can switch from 100uW to 150mW on the menu). In fact, it seems that the range I get is always the same.
Going on Transmitter Menu -> Range Test gives "No range test possible".

This does not happen with any other protocol that works with the other two modules.

What can be the problem? I appreciate any help.
Last edit: 28 Sep 2017 10:50 by quad450.

Please Log in or Create an account to join the conversation.

More
28 Sep 2017 01:01 #64700 by mwm
Possibly your A7105 doesn't have a PA, or it got fried. Post pictures of current install and links to the datasheet for that chip. Or a link to the product page.

Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.

My remotely piloted vehicle ("drone") is a yacht.

Please Log in or Create an account to join the conversation.

More
28 Sep 2017 10:01 - 28 Sep 2017 10:52 #64710 by quad450
Hi,

thanks for the answer.
The chip is XL7105-D03B and here are attached my connections (red circles in the second image are for A7105 wires).

EDIT: It seems that the problem is related to the protocol AFHDS-2A; in fact, if I change, for example, to the Hubsan protocol, which uses the same transreceiver module, the Range Test is working.
Attachments:
Last edit: 28 Sep 2017 10:52 by quad450.

Please Log in or Create an account to join the conversation.

More
28 Sep 2017 10:52 #64712 by aMax
Trust only in what you can measure....;)
Does your Flysky A1 protocol behave the same?

Simply setup your Devo and a multimeter for currend measurements. Then check every rf output power step and look what the multimeter displays.( both protocols)

Devo7e, TaranisQ X7, R9M , 4in1 MM, Futaba FC18plusV3.2 & DFT/FLD-02

Please Log in or Create an account to join the conversation.

More
28 Sep 2017 10:54 #64714 by quad450

aMax wrote: Trust only in what you can measure....;)
Does your Flysky A1 protocol behave the same?

Simply setup your Devo and a multimeter for currend measurements. Then check every rf output power step and look what the multimeter displays.( both protocols)


I found it is related to the protocol AFHDS-2A just right now.

Please Log in or Create an account to join the conversation.

More
28 Sep 2017 11:15 - 28 Sep 2017 11:18 #64715 by vlad_vy
A7105_SetPower(Model.tx_power); for AFHDS-2A protocol used once only, at protocol init sequence. So, it's question to protocol developer (goebish).
Last edit: 28 Sep 2017 11:18 by vlad_vy.

Please Log in or Create an account to join the conversation.

More
28 Sep 2017 12:20 #64719 by aMax
Then a cold start with a prior saved parameter for tx power should get around this problem.

Devo7e, TaranisQ X7, R9M , 4in1 MM, Futaba FC18plusV3.2 & DFT/FLD-02

Please Log in or Create an account to join the conversation.

More
28 Sep 2017 15:49 - 28 Sep 2017 15:52 #64720 by quad450
True, TX power is set only in afhds2a_init(). I had not checked the code.

I tested with the output power already set up before powering on the transmitter and RSSI value shows the difference.
Last edit: 28 Sep 2017 15:52 by quad450.

Please Log in or Create an account to join the conversation.

More
21 Oct 2017 13:36 #65160 by goebish
Fixed, waiting for pull request to be merged
github.com/DeviationTX/deviation/pull/306

Please Log in or Create an account to join the conversation.

Time to create page: 0.050 seconds
Powered by Kunena Forum