News:

  • May 05, 2026, 08:17:48 AM

Login with username, password and session length

Author Topic: RX/WX Edge Triggered  (Read 6389 times)

Tark

  • Jr. Member
  • **
  • Posts: 16
RX/WX Edge Triggered
« on: November 13, 2015, 03:19:56 PM »
I just want to verify that if I have multiple RX/WX's that are Edge Triggered, if on Scan A they are all true, then they will all execute regardless of what the rung status is on Scan B?  In other words, if I have 10 WX's that are triggered from the same bit, if on Scan A the bit is true all 10 of the WX's will execute even if on the next Scan the bit is false?

I'm assuming the above answer is Yes, then my next question will be - What happens in a case where a WX instruction is true on one scan, false on the next scan, then true, then false, would this build up a large que of the WX instruction?

Last question  ;) - Do the DLRX/DLWX and MRX/MWX instructions perform in the same manner as the RX/WX instructions?

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6154
  • Yes Pinky, Do-more will control the world!
Re: RX/WX Edge Triggered
« Reply #1 on: November 13, 2015, 03:25:09 PM »
I just want to verify that if I have multiple RX/WX's that are Edge Triggered, if on Scan A they are all true, then they will all execute regardless of what the rung status is on Scan B?  In other words, if I have 10 WX's that are triggered from the same bit, if on Scan A the bit is true all 10 of the WX's will execute even if on the next Scan the bit is false?

I'm assuming the above answer is Yes, then my next question will be - What happens in a case where a WX instruction is true on one scan, false on the next scan, then true, then false, would this build up a large que of the WX instruction?

Last question  ;) - Do the DLRX/DLWX and MRX/MWX instructions perform in the same manner as the RX/WX instructions?

Edges are latched in the instruction. Single events aren't missed, but multiples are not queued.

DLRX/WX and MRX/WX do work the same way.
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO