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. Fanuc 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

FANUC Increase Payload schedule-listing items

  • a00948630
  • September 5, 2019 at 5:53 PM
  • Thread is Unresolved
  • a00948630
    Trophies
    3
    Posts
    9
    • September 5, 2019 at 5:53 PM
    • #1

    Hello all,

    I need to define more than 10 motion payloads (different toolings) but I can't find a way to increase this limit.

    Do you know if this limit can be increased and if so, how can I do it?

    Thanks in advance!

    Regards.

  • Go to Best Answer
  • CPh
    Reactions Received
    2
    Trophies
    3
    Posts
    51
    • September 6, 2019 at 9:32 AM
    • #2

    Hello,

    Unfortunately I read somewhere that it is not possible to increase this limit...

  • HawkME
    Reactions Received
    568
    Trophies
    10
    Posts
    3,268
    • September 6, 2019 at 1:09 PM
    • #3

    I recommend taking your various payload sizes and creating 10 schedules that cover the entire range. Then just select the closest one. In most situations this is an adequate solution, especially considering that many people get payload wrong altogether and still function :uglyhammer2:.

  • Online
    Nation
    Typical Robot Error
    Reactions Received
    529
    Trophies
    9
    Posts
    1,908
    • September 6, 2019 at 3:30 PM
    • #4

    I wrote a small program to write to payload 1 and then set it dynamically. This might work for your situation. I haven't had the chance to test it though.

    Code
    : !Payload in kg. ;
    : $PLST_GRP1[1].$PAYLOAD=(AR[1]) ;
    : !Payload CoG in cm. ;
    : $PLST_GRP1[1].$PAYLOAD_X=(AR[2]) ;
    : $PLST_GRP1[1].$PAYLOAD_Y=(AR[3]) ;
    : $PLST_GRP1[1].$PAYLOAD_Z=(AR[4]) ;
    : !Payload inertia in kgfcm^2. ;
    : $PLST_GRP1[1].$PAYLOAD_IX=(AR[5]*980) ;
    : $PLST_GRP1[1].$PAYLOAD_IY=(AR[6]*980) ;
    : $PLST_GRP1[1].$PAYLOAD_IZ=(AR[7]*980) ;
    : PAYLOAD[1] ;
    Display More

    Check out the Fanuc position converter I wrote here! Now open source!

    Check out my example Fanuc Ethernet/IP Explicit Messaging program here!

  • a00948630
    Trophies
    3
    Posts
    9
    • September 6, 2019 at 5:48 PM
    • #5

    Hello Nation,

    I just tested this and it changes the payload values correctly! :thumbs_up:

    Just one more question, is there a way to know/validate that the robot is actually using this new values? Is there a test that I can do to validate?

    Thanks in advance :smiling_face:

    Regards.

  • Online
    Nation
    Typical Robot Error
    Reactions Received
    529
    Trophies
    9
    Posts
    1,908
    • September 6, 2019 at 7:10 PM
    • #6

    That is what I am not sure of.

    One way to test would be to put in a really heavy payload when you actually have a light payload and see if the arm overshoots its programmed points a little bit.

    Another way would be to run a test path in auto, one time with a light payload set, and another with a heavy payload set and watch to see if the path cycle times change. Heavy payload should accelerate slower.

    Check out the Fanuc position converter I wrote here! Now open source!

    Check out my example Fanuc Ethernet/IP Explicit Messaging program here!

  • Lemster68
    Reactions Received
    295
    Trophies
    9
    Posts
    2,458
    Blog Articles
    7
    • September 6, 2019 at 8:25 PM
    • #7
    Quote from Nation

    That is what I am not sure of.

    One way to test would be to put in a really heavy payload when you actually have a light payload and see if the arm overshoots its programmed points a little bit.

    And you could adjust the collision guard to be more sensitive, triggering a false collision.

  • pdl
    Reactions Received
    266
    Trophies
    9
    Posts
    1,506
    • September 6, 2019 at 9:53 PM
    • #8

    You could also look at the disturbance torque status page (MENU > STATUS > AXIS > NEXT > F4 for "DISTURB".

    The values in the allow column should change with the active payload.

  • domo_arigato
    Reactions Received
    8
    Trophies
    3
    Posts
    14
    • September 6, 2019 at 10:11 PM
    • #9

    I have never tested this personally so take this with a grain of salt: there is apparently a way to "trick" the controller to use the payload values for other motion groups as group 1, thus increasing the number of payload schedules available to group 1 beyond the default 10.

    From what I understand, this process it long and tricky, and involved changing variables via a Controlled Start, rebooting, changing some other system variables, booting back into a Controlled Start, etc. I unfortunately have never used the process (and willingly admit I'm not 100% sure it even exists), but I would suggest reaching out to CRC to see if they can walk you through the process.

    On an aside; will changing a payload's values programmattically on-the-fly via the above quoted $PLST_GRP1[1].$PAYLOAD=(n) system variable set mess with the motion planning algorithm that FANUC has running in the background to calculate motor torque, current draw, encoder counts/speed rates/whatever type of PID algorithm they have going on? I always assumed that changing the variable as it's being used could cause corruption of the motion planner.

  • a00948630
    Trophies
    3
    Posts
    9
    • September 6, 2019 at 10:23 PM
    • #10

    Hello all,

    I'll make the tests that you all recommended me for validating if the new payload values are being taken by the robot, I'll also evaluate the option from HawkME and analyze all possibilities.

    Thank you all!

    :smiling_face::smiling_face::smiling_face::thumbs_up:

  • a00948630
    Trophies
    3
    Posts
    9
    • September 6, 2019 at 10:39 PM
    • #11
    Quote from domo_arigato

    On an aside; will changing a payload's values programmattically on-the-fly via the above quoted $PLST_GRP1[1].$PAYLOAD=(n) system variable set mess with the motion planning algorithm that FANUC has running in the background to calculate motor torque, current draw, encoder counts/speed rates/whatever type of PID algorithm they have going on? I always assumed that changing the variable as it's being used could cause corruption of the motion planner.

    I was also not really sure about this, as when someone manually changes any value inside the payload schedule page, we get a "Path and Cycletime will change. Set it?" message, not sure it after hitting “Yes” a new calculation was made but dynamically modifying the variables could result on something like what you mention, but maybe not and this is just a warning for just entering the value and it would be the same as modifying the variables directly.

    Tests will say :face_with_tongue:

  • Dpreston
    Reactions Received
    4
    Trophies
    3
    Posts
    23
    • September 17, 2019 at 9:37 PM
    • Best Answer
    • #12

    Gents, I just came across this post while looking for something else.

    You can change the number of payload schedules by changing the following variable. You must be in a controlled start to make the change.

    In controlled start go to $PLST_SCHNUM and change it to the number you need. Do a cold start and let the robot boot up. Go back into a controlled start and verify that $PLST_SCHNUM and $PLST_SCHMAD are both set to that number. Go back into a cold start and check the number of available payload schedules. I don't know what the max number you can have is; I've been up to 64.

    Good luck!

  • TrainMan
    Trophies
    3
    Posts
    1
    • October 8, 2019 at 8:55 PM
    • #13

    I changed these variables over a year ago to 125 and the robot performed fine. The only limit is the memory it takes up in the controller.

  • RWD Controls
    Reactions Received
    3
    Trophies
    1
    Posts
    5
    • October 25, 2023 at 7:01 PM
    • #14

    From Operators Manual B-83284EN/10:

    "Up to 10 of payload data can be set as standard. The number of payload data can be increased up to 256 by the following way. (up to 32 in R-30iB and R-30iB Mate)

    a. Turn on the controller with [PREV] and [NEXT] key pressed.

    b. Select "3 Controlled start".

    c. Press the [MENU] key.

    d. Select "4 Variables"

    e. Set the number of payload data to the system variable $PLST_SCHNUM.

    f. Restart (power off/on) the controller and "Control start" again.

    g. Press the [FCTN] key.

    h. Select "1 START (COLD)".

    This worked for me on a R-30iB Mini Plus.

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
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • 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
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Tags

  • Fanuc
  • Payload
  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