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

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