Last modified by Xiaoling on 2023/12/27 09:15

From version 210.3
edited by Xiaoling
on 2023/08/07 16:16
Change comment: There is no comment for this version
To version 144.1
edited by Edwin Chen
on 2022/11/22 12:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
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,7 +12,6 @@
12 12  
13 13  
14 14  
15 -
16 16  = 1.  Introduction =
17 17  
18 18  == 1.1  What is TrackerD ==
... ... @@ -32,12 +32,15 @@
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  )))
34 +)))
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.
38 +
39 +
38 38  )))
39 39  
40 -[[image:image-20230213110119-1.png||height="382" width="834"]]
42 +[[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.**
... ... @@ -93,10 +93,7 @@
93 93  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 94  * Tracking: max: 38mA
95 95  
96 -(% style="display:none" %)
97 97  
98 -
99 -
100 100  == 1.3  Features ==
101 101  
102 102  
... ... @@ -115,10 +115,7 @@
115 115  * Tri-color LED, Alarm button
116 116  * Datalog
117 117  
118 -(% style="display:none" %)
119 119  
120 -
121 -
122 122  == 1.4  Applications ==
123 123  
124 124  
... ... @@ -125,10 +125,7 @@
125 125  * Logistics and Supply Chain Management
126 126  * Human tracking
127 127  
128 -(% style="display:none" %)
129 129  
130 -
131 -
132 132  = 2.  Use TrackerD =
133 133  
134 134  == 2.1 How it works? ==
... ... @@ -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"]]
139 +[[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"]]
151 +[[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"]]
160 +[[image:1664501711466-918.png]]
168 168  
169 169  
170 170  
171 -[[image:1664501721248-725.png||_mstalt="294450"]]
164 +[[image:1664501721248-725.png]]
172 172  
173 173  
174 -[[image:1664501734705-405.png||_mstalt="293306"]]
167 +[[image:1664501734705-405.png]]
175 175  
176 176  
177 177  
... ... @@ -178,15 +178,15 @@
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"]]
174 +[[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"]]
180 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
188 188  
189 -[[image:1664502835802-546.png||_mstalt="295061"]]
182 +[[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.
... ... @@ -209,16 +209,16 @@
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.
205 +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**
207 +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
210 +(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
211 +|=(% 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
212 +|=(% 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"]]
214 +[[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
225 +*0x01: EU868
233 233  
234 -0x02: US915
227 +*0x02: US915
235 235  
236 -0x03: IN865
229 +*0x03: IN865
237 237  
238 -0x04: AU915
231 +*0x04: AU915
239 239  
240 -0x05: KZ865
233 +*0x05: KZ865
241 241  
242 -0x06: RU864
235 +*0x06: RU864
243 243  
244 -0x07: AS923
237 +*0x07: AS923
245 245  
246 -0x08: AS923-1
239 +*0x08: AS923-1
247 247  
248 -0x09: AS923-2
241 +*0x09: AS923-2
249 249  
250 -0x0a: AS923-3
243 +*0x0a: AS923-3
251 251  
252 -(% style="color:#037691" %)**Sub-Band:**(%%) value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
245 +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  
249 +
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
257 +(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
258 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
259 +|=(% 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,49 @@
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)(%%)  
281 +(% 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"]]
286 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
287 +|=(% 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
288 +|=(% 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 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,
294 +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" %)(((
297 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
298 +|=(% scope="row" style="width: 60px;" %)(((
299 +**Size(bytes)**
300 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
301 +2
302 +)))|(% style="width:30px" %)(((
303 +2
304 +)))
305 +|=(% 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"]]
309 +[[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:"]] 
314 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
315 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
316 +|=(% 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 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:"]]
321 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
322 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
323 +|=(% 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"]]
340 +[[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"]]
345 +[[image:1664502166010-515.png]]
351 351  
352 352  
353 353  
... ... @@ -370,9 +370,7 @@
370 370  * 3.40v ~~ 3.69v:  20% ~~ 40%
371 371  * < 3.39v:  0~~20%
372 372  
373 -(% style="display:none" %) (%%)
374 374  
375 -
376 376  ==== (% style="color:blue" %)**MOD:**(%%) ====
377 377  
378 378  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -416,23 +416,25 @@
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)
412 +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" %)(((
415 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
416 +|=(% scope="row" style="width: 60px;" %)(((
417 +**Size(bytes)**
418 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
419 +|=(% 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"]]
424 +[[image:1665301687277-443.png]]
430 430  
431 431  
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.
430 +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,13 @@
443 443  
444 444  The payload is 15 bytes, as below.
445 445  
446 -(% border="1" style="background-color:#f2f2f2; width:500px" %)
447 -|(((
441 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
442 +|=(% scope="row" %)(((
448 448  **Size(bytes)**
449 449  )))|4|4|2|1|1|1|1|1
450 -|**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
445 +|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
451 451  
452 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
447 +[[image:image-20221009160309-2.png]]
453 453  
454 454  
455 455  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -460,11 +460,11 @@
460 460  User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
461 461  
462 462  
463 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
464 -|(% style="width:60px" %)(((
458 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
459 +|=(% scope="row" style="width: 60px;" %)(((
465 465  **Size(bytes)**
466 466  )))|(% 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
467 -|(% style="width:50px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
462 +|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
468 468  iBeacon MAJOR
469 469  )))|(% style="width:63px" %)(((
470 470  iBeacon MINOR
... ... @@ -476,7 +476,7 @@
476 476  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
477 477  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
478 478  
479 -[[image:1664502425687-834.png||_mstalt="296738"]]
474 +[[image:1664502425687-834.png]]
480 480  
481 481  
482 482  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -487,44 +487,23 @@
487 487  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
488 488  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
489 489  
490 -(% style="display:none" %) (%%)
491 491  
492 -=== 2.4.6  Uplink FPORT~=7, Alarm information status(Since firmware 1.4.4) ===
486 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) ===
493 493  
494 494  
495 -The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
496 -
497 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:284.818px" %)
498 -|(% style="width:97px" %)**Size(bytes)**|(% style="width:103px" %)2|(% style="width:81px" %)1
499 -|(% style="width:97px" %)**Value**|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon
500 -
501 - [[image:image-20230302145315-1.png]]
502 -
503 -**alarm**=(bytes[0] & 0x40)  ~/~/ Alarm status
504 -
505 -**batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
506 -
507 -**mod** = bytes[2] & 0xC0;
508 -
509 -**Lon**=(bytes[2] & 0x20)
510 -
511 -
512 -=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) ===
513 -
514 -
515 515  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.
516 516  
517 517  
518 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
519 -|(% style="width:65px" %)(((
492 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
493 +|=(% scope="row" style="width: 60px;" %)(((
520 520  **Size(bytes)**
521 -)))|(% style="width:50px" %)6|(% style="width:50px" %)4|(% style="width:133px" %)2|(% style="width:50px" %)1
522 -|(% style="width:69px" %)**Value**|(% style="width:48px" %)SSID|(% style="width:48px" %)RSSI|(% style="width:103px" %)(((
495 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
496 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
523 523  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
524 -)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]
498 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
525 525  
526 526  (% class="wikigeneratedid" %)
527 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
501 +[[image:1667288597595-714.png||height="212" width="1151"]]
528 528  
529 529  
530 530  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -531,9 +531,8 @@
531 531  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
532 532  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
533 533  
534 -(% style="display:none" %) (%%)
535 535  
536 -=== 2.4.8  Add Payload format in TTN V3 ===
509 +=== 2.4.7  Add Payload format in TTN V3 ===
537 537  
538 538  
539 539  In TTN V3, user can add a custom payload so it shows friendly.
... ... @@ -541,15 +541,17 @@
541 541  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
542 542  
543 543  
544 -[[image:1664502649601-895.png||_mstalt="296985"]]
517 +[[image:1664502649601-895.png]]
545 545  
546 546  
547 547  
548 -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]]
521 +Add the decoder from this link: 
549 549  
523 +[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
524 +
550 550  Save the change the uplink message will be parsed. As below:
551 551  
552 -[[image:1664502676891-606.png||_mstalt="296673"]]
527 +[[image:1664502676891-606.png]]
553 553  
554 554  
555 555  == 2.5 Integrate with Datacake ==
... ... @@ -560,7 +560,7 @@
560 560  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]]
561 561  
562 562  
563 -[[image:1664502695771-538.png||_mstalt="297349"]]
538 +[[image:1664502695771-538.png]]
564 564  
565 565  
566 566  == 2.6 Integrate with Tago ==
... ... @@ -571,70 +571,29 @@
571 571  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]]
572 572  
573 573  
574 -[[image:1664502715371-321.png||_mstalt="292162"]]
549 +[[image:1664502715371-321.png]]
575 575  
576 576  
577 -== 2.7  Integrate with Node-red ==
552 +== 2.7  Datalog Feature ==
578 578  
579 579  
580 -~1. Install node-red, please refer to the installation method in the link:
581 -
582 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
583 -
584 -
585 -2. Import the created flow template, please refer to the import method in the link:
586 -
587 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
588 -
589 -
590 -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]]
591 -
592 -(% 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.**
593 -
594 -[[image:image-20230307135914-1.png||height="527" width="1045"]]
595 -
596 -
597 -[[image:image-20230307135932-2.png||height="527" width="1044"]]
598 -
599 -
600 -3. Display the map
601 - Enter the link to the map:
602 -
603 - Change its suffix to ditu:http:~/~/119.91.62.30:1880/**ditu/**
604 -
605 -**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
606 -
607 -
608 - Hit all input in input stream
609 -
610 - [[image:image-20230308115616-2.png||height="563" width="1070"]]
611 -
612 -
613 - View map again
614 -
615 -[[image:image-20230308115701-3.png||height="571" width="1085"]]
616 -
617 -
618 -== 2.8  Datalog Feature ==
619 -
620 -
621 621  total 273 entries,by default,
622 622  
623 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
557 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
624 624  
625 625  Example use case.
626 626  
627 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
561 +[[image:image-20221009234703-2.png||height="328" width="899"]]
628 628  
629 629  
630 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
564 +[[image:image-20221009234629-1.png||height="390" width="577"]]
631 631  
632 632  
633 -== 2. Alarm Mode ==
567 +== 2.8 Alarm Mode ==
634 634  
635 635  
636 636  (((
637 -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.
571 +User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
638 638  )))
639 639  
640 640  
... ... @@ -655,24 +655,17 @@
655 655  )))
656 656  
657 657  
658 -== 2.10  Transport Mode ==
592 +== 2.9 Transport Mode ==
659 659  
660 660  
661 -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"]]**.
595 +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.
662 662  
663 -When device is set in Transport Mode, it will uplink more frequenctly during moving.
664 664  
665 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
666 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
667 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
598 +== 2.10 LED Status ==
668 668  
669 -(% style="display:none" %) (%%)
670 670  
671 -== 2.11  LED Status ==
672 -
673 -
674 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:500px" %)
675 -|=(% 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**
601 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
602 +|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
676 676  |(% 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
677 677  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
678 678  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
... ... @@ -685,14 +685,13 @@
685 685  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
686 686  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
687 687  
688 -(% style="display:none" %) (%%)
689 689  
690 -== 2.1 Button Function ==
616 +== 2.11 Button Function ==
691 691  
692 692  
693 693  (% style="color:blue" %)**RESET button:**
694 694  
695 -[[image:1664502835802-546.png||_mstalt="295061"]]
621 +[[image:1664502835802-546.png]]
696 696  
697 697  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
698 698  
... ... @@ -699,19 +699,17 @@
699 699  
700 700  (% style="color:red" %)**RED button:**
701 701  
702 -[[image:image-20230213110506-3.png]](% style="display:none" %)
628 +[[image:1664502854406-763.png]]
703 703  
704 -(% style="display:none" %) (%%)
705 705  
706 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
707 -|=(% 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**
631 +(% border="1" style="background-color:#ffffcc; width:510px" %)
632 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
708 708  |(% 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"]]
709 709  |(% 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
710 710  |(% 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.
711 711  
712 -(% style="display:none" %) (%%)
713 713  
714 -== 2.1 USB Port Function ==
638 +== 2.12 USB Port Function ==
715 715  
716 716  
717 717  The USB interface of TrackerD has below functions:
... ... @@ -721,18 +721,7 @@
721 721  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
722 722  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
723 723  
724 -(% style="display:none" %) (%%)
725 725  
726 -== 2.14  Sleep Mode ==
727 -
728 -
729 -(% 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.
730 -
731 -In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
732 -
733 -Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
734 -
735 -
736 736  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
737 737  
738 738  
... ... @@ -747,22 +747,22 @@
747 747  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.
748 748  
749 749  
750 -[[image:1664502999401-486.png||_mstalt="296985"]]
663 +[[image:1664502999401-486.png]]
751 751  
752 752  
753 753  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:
754 754  
755 755  
756 -[[image:1664503022490-662.png||_mstalt="293332"]]
669 +[[image:1664503022490-662.png]]
757 757  
758 758  
759 -[[image:1664503035713-500.png||_mstalt="291096"]]
672 +[[image:1664503035713-500.png]]
760 760  
761 761  
762 -[[image:1664503047675-651.png||_mstalt="295386"]]
675 +[[image:1664503047675-651.png]]
763 763  
764 -(% style="display:none" %) (%%)
765 765  
678 +
766 766  == 3.2 Command Set ==
767 767  
768 768  === 3.2.1 Set Transmit Interval ===
... ... @@ -828,7 +828,7 @@
828 828  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
829 829  
830 830  
831 -=== 3.2.5 Disable/Enable LED flash and buzzer ===
744 +=== 3.2.5 Disable/Enable LED flash ===
832 832  
833 833  
834 834  Disable/Enable LED for position, downlink and uplink
... ... @@ -888,9 +888,9 @@
888 888  
889 889  (% style="color:#037691" %)**cc:   **
890 890  
891 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
804 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
892 892  
893 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
806 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
894 894  
895 895  (% style="color:blue" %)**Example:**
896 896  
... ... @@ -952,8 +952,8 @@
952 952  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
953 953  
954 954  
955 -=== 3.2.10 Disable/Enable the confirmation mode ===
956 956  
869 +**Disable/Enable the confirmation mode**
957 957  
958 958  * (% style="color:blue" %)**AT Command:**
959 959  
... ... @@ -972,7 +972,7 @@
972 972  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
973 973  
974 974  
975 -=== 3.2.11  Auto Send None-ACK messages ===
888 +=== 3.2.10  Auto Send None-ACK messages ===
976 976  
977 977  
978 978  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.
... ... @@ -990,10 +990,10 @@
990 990  
991 991  * (% style="color:blue" %)**Downlink Command: 0x34**
992 992  
993 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
906 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
994 994  
995 995  
996 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
909 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
997 997  
998 998  
999 999  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.
... ... @@ -1002,16 +1002,16 @@
1002 1002  
1003 1003  (% style="color:blue" %)**AT Command:**
1004 1004  
1005 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
918 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
1006 1006  
1007 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
920 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
1008 1008  
1009 1009  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)**
1010 1010  
1011 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
924 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
1012 1012  
1013 1013  
1014 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===
927 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===
1015 1015  
1016 1016  
1017 1017  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.
... ... @@ -1020,16 +1020,16 @@
1020 1020  
1021 1021  (% style="color:blue" %)**AT Command:**
1022 1022  
1023 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
936 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1024 1024  
1025 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
938 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1026 1026  
1027 1027  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)**
1028 1028  
1029 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
942 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
1030 1030  
1031 1031  
1032 -=== 3.2.1 Disable/Enable Information printing(Since firmware 1.4.1) ===
945 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) ===
1033 1033  
1034 1034  
1035 1035  Users can use this feature to enable/disable Information printing.
... ... @@ -1036,11 +1036,11 @@
1036 1036  
1037 1037  (% style="color:blue" %)**AT Command:**
1038 1038  
1039 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
952 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
1040 1040  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1041 1041  
1042 1042  
1043 -=== 3.2.1 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===
956 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===
1044 1044  
1045 1045  
1046 1046  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -1047,131 +1047,14 @@
1047 1047  
1048 1048  (% style="color:blue" %)**AT Command:**
1049 1049  
1050 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
963 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1051 1051  
1052 1052  
1053 1053  (% style="color:blue" %)**Downlink Payload:0X24**
1054 1054  
1055 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
968 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
1056 1056  
1057 1057  
1058 -=== 3.2.16  Get or Set Threshold for motion detect(Since firmware 1.4.3) ===
1059 -
1060 -
1061 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1062 -
1063 -(% style="color:blue" %)**AT Command:**
1064 -
1065 -(% style="color:#037691" %)**AT+PT=xx**
1066 -
1067 - Example:
1068 -
1069 - AT+PT=14    ~-~->    Set to detect car motion.
1070 -
1071 - AT+PT=41  ~-~->    set to detect walk motion.
1072 -
1073 -
1074 -(% style="color:blue" %)**Downlink Payload:0xB4**
1075 -
1076 -0xB4 14          ~/~/  Same as AT+PT=14
1077 -
1078 -
1079 -=== 3.2.17  Set AT command window time(Since firmware 1.4.5) ===
1080 -
1081 -
1082 -AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
1083 -
1084 -(% style="color:blue" %)**AT Command:**
1085 -
1086 -(% style="color:#037691" %)**AT+ATST=XX**
1087 -
1088 - Example:
1089 -
1090 - AT+ATST=15    ~-~-> Set the time to 15 seconds
1091 -
1092 -(% style="color:blue" %)**Downlink Payload:0XB5**
1093 -
1094 -0xB5 0F          ~/~/  Same as AT+ATST=15
1095 -
1096 -
1097 -=== 3.2.18  Set the stepmeter mode(Since firmware 1.4.5) ===
1098 -
1099 -
1100 -After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
1101 -
1102 -(% style="color:blue" %)**AT Command:**
1103 -
1104 -(% style="color:#037691" %)**AT+PM=xx**
1105 -
1106 - Example:
1107 -
1108 - AT+PM=1    ~-~->  Turn on step counting mode
1109 -
1110 -AT+PM=0    ~-~->  Turn OFF step counting mode
1111 -
1112 -(% style="color:blue" %)**Downlink Payload:0XB6**
1113 -
1114 -0xB6 01          ~/~/  Same as AT+PM=1
1115 -
1116 -
1117 -=== 3.2.19  Set down the decline detection mode(Since firmware 1.4.5) ===
1118 -
1119 -
1120 -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.
1121 -
1122 -(% style="color:blue" %)**AT Command:**
1123 -
1124 -(% style="color:#037691" %)**AT+FD=xx**
1125 -
1126 - Example:
1127 -
1128 - AT+FD=1    ~-~->  Turn on the Fall detection
1129 -
1130 -AT+FD=0    ~-~->  Turn OFF the Fall detection
1131 -
1132 -(% style="color:blue" %)**Downlink Payload:0XB7**
1133 -
1134 -0xB7 01          ~/~/  Same as AT+FD=1
1135 -
1136 -
1137 -=== 3.2.20 Disable/Enable buzzer(Since firmware 1.4.6) ===
1138 -
1139 -
1140 -Disable/Enable buzzer for Alarm, downlink and uplink
1141 -
1142 -(% style="color:blue" %)**AT Command:**
1143 -
1144 -(% style="color:#037691" %)**AT+BEEP=XX**
1145 -
1146 - Example:
1147 -
1148 -AT+BEEP=1 ~-~-> Turn on the buzzer
1149 -
1150 -AT+BEEP=0 ~-~-> Turn OFF the buzzer
1151 -
1152 -(% style="color:blue" %)**Downlink Payload:0XB9**
1153 -
1154 -0xB9 01 ~/~/ Same as AT+BEEP=1
1155 -
1156 -
1157 -=== 3.2.21 Set long press time(Since firmware 1.4.6) ===
1158 -
1159 -
1160 -When using the red button Changan to alarm, press and hold the time to set 0~~10 seconds, which is convenient for use scenarios.
1161 -
1162 -(% style="color:blue" %)**AT Command:**
1163 -
1164 -(% style="color:#037691" %)**AT+EAT=XX**
1165 -
1166 - Example:
1167 -
1168 -AT+EAT=2 ~-~-> Set the long press time to 2s
1169 -
1170 -(% style="color:blue" %)**Downlink Payload:0XBA**
1171 -
1172 -0xBA 02 ~/~/ Same as AT+EAT=2
1173 -
1174 -
1175 1175  = 4. Setting for Different Scenarios =
1176 1176  
1177 1177  
... ... @@ -1204,10 +1204,10 @@
1204 1204  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1205 1205  
1206 1206  
1207 -[[image:1664503563660-578.png||_mstalt="296777"]]
1003 +[[image:1664503563660-578.png]]
1208 1208  
1209 1209  
1210 -[[image:1664503574618-659.png||_mstalt="297986"]]
1006 +[[image:1664503574618-659.png]]
1211 1211  
1212 1212  
1213 1213  
... ... @@ -1223,15 +1223,16 @@
1223 1223  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1224 1224  
1225 1225  
1226 -[[image:image-20221207120501-1.png]]
1022 +[[image:image-20221118105220-2.png]]
1227 1227  
1228 1228  
1229 1229  
1230 1230  After upgrade finish, it will show finish as below:
1231 1231  
1232 -[[image:image-20221207133911-7.png]]
1028 +[[image:image-20221118105402-4.png]]
1233 1233  
1234 1234  
1031 +
1235 1235  = 6. Developer Guide =
1236 1236  
1237 1237  == 6.1 Compile Source Code ==
... ... @@ -1244,81 +1244,24 @@
1244 1244  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]]
1245 1245  
1246 1246  
1247 -[[image:1664503635019-941.png||_mstalt="294658"]]
1044 +[[image:1664503635019-941.png]]
1248 1248  
1249 1249  
1250 1250  
1251 1251  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1252 1252  
1253 -[[image:1664503715811-892.png||_mstalt="295698"]]
1050 +[[image:1664503715811-892.png]]
1254 1254  
1255 1255  
1256 -=== 6.1.2  Build the development environment ===
1257 -
1258 -
1259 -**~1. Download and install arduino IDE**
1260 -
1261 -[[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]]
1262 -
1263 -
1264 -**2. Download the ESP32 development package in the arduino IDE**
1265 -
1266 -[[image:image-20221213100007-1.png]]
1267 -
1268 -
1269 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1270 -
1271 -[[image:image-20221213100626-2.png]]
1272 -
1273 -
1274 -Restart the IDE after the addition is complete, then:
1275 -
1276 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1277 -
1278 -
1279 -[[image:image-20221213101040-4.png]]
1280 -
1281 -
1282 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1283 -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)**
1284 -
1285 -
1286 -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:
1287 -
1288 -(% style="color:blue" %)**Methods as below:**
1289 -
1290 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1291 -
1292 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1293 -
1294 1294  (% 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.
1295 1295  
1296 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1055 +[[image:image-20221024105643-1.png]]
1297 1297  
1298 -
1299 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1300 -
1301 -[[image:image-20221213102334-6.png]]
1302 -
1303 -(% style="color:red" %)**Note: This step requires a python environment**
1304 -
1305 -
1306 -Either way, in the end:
1307 -
1308 -The final effect is to open the arduino and you can see the esp32
1309 -
1310 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1311 -
1312 -
1313 -
1314 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1315 -
1316 1316  **~ Figure1**
1317 1317  
1318 1318  
1060 +[[image:image-20221024105643-2.png]]
1319 1319  
1320 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1321 -
1322 1322   **Figure2**
1323 1323  
1324 1324  
... ... @@ -1327,7 +1327,7 @@
1327 1327  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1328 1328  
1329 1329  
1330 -[[image:1664503752288-974.png||_mstalt="298194"]]
1070 +[[image:1664503752288-974.png]]
1331 1331  
1332 1332  
1333 1333  == 6.2 Source Code ==
... ... @@ -1335,19 +1335,19 @@
1335 1335  
1336 1336  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1337 1337  
1338 -[[image:1664503794261-827.png||_mstalt="296387"]]
1078 +[[image:1664503794261-827.png]]
1339 1339  
1340 1340  
1341 1341  
1342 1342  * (% style="color:blue" %)**Click to upload**
1343 1343  
1344 -[[image:1664503808294-336.png||_mstalt="295711"]]
1084 +[[image:1664503808294-336.png]]
1345 1345  
1346 1346  
1347 1347  
1348 1348  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1349 1349  
1350 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1090 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1351 1351  
1352 1352  
1353 1353  = 7.  FAQ =
... ... @@ -1361,12 +1361,12 @@
1361 1361  == 7.2 What is the pin mapping for the USB program cable? ==
1362 1362  
1363 1363  
1364 -[[image:1664499635206-262.png||_mstalt="295360"]]
1104 +[[image:1664499635206-262.png]]
1365 1365  
1366 1366  
1367 1367  
1368 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:314px" %)
1369 -|=(% 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**
1108 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
1109 +|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
1370 1370  |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1371 1371  |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1372 1372  |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
... ... @@ -1376,9 +1376,7 @@
1376 1376  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1377 1377  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1378 1378  
1379 -(% style="display:none" %) (%%)
1380 1380  
1381 -
1382 1382  == 7.3 Notes on using different serial port tools for TrackerD ==
1383 1383  
1384 1384  === 7.3.1  Serial port utility ===
... ... @@ -1389,13 +1389,13 @@
1389 1389  Need to adjust the data stream to RTS/CTS on physical restart.
1390 1390  
1391 1391  (% class="wikigeneratedid" %)
1392 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1130 +[[image:image-20221102140621-1.png]]
1393 1393  
1394 1394  
1395 1395  
1396 1396  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1397 1397  
1398 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1136 +[[image:image-20221102140638-2.png]]
1399 1399  
1400 1400  
1401 1401  === 7.3.2  SecureCRT ===
... ... @@ -1404,22 +1404,22 @@
1404 1404  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.
1405 1405  
1406 1406  
1407 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1145 +[[image:image-20221102140704-3.png]]
1408 1408  
1409 1409  
1410 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1148 +[[image:image-20221102140712-4.png]]
1411 1411  
1412 1412  
1413 1413  === 7.3.3  PUTTY ===
1414 1414  
1415 1415  
1416 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1154 +[[image:image-20221102140748-5.png]]
1417 1417  
1418 1418  
1419 1419  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.
1420 1420  
1421 1421  
1422 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1160 +[[image:image-20221102140801-6.png]]
1423 1423  
1424 1424  
1425 1425  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1434,7 +1434,7 @@
1434 1434  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1435 1435  
1436 1436  
1437 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1175 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1438 1438  
1439 1439  
1440 1440  
... ... @@ -1441,7 +1441,7 @@
1441 1441  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1442 1442  
1443 1443  
1444 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1182 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1445 1445  
1446 1446  
1447 1447  
... ... @@ -1448,7 +1448,7 @@
1448 1448  **3. Compile the AS923_JP band, please refer to the intention shown**
1449 1449  
1450 1450  
1451 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1189 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1452 1452  
1453 1453  
1454 1454  
... ... @@ -1455,24 +1455,12 @@
1455 1455  **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.**
1456 1456  
1457 1457  
1458 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1196 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1459 1459  
1460 1460  
1461 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1199 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1462 1462  
1463 1463  
1464 -== 7.5 Are there example python example for BLE Indoor Positioning? ==
1465 -
1466 -
1467 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1468 -
1469 -
1470 -== 7.6 Can alert mode and transport mode be used together? ==
1471 -
1472 -
1473 -Yes, you can also press the panic button to sound the alarm if set to transport mode
1474 -
1475 -
1476 1476  = 8  Trouble Shooting =
1477 1477  
1478 1478  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
... ... @@ -1479,7 +1479,7 @@
1479 1479  
1480 1480  
1481 1481  (((
1482 -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
1208 +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
1483 1483  )))
1484 1484  
1485 1485  
... ... @@ -1493,69 +1493,50 @@
1493 1493  
1494 1494  == 8.3  Problem after Upgrading Firmware ==
1495 1495  
1496 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1222 +=== 8.3.1 Continue Restart after upgrading ===
1497 1497  
1498 1498  
1499 -**Error Output**
1500 -
1501 -
1502 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1503 -
1504 -
1505 1505  (((
1506 -Some partition is missed during upgrade, please upgrade below four files as example:
1507 -
1508 -[[image:image-20221207120524-2.png]]
1226 +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
1509 1509  )))
1510 1510  
1511 1511  
1512 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1230 +[[image:image-20221118105249-3.png]]
1513 1513  
1514 1514  
1515 -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
1233 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1516 1516  
1517 1517  
1518 -=== 8.3.3 "flash read err" after upgrade firmware ===
1236 +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
1519 1519  
1520 1520  
1239 +=== 8.3.3 "flash read err" after upgrade firmware ===
1240 +
1521 1521  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1522 1522  
1243 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1523 1523  
1524 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1525 1525  
1526 -
1527 1527  User need to upgrade again with below four files to solve this issue.
1528 1528  
1529 - [[image:image-20221207120530-3.png]]
1248 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1530 1530  
1531 1531   **Figure 2**
1532 1532  
1533 1533  
1534 -=== 8.3. "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1253 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1535 1535  
1536 -
1537 1537  User might erase the entire flash include keys and default settings which cause this issue.
1538 1538  
1539 -After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below.
1257 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1540 1540  
1259 +[[image:image-20221122100004-3.png]]
1541 1541  
1542 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1261 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1543 1543  
1544 1544  
1545 -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.
1264 +Example:
1546 1546  
1547 -After AT+FDR. please set
1548 -
1549 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1550 -
1551 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1552 -
1553 -**Example:**
1554 -
1555 -AT+PDOP=7.00
1556 -
1557 -AT+FTIME=180
1558 -
1559 1559  AT+DEUI=70B3D57ED0053981  
1560 1560  
1561 1561  AT+APPEUI=D23345667BCBCCAF
... ... @@ -1569,6 +1569,13 @@
1569 1569  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1570 1570  
1571 1571  
1279 +
1280 +==== 8.3.4  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 ====
1281 +
1282 +
1283 +[[image:image-20221122100004-4.png]]
1284 +
1285 +
1572 1572  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1573 1573  
1574 1574  
... ... @@ -1582,61 +1582,15 @@
1582 1582  
1583 1583  2)  Set PDOP to a higher value.
1584 1584  
1585 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.)
1299 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.)
1586 1586  
1587 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces)
1301 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces)
1588 1588  
1589 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments)
1303 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments)
1590 1590  
1591 1591  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
1592 1592  
1593 1593  
1594 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1595 -
1596 -
1597 -When upgrading, use the erase button to upgrade
1598 -
1599 -[[image:image-20221207120536-4.png]]
1600 -
1601 -
1602 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1603 -
1604 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1605 -
1606 -
1607 -Please upgrade these four files,link(The boot_app0 file is in the version folder you need)
1608 -
1609 -[[image:image-20221207134028-8.png]]
1610 -
1611 -
1612 -Reboot information after upgrade
1613 -
1614 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1615 -
1616 -
1617 -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
1618 -
1619 -[[image:image-20221128111850-5.png]]
1620 -
1621 -
1622 -After the parameters return to normal, upgrade to the version you need again
1623 -
1624 -[[image:image-20221207120601-5.png]]
1625 -
1626 -
1627 -At this point, the parameters return to normal after running AT+FDR again
1628 -
1629 -[[image:image-20221128112035-7.png]]
1630 -
1631 -
1632 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1633 -
1634 -
1635 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1636 -
1637 -2. Send some commands through the serial port to prompt an error (Example:AT+SMOD=1,0,1)
1638 -
1639 -
1640 1640  = 9.  Order Info =
1641 1641  
1642 1642  
... ... @@ -1658,7 +1658,6 @@
1658 1658  
1659 1659  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1660 1660  
1661 -(% style="display:none" %) (%%)
1662 1662  
1663 1663  = 10.  Packing Info =
1664 1664  
... ... @@ -1675,7 +1675,6 @@
1675 1675  
1676 1676  * Weight: 50g
1677 1677  
1678 -(% style="display:none" %) (%%)
1679 1679  
1680 1680  = 11. Support =
1681 1681  
... ... @@ -1684,9 +1684,7 @@
1684 1684  
1685 1685  * 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]].
1686 1686  
1687 -(% style="display:none" %)
1688 1688  
1689 -
1690 1690  = 12.  Reference =
1691 1691  
1692 1692  
... ... @@ -1695,6 +1695,3 @@
1695 1695  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1696 1696  
1697 1697  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1698 -
1699 -
1700 -)))
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