Jump to content

New Garmin Oregon 600 Series


Atlas Cached
Followers 36

Recommended Posts

@Kolenka

Thanks and let me be more precise about points no. 2 and 3

 

I know manual of Oregon, but what about real test data?

So,

2. Does "off course" alarm works if navigating Trackback?

3. Do you have real field records to confirm "total ascents"and"total descents"?

 

2) I don't really know how well the marine alarms work, but since the code is built on top of the Montana's code, I'd expect similar behavior, possibly with fewer bugs. I don't go boating with the Oregon, and so I've never really used any of the marine features.

 

3) That's the only way I can confirm it. But because the trip data is never savable, it really can only be compared to the current track, which is what I did to answer your question.

I also commented that I assume you have the 600 configured to reset the trip data when you reset the track data. Because if you don't, they cannot be expected to match. One will have a different set of samples than the other, and will display different values. Especially when total ascent/descent are counters, and not an average.

 

But these are the screenshots I'm getting:

600_trip.jpg600_triptrack.jpg

 

Are they routable? The 24K maps are have pretty much the same roads and POIs as City Navigator. Is this now true for the 100K maps?

 

The 100k maps are still not routable. But they do derive the trail/road data the same way. The latest DVD even includes the Navteq symbol now according to Garmin's website.

 

Although I will say the Navteq map data is at least 1-2 years old. I'm seeing errors that have been corrected in Garmin's City Navigator maps for at least that long.

 

I'm not suggesting that anyone test this, but... Does anyone have info/speculation on the long-term scratch resistance of the 600 series screens? Yeah, yeah... put some protection on it, but given the obvious differences in materials used in various models, if these screens are iPhone5-like in hardness, let's say, it would be appreciated.

 

Some folks mentioned plastic in earlier posts, but capacitive touch screens all use glass to create the correct capacitive effect (using glass in place of ceramics). I can't really tell what exact type of glass it is just from handling it though. Is it one of Corning's impact-resistant glasses like Gorilla Glass? I hope so.

Edited by Kolenka
Link to comment

Hi, I have always used my phone GPS but my new phone screen is no good. I am now looking for a handheld GPS. Do you have to buy separate maps for different areas on top of the cost of the handheld. I have used my phone while caching in America, Iceland, UK and Tunisia and never have to pay for any upgrades on maps.

 

thanks

Link to comment

 

It looks like that might be changing with the v5 maps. Hard to tell exactly at this point, and I decided to skip on them. Does anyone have the v5 DVD?

 

I will say that the experience when you go over the limit is pretty unhelpful. It is easy to miss lack of coverage unless you inspect it personally at the appropriate zoom levels. Which is incredibly time consuming. So I could see how someone could get 6000 tiles loaded and not notice a coverage gap.

 

Well, hopefully it does change with those new V5 maps. When are those coming out? As for loading all 6000+ tiles on my (now returned) Montana, it will let you do it just fine. And, it wasn't that hard at all to see gaping holes in coverage because they still showed up at pretty decently zoomed out levels.

Link to comment

Well, hopefully it does change with those new V5 maps. When are those coming out? As for loading all 6000+ tiles on my (now returned) Montana, it will let you do it just fine. And, it wasn't that hard at all to see gaping holes in coverage because they still showed up at pretty decently zoomed out levels.

 

Garmin sneakily released them in January. It's hard to tell with online orders if you will get the V5 maps or not though unless they advertise it. Only seen one place other than Garmin advertise that they have the 2013 Topos. Methinks Garmin doesn't sell them very often.

Link to comment
2) I don't really know how well the marine alarms work, but since the code is built on top of the Montana's code, I'd expect similar behavior, possibly with fewer bugs. I don't go boating with the Oregon, and so I've never really used any of the marine features.

I do not go boating with my Garmin either!

Nevertheless I use Marine alarms in ordinary navigation - it warns me if I am off course and incidentally do not look at the screen (e.g. when my eTrex is in my pocket).

 

So, kindly ask you to try this "off course" marine alarm when navigating Trackback.

It does not work in etrex 30 at all... maybe will work in Oregon 6xx.

 

And, thanks for confirmation about altitudes! It seems that they use quite different alghoritm than in eTrex :). In eTrex 30 I always get completely different values of ascents/descents in comparison to Trip computer which makes me dissapointed :(

Edited by wmarek74
Link to comment

The new v5 of Topo 100k (that comes with the "t" models) has had it's road and trail system upgraded. It now has all of the roads and trails shown on the Topo 24k product from Garmin. The only difference appears to be the water features and topo lines. I might actually recommend the "t" models now based on this improvement. The roads used to be based on inaccurate tiger data and was a major drawback.

 

Are they routable? The 24K maps are have pretty much the same roads and POIs as City Navigator. Is this now true for the 100K maps?

 

No, v5 roads are not routable. The upgrade in road/trail data makes sense though, the old stuff was horrible. I'm going to assume the new Oregon "t" models will come with v5.

Link to comment

Below is some information I retrieved about Garmin's U.S. Topo 100k v.5 maps

 

-------------------------------

 

Garmin TOPO U.S. 100K v.5

 

Version: 5.00

Released: January 2013

Part Number: 010-D1309-00

Maps: 553, sub-files 2204

 

Outdoor enthusiasts: Garmin mapped every hill and valley for your next great adventure. Now with more detail than ever, this product covers the finer points of the outdoors with topographic maps comparable to 1:100,000 scale USGS maps. It also includes terrain contours, topo elevations, summits, parks, coastlines, rivers, lakes, geographical points and more.

 

Provides detailed digital topographic maps, comparable to 1:100,000 scale USGS maps.

 

Includes updated road content, by NAVTEQ (non-routable).

 

Contains detailed hydrographic features, including coastlines, lake/river shorelines, wetlands and perennial and seasonal streams.

 

Includes searchable points of interests, such as parks, campgrounds, scenic lookouts and picnic sites.

 

Provides elevation profile on compatible devices so you can estimate terrain difficulty.

 

Contains roads, trails and highways in metropolitan and rural areas so getting to your destination is easy by creating point-to-point routes on compatible devices.

 

Displays national, state and local parks, forests and wilderness areas.

 

Includes digital topographic maps for the entire U.S., including Alaska, Hawaii and Puerto Rico.

Link to comment

Below is some information I retrieved about Garmin's U.S. Topo 100k v.5 maps

 

-------------------------------

 

Garmin TOPO U.S. 100K v.5

 

 

Summary: Everything is the same except for the road data being updated to Navteq (City Navigator) non-routable data.

Link to comment

Apologies if it's in the thread but haven't seen it yet. Could those that bought the new 600 please comment on the screen brightness/technology compared to the Dakota and former Oregon. I have the Dakota and it is completely different than the Montana's screen. I believe the old Oregon is the same as the Dakota. Is this new Oregon more like the Montana. .. . The old Oregon . . . . .or somewhere in the middle? The screen is really the only thing that bothers me about my Dakota.

 

Thanks.

Link to comment

www.outdoorsmagic.com Just In - Garmin Oregon 600 GPS

 

Thanks. The one photo they have next to the old Oregon shows a definite difference in glare . . At least at that specific angle .but can only assume it's more readable generally. Still looks a little washed out and dim. They liked the screen but a little non specific in explanation.

 

Any other real users comments would be welcome. Thanks.

Link to comment

Apologies if it's in the thread but haven't seen it yet. Could those that bought the new 600 please comment on the screen brightness/technology compared to the Dakota and former Oregon. I have the Dakota and it is completely different than the Montana's screen. I believe the old Oregon is the same as the Dakota. Is this new Oregon more like the Montana. .. . The old Oregon . . . . .or somewhere in the middle? The screen is really the only thing that bothers me about my Dakota.

 

Thanks.

 

It's the nicest looking screen I've ever seen on a handheld GPSr. I was out last weekend in the early evening and didn't even have to use the backlight. I think one thing that really helps it is the lack of that extra layer that the resistive touch screens have.

Link to comment

 

It's the nicest looking screen I've ever seen on a handheld GPSr. I was out last weekend in the early evening and didn't even have to use the backlight. I think one thing that really helps it is the lack of that extra layer that the resistive touch screens have.

 

Wow. That's quite an endorsement!

Link to comment

 

It's the nicest looking screen I've ever seen on a handheld GPSr. I was out last weekend in the early evening and didn't even have to use the backlight. I think one thing that really helps it is the lack of that extra layer that the resistive touch screens have.

 

Wow. That's quite an endorsement!

 

Yeah, having had the opportunity to use a Dakota in the past, I can say that there is no contest between it and the Oregon 600.

Link to comment

Kolenka,

 

Did Ya noticed that difference between Maximum Elevation (602ft) and Minimum Elevation (107ft) is much more than sums of Ascents and Descents???

It seems that now both records are buggy(!)

 

Be careful not to confuse Trip Data and Track Data (screenshot on the left is Trip Data, right is Tracklog Data). The min/max elevations are recorded in the Trip Data. The Tracklog can be a subset of the Trip Data and does not necessarily reflect the Trip Data. Kolenka could have started/stopped the tracklog at any time during his trip. The data records are not buggy. I've been testing that very thing out over and over again and they are usually within feet of another.

 

It helps to understand the difference and relationships between Trip Data and Tracklog data before calling them buggy. Kolenka could have turned his GPS on at his house(107ft), drove to the trailhead (250ft), cleared his tracklog and began tracking at 250ft then hiking to 600ft and back down to the trailhead where he saved the tracklog. Making his screenshot calculations just about perfect.

Edited by yogazoo
Link to comment

Below is some information I retrieved about Garmin's U.S. Topo 100k v.5 maps

 

-------------------------------

 

Garmin TOPO U.S. 100K v.5

 

Version: 5.00

Released: January 2013

Part Number: 010-D1309-00

Maps: 553, sub-files 2204

 

Outdoor enthusiasts: Garmin mapped every hill and valley for your next great adventure. Now with more detail than ever, this product covers the finer points of the outdoors with topographic maps comparable to 1:100,000 scale USGS maps. It also includes terrain contours, topo elevations, summits, parks, coastlines, rivers, lakes, geographical points and more.

 

Provides detailed digital topographic maps, comparable to 1:100,000 scale USGS maps.

 

Includes updated road content, by NAVTEQ (non-routable).

 

Contains detailed hydrographic features, including coastlines, lake/river shorelines, wetlands and perennial and seasonal streams.

 

Includes searchable points of interests, such as parks, campgrounds, scenic lookouts and picnic sites.

 

Provides elevation profile on compatible devices so you can estimate terrain difficulty.

 

Contains roads, trails and highways in metropolitan and rural areas so getting to your destination is easy by creating point-to-point routes on compatible devices.

 

Displays national, state and local parks, forests and wilderness areas.

 

Includes digital topographic maps for the entire U.S., including Alaska, Hawaii and Puerto Rico.

 

This is new and interesting. The DVD version requirements state:

 

This product may be unlocked and used on 1 compatible device (to unlock, simply follow the instructions on the certificate that comes in the packaging). If you want to use this same map on subsequent devices, you must purchase a new map for each device.

Link to comment

Yogazoo,

Notice that Trip odometer 5.38 miles is equal to Track distance (also 5.38 miles).

Also: Moving Avg (Speed) both in Trip computer and Track record is equal to 5 miles/h.

So,Your explanation is incorrect.

I predict altitude measurements as huge bug of this very first release of FW Oregon 6xx :-(

Edited by wmarek74
Link to comment

No, v5 roads are not routable. The upgrade in road/trail data makes sense though, the old stuff was horrible. I'm going to assume the new Oregon "t" models will come with v5.

 

Someone in-thread already confirmed the 600t does come with the v5 maps (v5.01 specifically). I saw a 600t in the local REI when I was there looking at something else, and also can confirm they come with the v5 100k maps. The missing hydrology data was killer though. I played a bit with the hike area I went to on Saturday and suddenly noticed that a major creek (complete with waterfall) was totally missing from the 100k data. It was probably the most obvious water feature on the entire trip.

 

Summary: Everything is the same except for the road data being updated to Navteq (City Navigator) non-routable data.

 

That's what it is looking like.

 

Apologies if it's in the thread but haven't seen it yet. Could those that bought the new 600 please comment on the screen brightness/technology compared to the Dakota and former Oregon. I have the Dakota and it is completely different than the Montana's screen. I believe the old Oregon is the same as the Dakota. Is this new Oregon more like the Montana. .. . The old Oregon . . . . .or somewhere in the middle? The screen is really the only thing that bothers me about my Dakota.

 

Thanks.

 

The screen is glass, and has clarity closer to something like the eTrex. I haven't used a Montana in the field, but it is an obvious leap over the Oregon 450 in clarity in the sunlight. I went for a hike on Saturday where it was raining, and we were in the forest, so daylight wasn't that great. I left the backlight off and never actually had to turn it on. This is with shading turned on (so the background was dark green). I was very pleased with the results of the screen, as being able to leave the backlight off in the field is a great way to draw out the battery life.

 

Yogazoo,

Notice that Trip odometer 5.38 miles is equal to Track distance (also 5.38 miles).

Also: Moving Avg (Speed) both in Trip computer and Track record is equal to 5 miles/h.

So,Your explanation is incorrect.

I predict altitude measurements as huge bug of this very first release of FW Oregon 6xx :-(

 

I'll also point out that GPS altitude measurements, and measurements from an incorrectly calibrated barometer are going to do weird things. When your GPS accuracy is in the 10-15m range, your elevation measurements will jump around as well. If this affected the ascent/descent measurements, those two measurements would be worthless. I'd suspect that Garmin is using some sort of rejection filter on the track data for calculating ascent and descent. And that rejection filter is not being used when determining the minimum and maximum. Or even use the map's DEM data when available. In fact, I'd practically bet money on it, since that track in no way was near 600ft or 100ft, but it was indoors at times where my GPS error is high enough to account for that minimum and maximum.

 

This particular track is mostly me messing around with the device over 2-3 days, and a short trip on a bike. So about half the points are from indoors and basically worthless junk data due to the error involved. The goal was to demonstrate (quickly) that it does actually show the same information for the trip and track data.

 

I have an actual hike track which has much more sensible max/min values, and ascent/descent values that are much more in line with the topographic data for the area.

 

I'll take a look at the track data and see if I can confirm my suspicions, but my indoor reception can be terrible on the bottom floor where my PC is. I've seen accuracy in the 300-400ft range often enough that I'd be very surprised if junk data wasn't the reason for the discrepancy... and in this case, having ascent/descent data that is much smaller is the correct result. This isn't real data, folks. Be careful not to jump to conclusions based on a screenshot from a single track without knowing the context in which it was captured.

Edited by Kolenka
Link to comment

What the heck is going on now ?

 

Q2eE6k1.png

 

So does that mean people who pre-ordered will get it within 2-5 days or are they completely sold out and no one is getting anything

 

Usually helps to know which site this is from, but I'm under the impression that supplies are very limited. Some REI stores which had them are clean out by now.

Link to comment

Kolenka,

I'd just like to know if one can trust Trip computer and Track altitudes.

As for now: no confirmation, just very vague records.

Surprisingly, also track records seems to base partly on alghoritm used in Trip computer (most probably pure air pressure based figures) if regards ascents and descents.

Link to comment

Kolenka,

I'd just like to know if one can trust Trip computer and Track altitudes.

As for now: no confirmation, just very vague records.

Surprisingly, also track records seems to base partly on alghoritm used in Trip computer (most probably pure air pressure based figures) if regards ascents and descents.

 

My GPS track from Saturday is within 10m of the 24k topo map DEM along the whole route (with the same delta consistently throughout the track as well). So it isn't perfect, but it's actually pretty good. I haven't even tried to calibrate the altimeter in this thing with truly accurate data, just whatever auto-calibrate it might have. That track is not the one I took a screengrab of, as it was already saved and cleared out of the current track.

 

The algorithms have been merged, that's obvious, but keep in mind that ascent/descent refer to a delta in your elevation between two points along a path. If two points aren't connected, can you really determine if an ascent or descent actually took place? This particular track has a lot of gaps it in from being turned off repeatedly since Saturday, so there are a lot of disconnected segments that make up a single track/trip there.

 

EDIT: I gotta ask, what criteria do you have for being able to trust the data vs not? The very nature of GPS means it is an estimate, at best, so I'm curious how you define "accurate enough" to be trustworthy?

Edited by Kolenka
Link to comment

This is new and interesting. The DVD version requirements state:

 

This product may be unlocked and used on 1 compatible device (to unlock, simply follow the instructions on the certificate that comes in the packaging). If you want to use this same map on subsequent devices, you must purchase a new map for each device.

 

Which is weird, since the 600t's data seemed to be at least a couple years out of date for the roads, and unroutable. Yet, the 24k DVDs which are routable are okay?

 

I'm confused.

Link to comment

Kolenka, can you compare track properties (ascents and descents) in Oregon and in BaseCamp?

 

Now that I've had time to do some actual comparisons with my track from Saturday...

 

Device:

  • Min: 236 ft
  • Max: 502 ft
  • Ascent: 551 ft
  • Descent: 545 ft

 

Basecamp Windows:

  • Min: 236 ft
  • Max: 502 ft
  • Ascent: 551 ft
  • Descent: 545 ft

 

Basecamp Mac:

  • Min: Not Reported
  • Max: Not Reported
  • Ascent: 551 ft
  • Descent: 545 ft

 

It does look like it is consistent across the board. And I suspect the trip computer is using a track internally now.

 

As for that weird result, there's definitely some interesting filtering rejection happening. Of the current track, there are 5 distinct segments. The first segment is where most of the ascent/descent comes from. It ranges from 107ft to 340ft. Suddenly the last two samples in the track jump up to 602 ft that you see as the maximum. Other segments have very little ascent/descent, but are all over the place in terms of altitude (due to GPS error and being indoors). There's definitely some data filtering going on as Basecamp is even reducing/minimizing the effect of these last two points of the first segment.

Edited by Kolenka
Link to comment

I'm having an issue adding maps to my 600. I'm adding sections of several maps-National Parks 24k; state topos from GPS File Depot; and the older 100k Garmin topos.

 

Using Basecamp, it pulls up a list of maps that I can add to my 600, and the 100k topos are on that list. I go through the selection process to add the maps, and it give a list of maps to be added, which includes all of the maps I've selected including the 100k topos. Basecamp then goes through the motions of adding the maps to my 600. After, when I open my 600, all of the maps show up except the 100k topo maps. I have plenty of space on my card, and according to Basecamp, these maps are compatible with my device.

 

Any ideas??

Edited by BHP1
Link to comment

I am just surprised that trip computer in Oregon perfectly matches the track record. Does it depend somehow on track record interval?

 

I think they will match if you set the interval to once per second.

 

The track interval on my 600 is Auto/Normal. I'll try other values and see if it still matches.

Link to comment

I'm having an issue adding maps to my 600. I'm adding sections of several maps-National Parks 24k; state topos from GPS File Depot; and the older 100k Garmin topos.

 

Using Basecamp, it pulls up a list of maps that I can add to my 600, and the US topos are on that list. I go through the selection process to add the maps, and it give a list of maps to be added, which includes all of the maps I've selected including the US topos. Basecamp then goes through the motions of adding the maps to my 600. After, when I open my 600, all of the maps show up except the US topo maps. I have plenty of space on my card, and according to Basecamp, these maps are compatible with my device.

 

Any ideas??

 

How many different maps are you installing? Any that spill over into two .img files? It seems that there is a limit of 8-9 different map files that the 600 will load. And it doesn't "merge" maps that are split across two imgs like the 450 does on the current firmware.

Link to comment

Kolenka, can you provide some basic information for a complete newbie on what recommended options to configure on the 600? This is my first handheld GPS. I don't even know how to do something basic like record a track/trip or whether I should reset trip data when I start a new track.

 

I noticed by default the screen turns off after a short while, to save battery. But then I'm not sure if it is still recording track/trip data or if the unit itself turned off. I have to press the power button to turn it back on. So I turned off battery saving, which then just turns off the back light but leaves the screen on. I guess my question is if I want to capture track data, what is the best way to do it so the screen is "locked" but it is still capturing data? Ideally I want to start recording a track and then put the unit in my pocket without worrying about things changing because the screen gets touched.

Link to comment

Kolenka, can you provide some basic information for a complete newbie on what recommended options to configure on the 600? This is my first handheld GPS. I don't even know how to do something basic like record a track/trip or whether I should reset trip data when I start a new track.

 

I noticed by default the screen turns off after a short while, to save battery. But then I'm not sure if it is still recording track/trip data or if the unit itself turned off. I have to press the power button to turn it back on. So I turned off battery saving, which then just turns off the back light but leaves the screen on. I guess my question is if I want to capture track data, what is the best way to do it so the screen is "locked" but it is still capturing data? Ideally I want to start recording a track and then put the unit in my pocket without worrying about things changing because the screen gets touched.

 

Garmin's manuals say that it will record when using battery saver, and the screen turns off. Both the screen and GPS chip itself are noticeable drains on the battery, but it can't really turn off the GPS chip without making the device a lot more frustrating to use.

 

The thing that is confusing about these devices at first is that there are multiple ways to accomplish the same basic result, so which way you go is really up to you:

- You can use the 'lock screen' feature: press the power button and press the small lock button at the bottom. This means you can put it wherever and still whip it out for reference.

- Use the power save feature. It will still record, and while the screen is off, it won't accept touch input.

 

As for how to handle track/trip resetting, also up to you. I don't like the trip/track data being separate (and I like a "simpler" experience overall where there is less for me to keep track of), so I have my device set so that it resets the trip computer when I reset the current track. Some people don't like that behavior, and will disable that. No real problem with either one, just go with what works best for you.

Link to comment

I'm having an issue adding maps to my 600. I'm adding sections of several maps-National Parks 24k; state topos from GPS File Depot; and the older 100k Garmin topos.

 

Using Basecamp, it pulls up a list of maps that I can add to my 600, and the US topos are on that list. I go through the selection process to add the maps, and it give a list of maps to be added, which includes all of the maps I've selected including the US topos. Basecamp then goes through the motions of adding the maps to my 600. After, when I open my 600, all of the maps show up except the US topo maps. I have plenty of space on my card, and according to Basecamp, these maps are compatible with my device.

 

Any ideas??

 

How many different maps are you installing? Any that spill over into two .img files? It seems that there is a limit of 8-9 different map files that the 600 will load. And it doesn't "merge" maps that are split across two imgs like the 450 does on the current firmware.

 

I have a total of 8 .img files. I didn't see anything about a map limit in the manual or in a google search. So, I experimented by removing one map and trying to add some 100k topo sections. Still no go. I now have 7 .img files on my device. The 100k US topos simply aren't being loaded even though Basecamp says they are compatible, and they show up in the list of maps that is being installed.

 

The only reason for this issue that I can think of is that Garmin has somehow locked out installing these maps on the 600. I'm wondering if I can create a GPS img file in Mapsource and then copy that to the 600.

 

EDIT: I created an .img file in Mapsource, loaded on an SD card, then copied that file to my 600. The maps work fine, so I'm not sure what the issue is with Basecamp.

Edited by BHP1
Link to comment

I have a total of 8 .img files. I didn't see anything about a map limit in the manual or in a google search. So, I experimented by removing one map and trying to add some 100k topo sections. Still no go. I now have 7 .img files on my device. The 100k US topos simply aren't being loaded even though Basecamp says they are compatible, and they show up in the list of maps that is being installed.

 

I only discovered there was a limit by trying to install the maps and going into the map selection screen, and noticing that only some of the maps were selectable. As I removed maps, the missing ones started to appear in the list so I could enable/disable them. Very weird behavior.

 

The only reason for this issue that I can think of is that Garmin has somehow locked out installing these maps on the 600. I'm wondering if I can create a GPS img file in Mapsource and then copy that to the 600.

 

I'd be surprised if they did. Really the only way to confirm that is to load an SD card with just those img files from the 100k topo and see if they load. Even then, it could be a bug with Map Installer.

Link to comment

I have a total of 8 .img files. I didn't see anything about a map limit in the manual or in a google search. So, I experimented by removing one map and trying to add some 100k topo sections. Still no go. I now have 7 .img files on my device. The 100k US topos simply aren't being loaded even though Basecamp says they are compatible, and they show up in the list of maps that is being installed.

 

I only discovered there was a limit by trying to install the maps and going into the map selection screen, and noticing that only some of the maps were selectable. As I removed maps, the missing ones started to appear in the list so I could enable/disable them. Very weird behavior.

 

The only reason for this issue that I can think of is that Garmin has somehow locked out installing these maps on the 600. I'm wondering if I can create a GPS img file in Mapsource and then copy that to the 600.

 

I'd be surprised if they did. Really the only way to confirm that is to load an SD card with just those img files from the 100k topo and see if they load. Even then, it could be a bug with Map Installer.

 

I did load an SD with a Mapsource .img file and copied that over to my 600 and it opens with no issues.

 

I'm only loading sections, not whole maps, so I've not seen any of my map selections greyed out. I only total 466mb with the maps I've loaded. I guess it's an issue with the map loader and the older 100k maps.

Link to comment

I'm only loading sections, not whole maps, so I've not seen any of my map selections greyed out. I only total 466mb with the maps I've loaded. I guess it's an issue with the map loader and the older 100k maps.

 

Entirely possible.

 

In my case, it wasn't that map sections were grayed out, the map imgs themselves weren't even being loaded. It was as if they weren't on the SD card at all.

Link to comment

good news for people who ordered from LL Bean, here a transcript of my chat with their customer service today:

 

Me: I have a question about my order #xxxx It is now showing "backorder filling". Does that mean it's being shipped? thanks

Diane: Good afternoon.

Me: hello

Diane: That means we just received the Garmin and are still to process the item so we can send it out to you.

Me: any idea how long that usually takes?

Diane: A normal order shipping to Colorado would take 5-6 business days.

Me: so 5-6 days after it's shipped or that's how long it takes to process ?

Diane: From today. So you should have it next week.

Me: ok, thank you !

Diane: Is there anything else I can help you with?

Me: that's it

Diane: Thank you for contacting L.L.Bean. I am pleased that I was able to help you. Have a wonderful afternoon.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Followers 36
×
×
  • Create New...