DSM Telemetry support

If you provide your code in whatever state, it would save me from needing to reinvent the wheel.
Otherwise I'll clone what you have.

Possible we need start to divide telemetry processing/setup by protocol. Every protocol has different set of sensors and different options set for sensors.

At the future, with several telemetry protocol it will be even more mixed and difficult to work.

It will be easy to work with telemetry if after protocol change we will have definite set of sensors, setup options and pages.

my plan is to store a mask indicating which data each protocol supports and to use that mask to determine which pages (or sections of pages on the devo8/12) to make available.
This way i don't directly tie the display code to the protocol stack, which I don't want to do/

I've checked in a complete revamp of the telemetry system. It adds different displays for DSM vs Devo. I had to completely rework how updates are detected so the code behavior may be different.

The code has only been lightly tested for devo8 and dsm and only in the emulator, so it is likely there are a lot of bugs remaining. I'll try to start testing it on a real radio, but I expect all sorts of things I missed to pop up.

The DSM page is based on RW9UAO's layout. I only enabled the flightlog page so far.

Anyhow, if someone wants to be a guinea-pig, I'm interested in feedback.

I don't see any changes in emulator, Devo 12 and Devo 8. What I do wrong?

select protocol = DSM2
press and enable Telemetry
press 'Bind' to actuvate protocol.
go to main page
press left/right to get to telemetry page

I can't select 'Temp' at layout config page.

Yep. that is because there is currently one more source on the DSM telemetry than the Devo telemetry. One of the things left to do is to figure out how to handle that properly.

In the meantime, you can trade 'Temp' for something else by, for instance, swapping the order of TELEM_DSM_FLOG_TEMP1 and TELEM_DSM_FLOG_HOLDS in telemetry.h

telemetry.h

struct telem_dsm_sensors {
u16 amps; - 16bit signed integer
u16 airspeed;
u16 altitude; - 16bit signed integer
};

struct telem_dsm_gforce {
u16 x; - 16bit signed integer
u16 y; - 16bit signed integer
u16 z; - 16bit signed integer
u16 xmax; - 16bit signed integer
u16 ymax; - 16bit signed integer
u16 zmax; - 16bit signed integer
u16 zmin; - 16bit signed integer
};

Possible will be better place telemetry sensors at the and of the selection list (at layout config), it's variable length structure for every protocol.

How can altitude be negative? Unless you are in a submarine (in which case you use a different sensor) negative is very, very. bad, right?

I think I'll likely make the gforce sensor data 8-bit. that will allow me to store the same range as voltage (-12.8 to +12.8g). That is a lot of g-force that I wouldn't expect to be exceeded except on a crash in which case it probably doesn't matter.
keeping the data-size small enables more logging data and less ram.

PhracturedBlue wrote: How can altitude be negative? Unless you are in a submarine (in which case you use a different sensor) negative is very, very. bad, right?

Probably the reference 0 is not at the see level...

FDR wrote:

PhracturedBlue wrote: How can altitude be negative? Unless you are in a submarine (in which case you use a different sensor) negative is very, very. bad, right?

Probably the reference 0 is not at the see level...

A negative altitude calibrated at the operator's position also seems...bad....
unless you are standing at the edge of a cliff and flying below yourself. It isn't really an issue though. If their data is signed, Ill keep it that way.

It is barometric sensor. What do you think it will show at low atmosphere pressure (below 760 mm Hg)? Positive altitude or negative altitude?

I need DX8 log (.tlm) file with negative GPS altitude to find out how encoded the negative altitude. Possible it coded by a bit in the byte 15 of GPS packet 0x16.

Just a small addition:

//===============================================================

Data type = 0x12 Altimeter Sensor

0[00] 18(0x12)
1[01] 00
2[02] Altitude MSB (Hex)
3[03] Altitude LSB (Hex) 16bit signed integer, in 0.1m
4[04] Max Altitude MSB (Hex)
5[05] Max Altitude LSB (Hex) 16bit signed integer, in 0.1m
6[05] Unknown
7[07] Unknown
8[08] Unknown
9[09] Unknown
10[0A] Unknown
11[0B] Unknown
12[0C] Unknown
13[0D] Unknown
14[0E] Unknown
15[0F] Unknown

//===============================================================