TZT13XL NMEA 2000 Problems with Multiple MFD's

[mbell20688]

Hello. I think I discovered a problem with NMEA 2000 PGN output while using multiple TZT13XL MFD's. I bought a NMEA 2000 bus analyzer to help understand the symptoms I was seeing. While operating a single MFD the water depth PGN is sent reliably once per second. When a second MFD is booted the same PGN is output 3-5 times at one second intervals, and then is not output for 5-15 seconds. The non-output periods are shorter if all other PGN outputs from the MFD are turned off, but there are about 5 second intervals without water depth PGN outputs. I log these NMEA 2000 depth messages for use by others, so reliable depth PGN messages are important.

The transducer is connected to one MFD, and that is the only device that sends these PGNs. NMEA 2000 bus voltages and terminations are normal and bus loading never exceeds 8-10%. Other devices on the NMEA 2000 bus have no effect on this, and operating the DRS6ANXT radar also has no effect. I have data log files if that would be helpful.

 

[TheReaper]

Are both TZT13X displays connected to NMEA2000 AND Ethernet? If so, Go to Settings-Initial Setup-Data Sensors-Sensor List and see if the IP addresses are the same for both TZT13Xs...they should not be. If they are, master reset the chart slave (ensure it is the only one on and not connected to Internet at the time. Lastly, ensure that software for both is v25.11

 

[mbell20688]

Thanks for your comment. Yes, both TZT13X MFDs are connected to NMEA 2000 and the ethernet. IP addresses are different for them, as are NMEA 2000 device and system instances. The water depth PGN only came from the MFD that has the transducer connected, but just to be sure I cleared all cases of two sources for any given PGN containing data. Still have the problem.

I really suspect a latent software problem is the cause of this. I talked to Furuno tech support in Camas today, and sent log files of NMEA 2000 data both with ethernet connected and not connected. They said they will forward the data on to developers in another location, and I don't expect a response before next week.

Again, thanks for your comment.