RC631 Plus chart plotter = Says Raymarine on boot - V3.2
ST6001+ Autopilot head
GPS Head not sure which one but is original

At companionway
ST60 Wind
ST60 Depth
ST 60 Speed

Questions:
First the RL70 and RC631 are connected via seatalk and HSB2. both work fine independently, however, I believe that these two units should be able to share chart and radar screens via the HSB2. However I cannot get this to happen. About the only thing they seem to share are the cursors. Meaning RL70 cursor shows on RC631 and the RC631 cursor shows on RL700. But that is it, no chart or radar sharing.

All the other data is shared on the seatalk network. If I switch the c-map card between units I can get charts on one or the other. However when it's in the RL70 I cannot get the radar to overlay on the chart.

How do I trouble shoot this?

If I can't get them to share chart and rader then I may plan on upgrading the radar and MFD displays. i.e. new radome and MFd's at nav and helm
But I would like to keep all the ST60's, 400G course computer and ST6001+. From what I can dechiper I will need to mate the seatalk with the seatalkng, is that correct? What other considerations?

Lastly, which autopilot control head would replace the ST6001 and still keep the course computer and the other autopilot peripherals?

Q1. I believe that these two units should be able to share chart and radar screens via the HSB2. However I cannot get this to happen. About the only thing they seem to share are the cursors. Meaning RL70 cursor shows on RC631 and the RC631 cursor shows on RL700. But that is it, no chart or radar sharing.

A1. SeaTalk communications is responsible for sharing alphanumeric GPS, instrument, navigational, and system state data. Hsb2 communications is responsible of sharing of radar imagery, fishfinder imagery, and cartography. Please click here to view a FAQ addressing troubleshooting hsb2 communications. Unfortunately, should one or more of the displays have failed hsb2 communications circuitry, then it must be replaced, as Raymarine's Product Repair Center can no longer service these displays.

Q2. But I would like to keep all the ST60's, 400G course computer and ST6001+. From what I can dechiper I will need to mate the seatalk with the seatalkng, is that correct? What other considerations? Lastly, which autopilot control head would replace the ST6001 and still keep the course computer and the other autopilot peripherals?

It is recommended that the hsb2 port of the display be tested first. If a fault is found with the hsb2 port of either display, then there is no need to proceed with further resistance testing. From there, testing should be performed to the inline termination plugs and then finally with the cables.

Continuing on I am replacing the Pathfinders with a new E125 and HD424 digital unit.

I purchased the ST1 to STNG converter and my question is how do I count the number of ST1 instruments on the network. Apparently the converter only works up to 5.

So i have currently on the ST1 buss:

Ray GPS
Tridata at nav - this is where the transducers are connected
Wind at nav also transducer connected
400 G course computer
Auotpilot ST6001 control head
Do the autopilot and course computer count as one or two?

Then there is a line that goes to (3) ST60 repeaters that are daisy chained, do treat this as one or as three?

SO i think i either have 5, 6 or 8.

If i have 5 then i'm good with one converter if i have 6 or 8 i will need another converter, correct?

The items listed below are representative of five SeaTalk devices:
- Ray GPS (assume that this sensor supports SeaTalk rather than NMEA 0183 or SeaTalkng communicatons protocol)
- Tridata at nav - this is where the transducers are connected
- Wind at nav also transducer connected
- 400 G course computer
- Auotpilot ST6001 control head

As your system features the three additional SeaTalk devices listed below:
- 3) ST60 repeaters that are daisy chained,
increasing the count to eight SeaTalk devices, it will be necessary to install two SeaTalk to SeaTalkng Converters and link them to one another via an appropriate length of SeaTalkng Backbone Cable.