Frankie Arzu

@f2knpw I remember you did some work with RemoteID.. any comments. More info on the Open-Remote-ID specifications: https://mavlink.io/en/services/opendroneid.html

If we can send an RemoteID from the Plane/Drone, what do you think of the sensor naming? RID??

Added new sensors: RID: RemoteID/FAA ID (last 16 bytes) RIDs: RemoteID Flight Status.. 0..2... still figuring out RIDo:Owner (last 16 bytes) New Firmware: TX16S 2.9.3 + SkyID: https://github.com/frankiearzu/DSMTools/blob/main/EdgeTx_Firmware/edgetx_2.9.3-SkyId.bin LUA Script:...

Just cleanup.. i think is not needed. We can display it with a LUA script. Unless someone request it to be a proper edgetx sensor to write it to Telemetry...

Just an observation while reading the code: (Still have to test it) if you clear the telemetryItem when loosing telemetry streaming, auto-offset sensors will be re-started. For example, absolute altitude...

That will be great.. i have been trying to understand a complex plane template in SoarETX and having a name/comment for the Logical switches will help a lot.

Same behavior in 2.9.2 and 2.9.0 All the sensor values are internally stored as integers. The PREC affects the display only of the sensor, by multiplying/dividing by a power of...

Just adding comment to  At least in sensor, precision also describes how the value is coming from the telemetry feed. In telemetry, everything is an integer.. so a value...

That method of delay seems weird "while (time + 10 > getTime()) do end", the run() function should do work and exit as soon as it can. Also using CPU...

The challenge with embeded programming is that is not like traditional PC software. In many embeded systems, they use what is called "Cooperative Multitasking" that is that a running task...