Fun with full-screen telemetry!

Hallo Reinhard,

finde deine App klasse, das ändern der einzelnen werten geht supper nur was ich noch nicht ganz so verstehe wie mach ich das dann Modell spezifisch dann benötige ich mehre apps und auch mehre JSN Dateien richtig??? Würde sie jetzt zu gern auf dem sender spielen.

Mfg
Thorn

Hello,

I'm taking a different approach to solve my specific needs. but hope it helps.

My approach. I'm creating an integrated screen that includes all the MUI or MEZON sensors, and it adapts to the different scenarios:

Sensors on screen:
Instant and Max Battery Current
Battery Consumption
Instant, Max and Min Battery Voltage
Instant Energy (only available when using MUI, and only available on MUI updated to 2.03)
Motor Timer
Instant Receiver Voltage

Graphic representation on screen:
Battery, with four levels of warning, customizable.
Battery Consumption percentage.

Sensor detection:
even if more sensors are connected, the INTelemetry application only allows to select any MUI or MEZON sensors

Embedded warnings:
For the battery consumption, three warning levels are customizable, both in terms of level (as percentage of available capacity) and as a sound message.
For my configuration, I use:
Green: above 80%
Blue: between 80% and 67%
Amber: between 66% and 31%
Red: 30% and below.

If the sensor gets unavailable (for example, if Q is weak) the sensor text changes color, taking into consideration how long the signal is lost. The time is not customizable.
Blue: 500 millisecons without valid sensor
Amber: 2 seconds without a valid sensor
Red: 5 seconds without a valid sensor

The INTELemetry uses the system color profile where possible.

TODOS:
Incorporate MEZON-specific readings, such as PWM and motor speed.
Evaluate/incorporate the option to include other graphic sensors, such as horizon, bearing, airspeed for one plane where I have a fuller suite: GPS, RexAssist, Speed Sensor, Vario and Mezon.
Evaluate/incorporate the option to use a SBEC with telemetry when using Opto controllers, and to have that information also on screen.
Evaluate/incorporate the option for telemetry, including second receiver, backup receiver and/or central box.
Use warning colors that make sense depending on the color profile (example: in Warm Red the foreground color is red, as my alert color... not useful).
Have some sensors to be persistent and reset only when a specific switch is used and not when I turn off the receiver.
Include translations to German, French, Czech, French and Portuguese. At the moment, the application is available in English, Spanish and Italian, with other languages defaulting to English.


I've been able to keep the code as efficient as possible, and at the moment it looks that it should work on a 16 (not confirmed).

that looks very nice thank you for the great work. to test later.


Sincerely
Thorn

Hello abief

i have copied:
InTel.lc -> Apps
InTel .. lang ..en/de (usw) . -> Apps

If i load the Applikation i get

Error in InTel: bad argument #1 to 'decode' (string expected, got nil)

to wich Path must i copy the language Files

Gruß Reinhard

Ich würde vor allem mal keine App laden die keine *.lua-Datei dabei hat um den Code zu kontrollieren!!!

Above all, I would not load an app that does not have a * .lua file to control the code !!!

Hallo zusammen
Am Simulator ist es vollkommen unproblematisch ein .lc Programm zu laden,
Jeti Lua ist ein Interpreter ohne die Möglichkeit C-Teile zu laden, set Aufrufe kannst du auch in der vorcompilierten Version erkennen.
Um mal zu sehen, was andere wie gelöst haben ist das für mich vollkommen ok.
Ein komplexes Source Programm (LUA) kann man ohne viel Arbeit auch nicht überblicken.

Gruß Reinhard