# Running a project on multiple terminals, without interfering with each other

**URL:** <https://forum.inductiveautomation.com/t/running-a-project-on-multiple-terminals-without-interfering-with-each-other/98214>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [November 5, 2024, 3:00pm UTC](https://forum.inductiveautomation.com/t/running-a-project-on-multiple-terminals-without-interfering-with-each-other/98214 "2024-11-05T15:00:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Raymond\_Wyant](https://avatars.discourse-cdn.com/v4/letter/r/43a26b/32.png) [@Raymond\_Wyant](https://forum.inductiveautomation.com/u/Raymond_Wyant)\
**Post date:** [November 5, 2024, 3:00pm UTC](https://forum.inductiveautomation.com/t/running-a-project-on-multiple-terminals-without-interfering-with-each-other/98214/1 "2024-11-05T15:00:40Z")

</div>

Hello. I just started working with ignition, and finished my core course a couple weeks ago. The project I am working on involves replacing an old Labview system with Ignition. Currently, the Labview is run on ech terminal completely independently, and there is a set of "system" variables that are set for each line, 1, 2, and 3.

I am trying to figure out the best way to do this with Ignition, as I don't want tags to be carried over from one system to another, so I was thinking I might have to make a project and associated tags for each system? Or is there a way to make a tag that is specific to an instance of the client launcher?

I can absolutely give more details, I am just a bit lost as to what to do here.

Thanks.

---

<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:** [November 5, 2024, 3:17pm UTC](https://forum.inductiveautomation.com/t/running-a-project-on-multiple-terminals-without-interfering-with-each-other/98214/2 "2024-11-05T15:17:13Z")

</div>

> [@Raymond\_Wyant](#):
>
> client launcher?

This suggests you plan to use Vision? (You should tag your topic.) If so, Vision client projects can define "Vision Client Tags", which exist independently in each running client. Similar functionality is available in Perspective session properties.

Be aware that such tags/properties cease to exist when the client is closed.

---

<div class="post-metadata">

**Author:** ![Raymond\_Wyant](https://avatars.discourse-cdn.com/v4/letter/r/43a26b/32.png) [@Raymond\_Wyant](https://forum.inductiveautomation.com/u/Raymond_Wyant)\
**Post date:** [November 5, 2024, 3:19pm UTC](https://forum.inductiveautomation.com/t/running-a-project-on-multiple-terminals-without-interfering-with-each-other/98214/3 "2024-11-05T15:19:16Z")

</div>

This is Vision. I apologize, I am just getting started into this, and I didn't even think about tagging it as such.

That sounds like exactly what I need to do. Thank you. Could you give me a rough idea where to look for this?

---

<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:** [November 5, 2024, 3:22pm UTC](https://forum.inductiveautomation.com/t/running-a-project-on-multiple-terminals-without-interfering-with-each-other/98214/4 "2024-11-05T15:22:21Z")

</div>

When working on Vision objects, like windows or templates, the Ignition Tag browser exposes another Tag Provider in the drop-down at the top of that panel, for "Vision Client Tags".

---

<div class="post-metadata">

**Author:** ![Raymond\_Wyant](https://avatars.discourse-cdn.com/v4/letter/r/43a26b/32.png) [@Raymond\_Wyant](https://forum.inductiveautomation.com/u/Raymond_Wyant)\
**Post date:** [November 5, 2024, 3:24pm UTC](https://forum.inductiveautomation.com/t/running-a-project-on-multiple-terminals-without-interfering-with-each-other/98214/5 "2024-11-05T15:24:47Z")

</div>

Thank you very much, this is exactly what I needed.
