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

Interrupt Job

  • Jrk
  • January 30, 2024 at 8:08 AM
  • Thread is Unresolved
  • Jrk
    Reactions Received
    1
    Trophies
    3
    Posts
    21
    • January 30, 2024 at 8:08 AM
    • #1

    Hello,

    I have a question about interrupt job on NX100 controller.

    Instead of looking input signal to be TRUE,

    I want to trigger interrupt job when input signal switches to FALSE.

    What is the simplest way to achieve that?

  • Go to Best Answer
  • ljuba
    Reactions Received
    33
    Trophies
    5
    Posts
    281
    • January 30, 2024 at 1:15 PM
    • #2

    switch it in ladder

  • Jrk
    Reactions Received
    1
    Trophies
    3
    Posts
    21
    • January 30, 2024 at 2:31 PM
    • #3

    Thank you for your reply!


    I check concurrent IO documentation, and want to check if I understood correctly + some additional questions


    Actual set of commands regarding input that I want to use:

    GSTR #20030

    GOUT #00030

    From my understanding an input Relay group of 8 #20030 is now connected to group #00030 (and in this group is signal that I want to see negated)


    From this group I want only one signal on Relay 20037 to connect negated to "some variable" with command so I plan to add lines:

    STR-NOT #20037

    OUT #"variable"

    Here I have 2 questions:

    1. Since this is ladder like in PLC, there is no problem with "reading" same variable 2 times (so it won't influence first set of commands: GSTR #20030 OUT #00030) ?

    2. What variable can I use, where to declare BOOL variable for my OUT, or can I just use some Auxiliary Relay signals that are not already used?

    And in the end in the interrupt for Input signal I will put this "new variable"

  • 95devils
    Reactions Received
    235
    Trophies
    8
    Posts
    1,951
    • January 31, 2024 at 12:29 AM
    • #4

    Are you sure you ladder is mapped as

    GSTR #20030

    GOUT #00030

    and not

    GSTR #20030

    GOUT #00010?

    Assuming standard mapping step 1 is to delete the:

    GSTR #20030

    GOUT #00010

    Step 2 is to write the following:

    STR #20030

    OUT #00010

    STR #20031

    OUT #00011

    STR #20032

    OUT #00012

    STR #20033

    OUT #00013

    STR #20034

    OUT #00014

    STR #20035

    OUT #00015

    STR #20036

    OUT #00016

    STR #20037

    OUT #00017

    Step 3 is to compile. Your ladder is back to the way it was but with group 1 broken out.

    Write your logic for whichever Universal Input you wish to use as the trigger for the interrupt job.

    I know a thing or two, because I’ve seen a thing or two. Don't even ask about a third thing. I won't know it.

  • 95devils
    Reactions Received
    235
    Trophies
    8
    Posts
    1,951
    • January 31, 2024 at 12:34 AM
    • #5
    Quote from Jrk

    Here I have 2 questions:

    1. Since this is ladder like in PLC, there is no problem with "reading" same variable 2 times (so it won't influence first set of commands: GSTR #20030 OUT #00030) ?

    2. What variable can I use, where to declare BOOL variable for my OUT, or can I just use some Auxiliary Relay signals that are not already used?

    And in the end in the interrupt for Input signal I will put this "new variable"

    1. You can read the same address as many times as you want. You can only write to the address once.

    2. The only addresses you can use with interrupt job is an Universal/General Purpose Input.

    Interrupt Job was developed for press tending. The input is the press starting to roll which is a rising edge signal.

    I know a thing or two, because I’ve seen a thing or two. Don't even ask about a third thing. I won't know it.

  • Jrk
    Reactions Received
    1
    Trophies
    3
    Posts
    21
    • January 31, 2024 at 7:28 AM
    • #6

    Thank you, now everything is clear, can't wait Saturday to test it.

    Quote from 95devils

    Are you sure you ladder is mapped as

    GSTR #20030

    GOUT #00030


    and not


    GSTR #20030

    GOUT #00010?

    Display More

    You are correct, actual map is with GOUT#00010.

    Quote from 95devils

    Interrupt Job was developed for press tending. The input is the press starting to roll which is a rising edge signal.

    Yes, this makes sense.

    I want to use interrupt to stop the program when air pressure is lost and my pressure sensor has only one NO switch.

    I could connect it to a new hardware relay and use NC contact as input, but I figure it must be possible to do it with software.

  • 95devils
    Reactions Received
    235
    Trophies
    8
    Posts
    1,951
    • January 31, 2024 at 12:46 PM
    • Best Answer
    • #7
    Quote from Jrk

    I want to use interrupt to stop the program when air pressure is lost and my pressure sensor has only one NO switch.

    I could connect it to a new hardware relay and use NC contact as input, but I figure it must be possible to do it with software.

    That’s 10x the work for this. Depending on the application the controller is set up for there may be a dedicated set of terminals for air pressure.

    If not a simple user alarm would suffice. One or two rungs added to the ladder. Add the text to display on the screen.

    Advantages to this are:

    No breaking out input groups.  

    No adding EI and DI instructions in a job.

    No creating the job that will execute on the interrupt.

    No additional Jump/Call job.

    No Clear instruction.

    No assigning the interrupt input.

    No assigning the executing job on the interrupt.


    I know a thing or two, because I’ve seen a thing or two. Don't even ask about a third thing. I won't know it.

  • Robodoc
    Reactions Received
    56
    Trophies
    7
    Posts
    1,062
    • February 3, 2024 at 2:36 PM
    • #8

    run your input through a relay

    Robodoc

  • Jrk
    Reactions Received
    1
    Trophies
    3
    Posts
    21
    • February 12, 2024 at 11:04 AM
    • #9
    Quote from 95devils

    That’s 10x the work for this. Depending on the application the controller is set up for there may be a dedicated set of terminals for air pressure.

    If not a simple user alarm would suffice. One or two rungs added to the ladder. Add the text to display on the screen.

    Advantages to this are:

    No breaking out input groups.

    No adding EI and DI instructions in a job.

    No creating the job that will execute on the interrupt.

    No additional Jump/Call job.

    No Clear instruction.

    No assigning the interrupt input.

    No assigning the executing job on the interrupt.

    Display More

    Finally found time to tinker with ladder editor over last weekend, and it went smoother than I taught.

    Thank you for pointing out the user alarm option, it work's like a charm.

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

  • Interrupt Job Not Working

    • Jack82
    • September 13, 2023 at 9:34 PM
    • Yaskawa Motoman Robot Forum
  • Test an Interrupt Job in Motosim

    • StachLee
    • June 27, 2023 at 12:06 PM
    • Yaskawa Motoman Robot Forum
  • Interrupt or other mechanism to reset program

    • krzych
    • February 15, 2014 at 9:26 AM
    • Yaskawa Motoman Robot Forum
  • Macro job (suspend job)

    • Denis-motoman
    • January 30, 2023 at 10:39 AM
    • Yaskawa Motoman Robot Forum
  • Cancel Program and Send Pointer to Cell.

    • PGG
    • August 31, 2017 at 10:40 PM
    • KUKA Robot Forum
  • Hold from external input

    • dset
    • January 20, 2022 at 6:21 AM
    • Yaskawa Motoman Robot Forum
  • Unintended motion

    • Robottech
    • February 2, 2021 at 12:28 AM
    • Yaskawa Motoman Robot Forum
  • INTERRUPT ON BETWEEN PTP C_PTP

    • rvsh
    • May 30, 2020 at 3:31 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