Introduction

There are some different classes and objects that are used to handle the communication.

RemoteConfig

Required to have any remote communication at all. Without this no remotehandler is started.
Place one object in the node-hierarchy.

RemNode

Defines a link of some type to a remote node over a specific protocol.
Several different protocols are supported and there is one specific class for each protocol.
The supported protocols are:

TCP/IP
UDP/IP
RabbitMQ
MQTT
MQ (BEA Message Queue)
ALCM (an old Digital protocol, supported for historical reasons)
Serial
Modbus/RTU Serial
3964R (serial protocol from Siemens)
Webspere MQ

Configuration of each protocol is described further down.
Place RemNode-objects below the RemoteConfig-object.

RemTrans

Generic class that defines a specific message to or from a specific remote node on a
specific protocol. Should be placed below the RemNode-object. The size of a message to be sent
is specified in the RemTrans-object. The data to be sent however resides in a buffer that is
configured as a child to the remtrans-object. When a message is to be sent, data of the length
specified in the remtrans-object is fetched from the buffer. Sometimes however a header of some
length is added to the message.

Buffer

Defining the send- and/or receive data area for each message. Exists in different sizes.
Should be placed below a RemTrans-object. The buffer must be of at least the size of the
message that will be received or sent. If size is not enough message will be cut in the end.

RemTransSend

Function object used in a plc-program for sending messages.

RemTransRcv

Function object used in a plc-program for receiving messages.

Logging of transactions

Remote transactions can be logged to text file. The extent of the logging is configured
in the LoggLevel attribute of the RemTrans object. The log file is configured with a
LoggConfig object.