TZT16F and Seakeeper Ride - no IP address

alphabradley

New member
Hi everyone,

I installed a Seakeeper Ride in my Regulator 34 this offseason. I followed all of the instructions from Furuno and Seakeeper. I installed the app and updated all of the MFDs with the latest software.

However, the MFD is not provisioning an IP address to the device. All of the settings on the hardware are correct.

I have tried to connect it via my HUB101 *and* a direct connection to the master MFD. Still, no IP address.

Has anyone experienced this? I had a similar problem when interfacing with my TimeZero software; originally, I had to force an IP address on the device to work. Magically, the DHCP worked later and I haven't had the problem since. The Furuno network is two TZT16F, a FLIR M364C, DFF-3D, and a DXT radar already onboard. Everything else is NMEA.

I'm going to experiment with connecting a laptop w/ a DHCP server onboard to see if the Seakeeper device is accepting not accepting DHCP addresses (which I guess is possible)

Any ideas?

Thanks in advance!
 
Last edited:
Have you followed all the steps in the SeaKeeper commissioning document?


Normally those that set the DHCP setting to ON in the Furuno service menu have no problems adding a Seakeeper Ride hotpage as long as the seakeeper device has newer software and configured as they require. I recommend the newest Furuno software be loaded in the TZT3 (v3.80)

1747693053208.png
1747693123540.png
 
Hi Johnny! Thanks for the reply. We've already updated to 3.8 on the TZTs and no luck. We swapped the control unit on the Seakeeper as well and no IP would provision. I'll keep digging...
 
The Furuno will refuse to let you create a hot page for the Ride system until you have loaded the ENC file in the service menu and the Ride system get an appropriate IP address on the bus. If it doesn't see the updated ride system, it won't offer the Icon. Ensure you don't have an old hub or something that causes any bottle necking. NO PLASTIC RJ45s on a boat. Everything needs to be shielded with metal RJ45s. It only takes one plastic RJ45 on the network to ruin your day.
 
having the same EXACT issue. have replaced ethernet cable etc. nothing...being told by the seakeeper dealer to buy a 5inch display dedicated to seakeeper.....frustrating
 
@alphabradley @CBBeaty
I have the Seakeeper Ride SW Module (V2024.2.0) sitting on my bench and working with my TZT10X (V25.11) and TZT19F (V3.80).
I'm waiting on their USB OTG cable to update my module so I can test Seakeeper's newest software to see if something changed.
Make sure both dip switches are off in the SW module (towards the numbers).
Make sure that the Seakeeper Ride system is powered up and online.
Make sure that the .enc file is installed in the TZT3 or TZTXL and that you have it set as one of your five in the Active Product Slot.

IMG_8976.jpgIMG_8977.jpgIMG_8978.jpg
 
@alphabradley @CBBeaty
I have the Seakeeper Ride SW Module (V2024.2.0) sitting on my bench and working with my TZT10X (V25.11) and TZT19F (V3.80).
I'm waiting on their USB OTG cable to update my module so I can test Seakeeper's newest software to see if something changed.
Make sure both dip switches are off in the SW module (towards the numbers).
Make sure that the Seakeeper Ride system is powered up and online.
Make sure that the .enc file is installed in the TZT3 or TZTXL and that you have it set as one of your five in the Active Product Slot.

View attachment 6404View attachment 6405View attachment 6406
Switches are set correctly. ENC file is visible and can be chosen in the Serivce/Utilities for 1 of the 5 preset blank app windows. Exit power off and back on and the SeakeeperRide app icon is NOT in the lower right of the home screen. Interestingly, Zipwakes app Icon is there but we didn't put it there, deleted it and it reappears on its own. No idea. You can't update the seakeeper ride module software without the TZT22X seeing it and giving it an IP address. Ordered the 5 inch display. It should not be this hard.
 
@Johnny Electron Correct.
@CBBeaty The ZipWake icon should not appear on it's own. That is a bug. Did you create a Seakeeper Ride page? On the home page, press the "+ Create New Page" and the Seakeeper Ride icon should be in there on the bottom right for you to make a page. I agree that your systems should not be this hard to complete. We have a lot of fully functional systems out there. Two just this week that I'm invloved with, one of our Brand Ambassadors that we just visited with along with another vessel that is being delivered next week.
 
Switches are set correctly. ENC file is visible and can be chosen in the Serivce/Utilities for 1 of the 5 preset blank app windows. Exit power off and back on and the SeakeeperRide app icon is NOT in the lower right of the home screen. Interestingly, Zipwakes app Icon is there but we didn't put it there, deleted it and it reappears on its own. No idea. You can't update the seakeeper ride module software without the TZT22X seeing it and giving it an IP address. Ordered the 5 inch display. It should not be this hard.
Actually, there is a way to update the software on the Seakeeper Ride without a display or active IP. I'll be doing this tomorrow with the latest release (seakeeper-ridesm-2025.5.0.swu), which I downloaded from the below URL:


Note, you'll need a USB device, formatted FAT32, and a USB -> microUSB connector that supports OTG. There are a lot of different products on Amazon that support it -- I'm using https://www.amazon.com/dp/B01M098EAG

I'll report back tomorrow based on what happens.
 
Got it working!

I ultimately had to provision the unit via a Simrad display. The Seakeeper ride would not connect to my furunos, even after trying to upgrade to the 2025 software via the USB port without the Furuno identifying the device.

When I attached the Simrad, the unit still had the 2023 software on. I updated the software while attached to the Simrad, disconnected and rewired the unit, changed the DIP switches, and rebooted everything. Upon reboot, it got an IP address in line with the Furuno network subnet and the Furuno MFDs were able to see the device.

I had a brand new, straight from the box Seakeeper controller in case I needed a backup. We tried to follow the Furuno and Seakeeper instructions again, and they did not work. We repeated with the above approach and everything was fine.

There has to be a way to force a software update on the Seakeeper ride without the Ride app connected. Given the instructions from Seakeeper and Furuno, the MFDs should have been able to provision an IP address so the Seakeeper interface would allow for an update.

So, if you are facing this AND have access to a comparable MFD, do the software update via your non-Furuno MFD, reset the switches, and voila. It's clear that the 2023 software that comes out-of-the-box from Seakeeper will not work within the instructions given by both firms.

Both Furuno MFDs were already running 3.8.0 and all other wiring was correct. I was able to force an IP address onto the Seakeeper via a DHCP server running on a laptop. I did NOT try forcing that IP into the Furuno scheme/subnet, which would have identified some sort of provisioning issue.

Good luck everyone.
 
Last edited:
Glad to hear you got it sorted out. I wish everyone was like us and tried to send out equipment with current software revisions. It makes things easier on everyone.
 
Back
Top