VX2 port 2 out drops out

[Anonymous]

I have finally got my VX to "talk" to my Raymarine autopilot but randomly, the output from the VX2 port 2 just drops out. Everything is OK on the display, but I get an error from the autopilot that nav data is missing.

I have to reboot the VX2 for it come back.

The only load on the port is a single connection to a multiplexer (single listener). Is this a known/addressable issue?

 

[Johnny Electron]

Yes, it seems to be a known issue with Raymarine. This happens with many brands of plotters, not just Furuno. You can find other postings about similar problems with the older pilot(s). It has nothing to do with your Vx2 output but a NMEA level mismatch because the Raymarine pilot isn't clearly using RS422 NMEA 0183. Most customers fix the problems by connecting to the 0183 connection at the back of the Raymarine control head (if there is one) or purchasing the Raymarine NMEA 0183 to Seatalk converter. The converter is RS422 NMEA 0183 and interfaces correctly. The issue always seems to be when connecting direct to many of the Raymarine pilot processors. The input appears to be at a pseudo RS232 signal level. They normally don't work or work intermittently when connected to standard RS422 NMEA 0183 plotter. There could also be a chance it has to do with your multiplexer that you are using. It could be that at times you are pushing more data than it can handle and it is dropping or truncating data. Even with a proper multiplexer setup, you still might need to purchase the Raymarine 0183 to Seatalk converter.

 

[Anonymous]

Nope, it's not the Raymarine. I gave up on the internal NMEA ports on the Raymarine course computer(s) long ago.
I have the VX2 output going into a Shipmodul MiniPlex-2E. The output from the MUX goes to the Raymarine via a NMEA0183-seatalkNG converter (which seems solid). In parallel to this output, it's also going to a Furuno FCV-585 for lat/long and temp - which also drops out.

MUX is running at about 2% of capacity. I'll try checking on the computer as to whether the signal is still being received from the VX2 and sent out over ethernet.

I can try bypassing the MUX.

 

[Johnny Electron]

Yes, I recommend going from the Vx2 directly to the 0183 to seatalk converter or directly to the fcv585 for testing. Ensure you have no more than 7 NMEA sentences turned on at 4800 baud. If still dropping then your unit needs repair. Normally a port works or doesn't. Intermittent is rare, unless you select too many sentences and induce your own problem. The multiplexer would be more likely than a data port with single listener going bad.

 

[Anonymous]

So I've checked my connections and the FCV-585 is directly connected to the output of the VX2 at the MUX input and is dropping out also (so it's not the MUX or output to the RM autopilot). I've tried connecting shield (which wasn't) but problems is still happening.

Are there any diags I can run which checks the serial ports?

 

[Anonymous]

The only other thing you can try is a loop-back test. Connect port 2 white to port 2 yellow and port 2 black to port 2 green. Once you have that connection done, go to the port 2 setup in the vx2 and use the port monitor to see what data is coming in. You'll probably have to clear the screen a couple times to see if the data actually stops transmitting. Other than that, the system will have to go to our repairs section for evaluation.