Hello,
I have been tasked with installing a gigablox board to allow for fiber optic communication with the Blue ROV. Everything was working before adding this board. Afterwards, I get the 1GB transfer speed, but I am unable to open blueos.
I have tried many solutions related to the IP address and wiring connections and everything should be fine.
I believe that I have exhausted all methods of troubleshooting that I personally know. Any help would be greatly appreciated!
Hi @tlspence -
Welcome to the forums!
Do you know what version of BlueOS you were running when you lost communications? Does connecting directly with an Ethernet cable to the Pi, and setting your IP address properly, get you connected to BlueOS at 192.168.2.2?
This could be a hardware or software issue depending on the situation!
Thank you!
I am unsure of the version of BlueOS. I have tried connecting it to the Pi and did not see any results. I was unable to see the ethernet port in my adapters list.
I have been able to see the adapter in other scenarios besides this one.
Hi @tlspence -
Are you using Windows? If your computer has a built in ethernet jack, it should show up in your network adapters list - see the instructions here to configure it.
If you have connection with the direct ethernet, then the issue is with your tether or that ethernet switch. If not, then your software may have an issue and a reflash of SD card or access via WiFi IP address may be required.
I am using windows. I do have a built in ethernet jack and I have done the configuration of the ethernet ip and subnet before. I currently am not using a tether, just a fiber patch cable with an attenuator to have the correct dBm levels. I have tried reflashing on a seperate SD card.
Hi @tlspence -
I’d recommend connecting directly via ethernet to isolate the potential issue -if it works via direct connection, and not via fiber / botblox gigabit then your issue is related to the network, not the software!
I have removed the new board and have done my best to return it to its original state. On the fathom x tether board I am net getting a light next to link after the start-up process. I believe that I have wired everything correctly. What could be causing this issue? Is there something wrong with the Pi?
Hi @tlspence -
The Pi has nothing to do with the Fathom-X tether module - its function does not impact the network link. Please measure your tether resistance and share the result:
With it connected, you should have consistent resistance for each of the two wires from the pair used. note that it does not matter if + goes to +, or -, on the green screw terminals for the tether connection.
I am not receiving a reading for the resistance when after multiple variations of measurement. Even moving through the different scales of measurement.
Hi @tlspence -
If you’re saying your multimeter says “open circuit” and does not give a resistance measurement when trying to measure the resistance of a wire in the tether from one end to the other, this may be why the link light is not coming on! If the tether is damaged and no connection exists, resistance is infinite, and no communications can occur. Can you try measuring a different tether pairs resistance?
I do see past mention of fiber optic comms in this thread - the resistance is only relevant to the fathom-x / copper…
I do not have another tether to test. This test was done on the base Blue ROV tether. No fiber optics were here at the time.
If this won’t matter for fiber optics. Then can I remove the fathom board and tether if I want to move into fiber?
Hi @tlspence -
If you’re measuring open circuit on wires in your copper tether, than it is damaged and will not work.
The Fathom-X sends data over a twisted pair of copper wire, giving you a transparent ethernet link at distances greater than ethernet can achieve. If you’re using fiber optics to communicate with your system, then you are correct, it is not a relevant component.
Hi @tlspence -
You may want to check the pin out on the botblocks router, it may be different that the Blue Robotics standard whenever switch…
Hello,
The issue has been found. In the original state, with the Fathom tether, there was a wire that was not working. After its replacement the device works again.
I am now moving back to working on getting the fiber optics to work.
Hello,
I have wired the Giga Blox board to the raspberry pi. With the boards auto-negotiating ports I have plugged an ethernet cable into the pi from the board, I have powered the board on, then completed all configuration on the control panel to change adapter settings. Is there anything I am missing for why this device is not accessing blueos? Here is a photo of the board for reference.
Hi @tlspence -
How did you connect the board from the GigaBlox to the Pi?
Was it by using the included cable?
Hello,
I used the included cable and connected it to the middle left port of gigablox and then to the ethernet port on the Raspberri Pi
Hi @tlspence -
If you plug two devices into the switch via those adapters, like the Pi running BlueOS and your computer, can you reach the device at 192.168.2.2? This assumes you’ve properly configured your network adapter with a static IP on the .2.X subnet…
Hello,
No, I am unable to access blue os through 192.168.2.x I typically receive “a network change has occurred” or “blueos took to long to respond”
Hi @tlspence -
You may want to try with two normal computers, pinging each other’s static IP address while both connected to the botblox ethernet switch? If that doesn’t work, then it sounds like there is an issue with the hardware, worth bringing up to the ethernet switch vendor!
