0
Function group logic works even when it is disabled
When using a function group with a slope filter, I encountered a problem: the slope continues to increase, even when the group is disabled. It appears that the group continues calculating in the background.
Customer support service by UserEcho
What IQANdesign version are you using?
Are you sure the slope is continuing to work when the group is disabled?
The slope will not remember the value it had when you disabled the group and will start from whatever the input is when it is enabled.
Hi Thomas,
We've run this program for some years now with no problem, and we encountered this problem after one of the latest updates to 7.
I do have a movie of it. In it, the input is 0, and also the slope is 0 when the group is disabled. When enabled, it is directly 93, the max setting.
I did some testing and can not see any different behavior from 6.08 to 7.06 in regards to the slope being enabled and disabled.
Would it be possible to see the function group in question to see if i can figure out what is going on here?
Hi Thomas,
I made this program to show the problem. In the actual program, I can't find a difference other than a different calculation order in the program. It looks like the slope is doing the slope calculation before it looks to its enable state, after putting in a delay of one cycle you can see the difference in behavior of the slope.I would expect the slope would first check its enable state before staring the calculation
Test.idax
This seems to be working as it should.
The behavior has to do with the initial value of the input to the slopes when it is enabled.
The one without delay has the input value set to 100 when it is calculated the first time so that is the starting value for that slope.
The one with delay has the input set to 0 for the first calculation so it gets that starting value.
Then the next cycle the input becomes 100 and starts to slope up to that.
You can get this behavior by shifting the calculation order inside the group.
Take the one without delay for example.
If you put the slope before the input math channel in the calculation order you will get the same behavior as the one with the delay.
So if you have done an auto order inside the group it could have shifted the behavior of your application.
Tested this in 7.06, 6.08 and 5.08 and it works the same in all.