Hy,
so , damit wird es etwas klarer, wie die TelemetrieFelder in V2.1 zu behandeln sind, damit bestehende LUA Scrpte laufen sollten..
if I understand the user could name her/hist altitude "anything" instead of "alt". Is that right ?
And (s)he'll have to configure the inputs we're using in the scripts ?
If that's the case, sorry guys, I don't share the enthusiasm. From the user point of view, it's really not an improvement
-----------------------------------------------------------------------------------------------------------
There are NO telemetry fields predefined in 2.1. you have 2 options!
1. set every sensor you're using up manually - you'll need the sensor IDs to do this.
You can name each sensor whatever you like (4 characters).
or
2. turn your model and tx on, and the sensors will be automatically configured on the tx. so far this seems to work fine, and the sensors are given default names, Alt, VSpd, Temp, VFAS etc.
BUT, there is nothing to stop you renaming them if you wanted to for some reason.
you could also adjust the units, precision, range, offset etc for each sensor, allowing more sensors to be used for more things
I would assume most people would use the auto-discovery option,
and leave the sensor names as they are, but yes, they could be anything.
so , damit wird es etwas klarer, wie die TelemetrieFelder in V2.1 zu behandeln sind, damit bestehende LUA Scrpte laufen sollten..
if I understand the user could name her/hist altitude "anything" instead of "alt". Is that right ?
And (s)he'll have to configure the inputs we're using in the scripts ?
If that's the case, sorry guys, I don't share the enthusiasm. From the user point of view, it's really not an improvement
-----------------------------------------------------------------------------------------------------------
There are NO telemetry fields predefined in 2.1. you have 2 options!
1. set every sensor you're using up manually - you'll need the sensor IDs to do this.
You can name each sensor whatever you like (4 characters).
or
2. turn your model and tx on, and the sensors will be automatically configured on the tx. so far this seems to work fine, and the sensors are given default names, Alt, VSpd, Temp, VFAS etc.
BUT, there is nothing to stop you renaming them if you wanted to for some reason.
you could also adjust the units, precision, range, offset etc for each sensor, allowing more sensors to be used for more things
I would assume most people would use the auto-discovery option,
and leave the sensor names as they are, but yes, they could be anything.
