So, what’s the verdict on 25.1?

[til]

I did the update on the water over the air like I usually do, with my phones hotspot
My setup is a 12" live, AT1, TM150M and a 2-1. Update went smoothly.
The TM150m is finally back to it's previous quality of some years ago.
AT very clean picture.
Everything else with no problem as far as I can tell.
Something I'm not sure I managed to do before ist to set a waypoint from the AT.
It works indirectly by putting the cursor on a point in the AT, then see the cursor on your map, activate the map pane and there set waypoint to cursor.
Quite helpful when using the AT to scout for fish.

[06x6spdGTO]

I have a Carbon, doesn't work on it either. It's the source that goes away, not a HU issue. Same as they did with Battery Voltage source on the Ghost 1.3 update... the source just goes Keyser Soze. :(

Have you attempted the following with all devices powered up on the network:
Menu -> Settings --> System ---> Restore Defaults ----> ONLY CHECK GLOBAL ---> Confirm

[78Staff]

Have you attempted the following with all devices powered up on the network:
Menu -> Settings --> System ---> Restore Defaults ----> ONLY CHECK GLOBAL ---> Confirm

I've tried several different resets - HU factory reset, sources auto detect/configure, etc - but tbh I don't think I have tried that exact menu reset. I will give it a try and report back.

[78Staff]

I've tried several different resets - HU factory reset, sources auto detect/configure, etc - but tbh I don't think I have tried that exact menu reset. I will give it a try and report back.

Still no change, unfortunately... Global or Local, makes no difference.


SS3D Temp Source after v25.1 update and various resets, etc...




SS3D Temp Source after reverting to v21 (or v18)...

[06x6spdGTO]

Still no change, unfortunately... Global or Local, makes no difference.


SS3D Temp Source after v25.1 update and various resets, etc...




SS3D Temp Source after reverting to v21 (or v18)...

Oooffff.... and that is swapping software back on the same day with both of those screen shots?

Usually the global reset method I outlined above is the best technique to reset sonar modules... Now I will tell you I have seen it need to be done 2x before it takes... This is the NUMBER 1 greatest technique to fix No Source issues on Active Target (given the box is properly powered up, Ethernet Connected, and ON when you perform the Global Reset)...

I know its a stretch but give it one more go of the global reset... If its still not taking, its likely a hiccup in the software.

[78Staff]

Oooffff.... and that is swapping software back on the same day with both of those screen shots?

Usually the global reset method I outlined above is the best technique to reset sonar modules... Now I will tell you I have seen it need to be done 2x before it takes... This is the NUMBER 1 greatest technique to fix No Source issues on Active Target (given the box is properly powered up, Ethernet Connected, and ON when you perform the Global Reset)...

I know its a stretch but give it one more go of the global reset... If its still not taking, its likely a hiccup in the software.

Yeah, literally within minutes. I'll give it another go tomorrow.

One thing - you mentioned having all devices powered up, but the instructions on screen when you do the restore defaults state to turn all other displays off. I left all on per your post above, but not sure if that is making any difference all on or all off?

[Marc Marcantonio]

Depth Routing

you need to have: HDS Pro + integrated Lowrance/Simrad branded Trolling Motor connected via N2K + CMAP

it will not work on HDS Live or Carbon or Elite FS or Navionics.
Need to set your range to 3ft or greater target.
example: 12-16ft.

The option to depth route will not appear if you are not on the chart page when you open the trolling bar.

I was able to use the Depth Routing today and posted a new thread with a video how to activate it. Thank you for the help!

[Scuirus]

Important information from 25.1 release notes:

Legacy Sonar Networking
Legacy Sonar Networking compatibility to older devices has been changed via this software update. The older style “Single Source” sonar networking mode has been removed. Beginning with 25.1, only the current “Multiple Source” networking mode will be supported.
HDS Gen1, Gen2, and Gen2 Touch series displays will no longer be able to read sonar data from devices on the network with 25.1 software installed.

• NOTE: Networks that include these legacy displays alongside a current generation Lowrance display should continue to utilize the 23.3 software version. This will enable the current generation display to talk on the network in the older “Legacy Single Source” mode with the older display

The selection box for choosing your sonar networking mode has been removed from the Sonar Settings page.



This is also valid for BSM-2 and BSM-3 sonar modules

[78Staff]

Yeah, literally within minutes. I'll give it another go tomorrow.

One thing - you mentioned having all devices powered up, but the instructions on screen when you do the restore defaults state to turn all other displays off. I left all on per your post above, but not sure if that is making any difference all on or all off?

Tried again today, did it multiple times, along with several iterations of resest/reboots/auto configs/etc. I guess I'll just have to wait to see if Lowrance comes up with anything.

Important information from 25.1 release notes:

Legacy Sonar Networking
Legacy Sonar Networking compatibility to older devices has been changed via this software update. The older style “Single Source” sonar networking mode has been removed. Beginning with 25.1, only the current “Multiple Source” networking mode will be supported.
HDS Gen1, Gen2, and Gen2 Touch series displays will no longer be able to read sonar data from devices on the network with 25.1 software installed.

• NOTE: Networks that include these legacy displays alongside a current generation Lowrance display should continue to utilize the 23.3 software version. This will enable the current generation display to talk on the network in the older “Legacy Single Source” mode with the older display

The selection box for choosing your sonar networking mode has been removed from the Sonar Settings page.

This is also valid for BSM-2 and BSM-3 sonar modules

I'm not sure this would apply to SS3D - althought it is an older product, 2015 I think - since Marc C is (possibly) still able to to view SS3D Temp Source.

And the SS3D part works great for me, it's just the temp source that is the issue. Same for NoCal, although I think he's going to try a few things to see if he can get his to appear. I'm at my wits end and tbh a bit tired of fussing with it, so have reverted to the older s/w version for now. Hell if I can find a cheap Lowrance NMEA temp sensor I'd be willing to add it, but I'm not spending $100+ for one.

[78Staff]

I don't think so, as mentioned above and in earlier posts it works fine when I revert back to previous versions... only breaks when I load up v25. Same thing happens for NoCal as well, so it's not just me.

Marc is that actually SS3D temp in your video? I though you mentioed you didn't use SS3D temp but used the the oem Ranger temp sensor?

Marc, can you confirm that you were actually using SS3D source for temp? Maybe post the setting screens like mine to compare the differences (if any) between yours and mine and NoCal's?

[Marc Marcantonio]

Marc, can you confirm that you were using SS3D source for temp? Maybe post the setting screens like mine to compare the differences (if any) between yours and mine and NoCal's?

Yes I did, but now I realize you are using a Carbon, and I am using a Pro. Since the Carbon is two generations behind, I doubt the bug fix attempted to address Carbon units.

I won't be checking anything for a while as my brand-new Pro 12 on my console (the one in the video) died yesterday, and I shipped it back today; and I will be in California and Washington DC for the next month.

[78Staff]

Yes I did, but now I realize you are using a Carbon, and I am using a Pro. Since the Carbon is two generations behind, I doubt the bug fix attempted to address Carbon units.

I won't be checking anything for a while as my brand-new Pro 12 on my console (the one in the video) died yesterday, and I shipped it back today; and I will be in California and Washington DC for the next month.

Actually no, I am running Two 12" Pros at the console. Ignore the Carbon in the source list, it was a short experiement to squeeze a smaller unit on the bow lol. Already pulled it off in fact.

But, since you mention it, now I am wondering if the presence of the Carbon on the network during the update caused any issues. I mean, you would not think so since the SS3D is also an older (2015) product, but with Lowrance you just never know. Maybe I'll try again tomorrow since I've pulled the carbon off the boat.

[Joey805]

I have a carbon 12 with a TM150 and a 3in1 plugged directly into the back of the unit. Prior to the update, I was running 22.1.1 and when I ran the TM150 on custom 105, the 3in1 would freeze up. I just updated the unit to 25.1 and tried again. The 3in1 still freezes up when running the TM150 on custom 105. As soon as I change in to anything that is not custom, the 3in1 is no longer frozen.

I was hopeful that this issue would be fixed, as the release notes of 25.1 mentioned it.

Other bug fixes and improvements

• Elite FS max SideScan range increased
• SideScan interference improvements
• Sonar improvements when using Airmar Medium Chirp transducers
• Added support for Airmar Medium Ultra-wide transducers
• Fixed an issue where SideScan would not work correctly when using custom frequencies on 2D Sonar
• Sirius XM improvements

[Scuirus]

SS3D is not a legacy unit when it comes to sonar networking. Legacy units are products running NOS54 or older software. v25.1 is NOS70. A HDS Gen3 would in this respect be considered a legacy unit if running NOS54 or older, but this could easily be fixed by updating the software.

[78Staff]

Went back to v21.. have temp again, but v25 is clearly better imo for SS/DS... easily noticeable this weekend on the water after running v25 :(.

I'm at an impass... wait for Lowrance to figure it out (HD360 Nosecone, Orbit anyone :( ).
Buy a $100 NMEA Temp Sensor :(.


I thought I had a HD 3n1, so was considering installing it, and having both SS3D and HD3n1 available, although that would be a few hundred to get the correct TS&S parts. But, I can't find it, so I guess I let it go when I sold of a few Pro's last year :(. I thought I had held one back, but I guess not.

[Brewerbass]

Everything thing is good including at with 25.1, could see small ned rig easily today and all the other screens look good

[78Staff]

Went back to v21.. have temp again, but v25 is clearly better imo for SS/DS... easily noticeable this weekend on the water after running v25 :(.

I'm at an impass... wait for Lowrance to figure it out (HD360 Nosecone, Orbit anyone :( ).
Buy a $100 NMEA Temp Sensor :(.


I thought I had a HD 3n1, so was considering installing it, and having both SS3D and HD3n1 available, although that would be a few hundred to get the correct TS&S parts. But, I can't find it, so I guess I let it go when I sold of a few Pro's last year :(. I thought I had held one back, but I guess not.

I've noticed I can pickup several iterations of 2D style transducers, either Thru-Hull with temp probe, or skimmer types with temp etc for well less than buying a $105 Lowrance Temp Sensor. Might be older 7 pin version, but I do have a 7 to 9 pin cable laying around somewhere... (Probably next to that HD3n1 I can't find... lol). Ie Just just lay the transducer in the bilge and run the probe out and screw it into the jackplate. Or hang a skimmer off the jackplate somewhere, all I need is for the temp sensor to be wet. Still looking for the HD3n1... I still believe I held one back, b/c I know I was thinking about mounting it on the other side of the jacklate from the SS3D. :(.

Lowrance asked for some screenshots, so I sent them over last week, but haven't heard anything. I also had them send me a replacement pull cable for the Ghost, 3rd one in 2 years. Maybe they will send me a temp sensor, like when they sent out all those NEP-2's when there software wouldn't allow networking with other units due to different chip they were using a year or so back....

[78Staff]

Not a fan of v21... so back to v18 for now. Hopefully Lowrance can figure it out, b/c I do like 25.1 for SS3D otherwise....

[Marc Marcantonio]

I've noticed I can pickup several iterations of 2D style transducers, either Thru-Hull with temp probe, or skimmer types with temp etc for well less than buying a $105 Lowrance Temp Sensor. Might be older 7 pin version, but I do have a 7 to 9 pin cable laying around somewhere... (Probably next to that HD3n1 I can't find... lol). Ie Just just lay the transducer in the bilge and run the probe out and screw it into the jackplate. Or hang a skimmer off the jackplate somewhere, all I need is for the temp sensor to be wet. Still looking for the HD3n1... I still believe I held one back, b/c I know I was thinking about mounting it on the other side of the jacklate from the SS3D. :(.

Lowrance asked for some screenshots, so I sent them over last week, but haven't heard anything. I also had them send me a replacement pull cable for the Ghost, 3rd one in 2 years. Maybe they will send me a temp sensor, like when they sent out all those NEP-2's when there software wouldn't allow networking with other units due to different chip they were using a year or so back....

I rely upon a Lowrance EP-80 temp sensor which is mounted through my hull in the setback area of my Ranger. It is always in the water and out of the sunlight which gives it the true water temperature unlike sensors near the surface exposed directly to sunlight. Here is a link for one. I would give serious consideration to installing this one even if you get your SS3D sensor working again:

https://www.hodgesmarine.com/low000-...All%20Products

[Moonlighter]

Did the update on my Elite FS9 with TM150M and took the boat for a test run today - both to test the update and to test the new Lectrotab trim tabs that I installed.

My boat is a heavy alloy saltwater V hull 18ft cuddy cab.

The trim tabs went great. Should have put them on years ago like everyone told me.

25.1 - went very well after a bit of a shakey start.

When the boat was launched, at the ramp in maybe 6ft of water with the Elite FS on Medium Chirp frequency, the top half of the sonar screen was completely brown…. Never seen it do that before. Bottom half was normal. Weird.

So I switched to custom frequency 105khz and that fixed that issue…… hmmmmm….

After running for 20 minutes I thought what the heck - and changed back to Medium Chirp frequency and bingo, all good. Full screen normal image.

I think the sensitivity is improved as I needed to back it off a bit to declutter the screen. After that I got a great image in all depths and at speeds up to 25 knots, and the Bay was quite choppy, maybe 2- 3ft waves pushing against current. Never lost bottom once, depths up to 45ft (15m).

So the issue with the previous version software messing up TM150M and turning the image all blue when run in Medium Chirp mode has definitely been fixed.

As a bonus, after running the Suzuki DF115B for a few minutes, up pops a message on the FS saying Suzuki engine detected and App activated! Sure enough there is now a Suzuki App on the home page that takes you to a custom Suzuki dashboard that can be edited and customised to suit your preferences. This app is activated when the Lowrance display detects the Suzuki SMG4 digital gauge on the N2K network. So a nice little bonus!