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