_Art_

Off. When I’m walking with lock to road off, the street are still in the right place.

What a mess! https://imgur.com/a/T2qfOvw I also noticed the backlight on one of the times I got it out, so maybe the buttons being easier to push wasn’t a great idea. I wonder if it has anything to do with shorter battery life some people are getting. I’d need to turn backlight off or lock the keys.

Without any battery backup or memory retention at all, it should still take only a few minutes in good conditions to get a position fix. It’s a problem.

I’m very sure that the GPSMAP 66 firmware began as the most recent Oregon 7xx build at the time. Much more than just sharing some functions. The 66 firmware 2.50 is still named "Oregon7xx". The logo splash screen is still named “Oregon7xx Splash Screen”. 66 firmware 2.50 contains all of the on-screen button graphics which are only of any use for displaying on the Oregon's touch screen, The 66 contains the Oregon full screen background image only ever displayed on an Oregon, and very large chunks of both firmware files are still exactly identical, even though both units have received individual updates since the 66 came out. It does make sense to begin with software for similar hardware, and go from there with new features, but baffles me a how a new model can have so many bugs seemingly unrelated to new features for a new model. For hardware with identical processors, RAM, and displays, it shouldn’t be very difficult.

That’s a strange way to describe the issue. It’s never trying to orient the map screen to face the destination. That only incidentally happens if you are walking toward it. The actual compass screen can do that. I’m wondering what happens if you spin it about on a desk slowly like that, even if you are shaky.

It’s not the tremor by the way. Didn’t think to try it before, but you could have a full on fit much worse than you’re doing and it’s fine. Anyone with a 64 can try it.

True North is an option in the Satellite page, but I don’t know how a 64 could get that information dynamically. It’s maybe just a constant that is updated with firmware.

GPS drift is the reason Garmin are quoted to have given in the thread linked by the OP, and what I think most likely. I’m not so sure it was understood in that conversation though.

That’s not a compass, that’s Jim, and if the map is in track up mode, it’s suppose to point where Jim is facing, yes. That may not be the cache.. Only if you are actually facing the cache. If the map is in north up mode, it should always be oriented so the map is north at the top of the screen, but Jim can still change direction on the map. I have doubt the compass you had as a young boy would work well in a car. Have you tried at home? It sounds like you doubt this works:

A charge controller (for example Maxim DS2715) should be thinking about all of that so you have to be thinking about none of it (for any decent charger). https://www.maximintegrated.com/en/products/power/battery-management/DS2715.html

It would be interesting if someone owns this and an Oregon 7xx as well to see of any of Oregon’s bugs are in this too. It happens the startup Garmin logo screen (which I’ve also found) is named “Oregon 7xx Splash Screen”, and the entire firmware chunk of the GCD file is named “Oregon 7xx” as well. Not really confirmation they started with Oregon firmware, but may have. I’ll bet that background is in that model Oregon as well, and not displayed, just like GPSMAP66. I decided to buy another 66 soon.

In the Transformers movie, a 60csx is used as a GPS, but it’s sideways in(it’s non existant) landscape mode, with a futuristic display.

Not exactly how it’s done, but in a nutshell, yes: https://imgur.com/a/ocmyPt1 I didn’t want to go OT too much in this thread, but committed to another one for Oregons as well (all three fw versions). That’s not how I left the 64st by the way, just something ridiculous for a demo.

If Oregon, Colorado, GPSMAP 66 & whatever else are all 240x400 I will switcheroo any or all of them, and that can be Oregon Whiz. and I don’t have to store imagery if the user provides the fw files lol.

There are similar landscape photos in stock images of Montera, Montana, and Oregon, all demonstrating the camera, but I can’t find that one. It does interest me, because they should be able to reuse the same programming guts in every GPSr. Evidence that they don’t would be interesting. That bug in address search they acknowledged in the 2.50 change log is confusing to me. Garmin GPS have done address search with a UI for almost 20 years. Anyways, I like the pebbles in the Oregon, and water droplets in the Colorado both better than this

It’s in firmware versions 2.10 and 2.50 for GPSMAP 66. For version 2.50 it begins at offset 0xB5E73A, and is spread over about four data blocks. It’s the only full screen image other than the test pattern that appears in the test screen.

The dsPic I used to read SPI from the chirp does have two hardware SPI modules built in! It could have just as easily been jus the chirp and one micro, but had it gone further, that might have been a hinderance. THere’s just no SPI mode for (spying on comms). The RF transceiver SPI is duplex, and the whole thing really needs two hardware SPI modules to work properly. Any Arduino / Pi stuff I’ll never use. Arduino especially I’m not for it.

Well for some useless trivia: Unless this is from another GPSr source, from which they recycled the firmware for the GPSMAP 66, I guess this was going to be the background wallpaper until somebody changed their mind https://imgur.com/a/WlmNaVu

Hi, I never followed up, and can just show the last of three videos I made about it: https://www.youtube.com/watch?v=Dz6-qLMY_aE&t=1s That’s at least as far as I’d take it without knowing something specific about it’s encryption technique. I ended up only wrecking one of two chirp units, so guess I could place one. Is a “beacon only” geocache a thing?

I went over and was there for the update. It crashed starting up straight after, but was ok starting up after that. Not much time to test a lot other than I was most interested in, but the problem exiting the Recording Controls menu (back to map screen) appears to be fixed. It still crashes browsing the map at low zoom level. Anything from 8km to 20km if Birdseye imagery is enabled. Birdseye imagery is no longer displayed if you zoom out further than 20km printed on the scale. Where the ordinary Garmin Topo map could crash it before, it appears to only happen for Birdseye imagery now. I think it would be fixed for now if they simply disabled Birdseye imagery for any view above the 5km zoom level. This is the downloaded highest quality sat imagery. For HEMA raster map which is also just a bunch of jnx files that cover all of Australia, that is displayed up to 12km zoom level, and doesn’t seem to crash it at all. Maybe it’s just that it’s the high quality imagery that it can’t handle it. The same imagery is used with my 64st and never has a problem, so I’m only comparing to that.

Literally the day after I sold mine! lol. Still keen to see how it goes for people. I’ll probably buy another if I think it will stay powered to maintain a track log. Luckily it’s sold to a friend, so I’ll be able to have a good look at it, and he might even give it to me to do the update.

I sold mine at a $50 loss, rather than any hassle in taking back for refund after 3 months now. Actually I included the Garmin battery pack so it did cost me a bit more. Now I do like the hardware, and will probably buy another one later if I know a lot of things are fixed, but 3 months where I wouldn’t want to use it is too much.

Does that mean the internal charge controller is working properly now, or you didn’t try?

Here’s one of them: https://www.sendspace.com/file/dbzq77

Whoops, may have found another one. I made two custom maps lat night that both worked for the 64st, and both crashed the 66st any time they would be displayed. Both were single 1024x1024 JPEG images. So has anyone tried any custom maps?