-
Notifications
You must be signed in to change notification settings - Fork 57
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
Network Issue #499
Comments
Hi, |
I have flashed the Raspberry Pi again. Thank you. But I'll try my laptop to configure it. For some reason, it does not identify the topics—also, nine robots run under one institutional Wi-Fi. |
Hello @Tauhid-Tanjim13
Looking forward to hearing from you soon. |
Hello @Tauhid-Tanjim13 |
Robot Model
Turtlebot4 Standard
ROS distro
Humble
Networking Configuration
I do not know
OS
Ubuntu 22.04
Built from source or installed?
Built from Source
Package version
Package: ros-humble-turtlebot4-description
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 29045
Maintainer: rkreinin [email protected]
Architecture: arm64
Version: 1.0.5-1jammy.20240830.231101
Depends: ros-humble-irobot-create-description, ros-humble-joint-state-publisher, ros-humble-robot-state-publisher, ros-humble-urdf, ros-humble-ros-workspace
Description: TurtleBot4 Description package
Type of issue
Networking
Expected behaviour
Lights:
MTR: On
COMM: On
WIFI: On
BATT: On
POWER: On
Actual behaviour
Instead, we observed:
Lights:
MTR: On
COMM: Off
WIFI: On
BATT: Off
POWER: On
Topics available on ros2 topic list:
/parameter_events
/rosout
When the robot is initially powered on, the light ring of the Create3 turns red
![image](https://private-user-images.githubusercontent.com/112510861/388055840-28df1fb5-f95f-4f6b-a156-a9c164d49c28.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk4MTE1ODcsIm5iZiI6MTczOTgxMTI4NywicGF0aCI6Ii8xMTI1MTA4NjEvMzg4MDU1ODQwLTI4ZGYxZmI1LWY5NWYtNGY2Yi1hMTU2LWE5YzE2NGQ0OWMyOC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxN1QxNjU0NDdaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03MzlhODlmZmRiNWJiZjA3ZmEwMWQ3OGM5OTRiNmYzZDE3ZDE3YzhkODYyNzYyOTBkM2E3ZjhlYTA1NTQyMTE2JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.wwgcU1h1HwwXBUZKHPK4ROnx2dcnSISFK3xw4tvZvuo)
After a short while, the light ring changes to another state
![image](https://private-user-images.githubusercontent.com/112510861/388056279-f1da57d0-99a4-4dfa-b447-920da9fb959c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk4MTE1ODcsIm5iZiI6MTczOTgxMTI4NywicGF0aCI6Ii8xMTI1MTA4NjEvMzg4MDU2Mjc5LWYxZGE1N2QwLTk5YTQtNGRmYS1iNDQ3LTkyMGRhOWZiOTU5Yy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxN1QxNjU0NDdaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00OTMwOTc4YmM0YjkxOGQwZTNlM2U5ODljZjg3OGNmZjk3MjQ0ZmY3OGJjZDA5Yjg4NzU3ZmEyODEyODhiMzg4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.0VUPByOwC1cGjBiy8zhZIQFx9tZWyhEACr-LeOYcCRY)
Error messages
To Reproduce
Other notes
While I have resolved the problem a few times by following the instructions in the TurtleBot4 documentation (mostly simple discovery mode using rmw_fastrtps), the issue persists intermittently. We have nine robots, and not all of them are having this issue.
Additionally, we failed to connect the remote PC to control the TurtleBot4 or echo ROS topics. As a workaround, we run all the programs directly on the Raspberry Pi (RPI) inside the robot, like map generation and SLAM. Even after resolving the connectivity issue using a simple Discovery Server setup, the problem reoccurs unpredictably.
The text was updated successfully, but these errors were encountered: