I have an existing machine running a ignition project. We are creating a duplicate machine, and want it to run a separate but identical ignition project. Both of these machines will have their own PLCs with different IP addresses, but are running on the same ignition gateway.
What would be the best way to go about this? I know I can export the project and import it into a new project, and I can export the tags to a text file, then mass edit the paths and folders to separate them for the new PLC. How would I go about changing all of the tag bindings to point to the new tags only on the new project though? Do I need to go through and manually edit every single tag binding?
I'd probably handle this as such.
- Create a separate tag provider for each project.
- Create the main project, and then create a project for each machine that inherits from the main project. Then in each of those projects would be assigned the tag provider.
If you have event scripts etc... in the project then it gets a bit more complicated.
In this way, then future projects are just export tags, change the PLC and re-import into a new tag provider.
1 Like
If you have event scripts etc... in the project then it gets a bit more complicated.
You'll need to ensure whatever is running the scripts respects which child project it is in
If you plan on scaling this out to more than 2 machines, you might want to start looking into a hub and spoke architecture where each "machine" has its own PC running Ignition Edge and sending data to your central Ignition gateway. This also helps when you need to upgrade the main server, it won't impact production as each machine is independent and has their own store and forward mechanism. Again, depending on how much scaling out you need.