OSR /OSF in AB

Bering C Sparky

Lifetime Supporting Member
Join Date
Mar 2014
Location
Bering Sea, Alaska
Posts
1,117
Carry over from another post, but I was asked a question about how AB One Shots functioned on the AD Forum.

Here is the question I was asked:

I'm not familiar with AB. Is the one-shot behavior an attribute of the element itself, rather than the instruction?

I answered the question:

Yes exactly,
Each One Shot is a unique and individual tag. One Shots become True when the logic before them is True. Not when another instruction with the same tag is True elsewhere in the program.
In Allen Bradley, when a One Shot is placed on a rung, it requires all the instructions before it (to its left) on the rung, to be True in order for the Output to the right of the One Shot to become True for 1 scan.

But then I got to thinking........
I have never used OSR or OSF instructions in AB....only the ONS instruction.

Am I right to assume that the OSR and OSF instructions in Allen Bradley generally follow the same rules as far as, the logic on the rung before the One Shot instruction must be true in the case of the OSR and False in the case of the OSF for the One Shot to become True itself for one scan?

I always assumed that they followed the same general rules as the ONS in this way.

But now I see that AD software acts differently and the One Shot is not a unique tag but replicated from others in the program to function more as a one shot XIC or XIO (Rising / Falling) to a specific tag that is used elsewhere in the program.

Do the OSR and OSF instructions in AB at like the ones in AD also????
Or do they follow the same general rules as the ONS instruction????

I could dig out my old AB software and emulator and try it myself but was hoping someone would just give me the answer for free, so I can put this out of my mind and move on.

Thanks in advance.

BCS
 
Last edited:
I always refer to 'help' documentation on the instruction itself. I have found AB documentation to be fairly though.

Note that a few instructions vary based on the specific family being programmed. Be sure to check that.
 
Last edited:
Slightly off-topic but, the Click PLC even allows a built in one-shot option for certain box instructions, for example - COPY and MATH. This would allow the elimination of a separate one-shot external to the instruction.

Notice the pulse symbol by the instruction type.

Click PLC oneshot.PNG
 
Last edited:
Guess I am not getting anything for free today.

No one wants to just give me the answer to the question and are going to make me work for it I guess.

I will look up the answer to my question online or dig out what little software I have for AB later and find out.

Just pulled into Dutch so going to be busy for a while.

BCS
 
Last edited:
here are some related threads ... if I get time tomorrow (not likely - I'm swamped these days) I'll give you a step-by-step breakdown ... actually it will have to be several breakdowns – because of the variations between the different Allen-Bradley platforms ... anyway - most (if not all) of the different ideas involved are covered in the following threads ...

http://www.plctalk.net/qanda/showthread.php?p=526030&postcount=10

http://www.plctalk.net/qanda/showthread.php?p=284127&postcount=4

http://www.plctalk.net/qanda/showthread.php?p=603722&postcount=13

TIP: following through the continuing conversation presented in the last link above, should go a long way towards convincing you that you're not always going to be able to trust the "books" for subjects like this ... an operational test with the precise equipment is a much more reliable way to nail down the details ...
 
Last edited:
I'm pretty sure that your main issue is that there are differences between how the Automation Direct software handles One-Shots - and how the Allen-Bradley software handles them ... what makes it even more challenging is that there are quite a few differences between how they get handled just by the various Allen-Bradley platforms ...

anyway - before you move on, you'll certainly want to consider how the "retentive" Latch/Unlatch instructions in Allen-Bradley differ from the Set/Reset instructions in Automation Direct systems ... many people think that these are directly interchangeable ... they are NOT ... and quite a few safety issues can arise when these are misused by programmers who don't really understand the differences ...

the following link should help ...

http://www.plctalk.net/qanda/showthread.php?p=71786&postcount=1

man - has it been 12 years since I wrote that? ... it seems like yesterday ...
 
Ron,

I know I have read this post before, but its been years ago.
Now that I am actually working with Automation Direct devices it was good to read this again.

As always your post are very informative and helpful.

Thanks again,
BCS
 

Similar Topics

Just wondering if i can make my code look a little nicer and sharing storage bits like below https://imgur.com/a/SMNxOPu does this work or does...
Replies
9
Views
1,567
We have a vendor that loves ONS logic. It does ok as long as things run as expected. Well we all no nothing runs as expected for very long. If the...
Replies
3
Views
1,329
Hi, I hope I have what is a basic PLC5 coding question. I have four fans: two for supply (HVU1, HVU2) and two for exhuast (EF1, EF2). The...
Replies
0
Views
5,258
Hello, I am having an issue with an OSR bit starting a rotary indexer. Running AB studio5000 on a 5069 L320ER v32.1 I have 13 inputs before an...
Replies
9
Views
2,352
I'm looking at an offline copy of a program that has these two rungs, in this order (see attachment). B3:16/3 is a OSR in the first rung and an...
Replies
9
Views
2,363
Back
Top Bottom