Show last authors
author | version | line-number | content |
---|---|---|---|
1 | [[image:image-20220526143317-1.png]] | ||
2 | |||
3 | Downlink | ||
4 | |||
5 | |||
6 | **~ ** | ||
7 | |||
8 | **~ Contents:** | ||
9 | |||
10 | {{toc/}} | ||
11 | |||
12 | |||
13 | |||
14 | = 1. Parse Payload = | ||
15 | |||
16 | ((( | ||
17 | The following is our operation process and interface. | ||
18 | ))) | ||
19 | |||
20 | ((( | ||
21 | The code can be run in the payload parser. | ||
22 | ))) | ||
23 | |||
24 | [[image:image-20220526143905-6.png]] | ||
25 | |||
26 | Parse Payload | ||
27 | |||
28 | |||
29 | [[image:image-20220526143653-4.png]] | ||
30 | |||
31 | Parse Payload | ||
32 | |||
33 | = 2. Create device steps at Tago = | ||
34 | |||
35 | Take the creation of LGT92 as an example | ||
36 | |||
37 | [[image:https://wiki.dragino.com/images/thumb/a/ab/TAGO_IO1.png/600px-TAGO_IO1.png||alt="TAGO IO1.png" height="270" width="600"]] | ||
38 | |||
39 | Get the authorization code and fill in it. | ||
40 | |||
41 | |||
42 | [[image:https://wiki.dragino.com/images/thumb/f/f3/TAGO_IO2.png/600px-TAGO_IO2.png||alt="TAGO IO2.png" height="503" width="600"]] | ||
43 | |||
44 | All the following options require authorization. | ||
45 | |||
46 | |||
47 | [[image:https://wiki.dragino.com/images/thumb/a/a4/TAGO_IO3.png/600px-TAGO_IO3.png||alt="TAGO IO3.png" height="448" width="600"]] | ||
48 | |||
49 | create device. | ||
50 | |||
51 | |||
52 | [[image:https://wiki.dragino.com/images/thumb/0/02/TAGO_IO4.jpg/600px-TAGO_IO4.jpg||alt="TAGO IO4.jpg" height="256" width="600"]] | ||
53 | |||
54 | [[image:https://wiki.dragino.com/images/thumb/5/58/TAGO_IO5.png/600px-TAGO_IO5.png||alt="TAGO IO5.png" height="488" width="600"]] | ||
55 | |||
56 | [[image:https://wiki.dragino.com/images/thumb/a/af/TAGO_IO6.jpg/600px-TAGO_IO6.jpg||alt="TAGO IO6.jpg" height="109" width="600"]] | ||
57 | |||
58 | [[image:https://wiki.dragino.com/images/thumb/0/0d/TAGO_IO7.png/600px-TAGO_IO7.png||alt="TAGO IO7.png" height="316" width="600"]] | ||
59 | |||
60 | The corresponding widget can be created according to the decoding of the device on TTN. | ||
61 | |||
62 | [[image:https://wiki.dragino.com/images/thumb/8/8b/TAGO_IO8.jpg/600px-TAGO_IO8.jpg||alt="TAGO IO8.jpg" height="341" width="600"]] | ||
63 | |||
64 | [[~[~[image:https://wiki.dragino.com/images/thumb/6/6b/TAGO_IO9.jpg/600px-TAGO_IO9.jpg~|~|alt="TAGO IO9.jpg" height="325" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:TAGO_IO9.jpg]] | ||
65 | |||
66 | = 3. Create LGT92 positioning widget = | ||
67 | |||
68 | ((( | ||
69 | ((( | ||
70 | Creating lgt92 in TTN does not require manual creation, you directly select LGT92 in the brand. | ||
71 | ))) | ||
72 | ))) | ||
73 | |||
74 | ((( | ||
75 | ((( | ||
76 | Devices registered from the LoRaWAN device repository do not need to add a decoder. To manually create a device, you need to add a decoder. | ||
77 | ))) | ||
78 | ))) | ||
79 | |||
80 | ((( | ||
81 | ((( | ||
82 | **Note**: LAQ4 is not registered in the LoRaWAN device repository, the device needs to be created manually. | ||
83 | ))) | ||
84 | ))) | ||
85 | |||
86 | [[image:https://wiki.dragino.com/images/thumb/1/13/TAGO_IO13.png/600px-TAGO_IO13.png||alt="TAGO IO13.png" height="397" width="600"]] | ||
87 | |||
88 | The same steps are used to create widgets and location maps. | ||
89 | |||
90 | |||
91 | [[image:https://wiki.dragino.com/images/thumb/e/e1/TAGO_IO10.png/600px-TAGO_IO10.png||alt="TAGO IO10.png" height="329" width="600"]] | ||
92 | |||
93 | [[image:https://wiki.dragino.com/images/thumb/3/3c/TAGO_IO11.png/600px-TAGO_IO11.png||alt="TAGO IO11.png" height="334" width="600"]] | ||
94 | |||
95 | [[image:https://wiki.dragino.com/images/thumb/3/30/TAGO_IO12.png/600px-TAGO_IO12.png||alt="TAGO IO12.png" height="404" width="600"]] | ||
96 | |||
97 | LGT92 displays the walking track according to the location of the sent data packet. | ||
98 | |||
99 | The device sets the time interval for sending data packets to control the positioning track. | ||
100 | |||
101 | [[image:https://wiki.dragino.com/images/thumb/6/63/TAGO_IO14.png/600px-TAGO_IO14.png||alt="TAGO IO14.png" height="423" width="600"]] | ||
102 | |||
103 | = 4. Real Time Location System demo(RTLS) = | ||
104 | |||
105 | == 4.1 Introduction == | ||
106 | |||
107 | ((( | ||
108 | The purpose of this document is to describe the Real Time Location System demo(RTLS). It is created as a manual guide for understanding each process of the application, explaining types of users and setting the application. | ||
109 | ))) | ||
110 | |||
111 | ((( | ||
112 | You can access the application through: | ||
113 | ))) | ||
114 | |||
115 | ((( | ||
116 | [[https:~~/~~/rtls.run.tago.io>>url:https://rtls.run.tago.io/]] | ||
117 | ))) | ||
118 | |||
119 | * ((( | ||
120 | The user can read this document for the description of the real-time positioning system demonstration. | ||
121 | ))) | ||
122 | |||
123 | ((( | ||
124 | [[https:~~/~~/www.dragino.com/downloads/downloads/LoRa_End_Node/LBT1/RTLS_demo_documentation.pdf>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/LBT1/RTLS_demo_documentation.pdf]] | ||
125 | ))) | ||
126 | |||
127 | == 4.2 Instructions for using LBT1 with RTLS == | ||
128 | |||
129 | ((( | ||
130 | (1)RTLS supports TTNv3 and helium servers for indoor positioning. | ||
131 | ))) | ||
132 | |||
133 | ((( | ||
134 | (2)The user needs to register the device with LBT1 on the TTNv3 or helium server. | ||
135 | ))) | ||
136 | |||
137 | ((( | ||
138 | (3)Then the user needs to integrate the application into Tago. | ||
139 | ))) | ||
140 | |||
141 | ((( | ||
142 | (4)Create LBT1 devices and beacons in RTLS. Please refer to the RTLS instruction document for the specific process. | ||
143 | ))) | ||
144 | |||
145 | ((( | ||
146 | (5)The coordinate position will be updated every time the device sends a data packet. | ||
147 | ))) | ||
148 | |||
149 | [[image:https://wiki.dragino.com/images/thumb/d/d7/RTLS1.png/600px-RTLS1.png||alt="RTLS1.png" height="314" width="600"]] |