– Copied from a customer email –
I am part of a team working with Blue Robotics ROVs and we have used several of your Nano switches in the past to network Jetsons, IP cameras, and other devices with our ROVs. We are currently facing a pressing issue that we were hoping that you could provide some insight into.
One of our BotBlox GigaNano switches with RJ45Conn failed during our last field work. With this particular ROV we are using the BlueRobotics ethernet switch in a main enclosure, connected to the BotBlox GigaNano switch in a second enclosure. The standard BlueRobotics 16V battery power is shared between the enclosures. During the field work, one of the ports on the nano switch failed. We fixed this this by replacing the switch.
A few days later, we started having connectivity issues with the Jetson Nano installed in the second enclosure. We have been having a great deal of packet loss and are unable to connect. We found a stop-gap solution by using two of the nano switches in the lower bottle, which hosts a Jetson Nano, WaterLinked DVL, and a DWE Gigabit Fiber to Ethernet Converter board. The DWE board and Jetson Nano are powered using a step-down transformer off of the 16V BlueROV battery.
Do you have any insight into why we could be having these connectivity issues; Why two switches seem to work when one does not?
I would greatly appreciate your insight as we troubleshoot this issue.
There’s a lot here so I’ll try break it down.
One of our BotBlox GigaNano switches with RJ45Conn failed during our last field work
Can you share a little more colour on this? What were the environmental conditions? How did it fail specifically? How long had it been working for? Anything unusual in the system at the time of failure? The reason for the failure could be related to your later described issue, or it could be unrelated… Having more information on the nature of the failure would be helpful.
A few days later, we started having connectivity issues with the Jetson Nano installed in the second enclosure. We have been having a great deal of packet loss and are unable to connect. We found a stop-gap solution by using two of the nano switches in the lower bottle, which hosts a Jetson Nano, WaterLinked DVL, and a DWE Gigabit Fiber to Ethernet Converter board
First off, can you clarify if this issue was always the case, or whether it was working just fine with one GigaBlox Nano before, and later this issue arose? Sometimes such issues can be caused by ethernet PHYs not behaving well with each other (ethernet PHY related bugs), and in such cases, adding two switches in series can solve the issue. That being said, you appear to say that this issue came later? If this issue came later, then I don’t think it could be an ethernet related bug, as this would have been there from the start. Can you please let me know?