Separate beeps for left/right turns when guiding along a route.

Krzychu L-ski shared this idea 19 days ago
Collecting votes

When I use the AndroidPhone for navigating outdoor I use the phone's Speaker instead of headphones. The idea for mine and the other requests is to AVOID looking at the device during guidance/navigation. It would be nice to have in GUIDANCE the following new features:

1. Separate entries for left/right turns as beeps when following the route.

2. Separate entries for left/right as beeps when out of the route.


Do you think I may propose the functionality in the Help Desk?

Thanks.

Krzysztof

Comments (19)

photo
0

Hi Krzysztof,

go to Locus settings > Guidance > Notification of next turn > enable it and select beep, own sound or text to speech.

When guiding along an imported route, please be aware that Locus generates voice commands according to the shape of the route line, not according to intersections, because it doesn't know the nods (unlike the router). therefore, sometimes not all turns are announced, or vice versa, some road bends are announced without need.

best regards

Michal, Locus team

photo
0

Dear Michał,

Thank you for your response. I'm OK with the fact Locus generates commands according to the shape. I would like to have two separate notifications whether the imported route bends left or right.

Thank you.

Krzysztof

On 5 Aug 2019 09:59, Locus Map <locus.map@asamm.com> wrote:

photo
0

Hi Krzystof,

set text-to-speech as your guidance alert - it will announce where to go right ot left.

best regards

Michal

photo
0

Following GPX route with turns left/right works great in navigation but not with guidance with beeps. I thought I would like to configure 2 beeps to turn left and 4 beeps to turn rights in guidance. Currently it's not possibile. I prefer beeps as it's uses less battery than text-to-speech.

Today I will try the guidance anyway with text-to-speech to confirm.


Do you think its possible to incorporate that function (beeps left/right) ?


Thank you.

photo
0

Hi Krzysztof,

it is possible to use something similar to your needs in the navigation mode. Download "Morse Voice Samuel" from Locus Store and select it as the navigating voice in the navigation settings (https://docs.locusmap.eu/doku.php?id=manual:user_guide:functions:navigation:settings#select_voice).

best regards

Michal

photo
0

Hi Michal,


That workaround helped a little bit. I tried to test it in the town and encountered some issues. Not sute how it's going to work on the MTB trail in the mountains. Having implemented function for left/right turns in "Guidance" would resolve the issue.

Thank you for your help and assistance. I really appreciate it. Once again, Locus Maps it's a great software!

Best Regards,

Krzysztof

photo
0

Hi Krzysztof,

there is a similar idea at our helpdesk: https://help.locusmap.eu/topic/in-guidance-mode-beep-correspondingly-left-or-right-audio-channel-when-out-of-course. You can vote for it. Nevertheless, it got only 2 votes in three years so it's quite improbable this option will be implemented.

best regards

MIchal

photo
0

It is slightly different functionality request that what I'm looking for. When I use the AndroidPhone for navigating outdoor I use the phone's Speaker instead of headphones. The idea for mine and the other requests is to AVOID looking at the device during guidance/navigation. It would be nice to have in GUIDANCE the following new features:

1. Separate entries for left/right turns as beeps when following the route.

2. Separate entries for left/right as beeps when out of the route.


Do you think I may propose the functionality in the Help Desk?

Thanks.

Krzysztof

photo
1

Just curious.

I tried to test it in the town and encountered some issues.

Some issues = ?

photo
1

Can you please vote for this guidance function please? Thanks

photo
photo
1

Hi,

I unpacked the morse code sounds and realized that "left" turns are indicated as 1 beep and "right" turns as 2 beeps. When attempted to navigate a few times I got 2 beeps (right turn) but the route on screen was showing "left".

I can't understand why and what's wrong.

Best regards.

photo
1

A. Design is correct ? Have a look here. Maybe identical design problem ?

https://help.locusmap.eu/topic/confusing-arrows-and-voice-commands-during-route-navigation#comment-62069

B. In Navigation setting > advanced > Two commands at once: Uncheck !


(By a file edit change the used sound, into any sound you eventually do prefer ! )


By the way, I do know the (correct) morse code, so why a T (morse) "dash" for Left, I (morse) "dot dot" for Right and S (morse) "dot dot dot" for Straight ?

1. Most compact and simple to remember. (Tested by persons NOT knowing THE code).

2. In my country, (work)horses guided by a single line even know the (morse) method.

Long line pull is Go Left...double short line pull is Go Right. .... So.....

photo
1

Hi 0709,


Thanks for the tip, I will try that soon.


I use the Locus Maps mainly for MTB off-road rides in the mountains.


I found "guidance" more accurate than "navigation" when following imported GPX route. The guidance configured with beeps uses less device's energy than Text-to-speech in navigation. Additionally when following GPX track I do not need to have a map loaded. Overall guidance is roughly 30% more energy efficient than navigation.


The problem I have is mainly when descending fast and "guidance" informs about turn (left or right). Currently I have to stop to look at the device to figure out whether to turn left or right. With proposed function I can hear the notice to turn left or turn right without looking at the device.


/PS: please vote for this new Locus enhancement.


Kind regards,


Krzysztof

photo
1

More energy efficient ? Navigation <=> Guiding 30 % ? Wow.... Did you monitor measure ?


Never display on ? No map look ? Never ?


Anyway by (morse beep) (TTS) navigation it is sure possible to cycle without continous display on (THE largest power consumer), or even without auto screen on_off method triggered by nav announcements.


When the phone is mounted at the bike handle bar. Open and close screen display by the comfortable (little power consumer) gesture method.


Some MTB cyclist (active here in this forum) sure do use (a free combination of) all such available Locus methods.


I notice FAST descends so such means fast speed changes along track.


See:

https://help.locusmap.eu/topic/transfer-function-in-config-cfg-to-gui-navigation-expert-setting#comment-73540

photo
1

As MTB we use the function: With a navigation instruction or guidance beep, the screen turns on automatically. This then goes off after 5 seconds (adjustable).In addition, some use a remote control. So you can manually include the screen with a button via Bluetooth. The button is next to the brake. I do not have a link right now.

photo
1

All you need to do is check how much energy the luminous screen has used in the phone's application and the answer will be jasan, each display gets depending on the type of backlight consumes a different amount of energy, and depending on its resolution (here more or less current is downloaded by the graphics card).


The idea with the signals is very good, I'm waiting for it to work, on a few hours trip there is no problem with battery maintenance, but if you participate in multi-day trips / races without electricity, every hour more device works :) greetings

photo
1

Hi 0709,


My measures show 20-30% energy save guidance (beeps) over navigation with T2S. My goal is to never look at the display. I don't want to keep my phone on the handlebar on fast sheaky descends. I prefer to keep in in my back pocket when riding.

With current guidance configuration I need separate beep entries for left and right turns.

I can configure 1 beep for left turn and 3 beeps for right turn. Then display is used!


Kind regards.

photo
1

Hi freischneider,


Good tip, thanks. My phone must remain in the back pocket on fast / sheaky descends. Additional BT device to charge? - no, thank you, Just me, bike and smartphone (Locus).


Kind Regards,

KL

photo
photo
1

Good day Krzysztof,

interesting idea. Why text-to-speech notification option is not suitable for your needs?

Extra settings sound too complicated for me, but what about adding different sounds for these four cases? Are we able to create four different beep sounds that will be different enough, to correctly notice it during a ride? Such solution should be directly hard coded in the application without the need for more settings.

Menion

photo
1

That's right, the proposed functionality must be hard-nosed into the Locus app under "Guidance" settings.

Thanks

KL

photo
photo
1

Hi Menion :)


I use the Locus Maps mainly for MTB off-road rides in the mountains.


I found "guidance" more accurate than "navigation" when following imported GPX route. The guidance configured with beeps uses less energy than Text-to-speech in navigation. Additionally when following GPX track I do not need to have a map loaded. Overall guidance is roughly 30% more energy efficient than navigation.


The problem I have is mainly when descending fast and "guidance" informs about turn (left or right). Currently I have to stop to look at the device to figure out whether to turn left or right. With proposed function I can hear the notice to turn left or turn right without looking at the device.


/PS: please vote for this new Locus enhancement.


Kind regards,

Krzysztof

photo
2

Hello,

understand, but why "Currently I have to stop to look at the device to figure out whether to turn left or right." ... if you select Text-to-speech? It should directly say which turn to take.

/254e780bd00fcd2e31ac774d094bffdb

photo
1

Small sorry for hijacking this thread. I've merged the duplicated topic made by Krzychu, where we already partially discussed this feature. Sorry for double notification emails and thanks for understanding.

photo
1

but you can't assign either speech or any signals to the information "turn right", "turn left" because there is no choice if I understood it correctly, what you mean

photo
1

As I mentioned earlier I don't want to use Text2Speech with the noisy wind in the ears It's hard to understand any T2S voice. For this reason I prefer Beeps. In guidance there is only one configuration item for all turn. I need separate options for left and right turns.

photo
1

Well said Michał. For multiday unsupported events every piece of energy counts.

Hi Locus, please implement this feature into the app. Thanks

photo
3

[Quote] Overall guidance is roughly 30% more energy efficient than navigation.

Impressive 30 % ? Must be dedectable > Test.

After Locus install > To do: Degrease too many (bla bla bla) Locus Navigation instructions by:

Navigation > TTS > * Compact TTS by edit xx.tts - ** Single announcement by edit config.cfg - Two commands at once uncheck

Navigation > Voice Morse by Locus store. > ** Single announcement by edit config.cfg - Two commands at once uncheck

Airplane mode - Display continuous OFF ! - Battery 100% charged - Virtual drive by Lockito.

Measurement by simple USB powermonitoring tool (non professional).

Powerconsumption indication over 40 minutes/mode - (4 x identical testdrive/circuit).

Result:

Navigation by TTS: 0,628 Wh

Navigation by Voice Morse (L/R/S/+): 0,636 Wh

Guiding by TTS: 0,698 Wh

Guiding by tone (3 beeps): 0,642 Wh.

* examples: https://forum.locusmap.eu/index.php?topic=3245.msg49934#msg49934

(Use google translate & login to the forum to find the attachments)

** # times before command, when Locus notify (in seconds), default is: 15|35|300navigation_announcements_times=15

[Quote]/PS: please vote for this new Locus enhancement.

e735a0c1ac37ae851a32cd792f49f77e

Frequency - Speed - Code ? http://www.morseresource.com/morse/makemorse.php

photo
1

Guiding ONLY by tones ?

Instructions by code sounds (morse) in the guiding modus for ontrack L/R/S (all variants slight/sharp) no problem.

Be guided (no street pattern/recalculation) toward the track position by sound ONLY is more complicated ?

hmm...No Display View.. ONLY by Sound (tones) ?

I was thinking at the * Lorenz navaid system > but ear comfortable, by on track muted 'equi' signal.

1. The optimal 'equi' small range by: SET off track trigger (32m)

2. Off track: Generate guiding tone indications toward track by:

- Continuous (low comfortable tone frequency) dot zone > move rightwards.

- Continous (low comfortable tone frequency) dash zone > move leftwards


Reversed sound pattern ? = You are moving into the "Knickebein" reversed direction ;-)


To Test: Find prefered comfortable lower tone frequency and ritmus.

Out of track warning correction is only occasionally and temporarily !


Attached: example (400 Hz) and (330 Hz).

A fastly produced demo. (Dots could be shorter and dashes be longer ?)

Corrections: "Move rightwards / Equi / Move leftwards".(Not sure if people (MTB) would love the 'noise')


* https://en.wikipedia.org/wiki/Lorenz_beam

photo
1

Thanks 0709

photo
1

As you noted by wiki info, the Lorenz system was developed to follow a straight bundle line, although some wanted to "bend" the indication ;-).


Would such a +/- method work successfully as a guideline for the continuously "bending" MTB paths?


How did a Lorenz signal sound? Demo sound @ 7:20 min.


https://youtu.be/kDv1ELePCnU

photo
1

Question was: Generate off-track alert tones with direction info to the route. No display viewing! So a regularly recurring signal is needed. (Usefull for Locus Guiding and Navigation)


Test 1: Lorenz signals simulated with audiopulse generator. Conclusion: Unsuitable due to hearing uncomfort at longer use.


Locus setting off track alert preferred:

(Set 2x): Free pattern (._) // (_.) and frequency (xxxx Hz) and pause (xx sec).


Test 2: Frequency 440 Hz for better hearing comfort.


Hint "off track"> track is on the right> Morse letter A (dot_dash).

Hint "off track" > track is on the left> Morse letter N (dash_dot).


Attachment: Example audio with a short interval.

In real use, I would set longer (xx sec) breaks.

photo