turnigy tgy 9x + frsky R9M Smart Port telemetry

[rafzal]

My first post at this forum so hello all.

I want try use FrSky R9M with Turnigy TGY 9X (Atmega64) with Er9x-FrSky Telemetry
I know that TGY 9X is quite old stuff but at this time I'm not able to buy something else.

FrSky_R9M_and_R9.jpg (25.05 KiB) Viewed 1866 times

Previously I had FrSky DJT transmitter and D4R-II, and telemetry work fine. I have MAX3232 converter inside, and outside cables with connector for RS232 in DJT module.
MAX3232:

MAX3232inTGY9X.jpg (39.01 KiB) Viewed 1866 times

RS232 cable outside:

RS232inTGY9X.jpg (89.67 KiB) Viewed 1866 times

Now I use R9M transmitter wit R9 receiver.

As MikeB wrote in this thread:
viewtopic.php?t=11001

For the EU version:
Use the XJT(PXX) protocol and the R9M will operate in 25mW, 8 channel mode with telemetry.
Use the PPM protocol and set the switches on the R9M to select 200mW or 500mW output. You don't get telemetry with either of those.
The only configuration you don't get is 25mW, 16 channel with telemetry.

For the international version, XJT will give 10mW with telemetry. Use PPM and the switches for other powers, you won't get telemetry.

I'll see if I can add anything, but the '64 has very little flash space left (around 400 bytes).

Mike

I put R9M module in TGY 9X and change protocol to XJT and BIND to receiver R9 using BIND option. Binding was successful and RC channel start to work via SBUS.

XJT_protocol.jpg (13.17 KiB) Viewed 1866 times

And I connected RS232 same as in DJT module (Rx Tx 5V GND). But telemetry don't work.

So I have some questions:

1. Telemetry work only on Smart Port module? So should I connect Smart Port Output from R9M module to input(to Rx) of MAX232? Or should I connect in another way?

2. Telemetry of signal (Rssi & Tssi) should work if SmartPort is not connected to R9 receiver?

3. I use Pixhawk wit Ardupilot, with DJT & D4R-II I used option "3" in uart options "FrSky D, See FrSky Telemetry", so should I use another option in here?
"4"-FrSky SPort or "10"-FrSky SPort Passthrough (OpenTX)
link:
https://ardupilot.org/plane/docs/common ... tions.html

I know that on receiver side I should connect in that way:


4. Frsky R9M and R9 modules has ACCST 868Mhz EU firmware as provided by the seller. As i read about this modules if module will have ACCESS firmware I shoulden't be able to run anything on TGY9X? It's true?
If no - how I can check which firmware is installed?

I have er9x-r820 with FRSKY MOD:

version.jpg (12.42 KiB) Viewed 1866 times

ABBC3_OFFTOPIC

MikeB, Er9x is glorious, thank You for supporting this old stuff. I really appreciate that

[MikeB]

In the Protocol menu, after having selected XJT, check if you are able to set the Type to R9M. With the ATMEGA64, there is limited support for the R9M module, there is not enough flash space for full support.

For the Telemetry, it should work if you connect the SPort signal on the back of the module to the Rx signal of the RS232 converter (use the same wire that connected to the Tx signal of the module).

Mike

[raza]

after selecting XJT protocol, avaiable types are; "D8", "D16" and "LRP"

i know that Atmega64 is limited, but still can I have in this configuration telemtry?

[MikeB]

You appear to have R820 on your Tx. R821 has been released. This may have the R9M type in it.
Try D16 and see if the SPort telemetry does work.

Mike

[rafzal]

Hi, To this time I used Er9x v1. I just read that Er9x V2 exist and support R9M modules. Earlier I missed that.
viewtopic.php?f=5&t=8217
Thanks Mike.
BR
RaZa

[raza]

Hello again,
I just start again because telemetry in TGY 9X still don't work with er9xV2.
So I flashed my radio with the newest firmware (er9xProv822z1.zip) from here: viewtopic.php?t=4598
I used er9x-frsky firmware. I can bind with reciver with no problems, rc channnels works great, but telemetry: only RSSI work - nothing else.

I use these settings:
Protocol:
R9M RxNum 0
Power 25-8
Chanels: 8
Country Eur

UsrProto: FrHub
NumBlades: 4, (i tried also with 1)

In Pixhawk:
serial4_baud: 57 (mean 57600)
serial4_options: 4 (halfduplex) (also tried 0)
serial4_protocol: 10 (FrSky Smart Port Passtrough (OpenTX)

For any tips i will be grateful.
BR
RAZA

[MikeB]

Try changing the UsrProto to FrSky, not FrHub.
I'll see if I can check thing out later, I don't have a '64 9X any more, but can try the '64 firmware on a '128.

Mike

[raza]

Hi,
In "ModelSetup"->"Telemetry" -> "UsrProto" have only two options: "FrHub" and "WSHhi"

Eepe also have only these two options:

eepe_frsky_settings.png

(27.27 KiB) Not downloaded yet

[MikeB]

The main problem is you are using Pixhawk passthrough telemetry. There just isn't enough flash space in the '64 to be able to process that.
Since you have RSSI working, then the Smart Port from the R9 module is working.
I tested the same firmware with a R9 Rx and a FrSky vario on the SPort and got the altitude data correctly.
Can Pixhawk send normal SPort data instead of the passthrough data?

Mike

[raza]

Hi,
"Can Pixhawk send normal SPort data instead of the passthrough data?"
Propably yes:
I can set one of these options: "FrSky D" (that was working on DJT module), "FrSky SPort" and "FrSky SPort Passtrough (OpenTX)"

ardupilot_uartOptions.png

(40.93 KiB) Not downloaded yet

So i try with all these settings, but no luck.
What buad rate Smart Port need?

"There just isn't enough flash space in the '64 to be able to process that."
Maybe is a time for looking some Taranis.

And still thinking about "FrSky telemetry" which You mentioned. Is it in Er9x?

[MikeB]

Smart Port needs 57600 baud and "half Duplex" so with the Tx pin connecting to the SPort signal. The SPort is also inverted, and there is a comment in your PNG file saying you may need external inverter hardware, although the options also imply there are invert options for Tx and Rx signals.

Standard FrSky SPort telemetry is supported in er9x, just some of the later sensors (e.g. redundancy bus) are not handled due to lack of flash space in the '64.

Mike