Field Test Data Processor

The Field Test Data Processor Extension is a gateway-side application for local LoRaWAN field test data processing. Installed on a RAK WisGateOS 2 gateway, it connects to the LoRaWAN Network Server (LNS) through MQTT, receives uplink metadata from Field Tester devices, and calculates key link-quality metrics such as RSSI, SNR, and packet-loss rate.

The processed results can be sent back to supported Field Tester devices through downlink feedback and can also be used on the gateway for real-time heatmap visualization, network-parameter review, and CSV data export.

The extension supports the Built-in LNS on RAK gateways, as well as third-party LNS platforms such as ChirpStack v3 / v4, TTN, TTI, and AWS IoT Core. It can also support multiple Field Tester devices in the same deployment, enabling centralized gateway-side processing and analysis across different test points.

For Field Tester devices with an on-device reporting interface, part of the processed results may also be displayed directly on the device. In all cases, the extension acts as the gateway-side data processing component for local signal-quality analysis without relying on external cloud services.

NOTE

This extension is compatible with WisGateOS 2 v2.2.x and later.

Field Test Data Processor Extension Parameter Definitions

Name	Description
Device EUI	The unique identifier of the Field Tester Plus device currently being analyzed.
RSSI Chart	Received Signal Strength Indicator. Shows the signal strength of uplink packets received by the gateway. Measured in dBm. Closer to 0 = stronger signal.
SNR Chart	Signal-to-Noise Ratio. Indicates how much stronger the signal is compared to background noise. Higher values represent better communication quality.
DateRate	The LoRaWAN Data Rate (DR) used for the uplink. Lower DR values offer longer range but lower data throughput.
Region	Frequency band used by the Field Tester Plus (e.g., EU868, US915). Must match the configuration of the connected gateway.
Loss Rate	Uplink packet loss rate, calculated based on gaps in frame counters. Ideally should be 0%.
Last Time	Timestamp of the last successfully processed uplink. Useful for checking if the device is still active.
Label	A user-defined location tag for the current test point (e.g., 3F-Elevator). This label will appear in exported CSV reports.
No. of Gateway	Number of gateways that received the latest uplink.
Gateway EUI	The unique identifier of the gateway that received the latest uplink (typically the nearest or strongest gateway).
Distance	Estimated distance (in meters) between the device and the gateway. Requires GPS on the device.

Install the Field Test Data Processor Extension

To install this extension, follow Add an Extension.

Configure the Field Test Data Processor Extension

Configure the Field Test Data Processor Extension based on the LoRaWAN Network Server currently connected to your gateway. The extension communicates with the selected LNS through MQTT, so you need to follow the corresponding configuration steps for your network server type.

Built-in Network Server

1. To access the Field Test Data Processor extension, click Launch.

Figure 1: Launch the Field Test Data Processor extension

2. Click the Configuration tab to set the following parameters.

Figure 1: Set parameters

• LoRa Network Server: Select the LoRaWAN Network Server where the Field Tester device is registered. In this example, select Built-in Server.

• MQTT Integration:

  • MQTT Broker Address: Set to localhost for the built-in server.

  • Port: Use the default port 1883.

  • Enable User Authentication: Leave as default (no authentication required).

  • Enable TLS Setting: Leave as default.

  • Uplink Topic:

    application/{appName}/device/{devEui}/rx

  • Downlink Topic:

    application/{appName}/device/{devEui}/tx

  NOTE

  • {appName} and {devEui} are topic placeholders. Keep them unchanged if you want the extension to process all Field Tester devices under the configured application.
  • You may replace them with a specific application name or device EUI only when you want to limit processing to a particular application or device. In that case, messages from other applications or devices will not be received or processed by the extension.

3. To save the changes, click Save changes.
4. After the Field Tester successfully joins the network and starts sending uplink data, click the Device Overview tab to view the real-time heatmap and network performance data processed by the Field Test Data Processor Extension.

Figure 1: Device Overview

NOTE

The heatmap is available only when the Field Test Data Processor Extension is correctly connected to the LNS through MQTT and has received valid uplink data from the Field Tester. If no heatmap or performance data appears, verify the device join status, uplink transmission, and MQTT configuration.

5. Click Show Data to view a detailed breakdown of all data points collected by the Field Tester. For complete definitions of all parameters shown in this table, refer to the Field Test Data Processor Extension – Parameter Definitions section.

Figure 1: Detailed data

6. (Optional) Click Export to generate a CSV report of the labeled field test data. Export the CSV report when you need to compare signal quality across different test locations, perform further offline analysis, share test results with the project team, or keep the data as part of the project acceptance record.

   NOTE

   Only data points that have been labeled on the device are included in the exported CSV report.

Chirpstack v3

1. To access the Field Test Data Processor extension, click Launch.

Figure 1: Launch the Field Test Data Processor extension

2. Click the Configuration tab to set the following parameters.

Figure 1: Set parameters

• LoRa Network Server: Select ChirpStack v3.

• MQTT Integration:

  • MQTT Broker Address: Enter the IP address or domain of your ChirpStack MQTT broker.

  • Port: Use the default MQTT port 1883.

  • Enable User Authentication: Leave as default (no authentication required).

  • Enable TLS Setting: Leave as default.

  • Uplink Topic:

    application/{applicationId}/device/{devEui}/event/up

  • Downlink Topic:

    application/{applicationId}/device/{devEui}/command/down

  NOTE

  • {applicationId} and {devEui} are topic placeholders. Keep them unchanged if you want the extension to process all Field Tester devices under the configured application.
  • You may replace them with a specific application ID or device EUI only when you want to limit processing to a particular application or device. In that case, messages from other applications or devices will not be received or processed by the extension.

3. To save the changes, click Save changes.
4. After the Field Tester successfully joins the network and starts sending uplink data, click the Device Overview tab to view the real-time heatmap and network performance data processed by the Field Test Data Processor Extension.

Figure 1: Device Overview

NOTE

The heatmap is available only when the Field Test Data Processor Extension is correctly connected to the LNS through MQTT and has received valid uplink data from the Field Tester. If no heatmap or performance data appears, verify the device join status, uplink transmission, and MQTT configuration.

5. Click Show Data to view a detailed breakdown of all data points collected by the Field Tester. For complete definitions of all parameters shown in this table, refer to the Field Test Data Processor Extension – Parameter Definitions section.

Figure 1: Detailed data

6. (Optional) Click Export to generate a CSV report of the labeled field test data. Export the CSV report when you need to compare signal quality across different test locations, perform further offline analysis, share test results with the project team, or keep the data as part of the project acceptance record.

   NOTE

   Only data points that have been labeled on the device are included in the exported CSV report.

Chirpstack v4

1. To access the Field Test Data Processor extension, click Launch.

Figure 1: Launch the Field Test Data Processor extension

2. Click the Configuration tab to set the following parameters.

Figure 1: Set parameters

• LoRa Network Server: Select ChirpStack v4.

• MQTT Integration:

  • MQTT Broker Address: Enter the IP address or domain of your ChirpStack MQTT broker.

  • Port: Use the default MQTT port 1883.

  • Enable User Authentication: Leave as default (no authentication required).

  • Enable TLS Setting: Leave as default.

  • Uplink Topic:

    application/{applicationId}/device/{devEui}/event/up

  • Downlink Topic:

    application/{applicationId}/device/{devEui}/command/down

  NOTE

  • {applicationId} and {devEui} are topic placeholders. Keep them unchanged if you want the extension to process all Field Tester devices under the configured application.
  • You may replace them with a specific application ID or device EUI only when you want to limit processing to a particular application or device. In that case, messages from other applications or devices will not be received or processed by the extension.

3. To save the changes, click Save changes.
4. After the Field Tester successfully joins the network and starts sending uplink data, click the Device Overview tab to view the real-time heatmap and network performance data processed by the Field Test Data Processor Extension.

Figure 1: Device Overview

NOTE

The heatmap is available only when the Field Test Data Processor Extension is correctly connected to the LNS through MQTT and has received valid uplink data from the Field Tester. If no heatmap or performance data appears, verify the device join status, uplink transmission, and MQTT configuration.

5. Click Show Data to view a detailed breakdown of all data points collected by the Field Tester. For complete definitions of all parameters shown in this table, refer to the Field Test Data Processor Extension – Parameter Definitions section.

Figure 1: Detailed data

6. (Optional) Click Export to generate a CSV report of the labeled field test data. Export the CSV report when you need to compare signal quality across different test locations, perform further offline analysis, share test results with the project team, or keep the data as part of the project acceptance record.

   NOTE

   Only data points that have been labeled on the device are included in the exported CSV report.

The Things Network

1. To access the Field Test Data Processor extension, click Launch.

Figure 1: Launch the Field Test Data Processor extension

2. Click the Configuration tab to set the following parameters.

Figure 1: Set parameters

On TTN, you can view your application's MQTT credentials under: Applications > your application > Other integrations > MQTT.

Figure 1: MQTT integration credentials

• LoRa Network Server: Select the LoRaWAN server where your Field Tester device is registered. In this case, choose The Things Network.

• MQTT Integration:

  • MQTT Broker Address: The public address for the MQTT broker is eu1.cloud.thethings.network.

  • Port: Use the default MQTT port: 1883

  • Enable User Authentication: This option must be enabled.

    • Username: Copy the Username from the MQTT Connection credentials section in the TTN console.
    • Password: Use the API key generated by clicking Generate new API key in the TTN console.

  • Enable TLS Setting: Leave this at its default value.

  • Uplink Topic: Uplink topic template:

    application/{applicationId}/device/{devEui}/event/up

  • Downlink Topic: Downlink topic template:

    application/{applicationId}/device/{devEui}/command/up

  NOTE

  • {applicationId} and {devEui} are topic placeholders. Keep them unchanged if you want the extension to process all Field Tester devices under the configured application.
  • You may replace them with a specific application ID or device EUI only when you want to limit processing to a particular application or device. In that case, messages from other applications or devices will not be received or processed by the extension.

3. To save the changes, click Save changes.
4. After the Field Tester successfully joins the network and starts sending uplink data, click the Device Overview tab to view the real-time heatmap and network performance data processed by the Field Test Data Processor Extension.

Figure 1: Device Overview

NOTE

The heatmap is available only when the Field Test Data Processor Extension is correctly connected to the LNS through MQTT and has received valid uplink data from the Field Tester. If no heatmap or performance data appears, verify the device join status, uplink transmission, and MQTT configuration.

5. Click Show Data to view a detailed breakdown of all data points collected by the Field Tester. For complete definitions of all parameters shown in this table, refer to the Field Test Data Processor Extension – Parameter Definitions section.

Figure 1: Detailed data

6. (Optional) Click Export to generate a CSV report of the labeled field test data. Export the CSV report when you need to compare signal quality across different test locations, perform further offline analysis, share test results with the project team, or keep the data as part of the project acceptance record.

   NOTE

   Only data points that have been labeled on the device are included in the exported CSV report.

AWS IoT

1. To access the Field Test Data Processor extension, click Launch.

Figure 1: Launch the Field Test Data Processor extension

2. Click the Configuration tab to set the following parameters.

Figure 1: Configure the MQTT broker parameters

• LoRa Network Server: Select AWS IoT.

• MQTT Broker Address:

  To obtain the MQTT broker address, navigate to: AWS IoT > Connect > Domain configurations, then click on iot:Data-ATS in the Domain configurations list and copy the Domain name.

  Figure 1: Configure the MQTT broker address

• Port: Set to 8883, the default port for secure MQTT communication over TLS.

• Enable User Authentication: Leave this setting as default.

• Enable TLS Setting: Enable TLS setting to ensure the security of MQTT message transmissions. Therefore, you need to create certificates in AWS IoT.
  a. AWS IoT policies allow you to control access to the AWS IoT Core data plane operations. To create an AWS IoT policy. Go to AWS IoT > Security > Policies, click Create policy.

  Figure 1: Go to create an AWS IoT policy

  b. Configure policy parameters and click Create.

  Figure 1: Configure parameters

  c. Create certificates to authenticate the connection between the device and the Field Test Data Processor extension. Go to AWS IoT > Security > Certificates, click Create certificate.

  Figure 1: Go to create certificates

  d. Configure certificate parameters and click Create.

  Figure 1: Configure parameters

  e. Download the certificate and key files. Click Continue.

  Figure 1: Download the certificate and key files

  f. In the Certificates list, click the Certificate ID created in the previous step to enter the certificate details page.

  Figure 1: Certificate details

  g. Click Attach policies to add the created AWS IoT policy for the certificates.

  Figure 1: Attach policies

  h. Add the certificates to the Field Test Data Processor extension.

  Figure 1: Add certificates

• Uplink Topic: To receive the uplink data from AWS IoT, you need to create a destination that will process the uplink data to this uplink topic.

  The uplink topic used here should match the one configured in your AWS IoT destination (e.g., RecvFieldTesterUplink), which is typically created during device registration.

• Downlink Topic: To send downlink messages to a Field Tester device, you need to create a Lambda function.
  a. To create a Lambda function. Go to the AWS Lambda console and click Create function.
  b. Configure the function name and runtime.

  Figure 1: Create Lambda function

  c. Copy the following Python code into the Code source and click Deploy.

  import json
  import boto3
  import base64
  import codecs
  import binascii
  
  client = boto3.client("iotwireless")
  
  def lambda_handler(event, context):
  
      print(event)
  
      device_id = event["deviceID"]
      data = event["data"]
      fPort = event["fPort"]
      client.send_data_to_wireless_device(TransmitMode=0,
                                        Id=device_id,
                                        WirelessMetadata={
                                            "LoRaWAN": {"FPort": fPort}},
                                        PayloadData=data)
    return {
        'statusCode': 200,
        'body': json.dumps('Hello from Lambda!')
    }

  Figure 1: Add Python code

  d. Create a message routing rule in AWS IoT to subscribe the downlink topic and call this Lambda Function to process the downlink message. Go to AWS IoT > Message routing > Rules and click Create rule.
  e. Follow the steps in the following figure to create the message routing rule. Then click Create.

  Figure 1: Specify rule properties
  Figure 1: Configure SQL statement
  Figure 1: Attach rule actions
  Figure 1: Review and create

  f. Configure the downlink topic.

  Figure 1: Downlink topic

3. To save the changes, click Save changes.
4. After the Field Tester successfully joins the network and starts sending uplink data, click the Device Overview tab to view the real-time heatmap and network performance data processed by the Field Test Data Processor Extension.

Figure 1: Device Overview

NOTE

The heatmap is available only when the Field Test Data Processor Extension is correctly connected to the LNS through MQTT and has received valid uplink data from the Field Tester. If no heatmap or performance data appears, verify the device join status, uplink transmission, and MQTT configuration.

5. Click Show Data to view a detailed breakdown of all data points collected by the Field Tester. For complete definitions of all parameters shown in this table, refer to the Field Test Data Processor Extension – Parameter Definitions section.

Figure 1: Detailed data

6. (Optional) Click Export to generate a CSV report of the labeled field test data. Export the CSV report when you need to compare signal quality across different test locations, perform further offline analysis, share test results with the project team, or keep the data as part of the project acceptance record.

   NOTE

   Only data points that have been labeled on the device are included in the exported CSV report.

The Things Industries

1. To access the Field Test Data Processor extension, click Launch.

Figure 1: Launch the Field Test Data Processor extension

2. Click the Configuration tab to set the following parameters.

Figure 1: Set parameters

On TTI, you can view your application's MQTT credentials under: Applications > your application > Other integrations > MQTT.

Figure 1: MQTT integration

• LoRa Network Server: Select The Things Industries.

• MQTT Integration:

  • MQTT Broker Address: Use the TTI public MQTT broker address: eu1.cloud.thethings.industries

  • Port: The default MQTT port is 1883.

  • Enable User Authentication: This option must be enabled.

    • Username: Copy the Username from the MQTT Connection credentials section in the TTN console.
    • Password: Use the API key generated by clicking Generate new API key in the TTN console.

  • Enable TLS Setting: Leave this at its default value.

  • Uplink Topic:

    application/{applicationId}/device/{devEui}/event/up

  • Downlink Topic:

    application/{applicationId}/device/{devEui}/command/down

  NOTE

  • {applicationId} and {devEui} are topic placeholders. Keep them unchanged if you want the extension to process all Field Tester devices under the configured application.
  • You may replace them with a specific application ID or device EUI only when you want to limit processing to a particular application or device. In that case, messages from other applications or devices will not be received or processed by the extension.

3. To save the changes, click Save changes.
4. After the Field Tester successfully joins the network and starts sending uplink data, click the Device Overview tab to view the real-time heatmap and network performance data processed by the Field Test Data Processor Extension.

Figure 1: Device Overview

NOTE

The heatmap is available only when the Field Test Data Processor Extension is correctly connected to the LNS through MQTT and has received valid uplink data from the Field Tester. If no heatmap or performance data appears, verify the device join status, uplink transmission, and MQTT configuration.

5. Click Show Data to view a detailed breakdown of all data points collected by the Field Tester. For complete definitions of all parameters shown in this table, refer to the Field Test Data Processor Extension – Parameter Definitions section.

Figure 1: Detailed data

6. (Optional) Click Export to generate a CSV report of the labeled field test data. Export the CSV report when you need to compare signal quality across different test locations, perform further offline analysis, share test results with the project team, or keep the data as part of the project acceptance record.

   NOTE

   Only data points that have been labeled on the device are included in the exported CSV report.