Passing a parameter in a tag path in Expression tags

Ignition
,
1

Hello Everyone,
Might be a dumb question but is it possible to have {[PLC]tag_Path/path/{some parameter}/Something.value}
Where the parameter will be the template custom property. I want to use this in the case of Signal Generator so there's no custom property for that.

Elaborating more:
I have conveyor animation template in which I used Signal Generator for smoother effect using this guide Component Animation. I have several conveyor based station and so I created a template for the conveyor +signal generator. I have two expression tags. One tag provides the following output: "Receive", "Loaded", "Unloaded". The other tag provides "Active", "Complete", "Incomplete". All outputs are string datatype. Currently I only care about "Receive" state. The conditions are like following:
"Receive": "Active" <-- Means conveyor running
"Receive": "Complete" <-- Receiving complete. Conveyor stop
I want to run signal generator according to those conditions in order to have conveyor animation. There are several stations and each station has its own conveyor belt. Hence, I have several expression tags.

Now, how do I use those condition to run the signal generator component? This component is not flexible in terms of scripting as there are no custom properties option. I thought using Expression tag {[PLC]tag_Path/path/{StationName}/Something.value} I could pass "StationName" parameter which is custom property of the tamplate. Is there any other way to do this efficiently?

2

It's a bit unclear what you're asking exactly.
Are you talking about a tag binding ?

3

My bad let me make things more clear.

4

If you want an indirect tag in an expression you can use tag(), so it could be:

tag([PLC]tag_Path/path/{StationName}/Something) will return that indirect tags value

5

yeah but using tag() causes performance issues.

6

Do you mean you cannot add a custom property ? That seems odd to me. What component is it exactly ?

Using indirect tag bindings on custom properties for both tags, then using those in expressions, would be the best solution.

7

That's signal generator component.
image

8

If a component doesn't support custom props, and you need one, create the custom property on the container.

Nesting curly braces is completely unsupported. In a UI, the alternative approach is to move the subexpression to a custom property with an indirect binding. In expression tags--only expression tags--you would use the tag() expression function.