Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by _Art_

  1. It was to better describe a reply to this: "It's not desirable because it doesn't make it any more ACCURATE." When it actually does: https://www8.garmin.com/manuals/webhelp/gpsmap66s_st/EN-US/GUID-DC65C2FC-0EA3-4182-9B6D-8DB8E4125B56.html Maybe for a Geocaching profile. and I guess for GC coord entry it shouldn’t be there, but for other uses, it’s desirable. If the 62 does waypoint averaging, it might not show the entire float, but it would still exist in memory. You could possibly see the entire precision value printed once the data is exported and viewed somewhere else.
  2. Sampling the same position multiple instances over a duration, and calculating the mean of all samples does make the position more accurate. I haven’t used it, but that would be what the GPSMAP 66 Waypoint Averaging feature does. A UBlox timing GPS module can be prompted to enter a self survey mode that takes a day or two to find a very accurate position, which can then be entered into a field that gives it’s PPS output higher accuracy, to make a real time clock more accurate.
  3. But they kinda have, because Waypoint Averaging is a thing, and it was a thing long before Garmin decided it was a thing. You could take samples from multiple devices at different times to create a better map or track.
  4. I guess for geocache, the whole idea is not giving a precise location because you’re supposed to find it yourself. For any other purpose a GPS or mapping has, I don’t see why more precision would be undesirable.
  5. Well still, Is there a difference if you just omit the last places by typing nothing? What they will have done is always used 32 bit floats which can have 7 decimal places precision, and just printed the rest of the value that always existed in memory anyway. 40.4819050°, -078.5484983° You could have a coordinate pair to enter (geocache or not) with 32 bit precision.
  6. It’s the same format with an extra digit of precision. They probably did it as the receivers have become more accurate.
  7. Every Garmin handheld doesn’t necessarily work fine when it was sent It would be a little more confusing for the seller of an older unit that was once a daily user. I do feel sorry for those who make a career out of becoming a licensed distributor for the stuff though.
  8. It will be interesting that all over the world, some people are going to sell some GPS hardware on eBay that worked fine when it was sent, and has an issue straight away when it arrives at the buyer’s address.
  9. Off. When I’m walking with lock to road off, the street are still in the right place.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. 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.
  15. 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.
  16. 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.
  17. 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:
  18. 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
  19. 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.
  20. 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.
  21. 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.
  22. 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.
  23. 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
  24. 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.
  25. _Art_

    Chirp Qs

    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.
  • Create New...