If Locus will support HR monitors (bluetooth / ant+) it would be nice to make some add-on for create workouts.Endomondo and other apps can only record and publish your result but it's not possible prepare some, for example basic interval training. Garmind Edge/ Forunner series could do that but when I heave Locus and Xperia Activ and Ant+ sensors I would like leave my Garmin on the shlef and use phone:)
Posted 3 years ago
Menion, Official Rep
didn't had this idea at morning around 9 votes? Interesting ...
Seems, I'll have to do something with it soon :)
Seems, I'll have to do something with it soon :)
Just HR? What about speed/cadence (and eventually power sensor)? Locus would be the first and only android cartographic navigator with full ant+ support!
For the HR a chart would be great, but not really necessary, the important feature is recording HR (and cadence) into gpx or tcx.
For the HR a chart would be great, but not really necessary, the important feature is recording HR (and cadence) into gpx or tcx.
Menion, Official Rep
hmm I need small explanations please
Bluetooth HR, like this for example http://www.zephyranywherestore.com/hx..., record heard cadence and speed, right?
What is then difference to ANT+?
It's only way how device communicated with your phone right? But information are quite similar (or same). Am I understanding correctly?
So my idea is just to purchase for example above device and add support for this. When it will work, I should borrow from someone phone + monitor with ANT+ support, and just add possibility to read also from this sensor, correct?
Bluetooth HR, like this for example http://www.zephyranywherestore.com/hx..., record heard cadence and speed, right?
What is then difference to ANT+?
It's only way how device communicated with your phone right? But information are quite similar (or same). Am I understanding correctly?
So my idea is just to purchase for example above device and add support for this. When it will work, I should borrow from someone phone + monitor with ANT+ support, and just add possibility to read also from this sensor, correct?
Well. To be honest with you. BT heart rate strap is a dinosaur tech today. And I mean standard 2.0 BT. It's high energy consumption prevents from using it normally and signal is unstable to say the least. It's just not reliable.
What I would suggest You to focus on is BT 4.0 (aka BT SMART, BLE, BT SMART READY) it's a BT but with low energy consumption. It will be the competition for the ant+ in the nearest future. These two data formats stream mainly Heart rate and heart rate variability. I would not worry about the speed and cadence in zephyr because they are calculated from accelerometer. You can do it on any android device.
So to conclude.
ANT+ needs ant+ chip to communicate with android.
BT heart rate strap (old tech) needs simple bt chip to communicate.
BLE needs bt 4.0. That will be the best bet for you to focus on. (See iphone 4s and 5, they have and use it succesfully)
I mean there is a lot of info on the subject. If you want I can get you all the info by email. Too much spamming here i guess :)
What I would suggest You to focus on is BT 4.0 (aka BT SMART, BLE, BT SMART READY) it's a BT but with low energy consumption. It will be the competition for the ant+ in the nearest future. These two data formats stream mainly Heart rate and heart rate variability. I would not worry about the speed and cadence in zephyr because they are calculated from accelerometer. You can do it on any android device.
So to conclude.
ANT+ needs ant+ chip to communicate with android.
BT heart rate strap (old tech) needs simple bt chip to communicate.
BLE needs bt 4.0. That will be the best bet for you to focus on. (See iphone 4s and 5, they have and use it succesfully)
I mean there is a lot of info on the subject. If you want I can get you all the info by email. Too much spamming here i guess :)
Hi, the belt transmit only the HR, (the speed and DISTANCE advertised, are provided by the phone'gps, so some kind of false advertising), but no cadence nor speed.
BT belts, like that one from zephyr and the one from polar (that works well, but only wit BT4 devices) transmits only HR, they are popular among runners.
On the other hand there are ANT+ devices, popular among bikers (garmin standard). ANT+ is a different wireless protocol, only few xperia phone have native ant+ support (xperia active is the more popular) but there are ant+ dongle available.
Among bikers are widespread HR ant+ belts, and also speed/cadence sensors (mainly from garmin), a s/c sensor is mounted on the bike, near the rear wheel and transmit data from the wheel (speed) and from the crank (cadence).
There are also power sensors (very expensive, >1000€) also mounted on the bike, as now I think only ipbike through ipsensorman support these on android, but it's not a cartographic app, only gps recording.
BT belts, like that one from zephyr and the one from polar (that works well, but only wit BT4 devices) transmits only HR, they are popular among runners.
On the other hand there are ANT+ devices, popular among bikers (garmin standard). ANT+ is a different wireless protocol, only few xperia phone have native ant+ support (xperia active is the more popular) but there are ant+ dongle available.
Among bikers are widespread HR ant+ belts, and also speed/cadence sensors (mainly from garmin), a s/c sensor is mounted on the bike, near the rear wheel and transmit data from the wheel (speed) and from the crank (cadence).
There are also power sensors (very expensive, >1000€) also mounted on the bike, as now I think only ipbike through ipsensorman support these on android, but it's not a cartographic app, only gps recording.
Menion, Official Rep
thank you both for very very valuable information. Currently I need to finish some other smaller tasks, so I expect that since next year, I'll start work on it.
So expect that I'll need some more info during a progress and also some testing ;). So thanks once more for now and I'll let you know what things start to move ...
So expect that I'll need some more info during a progress and also some testing ;). So thanks once more for now and I'll let you know what things start to move ...
Menion, Official Rep
ps. My phone is xperia arc s with android 4.0
sorry I have 2 phones, I tried with the new one (and it didn't work), but by mistake I wrote the name of the old one. now I edited the post
I dug out my old xperia x8 with android 2.3 and ant+ of this beta works.
Is ant+ working wirh other apps on you arc s? if now i will send you neccasry files so you can put them to your rom. Root needed
Yes, usually it works, but I just tried and no ant+ app was working, fixed with a reboot, and this beta works too.
Menion, Official Rep
yes, a screen with all the values is important, is also really important a configuration screen where one can chose which sensor enable and directly imput the sensor ID (if ant+ is first started near other cyclists it could pick up their sensors)
Yes, exporting to gpx is really important, I don't know if there is a gpx extension which supports all the main sensors (hr, speed, cadence, power), but for sure exists a tcx extension for all that.
About speed sensor: it's definitely more precise than gps speed, but as far as I know every analysis program ignores the speed field in the gpx and calculate it's own value from the gps points, but for the tcx there's a distance field where you can put the current distance (in meters) calculated with the speedsensor (because the speed sensor is primarily a distance sensor, you just need to record the n° of wheel rotations to know the exact distance for every gps point), this field is then used in sporttracks.
For tcx, the schema is here: http://developer.garmin.com/schemas/t...
http://www8.garmin.com/xmlschemas/Tra...
Here's a open source tcx writer:
http://code.google.com/p/mytracks/sou...
Here's a sample of the trackpoint:
https://docs.google.com/document/d/19...
Yes, exporting to gpx is really important, I don't know if there is a gpx extension which supports all the main sensors (hr, speed, cadence, power), but for sure exists a tcx extension for all that.
About speed sensor: it's definitely more precise than gps speed, but as far as I know every analysis program ignores the speed field in the gpx and calculate it's own value from the gps points, but for the tcx there's a distance field where you can put the current distance (in meters) calculated with the speedsensor (because the speed sensor is primarily a distance sensor, you just need to record the n° of wheel rotations to know the exact distance for every gps point), this field is then used in sporttracks.
For tcx, the schema is here: http://developer.garmin.com/schemas/t...
http://www8.garmin.com/xmlschemas/Tra...
Here's a open source tcx writer:
http://code.google.com/p/mytracks/sou...
Here's a sample of the trackpoint:
https://docs.google.com/document/d/19...
Theoretically in Garmin when GPS reception is poor (or speed is low) speed is calculated from speed sensor.
BTW: what's about calibration /auto (supported by GPS) of wheel size?
BTW: what's about calibration /auto (supported by GPS) of wheel size?
I read something about that, but then I believe the speed value isn't written into the tcx directly, but as a distance measurement.
Of course if the speed sensor is present, I think locus should show the speed calculated from the sensor and not from the gps, but for the logging I believe there's no speed support neither in the gpx nor in the tcx files.
As for the auto calibration of the wheel size I don't care, how many meters on a straight line are necessary to have a precise measure? Isn't simpler to measure the wheel size with a ruler?
Of course if the speed sensor is present, I think locus should show the speed calculated from the sensor and not from the gps, but for the logging I believe there's no speed support neither in the gpx nor in the tcx files.
As for the auto calibration of the wheel size I don't care, how many meters on a straight line are necessary to have a precise measure? Isn't simpler to measure the wheel size with a ruler?
prolegs