Sonoptix Echo interface pinout for Ethernet Switch?

Third Party Products Sonar and Acoustics
1

I have an Sonoptix Echo and want to terminate the internet wires (G, G/W, O, O/W) to a 4 pin JST GH connector so it can fit through the M10 hole. Does the Echo use the standard color scheme that other devices use? Is there a pin out diagram? Don’t see one in the App Guide for the Echo. The ports on the Switch are labeled so just need to know what the wire colors correspond to.

2

Hi @bajaMike -
Yes, the Sonptix Echo follows the standard ethernet color pinout for Blue Robotics devices. The Technical Details section of the product page has the information:

image
image2772×246 9.9 KB

You can also find that pinout in the Blue Robotics connector standard.

1 Like
3

Yep, see that now. Have there been any issues with this sonar not working well?

4

I noticed that the Echo User Manual pg 4 shows the colors to be a different configuration. Is the Echo cable a Subsea type cable?

5

Hi Mike -
Good catch!

image
image1184×712 79 KB

I would trust the Blue Robotics connector standard and technical details for now, but if it turns out to be reversed it shouldn’t hurt anything to switch to the current orientation.

Can you share what you mean by “subsea type cable” ? It is indeed a cable material intended for use in underwater applications, as you may expect from an underwater sonar!

6

I went ahead and wired it to the BR standard. It works and can now get the first screen showing the radar image!! Great, but now when I load up the QGC the ROV cannot connect to the laptop? I wonder if the network settings need to be modified? In my Windows 11 settings, I see Ethernet with a red X and Ethernet 2 that is working and is the sonar. What should I set Ethernet w a red X to so they don’t conflict?

7

Hi @bajaMike -
There should only be one ethernet adapter used to connect to both the ROV and Sonar - if you can reach the Sonoptix then you’re likely on the correct subnet, but may not have set your computers static IP to 192.168.2.1. Can you reach BlueOS at 192.168.2.2 or blueos.local?
Was the computer connecting to QGC previously?
What version of QGC are you using? We recommend an older version, 4.2.8. or using Cockpit!

Please verify you’ve followed the network setup instructions.

8

Got it now Tony, thanks. It was a network setting issue. Both run OK now. I have not yet tried Cockpit so maybe will give it a go. Have a Merry Christmas!

1 Like