I've been sitting on this issue for about a year hoping for a fix from Icom, but nothing seems forthcoming, so it's time to post anyway. I prefer to post problems along with their solutions, but most of the time that's not possible. At a bare minimum, I try to give the vendor ample time to respond.
The bottom line is that I can't recommend anything except the simplest version of the M506 with no N2K and no AIS since the N2K interface is fundamentally broken.
The M506 is one of Icom's newest marine VHF radios and is available in several different configuration. They choices are:
VHF, No NMEA 2000, No AIS Receiver
VHF, NMEA 2000, No AIS Receiver
VHF, NMEA 2000, Receiver
I picked the model with NMEA 2000, but no AIS. My primary navigation data was all on N2K at the time so that made sense. The VHF could pick up GPS info from N2K enabling DSC emergency calling, and it could transmit incoming DSC alerts to my charting software to show the location of a distress call. These are all important safety features. Below is a picture of two of them side by side on my overhead dash.
|Two side-by-side M506 VHFs|
As radios go, these are really, really good. Incredible clarity, noise cancellation, the ability to play back recent reception, etc. I've been very happy with Icom radios, and these are no exception, except for the N2K interface on the M506. That's a disaster.
The first sign of trouble was that when getting underway, I would power on all sorts of things, and within a few seconds alarms would be going off on other devices indicating a loss of GPS signal. The errors would clear on their own and not recur until the next time I got underway. It took me quite a while to figure out that it was the VHFs that were causing it.
After many hours of traces and decoding messages, I finally saw what was happening. The twist is that it takes two M506s on the same N2K bus to cause the problem. Each one stimulates the bug in the other.
For those interested, here's what happens. Otherwise skip over this numbered section:
- VHF 1 powers on.
- To figure out what GPSs are on the N2K bus, the M506 sends out a broadcast request for the GPS message. Devices that can send that message do so, and other devices decline. Through this, the M506 figures out what GPSs are available, or so it thinks.
- VHF 2 powers on
- VHF 2 sends out the same broadcast request for the GPS message.
- VHF 1, hearing the request, responds with the GPS message. This is where the train skips the tracks. The VHF is a VHF, not a GPS. The GPS message it sends contains blank GPS information, but it still sends the message.
- VHF 2 hears the response from VHF 1 and concludes that it's a valid GPS source even though it isn't.
- Other devices on the network also hear the GPS message from VHF 1, think it is a higher priority GPS than the one they are currently using, and dutifully switch to the higher priority GPS. But the joke's on them because the GPS message from VHF 1 was blank, and it doesn't send any more if them.
- Other devices finally figure out that there is no good GPS data coming from VHF 1 (duh) and switch back to the GPS they were using before. But this disruption is enough to set off alarms on the AIS transceiver and Coastal Explorer.
- Now, just to add insult to injury, VHF 1 sees that the bus has reconfigured when VHF 2 powered on, and it once again sends out its broadcast request for GPS messages. VHF 2 hears the request and responds with a blank GPS message just as VHF 1 did earlier. Everything blinks and alarms again, then finally settles down.
- Because both VHFs have sent out this silly GPS message, everyone else on the bus thinks they are a valid GPS sources. If you look through the menus in Coastal Explorer, the Furuno NavPilot, or either of the VHFs, they all list the M506s as possible and valid GPS sources even though they clearly are not. How messed up is that?
Demonstrating the problem is very simple. All you need are two M506s on the same N2K bus. Power both on, then work through the menus to select which GPS you want the VHF to use. On each you will see the other M506 as an eligible GPS source, when of course it isn't.
|M506 main screen|
|Page to select N2K sources for GPS and AIS|
|How can the M506 be a GPS source when it's a VHF?|
But wait, there is more. Look back two pictures and you will see where you can select which AIS source you want the M506 is display on its own screen. Well, that has the exact same problem. Both my VHFs show the other as a valid and eligible AIS source even though neither of them has AIS.
So, great VHF, but don't waste your money on anything but the simplest, 0183 version of the product.
In closing, let me also add that I have updated both VHFs to the latest FW (V1.004). That helped with some other problems, but does not fix any of what I have reported. Icom also provided me with V1.005 to try, but no joy. It didn't address the issues. So don't waste your time and money sending your M506 back to Icom for updates - at least not at this time because they don't fix these problems.
[Update as of 24-Feb-2017]
Last fall (2016) ICOM came out with new firmware for the M506, but it doesn't fix the problems reported here. The new Firmware is V1.1 for the main VHF, and V1.006 for the UX-232 module which is the NMEA 2000 interface.
And last summer (2016) I discovered that having two M506 VHFs on the same N2K network isn't the only way to stimulate the problem. A single M506 plus a Furuno TZT2 chart plotter does it too. Check out the photo below where the TZT2 seems to think that the M506 is a valid data source for all sorts of crazy data. Drift, pitch and roll, rudder, rate of turn, atmospheric pressure? Really?