PacePro strategies not suitable for slower runners

I have just tried to set up a PacePro strategy for the recent CCC 2019 course(just a hypothetical). I have noticed that compared to the official cutoff time it only allows "crazy fast" paces to be inserted. The official cut off for CCC is >26 hours, and puting this course into PacePro it alows only like 15h with an avarege pace of 8,12 min/km. Now< i have no doubt that there are those who can manage this tempo up and down for 100 K, however I think it should be more flexible. Also I am not sure if it realy takes into consideration the differences of up and down- it seems pretty even for the whole 100 K? Any thoughts as to what am I doing wrong? Apart for being to slow....

  • PacePro strategies created on the fenix 6 watch  do not have desired uphill effort and negative/pozitive split preferences.

  • Yeah, I did notice that. Seems like it reverts back to the old "Virtual Partner" functionality from previous Fenix models.

  • Hello everyone,

    I tested the PacePRO function several times with my Fenix 6X, over workout distances of 15, 20 and 25kms and 450-500m for D+ max.
    My gpx tracks are always defined with Basecamp from OpenMTB maps, whose DEM data are in my opinion among the most reliable (see https://openmtbmap.org/ ).
    So, one can usually define with good confidence workouts based on PacePRO.
    After at least 5 tests on these distances, I am rather very satisfied because these workouts are for "easy trails" with little elevation gain.
    Unfortunately, I found also that it is not possible to use PacePRO for more difficult trails with higher elevations.
    As an example, (see www.cjoint.com/.../JBtpgVwECfl ) the minimum time (or the maximum "Goal Pace") that can be apply to create a PacePRO program is about 24 hours for the UTMB (Mont-Blanc) (more than 160 kms, more than 10000m D+). Obviously the issue is the same for CCC !!
    You must be called Pau Capell to be able to use it ;-(. And even the first women (Courtney Dauwalter from USA) exceeds the maximum time possible to use PacePRO on UTMB (see example above) ;-(.The major problem SEEMS above all that the PacePRO function is almost unusable on all types of Trail in mountain areas or with elevation differences requiring setting "Goal Pace" slower, which can be the case for a VERY great majority of us.
    I saw that it could be possible to create a pacePRO program directly from the watch. I tried and I saw that this is possible. But what I want is to adjust also the "pacing strategy", the "uphill effort" and before all the splits based on "Elevation changes".

    I think that is not possible!! Any new ideas!!

    Thanks in advance

    Regards,
    Gerard C.
    France

  • Meanwhile you can use AppBuilder and make a data field with the following formula:

    setv(1,"pace_1(km/h)"); setv(2,"pace_2(km/h)");…; setv(n,"pace_n(km/h)");getv(findltindex(distance,"distance_1","distance_2",...,"distance_n")+1)

  • Hello everyone,

    Is there anything new about a possible improvement made by the Garmin teams, to generate "PacePro" strategies via garmin.connect.com that could be used by the vast majority of riders, not just the great champions?

    At least (in my opinion):

    - Goal pace 17-18 mn/km (about 27-29 mn/miles) in lieu of 8:42 mn/km (14 mn/miles);
    - Ability to adjust Elevation Changes, the pacing strategy, and the Uphill effort. For this last parameter, it could be welcome to increase a bit the range of variation (min and max values);
    - In all case ability to generate the PacePro strategy, with navigation (**).

    (**)  It seems that when you generate a "PacePro Strategy", directly from the watch, you don’t have the ability to have simultaneously "PacePro" and navigation on the map - Am I right?

    Thanks in advance

    Regards,
    Gerard C

  • Hello all,
    I'm trying to edit a Pacepro plan for my next trail race, which has a couple of very steep climbs (30 to 35% grade average) which I do not think will ascend faster than 25 or even 30 min/km (already 30 km behind us when the first one comes). I found out you can "cheat" and save pacepro splits up to 19:59 min/km (even if the system clearly doesn't want you to). Have yet to test if it works on the watch...
    Has anyone tried to open and edit .fit files created on the watch to see it the Pacepro plan could be edited manually, and saved back to the watch ?

  • I had a look at the PacePro fit files, on first sight they look simple enough, but I can't write them with the FitSDK because they contain undocumented fields. You could try to ask this on the FIT Developer forum. 

    The AppBuilder mentioned by cargIp in this thread may work for you.

    I tried PacePro while preparing for an upcoming race on hilly terrain. It is quite good. But for that race I'll use the old-school style pace table written on my arm. I think the PacePro screen will be too high in 'cognitive workload' during an event like that. 

  • but I can't write them with the FitSDK because they contain undocumented fields.

    Try to use the -u option, i.e.

    java -jar FitCSVTool.jar -u -c myfit.csv myfit.fit

  • Thanks!!! I have yet to try it, but that's awesome! I never knew fitcsv could do that.

  • Sorry I'm not a developer and my skills in this area are highly limited... Do you mean with fitcsv you could edit pacepro as text files, and re-convert them to fit after changing splits pace ? That would be perfect since long races are not something you do quite often... I'll try to have a look into that ! Thanks for the advice :)