Hello
I just installed the Side Scan sonar to the Blue Boat and tried to set up the software. After setting up the hardware, when I connected to 192.168.2.3, the Wireless Clients section showed 192.168.2.4 instead of 192.168.2.2. And when I tried to connect to 192.168.2.2, the browser showed “This site can’t be reached”. I also couldn’t successfully ping 192.168.2.2
Does this issue have anything to do with the installation of the side scan sonar? How should I troubleshoot it? Thank you.
Update -
I found that if I remove the ethernet cable that routed to/from the ethernet switch, the Wireless Clients showed 192.168.2.2, and I can access the BlueOS without a problem. What changes should I make when connecting the ethernet switch board to make the configuration work?
Hi @ichen -
Welcome to the forums!
It sounds like you’ve connected two ethernet devices to the same port - remember that for the ethernet switch, ports 1 and 5 are available both as jst-gh (small) connectors as well as the larger RJ-45 jack. Plug the side-scan sonar modules into any 2 of the middle 3 ports, leaving 1 and 5 free for RJ-45 connectors going to the Raspberry Pi and Mikrotik Radio!
From the guide
Hello @tony-white
Thanks for the reply. I followed the instructions when connecting the ethernet cables and used only ports 2 and 3 for the small connectors. I attached a photo of my current configuration. Is there any suggestion that can help me further troubleshoot? Thank you.
Hi @ichen -
Do you see network activity lights on 4 ports on the ethernet switch when the system is powered?
Are the sonar electronics mounted to the tray in the other hull connected to power?
It can be tough to fully insert the power cables into the vertical push-latch connectors on the PCB - have you verified they are fully seated on both sonar PCBs?
Hello @tony-white
I don’t see any of them blinking when connecting all devices. All boards (Rpi/Sonar boards) are powered. And I can see the ethernet port blinking when only connecting the ethernet cable to Rpi and ignoring the ethernet switch.
I think we can narrow the issue down to the Ethernet switch. The power light for the ethernet switch was on. How should we further debug? Thanks.
Hi @ichen -
It does seem like the ethernet switch is causing your issue! We’ve had a limited quality issue with those recently. You can reach out via our support form, reference this thread, and provide an order # to receive a replacement. Or, if you’re in a hurry, simply removing the R6 resistor should fix the issue:
Unfortunately, the reason these boards are now failing at high rates stems from a slight variation in one of the chips (RTL8305)–which is unmarked on the chip itself. The slight variants should have been functional substitutions, but the variant most recently used exposed an issue in the circuit design. For some reason the circuit worked fine with the older chip despite being out of spec according to the datasheet.
If an ethernet switch is being considered as the source of an issue, look for:
- Bottom side of PCB has marking “PCB BR-102507-001 RevC”
- When measured with a multimeter, test point TP3 (1VD) measures 1.2V instead of 1V
- When power is connected, none of the 5 ethernet LEDs flash
This test point is located on the bottom side of the board, just to the right of the PCB version markings. If all of these conditions are met, the ethernet switch can and should be reworked as stated in the solution (removal of R6).
