Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 210.5
edited by Xiaoling
on 2023/08/07 16:19
Change comment: There is no comment for this version
To version 143.1
edited by Bei Jinggeng
on 2022/11/22 10:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png||_mstalt="293696"]]
2 +[[image:1664505654417-133.png]]
3 3  
4 4  
5 5  
... ... @@ -12,9 +12,9 @@
12 12  
13 13  
14 14  
15 -
16 16  = 1.  Introduction =
17 17  
17 +
18 18  == 1.1  What is TrackerD ==
19 19  
20 20  
... ... @@ -32,17 +32,21 @@
32 32  (((
33 33  The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
34 34  )))
35 +)))
35 35  
36 36  (((
37 37  TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
39 +
40 +
38 38  )))
39 39  
40 -[[image:image-20230213110119-1.png||height="382" width="834"]]
43 +[[image:1664499921684-770.png]]
41 41  
42 42  
43 43  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
44 44  
45 45  
49 +
46 46  == 1.2 Specifications ==
47 47  
48 48  
... ... @@ -93,10 +93,6 @@
93 93  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 94  * Tracking: max: 38mA
95 95  
96 -(% style="display:none" %)
97 -
98 -
99 -
100 100  == 1.3  Features ==
101 101  
102 102  
... ... @@ -115,10 +115,6 @@
115 115  * Tri-color LED, Alarm button
116 116  * Datalog
117 117  
118 -(% style="display:none" %)
119 -
120 -
121 -
122 122  == 1.4  Applications ==
123 123  
124 124  
... ... @@ -125,12 +125,9 @@
125 125  * Logistics and Supply Chain Management
126 126  * Human tracking
127 127  
128 -(% style="display:none" %)
129 -
130 -
131 -
132 132  = 2.  Use TrackerD =
133 133  
126 +
134 134  == 2.1 How it works? ==
135 135  
136 136  
... ... @@ -137,6 +137,7 @@
137 137  TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
138 138  
139 139  
133 +
140 140  == 2.2 Quick guide to connect to LoRaWAN server ==
141 141  
142 142  
... ... @@ -143,7 +143,7 @@
143 143  Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 
144 144  
145 145  
146 -[[image:image-20230213110214-2.png||height="388" width="847"]]
140 +[[image:1664501652064-326.png]]
147 147  
148 148  
149 149  
... ... @@ -155,7 +155,7 @@
155 155  Each TrackerD is shipped with a sticker with the default device EUI as below:
156 156  
157 157  
158 -[[image:image-20230426085815-1.png||height="259" width="558"]]
152 +[[image:1664501677253-891.png]]
159 159  
160 160  
161 161  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -164,14 +164,14 @@
164 164  **__Add APP EUI in the application:__**
165 165  
166 166  
167 -[[image:1664501711466-918.png||_mstalt="295828"]]
161 +[[image:1664501711466-918.png]]
168 168  
169 169  
170 170  
171 -[[image:1664501721248-725.png||_mstalt="294450"]]
165 +[[image:1664501721248-725.png]]
172 172  
173 173  
174 -[[image:1664501734705-405.png||_mstalt="293306"]]
168 +[[image:1664501734705-405.png]]
175 175  
176 176  
177 177  
... ... @@ -178,20 +178,21 @@
178 178  **__Add APP KEY and DEV EUI:__**
179 179  
180 180  
181 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
175 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
182 182  
183 183  
184 184  
185 185  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
186 186  
187 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
181 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
188 188  
189 -[[image:1664502835802-546.png||_mstalt="295061"]]
183 +[[image:1664502835802-546.png]]
190 190  
191 191  
192 192  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
193 193  
194 194  
189 +
195 195  == 2.3  Positioning Mode(SMOD) ==
196 196  
197 197  
... ... @@ -204,21 +204,23 @@
204 204  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
205 205  
206 206  
202 +
207 207  == 2.4  Uplink Payload ==
208 208  
205 +
209 209  === 2.4.1 Uplink FPORT~=5, Device Status ===
210 210  
211 211  
212 -Uplink the device configures with (% style="color:blue" %)**FPORT=5**(%%). Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.
209 +Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.
213 213  
214 -Use can also get the Device Status uplink through the downlink command: (% style="color:#037691" %)**Downlink:  0x2301**
211 +Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
215 215  
216 216  
217 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:440px" %)
218 -|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**Size(bytes)**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 30px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1
219 -|(% style="width:108px" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
214 +(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
215 +|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
216 +|=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
220 220  
221 -[[image:1665301570342-765.png||_mstalt="294580"]]
218 +[[image:1665301570342-765.png]]
222 222  
223 223  
224 224  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -229,30 +229,31 @@
229 229  
230 230  (% style="color:#037691" %)**Frequency Band**:
231 231  
232 -0x01: EU868
229 +*0x01: EU868
233 233  
234 -0x02: US915
231 +*0x02: US915
235 235  
236 -0x03: IN865
233 +*0x03: IN865
237 237  
238 -0x04: AU915
235 +*0x04: AU915
239 239  
240 -0x05: KZ865
237 +*0x05: KZ865
241 241  
242 -0x06: RU864
239 +*0x06: RU864
243 243  
244 -0x07: AS923
241 +*0x07: AS923
245 245  
246 -0x08: AS923-1
243 +*0x08: AS923-1
247 247  
248 -0x09: AS923-2
245 +*0x09: AS923-2
249 249  
250 -0x0a: AS923-3
247 +*0x0a: AS923-3
251 251  
252 -(% style="color:#037691" %)**Sub-Band:**(%%) value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
249 +Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
253 253  
254 254  (% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
255 255  
253 +
256 256  (% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
257 257  
258 258  Use can also get the Device Status uplink through the downlink command:
... ... @@ -260,9 +260,9 @@
260 260  
261 261  (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
262 262  
263 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:270px" %)
264 -|(% style="width:60px" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)2 bits|(% style="width:80px" %)4 bits
265 -|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
261 +(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
262 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
263 +|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
266 266  
267 267  (% style="color:blue" %)** SMOD：**
268 268  
... ... @@ -284,48 +284,47 @@
284 284  
285 285  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
286 286  
287 -(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
285 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
288 288  
289 289  
290 290  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
291 291  
292 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:413px" %)
293 -|(% style="width:77px" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:88px" %)1 Bit|(% style="width:50px" %)1 Bit|(% style="width:128px" %)1 Bit
294 -|(% style="width:75px" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
290 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
291 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
292 +|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
295 295  
296 -(% style="display:none" %)
297 -
298 -
299 -
300 300  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
301 301  
302 302  
303 -Users can use (% style="color:blue" %)**AT+SMOD=1,0,0**(%%) to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
297 +Users can use **AT+SMOD=1,0,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
304 304  
305 305  
306 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:320px" %)
307 -|(% style="width:60px" %)**Size(bytes)**|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)2|(% style="width:30px" %)2
308 -|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
300 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
301 +|=(% scope="row" style="width: 60px;" %)(((
302 +**Size(bytes)**
303 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
304 +2
305 +)))|(% style="width:30px" %)(((
306 +2
307 +)))
308 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
309 309  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
310 310  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
311 311  
312 -[[image:1665301636888-168.png||_mstalt="298012"]]
312 +[[image:1665301636888-168.png]]
313 313  
314 314  
315 315  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
316 316  
317 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:321px" %)
318 -|(% style="width:60px" %)**Size(bit)**|(% style="width:60px" %)1 bit|(% style="width:134px" %)1 bit|(% style="width:67px" %)14 bits
319 -|(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:114px" %)Alarm Indicate|(% style="width:62px" %)[[BAT>>||anchor="HBAT:"]] 
317 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
318 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
319 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
320 320  
321 -(% style="display:none" %)
322 -
323 -
324 324  ==== (% style="color:blue" %)**FLAG:**(%%) ====
325 325  
326 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:184px" %)
327 -|(% style="width:68px" %)**Size(bit)**|(% style="width:61px" %)2 bits|(% style="width:55px" %)1 bit
328 -|(% style="width:79px" %)**Value**|(% style="width:56px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:50px" %)[[LON>>||anchor="HLON:"]]
323 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
324 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
325 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
329 329  
330 330  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
331 331  
... ... @@ -342,12 +342,12 @@
342 342  2.  In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
343 343  
344 344  
345 -[[image:1664502116362-706.png||_mstalt="293306"]]
342 +[[image:1664502116362-706.png]]
346 346  
347 347  
348 348  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
349 349  
350 -[[image:1664502166010-515.png||_mstalt="291395"]]
347 +[[image:1664502166010-515.png]]
351 351  
352 352  
353 353  
... ... @@ -370,9 +370,6 @@
370 370  * 3.40v ~~ 3.69v:  20% ~~ 40%
371 371  * < 3.39v:  0~~20%
372 372  
373 -(% style="display:none" %) (%%)
374 -
375 -
376 376  ==== (% style="color:blue" %)**MOD:**(%%) ====
377 377  
378 378  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -413,26 +413,30 @@
413 413  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
414 414  
415 415  
410 +
416 416  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
417 417  
418 418  
419 -The default uplink payload includes total 11 bytes ((% style="color:blue" %)**AT+SMOD=1,1,0**(%%)). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
414 +The default uplink payload includes total 11 bytes (**AT+SMOD=1,1,0**). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
420 420  
421 421  
422 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:300px" %)
423 -|(% style="width:60px" %)**Size(bytes)**|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:70px" %)2|(% style="width:50px" %)1
424 -|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
417 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
418 +|=(% scope="row" style="width: 60px;" %)(((
419 +**Size(bytes)**
420 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
421 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
425 425  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
426 426  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
427 427  
428 428  (% class="wikigeneratedid" %)
429 -[[image:1665301687277-443.png||_mstalt="296140"]]
426 +[[image:1665301687277-443.png]]
430 430  
431 431  
429 +
432 432  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
433 433  
434 434  
435 -Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
433 +Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
436 436  
437 437  
438 438  (% style="color:red" %)**Note for this mode:**
... ... @@ -443,13 +443,16 @@
443 443  
444 444  The payload is 15 bytes, as below.
445 445  
446 -(% border="1" style="background-color:#f2f2f2; width:500px" %)
447 -|**Size(bytes)**|4|4|2|1|1|1|1|1
448 -|**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
444 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
445 +|=(% scope="row" %)(((
446 +**Size(bytes)**
447 +)))|4|4|2|1|1|1|1|1
448 +|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
449 449  
450 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
450 +[[image:image-20221009160309-2.png]]
451 451  
452 452  
453 +
453 453  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
454 454  
455 455  
... ... @@ -458,9 +458,11 @@
458 458  User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
459 459  
460 460  
461 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
462 -|(% style="width:60px" %)**Size(bytes)**|(% style="width:30px" %)16|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:120px" %)2|(% style="width:50px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1
463 -|(% style="width:50px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
462 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
463 +|=(% scope="row" style="width: 60px;" %)(((
464 +**Size(bytes)**
465 +)))|(% style="width:30px" %)16|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:120px" %)2|(% style="width:50px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1
466 +|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
464 464  iBeacon MAJOR
465 465  )))|(% style="width:63px" %)(((
466 466  iBeacon MINOR
... ... @@ -472,7 +472,7 @@
472 472  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
473 473  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
474 474  
475 -[[image:1664502425687-834.png||_mstalt="296738"]]
478 +[[image:1664502425687-834.png]]
476 476  
477 477  
478 478  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -483,44 +483,22 @@
483 483  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
484 484  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
485 485  
486 -(% style="display:none" %) (%%)
489 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
487 487  
488 -=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
489 489  
490 -
491 -The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
492 -
493 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:284.818px" %)
494 -|(% style="width:97px" %)**Size(bytes)**|(% style="width:103px" %)2|(% style="width:81px" %)1
495 -|(% style="width:97px" %)**Value**|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon
496 -
497 - [[image:image-20230302145315-1.png]]
498 -
499 -**alarm**=(bytes[0] & 0x40)  ~/~/ Alarm status
500 -
501 -**batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
502 -
503 -**mod** = bytes[2] & 0xC0;
504 -
505 -**Lon**=(bytes[2] & 0x20)
506 -
507 -
508 -=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
509 -
510 -
511 511  TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
512 512  
513 513  
514 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
515 -|(% style="width:65px" %)(((
495 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
496 +|=(% scope="row" style="width: 60px;" %)(((
516 516  **Size(bytes)**
517 -)))|(% style="width:50px" %)6|(% style="width:50px" %)4|(% style="width:133px" %)2|(% style="width:50px" %)1
518 -|(% style="width:69px" %)**Value**|(% style="width:48px" %)SSID|(% style="width:48px" %)RSSI|(% style="width:103px" %)(((
498 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
499 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
519 519  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
520 -)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]
501 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
521 521  
522 522  (% class="wikigeneratedid" %)
523 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
504 +[[image:1667288597595-714.png||height="212" width="1151"]]
524 524  
525 525  
526 526  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -527,27 +527,27 @@
527 527  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
528 528  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
529 529  
530 -(% style="display:none" %) (%%)
511 +=== 2.4.7  Add Payload format in TTN V3 ===
531 531  
532 -=== 2.4.8  Add Payload format in TTN V3 ===
533 533  
534 -
535 535  In TTN V3, user can add a custom payload so it shows friendly.
536 536  
537 537  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
538 538  
539 539  
540 -[[image:1664502649601-895.png||_mstalt="296985"]]
519 +[[image:1664502649601-895.png]]
541 541  
542 542  
522 +Add the decoder from this link: 
543 543  
544 -Add the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
524 +[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
545 545  
546 546  Save the change the uplink message will be parsed. As below:
547 547  
548 -[[image:1664502676891-606.png||_mstalt="296673"]]
528 +[[image:1664502676891-606.png]]
549 549  
550 550  
531 +
551 551  == 2.5 Integrate with Datacake ==
552 552  
553 553  
... ... @@ -556,9 +556,10 @@
556 556  Instruction is here:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example~~-~~-AddTrackerDGPSTrackingInDataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example--AddTrackerDGPSTrackingInDataCake]]
557 557  
558 558  
559 -[[image:1664502695771-538.png||_mstalt="297349"]]
540 +[[image:1664502695771-538.png]]
560 560  
561 561  
543 +
562 562  == 2.6 Integrate with Tago ==
563 563  
564 564  
... ... @@ -567,70 +567,31 @@
567 567  Instruction is here: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget]]
568 568  
569 569  
570 -[[image:1664502715371-321.png||_mstalt="292162"]]
552 +[[image:1664502715371-321.png]]
571 571  
572 572  
573 -== 2.7  Integrate with Node-red ==
574 574  
556 +== 2.7  Datalog Feature ==
575 575  
576 -~1. Install node-red, please refer to the installation method in the link:
577 577  
578 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
579 -
580 -
581 -2. Import the created flow template, please refer to the import method in the link:
582 -
583 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
584 -
585 -
586 -The address of the flow template: [[dragino-end-node-decoder/TrackerD.json at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/TrackerD.json]]
587 -
588 -(% style="color:red" %)**Note: If you are using NODE-RED for the first time, please search and install the two plug-ins in the figure below in node-red to fully use the flow template.**
589 -
590 -[[image:image-20230307135914-1.png||height="527" width="1045"]]
591 -
592 -
593 -[[image:image-20230307135932-2.png||height="527" width="1044"]]
594 -
595 -
596 -3. Display the map
597 - Enter the link to the map:
598 -
599 - Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
600 -
601 -**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
602 -
603 -
604 - Hit all input in input stream
605 -
606 - [[image:image-20230308115616-2.png||height="563" width="1070"]]
607 -
608 -
609 - View map again
610 -
611 -[[image:image-20230308115701-3.png||height="571" width="1085"]]
612 -
613 -
614 -== 2.8  Datalog Feature ==
615 -
616 -
617 617  total 273 entries,by default,
618 618  
619 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
561 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
620 620  
621 621  Example use case.
622 622  
623 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
565 +[[image:image-20221009234703-2.png||height="328" width="899"]]
624 624  
625 625  
626 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
568 +[[image:image-20221009234629-1.png||height="390" width="577"]]
627 627  
628 628  
629 -== 2.9  Alarm Mode ==
630 630  
572 +== 2.8 Alarm Mode ==
631 631  
574 +
632 632  (((
633 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. Alarm Mode is used to send SOS info to IoT platform.
576 +User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
634 634  )))
635 635  
636 636  
... ... @@ -640,7 +640,7 @@
640 640  
641 641  
642 642  (((
643 -**Two ways to exit alarm mode:**
586 +Two ways to exit alarm mode:
644 644  )))
645 645  
646 646  * Server sends a downlink command to exit.
... ... @@ -651,24 +651,19 @@
651 651  )))
652 652  
653 653  
654 -== 2.10  Transport Mode ==
655 655  
598 +== 2.9 Transport Mode ==
656 656  
657 -In Transport Mode, TrackerD will check if there is motion (threldhold defined by **[[PT)>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** . If there is no motion, device will send uplinks every 20 minutes (Defined by **[[TDC)>>||anchor="H3.2.1SetTransmitInterval"]]** . If there is motion, device will send uplink every 5 minutes(defined by **[[MTDC)>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]**.
658 658  
659 -When device is set in Transport Mode, it will uplink more frequenctly during moving.
601 +In Transport Mode, TrackerD will check if there is motion. If there is no motion, device will send uplinks every 20 minutes. If there is motion, device will send uplink every 5 minutes.
660 660  
661 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
662 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
663 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
664 664  
665 -(% style="display:none" %) (%%)
666 666  
667 -== 2.11  LED Status ==
605 +== 2.10 LED Status ==
668 668  
669 669  
670 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:500px" %)
671 -|=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**Event**|=(% style="width: 200px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**AT+LON to control on/off**
608 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
609 +|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
672 672  |(% style="width:157px" %)**Power On**|(% style="width:271px" %)(% style="color:blue" %)**BLUE, **(% style="color:red" %)**RED , **(% style="color:green" %)**Green** flash once|(% style="width:202px" %)N/A
673 673  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
674 674  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
... ... @@ -681,14 +681,12 @@
681 681  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
682 682  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
683 683  
684 -(% style="display:none" %) (%%)
622 +== 2.11 Button Function ==
685 685  
686 -== 2.12  Button Function ==
687 687  
688 -
689 689  (% style="color:blue" %)**RESET button:**
690 690  
691 -[[image:1664502835802-546.png||_mstalt="295061"]]
627 +[[image:1664502835802-546.png]]
692 692  
693 693  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
694 694  
... ... @@ -695,21 +695,18 @@
695 695  
696 696  (% style="color:red" %)**RED button:**
697 697  
698 -[[image:image-20230213110506-3.png]](% style="display:none" %)
634 +[[image:1664502854406-763.png]]
699 699  
700 -(% style="display:none" %) (%%)
701 701  
702 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
703 -|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Description**
637 +(% border="1" style="background-color:#ffffcc; width:510px" %)
638 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
704 704  |(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.8AlarmMode"]]
705 705  |(% style="width:135px" %)Exit Alarm Mode|(% style="width:220px" %)Fast press the (% style="color:red" %)**RED** (%%)button 10 times|(% style="width:265px" %)Exit Alarm Mode
706 706  |(% style="width:135px" %)Enter Deep Sleep Mode|(% style="width:220px" %)Press and hold the button for 10 seconds, then quickly press the device 3 times to enter deep sleep|(% style="width:265px" %)This is the mode ship out from factory. CPU will be complete in sleep mode and no LoRa activity, only use before deploy.
707 707  
708 -(% style="display:none" %) (%%)
643 +== 2.12 USB Port Function ==
709 709  
710 -== 2.13  USB Port Function ==
711 711  
712 -
713 713  The USB interface of TrackerD has below functions:
714 714  
715 715  * Power on the device
... ... @@ -717,18 +717,6 @@
717 717  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
718 718  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
719 719  
720 -(% style="display:none" %) (%%)
721 -
722 -== 2.14  Sleep Mode ==
723 -
724 -
725 -(% style="color:blue" %)**Sleep Mode:**(%%) To prevent accidental touch of the red button during transportation or assembly, so the peripherals of the device are turned off and enter deep sleep.
726 -
727 -In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
728 -
729 -Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
730 -
731 -
732 732  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
733 733  
734 734  
... ... @@ -737,6 +737,7 @@
737 737  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
738 738  
739 739  
661 +
740 740  == 3.1 Access AT Command ==
741 741  
742 742  
... ... @@ -743,24 +743,25 @@
743 743  TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below.
744 744  
745 745  
746 -[[image:1664502999401-486.png||_mstalt="296985"]]
668 +[[image:1664502999401-486.png]]
747 747  
748 748  
749 749  In PC, User needs to set serial tool baud rate to (% style="color:green" %)**115200**(%%) to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
750 750  
751 751  
752 -[[image:1664503022490-662.png||_mstalt="293332"]]
674 +[[image:1664503022490-662.png]]
753 753  
754 754  
755 -[[image:1664503035713-500.png||_mstalt="291096"]]
677 +[[image:1664503035713-500.png]]
756 756  
757 757  
758 -[[image:1664503047675-651.png||_mstalt="295386"]]
680 +[[image:1664503047675-651.png]]
759 759  
760 -(% style="display:none" %) (%%)
761 761  
683 +
762 762  == 3.2 Command Set ==
763 763  
686 +
764 764  === 3.2.1 Set Transmit Interval ===
765 765  
766 766  
... ... @@ -778,6 +778,7 @@
778 778  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
779 779  
780 780  
704 +
781 781  === 3.2.2 Set Alarm Packet transmission interval ===
782 782  
783 783  
... ... @@ -795,6 +795,7 @@
795 795  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
796 796  
797 797  
722 +
798 798  === 3.2.3 Set Transport Mode Packet transmission interval ===
799 799  
800 800  
... ... @@ -812,6 +812,7 @@
812 812  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
813 813  
814 814  
740 +
815 815  === 3.2.4 Exit Alarm ===
816 816  
817 817  
... ... @@ -824,9 +824,10 @@
824 824  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
825 825  
826 826  
827 -=== 3.2.5 Disable/Enable LED flash and buzzer ===
828 828  
754 +=== 3.2.5 Disable/Enable LED flash ===
829 829  
756 +
830 830  Disable/Enable LED for position, downlink and uplink
831 831  
832 832  * (% style="color:blue" %)**AT Command:**
... ... @@ -841,6 +841,7 @@
841 841  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
842 842  
843 843  
771 +
844 844  === 3.2.6 Disable/Enable Transport Mode ===
845 845  
846 846  
... ... @@ -858,6 +858,7 @@
858 858  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
859 859  
860 860  
789 +
861 861  === 3.2.7 Set Positioning Mode ===
862 862  
863 863  
... ... @@ -884,9 +884,9 @@
884 884  
885 885  (% style="color:#037691" %)**cc:   **
886 886  
887 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
816 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
888 888  
889 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
818 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
890 890  
891 891  (% style="color:blue" %)**Example:**
892 892  
... ... @@ -904,6 +904,7 @@
904 904  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
905 905  
906 906  
836 +
907 907  === 3.2.8 Set MAX GPS position time ===
908 908  
909 909  
... ... @@ -910,7 +910,7 @@
910 910  Set max positioning time, default is 150 seconds. TrackerD will try to get location info within this period. If fail to get position data within this time, TrackerD will use 000000 for latitude and longitude.
911 911  
912 912  
913 -If **AT+FTIME=0**. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
843 +If AT+FTIME=0. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
914 914  
915 915  
916 916  * (% style="color:blue" %)**AT Command:**
... ... @@ -925,6 +925,7 @@
925 925  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
926 926  
927 927  
858 +
928 928  === 3.2.9 Set PDOP value for GPS fix accuracy ===
929 929  
930 930  
... ... @@ -948,8 +948,8 @@
948 948  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
949 949  
950 950  
951 -=== 3.2.10 Disable/Enable the confirmation mode ===
952 952  
883 +Disable/Enable the confirmation mode
953 953  
954 954  * (% style="color:blue" %)**AT Command:**
955 955  
... ... @@ -968,9 +968,10 @@
968 968  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
969 969  
970 970  
971 -=== 3.2.11  Auto Send None-ACK messages ===
972 972  
903 +=== 3.2.10  Auto Send None-ACK messages ===
973 973  
905 +
974 974  TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
975 975  
976 976  
... ... @@ -986,12 +986,13 @@
986 986  
987 987  * (% style="color:blue" %)**Downlink Command: 0x34**
988 988  
989 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
921 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
990 990  
991 991  
992 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
993 993  
925 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
994 994  
927 +
995 995  BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
996 996  
997 997  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -998,18 +998,19 @@
998 998  
999 999  (% style="color:blue" %)**AT Command:**
1000 1000  
1001 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
934 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
1002 1002  
1003 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
936 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
1004 1004  
1005 1005  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
1006 1006  
1007 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
940 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
1008 1008  
1009 1009  
1010 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
1011 1011  
944 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
1012 1012  
946 +
1013 1013  WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
1014 1014  
1015 1015  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -1016,158 +1016,44 @@
1016 1016  
1017 1017  (% style="color:blue" %)**AT Command:**
1018 1018  
1019 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
953 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1020 1020  
1021 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
955 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1022 1022  
1023 1023  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
1024 1024  
1025 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
959 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
1026 1026  
1027 1027  
1028 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
1029 1029  
963 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
1030 1030  
965 +
1031 1031  Users can use this feature to enable/disable Information printing.
1032 1032  
1033 1033  (% style="color:blue" %)**AT Command:**
1034 1034  
1035 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
970 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
1036 1036  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1037 1037  
1038 1038  
1039 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1040 1040  
975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1041 1041  
977 +
1042 1042  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
1043 1043  
1044 1044  (% style="color:blue" %)**AT Command:**
1045 1045  
1046 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
982 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1047 1047  
1048 1048  
1049 1049  (% style="color:blue" %)**Downlink Payload:0X24**
1050 1050  
1051 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
987 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
1052 1052  
1053 1053  
1054 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1055 1055  
1056 -
1057 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1058 -
1059 -(% style="color:blue" %)**AT Command:**
1060 -
1061 -(% style="color:#037691" %)**AT+PT=xx**
1062 -
1063 - Example:
1064 -
1065 - AT+PT=14    ~-~->    Set to detect car motion.
1066 -
1067 - AT+PT=41  ~-~->    set to detect walk motion.
1068 -
1069 -
1070 -(% style="color:blue" %)**Downlink Payload:0xB4**
1071 -
1072 -0xB4 14          ~/~/  Same as AT+PT=14
1073 -
1074 -
1075 -=== 3.2.17  Set AT command window time（Since firmware 1.4.5） ===
1076 -
1077 -
1078 -AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
1079 -
1080 -(% style="color:blue" %)**AT Command:**
1081 -
1082 -(% style="color:#037691" %)**AT+ATST=XX**
1083 -
1084 - Example:
1085 -
1086 - AT+ATST=15    ~-~-> Set the time to 15 seconds
1087 -
1088 -(% style="color:blue" %)**Downlink Payload:0XB5**
1089 -
1090 -0xB5 0F          ~/~/  Same as AT+ATST=15
1091 -
1092 -
1093 -=== 3.2.18  Set the stepmeter mode（Since firmware 1.4.5） ===
1094 -
1095 -
1096 -After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
1097 -
1098 -(% style="color:blue" %)**AT Command:**
1099 -
1100 -(% style="color:#037691" %)**AT+PM=xx**
1101 -
1102 - Example:
1103 -
1104 - AT+PM=1    ~-~->  Turn on step counting mode
1105 -
1106 -AT+PM=0    ~-~->  Turn OFF step counting mode
1107 -
1108 -(% style="color:blue" %)**Downlink Payload:0XB6**
1109 -
1110 -0xB6 01          ~/~/  Same as AT+PM=1
1111 -
1112 -
1113 -=== 3.2.19  Set down the decline detection mode（Since firmware 1.4.5） ===
1114 -
1115 -
1116 -This mode is used in conjunction with AT+PT(The recommended threshold is between 50 and 70, you need to set it according to the environment yourself). This function is used in hospitals, nursing homes, nursing homes and other places to prevent the elderly and patients from falling. No one knows.
1117 -
1118 -(% style="color:blue" %)**AT Command:**
1119 -
1120 -(% style="color:#037691" %)**AT+FD=xx**
1121 -
1122 - Example:
1123 -
1124 - AT+FD=1    ~-~->  Turn on the Fall detection
1125 -
1126 -AT+FD=0    ~-~->  Turn OFF the Fall detection
1127 -
1128 -(% style="color:blue" %)**Downlink Payload:0XB7**
1129 -
1130 -0xB7 01          ~/~/  Same as AT+FD=1
1131 -
1132 -
1133 -=== 3.2.20 Disable/Enable buzzer（Since firmware 1.4.6） ===
1134 -
1135 -
1136 -Disable/Enable buzzer for Alarm, downlink and uplink
1137 -
1138 -(% style="color:blue" %)**AT Command:**
1139 -
1140 -(% style="color:#037691" %)**AT+BEEP=XX**
1141 -
1142 - Example:
1143 -
1144 -AT+BEEP=1 ~-~-> Turn on the buzzer
1145 -
1146 -AT+BEEP=0 ~-~-> Turn OFF the buzzer
1147 -
1148 -(% style="color:blue" %)**Downlink Payload:0XB9**
1149 -
1150 -0xB9 01 ~/~/ Same as AT+BEEP=1
1151 -
1152 -
1153 -=== 3.2.21 Set long press time（Since firmware 1.4.6） ===
1154 -
1155 -
1156 -When using the red button Changan to alarm, press and hold the time to set 0~~10 seconds, which is convenient for use scenarios.
1157 -
1158 -(% style="color:blue" %)**AT Command:**
1159 -
1160 -(% style="color:#037691" %)**AT+EAT=XX**
1161 -
1162 - Example:
1163 -
1164 -AT+EAT=2 ~-~-> Set the long press time to 2s
1165 -
1166 -(% style="color:blue" %)**Downlink Payload:0XBA**
1167 -
1168 -0xBA 02 ~/~/ Same as AT+EAT=2
1169 -
1170 -
1171 1171  = 4. Setting for Different Scenarios =
1172 1172  
1173 1173  
... ... @@ -1174,6 +1174,7 @@
1174 1174  
1175 1175  = 5. Upload Firmware =
1176 1176  
997 +
1177 1177  == 5.1 Firmware Change Log ==
1178 1178  
1179 1179  
... ... @@ -1180,6 +1180,7 @@
1180 1180  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1181 1181  
1182 1182  
1004 +
1183 1183  == 5.2 How to upgrade firmware ==
1184 1184  
1185 1185  
... ... @@ -1200,10 +1200,10 @@
1200 1200  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1201 1201  
1202 1202  
1203 -[[image:1664503563660-578.png||_mstalt="296777"]]
1025 +[[image:1664503563660-578.png]]
1204 1204  
1205 1205  
1206 -[[image:1664503574618-659.png||_mstalt="297986"]]
1028 +[[image:1664503574618-659.png]]
1207 1207  
1208 1208  
1209 1209  
... ... @@ -1212,7 +1212,7 @@
1212 1212  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1213 1213  
1214 1214  
1215 -**Users need to use below files:**
1037 +Users need to use below files:
1216 1216  
1217 1217  boot_app0.bin @0e000
1218 1218  
... ... @@ -1219,19 +1219,22 @@
1219 1219  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1220 1220  
1221 1221  
1222 -[[image:image-20221207120501-1.png]]
1044 +[[image:image-20221118105220-2.png]]
1223 1223  
1224 1224  
1225 1225  
1226 1226  After upgrade finish, it will show finish as below:
1227 1227  
1228 -[[image:image-20221207133911-7.png]]
1050 +[[image:image-20221118105402-4.png]]
1229 1229  
1230 1230  
1053 +
1231 1231  = 6. Developer Guide =
1232 1232  
1056 +
1233 1233  == 6.1 Compile Source Code ==
1234 1234  
1059 +
1235 1235  === 6.1.1 Set up ARDUINO compile environment ===
1236 1236  
1237 1237  
... ... @@ -1240,81 +1240,24 @@
1240 1240  Install IDE on PC, open and click (% style="color:#037691" %)**File ~-~-> Preference**,(%%) add the following URL:  [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]]
1241 1241  
1242 1242  
1243 -[[image:1664503635019-941.png||_mstalt="294658"]]
1068 +[[image:1664503635019-941.png]]
1244 1244  
1245 1245  
1246 1246  
1247 1247  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1248 1248  
1249 -[[image:1664503715811-892.png||_mstalt="295698"]]
1074 +[[image:1664503715811-892.png]]
1250 1250  
1251 1251  
1252 -=== 6.1.2  Build the development environment ===
1253 -
1254 -
1255 -**~1. Download and install arduino IDE**
1256 -
1257 -[[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]]
1258 -
1259 -
1260 -**2. Download the ESP32 development package in the arduino IDE**
1261 -
1262 -[[image:image-20221213100007-1.png]]
1263 -
1264 -
1265 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1266 -
1267 -[[image:image-20221213100626-2.png]]
1268 -
1269 -
1270 -Restart the IDE after the addition is complete, then:
1271 -
1272 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1273 -
1274 -
1275 -[[image:image-20221213101040-4.png]]
1276 -
1277 -
1278 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1279 -Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)**
1280 -
1281 -
1282 -Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import:
1283 -
1284 -(% style="color:blue" %)**Methods as below:**
1285 -
1286 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1287 -
1288 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1289 -
1290 1290  (% id="cke_bm_4554S" style="display:none" %) (%%)Find the path of SP32 installation, find the file as shown in Figure 1, and change the SPI pin to the shown in Figure 2.
1291 1291  
1292 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1079 +[[image:image-20221024105643-1.png]]
1293 1293  
1294 -
1295 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1296 -
1297 -[[image:image-20221213102334-6.png]]
1298 -
1299 -(% style="color:red" %)**Note: This step requires a python environment**
1300 -
1301 -
1302 -Either way, in the end:
1303 -
1304 -The final effect is to open the arduino and you can see the esp32
1305 -
1306 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1307 -
1308 -
1309 -
1310 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1311 -
1312 1312  **~ Figure1**
1313 1313  
1314 1314  
1084 +[[image:image-20221024105643-2.png]]
1315 1315  
1316 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1317 -
1318 1318   **Figure2**
1319 1319  
1320 1320  
... ... @@ -1323,31 +1323,34 @@
1323 1323  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1324 1324  
1325 1325  
1326 -[[image:1664503752288-974.png||_mstalt="298194"]]
1094 +[[image:1664503752288-974.png]]
1327 1327  
1328 1328  
1097 +
1329 1329  == 6.2 Source Code ==
1330 1330  
1331 1331  
1332 1332  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1333 1333  
1334 -[[image:1664503794261-827.png||_mstalt="296387"]]
1103 +[[image:1664503794261-827.png]]
1335 1335  
1336 1336  
1337 1337  
1338 1338  * (% style="color:blue" %)**Click to upload**
1339 1339  
1340 -[[image:1664503808294-336.png||_mstalt="295711"]]
1109 +[[image:1664503808294-336.png]]
1341 1341  
1342 1342  
1343 1343  
1344 1344  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1345 1345  
1346 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1347 1347  
1348 1348  
1118 +
1349 1349  = 7.  FAQ =
1350 1350  
1121 +
1351 1351  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1352 1352  
1353 1353  
... ... @@ -1354,15 +1354,16 @@
1354 1354  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1355 1355  
1356 1356  
1128 +
1357 1357  == 7.2 What is the pin mapping for the USB program cable? ==
1358 1358  
1359 1359  
1360 -[[image:1664499635206-262.png||_mstalt="295360"]]
1132 +[[image:1664499635206-262.png]]
1361 1361  
1362 1362  
1363 1363  
1364 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:314px" %)
1365 -|=(% style="width: 120px;background-color:#D9E2F3;color:#0070C0" %)**Pin**|=(% style="width: 69px;background-color:#D9E2F3;color:#0070C0" %)**Color**|=(% style="width: 125px;background-color:#D9E2F3;color:#0070C0" %)**USB Pin**
1136 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
1137 +|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
1366 1366  |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1367 1367  |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1368 1368  |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
... ... @@ -1372,11 +1372,9 @@
1372 1372  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1373 1373  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1374 1374  
1375 -(% style="display:none" %) (%%)
1376 -
1377 -
1378 1378  == 7.3 Notes on using different serial port tools for TrackerD ==
1379 1379  
1149 +
1380 1380  === 7.3.1  Serial port utility ===
1381 1381  
1382 1382  
... ... @@ -1384,16 +1384,18 @@
1384 1384  
1385 1385  Need to adjust the data stream to RTS/CTS on physical restart.
1386 1386  
1157 +
1387 1387  (% class="wikigeneratedid" %)
1388 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1159 +[[image:image-20221102140621-1.png]]
1389 1389  
1390 1390  
1391 -
1392 1392  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1393 1393  
1394 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1395 1395  
1165 +[[image:image-20221102140638-2.png]]
1396 1396  
1167 +
1168 +
1397 1397  === 7.3.2  SecureCRT ===
1398 1398  
1399 1399  
... ... @@ -1400,22 +1400,23 @@
1400 1400  The default command window of SecureCRT is not displayed. Entering a command requires a complete input of the entire command. You can open the command window in the view.
1401 1401  
1402 1402  
1403 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1175 +[[image:image-20221102140704-3.png]]
1404 1404  
1405 1405  
1406 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1178 +[[image:image-20221102140712-4.png]]
1407 1407  
1408 1408  
1181 +
1409 1409  === 7.3.3  PUTTY ===
1410 1410  
1411 1411  
1412 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1185 +[[image:image-20221102140748-5.png]]
1413 1413  
1414 1414  
1415 1415  Since putty does not have a command window, you need to fill in the complete command externally, and then copy it to putty.The information copied outside can be pasted by right-clicking the mouse in putty.
1416 1416  
1417 1417  
1418 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1191 +[[image:image-20221102140801-6.png]]
1419 1419  
1420 1420  
1421 1421  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1427,58 +1427,38 @@
1427 1427  See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1428 1428  )))
1429 1429  
1430 -**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1203 +1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
1431 1431  
1205 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1432 1432  
1433 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1207 +2.Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
1434 1434  
1209 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1435 1435  
1211 +3.Compile the AS923_JP band, please refer to the intention shown
1436 1436  
1437 -**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1213 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1438 1438  
1215 +4.In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below.
1439 1439  
1440 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1217 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1441 1441  
1219 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1442 1442  
1443 1443  
1444 -**3. Compile the AS923_JP band, please refer to the intention shown**
1445 1445  
1446 -
1447 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1448 -
1449 -
1450 -
1451 -**4. In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below.**
1452 -
1453 -
1454 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1455 -
1456 -
1457 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1458 -
1459 -
1460 -== 7.5 Are there example python example for BLE Indoor Positioning? ==
1461 -
1462 -
1463 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1464 -
1465 -
1466 -== 7.6 Can alert mode and transport mode be used together? ==
1467 -
1468 -
1469 -Yes, you can also press the panic button to sound the alarm if set to transport mode
1470 -
1471 -
1472 1472  = 8  Trouble Shooting =
1473 1473  
1225 +
1474 1474  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1475 1475  
1476 1476  
1477 1477  (((
1478 -Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**AT+INTWK=1**(%%)), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1230 +Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1479 1479  )))
1480 1480  
1481 1481  
1234 +
1482 1482  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1483 1483  
1484 1484  
... ... @@ -1487,152 +1487,85 @@
1487 1487  )))
1488 1488  
1489 1489  
1243 +
1490 1490  == 8.3  Problem after Upgrading Firmware ==
1491 1491  
1492 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1246 +=== 8.3.1 Continue Restart after upgrading ===
1493 1493  
1494 1494  
1495 -**Error Output**
1496 -
1497 -
1498 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1499 -
1500 -
1501 1501  (((
1502 -Some partition is missed during upgrade, please upgrade below four files as example:
1503 -
1504 -[[image:image-20221207120524-2.png]]
1250 +If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1505 1505  )))
1506 1506  
1507 1507  
1508 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1254 +[[image:image-20221118105249-3.png]]
1509 1509  
1510 1510  
1257 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1258 +
1511 1511  It is because the partitions are different when upgrading versions above 1.4.1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1
1512 1512  
1513 1513  
1514 -=== 8.3.3 "flash read err" after upgrade firmware ===
1262 +==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ====
1515 1515  
1264 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1516 1516  
1517 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1266 + Figure 1  
1518 1518  
1268 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1519 1519  
1520 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1270 + Figure 2
1521 1521  
1272 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1522 1522  
1523 -User need to upgrade again with below four files to solve this issue.
1274 +[[image:image-20221122100004-3.png]]
1524 1524  
1525 - [[image:image-20221207120530-3.png]]
1276 +Please AT+FDR, and then enter the following instructions by the information on the label
1526 1526  
1527 - **Figure 2**
1278 +AT+DEUI=70B3D57ED0053981
1528 1528  
1529 -
1530 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1531 -
1532 -
1533 -User might erase the entire flash include keys and default settings which cause this issue.
1534 -
1535 -After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below.
1536 -
1537 -
1538 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1539 -
1540 -
1541 -Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1542 -
1543 -After AT+FDR. please set
1544 -
1545 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1546 -
1547 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1548 -
1549 -**Example:**
1550 -
1551 -AT+PDOP=7.00
1552 -
1553 -AT+FTIME=180
1554 -
1555 -AT+DEUI=70B3D57ED0053981  
1556 -
1557 1557  AT+APPEUI=D23345667BCBCCAF
1558 1558  
1559 1559  AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1560 1560  
1561 -AT+DADDR=260b4dce    ( no need for OTAA)
1284 +AT+DADDR=260b4dce
1562 1562  
1563 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1286 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1564 1564  
1565 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1288 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1566 1566  
1567 1567  
1568 -== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1569 1569  
1292 +==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ====
1570 1570  
1571 -Please download version 1.4.2 again
1294 +[[image:image-20221122100004-4.png]]
1572 1572  
1296 +== ==
1573 1573  
1574 -== 8.5  How to deal with unsuccessful GPS positioning? ==
1298 +== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
1575 1575  
1300 +Please download version 1.4.2 again
1576 1576  
1577 -1） Make Sure the device is in Open Area where can see the sky.
1578 1578  
1303 +(((
1304 +== 8.5 How to deal with unsuccessful GPS positioning? ==
1305 +
1306 +1） Make Sure the device is in Open Area where can see the sky. 
1579 1579  2)  Set PDOP to a higher value.
1580 1580  
1581 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1309 + AT+PDOP=2(can be positioned precisely.）
1582 1582  
1583 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1311 + AT+PDOP=7(Quickly locate in open spaces）
1584 1584  
1585 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1313 + AT+PDOP=14.7(Positioning can be acquired in complex environments）
1586 1586  
1587 1587  Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP
1316 +)))
1588 1588  
1589 1589  
1590 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1319 +== ==
1591 1591  
1592 1592  
1593 -When upgrading, use the erase button to upgrade
1594 -
1595 -[[image:image-20221207120536-4.png]]
1596 -
1597 -
1598 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1599 -
1600 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1601 -
1602 -
1603 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1604 -
1605 -[[image:image-20221207134028-8.png]]
1606 -
1607 -
1608 -Reboot information after upgrade
1609 -
1610 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1611 -
1612 -
1613 -Use (% style="color:blue" %)**AT+FDR**(%%) command to reset and then use (% style="color:blue" %)**AT+CFG**(%%) to check whether the configuration is back to normal
1614 -
1615 -[[image:image-20221128111850-5.png]]
1616 -
1617 -
1618 -After the parameters return to normal, upgrade to the version you need again
1619 -
1620 -[[image:image-20221207120601-5.png]]
1621 -
1622 -
1623 -At this point, the parameters return to normal after running AT+FDR again
1624 -
1625 -[[image:image-20221128112035-7.png]]
1626 -
1627 -
1628 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1629 -
1630 -
1631 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1632 -
1633 -2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1634 -
1635 -
1636 1636  = 9.  Order Info =
1637 1637  
1638 1638  
... ... @@ -1641,21 +1641,13 @@
1641 1641  (% style="color:blue" %)**XXX**(%%): The default frequency band
1642 1642  
1643 1643  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1644 -
1645 1645  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1646 -
1647 1647  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1648 -
1649 1649  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1650 -
1651 1651  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1652 -
1653 1653  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1654 -
1655 1655  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1656 1656  
1657 -(% style="display:none" %) (%%)
1658 -
1659 1659  = 10.  Packing Info =
1660 1660  
1661 1661  
... ... @@ -1662,35 +1662,22 @@
1662 1662  (% style="color:#037691" %)**Package Includes**:
1663 1663  
1664 1664  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1665 -
1666 1666  * USB recharge & program cable x 1
1667 1667  
1668 1668  (% style="color:#037691" %)**Dimensions and Weight**:
1669 1669  
1670 1670  * Device Size: 85 x 48 x 15 mm
1671 -
1672 1672  * Weight: 50g
1673 1673  
1674 -(% style="display:none" %) (%%)
1675 -
1676 1676  = 11. Support =
1677 1677  
1678 1678  
1679 1679  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1680 -
1681 1681  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].
1682 1682  
1683 -(% style="display:none" %)
1684 -
1685 -
1686 1686  = 12.  Reference =
1687 1687  
1688 1688  
1689 1689  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1690 -
1691 1691  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1692 -
1693 1693  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1694 -
1695 -
1696 -)))
image-20221128102938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -41.3 KB
Content
image-20221128103040-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -19.2 KB
Content
image-20221128110503-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.6 KB
Content
image-20221128111443-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -15.6 KB
Content
image-20221128111850-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.5 KB
Content
image-20221128111951-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.4 KB
Content
image-20221128112035-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.7 KB
Content
image-20221207120501-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120524-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120530-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120536-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120601-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207133836-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
image-20221207133911-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -46.3 KB
Content
image-20221207134028-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.3 KB
Content
image-20221213100007-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -32.7 KB
Content
image-20221213100626-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -35.7 KB
Content
image-20221213100808-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -91.3 KB
Content
image-20221213101040-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -26.3 KB
Content
image-20221213102311-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.7 KB
Content
image-20221213102334-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.5 KB
Content
image-20221213102718-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20221213110952-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -152.8 KB
Content
image-20230213110119-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -182.3 KB
Content
image-20230213110214-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -182.3 KB
Content
image-20230213110506-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.8 KB
Content
image-20230302145315-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -35.1 KB
Content
image-20230307135914-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -131.8 KB
Content
image-20230307135932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -109.7 KB
Content
image-20230308115430-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -2.4 MB
Content
image-20230308115616-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -152.7 KB
Content
image-20230308115701-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -2.4 MB
Content
image-20230426085815-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -190.0 KB
Content