This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

My experience with v3.40

After a short 44 mi. ride this morning here are my findings:

Grade % = completely useless. Garmin remedied the limit of 6 or 7% but now it is wildly erratic, inaccurate and never stabilizes. The numbers are all over the place. I made several stops after riding different gradients and took notes:

Flat (0%):

+5, -2, 0, +4, +3, -1, +2, 0, -4, +3, -2, 0, +1

3-4% grade:

-1, -3, +9, 0, -4, +5, -2, +7, -3, +6, +4, 0, -2

On a steeper climb, 10-11%:

After around 6-7% it was less erratic and made smaller fluctuations between 8% and 10% which is normal. I don"t know if it ever displayed 11% as I was dividing my attention. ;-)

It's just as bad on descents.

Incident Detection: Garmin has increased the sensitivity WAY too high! From 21-22mph I made a stop and lifted the bike six inches to maneuver around some road construction. The darned alert sounded! Good thing I was able to cancel it before it shot off messages. I have permanently disabled it.

BT Connection (phone): I'm one of the luckly ones who previously had no problems with my (older) phone, Galaxy S5, until today. It always connected right away but not today until about a half mile into the ride.

Autostart LiveTrack: Unable to test (see above)

Recovery time now displays at the end of a ride.

Recording to micro SD:
I haven't yet connected my 1030 via USB to actually verify this but today's ride listed in History has an asterick associated with it. I am assuming this identifies the file as being located on the SD card. That said, I did not get the usual "Ride uploaded" message at the end of the ride. Worse, I attempted to upload it directly from the device and received an "upload failed" message. Some minutes later, notifications appeared on my phone, both GC and Strava. Problem may be coincidental, or perhaps not.

I forgot to test the 3D mode on the map. Next time.


  • Former Member
    0 Former Member over 7 years ago
    To connect via ANT you need to disable the BLE pairing that you already have and do a new search. It may take a while for the ANT ID to show up.

    The P1 pedals will default to using a crank length of 172.5. If you cannot get the ANT pairing to work you can use the BLE pairing and the PowerTap phone app to set the crank length.


    Thanks for your help Alan. I can’t find how to disable the BLE for the sensors, the only one I see is for the phone.

    Also thought the option of the app but the latest version of it doesn’t have the option like used to be. And looking for the reason I learn that it doesn’t work for this purpose, because that lenght only works when you are recording on the Powertap app. You need to get it right in the garmin in order to the pedals calculate it accurately.

    In other topic, with the v3.4 the rides was auto-uploading fine, but today with the 3.5 tried everything and ended connecting it to the computer.
  • Sorry I should I have been clearer. There is not a way to disable the P1's from sending both BLE and ANT messages. What I meant was to disable the BLE pairing that you made for the P1 on the Edge.

    On the list of paired sensors on the Edge, find the entry that is for the P1 and open it, and then using the slider button at the top of the page switch that off so that the Edge stops looking for that BLE address.

    Strange about the phone app. What if you don't have a Garmin. I would not think that PowerTap would want to require their customers to by a Garmin just to set the crank length.

    Are you on an Android or iOS phone?

    What crank length are you using?
  • Former Member
    0 Former Member over 7 years ago
    Sorry I should I have been clearer. There is not a way to disable the P1's from sending both BLE and ANT messages. What I meant was to disable the BLE pairing that you made for the P1 on the Edge.

    On the list of paired sensors on the Edge, find the entry that is for the P1 and open it, and then using the slider button at the top of the page switch that off so that the Edge stops looking for that BLE address.

    Strange about the phone app. What if you don't have a Garmin. I would not think that PowerTap would want to require their customers to by a Garmin just to set the crank length.

    Are you on an Android or iOS phone?

    What crank length are you using?


    That works great! Thank you! Now I can set the crank length and the calibration prompt works.

    The thing with the crank length is the pedals doesn't store that value. They read it on the computer (of any brand) or from the app using to record the activity. So you have to set it right on each app and computer.

    I have iOS, in the previous version where you update the firmware was the crank length for each pedal. This is why I also had this misconception, now they move it inside the app to avoid it.

    Best regards
  • The current software version is 7.30. Please start a new thread if you would like the discussion to continue.