How to configure ThingPark CUPS with R1520LG

How to configure ThingPark CUPS with R1520LG

How to configure ThingPark CUPS with R1520LG

1. Objective

This guide provides configuration instructions for the LoRaWAN gateway CUPS (Configuration and Update Server) feature. This guide enables users to equip the gateway with cloud-based remote management capabilities by configuring CUPS authentication credentials just once. Once configured, the gateway automatically retrieves and dynamically synchronizes LNS (LoRaWAN Network Server) routing addresses and RF channel parameters (Channel Plans) via the CUPS protocol. It also supports subsequent security certificate rotation, thereby enabling fully automated, zero-touch maintenance throughout the gateway's lifecycle.

2. Applicability

This guide is applicable to the following products: 
  1. Product Models:R1520LG 
  2. Firmware Version: RobustOS Pro v2.5.0 and later 
  3. Testing Platform:ThingPark Community 
  4. System Environment:
    1. PC End :Windows 11
    2. Device End:Debian 11

3. Prerequisites

Before you begin ensure you have all the necessary components,files, and credentials prepared. 
Hardware & Wiring: 
  1. R1520LG : Make sure the device is powered on. 
  2. The device is connected to the Internet. 
Software & Files: 
  1. Make sure CUPS function is available on your device.
  2. A web browser 
  3. A third-party verification code supplier (e.g.,Microsoft Authenticator, Google Authenticator etc.) 
Knowledge & Credentials: 
  1. Admin access to the R1520LG web GUI (username and password) 
  2. An active account for ThingPark platform 
  3. A basic of understanding of CLI command. 

4. Procudure

Depending on deployment requirements, you can use any of the following methods to complete the CUPS configuration for the gateway:

4.1 Scenario 1: Manually configuring CUPS parameters

4.1.1 Preparing Stage
At this stage, you first need to register an account on the ThingPark Community by visiting https://community.thingpark.org/register/; the page appears as shown in the image:
image

After completing the required information, a confirmation message will appear. You can subsequently access the main control interface by entering your email and password and completing third-party authentication, as shown in the figure:

Third-party authentication requires a one-time authentication code; it is recommended to use Microsoft Authenticator to generate the code, as shown in the image:

Note:Third-party authentication can be implemented using various authentication apps, such as Microsoft Authenticator, Google Authenticator, 2FAS, etc. 

After successful activation, enter the platform management interface, as shown in the figure:
4.1.2 Register the device on the platform
Once you are on this screen, click Base Stations -> Add Base Station.
image

Alternatively,register the device by clicking imagein the top-right corner if the "Base Station" module on the dashboard:
image

Since the device has not yet been fully registered on the platform and there is no pre-existing registration template for the specific device model, click "Generic" to create a generic template
image

Enter the registration panel and select "Basics Station Packet Forwarder" under the "Model" field; taking the R1520LG (US915 frequency band) as an example:
image

When registering using the general template, you must enter the device's address; you can do this by typing the address into the search box on the map:
image

When this screen appears, it indicates that platform registration is complete; the next step is to register the device.
image

4.1.3 Import data and establish a connection at the device unit.
Access the R1520LG Web UI, navigate to LoRaWAN > LoRa Settings, set the LoRaWAN network server to "External NS" mode, and enable the Packet Forwarder:
image

Select "Basic Station" in the "Packet Forwarder" module, then choose "CUPS" from the connection mode options that appear below; finally, enter the required information into the CUPS Server URL and CUPS Server Port fields as prompted by the platform. https://community.thingpark.io:443/ Under CUPS Authentication Mode, select "Client Authentication TLS Server," then click the link for "Manage Certificates" to import the certificate:
image

You need to manually set up the ThingPark connection and download the Amazon Root CA 1
certificate to upload as `cups.trust`. Here is the direct link to the certificate: https://www.amazontrust.com/repository/AmazonRootCA1.pem. Open CMD on your PC and enter the relevant commands:
https://www.amazontrust.com/repository/AmazonRootCA1.pem > cups.trust
After downloading the certificaate via the CLI, navigate to System -> Certificate Manager, drag the certificate to the CA Cert field under CUPS CA File Import, Click image to upload the certificate.
image

If the certificates are uploaded successfully and the parameters are correct, the device will attempt to connect to the ThingPark CUPS server to retrieve `tc.trust`, `tc.crt`, and `tc.key`, which facilitate the connection to the LNS server. A successful connection is shown in the figure below:
image

Note: If the certificate retrieval fails, it may be due to the accidental deletion of tc.trust, which prevents the communication channel from being established. In this case, it is recommended to return to the platform and regenerate the CUPS server certificate under Base Stations -> Advanced -> Security, then restart the device to re-establish the connection.
image

5. Verfication

Under LoRaWAN -> LoRa Settings -> Status, check whether Basic Station is connected:
image

Alternatively, check the platform to see if the Base Station is in the "Active" state and whether the Lo RaWAN Radio Status has collected device-related information:
image

6. Troubleshooting

If the Basics Station is not connected, navigate to System -> Debug and search for system information related to "rosp_lora" and "packet forwarder" to identify any potential errors:
This error arises when an incorrect frequency band is selected, causing the platform to issue an incompatible SC1301 configuration that does not match the device's actual settings, thereby resulting in a connection failure. To resolve this, you can attempt to modify the frequency band on the platform or create a new Base Station configuration for the connection.

image
This error arises from the incorrect deletion of existing `tc.trust` or `cups.trust` files, causing the device to lack the necessary authentication credentials when connecting to a CUPS or LNS server, which ultimately leads to connection failure. To resolve this issue, you can regenerate the certificates via the platform's "Advanced" interface, then reboot the device and re-initiate the connection.
    • Related Articles

    • How to Connect the R1520-LG Basic Station to Netmore LNS

      Overview This guide provides step-by-step instructions on how to connect a Robustel R1520-LG LoRaWAN gateway to the Netmore LoRaWAN Network Server (LNS) using the Basic Station protocol. The process involves configuring the gateway on the Netmore ...
    • How to Configure BACnet IP Data Collection

      1. Protocol Overview Protocol Description: BACnet IP is a communication protocol for building automation and control networks, based on IP networks for data communication and control. It enables interoperability between building devices, supporting ...
    • How to Configure Modbus TCP Data Collection

      1. Protocol Overview Protocol Description: Modbus TCP is a common industrial automation protocol based on TCP/IP network transmission. Application Scenarios: This protocol is widely used for data acquisition and control of devices such as PLCs, ...
    • How to configure Modbus RTU data collection

      1. Protocol Overview Protocol Description: Modbus RTU is a standard industrial automation protocol that transmits binary data over serial links (e.g., RS-232 or RS-485). Application Scenarios: Widely used for devices that support serial ...
    • How to Configure OPC UA Data Collection

      1. Protocol Overview Protocol Description: Modbus TCP is a common industrial automation protocol based on TCP/IP network transmission. Application Scenarios: This protocol is widely used for data acquisition and control of devices such as PLCs, ...