new Garmin Edge x40 Series (Explore too)
Some Garmin Edge 540, 840, and 1040 owners will soon ask, “Why can’t I attach my Garmin to my computer anymore?” The answer is that you’ve just received an upgrade! You will still be able to link to your computer but in a more inconvenient way, which might stop you from doing some actions.
This is a minor update for the Edge x40 series. It’s not yet in public beta and highlights a supposed upgrade to MTP.
Here: Garmin Edge 540/840 beta, and the same for the corresponding Explore model
Here: Garmin Edge 1040 beta
Unlike the Edge 1050, the x40 series can currently connect to desktop computers and appear as a drive letter, allowing you to automate some actions and edit files directly on the Edge.
The ‘update’ to MTP restricts all of that. Here’s what happens
- Can no longer mount the Edge as a drive letter. Some sports programs require this.
- The connection is slower.
- You can’t edit files on the Edge but you can copy them off, edit elsewhere and paste back.
Garmin has done this for technical reasons that help the company, including:
- File Management: MTP allows for safer file handling without ejecting the device.
- Compatibility: Works with various file systems, ensuring broad device compatibility.
- Battery Efficiency: Consumes less power than USB mass storage mode.
- Data Protection: Reduces file corruption risk, as the device’s OS controls transfers.
- Multitasking: Allows device functionality while connected.
Thoughts
I bemoaned this same ‘upgrade’ to watches several years ago. If you want to attach your Edge as a Drive letter to a PC, there is no workaround other than using paid-for and obscure software.
It’s great that the over-shift tone has been added. That is one of the few tones I’m grateful for on Garmin Edges that other brands seem to lack – there is a beep as you reach one of the two most extreme gears ~(it would also be nice to have this in Gear 9 on an 11-spd Ultegra Di2 setup (which prevents shifting to Gear 10…unlike Dura-Ace)
This release has further undocumented features that allow more detailed configurations of Di2 buttons to handle media files during the ride.
Change Log: Log 25.17
- Updated to MTP (Media Transfer Protocol).
- Restored electronic shifting over-shift tone.
- GroupRide
- Fixed GroupRide dynamic glance, failing to update with finished ride data.
- Fixed GroupRide awards getting reset after a power cycle.
- Garmin Coach
- Fixed an issue where the dynamic area would not update with the Garmin Coach workout.
- Fixed Garmin Coach workout not showing as complete in the Garmin Coach glance.
- Fixed issue where the device wouldn’t show some Garmin Coach plans in the Garmin Coach widget.
- Removed legacy FTP test.
- Lactate Threshold estimates are applied automatically after training with heart rate.
- Added 10s/30s average power graphical data field.
- Added a confirmation message for successful manual altimeter calibration.
Overshift Tone was not added but restored, it’s here in current public release.
I think it was removed I that beta wich you have to install as a step to get to the new beta cycle.
MTP is only relevant at exactly one operation for the majority of users: creating startup.txt since betas are OTA. And I still believe betas OTA is a mistake because installing it on MTP devices sorted out the dumbest 30% of users who weren’t able to read the provided instructions Those user now complain on watch betas that diving oder ecg is disabled etc.
when i used sporttracks it essentially worked best if i had a drive letter for my forerunner/edge/elemnt. MTP stopped that.
So both the links take you to a Forerunner 955 page…
fixed, thank you Jon
Even less reasons to upgrade from an older device I guess. Improved battery life and improved gps accuracy are the only things that make me want to update, but it’s good enough in the 520.
agreed.
i think the x50 next year should be good enough to temp an upgrade from x20
Switching to MTP is a massive problem for me because I use my Expore2 as navigation device on long bike journeys. Loading a new route in offline conditions isn’t possible with Garmin Connect so I made a cable connection via USB-C to my Phone or iPad and pushed the gpx-file to my device. If I get the update I have no solution for this! Sorry Garmin: My last device I stayed with is mostly useless to me!!!
you should still be able to conenct but as a media device and not as a drive letter.
unsure how that precisely affects you with a cable link to a phone/pad
I know how much I prefer working with mass storage over working with MTP, but considering the real risk of file system mishaps I can’t help but congratulating Garmin on resolving what must have been a major source of support issues. It’s the same category as the removal of microSD in the 1030+: a powerful tool gone (I used to travel without OTG cable, knowing that I could pop the microSD in my phone if ever I needed access to newfiles), but so many bug reports caused by flaky memory cards avoided.
a good and different perspective.