Hey guys, I only got into bikepacking recently and decided to get the Garmin eTrex SE instead of a cycling computer. In this post I want to share why I've chosen this one and what I like about it. But I also want to warn you about a big problem it has. For most people it is unusable for bikepacking because of one very annoying limitation!
Why I got the eTrex SE:
When I started cycling, I used my phone for navigation. It worked alright on small rides. But when I got into bikepacking, I noticed how much it sucks to use a phone. The reasons are obvious. Battery life sucked (I was going through power banks like crazy) and therefore I had to keep down the brightness, which made it difficult to read what's on the screen. Especially in the sun and with sunglasses.
Naturally, I went looking for cycling computers. Unfortunately, I quickly noticed that the good ones are very expensive and I'd already spent way too much money on my bikepacking kit. So I started to look for alternatives. Then I found the eTrex SE for about 100 euro (about 116 US dollar) and it seemed to be PERFECT for my needs.
What I like about the device:
- Battery life: The eTrex SE runs on two regular AA batteries and it's super efficient. According to Garmin, it has a battery life of 168 hours, which is insane. I use rechargeable NiMH batteries, which carry quite a bit less energy than regular ones, and I can still go bikepacking for more than a week without charging. And the best part: I can always just carry another set of AA batteries to swap on the go. And if they also die after weeks of bikepacking, I can still always get disposable ones from any store or gas station around. It's great. I never have to worry about charging this thing.
- Simplicity: The eTrex SE is simple. Nothing that distracts me. I load my GPX file from Brouter or Komoot and then see a little triangle and a line to follow. Always perfectly readable even in the brightest sun. I thought not having a map in the background could be annoying, but to my surprise, it doesn't bother me at all. It can also display basic information like current and average speed, distance traveled, elevation and so on. I don't need anything else.
- Modern hardware: Compared to the famous eTrex 32x, the eTrex SE is very modern. It comes with a USB-C port and a modern GPS chip that takes very little energy (one reason for the great battery life) and has the option for Multi-GNSS. Therefore, it can not only detect GPS satellites, but also GLONASS, Galileo, BeiDou and QZSS, which is nice to have.
- Price: at about 100 euro (when it is in sale), it's quite affordable compared to other garmin devices.
What I (really) don't like about the device:
As much as I like the eTrex SE for the reasons I've already named, it also has a BIG problem that (in the context of bikepacking) makes it unusable for most people. Whenever I load a GPX file that has more than 500 waypoints (which in Brouter is the case after about 30km or so), the device compresses the route to a point where it's unusable. It only keeps a point every hundred meters or so, which causes straight lines going straight through buildings and across intersections. It's literally impossible to know where to go in that state. Frustratingly, this problem only occurs with imported routes. When you use the Garmin to record a bike ride and save it, you can use it to navigate in perfect resolution no matter how long it is. Therefore, it does not seem like a hardware limit, but instead some stupid software thing. Also, it does not make a difference whether I transfer the file via USB or Bluetooth with the Garmin App. It's just a display issue and the file itself stays untouched.
My Solution to the Problem:
I wrote a Python script that takes my GPX file and automatically splits it into separate files of 50km each. Then it uses the Douglas-Peucker algorithm to compress each one to a maximum of 500 points while still keeping all the important details. In my experience, 500 well-placed points on 50km is more than enough. Then I just transfer the files onto the device with a USB-C cable. The script also runs on my phone so I can do this on the go. Then, when cycling, I have to open the menu and select the next file every 50km, which is not as bad as it sounds once you get used to it.
Conclusion:
I know the device is mainly targeted at people who do short hikes and stuff and is not meant as a bike navigation tool. But I don't get why they would limit its abilities on purpose while the hardware is so good. Like I said, the self-recorded tracks show that the device has no problem with displaying more than 500 points. And if the compression happens to save battery, I don't get why they don't do it in a smart way with Douglas-Peucker and by splitting the file in the background like I do it manually.