FrSky alt sensor
FrSky alt sensor
I can't find how to set the telemetry menu of the 221 FW to make the alt sensor work when linked with the A2 input of the D8 Rx; it works fine with my OpenTx Horus.
- MikeB
- 9x Developer
- Posts: 17993
- Joined: Tue Dec 27, 2011 1:24 pm
- Country: -
- Location: Poole, Dorset, UK
Re: FrSky alt sensor
I assume this is for the Vario, rather than altitude.
First, go to "Model Setup", select Telemetry, then "Vario" from the popup.
Set the Source to A2.
Select a switch to enable the vario tones.
You may then need to adjust the sensitivity value to quite a large value e.g. 50 to get a good response.
Mike
First, go to "Model Setup", select Telemetry, then "Vario" from the popup.
Set the Source to A2.
Select a switch to enable the vario tones.
You may then need to adjust the sensitivity value to quite a large value e.g. 50 to get a good response.
Mike
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
The difficult we do immediately,
The impossible takes a little longer!
Re: FrSky alt sensor
Thanks Mike, of course it is the vario sensor, but I need to display the altitude; I remember it worked some (!) years ago with an old FW...
Re: FrSky alt sensor
If I remember well you can't get altitude from A2, that only gives vertical speed.
Altitude needs to come from hub telemetry.
Altitude needs to come from hub telemetry.
- MikeB
- 9x Developer
- Posts: 17993
- Joined: Tue Dec 27, 2011 1:24 pm
- Country: -
- Location: Poole, Dorset, UK
Re: FrSky alt sensor
I assumed from the reference to A2 you were trying to get the vertical speed reported.
For the altitude, you need to connect the Data Out port on the Vario to the serial port on the receiver ("D" type Rx).
I assume you are using a 9XR-PRO (from the thread we are in), what Tx module are you using?
Mike
For the altitude, you need to connect the Data Out port on the Vario to the serial port on the receiver ("D" type Rx).
I assume you are using a 9XR-PRO (from the thread we are in), what Tx module are you using?
Mike
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
The difficult we do immediately,
The impossible takes a little longer!
Re: FrSky alt sensor
Yes, I use an old glider with the vario sensor plugged on the A2 port of the "D" Rx and the multi module 9XRPRO; what is strange is the last time I fly it it worked fine but, of course, not with the multi module. I will give it a try with the XJT module.
- MikeB
- 9x Developer
- Posts: 17993
- Joined: Tue Dec 27, 2011 1:24 pm
- Country: -
- Location: Poole, Dorset, UK
Re: FrSky alt sensor
You may have a problem with the polarity of the telemetry data, depending on the options chosen in the multi module.
From the main screen, go UP LONG, then RIGHT about 7 times to the "DEBUG" display. At the bottom of the screen is "TelRxCount". This is a running total of the bytes received from the telemetry. Is this changing?
If it is changing, then you are receiving something. Check the settings in the Telemetry menu for which COM port the telemetry is on (you need COM1) and the COM port Invert. Try changing the COM port Invert so you change the COM 1 polarity.
Mike
From the main screen, go UP LONG, then RIGHT about 7 times to the "DEBUG" display. At the bottom of the screen is "TelRxCount". This is a running total of the bytes received from the telemetry. Is this changing?
If it is changing, then you are receiving something. Check the settings in the Telemetry menu for which COM port the telemetry is on (you need COM1) and the COM port Invert. Try changing the COM port Invert so you change the COM 1 polarity.
Mike
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
The difficult we do immediately,
The impossible takes a little longer!
Re: FrSky alt sensor
Thanks Mike, I have to add the telemetry works fine except the vario sensor; I get RSSI and voltage sensor linked to A1; I checked an other old glider with the same Rx?sensor with the same result.
Of course at the time I flew those gliders the MM. don't exist...when I tell it works with Opentx it uses the internal module so it seems the issue come from Ersky9x/mmodule.
Of course at the time I flew those gliders the MM. don't exist...when I tell it works with Opentx it uses the internal module so it seems the issue come from Ersky9x/mmodule.
- MikeB
- 9x Developer
- Posts: 17993
- Joined: Tue Dec 27, 2011 1:24 pm
- Country: -
- Location: Poole, Dorset, UK
Re: FrSky alt sensor
Please confirm if you have the Data Out port on the Vario connected to the serial port on the receiver ("D" type Rx), not A2.
Mike
Mike
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
The difficult we do immediately,
The impossible takes a little longer!
Re: FrSky alt sensor
Yes it is connected, and as I told it works with Horus/internal module/Opentx
maybe the "Alt" option in the telemetry menu of the 9XR-Pro match only the Sport connection ?
maybe the "Alt" option in the telemetry menu of the 9XR-Pro match only the Sport connection ?
- MikeB
- 9x Developer
- Posts: 17993
- Joined: Tue Dec 27, 2011 1:24 pm
- Country: -
- Location: Poole, Dorset, UK
Re: FrSky alt sensor
I'll see if I can check it is OK with the multiprotocol module, I certainly had that setup working with a DJT in a 9X.
You might try creating a raw log file, and posting it so I can see what you are receiving. RSSI, A1 and A2 are handled differently in the module to the user data on the serial port of the Rx.
See here for how to create a raw log file on the SD card: http://openrcforums.com/forum/viewtopic ... ng#p123508.
Mike
You might try creating a raw log file, and posting it so I can see what you are receiving. RSSI, A1 and A2 are handled differently in the module to the user data on the serial port of the Rx.
See here for how to create a raw log file on the SD card: http://openrcforums.com/forum/viewtopic ... ng#p123508.
Mike
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
The difficult we do immediately,
The impossible takes a little longer!