Two questions about TIA / S7-1200 (I didn't feel right starting two threads at once):

1.  What is the simplest, cleanest way to code push-push logic on this platform?

2.  How does one compare a TON's current time (CT) to a fixed value?  I feel like this *should* be easy, but I think I'm struggling with data types here.

Thanks for any help.

Mike_Gera

1.  What is the simplest, cleanest way to code push-push logic on this platform?

 What is that push-push logic you speak of?

Mike_Gera

2.  How does one compare a TON's current time (CT) to a fixed value?  I feel like this *should* be easy, but I think I'm struggling with data types here.

Just use a comparator (I presume you use a LAD).

On the other hand, that's what a timer itself does - it compares a time which has passed since some point in the past with PT.

 Ah...this is the answer.

This sounds stupid (probably because it is), but I ASSumed that the defacto timer time was in ms.  Therefore, if I wanted to do something at or above 1 sec, for example, I was coding:

.ET >= 1000.

Never even thought to use "T#".

Thanks for the help.

jacek d

 

Mike_Gera

2.  How does one compare a TON's current time (CT) to a fixed value?  I feel like this *should* be easy, but I think I'm struggling with data types here.

Just use a comparator (I presume you use a LAD).

On the other hand, that's what a timer itself does - it compares a time which has passed since some point in the past with PT.

 OK, I'll take the bait, why is push-push (A.K.A. "double-tap") logic evil?

Thanks.

0_Einstein

Are you asking about a pushbutton getting pushed twice, like a double-tap?  If so, I recommend forgetting any request to implement double-tap pushbuttons until you have obtained a customer sign-off after delivery for the final payment.  Then say, double-tap is a consumer electronics feature best left at home and out of the workplace.

That is simply my opinion.

Mike_Gera

Two questions about TIA / S7-1200 (I didn't feel right starting two threads at once):

1.  What is the simplest, cleanest way to code push-push logic on this platform?

2.  How does one compare a TON's current time (CT) to a fixed value?  I feel like this *should* be easy, but I think I'm struggling with data types here.

Thanks for any help.

 

I now think that we're on two different pages.

By "push-push", I mean that one HMI (or physical) button works as both a 1 (ON) and a 0 (OFF) button.

When the controlled bit is in the 0 state and the button is pressed, the bit state becomes 1.  When the controlled bit is in the 1 state and the same button is pressed, the bit state becomes 0.

I am not talking about "double-clicking" a button.

Sorry for the confusion.

0_Einstein

Finding a or the universal double-tap speed that works for every customer, every customer's operators, every customer's technicians, every customer's engineers, and everyone who might help during install / commissioning of equipment - is virtually impossible.

You could develop a "customize screen" to adjust the double-tap timing, but that's something else to code, debug, and maintain.

Then there's the whole "what should double-tap do" intuitively in any given situation.

And of course, Siemens HMI's don't offer double-tap as a built-in option (last I checked anyway), so a non-HMI option should not implement it for those customers that require HMIs over individual PBs.

If you avoid the entire double-tap conversation by not allowing it, your hair stays attached to your head longer.

Mike_Gera

 OK, I'll take the bait, why is push-push (A.K.A. "double-tap") logic evil?

Thanks.

0_Einstein

Are you asking about a pushbutton getting pushed twice, like a double-tap?  If so, I recommend forgetting any request to implement double-tap pushbuttons until you have obtained a customer sign-off after delivery for the final payment.  Then say, double-tap is a consumer electronics feature best left at home and out of the workplace.

That is simply my opinion.

Mike_Gera

Two questions about TIA / S7-1200 (I didn't feel right starting two threads at once):

1.  What is the simplest, cleanest way to code push-push logic on this platform?

2.  How does one compare a TON's current time (CT) to a fixed value?  I feel like this *should* be easy, but I think I'm struggling with data types here.

Thanks for any help.

 

Good advice, and well-received.  Thanks! 

0_Einstein

Next time, click on the TON timer, then press F1.  Towards the bottom the built-in help system shows options for configuring the block in logic.  It will give you the "thought" of using T#, and provides you with links for valid TON PT input values (time datatype).

Mike_Gera

 Ah...this is the answer.

This sounds stupid (probably because it is), but I ASSumed that the defacto timer time was in ms.  Therefore, if I wanted to do something at or above 1 sec, for example, I was coding:

.ET >= 1000.

Never even thought to use "T#".

Thanks for the help.

jacek d

Mike_Gera

2.  How does one compare a TON's current time (CT) to a fixed value?  I feel like this *should* be easy, but I think I'm struggling with data types here.

Just use a comparator (I presume you use a LAD).

On the other hand, that's what a timer itself does - it compares a time which has passed since some point in the past with PT.

 

New question published by Mike_Gera is split to a separate thread with the subject How can enable E-Mail notifications for this forum?.

Best regards
Jen_Moderator

Mike_Gera

By "push-push", I mean that one HMI (or physical) button works as both a 1 (ON) and a 0 (OFF) button.

In case of Siemens it is called "toggle". And in their HMIs you can find a built-in function which does this.

In case of programming it by yourself, you need a positive pulse detection and an xor operation.