Greetings Deer,
if you already know how an STI (Selectable Timed Interrupt) works, then you’re more than halfway home to understanding a PII (Processor Input Interrupt) ...
you probably already know about this - but just in case, here’s the basic idea behind an STI:
the processor temporarily interrupts its program scan - and jumps over to the ladder file that you’ve set up as an STI file - and starts scanning there ... the processor does this “interrupt” at a time (a frequency) which you select and configure ... in other words, with an STI you tell the processor: “whatever you’re doing, and wherever you are in the scan, stop what you’re doing and go run the STI file instead ... then come back to where you were and finish the normal program scan” ... and the most important thing for our discussion is that you get to tell the processor how often to do this interrupt thing based on a TIME which you get to set ... secret handshake: STI is an “I”nterrupt to the program scan which takes place at a “T”ime that you get to “S”elect ...
STIs are fairly common ... now let’s talk about PIIs ... these are MUCH less common ... in fact, personally I’ve never seen one used in the real world ...
here’s the basic idea behind a PII:
the processor temporarily interrupts its program scan - and jumps over to the ladder file that you’ve set up as a PII file - and starts scanning there ... the processor does this interrupt whenever a certain input changes state ... and you get to select the input and configure whether a change from OFF-to-ON triggers the interrupt ... or whether a change from ON-to-OFF initiates the trigger action ... in other words, with a PII you tell the processor: “whatever you’re doing, and wherever you are in the scan, stop what you’re doing and go run the PII file instead ... then come back to where you were and finish the normal program scan” ... and the most important thing for our discussion is that you get to tell the processor how often to do this interrupt thing based on an INPUT changing state ... secret handshake: PII is an “I”nterrupt to the program scan which takes place when an “I”nput to the “P”rocessor changes state ...
so that’s the basic idea ... when do you use a PII? ... maybe for something like a very fast acting process ... something like a canning line where decisions have to be made very quickly - and a programmed output response needs to be taken very quickly ... there is more information about “when-to-use-it” and more details on PIIs in general starting on page 18-1 of
this manual ...
finally ... note that the PII function is native to the PLC-5 platform and to RSLogix5 software ... for the SLC-500 platform and RSLogix500, take a look at the DII (Discrete Input Interrupt) ... but ... I’ve never seen one of those used in the real world either ...
I hope that this “basic idea” information is what you were looking for ... but if you need more detail, please post again ... I’ll be glad to give it another try ...