Originally Posted by alex2035
Troubleshoot it yourself if you feel audacious. At least the DB9 /data cable part.
Look at the end of the C 120 NMEA DATA cable (the exposed cables), BROWN and GREEN should be wired together , AND this should connect to PIN 5 of the DB9 connector (follow cable and unscrew the caps to reveal, or measure from the outside if moulded), the tiny numbers are embedded in front of connector, PIN 5 is one end of top row (NMEA BOX operating manual page 18 has a diagram).
Then verify YELLOW cable from C120 NMEA DATA Cable goes to PIN 2 on DB9
Finally, verify WHITE cable from same goes to PIN 3 on DB9
For some reason and from my experience, all this cabling should be done, because even if you only need to "send" waypoints to C120 it will refuse to do it until you connect ins and outs as told.
Once you see this conditions met, try to do a transfer but I suggest you do not have any other of the connected elements switched on, leave them away for the transfer. Have C120 and OPCN up running only and do your trial. it should work. remember first prepare C120 to receive then put OCPN to the work.
So I did what you said and checked all the connections and I got it to work.
I realized when checking all the wires coming out of the AIS650 and C120 that the TX from the DB9 on my laptop
was connected to the NMEA OUT on the C120. I instead connected it to NMEA IN, configured the NMEA port to 4800 on the C120, put the C120 in to NMEA receive, and presto, routes and waypoints transfer over cleanly with names intact, etc. So long as other devices such as the AIS
unit are powered down and not talking on the NMEA C120 Input port.
This leaves me with a bit of a confusion on how to operationalize this.
I have now two laptop
1. a DB9 cable with 38400 baud connection to the single
NMEA port on the c120 to which is also connected a 650 AIS, a backup Garmin
640 chart plotter, VHF
. RX on the DB9 goes to NMEA INPUT on the C120.
2. A cable to the NMEA input on the interface box at 4800 baud
I was getting in openCPN AIS data from cable 1 and Seatalk
data from cable 3.
Concerning cable 1, the RX on the laptop com port is going to the INPUT wire on the NMEA C120. If I also send the TX from the same com port to the INPUT wire on the NMEA C120 and reconfigure the port in openCPN and C120 to 4800 baud and turn off the AIS unit then I can send routes over cable 1 from openCPN. I confirmed this by just putting a jumper across the RX and TX of the DB9 connector that is connected to the Com to USB connector cable so that the TX went to the INPUT on the C120.
Obviously doing it thisway is a bit of a kludge.
I think I will never be able to avoid reconfiguring NMEA on the C120 to 4800 baud and disconnecting AIS by doing so and turning off the AIS unit so it isn't talking on the C120 NMEA input.
But I suppose I could run a third com cable and com port configured at 4800 baud in device manager and in openCPN taking TX to the INPUT on the C120. That way I wouldn't have to mess with cable 1 above.
Does this make sense??
Thanks for any thoughts you may have on how to make this more operational.