Error when connecting real robot

ROSDS Support
1

Hi,
I am not sure if this is an error or somethin else. I just finished one online presentation this week. Maybe because during the process I need more time to connect with robot, I was allowable to book more than 2 booking in this week. And afterwards, I find that I can still book more than 2 appointments.
But when I test my code in these extra bookings, I always met with some weird errors, this is one of them:

[INFO] [1681492147.712145]: The service: /find_wall is found
[INFO] [1681492147.864953]: robot is looking for the wall......
[INFO] [1681492148.024390]: the service server is ready
[INFO] [1681492148.077283]: call the service by:
[INFO] [1681492148.129466]: rosservice call /find_wall
shutdown request: user request
signal_shutdown hook error[cannot join current thread]
shutdown request: user request
signal_shutdown hook error[cannot join current thread]
[find_wall_2_node-1] process has finished cleanly
log file: /home/user/.ros/log/70a20ef2-dae5-11ed-8723-b827eb45ef28/find_wall_2_node-1*.log
Traceback (most recent call last):
  File "/opt/ros/noetic/lib/python3/dist-packages/rospy/impl/tcpros_service.py", line 522, in call
    responses = transport.receive_once()
  File "/opt/ros/noetic/lib/python3/dist-packages/rospy/impl/tcpros_base.py", line 737, in receive_once
    self.stat_bytes += recv_buff(sock, b, p.buff_size)
  File "/opt/ros/noetic/lib/python3/dist-packages/rospy/impl/tcpros_base.py", line 109, in recv_buff
    raise TransportTerminated("unable to receive data from sender, check sender's logsfor details")
rospy.exceptions.TransportTerminated: unable to receive data from sender, check sender's logs for details

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/user/catkin_ws/src/section_topics/scripts/FindWall_FollowWall.py", line 157, in <module>
    wall_following = Wall_Following_Class()
  File "/home/user/catkin_ws/src/section_topics/scripts/FindWall_FollowWall.py", line 80, in __init__
    self.find_wall_restult = self.my_Service_client(
  File "/opt/ros/noetic/lib/python3/dist-packages/rospy/impl/tcpros_service.py", line 442, in __call__
    return self.call(*args, **kwds)
  File "/opt/ros/noetic/lib/python3/dist-packages/rospy/impl/tcpros_service.py", line 530, in call
    raise rospy.exceptions.ROSInterruptException("node shutdown interrupted service call")
rospy.exceptions.ROSInterruptException: node shutdown interrupted service call
[find_wall_follow_wall_node-2] process has died [pid 1623, exit code 1, cmd /home/user/catkin_ws/src/section_topics/scripts/FindWall_FollowWall.py __name:=find_wall_follow_wall_node __log:=/home/user/.ros/log/70a20ef2-dae5-11ed-8723-b827eb45ef28/find_wall_follow_wall_node-2.log].
log file: /home/user/.ros/log/70a20ef2-dae5-11ed-8723-b827eb45ef28/find_wall_follow_wall_node-2*.log
all processes on machine have died, roslaunch will exit
shutting down processing monitor...
... shutting down processing monitor complete
done

I have no idea where this shutdown request: user request came from. I am curious whether this is kinda punishment of having booked more 2 appointments in one week, or the problem from my code(If it is this case, I will be more confused about). I hope it is kinda punishment actually :sweat_smile: Then maybe I can return to normal situation in the legal 2 bookings in next week…
Jialei Li

2

Hello @MeineLiebeAxt ,

Checking at this older post, it seems to be related to the speed limit in the real robot:

3

Hi,
thanks for your advice. But I never set my speed larger than 1. And actually it is not always to come cross this kind of problem. Sometimes just re-connect real bot can solve the problem. But frequent reconnection is also problematic…I am not sure if this is just a random problem.
Jialei Li

4

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.