Jump to content

Firmware 2.70, But Gps Software(sirf) 2.40 ?


Recommended Posts

Hi,

since I bought my 60 CSX I have the GPS Software version 2.40 (I assume it is the SIRF firmware).

I used the Garmin firmwares 2.62, then 2.60 and now 2.70, but the GPS receivers version always stayed the same (2.40).

I have heard that somebody has 2.50 (could you check your 76 and 60's out there?).

 

Question is: How can this be upgraded, and what does it change exactly ?

 

Thanks for any hints and tips, NZ

Link to comment

Hi

 

Firmware is diffrent to software. In simple terms think of Firmware as the Operating System. In fact it is an update of the Read Only Memory (ROM) where Software would update the Random Access Memory (RAM). But it all gets a bit fuzzy in a device like this.

 

This is an upgrade of how the hardware interfaces with the software and the list of what it does is on the upgrade page of the Garmin website. I'll be updating my GPS as soon as I get home (currently lunchtime in the UK).

 

If it was a software upgrade they would be changing things like how the screen looked. Wonder if they could do a software upgrade to work out how long it takes to boil a kettle at altatude?

 

 

<_<:mad:

Link to comment

at this time we have for gpsmap 60 csx:

 

Software Version 2.70

GPS SW Version 2.40

 

We are talking about the GPS SW VERSION which might be also 2.50 for some users

Normally the Garmin-FW update is only for the software Version (2.70 currently)

Link to comment

My GPSMap60Cx started out at SW version 2.30, and still there, and the firmware is 2.70 now, so I'm wondering if the lower number, is what was installed at the factory?? or not?

I don't think so, because somebody bought a CSX and had the combination 2.50/2.60 on it.

 

To clarify to the others what we are talking about, here an image of what my 60 CSX tells me, when I display the software version:

 

software.jpg

 

So I have the combination 2.70/2.40 now, and my question is, if this 2.40 can also be upgraded.

I wrote a question to Garmin about that, but it usually takes some days until to a response.

Possibly some of you already know more about that, therefore I asked.

Edited by NewZealand
Link to comment

 

Yes - see my post above <_<

I reread your post, but other that that I've personally not seen any evidence, anecdotal or otherwise, that the GPS SW has ever changed due to any user-iniitiated activity. Are you saying that you've performed an upgrade on a 60*x or 76*x where the GPS SW version changed? The only reports of the GPS SW changing were due to replacement of the entire unit. But perhaps I missed something along the way...

 

Based on the information I've seen I'd guess that it represents one or more of the following:

 

- the original version of the firmware that was installed on the unit and/or is in ROM

- the version of the "brainstem' code such as the loader -- either in ROM or seperate area of flash

- the SiRF firmware revision level (seems somewhat less likely given WAAS changes in 2.70 that didn't affect it)

- is related to the hardware revision level of the unit (despite saying "SW")

Link to comment

 

Yes - see my post above <_<

I reread your post, but other that that I've personally not seen any evidence, anecdotal or otherwise, that the GPS SW has ever changed due to any user-iniitiated activity. Are you saying that you've performed an upgrade on a 60*x or 76*x where the GPS SW version changed? The only reports of the GPS SW changing were due to replacement of the entire unit. But perhaps I missed something along the way...

 

Based on the information I've seen I'd guess that it represents one or more of the following:

 

- the original version of the firmware that was installed on the unit and/or is in ROM

- the version of the "brainstem' code such as the loader -- either in ROM or seperate area of flash

- the SiRF firmware revision level (seems somewhat less likely given WAAS changes in 2.70 that didn't affect it)

- is related to the hardware revision level of the unit (despite saying "SW")

What dfred said...

And I'll add that I cannot find any downloads from Garmin's Web site, I've updated my firmware to 2.70 and my software version is 2.30!

Link to comment

I just received a replacement 60CSx GPSr from Garmin yesterday, the S/N was over 25,000 higher than my original. The original was SW Version 2.40 and the new unit has SW Version 2.5. I'd like to know what the difference is myself... ;)

Link to comment

If you run Webupdater http://www.garmin.com/support/download_det...ct=999-99999-27 on your unit for the first time, it will probably load the same version as you already have. But if you run it once more again, it will load GPS SW 2.50 ! Really, it works !

GOOD catch! I did the firmware update without the webupdater, and the GPS SW was 2.30. Just ran the updater, and it said the firmware was current, but then provided an option to check for the gps receiver software. It offered the option to update it, and now it is 2.70 and 2.50.

 

Tx dood.

 

R

Link to comment
If you run Webupdater http://www.garmin.com/support/download_det...ct=999-99999-27 on your unit for the first time, it will probably load the same version as you already have. But if you run it once more again, it will load GPS SW 2.50 ! Really, it works !
It works just great! Only thing that gave me a little scare was that my computer is in a spot where I can't get a GPS signal inside. After the update to 2.50 I was checking to see if everything on my 60CSx was still working correctly and I noticed the displayed time on the altimeter screen (actually on any screen) was "Sep '04." Until I went outside to get satellite lock, the time wasn't set. It immediately aquired the correct time and date from the GPS network.
Link to comment

Anyone notice any difference after updating to GPS SW Version 2.50, outside of those noted in Software Version 2.70?

Though I only have it since a few hours, I already have a difference:

EGNOS Satellite 33 disappeared and was replaced by 37. Don't know yet which one that is, but will check it.

Link to comment

Anyone notice any difference after updating to GPS SW Version 2.50, outside of those noted in Software Version 2.70?

Though I only have it since a few hours, I already have a difference:

EGNOS Satellite 33 disappeared and was replaced by 37. Don't know yet which one that is, but will check it.

That's interesting, 37 is PRN124 (Artemis) and is quite new. Actually 33 (PRN120, AOR-E) will be turned off in the middle of the year.

Do you guys in Europe with the old (non 2.50) SIRF software still see 33 or also see 37 now?

I just want to know if it is a Firmware issue (which would be positive to see the satellite which will be the production one, and not the one which will go out of order), or if ESA changed something today accidently (possibly 33 doesn't send, as it was the case a few days ago for some minutes).

Edited by NewZealand
Link to comment

So, what did upgrading from GPS SW 2.3 to 2.5 buy us??

 

Seems like it took a lot longer for the satellite page to settle down. Lots of bars jumping around. It is showing a 7' EPE now with max lock on 10 sats (using Gillson antenna). I haven't seen it show 7' in a long time. Waas is enabled and 35 is still winkin and blinkin in the ESE and showing as a hollow bar at about 50% height.

Link to comment

Waas is enabled and 35 is still winkin and blinkin in the ESE and showing as a hollow bar at about 50% height.

 

I'm beginning to think, as others have stated, that this is not necessarily a software related issue. I get a solid 35 with WAAS corrections here in Southern California. Perhaps is has more to do with your location?

 

As far as changes with the 2.5 SW-- I haven't noticed much....

Link to comment

Waas is enabled and 35 is still winkin and blinkin in the ESE and showing as a hollow bar at about 50% height.

 

I'm beginning to think, as others have stated, that this is not necessarily a software related issue. I get a solid 35 with WAAS corrections here in Southern California. Perhaps is has more to do with your location?

 

As far as changes with the 2.5 SW-- I haven't noticed much....

 

I am thinking it has to do with location.......seems like a lot of guys on the west coast are getting D's

 

I just upgraded...already had 2.7........now have 2.7 and 2.5

 

I am showing a hollow bar about halfway up for 35 (only waas I am picking up and it is still showing it E/SE) and no D's by letting my GPSr sit outside with the Gilsson antenna.

 

I've had my 60CSx for about since 3-16 and only got a filled in bar on a WAAS bird for part of one day....most of the time it shows a hollow bar.......and that one day that I was getting a filled in bar is the only time I have shown D's with this GPSr........it was showing 35 in an E/SE positin....my 60C and legend C have been picking up 1-2 WAAS birds and showing D's and showing 35 to the west

 

near Fort Worth TX

Link to comment

I'm in Tucson, AZ. I picked up 35 and 47 today with solid bars and had D's. That screenshot was from the 2.60 firmware. With that firmware you couldn't get a solid bar.

 

Maybe you should leave it outside for a bit with a clear view and see if it can get a lock. Sometimes it takes a little while.

Link to comment

I'm in Tucson, AZ. I picked up 35 and 47 today with solid bars and had D's. That screenshot was from the 2.60 firmware. With that firmware you couldn't get a solid bar.

 

Maybe you should leave it outside for a bit with a clear view and see if it can get a lock. Sometimes it takes a little while.

 

 

I was wondering if I need to do a reset or hard reset , or if I just need to wait until 35 is finished moving and sending corrections

Edited by birddog14
Link to comment

Do you guys in Europe with the old (non 2.50) SIRF software still see 33 or also see 37 now?

I just want to know if it is a Firmware issue (which would be positive to see the satellite which will be the production one, and not the one which will go out of order), or if ESA changed something today accidently (possibly 33 doesn't send, as it was the case a few days ago for some minutes).

 

I've seen 33 and 37 with 2.4, and still see them w/ 2.5 now.

 

Today got solid lock first on 33, then on 39, but not on 37 (although it showed up w/ 1/2 strength).

I'm located in Sofia, and one of the EGNOS base-stetions is here, so corrections are supposed to be of use :ph34r:

Link to comment

This email come from Garmin who was kind enough to pass the information received from SiRF. The latter is responsible for the GPS SW version.

 

Thank you for contacting Garmin International,

 

I got the following information from the engineers:

Here is a list of firmware changes for units with a Sirf antenna. This is normally seen in the system menu of a device under GPS SW version. V2.20 is the production version, and at v2.50 a tunnel re-acquisition issue was solved, except on the Nuvi. Normally the GPS SW version is updated through Web Updater.

 

Change History

 

Version 2.50:

 

1. Improve tunnel re-acquisition problem.

 

------------------------------------------------------------

 

Change History

 

Version 2.40:

 

1. Changes made for manufacturing purposes.

 

------------------------------------------------------------

 

Change History

 

Version 2.30:

 

1. Changes made for manufacturing purposes.

 

If you need additional assistance, please call our 800-800-1020 line during our regular business hours of 8:00 to 5:00 Central Time, Monday through Friday. Any one of our Technical Support staff would be happy to help you further.

 

With Best Regards,

Garmin International

Senior Product Support Specialist

800-800-1020

913-397-8200

913-440-5488 (fax)

http://www.garmin.com/

Edited by Rhialto
Link to comment

Thank you for contacting Garmin International,

 

I got the following information from the engineers:

Here is a list of firmware changes for units with a Sirf antenna. This is normally seen in the system menu of a device under GPS SW version. V2.20 is the production version, and at v2.50 a tunnel re-acquisition issue was solved, except on the Nuvi. Normally the GPS SW version is updated through Web Updater.

 

Change History

 

Version 2.50:

 

1. Improve tunnel re-acquisition problem.

 

I'm getting increasingly disappointed with Garmin engineering. Simple field tests make it clear that the tunnel problem has not been solved, or even improved. See

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

 

Come on guys! You make great products, and problems like this are more annoying than they are critical. But take a unit outside and test it before you announce to the world that the problem is solved!

Link to comment

Thank you for contacting Garmin International,

 

I got the following information from the engineers:

Here is a list of firmware changes for units with a Sirf antenna. This is normally seen in the system menu of a device under GPS SW version. V2.20 is the production version, and at v2.50 a tunnel re-acquisition issue was solved, except on the Nuvi. Normally the GPS SW version is updated through Web Updater.

 

Change History

 

Version 2.50:

 

1. Improve tunnel re-acquisition problem.

 

I'm getting increasingly disappointed with Garmin engineering. Simple field tests make it clear that the tunnel problem has not been solved, or even improved. See

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

 

Come on guys! You make great products, and problems like this are more annoying than they are critical. But take a unit outside and test it before you announce to the world that the problem is solved!

 

I will modify my post to clarify this but that software comes from SiRF, the engi at Garmin only passed the information.

Link to comment

It is true, that the tunnel reacquisition problem is not solved (I had it yesterday).

However, I had it only because I forgot to turn off WAAS/EGNOS.

Without WAAS it works fine.

I'm in the EGNOS area, and EGNOS data are still in testmode by ESA and therefore are not used for position corrections in the Garmin units (they display only that the data are received).

This may change during the year, when ESA goes productive with EGNOS, but even then for me this correction is useless, because these satellites are deep at the southern sky and I can see them not often.

This may be different vor boat navigating or navigating in the flatlands.

But people who use the units in the mountains or in cities should turn off WAAS/EGNOS, it's just a senseless overhead for the processor, and the unit is accurate enough without it (or do you need to land a jumbojet on a foggy airport?).

Edited by NewZealand
Link to comment

Yesterday, 12 May, I upgraded the firmware to 2.71 beta. After reading this thread I checked to see what SW version I am running and it is 2.30.

 

I ran the Web Updater and it said that the firmware was up to date, would I like to check and see if the SW was up to date? I clicked continue, and the Web Updater updated the SW to 2.5 and the firmware remained at 2.71.

 

I'm a happy camper!

Link to comment

ok.......I went about 100 miles north west of Fort Worth thursday to go turkey hunting. I put my Gilsson antenna on and headed out.......I was showing 35 as a hollow bar about halfway up and STILL showing it in the east. Not for sure, but about half way out there (not sure because I wasn't really watching it...just letting it sit) I was getting a FULL bar for 35 and showing it in the west and the other 11 bars were all maxed out and showing Ds with 7 foot accuracy.

 

Once I got there, I turned the unit off for about 1 minute and then turned it back on and it goes back to showing 35 in the east and a halfway full bar and no Ds..I was figuring that since I had just had it on for about 1.5 hours and showing 35 in the west that when I turned it back on it was still think it is in the same spot.......but If I let it sit there for a while it will show 35 in the west. Any ideas on what would cause this?

Link to comment

Once I got there, I turned the unit off for about 1 minute and then turned it back on and it goes back to showing 35 in the east and a halfway full bar and no Ds..I was figuring that since I had just had it on for about 1.5 hours and showing 35 in the west that when I turned it back on it was still think it is in the same spot.......but If I let it sit there for a while it will show 35 in the west. Any ideas on what would cause this?

For whatever reason the SiRF units go back to the default almanac values for the WAAS satellites whenever you turn them off or even go to "Use with GPS off" momentarily. Previous models always retained the most recent almanac data; not sure why they decided not to for the SiRF models.

 

My theory has been that you need to get updated almanac data for 35 from another WAAS satellite before it will use correctional data from 35. Are you sure that you aren't able to see one of the other WAAS prior to getting D's from 35? If so, that means the unit is getting updated almanac data for 35 from some other source (maybe 35 itself). Hard for me to say here (in Los Angeles); 47 comes in here to strong for me to not see it for any length of time.

Link to comment

I will modify my post to clarify this but that software comes from SiRF, the engi at Garmin only passed the information.

I apologize for my previous response; it was a bit of a rant!

 

Yes, I realize that Garmin is having to rely on SiRF to correct problems; it's probably frustrating for the Garmin technical staff not to be able to deal with problems directly, and I sympathize with them, having been in similar positions in the past myself. My main point was that as "prime contractor" on the unit, Garmin should do a bit of independent testing of solutions before declaring the problem resolved.

Link to comment

I will modify my post to clarify this but that software comes from SiRF, the engi at Garmin only passed the information.

I apologize for my previous response; it was a bit of a rant!

 

Yes, I realize that Garmin is having to rely on SiRF to correct problems; it's probably frustrating for the Garmin technical staff not to be able to deal with problems directly, and I sympathize with them, having been in similar positions in the past myself. My main point was that as "prime contractor" on the unit, Garmin should do a bit of independent testing of solutions before declaring the problem resolved.

 

my 60 csx is only picking up one waas bird (that I know of....I have not seen it pick up more than one waas bird since I have had it)..........35

 

my 60C and legend C both pick up 35 and 47 and show them in the west

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...