DAEnetIP3
User Manual
-
65
-
17.1.
TCP/IP socket based protocol
DAEnetIP3 controller has possibility for access via TCP/IP protocol. The user may
connect with custom software to port that is defined for socket based TCP/IP
communication. This port is called
User Socket Port
.
The communication message format (ADU - application data units) over TCP/IP
socket is shown on figure 56. It is added serial address to the command, answer and
error messages. The idea is that in this way the user can access over TCP/IP
protocol not only the server DAEnetIP3 module, but all the modules connected over
the serial network to this DAEnetIP3 controller. These controllers are distinguished
by the Address field (2 bytes), which is actually the serial address.
The idea is shown on figure 57. The user connects to DAEnetIP3 with serial
address 00, but he can communicate with DAEnetIP3 [serial address = 01] and
DAEnetIP3 [serial address 02]. DAEnetIP3 [serial address=00] is actually bridge
between TCP/IP network and serial network. When data comes in to DAEnetIP3
[serial address 00] to
User Socket Port,
it checks if the address is 00. If yes it
decodes the command and executes it or returns error code. In both case it resends
the TCP/IP packet data to the serial network. If the address (in this example) is 01 or
02, then DAEnetIP3 [serial address 00] just pass the TCP/IP packet data through the
serial network and DAEnetIP3 [serial address 01 or 02] decodes the command
executes it and returns answer or error again over the serial network. After that
DAEnetIP3 [serial address 00] takes this serial data and sends it over the TCP/IP
network.
In this way the user is able to access many serially connected DAEnetIP3
controllers over the WAN/LAN/WLAN only via one IP address with the denkovi
protocol.
The serial address FF is reserved and all DAEnetIP3 controllers accept
commands with this address but sends respond with its own address.
Figure 56.
TCP/IP socket based application protocol