Ok, you need to pulse those signals automatically but what is it that you want to use as the specifications to create the pulses?

Just focus on the very first "pulse" that is needed to be generated.

What condition(s) are required of the system that will cause a pulse to be created?

List them all please. 

rick.fronda11

I need to give clock pulses here automatically. I am currently doing manually. Please help me here

If someone ask me why I am clicking a box in the watch table, that is not the same as asking WHEN DO YOU CLICK THE BOX IN THE WATCH TABLE.

I wrote:

What condition(s) are required of the system that will cause a pulse to be created?

 My apologies for the "online" equivalent of yelling.

BUT YOU ARE NOT LISTENING.

WHAT happens in the world that makes you click the boxes in the watch table?

Suppose someone asks me, please update the runtime of pumps on that s7-1200 PLC system.  Then they say, I want to know the runtime values at 8 AM, 4 PM, and 12AM every day except on Sunday.  On Sunday, I want to know it at 6 AM, 12 PM, 6 PM, and 12 AM.  Do not ask me why, just do it.

The above example tells me WHAT conditions exist in the world that would require a pulse to the signals you are currently doing manually.

Another example:

Suppose someone asks me, please update the runtime of the pumps on that s7-1200 PLC system.  Then they say, I want to know the runtime values anytime the pressure goes above 3 bar, 4 bar, and 5 bar.  When it below 3 bar, just report the runtime values if it ever drops to 2 bar.

These are the WHEN questions that can then be converted into PLC logic.

We do not know WHEN you want to replace your mouse and brain with PLC logic.

We have only heard you say what you want to DO when the "WHEN" stuff happens.

.

For Pump #1, let's say "Pump1Start" is the tag that when on causes Pump #1 to run.

If you can then tell me what one count equals in human time, I can help further.

For example, if running time is seconds, then something like this:

SCL:

IF "Pump1Start" AND "Clock_1Hz" THEN

IF NOT Last_Scan_Clock THEN

TRIGGER_COUNT := true;

ELSE

TRIGGER_COUNT := false;

END_IF;

END_IF;

Last_Scan_Clock := Clock_1Hz;

This is not tested, but it seems to satisfy the requirement of being able to increment a counter once a second.

If you need a counter to count once a minute, you need to create a way to detect a minute passing.  There are many ways, like using a TON timer, or comparing system date/time every scan until the minute value changes, or counting the seconds pulser above until it reaches 60 in a counter, then resetting the counter and triggering a minute count action.

Up to you how you implement it, but this is one way.  You will have to make it work in your own system and convert the above to LADder logic, but it could be as simple as something like this:

P1Run  CLK_1Hz                TRIGGER_CNT_P1
-| |-----| |---[P-TRIG]------------( )------

rick.fronda11

What condition(s) are required of the system that will cause a pulse to be created?

List them all please.

Dear Sir huggy,

When pump 1 will be started then that time the pulses should be started of this pump that will be the input of counter and counter will calculate the running time of pump.

similarly when pump 2 will be started then that time the pulses should be started of this pump that will be the input of counter and counter will calculate the running time of pump.

similarly when pump 3 will be started then that time the pulses should be started of this pump that will be the input of counter and counter will calculate the running time of pump.

Hope you understood it and help me now.

I do not understand why you give huggy_d1 a bad 1 star rating.
He and #dP have gone out of their way to help you.

Only you do not understand the help. The problem is with you, not with the two helpers.

huggy_d1

If someone ask me why I am clicking a box in the watch table, that is not the same as asking WHEN DO YOU CLICK THE BOX IN THE WATCH TABLE.

I wrote:

What condition(s) are required of the system that will cause a pulse to be created?

 My apologies for the "online" equivalent of yelling.

BUT YOU ARE NOT LISTENING.

WHAT happens in the world that makes you click the boxes in the watch table?

Suppose someone asks me, please update the runtime of pumps on that s7-1200 PLC system.  Then they say, I want to know the runtime values at 8 AM, 4 PM, and 12AM every day except on Sunday.  On Sunday, I want to know it at 6 AM, 12 PM, 6 PM, and 12 AM.  Do not ask me why, just do it.

The above example tells me WHAT conditions exist in the world that would require a pulse to the signals you are currently doing manually.

Another example:

Suppose someone asks me, please update the runtime of the pumps on that s7-1200 PLC system.  Then they say, I want to know the runtime values anytime the pressure goes above 3 bar, 4 bar, and 5 bar.  When it below 3 bar, just report the runtime values if it ever drops to 2 bar.

These are the WHEN questions that can then be converted into PLC logic.

We do not know WHEN you want to replace your mouse and brain with PLC logic.

We have only heard you say what you want to DO when the "WHEN" stuff happens.

.

rick.fronda11

Dear and respected sir huggy,

Please tell me the which functional blocks i need to use because my all programming is in functional block but not ladder logic.

P1Run  CLK_1Hz                TRIGGER_CNT_P1
-| |-----| |---[P-TRIG]------------( )------