UFACTORY Studio simulation

1

A way to run UFACTORY Studio without real robot.

1.Get the docker image

docker pull danielwang123321/uf-ubuntu-docker

2.Create and run container

On Linux Ubuntu

docker run -it --name uf_software danielwang123321/uf-ubuntu-docker

On Windows
If only use UFACTORY Studio

docker run -it --name uf_software -p 18333:18333 danielwang123321/uf-ubuntu-docker

If you want use not only the UFACTORY Studio but also the xArm SDK on Windows, please use this command:

docker run -it --name uf_software -p 18333:18333 -p 502:502 -p 503:503 -p 504:504 -p 30000:30000 -p 30001:30001 -p 30002:30002 -p 30003:30003 danielwang123321/uf-ubuntu-docker

3.Run the xArm robot firmware and UFACTORY Studio

/xarm_scripts/xarm_start.sh 6 6

The 6 6 means xArm 6, change it accordingly if you prefer other robots:

5 5, xArm 5
6 6, xArm 6
7 7, xArm 7
6 9, Lite 6
6 12, 850

4.Access the UFACTORY Studio

On Linux Ubuntu
Run a web browser and input 172.17.0.2:18333

On Windows
Run a web browser and input 127.0.0.1:18333

If you need use xArm SDK,
Ubuntu Linux: the robot IP is 172.17.0.2

Windows: the robot IP is 127.0.0.1

Note:
Test under Ubuntu 24.04 and Windows10

1 Like
2

Hi Daniel

I tried your instructions, it’s very easy now, thanks a lot. However, I had to modify some parts to make it work.

First, when I created the container, I had to expose port 18333 like this:

docker run -it --name uf_software -p 18333:18333 danielwang123321/uf-ubuntu-docker

Lastly, even though the IP of the bot is the one you mention, I had to use http://localhost:18333 to access the simulator in my web browser

image
image1362×680 73.7 KB

image
image1365×679 74.8 KB

1 Like
3

Hi Fabian,
Did you use the Windows?
I did a test on Windows 10 and found it do requires to expose the port while creating the container.
The url on windows is 172.0.0.1:18333 after execute the below command and start the robot software.
docker run -it --name uf_software -p 18333:18333 danielwang123321/uf-ubuntu-docker
Let me modify the guidance.

4

Hi Daniel,

Yes, I use Windows 10

5

Hi Fabian,
Thanks for your feedback, I did update the guidance for Windows.
Please let me know if you have any questions.

6

Hello, I have the simulator up and running, thanks for making that possible. The sim is telling me that the contents of the friction file are invalid. Is there a way I can get around this?
image

7

Please provide more information

  1. The platform, windows or linux?
  2. The firmware/software version of the information page like that.
  3. Did you update the software/firmware?
    image
    image2598×1775 256 KB
8

Thanks for replying Daniel, I figured it out. I do not have an arm at the moment, I am only playing with the sim. I got around the alert to get the sim working.

9

Thank you for your feedback! We’re glad to hear that you managed to resolve the issue. The purpose of our simulation environment is precisely to support users who may not have access to a physical robot temporarily, allowing them to learn and develop in a virtual environment.

If you encounter any further issues while using the simulator, please don’t hesitate to reach out. We’re here to assist you!

Wishing you continued success with your projects! :blush:

10

Hi Daniel,

Thanks a lot for the input. I also managed to use the simulator for days. However, I found that, once I restarted my laptop, I couldn’t access the simulator but this can be solved by following the instructions again and removing the previous container.

This would cause some troubles because the scripts tried on the previous container would also disappear. Do you have advice on solving this?

Regards,
Lee

11

Thanks for the feedback.
Maybe the problem is after you restarting your computer, you craeted a new container insteat of starting the previouse container. Here is the normal steps to start the previouse contrainer on Winodws. Please give a try and let me know the result.

  1. Start the container by docker start command on your windows shell.
docker start uf_software
  1. Enter the shell of the container
docker exec -it uf_software /bin/bash
  1. Start the xArm 6 firmware and the ufactory studio on the shell of the container
/xarm_scripts/xarm_start.sh 6 6