New Topic

Locus Map - help desk Topic Idea Locus Map (Android)

This object is in archive!

Category Locus Map (Android)

Tags profile, bike computer, trip computer, track recording, audio coach

Comments 22

Subscribers 31

Votes 30

Multiple profiles for bicycles / multiple sensors / multiple circumference

Ralf Schmidt shared this idea ago

Completed

Hello,

a nice feature is a second profile to record tracks with 2 bicycles. Both are with a different Cadence / Speedsensor. At the moment i can connected with only one device. When i change des Bike so i must kill the assozioation and make a new with the other device. The Garmin Egde 705 has 3 profile.

The second very nice feature is a automaticle Adjustment for the wheel size. My old Garmin Edge 705 make this after ca. 2.000 meters recording. The software recognice if the tire pressure ist lower or higher and adjustment the the wheelsize.

My english is not very well and i hope you understand what i mean.

Thanks for the great Software with all the features!

regards

Ralf

Merged Objects

Ulrich Kiermayr

Multiple (BT) Speed Sensors for different bikes

Hello,

I own several bikes. For all of them I have speed and cadence sensors and use Locus for navigation and tracking. Since all the bikes have different wheel sizes, it is necessary to change that value in Locus before using the bike.

It would be useful to support multiple Speed Sensors with different diameters of the wheel.

p.s.: for the cadence sensor it is sligtly different since there no diameter is required. Only the use/pairing of different sensors would be required.

Greetings , Ulrich

Bernhard Friess

Locus Map could only connect to ONE BT Speed&Cadence sensor

I'm using happily Locus Map to track all of my activities like biking, skating or hiking. For biking I use regularily 3 different bikes.

Now I have equiped all 3 bikes with combined BT speed&cadence sensors. It seems as if I could connect only one sensor to Locus. This means if I was cycling with the MTB and have connected the sensor mounted to the MTB and I change to the Tandem, I have to disconnect the sensor mounted to the MTB and then connect the sensor mounted to the Tandem.

It would be much more connvenient if I could connect all 3 sensors of all 3 bikes and just aktivate the sensor of the bike which I want to use.

Does this make sense? Is there a way to handle my situation more easily or could Locus Map be Updates accordingly?

Best regards

Bernhard

Hannes

Set certain sensors for certain profiles and automatic connection

Hello,

Locus Maps is great but there are always some improvements that could be made.

I have 3 bikes with different ANT+ sensors. It would be great to create a individual profile for each bike and determine the certain ANT+ sensors that automatically connect when I start a track.

Now when I start a track with a profile it searches for the general type of sensors I have in this profile (heart rate, speed, cadence) and I have to select the certain sensor manually to connect.

E.g. I have a speed bike (Cervelo) with certain sensors that I searched and connected in advance and gave them a certain name, like GarminHeartrate1, GarminSpeed1...

It would be great to create a profile called Cervelo and when I start a track it automatically connects to GarminHeartrate1, GarminSpeed1.... without the need to select them.

Hope someone finds this helpful, too. It is not only useful for bikes but hiking, walking, etc.

Drachen1000

Different wheel circumferences in sensor speed settings

I use locus with different bikes for example MTB and Road bike. For speed measurement

I use a ANT+ speed sensor. In the ANT+ sensor settings you can enter the wheel circumference. My problem is here I can enter only one value for the circumference, so I have to change these settings every time when I change the bike. It would be great when you can enter a second circumference value in the ANT+ settings and you can choose the different values.

Perhaps these settings can be even considered in the profiles (MTB / Road).

Robert

Support for multiple bikes

When selecting different profiles and then having a look to the bluetooth manager it should be possible to add different diameters of the wheel for different profiles. E.g. when selecting the profile road bike and then the profile mtb I have to change the diameter of the sensor every time I switch the bike

I like this idea 0

Replies (7)

gynta ●

>..i hope you understand what i mean

not really :)

You can create more profiles

see settings >track recording >add new profile

URL

Menion ●

I think I have got it.

ANT+/BT sensors for speed and cadence also has special parameter - "Circumference". And in case, you have two different bikes, where both has different sensor, you always have to manually change this parameter before usage with same device. Is it correct?

So Ralf needs (and probably not just him), so way to quickly define this parameter maybe attached to track record profile. So I can imagine like two track record profiles "Bike 1" and "Bike 2", where both will be almost same except this special parameter for speed/cadence sensor. Am I correct?

URL

Ulrich Kiermayr ●

Yes. That would be very useful.

URL

Ralf Schmidt ●

Hi Menion,

yes, absolutely.

If I can configure 2 or more devices and match it to the profile.

@gynta

Ok, I try it with an Example.

Cadence/Speedsensor from Bike1 has deviceID abcdef and this Bike has a wheelsize 2138 mm

Cadence/Speedsensor from Bike2 has deviceID uvwcyz and this Bike has a wheelsize 2012 mm.

At current I must delete the assoziation from Device1 and pair to Device2.

Regards

URL

Ralf Schmidt ●

For the automatically wheel size found I this text in the manual:

"In the Wheel Size field, select Auto to have the GSC10automatically detect your tire size using GPS data, or select Custom to enter your wheel size. For a table of sizes and circumferences, see page 64"

Here is the link to the manual http://static.garmincdn.com/pumac//2297_OwnersManual.pdf Page 15

URL

Bernhard Friess ●

Unfortunately my new topic from yesterday was merged with this one. I find this not really smart as a huge portion of this topic is around multiple profiles which I think could be handled with Locus map already.

I brought up an issue where I can't see a feasible solution so far: usage of a phone with Locus Map in combination with various bikes. I use regularily 3 different bikes and I have all three of them equiped with BT SPD&CAD sensors.

The issue is that Locus Map can apparently only maintain a connection to a single SPD&CAD sensor. This means everytime when I use a different bike (with a different SPD&CAS sensormounted to it) than before I have to delete the connection of Locus Map to the previous SPD&CAD sensor and establish a new connection to the SPD&CAD mounted to the bike I want to use.

It would be much more comfortable if Locus Map could store connections to multiple SPD&CAD sensor and I could simply activate the respective sensor which is mounted to the bike I'm gonna use.

The second aspect is a sort of automatic calibration of the SPD sensor by comparing GPS and SPD sensor data: this would be a great enhancement as well but is of much lower priority for me.

Menion, what is your view about maintaining and storing connections to multiple BT SPD&CAD sensors?

URL

Menion ●

Good day Bernhard,

I've merged your topic here because it's point is same ... support or multiple sensors at once without need to remove it's connection in manager.

I agree that this feature is needed and when Bluetooth/ANT+ system was created it was not counted with such option. So such change currently means rewrite of both systems from scratch. Not a simple task and not planned on next months because of many other work. I'll anyway try to keep this in mind and give it little bit higher priority.

URL

Bernhard Friess ●

Hi Menion,

Many thanks for your fast reply!

Ok, when you write "I agree that this feature is needed and when Bluetooth/ANT+ system was created it was not counted with such option. So such change currently means rewrite of both systems from scratch." then I understand that this will cause a lot of effort whihc cannot happen quickly.

This is a bit sad but I understand now the situation. So I will have to handle it the way it currently is and be a bit patient until you take some time for a fundamental change in the ANT+ and BT sensor area. And you're right, the same requirement is of course valid for ANT+ SPD&CAD sensors as well!

URL

Hannes ●

@Menion

I started almost the same idea a couple of days ago and the thread was merged with this one, too.

I hope this idea will find its way into the app very soon because this is really a necessary feature and in my opinion much more important than support for another map, e.g. The idea is already 2 years old and this feature is the basic feature of every bike computer.

In my case I have a lot of friends who do not buy Locus Pro just because of this reason. They are using other Apps like Orux or IPBike+ which do support this feature.

So I hope this will be realized soon. When you bear that in mind please also bear in mind that each speed sensor must have the capability to save its own diameter of the bike as they differ from bike to bike, too.

Furthermore it would be nice if you simultaneously add support for power meters, too, when you are about to program this from scratch because this is a very important feature for a lot of bikers, too.

URL

Ulrich Kiermayr ●

Hi,

Since there is a new Bicycle in town: Any news on that topic?

Cheers

URL

Menion ●

Good day Ulrich,

unfortunately there are currently no plants to implement this feature during next months. It will require rewrite of whole BT/ANT+ system almost from scratch, which is planned, but not priority now, sorry.

URL

Hannes ●

Hello Menion,

I understand the amount of effort that need to be done. But can you be a little bit more precise when this will be approximately on the roadmap in the future? Still in 2018 or later?

For any real biker it is a no-go for using this app as a daily attendant with the bike, because it is a pain when you own more than one bike which is usual (e.g. I own 4 bikes that I use regularly). Not only for changing sensors but also for changing the wheel size in the sensor ;(

URL

Menion ●

Hello,

I really can't promise more precise dates. Who knows me know, that I do not have reallyy exact road plan. My priority on a Spring months are more related on geocaching ( because I did not work on it for a very long time and there are seriously missing some things ) and after that, cards are not placed yet. In 2018? I really would like to rewrite and merge BT + ANT+ managers into single working system and I believe, on 90% it will be done this year.

URL

Bear ●

Hi. I would vote for solving this problem asap because it would probably solve also my problem...

I have two bikes with different wheel sizes.

1st bike with BT speed/cadence sensor

2nd bike with BT speed sensor

Bug: No problem to set and save different wheel circumference for each sensor/bike. But after restart of Locus, the same value (the last saved one) is set for both sensors. Of course, it gives wrong speed values for one of the bikes.

URL

Theo D ●

Are there any news/updates on this regarding roadmap? I'd also like to have this feature for heart-rate sensors. I currrently own a bluetooth breast-chest and one for the upper arm. From time to time I use one or the other and it would be really nice if locus could establish to the one I'm currently wearing automatically.

URL

Roman ●

Dears,

It's a four years for this topic as I read this post now.

Is the solution implemented ?

URL

Menion ●

Hello Roman, sorry, not yet.

URL

Oliver Naumann ●

Hi Menion, as I have 2 bikes now with different Wheel Sizes, I would ALSO appreciate, if you could find a solution fo using different Circumfences for different Sensors / Bikes.

I keep forgetting to change the values and mess up my recordings :-(

thanks,

MoosHam

URL

Oliver Naumann ●

Wooha Menion, seems you have finally closed this topic with the new Sensor Manager in 4.4.0

Seems to work like advertised, thanks for adding this!

thanks,

MoosHam

URL

Menion ●

Uff finally :).

Everything works correctly for you? You may add multiple sensors, every with own parameters and every attached to different recording profile. You may currently even add the same sensor twice. Not sure if this is useful at all ...

Thanks for notification in this topic ... I'm glad to finally mark it as "Implemented" ... after 6 years. Not bad :).

Menion

URL

Ulrich Kiermayr ●

Great news @Menion 👍👏

However, I had to report a Bug in the new system 😉

Cheers & Thanks

URL

Oliver Naumann ●

unfortunately I also ran into this issue, took me a while to figure out what was wrong... I also commented under the Bug Report. I am sure, Menion will find a fix quickly, as usual!

URL