Welddata: Wrong definition ofr arcdata

DominikF
DominikF ✭
in RAPID Programming
I want to define welddata wd1in RobotStudio. 

PERS welddata wd1:=[3,0,[1,0,26,11,0,206,0,0,0],[0,0,0,0,0,0,0,0,0]];

I normally define 9 values for the arcdata. When I do that, RobotStudio reports an error and requires 10 values.

It might be a basic question, but what did I do wrong here, or do I need to change something?
Thank you in advance. I am a beginner concerning this definitions.

Answers

  • matti
    matti ✭
    Hallo, according to manual (3HAC050988-001 Rev.G) 9 is the maximum of values for arcdata if everything is unmasked. Maybe you try to define "PERS arcdata testd" in RSO. Move the cursor over "arcdata" and check the fly-out.
  • DominikF
    DominikF ✭
    Thank you matti!
  • DominikF
    DominikF ✭
    I checked it the different documentations and also the one that you have recommended. 

    However, when I define the input with 9 values for the arcdata like that:

    PERS welddata wd:=[4.5,0,[1,0,24.75,10.5,0,266,0,0,0],[0,0,0,0,0,0,0,0,0]];

    RobotStudio highlights an error, stating that it needs 10 inputs for the arc data.
    Do I have to define any special settings?
    I have installed the ArcWare 7+ for OmniCore.

    Thank you in advance!

  • mandolas
    mandolas ✭
    edited April 8
    Hi ...
    In more recent versions, the welddata structure has included a tenth parameter, usually related to arc voltage or some new additional parameter, such as burnback time, depending on the setup.
    PERS welddata wd1 := [3, 0, [1,0,26,11,0,206,0,0,0], [0,0,0,0,0,0,0,0,0], 0];
    That last 0 could represent, for example, a default value of arc voltage or another additional parameter that your system version expects.

    Good Job
  • matti
    matti ✭
    Hallo, when moving the pointer over the welddata-type, a flyout should show what the interpreter expects.
  • DominikF
    DominikF ✭
    Thank you mandolas & matti for your support! I tested the different syntax for the welddata for RobotWare 7.xx and 6.xx and it worked in RobotStudio, without showing an error.

Categories

In this Discussion