[CA] [CA11] RS150 STNG connection failure

[edwardkern]

Having trouble with a RS150 on the STNG 5 way connector under cockpit. Two red blinks every four or five seconds. Documentation suggests network issue. I thought it was the cable, so got another, but still no connection (two red lines in attachment, original cable inside radar mounting pole, second direct run as boat is hauled, mast unstepped). Then tried new cable to an open port on 5-way at Nav Station and it worked (green line, shows up as GPS source on Axioms) . Then tried old cable to 5-way in pedestal pod and it worked again (green line, left), then connected P70 to 5-way under cockpit expecting connection to fail and to confirm that there was something wrong with the 5-way under the cockpit, BUT it worked (crossed green lines, left).

Will be trying a new 5-way, but doubt that will solve the issue. Anyone see any issues with this configuration?

Tried re-configuring slightly today with the RS150 connected to a T or a five-way connector near the middle of the backbone. It is not seen by the Axioms on the either end of the backbone, but is seen when connected to a five-way connector or st1-stng converter port (yes white, NOT yellow) at the end of the backbone.

[Chuck - Raymarine - Moderator]

Welcome to the Raymarine Forum Edward,

Please attach a diagram of your system's SeaTalkng / NMEA 2000 network, listing the make/mode each device which has been connected as a spur to the SeaTalkng / NMEA 2000 as well those which have been interfaced to the yellow socket of the SeaTalk to SeaTalkng Converter. Please additionally specify how your backbone has been powered and where its power insertion spur is located (i.e. need to know which devices are installed on each side of the power insertion spur). If the system features an autopilot ACU or course computer, please be certain to specify its make/model.

[edwardkern]

Chuck

Here is the diagram; issue is with network connection for the RS150; the master Axiom is in the cockpit and can see only the GPS in itself and the second Axiom; the P70 control head can see the Vesper AIS GPS as well.

Ed

[Chuck - Raymarine - Moderator]

Ed,

General comments:
- Only the system's Data Master MFD will be able monitor and detect devices which have been interfaced to the system's SeaTalkng / NMEA 2000 backbone.
- The diagram does not show that Termination Plugs have been installed within the backbone's two end sockets ... please verify that this is so and respond accordingly.
- While the SeaTalk to SeaTalkng Converter has been designed and tested for use with ST50+ instruments, it is not supported for use with ST50 instruments ... please verify whether the instruments shown within your diagram are ST50 or are ST50+ instruments. Should the instruments be determined to be ST50 instruments, then it is recommended that they be unplugged from the system until such times the source of the problem has been identified and later after connection to the system has been determined to not cause any problems with the system.

It is recommended that the circuits supplying power to the system be switched OFF, that the third party AIS transceiver be unplugged from the system, and that the circuits supplying power to the system be switched ON. The software levels within all Raymarine products and networking components should then be updated with the latest available software via the Data Master MFD. After doing so, the Data Sources feature of the Data Master MFD should then be exercised to manually designate that the Raystar 150 GPS Sensor will be the system's data source for GPS data and date/time data. The vessel should then be connected to shore power and its batteries permitted to attain full charge. Afterwards and while still connected to shore power, the system should then be tested. Should the problem persist, then please respond accordingly. Should the problem abate, then the third party AIS transceiver should be connected to the system once again and the system should then be tested. Should adding the third party AIS transceiver to the system again cause the reported problem then it would be recommended the third party AIS receiver/transceiver be disconnected from the system, its manufacturer contacted to determine whether any software updates are available, and if so, that the third party AIS receiver/transceiver be updated with the latest available software and then re-tested with the system. Should the problem re-occur when later testing the third party AIS receiver/transceiver with the system, then the AIS transceiver should be configured to not transmit PGNs containing GPS and date/time date to the SeaTalkng / NMEA 2000 backbone.

[edwardkern]

STng bus has termination plugs each end. (I think drawing shows extra concentric circle).

Third party (Vesper) AIS firmware updated last week.

I did see some message about NOT manually selecting some data sources (either those NOT STng or NEMA 2000/Cannet)

Batteries are fully charged with winter charger (we launch tomorrow); no such thing as shore power after that.

I find it odd that the Master Axiom sees the RayStar 150 when it is connected at the either end of the STng backbone, but not in the middle.

My legacy TriData, Wind, Close Hauled and Multi are all ST50+. The ST600 and ST1 NEMA0183 converter I am not sure of their classification.

Ed

[Chuck - Raymarine - Moderator]

Edward,

Per our phone conversation today, it is recommended that the resistance across the CAN_H and CAN_L pins within the termination plugs be verified to be 120 Ohms and that they be replaced if found to not be so. Please click here to view a FAQ addressing the pin-outs for the SeaTalkng networking components.

It is recommended that the compressed software update folder containing LightHouse 3 for Axiom MFDs be downloaded to your computer and that its contents then be extracted into the root level directory of a microSD memory card. This process is detailed below:
Software update procedure:
1) Insert your microSD memory card into your computer's memory card reader
2) Download the desired software update compressed folder from the LightHouse 3 for Axiom & Axiom Pro MFDs software update web page. The compressed folder containing the software update files will be downloaded from the product's software update web page and saved on the computer used to download the software update zip file ... the downloaded file will typically be located within the Downloads folder of computers running the Windows operating system
3) Open the computer's Downloads folder (or your computer's folder where downloaded files are saved)
4) Right click on the downloaded compressed folder containing the software update files to display a menu of options
5) Left click on the EXTRACT ALL menu option to display the Extract Compressed (zipped) Folders dialog
6) Left click on the Browse button within the Extract Compressed (zipped) Folders dialog to display the Select a Destination dialog
7) Within the Select a Destination dialog, left click on the drive letter corresponding to your microSD memory card, and then click on the OK button.
8) After all files have been extracted, remove the microSD memory card containing the software update files from the computer's memory card reader
9) Power the system's MFDs ON, permit them all to complete startup initialization, and then acknowledge the Limitations of Use notice.
10) Insert the microSD memory card containing the software update files into the Data Master MFD's memory card reader
11) Command the Data Master MFD to Update Software (HOME->SET-UP->GETTING STARTED->UPDATE SOFTWARE) and then to Check SD Card
12) When provided a list of products for which software updates are available, select to update only the software within the Axiom MFDs. The Data Master MFD will push the software update out to the system's other MFDs
13) After updating the software within the MFDs, command the Data Master MFD to Update Software (HOME->SET-UP->GETTING STARTED->UPDATE SOFTWARE) and then to Check SD Card
14) When provided a list of products for which software updates are available, select to update only the software within the EV-1 CCU***.
13) After updating the software within the EV-1 CCU, command the Data Master MFD to Update Software (HOME->SET-UP->GETTING STARTED->UPDATE SOFTWARE) and then to Check SD Card
14) When provided a list of products for which software updates are available, select to update the software within the remaining components of your system for which software updates are available.

As noted during our conversation, following software updates to an Evolution autopilot, it is recommended that the Pilot Factory Reset be executed, Dockside Wizard be executed, and that the vessel again be taken out to "Detect Magnetics". Please click here to view a FAQ addressing this subject.


*** You must update EV1 CCU's software before updating your ACU.

[edwardkern]

Attachment.

[Chuck - Raymarine - Moderator]

Edward,

Please click here to view a FAQ addressing why Data Source Selection may be blocked. When such notices are posted, it is generally recommended that the command be immediately executed a second time, as it may be a false indication. As indicated within the referenced FAQ should the problem persist, then it is recommended that the blocking device be temporarily disconnected from the backbone until after having completed the Data Source selection. If uncertain of which is the blocking device, then it is recommended that each device except for the Data Master MFD and the device which you are seeking to have perform as the system's data source be temporarily disconnected from the backbone to permit data source selection to be successfully executed.