Skip to Content
Last modified by Bei Jinggeng on 2025/08/01 17:45
From version 124.1
edited by Bei Jinggeng
on 2022/11/16 17:45
Change comment: There is no comment for this version
To version 53.1
edited by Edwin Chen
on 2022/10/06 18:13
Change comment: Uploaded new attachment "image-20221006181316-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Edwin
Content
... ... @@ -97,6 +97,7 @@
97 97  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
98 98  * Tracking: max: 38mA
99 99  
100 +
100 100  == 1.3  Features ==
101 101  
102 102  
... ... @@ -115,6 +115,7 @@
115 115  * Tri-color LED, Alarm button
116 116  * Datalog
117 117  
119 +
118 118  == 1.4  Applications ==
119 119  
120 120  
... ... @@ -121,9 +121,10 @@
121 121  * Logistics and Supply Chain Management
122 122  * Human tracking
123 123  
124 -= 2.  Use TrackerD =
125 125  
127 += 2.1 Use TrackerD =
126 126  
129 +
127 127  == 2.1 How it works? ==
128 128  
129 129  
... ... @@ -172,143 +172,53 @@
172 172  **__Add APP KEY and DEV EUI:__**
173 173  
174 174  
175 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
178 +[[image:1664501784668-703.png]]
176 176  
177 177  
178 178  
179 -(% style="color:blue" %)**Step 2**:(%%) Push this button will reboot the device.
180 180  
181 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
183 +(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
182 182  
183 183  
184 -
185 185  (% 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.
186 186  
187 187  
189 += 2.3 Positioning Mode(SMOD) =
188 188  
189 -== 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.
190 190  
195 +User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
191 191  
192 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
193 193  
194 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
195 -* (% 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.
196 -* (% 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.
197 197  
198 -Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
199 +== 2.3 Uplink Payload ==
199 199  
200 200  
202 +=== 2.3.1 Uplink FPORT~=5, Device Status ===
201 201  
202 -== 2.4  Uplink Payload ==
203 203  
204 204  
205 -=== 2.4.1 Uplink FPORT~=5, Device Status ===
206 +=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
206 206  
207 207  
208 -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. )
209 209  
210 -Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
211 211  
212 -
213 -(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
214 -|=(% 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
215 -|=(% 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 -
217 -[[image:1665301570342-765.png]]
218 -
219 -
220 -(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
221 -
222 -(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
223 -
224 -(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
225 -
226 -(% style="color:#037691" %)**Frequency Band**:
227 -
228 -*0x01: EU868
229 -
230 -*0x02: US915
231 -
232 -*0x03: IN865
233 -
234 -*0x04: AU915
235 -
236 -*0x05: KZ865
237 -
238 -*0x06: RU864
239 -
240 -*0x07: AS923
241 -
242 -*0x08: AS923-1
243 -
244 -*0x09: AS923-2
245 -
246 -*0x0a: AS923-3
247 -
248 -Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
249 -
250 -(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
251 -
252 -
253 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
254 -
255 -Use can also get the Device Status uplink through the downlink command:
256 -
257 -
258 -(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
259 -
260 -(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
261 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
262 -|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
263 -
264 -(% style="color:blue" %)** SMOD：**
265 -
266 -(% style="color:red" %)** 1 :** (%%) GPS ONLY
267 -
268 -(% style="color:red" %)** 2 :** (%%) BLE ONLY
269 -
270 -(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
271 -
272 -
273 -(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
274 -
275 -(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
276 -
277 -(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
278 -
279 -
280 -(% style="color:blue" %)** BLE_Settings:**
281 -
282 -(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
283 -
284 -(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
285 -
286 -
287 -(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
288 -
289 -(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
290 -|=(% 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
291 -|=(% 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"]]
292 -
293 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
294 -
295 -
296 -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 -
298 -
299 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
300 -|=(% 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;" %)(((
301 301  **Size(bytes)**
302 -)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
303 -2
304 -)))|(% style="width:30px" %)(((
305 -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)
306 306  )))
307 307  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
308 308  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
309 -)))|(% 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:"]]
310 310  
311 -[[image:1665301636888-168.png]]
224 +[[image:1664501958445-288.png]]
312 312  
313 313  
314 314  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -319,9 +319,9 @@
319 319  
320 320  ==== (% style="color:blue" %)**FLAG:**(%%) ====
321 321  
322 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
323 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
324 -|=(% 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 
325 325  
326 326  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
327 327  
... ... @@ -331,18 +331,22 @@
331 331  * Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
332 332  * Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
333 333  
247 +
334 334  (% style="color:red" %)**Important note:**
335 335  
336 336  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.
337 337  
338 -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.
339 339  
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:
340 340  
256 +
341 341  [[image:1664502116362-706.png]]
342 342  
343 343  
344 -3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
345 345  
261 +4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
262 +
346 346  [[image:1664502166010-515.png]]
347 347  
348 348  
... ... @@ -349,15 +349,15 @@
349 349  
350 350  ==== (% style="color:blue" %)**Alarm:**(%%) ====
351 351  
352 -**Example: ** 0x4B & 0x40 >> 6 = 0x01
269 +Example:  0x4B & 0x40 >> 6 = 0x01
353 353  
354 354  
355 355  ==== (% style="color:blue" %)**BAT:**(%%) ====
356 356  
357 -**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
274 +Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
358 358  
359 359  (((
360 -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: \
361 361  )))
362 362  
363 363  * > 4.0v :  80% ~~ 100%
... ... @@ -366,33 +366,18 @@
366 366  * 3.40v ~~ 3.69v:  20% ~~ 40%
367 367  * < 3.39v:  0~~20%
368 368  
369 -==== (% style="color:blue" %)**MOD:**(%%) ====
370 370  
371 -**Example: ** (0x60>>6) & 0x3f =1
372 -
373 -**Set the format of GPS data uplink link：**
374 -
375 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
376 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
377 -
378 -
379 -**Set the format of BLE data uplink link：**
380 -
381 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
382 -
383 -
384 384  ==== (% style="color:blue" %)**LON:**(%%) ====
385 385  
386 -**Example:** (0x60>>5) & 0x01=1.
387 387  
388 388  Enable/Disable LED activity for uplink
389 389  
390 390  (((
391 -(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
293 +0x00:  Disable LED indicator.
392 392  )))
393 393  
394 394  (((
395 -(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
297 +0x01:  Enable LED indicator (Default Value)
396 396  )))
397 397  
398 398  
... ... @@ -407,57 +407,15 @@
407 407  
408 408  
409 409  
410 -=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
312 +=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
411 411  
412 412  
413 -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)
414 414  
316 +=== 2.3.4 BLE positioning Payload(Fport2) ===
415 415  
416 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
417 -|=(% scope="row" style="width: 60px;" %)(((
418 -**Size(bytes)**
419 -)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
420 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
421 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
422 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
423 423  
424 -(% class="wikigeneratedid" %)
425 -[[image:1665301687277-443.png]]
319 +Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
426 426  
427 -
428 -
429 -=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
430 -
431 -
432 -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.
433 -
434 -
435 -(% style="color:red" %)**Note for this mode:**
436 -
437 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
438 -* 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.
439 -* 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
440 -
441 -The payload is 15 bytes, as below.
442 -
443 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
444 -|=(% scope="row" %)(((
445 -**Size(bytes)**
446 -)))|4|4|2|1|1|1|1|1
447 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
448 -
449 -[[image:image-20221009160309-2.png]]
450 -
451 -
452 -
453 -=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
454 -
455 -
456 -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.
457 -
458 -User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
459 -
460 -
461 461  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
462 462  |=(% scope="row" style="width: 60px;" %)(((
463 463  **Size(bytes)**
... ... @@ -477,41 +477,20 @@
477 477  [[image:1664502425687-834.png]]
478 478  
479 479  
480 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
340 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
481 481  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
482 482  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
483 483  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
484 -* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
344 +* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
485 485  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
486 486  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
487 487  
488 -=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
489 489  
349 +=== 2.3.5 Add Payload format in TTN V3 ===
490 490  
491 -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.
492 492  
352 +In TTN V3, use can add a custom payload so it shows friendly.
493 493  
494 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
495 -|=(% scope="row" style="width: 60px;" %)(((
496 -**Size(bytes)**
497 -)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
498 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
499 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
500 -)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
501 -
502 -(% class="wikigeneratedid" %)
503 -[[image:1667288597595-714.png||height="212" width="1151"]]
504 -
505 -
506 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
507 -* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
508 -* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
509 -
510 -=== 2.4.7  Add Payload format in TTN V3 ===
511 -
512 -
513 -In TTN V3, user can add a custom payload so it shows friendly.
514 -
515 515  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
516 516  
517 517  
... ... @@ -518,9 +518,8 @@
518 518  [[image:1664502649601-895.png]]
519 519  
520 520  
521 -Add the decoder from this link: 
360 +Add the decoder from this link:
522 522  
523 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
524 524  
525 525  Save the change the uplink message will be parsed. As below:
526 526  
... ... @@ -528,12 +528,16 @@
528 528  
529 529  
530 530  
531 -== 2.5 Integrate with Datacake ==
369 +== 2.4 Integrate with Datacake ==
532 532  
533 533  
372 +(((
534 534  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 +)))
535 535  
376 +(((
536 536  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 +)))
537 537  
538 538  
539 539  [[image:1664502695771-538.png]]
... ... @@ -540,12 +540,16 @@
540 540  
541 541  
542 542  
543 -== 2.6 Integrate with Tago ==
385 +== 2.5 Integrate with Tago ==
544 544  
545 545  
546 -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 +)))
547 547  
392 +(((
548 548  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 +)))
549 549  
550 550  
551 551  [[image:1664502715371-321.png]]
... ... @@ -552,25 +552,9 @@
552 552  
553 553  
554 554  
555 -== 2.7  Datalog Feature ==
401 +== 2.6 Alarm Mode ==
556 556  
557 557  
558 -total 273 entries,by default,
559 -
560 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
561 -
562 -Example use case.
563 -
564 -[[image:image-20221009234703-2.png||height="328" width="899"]]
565 -
566 -
567 -[[image:image-20221009234629-1.png||height="390" width="577"]]
568 -
569 -
570 -
571 -== 2.8 Alarm Mode ==
572 -
573 -
574 574  (((
575 575  User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
576 576  )))
... ... @@ -577,7 +577,7 @@
577 577  
578 578  
579 579  (((
580 -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.
581 581  )))
582 582  
583 583  
... ... @@ -585,7 +585,7 @@
585 585  Two ways to exit alarm mode:
586 586  )))
587 587  
588 -* Server sends a downlink command to exit.
418 +* Server send a downlink command to exit.
589 589  * User fast press the RED button 10 times.
590 590  
591 591  (((
... ... @@ -594,23 +594,20 @@
594 594  
595 595  
596 596  
597 -== 2.9 Transport Mode ==
427 +== 2.7 Sports Mode ==
598 598  
599 599  
600 -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.
601 601  
431 +== 2.8 LED Status ==
602 602  
603 603  
604 -== 2.10 LED Status ==
605 -
606 -
607 -(% border="1.5" style="background-color:#ffffcc; width:500px" %)
434 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
608 608  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
609 609  |(% 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
610 610  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
611 611  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
612 612  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
613 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
440 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
614 614  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
615 615  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
616 616  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -618,9 +618,10 @@
618 618  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
619 619  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
620 620  
621 -== 2.11 Button Function ==
622 622  
449 +== 2.9 Button Function ==
623 623  
451 +
624 624  (% style="color:blue" %)**RESET button:**
625 625  
626 626  [[image:1664502835802-546.png]]
... ... @@ -633,15 +633,16 @@
633 633  [[image:1664502854406-763.png]]
634 634  
635 635  
636 -(% border="1" style="background-color:#ffffcc; width:510px" %)
637 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
638 -|(% 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"]]
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**
466 +|(% 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"]]
639 639  |(% 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
640 640  |(% 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.
641 641  
642 -== 2.12 USB Port Function ==
643 643  
471 +== 2.10 USB Port Function ==
644 644  
473 +
645 645  The USB interface of TrackerD has below functions:
646 646  
647 647  * Power on the device
... ... @@ -649,6 +649,7 @@
649 649  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
650 650  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
651 651  
481 +
652 652  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
653 653  
654 654  
... ... @@ -673,9 +673,11 @@
673 673  [[image:1664503022490-662.png]]
674 674  
675 675  
506 +
676 676  [[image:1664503035713-500.png]]
677 677  
678 678  
510 +
679 679  [[image:1664503047675-651.png]]
680 680  
681 681  
... ... @@ -719,21 +719,21 @@
719 719  
720 720  
721 721  
722 -=== 3.2.3 Set Transport Mode Packet transmission interval ===
554 +=== 3.2.3 Set Sports Mode Packet transmission interval ===
723 723  
724 724  
725 -Set Transport Mode packet transmit interval
557 +Set sports packet transmit interval
726 726  
727 727  * (% style="color:blue" %)**AT Command:**
728 728  
729 729  (% style="color:#037691" %)**AT+MTDC=xx. **
730 730  
731 -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
732 732  
733 733  
734 734  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
735 735  
736 -(% 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
737 737  
738 738  
739 739  
... ... @@ -768,21 +768,21 @@
768 768  
769 769  
770 770  
771 -=== 3.2.6 Disable/Enable Transport Mode ===
603 +=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
772 772  
773 773  
774 -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
775 775  
776 776  * (% style="color:blue" %)**AT Command:**
777 777  
778 778  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
779 779  
780 -Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
612 +Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
781 781  
782 782  
783 783  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
784 784  
785 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
617 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
786 786  
787 787  
788 788  
... ... @@ -789,47 +789,35 @@
789 789  === 3.2.7 Set Positioning Mode ===
790 790  
791 791  
792 -SMOD define how TrackerD scan and uplink data:
624 +SMOD define the how TrackerD scan and uplink date.
793 793  
626 +GPS室外定位模式：  设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
794 794  
795 -* (% style="color:blue" %)**AT Command:**
628 +BLE室内定位模式：  设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
796 796  
797 -(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
630 +GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
798 798  
799 -(% style="color:#037691" %)** aa:**
632 +运动模式：  设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
800 800  
801 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
802 802  
803 -* (% 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.
804 804  
805 -* (% 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:**
806 806  
807 -(% style="color:#037691" %)**bb:**
638 +(% style="color:#037691" %)**AT+SMOD=xx. **
808 808  
809 -* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
810 810  
811 -* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
641 + **Example:**
812 812  
813 -(% style="color:#037691" %)**cc:   **
643 + AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
814 814  
815 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
816 -
817 -* (% 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
818 818  
819 -(% style="color:blue" %)**Example:**
647 + AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
820 820  
821 - AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
822 822  
823 - AT+SMOD=1,1,0 ~-~->  GPS +BAT State
824 -
825 - AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
826 -
827 - AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
828 -
829 -
830 830  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
831 831  
832 -(% 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
833 833  
834 834  
835 835  
... ... @@ -846,7 +846,7 @@
846 846  
847 847  (% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
848 848  
849 -**Example:**  AT+FTIME=150
669 +Example:  AT+FTIME=150
850 850  
851 851  
852 852  * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
... ... @@ -855,7 +855,7 @@
855 855  
856 856  
857 857  
858 -=== 3.2.9 Set PDOP value for GPS fix accuracy ===
678 +=== 3.3.9 Set PDOP value for GPS fix accuracy ===
859 859  
860 860  
861 861  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.
... ... @@ -883,110 +883,22 @@
883 883  
884 884  * (% style="color:blue" %)**AT Command:**
885 885  
886 -(% style="color:#037691" %)**AT+CFM=xx**
706 +(% style="color:#037691" %)**AT+CFM=xx. **
887 887  
888 888  
889 889  **~ Example:**
890 890  
891 - AT+CFM=0    **~-~->   ** Disable confirmation
711 + AT+ CFM=0    **~-~->   ** Disable confirmation
892 892  
893 - AT+CFM=1    **~-~->  ** Enable confirmation
713 + AT+ CFM=1    **~-~->  ** Enable confirmation
894 894  
895 895  
896 896  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
897 897  
898 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
718 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
899 899  
900 900  
901 901  
902 -=== 3.2.10  Auto Send None-ACK messages ===
903 -
904 -
905 -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.
906 -
907 -
908 -* (% style="color:blue" %)**AT Command: AT+PNACKMD**
909 -
910 -The default factory setting is 0.
911 -
912 -
913 -**Command Example Function Response:**
914 -
915 -(% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
916 -
917 -
918 -* (% style="color:blue" %)**Downlink Command: 0x34**
919 -
920 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
921 -
922 -
923 -
924 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
925 -
926 -
927 -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.
928 -
929 -(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
930 -
931 -(% style="color:blue" %)**AT Command:**
932 -
933 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
934 -
935 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
936 -
937 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
938 -
939 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
940 -
941 -
942 -
943 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
944 -
945 -
946 -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.
947 -
948 -(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
949 -
950 -(% style="color:blue" %)**AT Command:**
951 -
952 - (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
953 -
954 - (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
955 -
956 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
957 -
958 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
959 -
960 -
961 -
962 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
963 -
964 -
965 -Users can use this feature to enable/disable Information printing.
966 -
967 -(% style="color:blue" %)**AT Command:**
968 -
969 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
970 -\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
971 -
972 -
973 -
974 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
975 -
976 -
977 -The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
978 -
979 -(% style="color:blue" %)**AT Command:**
980 -
981 -(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
982 -
983 -
984 -(% style="color:blue" %)**Downlink Payload:0X24**
985 -
986 -Example: 0x24 01 ~/~/ Same as AT+CHE=1
987 -
988 -
989 -
990 990  = 4. Setting for Different Scenarios =
991 991  
992 992  
... ... @@ -1027,10 +1027,9 @@
1027 1027  [[image:1664503574618-659.png]]
1028 1028  
1029 1029  
1030 -
1031 1031  (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
1032 1032  
1033 -[[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]]
1034 1034  
1035 1035  
1036 1036  Users need to use below files:
... ... @@ -1067,24 +1067,12 @@
1067 1067  [[image:1664503635019-941.png]]
1068 1068  
1069 1069  
1070 -
1071 1071  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1072 1072  
1073 1073  [[image:1664503715811-892.png]]
1074 1074  
1075 1075  
1076 -(% 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.
1077 1077  
1078 -[[image:image-20221024105643-1.png]]
1079 -
1080 -**~ Figure1**
1081 -
1082 -
1083 -[[image:image-20221024105643-2.png]]
1084 -
1085 - **Figure2**
1086 -
1087 -
1088 1088  * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1089 1089  
1090 1090  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
... ... @@ -1143,130 +1143,11 @@
1143 1143  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1144 1144  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1145 1145  
1146 -== 7.3 Notes on using different serial port tools for TrackerD ==
1147 1147  
1148 1148  
1149 -=== 7.3.1  Serial port utility ===
867 += 8.  Order Info =
1150 1150  
1151 1151  
1152 -Serial port utility requires you to automatically add data streams.
1153 -
1154 -Need to adjust the data stream to RTS/CTS on physical restart.
1155 -
1156 -
1157 -(% class="wikigeneratedid" %)
1158 -[[image:image-20221102140621-1.png]]
1159 -
1160 -
1161 -When using AT commands, the data flow needs to be adjusted to XON/XOFF
1162 -
1163 -
1164 -[[image:image-20221102140638-2.png]]
1165 -
1166 -
1167 -
1168 -=== 7.3.2  SecureCRT ===
1169 -
1170 -
1171 -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.
1172 -
1173 -
1174 -[[image:image-20221102140704-3.png]]
1175 -
1176 -
1177 -[[image:image-20221102140712-4.png]]
1178 -
1179 -
1180 -
1181 -=== 7.3.3  PUTTY ===
1182 -
1183 -
1184 -[[image:image-20221102140748-5.png]]
1185 -
1186 -
1187 -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.
1188 -
1189 -
1190 -[[image:image-20221102140801-6.png]]
1191 -
1192 -
1193 -== 7.4 How to modify source code to compile different frequency band bin file? ==
1194 -
1195 -1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
1196 -
1197 -[[image:image-20221116111844-1.png||height="227" width="782"]]
1198 -
1199 -2.Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
1200 -
1201 -[[image:image-20221116111844-2.png||height="262" width="781"]]
1202 -
1203 -3.Compile the AS923_JP band, please refer to the intention shown
1204 -
1205 -[[image:image-20221116111844-3.png||height="338" width="746"]]
1206 -
1207 -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.
1208 -
1209 -[[image:image-20221116111844-4.png||height="641" width="739"]]
1210 -
1211 -[[image:image-20221116111844-5.png||height="551" width="708"]]
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 -== 8.4 If the device's led light is always on when upgrading（since firmware 1.4.1） ==
1248 -
1249 -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.
1250 -
1251 -
1252 -(((
1253 -== 8.5 How to deal with unsuccessful GPS positioning? ==
1254 -
1255 -1） Make Sure the device is in Open Area where can see the sky. 
1256 -2)  Set PDOP to a higher value.
1257 -
1258 -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
1259 -)))
1260 -
1261 -
1262 -== 8.6 When positioning, it will restart or the PDOP setting is unsuccessful ==
1263 -
1264 -Please download version 1.4.2 again
1265 -
1266 -
1267 -= 9.  Order Info =
1268 -
1269 -
1270 1270  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1271 1271  
1272 1272  (% style="color:blue" %)**XXX**(%%): The default frequency band
... ... @@ -1279,9 +1279,10 @@
1279 1279  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1280 1280  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1281 1281  
1282 -= 10.  Packing Info =
1283 1283  
883 += 9.  Packing Info =
1284 1284  
885 +
1285 1285  (% style="color:#037691" %)**Package Includes**:
1286 1286  
1287 1287  * TrackerD LoRaWAN GPS/BLE Tracker x 1
... ... @@ -1289,18 +1289,20 @@
1289 1289  
1290 1290  (% style="color:#037691" %)**Dimensions and Weight**:
1291 1291  
1292 -* Device Size: 85 x 48 x 15 mm
893 +* Device Size: 85 x 48 x 15 cm
1293 1293  * Weight: 50g
1294 1294  
1295 -= 11. Support =
1296 1296  
897 += 10. Support =
1297 1297  
899 +
1298 1298  * 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.
1299 1299  * 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]].
1300 1300  
1301 -= 12.  Reference =
1302 1302  
904 += 11.  Reference =
1303 1303  
906 +
1304 1304  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1305 1305  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1306 1306  * [[**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-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
image-20221116111844-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -15.8 KB
Content
image-20221116111844-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -32.6 KB
Content
image-20221116111844-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -37.0 KB
Content
image-20221116111844-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -96.8 KB
Content
image-20221116111844-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -78.0 KB
Content