Network | MidTeQ EMS Documentation

App Certificates

Configuration from A to Z

Control response time

Customer Specific

EMS Installation Network Quick Start Safety, maintenance and legal notices Specifications Status LEDs

Troubleshooting

Wiring & connectivity guidelines

Advanced network settings

Data usage

Tip

Tip

See for more information about the data usage of the MidTeQ PULSE EMS.

For troubleshooting high data usage, see also

Wiring

See for wiring the Ethernet network.

Security policy

Security policy: Download the PDF.

Firewall

Network ports for outbound connections

Tip

Tip

Most home and small business networks allow all outbound connections by default. You do not have to do anything in this case.

The MidTeQ PULSE EMS requires that outbound connections in the network firewall are allowed on the following ports:

Installation

Previous Page

Quick Start

Next Page

On this page

Advanced network settings Data usage Wiring Security policy Firewall Network ports for outbound connections Network ports for inbound connections Fixed IP addresses VLAN

TCP port 80 & 443: General Internet connection port. Without this port, the MidTeQ PULSE EMS cannot function. Some monitored & controlled devices use port 80 locally for communication, but this port is not generally used for internet communication.
TCP port 1194: Remote service connection port for updates, diagnostic services and remote support. The MidTeQ PULSE EMS can function without this port, but may not receive updates, and remote support is not possible. It is recommended to enable this port. You can change this port in the MidTeQ PULSE EMS configuration to port 1192 or any port in the range 35000 to 40000 if needed.
TCP port 1883 and 8883: Used for MQTT; required in case the MidTeQ PULSE EMS must be able to receive live control signals (e.g. when coupled to the imbalance / FCR energy markets!)
UDP port 123: NTP Port (Clock). Without this port, the MidTeQ PULSE EMS cannot update its internal clock. This is important for proper communication.

Network ports for inbound connections

The MidTeQ PULSE EMS does not require opening any network ports for inbound connections.

Warning

Warning

It is strongly discouraged and NOT necessary to configure your firewall to port forward or allow incoming TCP and UDP connections on the listed ports above! This is a serious security risk.

Domain whitelist

To avoid connectivity issues after future updates, it is recommended to whitelist all the eniris.be and eniris.io domains with a wildcard:

*.eniris.be
*.eniris.io
a2j3w1vc0ecyne-ats.iot.us-east-1.amazonaws.com (Only when using Yuso)

At least the following MidTeQ PULSE domains are used at present by the MidTeQ PULSE EMS:

api.eniris.be - (telemetry & energy measurements) - TCP port 443:
authentication.eniris.be - (authentication) - TCP port 443
public-health.eniris.be - (device health monitoring system) - TCP port 443
mender.eniris.be - (device update system) - TCP port 443
public-mender.eniris.be - (device update system) - TCP port 443
mqtt.eniris.be - (MQTT) - TCP ports 1883 & 8883
neoregistry.eniris.be - (device update system) - TCP port 443
neodata-ingress.eniris.be - (data ingress api) - TCP port 443
vpn.eniris.be - (remote support) - TCP & UDP ports 1192-1194 and 35000-40000
ntp.eniris.be - (clock synchronization) - UDP port 123

Fixed IP addresses

The MidTeQ PULSE EMS is by default configured to use DHCP. You can change this to a fixed IP address in the 'Settings' tab of the commissioning interface.

Tip

Tip

Only configure a fixed IP address in the MidTeQ PULSE EMS if you have no other choice. It is recommended to always use DHCP, and configure your router to always assign the same IP address to the MidTeQ PULSE EMS instead!

Warning

Warning

Write down the IP address you configure. You will need this if the MidTeQ PULSE EMS would become inaccessible after changing the IP address!

Note

Note

Lost access to the commissioning interface If you lose access to the commissioning interface after setting a fixed IP address, then check out the troubleshooting section.

VLAN

Tip

Tip

As an optional security measure, the MidTeQ PULSE EMS can be placed within a dedicated VLAN. When implementing this configuration, ensure that all devices requiring communication with the controller are assigned to the same VLAN.

Troubleshooting - Data usage

wiring & connectivity guidelines