AdoModelUser GuidesLoRaWAN-DTU Quick Start

LoRaWAN-DTU Quick Start Guide

User Guideline (UG) · Classification: Controlled · Rev 1.1 — Configure DTU, Gateway and NS for quick LoRaWAN-DTU deployment.

1. Overview

This document is intended to enable quick implementation of LoRaWAN-DTU usage.

1.1 Purpose

Configure DTU, Gateway and NS to enable quick use of LoRaWAN-DTU.

1.2 Target Audience

This document (user manual) is primarily intended for the following engineers:

  • R&D Engineer
  • Technical Support Engineer
  • Maintenance Engineer

1.3 Scope

The software setup described in this document is based on Windows 10 system.

1.4 References

<Omitted>

2. Hardware List

Gateway

  • POE (Input AC 100~240V, Output DC 48V) and POE Splitter (48V Input)
  • POE SPLITTER (OUT: 12V 2A; built into the gateway, no manual wiring required)
  • 915MHz omnidirectional fiberglass antenna. The antenna should be connected to LoRa_ANT_RX/TX

Overall view:

POE adapter and POE splitter of the gateway
Gateway — POE (Input AC 100~240V, Output DC 48V) and POE Splitter (48V Input)
915MHz omnidirectional fiberglass antenna
Gateway — 915MHz omnidirectional fiberglass antenna (connect to LoRa_ANT_RX/TX)
Gateway overall view
Gateway — overall view

DTU

  • 915MHz antenna
  • RS485 to USB converter (Separate purchase / Optional)
  • DTU module
  • 12V 1A DC adapter (Separate purchase / Optional; DC 9~12V, 1~2A is acceptable)
DTU hardware list
DTU — hardware list: 915MHz antenna, RS485-to-USB converter, DTU module, 12V 1A DC adapter

3. Gateway

The gateway is pre-configured by default. You only need to log in to the backend for checking if it cannot uplink data to NS.

3.1 Log in to LoRaWAN Gateway

Methods to obtain the gateway IP address:

  1. Log in to the router admin page and open the DHCP client list.
  2. Unplug and plug the network cable of the gateway, then refresh the DHCP client list. The IP address that appears again is the gateway IP address.

Gateway Login

After obtaining the IP address, connect the gateway with a network cable. Use a computer in the same LAN to log in via ip + 8088, e.g.: xx.xx.xx.29:8088

Default username: root
Default password: admin

Gateway login page
Gateway login page — log in via IP + 8088 (default username: root, default password: admin)

3.2 Frequency Point and NS Configuration

The default page is "Device Information", where you can view the gateway ID and version number. The ID can also be obtained from the label on the gateway.

Click "ParameterConfig" on the left to configure frequency points and NS.

Frequency points are pre-configured by default before shipment and do not need modification. Just confirm whether the NS address is correct.

North America NS address: adomodelcloud.com

Gateway Device Information page
Device Information page — gateway ID and version number
Gateway ParameterConfig page
ParameterConfig page — configure frequency points and NS

3.3 Modify Static IP

The gateway uses dynamic IP by default, and the IP may change after power reboot. To set a static IP:

  1. Click "Ethernet" on the right.
  2. Select "Static IP" in the "Method" field.
  3. Click Apply below.
  4. After successful application, wait 10 seconds and reboot the gateway. The static IP will take effect.
Ethernet settings with static IP selection
Ethernet settings — set the "Method" field to Static IP and click Apply

4. LoRaWAN NS

4.1 Login

North America LoRaWAN NS website: http://adomodelcloud.com:4560/

Account and password shall be provided by the sales representative.

4.2 Add Gateway

First ensure that the NS address configured on the gateway is consistent.

4.2.1 If Gateway Already Exists

Check if the frequency band is correct.

NS gateway frequency band check
NS — check the gateway frequency band

If the frequency band is correct, no modification is needed. If incorrect, click Delete Gateway on the left and add again.

4.2.2 Create New Gateway

Click "Gateway" on the left, then "New Gateway".

Gateway name and description can be filled arbitrarily, height defaults to 0.

  1. Gateway ID:

    • Can be obtained by logging into the gateway
    • Can be obtained from the label value on the gateway (ID is 16 digits, if the label only has 15 digits, add 0 at the end).

  2. Network Server: Select the same frequency band as configured on the gateway. The previous gateway is configured with US915 0-7, so select US_902-928 here (note: US_902-928 is for 0-7 channels, while US_902-928-2 is for 8-15 channels).

NS Gateway list and New Gateway entry
NS — Gateway list, click "New Gateway"
New Gateway gateway ID and network server selection
New Gateway — Gateway ID and Network Server (frequency band) selection
New Gateway details form
New Gateway — gateway details form

The newly created gateway will display a red dot, indicating offline status.

Wait for about 5 minutes and refresh the page. It turns green when online successfully.

Newly created gateway showing red offline dot
NS — newly created gateway displays a red dot (offline status)
Gateway turning green when online
NS — gateway turns green when it comes online successfully
Gateway online status detail
NS — gateway online status

4.3 Create New Application

Click "Application" on the right, then "New Application".

"Application Name" and "Application Description" can be filled arbitrarily. Select "None" for "Payload Data Encoder".

"Network Service Configuration" selects US-915-profile.

Note US-915-profile is for 0-7 channels, while US-915-2-profile is for 8-15 channels.

Click the application name to enter the application.

NS Application list and New Application entry
NS — Application list, click "New Application"
New Application configuration form
New Application — name, description, Payload Data Encoder and Network Service Configuration
Application created in NS
NS — the newly created application

4.4 Add Device

Devices need to be added within the application.

DEVEUI (IMEI): Can be obtained from the label on the side of DTU, or read using the host computer software.

CLASS: DTU uses classC mode by default.

Click Create.

After clicking Create Device, you will be redirected to the APPKEY page. APPKEY can also be obtained from the label on the side of DTU or read via the host computer software. Click Update Key, and the device addition is completed.

Add device page with DEVEUI and class settings
Add device — DEVEUI (IMEI) and CLASS (classC by default)
APPKEY page with Update Key
APPKEY page — click Update Key to complete the device addition

Re-enter the created application, and the application you just created will be displayed.

Application after re-entering
NS — re-enter the created application
Device list inside the application
NS — device list within the application

5. DTU

5.1 Hardware Connection

The DTU connects field sensors to the LoRaWAN network. The RS485-to-USB connection (Scenario A) is for quick start and configuration — the DTU must be configured this way before a sensor can be used. The sensor is connected to the RS485 port (Scenario B).

Scenario A — RS485-to-USB connection (quick start and configuration):

  1. Connect the 12V 1A adapter to the DC port of DTU
  2. Connect RS485 to USB converter to the RS485 port of DTU
  3. Connect the rubber antenna to the antenna port

After normal power-on: POWER light is always on, WORK light flashes every 1 second

Scenario B — connecting a real sensor:

Connect the sensor to the DTU over RS485: sensor A+ / B− to the DTU's A+ / B− terminals (observe the polarity; if the sensor uses a modular RS485 connector, refer to its pinout). Power the sensor as required by its datasheet — some sensors share the DTU's 12 V supply. The antenna and DC power connections are the same as in Scenario A.

DTU hardware connection Scenario A
Scenario A — RS485-to-USB connection for quick start and configuration
DTU hardware connection Scenario B
Scenario B — sensor connected to the DTU RS485 port
Note Modbus polling is optional — configure Modbus through the host computer only if the sensor must be polled by the DTU; a sensor that sends data automatically over RS485 needs no Modbus configuration. In Scenario B the uplink data content is determined by the sensor's output protocol — use the sensor's documentation to interpret the data received on the NS platform; see the NS platform documentation for custom payload codecs.

Wiring reference table (Scenario B):

Sensor sideDTU sideNote
RS485 A+A+Data positive line
RS485 B−B−Data negative line
Power + (if required)External 12 V supplyPer sensor datasheet
GNDGNDCommon ground recommended for stable RS485 communication

5.2 Host Computer Configuration

5.2.1 Open Serial Port on Host Computer

  1. Open the host computer software, the default page is "COM Config"
  2. Click the Port drop-down box to select the RS485 port
  3. Use default values for other parameters: 9600 8N1.
  4. Click Open Serial Port
  5. Click Query. If "Transparent" or "Config" is displayed above, it indicates successful connection to DTU
Host computer software COM Config page
Host computer software — COM Config page (Port selection, 9600 8N1)

5.2.2 Configure LoRaWAN Parameters

  1. Click "Device Info" on the left
  2. Click "Read" and wait for about 20 seconds to get all parameters

Modify parameters. If the parameters are already consistent with NS, no modification is needed. Generally only modify: APPKEY, leave other parameters unchanged.

Confirm that BAND is US915 (factory default for North America), then click Write.

After Write, DTU parameters will be automatically re-read. If the read parameter is US915 as shown in the figure, it indicates successful writing.

Device Info reading LoRaWAN parameters
Device Info — click "Read" to get all parameters (wait about 20 seconds)
Device Info after Write showing BAND US915
Device Info — after Write, parameters are re-read (BAND = US915)

5.2.3 Configure Modbus Parameters

Modbus polling is optional — configure it only when the sensor must be polled by the DTU over Modbus. Modbus is disabled by default and must be enabled manually.

  1. Switch to the Modbus page.
  2. Turn the switch ON.
  3. Enter the Modbus parameters. Scan Cycle is the polling period — minimum 6 seconds (for testing); use more than 120 seconds in normal operation.
  4. Click Write.
  5. A pop-up message confirms that the write was successful.
Note The sensor can now be connected and used. To make the logs easier to read, the LoRaWAN verification below is still performed over USB.
Modbus configuration page
Modbus page — enable Modbus and enter the polling parameters
Pop-up message confirming write success
Pop-up message — write successful

5.3 DTU Function Verification

After configuring parameters with the host computer software, close the software and reboot the DTU.

5.3.1 Automatic Network Access

First ensure that the gateway is online on NS, and NS has created an application and added the device. Use the host computer software to read LoRaWAN parameters to ensure consistency with NS's DEVEUI, APPKEY, and BAND.

DTU will automatically access the network after reboot.

The NET light will be on when network access is successful.

Click the device in the NS application.

DTU status LEDs
DTU — status LEDs: the NET light is on when network access is successful
DTU indicator lights after network access
DTU — indicator lights after successful network access

Click "Live LoRaWAN Frame" at the top to view network access requests, responses and data uplink. (An empty packet will be automatically uplinked after network access)

NS Live LoRaWAN Frame view
NS — "Live LoRaWAN Frame" view: network access requests, responses and data uplink

After DTU successfully accesses the network, use a serial port tool to send hex directly through the RS485 port.

Example: 00112233445566778899aabbccddeeff

Open "Live Data" of the NS device to check that the hex received by RS485 has been completely uplinked to NS.

NS will respond after uplink, and the LINK light will flash when DTU receives the response.

Note The same verification applies to a real sensor in Scenario B. The DTU uplinks once every 6 seconds — if multiple frames are received within 6 seconds, only the latest is uplinked. The payload must be within 220 bytes; data longer than that is not uplinked over LoRa.
Serial port tool sending hex data
Serial port tool — send hex data directly through the RS485 port
NS Live Data showing uplinked hex payload
NS — "Live Data" view showing the hex received by RS485 uplinked to NS
NS response and LINK indication
NS — response after uplink; the LINK light flashes when the DTU receives the response

Data can be directly downlinked from NS after DTU accesses the network.

When clicking "Live Data" or "Live LoRaWAN Frames" above the device, there will be a green "Open downlink tool" button, click to open it.

  1. Check Hex mode
  2. Fill in data, e.g.: ffeeddccbbaa99887766554433221100
  3. Click Send

After sending, NS will display TXACK. The LINK light will also flash when DTU receives the downlink data, and the RS485 port will output the downlink HEX content at the same time.

NS downlink tool button
NS — green "Open downlink tool" button above the device
Downlink tool with Hex mode
Downlink tool — Hex mode and data input
NS TXACK after sending downlink
NS — TXACK displayed after sending downlink

6. Troubleshooting

6.1 Gateway Cannot Go Online

  • Verify that the gateway ID and NS address are correct
  • Check if the gateway ID on NS matches the actual gateway ID
Gateway ID and NS address verification
NS — verify gateway ID and NS address
Gateway detail for ID verification
NS — gateway detail for ID verification
Gateway status and configuration check
NS — gateway status and configuration check

6.2 DTU Cannot Access Network

Compare DEVEUI, BAND, and APPKEY read from the host computer with those filled in NS to ensure consistency.

Host computer reading DEVEUI, BAND and APPKEY
Host computer software — read DEVEUI, BAND and APPKEY

NS device DEVEUI and BAND:

NS device DEVEUI and BAND
NS device — DEVEUI and BAND

NS device APPKEY:

NS device APPKEY
NS device — APPKEY

Also ensure that the gateway is configured with the same BAND.

Download the Full Guide

Download the original quick start document (DOC) or the rendered PDF version (Rev 1.1).

Download Source (DOC)
Download PDF version (.pdf)