Well, the absolute addresses for the tags change with each version of the code, so this won’t be a one time thing. And, I have many PLCs and I want to automate this to a single click of the button.
Right now I export the S7 project to a text file and create the Kepware csv import file with a script in Ignition. I need to do the same thing if I am going to use the built in Siemens driver. How should I approach this? Create a csv file and import the tags through the designer? Or create a query and write the tags directly to the database? I would prefer the latter because then I could fully automate the process and update the tags from a client without opening the designer at all. But, maybe there is something else in your architecture that prevents this?
Lastly, I use dot names in the PLC (they are based on the hierarchy of the udts), so I have something like Machine.Motor.Running.Status, and Kepware creates folders based on the dots, so the tag appears as Machine_1/Motor_2/Running/Status. When I export the SQL tags from Ignition, I can see that it does something with these folders, but can’t really see a pattern. Should I just skip the folder approach and create the tags in a long list like Machine_1_Motor_2_Running_Status? Otherwise, how does the tag structure work in Ignition if I wanted to create the csv file with scripting?