Adding a "Watchdog Timer" feature to the AC diversion load program code to help fill in missing power data that seem to occur from time to time. The basic idea is to detect when the reported power data is older than the designed reporting interval. This is done by taking advantage of the Program Logic Event Generator (PLEG) time stamp information in the device property that records the power data. The logic is that if either of the 2 diversion load interval times (Clamp1Check or Clamp2Check) have run and expired, then check the "age" of the power data and if it's older than the reporting interval, request new data from the power meter. More to come... Subscribe for more content like this Comment, like, share & click the bell icon And as always, thanks for watching Intro/Outro: Louisiana Fairytale by Austin Rogers https://web.archive.org/web/20170402222425/http://drfiddle.com/show_tune.php?id=94 ... https://www.youtube.com/watch?v=aBfVvFDMiyk

Documenting my bike computer training pages setup, how/why to lock the screen, and how to make changes to those pages. The Edge 800 (and similar bike computers) from Garmin have the ability to gather and display a myriad of data. I have 5 user defied screens set up plus a number of the other screens, some of which can have additional data displayed as well. I use the various user defined screens for various types of riding. The first screen is used on most riding I do on the roads and bike paths. For example, winds are a factor in this type of riding, so I have my heading displayed so I can gauge wind speed and direction. The 2nd screen is set up for climbing, wind is not a factor here, but grade, ascent rate and elevation are important. I also add temperature here as if I'm climbing a steep grade at a slow speed, I find it's easy to overheat in higher temperatures. With my 20-42 gearing, I may find myself riding under 3 MPH (5 KMH) and in the deep mountain valleys, there can be little wind to keep me cool. The 3rd screen is set up for road climbing. I can start the lap counter at the base of a climb and with a local climb database, I know the length of the climb as well as the final elevation, so can track my progress with this screen. The 4th and 5th screens are my descending screens when I ride in the open space preserves and county parks with speed limits. It's over $400 fine if you are caught on radar exceeding the speed limit. Rangers have stealthy locations they set up at at the bottoms of steep descents where they can nab unsuspecting riders. I've seen riders pulled over getting tickets and I myself have been stopped once by a ranger proclaiming she thought I was doing 9MPH but the radar gun said 8MPH. Not sure what that was about. Trail etiquette is to warn oncoming riders if you've passed ranger activity coming up the hill. If Garmin is listening, please add the ability to set an audible warning for exceeding a preset speed limit on the bike GPS units. You guys could make this into a big marketing feature, as the cost of a GPS unit is about the cost of a speeding ticket out here in NoCal. It took me perhaps 6 months to get these pages dialed in to suite my needs and riding style. I tried to keep some common data fields in similar locations across screens, like speed, cadence and heart rate. Be sure to document your finished screen layout because that can change at random. Most of the random changes I've seen have been due to not locking the screen before putting the GPS in a pocket while using it. But one time a change seemed to happen when plugging into a USB power bank with the GPS running. Have done this many times, but one time a data field changed. I got a lot of good information of of DC Rainmaker's web page ... https://www.youtube.com/watch?v=0xBp25pXxY4