wifi name of turtlebot4 change to clear6b and turtlebot wifi didn't apper at all

[Hanbali11]

Please provide the following information:

• OS: (e.g. Ubuntu 22.04
• ROS : (e.g. humble)
• Built from installed:

• Expected behavior so basically I was working to connect the robot to my computer and it connected successfully after that I try to send the wifi and the name of the main wifi to the robot to connect both robot and laptop to the same wifi after sending the information to the robot I didn't know if he receives it or not so I try to do that after switching it off and try again so the wireless name in the robot change from 'turtlebot4' to 'clear6bbr'
  note that before sending the information I was able to see the data of the robot but after switching it off the robot change to another wifi name as I mentioned

[MikeDegany]

I'm not entirely sure I've captured your problem accurately, but it appears that you might have initially connected to the Turtlebot on access point mode, modified the Wi-Fi configurations, and lost the connection. One potential solution is to use an Ethernet cable to SSH into the Raspberry Pi.

[hilary-luo]

Hi @Hanbali11,

My understanding is that you are running humble and thus used the turtlebot4-setup tool to configure your wifi credentials. When doing this, are you sure that you changed the robot from access point mode to client mode? If you left the robot in access point mode but changed the SSID and password, then the turtlebot will continue to broadcast its own network and adopt the new ssid and password that you entered. This could cause problems if there is already a network with this SSID.

Please connect to the turtlebot using the recovery instructions. Launch the turtlebot4-setup tool again and ensure that the Wi-Fi Setup settings show the mode as client

If you change any settings then ensure to apply the settings.

[Hanbali11]

I did what the recovery instruction say ,but the result came like ''$ ssh ubuntu@192.168.185.3 ssh: connect to host 192.168.185.3 port 22: Connection refused''

[hilary-luo]

@Hanbali11 Can you restart by re-imaging the raspberry pi. Once you have it up and running again, ensure to follow the wifi set up instructions that correspond with the ros-distro that you are running (humble or galactic). As you run through this keep very detailed information on exactly what you do / run and then if you run into any issues give me the details here (include the name of which image you use and specific terminal outputs at each step).

It is possible that the origin of your issues was running the wrong wifi set up instructions for your ROS distro.

[Hanbali11]

thank you