Skip to main content

Port table

Ports YTCC listens on​

PortServiceListens onKey in Settings › Ports
4222Message bus (NATS)127.0.0.1nats
5000Process manager control port127.0.0.1manager
8090Alarm service, started with a project127.0.0.1alarm
8770Live data server (gateway)all interfaces (0.0.0.0)gateway
8771Project server127.0.0.1projects
8772Project bridge127.0.0.1bridge
8773Web interface127.0.0.1; see Open the interface from other computersui_web
8774AI access (MCP)127.0.0.1mcp

PostgreSQL uses port 5432. It is installed separately and YTCC connects to it.

UDP port 8775 answers the server search of the YTCC desktop application on the local network. It is off by default and is turned on in the settings file of the installation; when on, it answers with the server name, the interface port and the version, never with projects, users or signals.

YTCC checks each of these ports when it starts. If a port is in use, it stops with an error that names the port. The setup program checks them before installing and suggests a free port block when they clash; see Install with the setup program.

Steps​

Changing the ports needs a root sign-in on the home page.

1. Open the port settings​

On the home page, click Settings and, under Server, Ports. The section lists the ports of this installation with their key. The ports of the web interface and the live data server are marked as front-door ports: after you change one, open the interface at the new address. The port of the message bus is marked as needing a restart of the whole YTCC.

Settings, section Ports under Server, with the keys alarm, bridge, gateway, manager, mcp, nats, projects and ui_web, their port numbers and Save.

2. Change a port​

Type the new number in the field of the port. Next to the field, YTCC shows whether the port is free on this computer. Click Save. The section confirms that the port is saved.

Ports section after a port was changed and saved, with the confirmation under the list.

The new port applies when YTCC starts again: restart the YTCC service in Services (see The YTCC service). When you changed the port of the web interface or of the live data server, open the interface at the new address afterwards; the desktop shortcuts keep the port of the installation, so type the new address in the browser. Update firewall rules that depend on the port.

3. Give a project its own ports (optional)​

Click Projects and ports under Server. A project enters the table when it is first started under this installation; until then the section says No projects registered in this version; a project is added when it is first started. The table lists the projects with Autostart and the ports of each project: always alarm, and gateway and nats when a project has them. A project with its own ports runs with its own message bus and gateway; a project with empty fields uses the shared ones of the installation. A port that another YTCC installation also uses is marked with a warning sign. Click Save; project ports apply when the project is started again.

Projects and ports section on a server where no project has been registered yet: No projects registered in this version; a project is added when it is first started.

See Application settings for Autostart.

Ports drivers connect to​

Drivers connect to field devices. These are the default device ports; each device can use its own.

PortProtocol
102Siemens S7 (ISO-on-TCP), IEC 61850 MMS
161 (UDP)SNMP
502Modbus TCP
1883MQTT client
2404IEC 60870-5-104
4840OPC UA client
19999DNP3 over TLS
20000DNP3
44818EtherNet/IP
47808 (UDP)BACnet/IP
48898Beckhoff ADS

IEC 60870-5-101 over TCP has no standard port; each RTU uses its own.

Ports drivers listen on​

Some driver roles accept connections from devices. These ports are opened only when such a driver runs in a project:

PortDriver role
162 (UDP)SNMP trap receiver
1883MQTT broker
4840OPC UA server
20000 / 19999DNP3 in listening mode (TCP / TLS)
47808 (UDP)BACnet/IP local socket