DST800 does not show up in Raymarine setup

[roetter]

I had a faulty DST800 transducer. Just installed a brand new one. It appears to work. I get depth and temperature again. At anchor so no speed.

However, it does not show up in the setup, as the old broken one did. The old one gave errors in depth in shallow water or no reading less than 2 meters.

[smac999]

Does it show up in the nmea 2000 device list? Which mfd are you using?

[roetter]

2 Raymarine e125 two on a network, with 4 times I70 and 2 times 70 autopilot control heads. I always used the i70 for setting up my system. It still sees the ITC5 with the wind. But the new DST800 does not show up where the old one did. I just ran the latest Raymarine software update again, as I did a month ago, just in case, but still the same. It only sees the ITC5

[roetter]

Just tried again and now the DST 800 shows up. Then it disappeared again. Seems, once the MFDs have been on the network, the system can not see the DST800 anymore.. Shutting down the two MFDs and then powering up the system then using i70 setup and it works. That is no good to adjust the speed tables.

[roetter]

Did some more testing. Some of the things I said before were just coincidental.
Connected the old DST 800 - setup sees it every time.
Connect the new transducer - setup sees it after power up. Once I go into the speed table, edit a point and go back out of setup, it will not find the transducer again. Occasionally, disconnecting the backbone (blue) cable going to the transducer spur will make it work. However, the only reliable way is to power down and up the system.
If I just search for the transducer, then go back out and then search again, then it finds it every time. As soon as I go into Speed/Advanced/Cal Table/ Edit/ and edit a point, then go out - it will not find the DST 800 anymore. Even half a dozen searches does not bring it up. If I power down just the i70, then up again, then it will find the transducer again.

[tanglewood]

Welcome to N2K

These are just guesses, but might give you something to go on....

If you look at the labels on your two DST800s, are the SW revs different? That might be what's changed.

Another possibility is that some new PGN is being sent by the new DST that's confusing the E125 or some other device.

In my experience the only way to figure out these issues is with an analyzer of some sort, like Maretron's N2KAnalyze or Actisense's NMEAReader. Until you can see what sequence is sending things south, you are really poking in the dark.

You could try connecting the DST to only one display/config device to see if that is stable. You might then be able to get things configured such that they will work with the larger system.

Many devices also have the ability to turn certain PGNs on and off. You will need to right tools to do it, and I don't happen to know what they are for the DST, but would love to know if you find out since I have one that is also misbehaving in it's own unique way. Airmar might have a tool. Then you will just need to figure out which PC to N2K adapter it works with. The Actisense is common, but not universal.

Oh, do any of the Raymarine devices let yo see what PGNs a device is sending? If they do, you might look for differences between your two DSTs.

[roetter]

Thanks. I check the software versions. All my devices have just been updated to the latest software a month ago. I ran the update again today to see if the DST800 needs an update. I try Raymarine support or Airmar support.

[tanglewood]

Originally Posted by roetter

Thanks. I check the software versions. All my devices have just been updated to the latest software a month ago. I ran the update again today to see if the DST800 needs an update. I try Raymarine support or Airmar support.

Are you doing these updates via Raymarine? Does it update the DST? I would be surprised if it does.

[roetter]

I am using the Raymarine update package. I am not sure if the DST800 software is part of that. Probably not, but I ran it anyway to be sure I did not miss anything.

[dietervoegeli]

It is possible that it only transmits PGN with the boat in movement.

[offpist]

Originally Posted by dietervoegeli

It is possible that it only transmits PGN with the boat in movement.

No.. I have the DST800 and it transmits PGN also when not moving.


Do you happen to have an "Raymarine SeaTalk1 to SeaTalkng converter" in your system? We had a problem on the Seatalk1 network and this gave all kinds of problem om the SeatalkNG network including dropout of speed and depth. So if you have this converter, just try disconnecting it.

[jamesdavis]

Just be sure any NMEA cable runs you have are properly terminated at BOTH ENDS. Signal levels and noise margins can be shifted and improper if not.
This should be elementary for anyone who has done this before I would think.

[roetter]

Originally Posted by jamesdavis

Just be sure any NMEA cable runs you have are properly terminated at BOTH ENDS. Signal levels and noise margins can be shifted and improper if not.
This should be elementary for anyone who has done this before I would think.

All is properly terminated. There is no problem when I put the faulty transducer back on, except the depth is not working under 2.5m.

[lateral]

There is this, if you can find where to purchase/borrow/hire.
http://www.airmartechnology.com/uplo...es-tdt1000.pdf
Bet the price is eyewatering.

I have similar problems with turning on a Zeus mfd & it disabling the DST800.
Also, the DST800 boat speed has (off) ascribed to it in the mfd device List.
And it just doesn't show up in the tritons.
Also have a rx error.
Going over the the system device/connector, one by one.

How do I check the health of my NMEA 2000 cabling before powering my network? - Print View