DIMAX804KC User’s Manual
20
DEXON Systems
4
EXTERNAL PROGRAMMING
There are three different interfaces to control DIMAX device externally: TCP/IP socket interface,
WebSocket interface and RS-232 serial interface. All interfaces use the same XML format
communication protocol.
The software of DIMAX device behaves as a server. The client application’s request messages
are received and processed by the DIVIP server. The requested tasks are performed and reply
messages are sent back to the client by the server.
TCP/IP
The DIMAX device can be controlled through TCP/IP socket interface. The software listens to
the port 6464 and accepts TCP connections of client applications. It receives and processes the
clients’ request messages and performs the requested tasks.
Asynchronous events can be sent by the DIVIP server through the port 6465.
WebSocket
The DIMAX device can be controlled through WebSocket interface. The software listens to the
port 6466 and accepts WebSocket connections of client applications. It receives and processes
the clients’ request messages and performs the requested tasks.
Asynchronous events can be sent by the DIVIP server through the port 6467.
RS-232
The DIMAX device can be controlled through RS-232 interface, too.
The parameters of the serial port initially can be set in the front panel menu or from an external
program through TCP/IP socket interface, e.g.: the control application described in the previous
section.
The default parameters of the RS-232 port:
Baud rate: 9600 bps
Data bits: 8 bits
Parity: no
Stop bits: 1 bit
Flow control: no
The requests and replies have the same format as in case of TCP/IP interface.
Asynchronous events are not sent to the client application through the serial interface.
Note: When the TCP/IP or WebSocket socket is closed the authenticated connection is
terminated, therefore you have to keep the socket interface open while you would like to control
the Device. If the authentication is terminated you will get this error message: Client is not
authenticated! The serial port does not require the authenticated connection.
4.1
Message Format
The request, reply and event messages have common XML based formats. There are different
types of messages in terms of complexity:
Message without any parameter:
<msg_name />, e.g: <query_device_info />
To Next Page
Loading...