Hi All, Wondered if anyone could offer us some advice regarding an issue we're seeing with multiple expression tags. It appears that SOME (not all) of our expression tags result in an Error_EspressionEval error. They're all based on a UDT and are quite simple 'If' logic in the main. One of our t…

[image] Robert_Collinson: One of our tags named P_Target_Count is itself is returning an Integer with the following expression: Are you recursively referencing the P_Target_Count tag?

Thanks for the reply, only, apologies, not sure what you mean...can you expand on this?

Sure, You say that P_Target_Count is returning an Integer with the expression. That expression is referencing the Tag {[.]P_Target_Count}.

Ah, sorry, yes, it is 'self referential'...is that a bad thing to do? This is code we've been passed to support, and, as mentioned, seems to work fine when used in Ignition 7.9...it seems however no longer to be the case within the 8.1 test system we've been asked to migrate it over to though

In other words, expression tags are not really designed to handle X = X + 1 or anything like it. If it worked in v7.9, it was by accident.

Magic! I mean, even in 8.1, it works for a while :smiley: how could we get around this issue then...is the answer going to be...scripts, many, many scripts?

[image] Robert_Collinson: Ah, sorry, yes, it is 'self referential'...is that a bad thing to do? Yeah, definitely not a great practice. One I'm surprised works at all. [image] Robert_Collinson: how could we get around this issue then... Is this really something that needs to be Gatewa…

Looks like you are trying to integrate over time? Use timestamps and value change events to control the action, a "prior accumulation" for rate changes, and an expression tag to yield current value from time.

have to be honest, it uses the words 'time' only, it seems to be a 'counter' based on the the tag update rate...ticking up +1 for every cycle through the tags. Not entirely sure it's time based...i mean, you're right, it could be as we'd just need to look at the cycle time and work backwards from t…

[image] Robert_Collinson: based on the the tag update rate That means it is integrating over time. Change the update rate (which isn't very precise anyways) and you change the result. Using timestamps as the basis for the calculation makes it independent of the tag update rate.

Inductive Automation Forum

Basic Integer Expression Tag producing Error_ExpressionEval error

Ignition

vision, ignition81

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled