Unstable connection to Bluetooth GPS HC-06

Hi Bernhard,

there are some tips in this user guide article: https://docs.locusmap.eu/doku.php?id=manual:faq:bt_sleep_issues

Hi Michal,

Thank you for your prompt response.

I've already tried everything you suggest.

My BT modem also works. I also tested it with BT terminal programs with stable connections. The problem only exists with Locus Pro for external BT-GPS receiver. I am at a loss.

If you have any ideas, please let me know.

greetings from Vienna

Bernhard

Am 23.01.2019 um 13:38 schrieb Locus Map <locus.map@asamm.com>:

Hi Bernhard,

could you please try this experiment:

- switch on NMEA recording in your Locus settings > GPS&sensors > NMEA recording > always

- turn on your BT GPS and let Locus record NMEA data for 5 minutes

- turn Locus off and send me the NMEA file stored in /Locus/data/nmea directory

Thanks

Servus Michal,

Thank you for your assistance in solving my problem.

The folder NMEA data is completely empty.

For comparison, I send you a data telegram from a terminal software (Serial Bluetooth Terminal 1.18 ), while the BT connection remains completely stable.

If I connect my BT modem (HC-06) without data content with the terminal software, the connection remains stable.

When I connect my BT modem to Locus Pro, the rhythmic connection aborts.

Gruß aus Wien

Bernhard

12:58:24 Connecting to HC-06/10 ...

12:58:26 Connected

12:58:26 E

12:58:28 $GPGGA,000000,4816.1665,N,01622.6284,E,1,04,3.74,0,OE1PKW,+8,,*3E

12:58:38 $GPGGA,000000,4816.1665,N,01622.6284,E,1,04,3.72,0,OE1PKW,+8,,*38

12:58:46 Exported configuration to clipboard

12:58:47 $GPGGA,000000,4816.1665,N,01622.6284,E,1,04,3.75,0,OE1PKW,+8,,*3F

12:58:56 $GPGGA,000000,4816.1665,N,01622.6345,E,1,04,3.75,0,OE1PKW,+8,,*33

12:59:05 $GPGGA,000000,4816.1665,N,01622.6345,E,1,04,3.74,0,OE1PKW,+8,,*32

12:59:15 $GPGGA,000000,4816.1665,N,01622.6345,E,1,04,3.77,0,OE1PKW,+8,,*31

12:59:24 $GPGGA,000000,4816.1665,N,01622.6345,E,1,04,3.74,0,OE1PKW,+8,,*32

12:59:33 $GPGGA,000000,4816.1665,N,01622.6345,E,1,04,3.77,0,OE1PKW,+8,,*31

12:59:43 $GPGGA,000000,4816.1665,N,01622.6345,E,1,04,3.77,0,OE1PKW,+9,,*30

12:59:52 $GPGGA,000000,4816.1665,N,01622.6345,E,1,04,3.77,0,OE1PKW,+9,,*30

13:00:01 $GPGGA,000000,4816.1650,N,01622.6349,E,1,04,3.75,0,OE1PKW,+8,,*39

13:00:10 $GPGGA,000000,4816.1650,N,01622.6349,E,1,04,3.76,0,OE1PKW,+8,,*3A

13:00:20 $GPGGA,000000,4816.1650,N,01622.6349,E,1,04,3.74,0,OE1PKW,+8,,*38

13:00:29 $GPGGA,000000,4816.1650,N,01622.6349,E,1,04,3.74,0,OE1PKW,+9,,*39

13:00:38 $GPGGA,000000,4816.1650,N,01622.6349,E,1,04,3.74,0,OE1PKW,+8,,*38

13:00:47 Disconnected from device

Am 25.01.2019 um 10:28 schrieb Locus Map <locus.map@asamm.com>:

Hi Bernhard,

how do you connect your BT GPS to your phone? Directly to Locus via its bluetooth manager or via some third party app like "Bluetooth GPS"?

BR

Michal

Hi Michal,

Yes, after restarting the smartphone I start Locus Pro and connect via B via the BT-Manager in the app.

The green info field "Connected to HC-06" is also displayed. After a few seconds, the orange info field "Device connection interrupted" appears, again a few seconds later the information field "Connected to HC-06" and this is repeated again and again.

I've also tried this with other Android smartphones (V 4.2.2) and various HC-06 BT modems.

With terminal software "Bluetooth GPS" I have only checked whether the BT connection is stable and whether Gps data is transmitted. This works fine.

Thank you for your interest in this issue and hopefully the mistake can be found.

greetings from Vienna

BernhardAm 28.01.2019 um 12:06 schrieb Locus Map <locus.map@asamm.com>:

Hi Bernhard,

tr to start everything over again (Locus + BT GPS unit) and make a log report (https://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log) and send it here. We'll analyse it, perhaps something will show wehere the problem is.

MIchal

Am 28.01.2019 15:22 schrieb Locus Map <locus.map@asamm.com>:

Good day Bernhard,

this seems to be a complicated problem, mainly because we are unable to simulate it on own devices.

I've prepared a special test Locus Map Free version for you: https://asamm.myqnapcloud.com/share.cgi?ssid=0QX2EoT .

If you still want to invest a time into this issue, please install it, run it, try your BT connection over the app, and when it starts to do troubles like your Pro version, close app by the back button. In Locus/logs directory then should be a special log file with some information that may help me here so attach it here. Thank you!

Hi Menion,

after installing the Trial version of LocusMap Free 3.36.0.1, the error effect with the BT-Interrupt is the same.

Attached are some logs files as desired.

Thank you for your effort and interest.

greetings from Vienna

Bernhard 29.01.2019 um 09:16 schrieb Locus Map <locus.map@asamm.com>:

Good day Bernhard,

thanks for the logs. These logs are generated by beta version of Locus Map I send you? Doesn't look like.

Anyway in private topic you wrote that your BT GPS send data only in 5-10 sec interval? Why this? Locus Map has defined timeout to 5 seconds so this will most probably be THE problem. I'll increase this timeout to 10 seconds to next version and we will see.

Good Day Menion,

I regret that I made this mistake with the log file in the beta version.

I wrote this with the 5 to 10 second interval of the incoming GPS data at the beginning of our correspondence.

If possible, I ask you to increase the TimeOut to 20 seconds to have some time reserve.

Your suggestion that the timeout without GPS data to enlarge, so that the BT connection persists, is certainly good.

That would be a good thing if that works.

greetings from Vienna

Bernhard

Am 01.02.2019 um 10:12 schrieb Locus Map <locus.map@asamm.com>:

Good day Bernhard,

did you found a moment to test BT GPS connection in latest 3.36.2 version? Let us know, thank you.

Good day Menion,

I have not received version 3.36.2 yet.

So far, I have only received version 3.36.0.1 on January 29, 2019 for testing, but it did not bring any positive change.

If you send me the latest version 3.36.2 please, I will test and report immediately.

Thank you for your trouble and greetings from Vienna.

Bernhard

Am 11.02.2019 um 09:08 schrieb Locus Map <locus.map@asamm.com>:

New versions are already published on Google Play, so please check and update them from this application. Thanks

Servus Menion,

Thanks for the timeout change to about 15 seconds. Now the BT connection remains stable.

I did not know that the change over Playstore is to do with an update.

Question: Which GPS data are needed for the map display (blue circle or arrow)?

I suspect GGA and RMC data.

If you could tell me that please.

greetings from Vienna

Bernhard

Am 11.02.2019 um 13:20 schrieb Locus Map <locus.map@asamm.com>:

Perfect, I'm really glad that you wrote me core information (refresh time of your BT GPS), so we were able to solve it quite easily!

And yes, GGA and RMC are core sentences needed for proper work of external module.

Menion

Servus Menion,

I was able to test the new LocusPro version with my GPS and Bluetooth-devices today ... and it's going great.

Thank you again for your help and cooperation.

Bernhard from Vienna

Am 11.02.2019 um 16:38 schrieb Locus Map <locus.map@asamm.com>:

Servus Menion,

Thanks again for your help so far with my Bluetooth problem of TimeOut time and the RMC and GGA protocols ... works perfectly.

I have another question and request:

Can you please connect the GPS input data interface of the Android smartphone with the map cursor (red cross)?

Then you would have a map view in which the own location (red cross) AND the incoming via the Bluetooth interface location information of an external GPS receiver with course line and distance and heading to the distant target object (blue circle). See screenshot.

This addition would be very practical and would greatly increase the clarity and could also be beneficial for other users of LOCUS Pro.

Thank you again for your help and cooperation.

Bernhard from Vienna

Am 18.02.2019 um 23:54 schrieb Bernhard Pasteka <bernhard.pasteka@drei.at>:

Servus Menion,

I was able to test the new LocusPro version with my GPS and Bluetooth-devices today ... and it's going great.

Thank you again for your help and cooperation.

Bernhard from Vienna

Am 11.02.2019 um 16:38 schrieb Locus Map <locus.map@asamm.com>:

Good day Bernhard,

glad timeout solution helped and it works as expected now.

About your request: may you please describe it more in detail? The red cross is the current map screen center, not your current location.

Menion

Good day Menion,

thanks for the prompt response.

Yes, I know that the red cross represents the map center.

But I thought that with this red cross you do not represent the middle of the map, but the own location of the built-in GPS receiver.

This shows at a glance the remote location (blue circle) of the external Bluetooth GPS and the own location (red cross) in the map view with heading and distance.

That means: I then see my own position (Android phone) as a red cross AND the position of the external Bluetooth GPS as a blue circle.

I hope I could describe that understandably.

If you speak German, we can also write in German.

Bernhard from Vienna

Am 15.05.2019 um 15:01 schrieb Locus Map <locus.map@asamm.com>:

Hello,

understand. Anyway, it does not work this way.

The red cross is always only! map screen center, nothing more.

The blue circle is always active GPS location source. Not matter if the active source is internal GPS or external BT GPS, the visible result (blue circle) is always the same.

See both location sources at once is currently not possible and also not planned. Thanks for understanding.