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