Hello, I have a Hunter 49 2009 with Raymarine E120 mfd in the cockpit and E80 below, they have been working ok for 4 years connected via seatalk hs.
I had to send the E120 to fix the blacklit cctl and when I installed it back none of them can see each other.
The E120 IP address is 10.10.167.235
The E80 IP address is 10.10.173.41
They both have app ver v.5.52 and Bootcode Version v1.03
Individually they work fine, radar, st70 wind depth, engine, ais, etc.
When connected together they both ask to be set as Master.
How can I change the IP address in one to fix this problem?
IP addresses cannot be changed in the field. The IP addresses appear correct and as such would not be responsible for the reported issue. Are these MFDs interfaced via a SeaTalkhs Network Switch or via a SeaTalkng Crossover Coupler? If interfaced via a SeaTalkhs Network Switch, are there other devices interfaced to the network switch.
Please see the message sent to you yesterday. SeaTalkhs is not specific enough of an answer. Please respond with the applicable method identified within that message. Should the physical interface be not within the methods that I listed, then please identify the exact physical components used to interface these two MFDs.
Hello again, sorry for the wrong answer.
This MFDs were installed by Hunter Marine and I don't have the schematics for the E's install.
I am waiting for an answer from Marlow Hunter regarding the e80 e120 connection.
Maybe Both MFDs have been joined to one another via a single SeaTalkhs cable having weatherproof locking rings on both ends of its cable.
I am sure of what comes out of each unit and what comes in but don't know what's in between.
I was at the boat yesterday and opened every board I did not find any network switch.
The E120 on the cockpit only has the power conector, the Seatalk HS and vga video in.
The e80 is another story.
Beside the Seatalk HS and power it has:
2kw radome cable connector
4X ST70 with tridata + M200 engine monitor thorught a06061 seatalk ng to E series
spx 30 autopilot computer / smart rf controller / EM-TRACK B100 ais transceiver -> nmea 0183
ICOM IC-M422 dsc -> sea talk alarm out
VGA OUT -> PANASONIC 37" MONITOR
VGA IN <- outdoor video camera.
Everything has been working well for more than 2 years, I see everything everywhere.
Last december I had to send the E120 for repair of the Backlit CCRl and when I put it back in there was no communication with the E80.
Should both MFDs have been powered ON and commanding one of the MFDs to be the Data Master not cause the other MFD to then be configured as a repeater, then there may be a fault with the MFD repair or within the installation. However, before troubleshooting the system can begin, we must first verify that the installation was correctly performed ... past system performance is not necessarily an indicator of whether the products were correctly interfaced. The diagram which you have supplied does not include the E-Series Classic MFDs and does not specify how these items have been interfaced to one another. Please send the SeaTalkhs interfacing questions that I sent to you to Hunter for specification regarding how the SeaTalkhs communications path was created between these products. Should you not be able to obtain this information from Hunter Marine, then you may want to seek the assistance of an Raymarine installer.
This is the answer from Hunter Marine.
There should be a crossover coupler near the chartplotter at the nav station. I have attached a picture of it.
Director of Engineering
More detailed answer.
The E120 has a 10 meter Seatalk-HS cable that is connected to a Raymarine cross over coupler then a 1 meter or so Seatalk-HS cable to the E80.
If unable to perform the diagnostics, it is recommended that a certified Raymarine Installer in your area be contacted to assist. Alternatively, the MFD(s) may be sent to Raymarine's Product Repair Center to be bench checked.
System instability and/or loss of communications between MFDs may be caused by not operating the same version of MFD software in each MFD, software incompatibility with the chart card being used, or failure of the SeaTalkhs communications cabling between the MFDs, or failure of the MFD hardware itself. System instability may also be caused by SeaTalkhs communications problems. Most SeaTalkhs communications problems are due to one or more of the following:
- each MFD has not been updated with E-Series Classic MFD v5.69 software. The version number of the software installed within the MFDs may be accessed via the command sequence MENU->SYSTEM DIAGNOSTICS->SOFTWARE SERVICES->UNIT INFO->APP VERSION on each MFD.
- a Factory Reset operation has not been performed on the MFDs following the software update
- insufficient power being supplied to the system (measure the voltage at the display end of each MFD's power cable)
- installation issues (see below)
- invalid MFD serial number(s). An invalid serial number may result if problems occur when a MFDs software is updated or when an incompatible memory card is used to perform the software update. The serial number for each MFD should be checked (MENU->SYSTEM DIAGNOSTICS->SOFTWARE SERVICES->UNIT INFO->SERIAL NUMBER) ... should this item specify invalid, then the MFD will need to be serviced by Raymarine's Product Repair Center.
- duplicate SeaTalkhs IPs have been encoded into the devices of the system. One may check the IP of each MFD via the command sequence MENU->SYSTEM DIAGNOSTICS->EXTERNAL INTERFACES->SEATALKHS->IP ADDRESS. Pressing the DEVICES function key will list all other SeaTalkhs devices within the network, their IPs, software revisions, and IPs … you have already provided this information ... the IPs are valid and not duplicated within your system.
From an installation standpoint, the following issues must be addressed when troubleshooting a SeaTalkhs communications problems:
- the MFDs must be interfaced via SeaTalkhs using a pair of SeaTalkhs cables that have been joined with a SeaTalkhs Crossover Coupler, SeaTalkhs Network Switch, or SR6 Sirius Satellite Weather Receiver/Network Switch. It is NOT permissible to connect an E-Series MFD directly to the any other SeaTalkhs device without using a SeaTalkhs Crossover Coupler or a SeaTalkhs Network Switch ... this has been verified by Marlow-Hunter.
- inspect the SeaTalkhs Network Switch, clip any zip-ties anchoring the SeaTalkhs cables to the SeaTalkhs Network Switch (this may actually be causing an intermittent connection to the switch socket) and anchor/strain relive these cables outside of the switch ... N/A - SeaTalkhs Crossover Coupler installed
- SeaTalkhs cables, NOT generic Cat5e or custom constructed Cat5e, must be used to interface SeaTalkhs devices ... this has been verified by Marlow-Hunter
- Excess SeaTalkhs cable must be loosely coiled and secured to a bulkhead to prevent bend radius of less than 3" ... you will need to inspect the SeaTalkhs cables
- Bend radius of any SeaTalkhs Cable should not be less than 3" ... particular care should be taken to inspect the SeaTalkhs cables of any MFDs installed within pods to ensure that they are not subjected to such bends and/or have been kinked or otherwise damaged by such bends
- The marine electronics must be powered from an isolated power source
- The circuit powering the Raymarine products has been constructed of cable of the appropriate gauge for the round trip distance between the Raymarine products and the power source.
If responding to this incident, please specify the serial numbers, software revisions, and IPs of each SeaTalkhs device as reported by the system using the command sequences listed above.
A Raymarine installer may test the SeaTalkhs communications circuitry of each MFD by interfacing the MFDs one at a time to a a PC running RayTech RNS 6.1 software or to another SeaTalkhs device (ex. DSM30/300, Digital/HD/Super HD Digital Radar Scanner, or SR100). Should the MFD not be able to communicate with one of these devices, then that MFD should be serviced by Raymarine's Product Repair Center.
Could you send me the step by step procedure for upgrading from 5.52 to 5.69?
Do you Know what will happened with the non Raymarine devices connected to the system when upgrading form 5.52 to 5.69? (M200 engine monitor Seatalk ng nmea2000 and/or EM-TRACK B100 ais transceiver nmea 0183)
Seatalk hs cable on the boat tested (with a network cable tester) like a new spare cable I have, pairs 1,2 and 3,6 .
Is there any other test to run on the cables? should pairs 4,5 and 7,8 also show?
I used this new cable to connect each MFD to my computer and I could see each of them and confirm their IP and Mac addresses.
The E-Series Classic MFD software and detailed software update instructions may be accessed by clicking here. The software update will have no impact any external devices. However, following the software update, the Port 1 setting of MFD which is interfaced to the AIS receiver will need to be configured to AIS 38400.
There are no additional cable tests to perform. Raymarine products only use the pairs which you have identified.
Could you please confirm that Raymarine's Seatalk hs IP addresses work differently than standard ethernet?
In standard ethernet network these devices, E120 IP address 10.10.167.235 and E80 address 10.10.173.41 are in different subnets and will not see or talk to each other.
Thanks for all your help,
This is indeed the case. Raymarine's products featuring an Ethernet interface are designed around products having fixed IPs employing Class A addressing. The IPs of your E-Series MFDs are indeed valid.