andyakashrek

The co may own the property?

And I think I may be further north still.

Yep--tried it both ways. Unzip then move, and just move the original and it opened in the Garmin folder. I've requested a new file, so will see if maybe something went wrong with the first download. I think the problem may be that I'm using a Mac, and was using the wrong file. Just got the new download so will see how that goes. As Sussamb said, have you selected the map on the gpsr and secondly I see you are using an older model garmin, does it support maps and also what type and size, gb, sd card are you using?

Having turned waas off on my 550t the unit displays my position on the map much faster than if waas is enabled.Now I can park,boot the unit,put my boots on and it's ready to go. With waas on it takes @5 minutes to find my position. So,in Gloucestershire uk,it seems that,for me, waas off is the way to go.

That is kind of annoying. Some of NeonGeo's really cool features are only half finished, and the creator seems to have disappeared. I have tried Cachesense, but I can't seem to get the hang of it. Maybe I should give it another try... Cachesense is a very powerful app and does everything you need, but, it can be a bit of a learning curve. I use it on a Z10 and a legacy BlackBerry and they are laid out differently. Explore the menus and play about with the options at home and you'll soon be a cachesense pro. Downside of cachesense, very little help documentation.

What do you want to achieve? Hidden text? If you let us know someone could probably help.

I believe that wp1 is reserved by the garmin operating system, i did read why once but can't remember now. As for the other numbers you could use waypoint manager to find and then delete them if you wish. Edit Scrap the above, I just remembered it is 000 that's reserved. To delete waypoints there are three ways: Select a Waypoint and tap the edit button (pencil icon) will allow you to select Delete Waypoint Main Menu>Setup>Reset>Delete All Waypoints will delete all waypoints. Main Menu>Waypoint Manager>[search/select waypoint]>Delete Waypoint will allow you to delete individual waypoints..

What firmware version was it, I'm on 6.6.

Hi, this is a common issue, if you search the forums you will find the answer. Basically I think you are using IE as your browser and you will need to add Groundspeak to the compatibility list. It's all detailed elsewhere. Alternatively if you are a premium member, I haven't checked, simply drag and drop a PQ into the garmin / gpx folder, preferably on an sd card. Sorry can't be more specific at moment, no time. Good luck.

Sky really that colour,with the white fadeout? Looks like a brochure advertisement.

Photoshop

On my 550t, I would expect your 650 to be the same, I have to briefly press and release the Power button as you say. This brings up a slider to adjust the brightness. On my unit this is quite easy as it takes a long press to turn the unit off. Perhaps you are pressing the button for too long?

One of my trackables was picked up and the cacher logged they were taking it to the other side of the UK to place in a cache, which they named. This hasn't happened and I looked at his profile, never logged in to the site and seems to only cache in may,presumably on holiday. I have tried to contact him through his profile but am not hopeful of reaching him as he has never logged in and it may not be a primary email. Still it may turn up may 2015 when he next goes on holiday. There is a photo on his profile page and it shows someone of school age, which if it is him would explain the annual holiday. Mine is not the only trackable he is holding. Oh well, I'll just have to wait and see what happens.

In a word,no. Basic gpsr's like the yellow etrex will do the job but don't expect paperless performance. I use both, Z10 for caching on the fly with cachesense app and I have 2 garmin as well.

I believe that my two units have different chip sets, I wonder if the software in the OR is not as good as the hcx and that is why it takes so long to get started. I will have a look at what I can find out.

Went out last night and found a cache on top of a high hill with 360 degree view of sky no trees around. 550t did not get a single D in any satellite bar. All full and green highest number #33. Vista hcx mostly D's. When the OR does get waas lock it is taking 30 mins, more than 5 mins to show position on map page. That's why I'm setting it to normal gps only. Very poor for a high end unit.

Go here, http://garminoregon.wikispaces.com/ Click on get started, may be something else but there is a link, download wayne millers functional overview.

On my copies of cachesense, if I open the application, at the top right I can click the hammer and spanner icon to display a drop down menu, click cachesense shop and there is an option to purchase the licence. Yes it is a one off cost. This is on blackberry, I don't know how it works on android but it is probably similar, it would be helpful if we knew what platform you are using.

You are assuming that the op is using an android or iPhone. They may be on blackberry like me.

To get back to the OP's questions I would say YES I use waas on my vista hcx and NO I don't use waas on my Oregon 550t.

I was more interested in why the OR dropped the lower numbered satellites. Do they used different chip sets?

Ok, sat in garden this afternoon and placed both units on the deck and powered both on at the same time. The hcx got more bars full much quicker than the OR. After about 10 mins the hcx had D showing on most satellites. The OR took nearly 25 mins to reach D state. BUT, the hcx saw and locked onto more satellites. The OR seemed to have trouble finding and holding onto the lower number satellites but in the higher range was the same. It also found #37, which the hcx did not, but with no D, and strangely tried to connect with #49. When the OR found and locked onto #2,#10,#12 the indicated accuracy was nearly the same as the hcx, @11 ft, however when it dropped these 3 satellites indicated accuracy went out to @30 feet. The hcx did not drop any and remained steady. This drifting may go some way to explain the inaccuracies I experienced in the field in side by side tests. This dropping behaviour carried on for the 45 mins I observed the satellite map. The units were not touched or moved during the test. At any time the hcx showed more D's than the OR. Any thoughts?

I didn't check to see if waas lock had been achieved, I will place them both side by side in the garden this afternoon and see what happens and what satellites are being picked up. Went out last night and just used the 550t, waas disabled, and found the 4 caches I went for easily with the unit indicating where gz should be and in all 4 cases the cache was within a couple of feet of indicated position, even under heavy tree cover.

Another vote for cachesense. I use it on my Z10 and PlayBook, great for logging in the field.

If by "accuracy" you mean the "EPE" data it might be deceiving you. "EPE" readings don't really mean a thing and might be more true with WAAS enabled. WAAS/EGNOS measures atmospheric distortion and attempts to correct it. If you do see higher EPE numbers with WAAS enabled the EPE may in fact be more representative of the true expected error. With WAAS off the only statistics the GPS has to calculate EPE are satellite number and arraignment. You have to be careful using EPE as a true measurement of accuracy because it's all relative to available data and the algorithm Garmin decides to use (which may be different between units). In short, be very careful about making statements like "more accurate" when referencing the EPE numbers. Even if you're using anecdotal observations about being "closer to the cache" you have to be careful about drawing any kind of factual conclusions about accuracy. If WAAS /EGNOS provides the GPS unit with more information about the satellite signals it receives (and it does) then I will trust that more information is a good thing most if not all of the time. To me the additional information is worth the extra 0.5 ma the unit draws with it enabled. And hey, the HCX is such a dinosaur if they haven't gotten the firmware fixed by now they never will. Perhaps you misunderstood what I wrote. I loaded the same cache information on both units and went out to look for them, hcx in one hand 550t in the other, both waas enabled. The hcx consistently pointed to the cache hiding place and reported that there was only a few feet left to travel,compass page. Whilst stood in the same position the 550t would point in a different direction and often between 20 - 30 feet left to travel. This behaviour carried on for each cache i looked for. However with waas disabled on the 550t it behaved the same as the hcx with waas. That is it pointed to the same place and the same distance to travel. That is why I said the hcx with waas was 'more accurate ' than the 550t with waas. The hcx consistently put me nearer to the cache hiding place. With the 550t and waas I could have been looking more than 30 feet away and in a different direction, based on compass screen. As for firmware I was referring to the 550t firmware. I acquired the unit with v3.9, updated to present version 6.6 and found compass behaviour was erratic, sticky and sometimes froze. Did a bit of research and found that this was common with that version. Downgraded several versions to 5.50 and that sorted it. So it looks like garmin still have work to do with this unit whereas the hcx dinosaur seems to function properly.