07-04-2018 00:16
07-04-2018 00:16
I use my Ionic for running purposes and it works quite well.
Especially I love the ability to be able to listen to music without the need for my mobile phone.
But I do have questions on the pace which is shown:
1) After each kilometer I do get informed on the pace of the last kilometer. But the stats are not shown after e.g. 3.00km but 3.03km instead. Is this supposed to be a feature or the calculation is wrong?
2) If a run through a (even very short) tunnel the GPS signal gets lost and immediatelly the current pace gets destroyed. Wouldn't it be reasonable to somehow calculate the pace differently when GPS signal gets lost for some seconds?
3) When I climb up or down a very (!) short "hill" this also corrupts the pace - is this a known issue?
07-04-2018 10:50
07-04-2018 10:50
Trumml,
I use a Charge HR on one wrist and a Garmin 920XT on the other. The Garmin 920XT is a serious runner's watch. What you are probably seeing on the Ionic is "Lap speed" at all times instead of "average lap speed". "Lap speed" changes instantly as you slow or speed down, so it is more difficult to pace yourself versus "average lap speed". I understand the Ionic does not have "average and this
is why I have not purchased an Ionic yet, but the issues you mention are somewhat common to GPS phones, so I will share what my experience and knowledge is.
By the time you see the distance and you stop the watch, you have probably lost a second or so and the watch is still recording until you stop the watch. The difference of .03 is trivial, but some watches, like my Garmin, automatically start a new lap at each mile or kilometer so that at least each lap is recorded. it sounds like your Ionic is just recording the run all as one lap. Maybe there is a setting to make it record a lap every km or mile. If there is a "lap button" on the watch, you can also start a new lap manually with that. Sometimes if you are running four 800 meter sprints followed by 2 minute walks in between, the lap button will start and stop a lap with each sprint and walk. Of course if you are running and don't want to be looking at the watch all of the time for completion of a km or mile, it would be helpful if the watch beeps or vibrates at each km or mile so that if it does not start a new lap, you could do it manually.
If the watch is recording instant speed, it will be interrupted as you slow or accelerate going up or down a hill. It should not corrupt the pace, but might delay the computation of an accurate reading. I have noticed on my GPS watch that sometimes I think I have completed a lap at a certain speed and when looking at the downloaded data afterwards, it is slightly different than what I saw on watch during the run. I think this is normal.
I am not sure why the GPS would destroy your run pace in a tunnel or area with no GPS. Is this with or without your phone being with you? Sometimes the phone's GPS is more accurate than the watch and maybe that might help. I usually do not take my phone with me and everything gets downloaded to the phone and ultimately to my computer just fine, but if the phone is with me, it is coordinated more often and might help preserve your run data.
I joined this forum in hopes of finding out when the Ionic has more features that serious runners need. Once I started training recently for a marathon, I had to step up from just using a Charge HR plus a cell phone running app and another watch that only had a simple elapsed time on it.
07-04-2018 20:58
07-04-2018 20:58
Thank you for your quick reply.
The ionic does have pace per kilometer as well as the pace average.
The issues (from my point of view) is that the pace average is the average of the overall run - which is working well but not what I was searching for.
I was searching for the current pace but somehow straigthened over the last 60 meters (I am not sure how to translate that to English). This way loosing GPS signal for a few seconds would not be a problem.
I run with my Ionic only - no phone (that's the reason I bought the Ionic to listen to music without my phone). When results are transferred to my phone I do see each executed lap exactly as 1 kilometer. What I was asking for why on the Ionic itself I see some laps (while running and while getting informed about lap speed) after e.g. 1.03 kilometer (instead of 1.00 km).
So I would say basically Ionic does have nice and working running features. It is about details...