I'm using a project based on Teensy to "translate" Mavlink telemetry to FrSky SPort telemetry. (the current version is 1.3 located here: http://diydrones.com/forum/topics/amp-t ... -converter).
My goal is to build a "kind" of HUD display as a telemetry script on the Taranis.
Until version 2.05 of OpenTX we could translate the following with no issues:
Data transmitted to FrSky Taranis:
Cell ( Voltage of Cell=Cells/nr of cells. [V])
Cells ( Voltage from LiPo [V] )
A2 ( Analog voltage from input A0 on Teensy 3.1 )
Alt ( Altitude from baro. [m] )
GAlt ( Altitude from GPS [m])
HDG ( Compass heading [deg])
Rpm ( Throttle when ARMED [%] )
AccX ( AccX m/s ? )
AccY ( AccY m/s ? )
AccZ ( AccZ m/s ? )
VSpd ( Vertical speed [m/s] )
Speed ( Ground speed from GPS, [km/h] )
T1 ( GPS status = ap_sat_visible*10) + ap_fixtype )
T2 ( ARMED=1, DISARMED=0 )
Vfas ( same as Cells )
Longitud
Latitud
From 2.05 that the Voltage related data stopped being "interpreted" and I can't figure why.
The code running on the Teensy assumes the following:
// Frsky Sensor-ID to use.
#define SENSOR_ID1 0x1B // ID of sensor. Must be something that is polled by FrSky RX
#define SENSOR_ID2 0x0D
#define SENSOR_ID3 0x34
#define SENSOR_ID4 0x67
// Frsky-specific
#define START_STOP 0x7e
#define DATA_FRAME 0x10
//Frsky DATA ID's
#define FR_ID_SPEED 0x0830
#define FR_ID_VFAS 0x0210
#define FR_ID_CURRENT 0x0200
#define FR_ID_RPM 0x050F
#define FR_ID_ALTITUDE 0x0100
#define FR_ID_FUEL 0x0600
#define FR_ID_ADC1 0xF102
#define FR_ID_ADC2 0xF103
#define FR_ID_LATLONG 0x0800
#define FR_ID_VARIO 0x0110
#define FR_ID_CELLS 0x0300
#define FR_ID_CELLS_LAST 0x030F
#define FR_ID_HEADING 0x0840
#define FR_ID_ACCX 0x0700
#define FR_ID_ACCY 0x0710
#define FR_ID_ACCZ 0x0720
#define FR_ID_T1 0x0400
#define FR_ID_T2 0x0410
#define FR_ID_GPS_ALT 0x0820
#define _FrSkySPort_Serial Serial1
#define _FrSkySPort_C1 UART0_C1
#define _FrSkySPort_C3 UART0_C3
#define _FrSkySPort_S2 UART0_S2
#define _FrSkySPort_BAUD 57600
Can someone share from greatly appreciated knowledge on FrSky so that I can understand what's happening (or not happening in this case
)Some additional questions:
I have some additional parameters that I would like to send down to the Taranis (roll, pitch, yaw angles) that I was thinking of either "repurposing" the AccXYZ values or using the A3/A4 raw values, but short of finding elsewhere here on the forum the current limits of A3-255 and A4-330, didn't find much more on how to use them (the roll angles are natively on grads, but we can send anything after being "treated" on the Teensy).
I'm attaching a draft mockup on what I intend to "build" on the Taranis, once I get this figured out.
- Draft sketch HUD roll/pitch
Thanks
