Welcome to ELAM Solutions Helpcenter

All topics /
Categories /
Getting started
/
Network requirements

Network requirements

Published:
April 3, 2024
Updated:
April 3, 2024
From:
Waldemar

Table of Content

ELAM Solutions is designed to have low IT requirements. Basically, if you have access to the Internet, you can also use ELAM Solutions. The rest of this article is much more aimed at people with IT knowledge.

Minimum requirements for latency and bandwidth

ELAM Solutions is cloud-based web application and is only as good as the connection it supports. While developing our application, we kept in mind various aspects of performance, from usability to data transfer speed. In this article we would like to present some minimum requirements for latency and bandwidth to ensure that you have the best experience with ELAM Solutions.

You can check your Latency via this Azure Test URL: https://www.azurespeed.com/Azure/Latency

Note: Please choose "Germany West Central" for tests.

What is latency and bandwidth?

Before we get into the specific requirements, it is important to understand what latency and bandwidth actually are.

Latency

Latency refers to the time delay that occurs when data is transferred from one point to another. It is usually measured in milliseconds (ms). For web applications, low latency is critical for a fast and smooth user experience.

Bandwith

Bandwidth refers to the maximum rate at which data can be transmitted over a network. It is usually measured in megabits per second (Mbps) or gigabits per second (Gbps). The higher the bandwidth, the more data can be transferred in a given time, which in turn enables faster and more efficient use of the application.

Minimum requirements

Latency

For the best user experience, we recommend a latency of 100 ms or less. This provides a responsive user interface and enables real-time interactions that are required for many features of our application.

Bandwith

For bandwidth, we recommend a minimum speed of 25Mbps. If you want to display a particularly large amount of media such as images, PDFs, or videos in ELAM Assistant, we recommend a minimum bandwidth of at least 50Mbps.

Timeouts and WLAN connections: A special relationship

The type and quality of your Internet connection can have a significant impact on the occurrence of timeouts. WLAN connections are particularly susceptible to a number of problems that can cause timeouts.

Signal strength

Weak signal strength can result in an unreliable connection and subsequent timeouts. If you are too far away from the router or if physical barriers such as walls interfere with the signal, data packets may be lost.

Interference

WLAN connections are susceptible to interference from other electronic devices and networks. This interference can disrupt data transmission and cause timeouts.

Network overload

In a overloaded network where many devices send and receive data over the same WLAN, bandwidth can be severely limited. This can lead to requests not being processed in time, which in turn can trigger timeouts.

Changing network environment

Mobile devices that switch from one WLAN network to another or switch back and forth between WLAN and mobile data can also experience timeouts. Such switches can delay or interrupt data transmission.

Use internet connection via WLAN

Important: Please note that the WiFi of the SWA5 clients is only intended for incoming connections and cannot be used to establish an Internet connection. If you need an internet connection, please use a method such as Ethernet (LAN) or an external WiFi dongle.

If you want to use an external WiFi dongle to establish an Internet connection, please note the following information:

  1. Dongle positioning: Place the dongle in a central location and avoid physical barriers to improve signal strength.
  2. Network selection: If possible, use the 5 GHz band instead of the 2.4 GHz band, as it is usually less susceptible to interference.
  3. Quality of Service (QoS) settings: Some devices offer QoS settings to ensure that important data packets receive priority. This can help minimize timeouts in critical applications.
  4. Wired connection: If a constant, reliable connection is required, consider a wired connection, especially for data-intensive tasks during production.

By following these recommendations, you can minimize the likelihood of timeouts due to WLAN-related issues and ensure a better and more stable user experience with our cloud-based web application.

Adequate latency and bandwidth are critical for an optimal user experience when using ELAM Solutions. By ensuring that your network connection meets these minimum requirements, you will be able to take full advantage of the rich features of ELAM Solutions. If you are experiencing connectivity issues, we recommend that you check your network performance and make adjustments as necessary.

Network settings for IoT Tools

This topic assumes that you have purchased a SWA (Smart Work Assistant) device with which you want to use tools in ELAM Solutions. Basically, a SWA is a normal computer with an UbuntuOS. All tools basically communicate via a gateway service with a IoT Hub in the ELAM Solutions Cloud.

Tool communication

Tools are automatically recognized when they are connected to the SWA5 Client WiFi.

To enable tool communication, your IT organization must ensure that the following domains and ports are generally accessible via your company network:

  • Domain - thingsboard-mqtt.elam-solutions.com
  • Port - 1883
  • Port - 8080

Smart Work Assistant updates

Tool controllers are installed on every Smart Work Assistant and are supplied remotely with updates and patches. To enable SWA updates, the following domains must be accessible via port 80 and 443:

  • usn.ubuntu.com
  • changelogs.ubuntu.com
  • landscape.canonical.com
  • archive.ubuntu.com
  • esm.ubuntu.com

Network settings for ELAM Solutions

The access to the ELAM Administration or -Analytics is basically done via your desktop computer. The following domains and ports must be accessible from your network.

  • Domain - elam-solutions.com
  • Port - 80
  • Port - 443

The following figure shows which domains and ports are used when using IoT tools with a Smart Work Assistant (SWA) and ELAM Administration/Analytics with a desktop computer:

Troubleshooting

Tools are not being automatically created in the administration, what can be the problem?

Basically, tools in ELAM-Solutions can be used plug & play. Once the tools connect to the SWA, new tools are automatically created in your ELAM administration.  

If this is not the case, the cause is that the above domains and ports are not enabled:

  • Domain - thingsboard-mqtt.elam-solutions.com
  • Port - 1883
  • Port - 8080

Plug & Play functionality is currently supported for the following tool types:

  • Scanner
  • Bossard SmartTool
  • KBS Pick to Light
  • Kolver K-Ducer

The following tools do not require a SWA device and communicate directly via a central API:

  • Bossard SmartLabels

Read in this article the supported browser.

Firewall issues

In some cases, firewall settings may block access to ELAM Solutions.

Check firewall settings

We recommend contacting your IT department to review the firewall settings in your network. It is important to ensure that there are no rules or blockades preventing network traffic to ELAM Solutions. Make sure that incoming and outgoing connections to the domain and ports of ELAM Solutions are allowed.

Domain- elam-solutions.com

  • Port - 80
  • Port - 443

Test accessibility

Take a moment to test the accessibility of ELAM Solutions from your network. Try accessing ELAM Solutions using different browsers and devices. This will help determine if the issue is limited to specific devices or browsers, or if the connection is being blocked altogether.

Alternative access methods

To determine if the problem is specific to your network, you can try accessing ELAM Solutions using an alternative internet connection. For example, you can use a mobile hotspot or another network. If you find that ELAM Solutions is accessible through this alternative connection, it confirms that the firewall settings in your network are the main issue.