THEMA:

I am thrilled to present Dave McQueeney's amazing LUA application that puts a Google Map on your transmitter screen. With this you can see the position of the model in real time, see its track history, colour code the track with a telemetry value, get spoken warnings about no-fly zones, and do GPS triangle racing. This app has taken a lot of development but it is very sophisticated and we are sure that you will find it very useful.
The training comes in 3 episodes, episode 1 deals with the basics, episode 2 the no-fly zones, episode 3 GPS triangle racing. The end of each video contains a link to the next video.
I have spent a lot of time editing the youtube sub-titles to be proper English language so that if you choose sub-titles automatically translated into your language it should make sense!

Two very nice programs. In particular, the map creation program. That must have taken a lot of time....

Relative to an older version, the speed and altitude indications are missing from the sides of the screen.Have they been removed from the program?

Maybe it is an idea to make the image of the aircraft on the screen with the map selectable. Not everyone flies a jet. An image of a glider or motor plane would be more realistic.

Nico.

NicoS schrieb:

Two very nice programs. In particular, the map creation program. That must have taken a lot of time....

Relative to an older version, the speed and altitude indications are missing from the sides of the screen.Have they been removed from the program?

Maybe it is an idea to make the image of the aircraft on the screen with the map selectable. Not everyone flies a jet. An image of a glider or motor plane would be more realistic.

Nico.

Small screen easily gets too cluttered with info.
Different aircraft symbols are available but selecting them has not been built into the program yet. Perhaps it will be in an update. If we had not said "that is enough!" then the app would never be finished and never be published.

Harry is right that it's not built-in in a convenient way .. but .. there is a way if you are willing to do some file editing are comfortable with a simple json file. I apologize in advance if this is too geeky an answer (see below).

Regarding speed and altitude .. they do come up when a triangle race is in progress, but we were seeking to declutter the screen. We could consider putting some back, perhaps as a menu option.

Regarding the icon:

After you download the app, look in the directory Apps/DFM-Maps/JSON on your Tx.

Suppose your model name is "Glider2" you can create a file Glider2_icon.jsn and the app will use that json file as an image when running with the Glider2 model. You'll see in that directory the T38.jsn icon that is the default, as well as glider.jsn which a user contributed. You can follow them as examples. They are just simple line drawings and if you are fluent in json you can make your own.

Happy to include more in the distro if you want to send them along

If you have spaces in your file name e.g. "Glider Number 2" then replace the spaces by underscores to make the file Glider_Number_2_icon.jsn.

The glider picture was contributed by a test user in Australia several years ago, I don't recall who but I'd love to give him credit!

Dave

Hi Harry and Dave,

great job!

Thanks a lot for all your efforts in creating this user friendly tool (Map creator) and publishing this App for everybody.
Must have been a massive workload. Well done !

It´s fun to make some GPS Triangle flights only using the transmitter without any additional auxiliarrys .

I just recognized some issues with "height values".
When using absolute height as input value,it seems as the app is not calculating the relative height by using field elevation of the maps.
It always displays absolute height. For example I also get "penalties" while GPS Racing as my field elevation is already exceeding the "max start height".

Did I made any mistake?

By the way: do you have some informaition about the "GPS-Penalty" calculation?

Thanks and best regards
Claus

I will check that as soon as possible Claus. It was one of the items we fixed about 4 weeks ago and we got it to agree with the GPS relative height and with the vario relative height, but maybe an error has crept back in.