UnderAutomation
Eine Frage?

[email protected]

Kontakt
UnderAutomation
⌘Q
Diese Seite ist nur auf Englisch verfügbar.

Work without a robot

The simulator of each robot maker: ROBOGUIDE, MotoSim, URSim, RobotStudio and Stäubli Robotics Suite. How to connect to it, what each brand page says about its limits, and what has not been tested with the common API.

  • Prerequisites
  • What is tested
  • Example
  • Connection parameters of the simulators
  • Fanuc: ROBOGUIDE
  • Yaskawa: MotoSim
  • Universal Robots: URSim
  • ABB: RobotStudio
  • Stubli: Stubli Robotics Suite
  • Reference
  • What to read next

This page explains what you can use instead of a robot to develop with UnderAutomation.Robotics: the simulator of each robot maker, how to connect to it, and what its brand page says about the limits. It applies to Fanuc, Yaskawa, Universal Robots, ABB and Stäubli.

A simulator of a robot maker runs the software of the controller on a PC. The Fanuc, Universal Robots, ABB and Stäubli SDKs connect to it with the same protocols as to a real controller. Yaskawa is the exception, see the MotoSim section. The simulators are products of the robot makers, with their own licenses.

Prerequisites

  • The simulator of your brand (not for Yaskawa: see MotoSim), installed and started on a PC, with a cell or a station that has your robot and the options of your real cell.
  • The license of the brand, or the 30 day trial, as for a real controller. See Licensing.
  • The connection settings of Connect to your robot. A virtual controller has the same settings as a real one: services, remote mode, user and password.

What is tested

The pages of the brand SDKs describe the simulators that they were used with. The common API takes the same connection parameters, but it has not been run on the simulators yet. A method of the common API that works on a real controller can behave differently on a simulator, and the opposite. Test each method that your application calls on your simulator before you rely on it.

The page of each service says which methods a brand has: a simulator cannot add a method that the brand does not have. See Routing.

Example

Connection parameters of the simulators

Each brand SDK has its own way to reach its simulator: a folder, the address of the PC, or a file. This example builds the parameters of every simulator listed here, except MotoSim, with the settings of their brand pages. MotoSim is not in it: see its section.

static void Main()
{
// Fanuc ROBOGUIDE: the folder of the virtual robot, with the file services.txt that gives its ports
UnderAutomation.Fanuc.ConnectionParameters fanuc =
new UnderAutomation.Fanuc.ConnectionParameters(@"C:\Users\you\Documents\My Workcells\CRX 10iA L\Robot_1");
// ABB RobotStudio: the virtual controller answers on this PC. RobotWare 7 uses RWS 2.0. Set UseHttps to what the virtual controller answers on
UnderAutomation.ABB.ConnectionParameters abb = new UnderAutomation.ABB.ConnectionParameters("127.0.0.1");
abb.Rws.Version = UnderAutomation.ABB.Rws.RwsVersion.OmniCore_V2_0;
abb.Rws.UseHttps = true;
// Universal Robots URSim PolyScope X in Docker, started with the port 80 of the container on the port 8080
UnderAutomation.UniversalRobots.ConnectParameters ur = new UnderAutomation.UniversalRobots.ConnectParameters("127.0.0.1");
ur.Rest.Port = 8080;
// Stäubli Robotics Suite: the .controller file of the emulated controller
UnderAutomation.Staubli.ConnectionParameters staubli =
new UnderAutomation.Staubli.ConnectionParameters(@"C:\Users\me\Documents\Staubli\SRS\MyCell\Controller1\Controller1.controller");
RobotConnectionParameters[] simulators = { fanuc, abb, ur, staubli };
foreach (RobotConnectionParameters parameters in simulators)
{
RobotController robot = new RobotController();
robot.Connect(parameters);
Console.WriteLine($"{robot.Brand}: {robot.Info.Read().Model}");
robot.Disconnect();
}
}
}
Click to see the full code

The sections below say what each brand page tells about its simulator.

Fanuc: ROBOGUIDE

The virtual controller of ROBOGUIDE runs the controller software of the workcell. The brand page says that every function of the Fanuc SDK sends the same requests to ROBOGUIDE and to a real controller.

  • The options of the controller are the ones chosen when the workcell is created. A protocol that needs an option on a real controller needs it in the workcell too: see the table of the brand page.
  • The address is the folder of the robot in the workcell, not an IP address. The folder holds services.txt, which gives the ports of the virtual robot. With an IP address, the SDK uses the default ports of a real controller.
  • The inputs and outputs of the virtual robot are not wired: simulate the inputs.
  • Telnet KCL needs a port to enable on the virtual robot, and ROBOGUIDE V10 does not simulate it.
  • Timings are not the timings of the real controller: do not measure cycle times on the simulator.

Brand page: Test with ROBOGUIDE.

Yaskawa: MotoSim

MotoSim EG-VRC is the offline programming and simulation software of Yaskawa. The brand page says that MotoSim does not simulate the network of the controller: its virtual controller does not answer the High Speed Ethernet Server, so the Yaskawa SDK cannot connect to it. The common API uses the Yaskawa SDK, so it has the same limit.

To test the connection and the methods, the brand page asks for a controller with the High Speed Ethernet Server enabled: a real controller, or a debug controller on a test bench, of the same generation as your cell. The brand page says that every function of the SDK that does not move the robot can be tested on a debug controller.

MotoSim and the SDK work on the same job files: teach and check a job in MotoSim, export it, send it to the controller and start it. To develop without a controller, keep the calls to the robot in one class of your application and test the rest with a fake of this class.

Brand page: Develop without a robot.

Universal Robots: URSim

URSim runs the software of the controller. The brand page describes URSim PolyScope and URSim PolyScope X.

SimulatorRobotsRuns in
URSim PolyScopeCB-Series and e-SeriesA Linux virtual machine in VirtualBox
URSim PolyScope XRobots with PolyScope XA Docker container
  • On URSim PolyScope, the address of the robot is in the menu of PolyScope. The services and the remote control are set in PolyScope, as on a robot.
  • On URSim PolyScope X, connect to 127.0.0.1. The container publishes the ports of the interfaces that you list in the docker run command. The brand page gives the command and says which interfaces PolyScope X has. When the port 80 is mapped to another port, set the port of the REST API in the parameters.
  • To accept commands, PolyScope X must be in remote control.
  • The Linux user and the folder of the programs are not the ones of a robot.

Brand page: Develop without a robot (URSim).

ABB: RobotStudio

RobotStudio runs a virtual controller on the PC. The brand page says that it answers Robot Web Services like a cabinet on the network, and that the whole ABB SDK works against it.

  • The virtual controller answers on 127.0.0.1. The RobotWare of the station gives the version of the web services: RobotWare 6 is an IRC5 controller, RobotWare 7 and later an OmniCore controller. Set Version and UseHttps to match.
  • The system must include the options that your code uses. A request for a missing option is refused with an error that names the option.
  • A virtual controller simulates the robot software, not the hardware. Some resources are not implemented: the brand page lists them, and the SDK says that the resource needs a real controller.
  • No signal of a bare virtual controller can be written, until the system is built with an I/O configuration.
  • Moves and many writes depend on the operating mode and on the mastership, as on a real controller.

Brand page: Test with a RobotStudio virtual controller.

Stäubli: Stäubli Robotics Suite

The emulator of the CS8 or CS9 controller of Stäubli Robotics Suite runs the controller software. The brand page says that every function of the Stäubli SDK sends the same requests to the emulator and to a real controller.

  • The address is the path of the .controller file of the emulated controller, not an IP address. The SDK reads the SOAP port in the configuration of the emulated controller, next to this file. A UNC path reaches the emulator of another PC: allow the SOAP port in its firewall.
  • The user and the password are the ones of the emulated controller.
  • Power and moves need the remote mode on the emulated controller too.
  • The emulator has no FTP server: the file client reads and writes the folder of the .controller file.
  • The input and output boards are the ones of the cell in Stäubli Robotics Suite, so the names can differ from your real cell.
  • Timings are not the timings of the real controller.

Brand page: Test with the Stäubli Robotics Suite emulator.

Reference

The brand pages are the reference of each simulator: they describe its settings, its connection and its limits. This table lists them.

BrandSimulatorWhat you give as addressBrand page
FanucROBOGUIDEThe folder of the robot in the workcellTest with ROBOGUIDE
YaskawaMotoSim EG-VRC, not reachable by the SDKA real or debug controllerDevelop without a robot
Universal RobotsURSim PolyScope and URSim PolyScope XThe address shown by PolyScope, or 127.0.0.1Develop without a robot (URSim)
ABBRobotStudio127.0.0.1Test with a RobotStudio virtual controller
StäubliStäubli Robotics SuiteThe .controller file of the emulated controllerTest with the Stäubli Robotics Suite emulator

The brand SDK objects stay available on the same connection with robot.Native: see Connect to your robot.

What to read next

  • Connect to your robot: the connection parameters of each brand.
  • Errors: read the result of each protocol when Connect fails.
  • Routing: which protocol each method uses.
  • Get started with .NET: a first program.