Update to the Tag Configuration Editor

[BeCeGa]

We are updating the TCE. This update will allow it to work with the latest version of the CVT, and be able to use the new features from it.

Some changes will be making will affect how the tags are displayed in the tree, and adding additional functions like multiple variable editing and filtering.  If you have any feedback on using this tool please let me know what features you like and would still require in the new version.

The new version will be able to import configurations created in the previous version.

We are considering removing the folders of the editor, and allow creating Groups as defined in the new CVT. Is anyone using the folders or have several layers of the folders?

How many tags have your biggest projects using TCE?

Thank you for the feedback

Benjamin Celis

[LeifS]

Sorry, I didn't see this post until now.

We currently use the TCE in two CIE-CVT based projects.

The TCE-file contains three controllers, two PXI and one cRIO, and three HMI's and below all these we use folders to logically group different tags. I think we could use the new grouping ability instead of folders.

The total no of tags (CIE+Local CVT+Network) is approximately 300-400 in the XML-file.

[smithd]

Thanks for the feedback. One of the things benjamin didn't mention is that we're also looking at using a different tree view, as this would allow us to reuse the code from the tag bus framework (see some of the other documents in this project) and get the TCE up and running more quickly. While the TCE is tag focused, this implementation would instead be component-focused, like what you see here:

This has some pros:

• Reuse significant amounts of UI and configuration validation code.
• Easier to understand the use of a given component -- all the scan engine data is in one place, for example
• maps more directly to the actual software, which may make it easier to understand.

But there are some cons we know of as well:

• Its a big departure from the existing TCE
• Its difficult to visualize interactions between different components
  • We've tried to resolve this in part with different mapping views, like what you see below. Here, a scan engine channel is being mapped to the CVT and to a UI element.

So some followup questions:

How do you feel about these changes?

Are there other cons you can thing of?

In your use have you thought of better ways to represent this information?

Thanks,

Daniel