LED Status & troubleshooting

The x500 IoT gateway has two LEDs located right above the LAN ports. These show the current status of the x500 IoT gateway’s connection. The upper LED indicator  displays the signal status, only applicable for Wi-Fi variants, and the lower LED indicator (RDY) shows the activity status. This article explains what all the various statuses mean, while also suggesting troubleshooting actions.

Important note

Once the x500 IoT gateway is connected and powered on, please wait 2 minutes while the x500 IoT gateway goes through its steps to connect to the X4 remote, indicating different statuses each step. The final status is, logically, indicated after these 2 minutes.

Signal LED

The signal LED displays the signal status, only applicable for Wi-Fi variants. Below you will find the descriptions and troubleshooting suggestions for each of the signal LED statuses.

This means the cellular module is being initialized. Please wait for the x500 IoT gateway to finish. You will see a different LED status shortly.

Blinking red 1 pulse

This means the x500 IoT gateway is unable to connect to the network. Only applicable for Wi-Fi variants.

The most common causes for the x500 IoT gateway Wi-Fi variant are:

  1. The specified Wi-Fi network is unavailable or the entered password is incorrect. You can easily test this by connecting to the network with your laptop or smartphone.

Case sensitive SSID

Bear in mind that the SSID you entered in the Lenze configuration file is case sensitive. This means that “WiFiGuestNetwork” is not the same as “wifiguestnetwork“.

  1. There is no reception. The Wi-Fi modem may be out of reach or it’s signal may be blocked (i.e. by the machine’s control box). We have an antenna available to bypass the signal blocker by placing the antenna outside the signal blocker using a screw mount antenna. Other options are a relocation of the x500 IoT gateway/Wi-Fi hotspot or the installment of a Wi-Fi amplifier.

Constant red

This means the x500 IoT gateway is connected, but has poor reception. This may not be an issue, but can result in slower data transmission or occasional disconnects. Read the “no reception” part at the “blinking red 1 pulse”-status for ways to improve reception.

Constant purple

This means the x500 IoT gateway is connected, and has medium reception. This may not be an issue, but you can read the “no reception” part at the “blinking red 1 pulse”-status for ways to improve reception.

Constant blue

This means the x500 IoT gateway is connected, and has good reception.

Activity LED

The activity LED (RDY) displays the activity status. Below you will find the descriptions and troubleshooting suggestions for each of the activity LED statuses.

(RDY) Constant red

This means the x500 IoT gateway is booting or not registered. If you’ve already registered the x500 IoT gateway, please wait a minute for the x500 IoT gateway to finish booting. You will see a different LED status shortly. If you’ve not yet registered the x500 IoT gateway, you can view our getting started-section for more information.

(RDY) Blinking red 1 pulse

This means the x500 IoT gateway is waiting for internet access. First you can test if there is an internet connection by connecting to the network using a laptop or mobile device, preferably using the very same Ethernet cable (in case of a wired connection). The most common causes are:

  1. The network may require confirmation or login via a webportal before you’re actually given internet access, which the x500 IoT gateway is unable to do. You can easily test this by connecting your smartphone or laptop to the same network. Guest and public networks are often equipped with this confirmation/login layer. If this is the case, connect to a different network without confirmation/login layer.
  2. The local IT department may choose to only allow internet access to specific devices, based on i.e. the MAC address or IP address. Contact your IT department and provide them our connectivity requirements, explaining how the x500 IoT gateway sets up its connection.
  3. If you are connected to a proxy server for your internet connection, then you’ll have to configure the x500 IoT gateway to connect via that proxy server as well. The local IT department will know if this is the case and can provide you with the necessary information. View our “connected via a proxy server” article on how to easily configure your x500 IoT gateway accordingly.

(RDY) Blinking red 3 pulses

Corporate 10.3.x.x subnet

The x500 IoT gateway’s VPN connection uses subnet 10.3.x.x. It is therefore incompatible with corporate networks that use this same subnet.

This means there is a LAN/WAN conflict, which means the x500 IoT gateway knows no noticeable difference between the corporate network (WAN) and the machine network (LAN). The router cannot reliably access the internet because of this.

This is commonly resolved by changing the LAN side subnet. The subnet of the default LAN side IP address (192.168.140.1) is the “192.168.140” part. You can change this on the x500 IoT gateway’s [Config] tab, if it’s online, or by creating a new configuration file.

Detailed explanation

Here you’ll find all possible LAN/WAN conflict situations. We’ll be using “192.168.140” as example, but the logic in the table below can be applied to any subnet.

WANLANDescription
192.168.140.x (255.255.255.0)192.168.140.x (255.255.255.0)LAN=WAN This is the most common LAN/WAN conflict. The “192.168.140” of both networks conflict with one another. A router cannot distinguish between the LAN and WAN network.
192.168.x.x (255.255.0.0)192.168.140.x (255.255.255.0)WAN>LAN The LAN’s “192.168.140” is considered a part of the WAN network (192.168.0.1 – 192.168.255.254). A router cannot distinguish whether “192.168.140.x” is a part of the LAN network, or the WAN network.
192.168.140.x (255.255.255.0)192.168.x.x (255.255.0.0)LAN>WAN Similar to the previous one, but now the other way around. WAN is considered a part of the LAN network. A router cannot distinguish whether “192.168.140.x” is a part of the LAN network, or the WAN network.

(RDY) Blinking red 4 pulses

This means the router was removed from X4 remote, and you’ll have to register it again via USB flash drive:

  • Don’t restart the x500 IoT gateway, leave it turned on.
  • Insert a USB flash drive with configuration file (details).

USB already inserted?

If a USB flash drive with configuration file is already in the x500 IoT gateway, simply reinsert the flash drive: take out the USB flash drive and insert it again.

(RDY) Blinking red 5 pulses

This means the router was previously registered at your company on X4 remote. You’ll have to remove the old registration first and then register it again via USB flash drive.

  • Don’t restart the x500 IoT gateway, leave it turned on.
  • Remove the old registration from the X4 remote platform.
  • Insert a USB flash drive with configuration file (details).

USB already inserted?

If a USB flash drive with configuration file is already in the x500 IoT gateway, simply reinsert the flash drive: take out the USB flash drive and insert it again.

(RDY) Blinking blue 1 pulse

This means the x500 IoT gateway is connecting to X4 remote. You will see a different LED status shortly.

(RDY) Blinking blue 2 pulses

This means the x500 IoT gateway is setting up a VPN connection. The x500 IoT gateway may be prevented/blocked from setting up a VPN connection if this takes longer than 2 minutes. The most common causes are:

  • The company network has an OpenVPN filter active in their firewall. The local IT department will know if this is the case. You can provide them our connectivity requirements if they have questions about how the x500 IoT gateway sets up its connection.
  • Your x500 IoT gateway is located in a censored network. Some countries have banned or restricted VPN usage. Turning on the “stealth mode“-feature on X4 remote will legally bypass this and enable the x500 IoT gateway to set up its VPN connection.

Applicable countries

Stealth mode may be required in various countries as they have banned or restricted VPN usage. These include, but are not limited to: China, Russia, Iran, United Arab Emirates, Oman, Turkey, Iraq, Turkmenistan, Belarus, North Korea, and Uganda. (source)

(RDY) Constant blue

This means the x500 IoT gateway has an active VPN connection to X4 remote. The device is online on X4 remote.