# Project Memory/Tag Structure With Duplicate Device IP

**URL:** <https://forum.inductiveautomation.com/t/project-memory-tag-structure-with-duplicate-device-ip/19172>\
**Category:** Ignition\
**Created:** [August 9, 2018, 1:55pm UTC](https://forum.inductiveautomation.com/t/project-memory-tag-structure-with-duplicate-device-ip/19172 "2018-08-09T13:55:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![19tb21](https://avatars.discourse-cdn.com/v4/letter/1/0ea827/32.png) [@19tb21](https://forum.inductiveautomation.com/u/19tb21)\
**Post date:** [August 9, 2018, 1:55pm UTC](https://forum.inductiveautomation.com/t/project-memory-tag-structure-with-duplicate-device-ip/19172/1 "2018-08-09T13:55:21Z")

</div>

Good Morning,

I am getting ready to commission a program change on an Allen Bradley CompactLogix PLC. I intend to test the changes with an Ignition HMI I have built. However right now, I have no OPC tag binding set-up in the HMI program because the OPC tags do not yet exist in Ignition.

I intend to create a new device in the Ignition Gateway and point it the processor. However, right now, there is a different existing, more SCADA-like project that uses a few tags from the current PLC program. Can I simply disable the device in the gateway, create a new device with the same IP address and thus set up a separate device from which I can pull in tags for the new PLC project?

Will this have any deleterious effect on the other existing project with its existing tag binding? I may need to roll it back if I can’t get the kinks worked out before production starts again.

Thanks,

T

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 9, 2018, 1:58pm UTC](https://forum.inductiveautomation.com/t/project-memory-tag-structure-with-duplicate-device-ip/19172/2 "2018-08-09T13:58:26Z")

</div>

There’s no problem with this.

Your new device will have to be named something different, and any tags you currently have set up that point to the device you’re going to disable will have bad quality.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 9, 2018, 3:54pm UTC](https://forum.inductiveautomation.com/t/project-memory-tag-structure-with-duplicate-device-ip/19172/3 "2018-08-09T15:54:18Z")

</div>

Or don’t disable the other driver. You can have multiple simultaneous drivers pointing at the same PLC. This is quite helpful if there are throughput problems due to network latency (up to the PLCs connection limits).

---

<div class="post-metadata">

**Author:** ![19tb21](https://avatars.discourse-cdn.com/v4/letter/1/0ea827/32.png) [@19tb21](https://forum.inductiveautomation.com/u/19tb21)\
**Post date:** [August 9, 2018, 5:11pm UTC](https://forum.inductiveautomation.com/t/project-memory-tag-structure-with-duplicate-device-ip/19172/4 "2018-08-09T17:11:09Z")

</div>

Oh, very interesting point.