RobotStudio event

Developer Tools 5.13.02 is available!

Options

Dear Developer Tools users,

Developer Tools 5.13.02 has been released and is available for download from the RobotStudio Community (http://www.robotstudio.com/community).

The Developer Tools includes:
  • FlexPendant SDK
  • PC SDK
  • RobotStudio SDK
 

The Developer Tools are part of the RobotStudio 5.13.02 installer.

RobotStudio and Developer Tools are shipped with RobotWare which means that there is one common image. 
  
Installation and Upgrade
  • FlexPendant SDK 5.13.02 will upgrade any existing installation of FlexPendant SDK 5.13 or FlexPendant  5.13.01
  • PC SDK 5.13.02 will upgrade any existing installation of PC SDK 5.13 or PC SDK 5.13.01
  • RobotStudio SDK 5.13.02 will upgrade any existing installation of RobotStudio SDK 5.13 or RobotStudio SDK 5.13.01

Note: Users that are upgrading from RobotStudio 5.13 or 5.13.01 are recommended to perform an installation Repair directly after the installation has completed. The reason is that two files required for FlexPendant SDK and ScreenMaker will be missing otherwise (ABBct.exe and ABBct.exe.config). This is not needed if performing a so-called clean installation where no previous version of RobotStudio 5.13 is installed on the computer.

What's New (5.13 - 5.13.02) 

Starting with RobotStudio 5.13, the FlexPendant SDK and PC SDK are distributed as a part of the RobotStudio installer. They are installed with the Complete
installation of RobotStudio and can optionally be installed with the Custom installation
option. 

 

PC SDK


Improved support for 64-bit operating systems

Some PC SDK methods which internally relied on FTP file transfer between the PC and IRC5 controller failed on a 64-bit operating system, where the program files folder had a paranthesis in the path. E.g "Program Files (x86)". Previous versions threw an exception.

 

Access RAPID data declared in hidden and installed modules

It is now possible to access RAPID data that are declared in hidden modules, in hidden tasks, and in installed modules. Such data are not included in a Search Symbol result, and can only be accessed if the name and location of the data is known by the developer.

 

For example you can use Rapid.GetRapidData to access a data declared in an installed module.

// Access data declared in an installed module <?: prefix = o ns = "urn:schemas-microsoft-com:office:office" /><?: PREFIX = O />

// An installed module is loaded from a install script using the -install option.

RapidData data = controller.Rapid.GetRapidData("T_ROB1", "#SYS", "num4");


 

Simulate physical setting of input signals on a Virtual Controller
It is now possible to simulate the physical setting of the value of an input signal. The previously existing method to set the value of a signal is similar to setting a signal from RAPID. Depending on the Access Level the controller safety system may or may not allow the signal value to be changed. When a physical signal is set by connecting it to +24V the controller cannot prevent it from happening, no matter what Access Level the

signal has.

 

Use Signal.InputAsPhysical to set get the same behaviour as a setting a signal physically (by connecting the I/O board to 24V)

 

Controller start mode "-I" now available

It is now  possible to do a I-Start via PC SDK. A new enum value, IStart, has been added to the enum ControllerStartMode.

 

Example:

using (Mastership.Request(m_controller.Rapid))

using (Mastership.Request(m_controller.Configuration))

{

   m_controller.Restart(ControllerStartMode.IStart);

}

 

RobotStudio SDK

 

API Reference Documentation can be launched from RobotStudio Help menu
You can launch the RobotStudio API Reference documentation from the RobotStudio Help menu, or using the shortcut Alt+F1.


XML Schemas documented
The RobotStudio SDK public XML Schemas are documented in the reference documentation.

Visual Studio Project Template for Smart Component Code Behind
A new template is available that helps you get started with developing a Smart Component with Code Behind. The template project includes C# source for a Code Behind class, the XML source for the Smart Component library and a post build step that calls the LibraryCompiler.exe to compile the component and embeds the Code Behind assembly as an asset.

LibraryCompiler.exe
The commandline tool LibraryCompiler.exe, can be used to automate the creation of RobotStudio library files, such as Mechanism and Smart Components from XML library source files.
 
Please refer to the RobotStudio SDK 5.13.02 Release Notes for an extensive list of new classes and methods.


Niklas Skoglund
ABB 
Niklas Skoglund2010-10-20 10:41:24

Best Regards, Niklas Skoglund
ABB Robotics

Developer Center
RobotStudio Blog