GPSrChive Discussion Forum

Nail wrote: Tue Apr 04, 2023 8:36 am

Gadwin wrote: Tue Apr 04, 2023 8:25 am But that is not interesting and garmin explicit advertise, that their Multi-band devices can handle even in difficult environment. It is natural to expect, that a device which has also Multi-GNSS and Multi-Band and even one stallite system more on board, that it should at least perform the same like its previous model.

In good conditions, the 67 is better than the 66sr.
See this test. The black circles are places where I was 100% following the same line.

Spoiler

67vs66sr8.jpg

By the way, because Bug 11 is quite annoying. Did you check, that "Lock on road" is on "No" on your GPSMAP 67?

Yes, I was on foot when I produced that GPS track and it looks like my route. Today, I had better performance of 6 - 7 feet during my daily walk. Accuracy is better when multi-band is enabled with GNSS.

Gadwin wrote: Tue Apr 04, 2023 4:06 pm

Nail wrote: Tue Apr 04, 2023 8:36 am

Gadwin wrote: Tue Apr 04, 2023 8:25 am But that is not interesting and garmin explicit advertise, that their Multi-band devices can handle even in difficult environment. It is natural to expect, that a device which has also Multi-GNSS and Multi-Band and even one stallite system more on board, that it should at least perform the same like its previous model.

In good conditions, the 67 is better than the 66sr.
See this test. The black circles are places where I was 100% following the same line.

Spoiler

67vs66sr8.jpg

By the way, because Bug 11 is quite annoying. Did you check, that "Lock on road" is on "No" on your GPSMAP 67?

A question: how to read your image, there is no link and it does not display.

neilwoody wrote: Tue Apr 04, 2023 9:41 pm Yes, I was on foot when I produced that GPS track and it looks like my route.

Can you add large close-ups like the yellow border?
The trail floats strongly in the green elpis, did you walk like that or did you walk along the edge of the road? I think it's on the edge of the road, but I could be wrong.
In general, this is an acknowledgment that you have walked this path.

Spoiler

67vs66sr16.jpg

I did walk along the left shoulder of the road. A few times, I walked closer to the center of the highway or to the right shoulder to avoid muddy areas. I show my GPSMAP 67 track on Google Earth.

Spoiler

GPSMAP67test.jpg

Today I made a definitive decision to return the GPSMAP 67 to the seller. It's been a few days since I got it, I haven't experienced such anomalies with the GPSMAP 66sr in a year. I don't know when the issues will be fixed or if they will fix it at all. Yesterday's event had an impact on my final decision. I went to town in the evening to pick up my daughter. I took the GPSMAP 67 with me and recorded the route. The whole route looks ok. I reached the agreed point, parked on the street, did not get out of the car. I recorded the course, did not turn off the 67, after 9 minutes I started the record and went to the next intersection, I took my daughter. We drove home, the whole route is ok. The whole problem appeared in the parking place. On the record, it looks like I entered the building on the other side and drove through it and drove on. The recording was set to a 2s interval, you can see that within 2 seconds I jumped across a wide street and found myself in a building (13m), which is not possible. The building where I parked had four floors, the one on the other side of a similar height. The red line marked the actual route, parking and stop.

Spoiler

67vs66sr17.jpg

Cloudless sky.

I also did yesterday some hikes in a familiar place and unfortunately the track was also quite often off. Especially when it lost the signal for some minutes. I never experienced less than 1.8m how some here reported and that was really a second. I am not confindent, that garmin will fix it, because of Bug 9. Less acuuracy = less need of zoom. It seems to be all intended...

Gadwin wrote: Thu Apr 06, 2023 6:04 am Less acuuracy = less need of zoom. It seems to be all intended...

I thought so too. Amazingly, the track quality in 66sr can be checked on the device. You need a computer screen for the GPSMAP 67.

According to

Spoiler

https://www.avnet.com/wps/wcm/connect/o ... ID=nxvsTVu

, seems AG3335M much more support for L5. I do only wonder, as AG3335MN is marked for indian market, why Garmin choosed that one.

Afaik only the sapphire model of the Fenix 7 supports multi-band, the other models only support multi-GNSS. So in that way the use of the AG3335MN makes sense.

Does anyone know what chipset the 66sr uses? Might be interesting to know in light of the discussions on the accuracy in another topic.