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