You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The driver in tmrlib keeps reconnecting, even after the connection is reported to be ok.
To reproduce:
Start the listennode on the cobot
Start the tmr_driver - most of the times the tmr_driver connects
stop the listennode - tmr_driver starts trying to reconnect
start the listennode
tmr_driver will report that the TM robot is connected, but it will keep trying to reconnect forever.
Below the output of starting the listennode after the tmr_driver is started, which will produce the same behavior. I added printing of the return code from the sct_func function
[INFO] [tmr_sct]: (TM_SCT) connect(1000ms)...
[ INFO] TM_COM: ip:=192.168.2.47
[ INFO] TM_COM: rv:=0
[ INFO] TM_COM: Connection is ok
[ INFO] TM_COM: O_NONBLOCK connection is ok
[ INFO] TM_COM: TM robot is connected. sockfd:=33
[ERROR] [tmr_sct]: Received communication feedback code: 3
[INFO] [tmr_sct]: (TM_SCT): sct_func returned false
[INFO] [tmr_sct]: (TM_SCT) reconnect in 3 sec...
[INFO] [tmr_sct]: (TM_SCT) connect(1000ms)...
[ INFO] TM_COM: ip:=192.168.2.47
[ INFO] TM_COM: rv:=0
[ INFO] TM_COM: Connection is ok
[ INFO] TM_COM: O_NONBLOCK connection is ok
[ INFO] TM_COM: TM robot is connected. sockfd:=33
[ERROR] [tmr_sct]: Received communication feedback code: 3
[INFO] [tmr_sct]: (TM_SCT): sct_func returned false
[INFO] [tmr_sct]: (TM_SCT) reconnect in 3 sec...
[INFO] [tmr_sct]: (TM_SCT) connect(1000ms)...
[ INFO] TM_COM: ip:=192.168.2.47
etc. etc.
As you can see the TM_COM prints out Connection is ok and that TM robot is conneted. sockfd:=33, but it returns a feedback code 3 (CommRC::NOTCONNECT) however, causing the tmr_sct driver to keep trying to reconnect.
The text was updated successfully, but these errors were encountered:
janandries
changed the title
Connection fails (CommRC::NOTCONNECT) when starting tmr_controller node after ListenNode program
tmr_driver keeps reconnecting
Jul 1, 2021
Hi there ! Same error here but starts immediatly after first connect. Did you manage to solve it ?
I'lll try to on my own and keep you updated if I succeed.
Bye
After configuring the PC's IP adress on Ubuntu changes were effective only after reboot
The issue was coming from the ethernet slave configuration. After setting the table, when saving it the name has to be Data_Table_Setting_TM_ROS_Default
The driver in
tmrlib
keeps reconnecting, even after the connection is reported to be ok.To reproduce:
Below the output of starting the listennode after the tmr_driver is started, which will produce the same behavior. I added printing of the return code from the
sct_func
functiontmr_ros2/tmr_driver/src/tmr_ros2_sct.cpp
Line 129 in d4841bb
Output:
... here I start the ListenNode in the TMFlow ...
etc. etc.
As you can see the TM_COM prints out
Connection is ok
and thatTM robot is conneted. sockfd:=33
, but it returns a feedback code 3 (CommRC::NOTCONNECT
) however, causing the tmr_sct driver to keep trying to reconnect.The text was updated successfully, but these errors were encountered: