[RADF]

No connection with Wlkata Mirobot

Hello, I hope someone can help me. I've already seen a video on LinkedIn:

https://www.linkedin.com/posts/robodk_wl...bdomain=al

Where they managed to connect a Mirobot Wlkata to RoboDK and follow some paths, but I haven't been able to solve that. At the university we have 20 of these robots but it hasn't been possible to do it.

I've tried many combinations:

Physically on the robot:
1- Connecting the USB cable directly to the base of the robot without connecting the control box.



2- Connecting the USB cable directly to the base of the robot and with the control box to the robot.



3- Connecting the USB cable to the control box and this to the robot.




In RoboDK:
1- Using the IP 127.0.0.1 and the port that RoboDK assigns by default using the WlkataDriver.py (it is the only driver that the program has in the list).



2- Using the IP that is configured in the Wlkata Studio 2.03 program IP that it uses for VS-Robot 127.0.0.1 and port 8205.





3- Using the COM port where the robot is connected.






All these combinations of RoboDK with the physical connection combinations of the robot.

-----
The only one that has managed to respond is doing the initialization of the robot using this configuration:

"Using the COM3 port (where I have the robot connected), either of the two ports 12345 or 8502, connecting the USB cable directly to the base of the robot and having the control box connected to the robot."

But it stays on "Connecting to robot COM3:12345" or "Connecting to robot COM3:8502" and can stay like that for hours trying to connect without doing anything.



I can't think of anything else to do.


Can you help me or advise me?
Thanks in advance

[Albert]

Did you start the Wlkata Studio software? Usually the connection should be done to the software itself, which will drive the real robot. Make sure you are not using required ports already when you start the Wlkata Studio software.

[RADF]

Did you start the Wlkata Studio software? Usually the connection should be done to the software itself, which will drive the real robot. Make sure you are not using required ports already when you start the Wlkata Studio software.

Hello, yes, I have done the test without opening Wlkata Studio, with Wlkata Studio open at all time and Wlkata Studio only at startup, and I also use a port monitor to see the status of the COM ports, when I have Wlkata Studio open, RoboDK does absolutely nothing, when I have it closed the only thing RoboDK does is execute a homming but it does not exit from there, it remains in an infinite waiting loop as seen in the images.

[Albert]

Can you try placing the attached file here:
C/RoboDK/api/robot/WlkataDriver.py
And try the connection again by restarting RoboDK?

If you still have issues, could you conact us by email and mention this thread and an updated connection log?

We look forward to fixing this issue. It may be easier if we setup a call with an technical expert:
https://robodk.com/contact

[RADF]

Can you try placing the attached file here:
C/RoboDK/api/robot/WlkataDriver.py
And try the connection again by restarting RoboDK?

If you still have issues, could you conact us by email and mention this thread and an updated connection log?

We look forward to fixing this issue. It may be easier if we setup a call with an technical expert:
https://robodk.com/contact

Hi, I already tried the driver that you shared with me but it didn't work. I've been trying other combinations and nothing. I sent an email months ago but they didn't give me any follow-up, and I don't know what to do.

[Albert]

We published a new version 2 days ago with the new version of the Wlkata driver:
https://robodk.com/download

Can you try again with this version?
If it fails, can you provide us with the connection log?