# Indirect OpcItemPath

**URL:** <https://forum.inductiveautomation.com/t/indirect-opcitempath/74957>\
**Category:** Ignition\
**Created:** [June 13, 2023, 1:56pm UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957 "2023-06-13T13:56:25Z")\
**Posts on this page:** 13\
**Page:** 2

<div class="post-metadata">

**Author:** ![SHuidrom](https://avatars.discourse-cdn.com/v4/letter/s/3be4f8/32.png) [@SHuidrom](https://forum.inductiveautomation.com/u/SHuidrom)\
**Post date:** [June 30, 2023, 6:35am UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/21 "2023-06-30T06:35:06Z")

</div>

@woodsb02, you were right. We have identified that on the PLC comms device settings, there are allowed 16 concurrent connections on one comms device for MODBUS-TCP option. But these needs to be 'Enabled' on the PLC comms device level depending on how many connections are needed (out of 16), and each connection assigned to the respective modbus-tcp slave IP address.  
This will allow concurrent device connection on Ignition scada.

---

<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:** [July 12, 2023, 6:17pm UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/22 "2023-07-12T18:17:32Z")

</div>

This might be of interest:

> [@Ignition OPC UA Server Redundancy (Modbus TCP)](https://forum.inductiveautomation.com/t/ignition-opc-ua-server-redundancy-modbus-tcp/67123/10):
>
> It wasn't quite as easy as the last change, but relatively easy. Utterly untested, feedback welcome: BETA for Ignition 8.1: [v1.1.4.231931604](https://www.automation-pros.com/ignition/Advanced%20Modbus%20Driver-1.1.4.231931604-v81.modl) Some notes: When active, the driver alternates between the live connections on a per-batch basis. For this driver, a "batch" is a memory area subset of a single system.opc.readValues() request, system.opc.writeValues() request, or subscription poll. (Coils with coils, discrete inputs with discretes, et cetera.) This is effectively load-balancing bet…

---

<div class="post-metadata">

**Author:** ![woodsb02](https://avatars.discourse-cdn.com/v4/letter/w/6a8cbe/32.png) [@woodsb02](https://forum.inductiveautomation.com/u/woodsb02)\
**Post date:** [July 12, 2023, 9:31pm UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/24 "2023-07-12T21:31:26Z")

</div>

> [@pturmel](#):
>
> This might be of interest

This is fantastic - thanks - I’ll definitely give it a try. This will definitely be an advantage for us to use your advanced modbus driver.

I’ve also submitted this as an “idea” to add support for redundant slaves to the Modbus TCP driver that comes out of the box in Ignition. If others would like to see this supported added to Ignition, it would help if you up-voted the idea at the link below.  
[https://inductiveautomation.canny.io/ignition-features-and-ideas/p/modbus-tcp-driver-redundancy](https://inductiveautomation.canny.io/ignition-features-and-ideas/p/modbus-tcp-driver-redundancy)

---

<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:** [July 13, 2023, 12:56am UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/25 "2023-07-13T00:56:04Z")

</div>

> [@woodsb02](#):
>
> help if you up-voted the idea

Heh. You know _ **I'm** _ not gonna up-vote it... 🤑

---

<div class="post-metadata">

**Author:** ![woodsb02](https://avatars.discourse-cdn.com/v4/letter/w/6a8cbe/32.png) [@woodsb02](https://forum.inductiveautomation.com/u/woodsb02)\
**Post date:** [August 28, 2024, 3:00pm UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/26 "2024-08-28T15:00:02Z")

</div>

Quick update - correct me if I’m wrong, but the `system.device.setDeviceHostname` solution doesn’t work if you’re running on the redundant gateway, because Ignition only allows you to make configuration changes on the master gateway.

Does that sound correct?

The scenario here is redundant ignition servers with a redundant Modbus connection. If the master ignition server is down (so the backup server is active), and then the primary modbus connection fails (so the backup ignition server has to failover the device connection to the secondary modbus hostname/IP address).

---

<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 28, 2024, 3:02pm UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/27 "2024-08-28T15:02:09Z")

</div>

That sounds right.

---

<div class="post-metadata">

**Author:** ![woodsb02](https://avatars.discourse-cdn.com/v4/letter/w/6a8cbe/32.png) [@woodsb02](https://forum.inductiveautomation.com/u/woodsb02)\
**Post date:** [August 28, 2024, 3:09pm UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/28 "2024-08-28T15:09:57Z")

</div>

Thanks.

Am I correct that when the backup ignition server is active, whilst you cannot write to device configuration - you CAN write to UDT parameters… and therefore the alternative solution of using UDT inheritance to dynamically modify the OpcItemPath should work on the backup server?

---

<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 28, 2024, 3:22pm UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/29 "2024-08-28T15:22:11Z")

</div>

That also sounds right, but I'm not sure, so it's probably best to try it and see.

---

<div class="post-metadata">

**Author:** ![woodsb02](https://avatars.discourse-cdn.com/v4/letter/w/6a8cbe/32.png) [@woodsb02](https://forum.inductiveautomation.com/u/woodsb02)\
**Post date:** [August 31, 2024, 2:15am UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/30 "2024-08-31T02:15:25Z")

</div>

@Kevin.Herron do you think there is a chance the feature to use the `system.device.setDeviceHostname` function on the backup server could be implemented? (Would it help if I submitted it to the ideas page?)

USE CASE 1 (higher priority) - After a gateway failover, when the backup server is active - to allow redundant PLC comms from the backup server to continue to work.

USE CASE 2 (lower priority) - when the backup server is standby with a “warm” configuration - when comms to PLC-A address is good from the primary server but bad from the backup server (so only the backup server could fail over to PLC-B address for warm).

---

<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 31, 2024, 2:31am UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/31 "2024-08-31T02:31:07Z")

</div>

No, configuration of the backup gateway is fundamentally not allowed to be modified.

8.3 is introducing a new concept where essentially anything with configuration can optionally have a backup-specific version of that configuration that is used when the running gateway is in the backup role.

---

<div class="post-metadata">

**Author:** ![woodsb02](https://avatars.discourse-cdn.com/v4/letter/w/6a8cbe/32.png) [@woodsb02](https://forum.inductiveautomation.com/u/woodsb02)\
**Post date:** [August 31, 2024, 2:46am UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/32 "2024-08-31T02:46:42Z")

</div>

That sounds like a nice feature for 8.3.

However, it doesn’t help in this case, because we want the hostname configuration to be able to be dynamically changed on the (active) backup based on health communication status to the PLC.

Anyone with redundant servers connecting to redundant PLCs is likely to want this.

Is it possible to make this one gateway configuration editable on the backup server (an exception to the rule)?

---

<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 31, 2024, 2:49am UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/33 "2024-08-31T02:49:47Z")

</div>

> [@woodsb02](#):
>
> Is it possible to make this one gateway configuration editable on the backup server (an exception to the rule)?

No, sorry, not going to happen.

What you really want is first class support for network redundancy in the drivers, like what Kepware calls media-level redundancy (I think). Something like that isn't going to get implemented in an 8.1 point release and neither is some hack to make `setDeviceHostname` somehow work on the backup gateway.

---

<div class="post-metadata">

**Author:** ![woodsb02](https://avatars.discourse-cdn.com/v4/letter/w/6a8cbe/32.png) [@woodsb02](https://forum.inductiveautomation.com/u/woodsb02)\
**Post date:** [August 31, 2024, 2:52am UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/34 "2024-08-31T02:52:41Z")

</div>

Ok, thanks for letting me know.

[Previous page](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957.md?page=1)
