Losing depth on TZTBBX

[Wdeertz]

While underway today in a shallow area with a silty bottom I lost my depth reading from the Airmar DST200 n2k sensor. Nothing unusual here given the silty bottom the sensor wasn’t getting a signal bounced back. After a short while the DST200 started reporting the depth again which I could see on my RD33 screen, however my TZTBBX and TZT2BB both continued to show no depth reading (“- -“). I went into the settings screen on both the TZTBBX and TZT2BB data sources and the DST200 wasn’t showing as being available. I know the DST200 was putting data on the n2k network as it was showing a proper depth on the RD33 screen. I tried rebooting both TZTBBX/TZT2BB and the depth still didn’t show up. Only after I rebooted the entire n2k network did the DST200 show up again on TZTBBX/TZT2BB.

Is this normal behavior for both of these devices to not recognize n2k sensors that reappear on the network?

 

[Wdeertz]

Anyone experience this type of behavior? A software bug?

 

[Kraken]

If the DST200 is not being shown on your sensor list in the TZT then it is an issue with the NMEA2000 bus. If it is being shown bright white on the sensor list then go into data sources and make sure the DST200 is selected for depth

 

[Wdeertz]

If the DST200 is not being shown on your sensor list in the TZT then it is an issue with the NMEA2000 bus. If it is being shown bright white on the sensor list then go into data sources and make sure the DST200 is selected for depth

But why did my RD33 properly display the sensor data. To me that implies the DST200 was outputting data on the N2k network.

 

[Kraken]

The RD33 may be seeing data from the DST2000. If the TZT is not receiving the data from the DST200 then check the connection from the TZT to the backbone. If the DST200 shows up bright white on the sensor list in the TZT then make sure under data sources that you have the correct sensor selected for depth