...
If it is required not to transfer the values of specific objects, it is possible to start the GateWay Client process with one or more parameters /XOV (eXclude Object Values).
...
Objects whose names match the specified mask will not be transferred (not even their descendants). The /XOV parameter has a higher priority than the /ROV parameter.
Example: The transfer of all structured variables except system structures can be achieved by specifying /ROVSV.* /XOVSV._System*
Changing object names
If it is necessary to change object names (i.e. on the GateWay Client side, D2000 objects are named differently than on the GateWay Server side), it is possible to start the GateWay Client process with one or more /MON (Modify Object Names) parameters.
Syntax: /MON<expression,replacement>
Example: Deleting the string "MPPS." in the names of the opened objects we achieve by specifying /MONMPPS\.,
Example: Replacement MPPS -> MES is achieved with the parameter /MONMPPS,MES
Note: at most one substitution is performed on the D2000 object name (expression is searched for from the beginning of the name). For example, if an I/O tag M.MPPS.test.MPPS exists, then the parameter /MONMPPS,MES causes the I/O tag M.MES.test.MPPS to be opened on the remote side.
Pairing objects by UID
Transparent gateway supports pairing not only by object names but also by UID objects. This feature is enabled by the start parameter /UID, which must be used when starting both the GateWay Client and GateWay Server processes.
This feature can be used to implement the functionality of a transparent gateway regardless of changes in the names of the objects (provided that they have the same UID), i.e. objects can be renamed.
...