easyvictor
Newbie
Hi all. I have a boat with a Furuno NavNet3D system on it. For those not familiar, it's an ethernet based proprietary protocol (but the chartplotter can interface with older NMEA 0183/2000 sensors). The idea is that you can connect multiple displays, radar, and PCs to this ethernet network and they all talk.
I wanted to wire this NavNet3D protocol into my boat's WiFi network, so that my laptop on the network could display all this data wherever I am on the boat. According to Furuno, this isn't supported, you need to hard wire in your PC directly to the chartplotter. Being somewhat computer savvy, I knew it should be possible, because ethernet packets are ethernet packets. It shouldn't matter if it's over wireless or wired connections. I set out to do this, and I did, fairly easily. This post is mostly an "FYI" for those with similar installations and want the same capability I did.
I found the beginnings of a discussion on this topic over at Furuno Forums:
Furuno USA Community • View topic - NN3D & Internet
It showed that other people did have wifi working with their NN3D systems. But in those cases, the wifi router was only used as an "dumb" access point, essentially just putting the NN3D network into WiFi. The extra wrinkle that I wanted to solve was getting the NN3D protocol to work on an existing boat network that included a router and internet access (via a Wifi booster). The problem here is that on this existing setup, similar to a home WiFi network, the WiFi router acts as a router and as a DHCP server, giving out IP addresses to everyone that connects--and the NN3D chartplotter ALSO acts as a DHCP server, because it expects devices to be connected directly to it, and they need an IP address assigned. And you simply can't have two DHCP servers on one network.
My solution was the following:
- Leave the regular home router as the network's router and DHCP server
- Connect the NN3D network to this router
- Turn OFF the DCHP server on the NN3D chartplotter (Master: OFF)
- Set the IP subnet of the router to match the NN3D (172.31.X.X)
This way, all my devices are on the regular boat network, with internet access (assuming my booster is connected to the marina wifi, etc), and they are also able to see all the NN3D data including radar overlays, via TZ Navigator software for PC. Perfection!
If you don't care about wiring this into an existing wifi network, and just want NavNet over Wifi, you simply configure the router as an access point (NOT a router) and connect it to the NN3D ethernet wire. Then if you connect your PC to that wifi signal, you will also have NN3D data.
See the linked thread for more technical details or feel free to ask any questions here. I was getting too technical for Furuno so they locked my thread.
I wanted to wire this NavNet3D protocol into my boat's WiFi network, so that my laptop on the network could display all this data wherever I am on the boat. According to Furuno, this isn't supported, you need to hard wire in your PC directly to the chartplotter. Being somewhat computer savvy, I knew it should be possible, because ethernet packets are ethernet packets. It shouldn't matter if it's over wireless or wired connections. I set out to do this, and I did, fairly easily. This post is mostly an "FYI" for those with similar installations and want the same capability I did.
I found the beginnings of a discussion on this topic over at Furuno Forums:
Furuno USA Community • View topic - NN3D & Internet
It showed that other people did have wifi working with their NN3D systems. But in those cases, the wifi router was only used as an "dumb" access point, essentially just putting the NN3D network into WiFi. The extra wrinkle that I wanted to solve was getting the NN3D protocol to work on an existing boat network that included a router and internet access (via a Wifi booster). The problem here is that on this existing setup, similar to a home WiFi network, the WiFi router acts as a router and as a DHCP server, giving out IP addresses to everyone that connects--and the NN3D chartplotter ALSO acts as a DHCP server, because it expects devices to be connected directly to it, and they need an IP address assigned. And you simply can't have two DHCP servers on one network.
My solution was the following:
- Leave the regular home router as the network's router and DHCP server
- Connect the NN3D network to this router
- Turn OFF the DCHP server on the NN3D chartplotter (Master: OFF)
- Set the IP subnet of the router to match the NN3D (172.31.X.X)
This way, all my devices are on the regular boat network, with internet access (assuming my booster is connected to the marina wifi, etc), and they are also able to see all the NN3D data including radar overlays, via TZ Navigator software for PC. Perfection!
If you don't care about wiring this into an existing wifi network, and just want NavNet over Wifi, you simply configure the router as an access point (NOT a router) and connect it to the NN3D ethernet wire. Then if you connect your PC to that wifi signal, you will also have NN3D data.
See the linked thread for more technical details or feel free to ask any questions here. I was getting too technical for Furuno so they locked my thread.