Create3 Repeated chimes - log #246

slowrunner · 2022-11-21T14:34:09Z

slowrunner
Nov 21, 2022

My Create3 seems to be complaining. It is repeating the power up riff twice when powering up and then again sometimes.

From end of log:

Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] Waiting for proto_update to resume
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] [proto_update] Resuming
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] proto_update resumed
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] Waiting for robot_rx to resume
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] [robot_rx] Resuming
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] robot_rx resumed
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] mobility_pinger is already resumed
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] time_sync is already resumed
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] proto event: PP_NOTIFY_LOST_SYNC
Nov 21 13:47:18 tb4create3 user.notice create-platform: proto event: PP_NOTIFY_LOST_SYNC
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] proto event: PP_NOTIFY_SYNCED
Nov 21 13:47:18 tb4create3 user.notice create-platform: proto event: PP_NOTIFY_SYNCED
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] Waiting for proto_update to pause
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] [proto_update] Pausing
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] proto_update paused
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] Waiting for robot_rx to pause
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] [robot_rx] Pausing
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] robot_rx paused
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] Waiting for proto_update to resume
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] [proto_update] Resuming
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] proto_update resumed
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] Waiting for robot_rx to resume
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] [robot_rx] Resuming
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] robot_rx resumed
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] mobility_pinger is already resumed
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] time_sync is already resumed
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] Waiting for proto_update to pause
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] [proto_update] Pausing
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] proto_update paused
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] Waiting for robot_rx to pause
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] [robot_rx] Pausing
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] robot_rx paused
Nov 21 13:47:18 tb4create3 user.notice create-platform: [DBG] Waiting for [INFO] [1669038438.323606848] [_internal.mobility]: waiting for config packet...../../modules/mobility-node/src/mobility-node.cpp:223
Nov 21 13:47:19 tb4create3 user.notice create-platform: [INFO] [1669038439.340277808] [_internal.mobility]: waiting for config packet...../../modules/mobility-node/src/mobility-node.cpp:223
Nov 21 13:47:20 tb4create3 user.notice create-platform: proto_update to resume
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] [proto_update] Resuming
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] proto_update resumed
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] Waiting for robot_rx to resume
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] [robot_rx] Resuming
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] robot_rx resumed
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] mobility_pinger is already resumed
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] time_sync is already resumed
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] proto event: PP_NOTIFY_LOST_SYNC
Nov 21 13:47:20 tb4create3 user.notice create-platform: proto event: PP_NOTIFY_LOST_SYNC
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] proto event: PP_NOTIFY_SYNCED
Nov 21 13:47:20 tb4create3 user.notice create-platform: proto event: PP_NOTIFY_SYNCED
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] Waiting for proto_update to pause
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] [proto_update] Pausing
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] proto_update paused
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] Waiting for robot_rx to pause
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] [robot_rx] Pausing
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] robot_rx paused
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] Waiting for proto_update to resume
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] [proto_update] Resuming
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] proto_update resumed
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] Waiting for robot_rx to resume
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] [robot_rx] Resuming
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] robot_rx resumed
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] mobility_pinger is already resumed
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] time_sync is already resumed
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] Waiting for proto_update to pause
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] [proto_update] Pausing
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] proto_update paused
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] Waiting for robot_rx to pause
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] [robot_rx] Pausing
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] robot_rx paused
Nov 21 13:47:20 tb4create3 user.notice create-platform: [DBG] Waiting for proto_update[INFO] [1669038440.355482109] [_internal.mobility]: waiting for config packet...../../modules/mobility-node/src/mobility-node.cpp:223
Nov 21 13:47:21 tb4create3 user.notice create-platform: [INFO] [1669038441.372505210] [_internal.mobility]: waiting for config packet...../../modules/mobility-node/src/mobility-node.cpp:223

and now the webserver has stopped responding completely. The ROS2 code seems to be alive though.

shamlian · 2022-11-21T14:36:44Z

shamlian
Nov 21, 2022
Maintainer

This is highly irregular. Can you please post the whole log (more than three seconds' worth)? Maybe not, if the webserver is not responding. see if [robot-ip]/logs-raw will load. Also, what version of the robot software are you running?

5 replies

slowrunner Nov 21, 2022
Author

Version G.3.1

I shutdown and restarted, the webserver came back up.
Create3_Logs_2022-11-21.txt

shamlian Nov 21, 2022
Maintainer

After a reboot (except for some spam from Cyclone at the top), things look normal. Has something changed on the network, perhaps something that might be hammering the robot with packets? The chime happens when the create-platform application restarts. Because of the way that ROS 2 handles networking, one of the times the application restarts is when, for example, the robot's IP address changes. The initial log looks to me like the robot's load average is high, though there is no direct evidence of that.

slowrunner Nov 21, 2022
Author

I did reboot the TB4rpi several times without powering down the Create3. Perhaps that messed it?

When the Create3 webserver failed, I sent the Create3 a RobotPower call that did not complete.
The light ring was pulsing red. I held the Create3 power button till it shut off, but it came back to life immediately so I put it on the dock to charge, and all has been normal since.

slowrunner Nov 22, 2022
Author

Day 2 Startup - Two Chimes -with log

Prior to startup, the bot was "undocked, then put to sleep" around 05:00UTC:

ubuntu@tb4rpi:~/tb4rpi/utils$ ./c3_action_undock.sh 

*** Send Create3 Undock Action
*** ros2 action send_goal /undock irobot_create_msgs/action/Undock "{}"
Waiting for an action server to become available...
Sending goal:
     {}

Goal accepted with ID: c8249c5d83404f058460329c337027cb

Result:
    is_docked: false

Goal finished with status: SUCCEEDED
ubuntu@tb4rpi:~/tb4rpi/utils$ ./power_off.sh 

*** POWER OFF ***
Are you sure? yros2 service call robot_power irobot_create_msgs/srv/RobotPower
requester: making request: irobot_create_msgs.srv.RobotPower_Request()

response:
irobot_create_msgs.srv.RobotPower_Response(success=False, message='')

Success=false is not a problem
ubuntu@tb4rpi:~/tb4rpi/utils$ client_loop: send disconnect: Broken pipe

Around 10:54UTC I placed the bot on the dock, and subsequently the bot chimed twice starting up.

I captured the log at 11:06UTC which appears to cover both the shutdown and the boot.
2022-11-22_Create3_Chime_Twice.txt

Create3 v G.3.1

TurtleBot4 (lite) and irobot package versions:

ubuntu@tb4rpi:~/tb4rpi/utils$ dpkg -l | grep turtlebot
ii  ros-galactic-turtlebot4-base                        0.1.3-1focal.20221103.192250           arm64        Turtlebot4 Base Node),
ii  ros-galactic-turtlebot4-bringup                     0.1.3-1focal.20220916.172555           arm64        Turtlebot4 Robot Bringup
ii  ros-galactic-turtlebot4-description                 0.1.2-1focal.20220916.170722           arm64        Turtlebot4 Description package
ii  ros-galactic-turtlebot4-diagnostics                 0.1.3-1focal.20220916.170903           arm64        Turtlebot4 Diagnostics
ii  ros-galactic-turtlebot4-msgs                        0.1.2-1focal.20220916.170811           arm64        Turtlebot4 Messages
ii  ros-galactic-turtlebot4-navigation                  0.1.2-1focal.20220916.170904           arm64        Turtlebot4 Navigation
ii  ros-galactic-turtlebot4-node                        0.1.2-1focal.20220916.172252           arm64        Turtlebot4 Node
ii  ros-galactic-turtlebot4-robot                       0.1.2-1focal.20220915.002707           arm64        Turtlebot4 Robot Metapackage
ii  ros-galactic-turtlebot4-tests                       0.1.3-1focal.20220916.172113           arm64        Turtlebot4 System Tests

ubuntu@tb4rpi:~/tb4rpi/utils$ dpkg -l | grep irobot
ii  ros-galactic-irobot-create-control                  1.0.3-1focal.20220826.015741           arm64        Provides the diff-drive controller for the iRobot(R) Create(R) 3 Educational Robot.
ii  ros-galactic-irobot-create-description              1.0.3-1focal.20220727.092054           arm64        Provides the model description for the iRobot(R) Create(R) 3 Educational Robot.
ii  ros-galactic-irobot-create-msgs                     1.2.4-1focal.20220825.145954           arm64        Package containing action, message, and service definitions used by the iRobot(R) Create(R) platform

slowrunner Nov 23, 2022
Author

Another two chime startup day:
2022-11-23_Create3_Startup_Chimed_Twice.txt

Don't need a solution, as this TurtleBot4lite/Create3 is going to be exchanged with a new one (manufacturing defect).
I'll have it a couple more days for questions or additional testing.

slowrunner · 2023-12-12T00:28:35Z

slowrunner
Dec 12, 2023
Author

Closing - stale issue.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Create3 Repeated chimes - log #246

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 5 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Create3 Repeated chimes - log #246

Uh oh!

slowrunner Nov 21, 2022

Replies: 2 comments · 5 replies

Uh oh!

shamlian Nov 21, 2022 Maintainer

Uh oh!

slowrunner Nov 21, 2022 Author

Uh oh!

Uh oh!

shamlian Nov 21, 2022 Maintainer

Uh oh!

slowrunner Nov 21, 2022 Author

Uh oh!

Uh oh!

slowrunner Nov 22, 2022 Author

Uh oh!

slowrunner Nov 23, 2022 Author

Uh oh!

slowrunner Dec 12, 2023 Author

slowrunner
Nov 21, 2022

Replies: 2 comments 5 replies

shamlian
Nov 21, 2022
Maintainer

slowrunner Nov 21, 2022
Author

shamlian Nov 21, 2022
Maintainer

slowrunner Nov 21, 2022
Author

slowrunner Nov 22, 2022
Author

slowrunner Nov 23, 2022
Author

slowrunner
Dec 12, 2023
Author