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 | |||
| 34 | = 2. Create device steps at Tago = | ||
| 35 | |||
| 36 | Take the creation of LGT92 as an example | ||
| 37 | |||
| 38 | [[image:image-20220526143953-7.png]] | ||
| 39 | |||
| 40 | Get the authorization code and fill in it. | ||
| 41 | |||
| 42 | |||
| 43 | [[image:image-20220526144034-8.png]] | ||
| 44 | |||
| 45 | |||
| 46 | All the following options require authorization. | ||
| 47 | |||
| 48 | |||
| 49 | [[image:image-20220526144110-9.png]] | ||
| 50 | |||
| 51 | |||
| 52 | create device. | ||
| 53 | |||
| 54 | [[image:image-20220526145059-13.png||height="559" width="1314"]] | ||
| 55 | |||
| 56 | |||
| 57 | [[image:image-20220526145031-12.png]] | ||
| 58 | |||
| 59 | |||
| 60 | |||
| 61 | |||
| 62 | [[image:image-20220526145237-14.png||height="228" width="1287"]] | ||
| 63 | |||
| 64 | |||
| 65 | [[image:image-20220526145316-15.png]] | ||
| 66 | |||
| 67 | |||
| 68 | |||
| 69 | The corresponding widget can be created according to the decoding of the device on TTN. | ||
| 70 | |||
| 71 | [[image:image-20220526145459-16.png]] | ||
| 72 | |||
| 73 | |||
| 74 | [[image:image-20220526145527-17.png]] | ||
| 75 | |||
| 76 | |||
| 77 | = 3. Create LGT92 positioning widget = | ||
| 78 | |||
| 79 | ((( | ||
| 80 | ((( | ||
| 81 | Creating lgt92 in TTN does not require manual creation, you directly select LGT92 in the brand. | ||
| 82 | ))) | ||
| 83 | ))) | ||
| 84 | |||
| 85 | ((( | ||
| 86 | ((( | ||
| 87 | 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. | ||
| 88 | ))) | ||
| 89 | ))) | ||
| 90 | |||
| 91 | ((( | ||
| 92 | ((( | ||
| 93 | **Note**: LAQ4 is not registered in the LoRaWAN device repository, the device needs to be created manually. | ||
| 94 | ))) | ||
| 95 | ))) | ||
| 96 | |||
| 97 | [[image:https://wiki.dragino.com/images/thumb/1/13/TAGO_IO13.png/600px-TAGO_IO13.png||alt="TAGO IO13.png" height="397" width="600"]] | ||
| 98 | |||
| 99 | The same steps are used to create widgets and location maps. | ||
| 100 | |||
| 101 | |||
| 102 | [[image:https://wiki.dragino.com/images/thumb/e/e1/TAGO_IO10.png/600px-TAGO_IO10.png||alt="TAGO IO10.png" height="329" width="600"]] | ||
| 103 | |||
| 104 | [[image:https://wiki.dragino.com/images/thumb/3/3c/TAGO_IO11.png/600px-TAGO_IO11.png||alt="TAGO IO11.png" height="334" width="600"]] | ||
| 105 | |||
| 106 | [[image:https://wiki.dragino.com/images/thumb/3/30/TAGO_IO12.png/600px-TAGO_IO12.png||alt="TAGO IO12.png" height="404" width="600"]] | ||
| 107 | |||
| 108 | LGT92 displays the walking track according to the location of the sent data packet. | ||
| 109 | |||
| 110 | The device sets the time interval for sending data packets to control the positioning track. | ||
| 111 | |||
| 112 | [[image:https://wiki.dragino.com/images/thumb/6/63/TAGO_IO14.png/600px-TAGO_IO14.png||alt="TAGO IO14.png" height="423" width="600"]] | ||
| 113 | |||
| 114 | = 4. Real Time Location System demo(RTLS) = | ||
| 115 | |||
| 116 | == 4.1 Introduction == | ||
| 117 | |||
| 118 | ((( | ||
| 119 | 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. | ||
| 120 | ))) | ||
| 121 | |||
| 122 | ((( | ||
| 123 | You can access the application through: | ||
| 124 | ))) | ||
| 125 | |||
| 126 | ((( | ||
| 127 | [[https:~~/~~/rtls.run.tago.io>>url:https://rtls.run.tago.io/]] | ||
| 128 | ))) | ||
| 129 | |||
| 130 | * ((( | ||
| 131 | The user can read this document for the description of the real-time positioning system demonstration. | ||
| 132 | ))) | ||
| 133 | |||
| 134 | ((( | ||
| 135 | [[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]] | ||
| 136 | ))) | ||
| 137 | |||
| 138 | == 4.2 Instructions for using LBT1 with RTLS == | ||
| 139 | |||
| 140 | ((( | ||
| 141 | （1）RTLS supports TTNv3 and helium servers for indoor positioning. | ||
| 142 | ))) | ||
| 143 | |||
| 144 | ((( | ||
| 145 | （2）The user needs to register the device with LBT1 on the TTNv3 or helium server. | ||
| 146 | ))) | ||
| 147 | |||
| 148 | ((( | ||
| 149 | （3）Then the user needs to integrate the application into Tago. | ||
| 150 | ))) | ||
| 151 | |||
| 152 | ((( | ||
| 153 | （4）Create LBT1 devices and beacons in RTLS. Please refer to the RTLS instruction document for the specific process. | ||
| 154 | ))) | ||
| 155 | |||
| 156 | ((( | ||
| 157 | （5）The coordinate position will be updated every time the device sends a data packet. | ||
| 158 | ))) | ||
| 159 | |||
| 160 | [[image:https://wiki.dragino.com/images/thumb/d/d7/RTLS1.png/600px-RTLS1.png||alt="RTLS1.png" height="314" width="600"]] |