Inheriting Signal Name Attribute from Single Scalar Data

[spastichawk]

I am currently trying to log data to a file. Attached is a small clip of the program where I am logging the data. Functionally the code shown works and produces the output that I want except for naming the columns in the excel sheet with the correct signal names. In the past I have used the "Set Attributes" express vi to fix this but it is cumbersome especially when making any upstream code changes. Is there a way to have it assume the signal names automagically?

[LocalDSP]

What do you mean with 'cumbersome' and what type of upstream changes are you doing that don't reflect in your Attributes management code?

In your screenshot the parameter names are easily extractable from the cluster properties, but of course if you change the cluster content, that won't work straight forward.

So please attach example VIs of what works and what is challenging you, that will help the community understanding where you get stucked.

[spastichawk]

If I want the signal names to transfer from the cluster, i need to convert to a dynamic signal then modify signal attributes where I manually populate the name string. If i modify the name of the signal in the cluster where the cluster is built i then need to manually update the name for the log file.

If i can extract the name (string) from the cluster then i can make this function automatic for each item in a cluster.

[LocalDSP]

It sounds like your problem is more related to getting the right parameter name (label?) from your cluster. Please correct me if I am wrong.

I guess what you need to do is to create a TypeDef that defines the cluster and use that TypeDef Control/Indicator both where you are creating and where you are reading your cluster. You'll then only have to update that TypeDef every time you modify your cluster parameter names (or content in general).

  An alternative (and more generic) approach to your task would require you to pass both parameter name (string) and value (what-ever-it-is) as part of your cluster, eventually as an array of clusters if needed.