Hi sir5
Is it possible to update the custom data field to support for Edge 1050 please? I’m unable to install it on the 1050 at the moment. Thanks a lot!
1 Like
I second this request. I tried to contact the Dev via Connect IQ but got no answer so far. I would love to be able to continue using the datafield with my new Edge 1050 and I am also willing to make a donation to support the update. @sir5
The ‘Target Power’ data field is now updated for the 1050. It has been working on mine for the past couple of months.
I think you refer to the “Target Power” datafield, while we refer to the “Target Power Range” datafield 
Sorry, didn’t read above and assumed. Updated my post
Dear all,
Thank you for reaching out. Had a difficult time in the past months, so I was not very active online.
Now, about the CIQ-app TargetPowerRange.
A bit background:
-I am not a programmer, have never been. I have taught myself to “program” when I did not succeed in finishing text-adventures in 1980. I just like to explore things I do not know about. When Garmin ended the undocumented feature of including the TargetPower in a field that was meant for a trainer, I decided to “program” a CIQ field (TargetPower). It took me 2 months to understand the basic of how to install all the needed stuff and how to compile. The “program” itself was written in 20 minutes.
-End of summer of 2022 I had some spare time, it was a rainy weekend and someone was complaining about the standard workout page of Garmin (that I myself do not use). I played around with the graphical possibilities of Garmin. So I created TargetPowerRange. It was a nightmare to make it neat for the two sizes: 800 and 1000 series. Not the graphics, but the text. With a bit of math it is easy to resize the graphics, but for the text I was dependent on Garmin. It turns out a “small” or “large” font differs relatively to the size of the device. A lot of trial and error. Even more difficult if you have to rely on the simulator and not having such a device yourself.
-For the 1050 I would need a complete weekend of time to trial and error the lay-out. But private life is still offering challenges, work life is demanding, including a lot of travelling and finally I want to keep on training.
If someone with (a bit of) programming skills and some spare time is interested, then he/she can use my code and adjust it for the 1050.
I am willing to adjust or make a separate field for the 1050, but I am just too time-constraint.
Perhaps I could upload to GitHub and someone could do the adjustments for me?
Or I could try CoPilot to do the adjustment for me..
2 Likes
Hello @sir5 and first of all thank you for taking the time to answer.
I understand perfectly what you mean. I am no expert in programming but I am rather tech savy so if you are willing to share the code as you suggested, I will try to mod it on my spare time.
All the best!
Hello @sir5 , as I said I would be interested in taking a look at the code if you are willing to share it to GitHub! Best regards!
Hi,
If you provide me with an email address I will send you the code (TR forum does not accept files with “mc” or “zip” suffixes.
Yesterday I have spent the entire evening in trying to get this compiled by the updated Garmin compiler. Unfortunately I did not succeed. Some code is depricated and I do not know how to adjust.
So I did not even reach the point on where I could start adjusting for the 1050!
The problem is the “override” of the intitial view (function getInitialView() in TarPowRangeApp.mc. I have been able to get around the compiling error, but the app does not work afterwards.
The main code is in TarPowRangeView.mc in the source directory.
Waiting for your email address in PM.
Good luck after that!
Sir5
Hello,
I sent you a PM with my email address.
I gladly take a look at the code and see if I can start over with a new project and transpose the code on the newer SDK.
Meanwhile (for everyone…), I spent the past week coding 2x new datafield that I am now using with the edge 1050 and that they fit its workout page:
The top datafield shows info about the next step
*LAPKY means a LAP key press is required to go to the next step. If that is not the case, the datafield displays “AUTO”. When a lap key press is required, the datafield also flashed from white to red in 1 sec intervals (of course, this is not visible from the picture).
*INVTL indicates the type of interval (BREAK, INTVL, CDOWN, …)
*Then time and average power of next intervals are displayed. If the next interval does not have a time (e.g. typical behaviour after rest intervals: press lap to advance) it will display “FREE”
The central datafield displays:
*MIN, TARGET and MAX power for the current step
*live 3s average power
*Then: depending on live 3s power, the whole datafield background gets:
(let’s assume for example targets MIN 100W, MAX 120W = TARGET 110W)
- GREEN, if power within target range (100 to 120W)
- RED, if power above target range (>120W)
- BLUE, if power is slightly below target, defined as 90-100% of min power (90 to 99W)
- White (as you see in the picture) if power is not available or well below target (<90W)
GREEN. If 3s power is above the max target, the whole datafield background gets RED. If 3s power is 10% below target, the whole datafield background
Below in the additional datafields I use the default LAP power (useful in long intervals), time to go, HR and cadence.
What do you think?