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.


  • And one more error found - the Stress Score can not be saved.

    Next blunder - in spite of setting the Polish language, the message is displayed in English.ciq.forums.garmin.com/.../1263688.jpg
  • What model of D-Fly are you using?
    • SM-EWW01
    • EW-WU101
    • EW-WU111


    Problem has been solved after my urging to use the app and not the Windows/laptop method. I do not own any Apple products but I probably will shortly.

    I have the EW-WU111. 9150 Groupset, everything recent. The problem is that there are still many "pro" guys at dealers and LBS that do not know about the Apple-app-only requirement to update the WU111. Some still think, wrongly, that the old method via hardwire on a laptop updates all components simultaneously as was the case previously.

    -Patricia
  • Correct. The new BLE/ANT D-Fly needs updating from the phone app.
  • Not to beat a dead horse but...

    I had made a call to Shimano and spoke with a customer service rep who also confirmed this and replied, "go find someone with an iPhone." Seriously? And they call this customer service? One well-experienced service mgr. experienced a failure/abort 10% into the process and called Shimano for assistance. Interestingly, thevery same Shimano rep replied, "Yes, this (aborted update) is a known issue with the app." He did not know I was present and listening to the conversation. The same CS rep made these statements to two people within 90 minutes! Pretty unimpressive.

    -Patricia
  • I have reported the Stress Score error mentioned here and the language issue.
  • The auto mode livetrack doesn't work with 3.4.
  • 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.

    2. When using GPS for speed and distance I got several GPS signal lost notifications. It was sunny, clear and I was out in the open during all of these failures.

    3. Had about 15 BT phone disconnects and reconnects.

    4. During the 52 mile route, about 30 miles in, I went to the map page and the Edge 1030 froze and locked up. The only way to get it working was a hard power down. When I booted back up, the previous 30 mile were gone. Had to start a new ride.

    5. Varia Radar stayed connected but the Edge failed to form the Light Network.

    Bottom line, it's going back! I requested a return and already have the return shipping label. I'll factory reset it and mailbox back tomorrow.
  • I certainly understand your frustration. It's a shame that problems haven't been resolved given that there are many who have working devices with far less, hopefully temporary, bugs.
  • Not to beat a dead horse but...

    I had made a call to Shimano and spoke with a customer service rep who also confirmed this and replied, "go find someone with an iPhone." Seriously? And they call this customer service? One well-experienced service mgr. experienced a failure/abort 10% into the process and called Shimano for assistance. Interestingly, thevery same Shimano rep replied, "Yes, this (aborted update) is a known issue with the app." He did not know I was present and listening to the conversation. The same CS rep made these statements to two people within 90 minutes! Pretty unimpressive.

    -Patricia


    I encountered this when installing my EW-WU111. The firmware upgrade was interrupted. My entire Di2 system was bricked! It was entirely inert. I was not pleased, but after trying a variety of random things I got everything back in working order.

    Here’s what I did:
    • Removed the EW-WU111.
      • Now the lights on the junction box are just going nuts! All sorts of random flashing and flickering. A lot more green than red.

    • Attached the adaptor and connected via the Windows desktop E-Tube software. The derailleurs were not recognized.
    • Disconnected the E-Tube application and the adaptor hardware.
    • Disconnected both derailleurs.
    • Lights no longer going nuts..
    • Connected to the PC (really an emulator running under VMware on a Mac). Now everything is recognized but the disconnected derailleurs.
    • Disconnect E-Tube and adaptor.
    • Reconnect the derailleurs. Success! It shifts!
    • Reconnected to E-Tube which reports everything operational.

    At that, I hung it up for the night.

    The next morning I decided I’d give the EW-WU111 another try. It reports damaged firmware and offers to reinstall it. What are my choices? I said OK. It worked. So I now have what I wanted, but I gotta tell you, having a bike with an entirely inert shifting system is pretty alarming!