Hi!
That is my first time using the BlueROV2. I have updated the softwares and now I am in the step where we need to connect to 192.168.2.2 from a browser. The problem is I get this message on my rpi :
So, I would be happy, if you have any idea about what’s going on with my rpi 
Thanks in advance 
and have a good easter weekend
Hello @navylos_ear you had some answers and help here, but they were misguided and missing the root cause of the problem. So I have deleted those posts to clear the confusion.
To be clear, you are having issues communicating with the raspberry pi over the network (cannot access http://192.168.2.2:2770 through the browser), so now you have connected a keyboard and a monitor to the Pi to troubleshoot. The messages that you see on the monitor are from the boot process, and they are all normal, and not the cause of the network problem (even the lines that say error and exception, the pixhawk autopilot connection is ok and it should still work).
What you need to do is verify your network configuration and communication. Your computer network is not configured correctly to connect to the raspberry pi.
Please carefully follow these troubleshooting steps here, which should solve your situation. If you have a problem with these steps, let us know.
Hi Jacob, thank you for your answer, however I have already followed these steps, this is what I get when I tried to ping 192.168.2.2:
I changed the ethernet cable to check if it comes from here but have the same result…
turn off my firewalls and reboot my laptop, have the same result…
Here is my QGC config too :
I’m really runing out of ideas haha 
.
Ok, so you are in an interesting situation. The output of ipconfig is showing the correct configuration for the network, and indicates that you should be able to ping the ROV. However, the ping fails.
Please check for me that the lights on the ethernet port connector are illuminated on the raspberry pi and on your ethernet adapter. If they are, then the problem is probably in windows.
I have seen situations like this in a couple of cases in the past, and the only solution I found was a bit extreme - is to reset windows networking configuration. You will need to set up any wifi and things like that again if you do this, but I think you should try. https://www.howtogeek.com/265870/how-to-reset-your-entire-network-in-windows-10-and-start-from-scratch/#:~:text=On%20the%20Windows%20Settings%20screen,the%20“Network%20reset”%20link.
I have checked the lights on the ethernet port of the raspberry pi, it’s blinking, for the ethernet port of the adapter you mean, the one on the fxti :
…
I’ll be back tomorrow Jacob, hope we’ll find the answer I still have hope!
Have a nice day!
Hello, Jacob. I hope everything is going well for you!
Do you have any idea what the problem is with my BlueRov2??
Hello, Jacob. I hope everything is going well for you!
Do you have any idea what the problem is with my BlueRov2??
Ok @navylos_ear, from what I can see:
So now I think the problem may be with the physical ethernet connection. We can narrow down the problem by removing the tether and FXTI from the system. You can do this by connecting an ethernet cable directly between the Ethernet port on the Raspberry pi, and the Ethernet port on the network adapter you are using with windows. Please try to do that and let me know the result.
Hi Jacob!
Thank you for the reply, I’ll test this out
I’ll get in touch with you when it’s done 
Stay safe and have a nice day,
Regards.
Solyvan
Hi Jacob, good news, I’m able to connect to the BlueRov2 by removing the tether and FXTI! Do you know by the result I get where the problem is located ??
Best regards,
Solyvan.
Ok, so we need to troubleshoot the tether and tether interface boards.
Double check:
The power and link lights on both interface boards should be illuminated when they are connected correctly - are they illuminated on your board when the tether is connected? What about with a shorter cable?
Hi Jacob! Firstly, thank you for the help.
So I try what you said :
.**each connection is secure on the [Fathom X boards]in the ROV and the [FXTI topside interface box] Re-seat and tighten the wires in the screw terminal blocks : ** done✔
. ** make sure the USB power supply is powerful enough for the FXTI topside interface box. Try using another USB port or a powered USB hub.** : The FXTI is only powered by my laptop, how should I power it with another USB power supply??
.** Try to replace the tether conductors with a pair of shorter wires - to see if the problem is in the tether cable/conductors or the interface boards. Connect the interface boards directly with some pair of shorter wires screwed into the green terminal blocks.** done 
.The power and link lights on both interface boards should be illuminated when they are connected correctly - are they illuminated on your board when the tether is connected? What about with a shorter cable?
When I use a pair of shorter wires, the lights (link & pwr) are illuminated on both Fathom X.
But when I use the tether, there is only the Pwr that is illuminated.
So the problem come from the tether ???
Regards,
Solyvan
When I use a pair of shorter wires, the lights (link & pwr) are illuminated on both Fathom X. However I can’t connect to the Bluerov, i’ve tried to ping it and get a “unable to reach 192.168.2.2”…
The lights (link & pwr) are illuminated on both Fathom X while I use a pair of shorter wires. However, I am unable to bind to the Bluerov; I attempted to ping it and received the message “unable to access 192.168.2.2”…
A post was split to a new topic: Cannot connect to ROV after software update
The FXTI is only powered by my laptop, how should I power it with another USB power supply??
Try a different usb port on the laptop if there is more than one, or try another laptop, or get a usb hub that connects to an external power supply.
The lights (link & pwr) are illuminated on both Fathom X while I use a pair of shorter wires. However, I am unable to bind to the Bluerov; I attempted to ping it and received the message “unable to access 192.168.2.2”…
This is an issue we should get past before trying to fix the tether. Are you still unable to ping?
Hi Jacob!
Yes I’m still unable to ping 192.168.2.2
Hi again @jwalser !
Do you have any idea about the situation with my ROV? The issue come from the tether or from the Fathom X?
Solyvan.
Please email support@bluerobotics.com to ask for a new fathom x, and you can arrange a remote desktop session for technical support. Provide a link to this thread please.
