Strict Navigation

[Joachim Buhl]

Hello All

Tell me, what I'm doing wrong.
Adding waypoints: https://youtu.be/DSeLveY_LSc

Also here. No announcements in simulation.
https://youtu.be/BFJttu7Sb0o
I think I know why.
The parameters where resetted to 0 at each program start. Strange. Only if I use one number it works. The seperator is comma, isn't it?

navigation_announcements_times=0

[menion]

Hmm I only see that existing waypoint it attached to trackpoint 29, because when you try to convert it to waypoint, it is not possible. But I do not see attempt to convert trackpoint 63 to waypoint, try it. If it will work, it only confirm that waypoint is just incorrectly attached to trkpt 29, that's all. Why this happen? Do not know ... it depend on how you created this route.

Btw fact that is incorrectly attached is also visible in waypoints desciption where distance to start is shorted then distance to end.

EDIT: and yes, separator is comma. Do you change this file when Locus is completely closed?

[Joachim Buhl]

Hello Menion

Locus closed, with task manager all apps killed.
With ES Explorer editor config changed to 15,35,300.
Saved.
Close file, open again to check if saved, check, ok.
Open Locus Beta, try to simulate, no announcements.
Close Locus, killed all.
Open config: set to 0

Bye

[Joachim Buhl]

Hello Again

I checked the waypoint thing with the same track, but shortened (see attached).
I created it within Locus with Mapquest routing and announcements.
First step over the first crossing. No announcement created by mapquest because its straight ahead, ok.



Than "around the block" coming back to this crossing second time. Mapquest creates "Left", ok.



If I save this track now and I want to add an announcement for the first way to the crossing (Point 4, "Straight"), I see that there is the "Left" of mapquest assigned.
If I choose the second point (39) I can add manually a navigational waypoint.

So the conclusion is, that Mapquest/Locus is placing instruction wrong when creating the route.

Thanks

Bye

[menion]

Uff, this one was complicated.

Anyway same issue should happen for all services, not just mapQuest. After looong testing, issues found and fixed and seems that now it works correctly. Thanks for a report and patience!

[Joachim Buhl]

Hello Menion

Great, Thanks.

Issue with announcement settings in config file is still strange. Yesterday I set it to only 15 seconds, but I got the announcements right before turn, sometimes too late :-).
 Today I set it to 45 and now they come around 20 meters before at bike speed.
But this is not 45sec. It's more like 5sec. Something is messed up.

Bye

[Joachim Buhl]

Hello Menion

Many many thanks Menion.
Strict navigation, manual added navi waypoints, no problems with overlapping tracks anymore, perfect for mountain biking. Thanks.

I have still problems with announcements.
And because video helped last time...
Announcements: https://youtu.be/_Ho31fKWfs0

Thanks

[menion]

Hello Joachim, nice vide, but sorry, I have absolutely no idea what to do with this. Seems you do all correctly.

Maybe, you may try always working cure - set new value, restart device, after a while, start Locus

[Joachim Buhl]

Hello Menion

Doesn't work.
Do you know what always works?
Deleting the file.
And than Locus creates a new one.
And then it's 15|35|300 , so seperator is | and not ,  .

Now it works but not with right time.
75sec in config file is more about 20sec, and 15sec in config file is 5sec. Strange.

Bye

[menion]

Hmm sorry for issue with '|' ... my mistake.

Issue with timings ... you are testing it in the field? Because I had no such troubles and I'm sure that such problem should be reported by a lot more people then just you ...

[Joachim Buhl]

Hello Menion

Yes, I did a 30km tour today with one announcement at 60sec according to config file.
The display timeout was 10sec.
The display timeout worked well (counted) and the display was always off right before the turn.
So the announcement comes around 10-20sec before even if its set to 60sec.

Thanks

Bye

[menion]

Joachim, sorry for a late response. I currently have no answer for you. It works, that if in Locus is any serious problem, more and more people contact us. In this case, you are still alone. After few days I'm leaving on 10 days on bike, so I'll try to use Locus guidance/navigation system as much as possible and hope, I'll find some useful info.

[Joachim Buhl]

Hello

I don't know why, but the problem is gone.
In simulation I can change the values to 5|20 and I get the same result as with 15|75 before. Tomorrow real life test. Strange.

Bye