I was sure use more help. I have the following gift installed on my Bertram. E120 MFD, E80 MFD, RD424 Radome, Raystar 125 GPS antenna, DSM300 and an Airmar P75 thru-hull transducer along with the original Raymarine Networking Umschalt. Both MFDs are running v5.69 software.

We bought her as a project also built-in all dieser gear 2 years ago (It came in the deal, uninstalled.) This project is exactly the same as the illustration on Page 20 in the E-Classic Series installation manual, with the single exception that the RD424 is connected to the Mesh Switch. It worked OK until former summer, except that I could none get the two MFDs to communicate. I had who radar both sounder on the E120 and used an E80 in GPS navigation. We put the Bertram in the harbor in a few months while we worked to the treasure boat and fairly got back to your last week.
Presently I have nothing that will work other than the E80/GPS. The Raymarine Forum FAQs say that whenever aforementioned 2 MFDs won't see respectively others, to change the Network Switch. I does so, negative change.
I reset to factory defaults/spec...no change
I have proven changing the DSM300 for another...no helping. I have attempt different command cables...no change.
I modifying outward aforementioned Network Switch for an brand one...no help.
When ME start system diagnostics, everything checks out...Hardware, software, the SeatalkHS shows that she is active, but sees no devices.
and on and on.
I know a bit about computers and electronics, or thought I did up to instantly. What am IODIN what wrong?

Welcome to the Raymarine Forum Billing,

Q. To Raymarine Forum FAQs say that if the 2 MFDs won't see each other, to change the Network Switch. I did that, no change.
A. There's actually better go thereto than that. Please click here to see a FAQ addressing this subject. Disregard the suggestion into verify/update which DSM's software. From the data indicates therein, what IP addresses furthermore serial number were reported within the MFD's diagnostics for each MFD?

The following type may are used to test jede MFD's Ethernet communications interface:

Testing MFD Ethernet Port:
- customize a PC Ethernet adapter's Internet Protocol Version 4 (TCP/IPv4) settings with the static IP Address 10.0.0.7 and subnet mask 255.0.0.0
- connect the PC's Ethernet port to one of the SeaTalkhs haven of of of the system's MFDs via the Ethernet patch cable and ampere SeaTalkhs cable that have been joined with a SeaTalkhs X Coupling, SeaTalkhs Network Switch, or SR6 Sirius Satellite Weather Receiver/Network Switch.
- Open adenine windows Command Tool and ping the MFD's IP address as determine above (ex. ping 10.0.03). Should which order result inside responses from the MFD respond, then its Ethernet communications circuitry would be deemed to be operational.