Getting only 5 meters range using DSMX on Devo 7e!

I'm having a big problem with the range of my Devo 7e when using it with DSMX/DSM2 protocol.
I did my range mod using this conductive paste that I bought from Banggood. See photo of my finished range mod attached.
After that I added the A107 and nrf24l01 modules. Both of these modules work correctly and I can fly Hubsan, Nihui, MJX, Syma and Eachine toy quads.

But when I try to fly my Blade Nano QX which uses DSMX, once the quad gets beyond 5 meters I lose control of it. I already have the transmit power set to the maximum of 150mw.

I did not do any soldering underneath the RF shield so there was no chance I damaged anything in there. I don't understand why the range is so poor.
I'm using this test build (deviation-devo7e-v4.0.1-e9e4b2c) of DeviationTx that has the MJX protocols.
I've also attached my hardware.ini and tx.ini files.

Any advice on what might be causing the problem?

Did you read all product reviews..? Some report it isn't conductive at all.
Have you check your work with a multimeter? In the end your devo should work at least as before.
If not, something different must have happened.
How did you remove the RF shield? Inspect the antenna wire soldering point....

Can't find this build e9e4b2c anywhere. Link? Date?

5m with 150mw?
DSMx AR6210 should be about 30-60m on 1mw.
>5m on 100uw.

Try latest nightly-build or hexfet test-build protocol combo.

Try commenting out the has_pa line for the CYRF module by adding a semicolon in front of it.
That particular instruction line is not for the onboard CYRF of a DEVO Tx. It is for a CYRF transceiver that is added to a non-DEVO Tx that does not have one to begin with.

;Only useful for transmitters with an after-market vibration motor
;enable-haptic=1
;
;switch_types: 3x2, 3x1, 2x2
;extra-switches=
;
[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

That may not be your problem, but it is something to try.

Hi,
I have the same problem as jayodas...
I have the range mod with wire solded....I checked the work with a multimeter and seems ok..

With a 200QX which DSMX at 150mW, I only have 15-17meters...
With a Ladybird wich DEVO at 150mW, I have 25-30m...

Deviation V4.0.1-dfa9397
I attach .ini files..

what might be causing the problem?

Thanks very much for replying aMax, Thomas.Heiss, and RedSleds.

I did use my multi-meter to touch both ends of the diode after the paste dried and it beeped to indicate there was conductivity between it.
That's as much as I did and at that time I did not find any information about testing for precise resistance readings.
Since my RF shield has been soldered back on already I'm going to test my tube of conductive paste to see whether it is really conductive paste or not.
I hope I didn't receive thermal paste instead of conductive paste!!

I'm also going to try the hexfet test-build protocol combo and also comment out that has_pa-cyrf6936 line and test range again.

Ok, I tested my tube of conductive paste by spreading a good amount out on some cardboard, letting it dry and then using my multi-meter to test conductivity.
It has zero conductivity! So it was a big mistake for not testing it out before using it to do my range mod.

I've also updated the firmware to the hexfet test-build protocol combo.
And commented out the has_pa-cyrf6936 line.
The range problem still exists.

So my question is: Since I've already soldered on my A107 and nrf24l01 modules, is it still possible for me to remove the RF shield again to try this mod with some good quality conductive paste?

Thanks!

Thats the conductive paste I butchered my module trying to remove it so be careful... It is conductive tho if heated until dry.
Maybe wait more and apply heat before you try anything else?