DamAnirban
commented
1 year ago Any Ideas regarding this issue? I have been trying for the past few days to no avail. Any pointers will be really helpful. Thanks.
Closed DamAnirban closed 1 year ago
DamAnirban
commented
1 year ago Any Ideas regarding this issue? I have been trying for the past few days to no avail. Any pointers will be really helpful. Thanks.
AnupamKumarPranav
commented
1 year ago Hi, I am also facing the same issue regarding setup and connecting the robot arm. Need some help.
sugangandhi
commented
1 year ago In the IPV4 section you need to add the ROBOT IP. In my case 192.168.1.1 and netmask 255.255.255.0.
you can check your ROBOT IP in teach pendent and also check your ethernet cable connection.
@DamAnirban @AnupamKumarPranav
DamAnirban
commented
1 year ago Hi @sugangandhi , thanks for responding. Yes the IP, netmask is already added in the IPV4 section. Its 192.168.127.100 and 255.255.255.0 in my case (same in the network settings in the Robot Teaching Pendant). I have added the screenshot of the connection. The error still persists.
sugangandhi
commented
1 year ago Hi @sugangandhi , thanks for responding. Yes the IP, netmask is already added in the IPV4 section. Its
192.168.127.100and255.255.255.0in my case (same in the network settings in the Robot Teaching Pendant). I have added the screenshot of the connection. The error still persists.
Sorry for this, Have you successful in catkin_make.
Then reset your IP in techpendent or
try with reinstall the complete doosan-ros packages.
DamAnirban
commented
1 year ago Hi @sugangandhi . There is no problem with catkin_make. Reset the IP in the pendant also. Did a complete reinstall of the doosan-ros packages....wasnt able to solve it.
Update - I have added more images of the problem.
@doosan-robotics , any ideas will be helpful.
sugangandhi
commented
1 year ago Hi @sugangandhi . There is no problem with
catkin_make. Reset the IP in the pendant also. Did a complete reinstall of the doosan-ros packages....wasnt able to solve it.pdate - I have added more images of the problem.
first one is my network IP second is my A0509 IP DNS -> Automatic Try like this!
DamAnirban
commented
1 year ago No that did not work. But I solved it finally :-). I cant believe the problem was this -> The robot controller was connected directly to my PC. This was the output of the nmap command. The port is closed for some reason.
Then checked all ports-
Clearly, No tcp port is open. So added a network switch in between.
Earlier, Robot Controller<----------------->PC Now, Robot Controller<---------------network switch--------------->PC.
voila -
The port is now open and it works.
Saketh-Vaishya
commented
1 year ago @DamAnirban Hey is the issue resolved with port switch , can you explain more about the solution and what is the exact problem .. Because i have seen many people are not using port switch . Do you think is this a permanent solution
duygiang1162
commented
6 months ago How did you fixed this problem? Please help me
Hi All,
I have a new Doosan A0509s arm. I am trying to run it using ROS.
The virtual mode works and launches properly when using the following -
roslaunch dsr_launcher dsr_moveit.launch model:=a0509The problem arises when I am connecting the Real robot. I am running the following -
roslaunch dsr_control dsr_moveit.launch model:=a0509 host:=192.168.137.100 mode:=realBut, I am getting the following errors -
I am adding the terminal+error details, robot connection details in the files attached. I am also adding the terminal details of the virtual mode which is working ok. I am able to ping to 192.168.137.100 when using the real robot, but ROS is unable to connect to it.
System details - Ubuntu 20.04 Ros Noetic
Can you please help me debug this issue?
Thank you.
Update : I have tried -
$sudo -icd into catkin workspace, source. Then run the roslaunch. Did not work.$sudo ufw statusShows inactive. My pc is connected directly to the controller via ethernet cable.ROS -
Error -
Laptop Connection -
Robot Teaching Pendant -
Entire Terminal when I run Roslaunch -