Showing posts with label Garmin Fenix 5X. Show all posts
Showing posts with label Garmin Fenix 5X. Show all posts

Sunday, May 27, 2018

Update: Running with Poles, Garmin Fenix 5X, and Sore Quads

I'm no spring chicken, so I've been careful about increasing my mileage and elevation too quickly as I train for a run on Washington Section J Southbound of the PCT. I want my body to adapt to a gradual increase in the pounding punishment of trail running.

I make this sound fun, don't I?

This weekend, I increased my distance by two miles and my elevation by 500 feet after having run the same distance for seven weeks with some easy weekends thrown in. I planned out a course in the Issaquah Alps (Tiger, Squak, and Cougar Mountains) that was supposed to be 22 miles according to Garmin Connect. According to my Garmin Fenix 5X, it was 24.52 partly due to me taking a wrong turn. But my planned 20 mile runs each turned out to be longer, too (22 miles and 21.5 miles), so I figured it was par for the course.

I approach the summit of West Tiger 1, a place I've never been despite growing up in Issaquah. I forgot to put my 22-mile alps course on my watch, so I had to navigate using the map on my watch and my notes as to what turns to take.

I successfully reached the top of West Tiger 1 and looked back where I'd come from to see a sign confirming my location. Had it not been for two other trail runners who came a minute later, I might not have found the unmarked Poo Top Trail, though it was the only trail up there.

In an attempt to avoid sore quads and calves, I have been employing several tactics: trekking poles, downhill technique, hydration, and fueling (before, during, and after). Last week, I ran 12 miles on Squak Mountain with running poles for the first time. It took me a bit to get the hang of it (see previous post), but this weekend went much better. I have come to a few conclusions about running with poles:

  • They are extremely helpful for moderate to steep climbs and steep descents. 
  • The most effective use uphill seems to be a motion that mimics the arm motion when you're on an elliptical. (I'm still working out good downhill technique.)
  • It's best to put them in your pack if you're not going to be using them for a while. My shoulder fatigued yesterday because I had been carrying them both in my right hand for a long time.
  • On easier climbs and easy to moderate descents, I prefer no poles.
  • Not having your hands free is a bit of a pain. You can't look at your watch, drink, or eat while using poles. 
  • Planting a pole on the inside of a downhill switchback is a great and fun technique for getting around the corner swiftly.

Do they help? On the one hand, I can feel a little soreness in my quads today, but on the lower quads rather than the upper quads. A new experience is that my arms are tired. Carrying anything for a sustained time was hard today when normally I wouldn't notice it. My legs were a bit heavy for today's eight-mile run, but not bad considering yesterday's effort. Also, I ascended Tiger Mountain about a minute faster yesterday than the previous time I ran up it. Next week, I will do another 22-mile trail run and I will take just one pole to see how I like that. Overall, I think the poles help distribute the effort to the upper body, thereby lessening leg muscle soreness.

Pole updates: third run near end of post

I also tried out my fastpack vest. It needs some adjustments in the fit--I need to tighten up the side straps and loosen the front straps so that the two sides of the vest sit wider across my chest. It's not a women's specific pack, that's for sure! All in all, I don't think I'll have any issues with it, and my bear spray fit securely in one of the easily accessible front pockets. My vest and poles.

As for fueling and hydrating, I took more water than I ever have--about 40 ounces--for a run of seven hours. I tried something new in my water, Tailwind. I previously thought that it had protein that was vegan, but it turns out that that is their recovery drink. Nonetheless, I preferred Tailwind to Clif. There's not much in Clif, maybe 40 calories a serving. I used Endurox for my recovery drink, which is not vegan, and it upset my stomach. It has whey protein, which is supposed to be the best for recovery, but not being used to dairy, my stomach didn't like it and I found the taste unpleasant. To me, it had an aftertaste a little like sour milk. I just bought a huge container of it, too. I plan to get some Tailwind recovery drink instead.

One last update is regarding my watch. When I ran on Squak Mountain last week, I was certain that I was following the magenta marked course, but it was no course I had ever created so I was baffled. This weekend, I figured it out! When you get off course, the Fenix 5X will route you a new course to get you back on track. I think I like that feature. I just wish it could be a different color so that you would know you were off course but on track to get back on course...but not actually on your planned route.

Coming up, I'll sew the screen on my bivy and write my article for Backpacking Light about making my own bivy. I have abandoned my plans so far for training on other parts of the PCT because the elevation gain is too slight. But I hope to put the bivy to use before June is over.


Monday, May 7, 2018

Issaquah Alps Westbound Trail Run

I was finally successful with my Garmin Fenix 5X! I used it to navigate some unfamiliar trails southwest of Tiger Mountain's peak and also make my way on Squak and Cougar in the opposite direction I am used to. I noticed that it also gives me an ETA, and it was pretty accurate. In the beginning, it said 1:45, and then later 2:30 and 2:10 as my steep climbs, flat, and downhill running evened out; I ended up finishing at 2:00. Obviously, the longer I was out, the more accurate it got. Overall, I find the watch easy to use...now that I know how to use it. Getting there was challenging, though!

Speaking of challenges, my run was probably the hardest effort I have ever put forth. It was 22.3 miles with 6,900+ feet of elevation gain. Starting with Tiger and finishing with Cougar meant slightly more elevation gain than loss. I loved the Tiger Mountain part of the run. I went on a trail I had never been on before after the peak of West Tiger 3, and it was quiet, rolling, and soft. I did see nine other trail runners along this portion of the route, so it must be popular with trail runners. They were all running in the opposite direction, which made me wonder briefly about their routes. The trail dropped me down to Poo Poo Point for a quad-punishing descent to Hobart Road.

I fasten my vest and get ready to start at the base of Tiger Mountain. My husband likes to take a picture of me at the start just in case something happens to me. This way, he knows what I am wearing in case he has to described it to authorities.
I am happy with my accomplishment of descending to Poo Poo Point. It was a beautiful day for a trail run!
Climbing Squak from the east side is definitely steeper than climbing from the west. The East Ridge Trail was full off sharply slanted switchbacks I thought would never end. Fortunately, my watch tells me how far I am from my next turn, so I knew it would eventually come to an end, and in just how far. I had to power hike (fast hiking pushing on my knees to go faster) more than half of it. Once I got to the East Side Trail, it was completely runnable--rolling ups and downs and quite pleasant. I knew I had some solid descent and climbing ahead of me before I got to make my main descent down to SR 900. I dropped down quite a bit on the Bullit Fireplace Trail only to climb back up on the Chybinski Loop. I was relieved to finally get to Margaret's Way, which is fairly gentle until the last pitch downward.

One more mountain to go, and the shortest stretch. I knew the climb from the east was steep, but I was surprised at how much I was still able to run. Lots of power hiking up steep switchbacks and step-ups were a sign that my legs were simply dead; my quads hurt, but I just kept pushing onward. My mantra for the day was Jillian Michael's "Get comfortable with being uncomfortable!" and I thought that many times on Cougar. I knew once I got to Shy Bear I was home free. The descent on the Quarry Trail was at times painful, but I plodded on and took it easy so I didn't trip. I was so happy to see my car!

Afterward, I forced myself to eat half a banana and a Clif Bar, and to drink my recovery drink from Pacific Health Labs. It's weird, but food just isn't appetizing after that much running. The last time I had eaten was at 4:00 am. My run, which I started a little late at 7:50, took six hours, 10 minutes. I used gels and an Endurox slurry, along with a Clif carb/electrolyte powder added to my water along the way. I finally ate solid food at 2:00.

I didn't take an ice bath when I got home this time. I am always cold when I finish a run like this, despite the 70 degree afternoon, and I just couldn't bare the thought of getting into cold water. I took a hot shower instead and it relaxed my tired muscles. I ended the evening with a soak in the hottub.

I slept HARD. Sunday morning, I had a six mile run to do, and I thought it would be awful, but I surprised myself. I had a great run. My legs were tired and burned with lactic acid, but they weren't that heavy. After a slow first mile, I managed a 9:43 mile with hills on the Tolt Pipeline. I finished with a trip down and back up 'the big hill' with a mile time of 12:01. That's better than I usually do. Huh.

Today, it was tough to get up before 6:00 for work, and I sleepily struggled through my core routine. Somehow, I managed to do the usual exercises as well as weighted squats and dumbbell deadlifts. I shook out my legs with a nice mountain bike ride in the afternoon with my good friend Nicole. My legs burned a bit on the climb up the High School Trail, but afterward, I felt great. My soreness is ebbing (DOMS). A few minutes with the foam roller tonight should take care of any residual soreness.

Next weekend will be another 20 mile long run. It will be the first time I have ever trained with back to back hard weeks instead of alternating easy and hard weeks. I am hoping to create a route all on Tiger Mountain. We shall see!

Wednesday, May 2, 2018

Using Map Navigation with the Garmin Fenix 5X

8/11/2018 update:
Since this post, I have used my Fenix 5X to navigate for three months. I now LOVE the watch and have no trouble using it. If you have recently purchased one, be patient. I takes time to learn to use the watch. If you are having trouble with it, please send me an email or post a comment with your question, and I am happy to help! The one thing I haven't used (because everything I've read says you can't) is waypoints. But I've followed courses I've created in Garmin Connect, GPX tracks that I've downloaded, and just used the map when out on the trail. I love the maps, and also being able to track my effort via my heart rate, which can be very useful when running for eight hours, the last several in in the heat.

Original post:
I had mixed success on today's run with my Garmin Fenix 5X. I made a route for Tiger Mountain, starting at Issaquah High School, doing a big outer loop partly on the mountain and a smaller loop inside the big one on the Lake Tradition Plateau to round out an eight-mile course. Oddly, I didn't get any course signals today at all, neither on or off course alerts. As I started up the West Tiger 3 trail, I decided to try to get the map to show while navigating.

My double loop route on Tiger Mountain

I read on the Garmin Forum that holding the menu button for three seconds AFTER hitting the up or down button would bring up the map. I thought I tried that last weekend on Squak Mountain, but the key was hitting the up or down button first. When I did that and then held menu for three seconds, I was able to choose "Show Map."

I had another surprising choice as well: turn-by-tun navigation. I tried that first, and it simply gave me a written direction for the upcoming turn on a specific trail. It seems you have to hit the down button to get the next direction, but I may not have given it enough time. Anyway, the next direction said to turn left on a service road, and then it said service road end. I thought it meant the end of the course, so I abandoned the turn-by-turn navigation. Looking back, I realize now that the watch may have actually been referring to the end of the service road (which does end at the parking lot nearby).

Anyway, I switched to map view instead. I was so excited because I could finally see my route and my progress on it while running. I was also wearing my new sunglasses with the new location of the reading bifocal half circles, so I could easily see the map. My only problem was I couldn't understand how to read it! I got to a junction and should have turned right but I didn't think that was what the course showed, so I didn't take it. Big mistake. By the time I confirmed my suspicion that I was off course, I was .9 of a mile (according to the helpful sign) from the summit of Tiger! Oops. A little more elevation than I wanted because I have a big elevation day this coming Saturday.

I started to continue the route to the top, figuring I may as well finish now that I was so close, but then I looked at the time. It was 7:52, and I wanted to be done by 8:20. I sped back down and took the turn I was supposed to take. It took me by the Talus Rocks and then down the Nook trail. I ended up doing nine and a half miles. One exciting thing happened as I got back on course. Even though I was no longer in map mode, it started giving me turn warnings and showing the map. It beeped at me and showed a big arrow for my upcoming turn, and gave me a countdown in feet as well. It gave me a second countdown and warning when I got closer, and went to zero feet at the exact moment that I should make the turn.

Originally, I thought that the watch was not set to track orientation, but when I checked it was. (The options are north orientation and track orientation.) Now that I think about it, I think it was doing exactly what I wanted and expected it to do but I just didn't realize it. I am pretty inexperienced with GPS tracking.

One thing that didn't work is the course points I put in to warn me of upcoming turns. The watch just beeped at me, but it didn't show the names of the course points so I had no idea which way to turn. It was a good idea, but I don't think it is needed.

Before Saturday's run, I am going to map out a simple course in my neighborhood to see if I can read it correctly. I also need to figure out how to get the course turns showing on the map, because they weren't doing that before. I am not sure what I did to get that to happen! It's a good thing I have the rest of May to figure out the watch before I hit the PCT!

Saturday, April 28, 2018

Navigating Squak Mountain with the Garmin Fenix 5

Today, I set out to do my easy weekend long run on Squak Mountain. I was looking for a run of 12 miles and I wanted a good deal of elevation gain, but I also wanted to try out navigating with my Garmin Fenix 5X.

After reading the Garmin forum, I decided to use Garmin Connect to create a course, which I sent to my watch. I used the "freehand" feature in Garmin Connect to draw my own route. It gave me elevation gain and mileage--nice! The map showed the trails on Squak Mountain and I planned out a lollipop loop route. The mileage was 12.23 and the elevation 4100 feet. I have to activate "Navigation" as a choice when I activate my watch (like when I choose trail run, run, mountain bike, etc.) and then I can choose "Map" to see the course or "Do Course." It seemed like a good plan. (Note: Since I first published this post, I have learned it is better to leave it on "follow roads." Even though I am not running on roads, it will still trace the trail(s) between point A and point B for me. Nice!)

I started off at 6:00 am in drizzle. As I crawled my way up Margaret's Way Trail, my watch beeped at me. I rushed to put my reading glasses on (my sunglasses are being redone and besides, did I mention it was raining?) but by the time I got them on my face, the notification was gone. I held them in my hand waiting for the next one. Soon after, my watch vibrated. I noticed it gave a green loop arrow and an "On Course" message. I guessed correctly that beeping meant I was off-course and vibrating meant I was on. These messages continued as I ran up Margaret's Way. I continued on the Chybinski Trail with positive reinforcement from my watch, but when things got confusing, Garmin was silent. I wasn't sure which way to go, and my watch gave me no feedback.

I tried pausing the run, choosing "Resume Later," but that didn't allow me to see the map of the course. I exited the run so I could see the map. It showed the course and where I was, and I tried to zoom in but couldn't find the trail or my location once I did. Useless. I continued on, starting the watch again.

By the time I was climbing the Central Peak of Squak Mountain, I knew I was off course. This would not have been too big of a deal, except that I needed to be back at my car by 9:10 to get to a hair appointment in North Bend. I had all kinds of trouble, from going up to the peak when my watch told me I was off course many times and even when it showed me a map with an arrow I couldn't decipher what I was supposed to do, to running STEEPLY down Squak Mountain Road in hopes of finding a trail to the west, to getting forced into mud by a branch only to have my shoe stay behind as I ran. No kidding! It took me three tries to yank it out.

In the end, I wound up desperately following signs back to SR 900 which is where my car was (but there are two trailheads on SR 900 about a mile apart). Eventually, I ended up on Chybinski Loop (not that any signs told me so) from the opposite side and I headed back down Margaret's Way as fast as I could go. I got to my car by 9:13. I was about five minutes late to my hair appointment.

Back to the drawing board...or should I say Garmin Connect? I refined my route by adding course points just before trail junctions. I named the points with things like "LEFT W PEAK" for a left turn on the West Peak Trail. My watch is supposed to give me warnings of the points as I approach. This, of course, is dependent on the watch having good reception.

The Garmin Connect application is TERRIBLE. I had done about half of the course points, clicking "save point" as I went. I got booted out--zoomed out completely and having to click edit again--when I had done half the course points. Only then did I realize that none of my work, including fine-tuning the trail, had been saved. I had spent about an hour doing this so I was kinda upset. I started over and clicked "save changes" often, which resulted in a full zoom out and having to click edit again. If I didn't, it booted me out, but only after I made some more changes to the course. Otherwise, nothing happened at all. I had to make changes to get booted out and lose those changes. Super annoying! I learned to save changes after each course point, which took a long time because it would always boot me out shortly after and then take forever to reload the edit screen. Garmin, please improve! (Note: I was using a PC laptop when I made my courses. Today I tried it on a PC desktop computer and didn't have any problems. Hmm.)

Kinda small, but you can see my course points, the purple flags on the route.
I plan to make new routes for my eight-mile run on Wednesday and my 20 miler next weekend and use course points. The only way to view the map is to avoid starting my watch ("Do Course") at the beginning of the run. I can't see the map if I start my watch to follow the course. But if the navigation isn't working due to poor reception, then the course point warnings do me no good. It would be nice to somehow be able to see the map when needed when I am following a course. According to help on the Garmin Forum, I should be able to see it. I believe I tried what it says to do (use the up or down arrow and hold menu for three seconds). I will try again Wednesday on a shorter run. Since the weather is supposed to be nice both Wednesday and Saturday, I am hoping to "Do Course" to try the course point warnings to make my way correctly. We shall see.

If anyone knows how to use the Garmin Fenix 5X to navigate while running in the woods, please comment! I could really use some help.

Wednesday, April 18, 2018

Garmin Fenix 5X Update

In Colorado while out on a mountain bike ride, I found myself saying, "As much as I hate my watch, I really like it." In a previous post, I ranted about the distance measurement inaccuracy, the trouble with getting maps for it, and the difficulty getting a computer to recognize it, but in fairness, the Garmin Fenix 5X is growing on me.

For starters, I like that I can have different settings for what is showing on the watch face for different activities. For example, when I am trail running, I have it show the overall time in the center, the largest number. On the top and bottom in smaller print, I have it show my lap pace and my distance, respectively. When I am mountain biking, I have it on the default settings, so it show my time, distance, elevation, elevation gain, And I have a ton of other options, like run, cross country skiing, rowing (which for me is kayaking), hiking, swimming, and more. When I look at the other data after a run or ride, it tells me whether the workout was maintaining, improving, or overreaching my aerobic and anaerobic fitness. I found this particularly useful when running at elevation in Colorado Springs. My second run there on my second full day, I did six miles and 1000 feet of elevation gain, and it told me I was overreaching. That told me I made the right decision in deciding to wait until Tuesday to do my long run, and also to do it on a rail trail.

I also like that I can see my heart rate at anytime, and also my heart rate profile over the last four hours. It will also tell me my recovery heart rate if I forget to get out of the run or bike screen. Of course I can also see my max heart rate and average heart rate for any given workout, which, again, I found useful in Colorado Springs. It helped me gauge my effort versus my perceived effort.

Some of the data the watch gives in Garmin Express; my watch itself when I review an activity will tell me that 4.1 is "significantly improving" my anaerobic fitness, and that 5.0 is "overreaching" my aerobic fitness. That information told me that I was struggling with getting enough oxygen, that the difficulty I thought I was experiencing with running at elevation wasn't just in my head. 


I haven't tried following a track yet, but I have put maps on it and transferred waypoints to it. I did that for the New Santa Fe Trail, but I kind of forgot to use it. Mostly, I wasn't sure how to get to the maps on it during a workout, so that is something I will still have to figure out. I wish I could find an expert to show me how to use it the way I want to. If I can figure out how to use it properly, I think I will actually really like it!

Friday, March 9, 2018

Why You Shouldn't Buy a Garmin Fenix 5X

Number 1: Garmin makes an unreliable product, be it the watch, the software, or their website. When I first got the Fenix 5X, I couldn't get Garmin Express to recognize that it was connected to my Windows-based laptop. I tried the MacBook Pro, and it finally recognized it. The next time I connected it to my laptop, it recognized--horray--but then, when it began installing an update, it didn't. Back to the MacBook Pro, where it continually disconnected and reconnected itself over the course of a half an hour. Incidentally, my husband's Garmin watch had the opposite problem. The MacBook Pro wouldn't recognize it, but my PC laptop does.

And the website. Talk about going in circles. I needed to return the maps I bought of Washington and the PCT on an SD card (because they can't be used with the Fenix 5X; you have to buy the download version...but the owner's manual of the Fenix 5X takes you to a page where you can buy the SD cards), and every time I clicked on Returns, it told me I needed to contact support for a RMC (return merchandise code). When I clicked the link to contact support, it took me back to the page I was on previously...and around and around I went.

Number 2: The price. I found it on Amazon for $600. I wish I had found the Sunto Traverse, which is only $419 and gets great reviews. I am four days past the return date on Amazon for returning the Fenix. Who knows? The Fenix 5X got great reviews, too.

Number 3: Accuracy. So far, I've run 15 or so times with the watch, and only two of those times have I found the watch measuring accurately. I kept making excuses for it: it was raining and windy; it was snowing; I was in heavy tree cover. But if it doesn't work in those conditions, it will hardly be worth using in western Washington.

So now I am stuck trying to get the Garmin watch to behave and work properly.

Saturday, February 17, 2018

To GPS or not to GPS?

After getting feedback from my friend, and after discussing logistics with my husband, I decided that a new GPS would be a good idea. There are some areas where the right trail seems like the wrong one apparently. My friend recommended map and compass if not GPS. The only problem is that our GPS is really old...like 15 years old. While it does work, it is big and, more importantly, heavy. And that just won't work. Here I am going to crazy lengths and expense to have my pack weigh seven pounds without water and then I throw in a pound or more of GPS!

A little research drew me to a GPS watch: the Garmin Fenix 5X. It's a new breed of wearable GPS that comes with pre-loaded maps. Not only that, but I can get specific Pacific Crest Trail Maps (that's a tonge-twister!) for it. I read lots of reviews while my husband watched some reviews on YouTube and priced it out. While I really only need a watch that gives me distance, time, and mile pace, being able to wear a watch and have a GPS at the same time really appeals to me. The watch does far more than I need a running watch to do, but what the heck! I went head and ordered it on Sunday from Amazon, where it was $50 cheaper, and also got the running pod with it that will tell me vertical oscillation, ground contact time and other hyper-specific running form details. I also bought some little silicone plugs for the charging port so it doesn't get dust inside.

The watch arrived the next day! I have small wrists, and my left wrist is especially thin due to Kienbock's Disease. The watch is big, handsome, and heavy. Perhaps I'll build up my wrist just by wearing it! I was planning to wait a while before using it because I wanted to preserve the battery for a while. The batteries in watches (and cell phones, for that matter), seem to hold less of a charge after repeated use. Since I am going to need the battery to last for over 20 hours of use, I wanted to get the most out of it. Apparently, the watch will run over 12 hours with continual, full-on use, but it has an Ultratrac mode where you can program it to shut itself off and "fill in" the gaps for a set amount of time, thereby increasing the battery usage to 35 hours!

Another feature I like is live tracking. While I will have a Spot Messenger, and I will have the live track feature on for it as well, it's nice to have another mode of communicating. It will kill the battery to have the notification feature on, but it apparently will get text and email as well. It would be fun to check, but it's not much use if I can't message back. I'll have to play with that.

I think curiosity is going to get the better of me, so I'll likely be charging it up and using it this weekend. I'll provide more information on ease of use in my next post.

I am sure I will appreciate the large size of the face when I am trying to follow a GPS track on the PCT!

Fast forward: It's been two weeks since I purchased the watch, and I finally gave in and charged it earlier this week. I've run twice with it, once behind the high school and today in Grand Ridge. It was pretty inaccurate today, likely due to being its first time in Grand Ridge, the tremendous tree cover there, and some pretty terrible weather (cloud cover). That being said, I like the watch. I spent some time post-run configuring the watch the way I like it, showing lap average pace on top, time large and in the middle, and distance on the bottom. I turned off all the features I don't need (like being reminded to move, my number of steps, my VO2 max, and all sorts of other things). Then I customized my settings for specific activities. For trail running, I turned on both GPS and Glonass, but for running, I just have it on GPS. I like that I can set up each activity differently. Next, I'll have to learn to do some GPS tracks.

I've been trying to remember to wear my watch when I am not running to get used to the feel and weight of it. I'd love to get the fancy titanium band for wear with clothes for work and use the band it came with for workouts. But it's really expensive. It can wait.

~LTR

Training for a 75-mile Fastpack in Retrospect

I've had considerable time to process my training for and run on Section J of the PCT this past August. My return to a normal running sc...