I've been experiencing multiple issues with the PacePro feature. Description of test conditions and issues documented below:
- Native Run activity.
- Created a PacePro Plan from a course in GC
- Started Run executing the PacePro plan and navigating the course.
- Viewed the PacePro data screen during the run.
- PacePro splits were set to 1 mile.
- 1 second Data Recording period.
- Connected Sensors:
- Tempe
- RD Pod
- Bose Sports earbuds (Amazon Music)
- Also used a fenix 7XSS executing the same PacePro Plan
- Issue 1
- Ahead/Behind audio announcement (at each PacePro split) is the opposite of actual. For example, PacePro Ahead/Behind Data Field displayed correctly “Overall Ahead/0:35”, but audio announcement says “Behind 35 seconds”. On the run In the test scenario, I was actually 35 seconds ahead, not behind the target pace. Another quirk with this issue is that the Instinct 2 that I was using with the same PacePro plan, displayed the Overall Ahead value as a negative number, while the 945 LTE displayed a positive number which also differs from the owner's manual graphic:
- Issue 2
- The distance of the Plan was 6.1 miles. Therefore, there were 6 complete mile splits and a partial remainder of a 10th of a mile. The Change-in-Pace announcement for the last 0.1 miles stated, “New Pace 58 seconds”. This is incorrect. The pace for the last split was programmed to 8:44min/mi, not 58secs/mi. The number of the announcement is the split time to finish the last 10th mile at the 8:44 pace. Obviously, for a full mile both those numbers are the same, but not for a partial mile that frequently happens on the last split of a plan.
- Issue 3
- At each New Pace announcement (each mile), the watch did not vibrate. I could hear the announcement in the earbuds and see the information on the watch face, but no buzz. The watch did vibrate as expected on lap splits and TBT alerts.