TransFXB

Thanks guys. I will go for an Oregon 450.

Hello, I would like to replace my (broken) Vista Hcx but I am confused by new Garmin range. What to choose in new Dakota and Oregon range to have something equivalent in features to Vista Hcx? I think Oregon 450 should do it (I don't need a camera, nor communication with other devives). Thanks in advance.

no more feedback about "drift" issue with 2.80/2.80 combination???

No drift experienced with 2.80/2.80 combination. Only 3m to 8m position difference (with a 3m to 7m indicated accuracy).

Yes, I have already reported here that when a "horizontal" drift happens, a vertical one (altitude) is there also.

Corey, this situation is so touchy that any advice could result in a ... dead unit. Difficult to help you without being exposed to a bad result. I would suggest anyway that you interrupt the process by, first trying to cancel it from your computer, second, by unpluging USB cable. And of course, try to upload firmware once again. Good luck...

I believe they have totally privileged battery saving, and btw don't want to give customers these options.

Same post as here: http://forums.Groundspeak.com/GC/index.php?showtopic=204671

it's for nüvi 2xx units.

very likely for some nüvi units. But not for eTrex.

Yes. I think jmundinger was referring to some discussions/rumors saying that eTrex Vista HCx chipset could have been changed to something else recently. So, his question is interesting by itself.

Here is (yet another!) example of what I call a drift recorded with eTrex Vista Hcx (2.60/2.60). On the first picture, you can see a shift of 69m (230ft) between the two traces on the same path (return trip). The drift, based on previous posts, is almost of the same magnitude: 50 to 70m (200 to 230ft). The lower track is correctly on the actual path, but the upper one is drifted-up. I will now test 2.70/2.60 AFTER a hard-reset... Note: for those who are curious and/or interested, these snapshots are from a guest Windows XP running in a virtual machine (VirtualBox) installed on a host Linux OS (Ubuntu). This is only way for me to run Mapsource as I have a desktop running Linux. What is interesting is that the altitude profile is also messed up (see below) by almost the same value (50m of 200ft).

Yes. And by the way, it is unlikely that a software update fixes the issue (for instance 2.60 -> 2.70, currently). Only a firmware (chipset micro-software) is likely to fix it (currently 2.60).

EFIALTIS, I experienced drift issue in totally clear sky (I mean, not under tree cover)BUT, always close (10 to 100m) to a reflective (?) body (building, cliff, and so on).

ok thanks FiveNines, that makes it! Motorcycle_mama, I am sorry but I don't think the links you provided could be consider as a proof. Unless I am wrong, forums (I know quite well GpsPassion and contribute rather frequently) are only reporting what they have heard, but no direct proof. Again, unless I am wrong, Garmin official website doesn't indicate which chipset is used. From my standpoint, rgn file information are relevant.

w/o being picky, could you provide a direct proof that Vista Hcx contains a MTK 3318 chipset?

I believe so...

this subject has been and is being extensively addressed. Please, be curious and just scroll down a bit in this forum...

Good point! I have also experienced this. Just plot trace in Mapsource AND have a look at corresponding altitude record in trace properties. When a drift occurs, altitude is messed-up too... In a way, this is coherent.

Possibly a Mediatek hardware with a Garmin made firmware (Bravo 2)?

Some thoughts.... Please keep in mind that a an eTrex Hcx unit has to versions. For instance, very last ones for eTrex Vista Hcx are 2.70/2.60 This is what you can see by going Main Menu/Settings/System and pressing lower lest button and then Software Version. The you have: 1) Software version (2.70 for instance) 2) GPS software version (2.60 for instance) Conclusion there is that we have two different things: 1) a software that handles GUI, plotting, odometer calculations, and so on, which is in this example at version 2.70 2) a software (firmware) that handles GPS chipset it self, which in this example at version 2.60 In the following, I ONLY refer to GPS software version, which is GPS chipset related (AKA firmware). Googling a bit Today, I found this: Google "type B gps" -> http://www8.garmin.com/support/download_details.jsp?id=3621 - version 2.30 Google "type M gps" -> http://www8.garmin.com/support/download_details.jsp?id=3733 - version 2.60 Google "type M2 gps" -> http://www8.garmin.com/support/download_details.jsp?id=3735 - version 2.60 Google "type G gps" -> no direction to Garmin Website, but to a resellor indicating that GPSMAP 60Cx, 60Cs and 76Csx are concerned By deduction (hmmm...), we probably can guess the following: eTrex Vista Hcx is probably not a type B (last shown version on Garmin is 2.30 and we know that last eTrex Hcx firmware version is 2.60) eTrex Vista Hcx is probably not type G which seems to concern GPSMAP60 series. eTrex Vista Hcx is most likely type M or M2 (2.60 versions proposed at garmin pages (above links) corresponds to what we actually have in our eTrex Vista Hcx Now, we can guess what is behind B, M, M2 and G letters: - M and M2 are likely to design Mediatek (MTK) chipsets - G is likely to design Sirf chipsets - B could design Bravo chipsets (and/or a specific Garmin software layer between GPS chipset and GUI). Being there, we can understand why GPSMAP60 serie (type G) is not experiencing drift issue, if we suppose that this drift issue is only to Mediatek (M and M2 types). This is also the case of old eTrex units (Legend, Vista, ...) which don't have a Mediatek chipset. Any other unit (other than eTrex) having a drift issue is likely to also have a Type M or M2 GPS chipset. I am not knowledgeable enough about Garmin product range, but does anybody know if it is the case? My conclusion so far, is that last software version (2.70) won't solve drift issue as it is only an evolution of the GUI, odometer calculation (and so on). From my prospective, only an update of firmware (from 2.60 to ???) could solve this issue. What do you think??? (Sorry for this very long post, but I wanted to give as much background as possible).

I have a Vista HcX, upgraded Yesterday to 2.70/2.60. Diagnostic screen says Bravo 2 Not checked yet what is (or no longer) on the splash screen (like above). I have experienced many times drift issue with 2.60/2.60 Drift issue not tested yet with 2.70/2.60 My conclusion so far is that having "bravo" in the diag screen is not a warranty to not have drift issue with 2.60/2.60

just paste this address in your news reader (RSS) software: http://www8.garmin.com/rss/software.jsp

still showing Feb 4, 2007 for Vista HCx but Feb 4, 2008 for Legend HCx

freeday, indeed your answer was accurate. I was confused because I have both units...