QUESTION: DFM-SWT - by Dave and Harry

hello harry, hello community

do I understand right, the app reads my sensors and I can assign thee to one of the 4 switch positions (1-2-3 toogle or long switch)
so far so good, the app announces the value and in the app I can choose the unit an decimals

when testing with an existing model the default jeti single seech anouncements out put is offering the option of a speechfile, so the output for a height sensor value can be:

<spoken wav file e.g.> HEIGHT <followed by the actual value e.g.> 304.6 <followed by the unit e.g.> metre

when testing the app it just puts out the value on the appropriate toggle action, am I doing anything wrong or is that by design no pre-wav and no post-unit just the value?

It does speak the pre-wav and the units for some items, I will ask Dave to give a better explanation!

Hi sf,
The app tries to have a wav file for common telemetry sensors, these are in the DFM-SWT/en and DFM-SWT/de directories. The wav file says the name of the sensor, e.g. "Altitude". But the app can't possibly know all possible sensor names, so you may have to add a wav file for a sensor name it does not know. For example, for sensor name "Volt" you would add Volt.wav (it's case sensitive) to the directory. And of course you can change the wav files that are there if you prefer something else.

I would be happy to extend the list of sensor names to other common ones that pilots would like to see.

For units, a similar problem exists. We do read the Jeti model file for the model the app is installed in, and we look for units for the sensor in question, but if there is no unit in the Jeti TX sensor table, then we don't announce a unit.

The app could be changed to allow pilots to add units and corresponding wav files but we have not done that.

Hope this helps
Dave

hey dave and harry

thx for your reply, x-mas coming plus I have jobwise and family-affairs that keep me more than busy but I am willing to help as much as I can

the sensor values I used where coming from sm-sensors, and I had no announcements at all, just the 0 figures for altitude and capacity
BUT I guess it's because the model respective receiver and sensor where not powered up
so I have to test and see what is limiting where - gimme some time please but will for sure give feedback, promised

as for the files and the logic used, I have not peaked into the app yet, just did a very fast quick install test
will check that too and come back to you

and last not least ... for the john-doe user it would be very nice if they app would follow settingswise the logic of jeti screens that are known
what I want to say is, it would be nice if there was
+ add sensor
get the f sensor switches and than for each a page where all is cumulated
- what shall happen
- wich file pre-announcede to be selected or none a default fallback
- wich unit again, select or default
- enter save back
next option/switch state

but again sorry I have just had a quick glance and will take time to look in deeper

what is sm-sensors? a sensor from sm-modellbau? I have their GPSLog3 .. if that is wht you are referring to .. what telemetry value was it?

it is an unilog bei sm-modellbau.de in that case, I use loads of unilogs and unisens
the sensors where height and capacity

rgds
guido