Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29

From version < 99.9 >

edited by Xiaoling
on 2022/07/25 08:44

To version < 99.15 >

edited by Xiaoling
on 2022/07/25 09:15

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -114,8 +114,10 @@
  Download and Install gateway-rs
--=== 2.2.5 Step 2: Back to Semtech UDP page ===
++=== 2.2.5  Step 2: Back to Semtech UDP page ===
++
++
  Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
  [[image:image-20220526135125-7.png]]
@@ -123,32 +123,41 @@
  Configuration of helium
--= 3. Gateway Registration for Basics Station =
--== 3.1 Introduction ==
++= 3.  Gateway Registration for Basics Station =
++
++== 3.1  Introduction ==
++
++
  (((
  (((
  The LoRa Basics™ Station protocol simplifies management of large scale LoRaWAN networks. LoRa Basics™ Station is the preferred way of connecting Gateways to The Things Stack. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]
++
++
  )))
  )))
  (((
--**Below list the support products and Requirements:**
++(% style="color:blue" %)**Below list the support products and Requirements:**
  )))
  (((
  (((
--      ~1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
++1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
  )))
  (((
 . Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
++
++
++
++
  )))
  )))
  (((
--**What do you need to prepare**
++(% style="color:blue" %)**What do you need to prepare**
  )))
  (((
@@ -155,12 +155,14 @@
  (((
  A gateway that can access the internet normally
++
  )))
  )))
--== 3.2 Step 1. Add Gateway ==
++== 3.2  Step 1: Add Gateway ==
++
  (((
  (((
  The example for **EU**
@@ -176,6 +176,8 @@
  (((
  (((
  Following picture is the successful added.
++
++
  )))
  )))
@@ -184,52 +184,66 @@
  Add Gateway
--== 3.3 Step 2. Create the API key ==
++== 3.3  Step 2: Create the API key ==
++
++
  user need to create the CUPS API key and LNS API key.
++
  [[image:image-20220526135349-9.png]]
  Create CUPS API key
++
  [[image:image-20220526135428-10.png]]
  Create LNS API key
++
  (% style="color:red" %)**Note : Please copy the API key.**
--== 3.4 Step 3. Update the gateway setting ==
++== 3.4  Step 3: Update the gateway setting ==
++
++
  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
++
  [[image:image-20220526135528-11.png]]
  paste the API key
--== 3.5 Step 4. Access the gateway GUI ==
++== 3.5  Step 4: Access the gateway GUI ==
++
++
  User need to update the API key and install the Certificate
++
  [[image:image-20220526135601-12.png]]
  Access the gateway GUI
--== 3.6 Step 5. Configure Station ==
++== 3.6  Step 5: Configure Station ==
++
++
  User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
--**just to clarify.**
++(% style="color:blue" %)**just to clarify:**
++
  (% class="box" %)
  (((
--   CUPS Server URI                     ~-~-> Server Adress
--   CUPS Authorization Key         ~-~-> Server CUPS API Key
--   LNS Authorization Key           ~-~-> Server LNS API Key
--   CUPS certificate                     ~-~-> Server CA(user can use the button to install the certificate by default)
++   CUPS Server URI                     ~-~->    Server Adress
++   CUPS Authorization Key         ~-~->    Server CUPS API Key
++   LNS Authorization Key           ~-~->    Server LNS API Key
++   CUPS certificate                      ~-~->    Server CA(user can use the button to install the certificate by default)
  )))
  [[image:image-20220526135654-13.png]]
@@ -237,32 +237,41 @@
  Congfigure Station
--== 3.7 Start Station ==
++== 3.7  Start Station ==
++
++
  (((
  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
++
  )))
--== 3.8 Siccessful Connection ==
++== 3.8  Siccessful Connection ==
++
  If user completes the above steps,which will see live date in the TTN.
++
  [[image:image-20220526135734-14.png]]
  Station live date
--== 3.9 Trouble Shooting ==
++== 3.9  Trouble Shooting ==
++
++
  User can check the station log in the logread/system log page.
++
  [[image:image-20220526135845-15.png]]
  Station Log
++
  and recode the station log in the system/Recode log page.
  [[image:image-20220526135940-16.png]]
@@ -270,8 +270,10 @@
  Recore Log
--= 4. Configure node connection to TTNv3 =
++= 4.  Configure node connection to TTNv3 =
++
++
  (((
  (((
  Following is an example for how to join the TTN v3 LoRaWAN Network.
@@ -288,12 +288,14 @@
  (((
  We take LES01 as an example.
++
  )))
  )))
--== 4.1 Step1 ==
++== 4.1  Step1 ==
++
  (((
  (((
  Create a device in TTN with the OTAA keys from LSE01.
@@ -317,11 +317,15 @@
  [[image:image-20220526140044-18.png]]
--== 4.2 Step2 ==
++== 4.2  Step2 ==
++
++
  (((
  (((
  There are all our nodes in the repository. Users can choose the corresponding brand, model, firmware version and frequency.The decoder and configuration information of the node are pre-configured.Users do not need to configure them.
++
++
  )))
  )))
@@ -328,34 +328,45 @@
  [[image:image-20220526140132-19.png]]
--== 4.3 Step3 ==
++== 4.3  Step3 ==
++
++
  Add APP EUI in the application:
++
  [[image:image-20220526140205-20.png]]
--== 4.4 Step4 ==
++== 4.4  Step4 ==
++
++
  Add APP KEY and DEV EUI:
++
  [[image:image-20220526140251-21.png]]
--= 5. TTN V3 integrated into MQTT server =
--== 5.1 Introduction ==
++= 5.  TTN V3 integrated into MQTT server =
++
++== 5.1  Introduction ==
++
++
  (((
  (((
  The Application Server exposes an MQTT server to work with streaming events. In order to use the MQTT server you need to create a new API key, which will function as connection password. You can also use an existing API key, as long as it has the necessary rights granted.
++
  )))
  )))
--== 5.2 Create device steps at MQTT ==
++== 5.2  Create device steps at MQTT ==
++
  (((
  (((
  The user creates a new API KEY after creating a device on TTN V3.
@@ -371,6 +371,8 @@
  (((
  (((
  Fill in Broker Address and Broker port.
++
++
  )))
  )))
@@ -379,8 +379,10 @@
  Fill in the username and password into MQTT.
++
  [[image:image-20220526140420-23.png]]
++
  The Application Server publishes uplink traffic on the following topics:
  (% class="box" %)
@@ -397,13 +397,18 @@
  )))
  (((
++
++
  (((
--**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
++(% style="color:red" %)**Note**: **Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.**
++
++
  )))
  )))
  [[image:image-20220526140452-24.png]]
++
  (((
  (((
  While you could subscribe to all of these topics separately, for the simplicity of this tutorial we use # to subscribe to all topics, i.e. to receive all uplink traffic.
@@ -420,7 +420,11 @@
  (((
  (((
--**Note**: Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.
++
++
++(% style="color:red" %)**Note**: **Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.**
++
++
  )))
  )))
@@ -434,17 +434,23 @@
  (((
  To send an unconfirmed downlink message to the device dev1 in application app1 in tenant tenant1 with the hexadecimal payload BE EF on FPort 15 with normal priority, use the topic v3/app1@tenant1/devices/dev1/down/push with the following contents:
++
++
  )))
  (((
--**Note**: Use this handy tool to convert hexadecimal to base64.
++(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.**
++
++
  )))
  [[image:image-20220526140936-27.png]]
--== 5.3 Send Downlink message ==
++== 5.3  Send Downlink message ==
++
++
  (((
  How to configure downlink in TTN V3?
  )))
@@ -454,7 +454,9 @@
  )))
  (((
--Downlink command:01 00 00 5A
++(% style="color:blue" %)**Downlink command: 01 00 00 5A**
++
++
  )))
  [[image:image-20220526141021-28.png]]
@@ -462,6 +462,7 @@
  downlink
++
  After sending, you can view it in live data.
  [[image:image-20220526141052-29.png]]
@@ -469,12 +469,15 @@
  downlink
++
  (((
  When downlink is successfully sent, the downlink information can be received on the serial port.
  )))
  (((
--**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
++(% style="color:red" %)**Note**:** If the downlink byte sent is longer, the number of bytes will be displayed.**
++
++
  )))
  [[image:image-20220526141116-30.png]]
@@ -490,13 +490,13 @@
  (((
  (((
--If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
++If the equipment uses (% style="color:blue" %)**CLASS A**(%%). You can set (% style="color:red" %)**AT+RPL=2** (%%)or send the downlink command: (% style="color:red" %)**2102**
  )))
  )))
  (((
  (((
--If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
++If the equipment uses (% style="color:blue" %)**CLASS C**(%%). You can set** (% style="color:red" %)AT+RPL=4(%%)** or send the downlink command: (% style="color:red" %)**2104**
  )))
  )))
@@ -503,6 +503,8 @@
  (((
  (((
  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
++
++
  )))
  )))
@@ -511,8 +511,10 @@
  downlink
--= 6. Request Remote Support =
++= 6.  Request Remote Support =
++
++
  (((
  These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
  \\If problem not solve, and you need dragino remote support, please follow to this document: [[TTN Support instruction>>url:https://www.dragino.com/downloads/index.php?dir=&file=TTNv3_Support_Guide.pdf]](% style="color:red" %) **If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the screenshots for each step to check. They include:**
@@ -524,19 +524,24 @@
  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
  * End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
--**~1. End Device Join Screen shot, we can check:**
++(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
++
  * If the device is sending join request to server?
  * What frequency the device is sending?
++
  [[image:image-20220526141308-33.png]]
  Console Output from End device to see the transmit frequency
--User can run **AT+CFG **command to print configuration information.
--* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
++User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
++* Is the device in OTAA mode or ABP mode? (% style="color:red" %)**AT+NJM=1** (%%)(OTAA mode), (% style="color:red" %)**AT+NJM=0**(%%) (ABP mode)
++
++
++
  [[image:image-20220526141612-36.png]]
@@ -543,13 +543,17 @@
  Console Output from End device to see the transmit frequency
--**2. Gateway packet traffic in gateway web or ssh. we can check:**
++(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
++
  * (((
  If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
  )))
  * (((
  If the gateway gets the Join Accept message from server and transmit it via LoRa?
++
++
++
  )))
  [[image:image-20220526141739-37.png]]
@@ -557,8 +557,9 @@
  Console Output from Gateway to see packets between end node and server.
--**3. Gateway Traffic Page in LoRaWAN Server**
++(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
++
  * (((
  If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
  )))
@@ -567,6 +567,9 @@
  )))
  * (((
  If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
++
++
++
  )))
  [[image:image-20220526141823-38.png||height="501" width="1144"]]
@@ -574,18 +574,21 @@
  The Traffic for the End node in the server, use TTNv3 as example
++
  [[image:image-20220526141917-39.png]]
  The Traffic for the End node in the server, use TTNv3 as example
--**4. Data Page in LoRaWAN server**
++(% style="color:blue" %)**4. Data Page in LoRaWAN server**
++
  (((
  (((
  (((
  If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
++
  [[image:image-20220526141956-40.png]]
  )))
  )))
@@ -594,6 +594,7 @@
  The data for the end device set in server
++
  [[image:image-20220526142033-41.png]]
  Check if OTAA Keys match the keys in device

Changes for page Notes for TTN

Summary

Details

Applications

Navigation