Video

Yes stop bits, like their hardwired counterparts should always be N.C., or "XIC" in ladder logic software for "fail safe" operation. But when I would explain Ladder logic programming to people with little or no electrical background i would usually try to dispense with most of the Normally closed, examine if closed, on, off, Hi, Low, ones and zeros, etc. All of that language, while useful can be very confusing to those without the background in electrical switching, relays etc, and they tend to, in my experience, get hung up on these concepts when much of it is unnecessary to learning to read the logic. I would instead present it like this: I would tell them to divide the screen into left and right. On the left side you have a set of "conditions" and on the far right you have an "outcome" based on those conditions. If the conditions are "true" then the outcome will then be true and of course if they are false the outcome will also be false. I would tell them to forget about all of the N.C., N.O. stuff for the moment and pay attention instead to the green highlights. If it is green then its true regardless of anything else. It is of course an oversimplification but I found it to be effective in getting people, with little and sometimes no experience, reading and understanding ladder logic without getting hung up on the whole Normally closed, on, off, concepts.

Yes stop bits, like their hardwired counterparts should always be N.C., or "XIC" in ladder logic software for "fail safe" operation. But when I would explain Ladder logic programming to people with little or no electrical background i would usually try to dispense with most of the Normally closed, examine if closed, on, off, Hi, Low, ones and zeros, etc. All of that language, while useful can be very confusing to those without the background in electrical switching, relays etc, and they tend to, in my experience, get hung up on these concepts when much of it is unnecessary to learning to read the logic. I would instead present it like this: I would tell them to divide the screen into left and right. On the left side you have a set of "conditions" and on the far right you have an "outcome" based on those conditions. If the conditions are "true" then the outcome will then be true and of course if they are false the outcome will also be false. I would tell them to forget about all of the N.C., N.O. stuff for the moment and pay attention instead to the green highlights. If it is green then its true regardless of anything else. It is of course an oversimplification but I found it to be effective in getting people, with little and sometimes no experience, reading and understanding ladder logic without getting hung up on the whole Normally closed, on, off, concepts.

Yes stop bits, like their hardwired counterparts should always be N.C., or "XIC" in ladder logic software for "fail safe" operation. But when I would explain Ladder logic programming to people with little or no electrical background i would usually try to dispense with most of the Normally closed, examine if closed, on, off, Hi, Low, ones and zeros, etc. All of that language, while useful can be very confusing to those without the background in electrical switching, relays etc, and they tend to, in my experience, get hung up on these concepts when much of it is unnecessary to learning to read the logic. I would instead present it like this: I would tell them to divide the screen into left and right. On the left side you have a set of "conditions" and on the far right you have an "outcome" based on those conditions. If the conditions are "true" then the outcome will then be true and of course if they are false the outcome will also be false. I would tell them to forget about all of the N.C., N.O. stuff for the moment and pay attention instead to the green highlights. If it is green then its true regardless of anything else. It is of course an oversimplification but I found it to be effective in getting people, with little and sometimes no experience, reading and understanding ladder logic without getting hung up on the whole Normally closed, on, off, concepts.

Yes stop bits, like their hardwired counterparts should always be N.C., or "XIC" in ladder logic software for "fail safe" operation. But when I would explain Ladder logic programming to people with little or no electrical background i would usually try to dispense with most of the Normally closed, examine if closed, on, off, Hi, Low, ones and zeros, etc. All of that language, while useful can be very confusing to those without the background in electrical switching, relays etc, and they tend to, in my experience, get hung up on these concepts when much of it is unnecessary to learning to read the logic. I would instead present it like this: I would tell them to divide the screen into left and right. On the left side you have a set of "conditions" and on the far right you have an "outcome" based on those conditions. If the conditions are "true" then the outcome will then be true and of course if they are false the outcome will also be false. I would tell them to forget about all of the N.C., N.O. stuff for the moment and pay attention instead to the green highlights. If it is green then its true regardless of anything else. It is of course an oversimplification but I found it to be effective in getting people, with little and sometimes no experience, reading and understanding ladder logic without getting hung up on the whole Normally closed, on, off, concepts.

Yes stop bits, like their hardwired counterparts should always be N.C., or "XIC" in ladder logic software for "fail safe" operation. But when I would explain Ladder logic programming to people with little or no electrical background i would usually try to dispense with most of the Normally closed, examine if closed, on, off, Hi, Low, ones and zeros, etc. All of that language, while useful can be very confusing to those without the background in electrical switching, relays etc, and they tend to, in my experience, get hung up on these concepts when much of it is unnecessary to learning to read the logic. I would instead present it like this: I would tell them to divide the screen into left and right. On the left side you have a set of "conditions" and on the far right you have an "outcome" based on those conditions. If the conditions are "true" then the outcome will then be true and of course if they are false the outcome will also be false. I would tell them to forget about all of the N.C., N.O. stuff for the moment and pay attention instead to the green highlights. If it is green then its true regardless of anything else. It is of course an oversimplification but I found it to be effective in getting people, with little and sometimes no experience, reading and understanding ladder logic without getting hung up on the whole Normally closed, on, off, concepts.

Well it does depend on the logic, but with a standard seal in circuit you would expect the NC stop pushbutton to be addressed with an XIC.

But.. it doesnt really matter with a plc. It's electronic. There is no loose wire to come off if it comes from an HMI. Of course if you want to have hardwired inputs into the PLC you can make the point for a NC stop PB. Thanks for the comment!

@automationnc safety, safety, safety. If you use a normally open stop to an XIO instruction and the wire breaks or contact doesn't seal you'll never get it to turn off minus e-stop circuit. Showing this leads people to a mojor error

@@andrewrolfe4263 As I mentioned, no wires from an HMI. I agreed that it would be prudent in a wired system. Doesn't matter for an HMI with comms.

Thanks for the comment and sorry the explanation wasn't clear to you. The primary purpose of the video was to cover how the SCP instruction works independent of any type of card. The "raw" or input values from different inputs cards can vary depending on which card is chosen. Unfortunately the 1769 would be very impractical for this video as the programming software used would not work with the Compact Logix. The 1762 is a micrologix series card and would be able to be used with this software as RSLogix500 was made for the SLC500 and micrologix processors. The primary take away I would like someone to get from this video is being able to use the SCP to scale something from one range to a different range. That information translates throughout all the AB processors and can still be used with the ControlLogix today.

OK! Finally! So get a little more detailed. Just about everything I cover is based on real life industry. What did you specifically have in mind when you posted this? What aspects of PLC programming are you interested in learning?

Thanks!

Not currently, but we are working on a downloads section for our subscribers. This might be a good addition!

ago czcams.com/video/T5ir_oDUy8o/video.html SINGLE PUSH BUTTON ON OFF LOGIC IN STUDIO 5000 AB PLC

Pas sûr que je comprenne

I appreciate the comment! We have much more content on our PLCMentor website and it was designed around maintenance techs that need to learn but where it's hard to do without them for a week.

ago czcams.com/video/T5ir_oDUy8o/video.html SINGLE PUSH BUTTON ON OFF LOGIC IN STUDIO 5000 AB PLC

Best plan there is to be honest with your employer or interviewer. Show your willingness to improve and learn like you are doing here and it will go a long way towards your success.

You'll have to give me a little more to go on there.

To do that we usually go to a SCADA system that allows pulling information from the PLC, storing history, and presenting the information to users.

www.udemy.com/course/ladder-logic/?referralCode=5F59E75E49773D233979

Sure - go to system options/ xref tab and enable cross references online is a check box. (You get to system options by going to Tools Menu/Options)

@@PLCMentor all ready I checked there but that icon is not activating .. when click on that one ..

Hello sir .. How to set preset time for timer online in PLC5 allen Bradley and download the same only that rung into the PLC5

@@ravindradesai5007 First you cannot selectively download in the PLC5. All or nothing. To change the preset on a timer in the PLC5, you just need to go to the instruction and change it right there. You could also change it in the data table.

Your representative can generally get you a timed license for such.

It gets difficult because your scaling depends very much on your I/O. Just because you have a 0-10VDC signal coming into the PLC doesnt mean it is represented easily in the PLC. This video is actually a step back from the concept you mention to just understand what the scaling function does without confusing the issue with what analog input card you are using. We get into those concepts in our later videos.

RSLogix Micro Starter Lite. I just downloaded it yesterday from Rockwell's website.