App
ANT+ Power Meter
개발자 takura87 · v0.7.5
평점
4.6
리뷰
55
다운로드
10,000
가격
무료
설명
- Note: From recent user reports it seems this is currently not working with TrainingPeaks. - DCRainmaker wrote about this: https://www.dcrainmaker.com/2021/05/how-to-use-a-cycling-power-meter-with-a-vivoactive-or-venu-watch.html - This is listed in: https://www.thisisant.com/directory/ - If you have problems or requests, please message me with your email address! While I appreciate all reviews, reviews work only one-way: negative ones often lack information to improve an real issue or may even be incorrect. SUMMARY: This datafield displays (and records) power (and cadence) A: from a power meter (PM) on a less-expensive device without "native" built-in PM support, or B: from a second PM on a devices with native PM support, e.g. to compare two PMs. INSTRUCTIONS: (1) This app will initially (when ANT ID in app settings is set to zero) search for a PM that is nearby, woken up and sending power data. If that's the only PM nearby, you're ready to go. If not, I recommend setting the ANT ID in the app settings to avoid connecting with another PM. You can do so using Garmin Express app on PC/Mac or Garmin Connect app on iOS/Android. If you don't know the ID of your PM, it's displayed after searching. Or look it up somewhere on the PM or somewhere in/on the package of your PM. (2) Searching will pause after 2 minutes to reduce impact on battery. Tap the data field or press start/stop/lap button to restart search. You can deactivate pausing in the app settings. (3) If it doesn't find your PM, please check that (a) your power meter is powered on and woken up, (b) there isn't radio noise nearby (e.g. microwave oven), (c) the PM is not paired natively in the settings of your Garmin device, (d) your PM is not connected in another CIQ app, (e) if searching repeats endlessly or you see "failed" between searches, you should try to restart the app: Switch to another activity and back, switch the datafield to something else and back, or switch the device off and on. (4) On devices with a touchscreen or a dedicated start/stop-button, you can manually trigger calibration (i.e. zero-offset) by tapping the data field or quickly pushing the start-stop button two times in a row (either start-stop or stop-start). The first time, a confirmation screen ("calibrate?") will be displayed and a second tap (or start-stop or stop-start) will start the calibration, followed by either "success", "failure" or time out. If you ignore "calibrate?", it will time out and return to normal. LIMITATIONS: Sadly, this is not a full replacement for a device with native PM support by its manufacturer. (i) Data written by this app is not equal to that written by native PM support due to a limitation by Garmin's ConnectIQ (CIQ) API. Whoever reads your .fit files needs to explicitly support custom CIQ data. Only a few platforms (e.g. TrainingPeaks) treat the data equally (please set the "saveAsPower" option in the app settings; note: large memory devices only!). Some (e.g. Garmin Connect) display the data (e.g. in activities) but don't analyze (e.g. as MMP). Most (e.g. STRAVA) will neither display nor analyze. (ii) For use case B, this data field is good with Garmin Connect, DCR's comparison tool, Golden Cheetah and TrainingPeak's WKO software. (iii) This ANT+ connection seems slightly less reliable than native connections and could drop when computational demand was high - e.g. a lot of other CIQ apps running and many events (e.g. navigation, BT notifications) happening at once. Please log important data using other means. (iv) Cadence and average power are only available on devices with memory for data fields larger than 16kB. Some power meters will require additional settings. For a third PM use the "Third PM" data field. FOR MORE INFO: https://takura87.wordpress.com/2020/06/14/ant-power-meter-datafield/
새로운 기능
Thank you for the requests to add newer devices. Ideally it would be as easy as ticking a few checkboxes and adding a few lines of compiler instructions, but I found out that some of the changes of Garmin's API are in practice not backwards compatible and the source code simply doesn't compile at this moment. With a lot going on in my life, the next expected date is therefore summer of 2024. I am happy to receive requests as that helps me to gauge interest and decide priorities, but please understand it may need some time to follow up on. IMPORTANT: I have received some reports (thanks!) since October '21 that some users had trouble with this - from recent reports, it seems that data is visible in Garmin Connect but no longer in Training Peaks, independent of the app settings. Unluckily I haven't had the time to check this in details, but as there have been no changes on my side, my best guess at this moment is that Training Peaks changed how they handle custom data fields. I am deeply sorry that I have been very busy during the last months and unable to check in detail - I will look into this once I find time. Please be patient, appreciate that someone is working on this for free and don't flood with negative reviews... if you have time, please click the Contact Developer link and let me know if this works for you at this moment or not. Sorry if you messaged me and I have been too busy yet to respond - I do read all messages and am grateful as they help me understand the situation. Note: Released a duplicate of V0.6.5 (without average power) as the companion "Third ANT+ Power Meter" data field. If you have problems with the most recent version, you could temporarily try that one instead. Would appreciate if you could use the "Contact Developer" link to let me know with your email address about the problem you are having. V0.7.5 (Nov 2,2022): Bug fix for 1040. V0.7.4 (Aug 17,2022): Added newer devices. V0.7.3 (Aug 12,2021): Improved handling of app settings to avoid functions that will be deprecated soon. Had to remove FR920xt from supported devices as it would no longer fit into memory - you can use the "third ANT+ PM" data field instead. V0.7.1 (Aug 11,2021): You can choose in app settings to display average power - either 3s, 5s, 10s, lap or activity average. If you see the CIQ symbol indicating an error, or don't see the option in the settings, please delete and re-install app. Requires a device with memory larger than 16kB for CIQ data fields. See here for details: https://developer.garmin.com/connect-iq/reference-guides/devices-reference/ V0.7: Properly supports extended ANT ID's larger than 16bit or 65535 decimal. This was accomplished with the help of a user as I didn't have such power meters available - thanks a lot!!!!!! V0.6.1: Shortened the duration a previous power value would be continued to be displayed in the absence of updates, e.g. due to radio interference, from 5 to 3 seconds, to more accurately reflect the actual communication conditions. Also changed handling of Torque Frequency messages. This might improve behavior when stopping pedaling on some power meters. Would appreciate feedback. Requests on hold: - I sometimes receive the request to only record power, not cadence. Sadly, with the current CIQ API, I'd have to make a separate app for that, which would require more time and potential for error to maintain this. - I sometimes receive requests to only display power, not cadence. I will consider this in the future, but making the display work for round and square displays and all the different data field layouts is already not trivial, and keeping this updated for new devices, extended ANT ID's etc has been consuming all the available time so far. Hope you'd understand!
리뷰
리뷰 기사가 곧 게시됩니다.