guide_wpt_time or guide_wpt_time_to_finish in custom screen

c.s.g. shared this question 1 year ago
Answered

Hello,

I know the end of support of custom screens in Locus is coming closer and closer. Nevertheless may I ask another question, the last, I promise ;-).

I am using "guide_wpt_time" on my custom screen in order to show the estimated minutes and seconds when I get to a geocache. But the corresponing value shows always "00m 00s" on my custom screen. Therefore I replaced "guide_wpt_time" with "guide_wpt_time_to_finish". But the result is the same.

Is this so, because I use the guidiance mode and not the navigation mode to get to the geocache? I think, I read something like that somewhere, but can not exactly remeber.

As a possible workaround I found in the guidiance settings (http://docs.locusmap.eu/doku.php?id=manual:user_guide:functions:guidance#style_on_map) in the chapter "Style on map" the possibility to show time to target below or above guiding line. Is this value show "correct" when I am in guiding mode?


c.s.g.

Comments (13)

photo
1

Hi,


hmm interesting. This should work. I'm checking a code and it seems to be fine. If you wants, send me your custom screeen and I'll check it. Anyway why don't you use "dashboard"? Because of missing compass/rotate objects?

photo
1

Hi Menion,


Thank you for your offer. I will send you my custom screen this evening as an attachment to a new post of this topic.

And yes, I am using custom screen because of missing compass / rotate objects. But also the custom screen gives me a look and feel like on my old garmin device with all information on top of the map. But the second point gets more and more less important for me.


c.s.g.

photo
1

Hi Menion,


I have attached my custom screen for geocaching.

The layout is optimized for a Samsung Galaxy S4.


c.s.g.

photo
1

Good day c.s.g.,

unfortunately it works for me. If I enable simulation of movement I see correct times in your custom screen, check:

f03ad0631fc204992181eb1532e4dfae

Thanks to this, I've found that time "Time to target" defined in settings for guidance line was incorrectly used as ETA (time or arrival), so I"ve at least fixed it.

Don't know how I may help here thought.

EDIT: screenshot was took in 7:25, so ETA next to cursor is correctly 7:25 + time in custom screen cca 10 min

photo
1

Hi Menion,


thank you for trying it. I will continue testing it by myself. Maybe just another setting problem elsewhere in Android. If I can not fix it, it is not a big problem for me.

You wrote, that you enable simulation of movement. Where can I find this setting in Locus?


c.s.g.

photo
1

Hello,


should not be based on Android or ROM or something like this, weird. Anyway if I want to invest some time to this custom screen/dashboard system, I will definitely be Dashboard, sorry.


Simulation, weell I have some secret features :), but one option is to use recorded NMEA files. Any NMEA placed into Locus/cache/nmea will be offered directly in Locus when you "turn on" gps. Not sure if this is somewhere in manul, probably not as this is really mainly for "testing".

photo
1

Hello Menion,


I do not think this is a custom screen problem anymore. It is a problem (only) on my device.

Even if a set "Figure below guiding line" in "guidiance setting" to "time to target" no valid values are displayed or updated.

Or if i set "Information Field" in the "Main Screen and Controlling settings" (http://docs.locusmap.eu/doku.php?id=manual:user_guide:maps_mainscr_ctrl) to "Guiding" there are only zero values for "estimated time of reaching your destination" displayed.

So this have to be a problem of my own and not in general. Deleting and reinstalling of Locus Pro did not help. Maybe another app, like the co-app GPS Status, installed on my device will cause the problem.

But still, it is not really a big problem.


c.s.g.

photo
1

Hello,


I have to say that this is really not possible. Both times are based on this simple things:

1) distance to target - this value is probably updated correctly, you may see it on the map

2) your current speed - it's an average value from few last seconds. If you are moving (you see blue arrow on a map instead of blue circle at your location), then all should work correctly and I never heard that it do not work or that there is any problem. Key is real movement, not just playing with app on sofa ...

photo
1

Hello Menion,


I am a little bit closer to the solution of my "mystery" ,-).

I. e. a test with higher speed using my car shows the expected values everywhere I want to show them, even in custom screen!? Now as the next step, I have to get it work with my normal walking speed, usually abou 3 to 4 km per hour.

May I ask you a last time for your support and may you tell my your settings of "GPS & Location" and "Sensors". Thank you.


c.s.g.

photo
1

Hello Menion,


I found the problem: It is me ;-).

I. e. this evening I recorded a track of about 1,5 Km. Until 1,0 Km there are no values for "time to target" displayed. Then I walked a little bit faster for about 200 m. And while doing that values for "time to target" are displayed as long as I walked faster, even a little bit longer.

My assumption: I am simply to slow for delivering valid values for computing "current speed", Maybe I have to be at least 1 m/s fast in order to make it work, that Locus can work as expected. My average speed for the whole recorded track was 2,9 Km / h or 0,80555555 m / s. I am sure, sometimes on my walk I am even slower than 0,5 m / s ;-). And this may cause the "problem".


Conclusion: My settings are ok. I am only to slow ;-).


c.s.g.

photo
1

Hello,


good observation :). I found one quite old parameter that decided if speed says "I'm moving". This parameter was set to 1 m/s. And guess, this was a problem. So in your case, on most of time, Locus though that you are not moving. I've reduced this parameter to half, so average speed around 1.8 km/h should be fine. You will see in next version. Thanks, we found useful improvement!

photo
1

Hi Menion,


could it be that this issue is not fixed in Locus Pro Version 3.17.2?


I.e. I recorded a short track with a maximum speed of 4,5 Km/h (1,25 m/s) and an average speed of 3,1 Km/h (0,8611 m/s). Most of the time the value of "time to target" shows nothing (If necessary I can provide you with the recorded track).


Am I still to slow or do I have to set a parameter to get it work (maybe in the config file) or is there something wrong with the new implemenation?


c.s.g.

photo
1

Hello c.s.g,

I'm really sorry, I've found another place where was again parameter 1.0 and not new changed 0.5 ( m/s ).


So excuse me and give Locus another try in next version. Thank you.