This is a quick post on my experiences with a Garmin Oregon 600 on a recent bicycle tour along the Munda Biddi Trail through the South-west of Western Australia, and the response from Mr Rob Grinter of Highly Tuned Athletes who until now I had never hesitated in recommending and was happy to have brought two Garmin GPS units from and a GoPro Hero 3 camera from. Regretfully I can no longer recommend dealing with Highly Tuned Athletes and personally will not buy from them again.
Garmin Oregon 600 and OpenCycleMap
According to Mr Rob Grinter most if not all the problems I had with my Garmin Oregon 600 recently occurred because I was using the OpenStreetMap OpenCycleMap. The problems listed below include problems which cause the unit to shut down. How the maps cause this is beyond me or for that matter any of these issues but there you go.
A lot of what I have experienced has been reported by others as well. For example at Geocaching.com forums there are two extensive threads on Garmin Oregon 6XX problems [see here and here] and if you visit Garmin’s own forums you get posts from people experiencing some of the same issues I have. The best place I have howerever for listing and reporting problems with the Garmin Oregon series of GPS units is the Garmin Oregon 6xx Wiki. That is a beauty! I guess all these people are using OpenStreetMap too :).
Mr Grinter referred to a OpenStreetMap’s disclaimer as his basis for describing me as being irresponsible for using it [when I was riding the Munda Biddi Trail] which I initially assumed was this one at their Wiki as justification for his position. Of course I am well aware are of the limitations of OpenStreetMap and in fact contribute to the mapping program. I also use on rides such as the one that I completed where I had all these problems the appropriate paper maps. However, it is a very long stretch of the imagination to try and attribute the problems with my Garmin Oregon 600 to OpenStreetMap. I am curious to read Garmin’s City Navigator or Topo maps disclaimer to see if it is different from the OpenStreetMap’s disclaimer so if you can post the details that would be appreciated.
You may find that weather conditions, construction projects, closures, or other events may cause road conditions or directions to differ from the map results. You should exercise judgment in your use of this Content. (b) Certain Content is provided under license from third parties, including but not limited to TomTom Global Content BV (“TomTom“), and is subject to copyright and other intellectual property rights owned by or licensed to TomTom and/or such third parties. You may be held liable for any unauthorized copying or disclosure of this Content. Your use of TomTom Content, including but not limited to printing or use in marketing or promotional materials, is subject to additional restrictions located in the Legal Notices page.
Update: Mr Grinter has now provided further information on this aspect. To quote his email:
Fault found was due to Experimental maps being inserted by Customer which the producer of said maps specifies that they are known to have bugs/issues and are under development, specifically in the area of your complaint. Free map provider clearly specifies that the maps should be used at own risk and should not be relied upon. http://www.openfietsmap.nl/
and in a further email
In relation to reading your list of errors, in fact your statement could not be further from the truth [I commented that I felt they had not considered them at all given their blaming me for my use of OpenStreetMap]. One of my senior technicians has spent 16 hours on your device testing the unit, putting it through some of the most througher testing known. Also, no less than 3 staff have read your letter front to back, several times, including 2 meetings to discuss its severity. This to you may seem like special treatment, however it is in fact normal around here. In a sentence, your letter, its contents and each and every fault, was taken with the utmost seriousness and well beyond.
and then this comment …
The initial fault is not a major fault, it is probably not even a minor fault based on the abnormal manner in which it has been used, hence If you wish to play out this transaction and complaint via Consumer Victoria, then you are welcome do so.
So there you go. OpenStreetMap are responsible for tracking issues, GPS drift issues, the Oregon 600 shutting down randomly, not synchronizing with the GSC-10 etc. Damn pesky maps! Unfortunately Mr Grinter seems to have a problem understanding the disclaimer or is deliberately misrepresenting it and in particular the difference between routing and tracking. The disclaimer is of course an appropriate one if you are using the maps for routing purposes, however they have no bearing on tracking other than giving you a visual of where you have been. If there is no road or track on the maps then of course these will not show and the tracking line will show as going as simply a line; exactly what happens when using Garmin’s own maps where it does not have tracks or roads included. To seriously try to blame the maps and use this disclaimer as justification for the issues that I experienced is very disappointing or a case of simply being ill-informed. Either way it was not a nice way for Mr Grinter to respond.
To describe the maps as “experimental” however simply shows a lack of understanding of what they are. For a retailer in this space Mr Grinter’s knowledge is seriously lacking and is a discredit to the hundreds if not thousands of community members who contribute to the maps. A simple read of the OpenStreetMap Foundation wiki should have addressed his lack of understanding.
For the record I download my OpenCycleMap from Free maps for Garmin brand GPS device (“producer” refereed to by Mr Grinter). DCRainmaker (well known Garmin tester and blogger) has an excellent post on using these maps with Garmin Edge units if you are interested. Check out Ray’s blog anyway. It is an excellent read!
Garmin Oregon 600 Problems
I made an error of judgement and just prior to leaving on my ride of the Munda Biddi Trail in July 2013 I updated my Garmin Oregon 600 to the latest firmware at the time and didn’t have a serious chance to test all went well. The first problem I noticed was that I lost my Geocaching profile, which whilst it didn’t stop the unit functioning was annoying for me as it meant I couldn’t easily display the information I wanted given my intended use of the unit. I now believe that the firmware upgrade probably contributed to a number of the issues I experienced as when I returned from the ride I did install the firmware file provided by Peter at Highly Tuned Athletes (I didn’t have a computer with me on the ride to do the re-install prior to my return) and that restored at least my missing profile. In hindsight that was probably an error of judgement on my part as I then sent my Oregon 600 off to Highly Tuned Athletes for warranty analysis. They in turn determined there was nothing wrong with the unit and the story begins. I now wonder whether the replacing of the firmware contributed to that outcome, which in itself is a good one, but lead ultimately to a serious breakdown in the customer-retailer relationship.
That said this is what I experienced on the trail with my Oregon 600.
Here is one of tracks recorded on my Garmin Oregon 600 on my ride of the Munda Biddi Trail. This is typical of what I experienced every day of the tour. It is uploaded at Garmin Connect which allows users to select and use, you guessed it, OpenStreetMap, those same evil maps that apparently “caused” all 13 problems I experienced.
This day’s riding according to the Munda Biddi Trail map was 53 kilometres. Apparently I actually rode 83.75 kilometres and reached speeds of 151.9 km/h on my loaded touring bike.
For those interested each day’s ride log, the map distance and what my Garmin Oregon 600 recorded are listed below. I did some pretty amazing speeds apparently and rode some pretty interesting “tracks” and roads. You can see in the last few days of riding where I learnt to turn the Oregon 600 off every time I stopped. This helped to reduce the error levels over the days ride.
|Day's Ride||Map Distance||Garmin Distance||Error|
|Albany to Denmark||74.85||103.93||29.08|
|Denmark to Jinung Beigabup Campsite||41.58||55.85||14.27|
|Jinung Beigabup Campsite to Booner Mundak Campsite||73.75||58.53||-15.22|
|Booner Mundak Campsite to Walpole||52.36||83.75||31.39|
|Walpole to Kwokralup Beela Campsite||30.54||36.07||5.53|
|Kwokralup Beela to Yirra Karra Campsite||49.53||56.95||7.42|
|Yirra Karra Campsite to Northcliffe||49.8||94||44.2|
|Northcliffe to Pemberton ?||44.45||65.66||21.21|
|Pemberton to Manjimup ?||83.28||77.06||-6.22|
|Manjimup to Karta Burnu Campsite||23.22||30.01||6.79|
|Karta Burnu Campsite to Donnelly Mill||23.5||36.34||12.84|
|Donnelly Mill to Nannup||37.3||31.29||-6.01|
|Nannup to Jarrahwood||26.71||27.88||1.17|
|Jarrahwood to Donnybrook||44.61||47.52||2.91|
If you have any suggestions as to how the maps caused these issues I would love to know or possible fixes of the problems I experienced please do let me know below.
The following list of my problems is taken from my letter to Mr Grinter. It is interesting to compare my list to that provided at Garmin Oregon 6xx Wiki bug list page. There are a few similar ones for sure.
- My Garmin Oregon 600 not synchronise with either of my Garmin GSC-10 sensors despite both advertising material and the manual indicating otherwise. Those same GSC-10 sensors synchronise with Garmin Edge 810 and previously with my Garmin Edge 800 so I know the issue is not with the sensor. Interesting the Oregon 600 will synchronise with my Adidas HRM strap. I consider this critical failure as it was one the features I lead to my purchase of the unit. Any replacement or repair must have this functionality working correctly please or there is little point in replacing or repairing the unit.
- The Oregon 600 has been inconsistent with its auto-pause function. Sometimes it will auto-pause sometimes it will not. The amount of tree coverage appears to have no influence on this. I have found that on more than one day, a day of riding could be recorded with approximately 60% being added to the day’s distance when compared to the map. I didn’t deviate from my planned route at all and hence this sort of error level is extremely concerning, more so if one is navigating and using distances as a critical navigation tool. I found the only solution to this was to physically turn off the unit whenever I stopped.
- In contrast to the issues raised in dot point 2, I found I could be riding along when the Oregon 600 would simply go into auto-pause mode. This was a known fault in early firmware updates of the Garmin Edge 800 and which was fixed so it is staggering to see it happening again now with a much more modern unit in the Garmin range.
- I found the Oregon 600 showings speeds up to 30 to 40 km/h when I am doing 10 km/h or less and again in situations where often there was little to no tree coverage. On one day it recorded a maximum speed of 90 km/h! I was riding a loaded mountain bike on dirt trails where my average speed would have been around 10 km/h over the day.
- The Garmin Oregon 600 route tracking gets confused following a turn in the road or trail and often then heads off showing me going well off-track and adding considerable distances to the day’s ride distance.
- On more than one occasion it would simply just recorded me heading off into the wilds for no apparent reason;
- My Oregon 600 regularly looses satellites even in clear tree coverage (e.g., riding in farming country). When this occurs I have to use the auto locate satellites feature to re-locate the satellites. When I do this the Oregon 600 finds the satellites within seconds. On some days this was happening up to 15 times over a six to eight hour ride. In my view this is a very serious concern as surly a company such as Garmin Limited with a history of GPS development should have such a fundamental functionality working correctly.
- If I switch to external power source (e.g., USB battery supply) it causes the Oregon 600’s screen to change to a different display and at times simply changes the chosen the profile! It simply seems to have a mind of its own.
- I found that a set of Duracell Ultra alkaline batteries I tried (fresh purchase) lasted no more eight hours which is well short of the claimed battery life. I was getting similar battery life times from a rechargeable batteries as well;
- My Oregon 600 will at least once a day randomly turn off;
- My Oregon 600 will lock up requiring the removal of the batteries to force it to restart again seemly on a random basis;
- Tones continue to sound even though they have been turned off in the settings
- Updating to firmware 2.8 resulted in the lost of the geocaching profile as per our email discussions.
I also notified Dr Min Kao, Executive Chairman of Garmin Ltd of my concerns including the non-reposone of Garmin support when contacted BEFORE going back to Highly Tuned Athletes. Of course I have not received a response from Dr Kao but did get an email from a Amador Leal, Tier 2 Support at Garmin Australasia on August 13, 2013 asking for the best time to phone me on August 14, 2014. I replied on August 13, 2013 with a suitable time to call on the morning of August 14, 2013 and of course Amador Leal didn’t phone.
I guess it is really too much to expect to actually receive customer service from Garmin Australasia. So much for Garmin Ltd’s value statements:
The foundation of our culture is honesty, integrity, and respect for associates, customers, and business partners. Each associate is fully committed to serving customers and fellow associates through outstanding performance and accomplishing what we say we will do.
Garmin Oregon 600 Fit for Purpose?
Australian consumer law is meant to protect consumers who purchase goods in Australia. Of course to get any protection the consumer has to jump through the hoops which can include having to go, in this instance I believe to the Victorian Civil and Administrative Tribunal (VCAT) for a remedy. That is the final solution, the first step is to raise the concerns with the retailer, Highly Tuned Athletes. Regretfully their response is that it is my fault for using OpenStreetMap and that there is nothing wrong (which may in part be because I re-installed the firmware). I guess those track logs that I recorded are fictitious and I made up all the faults. Oh I even sent screen grabs of what I believe Mr Grinter refers to as my “minor issue” [post about this initial problem at Garmin forums] from my unit to Highly Tuned Athletes so I guess they are made up as well. The next stop open to me is either seeking a charge back via my credit card provider (online purchase) and/or seeking the involvement of Consumer Affairs Victoria. I have decided to see what happens when I get my Oregon 600 back from Highly Tuned Athletes and see how it performs in the bush over the next month or so before deciding how to go forward on this, if at all. Whilst Amador Leal of Garmin Australasia did eventually contact me and offered a new replacement unit that offer has now been withdrawn as I sought a refund from Highly Tuned Athletes which was in rejected anyway.
I have been told that my Garmin Oregon 600 is being returned from Highly Tuned Athletes after a “hard rest”. I was not exactly sure what a hard reset entails as it is not documented in the manual or the Garmin knowledge base but there is a mention of two master resets in the Garmin knowledge base which I assume is what is being referred to. The latest one is what I assume is the hard reset. Interesting this was added (or modified) to the Garmin Knowledge base on July 30, 2013 which was after I sent in my Oregon 600 to Highly Tuned Athletes. The earlier on appears to be a soft rest but is also referred to as a master reset.
I did try a soft rest early in the piece with my problems but that didn’t do anything. I was not aware at the time of the hard reset option; it does seem to have even been in the Garmin Knowledge base.
In closing I am putting this out there as it stands; I will move on with my Garmin Oregon 600 and see what happens. If this post is of benefit, great, if not so be it. I don’t know if I will buy Garmin again but I know I will never deal with Highly Tuned Athletes again.
I also acknowledge that having been told I was irresponsible by Mr Grinter on a phone call and being left without doubt that I was to put it colloquially “full of bullshit” I did get angry with Mr Grinter and one of his staff coped a short spray from me. I did not however swear or scream at Mr Grinter or his staff as claimed and I have never stated that he said I was liarer, implied it yes, stated it no. I have apologised to Mr Grinter’s and his staff for my outburst. Mr Grinter however has not apologise for calling me irresponsible or implying I am a liaring about my issues, neither has Mr Grinter apologised for raising his voice at me on the phone (I was stupid and reacted to this). I acknowledge my stupidity and accept the negative outcome from it.
Have fun out there.