RAK7437/RAK7437C LoRaWAN Configuration

This guide explains how to configure the LoRa parameters of your WisGate gateway to connect various types of LoRaWAN networks. Depending on your deployment scenario, the gateway can operate in one of the following modes:

Built-in Network Server

In this mode, the gateway functions as a LoRa Network Server (LNS), managing devices and processing packets locally. It also supports multi-gateway deployments by allowing extender gateways to join and be managed from the central gateway. This setup enables fully independent operation without external dependencies.

Packet Forwarder

The gateway forwards LoRa packets to an external network server, which handles all processing, device management, and application integration. This mode is ideal for integrating with public or private LoRaWAN infrastructures such as TTN or ChirpStack.

Basics Station

The gateway communicates with a remote LoRaWAN network server over a secure WebSocket (WSS) connection. This mode supports cloud-based deployments with enhanced security, certificate-based authentication, and dynamic server provisioning (via CUPS).

Built-In Network Server

This section explains how to configure your WisGate gateway to operate in Built-in Network Server (LNS) mode, enabling local LoRaWAN packet processing and device management.

Set the Gateway Work Mode

Navigate to LoRa® > Configuration. For Work mode, select Built-in network server.

Figure 1: Set the gateway work mode

Select Your Country & Region

Select your country and frequency band to ensure compliance with local regulations and to facilitate proper LoRa® operation.

Figure 1: Configure frequency band

For a detailed explanation of configuration parameters, refer to the WisGateOS 2 User Manual > Select Your Country & Regin section.

Create an Application

Create an application to logically group LoRaWAN devices for easier management and data routing.

For detailed instructions on how to create and manage applications, refer to the WisGateOS 2 User Manual > Create an Application.

Add End Devices

Add LoRaWAN end devices to your application to enable them to join the network and start transmitting data.

For detailed instructions on how to add and manage end devices, refer to the WisGateOS 2 User Manual > Add Devices.

Advanced Features (Optional)

Once the basic configuration is complete, you can leverage the additional features offered by the built-in network server to enhance device management, extend coverage, or integrate with external platforms.

The optional features described below are useful for scaling and customizing your deployment.

Country Code Setting

Ensures the gateway complies with regional frequency regulations. Selecting the correct country automatically sets the transmit power and sub-bands.

Guide Link: How to Configure Country Code on RAK LoRaWAN Gateways for Rf Compliance

Packet Filter

Filters uplinks by applying whitelist rules, ensuring that only authorized devices are allowed access, while blocking unknown devices to prevent network disruption.

Guide Link: Configure Packet Filter on RAK LoRa® Gateways

Gateway Backend

Facilitates communication between a central gateway and extender gateways using the MQTT protocol, while also supporting multi-gateway deployments.

Guide Link: How to Configure a RAK Multi-Gateway LoRaWAN® Network Using Gateway Backend (Built-in Network Server Mode)

AWS IoT Core Integration

Securely connects the gateway to AWS IoT Core using the endpoint URL and certificates, making it ideal for integrating with AWS cloud services.

Guide Link: How to Implement AWS Integration for WisGate Edge V2

Generic MQTT Integration

Forwards decoded uplinks to MQTT brokers, allowing integration with platforms such as ThingsBoard.

Guide Link: Configure Generic MQTT Integration With Built-in Network Server

Auto Add Devices

Automatically adds end devices to the LNS when they send join requests, which reduces the need for manual setup.

Guide Link: How to Use Auto Add Device on RAK LoRaWAN® Gateways

Batch Add Devices

Enables bulk registration of end devices through CSV upload or auto-generation, making it ideal for large-scale deployments.

Guide Link: How to Batch Add Devices to a RAK LoRaWAN® Gateway

Packet Forwarder

In this mode, the gateway forwards LoRaWAN packets to an external network server. All packet processing, device management, and data routing are managed by the external server.

Supported Network Servers

Depending on the protocol type you choose, the gateway supports the following external network servers. Each listed server includes a link to its corresponding configuration guide.

Semtech UDP GWMP Protocol

• The Things Network (TTN)
  

  Configuration Guide: How to Connect RAK Gateways to TTN v3 via UDP

• ChirpStack v3
  

  Configuration Guide: How to Connect RAK Gateways to ChirpStack v3 via UDP

• ChirpStack v4
  

• Confiuration Guide: How to Connect RAK Gateways to ChirpStack v4 via UDP

• Loriot
  

  Configuration Guide: How to Connect RAK Gateways to LORIOT via UDP

LoRa® Gateway MQTT Bridge

• MQTT for Built-in LNS
  

  Used in multi-gateway deployments to connect extender gateways to the central gateway, which runs the Built-in Network Server via MQTT.
  Configuration Guide: How to Configure a RAK Multi-Gateway LoRaWAN® Network Using Gateway Backend (Built-in Network Server Mode)

• ChirpStack v3
  

  Configuration Guide:

  • How to Connect RAK Gateways to Chirpstack v3 via MQTT (JSON)
  • How to Connect RAK Gateways to Chirpstack v3 via MQTT (Protobuf) 

• ChirpStack v4
  

  Configuration Guide: How to Connect RAK Gateways to ChirpStack v4 via MQTT

Advanced Settings (Optional)

In Packet Forwarder mode, RAK gateways provide additional features that enhance flexibility and address specific deployment requirements.

The features described below are optional, but they can be utilized to improve compatibility, optimize network performance, or fulfill specific deployment needs.

Country Code Setting

Ensures that the gateway complies with regional frequency regulations. Selecting the correct country automatically sets the transmit power and sub-bands.

Guide Link: How to Configure Country Code on RAK LoRaWAN Gateways for Rf Compliance

Set Private Channel

Use this feature to define custom sub-bands or frequency channel sets that align with your external server’s configuration. This reduces interference and facilitates deployment in specialized scenarios.

Guide Link: How to Configure Private LoRaWAN® Channels on RAK Gateways

Auto Data Recovery

Enables temporary local buffering of uplinks during connection loss to the external server. Once reconnected, the gateway can resend the cached data to prevent loss.

Guide Link: How to Enable Auto Data Recovery for Packet Forwarder Mode

Secondary LNS Forwarding

Enables a RAK gateway in Packet Forwarder mode to forward uplink packets to two LoRaWAN Network Servers simultaneously: one serves as the Primary LNS for device control, while the other functions as the Secondary LNS for uplink monitoring or redundancy.

Guide Link: Secondary LNS Forwarding: Forward Packets to a Secondary Network Server

Fake GPS

If your gateway lacks a built-in GPS module or has poor GPS signal reception, you can manually input static GPS coordinates. This feature is useful for mapping and network diagnostics.

Guide Link: How to Set Up Fake GPS for Virtual Gateway Location

Packet Filter

Filters uplinks by applying whitelist rules, ensuring that only authorized devices are allowed access while blocking unknown devices to prevent network disruption.

Guide Link: Configure Packet Filter on RAK LoRa® Gateways

Auto Connect to The Things Network (EU1) Server

Automatically connects to The Things Network (EU1) when using Semtech UDP forwarding, speeding up deployment for TTN users.

Guide Link: How to Auto-Connect RAK Gateway to TTN (EU1) in Packet Forwarder Mode

Basics Station

In Basics Station mode, the gateway supports connections to various types of servers. Depending on your deployment platform, you can configure the gateway to connect using one of the following server types: LNS, CUPS, or CUPS-BOOT.

Supported Network Servers

The following server types are supported in Basics Station mode:

LNS Server

Direct WebSocket-based data forwarding.

• AWS IoT Core
  

  Configuration Guide: How to Connect RAK Gateways to AWS IoT Core Using Basics Station (LNS)

• The Things Network (TTN)
  

  Configuration Guide: How to Connect RAK Gateways to TTN v3 Using Basics™ Station (LNS)

• ChirpStack v3
  

  Configuration Guide: How to Connect RAK Gateways to ChirpStack v3 Using Basics™ Station (LNS)

• ChirpStack v4
  

  Configuration Guide: How to Connect RAK Gateways to ChirpStack v4 Using Basics™ Station (LNS)

CUPS Server

Enables remote gateway configuration and credential management.

• AWS IoT Core
  

  Configuration Guide: How to Connect RAK Gateways to AWS IoT Core Using Basics Station (CUPS)

• The Things Network (TTN)
  

  Configuration Guide: How to Connect RAK Gateways to TTN v3 Using Basics™ Station (CUPS)

• Actility
  

  Configuration Guide: How to Connect RAK Gateways to Actility ThingPark Using Basics™ Station (CUPS)

CUPS-BOOT Server

This is used for initial provisioning before CUPS takes over and is generally not needed during normal operation.

Advanced Settings (Optional)

In Basics Station mode, RAK gateways provide several optional features that enhance deployment flexibility.

The features described below are optional and can be enabled to improve network security, enhance compatibility, and offer greater flexibility for specific deployment needs.

16 Channel

Enables full 16-channel support for LoRaWAN uplinks in Basic Station mode. This feature is useful for custom frequency plans and ensures compatibility with network servers that require extended channel configurations.

Guide Link: 16-Channel Support in Basics Station Mode

Packet Filter

Filters uplinks by applying whitelist rules, ensuring that only authorized devices are allowed access while blocking unknown devices to prevent network disruption.

Guide Link: Configure Packet Filter on RAK LoRa® Gateways