Having to redo a thousand tag paths because default tag provider

Ignition
1

I've completed importing and setting up a project on an edge gateway that would normally go on a regular central ignition gateway. The problem is there's thousands of tag path references for example "AI/PT-1010/Val" that work great on regular ignition gateways because ignition just auto fills in the path provider with "[default]". This works great so one project will work with many providers. The problem is that on an ignition edge gateway the provider needs to be "[edge]" not "[default]". I'm getting errors because all of my tag paths such as "AI/PT-1010/Val" are trying to read "[default]AI/PT-1010/Val" and not "[edge]AI/PT-1010/Val". If they know "[edge]" is the only provider possible on an edge gateway why would they still default the tag paths with the "[default]" provider prefix?

I need a way to add [edge] before every single tag path where ignition would normally put [default]. I feel like this should just have been done by ignition itself because edge doesn't even have the capability to do a [default] provider. This will save me days of work any help is appreciated. Thanks!

2

It's a project setting in standard Ignition. That [default] carried over when you moved the project. If the project had been created in Edge, it would be fine.

Look in the project properties in your Edge system to see if you can get to the default provider setting.

If not, it might be easiest to change the default provider setting in your standard Ignition instance (to "edge") and re-export. (Temporarily create a provider named "edge" to make the choice possible.)

2 Likes
3

Life saver I believe that worked thanks so so much.

4

I had to use Find and Replace to fix my issue.

1 Like