UAS Grants in Off-Line Programming

RobotStudio
1

Hi
I am unable to start simulations due to lack of “grants”.
I’m not connected to a robot, just using the virtual controllers.
I’m using RS & RW5.14.01.

How can I change the UAS grants while being off-line?

Thanks.

2

Here is a little more detail.

I never had this problem in the past, it started today, and all my RS stations are doing it. It must be some kind of configuration of RobotStudio itself…

If I click on the “Play” button in the simulation window, it pops the following messages in the “output” window, stating the following errors:

  • Could not set program pointer to entry point for Task
  • The program could not be started
  • Program Pointer has been reset
  • Start Program
    But nothing happens.

If I open the Virtual FlexPendant, I can use the program editor to move the program pointer to main and start the program. The robot returns home.
However, when I use our screenmaker HMI on the virtual flexpendant, if I click on any button on the HMI, it gives the following error:
Message: SYS_CTRL_E_UAS_REJECT: The operation was not allowed for the given user. Error Code: (0xc0048415)

I’m downloading v5.14.03 of RobotStudio to see if re-installing it will fix it…

3

The UAS configuration is suppressed for VCs. The reason is to prevent users from locking themselves out. The UAS files for the PC are located in the folder

C:UsersAppDataRoamingABB Industrial ITRobotics ITRobVC
The path is valid for Windows 7 - 64 bit edition. For XP the path starts a “Documents and Settings” but the last part is similar. To see it, you must enable Windows Explorer to show hidden files and folders.

Please proceed as follows to reset your UAS configuration

  1. Close all instances of Virtual Controllers and RobotStudio
  2. Make a backup copy of the folder RobVC and its content.
  3. Delete the original RobVC folder.
  4. Restart RobotStudio and load your station
    → The UAS files are re-created from the default configuration.

For the curious user there is, however, a workaround that enables you to actually modify the UAS files for the virtual controller:

  1. Start RobotStudio and add a virtual controller to your station.
  2. Start another instance of RobotStudio and add the locally running VC from the Online tab. This functionality is available in 5.14.03 but not in earlier versions.
  3. Request write access,
  4. Now, you can edit UAS on the PC.
4

Great!
Thanks Henrik. That fixed it.