Last modified by Bei Jinggeng on 2025/07/23 11:03

From version 113.5
edited by Xiaoling
on 2022/11/09 16:24
Change comment: There is no comment for this version
To version 54.1
edited by Edwin Chen
on 2022/10/06 18:13
Change comment: Uploaded new attachment "image-20221006181357-2.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -98,7 +98,6 @@
98 98  * Tracking: max: 38mA
99 99  
100 100  
101 -
102 102  == 1.3  Features ==
103 103  
104 104  
... ... @@ -118,7 +118,6 @@
118 118  * Datalog
119 119  
120 120  
121 -
122 122  == 1.4  Applications ==
123 123  
124 124  
... ... @@ -126,10 +126,9 @@
126 126  * Human tracking
127 127  
128 128  
127 += 2.1 Use TrackerD =
129 129  
130 -= 2.  Use TrackerD =
131 131  
132 -
133 133  == 2.1 How it works? ==
134 134  
135 135  
... ... @@ -178,10 +178,11 @@
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||alt="1654671889112-678.png"]]
178 +[[image:1664501784668-703.png]]
182 182  
183 183  
184 184  
182 +
185 185  (% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
186 186  
187 187  
... ... @@ -188,132 +188,42 @@
188 188  (% 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.
189 189  
190 190  
189 += 2.3 Positioning Mode(SMOD) =
191 191  
192 -== 2.3  Positioning Mode(SMOD) ==
191 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get GPS location info.
192 +* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking.
193 +* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.
193 193  
195 +User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
194 194  
195 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
196 196  
197 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
198 -* (% style="color:#037691" %)**BLE or WiFi ONLY:            **(%%)** **Only obtain iBeacon info via BLE and uplink  or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking.
199 -* (% style="color:#037691" %)**GPS/BLE Hybrid:                        **(%%)Combination for Indoor and Outdoor tracking. Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
200 200  
201 -Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
199 +== 2.3 Uplink Payload ==
202 202  
203 203  
202 +=== 2.3.1 Uplink FPORT~=5, Device Status ===
204 204  
205 -== 2.4  Uplink Payload ==
206 206  
207 207  
208 -=== 2.4.1 Uplink FPORT~=5, Device Status ===
206 +=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
209 209  
210 210  
211 -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.
209 +The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won't work on DR0 on US915/AU915 frequency band. )
212 212  
213 -Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
214 214  
215 -
216 -(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
217 -|=(% 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
218 -|=(% 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
219 -
220 -[[image:1665301570342-765.png]]
221 -
222 -
223 -(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
224 -
225 -(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
226 -
227 -(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
228 -
229 -(% style="color:#037691" %)**Frequency Band**:
230 -
231 -*0x01: EU868
232 -
233 -*0x02: US915
234 -
235 -*0x03: IN865
236 -
237 -*0x04: AU915
238 -
239 -*0x05: KZ865
240 -
241 -*0x06: RU864
242 -
243 -*0x07: AS923
244 -
245 -*0x08: AS923-1
246 -
247 -*0x09: AS923-2
248 -
249 -*0x0a: AS923-3
250 -
251 -Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
252 -
253 -(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
254 -
255 -
256 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
257 -
258 -Use can also get the Device Status uplink through the downlink command:
259 -
260 -
261 -(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40
262 -
263 -(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
264 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
265 -|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
266 -
267 -(% style="color:blue" %)** SMOD:**
268 -
269 -(% style="color:red" %)** 1 :** (%%) GPS ONLY
270 -
271 -(% style="color:red" %)** 2 :** (%%) BLE ONLY
272 -
273 -(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
274 -
275 -
276 -(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
277 -
278 -(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
279 -
280 -(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
281 -
282 -
283 -(% style="color:blue" %)** BLE_Settings:**
284 -
285 -(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
286 -
287 -(% style="color:red" %)** 2:**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
288 -
289 -
290 -(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
291 -
292 -(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
293 -|=(% 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
294 -|=(% 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 -
296 -
297 -
298 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
299 -
300 -
301 -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,
302 -
303 -
304 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
305 -|=(% scope="row" style="width: 60px;" %)(((
212 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
213 +|=(% scope="row" style="width: 50px;" %)(((
306 306  **Size(bytes)**
307 -)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
308 -2
309 -)))|(% style="width:30px" %)(((
310 -2
215 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
216 +2(optional)
217 +)))|(% style="width:87px" %)(((
218 +2(optional)
311 311  )))
312 312  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
313 313  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
314 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
222 +)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
315 315  
316 -[[image:1665301636888-168.png]]
224 +[[image:1664501958445-288.png]]
317 317  
318 318  
319 319  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -322,13 +322,11 @@
322 322  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
323 323  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
324 324  
325 -
326 -
327 327  ==== (% style="color:blue" %)**FLAG:**(%%) ====
328 328  
329 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
330 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
331 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
235 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
236 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits
237 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 
332 332  
333 333  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
334 334  
... ... @@ -338,18 +338,22 @@
338 338  * Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
339 339  * Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
340 340  
247 +
341 341  (% style="color:red" %)**Important note:**
342 342  
343 343  1.  When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF.
344 344  
345 -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:
252 +2.  In firmware version v1.5, Roll & Pitch is disabled by default.
346 346  
254 +3.  When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
347 347  
256 +
348 348  [[image:1664502116362-706.png]]
349 349  
350 350  
351 -3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
352 352  
261 +4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
262 +
353 353  [[image:1664502166010-515.png]]
354 354  
355 355  
... ... @@ -356,15 +356,15 @@
356 356  
357 357  ==== (% style="color:blue" %)**Alarm:**(%%) ====
358 358  
359 -**Example: ** 0x4B & 0x40 >> 6 = 0x01
269 +Example:  0x4B & 0x40 >> 6 = 0x01
360 360  
361 361  
362 362  ==== (% style="color:blue" %)**BAT:**(%%) ====
363 363  
364 -**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
274 +Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
365 365  
366 366  (((
367 -The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
277 +The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \
368 368  )))
369 369  
370 370  * > 4.0v :  80% ~~ 100%
... ... @@ -374,34 +374,17 @@
374 374  * < 3.39v:  0~~20%
375 375  
376 376  
377 -
378 -==== (% style="color:blue" %)**MOD:**(%%) ====
379 -
380 -**Example: ** (0x60>>6) & 0x3f =1
381 -
382 -**Set the format of GPS data uplink link:**
383 -
384 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
385 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
386 -
387 -
388 -**Set the format of BLE data uplink link:**
389 -
390 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
391 -
392 -
393 393  ==== (% style="color:blue" %)**LON:**(%%) ====
394 394  
395 -**Example:** (0x60>>5) & 0x01=1.
396 396  
397 397  Enable/Disable LED activity for uplink
398 398  
399 399  (((
400 -(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
293 +0x00:  Disable LED indicator.
401 401  )))
402 402  
403 403  (((
404 -(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
297 +0x01:  Enable LED indicator (Default Value)
405 405  )))
406 406  
407 407  
... ... @@ -416,57 +416,15 @@
416 416  
417 417  
418 418  
419 -=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
312 +=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
420 420  
421 421  
422 -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)
423 423  
316 +=== 2.3.4 BLE positioning Payload(Fport2) ===
424 424  
425 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
426 -|=(% scope="row" style="width: 60px;" %)(((
427 -**Size(bytes)**
428 -)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
429 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
430 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
431 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
432 432  
433 -(% class="wikigeneratedid" %)
434 -[[image:1665301687277-443.png]]
319 +Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
435 435  
436 -
437 -
438 -=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
439 -
440 -
441 -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.
442 -
443 -
444 -(% style="color:red" %)**Note for this mode:**
445 -
446 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
447 -* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
448 -* c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL
449 -
450 -The payload is 15 bytes, as below.
451 -
452 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
453 -|=(% scope="row" %)(((
454 -**Size(bytes)**
455 -)))|4|4|2|1|1|1|1|1
456 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
457 -
458 -[[image:image-20221009160309-2.png]]
459 -
460 -
461 -
462 -=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
463 -
464 -
465 -TrackerD supports BLE scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan BLE iBeacon and find the strongest iBeacon info and uplink.
466 -
467 -User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
468 -
469 -
470 470  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
471 471  |=(% scope="row" style="width: 60px;" %)(((
472 472  **Size(bytes)**
... ... @@ -486,7 +486,7 @@
486 486  [[image:1664502425687-834.png]]
487 487  
488 488  
489 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
340 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
490 490  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
491 491  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
492 492  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
... ... @@ -495,36 +495,11 @@
495 495  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
496 496  
497 497  
349 +=== 2.3.5 Add Payload format in TTN V3 ===
498 498  
499 -=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) ===
500 500  
352 +In TTN V3, use can add a custom payload so it shows friendly.
501 501  
502 -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.
503 -
504 -
505 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
506 -|=(% scope="row" style="width: 60px;" %)(((
507 -**Size(bytes)**
508 -)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
509 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
510 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
511 -)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
512 -
513 -(% class="wikigeneratedid" %)
514 -[[image:1667288597595-714.png||height="212" width="1151"]]
515 -
516 -
517 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
518 -* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
519 -* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
520 -
521 -
522 -
523 -=== 2.4.7  Add Payload format in TTN V3 ===
524 -
525 -
526 -In TTN V3, user can add a custom payload so it shows friendly.
527 -
528 528  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
529 529  
530 530  
... ... @@ -531,9 +531,8 @@
531 531  [[image:1664502649601-895.png]]
532 532  
533 533  
534 -Add the decoder from this link: 
360 +Add the decoder from this link:
535 535  
536 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
537 537  
538 538  Save the change the uplink message will be parsed. As below:
539 539  
... ... @@ -541,12 +541,16 @@
541 541  
542 542  
543 543  
544 -== 2.5 Integrate with Datacake ==
369 +== 2.4 Integrate with Datacake ==
545 545  
546 546  
372 +(((
547 547  After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
374 +)))
548 548  
376 +(((
549 549  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]]
378 +)))
550 550  
551 551  
552 552  [[image:1664502695771-538.png]]
... ... @@ -553,12 +553,16 @@
553 553  
554 554  
555 555  
556 -== 2.6 Integrate with Tago ==
385 +== 2.5 Integrate with Tago ==
557 557  
558 558  
559 -After TrackerD sends data to LoRaWAN server such as TTN, user can pass the data to Datacake and plot out, currently only support GPS plot.
388 +(((
389 +After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
390 +)))
560 560  
392 +(((
561 561  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]]
394 +)))
562 562  
563 563  
564 564  [[image:1664502715371-321.png]]
... ... @@ -565,25 +565,9 @@
565 565  
566 566  
567 567  
568 -== 2. Datalog Feature ==
401 +== 2.6 Alarm Mode ==
569 569  
570 570  
571 -total 273 entries,by default,
572 -
573 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
574 -
575 -Example use case.
576 -
577 -[[image:image-20221009234703-2.png||height="328" width="899"]]
578 -
579 -
580 -[[image:image-20221009234629-1.png||height="390" width="577"]]
581 -
582 -
583 -
584 -== 2.8 Alarm Mode ==
585 -
586 -
587 587  (((
588 588  User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
589 589  )))
... ... @@ -590,7 +590,7 @@
590 590  
591 591  
592 592  (((
593 -Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exits alert mode.
410 +Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode.
594 594  )))
595 595  
596 596  
... ... @@ -598,7 +598,7 @@
598 598  Two ways to exit alarm mode:
599 599  )))
600 600  
601 -* Server sends a downlink command to exit.
418 +* Server send a downlink command to exit.
602 602  * User fast press the RED button 10 times.
603 603  
604 604  (((
... ... @@ -607,16 +607,13 @@
607 607  
608 608  
609 609  
610 -== 2.9 Transport Mode ==
427 +== 2.7 Sports Mode ==
611 611  
612 612  
613 -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.
614 614  
431 +== 2.8 LED Status ==
615 615  
616 616  
617 -== 2.10 LED Status ==
618 -
619 -
620 620  (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
621 621  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
622 622  |(% 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
... ... @@ -632,10 +632,9 @@
632 632  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
633 633  
634 634  
449 +== 2.9 Button Function ==
635 635  
636 -== 2.11 Button Function ==
637 637  
638 -
639 639  (% style="color:blue" %)**RESET button:**
640 640  
641 641  [[image:1664502835802-546.png]]
... ... @@ -648,17 +648,16 @@
648 648  [[image:1664502854406-763.png]]
649 649  
650 650  
651 -(% border="1" style="background-color:#ffffcc; color:green; width:510px" %)
652 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
464 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
465 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
653 653  |(% 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.6AlarmMode"]]
654 654  |(% 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
655 655  |(% 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.
656 656  
657 657  
471 +== 2.10 USB Port Function ==
658 658  
659 -== 2.12 USB Port Function ==
660 660  
661 -
662 662  The USB interface of TrackerD has below functions:
663 663  
664 664  * Power on the device
... ... @@ -667,7 +667,6 @@
667 667  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
668 668  
669 669  
670 -
671 671  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
672 672  
673 673  
... ... @@ -692,9 +692,11 @@
692 692  [[image:1664503022490-662.png]]
693 693  
694 694  
506 +
695 695  [[image:1664503035713-500.png]]
696 696  
697 697  
510 +
698 698  [[image:1664503047675-651.png]]
699 699  
700 700  
... ... @@ -738,21 +738,21 @@
738 738  
739 739  
740 740  
741 -=== 3.2.3 Set Transport Mode Packet transmission interval ===
554 +=== 3.2.3 Set Sports Mode Packet transmission interval ===
742 742  
743 743  
744 -Set Transport Mode packet transmit interval
557 +Set sports packet transmit interval
745 745  
746 746  * (% style="color:blue" %)**AT Command:**
747 747  
748 748  (% style="color:#037691" %)**AT+MTDC=xx. **
749 749  
750 -Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
563 +Example:  AT+MTDC=300000  **~-~->    ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
751 751  
752 752  
753 753  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
754 754  
755 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
568 +(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
756 756  
757 757  
758 758  
... ... @@ -787,21 +787,21 @@
787 787  
788 788  
789 789  
790 -=== 3.2.6 Disable/Enable Transport Mode ===
603 +=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
791 791  
792 792  
793 -Users can use this feature to enable/disable Transport Mode.
606 +User can use this feature to check and set thread hole of movement detect
794 794  
795 795  * (% style="color:blue" %)**AT Command:**
796 796  
797 797  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
798 798  
799 -Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
612 +Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
800 800  
801 801  
802 802  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
803 803  
804 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
617 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
805 805  
806 806  
807 807  
... ... @@ -808,47 +808,35 @@
808 808  === 3.2.7 Set Positioning Mode ===
809 809  
810 810  
811 -SMOD define how TrackerD scan and uplink data:
624 +SMOD define the how TrackerD scan and uplink date.
812 812  
626 +GPS室外定位模式:  设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。
813 813  
814 -* (% style="color:blue" %)**AT Command:**
628 +BLE室内定位模式:  设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。
815 815  
816 -(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
630 +GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。
817 817  
818 -(% style="color:#037691" %)** aa:**
632 +运动模式:  设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。
819 819  
820 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
821 821  
822 -* (% style="color:red" %)**2: BLE or WiFi ONLY:                     **(%%)Only obtain iBeacon info via BLE and uplink  or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking.
823 823  
824 -* (% style="color:red" %)**3: GPS/BLE Hybrid:                       **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
636 +* (% style="color:blue" %)**AT Command:**
825 825  
826 -(% style="color:#037691" %)**bb:**
638 +(% style="color:#037691" %)**AT+SMOD=xx. **
827 827  
828 -* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
829 829  
830 -* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
641 + **Example:**
831 831  
832 -(% style="color:#037691" %)**cc:   **
643 + AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
833 833  
834 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
835 -
836 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
645 + AT+ SMOD =1,1    **~-~->**  GPS +BAT State
837 837  
838 -(% style="color:blue" %)**Example:**
647 + AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
839 839  
840 - AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
841 841  
842 - AT+SMOD=1,1,0 ~-~->  GPS +BAT State
843 -
844 - AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
845 -
846 - AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
847 -
848 -
849 849  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
850 850  
851 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
652 +(% style="color:#037691" %)**0xA5 01 00**    (%%) ~/~/  Same as AT+ SMOD =1,0
852 852  
853 853  
854 854  
... ... @@ -865,7 +865,7 @@
865 865  
866 866  (% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
867 867  
868 -**Example:**  AT+FTIME=150
669 +Example:  AT+FTIME=150
869 869  
870 870  
871 871  * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
... ... @@ -874,7 +874,7 @@
874 874  
875 875  
876 876  
877 -=== 3.2.9 Set PDOP value for GPS fix accuracy ===
678 +=== 3.3.9 Set PDOP value for GPS fix accuracy ===
878 878  
879 879  
880 880  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.
... ... @@ -902,110 +902,22 @@
902 902  
903 903  * (% style="color:blue" %)**AT Command:**
904 904  
905 -(% style="color:#037691" %)**AT+CFM=xx**
706 +(% style="color:#037691" %)**AT+CFM=xx. **
906 906  
907 907  
908 908  **~ Example:**
909 909  
910 - AT+CFM=0    **~-~->   ** Disable confirmation
711 + AT+ CFM=0    **~-~->   ** Disable confirmation
911 911  
912 - AT+CFM=1    **~-~->  ** Enable confirmation
713 + AT+ CFM=1    **~-~->  ** Enable confirmation
913 913  
914 914  
915 915  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
916 916  
917 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
718 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
918 918  
919 919  
920 920  
921 -=== 3.2.10  Auto Send None-ACK messages ===
922 -
923 -
924 -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.
925 -
926 -
927 -* (% style="color:blue" %)**AT Command: AT+PNACKMD**
928 -
929 -The default factory setting is 0.
930 -
931 -
932 -**Command Example Function Response:**
933 -
934 -(% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
935 -
936 -
937 -* (% style="color:blue" %)**Downlink Command: 0x34**
938 -
939 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
940 -
941 -
942 -
943 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
944 -
945 -
946 -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.
947 -
948 -(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
949 -
950 -(% style="color:blue" %)**AT Command:**
951 -
952 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
953 -
954 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
955 -
956 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)**
957 -
958 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
959 -
960 -
961 -
962 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===
963 -
964 -
965 -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.
966 -
967 -(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
968 -
969 -(% style="color:blue" %)**AT Command:**
970 -
971 - (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
972 -
973 - (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
974 -
975 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)**
976 -
977 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
978 -
979 -
980 -
981 -=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) ===
982 -
983 -
984 -Users can use this feature to enable/disable Information printing.
985 -
986 -(% style="color:blue" %)**AT Command:**
987 -
988 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
989 -\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
990 -
991 -
992 -
993 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===
994 -
995 -
996 -The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
997 -
998 -(% style="color:blue" %)**AT Command:**
999 -
1000 -(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1001 -
1002 -
1003 -(% style="color:blue" %)**Downlink Payload:0X24**
1004 -
1005 -Example: 0x24 01 ~/~/ Same as AT+CHE=1
1006 -
1007 -
1008 -
1009 1009  = 4. Setting for Different Scenarios =
1010 1010  
1011 1011  
... ... @@ -1046,10 +1046,9 @@
1046 1046  [[image:1664503574618-659.png]]
1047 1047  
1048 1048  
1049 -
1050 1050  (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
1051 1051  
1052 -[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
764 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1053 1053  
1054 1054  
1055 1055  Users need to use below files:
... ... @@ -1086,24 +1086,12 @@
1086 1086  [[image:1664503635019-941.png]]
1087 1087  
1088 1088  
1089 -
1090 1090  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1091 1091  
1092 1092  [[image:1664503715811-892.png]]
1093 1093  
1094 1094  
1095 -(% 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.
1096 1096  
1097 -[[image:image-20221024105643-1.png]]
1098 -
1099 -**~ Figure1**
1100 -
1101 -
1102 -[[image:image-20221024105643-2.png]]
1103 -
1104 - **Figure2**
1105 -
1106 -
1107 1107  * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1108 1108  
1109 1109  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
... ... @@ -1164,90 +1164,9 @@
1164 1164  
1165 1165  
1166 1166  
1167 -== 7.3 Notes on using different serial port tools for TrackerD ==
867 += 8.  Order Info =
1168 1168  
1169 1169  
1170 -=== 7.3.1  Serial port utility ===
1171 -
1172 -
1173 -Serial port utility requires you to automatically add data streams.
1174 -
1175 -Need to adjust the data stream to RTS/CTS on physical restart.
1176 -
1177 -
1178 -(% class="wikigeneratedid" %)
1179 -[[image:image-20221102140621-1.png]]
1180 -
1181 -
1182 -When using AT commands, the data flow needs to be adjusted to XON/XOFF
1183 -
1184 -
1185 -[[image:image-20221102140638-2.png]]
1186 -
1187 -
1188 -
1189 -=== 7.3.2  SecureCRT ===
1190 -
1191 -
1192 -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.
1193 -
1194 -
1195 -[[image:image-20221102140704-3.png]]
1196 -
1197 -
1198 -[[image:image-20221102140712-4.png]]
1199 -
1200 -
1201 -
1202 -=== 7.3.3  PUTTY ===
1203 -
1204 -
1205 -[[image:image-20221102140748-5.png]]
1206 -
1207 -
1208 -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.
1209 -
1210 -
1211 -[[image:image-20221102140801-6.png]]
1212 -
1213 -
1214 -
1215 -= 8  Trouble Shooting =
1216 -
1217 -
1218 -== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1219 -
1220 -
1221 -(((
1222 -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
1223 -)))
1224 -
1225 -
1226 -
1227 -== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1228 -
1229 -
1230 -(((
1231 -ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.
1232 -)))
1233 -
1234 -
1235 -
1236 -== 8.3  The reason why it has been restarted after upgrading(V.1.4.1) ==
1237 -
1238 -
1239 -(((
1240 -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
1241 -)))
1242 -
1243 -
1244 -[[image:image-20221107145243-1.png||height="695" width="443"]]
1245 -
1246 -
1247 -
1248 -= 9.  Order Info =
1249 -
1250 -
1251 1251  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1252 1252  
1253 1253  (% style="color:blue" %)**XXX**(%%): The default frequency band
... ... @@ -1261,10 +1261,9 @@
1261 1261  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1262 1262  
1263 1263  
883 += 9.  Packing Info =
1264 1264  
1265 -= 10.  Packing Info =
1266 1266  
1267 -
1268 1268  (% style="color:#037691" %)**Package Includes**:
1269 1269  
1270 1270  * TrackerD LoRaWAN GPS/BLE Tracker x 1
... ... @@ -1272,22 +1272,20 @@
1272 1272  
1273 1273  (% style="color:#037691" %)**Dimensions and Weight**:
1274 1274  
1275 -* Device Size: 85 x 48 x 15 mm
893 +* Device Size: 85 x 48 x 15 cm
1276 1276  * Weight: 50g
1277 1277  
1278 1278  
897 += 10. Support =
1279 1279  
1280 -= 11. Support =
1281 1281  
1282 -
1283 1283  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1284 1284  * 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]].
1285 1285  
1286 1286  
904 += 11.  Reference =
1287 1287  
1288 -= 12.  Reference =
1289 1289  
1290 -
1291 1291  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1292 1292  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1293 1293  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1665301570342-765.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.6 KB
Content
1665301636888-168.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.6 KB
Content
1665301687277-443.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.6 KB
Content
1665301786397-168.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.6 KB
Content
1667288597595-714.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -27.9 KB
Content
image-20221009160220-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.4 KB
Content
image-20221009160309-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -57.2 KB
Content
image-20221009234629-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -222.9 KB
Content
image-20221009234703-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -136.4 KB
Content
image-20221024105643-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.3 KB
Content
image-20221024105643-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -64.5 KB
Content
image-20221102140621-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -46.1 KB
Content
image-20221102140638-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -40.8 KB
Content
image-20221102140704-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -15.5 KB
Content
image-20221102140712-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -73.2 KB
Content
image-20221102140748-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -56.0 KB
Content
image-20221102140801-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -21.0 KB
Content
image-20221107145243-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -107.3 KB
Content