the Virtual FlexPendant, the RAPID Editor or the RAPID Tasks window, or, start the program from the
Simulation Play button.
Network Drives and UNC Paths
RobotStudio on computers with roaming user profiles
RobotStudio may fail on PC configurations with roaming user profiles, i.e. when the users’ documents
folder resides on a server and not on the local disk.
Workaround: Redefine the ’User Project Folder’ to a folder on the local disk (File → Options → General →
Files&Folders → User Project Folder).
Virtual Controller does not support UNC paths
UNC paths cannot be used to locate Virtual Controller systems. Using UNC paths for VC systems will
cause the log message ‘Failed to initialize FW upgrade framework’ to appear when the system starts.
Subsequent attempts to work with the VC such as synchronizing RAPID data will fail.
Creating and starting systems located on a network drive
When using a network drive to store RobotStudio data such as RobotWare systems or the RobotWare
mediapool, the following problems may occur:
Virtual controller does not start
Not possible to open Virtual FlexPendant
Cause: By default, the .NET Framework does not allow execution of code from a remote file system. This
means the application may behave unexpectedly if the media used by the system or the system itself
resides on a network share.
Workaround: To resolve this, the user must explicitly grant the required permissions:
1. Open the file
Virtual FlexPendant.exe.config
located in
C:\Program Files (x86)\ABB Industrial
IT\Robotics IT\RobotStudio 5.61\Bin
2. Add the following lines:
<?xml version="1.0"?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
</startup>
<runtime> <!-- THIS IS ONE OF THE NEW LINES!!! -->
<loadFromRemoteSources enabled="true"/> <!-- THIS IS ONE OF THE NEW LINES!!! -->
</runtime> <!-- THIS IS ONE OF THE NEW LINES!!! -->
</configuration>
The Virtual FlexPendant must be restarted for the changes to take effect. For further information, see
http://msdn.microsoft.com/en-us/library/dd409252(v=vs.100).aspx
RAPID
Robtargets that are LOCAL to a PROCEDURE cannot be synchronized with RobotStudio
The RobotStudio synchronization engine that translates 3D data of the station to RAPID code and vice
versa does not support robtargets that are declared locally to a procedure.
Workaround: Declare the robtargets as global or local to a module instead.
To Next Page
Loading...
