The Hungry Caterpillars

I have spoken to Memory map about this. I am personally pretty unhappy with it. I am also given to understand that it may well become even more "arkward" to register at some time in the future. Perhaps time to look elsewhere?

With the Memory map "upgrade" comes both a change in the licensing conditions and also the way in which you register it. In my experience with Memory map transferring data can actually alter the coordinates from the ones shown by Memory map and the ones then shown by your Garmin gps i.e SX64320 54380 as shown on Memory map can perhaps be translated on the Garmin as say SX64326 54385.

I have had a number of Garmin gps devices starting with the small yellow e trex . I however am not at all taken with the Colorado for many reasons. I much prefer the 60csx. Good idea badly executed-so far. A visit to the main site and check the fora there for more information. I do feel that Garmin are using its customers as beta testers perhaps more so than on any model preceding it. I would advise do your homework and use caution before splashing the cash.

hiho9 I ave found about 150 since then but no longer log them as not interested as I used to be. For instance today found three the last one being GC16GWS whilst counting skylarks and hoping to see some Twyte I have other hobbies including photography and natural history which is helped by my ability to record various species etc. i of course find the ability to record where I have seen various species of both flora and fauna very handy. You may also note that I also letterbox and in the last few years have found a few thousand some with a sighting compass map and local knowledge but also some large number with a gps the last a few weeks ago. Have you anytjing to add hiho9?

Actually derry I think unless you have a satellite fix the alarm may well not go off at the right time. It will actually calculate from the last satellite fix!!

I have found personally that a hard reset does not cure this problem. Neither does the beta update. They are most definitely aware because I informed them of this problem personally. I also informed them personally of the stopwatch mode problem as well. Before I put up their replies on the first issue I will ring them tomorrow to make sure I did not "mishear "there answer about the clock turning off. Much to my amazement they did say about the stopwatch losing time that they had not heard of this before. This is Garmin Support Europe so am uncertain if they are kept fully up to date on this or not.

Hi John also agree. Have used this perhaps ten times? However am unaware of any other soft reset method than the one you describe. Hi Blorenges I may well have the wrong end of the stick here. However my 60CSX seems to maintain the proper time regardless of having a satellite lock or not. At the moment my 60CSX has no satellite lock but is giving the correct time. However MY 300 does not. It actually gives the last time it was switched off until it finally gets a satellite lock when it then suddenly jumps to the right time! This prompted me to look closely at the stopwatch mode when I discovered this was off by about 24s/hr! And that is whilst I have satellite lock. in fact if you watch the stopwatch you can actually see it hang and gain. As many of the features on the 300 are dependent in one way or another to function correctly on the correct time you realise that other reported problems could be related to this. From earlier posts on this thread I am still uncertain just who else has actually checked properly for themselves on this.

You could be right. I do feel after fighting with my 300 that the chipset used is the real problem and is such that firmware and software fixes cannot really "fix" it.I would love to be wrong. I would not be interested in a new Colorado with the same chipset that is being used at the moment. I believe a number of the problems seen in others with same chipset as this? One thing I have noted is that the stopwatch mode is continually fast (9mins/day)and it actually hangs at some points. I wonder if this can be seen in all models that have this chipset? I am also very glad I hung on to my 60csx. Like Celtic Cacher I am hanging on waiting fot the "magic bullet" but am beginning to wonder after all this time that there may not be one?

Well as an apparent beta tester for the current unit I would consider it a nice gesture for Garmin when using the data produced to bring out a better model that actually works with a lot less problems they donate one to me. I wonder just which chipset they will use?

Stop putting words in my mouth. I am not as you put it "anti CO". Instead of trying to obfuscate perhaps we could return to the problems that you claim were sorted by the beta update. I gather you both now have 300s that both keep the correct time when switched off and then switched back on? And that neither of you have the stopwatch mode gaining time?

"Although I did notice when the gps had been turned off the time stopped and did not correct until it was put on again and it picked up a satellite - this has now been corrected by the beta update." Your post I believe? I am not posting about other units just the 300. As I have had little in the way of problems with other units including the 60CSX (60CS?) I have not had much reason to.

derrylynne I AM using the beta update. My clock still stops and my stopclock still loses about 9m/day. I am glad this beta update has sorted these problems for you and Chris. And this post from a person who sems to know more than most about the Colorado below is why- "I believe that the issue with timers running fast is the result of a firmware workaround for one of these hardware problems. Everyone who is running 2.51 seems to be seeing problem. I'm guessing if you stepped back to older firmware this problem would go away. My suspicion is that they are trying to work around a hardware issue by running the internal clocks faster than they are supposed to. GO$Rs I am unaware of any official admission that "the early software left much to be desired" Yes it most definitely did and that is why I felt like a beta tester for this unit and in fact still do. Perhaps you could point me in the right direction on this? As for Garmin Support as I have had made little use of their services whilst using six of their units over the last seven years I can only judge as I now find them . I have most definitely been in touch some number of times and found the support "bland" and generally uninformative. As for your last comments I can see it being very good but it isnt yet. As I posted the first time I ever mentioned this unit try before you buyor even better go out caching with somebody who has one.

Hi derrylynne, I am on the beta update. The clock still does not work whilst it is switched off. The stopwatch also still gains about 9 mins/day. I am glad that the beta update works well for you and Chris. This post below will explain why. This poster sems to know more than anybody else on the fora about the Colorados. "I believe that the issue with timers running fast is the result of a firmware workaround for one of these hardware problems. Everyone who is running 2.51 seems to be seeing problem. I'm guessing if you stepped back to older firmware this problem would go away. My suspicion is that they are trying to work around a hardware issue by running the internal clocks faster than they are supposed to. GO$Rs" I am unaware of anybody officially acknowledging that "the early software left much to be desired"? Perhaps you can point me in the right direction? Seeing that I bought mine some time ago you agree that I was although actually being used as beta tester because thats what I felt like and still do. I most definitely have been in touch with Garmin some number of times and have found them "bland" but definitely not very informative. As I have not often in the past seven years whilst using six other garmin units found much reason to use their services I have personally nothing else to judge them on. As for your last statement I will wait and see. I

What a laugh a minute you are. I am aware that I was probably one of the first people in the country to buy this particular model. If you look back through the threads you will see I mentioned this some little time ago and suggested that people wait or at least test before buying. Just what problem do have with that? There are most definitely "quirks" as mentioned by others. I brought up the mention of the clock a an easily checked problem that anybody could do as they obviously have. Now I like you have spent £300 on something that does not work as advertised. I am less than impressed. It is not my fault that derrylynne did not notice my earlier post on this and am less than impressed by jokes and idiocies about stopwatches. I was asking for genuine helpful advice after offering it myself about this particular model. And I would still offer the same advice, try before you buy or as Matrix has done talk to somebody who is honest in their appraisal of it. And by the way regardless of some persons comments my stopwatch is STILL about 9 mins/day fast and no the clock STILL does not work whilst the instrument is off.

Not so. I buy things for what they advertise they do. I do not buy a radio that claims to recieve fm mw and lw to find it only recieves fm. I also bought mine for those reasons you mention so smart alek answers dont cut it with me. I mentioned the time as a problem because other features of the 300 are inextricably intertwined with it. I posted in the hope of more informed opinion than you seem capable of giving.

Interesting about the crashes. I have had a number of these and am not certain but think it may be down to a sequence of actions. I am still trying to pin this down as we post!

I am no employee of anybodies. I have had the following and fully used them! first yellow etrex, First Vista, 60cs, 60csx and 305. I have had little if any problems with these. I have persisted with ONE 300 and am still having problems!! I have made a number of calls to Garmin support to no real avail. Now just tell me how we dedcide whether or not you are a Garmin employee?

Page 23 I believe. "STOPWATCH. The Clorado includes a stopwatch with a laptimer. The stopwatch can record the laptime based on distance or on a button press." Now instead of having a go at me perhaps you should be asking Garmin some very pointed questions!! As I will be doing in the very near future.

Pardon me but I have never read so much tripe in my life . I suggest you go and read the the manual and check just what it claims for the stopwatch mode. If you are willing to pay the best part of £300 for a GPS that does not live up to the claims it makes then thats your problem not mine.

I have put a number of posts up about satmap on this forum. To reiterate; Waterproof, will NOT run Memorymap. The maps which come on SD cards are about the same price as memorymap but can be transferred from one satmap to another. Battery life short. Think waterproof. Cannot load such programmes as cachemate. Only give British grid to eight places not ten. I spoke at some length to the person behind this and felt it could become the ideal geocaching device at least in the UK. Alas not to be. Beware rant coming on!! I am fed up to the back teeth of the people who are fully aware of what is required to make an ideal hand held GPS but apparently are so short of vision come up with something far short of what todays technology makes possible. They then charge a massive amount of money for something that may half do it. I can buy a laptop for £300 pounds for goodness sake but not a well thought out intuitive fairly bug free handheld GPS! at that price. And that includes EVERY manufacturer going. Added to that is the incomprehensibly high cost of OS mapping in this country. Ordnance Survey along with 50 years worth of rights was sold into private ownership for a song. And we dont half pay a price for that! To put it even more bluntly our pastime opens us up to be ripped off time after time.

"Those of us 60CSx owners that purchased theirs when first released remember going through the same growing pains. " No I dont remember their being this many problems with the 60csx at all. I most definitely did not feel like a beta tester for the 60csx.For the 300 I most definitley do.

Well all very nice. Apparently the clock shouldnt stop on the 300 when it is turned off! And after using it for 3 months it most definitely is not faultless!! If it is so faultless I take it that you will not be loading any firmware upgrades? How faultless is it when you are urged by Garmin Support to upload a beta firmware upgrade "at your own risk"? Mine has now taken upon itself to turn itself off for no apparent reason. Waterproof? Are you sure? Before this model I have had an old e trex yellow, a vista, a 60cx and a 60csx and have had little problems with any of these!!! The 300 is most definitely a different kettle of fish altogether!!

Unfortunately not so in my case!! I will be contacting them in a couple of days time with some very pointed questions!!!

Agree totally. I have a 300 which I am now about to return. I have returned to using my 60csx and pda rather than continue fighting with what I have finally discovered is a defective unit. And this is thanks to this forum not Garmin support!! I very fortunately hung on to my 60CSX. I would most certainly suggest you do the same.

I would seriously suggest you should at least try one first before buying. At the moment I have returned to my 60csx and pda. Hopefully at some time in the future the 300s will be sorted. I do not think they are at the moment. What amazes me is that Garmin support seem to be unaware of problems that are common in this particular model. I am unsure just how many people are using them extensively as I have done so am unaware if anybody but me has come across problems.