Skip to Content
Last modified by Bei Jinggeng on 2025/08/01 17:45
From version 145.1
edited by Edwin Chen
on 2022/11/22 12:21
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
Content
... ... @@ -14,6 +14,7 @@
14 14  
15 15  = 1.  Introduction =
16 16  
17 +
17 17  == 1.1  What is TrackerD ==
18 18  
19 19  
... ... @@ -45,6 +45,7 @@
45 45  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
46 46  
47 47  
49 +
48 48  == 1.2 Specifications ==
49 49  
50 50  
... ... @@ -95,6 +95,7 @@
95 95  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
96 96  * Tracking: max: 38mA
97 97  
100 +
98 98  == 1.3  Features ==
99 99  
100 100  
... ... @@ -113,6 +113,7 @@
113 113  * Tri-color LED, Alarm button
114 114  * Datalog
115 115  
119 +
116 116  == 1.4  Applications ==
117 117  
118 118  
... ... @@ -119,8 +119,10 @@
119 119  * Logistics and Supply Chain Management
120 120  * Human tracking
121 121  
122 -= 2.  Use TrackerD =
123 123  
127 += 2.1 Use TrackerD =
128 +
129 +
124 124  == 2.1 How it works? ==
125 125  
126 126  
... ... @@ -127,6 +127,7 @@
127 127  TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
128 128  
129 129  
136 +
130 130  == 2.2 Quick guide to connect to LoRaWAN server ==
131 131  
132 132  
... ... @@ -168,141 +168,53 @@
168 168  **__Add APP KEY and DEV EUI:__**
169 169  
170 170  
171 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
178 +[[image:1664501784668-703.png]]
172 172  
173 173  
174 174  
175 -(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
176 176  
177 -(% 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.
178 178  
179 -[[image:1664502835802-546.png]]
180 180  
181 -
182 182  (% 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.
183 183  
184 184  
185 -== 2.3  Positioning Mode(SMOD) ==
189 += 2.3 Positioning Mode(SMOD) =
186 186  
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.
187 187  
188 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
195 +User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
189 189  
190 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
191 -* (% 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.
192 -* (% 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.
193 193  
194 -Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
195 195  
199 +== 2.3 Uplink Payload ==
196 196  
197 -== 2.4  Uplink Payload ==
198 198  
199 -=== 2.4.1 Uplink FPORT~=5, Device Status ===
202 +=== 2.3.1 Uplink FPORT~=5, Device Status ===
200 200  
201 201  
202 -Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.
203 203  
204 -Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
206 +=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
205 205  
206 206  
207 -(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
208 -|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
209 -|=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
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 -[[image:1665301570342-765.png]]
212 212  
213 -
214 -(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
215 -
216 -(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
217 -
218 -(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
219 -
220 -(% style="color:#037691" %)**Frequency Band**:
221 -
222 -*0x01: EU868
223 -
224 -*0x02: US915
225 -
226 -*0x03: IN865
227 -
228 -*0x04: AU915
229 -
230 -*0x05: KZ865
231 -
232 -*0x06: RU864
233 -
234 -*0x07: AS923
235 -
236 -*0x08: AS923-1
237 -
238 -*0x09: AS923-2
239 -
240 -*0x0a: AS923-3
241 -
242 -Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
243 -
244 -(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
245 -
246 -
247 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
248 -
249 -Use can also get the Device Status uplink through the downlink command:
250 -
251 -
252 -(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
253 -
254 -(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
255 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
256 -|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
257 -
258 -(% style="color:blue" %)** SMOD：**
259 -
260 -(% style="color:red" %)** 1 :** (%%) GPS ONLY
261 -
262 -(% style="color:red" %)** 2 :** (%%) BLE ONLY
263 -
264 -(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
265 -
266 -
267 -(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
268 -
269 -(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
270 -
271 -(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
272 -
273 -
274 -(% style="color:blue" %)** BLE_Settings:**
275 -
276 -(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
277 -
278 -(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
279 -
280 -
281 -(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
282 -
283 -(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
284 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
285 -|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
286 -
287 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
288 -
289 -
290 -Users can use **AT+SMOD=1,0,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
291 -
292 -
293 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
294 -|=(% 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;" %)(((
295 295  **Size(bytes)**
296 -)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
297 -2
298 -)))|(% style="width:30px" %)(((
299 -2
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)
300 300  )))
301 301  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
302 302  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
303 -)))|(% 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:"]]
304 304  
305 -[[image:1665301636888-168.png]]
224 +[[image:1664501958445-288.png]]
306 306  
307 307  
308 308  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -313,9 +313,9 @@
313 313  
314 314  ==== (% style="color:blue" %)**FLAG:**(%%) ====
315 315  
316 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
317 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
318 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
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 
319 319  
320 320  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
321 321  
... ... @@ -325,18 +325,22 @@
325 325  * Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
326 326  * Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
327 327  
247 +
328 328  (% style="color:red" %)**Important note:**
329 329  
330 330  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.
331 331  
332 -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.
333 333  
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:
334 334  
256 +
335 335  [[image:1664502116362-706.png]]
336 336  
337 337  
338 -3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
339 339  
261 +4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
262 +
340 340  [[image:1664502166010-515.png]]
341 341  
342 342  
... ... @@ -343,15 +343,15 @@
343 343  
344 344  ==== (% style="color:blue" %)**Alarm:**(%%) ====
345 345  
346 -**Example: ** 0x4B & 0x40 >> 6 = 0x01
269 +Example:  0x4B & 0x40 >> 6 = 0x01
347 347  
348 348  
349 349  ==== (% style="color:blue" %)**BAT:**(%%) ====
350 350  
351 -**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
274 +Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
352 352  
353 353  (((
354 -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: \
355 355  )))
356 356  
357 357  * > 4.0v :  80% ~~ 100%
... ... @@ -360,33 +360,18 @@
360 360  * 3.40v ~~ 3.69v:  20% ~~ 40%
361 361  * < 3.39v:  0~~20%
362 362  
363 -==== (% style="color:blue" %)**MOD:**(%%) ====
364 364  
365 -**Example: ** (0x60>>6) & 0x3f =1
366 -
367 -**Set the format of GPS data uplink link：**
368 -
369 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
370 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
371 -
372 -
373 -**Set the format of BLE data uplink link：**
374 -
375 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
376 -
377 -
378 378  ==== (% style="color:blue" %)**LON:**(%%) ====
379 379  
380 -**Example:** (0x60>>5) & 0x01=1.
381 381  
382 382  Enable/Disable LED activity for uplink
383 383  
384 384  (((
385 -(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
293 +0x00:  Disable LED indicator.
386 386  )))
387 387  
388 388  (((
389 -(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
297 +0x01:  Enable LED indicator (Default Value)
390 390  )))
391 391  
392 392  
... ... @@ -400,55 +400,16 @@
400 400  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
401 401  
402 402  
403 -=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
404 404  
312 +=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
405 405  
406 -The default uplink payload includes total 11 bytes (**AT+SMOD=1,1,0**). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
407 407  
408 408  
409 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
410 -|=(% scope="row" style="width: 60px;" %)(((
411 -**Size(bytes)**
412 -)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
413 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
414 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
415 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
316 +=== 2.3.4 BLE positioning Payload(Fport2) ===
416 416  
417 -(% class="wikigeneratedid" %)
418 -[[image:1665301687277-443.png]]
419 419  
319 +Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
420 420  
421 -=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
422 -
423 -
424 -Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
425 -
426 -
427 -(% style="color:red" %)**Note for this mode:**
428 -
429 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
430 -* 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.
431 -* 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
432 -
433 -The payload is 15 bytes, as below.
434 -
435 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
436 -|=(% scope="row" %)(((
437 -**Size(bytes)**
438 -)))|4|4|2|1|1|1|1|1
439 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
440 -
441 -[[image:image-20221009160309-2.png]]
442 -
443 -
444 -=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
445 -
446 -
447 -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.
448 -
449 -User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
450 -
451 -
452 452  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
453 453  |=(% scope="row" style="width: 60px;" %)(((
454 454  **Size(bytes)**
... ... @@ -468,41 +468,20 @@
468 468  [[image:1664502425687-834.png]]
469 469  
470 470  
471 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
340 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
472 472  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
473 473  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
474 474  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
475 -* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
344 +* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
476 476  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
477 477  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
478 478  
479 -=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
480 480  
349 +=== 2.3.5 Add Payload format in TTN V3 ===
481 481  
482 -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.
483 483  
352 +In TTN V3, use can add a custom payload so it shows friendly.
484 484  
485 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
486 -|=(% scope="row" style="width: 60px;" %)(((
487 -**Size(bytes)**
488 -)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
489 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
490 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
491 -)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
492 -
493 -(% class="wikigeneratedid" %)
494 -[[image:1667288597595-714.png||height="212" width="1151"]]
495 -
496 -
497 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
498 -* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
499 -* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
500 -
501 -=== 2.4.7  Add Payload format in TTN V3 ===
502 -
503 -
504 -In TTN V3, user can add a custom payload so it shows friendly.
505 -
506 506  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
507 507  
508 508  
... ... @@ -509,56 +509,50 @@
509 509  [[image:1664502649601-895.png]]
510 510  
511 511  
360 +Add the decoder from this link:
512 512  
513 -Add the decoder from this link: 
514 514  
515 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
516 -
517 517  Save the change the uplink message will be parsed. As below:
518 518  
519 519  [[image:1664502676891-606.png]]
520 520  
521 521  
522 -== 2.5 Integrate with Datacake ==
523 523  
369 +== 2.4 Integrate with Datacake ==
524 524  
371 +
372 +(((
525 525  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 +)))
526 526  
376 +(((
527 527  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 +)))
528 528  
529 529  
530 530  [[image:1664502695771-538.png]]
531 531  
532 532  
533 -== 2.6 Integrate with Tago ==
534 534  
385 +== 2.5 Integrate with Tago ==
535 535  
536 -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.
537 537  
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 +)))
391 +
392 +(((
538 538  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 +)))
539 539  
540 540  
541 541  [[image:1664502715371-321.png]]
542 542  
543 543  
544 -== 2.7  Datalog Feature ==
545 545  
401 +== 2.6 Alarm Mode ==
546 546  
547 -total 273 entries,by default,
548 548  
549 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
550 -
551 -Example use case.
552 -
553 -[[image:image-20221009234703-2.png||height="328" width="899"]]
554 -
555 -
556 -[[image:image-20221009234629-1.png||height="390" width="577"]]
557 -
558 -
559 -== 2.8 Alarm Mode ==
560 -
561 -
562 562  (((
563 563  User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
564 564  )))
... ... @@ -565,15 +565,15 @@
565 565  
566 566  
567 567  (((
568 -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.
569 569  )))
570 570  
571 571  
572 572  (((
573 -**Two ways to exit alarm mode:**
415 +Two ways to exit alarm mode:
574 574  )))
575 575  
576 -* Server sends a downlink command to exit.
418 +* Server send a downlink command to exit.
577 577  * User fast press the RED button 10 times.
578 578  
579 579  (((
... ... @@ -581,22 +581,21 @@
581 581  )))
582 582  
583 583  
584 -== 2.9 Transport Mode ==
585 585  
427 +== 2.7 Sports Mode ==
586 586  
587 -In Transport Mode, TrackerD will check if there is motion. If there is no motion, device will send uplinks every 20 minutes. If there is motion, device will send uplink every 5 minutes.
588 588  
589 589  
590 -== 2.10 LED Status ==
431 +== 2.8 LED Status ==
591 591  
592 592  
593 -(% border="1.5" style="background-color:#ffffcc; width:500px" %)
434 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
594 594  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
595 595  |(% 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
596 596  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
597 597  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
598 598  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
599 -|(% 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
600 600  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
601 601  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
602 602  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -604,9 +604,10 @@
604 604  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
605 605  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
606 606  
607 -== 2.11 Button Function ==
608 608  
449 +== 2.9 Button Function ==
609 609  
451 +
610 610  (% style="color:blue" %)**RESET button:**
611 611  
612 612  [[image:1664502835802-546.png]]
... ... @@ -619,15 +619,16 @@
619 619  [[image:1664502854406-763.png]]
620 620  
621 621  
622 -(% border="1" style="background-color:#ffffcc; width:510px" %)
623 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
624 -|(% 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"]]
625 625  |(% 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
626 626  |(% 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.
627 627  
628 -== 2.12 USB Port Function ==
629 629  
471 +== 2.10 USB Port Function ==
630 630  
473 +
631 631  The USB interface of TrackerD has below functions:
632 632  
633 633  * Power on the device
... ... @@ -635,6 +635,7 @@
635 635  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
636 636  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
637 637  
481 +
638 638  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
639 639  
640 640  
... ... @@ -643,6 +643,7 @@
643 643  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
644 644  
645 645  
490 +
646 646  == 3.1 Access AT Command ==
647 647  
648 648  
... ... @@ -658,9 +658,11 @@
658 658  [[image:1664503022490-662.png]]
659 659  
660 660  
506 +
661 661  [[image:1664503035713-500.png]]
662 662  
663 663  
510 +
664 664  [[image:1664503047675-651.png]]
665 665  
666 666  
... ... @@ -667,6 +667,7 @@
667 667  
668 668  == 3.2 Command Set ==
669 669  
517 +
670 670  === 3.2.1 Set Transmit Interval ===
671 671  
672 672  
... ... @@ -684,6 +684,7 @@
684 684  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
685 685  
686 686  
535 +
687 687  === 3.2.2 Set Alarm Packet transmission interval ===
688 688  
689 689  
... ... @@ -701,23 +701,25 @@
701 701  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
702 702  
703 703  
704 -=== 3.2.3 Set Transport Mode Packet transmission interval ===
705 705  
554 +=== 3.2.3 Set Sports Mode Packet transmission interval ===
706 706  
707 -Set Transport Mode packet transmit interval
708 708  
557 +Set sports packet transmit interval
558 +
709 709  * (% style="color:blue" %)**AT Command:**
710 710  
711 711  (% style="color:#037691" %)**AT+MTDC=xx. **
712 712  
713 -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
714 714  
715 715  
716 716  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
717 717  
718 -(% 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
719 719  
720 720  
571 +
721 721  === 3.2.4 Exit Alarm ===
722 722  
723 723  
... ... @@ -730,6 +730,7 @@
730 730  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
731 731  
732 732  
584 +
733 733  === 3.2.5 Disable/Enable LED flash ===
734 734  
735 735  
... ... @@ -747,69 +747,60 @@
747 747  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
748 748  
749 749  
750 -=== 3.2.6 Disable/Enable Transport Mode ===
751 751  
603 +=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
752 752  
753 -Users can use this feature to enable/disable Transport Mode.
754 754  
606 +User can use this feature to check and set thread hole of movement detect
607 +
755 755  * (% style="color:blue" %)**AT Command:**
756 756  
757 757  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
758 758  
759 -Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
612 +Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
760 760  
761 761  
762 762  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
763 763  
764 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
617 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
765 765  
766 766  
620 +
767 767  === 3.2.7 Set Positioning Mode ===
768 768  
769 769  
770 -SMOD define how TrackerD scan and uplink data:
624 +SMOD define the how TrackerD scan and uplink date.
771 771  
626 +GPS室外定位模式：  设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
772 772  
773 -* (% style="color:blue" %)**AT Command:**
628 +BLE室内定位模式：  设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
774 774  
775 -(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
630 +GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
776 776  
777 -(% style="color:#037691" %)** aa:**
632 +运动模式：  设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
778 778  
779 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
780 780  
781 -* (% 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.
782 782  
783 -* (% 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:**
784 784  
785 -(% style="color:#037691" %)**bb:**
638 +(% style="color:#037691" %)**AT+SMOD=xx. **
786 786  
787 -* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
788 788  
789 -* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
641 + **Example:**
790 790  
791 -(% style="color:#037691" %)**cc:   **
643 + AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
792 792  
793 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
794 -
795 -* (% 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
796 796  
797 -(% style="color:blue" %)**Example:**
647 + AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
798 798  
799 - AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
800 800  
801 - AT+SMOD=1,1,0 ~-~->  GPS +BAT State
802 -
803 - AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
804 -
805 - AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
806 -
807 -
808 808  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
809 809  
810 -(% 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
811 811  
812 812  
655 +
813 813  === 3.2.8 Set MAX GPS position time ===
814 814  
815 815  
... ... @@ -816,7 +816,7 @@
816 816  Set max positioning time, default is 150 seconds. TrackerD will try to get location info within this period. If fail to get position data within this time, TrackerD will use 000000 for latitude and longitude.
817 817  
818 818  
819 -If **AT+FTIME=0**. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
662 +If AT+FTIME=0. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
820 820  
821 821  
822 822  * (% style="color:blue" %)**AT Command:**
... ... @@ -823,7 +823,7 @@
823 823  
824 824  (% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
825 825  
826 -**Example:**  AT+FTIME=150
669 +Example:  AT+FTIME=150
827 827  
828 828  
829 829  * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
... ... @@ -831,9 +831,10 @@
831 831  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
832 832  
833 833  
834 -=== 3.2.9 Set PDOP value for GPS fix accuracy ===
835 835  
678 +=== 3.3.9 Set PDOP value for GPS fix accuracy ===
836 836  
680 +
837 837  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.
838 838  
839 839  
... ... @@ -855,108 +855,26 @@
855 855  
856 856  
857 857  
858 -**Disable/Enable the confirmation mode**
702 +Disable/Enable the confirmation mode
859 859  
860 860  * (% style="color:blue" %)**AT Command:**
861 861  
862 -(% style="color:#037691" %)**AT+CFM=xx**
706 +(% style="color:#037691" %)**AT+CFM=xx. **
863 863  
864 864  
865 865  **~ Example:**
866 866  
867 - AT+CFM=0    **~-~->   ** Disable confirmation
711 + AT+ CFM=0    **~-~->   ** Disable confirmation
868 868  
869 - AT+CFM=1    **~-~->  ** Enable confirmation
713 + AT+ CFM=1    **~-~->  ** Enable confirmation
870 870  
871 871  
872 872  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
873 873  
874 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
718 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
875 875  
876 876  
877 -=== 3.2.10  Auto Send None-ACK messages ===
878 878  
879 -
880 -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.
881 -
882 -
883 -* (% style="color:blue" %)**AT Command: AT+PNACKMD**
884 -
885 -The default factory setting is 0.
886 -
887 -
888 -**Command Example Function Response:**
889 -
890 -(% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
891 -
892 -
893 -* (% style="color:blue" %)**Downlink Command: 0x34**
894 -
895 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
896 -
897 -
898 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
899 -
900 -
901 -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.
902 -
903 -(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
904 -
905 -(% style="color:blue" %)**AT Command:**
906 -
907 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
908 -
909 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
910 -
911 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
912 -
913 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
914 -
915 -
916 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
917 -
918 -
919 -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.
920 -
921 -(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
922 -
923 -(% style="color:blue" %)**AT Command:**
924 -
925 - (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
926 -
927 - (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
928 -
929 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
930 -
931 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
932 -
933 -
934 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
935 -
936 -
937 -Users can use this feature to enable/disable Information printing.
938 -
939 -(% style="color:blue" %)**AT Command:**
940 -
941 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
942 -\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
943 -
944 -
945 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
946 -
947 -
948 -The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
949 -
950 -(% style="color:blue" %)**AT Command:**
951 -
952 -(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
953 -
954 -
955 -(% style="color:blue" %)**Downlink Payload:0X24**
956 -
957 -Example: 0x24 01 ~/~/ Same as AT+CHE=1
958 -
959 -
960 960  = 4. Setting for Different Scenarios =
961 961  
962 962  
... ... @@ -963,6 +963,7 @@
963 963  
964 964  = 5. Upload Firmware =
965 965  
728 +
966 966  == 5.1 Firmware Change Log ==
967 967  
968 968  
... ... @@ -969,6 +969,7 @@
969 969  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
970 970  
971 971  
735 +
972 972  == 5.2 How to upgrade firmware ==
973 973  
974 974  
... ... @@ -995,33 +995,34 @@
995 995  [[image:1664503574618-659.png]]
996 996  
997 997  
998 -
999 999  (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
1000 1000  
1001 -[[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]]
1002 1002  
1003 1003  
1004 -**Users need to use below files:**
767 +Users need to use below files:
1005 1005  
1006 1006  boot_app0.bin @0e000
1007 1007  
1008 -US915.bin @ 0x10000(Select the bin file of the frequency band you need)
771 +ESP_LORA-eeprom-class.bin @ 0x10000
1009 1009  
1010 1010  
1011 -[[image:image-20221118105220-2.png]]
774 +[[image:1664503593459-435.png]]
1012 1012  
1013 1013  
1014 1014  
1015 1015  After upgrade finish, it will show finish as below:
1016 1016  
1017 -[[image:image-20221118105402-4.png]]
780 +[[image:1664503611848-385.png]]
1018 1018  
1019 1019  
1020 1020  
1021 1021  = 6. Developer Guide =
1022 1022  
786 +
1023 1023  == 6.1 Compile Source Code ==
1024 1024  
789 +
1025 1025  === 6.1.1 Set up ARDUINO compile environment ===
1026 1026  
1027 1027  
... ... @@ -1033,24 +1033,12 @@
1033 1033  [[image:1664503635019-941.png]]
1034 1034  
1035 1035  
1036 -
1037 1037  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1038 1038  
1039 1039  [[image:1664503715811-892.png]]
1040 1040  
1041 1041  
1042 -(% 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.
1043 1043  
1044 -[[image:image-20221024105643-1.png]]
1045 -
1046 -**~ Figure1**
1047 -
1048 -
1049 -[[image:image-20221024105643-2.png]]
1050 -
1051 - **Figure2**
1052 -
1053 -
1054 1054  * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1055 1055  
1056 1056  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
... ... @@ -1059,6 +1059,7 @@
1059 1059  [[image:1664503752288-974.png]]
1060 1060  
1061 1061  
815 +
1062 1062  == 6.2 Source Code ==
1063 1063  
1064 1064  
... ... @@ -1079,8 +1079,10 @@
1079 1079  [[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1080 1080  
1081 1081  
836 +
1082 1082  = 7.  FAQ =
1083 1083  
839 +
1084 1084  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1085 1085  
1086 1086  
... ... @@ -1087,6 +1087,7 @@
1087 1087  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1088 1088  
1089 1089  
846 +
1090 1090  == 7.2 What is the pin mapping for the USB program cable? ==
1091 1091  
1092 1092  
... ... @@ -1105,242 +1105,50 @@
1105 1105  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1106 1106  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1107 1107  
1108 -== 7.3 Notes on using different serial port tools for TrackerD ==
1109 1109  
1110 -=== 7.3.1  Serial port utility ===
1111 1111  
867 += 8.  Order Info =
1112 1112  
1113 -Serial port utility requires you to automatically add data streams.
1114 1114  
1115 -Need to adjust the data stream to RTS/CTS on physical restart.
1116 -
1117 -(% class="wikigeneratedid" %)
1118 -[[image:image-20221102140621-1.png]]
1119 -
1120 -
1121 -
1122 -When using AT commands, the data flow needs to be adjusted to XON/XOFF
1123 -
1124 -[[image:image-20221102140638-2.png]]
1125 -
1126 -
1127 -=== 7.3.2  SecureCRT ===
1128 -
1129 -
1130 -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.
1131 -
1132 -
1133 -[[image:image-20221102140704-3.png]]
1134 -
1135 -
1136 -[[image:image-20221102140712-4.png]]
1137 -
1138 -
1139 -=== 7.3.3  PUTTY ===
1140 -
1141 -
1142 -[[image:image-20221102140748-5.png]]
1143 -
1144 -
1145 -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.
1146 -
1147 -
1148 -[[image:image-20221102140801-6.png]]
1149 -
1150 -
1151 -== 7.4 How to modify source code to compile different frequency band bin file? ==
1152 -
1153 -
1154 -(% class="box infomessage" %)
1155 -(((
1156 -(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1157 -See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1158 -)))
1159 -
1160 -**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1161 -
1162 -
1163 -[[image:image-20221116111844-1.png||height="227" width="782"]]
1164 -
1165 -
1166 -
1167 -**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1168 -
1169 -
1170 -[[image:image-20221116111844-2.png||height="262" width="781"]]
1171 -
1172 -
1173 -
1174 -**3. Compile the AS923_JP band, please refer to the intention shown**
1175 -
1176 -
1177 -[[image:image-20221116111844-3.png||height="338" width="746"]]
1178 -
1179 -
1180 -
1181 -**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.**
1182 -
1183 -
1184 -[[image:image-20221116111844-4.png||height="641" width="739"]]
1185 -
1186 -
1187 -[[image:image-20221116111844-5.png||height="551" width="708"]]
1188 -
1189 -
1190 -= 8  Trouble Shooting =
1191 -
1192 -== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1193 -
1194 -
1195 -(((
1196 -Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1197 -)))
1198 -
1199 -
1200 -== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1201 -
1202 -
1203 -(((
1204 -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.
1205 -)))
1206 -
1207 -
1208 -== 8.3  Problem after Upgrading Firmware ==
1209 -
1210 -=== 8.3.1 Continue Restart after upgrading ===
1211 -
1212 -
1213 -(((
1214 -If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1215 -)))
1216 -
1217 -
1218 -[[image:image-20221118105249-3.png]]
1219 -
1220 -
1221 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1222 -
1223 -
1224 -It is because the partitions are different when upgrading versions above 1.4.1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1
1225 -
1226 -
1227 -=== 8.3.3 "flash read err" after upgrade firmware ===
1228 -
1229 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1230 -
1231 -[[image:image-20221122100004-1.png||height="497" width="534"]]
1232 -
1233 -
1234 -User need to upgrade again with below four files to solve this issue.
1235 -
1236 - [[image:image-20221122100004-2.png||height="619" width="389"]]
1237 -
1238 - **Figure 2**
1239 -
1240 -
1241 -=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1242 -
1243 -User might erase the entire flash include keys and default settings which cause this issue.
1244 -
1245 -After the upgrade is completed, enter AT+CFG as shown in the figure below.
1246 -
1247 -[[image:image-20221122100004-3.png]]
1248 -
1249 -Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1250 -
1251 -
1252 -Example:
1253 -
1254 -AT+DEUI=70B3D57ED0053981  
1255 -
1256 -AT+APPEUI=D23345667BCBCCAF
1257 -
1258 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1259 -
1260 -AT+DADDR=260b4dce    ( no need for OTAA)
1261 -
1262 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1263 -
1264 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1265 -
1266 -
1267 -
1268 -=== 8.3.4  If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ===
1269 -
1270 -
1271 -[[image:image-20221122100004-4.png]]
1272 -
1273 -
1274 -== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1275 -
1276 -
1277 -Please download version 1.4.2 again
1278 -
1279 -
1280 -== 8.5  How to deal with unsuccessful GPS positioning? ==
1281 -
1282 -
1283 -1） Make Sure the device is in Open Area where can see the sky.
1284 -
1285 -2)  Set PDOP to a higher value.
1286 -
1287 -* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1288 -
1289 -* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1290 -
1291 -* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1292 -
1293 -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
1294 -
1295 -
1296 -= 9.  Order Info =
1297 -
1298 -
1299 1299  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1300 1300  
1301 1301  (% style="color:blue" %)**XXX**(%%): The default frequency band
1302 1302  
1303 1303  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1304 -
1305 1305  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1306 -
1307 1307  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1308 -
1309 1309  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1310 -
1311 1311  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1312 -
1313 1313  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1314 -
1315 1315  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1316 1316  
1317 -= 10.  Packing Info =
1318 1318  
883 += 9.  Packing Info =
1319 1319  
885 +
1320 1320  (% style="color:#037691" %)**Package Includes**:
1321 1321  
1322 1322  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1323 -
1324 1324  * USB recharge & program cable x 1
1325 1325  
1326 1326  (% style="color:#037691" %)**Dimensions and Weight**:
1327 1327  
1328 -* Device Size: 85 x 48 x 15 mm
1329 -
893 +* Device Size: 85 x 48 x 15 cm
1330 1330  * Weight: 50g
1331 1331  
1332 -= 11. Support =
1333 1333  
897 += 10. Support =
1334 1334  
1335 -* 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.
1336 1336  
900 +* 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.
1337 1337  * 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]].
1338 1338  
1339 -= 12.  Reference =
1340 1340  
904 += 11.  Reference =
1341 1341  
1342 -* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1343 1343  
907 +* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1344 1344  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1345 -
1346 1346  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
910 +
911 +
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
image-20221118104359-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -38.0 KB
Content
image-20221118105220-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -40.2 KB
Content
image-20221118105249-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -40.2 KB
Content
image-20221118105402-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -43.7 KB
Content
image-20221122100004-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -18.0 KB
Content
image-20221122100004-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -127.2 KB
Content
image-20221122100004-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -12.5 KB
Content
image-20221122100004-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content