BUG: RobotStudio 5.13 RAPID Synchronization Dialog

Henrik Berlin

Background: The user interface for RAPID Synchronization between a RobotStudio station and a Virtual Controller has been remade to support synchronization of single data, which is a new feature of RS 5.13. The new design also supports sorting of paths. Unfortunately, two small bugs have entered the code without being discovered in time to be fixed for the 5.13 release. The problems will be fixed in RobotStudio 5.13.01 that will be available around the end of Q2 2010.

--------------------------------------------------------------------------------------------

Problem 1: Synchronize to VC may fail even though reported as success

Symptom: The problem may appear on controller systems that contain RAPID procedures that take arguments, see the example draw_square below that takes the argument named side_size of type num.

PROC draw_square(num side_size)

! ....

 

ENDPROC

These kind of procedures now erroneously appear in the dialog Synchronize to Station and can be selected for synchronization to the RobotStudio station. In the next step when synchronizing back to the Virtual Controller, these procedures cause the command Synchronize to VC to fail silently, even though the message ?_~Synchronization to VC completed?_T appears in the Output window.

Workaround: Delete the procedures and redo the Synchronize to VC command.

--------------------------------------------------------------------------------------------
Problem 2: Single data not synchronized when task is checked in Synchronize to VC

Symptom: When selecting an entire task in the Synchronize to VC dialog, only the paths (including referenced data) will be synchronized, not single data that are not referenced by a path, even though checked for synchronization.

Workaround: Select the single data only for synchronization.

--------------------------------------------------------------------------------------------

We apologize for any inconvenience these problems may cause.

Henrik Berlin

This problem is fixed in RobotStudio 5.13 with Patch 1, see http://forums.robotstudio.com/forum_posts.asp?TID=4009.