![OPTOGAMA MRO Manual Download Page 12](http://html.mh-extra.com/html/optogama/mro/mro_manual_1644043012.webp)
4.6. Ethernet connection
MRO software has implemented TCP/IP communication. It
is practically plug-and-play usage in the software once
network settings of the MRO device are correctly configured
for TCP/IP communication. The interface and usage of the
software stay the same as for USB or RS-232, only
communication pMROocol is changed.
NOTE:
MRO network settings must be configured using
USB or RS-232 connection before use. This can be done
using commands from Command description
(p. 16) or
using software.
4.6.1. About TCP/IP pMROocol
The device can communicate via RJ45 connector using
“Transmission Control PMROocol/Internet PMROocol”
(TCP/IP) network pMROocol. The TCP/IP pMROocol is
designed such that each computer or device in a network
has the unique IP address and each IP address can open
and communicate over up to 65535 different “ports” for
sending and receiving data to or from any other network
device. The IP address uniquely identifies the computer or
device on the network and a “Port Number” identifies a
specific connection between one computer or device and
another (between two IP addresses). A TCP/IP Port can be
thought of as a private two-way communications line where
the port number is used to identify a unique connection
between two devices. The TCP/IP pMROocol creates a
“virtual IP port” and the network hardware and software are
responsible for routing data in and out of each virtual IP
port.
4.6.2. Client and Server
Connection
TCP/IP connection works in a manner like a telephone call
where someone has to initiate the connection by dialling the
phone. At the other end of the connection, someone has to
be listening for calls and then pick up the line when a call
comes in.
The Client in a TCP/IP connection is the
MRO controller
that “dials the phone” and the
“Server” is
the computer or another device
that is “listening” for
calls to come in. The Client needs to know the IP address of
whatever Server it wants to connect to and it also needs to
know the port number that it wants to send and receive
data through after a connection has been established. The
server only has to listen for connections and either accept
them or reject when they are initiated by a client.
Once a connection through a TCP/IP port has been
established between a TCP/IP Client and a TCP/IP Server,
data can be sent in either direction. The MRO controller will
never send any data through TCP/IP port unless asked by
the TCP/IP Server sending commands (see in command
description Pg. 16). The connection between a Client and a
Server remains open until either the client or the server
terminates the connection.
The above description is basic and describes a general
concept of how TCP/IP communication works. For deeper
understanding at least networking basics must be known.
12