Changes for page Notes for TTN

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

From version < 99.14 >

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

To version < 99.11 >

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -255,10 +255,10 @@
  (% 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]]
@@ -266,41 +266,32 @@
  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]]
@@ -308,10 +308,8 @@
  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.
@@ -328,14 +328,12 @@
  (((
  We take LES01 as an example.
--
  )))
  )))
--== 4.1  Step1 ==
++== 4.1 Step1 ==
--
  (((
  (((
  Create a device in TTN with the OTAA keys from LSE01.
@@ -359,15 +359,11 @@
  [[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.
--
--
  )))
  )))
@@ -374,45 +374,34 @@
  [[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.  TTN V3 integrated into MQTT server =
++== 5.1 Introduction ==
--
--== 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.
@@ -428,8 +428,6 @@
  (((
  (((
  Fill in Broker Address and Broker port.
--
--
  )))
  )))
@@ -438,10 +438,8 @@
  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" %)
@@ -458,18 +458,13 @@
  )))
  (((
--
--
  (((
--(% 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}.**
--
--
++**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.
@@ -486,11 +486,7 @@
  (((
  (((
--
--
--(% 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.**
--
--
++**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.
  )))
  )))
@@ -504,23 +504,17 @@
  (((
  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:
--
--
  )))
  (((
--(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.**
--
--
++**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?
  )))
@@ -530,9 +530,7 @@
  )))
  (((
--(% style="color:blue" %)**Downlink command: 01 00 00 5A**
--
--
++Downlink command:01 00 00 5A
  )))
  [[image:image-20220526141021-28.png]]
@@ -540,7 +540,6 @@
  downlink
--
  After sending, you can view it in live data.
  [[image:image-20220526141052-29.png]]
@@ -548,15 +548,12 @@
  downlink
--
  (((
  When downlink is successfully sent, the downlink information can be received on the serial port.
  )))
  (((
--(% style="color:red" %)**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:image-20220526141116-30.png]]
@@ -572,13 +572,13 @@
  (((
  (((
--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 A. You can set **AT+RPL=2** or send the downlink command: **2102**
  )))
  )))
  (((
  (((
--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**
++If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
  )))
  )))
@@ -585,8 +585,6 @@
  (((
  (((
  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
--
--
  )))
  )))
@@ -595,9 +595,8 @@
  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:**

Changes for page Notes for TTN

Summary

Details

Applications

Navigation