Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 215.3
edited by Xiaoling
on 2023/10/27 18:00
Change comment: There is no comment for this version
To version 145.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,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,10 +125,6 @@
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  
134 134  == 2.1 How it works? ==
... ... @@ -143,9 +143,10 @@
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"]]
136 +[[image:1664501652064-326.png]]
147 147  
148 148  
139 +
149 149  The LPS8N is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. What the rest need to is register this device in TTN V3:
150 150  
151 151  
... ... @@ -154,7 +154,7 @@
154 154  Each TrackerD is shipped with a sticker with the default device EUI as below:
155 155  
156 156  
157 -[[image:image-20230426085815-1.png||height="259" width="558"]]
148 +[[image:1664501677253-891.png]]
158 158  
159 159  
160 160  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -162,26 +162,30 @@
162 162  
163 163  **__Add APP EUI in the application:__**
164 164  
165 -[[image:1664501711466-918.png||_mstalt="295828"]]
166 166  
157 +[[image:1664501711466-918.png]]
167 167  
168 -[[image:1664501721248-725.png||_mstalt="294450"]]
169 169  
170 170  
171 -[[image:1664501734705-405.png||_mstalt="293306"]]
161 +[[image:1664501721248-725.png]]
172 172  
173 173  
164 +[[image:1664501734705-405.png]]
165 +
166 +
167 +
174 174  **__Add APP KEY and DEV EUI:__**
175 175  
176 176  
177 -[[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"]]
171 +[[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"]]
178 178  
179 179  
174 +
180 180  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
181 181  
182 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
177 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
183 183  
184 -[[image:1664502835802-546.png||_mstalt="295061"]]
179 +[[image:1664502835802-546.png]]
185 185  
186 186  
187 187  (% 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.
... ... @@ -204,17 +204,18 @@
204 204  === 2.4.1 Uplink FPORT~=5, Device Status ===
205 205  
206 206  
207 -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.
202 +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.
208 208  
209 -Use can also get the Device Status uplink through the downlink command: (% style="color:#037691" %)**Downlink:  0x2301**
204 +Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
210 210  
211 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:440px" %)
212 -|(% 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
213 -|(% 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 214  
215 -[[image:1665301570342-765.png||_mstalt="294580"]]
207 +(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
208 +|=(% 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
209 +|=(% 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
216 216  
211 +[[image:1665301570342-765.png]]
217 217  
213 +
218 218  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
219 219  
220 220  (% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
... ... @@ -223,30 +223,31 @@
223 223  
224 224  (% style="color:#037691" %)**Frequency Band**:
225 225  
226 -0x01: EU868
222 +*0x01: EU868
227 227  
228 -0x02: US915
224 +*0x02: US915
229 229  
230 -0x03: IN865
226 +*0x03: IN865
231 231  
232 -0x04: AU915
228 +*0x04: AU915
233 233  
234 -0x05: KZ865
230 +*0x05: KZ865
235 235  
236 -0x06: RU864
232 +*0x06: RU864
237 237  
238 -0x07: AS923
234 +*0x07: AS923
239 239  
240 -0x08: AS923-1
236 +*0x08: AS923-1
241 241  
242 -0x09: AS923-2
238 +*0x09: AS923-2
243 243  
244 -0x0a: AS923-3
240 +*0x0a: AS923-3
245 245  
246 -(% style="color:#037691" %)**Sub-Band:**(%%) value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
242 +Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
247 247  
248 248  (% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
249 249  
246 +
250 250  (% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
251 251  
252 252  Use can also get the Device Status uplink through the downlink command:
... ... @@ -254,71 +254,71 @@
254 254  
255 255  (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
256 256  
257 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:270px" %)
258 -|(% style="width:60px" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)2 bits|(% style="width:80px" %)4 bits
259 -|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
254 +(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
255 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
256 +|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
260 260  
261 -(% style="color:blue" %)**SMOD：**
258 +(% style="color:blue" %)** SMOD：**
262 262  
263 -(% style="color:red" %)**1 :** (%%) GPS ONLY
260 +(% style="color:red" %)** 1 :** (%%) GPS ONLY
264 264  
265 -(% style="color:red" %)**2 :** (%%) BLE ONLY
262 +(% style="color:red" %)** 2 :** (%%) BLE ONLY
266 266  
267 -(% style="color:red" %)**3 :**  (%%) GPS/BLE Hybrid
264 +(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
268 268  
269 269  
270 -(% style="color:blue" %)**GPS_MOD: Define how to send GPS payload**
267 +(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
271 271  
272 -(% style="color:red" %)**0 : ** (%%) Enable uploading on-board Temperature and humidity values
269 +(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
273 273  
274 -(% style="color:red" %)**1 :** (%%) Disable uploading on-board Temperature and humidity values
271 +(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
275 275  
276 276  
277 -(% style="color:blue" %)**BLE_Settings:**
274 +(% style="color:blue" %)** BLE_Settings:**
278 278  
279 -(% style="color:red" %)**1: ** (%%) BLE Positioning with Strongest iBeacon
276 +(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
280 280  
281 -(% _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)(%%)  
278 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
282 282  
283 283  
284 284  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
285 285  
286 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:413px" %)
287 -|(% 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
288 -|(% 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"]]
283 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
284 +|=(% 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
285 +|=(% 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"]]
289 289  
290 -(% style="display:none" %)
291 -
292 -
293 293  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
294 294  
295 295  
296 -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,
290 +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,
297 297  
298 298  
299 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:320px" %)
300 -|(% 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
301 -|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
293 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
294 +|=(% scope="row" style="width: 60px;" %)(((
295 +**Size(bytes)**
296 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
297 +2
298 +)))|(% style="width:30px" %)(((
299 +2
300 +)))
301 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
302 302  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
303 303  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
304 304  
305 -[[image:1665301636888-168.png||_mstalt="298012"]]
305 +[[image:1665301636888-168.png]]
306 306  
307 307  
308 308  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
309 309  
310 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:321px" %)
311 -|(% style="width:60px" %)**Size(bit)**|(% style="width:60px" %)1 bit|(% style="width:134px" %)1 bit|(% style="width:67px" %)14 bits
312 -|(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:114px" %)Alarm Indicate|(% style="width:62px" %)[[BAT>>||anchor="HBAT:"]] 
310 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
311 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
312 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
313 313  
314 -(% style="display:none" %)
315 -
316 -
317 317  ==== (% style="color:blue" %)**FLAG:**(%%) ====
318 318  
319 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:184px" %)
320 -|(% style="width:68px" %)**Size(bit)**|(% style="width:61px" %)2 bits|(% style="width:55px" %)1 bit
321 -|(% style="width:79px" %)**Value**|(% style="width:56px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:50px" %)[[LON>>||anchor="HLON:"]]
316 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
317 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
318 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
322 322  
323 323  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
324 324  
... ... @@ -335,12 +335,12 @@
335 335  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:
336 336  
337 337  
338 -[[image:1664502116362-706.png||_mstalt="293306"]]
335 +[[image:1664502116362-706.png]]
339 339  
340 340  
341 341  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
342 342  
343 -[[image:1664502166010-515.png||_mstalt="291395"]]
340 +[[image:1664502166010-515.png]]
344 344  
345 345  
346 346  
... ... @@ -363,9 +363,6 @@
363 363  * 3.40v ~~ 3.69v:  20% ~~ 40%
364 364  * < 3.39v:  0~~20%
365 365  
366 -(% style="display:none" %) (%%)
367 -
368 -
369 369  ==== (% style="color:blue" %)**MOD:**(%%) ====
370 370  
371 371  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -409,23 +409,25 @@
409 409  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
410 410  
411 411  
412 -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)
406 +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)
413 413  
414 414  
415 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:300px" %)
416 -|(% style="width:60px" %)**Size(bytes)**|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:70px" %)2|(% style="width:50px" %)1
417 -|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
409 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
410 +|=(% scope="row" style="width: 60px;" %)(((
411 +**Size(bytes)**
412 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
413 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
418 418  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
419 419  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
420 420  
421 421  (% class="wikigeneratedid" %)
422 -[[image:1665301687277-443.png||_mstalt="296140"]]
418 +[[image:1665301687277-443.png]]
423 423  
424 424  
425 425  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
426 426  
427 427  
428 -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.
424 +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.
429 429  
430 430  
431 431  (% style="color:red" %)**Note for this mode:**
... ... @@ -436,11 +436,13 @@
436 436  
437 437  The payload is 15 bytes, as below.
438 438  
439 -(% border="1" style="background-color:#f2f2f2; width:500px" %)
440 -|**Size(bytes)**|4|4|2|1|1|1|1|1
441 -|**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
435 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
436 +|=(% scope="row" %)(((
437 +**Size(bytes)**
438 +)))|4|4|2|1|1|1|1|1
439 +|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
442 442  
443 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
441 +[[image:image-20221009160309-2.png]]
444 444  
445 445  
446 446  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -451,9 +451,11 @@
451 451  User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
452 452  
453 453  
454 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
455 -|(% 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
456 -|(% style="width:50px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
452 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
453 +|=(% scope="row" style="width: 60px;" %)(((
454 +**Size(bytes)**
455 +)))|(% 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
456 +|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
457 457  iBeacon MAJOR
458 458  )))|(% style="width:63px" %)(((
459 459  iBeacon MINOR
... ... @@ -465,7 +465,7 @@
465 465  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
466 466  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
467 467  
468 -[[image:1664502425687-834.png||_mstalt="296738"]]
468 +[[image:1664502425687-834.png]]
469 469  
470 470  
471 471  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -476,89 +476,47 @@
476 476  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
477 477  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
478 478  
479 -(% style="display:none" %) (%%)
479 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
480 480  
481 481  
482 -=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
483 -
484 -
485 -The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
486 -
487 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:284.818px" %)
488 -|(% style="width:97px" %)**Size(bytes)**|(% style="width:103px" %)2|(% style="width:81px" %)1
489 -|(% style="width:97px" %)**Value**|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon
490 -
491 - [[image:image-20230302145315-1.png]]
492 -
493 -**alarm**=(bytes[0] & 0x40)  ~/~/ Alarm status
494 -
495 -**batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
496 -
497 -**mod** = bytes[2] & 0xC0;
498 -
499 -**Lon**=(bytes[2] & 0x20)
500 -
501 -
502 -=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
503 -
504 -
505 505  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.
506 506  
507 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
508 -|(% style="width:65px" %)(((
484 +
485 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
486 +|=(% scope="row" style="width: 60px;" %)(((
509 509  **Size(bytes)**
510 -)))|(% style="width:50px" %)6|(% style="width:50px" %)4|(% style="width:133px" %)2|(% style="width:50px" %)1
511 -|(% style="width:69px" %)**Value**|(% style="width:48px" %)SSID|(% style="width:48px" %)RSSI|(% style="width:103px" %)(((
488 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
489 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
512 512  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
513 -)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]
491 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
514 514  
515 515  (% class="wikigeneratedid" %)
516 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
494 +[[image:1667288597595-714.png||height="212" width="1151"]]
517 517  
496 +
518 518  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
519 519  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
520 520  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
521 521  
522 -(% style="display:none" %) (%%)
501 +=== 2.4.7  Add Payload format in TTN V3 ===
523 523  
524 -=== 2.4.8  Uplink FPORT~=9, BLE Positioning with Multiple iBeacon（Since firmware 1.4.7） ===
525 525  
526 -TrackerD supports BLE scanning for indoor positioning. Users can set SMOD to BLE pure or GPS/BLE Hybrid, so TrackerD will scan up to 40 BLE iBeacons and send uplinks.
504 +In TTN V3, user can add a custom payload so it shows friendly.
527 527  
528 -User can set [[(% class="wikiinternallink wikiinternallink wikiinternallink" %)**BLEMASK**>>path:#H3.2.11A0SetBLEMASKtofilterBLEiBeacon]](%%) so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
506 +In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
529 529  
530 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
531 -|**Size(bytes)**|2|2|2|…..|2|2|2|2|1
532 -|**Value**|iBeacon MAJOR|iBeacon MINOR|iBeacon RSSI|…..|iBeacon MAJOR|iBeacon MINOR|iBeacon RSSI|[[Alarm & BAT>>path:#HAlarm26BAT:]]|[[FLAG>>path:#HFLAG:]]
533 533  
534 -(% class="wikigeneratedid" id="H" %)
535 -[[image:image-20231023103116-1.png||height="448" width="901"]]
509 +[[image:1664502649601-895.png]]
536 536  
537 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
538 -* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
539 -* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
540 -* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
541 541  
542 -(% class="wikigeneratedid" %)
543 -**Note: This mode does not have a fixed decoder. Its decoder depends on the number of beacons and can be parsed according to the order of the payload.**
544 -payload format: (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State
545 545  
513 +Add the decoder from this link: 
546 546  
547 -=== 2.4.9  Add Payload format in TTN V3 ===
515 +[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
548 548  
549 -
550 -In TTN V3, user can add a custom payload so it shows friendly.
551 -
552 -In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
553 -
554 -[[image:1664502649601-895.png||_mstalt="296985"]]
555 -
556 -
557 -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]]
558 -
559 559  Save the change the uplink message will be parsed. As below:
560 560  
561 -[[image:1664502676891-606.png||_mstalt="296673"]]
519 +[[image:1664502676891-606.png]]
562 562  
563 563  
564 564  == 2.5 Integrate with Datacake ==
... ... @@ -568,9 +568,10 @@
568 568  
569 569  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]]
570 570  
571 -[[image:1664502695771-538.png||_mstalt="297349"]]
572 572  
530 +[[image:1664502695771-538.png]]
573 573  
532 +
574 574  == 2.6 Integrate with Tago ==
575 575  
576 576  
... ... @@ -578,70 +578,30 @@
578 578  
579 579  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]]
580 580  
581 -[[image:1664502715371-321.png||_mstalt="292162"]]
582 582  
541 +[[image:1664502715371-321.png]]
583 583  
584 -== 2.7  Integrate with Node-red ==
585 585  
544 +== 2.7  Datalog Feature ==
586 586  
587 -~1. Install node-red, please refer to the installation method in the link:
588 588  
589 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
590 -
591 -
592 -2. Import the created flow template, please refer to the import method in the link:
593 -
594 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
595 -
596 -
597 -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]]
598 -
599 -(% 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.**
600 -
601 -[[image:image-20230307135914-1.png||height="527" width="1045"]]
602 -
603 -
604 -[[image:image-20230307135932-2.png||height="527" width="1044"]]
605 -
606 -
607 -3. Display the map
608 - Enter the link to the map:
609 -
610 - Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
611 -
612 -**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
613 -
614 -
615 - Hit all input in input stream
616 -
617 - [[image:image-20230308115616-2.png||height="563" width="1070"]]
618 -
619 -
620 - View map again
621 -
622 -[[image:image-20230308115701-3.png||height="571" width="1085"]]
623 -
624 -
625 -== 2.8  Datalog Feature ==
626 -
627 -
628 628  total 273 entries,by default,
629 629  
630 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
549 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
631 631  
632 632  Example use case.
633 633  
634 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
553 +[[image:image-20221009234703-2.png||height="328" width="899"]]
635 635  
636 636  
637 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
556 +[[image:image-20221009234629-1.png||height="390" width="577"]]
638 638  
639 639  
640 -== 2.9  Alarm Mode ==
559 +== 2.8 Alarm Mode ==
641 641  
642 642  
643 643  (((
644 -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.
563 +User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
645 645  )))
646 646  
647 647  
... ... @@ -662,25 +662,17 @@
662 662  )))
663 663  
664 664  
665 -== 2.10  Transport Mode ==
584 +== 2.9 Transport Mode ==
666 666  
667 667  
668 -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"]]**.
587 +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.
669 669  
670 -When device is set in Transport Mode, it will uplink more frequenctly during moving.
671 671  
672 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
673 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
674 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
590 +== 2.10 LED Status ==
675 675  
676 -(% style="display:none" %) (%%)
677 677  
678 -
679 -== 2.11  LED Status ==
680 -
681 -
682 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:500px" %)
683 -|=(% 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**
593 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
594 +|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
684 684  |(% 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
685 685  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
686 686  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
... ... @@ -693,15 +693,12 @@
693 693  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
694 694  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
695 695  
696 -(% style="display:none" %) (%%)
607 +== 2.11 Button Function ==
697 697  
698 698  
699 -== 2.12  Button Function ==
700 -
701 -
702 702  (% style="color:blue" %)**RESET button:**
703 703  
704 -[[image:1664502835802-546.png||_mstalt="295061"]]
612 +[[image:1664502835802-546.png]]
705 705  
706 706  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
707 707  
... ... @@ -708,22 +708,18 @@
708 708  
709 709  (% style="color:red" %)**RED button:**
710 710  
711 -[[image:image-20230213110506-3.png]](% style="display:none" %)
619 +[[image:1664502854406-763.png]]
712 712  
713 -(% style="display:none" %) (%%)
714 714  
715 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
716 -|=(% 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**
622 +(% border="1" style="background-color:#ffffcc; width:510px" %)
623 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
717 717  |(% 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"]]
718 718  |(% 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
719 719  |(% 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.
720 720  
721 -(% style="display:none" %) (%%)
628 +== 2.12 USB Port Function ==
722 722  
723 723  
724 -== 2.13  USB Port Function ==
725 -
726 -
727 727  The USB interface of TrackerD has below functions:
728 728  
729 729  * Power on the device
... ... @@ -731,19 +731,6 @@
731 731  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
732 732  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
733 733  
734 -(% style="display:none" %) (%%)
735 -
736 -
737 -== 2.14  Sleep Mode ==
738 -
739 -
740 -(% 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.
741 -
742 -In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
743 -
744 -Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
745 -
746 -
747 747  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
748 748  
749 749  
... ... @@ -757,22 +757,23 @@
757 757  
758 758  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.
759 759  
760 -[[image:1664502999401-486.png||_mstalt="296985"]]
761 761  
652 +[[image:1664502999401-486.png]]
762 762  
654 +
763 763  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:
764 764  
765 765  
766 -[[image:1664503022490-662.png||_mstalt="293332"]]
658 +[[image:1664503022490-662.png]]
767 767  
768 768  
769 -[[image:1664503035713-500.png||_mstalt="291096"]]
661 +[[image:1664503035713-500.png]]
770 770  
771 771  
772 -[[image:1664503047675-651.png||_mstalt="295386"]]
664 +[[image:1664503047675-651.png]]
773 773  
774 -(% style="display:none" %) (%%)
775 775  
667 +
776 776  == 3.2 Command Set ==
777 777  
778 778  === 3.2.1 Set Transmit Interval ===
... ... @@ -838,7 +838,7 @@
838 838  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
839 839  
840 840  
841 -=== 3.2.5 Disable/Enable LED flash and buzzer ===
733 +=== 3.2.5 Disable/Enable LED flash ===
842 842  
843 843  
844 844  Disable/Enable LED for position, downlink and uplink
... ... @@ -877,6 +877,7 @@
877 877  
878 878  SMOD define how TrackerD scan and uplink data:
879 879  
772 +
880 880  * (% style="color:blue" %)**AT Command:**
881 881  
882 882  (% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
... ... @@ -897,9 +897,9 @@
897 897  
898 898  (% style="color:#037691" %)**cc:   **
899 899  
900 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
793 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
901 901  
902 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
795 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
903 903  
904 904  (% style="color:blue" %)**Example:**
905 905  
... ... @@ -911,7 +911,6 @@
911 911  
912 912   AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
913 913  
914 - AT+SMOD=2,0,3  ~-~->  (iBeacon) (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State
915 915  
916 916  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
917 917  
... ... @@ -923,8 +923,10 @@
923 923  
924 924  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.
925 925  
818 +
926 926  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.
927 927  
821 +
928 928  * (% style="color:blue" %)**AT Command:**
929 929  
930 930  (% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
... ... @@ -942,8 +942,10 @@
942 942  
943 943  PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can't get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.
944 944  
839 +
945 945  A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
946 946  
842 +
947 947  * (% style="color:blue" %)**AT Command:**
948 948  
949 949  (% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
... ... @@ -958,8 +958,8 @@
958 958  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
959 959  
960 960  
961 -=== 3.2.10 Disable/Enable the confirmation mode ===
962 962  
858 +**Disable/Enable the confirmation mode**
963 963  
964 964  * (% style="color:blue" %)**AT Command:**
965 965  
... ... @@ -966,11 +966,11 @@
966 966  (% style="color:#037691" %)**AT+CFM=xx**
967 967  
968 968  
969 -**Example:**
865 +**~ Example:**
970 970  
971 -AT+CFM=0    **~-~->   ** Disable confirmation
867 + AT+CFM=0    **~-~->   ** Disable confirmation
972 972  
973 -AT+CFM=1    **~-~->  ** Enable confirmation
869 + AT+CFM=1    **~-~->  ** Enable confirmation
974 974  
975 975  
976 976  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
... ... @@ -978,7 +978,7 @@
978 978  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
979 979  
980 980  
981 -=== 3.2.11  Auto Send None-ACK messages ===
877 +=== 3.2.10  Auto Send None-ACK messages ===
982 982  
983 983  
984 984  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.
... ... @@ -996,10 +996,10 @@
996 996  
997 997  * (% style="color:blue" %)**Downlink Command: 0x34**
998 998  
999 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
895 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
1000 1000  
1001 1001  
1002 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
898 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
1003 1003  
1004 1004  
1005 1005  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.
... ... @@ -1008,16 +1008,16 @@
1008 1008  
1009 1009  (% style="color:blue" %)**AT Command:**
1010 1010  
1011 -(% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
907 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
1012 1012  
1013 -(% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
909 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
1014 1014  
1015 1015  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
1016 1016  
1017 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
913 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
1018 1018  
1019 1019  
1020 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
916 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
1021 1021  
1022 1022  
1023 1023  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.
... ... @@ -1026,16 +1026,16 @@
1026 1026  
1027 1027  (% style="color:blue" %)**AT Command:**
1028 1028  
1029 -(% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
925 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1030 1030  
1031 -(% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
927 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1032 1032  
1033 1033  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
1034 1034  
1035 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
931 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
1036 1036  
1037 1037  
1038 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
934 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
1039 1039  
1040 1040  
1041 1041  Users can use this feature to enable/disable Information printing.
... ... @@ -1042,11 +1042,11 @@
1042 1042  
1043 1043  (% style="color:blue" %)**AT Command:**
1044 1044  
1045 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
941 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
1046 1046  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1047 1047  
1048 1048  
1049 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
945 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1050 1050  
1051 1051  
1052 1052  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -1053,131 +1053,14 @@
1053 1053  
1054 1054  (% style="color:blue" %)**AT Command:**
1055 1055  
1056 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
952 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1057 1057  
1058 1058  
1059 1059  (% style="color:blue" %)**Downlink Payload:0X24**
1060 1060  
1061 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
957 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
1062 1062  
1063 1063  
1064 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1065 -
1066 -
1067 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1068 -
1069 -(% style="color:blue" %)**AT Command:**
1070 -
1071 -(% style="color:#037691" %)**AT+PT=xx**
1072 -
1073 -Example:
1074 -
1075 -AT+PT=14    ~-~->    Set to detect car motion.
1076 -
1077 -AT+PT=41  ~-~->    set to detect walk motion.
1078 -
1079 -
1080 -(% style="color:blue" %)**Downlink Payload:0xB4**
1081 -
1082 -0xB4 14          ~/~/  Same as AT+PT=14
1083 -
1084 -
1085 -=== 3.2.17  Set AT command window time（Since firmware 1.4.5） ===
1086 -
1087 -
1088 -AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
1089 -
1090 -(% style="color:blue" %)**AT Command:**
1091 -
1092 -(% style="color:#037691" %)**AT+ATST=XX**
1093 -
1094 -Example:
1095 -
1096 -AT+ATST=15    ~-~-> Set the time to 15 seconds
1097 -
1098 -(% style="color:blue" %)**Downlink Payload:0XB5**
1099 -
1100 -0xB5 0F          ~/~/  Same as AT+ATST=15
1101 -
1102 -
1103 -=== 3.2.18  Set the stepmeter mode（Since firmware 1.4.5） ===
1104 -
1105 -
1106 -After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
1107 -
1108 -(% style="color:blue" %)**AT Command:**
1109 -
1110 -(% style="color:#037691" %)**AT+PM=xx**
1111 -
1112 -Example:
1113 -
1114 -AT+PM=1    ~-~->  Turn on step counting mode
1115 -
1116 -AT+PM=0    ~-~->  Turn OFF step counting mode
1117 -
1118 -(% style="color:blue" %)**Downlink Payload:0XB6**
1119 -
1120 -0xB6 01          ~/~/  Same as AT+PM=1
1121 -
1122 -
1123 -=== 3.2.19  Set down the decline detection mode（Since firmware 1.4.5） ===
1124 -
1125 -
1126 -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.
1127 -
1128 -(% style="color:blue" %)**AT Command:**
1129 -
1130 -(% style="color:#037691" %)**AT+FD=xx**
1131 -
1132 -**Example:**
1133 -
1134 -AT+FD=1    ~-~->  Turn on the Fall detection
1135 -
1136 -AT+FD=0    ~-~->  Turn OFF the Fall detection
1137 -
1138 -(% style="color:blue" %)**Downlink Payload:0XB7**
1139 -
1140 -0xB7 01          ~/~/  Same as AT+FD=1
1141 -
1142 -
1143 -=== 3.2.20 Disable/Enable buzzer（Since firmware 1.4.6） ===
1144 -
1145 -
1146 -Disable/Enable buzzer for Alarm, downlink and uplink
1147 -
1148 -(% style="color:blue" %)**AT Command:**
1149 -
1150 -(% style="color:#037691" %)**AT+BEEP=XX**
1151 -
1152 -Example:
1153 -
1154 -AT+BEEP=1 ~-~-> Turn on the buzzer
1155 -
1156 -AT+BEEP=0 ~-~-> Turn OFF the buzzer
1157 -
1158 -(% style="color:blue" %)**Downlink Payload:0XB9**
1159 -
1160 -0xB9 01 ~/~/ Same as AT+BEEP=1
1161 -
1162 -
1163 -=== 3.2.21 Set long press time（Since firmware 1.4.6） ===
1164 -
1165 -
1166 -When using the red button Changan to alarm, press and hold the time to set 0~~10 seconds, which is convenient for use scenarios.
1167 -
1168 -(% style="color:blue" %)**AT Command:**
1169 -
1170 -(% style="color:#037691" %)**AT+EAT=XX**
1171 -
1172 -Example:
1173 -
1174 -AT+EAT=2 ~-~-> Set the long press time to 2s
1175 -
1176 -(% style="color:blue" %)**Downlink Payload:0XBA**
1177 -
1178 -0xBA 02 ~/~/ Same as AT+EAT=2
1179 -
1180 -
1181 1181  = 4. Setting for Different Scenarios =
1182 1182  
1183 1183  
... ... @@ -1210,10 +1210,10 @@
1210 1210  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1211 1211  
1212 1212  
1213 -[[image:1664503563660-578.png||_mstalt="296777"]]
992 +[[image:1664503563660-578.png]]
1214 1214  
1215 1215  
1216 -[[image:1664503574618-659.png||_mstalt="297986"]]
995 +[[image:1664503574618-659.png]]
1217 1217  
1218 1218  
1219 1219  
... ... @@ -1229,15 +1229,16 @@
1229 1229  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1230 1230  
1231 1231  
1232 -[[image:image-20221207120501-1.png]]
1011 +[[image:image-20221118105220-2.png]]
1233 1233  
1234 1234  
1235 1235  
1236 1236  After upgrade finish, it will show finish as below:
1237 1237  
1238 -[[image:image-20221207133911-7.png]]
1017 +[[image:image-20221118105402-4.png]]
1239 1239  
1240 1240  
1020 +
1241 1241  = 6. Developer Guide =
1242 1242  
1243 1243  == 6.1 Compile Source Code ==
... ... @@ -1250,81 +1250,24 @@
1250 1250  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]]
1251 1251  
1252 1252  
1253 -[[image:1664503635019-941.png||_mstalt="294658"]]
1033 +[[image:1664503635019-941.png]]
1254 1254  
1255 1255  
1256 1256  
1257 1257  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1258 1258  
1259 -[[image:1664503715811-892.png||_mstalt="295698"]]
1039 +[[image:1664503715811-892.png]]
1260 1260  
1261 1261  
1262 -=== 6.1.2  Build the development environment ===
1263 -
1264 -
1265 -**~1. Download and install arduino IDE**
1266 -
1267 -[[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]]
1268 -
1269 -
1270 -**2. Download the ESP32 development package in the arduino IDE**
1271 -
1272 -[[image:image-20221213100007-1.png]]
1273 -
1274 -
1275 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1276 -
1277 -[[image:image-20221213100626-2.png]]
1278 -
1279 -
1280 -Restart the IDE after the addition is complete, then:
1281 -
1282 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1283 -
1284 -
1285 -[[image:image-20221213101040-4.png]]
1286 -
1287 -
1288 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1289 -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)**
1290 -
1291 -
1292 -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:
1293 -
1294 -(% style="color:blue" %)**Methods as below:**
1295 -
1296 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1297 -
1298 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1299 -
1300 1300  (% 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.
1301 1301  
1302 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1044 +[[image:image-20221024105643-1.png]]
1303 1303  
1304 -
1305 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1306 -
1307 -[[image:image-20221213102334-6.png]]
1308 -
1309 -(% style="color:red" %)**Note: This step requires a python environment**
1310 -
1311 -
1312 -Either way, in the end:
1313 -
1314 -The final effect is to open the arduino and you can see the esp32
1315 -
1316 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1317 -
1318 -
1319 -
1320 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1321 -
1322 1322  **~ Figure1**
1323 1323  
1324 1324  
1049 +[[image:image-20221024105643-2.png]]
1325 1325  
1326 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1327 -
1328 1328   **Figure2**
1329 1329  
1330 1330  
... ... @@ -1333,7 +1333,7 @@
1333 1333  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1334 1334  
1335 1335  
1336 -[[image:1664503752288-974.png||_mstalt="298194"]]
1059 +[[image:1664503752288-974.png]]
1337 1337  
1338 1338  
1339 1339  == 6.2 Source Code ==
... ... @@ -1341,19 +1341,19 @@
1341 1341  
1342 1342  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1343 1343  
1344 -[[image:1664503794261-827.png||_mstalt="296387"]]
1067 +[[image:1664503794261-827.png]]
1345 1345  
1346 1346  
1347 1347  
1348 1348  * (% style="color:blue" %)**Click to upload**
1349 1349  
1350 -[[image:1664503808294-336.png||_mstalt="295711"]]
1073 +[[image:1664503808294-336.png]]
1351 1351  
1352 1352  
1353 1353  
1354 1354  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1355 1355  
1356 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1079 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1357 1357  
1358 1358  
1359 1359  = 7.  FAQ =
... ... @@ -1367,11 +1367,12 @@
1367 1367  == 7.2 What is the pin mapping for the USB program cable? ==
1368 1368  
1369 1369  
1370 -[[image:1664499635206-262.png||_mstalt="295360"]]
1093 +[[image:1664499635206-262.png]]
1371 1371  
1372 1372  
1373 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:314px" %)
1374 -|=(% 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**
1096 +
1097 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
1098 +|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
1375 1375  |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1376 1376  |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1377 1377  |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
... ... @@ -1381,9 +1381,6 @@
1381 1381  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1382 1382  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1383 1383  
1384 -(% style="display:none" %) (%%)
1385 -
1386 -
1387 1387  == 7.3 Notes on using different serial port tools for TrackerD ==
1388 1388  
1389 1389  === 7.3.1  Serial port utility ===
... ... @@ -1394,12 +1394,13 @@
1394 1394  Need to adjust the data stream to RTS/CTS on physical restart.
1395 1395  
1396 1396  (% class="wikigeneratedid" %)
1397 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1118 +[[image:image-20221102140621-1.png]]
1398 1398  
1399 1399  
1121 +
1400 1400  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1401 1401  
1402 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1124 +[[image:image-20221102140638-2.png]]
1403 1403  
1404 1404  
1405 1405  === 7.3.2  SecureCRT ===
... ... @@ -1408,22 +1408,22 @@
1408 1408  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.
1409 1409  
1410 1410  
1411 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1133 +[[image:image-20221102140704-3.png]]
1412 1412  
1413 1413  
1414 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1136 +[[image:image-20221102140712-4.png]]
1415 1415  
1416 1416  
1417 1417  === 7.3.3  PUTTY ===
1418 1418  
1419 1419  
1420 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1142 +[[image:image-20221102140748-5.png]]
1421 1421  
1422 1422  
1423 1423  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.
1424 1424  
1425 1425  
1426 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1148 +[[image:image-20221102140801-6.png]]
1427 1427  
1428 1428  
1429 1429  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1438,7 +1438,7 @@
1438 1438  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1439 1439  
1440 1440  
1441 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1163 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1442 1442  
1443 1443  
1444 1444  
... ... @@ -1445,7 +1445,7 @@
1445 1445  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1446 1446  
1447 1447  
1448 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1170 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1449 1449  
1450 1450  
1451 1451  
... ... @@ -1452,7 +1452,7 @@
1452 1452  **3. Compile the AS923_JP band, please refer to the intention shown**
1453 1453  
1454 1454  
1455 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1177 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1456 1456  
1457 1457  
1458 1458  
... ... @@ -1459,24 +1459,12 @@
1459 1459  **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.**
1460 1460  
1461 1461  
1462 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1184 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1463 1463  
1464 1464  
1465 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1187 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1466 1466  
1467 1467  
1468 -== 7.5 Are there example python example for BLE Indoor Positioning? ==
1469 -
1470 -
1471 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1472 -
1473 -
1474 -== 7.6 Can alert mode and transport mode be used together? ==
1475 -
1476 -
1477 -Yes, you can also press the panic button to sound the alarm if set to transport mode
1478 -
1479 -
1480 1480  = 8  Trouble Shooting =
1481 1481  
1482 1482  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
... ... @@ -1483,7 +1483,7 @@
1483 1483  
1484 1484  
1485 1485  (((
1486 -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
1196 +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
1487 1487  )))
1488 1488  
1489 1489  
... ... @@ -1497,68 +1497,50 @@
1497 1497  
1498 1498  == 8.3  Problem after Upgrading Firmware ==
1499 1499  
1500 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1210 +=== 8.3.1 Continue Restart after upgrading ===
1501 1501  
1502 1502  
1503 -**Error Output**
1504 -
1505 -
1506 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1507 -
1508 -
1509 1509  (((
1510 -Some partition is missed during upgrade, please upgrade below four files as example:
1511 -
1512 -[[image:image-20221207120524-2.png]]
1214 +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
1513 1513  )))
1514 1514  
1515 1515  
1516 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1218 +[[image:image-20221118105249-3.png]]
1517 1517  
1518 1518  
1519 -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
1221 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1520 1520  
1521 1521  
1522 -=== 8.3.3 "flash read err" after upgrade firmware ===
1224 +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
1523 1523  
1524 1524  
1227 +=== 8.3.3 "flash read err" after upgrade firmware ===
1228 +
1525 1525  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1526 1526  
1527 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1231 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1528 1528  
1529 1529  
1530 1530  User need to upgrade again with below four files to solve this issue.
1531 1531  
1532 - [[image:image-20221207120530-3.png]]
1236 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1533 1533  
1534 1534   **Figure 2**
1535 1535  
1536 1536  
1537 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1241 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1538 1538  
1539 -
1540 1540  User might erase the entire flash include keys and default settings which cause this issue.
1541 1541  
1542 -After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below.
1245 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1543 1543  
1247 +[[image:image-20221122100004-3.png]]
1544 1544  
1545 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1249 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1546 1546  
1547 1547  
1548 -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.
1252 +Example:
1549 1549  
1550 -After AT+FDR. please set
1551 -
1552 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1553 -
1554 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1555 -
1556 -**Example:**
1557 -
1558 -AT+PDOP=7.00
1559 -
1560 -AT+FTIME=180
1561 -
1562 1562  AT+DEUI=70B3D57ED0053981  
1563 1563  
1564 1564  AT+APPEUI=D23345667BCBCCAF
... ... @@ -1572,6 +1572,13 @@
1572 1572  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1573 1573  
1574 1574  
1267 +
1268 +=== 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 ===
1269 +
1270 +
1271 +[[image:image-20221122100004-4.png]]
1272 +
1273 +
1575 1575  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1576 1576  
1577 1577  
... ... @@ -1585,68 +1585,15 @@
1585 1585  
1586 1586  2)  Set PDOP to a higher value.
1587 1587  
1588 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1287 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1589 1589  
1590 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1289 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1591 1591  
1592 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1291 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1593 1593  
1594 1594  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
1595 1595  
1596 1596  
1597 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1598 -
1599 -
1600 -When upgrading, use the erase button to upgrade
1601 -
1602 -[[image:image-20221207120536-4.png]]
1603 -
1604 -
1605 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1606 -
1607 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1608 -
1609 -
1610 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1611 -
1612 -[[image:image-20221207134028-8.png]]
1613 -
1614 -
1615 -Reboot information after upgrade
1616 -
1617 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1618 -
1619 -
1620 -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
1621 -
1622 -[[image:image-20221128111850-5.png]]
1623 -
1624 -
1625 -After the parameters return to normal, upgrade to the version you need again
1626 -
1627 -[[image:image-20221207120601-5.png]]
1628 -
1629 -
1630 -At this point, the parameters return to normal after running AT+FDR again
1631 -
1632 -[[image:image-20221128112035-7.png]]
1633 -
1634 -
1635 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1636 -
1637 -
1638 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1639 -
1640 -2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1641 -
1642 -
1643 -== 8.8  Why when using some serial consoles, only inputting the first string port console will return "error"? ==
1644 -
1645 -
1646 -Need to enter the entire command at once, not a single character.
1647 -User can open a command window or copy the entire command to the serial console.
1648 -
1649 -
1650 1650  = 9.  Order Info =
1651 1651  
1652 1652  
... ... @@ -1668,9 +1668,6 @@
1668 1668  
1669 1669  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1670 1670  
1671 -(% style="display:none" %) (%%)
1672 -
1673 -
1674 1674  = 10.  Packing Info =
1675 1675  
1676 1676  
... ... @@ -1686,9 +1686,6 @@
1686 1686  
1687 1687  * Weight: 50g
1688 1688  
1689 -(% style="display:none" %) (%%)
1690 -
1691 -
1692 1692  = 11. Support =
1693 1693  
1694 1694  
... ... @@ -1696,10 +1696,6 @@
1696 1696  
1697 1697  * 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]].
1698 1698  
1699 -(% style="display:none" %)
1700 -
1701 -
1702 -
1703 1703  = 12.  Reference =
1704 1704  
1705 1705  
... ... @@ -1708,6 +1708,3 @@
1708 1708  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1709 1709  
1710 1710  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1711 -
1712 -
1713 -)))
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
image-20231023103116-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -48.2 KB
Content