How to change Constant with address in CASE loop TIA Portal 15.1

L D[AR2P#0.0] · Jul 4, 2020

Here's an example timing diagram showing what the code can do...

drbitboy · Jul 4, 2020

L D[AR2 said:
Here's the description from the TIA help...

thank you.

It's triggered on a rising edge of .IN, and it runs* until it expires, no matter what that .IN does after the rising edge.

* it is effectively sealed-in by its running state

Sergihno · Jul 4, 2020

What's wrong?

Sergihno · Jul 4, 2020

There is working example of what I have now with fixed period 1h=3sec
https://vimeo.com/user117954686/review/435345219/e91e715863

L D[AR2P#0.0] · Jul 4, 2020

The parameters PT and IN are in a different order in my screen shot....

chelton · Jul 4, 2020

@Sergihno don't forget to change your arrays to 0..23

Sergihno · Jul 5, 2020

L D[AR2 said:
The parameters PT and IN are in a different order in my screen shot....

But its done by system when I added timer.

Sergihno · Jul 5, 2020

chelton said:
@Sergihno don't forget to change your arrays to 0..23

Thank you, but I dont use real time stamp.

Sergihno · Jul 5, 2020

I tried as you mentioned, but its still the same. Could you please help with that.

chelton · Jul 6, 2020

You need to change the entire assignment, not just the PT:= and IN:=

Code:

#fbPulse(PT:= "db10_ScheduleData".PulseTime[#HourNow],
IN:=(#HourNow <> #HourOld) AND "db10_ScheduleData".TimeSlotEnabled[#HourNow],
Q => "Tag7")

Sergihno · Jul 6, 2020

L D[AR2 said:
The parameters PT and IN are in a different order in my screen shot....

I dont know why, but I have the parameters in this order by default, I dont change anything.

L D[AR2P#0.0] · Jul 6, 2020

The order of the parameters is not important, it is the argument that you supply to each parameter that is important.
Read the help for the TP block. The IN parameter is of type BOOL, but you were/are passing a TIME data type, hence the compiler error. Same for the PT parameter - it is of type TIME but you were/are passing a BOOL.

Sergihno · Jul 6, 2020

L D[AR2 said:
The order of the parameters is not important, it is the argument that you supply to each parameter that is important.
Read the help for the TP block. The IN parameter is of type BOOL, but you were/are passing a TIME data type, hence the compiler error. Same for the PT parameter - it is of type TIME but you were/are passing a BOOL.

Yeap, I've just readded it and it works. Thank you.

But now it is another issue. The index which is in [] in FB, cause PLC error. It's because time index is more than 23. I solved it

Then , I created my counter of 1 sec, counting till 23 and use it as index inside FB for choosing button and time from array, and then when it is reach 23 I reset it automatically, but the whole logic works different from I need. Maybe I described it in different way.
I attached diagram and logic what is should be. Could you please look through it?

L D[AR2P#0.0] · Jul 6, 2020

I don't understand your requirement. Please show the hours on your timing diagram.

drbitboy · Jul 6, 2020

If all twenty-four [duration of action out] values are 3s, then this pattern (6s of OUT:=1, 15s of OUT:=0, 3s of OUT:=1, etc.) would repeat every 72s.

Is that correct?

Or is it OUT:=1 for 6s at the start of hour 1, then OUT:=0 for 6s at the start of hour 3, etc?

How to change Constant with address in CASE loop TIA Portal 15.1

L D[AR2P#0.0]

Lifetime Supporting Member

drbitboy

Lifetime Supporting Member

Sergihno

Member

Sergihno

Member

L D[AR2P#0.0]

Lifetime Supporting Member

chelton

Member

Sergihno

Member

Sergihno

Member

Sergihno

Member

chelton

Member

Sergihno

Member

L D[AR2P#0.0]

Lifetime Supporting Member

Sergihno

Member

L D[AR2P#0.0]

Lifetime Supporting Member

drbitboy

Lifetime Supporting Member

Similar Topics