Hi team,
I am trying to use remote tag provider. since this is my first time i want to understand what can be done in remote tag provider and what cannot be. i have got the tags from source gateway. Is it possible to use tag change scripts in remote tags?
I also have UDT in which parameters are configured. is it possible for me to access the parameters in Remote tag change scripts?
It will be useful if someone could just give me the insights for remote tag providers.
Thanks in advance.
Think of remote tag providers as a reference to the source. Anything you do to the rtp will actually be done on the source. Note There are security settings on tag providers that from memory limit configuration via an rtp, so check those out.
One key thing to note is that the max update rate of tags on the rtp side will be capped at 1s
okay understood.
So i have source gateway where PLC devices are connected and OPC tags are configured. Now i have connected these tags in remote gateway. i can see the tags but the values are showing bad quality. is it necessary to configure PLC devices in remote gateway too?
Lets say gateway #1 (GW1) is your gateway that has the working OPC tags connected to devices, and gateway #2 (GW2) is the gateway that has a RTP set up to GW1's local tag provider. (I word it like this because "remote" is a relative term and can get confusing when trying to describe these situations.)
GW2 will not use OPC tags at all to talk to anything in GW1 as it will only need to use tags from GW1. If GW2 is allowed to edit tags in GW1, then any changes you make to GW1 tags from GW2 (including scripts on UDTs, etc) will execute and change on GW1, not GW2. If you need something like a value change script on GW1 tags, you'll have to create a reference tag in GW2 pointing to the tag in GW1, then put your value change script on the GW2 tag.
Or just use a gateway tag change event in a project in GW2. No reference tag required.
Plc device connections make plc tags available within the local gateway's opc-ua server. Ignition tag providers can be mapped to tags within any opc-ua client connection, including the local one. You could create an opc-ua client connection to other ignition gateway opc-ua servers, and this is one way that you could read a plc's tags if the plc is connected to another gateway. But you wouldn't be using a remote tag provider in this case.. This would circumnavigate the 1s poll rate limitation, but I'm not sure what impacts it would have...
If you add a plc device connection to your gw that has the rtp to another gateway, the tags in the rtp cannot see the device connections in your local gateway