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.


  • You are not alone -- the service mgr. bricked my DA Di2 too! I had one of the most expensive fixies in existence. I pedaled home completely p#@%ed. Learned my lesson about letting anyone other than my brilliant, experienced mechanic/tech guru touch my bike. The next morning he had it up and running in 30 minutes simply by plugging it in to the Windows eTube software (recognized, fortunately) and performing the update/diagnostic process followed by the wireless update of the EW-WU111. All went smoothly. No need to pull out wiring or disconnect derailleurs.

    Shimano should be ashamed.

    -Patricia

  • And the ascent total is still reporting higher than actual.


    My experience with the 1000 was that on any ride that was essentially flat, if I turned on map corrections in Garmin Connect the number would be adjusted downward (but who cares if 900 ft. over 35 miles became 700?). On rides with significant climbing, turning on correction would inevitably result in a significant increase in the total climbed.

    With the 1030 elevation correction has not so far (16 rides) resulted in nearly as big a change. So it seems to me that the elevation data (or its interpretation by the firmware) in the 1030 is distinctly better than that of the 1000.

    Which makes the gradient errors all the more puzzling.
  • Today was the final straw. Went on a 52 mile ride and had numerous issues.

    1. Speed and cadence would not auto connect or stay paired once I manually paired them. Finally deleted them and just used GPS.

    .


    Have the same issues.
    ANT+ sensors not auto connecting.

    And then today I had the HR sensor just stopped mid ride. Had to manually reconnect again. It worked from there on.
  • I didn’t feel like being a beta tester so I returned my 1030 pretty qickly for a full refund.

    I guess Garmin are pleased that many users are happy to continue testing the unit to iron out the bugs. Hopefully, sometime in the future it will be ready for the mainstream?
  • - Autostart for Livetrack works for me in 3.4 and didn’t work in 3.2
    - My iPhone 5s iOS 11.0.1 connects automatically with the Garmin Edge 1030 but Garmin Connect Mobile has to be opened in the phone, (location services and background app refresh on) also you have to switch on bluetooth via settings menu not control center.
    - Garmin Connect Mobile needs an update for iphone users in iOS 11 because you cannot use twitter or facebook share for Livetrack.
    - Training performance data is not transfered from Garmin Edge 1030 to Garmin Connect.
    - Resting Heart Rate is everytime I switch on the device reset to zero.
    - I switched off wheater data on Garmin Connect Mobile and is appearing on Garmin Edge 1030.
  • Former Member
    0 Former Member over 7 years ago
    I have some of the issues reported earlier, but no one has mention a issue with powertap pedals. I can’t set my crank lenght on the garmin, nor recieve the calibration prompt altought is activated.

    I feel like a made a mistake selling my 520 for this, this and other issues was covered way back.

    Almost forget to mention the problem with the speed, all my settings of distance and elevation are in meters but the speed keep appearing in mph, not in kph as it supossed to be. This last issue is not only shown on the 1030.
  • With the P1 pedals are you connecting over ANT or BLE?

    What software version do you have on the pedals? The latest is firmware 30.028, released July 17, 2017
  • We have released software version 3.50 to address the map issues reported here.
  • Former Member
    0 Former Member over 7 years ago
    With the P1 pedals are you connecting over ANT or BLE?

    What software version do you have on the pedals? The latest is firmware 30.028, released July 17, 2017


    The pedals are up to date and connected via BLE. Can I change it to ANT?

    I tried deleting the device and setting it again after updating the Edge, but nothing change.
  • 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.