RobotStudio event

Really annoying BUG - still in RS 5.14.03

Laro88
Laro88 ✭
in RobotStudio
I haven't paid attention to the evolution of RS5.14.03 but I noticed the continued precense of one today.
Scenario:
0. Go online using robot studio on a robot and open a file containing a specific wobj
1. Modify a wobj using three point on a real robot - resulting in a new wobj. Program is fine and so on.
2. reboot everything a couple of times, wait a week for example (like me) and then go online again and look at the wobj.

IT IS THE SAME OLD WOBJ being shown in RS although everything including pcs etc has been hard rebooted several times AngryAngryAngryAngry

Now - click "request write access" and BINGO - the real content of the wobj is magically present.

THIS IS REALLY BAD - because copying the content using RS uses and shows old data until write permission is requested.

Damn this is an annoying BUG in RS Dead which I "renoticed" again!!!.


Comments

  • Henrik Berlin
    Henrik Berlin ✭✭✭


    Hi,
     
    This behaviour is due to that work objects are defined as PERS-variables (persistents) that have a different behaviour compared to regular variables.
     
    PERS-variables are stored in some database in the controller memory. When such a variable is changed, the module that contains the inital value of the PERS must be updated. This is normally done when the editor is opened to view the file or when the module is saved, to name a few examples.
     
    In your particular case, the value was changed from the FlexPendant (that did not update the RAPID code, since the editor of the FlexPendant was never opened). Instead, the module was opened from RobotStudio. Unfortunately, RobotStudio could not update the module, since it requires write access to do the update. When RobotStudio got the write access, the module was updated.
     
    In this particular case, the problem would have been avoided if the FlexPendant updated the module contatining the workobject definition with the new value. Consequently, if this is a bug, it is a problem of the FlexPendant.

    Thank you for brining this problem to our attention.
    Henrik Berlin
    ABB
  • Laro88
    Laro88 ✭
    Might be right Henrik, however...

    I used the physical flexpendant to jog the robot and to use the "define 3 points" method, and I looked at the numbers on the flexpad when the definition was completed.

    You are right, the textual editor was not opened on the flex pad, unfortunately, I just looked at the numbers directly on the flexpad immediately after the definition.

    It seemed like the work object was updated in the robot controller (coordinates seemed ok when the robot performed motions ) - rather Robot Studio did not show the correct values until I requested write access.

    I hope you find a valid solution for this "caching" effect, I had a silimar problem with a rapid program a while ago - it was also incorrect until I requested write acess!

Categories

In this Discussion