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. Yaskawa Motoman 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

Indirect Job Call

  • KACInoBlee
  • December 4, 2017 at 2:08 PM
  • Thread is Resolved
  • KACInoBlee
    Trophies
    3
    Posts
    2
    • December 4, 2017 at 2:08 PM
    • #1

    Good Morning,
    Does anyone know if/how to use indirect addressing on a job call on an NX100 controller? For example, I have a LOT of jobs with a similar Job name; i.e., D##_Weld; where ## represents the die number. I'm currently doing something like this:
    CALL JOB:D1_WELD IF B001=1
    CALL JOB:D2_WELD IF B001=2
    ...
    ...
    CALL JOB:D12_WELD IF B001=12

    Obviously, with 12 dies and 7 actions with each die, this will result in 84 job calls!!

    I would prefer to have ONE Call that looks like this:
    CALL JOB:D[B001]_WELD

    This method would result in 7 job calls!

    Thanks!!

  • msklorz
    Trophies
    3
    Posts
    11
    • December 4, 2017 at 3:04 PM
    • #2

    Hi,
    You can rename jobs to numbers i.e. 1;2;12;15.
    Then you can call job B001 - in this way you will call job of name equal to value of B001.

    "CALL JOB: B001" if B001 is equal to 10 you will call job named "10"

  • KACInoBlee
    Trophies
    3
    Posts
    2
    • December 4, 2017 at 8:15 PM
    • #3

    msklorz,
    Thanks for the suggestion. However, I'm not that sure it's possible to call a byte register or other register from a CALL:JOB instruction. Even if it is, it still doesn't help me as I will then have 84 jobs named 1-84 with no information for what they do, which will still be incredibly confusing and cumbersome. It did give me an idea to try and build a job name string based on the action and the die number. However, if I can't call a register or string from the CALL:JOB instruction, that doesn't help either.

    Thanks.

  • Rafael Schroer
    Reactions Received
    1
    Trophies
    3
    Posts
    102
    • December 4, 2017 at 11:40 PM
    • #4
    Quote from KACInoBlee


    msklorz,
    Thanks for the suggestion. However, I'm not that sure it's possible to call a byte register or other register from a CALL:JOB instruction. Even if it is, it still doesn't help me as I will then have 84 jobs named 1-84 with no information for what they do, which will still be incredibly confusing and cumbersome. It did give me an idea to try and build a job name string based on the action and the die number. However, if I can't call a register or string from the CALL:JOB instruction, that doesn't help either.

    Thanks.

    Try to use JET instruction. I mande Thiago with onde byte for each jig.

    Enviado de meu 5051J usando Tapatalk

    Rafael Schroer

    Motoman & ABB OLP Programmer

  • msklorz
    Trophies
    3
    Posts
    11
    • December 5, 2017 at 8:38 AM
    • #5
    Quote from KACInoBlee


    msklorz,
    Thanks for the suggestion. However, I'm not that sure it's possible to call a byte register or other register from a CALL:JOB instruction.

    It is completely possible. In attachment you can see all possible way to use CALL instruction. In my opinion to make it more visible inside job you can just add a comment with description before calling job. You can also start each type of action with different number i.e. for welding "1X" where X is number of a die, for pick and place "2X" etc.

    Quote from RAFAEL FELIPE SCHROER


    Try to use JET instruction. I mande Thiago with onde byte for each jig.

    You can also use JET instruction. I'm not confident about that, but probably name of job which is registered in Job Registration Table won't be visible next to instruction because B000 is variable. Example:

    CALL JET#(1) ENTRY=B000 // D1_WELD ?

    You can find more details about CALL instruction in Inform II User’s Manual, 150078-1CD

    Images

    • call.PNG
      • 79.09 kB
      • 762 × 407
      • 44

    Files

    call.PNG_thumb 10.9 kB – 62 Downloads

    Edited once, last by msklorz (December 5, 2017 at 10:34 AM).

  • Lemster68
    Reactions Received
    295
    Trophies
    9
    Posts
    2,453
    Blog Articles
    7
    • December 5, 2017 at 10:27 PM
    • #6

    Here is a little giblet from one of our jobs which calls a job by name:

    CAT$ S000 S003 "-"
    CAT$ S000 S000 S001
    CAT$ S000 S000 "_S"
    CALL S000
    I hope that helps you out. Prior to getting into this job, the appropriate strings are set to call out different jobs by their name.

  • mil3k
    Reactions Received
    15
    Trophies
    3
    Posts
    71
    • December 7, 2017 at 5:19 PM
    • #7
    Quote from KACInoBlee


    Thanks for the suggestion. However, I'm not that sure it's possible to call a byte register or other register from a CALL:JOB instruction.

    Yes, it is possible. That's how we do it for years.

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