In the previous lesson we discussed the Process Image Input or PII and its size. We wrote a simple move instruction to access an analog input only to find that just as soon as we downloaded it to the PLC, the PLC faulted and went into stop mode. In this lesson we will discuss the PII further and also troubleshoot our code to determine why our seemingly simple move instruction faults the PLC. It’s all about Peripheral Input addressing, why we need to do it and how it’s done. I’m sure you’re curious as to what’s going on so let’s get started with this lesson and cure your curious.
In previous lessons we discussed the Process Image Input or PII, its purpose, size, and what happens when exceeded. We wrote a simple move instruction to demonstrate the PII boundary and faulted the PLC, diagnosed that fault, and found out how we need to handle our I/O when our PII boundary is ex...
For the last few lessons we have been discussing the Process Image Input or PII and using it within your PLC programs. We are continuing to educate on this topic by discussing the Process Image Output or PIQ. Just as we instructed previously the purpose, size, and boundary, we will inform the sam...
In a continuation of our discussions about the Process Image Input or PII and the Process Image Output or PIQ, this lesson is going to inform about the ability to force these peripheral objects. Previously we had opened a table to facilitate our testing and in this lesson, we’ll expand the table ...
5 Comments