Question for the Garmin Autopilot Boys?

[Skybolt]

6.20 installed GMN autodetect which is what hosed everything up.

That's what is confusing, why would it? Or I should say how did it?

 

[Skybolt]

6.20 installed GMN autodetect which is what hosed everything up.

Tom, curious if you tried booting the GMN fully and first, then turning on the Fusion?

I can't see the difference between auto finding the GMN and setting it manually.

I won't be able to try this out for a few weeks when the boat goes back in the water. Coming out this Friday for the spring service, still under a roof until then.

 

[ttmott]

Tom, curious if you tried booting the GMN fully and first, then turning on the Fusion?

I can't see the difference between auto finding the GMN and setting it manually.

I won't be able to try this out for a few weeks when the boat goes back in the water. Coming out this Friday for the spring service, still under a roof until then.

We discussed this in some other postings. When Fusion does autodetect and connect to the GMN it disables other network features. Before the autodetect there were no issues in configurations. I'll try to find where we discussed all of this.

 

[Skybolt]

We discussed this in some other postings. When Fusion does autodetect and connect to the GMN it disables other network features. Before the autodetect there were no issues in configurations. I'll try to find where we discussed all of this.

I was looking for that as well and couldn't find it and why I asked the question again. I think it may be pages back in this thread or the one you posted about firmware?

 

[alnav]

We discussed this in some other postings. When Fusion does autodetect and connect to the GMN it disables other network features. Before the autodetect there were no issues in configurations. I'll try to find where we discussed all of this.

The discussion is in a thread called "Stereo Upgrade".
Here's the explanation from the current Fusion manual:

 

[Skybolt]

The discussion is in a thread called "Stereo Upgrade".
Here's the explanation from the current Fusion manual:
View attachment 162202

So they purposely shut down the wifi piece when connect to t he GMN. So I guess that means the artwork will still work but not the fusion link app unless paired with the GMN. Stupid. So now that piece of the puzzle gets turned off so the app will still work.

Garmin needs to realize their plotters are not the be all end all of a boats network. Who want's to keep plotters on to be able to play music ... It's like thinking you must have the GXM 54 to use Sirius, guess they are now forcing that issue to a point.

EDIT: Here is the link starting a page 4. https://clubsearay.com/index.php?threads/stereo-upgrade.112667/page-4

 

[Skybolt]

I contacted Garmin Tech Support about getting an older FW rev and they said they don't exist. Once a new rev is released the old one becomes unavailable to the public.

I also gave them a use case for how we use the radio/MFD/network and he logged a case on it. Probably won't go anywhere but at least I made him understand there are more boats around then just center consoles.

 

[ttmott]

I contacted Garmin Tech Support about getting an older FW rev and they said they don't exist. Once a new rev is released the old one becomes unavailable to the public.

I also gave them a use case for how we use the radio/MFD/network and he logged a case on it. Probably won't go anywhere but at least I made him understand there are more boats around then just center consoles.

I did the same....

 

[Skybolt]

I did the same....

I do get why they don't allow access to the older FW. Makes no sense.

I did put in a request for the 6.10 FW version files. we'll see where that goes.

 

[ttmott]

I do get why they don't allow access to the older FW. Makes no sense.

I did put in a request for the 6.10 FW version files. we'll see where that goes.

It's a big deal to write and test code to back out of a revision. An you can't simple reload a previous revision because of the changes in a later revision. They won't do that based upon a couple of squawks.

 

[Skybolt]

It's a big deal to write and test code to back out of a revision. An you can't simple reload a previous revision because of the changes in a later revision. They won't do that based upon a couple of squawks.

It's not that big of a deal to provide the previous version of FW, I do this all of the time for various reasons. I am currently at 5.7 so going to 6.1 should be a issue at all. Even going back a rev shouldn't be an issue, the hardware is still the same.

I don't expect Garmin to change anything, just provide me with the previous version FW. I don't see the issue.

 

[ttmott]

It's not that big of a deal to provide the previous version of FW, I do this all of the time for various reasons. I am currently at 5.7 so going to 6.1 should be a issue at all. Even going back a rev shouldn't be an issue, the hardware is still the same.

I don't expect Garmin to change anything, just provide me with the previous version FW. I don't see the issue.

The previous version will not know nor be able to deal with changes and configurations made by a later version. A revision always has all previous changes to a baseline so it can build configuration regardless of the previous revision the user last installed. You can jump from 5.10 to 6.20 only because the latest has all the previous. The previous obviously can't have the latest. The only way would be to wipe the FW and start from scratch.

 

[Skybolt]

The previous version will not know nor be able to deal with changes and configurations made by a later version. A revision always has all previous changes to a baseline so it can build configuration regardless of the previous revision the user last installed. You can jump from 5.10 to 6.20 only because the latest has all the previous. The previous obviously can't have the latest. The only way would be to wipe the FW and start from scratch.

Tom I fully understand how this works. I asked for the previous version 6.10 because I am at 5.70. That said, unless the bootloarder or database (not applicable here) is changed between versions you should be able to down grade the FW. Like I said I do this a lot in trouble shooting versions in FW in communications platforms for NOC's hardware. I doubt a Fusion Stereo is as complicated as that and should have no issues going back a rev.

 

[ttmott]

Tom I fully understand how this works. I asked for the previous version 6.10 because I am at 5.70. That said, unless the bootloarder or database (not applicable here) is changed between versions you should be able to down grade the FW. Like I said I do this a lot in trouble shooting versions in FW in communications platforms for NOC's hardware. I doubt a Fusion Stereo is as complicated as that and should have no issues going back a rev.

I had thought you already moved to 6.20.....

 

[Smashpjp]

I just pulled my fusion radio off the Garmin Wifi and put it on the boat Wifi pep 12v router I have on the boat. Radio connected via nmea 2000 is good enough. I explored tweaking the networking and isolating networks and vlans to merge the networks with some layer 2 tricks, but eventually decided not to.

Given Garmins track ransomware record and device security, (Plus I ran a port scan on the MFD) keeping that thing away from any internet access is the safest bet. Sound like they added more lockdown for people that figured out a workaround

 

[ttmott]

I just pulled my fusion radio off the Garmin Wifi and put it on the boat Wifi pep 12v router I have on the boat. Radio connected via nmea 2000 is good enough. I explored tweaking the networking and isolating networks and vlans to merge the networks with some layer 2 tricks, but eventually decided not to.

Given Garmins track ransomware record and device security, (Plus I ran a port scan on the MFD) keeping that thing away from any internet access is the safest bet. Sound like they added more lockdown for people that figured out a workaround

Good points but it is infuriating that when you purchase a product for it's features and some of those features are deleted in subsequent mandatory FW revisions. And, it's not just this issue with their Fusion products the intrusion extends to the other Garmin products on the boat. If it's a vulnerability or security issue then fix that - don't take the easy road and delete features.
I have my MS RA770 configured with WiFi to my smart phone, connected to the boat's NMEA 2000 and (it was) connected to the Garmin Marine Network (ethernet).
The WiFi enabled streaming and remote control (via Fusion App) of the system from a distance with my smart phone.
The NMEA 2000 enabled MFD and wired remote control of the system.
The GMN enabled Sirius artwork and other control through the MFD's.

I've had to disconnect the system from the GMN to retain WiFi which is more important to me.

 

[Skybolt]

Garmin did this to make it easier to support the GXM54 and the new crowd of center consoles that need to make the MFD the center operating center of the boat, primarily for turning lights on/off etc. So they just leave the MFD on all of the time while on the boat.

Makes no sense to me why Garmin is catering to only new boats and has disregarded the existing clientele in their use case that Garmin created and to @ttmott Tom's point, has now abandoned.

Garmin's tech-support said after our conversation, that I should not update to the latest FW going forward.

 

[alnav]

Tried updating my units to the 35.10v yesterday. What a cluster. Both my 8616 and my 1222 ended up with the "recovery loader ready" message on the screen. I then had to remove each from the network and power down to get them to load. The 1222 still won't load so I will have to install from a sd card per Garmin. I may skip it because there isn't anything useful in this update. I was hoping for some changes to the TD 50 but nada. Therefor I would recommend skipping this update until they fix the deployment.

I updated today. I always use an SD card after early problems with AC. Only took 25 minutes for 3 MFD's, GPS and radar to update and reboot.