Hello everyone...

I am working on a project and I have used SCL language to create the FB. Now the problem is I have used timers in the FB. First, all was working fine. But as the complexity of the project increased and I have added more FB's and DB's to the project after a while timers in the FB's stopped working. The timer doesn't start even if the IN is true. At this movement, I am having the following problems-

1. Timers in FB are not starting after the IN is true.
2. After some changes in the program, CPU outputs in not turning on, even in online monitoring it shows on but in reality the output is off. whereas the expansion module outputs are working fine.
3. I tried resetting the CPU but no solution.

I tried using different instances of timers and each time after the timer is on I reset the timer by USING 'RESET_TIMER('....')'.

My CPU is 1212C 6ES7 212-1AE31-0XB0 FW-3.0

using TIA V15.

Could anyone give me any clue of how to resolve this problem?

I have attached some pictures of my projects here.

Thanks in advance.

x.nowshad

Hello everyone...

I am working on a project and I have used SCL language to create the FB. Now the problem is I have used timers in the FB. First, all was working fine. But as the complexity of the project increased and I have added more FB's and DB's to the project after a while timers in the FB's stopped working. The timer doesn't start even if the IN is true. At this movement, I am having the following problems-

1. Timers in FB are not starting after the IN is true.
2. After some changes in the program, CPU outputs in not turning on, even in online monitoring it shows on but in reality the output is off. whereas the expansion module outputs are working fine.
3. I tried resetting the CPU but no solution.

I tried using different instances of timers and each time after the timer is on I reset the timer by USING 'RESET_TIMER('....')'.

My CPU is 1212C 6ES7 212-1AE31-0XB0 FW-3.0

using TIA V15.

Could anyone give me any clue of how to resolve this problem?

I have attached some pictures of my projects here.

Thanks in advance.

Hello.

What you have shared with us is not very helpful. (I would love to have a conversation with you about naming conventions at some point.)

The official program guide says: Do not read states from parameter outputs. This was done for #Y21 and #Y22 in 4.JPG. Read online and see the states of all the various components. That would be more telling than the current screen capture.

I suggest you create two TEMP tags.
   #_done : BOOL
   #_elapsed : TIME

Use these two in all timers where the Q and ET pins are not linked to anything at the timer call. #_elapsed will be a good indicator that the timer is active, when monitoring the code online.

Next: Look through your list of outputs. Make a cross-reference of them. See where each output is used and how it is used. Suspect a problem if an output is written to more than once.

What are your thoughts up to this point?

x.nowshad

1. Timers in FB are not starting after the IN is true.

This can be the reason of the failure. 

Timers do not start when IN is TRUE. They start when IN changes from FALSE to TRUE, i.e. when in previous cycle IN was FALSE and in the current one IN is TRUE then a timer starts.

 Thank you for your reply.

here is one of the FB that contains timers. I will change the names and try again (thanks for the suggestion).

I will also try calling the timers without using its Q and ET.

another thing I want to clarify is the program runs ok for several times then stopped. I checked the output's cross-reference info. It's only used in one FB. I used a separate FB to drive the output directly. The malfunctioning FB only set and reset some DB bits which are used to drive the outputs.

My first doubt was regarding the timer instances that may be overlapped. but I checked is both ways. 

first, I use different timer instances for each call and reset the instance after use but no result.

secondly, I used only two instances everywhere, and once it's finished counting I reset the instance and reused it later.
In both cases, the result is the same. 

Here is one of my FB CASE statements................

-----------------------

Please ignore the naming I will change it.

thanks again for your reply.

qwazee

Hello.

What you have shared with us is not very helpful. (I would love to have a conversation with you about naming conventions at some point.)

The official program guide says: Do not read states from parameter outputs. This was done for #Y21 and #Y22 in 4.JPG. Read online and see the states of all the various components. That would be more telling than the current screen capture.

I suggest you create two TEMP tags.
   #_done : BOOL
   #_elapsed : TIME

Use these two in all timers where the Q and ET pins are not linked to anything at the timer call. #_elapsed will be a good indicator that the timer is active, when monitoring the code online.

Next: Look through your list of outputs. Make a cross-reference of them. See where each output is used and how it is used. Suspect a problem if an output is written to more than once.

What are your thoughts up to this point?

Thank you for your response.. 

I understand that timer will trigger only in raising the edge. could you please check my code segment in my previous reply.

jacek d

 

x.nowshad

1. Timers in FB are not starting after the IN is true.

This can be the reason of the failure. 

Timers do not start when IN is TRUE. They start when IN changes from FALSE to TRUE, i.e. when in previous cycle IN was FALSE and in the current one IN is TRUE then a timer starts.

x.nowshad

 Thank you for your reply.

here is one of the FB that contains timers. I will change the names and try again (thanks for the suggestion).

I will also try calling the timers without using its Q and ET.

another thing I want to clarify is the program runs ok for several times then stopped. I checked the output's cross-reference info. It's only used in one FB. I used a separate FB to drive the output directly. The malfunctioning FB only set and reset some DB bits which are used to drive the outputs.

My first doubt was regarding the timer instances that may be overlapped. but I checked is both ways. 

first, I use different timer instances for each call and reset the instance after use but no result.

secondly, I used only two instances everywhere, and once it's finished counting I reset the instance and reused it later.
In both cases, the result is the same. 

Here is one of my FB CASE statements................

5:

#G22 := TRUE;

#R21 := TRUE;

#RT22 := TRUE;

"m1r22_ton".TON(IN := #G22,

PT := #turn22_tme);

"m1yTime".TON(IN :=(#G22 AND #RT22),

PT := t#5s);

IF ("m1yTime".Q AND #G22) THEN

  #Y21 := FALSE;

  #Y22 := FALSE;

  RESET_TIMER("m1yTime");

END_IF;

IF "m1r22_ton".ET > (#turn22_tme - t#4s) THEN

  #Y22 := TRUE;

END_IF;

IF (("m1r21_ton".Q AND #G22 AND #R21 AND (NOT #hold)) OR #skip) THEN

  #RT22 := FALSE;

  RESET_TIMER("m1r22_ton");

  #state := 6;

ELSE

  #state := 5;

END_IF;

-----------------------

Please ignore the naming I will change it.

thanks again for your reply.

Hello.

The naming of the tags are not going to solve your problem.

Mr Jacek is correct of what the problem is. Think about moving the timers outside the CASE to ensure a transition can be seen. That means you will add a piece like (state = 5) for IN of the TIMER.

Good luck.

Hello Again,

I was able to run the timers. I tried putting timers outside the IF and CASE but didn't work. Then I tried different timers for each time I need a timer in the program. this works fine, irrespective of the timer position in to out of IF and CASE statement, until the FB is called again in the OB with a different instance.  Now I have the following questions

1. FB containing timer can be called only once in the program?

2. FB creates a separate DB for that instance but does it use the same DB of the timers?

3. Is this only happening in SCL or this is the same for every other language too? 

I believe there is something that I am missing, as if it's not possible to use FB(with timers inside) multiple times in the program, there is no sense of having FB. 

x.nowshad

I believe there is something that I am missing

And you are right.

If you want to build an FB which is able to have multiple instances, you can't use inside of it other FBs (yes, a timer is an FB too) which have their own global instance DBs. You must embed those FBs' instances in interface of your FB.

Programming guideline ch. 3.2.5