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

FDAT tool no change

  • ravitejagali
  • May 7, 2020 at 8:23 PM
  • Thread is Unresolved
  • ravitejagali
    Trophies
    3
    Posts
    143
    • May 7, 2020 at 8:23 PM
    • #1

    SLIN P1 Vel=2 m/s CPDAT1 Tool[1]:Toolo Base[0]

    Here point p1 is taught with Tool no 1 and base no 0.

    Inside folds we have fdata (frame data) , for the above point p1 fdat looks like this

    DECL FDAT P1={TOOL_NO 1,BASE_NO 0 ,IPO_FRAME #BASE,POINT2[] " ",TQ_STATE FALSE}

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

    If I change tool by fdata, what happens? Does it brings tool mismatch error or does it moves to new tool point p1

  • panic mode
    Reactions Received
    1,296
    Trophies
    11
    Posts
    13,136
    • May 7, 2020 at 9:14 PM
    • #2

    modifying inline form instructions (ILF) requires care because HMI makes changes in more than one place.

    if you are learning how to manipulate ILF instructions by text editor, make change using HMI and compare before/after in BOTH files (SRC and DAT).

    if you want to find out what happens if you make particular change (in certain places only), try to run it and see how it behaves,

    but keep in mind that you may be putting yourself and others in harms way. so always test changes in T1.

    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

  • hermann
    Reactions Received
    411
    Trophies
    9
    Posts
    2,623
    • May 8, 2020 at 8:04 AM
    • #3

    If you change the value in fdat, there will be no error, robot moves with changed tool.

    If you change the movement in HMI afterwards, you have to pay attention. The HMI uses different entries in the fold, and if you change only the speed in the online statement, HMI will change back the tool to the older value 😮. Crash can happen.

  • ravitejagali
    Trophies
    3
    Posts
    143
    • May 11, 2020 at 4:31 PM
    • #4
    Quote from panic mode

    modifying inline form instructions (ILF) requires care because HMI makes changes in more than one place. --> loacl variables(local program position variables) are ment only for local programms I hope. You mean if position name is no where used except in the local progam still it changes the config of tool for other points :exclamation_mark::exclamation_mark:

    if you are learning how to manipulate ILF instructions by text editor, make change using HMI and compare before/after in BOTH files (SRC and DAT).--

    if you want to find out what happens if you make particular change (in certain places only), try to run it and see how it behaves,

    but keep in mind that you may be putting yourself and others in harms way. so always test changes in T1.--> For sure Not, no one will do like that atleast myself. I asked clearly (If I change tool by fdata, what happens? Does it brings tool mismatch error or does it moves to new tool point p1)

  • ravitejagali
    Trophies
    3
    Posts
    143
    • May 11, 2020 at 4:32 PM
    • #5
    Quote from hermann

    If you change the value in fdat, there will be no error, robot moves with changed tool.

    If you change the movement in HMI afterwards, you have to pay attention. The HMI uses different entries in the fold, and if you change only the speed in the online statement, HMI will change back the tool to the older value 😮. Crash can happen.

    Thanks for your info :smiling_face: :smiling_face:

  • panic mode
    Reactions Received
    1,296
    Trophies
    11
    Posts
    13,136
    • May 11, 2020 at 5:34 PM
    • #6

    "loacl variables(local program position variables) are ment only for local programms I hope. You mean if position name is no where used except in the local progam still it changes the config of tool for other points :exclamation_mark::exclamation_mark:"

    no, when you insert ILF instruction into a program, KSS makes changes to both SRC and DAT file.

    point name, used tool etc are used more than once (more like three places each for single ILF).

    making manual change to just ONE of those places is asking for trouble... and can be dangerous.


    "Does it brings tool mismatch error or does it moves to new tool point p1)"

    if you want to find out, try it yourself. you did not even state the system detail.

    even if you did, i do not want to be the one telling you what your system will do if you screw around with ILF.

    this is EXACTLY why some things are password protected.

    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

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

Similar Threads

  • Kuka inline forms

    • NiNok
    • March 27, 2019 at 10:15 AM
    • KUKA Robot Forum
  • Transformation of existing programs, inline forms correction

    • Crmo
    • April 27, 2020 at 6:25 PM
    • KUKA Robot Forum
  • One point, two tools [solved]

    • Patrik Paukov
    • June 20, 2018 at 5:50 PM
    • KUKA Robot Forum
  • camera's coordinates to pick object

    • sudan
    • April 26, 2018 at 12:15 PM
    • KUKA Robot Forum
  • ConveyorTech -- Following motion makes no sense

    • SkyeFire
    • October 21, 2017 at 3:30 AM
    • KUKA Robot Forum
  • E6POS array and touch up problem

    • s.yilmaz
    • September 28, 2016 at 9:39 PM
    • KUKA Robot Forum
  • Krc fdat

    • Dig
    • August 28, 2016 at 6:45 PM
    • KUKA Robot Forum
  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