Data Field: Race Pacer

Also, please make sure your watch firmware version is up to date...

My watch firmware is 3.10 which is already the latest version for Traditonal Chinese users. I believe yours is 3.30?

Does it still help if I do the debug? If yes, then I will do it tomorrow morning as it's getting late over here.

Thank you for your help. Hope I can use Race Pacer ASAP.^_^

My watch firmware is 3.10 which is already the latest version for Traditonal Chinese users. I believe yours is 3.30?

Does it still help if I do the debug? If yes, then I will do it tomorrow morning as it's getting late over here.

Thank you for your help. Hope I can use Race Pacer ASAP.^_^

AnnaTseng, don't worry about "debug"... I've uploaded a new version to the IQ App Store that hopefully fixes your issue...
Seems some Garmin devices don't set DataField settings correctly, so I've changed the way I detect the field position...

Thanks for finding this issue

AnnaTseng, don't worry about "debug"... I've uploaded a new version to the IQ App Store that hopefully fixes your issue...
Seems some Garmin devices don't set DataField settings correctly, so I've changed the way I detect the field position...

Thanks for finding this issue

Hi! IT WORKS!!! :D:DTHANK YOU for solving the problem. :) Will try it for my next run. :o

Info

Hi
I have a question, this morning i run 1 hour for 12,6 km; in the settings I have insert 60 minutes for 12 km (metric system), that means a pace of 5:00 min/km.

So i expect to see the pacer screen grenn, but it was always red; maybe that I am wrongly setup the app? The choice between km or miles is automatic (due to watch configuration) or must be specified? If yes in wich mode?

Watch is a VivoActive

Thank yo very much

Hi
I have a question, this morning i run 1 hour for 12,6 km; in the settings I have insert 60 minutes for 12 km (metric system), that means a pace of 5:00 min/km.

So i expect to see the pacer screen grenn, but it was always red; maybe that I am wrongly setup the app? The choice between km or miles is automatic (due to watch configuration) or must be specified? If yes in wich mode?

Watch is a VivoActive

Thank yo very much

Hi, thanks for the feedback, yes it does detect your system settings unit of distance measurement. So as you say you did 12.6km in 60min, so should have been green by finish, so doesn't sound right. I tend to use miles, i'll do a test with km's.
Can you remember what sort of -ve to pacer times it was showing? Eg.vastly wrong?
I tend to find GPS elevation can spike around a bit next to buildings or under heavy trees, but that only effects pacing by +-10sec or so and averages out over time.
Also, can you remember if the settings summary said the right values before the start? Should have been something like
A: 123 D:0
12km in 60
P:5:00->5:00
If it didn't possibly had it failed to sync values?

I'll do a full test in the morning, but if you have any useful info on the figures you saw please? That would be most useful.
Thanks

Hi
I have a question, this morning i run 1 hour for 12,6 km; in the settings I have insert 60 minutes for 12 km (metric system), that means a pace of 5:00 min/km.

So i expect to see the pacer screen grenn, but it was always red; maybe that I am wrongly setup the app? The choice between km or miles is automatic (due to watch configuration) or must be specified? If yes in wich mode?

Watch is a VivoActive

Thank yo very much

Hi again, I did a test using "metric" units and pacing worked fine. I do have a suspicion what it might have been though, bear with me this isn't easy to explain! When your watch initially get a GPS position, the "elevation" can be off a bit until it gets a good lock, especially if you're starting near a big building or under trees. I typically find it takes about a minute to get a good elevation, hence why in the settings summary I display the A: <current elevation>, so you can check it looks good before starting...
So what effect this has is as follows, the watch will correct after about a minute of your run, however say it incorrectly gave you a start elevation 100m higher than it should be but then corrects after a 200m of your run start. Race Pacer thinks you've just run down a "really steep" hill, hence your GAP will be quite a bit faster than you 5min/km, say 4min/km, the theory being to hit your target when you need to run back up that 100m hill it thought you just ran down, you will run slower than 5min/km...etc... However, you didn't really run down a really steep hill(!) you were in fact running on flat ground at your 5min/km, hence it will actually show you a 30 seconds or more... behind the "pacer" that ran very fast down that imaginary really steep hill!! You would have actually found as you ran towards the end of the run the "pacer" difference would have trended towards you as the racepacer was expecting the 100m steep climb over a shorter and shorter distance...

So the answer to this is either, if you have a fr920xt use Baraometric altitude! otherwise fr230/5/VA users use the Summary A: <current elevation> display before hitting start and make sure it looks good before going... Alternatively use the "Start Elevation" setting I added for this very reason.

I know that's a bit complex, but hope it helps a bit!

Hi

Maybe that I have find the error, was a my mystake.
i setup 1:00:00 and not 60 minutes, so the pacer was 0:05 instead of 5:00

Sorry for the misundestanding and thanks for your help

Hi, ah yes the time is in total minutes. Due to memory constraints i have to keep code simple, rather than extra code to parse time formats unfortunately...
Good to see you're working now

Feedback?

Good to see from feedback someone has tried this in a marathon. Feedback on some "long" races would be really useful please...? I can only run 3 miles due to re-hab for a "sprained" ankle (sob:-( ), so haven't test/tried a long run yet.
- Hilly/flat?
- How was Estimate?
- Did you use -ve/+ve "split" feature?
- How did "gradient" adjusted hill pacing seem? (GPS or barometric altitude used?) I find GPS elevation noisy +/-30feet typically (or equiv. to +/- 10seconds on pacer)

Any feedback much appreciated.
Cheers!

Thanks for the DF, just installed it and tried it at home. Nice idea to offer a "split" feature if you're going to be using a specfic strategy or want to account manually for hills. The next step would be to offer more than two splits but of course that's going to become complex to set up ;-)

I don't intend to use the altitude as I don't think it would be very reliable on my sensorless FR235, should I zero out the gradient penalty/bonus values so there is no impact or would putting a 0 altitude difference be enough?