PXX protocol

Install the current protocol_pxx test build (bb6c3ca) firmware. Install the R9M module - no special wiring needed. Select the PXX protocol in the model config.

Please report your results here. So far the reports are that control works fine but not telemetry. When linked with the receiver the RSSI and receiver voltage should appear in the first two boxes on the telemetry test page.

The test build is built from recent master so no problem to use it for other protocols as well.

Did not did not do new test with U7E 256, but to confirm with R9M in my TS8G plus, on latetst test build, I can confirm PXX transmission works inc, binding, power etc.

But no telemetry for me here also, I tested at different power levels, as not sure R9 system has telemetry feature in all transmission modes....

Fernandez, if you can please run once the new pxx_log test build. It should put something in the datalog.bin file.

with bb6c3ca, in T8SG,is also all NULL, see attached.

Please try again with the pxx_log test build here (d87b33e) .

tested d87b33e on my TGSG plus, still all zero,no telemetry. Still I believe file looks some what different some rubbish at the start.

To ensure R9 is sending telemetry, o we need to be in specific powermode ?

That's not rubbish. The 0xaa means there was a start bit error; 0x55 is a stop bit error. The only explanations I can think of for a start bit error are an error in the bit rate or a noisy signal. Please make another two tests if you can. With the pxx_log build send the captured sport_r9m.bin file data to the serial port with inverted TX, 57600N81, and post the datalog.bin. Then install the test_serial build and try the loopback test at both 115200 and 57600 bps.

I'll work on a test build that will allow the bit rate to be adjusted.

The R9M interface doesn't require a specific power setting for telemetry. The R9M manual for the EU version does link power and telemetry settings, but that must be enforced in fros and opentx. Not sure why. The PXX protocol does not implement that restriction.

May have found the issue. Test build protocol_pxx is updated ( bb9abb6 ). Changed s.port input pin configuration from float to pull-up.

With the previous input pin configuration a noisy signal symptom might be the result if the R9M uses an open-drain output on the s.port pin. Try this before the tests in the previous post.

Ok thanks will try to test tonight. Maybe better to test with my U7E and my 3.5mm plug as I am sure Tx there RX lines work.

I found this post, which is somewhat strange ?
www.deviationtx.com/forum/protocol-devel...oxes?start=140#71053

The hardware modification in that post is only for the Crossfire protocol.

Hi Hexfet, bad news again for latest testbuild, telemetry still all at zero at my T8SG.

Okay, thanks for testing. If you can please run the tests outlined in the previous post (datalog capture while sending file, loopback test). I've uploaded a new pxx_log build (263cbb6) so please use that for the first test.

Test build is updated (7125363) . Optimized latency by starting mixer calculations in the protocol.

Test build is updated (73bec93) . Added protocol option TEST with values 0 to 3.

Please check the telemetry with TEST set to each of the values. Power cycle after changing this option. This tests new combinations of polarity and bit order. A value of 2 is same as previous builds.

Telemetry is verified working. Made a trip to my not-so-local hobby shop and tested with an open-box R9M they had on offer (thanks Will at Grayson Hobby !). When testing we didn't have a receiver but the R9M does still send RSSI and receiver voltage telemetry, with values 0 and 0.04.

The PXX protocol will be included in the next nightly build.

The T8SG V2 Plus requires a modification to enable telemetry with PXX. Discovered today that the bottom pin in the JR module bay is not connected to the serial RX pin. It is not connected to anything. To enable telemetry add a wire from the bottom JR bay pin to the ring connector of the trainer port jack (picture attached with red arrows, ignore the other bodges). I thought I'd verified previously that the bottom pin was already connected to RX, but it is not.

Nice Hexfet, so good to hear that it was the jumper Rx.(should have test latest with my U7E) But will check during weekend.

Much thanks for all the testing, Fernandez. Please check that the receiver voltage telemetry is reasonably accurate. Not sure the scale factor is correct.

I Installed the latest Test Version on my Devo F4 - XMS, but under Protocols i can´t find PXX?
The last one in the List is CRSF!

Please try the modular_protocols test build (90b9053) . This adds SBUS and PXX to the modular builds. The limited memory means PXX telemetry is not supported.

These protocols were not previously included in modular builds due to a serial port issue. A fix for that issue was merged today so they can now be supported.

Ok now i have PXX! There is no Option to Change the Tx Power (the only Option is default) so we can´t set the Power of the Module?
And the Channels in Betaflight only moving a Second and then nothing perhaps because of the missing Power Setting?

On my Devo 10 i can´t see Telemetry, Binding/Power/Controls work!
I will try to flash Flexfirmware (to get Telemetry at all power levels) or Bind with 10mW (=25mW?)
What can i try else?