Bug Alerts

NavNet 3D Garmin Autopilot N2K Communication

2011-02-05T20:25:55Z

I have a NavNet 3D system networked via NMEA 2000 with a Garmin GHP10 Autopilot system. The Garmin system does not see navigation data from the MFD12 unless I run the MFD12 installation wizard. The nav data transers fine after I run the installation wizard and I do not have to make any changes when I run it. I have to do this almost every time I power up the MFD12. Occationally it works without having to run installtion wizard, but not often.

Heading data transfer from the GHP10 system to the MFD12 works fine without running the installation wizard. I did have to specift the GHP10 as the heading data source for it to work reliably.

Can anyone help with the nav data transfer issue so that the autopilot can follow the MFD route without having to run the installation wizard? The two systems works great together when the data transfer works.

Update: I updated the Furuno firmware to the latest version (2.07) today and now it does not work even after running the installation wizard.

Garmin current predictions wrong in British Columbia

2010-12-28T20:31:30Z

The BC Boating Forum is reporting major errors -- ebbs shown as floods -- in current predictions for numerous passes. Hopefully the error is so big that many users will notice it (and Garmin will fix it quickly), because these passes have the strongest currents in all of North America:

http://www.cruising.bc.ca/boating_forum/index.php?topic=143.0

http://www.cruising.bc.ca

Lowrance HDS "not valid for area" issue

2010-11-21T17:29:29Z

I'm not sure this can be termed a bug, but some users might find it so. Apparently Lowrance has put some code in their latest software to discourage grey market sales outside the USA. It seems that if a unit meant for sale in the US is used in, say, New Zealand, a message "Not valid for Area" will blink on the screen, and nav units will default to Feet, miles, etc.

Here's a discussion by Kiwis trying to figure out what's going on:

http://www.fishing.net.nz/asp_forums/lowrance-hds-reports-not-valid-for-area_topic55743.html

And this video, though in French, is interesting, and has english comments:

http://www.youtube.com/watch?v=eWtFzv2s-mg

I think this issue only applies to HDS models with Insight U.S. charts included, but I'm not positive. I also think that Lowrance will let folks who buy such an HDS in the States use it overseas, but again I'm not positive.

Garmin AIS 600

2010-04-29T12:06:34Z

Does anyone know what the error message "01 PLL TX Unlocked" on a 600 AIS means. On start up, happy green "OK" LED. Happy Green "RX" blinking, On the first "TX" happy green, the "Waring" LED lights, followed by the "Error" LED. No happy "TX" after that. USB diagnostics only show the above error message. Unit is seeing AIS vessels in the area (at least class B).
N2K connected to 5212's, and the unit shows on the device list. Software is at 5.6. Good satellite reception. Inquiry was forwarded to Garmin engineering by tech support. There is somewhat of a shortage of docs in the box. wiring diagram only, and an inscrutable start up software disk. I will do a post on the %&*&^!* driver install. Tnx Bill Bishop

DSM300 sounder module problems?

2010-02-28T22:53:24Z

I have a client who is getting his 5th or 6th DSM sounder module within 12 weeks. The original unit (1 1/2 years old was spotty in operation. I replaced it under warranty, and this unit kept "falling asleep"(three blink red (high temp which did not exist)). I did the boot strap upgrades on the module, and E120's had current software .it was OK dockside, but would fail intermitantly during cruising. The Ray rep was called in and he replaced it with a new unit, and it failed immediately due to "cold solder joints. He replaced it with another new unit, and it failed due to cold solder joints. (I wasn't there, but thats what the rep said) a new unit is being tested under heat for 48 hours, and will be installed early next week. I hadn't seen the solder joint for almost two years, but the rep said this was ongoing until November 2009 in manufacturing. Symtoms are loss of bottom, blinking depth, DSM connection lost message, but screen stays blue, and may restore connection by itself.

Maretron GPS100 & GPS200 Variation issue

2010-02-18T22:15:49Z

Maretron's GPS receivers stopped outputting compass Variation data on 12/31/2009 when the existing World Magnetic Model ran out. It may cause issues with True Heading, Ground Wind, and other calculations. Firmware 2.2 updates the GPSs to WMM2010. More detail here:

http://www.panbo.com/archives/2010/02/a_world_magnetic_model_reminder_courtesy_maretron.html

Raystar 125 GPS substitution

2010-02-16T19:25:17Z

The same reliable installer who reported the Garmin AIS oddity (but who wants to remain anonymous) also reports that recently Raymarine has run out of the regular NMEA 0183 Raystar 125 GPS units and is substituting Airmar sensors with Raymarine labels. They work OK for positioning, COG, & SOG, he says, but attached Raymarine MFDs don't necessarily show a satellite skyview, HDOP, etc.

Garmin 4000 & 5000 series N2K AIS problem

2010-02-16T19:14:08Z

This is an oddball, but apparently a known problem. Some older 4- and 5000 Series MFDs may not see N2K AIS messages even though the device is recognized. In fact, it may only apply to Garmin's own VHF 300, a combo radio and AIS receiver, which will still get GPS off the network and put DSC messages on it. The symptom is not seeing AIS targets it should. The fix is sending it back to Garmin.

5212's with serial numbers lower than 159003090 are affected, along with 5208's lower than 157001659. Also 4212's lower than #155003882
and 4208s under #153004541.

Note, though, that the 5212 I've been long term testing is in the "affected" group, but has gotten N2K AIS fine from Simrad and Raymarine transponders (aside from lack of Class B static data message).

MaxSea Time Zero 1.8.1

2010-02-15T15:55:43Z

When starting MaxSea Time Zero 1.8.1 when one ore more MFDs are already running, the MFDs will lose sensor input (GPS, N2K, etc.). This has been confirmed on both the MFD/8 and MFD/12. After 2-11 minutes the MFD will frequently recover, but not in all cases.

MaxSea has reported that they are aware of the problem and working on a solution.

Raymarine SPX5 Sport Drive Safety Recall

2009-07-21T19:01:11Z

"We have identified a potential component problem with the SPX5 Sport Drive Pilot product which we have sold between February and July 2009. As a result the mechanical clutch assembly may fail, causing the steering of the vessel to lock in one direction, with a possible risk to the safety of the vessel and crew. Customers must stop using the products immediately and arrange de-installation and return to the retailer/dealer from whom it was purchased."

http://www.tradeonlytoday.com/home/498965-raymarine-issues-recall-of-sport-drive-pilot

Garmin Chart Card Problem

2009-06-05T10:53:31Z

Garmin is recalling all 2009 version g2 and g2 Vision Data Cards because at least a few show depths shallower than they really are. The problem apparently does not apply to charts build into plotters, just cards dated March, 2009. The Garmin FAQ is here.

Raymarine C-Wide and G-Series bug alert

2009-06-02T13:44:55Z

I doubt many boats are affected, but Raymarine has issued a bulletin for a bug that "only manifests itself in C-Series Widescreen and G-Series systems that meet ALL 3 of these conditions:

1. There is an external GPS sensor connected via SeaTalk to the display (such as the Raystar 125).
2. The datum is set to something other than WGS 1984.
3. The system has one of these software versions:
-C-Series Widescreen: v1.12 or v1.13
-G-Series GPM400: v2.25"

More info here.