Gps map updates

[minnowlimo]

Anyone have any updates saved between 2.58 and the current 2.79 and 37.01 gps map? Updated to the most recent and now needing to go back. Any help or info is appreciated.

1643
Lvs 34
37.01 with 2.79 currently

[719SHO]

Was the update bad? I just got a 1643 and wondering which update to go with.

[LWINCHESTER2]

Stay updated with the most current version.

[minnowlimo]

Yea wanted to go back and try a previous software version. However I am learing that now you CANNOT revert back to old software after updating to the 38.03 2.79.
I know this goes against what has been in the past because I too have forced updates back to older versions a few times. I updated unit with sd card (not active captain app) to 37.01. Then onto 38.03. Now when using same sd card 2 days later unit will not revert back to previous software version. Same card, same everything.

[JordanC]

Yea wanted to go back and try a previous software version. However I am learing that now you CANNOT revert back to old software after updating to the 38.03 2.79.
I know this goes against what has been in the past because I too have forced updates back to older versions a few times. I updated unit with sd card (not active captain app) to 37.01. Then onto 38.03. Now when using same sd card 2 days later unit will not revert back to previous software version. Same card, same everything.

Are you putting the unit into recovery mode before putting the SD card with 37.01 into it?

[minnowlimo]

Yes, I installed the 37.01 update with sd card, then used another card to move up to 38. Then used same exact card with 37 already loaded ( which updated the unit 2days prior) now it will not go back. It goes through the entire process as it is supposed to while installing software. Reboot and all, however when the whole process is finished and you go look at software it still says 38. 2 different sd cards and the one with 37 worked fine 2 days ago.

[JordanC]

Never heard of that, before putting the card with 37 in it, you are putting the unit into recovery mode? It will not roll back unless it is in that mode.

To perform a forced update:

1. Turn the device Off
2. Hold the power button until
   Recovery Loader Ready displays

• The GPSMAP® 10x2 chartplotters & GPSMAP®
12x2 chartplotters are keyed devices that need to have the Up arrow and Power button held until
Recovery Loader Ready displays

1. Insert software update card and a message of Starting Recovery
   Update will display
2. When the Software Updater page completes Press the Restart button

[minnowlimo]

Never heard of that, before putting the card with 37 in it, you are putting the unit into recovery mode? It will not roll back unless it is in that mode.

To perform a forced update:

1. Turn the device Off
2. Hold the power button until
   Recovery Loader Ready displays

• The GPSMAP® 10x2 chartplotters & GPSMAP®
12x2 chartplotters are keyed devices that need to have the Up arrow and Power button held until
Recovery Loader Ready displays

1. Insert software update card and a message of Starting Recovery
   Update will display
2. When the Software Updater page completes Press the Restart button

Correct, yes done it. It will go through the entire process like any other time when doing software changes,only when it's all finished and you go to look at what version it's on it still says 38. This is looking at the garmin unit itself, not on the app.

I am going through all the trouble of trying to go back in software because the latest 38 version is super wide to one side. When looking at a target dead on say at 12, then turn to the left image leaves the cone at say 11 o clock, now when looking to the right the image will fade some at 1 o clock but stays on screen all the way to say 2:30. Talking with people i know locally there are atleast 5 other people i know running 38 version with lvs34 and there all the same way. I'll try and post a video.

[minnowlimo]

https://youtube.com/shorts/E8GKcFK6k...sYiLlRjHYoZb9F

[Mahomee]

I went back I didnt like how they changed the text messages to just showing the first few words etc.

[LWINCHESTER2]

.......I am going through all the trouble of trying to go back in software because the latest 38 version is super wide to one side. When looking at a target dead on say at 12, then turn to the left image leaves the cone at say 11 o clock, now when looking to the right the image will fade some at 1 o clock but stays on screen all the way to say 2:30. Talking with people i know locally there are atleast 5 other people i know running 38 version with lvs34 and there all the same way. I'll try and post a video.

I doubit it. If that was the case the release notes would have included a statement regarding such a change. That's not a small matter and changes to cone widths don't happen haphazardly. The are set in the manufacturing of the transducer elements and measured at specific signal strengths. That said, the apparent cone width is affected by settings. A higher gain can make it appear a bit wider while filters (TVG, Noise Rej, etc) can make it appear smaller.

If yours appears wider or smaller I would focus on settings rather than software version. I have done repeated extensive testing of this kind of thing at a variety of depths and ranges. Step 1 is to place the target yourself, making sure it hangs completely vertical in the water. The line/cable under most buoys do not. Want to find out something really interesting, use a big jug and under it hang a 1/4" steel cable with a weight that does not reach the bottom. Start 80 ft away and do the left/right assessment, recording the results on a video. Then move to 75 and do it again and keep repeating at 5 ft closer intervals. Note the variations of brightness of the image at the different depths and ranges.

The cable has to be straight, your TM shaft plumb and use a 0 degree mount.

[minnowlimo]

I doubit it. If that was the case the release notes would have included a statement regarding such a change. That's not a small matter and changes to cone widths don't happen haphazardly. The are set in the manufacturing of the transducer elements and measured at specific signal strengths. That said, the apparent cone width is affected by settings. A higher gain can make it appear a bit wider while filters (TVG, Noise Rej, etc) can make it appear smaller.

If yours appears wider or smaller I would focus on settings rather than software version. I have done repeated extensive testing of this kind of thing at a variety of depths and ranges. Step 1 is to place the target yourself, making sure it hangs completely vertical in the water. The line/cable under most buoys do not. Want to find out something really interesting, use a big jug and under it hang a 1/4" steel cable with a weight that does not reach the bottom. Start 80 ft away and do the left/right assessment, recording the results on a video. Then move to 75 and do it again and keep repeating at 5 ft closer intervals. Note the variations of brightness of the image at the different depths and ranges.

The cable has to be straight, your TM shaft plumb and use a 0 degree mount.

I appreciate the advice, the transducer is on a 0 degree fished obsessed mount, and it is absolutely straight and not angled.

I completely understand the bouy cable may be a little angled but I can replicate this same thing on any cable bouy/dock post that I can find. Yet the results are the same. It is ALWAYS to one side.

I'll keep digging and see also what the problem with not being able to revert back to old software as I have done in the past. Thank you

[LWINCHESTER2]

What was interesting about the video was that the buoy line, as you moved from left to right, did not seem to go from weak to bright to weak. That is, the return appeared asymmetrical. Regardless of the size of the cone, whether narrow or wide, that should not have happened. The software, in Forward orientation, does a good job of calculating and displaying distance and depth. Pretty sure it has no capability distinguishing left to right except the strength of the return.

I have seen something similar to what you are seeing when pointing at vertical bridge piers and I have no explanation for what I see except that it is not dependent on the software version. For example, a vertical, rectangular shaped concrete bridge pier, when moving the TM from left to right should all appear top to bottom at the same time and similarly fade top to bottom, as the TM movement is continued, at the same time. It does not. It is as if I am using a canted transducer. I've gone to extreme efforts to make sure my TM shaft is plumb left to right and front to back and also use a Fish Obsessed 0 degree mount.

So my disagreement is not in what your are seeing, but that it is due to the software version. And if your are correct that the difference is in the software version, then whatever changed should have been included in the release notes. I hope you are able to continue in your investigation and please keep us informed as to the results.

[minnowlimo]

Thanks for your input, as I will update post whenever I resolve the issue. Maybe this will help someone down the road also. Several days ago after installing 38 software transducer went to rocking on the screen. Called Garmin and they are sending me a new transducer. If that's not the problem, then I will else where.

[JordanC]

This is the first I’ve heard of an update removing the ability to roll back software to an earlier version. Did Garmin comment on that while you were on the phone with them? I have 37.01 on my unit and think it’s the best out of every version since the 34 came out

[minnowlimo]

This is the first I’ve heard of an update removing the ability to roll back software to an earlier version. Did Garmin comment on that while you were on the phone with them? I have 37.01 on my unit and think it’s the best out of every version since the 34 came out

No he didn't comment on it. I have been able to force update from 37 back to older updates but after going to 38 it won't let me go back to 37 version. Like I said above with the exact same sd card that I had previously loaded 37 with. Out of town at the moment but going to look further when I get back.