The D2000 GateWay Client process can also be configured to access remote communication objects. In this mode, it masquerades as a KOM process (i.e., process SOME_NAME.KOM). It receives a list of communication objects for which it is the parent (lines, stations, I/O tags) from the D2000 Server, and tries to verify whether the required communication objects exist in the source system and, if so, ensures the transfer of the values of these objects. Unlike the transparent gateway mode, writing (control of output I/O tags) is also supported. Working with I/O tag process alarms (acknowledging, blocking, unblocking) is supported only if the D2000 GateWay Server is version 21.1 Rel 72 or later, with a patch dated September 11, 2026, or later.

Acknowledgement of process alarms is not yet supported.
Note: Writing in manual mode (manual setting of values), writing via the control object as well as setting the default value of output I/O tag works, but the remote I/O tag must be in manual mode (in the D2000 system, where the actual D2000 KOM process is running). Once the remote I/O tag is in automatic mode or has a default value (automatic/manual), writes made via the D2000 GateWay Client will be ignored (similar to attempts to write from a script). Since from the perspective of the remote point, all writes made via the D2000 GateWay Client are in manual mode, the values ​​will have the attributes Default=False (\DEF) and Manual=True (\MAN).

It is not possible to operate the GateWay Client process at the same time in the standard remote tags mode and also in "KOM mode of gateway", since in standard mode the process has the suffix GTW and is the parent of remote tags, and in the KOM mode it has the suffix KOM and is the parent of communication objects (lines, stations, I/O tags).

The GateWay Client process can, however, be operated at the same time in the transparent gateway mode and "KOM mode of gateway" configurations.

The KOM mode of gateway is a solution in cases when:

• It is necessary to access the values ​​of the input I/O tags as well as control the output I/O tags from a remote application (or from multiple applications).

• It is necessary to test the control of the output I/O tags from the test or development environment.

• It is necessary to divide one application into two because some communication servers cannot be upgraded to the new version of D2000. In this particular case, these were communication servers with ISA cards KMFB02 (used for L&G Profibus communication) and with the Windows XP operating system. It was not possible to install a newer version of Windows on these servers, so it was not possible to upgrade D2000 (e.g. to version V26). Therefore, the original application was divided into two parts- one part was upgraded and connected to the other via a gateway in KOM mode. The second part of the application contained only the configuration of old communications, the KOM process, and the GateWay Server.

To activate the KOM mode of the gateway, start the GateWay Client with /KOM parameter.

An example of running: The GateWay Client will connect to the target system as REMOTE.KOM process and communicate with the GateWay Server listening on address 172.16.0.22 and port 1000.

gtwcli.exe /KOM /WREMOTE /GTWC172.16.0.22:1000

As in the transparent gateway mode, 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 is achieved 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.

KOM mode of the gateway, similar to the transparent gateway mode, 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 gateway regardless of changes in the names of the objects (provided that they have the same UID), i.e., objects can be renamed.