confirmed vista HCX speed filter problem

[jmundinger]

There seems to be a new Version called GPS Chipset Type M software version 2.30 as of August 28, 2007

or what could it be?

 

That appears to be the latest version of webupdater.

[freeday]

There seems to be a new Version called GPS Chipset Type M software version 2.30 as of August 28, 2007

or what could it be?

 

That appears to be the latest version of webupdater.

Does it mean, your webupdater installs GPS Chipset v 2.30 ??

[knowschad]

Is web updater required to determine the current version I have installed, or is it also displayed somewhere in the unit itself? I can't seem to find it there.

press

menu-menu-setup-system-menu-software version

on your unit without using any computer

 

Thanks! Got it.

[jmundinger]

Does it mean, your webupdater installs GPS Chipset v 2.30 ??

 

I have no idea. I followed that link. And, from that link you can get to an explanation regarding WebUpdater. But, at that link, I couldn't see how to download anything except by running WebUpdater. Except to follow the link from this board, I couldn't figure out how to navigate to that page within Garmin's system - so, except for the connection to WebUpdater, I have no idea what that update is about.

 

Regardless, if you have WebUpdater installed on your computer, that is the easiest way to update the Vista HCx. And, if you have version 2.30 installed (the August 3, 2007 update) and run WebUpdater, you will get the message that there are not updates for the unit.

[+hogrod]

If you have WebUpdater installed on your computer, that is the easiest way to update the Vista HCx. And, if you have version 2.30 installed (the August 3, 2007 update) and run WebUpdater, you will get the message that there are not updates for the unit.

 

when updating my 60cx you have to run webupdater twice to get the chipset update. first time it checks for the unit software, then webupdater will ask you to check for additional software, this is when it will update the chipset.

[Smac999]

If you have WebUpdater installed on your computer, that is the easiest way to update the Vista HCx. And, if you have version 2.30 installed (the August 3, 2007 update) and run WebUpdater, you will get the message that there are not updates for the unit.

 

when updating my 60cx you have to run webupdater twice to get the chipset update. first time it checks for the unit software, then webupdater will ask you to check for additional software, this is when it will update the chipset.

 

2.3 has the compass nag and is worse then the software it comes with. don't upgrade untill they fix the speed problem. hopefully they will get rid of the compass nag with it.

[deltaf508]

Well I'm a little disappointed...Here's the response I got from them. I don't consider this a satisfactory answer, especially if the older models register just fine.

 

 

Thank you for contacting Garmin International,

 

In order to register speed on a gps unit, you normally have to be moving a 2.2 mph.

 

With Best Regards,

 

XXXX (Name removed to protect his job - If I were garmin, I wouldn't be training my staff to answer like that!)

Product Support Specialist

2nd Shift Marine Team

Garmin International

www.garmin.com

 

Here's my original message (which I thought was very straightforward and honest!

 

Garmin Support,

 

I have purchased the Vista HCx last month and am seeing the low speeds not register on my unit as everyone else is. Anything below 2.0 mph and the GPS does not register as moving. As my very first GPS I am very concerned that this will be taken care of. Also, as a handheld unit for hiking and for biking it seems that this would be a major flaw in the functionality of how this unit operates. Is there a firmware fix that would address this issue? It seems there are a number of customers on the internet that are seeing this issue and are worried about a fix as well. Thank you for your time and consideration.

 

http://forums.Groundspeak.com/GC/index.php...9653&hl=hcx

http://forums.Groundspeak.com/GC/index.php?showtopic=173468

http://forums.Groundspeak.com/GC/index.php...=173260&hl=

 

Take Care,

[freeday]

...

In order to register speed on a gps unit, you normally have to be moving a 2.2 mph.

...

 

And why does garmin implement a pedestrian-mode.

 

Oh, it is only for pedestrians that move with more then 2.2 mph.

 

Edited September 22, 2007 by freeday

[fujitsu]

Hi,

 

to me this is value of 2.2 mph is to high for a pedestrian use. I sincerely hope that garmin could improve this.

 

regards

[+allory]

2.3 has the compass nag and is worse then the software it comes with. don't upgrade untill they fix the speed problem. hopefully they will get rid of the compass nag with it.

 

But that is version 2.30 for the Legend HCx. The update being discussed is for the GPS chipset and could improve the tracking issue. It can only be accessed by running the WebUpdater. Garmin could have done this in a less confusing way.

[fujitsu]

Hi,

 

I try to upadate my etrex legend HCx with the webupdater and it told me that I have no update and asked me if I want to see if there is a unit software update. I answer yes but I get a error message. Sometrinh like it could not connect with the server.

 

So, did anyone have success when try to update addicional unit software for the new Etrex H series?

 

Does anyone install this version for the chipset? Does anyone know if the chipset type M is the mediatek chipset?

 

regards

[BuckyBuck]

This standard response from Garmin simply stating that you must be traveling at least 2.2 mph is disappointing, to say the least.

 

When I got this response the other day from someone at Garmin support who identified himself as a 2nd Shift Outdoor/Fitness Team Product Support Specialist, I pointed out that it was absurd that a GPS unit marketed as a "trail product" is unable to record distances traveled at less 2.2 mph. His response to that message was that he was merely "providing me with a possible solution to your problem." Do you think he was suggesting that the problem is that all of us who think this is a dreadful design flaw simply aren't walking fast enough?

 

I replied back, saying Garmin needs to fix this. He would "forward my suggestion to the appropriate channel." I hope that isn't Garmin-speak for the Delete key. I plan to continue hammering Garmin about this until something happens.

 

I have to say that I was extremely impressed with my Vista HCx's reception today when I went hiking in Ohio's Cantwell Cliffs area. My old eTrex Legend couldn't even find a satellite at the bottom of the gorge. My new HCx didn't lose the signal at any time. Of course, since I was going up and down the whole time, I have no idea how far I hiked because of THIS DREADFUL DESIGN FLAW that prevents the HCx from registering speeds and distances when you're moving at less than 2.2 mph. Yeah, I can probably look at my track log, but why should I have to do that?

[jmundinger]

This standard response from Garmin simply stating that you must be traveling at least 2.2 mph is disappointing, to say the least.

 

I had several email exchanges with Garmin regarding this issue. I got a measure of what I though was run-around, but was never informed that stock answer regarding 2.2 mph.

 

Fwiw, someone else mentioned in one of these threads that the speed threshold was 2.2kph - not 2.2 mph. That would be closer to what my unit does. The trip computer seems to fail at about 1.6 mph.

[BuckyBuck]

This standard response from Garmin simply stating that you must be traveling at least 2.2 mph is disappointing, to say the least.

 

I had several email exchanges with Garmin regarding this issue. I got a measure of what I though was run-around, but was never informed that stock answer regarding 2.2 mph.

 

Fwiw, someone else mentioned in one of these threads that the speed threshold was 2.2kph - not 2.2 mph. That would be closer to what my unit does. The trip computer seems to fail at about 1.6 mph.

 

The Garmin rep I communicated with seems to think it's 2.2 mph. Here's the first response I received from Garmin support (with names deleted) when I confronted them about this dreadful design flaw:

 

Dear (BuckyBuck),

 

Thank you for contacting Garmin International,

 

In order for distance to be recorderd you must be traveling at least 2.2 mph.

 

With Best Regards,

 

(Garmin support person's first name, last initial)

 

Product Support Specialist

2nd Shift Outdoor/Fitness Team

Garmin International

913-397-8200

800-800-1020

913-397-8282 (fax) Att: (Garmin support person's first name, last initial)

www.garmin.com

[hwyhobo]

Perhaps I am just totally dense, because I am lost. Does that mean that it will not track at all if you move more slowly? In other words, it will not drop track points? On the HCx I just received, it says it can track by "auto", "time", or "distance". So, I understand that by distance is out of the question. What about "Auto"? How does that work?

 

If I set it to "time", do I then need additional mapping software besides the Garmin Trip & Waypoint Manager on my computer to figure out distances?

Edited September 24, 2007 by hwyhobo

[dogwalkers2]

Perhaps I am just totally dense, because I am lost. Does that mean that it will not track at all if you move more slowly? In other words, it will not drop track points? On the HCx I just received, it says it can track by "auto", "time", or "distance". So, I understand that by distance is out of the question. What about "Auto"? How does that work?

 

If I set it to "time", do I then need additional mapping software besides the Garmin Trip & Waypoint Manager on my computer to figure out distances?

Distance records a track point every so many metres/feet travelled.

 

Time records a track point every so many minutes.

 

Auto records a track point according to some magical combination of time and distance, based on how much your track changes. That is, if you travel a nearly perfect straight line, it will lay down fewer track points than if you travelled a curvy course over the same distance and time.

 

You don't need any other software, since the distance calculation is based on the lat/long coordinates of the track points. Just the relative positions of things such as roads and lakes may be off due to the lower accuracy of the maps in T&WM.

[jmundinger]

Does that mean that it will not track at all if you move more slowly? In other words, it will not drop track points?

 

No. This is an issue with the trip computer. It does not affect tracking.

[ivane8]

Is web updater required to determine the current version I have installed, or is it also displayed somewhere in the unit itself? I can't seem to find it there.

 

On the Vista hcx, with the power off hold down on the joystick button (straight down, not in any direction) and turn the power on while doing this. It enters a diagnostic mode and shows things like software version, bravo version?, internal temp, voltage, signal to noise ratio, and the results of the post test (RAM, ROM, Base map etc. Also allows you to test the buttons. If you press the page button twice, it will cycle through some screen tests

[Smac999]

Does that mean that it will not track at all if you move more slowly? In other words, it will not drop track points?

 

No. This is an issue with the trip computer. It does not affect tracking.

 

it effects tracking if you have it set to track by distance. it doesn't track if it doesn't think you moved.

[SiliconFiend]

Does that mean that it will not track at all if you move more slowly? In other words, it will not drop track points?

 

No. This is an issue with the trip computer. It does not affect tracking.

 

it effects tracking if you have it set to track by distance. it doesn't track if it doesn't think you moved.

It will still track. The trip computer is triggered by the rate of movement. People are complaining that this threshold rate is too high for pedestrian use.

[Smac999]

Does that mean that it will not track at all if you move more slowly? In other words, it will not drop track points?

 

No. This is an issue with the trip computer. It does not affect tracking.

 

it effects tracking if you have it set to track by distance. it doesn't track if it doesn't think you moved.

It will still track. The trip computer is triggered by the rate of movement. People are complaining that this threshold rate is too high for pedestrian use.

 

exactly and if you are going slower then that rate it doesn't track. I have tested.

[+RRLover]

"People are complaining that this threshold rate is too high for pedestrian use."

 

 

And rightly so!

 

Norm

Edited September 25, 2007 by RRLover

[Alphawolf]

Does that mean that it will not track at all if you move more slowly? In other words, it will not drop track points?

 

No. This is an issue with the trip computer. It does not affect tracking.

 

it effects tracking if you have it set to track by distance. it doesn't track if it doesn't think you moved.

It will still track. The trip computer is triggered by the rate of movement. People are complaining that this threshold rate is too high for pedestrian use.

 

exactly and if you are going slower then that rate it doesn't track. I have tested.

Yes it does...I just did a 35 mile backpacking trip in Yellowstone. If left on, the unit recorded the tracks very, very well. However, the odometer recorded just a fraction of our actual mileage.

[+Grinch & Gremlin]

exactly and if you are going slower then that rate it doesn't track. I have tested.

Yes it does...I just did a 35 mile backpacking trip in Yellowstone. If left on, the unit recorded the tracks very, very well. However, the odometer recorded just a fraction of our actual mileage.

 

You guys are just debating semantics. Smac99, Alphawolf just means that the tracks are recorded properly internally so when you get home you can upload them into your computer and use them. He's agreeing that the odometer reading (what you mean by 'tracks') doesn't show the correct distance.

 

So you can't tell, while hiking, how far you've hiked. But when you get home, you can move the tracks to your computer and find out then. Real useful, eh? In fact, this is what makes it so absurd that Garmin hasn't done anything about it. If the tracks are being laid down correctly in the track log, then clearly the device 'knows' that it's moving. So if it knows that it's moving, it should be a simple adjustment to the firmware to pass that information along correctly to the trip computer screen.

 

One last thing. The error only occurs in track by distance mode. It works correctly if you use track by time so that's a workaround until they get it fixed.

[Smac999]

exactly and if you are going slower then that rate it doesn't track. I have tested.

Yes it does...I just did a 35 mile backpacking trip in Yellowstone. If left on, the unit recorded the tracks very, very well. However, the odometer recorded just a fraction of our actual mileage.

 

 

you are incorrect. I have tested it myself. gone walking slowing (no distance on trip meter. and looked at the tracks in mapsource. I had a single track point. the place I started. if the tracks are set to "track by distance" (is this the part you are missing? you're was probably set to auto or time) then unless the GPS thinks you are moving. it doesn't record. if you set it to track by distance. say 300 feet. it'll track everytime the trip meter rolls over 300 feet. if the trip meter never moves. you get no tracks.

 

I am strickly talking about track by distance.

Edited September 25, 2007 by Smac999

[MikeSSS]

I walk about 1.0 mph on rocky trails, sometimes slower, seldom faster.

 

I've never had a GPS, the purpose would be for the odometer function when walking and kayaking, finding the anchor ball, and maybe caching. Position on the interstate and finding the way back to places previously visited would be good too. Since I've never had a GPS I really don't know what I'd like to do with it or what they can do.

 

If the HCX is set to 'track by time', will I be able to get a reasonably accurate distance, time and speed from the odometer? If not then the HCX is of little value to me. If set to record every 5 seconds can it record a three or four hour walk, say 3,000 data points. Can the track be transferred into Google Earth? That would be very desirable. Copying locations out of Google Earth would be great too since I use Google Earth a lot.

 

I am looking at the 76 CSX too because it floats, a big plus for kayaking. Will the 76 CSX give me correct odometer readings for my very slow hobbling pace?

 

Is the 76 CSX's screen much harder to read than the HCX's?

 

What other things should I be asking? Information is very hard to find and the threads on this site are extremely valuable

 

Thanks for your help.

 

Mike S

[jmundinger]

Mike - the eTrex HCx series will do everything that you are looking for in a GPSr, except accurately record the distance walked when you are moving slowly. And, if you have the track log set to record set to "auto", the track log will have the distance, as well, you just won't be able to see it on the unit while on the trail. I don't have any experience regarding the track by distance vs. track by time vs. auto tracking issue - I have always used the auto, which is the default setting for that feature.

 

The HCx is a little smaller than the CSx. The unit is also less expensive. Unless an accurate odometer is a priority issue for you, I'd go with the HCx (but, I also have a bias for the eTrex units because I am familiar wiht them).

[dogwalkers2]

I walk about 1.0 mph on rocky trails, sometimes slower, seldom faster.

 

I've never had a GPS, the purpose would be for the odometer function when walking and kayaking, finding the anchor ball, and maybe caching. Position on the interstate and finding the way back to places previously visited would be good too. Since I've never had a GPS I really don't know what I'd like to do with it or what they can do.

 

If the HCX is set to 'track by time', will I be able to get a reasonably accurate distance, time and speed from the odometer? If not then the HCX is of little value to me. If set to record every 5 seconds can it record a three or four hour walk, say 3,000 data points. Can the track be transferred into Google Earth? That would be very desirable. Copying locations out of Google Earth would be great too since I use Google Earth a lot.

 

I am looking at the 76 CSX too because it floats, a big plus for kayaking. Will the 76 CSX give me correct odometer readings for my very slow hobbling pace?

 

Is the 76 CSX's screen much harder to read than the HCX's?

 

What other things should I be asking? Information is very hard to find and the threads on this site are extremely valuable

 

Thanks for your help.

 

Mike S

Mike - the eTrex HCx series will do everything that you are looking for in a GPSr, except accurately record the distance walked when you are moving slowly. And, if you have the track log set to record set to "auto", the track log will have the distance, as well, you just won't be able to see it on the unit while on the trail. I don't have any experience regarding the track by distance vs. track by time vs. auto tracking issue - I have always used the auto, which is the default setting for that feature.

 

The HCx is a little smaller than the CSx. The unit is also less expensive. Unless an accurate odometer is a priority issue for you, I'd go with the HCx (but, I also have a bias for the eTrex units because I am familiar wiht them).

Just to add a bit, I use an HCx for kayaking. If you put it in an Aquapac, it'll float and clip with a carribeaner to your deck lines, so it doesn't float away.

[Alphawolf]

exactly and if you are going slower then that rate it doesn't track. I have tested.

Yes it does...I just did a 35 mile backpacking trip in Yellowstone. If left on, the unit recorded the tracks very, very well. However, the odometer recorded just a fraction of our actual mileage.

 

You guys are just debating semantics. Smac99, Alphawolf just means that the tracks are recorded properly internally so when you get home you can upload them into your computer and use them. He's agreeing that the odometer reading (what you mean by 'tracks') doesn't show the correct distance.

 

So you can't tell, while hiking, how far you've hiked. But when you get home, you can move the tracks to your computer and find out then. Real useful, eh? In fact, this is what makes it so absurd that Garmin hasn't done anything about it. If the tracks are being laid down correctly in the track log, then clearly the device 'knows' that it's moving. So if it knows that it's moving, it should be a simple adjustment to the firmware to pass that information along correctly to the trip computer screen.

 

One last thing. The error only occurs in track by distance mode. It works correctly if you use track by time so that's a workaround until they get it fixed.

I am incorrect?!?! I don't think so... Here is a picture after uploading a tracklog to MapSource. My average speed for this entire tracklog was less than 1-mph (I was stepping over an incredible amount of deadfall timber). You can see, the tracklog recorded just fine. It is set to default "Auto".