Capturing a count

This is similar to a post I made last week, close, but not the same. I'm looking for a way to capture and send a value of a CTU.ACC that is being counted up by a digital input, and to have that value captured and moved using a MOV instruction, that ACC Value right before the CTU is reset to Zero. The CTU is timed and resets after 3 seconds, so when the first push button reset for that CTU is made true, I use that same Push button input for a one shot OTE's XIC to make the MOV true and it seems to work only while the one shot is active for that one scan. The ACC Value does move using the MOV but after the Counter is reset after that 3 seconds, the Value that was in the MOV goes back to Zero along with the new reset Value of Zero, the same as the CTU.ACC. My Question is; how does the Value in the MOV Change along with the CTU reset if the one shot only made the MOV rung true for only one Scan, which is far less time than 3 seconds. I hope I made good sense with this is one. Thanks.

I cannot read your picture at all. Either up the zoom level before making a screen capture, 'printing' to a PDF and attaching that or zipping and attaching this section of the program.

Break it down into the 4 things you need to do:
1) Add 1 to a number every time a digital input goes high:
Normally open contact for your input, one-shot (rising) to make sure that it only happens 1 each time the signal goes high (instead of every scan that the condition is true), and then ADD 1 to an integer called "COUNT". I personally never use CTUs. Call it preference.

2) Move the accumulated value into a holding register when the timer is done. Normally open contact for TIMER.DN, move "COUNT" into another integer

3) Reset your counter to 0 when the timer is done. Normally open contact for TIMER.DN, move 0 into "COUNT"

4) A timer that counts for 3 seconds. I assume this means you want a timer that counts for 3 seconds and then resets itself.
Normally Closed contact with TIMER.DN leading to the timer itself (TON). This means every time the timer is done, the DN bit will be true for a single scan, and the timer will restart.

Is your ONS getting fired twice? Once when you initially set Push_Button_Reset and again after 3 seconds+1 scan when the .DN XIO makes?

I assume your Push_Button_Reset is maintained? Make it momentary and latch around it with the .TT bit of the timer.

And really unless you need the 3 second timer, you could accomplish the MOV and reset as parallel outputs on the same rung as your Push_Button _Reset.

bernie_carlton said:

I cannot read your picture at all. Either up the zoom level before making a screen capture, 'printing' to a PDF and attaching that or zipping and attaching this section of the program.

Click to expand...

What's a good Program to convert it for how you need it?

Use the Windows snipping tool, save the capture, then upload it. Don't do any size modifications beyond that.

JeremyM said:

Use the Windows snipping tool, save the capture, then upload it. Don't do any size modifications beyond that.

Click to expand...

One problem is that the attachment feature seems to shrink images down in resolution. I have taken screen captures at full resolution and uploaded them here through an attachment, and when you try to view them they are tiny or blurry and you can't make things out.

I think screenshots in general are a bad way to do it. I've used a program called PDF995 to print things to PDF files. I'm sure many others exist.

bernie_carlton said:

I cannot read your picture at all. Either up the zoom level before making a screen capture, 'printing' to a PDF and attaching that or zipping and attaching this section of the program.

Click to expand...

How about this? Though I understand the instruction I've never used an OSR

If you want to copy the accumulated Count_up.ACC before it is reset, place the MOV instruction on the same rung as, but prior to, the RES instruction. No ONS required.

Your current code one-shot-rises a MOV flag, then performs the MOV, sure. But it depends on the Reset_Timer.DN bit, which rung 0 also looks at. Do you see how the reset occurs before your copy?

Is your attached image a .JPG or .PNG file? If it's the former, try snipping and saving as the latter, then uploading.

I'm posting this before I go back and read through the from you gentleman about my last post ....I did some more reading and then, this is what I came up with. Works like a Charm for what I was trying to do. What do you guys think? I'm studying on everything else that has been suggested also. Just have to study more to implement it. Thanks

JeremyM said:

If you want to copy the accumulated Count_up.ACC before it is reset, place the MOV instruction on the same rung as, but prior to, the RES instruction. No ONS required.

Your current code one-shot-rises a MOV flag, then performs the MOV, sure. But it depends on the Reset_Timer.DN bit, which rung 0 also looks at. Do you see how the reset occurs before your copy?

Is your attached image a .JPG or .PNG file? If it's the former, try snipping and saving as the latter, then uploading.

Click to expand...

Yep, I sure do. Excellent!

To make it more readable, I normally narrow the ladder window as much as possible without rung wrap before taking the screenshot.