1. Home
    1. Dashboard
    2. Search
  2. Forum
    1. Unresolved Threads
    2. Members
      1. Recent Activities
      2. Users Online
      3. Team Members
      4. Search Members
      5. Trophys
  3. Articles
  4. Blog
  5. Videos
  6. Jobs
  7. Shop
    1. Orders
  • Login or register
  • Search
This Thread
  • Everywhere
  • This Thread
  • This Forum
  • Articles
  • Pages
  • Forum
  • Blog Articles
  • Products
  • More Options
  1. Robotforum - Support and discussion community for industrial robots and cobots
  2. Forum
  3. Industrial Robot Support and Discussion Center
  4. KUKA Robot Forum
Your browser does not support videos RoboDK Software for simulation and programming
Visit our Mainsponsor
IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Sponsored Ads

program module attibutes?

  • panic mode
  • February 6, 2020 at 8:45 PM
  • Thread is Unresolved
  • panic mode
    Reactions Received
    1,300
    Trophies
    11
    Posts
    13,144
    • February 6, 2020 at 8:45 PM
    • #1

    anyone has info on some of the attributes such as &ACCESS or &PARAM.

    Some are obvious, such as V in &ACCESS is Visible.

    And &PARAM TEMPLATE shows name of template path and name used to create the program. But what is &PARAM EDITMASK *?

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

  • massula
    Reactions Received
    205
    Trophies
    8
    Posts
    1,440
    • February 6, 2020 at 11:53 PM
    • Best Answer
    • #2

    I don't know what it's real purpose, but is PARAM EDITMASK is used on VKRC robots, and I suppose it is a way to inform VSS what a user can or can't do on that specific program.

    VKRC has a strict program naming convention.

    So regular users can only create/manipulate programs named Folge(n), UPs or Makros, where the first is like a main program, the middle is a subprogram, and the later is somewhat a function (doesn't return values, but You can't put movement instructions inside).

    These names can be only appended by a number suffix, like Folge1, UP99 and Makro0. On a VKRC, if You put a module named, lets say, Prog01, compiler will complain and give You a red cross.

    There are some special makros, like MakroTrigger, MakroSPS and MakroSAW.

    VKRC robots also have VW_User, a meta thecnology package containing VW (not so) secret sauce. You can be more creative naming programs inside VW_USer area, but integrators shouldn't touch these programs, unless under very special circumstances.

    So, a header from a VKRC4 folge is like this

    Code
    &ACCESS RVO1
    &REL 39
    &COMMENT VWxxx
    &PARAM DISKPATH = KRC:\R1\Folgen
    &PARAM TEMPLATE = C:\KRC\Roboter\Template\vorgabe
    &PARAM TPVW_VERSION = 8.1.8
    &PARAM EDITMASK = Folge999[1-999]

    A header from a UP

    Code
    &ACCESS RVO1
    &REL 46
    &COMMENT VWxxx
    &PARAM DISKPATH = KRC:\R1\UPs
    &PARAM TEMPLATE = C:\KRC\Roboter\Template\upvorgabe
    &PARAM TPVW_VERSION = 8.1.8
    &PARAM EDITMASK = Up999[1-999]

    The header fom a regular Makro (Makro50)

    Code
    &ACCESS RVP2
    &REL 1
    &COMMENT INICIALIZACAO MARCAS
    &PARAM TEMPLATE = C:\KRC\Roboter\Template\makrovorgabe.src
    &PARAM TPVW_VERSION = 8.1.8
    &PARAM EDITMASK = Makro999[0-999]

    The header from MakroSPS, a special cyclic makro (acts like a .sub)

    Code
    &ACCESS RVO1
    &REL 18
    &COMMENT MAKRO_SPS_LASER
    &PARAM TEMPLATE = C:\KRC\Roboter\Template\makrospsvorgabe.src
    &PARAM TPVW_VERSION = 8.1.8
    &PARAM EDITMASK = MakroSPS

    And, finally, the header fom a VW_USER file (vw_usr_r.src)

    Code
    &ACCESS R
    &COMMENT LA_KS24.06.015_VW
    &PARAM DISKPATH = VW_User
    &PARAM EDITMASK = vw_usr_r
    &PARAM TPVW_VERSION = 8.1.8
    &REL 438
  • Stavros Tsalikis
    Reactions Received
    2
    Trophies
    2
    Posts
    1
    • June 18, 2021 at 7:06 AM
    • #3

    I know it is an old post and additionally i'm new to robot programming but i might found a clue about the &Access parameter. If you choose a module and press the edit button, under properties you can see 3 tabs. In the first tab you can select if you want your file to be hidden, write protected etc. This changes the access modifiers accordingly. In the second tab there is a checkbox where you can choose if your subprogram will be displayed when called etc . I hope this helps you somehow and really sorry if i was off topic :grinning_squinting_face:

Advertising from our partners

IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Advertise in Robotics
Advertise in Robotics

Job Postings

  • Anyware Robotics is hiring!

    yzhou377 February 23, 2025 at 4:54 AM
  • How to see your Job Posting (search or recruit) here in Robot-Forum.com

    Werner Hampel November 18, 2021 at 3:44 PM
Your browser does not support videos RoboDK Software for simulation and programming

Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • krc5
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Thread Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • krc5
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000
  1. Privacy Policy
  2. Legal Notice
Powered by WoltLab Suite™
As a registered Member:
* You will see no Google advertising
* You can translate posts into your local language
* You can ask questions or help the community with your knowledge
* You can thank the authors for their help
* You can receive notifications of replies or new topics on request
* We do not sell your data - we promise

JOIN OUR GREAT ROBOTICS COMMUNITY.
Don’t have an account yet? Register yourself now and be a part of our community!
Register Yourself Lost Password
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on Google Play
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on the App Store
Download