Skip to Content
Last modified by Bei Jinggeng on 2025/07/23 11:03
From version 113.2
edited by Xiaoling
on 2022/11/09 15:43
Change comment: There is no comment for this version
To version 51.32
edited by Xiaoling
on 2022/09/30 16:48
Change comment: There is no comment for this version

Summary

Details

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