-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ask for WiFi connection #480
Comments
Hello @Lynn-hh , After SSH'ing into the Turtlebot. are you able to make the necessary changes in the Turtlebot Setup Utility to connect to wi-fi (https://turtlebot.github.io/turtlebot4-user-manual/setup/basic.html#connect-the-raspberry-pi-to-your-network)? To do so:
If the above process fails would it be possible to verify the following:
With regards to the date and time being out of sync, once the Turtlebot connects to a network it should sync. If it does not try the instructions found here to force a sync - https://ubuntu.com/server/docs/use-timedatectl-and-timesyncd Let me know how these recommendations work for you. Looking forward to hearing from you soon. |
Thank you so much, I will try what you suggest
smatarCPR ***@***.***>于2024年10月16日 周三14:24写道:
… Hello @Lynn-hh <https://github.com/Lynn-hh> ,
Thank you for reaching out on the Turtlebot 4 github. APologies for the
late reply on this.
After SSH'ing into the Turtlebot. are you able to make the necessary
changes in the Turtlebot Setup Utility to connect to wi-fi (
https://turtlebot.github.io/turtlebot4-user-manual/setup/basic.html#connect-the-raspberry-pi-to-your-network)?
To do so:
1. Run the command turtlebot4-setup
2. Scroll to Wi-Fi Settings and enter the W-fi settings sub menu.
3. Change Wi-Fi Mode from [Access Point] to [Client]
4. Enter the details of the network, SSID is the network name, the
option below that should be password.
5. Select the bandwidth of the wi-fi network: 5.0 GHz or 2.4 GHz.
6. Scroll down and select the Save option, you should be brought back
to the main menu. Scroll down and select the Apply Settings.
7. Exit the setup utility, the Raspberry Pi should reboot with the new
network settings applied.
If the above process fails would it be possible to verify the following:
- Please provide the turtlebot logs using journalctl -b >
turtlebot4_log.txt
- Verify that the network you are connecting to does not have
additional security settings such as MAC address white listing or security
beyond a password.
With regards to the date and time being out of sync, once the Turtlebot
connects to a network it should sync. If it does not try the instructions
found here to force a sync -
https://ubuntu.com/server/docs/use-timedatectl-and-timesyncd
Let me know how these recommendations work for you. Looking forward to
hearing from you soon.
Best Regards,
Saif
—
Reply to this email directly, view it on GitHub
<#480 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BLNXUM2K7CSE65LMEB63423Z324QTAVCNFSM6AAAAABPMNDH3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJXG42TMMJVHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Robot Model
Turtlebot4 Lite
ROS distro
Humble
Networking Configuration
I do not know
OS
Ubuntu 22.04
Built from source or installed?
Installed
Package version
22.04
Type of issue
Networking
Expected behaviour
After the boot, the wifi can be retrieved and successfully connected to the wifi
Actual behaviour
Now I can only use the internet cable to ssh the turtlebot4.
Then I check with it, the first problem is the time error. It's still in 2023, but now is 2024.
When I use the "iwconfig" command to see the current status of the wireless card, it is not AP mode, it shows "managed". Maybe the current wireless NIC is in Managed mode
Then I disconnected the wifi connection, modified hostapd and started it. At this time, the wifi could be retrieved, but my computer could not connect to it.
Error messages
No response
To Reproduce
iwconfig wlan0
the current wireless NIC is in Managed mode
sudo nmcli device disconnect wlan0
sudo nano /etc/hostapd/hostapd.conf
sudo systemctl restart hostapd
Other notes
No response
The text was updated successfully, but these errors were encountered: