April 24, 2017 | Version 3.3
Thank you very much for the great Peter (Race) Pacer. Yesterday i run my second Marathon in 3:24:02 and your Data Field was amazing. THANKS THANKS THANKS
April 22, 2017 | Version 3.3
Exactly what I was searching for. Took e a long time to find this one.
Happy with the functionality and the optin to record the "time ahead" withthe fenix 5x!
Donaition done! Worth every cent!
April 19, 2017 | Version 3.3
Easy setup, perfect functionality. Highly recommended.
April 8, 2017 | Version 3.2
I wish it was easier to add custom distance. It takes an added calculation to convert mileage into meters. I can't add in a decimal into the field so my distance isn't accurate. I wish I could put in predicted finish time over pace, again this requires added calculation on my part.
April 10, 2017, peterdedecker
Hi Don, thank you for your feedback. Regarding custom distance to be entered in meters: the Peter's (Race) Pacer field is really pushing the maximum out of the available memory, when I would allow the custom distance to be entered in something else than meters then internally the field would need extra lines of code to convert this figure into meters and extra code (unfortunately) take extra memory (which is simply not available). Regarding the meters-value to be non decimal: I concur I would prefer a decimal value in here and in fact in version 1.2.5 this was a decimal value, but inconsistent behaviour between Garmin Connect Mobile and Garmin Express in transfers of float values by the API made me choose to opt for stability by choosing an integer value, when in the future float transfers become consistent and reliable I'll change it back. Regarding the ability to put in predicted finish time over pace: this is already possible for high memory devices (you can choose between the options Target Pace/Target Speed/Target Finish Time), for the older low memory devices (the connect IQ 1 compatible devices) you only have the option to specify the target pace as there's simply no memory to allow for the choice (eg on Fenix 3 device the data field is having a peak memory usage of 15.7k out of the available 16k). If you have an older device and you do want this choice then you might want to check out the app ( https://apps.garmin.com/en-US/apps/ea97af1f-1e5d-4541-820c-9bd994080d4c ) where I have more memory to play with and can enable all high memory logic also for low memory devices. Amongst others you will then have the choice to set a target finish time. Cheers, Peter.
March 12, 2017 | Version 3.1.1
Annoying "like it-donate" on display.
March 13, 2017, peterdedecker
I think I have been very generous by giving away all functionality in the program for free for everyone to enjoy. If you dislike the small donation encouragment message, that's easy to fix, you know...
Hint: read the encouragment message. ;)
February 5, 2017 | Version 1.3.3
Using version 1.3.3 on a Forerunner 235, it crashed at mile 12, displaying a blank screen with just "IQ!" on it, leaving me flying blind a critical time. Later at home I looked in the "apps/logs/ciq_log.txt" file and found there was out of memory error. I was able to salvage the run by switching to a second screen which still had accurate data fields.
It's a very useful and well-designed data field when it's not crashing, but if you are going to use version 1.3.3 on a Forerunner 235, uninstall all your other CIQ add-ons for best results, make sure to keep useful stats on your second screen as a backup.
If I could rely on this data field not to crash during a race, I would give it 5 stars.
There's less likely to be a problem on the Forerunner 735XT, which has more memory.
February 6, 2017, peterdedecker
Hi Mark, congrats on the personal best you achieved, way to go!
Please use the forum thread for future support topics. The out of memory error you see in the logfile is not from my data field, but from the "superb" watch face you're using. The "invalid value" error that made the data field crash (sorry about that) is coming from the connect iq framework itself and is unfortunately not something which is under my control, for details check the forum topîc I referred to. It could be that using another connect iq field (you're using it in combination with Runner Window) data field on another data screen enhances the chance of this error to occur. For the best stability don't use another connect iq data field in combination with this field. It's a wise thing to have a second screen as a backup, personally I use as a second screen native distance/speed/time/heart rate combo.
It's stable for me this way in this setup: past saturday I did a 6 hour training run with the field and it performed beautifully.
February 2, 2017 | Version 1.3.3
Great lay out. Very good support.Its perfect for the forerunner 235 for using as a pacer.
January 30, 2017 | Version 1.3
Great layout, and I love how you can adjust the laps during a race. Well done.
January 30, 2017, peterdedecker
Thanks! Enjoy the field! Cheers, Peter