Hello, I think that DC16V1 cannot be used for the app - it has no images and no colors, which are important for the app.
For F3B/F3F/F5B practice - it is good if you have not problem with these limitations:
- GPS speed/latency - Position detected by the GPS chip & telemetry is delayed approx. 0.5s from the real position. When you use "Pre-alarm" or proximity warning, it will be a working solution.
- GPS accuracy - normally the GPS has accuracy about +/- 2m. With increasing speed the accuracy goes worse.
- GPS glitches - sometimes, when the high-G turn manouvre is made, the position and speed is not measured accurately.
I tested our
(soon at Hepf) in F5F model and for speeds below 150km/h it worked very well.
Raf is correct, the app will not run on the DC16 .. in addition to the color issue, the memory usage is very large. The original DC 16 can only handle very small apps .. under 50K memory usage .. this app is 5-6x that size. We have been very impressed with the speed and scale that the newer Jeti systems can handle with lua apps.
I also agree that there are fundamental limits to telemetry latency in the Jeti system and the GPS sensors themselves. I have personally run the app with the Elite GPS logger which works very well.
The idea for this app was to get as much function as possible using the standard Jeti sensors and telemetry system. We don't expect it will be able to perform at the level of the much more expensive specialist stand-alone systems for triangle racing .. we are interested in feedback from pilots on how it performs for them.
We have seen this problem before on linux systems .. are you running on a linux system? If so, since the latest version of Jeti Studio was packaged with a version of OpenSSL that had a bug ... the fact that there is an expired certificate is causing this problem.
It should work find on other operating systems.
If you want to fix it, take a look at this article: letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/
If you remove the expired certificate, it will work fine since there is already another valid one. We had to fix this on our own system, Debian 10. If you want to know what we did, let me know.
Sorry for the inconvenience.