Conduct Field Tests With RAK10701-Plus Field Tester for LoRaWAN

This document outlines standard and scenario-based field testing workflows designed to accurately validate LoRaWAN coverage and network quality in real-world conditions.

How Field Tester Plus Works?

Before performing field testing, it’s important to understand how the Field Tester Plus operates under different conditions. After powering on and connecting to a LoRaWAN Network Server (LNS), the Field Tester Plus operates in one of two modes depending on your gateway setup:

Mode	Description
Field Tester Mode (Extension Installed)	Full metric reporting, including uplink and downlink RSSI/SNR, packet loss, and CSV report generation.
LinkCheck Mode (No Extension Installed)	Limited to Downlink RSSI/SNR and gateway count only. No uplink analysis or CSV export available.

The following workflow summarizes the field testing preparation and execution:

Figure 1: Field Tester Workflow

Standard Testing Procedure

Pre-Test Checklist

Before beginning field tests, confirm the following:

• Environmental Setup: Confirm gateway installation and area accessibility.
• Device Setup:
  • Set the LoRaWAN Frequency Band.
  • Configure OTAA parameters via WisToolBox (if required).
  • Ensure the antenna is connected securely.
• Network Setup:
  • Register the Field Tester Plus and gateway to the same LNS.
• Install Field Test Data Processor Extension to enable full metric reporting.

Test Execution

1. Power on the Field Tester Plus (press and hold the side button for 5 seconds).
2. Wait for LoRaWAN join confirmation (Joined status will appear).
3. Adjust device settings if needed:
   • TX Interval
   • Data Rate (DR)
   • ADR ON/OFF
4. Relocate the device to the physical test point you want to evaluate.
5. Trigger uplinks manually (double-press the button) or wait for auto-sending.

Real-time displayed metrics (in Field Tester Mode):

• Uplink Metrics: RSSI, SNR, Packet Loss, Data Rate
• Downlink Metrics: RSSI, SNR, Packet Loss, Data Rate
• MAX Distance: Estimated distance to the farthest gateway (requires GPS; minimum resolution is 250 meters).
• MIN Distance: Estimated distance to the nearest gateway (requires GPS; minimum resolution is 250 meters).
• Gateway Count: Number of gateways that successfully received the last uplink.
• Location: GPS coordinates (if GPS available) or manually entered Location Label for indoor or GPS-denied environments.

NOTE

You can also monitor real-time test data through the Field Test Data Processor Extension on your WisGateOS 2 gateway, which provides a broader view including all recent packets, signal quality, and heatmap visualization.

Figure 1: Field Tester Data Overview

Manual Labeling

If GPS is unavailable (e.g., during indoor testing), or if you want to tag test data for later analysis, assign a Location Label manually. This ensures the data is recorded and included in the CSV export. By default, the label is set to NULL. If it is not updated, the test data will be excluded from the CSV file.

To set a label:

1. Go to Settings > Label.
2. When the label field blinks, press down to open the on-screen keyboard.
3. Enter a label (up to 6 characters) and press Enter.
4. The selected parameter will blink, indicating it is active.
5. The labeled test cycle (usually 50 packets) will begin.

Post-Test Data Analysis (Data Export and Interpretation)

After completing field testing, you can export the structured test data for further analysis.

Export the Test Data

1. Open the Field Test Data Processor Extension UI on your WisGateOS 2 gateway.
2. Go to Device Overview page and click the Export button located in the top-right corner.
3. Download the generated CSV report.

Figure 1: Field Tester CSV File

Contents of the CSV Report

Each row in the CSV file corresponds to a labeled test point.

Field	Description
label	Location label manually entered.
time	UTC timestamp when the data was recorded.
rssi	Uplink signal strength (Received Signal Strength Indicator).
snr	Uplink signal-to-noise ratio.
signal_quality	Qualitative signal evaluation (e.g., Excellent, Good, Poor).
dr	LoRaWAN data rate used during transmission.
region	LoRaWAN frequency band (e.g., EU868, US915).
total receive	Number of uplink packets received.
total send	Number of uplink packets sent.
packet loss rate	Percentage of lost packets.
latitude	GPS latitude (if available).
longitude	GPS longitude (if available).
gwCount	Number of gateways that successfully received the uplink.
num_1_gateway_eui	EUI of the nearest receiving gateway.
num_1_gateway_distance	Estimated distance to the nearest gateway (requires GPS, minimum resolution: 250 meters).
Label Final PLR	Final packet loss rate calculated after completing the label cycle.

Signal Quality Reference

Figure 1: Signal Quality Reference

Metric	Ideal Range	When to Take Action
RSSI (Received Signal Strength Indicator)	-30 dBm to -90 dBm	If below -120 dBm, signal is very weak and likely unusable → Consider adding a gateway or adjusting placement
SNR (Signal-to-Noise Ratio)	Greater than 0 dB	If below 0 dB, especially -10 dB or worse, interference is likely → Check for RF noise or obstructions.
Packet Loss Rate	≤ 5 %	If above 20%, this indicates unstable connectivity → Improve antenna setup or enhance coverage area.

Scenario-Based Field Testing

This section explains how to apply the Field Tester Plus in different real-world situations to optimize LoRaWAN network deployment, coverage validation, and performance evaluation.

Pre-Deployment Gateway Planning

Identify the optimal locations for new gateways to maximize coverage and network performance.

Testing Steps

At each candidate site:

1. Place the Field Tester Plus stationary position.
2. Transmit at least 50 uplinks (automatic or manual).
3. Record the following key metrics:
   • RSSI (Target: > -90 dBm)
   • SNR (Target: > 0 dB)
   • Packet Loss (Threshold: < 5%)

Data Analysis

1. Export the CSV report from the Field Test Extension.
2. Analyze average RSSI, SNR, and packet loss at each site.

Recommendations Based on Results

Issue	Possible Cause	Recommended Action
Weak signal (RSSI < -120 dBm)	Excessive distance from the gateway	Install a new gateway closer to the affected coverage area
High interference (SNR < -10 dB)	Environmental RF noise or obstacles	Change frequency or relocate the gateway
High packet loss (>20 %)	Obstructed signal path or poor backhaul connectivity	Deploy additional gateways or optimize the placement of the existing gateway

Post-Deployment Coverage Validation

Verify that installed gateways provide reliable coverage across the operational area.

Testing Steps

1. Prioritize critical test points:
   • Access Points (Entries/Exits): Validate seamless device onboarding.
   • Structural Challenges (Basements/Elevators): Assess signal penetration in difficult environments.
   • High-Traffic Areas (Retail Spaces): Check network resilience under load.
2. At each test location:
   • Assign descriptive labels to test points (e.g., B1-Parking-A12).
   • Complete at least 50 uplinks to ensure statistical reliability.
3. For critical zones (Optional Best Practice):
   • Conduct measurements at different times of the day—morning, afternoon, and peak hours—to capture signal variations.
4. Record the following key metrics:
   • RSSI (Target: > -90 dBm)
   • SNR (Target: > 0 dB)
   • Packet Loss Rate (Threshold: < 5%)

Data Analysis

• Correlate packet loss with physical obstructions (via labeled test points)
• Observe whether RSSI, SNR, or packet loss fluctuates throughout the day.

Recommendations Based on Results

Finding	Interpretation	Recommended Action
Low RSSI (Weak Signal)	Gateway coverage is insufficient	Reposition the gateway or deploy a repeater
Poor SNR (High Interference)	Signal is blocked or distorted by obstacles	Investigate the surroundings, adjust the frequency, or reposition the gateway
High Packet Loss	Fluctuating or unstable connections	Enable ADR or lower the data rate (e.g., DR3 → DR2)

NOTE

After adjusting the network (moving gateway, adjusting power, etc.), repeat the testing cycle to validate performance improvements.

Maximum Coverage Distance Testing

Determine the maximum effective communication distance from a gateway under real deployment conditions.

Radial Testing Pattern

1. Start at the gateway's location (0 meters).
2. Walk outward along different radial paths from the gateway.
3. Maintain a consistent walking speed (~1 m/s) and antenna orientation.

Real-Time Monitoring:

• Distance: Measures via GPS (if available) or through manual tracking.
• RSSI: Triggers an alert if it drops below –120 dBm.
• Packet Loss Rate: Triggers an alert if it exceeds 20%.

Recommendations Based on Results

Problem	Cause	Solution
RSSI < -120 dBm	Signal strength is too weak	Increase transmission power or antenna gain
Packet Loss Rate > 20 %	Instability in the communication link	Reduce the data rate (e.g., DR1 to DR0)
Join Failures	Gateway is too far from the device	Deploy more gateways to improve coverage density