Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - 0709

Pages: [1]
Versions / Re: [APP] - version 3.20.x (31. 10. 2016+)
« on: November 16, 2016, 21:36:29 »
TTS = minus 2
The following users thanked this post: michaelbechtold

Versions / Re: [APP] - version 3.20.x (31. 10. 2016+)
« on: November 13, 2016, 20:09:16 »
Hi Menion, understand, and sure, of coarse correct.
Most important, improve very nice function, make tool more reliable.

DTSO test. See previous video.

DTSO Single wave: Detects "one wave" events of 100ms or >> longer.
Wave detect, ranges from a single fast, medium to very long wave even to simple touch mode.

DTSO flip cover action: Reliable: Exact same functionality as well known screen off at phone calls, phone near face.

DTSO Adviced usage:
Single wave, touch mode: Cycling, phone on bike handlebar, continuous view on free display.
Double wave: Walking, phone in and out pocket.
Flip cover: Phone in and out pocket, or flip cover open or closed = Direct excellent screen off/on action for walking.

Flip cover proximity control by DTSO and Locus Navigation:
The following users thanked this post: Sersus2

Commentar in attached  text and the attached demo tcx course test file.

[EN]Navigation data source: Brouter (cycle)
Auto recalculation: Point Priority
Distance for recalculation: 100m
Out of route notification: Alert distance 75m // Single beep repeat every second.  (not important = personal setting)
Advanced settings: Strict Route following (see message in comment txt).
Maximum allowed deviation: 75 m
Snap to route: off
Number of commands: /not necessary/ using  prepared track with navinstcuctions included.
Two commands at once: Set.  ( not important = personal user preference).
The following users thanked this post: reha73

[DE] - deutschsprachiger Forumsbereich / Re: bei Navigation 2 Cursor
« on: October 01, 2016, 14:50:24 »
[EN] Settings->Navigation->Advanced settings->Snap to route.
The following users thanked this post: balloni55

Wan ich es richtig verstehe ist Zielführung in English "Guiding" nicht ? 
Locus hat eine specific Guiding modus.
Aber hier bemerke ich es geht sich seit amfang beim schreiben ubers thema Navigation.

So nächtste commentar dan specific:
Der Locus Navigation;

@ Reha @..... @ .....!

Importierte track gpx. 
Source ?  Brouter web turnInstructionMode  = 2 ? 
Oder source: gpx trackfile ohne exported profile by locus extension ?

Using Locus Navigation autorecalculation "Point Priority" ?

1.  Brouter web exportiert keine [EN] Via Points (=Priority Points) oder [DE] Zwischenziele.
So beim auto-recalculation triggered durch "out of track" position wird dan neu berechnet direct zum Finish !

2. track ohne berechnungs profile.
Erstmals in actuellen Pro version 3.18.9 durch kurze antippen Navigation Anweisung panel:
In Neuberechnung select (Fahrad) modus (nun lange drucken), bestätigen der modus, danach menu verlassen, so keine neuberechnung starten !   
Der actuellen Locus setzt beim neuberechnung immer der KFZ modus bei JEDEN navigationsneustart !
Diese KFZ liebe, soll sich änderen und functioniert in actuellen Beta.

Problem 1 lösung:
a. Generiere der navigationstrack in Locus_Brouter app. Export gpx 1.1 track inclusive "Zwischenziele" (original config.cfg !).
b. Oder autorecalculate OFF, zuruck zum track mittels der alte gute methode, durch "guide line". 
c. Oder alternativ autorecalculation durch 'Route Priority".

Problem 2 lösung:
Generiere der navigationstrack in Brouter web oder Locus_Brouter app. Export gpx 1.1 track hat dan der correcte profile dabei.

Mehr flexibilität beim setzen von Priority (INFO) Punkten is erwunscht: 
So bitte..deine + stimmen und am besten eine kurzen commentar dazu.
So bleibt idea in top der liste, actuel und activ.
The following users thanked this post: reha73

Is correct und functional by gpx 1.1 (extensions Locus) : <locus:rtePointAction>50</locus:rtePointAction>

Die Navigation mit zwischenziel functioniert gut.
Und shau mal diese idea's, so köntte man comfortabel editieren direct in Locus_Brouter combination.
Idea: Frei setzen einer punkt, ist oder ein Via = Zwischenziel, oder ein punkt "shape" (wird nicht gespeichert) in der edit function "Route and Measure".
Setzen einer punkt IMMER etwas entfernt (zu beispiel in 50m entfernung) einer junction, wo anderseits der automatic routing möglich eine  navigation anweisung L/R/S positioniert !
Eine ganz functionelle informative 'Via' durch freie <name>(gpx) wahl und <desc>gpx. Der gpx<name> angekundigt mit sprache TTS und gpx<desc> mit text display.

Details in beilage and a gpx test file Locus gpx 1.1 in my previous example testfiles.

"Spielen" sie mal eine navigation 'virtual' nach und bemerk der TTS sprache und der text info in schirm. 
Informatives navigation punkt UND zwischenziel function zugleich !

The following users thanked this post: erfi


- Bis nächste version: Nicht benutzen !  Aufzeichnung nur während der Bewegung.
The following users thanked this post: Reniar

@ Andrew.
I tested your tracks  (from Long and short navigation works perfect on TAB4 or THL4000.
@Poutnikl. I know = before generated by Locus.

NEW EDIT: Both tracks are inclusive navigation hints !  (Also notice my used equipment for details)

Succesful Navigation start on the Samsung TAB4. Locus V3.17  (The most used tab for on desk "virtual" tests)
Sucessful Navigation start on the THL4000. Locus V3.17            (The mobile unit in use)

Unseccesfull Navigation start on the  the Samsung Tab Pro: Locus V 3.16.1 (needs push on nearest point)
After updating:
Unsuccesful Navigation start  on the Samsung Tab Pro: Locus V 3.17  (needs push on nearest point)
Unsuccesfull Navigation start on old Android phone: V 3.15.3.  (needs push on nearest point).

Extra EDIT:
Same testcircuit by .tcx file and exact the same report as above.
2 x succesfull  and 2x need a push on nearest point to start.
Attached: the tcx file.
The following users thanked this post: Andrew Heard

Versions / Re: [APP] - version 3.16.x (14. 3. 2016+)
« on: May 11, 2016, 17:53:08 »
From reply # 145.
they need to disappear as a default. Like with panels the USER decides if they should be visible all the time. If hidden, slide from left, or double tap can bring them to surface.

- By double tap bring ALL panels in front, then disappear.
- Allows to place dashboard near the screen boarder, and more visible map area.
- Navigation: If description available display<Notes>(gpx=desc) only, otherwise display<Name>(gpx=<name>) only.

EDIT: The missing info: Turn sharp right onto track road  (In portrait mode !)
The following users thanked this post: michaelbechtold

Pages: [1]