What's new
Aloft Forums

Welcome to Aloft Forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

ErskyTX Vario

I thought I still had r229 running when I did those screenshots! I'm upgrading many menus to the "new" layout as touch works better on them, so I keep flashing my Tx to test they are working correctly.
I've also changed the text font to a proportional font that looks much better. At the same time I'm getting the code merged with that for the X20, and using the same layout on colour radios without touch.

Mike
 
Flight testing conducted this morning. Receiver is a 3 channel EP plane, mounted vertically in the fuselage, stabilisation is not active.
Altitude is not zeroed on power up, but routine to do so is no biggie.

Plane was set into a gentle climb, altitude call outs increased numerically as the plane rose and decreased during descent, but numerical values seemed off; the more I climbed, the more off they seemed, the plane never appeared to be as high as the call outs stated, although that could very likely be uncalibrated old eyes.
Landed the plane, with transmitter about 3' above it, call outs were from -13' to -18'
Back to the stand and with the transmitter and plane at the same level, call outs varied from -3- to -5'.
Powered everything back up, zeroed altitude, repeated test with similar results.
Perhaps span calibration is needed.
Both times when altitude was initially zeroed, call outs were from -.3' to -.8'.

Have you used your vario Lemon DSMP in a plane? If so, did you get believable numbers from it?
I reduced RSSI warn from 20 to 5 as I started getting "receiver low" alarms with the plane barely 30' away. No problems with control at any point, however.
Does raise the question: Does constantly transmitted telemetry "absorb" significant amounts of signal strength?

Vspd tones changed with climb, or descent but I need to get into the audio/haptics to assign monotones at a reduced frequency instead of the nearly continuous warbles given.

Font on your screenshot does look better.
Did you notice on my photo of the Telemetry screen that the Alt Zero values in ft are superimposed over the metric values there when the window is initially opened?
 
ErskyTx is just reporting the altitude as received from the Rx, the only processing done is to convert from metres to feet. This calculation is simply *105/32, which is about 0.01% out.
It may be the 'plane is higher than you think!
The altitude is sent to with resolution of 0.1m, so about 0.33 feet.
The altitude sensor is just a pressure sensor, and these can drift a bit as well as the atmospheric pressure changing over time, so some difference at the end of a flight is "normal". The relative height of the Tx to the Rx has no effect.
I don't think I've ever used the Lemon Rx for a flight, I usually use FrSky.
The Lemon Rxs usually repurpose the 'A' value as RSSI with a range of 0 to 100. To allow for this, there is an item in the telemetry menu: "DSM 'a' as RSSI". If you tick this, then RSSI will be reported with that range (0-100).

I've now fixed the text being superimposed on that screen in the source code! At some point I changed the way text is written to the display, instead of drawing a solid background with the text on it, I now only write the actually text.

Mike
 
Back
Top