Hide last authors
author | version | line-number | content |
---|---|---|---|
8.2 | 1 | [[image:image-20220526143317-1.png]] | |
1.1 | 2 | ||
8.2 | 3 | Downlink | |
4 | |||
5 | |||
6 | **~ ** | ||
7 | |||
37.2 | 8 | **~ Table of Contents:** | |
1.10 | 9 | ||
1.6 | 10 | {{toc/}} | |
1.3 | 11 | ||
1.6 | 12 | ||
1.3 | 13 | ||
37.2 | 14 | = 1. Parse Payload = | |
1.3 | 15 | ||
37.2 | 16 | ||
1.3 | 17 | ((( | |
1.2 | 18 | The following is our operation process and interface. | |
1.3 | 19 | ))) | |
1.1 | 20 | ||
1.3 | 21 | ((( | |
1.2 | 22 | The code can be run in the payload parser. | |
37.2 | 23 | ||
24 | |||
1.3 | 25 | ))) | |
1.1 | 26 | ||
8.2 | 27 | [[image:image-20220526143905-6.png]] | |
1.1 | 28 | ||
1.2 | 29 | Parse Payload | |
1.1 | 30 | ||
31 | |||
37.2 | 32 | ||
8.2 | 33 | [[image:image-20220526143653-4.png]] | |
34 | |||
1.2 | 35 | Parse Payload | |
1.1 | 36 | ||
11.2 | 37 | ||
1.1 | 38 | ||
37.2 | 39 | = 2. Create device steps at Tago = | |
40 | |||
41 | |||
1.2 | 42 | Take the creation of LGT92 as an example | |
1.1 | 43 | ||
37.2 | 44 | ||
11.2 | 45 | [[image:image-20220526143953-7.png]] | |
1.1 | 46 | ||
25.5 | 47 | ||
48 | |||
25.6 | 49 | Get the authorization code and fill in it | |
1.1 | 50 | ||
37.2 | 51 | ||
11.2 | 52 | [[image:image-20220526144034-8.png]] | |
1.3 | 53 | ||
15.2 | 54 | ||
25.4 | 55 | ||
1.2 | 56 | All the following options require authorization. | |
1.1 | 57 | ||
37.2 | 58 | ||
11.2 | 59 | [[image:image-20220526144110-9.png]] | |
1.3 | 60 | ||
15.2 | 61 | ||
25.2 | 62 | ||
1.2 | 63 | create device. | |
1.1 | 64 | ||
37.2 | 65 | ||
15.2 | 66 | [[image:image-20220526145059-13.png||height="559" width="1314"]] | |
1.2 | 67 | ||
15.3 | 68 | ||
13.2 | 69 | [[image:image-20220526145031-12.png]] | |
1.2 | 70 | ||
71 | |||
15.3 | 72 | [[image:image-20220526145237-14.png||height="228" width="1287"]] | |
73 | |||
74 | |||
15.2 | 75 | [[image:image-20220526145316-15.png]] | |
1.3 | 76 | ||
15.2 | 77 | ||
15.3 | 78 | ||
37.3 | 79 | ||
1.2 | 80 | The corresponding widget can be created according to the decoding of the device on TTN. | |
81 | |||
37.3 | 82 | ||
16.2 | 83 | [[image:image-20220526145459-16.png]] | |
1.2 | 84 | ||
85 | |||
17.2 | 86 | [[image:image-20220526145527-17.png]] | |
87 | |||
17.3 | 88 | ||
1.2 | 89 | ||
37.4 | 90 | = 3. Create LGT92 positioning widget = | |
91 | |||
92 | |||
1.3 | 93 | ((( | |
1.9 | 94 | ((( | |
1.2 | 95 | Creating lgt92 in TTN does not require manual creation, you directly select LGT92 in the brand. | |
1.3 | 96 | ))) | |
1.9 | 97 | ))) | |
1.2 | 98 | ||
1.3 | 99 | ((( | |
1.9 | 100 | ((( | |
1.2 | 101 | 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. | |
1.3 | 102 | ))) | |
1.9 | 103 | ))) | |
1.2 | 104 | ||
1.3 | 105 | ((( | |
37.4 | 106 | ||
107 | |||
1.9 | 108 | ((( | |
37.4 | 109 | (% style="color:red" %)**Note**: **LAQ4 is not registered in the LoRaWAN device repository, the device needs to be created manually.** | |
110 | |||
111 | |||
1.3 | 112 | ))) | |
1.9 | 113 | ))) | |
1.2 | 114 | ||
23.2 | 115 | [[image:image-20220526145723-1.png]] | |
1.2 | 116 | ||
117 | The same steps are used to create widgets and location maps. | ||
118 | |||
119 | |||
37.5 | 120 | ||
23.2 | 121 | [[image:image-20220526145753-2.png]] | |
1.2 | 122 | ||
123 | |||
37.5 | 124 | ||
23.2 | 125 | [[image:image-20220526145831-3.png]] | |
1.3 | 126 | ||
23.2 | 127 | ||
128 | [[image:image-20220526145901-4.png]] | ||
129 | |||
37.5 | 130 | ||
1.2 | 131 | LGT92 displays the walking track according to the location of the sent data packet. | |
132 | |||
133 | The device sets the time interval for sending data packets to control the positioning track. | ||
134 | |||
37.5 | 135 | ||
23.2 | 136 | [[image:image-20220526145932-5.png]] | |
1.2 | 137 | ||
23.2 | 138 | ||
1.2 | 139 | ||
37.5 | 140 | = 4. Real Time Location System demo(RTLS) = | |
1.2 | 141 | ||
37.5 | 142 | == 4.1 Introduction == | |
143 | |||
144 | |||
1.3 | 145 | ((( | |
1.5 | 146 | 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. | |
1.3 | 147 | ))) | |
1.2 | 148 | ||
1.3 | 149 | ((( | |
37.5 | 150 | You can access the application through: [[https:~~/~~/rtls.run.tago.io>>url:https://rtls.run.tago.io/]] | |
1.3 | 151 | ))) | |
1.2 | 152 | ||
1.3 | 153 | * ((( | |
154 | The user can read this document for the description of the real-time positioning system demonstration. | ||
155 | ))) | ||
1.2 | 156 | ||
1.3 | 157 | ((( | |
1.2 | 158 | [[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]] | |
24.2 | 159 | ||
37.5 | 160 | ||
24.2 | 161 | ||
1.3 | 162 | ))) | |
1.2 | 163 | ||
37.5 | 164 | == 4.2 Instructions for using LBT1 with RTLS == | |
1.2 | 165 | ||
37.5 | 166 | ||
1.4 | 167 | ((( | |
1.2 | 168 | (1)RTLS supports TTNv3 and helium servers for indoor positioning. | |
1.4 | 169 | ))) | |
1.2 | 170 | ||
1.4 | 171 | ((( | |
1.2 | 172 | (2)The user needs to register the device with LBT1 on the TTNv3 or helium server. | |
1.4 | 173 | ))) | |
1.2 | 174 | ||
1.4 | 175 | ((( | |
1.2 | 176 | (3)Then the user needs to integrate the application into Tago. | |
1.4 | 177 | ))) | |
1.2 | 178 | ||
1.4 | 179 | ((( | |
1.2 | 180 | (4)Create LBT1 devices and beacons in RTLS. Please refer to the RTLS instruction document for the specific process. | |
1.4 | 181 | ))) | |
1.2 | 182 | ||
1.4 | 183 | ((( | |
1.2 | 184 | (5)The coordinate position will be updated every time the device sends a data packet. | |
37.5 | 185 | ||
186 | |||
1.4 | 187 | ))) | |
1.2 | 188 | ||
24.2 | 189 | [[image:image-20220526150133-6.png]] | |
26.1 | 190 | ||
191 | |||
192 | |||
37.6 | 193 | = 5. Install Tago Core in LPS8v2 = | |
26.1 | 194 | ||
37.6 | 195 | ||
196 | == 5.1 Tago Core == | ||
197 | |||
198 | |||
37.8 | 199 | Tago Core is a (% style="color:blue" %)**free**(%%), (% style="color:blue" %)**fast**(%%), and (% style="color:blue" %)**open-source**(%%) IoT platform for edge computing that you can use to parse, and analyze the data from your devices! | |
26.1 | 200 | ||
37.1 | 201 | Tago Core supports all major operating systems and can be downloaded on this [[Downloads page>>https://downloads.tagocore.com/]]. | |
28.1 | 202 | ||
29.1 | 203 | For more information on Tago Core, Users can check out this [[Link>>https://tagocore.com/docs#tagocore ]]. | |
204 | |||
28.1 | 205 | Once you have downloaded and extracted TagoCore, you can run it by opening a terminal in the folder where the tagocore binary is located and typing the following command: | |
206 | |||
29.1 | 207 | ||
28.1 | 208 | (% class="box infomessage" %) | |
209 | ((( | ||
210 | wget [[https:~~/~~/downloads.tagocore.com/v0.4.1/tagocore-v0.4.1-linux-armv7.tar.gz>>https://downloads.tagocore.com/v0.4.1/tagocore-v0.4.1-linux-armv7.tar.gz]] | ||
211 | tar -xvzf tagocore-v0.4.1-linux-armv7.tar.gz | ||
212 | ))) | ||
213 | |||
214 | [[image:image-20220713185521-1.png]] | ||
215 | |||
29.1 | 216 | ||
32.1 | 217 | ||
37.6 | 218 | == 5.2 Run Tago Core == | |
32.1 | 219 | ||
37.6 | 220 | ||
221 | When you run the following command, you can access the GUI of TagoCore using the LPS8v2 gateway (% style="color:blue" %)**IP_ADDRESS:8888.** | ||
222 | |||
223 | |||
29.1 | 224 | (% class="box infomessage" %) | |
225 | ((( | ||
226 | ./tagocore start | ||
36.1 | 227 | ||
228 | ./tagocore logs | ||
29.1 | 229 | ))) | |
32.1 | 230 | ||
36.1 | 231 | [[image:image-20220713191020-2.png||height="73" width="589"]] | |
32.1 | 232 | ||
37.7 | 233 | ||
36.1 | 234 | [[image:image-20220713194013-1.png||height="246" width="558"]] | |
235 | |||
37.7 | 236 | ||
32.1 | 237 | [[image:image-20220713191539-3.png||height="538" width="938"]] | |
238 | |||
26.1 | 239 |