Skip to content

Basic Guide to Communication Port Security v2.0

1. Communication Ports Overview

The following network communication is provided in Rainbow Robotics' Robot-Control Box.

  1. Networks for robot control and data collection, etc.
    • Robot Control: Port number 5000
    • Robot Data/Status Acquisition: Port number 5001
  2. Network for industrial communication and general data transmission and reception
    • Modbus TCP: Port number 502
    • Misubishi MC Comm.: User defined port number
    • LS Elec. XGT Comm.: Port number 2004
    • OMRON FINS Comm.: User defined port number
    • SIEMENS S7 Comm.: Port number 102
    • HMI MemLink Comm.: User defined port number
    • General TCP/IP Comm.: User defined port number

As mentioned above, ports 5000 and 5001 are always open, and the rest of the data network ports are available only when the user explicitly configures/programs them.

2. Communication Security

In Chapter 1, the ports required for security are ports 5000 and 5001.
This is because the rest of the data ports are used only if the user has to explicitly use that function.

Since ports 5000 and 5001 are always open ports, user can configure network security in the following two ways.

2.1 Block ports 5000/5001 from router/hub level to robot system

  • This is the simplest and surest way.
  • This is a method of blocking ports at the router level that relays the internal network and external network of the automation system. (Block port forwarding)
  • This is a method that blocks the 5000/5001 ports coming from the outside.

missing

2.2 Block access through software key/grammar

  • Even if the port is not blocked in the same way as in 1) above, a prescribed key and grammar are required to receive control/data through the 5000/5001 port.
  • Through this, if an unauthorized key or unspecified grammar is accessed from the outside, the robot stops working and the communication does not affect the system.

3. Others

The table below shows the usage categories of functions/networks for sending/receiving data.

ManufacturerCommunicationFeature
SIEMENSS7 ProtocolServer = PLC, Client = Robot
Modbus TCP MasterClient(Master) = Robot, Server(Slave) = PLC
Modbus TCP SlaveClient(Master) = PLC, Server(Slave) = Robot
RS232/485General Serial communication
TCP/IPGeneral TCP/IP communication
OMRONFINSServer = PLC, Client = Robot
Modbus TCP MasterClient(Master) = Robot, Server(Slave) = PLC
Modbus TCP SlaveClient(Master) = PLC, Server(Slave) = Robot
RS232/485General Serial communication
TCP/IPGeneral TCP/IP communication
MITSUBISHIMC Protocol 1E-BinaryServer = PLC, Client = Robot
MC Protocol 3E-BinaryServer = PLC, Client = Robot
Modbus TCP MasterClient(Master) = Robot, Server(Slave) = PLC
Modbus TCP SlaveClient(Master) = PLC, Server(Slave) = Robot
RS232/485General Serial communication
TCP/IPGeneral TCP/IP communication
LS ELEC.XGT ProtocolServer = PLC, Client = Robot
Modbus TCP MasterClient(Master) = Robot, Server(Slave) = PLC
Modbus TCP SlaveClient(Master) = PLC, Server(Slave) = Robot
RS232/485General Serial communication
TCP/IPGeneral TCP/IP communication
PROFACEMemory LinkServer = HMI, Client = Robot
M2I-TOPMemory LinkServer = HMI, Client = Robot