PXX protocol

I can't find the test build but is it now in nightly's? I will also test it.

I tested PXX power and I can confirm it works including the auto power.

Range check I do not measure any RF from antenna but Rx still stay connected. So its very low power.
When at auto power, the power will be high when RX is off, but when Rx is connected the power will be reduced a lot.

Thanks for testing.

I've found another bug, I think. That it's only happening in PXX mode I post it here.

My current version:
deviation-devo7e-v5.0.0-28ce50f

I added 2 3-position switches to my Devo 7E (hardware.ini extra-switches=3x2).
When I selected a model with PXX protocol one of the switches is showing strange behavior.
If I switch the left one to the middle position (A1) trim will be applied to the Roll stick as long
as the switch is in that position.

I don't have this problem on models with different protocols (e.g. FrSky X).
Also the problem only occuring if there is really a module connected (R9 in my case) to the trainer port.

Quite strange. Don't see anything in the code that would explain this.

This mod doesn't require any soldering to the processor, right? No chance of any shorts to the trainer port or trim button?

Please test if you get the same behavior with the SBUS and SUMD protocols. It won't hurt the R9 to send these signals to it.

Was the test done with a fully charged battery? Can you try with external power to the R9?

Try if it occurs also in rangecheck mode. High power UHF may cause RFI pick up on long cables, detecting false switching.

Potentially dangerous, but all our transmitters are pretty poor in RFI design.

hexfet wrote: Quite strange. Don't see anything in the code that would explain this.

This mod doesn't require any soldering to the processor, right? No chance of any shorts to the trainer port or trim button?

Please test if you get the same behavior with the SBUS and SUMD protocols. It won't hurt the R9 to send these signals to it.

Was the test done with a fully charged battery? Can you try with external power to the R9?

Hello! Thanks for the feedback!
The mod doesn't require any soldering, that's right. I'll check the connections of the Switch mod but I doubt to find any shorts.
power the R9 externally only. I use two 3000mAh 18650 cells to do it. there is only a signal and ground connection to the Devo.

I'll try the other protocols as soon as I'm @home.

Fernandez wrote: Try if it occurs also in rangecheck mode. High power UHF may cause RFI pick up on long cables, detecting false switching.

Potentially dangerous, but all our transmitters are pretty poor in RFI design.

Ohh, haven't thought on that. There are some relative long wires required for the switch mod. I'll try some shielding and lower output power.

Thank you!

EDIT: Haven't tried yet but that's probably it. I haven't had the problem before the Hotfix hexfet made for me and the Nightly I installed afterwards.
Before the fix there was only very low output power and the module had more distance to the Devo 7E.

You could place some 100pf caps one at each switch matrix lines at devo side to gnd.
Or could try a "Ferrite Clamp" around the cable bundle?

Sorry that I made you stress @hexfet.
It's like Fernandez thought. When I'm bringing a piece of aluminum foil between the Devo and the R9 Super 8 everything is working as it should. As soon I take it away the Devo starts to beep and is moving the trim.

Thanks again for all your input and sorry again @hexfet!

No worries. Glad you got it sorted

Hello everyone

I was a lucky owner of a t8sg v2 plus with an r9m module.
Since a few days I have massive RFI problems - Buttons are clicking without input, trimming runs away and the voltage indicator jumps around.
I have already shielded the whole JR bay with aluminum tape but the only thing that helps is less output power (range test works also) or an aluminum foil between the transmitter and the r9 antenna.
Does anyone have an idea why this suddenly happens after about one year of flawless operation and what else I could do about it?
Thanks for any good tips.

Kind regards
Matthias

Maybe your antenna is broken? Or coax is damaged ?

If you plan to use any metal shielding, be sure it “well”, connected to gnd, so many hard connections to the main pcb gnd.

( as at uhf a wire of a few cm is allready am antenna, so connecting the shielding with a wire to ground does not work....)

Was running test build 42d48d4 since Apr, but just now I think there's a bug. The dsm/dsmx protocols seems broken. Can't bind with my earlier dsm/dsmx models. I tried rolling back to the main branch 5.0 firmware and vlad_vy builds and both was able to bind with my dsm/dsmx models no problems.
Even tried the latest nightly builds and seem those too are broken with this same problem.

I've tried www.deviationtx.com/forum/builds/8508-re...ild-deviation-v5-x-x

- dsm/dsmx protocol doesnt work
- PXX unavailable in the build

also tried www.deviationtx.com/forum/builds/6407-de...cols?start=480#75000

-dsm/dsmx protocol works
- PXX unavailable

Unfortunately I dun hav older 5.0 nightlies to try out, all the recent builds hav broken dsm/dsmx

do you use txid in your config? If yes this could cause your already bound rx not to work with the newer version.

I've tried fresh bind multiple sats both dsm2 n dsmx all failed, also tried id none. And as a test when I flash to the main 5.0 firmware all sats were able to bind easily. Maybe someone can try this and confirm if the latest nightly builds have this problem?