Google Map on your transmitter screen

Hi Claus,
I checked it at the airfield today and the app is working correctly. I set the transmitter to speak out 4 values in sequence - triangle racing height, GPS absolute height, GPS relative height, vario relative height. The triangle height, and the two relative heights were all within a metre of each other, the GPS absolute height was higher by the field elevation. I will ask Dave to take a look in case he can think of why it is not working for you.

Hi Claus,

Thanks for the feedback and sorry for the problem.

First a workaround: there is a manual entry for field height in the settings menu, you can put the field elevation in meters there and it will be subtracted from GPS readings.

Now to help determine the issue, can you tell me what GPS you are using, and did you assign it manually using the Telemetry Sensors menu, or did the app automatically assign it? That will be a help to me.

It is our intent to do this automatically, so I would like to get to the bottom of it for you.

We get the field elevation from google maps, you can look at the file Apps/DFM-Maps/Maps/Fields.jsn and see what elevation we are using for your field if you are curious.

The penalties are computed according to the triangle racing rules gps-triangle.net/wp-content/uploads/2020...ns_sport_en_V1.5.pdf

In summary, if the max start height and speed are hmax and smax, and the entry height and speed are h and s, then penalty points are:
50 + 2*(s-smax) + 2*(h-hmax).

smax and hmax are settable on the race parameters menu and the default smax is 100 km/hr and the default hmax is 200m.

Dave

One other thing .. if you want to take a photo if your sensor screen with the GPS values showing, that would also help...

You don´t need to be sorry. It´s great that you relesed this App .
Maybe it´s also not a Bug but user-failure from my side.

My GPS sensor is a DIY Sensor from Nightflyer with a slightly modified Firmware.
github.com/nightflyer88/Jeti_VarioGPS-Sensor

I assigned the sensor manually. There was not automatic assignement done from the App.

Field elevation accoriding to the field.jsn is correct and matching real value.
This evelation is also shown as "ALT" value, when the plane is ready for start (on the ground).

My GPS provides following height values:
"Hoehe" = relative height
"Abs.Hoehe" = absolute height (<-- I used this value in your App).


Thanks a lot for taking care

By the way: What´s the reason for not using relative height in general and ignoring field elevation?

BR Claus

I see.. let me explain. Some GPSs have a choice of absolute or relative altitude. some have only relative and some have only absolute. For the GPSs we know about we have a file Apps/DFM-Maps/JSON/paramGPS.jsn which lists the channel names and configures them. I can add yours to the list for the next release. The screen you sent is everything I need for that.

For GPSs that are added manually, we assume they are relative altitude and do not subtract the field elevation. So for your GPS, since you can use absolute or relative, just choose relative and you will be all set.

Triangle racing rules require an absolute altitude and a supplied field elevation, which was part of our design consideration.

Perhaps I could also add an absolute/relative checkbox to the Sensor menu for a future release for manually added GPSs.

Thanks
Dave

Hi Dave,

thanks for your reply. It´s clear for me .

BR
Claus