Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Aggregator 1.4+

The Aggregator does not need any additional configuration, as it does not use any additional ports for internal communication.

Aggregator 1.0 - 1.3

This step does not refer to the configuration of machine ports, but to the configuration of internal port(s) used by the aggregator. Perform only if you need to prevent the aggregator from using specific internal ports.

The Aggregator will have to run one opc-ua server per connected machine (except for UMATI machines). The servers need to be accessible locally only. No port or firewall setup should be needed on the Aggregator machine. If not differently specified, the Aggregator will automatically assign ports to servers starting from port 4840. If these ports are already in use then the Aggregator will attempt to find the next best free port. You can also manually specify which ports you want to use following the next example:

  "machines": [
  ...
  # The umati server will run on port 5555
    {
      "url": "url",
      "umati_server_port": 5555,
      "unique_name": "unique_name",
      "type": "ULTIMAKER",
      "mes_id": [ 10 ]
    },
  ...
    # The umati server port will be auto-assigned when umati_server_port is set to 0
    {
      "url": "url",
      "umati_server_port": 0,
      "unique_name": "unique_name",
      "type": "ULTIMAKER",
      "mes_id": [ 10 ]
    },
  ...
    # The umati server port will be auto-assigned when umati_server_port attribute is omitted
    {
      "url": "url",
      "unique_name": "unique_name",
      "type": "ULTIMAKER",
      "mes_id": [ 10 ]
    },
  ...
  ],
  • No labels