Changes for page Notes for TTN

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

From version < 2.4 >

edited by Xiaoling
on 2022/05/17 09:37

To version < 1.5 >

edited by Xiaoling
on 2022/05/17 08:58

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -62,13 +62,9 @@
  === 2.2.2 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]]
--(((
--2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
--)))
++1. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
  === 2.2.3 Example ===
@@ -95,54 +95,38 @@
  == 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:**
--)))
--(((
--(((
--      ~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]]
  )))
--(((
--      2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
++1. (((
++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**
--)))
  (((
--(((
  A gateway that can access the internet normally
  )))
--)))
  == 3.2 Step 1. Add Gateway ==
  (((
--(((
  The example for **EU**
  )))
--)))
  (((
--(((
  User can add your gateway into The Things Network V3 according to the previous step
  )))
--)))
  (((
--(((
  Following picture is the successful added.
  )))
--)))
  [[image:https://wiki.dragino.com/images/thumb/5/5f/Add_gateway_1.1.png/600px-Add_gateway_1.1.png||height="397" width="600"]]
@@ -161,7 +161,7 @@
  Create LNS API key
--(% style="color:red" %)**Note : Please copy the API key.**
++**Note : Please copy the API key.**
  == 3.4 Step 3. Update the gateway setting ==
@@ -185,13 +185,11 @@
  **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:https://wiki.dragino.com/images/thumb/8/8c/Confiure_station_cao.png/600px-Confiure_station_cao.png||height="321" width="600"]]
@@ -228,42 +228,30 @@
  = 4. Configure node connection to TTNv3 =
  (((
--(((
  Following is an example for how to join the TTN v3 LoRaWAN Network.
  )))
--)))
  (((
--(((
  The gateway is already set up to connect to the TTN network, so we now need to configure the TTNv3 server.
  )))
--)))
  (((
--(((
  We take LES01 as an example.
  )))
--)))
  == 4.1 Step1 ==
  (((
--(((
  Create a device in TTN with the OTAA keys from LSE01.
  )))
--)))
  (((
--(((
  Each LSE01 is shipped with a sticker with the default device EUI as below:
  )))
--)))
  (((
--(((
  You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
  )))
--)))
  [[image:https://wiki.dragino.com/images/thumb/c/c7/TTNv3--01.png/600px-TTNv3--01.png||alt="TTNv3--01.png" height="277" width="600"]]
@@ -272,10 +272,8 @@
  == 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.
  )))
--)))
  [[image:https://wiki.dragino.com/images/thumb/f/fc/TTNv3--03.png/600px-TTNv3--03.png||alt="TTNv3--03.png" height="333" width="600"]]
@@ -296,30 +296,22 @@
  == 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 ==
  (((
--(((
  The user creates a new API KEY after creating a device on TTN V3.
  )))
--)))
  (((
--(((
  Then copy the password and open MQTT.fx.
  )))
--)))
  (((
--(((
  Fill in Broker Address and Broker port.
  )))
--)))
  [[image:https://wiki.dragino.com/images/thumb/8/82/V3_MQTT1_.png/600px-V3_MQTT1_.png||alt="V3 MQTT1 .png" height="325" width="600"]]
@@ -330,9 +330,7 @@
  The Application Server publishes uplink traffic on the following topics:
--(% class="box" %)
--(((
--   v3/{application id}@{tenant id}/devices/{device id}/join
++{{{   v3/{application id}@{tenant id}/devices/{device id}/join
     v3/{application id}@{tenant id}/devices/{device id}/up
     v3/{application id}@{tenant id}/devices/{device id}/down/queued
     v3/{application id}@{tenant id}/devices/{device id}/down/sent
@@ -341,41 +341,31 @@
     v3/{application id}@{tenant id}/devices/{device id}/down/failed
     v3/{application id}@{tenant id}/devices/{device id}/service/data
     v3/{application id}@{tenant id}/devices/{device id}/location/solved
--)))
++}}}
  (((
--(((
--**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
++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:https://wiki.dragino.com/images/thumb/d/dc/V3_MQTT3.png/600px-V3_MQTT3.png||alt="V3 MQTT3.png" height="400" width="600"]]
  (((
--(((
  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.
  )))
--)))
  [[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT4.jpg/600px-V3_MQTT4.jpg||alt="V3 MQTT4.jpg" height="326" width="600"]]
  (((
--(((
  Downlinks can be scheduled by publishing the message to the topic v3/{application id}@{tenant id}/devices/{device id}/down/push.
  )))
--)))
  (((
--(((
--**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.
++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.
  )))
--)))
  (((
--(((
  Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. Example:
  )))
--)))
  [[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT5.png/600px-V3_MQTT5.png||alt="V3 MQTT5.png" height="289" width="600"]]
@@ -384,7 +384,7 @@
  )))
  (((
--**Note**: Use this handy tool to convert hexadecimal to base64.
++Note: Use this handy tool to convert hexadecimal to base64.
  )))
  [[image:https://wiki.dragino.com/images/thumb/9/9f/V3_MQTT6.png/600px-V3_MQTT6.png||alt="V3 MQTT6.png" height="313" width="600"]]
@@ -418,7 +418,7 @@
  )))
  (((
--**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
++Note: If the downlink byte sent is longer, the number of bytes will be displayed.
  )))
  [[image:https://wiki.dragino.com/images/thumb/c/c9/Downlink_52.png/600px-Downlink_52.png||height="407" width="600"]]
@@ -426,28 +426,20 @@
  downlink
  (((
--(((
  If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
  )))
--)))
  (((
--(((
--If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
++If the equipment uses CLASS A. You can set AT+RPL=2 or send the downlink command: 2102
  )))
--)))
  (((
--(((
--If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
++If the equipment uses CLASS C. You can set AT+RPL=4 or send the downlink command: 2104
  )))
--)))
  (((
--(((
  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
  )))
--)))
  [[image:https://wiki.dragino.com/images/thumb/d/d9/Downlink_54.png/600px-Downlink_54.png||height="127" width="600"]]
@@ -457,7 +457,7 @@
  (((
  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:**
++\\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]] 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:
  )))
  * End node is connected to serial port to show the Join frequency and DR. (If possible)
@@ -466,6 +466,7 @@
  * 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:**
  * If the device is sending join request to server?
@@ -475,9 +475,9 @@
  Console Output from End device to see the transmit frequency
--User can run **AT+CFG **command to print configuration information.
++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)
++* Is the device in OTAA mode or ABP mode? AT+NJM=1 (OTAA mode), AT+NJM=0 (ABP mode)
  [[image:https://wiki.dragino.com/images/thumb/c/c5/LoRaWAN_Communication_Debug23.png/600px-LoRaWAN_Communication_Debug23.png||height="514" width="600"]]
@@ -485,12 +485,8 @@
  **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?
--)))
++* 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:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
@@ -499,15 +499,9 @@
  **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.
--)))
--* (((
--If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
--)))
--* (((
--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.
--)))
++* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
++* If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
++* 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:https://wiki.dragino.com/images/thumb/d/da/LoRaWAN_Communication_Debug22.png/600px-LoRaWAN_Communication_Debug22.png||height="268" width="600"]]
@@ -521,12 +521,8 @@
  **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:https://wiki.dragino.com/images/thumb/9/99/LoRaWAN_Communication_Debug4.png/600px-LoRaWAN_Communication_Debug4.png||height="222" width="600"]]

Changes for page Notes for TTN

Summary

Details

Applications

Navigation