Raymarine Seatalk - STng network help diagnose please

[PegasusPete]

This system did work, now doesn't for no apparent reason i.e. no recent changes.
I'm hoping the attached PDF explains and can be easily read on your device.
I think the Seatalk - STng Converter might be the problem.
Anybody got any diagnosis ideas?
Have asked raymarine and awaiting a response, thought I'd ask here as well.
Thanks

[Snore]

What doesn’t work? If you have blanking caps, segment the system. Start with MFD and add components until you find the one that causes issues.

[Tehani]

Originally Posted by PegasusPete

This system did work, now doesn't for no apparent reason i.e. no recent changes.
I'm hoping the attached PDF explains and can be easily read on your device.
I think the Seatalk - STng Converter might be the problem.
Anybody got any diagnosis ideas?
Have asked raymarine and awaiting a response, thought I'd ask here as well.
Thanks

It seems simple. In your Pegasus diagram you don't see SeatalkNG network power connection.

https://forums.ybw.com/index.php?thr...4/post-5767934

Look, it's the red and black wire. Connect it to the SeaTalk NG 5-way distributor on the right in your schematic. There you have free positions.

[PegasusPete]

Thanks Snore & Tahani,

Found the segment the system advice on Raymarine site after posting here.
Was thinking of starting with MFD and adding STng items one by one, problem is I won't get that far without buying another 3 way splitter block.
Then I add the Seatalk1 - STng converter and add Seatalk1 items one by one??

Power supply I haven't got my head around, yet.
MDF, AIS, Type 100 Course Comp all have their own power input.
I've found Seatalk1 cable between Repeater/ST60 Multi display and ST60 Tridata has 12v spliced into it.
If it needs power into the STng cable why did it work before?
Taking out one of the Seatalk1 cables drops power to p70s AP control head and i60 Wind, both connected via STng.

Appreciate your help, THANKYOU

[PegasusPete]

Updated my diagram
Tehani, appears the network is getting power from the Seatalk1 side of things.
Supplying power to the STng side as well would mean 2 power inputs.
Is that a good idea?
Think I read on Raymarine that STng items get power from the Seatalk - STng Converter.

[Tehani]

Originally Posted by PegasusPete

Updated my diagram
Tehani, appears the network is getting power from the Seatalk1 side of things.
Supplying power to the STng side as well would mean 2 power inputs.
Is that a good idea?
Think I read on Raymarine that STng items get power from the Seatalk - STng Converter.

You must give power on both sides.
They are isolated networks.

His new diadram is also wrong. The Seatalk network takes power from the autopilot connection and it is not necessary to put it on the outside. But still no power to the SeatalkNG network.

[PegasusPete]

Tehani,
You may well be right, but why did it work with power only from the Seatalk1 side??

[Squanderbucks]

Think about it this way. Forget about the Seatalk 1 as a primary system. Just as an add on to the Seatalk ng. Take all the Seatalk 1 stuff off the system. Setup your NG backbone and power connection. Get all NG stuff working.
Add the Seatalk 1 anywhere in the backbone or at the end ( with no power cable ). If at end put the terminator in its end plug(white).

Be sure and change the autopilot to connect via drop cable and NOT supply power to the backbone anywhere.

Powering the backbone cable from the autopilot is meant for those with a very limited network with nothing much more than a couple of autopilot heads and it’s accessories.

[cmichaux]

This sounds simple but we had the same problem, "working fine then stopped" and after a lot of testing it was the order in which we powered everything up. Works perfect now.

[j.g.evans]

I had SeaTalkng (NEMA 2000 with different connectors) instruments with old ST50 instruments in network. This did not work. Adding one ST60 instrument made all work. Raymarine had no answer why.

[Quebramar]

Squander bucks is right. You should avoid multiple power supply sources yet ensure it is distributed to all components.
I also changed my hybrid (ST1-STNG) setup when I changed the AP. The old AP 100 did provide power to ST1 (all instruments are on ST60) and then connected to Axiom etc through same ST1-STNG connector.
I now added a dedicated STNG backbone power source with the new AP, so it is the backbone that supplies every item that requires it and the option on the new AP to provide supply is off.
Switching power on the backbone only starts up the instruments, the AP and the MFD/radar have their own switches, as well as AIS and VHF. Works fine.

[Tehani]

Originally Posted by PegasusPete

Updated my diagram
Tehani, appears the network is getting power from the Seatalk1 side of things.
Supplying power to the STng side as well would mean 2 power inputs.
Is that a good idea?
Think I read on Raymarine that STng items get power from the Seatalk - STng Converter.

Certain. I have checked it right now. The Seatalk to SeatalkNG converter bridges the power between Seatalk and SeatalkNG.

I have powered only the Seatalk section, and SeatalkNG is still working. It doesn't seem too orthodox, but it is.

[Tehani]

Originally Posted by PegasusPete

Tehani,
You may well be right, but why did it work with power only from the Seatalk1 side??

Two more things:
1- It is normal that your radio does not receive the position, since the pilot probably does not translate that from Seatalk to NMEA0183. In any case, you should connect it to the NMEA output of the AP since in the diagram it looks like the radio is connected to the NMEA input of the AP.

2- Have the MFD display the list of SeatalkNG devices. In addition to E7, you should see the i60, p70s, the AIS 700, and the Seatalk to StkNG converter.

If the latter does not appear in the list, it is normal that there is no communication between the two buses.

[smac999]

Originally Posted by Tehani

It seems simple. In your Pegasus diagram you don't see SeatalkNG network power connection.

https://forums.ybw.com/index.php?thr...4/post-5767934

Look, it's the red and black wire. Connect it to the SeaTalk NG 5-way distributor on the right in your schematic. There you have free positions.

His screens are on so the backbone has power. Probably comming from the pilot cpu. The st to stng converter passes power so only one power can be put into the whole st / stng system.

You are going to have to separate the system out to find the problem. I would start by disconnecting the yellow wire beteeen the 2 systems and temporary put power into the stng backbone abd see if each works by itself.

The st to stng converter has an led light on it when it has power.

[ric14854]

The NG side of business needs proper terminating resistors on the two ends of the trunk. That would be the locations you labeled cap (as long as none of the devices have internal terminating resistor). I think that's the blue cap although I've seen some that are black top on internet. I've seen systems run without terminating resistor work and then stop working as you are experiencing. As well the AIS is seatalk ng device so not really using the stng conversion function.