Emerson PLCs support tag names that have a period in them as a part off how they support UDTs EG “BaseName.FieldName”. When importing tags like this into Ignition, the period automatically gets converted to an underscore. Thus “BaseName.FieldName” becomes “BaseName_FieldName” (but the OPC Item path retains the period).
From Tag Naming, Characters not allowed there is a vague allusion to tags conforming to the \L regex (I say vague because regex’s are very implementation specific). My takeaway from that question is that Ignition supports more non-alphanumeric characters than just an underscore.
So the conversion of a period to an underscore was one of many possible conversions that Ignition could make. What I want to know is if it is possible to manually control this choice with some sort of table that we can explicitly define how unsupported characters are converted to supported characters in tag names?
My desire for this stems from the PLC code I generally work with, where there can be tags “Name.Field” and “Name_Field” in the PLC that are both valid and totally independent tags (don’t ask!), so it is currently impossible to import both into Ignition at the same time. But if I could only just control the renaming process …
I’m not sure what other character you would use, but if you manually create the tag names (or write your own script to do it) then you can control how that happens, but I believe that is the only option you have.
Ahh I see, you assigned creating this task to some random person you hauled off the street, and you have no clue how they did it! Would it be reasonable to reign in this process with a table of explicit substitutions (with a fall back to the automagic process)
But even with manually re-naming the tags, how do I know what is valid without doing trial and error?