Two development models - virtual and real

About this section

When trying out a custom application, you can either use a virtual robot controller or a real robot system. This section provides information on how to use both the development models.

Virtual robot technology

The virtual controller of ABB’s RobotStudio allows the IRC5 or OmniCore controller software to execute on a PC, and supports application developers with a purely virtual environment to be used for development, test and debug.

As a real robot controller is normally not readily at hand for application development, virtual technology is very valuable.

Note

You are also strongly advised to study the Release Notes, for all up-to-date information, including new features and any known limitations of the release.

Requirements for virtual environment

The following software components must be installed to develop, test and debug using the virtual environment:

  • Microsoft Visual Studio 2019 or 2022 (Community edition or better)

The RobotWare option PC Interface is not needed in the virtual environment.

Note

For more information, see Installing and Licensing RobotStudio in Operating Manual - RobotStudio.

Requirements for real environment

The following software components must be installed to develop, test and debug using a real robot controller:

  • Microsoft Visual Studio 2019 or 2022 (Community edition or better)

  • Controller option PC Interface

  • Network connection between PC and robot controller

For information about how to set up the network, see How to set up your PC to communicate with robot.

Virtual test and debug

A PC application will run as an independent executable (exe). Using the virtual environment, it targets the virtual controller instead of a real robot controller.

Debugging is easy using the virtual controller and Visual Studio. You attach the application process to Visual Studio, set a break point in the code, and step through it as it executes.

Real tests necessary

The virtual environment is a very convenient choice, especially for testing and debugging.

This means that potential problems may be hard to detect until you test the application using a real robot system.

Porting the application from virtual to real robot controller

As for a PC SDK application, you will hardly notice any difference when using it with a real controller. The only real difference is that the communication between the application and the controller will now be done over a network, which may have an impact on performance.

Deployment to customer

During development, deployment to the controller is done manually. When the development phase is over and the application needs to be deployed to the customer, this should be done differently.

For information about how this should be done, see Deployment of a PC SDK application.