Skip to Content
Version 215.2 by Xiaoling on 2023/10/27 17:52
Show last authors
1 (% style="text-align:center" %)
2 [[image:1664505654417-133.png||_mstalt="293696"]]
3
4
5
6
7 (% class="wikigeneratedid" %)
8 **Table of Contents:**
9
10 {{toc/}}
11
12
13
14
15
16 = 1.  Introduction =
17
18 == 1.1  What is TrackerD ==
19
20
21 (((
22 TrackerD is an (% style="color:blue" %)**Open Source LoRaWAN Tracker**(%%) based on (% style="color:blue" %)**ESP32 MCU**(%%) and (% style="color:blue" %)**Semtech LoRa Wireless Chip**.
23 )))
24
25 (((
26 In TrackerD, there are various sensors such as GPS, WiFi, BLE, Temperature, Humidity, Motion Detection, and Buzzer. User can use TrackerD for different tracking scenario.
27
28 (((
29 TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.
30 )))
31
32 (((
33 The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
34 )))
35
36 (((
37 TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
38 )))
39
40 [[image:image-20230213110119-1.png||height="382" width="834"]]
41
42
43 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
44
45
46 == 1.2 Specifications ==
47
48
49 (% style="color:blue" %)**Micro Controller:**
50
51 * Espressif ESP32 PICO D4
52 * MCU: ESP32 PICO D4
53 * Bluetooth: Bluetooth V4.2 BR/EDR and Bluetooth LE
54 * WiFi : 802.11 b/g/n (802.11n up to 150 Mbps)
55 * Integrated SPI flash : 4 MB
56 * RAM: 448 KB
57 * EEPROM: 520 KB
58 * Clock Speed: 32Mhz
59
60 (% style="color:blue" %)**Common DC Characteristics:**
61
62 * Supply Voltage: 5V via USB port or Internal li-on battery
63 * Operating Temperature: -40 ~~ 60°C
64
65 (% style="color:blue" %)**LoRa Spec:**
66
67 * Frequency Range,
68 ** Band 1 (HF): 862 ~~ 1020 Mhz
69 * 168 dB maximum link budget.
70 * +20 dBm - 100 mW constant RF output vs.
71 * +14 dBm high efficiency PA.
72 * Programmable bit rate up to 300 kbps.
73 * High sensitivity: down to -148 dBm.
74 * Bullet-proof front end: IIP3 = -12.5 dBm.
75 * Excellent blocking immunity.
76 * Low RX current of 10.3 mA, 200 nA register retention.
77 * Fully integrated synthesizer with a resolution of 61 Hz.
78 * FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
79 * Built-in bit synchronizer for clock recovery.
80 * Preamble detection.
81 * 127 dB Dynamic Range RSSI.
82 * Automatic RF Sense and CAD with ultra-fast AFC.
83 * Packet engine up to 256 bytes with CRC.
84 * LoRaWAN 1.0.3 Specification
85
86 (% style="color:blue" %)**Battery:**
87
88 * 1000mA Li-on Battery power (for model TrackerD)
89
90 (% style="color:blue" %)**Power Consumption**
91
92 * Sleeping Mode: 200uA
93 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 * Tracking: max: 38mA
95
96 (% style="display:none" %)
97
98
99
100 == 1.3  Features ==
101
102
103 * LoRaWAN 1.0.3 Class A
104 * ESP32 PICO D4
105 * SX1276/78 Wireless Chip
106 * Arduino IDE Compatible
107 * Open source hardware / software
108 * Regular/ Real-time GPS,BLE,WIFI tracking
109 * Built-in3 axis accelerometer (LIS3DH)
110 * Humidity / temperature sensor : GXCAS Technology GXHT3X
111 * Motion sensing capability
112 * Power Monitoring
113 * Charging circuit via USB port
114 * 1000mA Li-on Battery power
115 * Tri-color LED, Alarm button
116 * Datalog
117
118 (% style="display:none" %)
119
120
121
122 == 1.4  Applications ==
123
124
125 * Logistics and Supply Chain Management
126 * Human tracking
127
128 (% style="display:none" %)
129
130
131
132 = 2.  Use TrackerD =
133
134 == 2.1 How it works? ==
135
136
137 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.
138
139
140 == 2.2 Quick guide to connect to LoRaWAN server ==
141
142
143 Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 
144
145
146 [[image:image-20230213110214-2.png||height="388" width="847"]]
147
148
149
150 The LPS8N is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. What the rest need to is register this device in TTN V3:
151
152
153 (% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
154
155 Each TrackerD is shipped with a sticker with the default device EUI as below:
156
157
158 [[image:image-20230426085815-1.png||height="259" width="558"]]
159
160
161 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
162
163
164 **__Add APP EUI in the application:__**
165
166
167 [[image:1664501711466-918.png||_mstalt="295828"]]
168
169
170
171 [[image:1664501721248-725.png||_mstalt="294450"]]
172
173
174 [[image:1664501734705-405.png||_mstalt="293306"]]
175
176
177
178 **__Add APP KEY and DEV EUI:__**
179
180
181 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
182
183
184
185 (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
186
187 (% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
188
189 [[image:1664502835802-546.png||_mstalt="295061"]]
190
191
192 (% 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.
193
194
195 == 2.3  Positioning Mode(SMOD) ==
196
197
198 Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
199
200 * (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
201 * (% 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.
202 * (% 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.
203
204 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
205
206
207 == 2.4  Uplink Payload ==
208
209 === 2.4.1 Uplink FPORT~=5, Device Status ===
210
211
212 Uplink the device configures with (% style="color:blue" %)**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.
213
214 Use can also get the Device Status uplink through the downlink command: (% style="color:#037691" %)**Downlink:  0x2301**
215
216 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:440px" %)
217 |(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**Size(bytes)**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 30px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1
218 |(% style="width:108px" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
219
220 [[image:1665301570342-765.png||_mstalt="294580"]]
221
222
223 (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
224
225 (% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
226
227 (% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
228
229 (% style="color:#037691" %)**Frequency Band**:
230
231 0x01: EU868
232
233 0x02: US915
234
235 0x03: IN865
236
237 0x04: AU915
238
239 0x05: KZ865
240
241 0x06: RU864
242
243 0x07: AS923
244
245 0x08: AS923-1
246
247 0x09: AS923-2
248
249 0x0a: AS923-3
250
251 (% style="color:#037691" %)**Sub-Band:**(%%) value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
252
253 (% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
254
255 (% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
256
257 Use can also get the Device Status uplink through the downlink command:
258
259
260 (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
261
262 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:270px" %)
263 |(% style="width:60px" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)2 bits|(% style="width:80px" %)4 bits
264 |(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
265
266 (% style="color:blue" %)**SMOD：**
267
268 (% style="color:red" %)**1 :** (%%) GPS ONLY
269
270 (% style="color:red" %)**2 :** (%%) BLE ONLY
271
272 (% style="color:red" %)**3 :**  (%%) GPS/BLE Hybrid
273
274
275 (% style="color:blue" %)**GPS_MOD: Define how to send GPS payload**
276
277 (% style="color:red" %)**0 : ** (%%) Enable uploading on-board Temperature and humidity values
278
279 (% style="color:red" %)**1 :** (%%) Disable uploading on-board Temperature and humidity values
280
281
282 (% style="color:blue" %)**BLE_Settings:**
283
284 (% style="color:red" %)**1: ** (%%) BLE Positioning with Strongest iBeacon
285
286 (% _mstmutation="1" style="color:red" %)**2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
287
288
289 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
290
291 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:413px" %)
292 |(% style="width:77px" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:88px" %)1 Bit|(% style="width:50px" %)1 Bit|(% style="width:128px" %)1 Bit
293 |(% style="width:75px" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
294
295 (% style="display:none" %)
296
297
298
299 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
300
301
302 Users can use (% style="color:blue" %)**AT+SMOD=1,0,0**(%%) to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
303
304
305 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:320px" %)
306 |(% style="width:60px" %)**Size(bytes)**|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)2|(% style="width:30px" %)2
307 |(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
308 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
309 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
310
311 [[image:1665301636888-168.png||_mstalt="298012"]]
312
313
314 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
315
316 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:321px" %)
317 |(% style="width:60px" %)**Size(bit)**|(% style="width:60px" %)1 bit|(% style="width:134px" %)1 bit|(% style="width:67px" %)14 bits
318 |(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:114px" %)Alarm Indicate|(% style="width:62px" %)[[BAT>>||anchor="HBAT:"]] 
319
320 (% style="display:none" %)
321
322
323 ==== (% style="color:blue" %)**FLAG:**(%%) ====
324
325 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:184px" %)
326 |(% style="width:68px" %)**Size(bit)**|(% style="width:61px" %)2 bits|(% style="width:55px" %)1 bit
327 |(% style="width:79px" %)**Value**|(% style="width:56px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:50px" %)[[LON>>||anchor="HLON:"]]
328
329 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
330
331
332 ==== (% style="color:blue" %)**Location info:**(%%) ====
333
334 * Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
335 * Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
336
337 (% style="color:red" %)**Important note:**
338
339 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.
340
341 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:
342
343
344 [[image:1664502116362-706.png||_mstalt="293306"]]
345
346
347 3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
348
349 [[image:1664502166010-515.png||_mstalt="291395"]]
350
351
352
353 ==== (% style="color:blue" %)**Alarm:**(%%) ====
354
355 **Example: ** 0x4B & 0x40 >> 6 = 0x01
356
357
358 ==== (% style="color:blue" %)**BAT:**(%%) ====
359
360 **Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
361
362 (((
363 The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
364 )))
365
366 * > 4.0v :  80% ~~ 100%
367 * 3.85v ~~3.99v:  60% ~~ 80%
368 * 3.70v ~~ 3.84v:  40% ~~ 60%
369 * 3.40v ~~ 3.69v:  20% ~~ 40%
370 * < 3.39v:  0~~20%
371
372 (% style="display:none" %) (%%)
373
374
375 ==== (% style="color:blue" %)**MOD:**(%%) ====
376
377 **Example: ** (0x60>>6) & 0x3f =1
378
379 **Set the format of GPS data uplink link：**
380
381 (% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
382 (% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
383
384
385 **Set the format of BLE data uplink link：**
386
387 (% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
388
389
390 ==== (% style="color:blue" %)**LON:**(%%) ====
391
392 **Example:** (0x60>>5) & 0x01=1.
393
394 Enable/Disable LED activity for uplink
395
396 (((
397 (% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
398 )))
399
400 (((
401 (% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
402 )))
403
404
405 ==== (% style="color:blue" %)**Hum:**(%%) ====
406
407 0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
408
409
410 ==== (% style="color:blue" %)**Tem:**(%%) ====
411
412 011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
413
414
415 === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
416
417
418 The default uplink payload includes total 11 bytes ((% style="color:blue" %)**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)
419
420
421 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:300px" %)
422 |(% style="width:60px" %)**Size(bytes)**|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:70px" %)2|(% style="width:50px" %)1
423 |(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
424 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
425 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
426
427 (% class="wikigeneratedid" %)
428 [[image:1665301687277-443.png||_mstalt="296140"]]
429
430
431 === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
432
433
434 Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-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.
435
436
437 (% style="color:red" %)**Note for this mode:**
438
439 * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
440 * 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.
441 * 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
442
443 The payload is 15 bytes, as below.
444
445 (% border="1" style="background-color:#f2f2f2; width:500px" %)
446 |**Size(bytes)**|4|4|2|1|1|1|1|1
447 |**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
448
449 [[image:image-20221009160309-2.png||_mstalt="429312"]]
450
451
452 === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
453
454
455 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.
456
457 User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
458
459
460 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
461 |(% style="width:60px" %)**Size(bytes)**|(% style="width:30px" %)16|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:120px" %)2|(% style="width:50px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1
462 |(% style="width:50px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
463 iBeacon MAJOR
464 )))|(% style="width:63px" %)(((
465 iBeacon MINOR
466 )))|(% style="width:71px" %)(((
467 iBeacon Measured Power
468 )))|(% style="width:50px" %)(((
469 iBeacon RSSI
470 )))|(% style="width:47px" %)(((
471 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
472 )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
473
474 [[image:1664502425687-834.png||_mstalt="296738"]]
475
476
477 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
478 * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
479 * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
480 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
481 * (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
482 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
483 * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
484
485 (% style="display:none" %) (%%)
486
487
488 === 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
489
490
491 The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
492
493 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:284.818px" %)
494 |(% style="width:97px" %)**Size(bytes)**|(% style="width:103px" %)2|(% style="width:81px" %)1
495 |(% style="width:97px" %)**Value**|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon
496
497 [[image:image-20230302145315-1.png]]
498
499 **alarm**=(bytes[0] & 0x40)  ~/~/ Alarm status
500
501 **batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
502
503 **mod** = bytes[2] & 0xC0;
504
505 **Lon**=(bytes[2] & 0x20)
506
507
508 === 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
509
510
511 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.
512
513 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
514 |(% style="width:65px" %)(((
515 **Size(bytes)**
516 )))|(% style="width:50px" %)6|(% style="width:50px" %)4|(% style="width:133px" %)2|(% style="width:50px" %)1
517 |(% style="width:69px" %)**Value**|(% style="width:48px" %)SSID|(% style="width:48px" %)RSSI|(% style="width:103px" %)(((
518 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
519 )))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]
520
521 (% class="wikigeneratedid" %)
522 [[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
523
524 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
525 * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
526 * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
527
528 (% style="display:none" %) (%%)
529
530 === 2.4.8  Uplink FPORT~=9, BLE Positioning with Multiple iBeacon（Since firmware 1.4.7） ===
531
532 TrackerD supports BLE scanning for indoor positioning. Users can set SMOD to BLE pure or GPS/BLE Hybrid, so TrackerD will scan up to 40 BLE iBeacons and send uplinks.
533
534 User can set [[(% class="wikiinternallink wikiinternallink wikiinternallink" %)**BLEMASK**>>path:#H3.2.11A0SetBLEMASKtofilterBLEiBeacon]](%%) so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
535
536 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
537 |**Size(bytes)**|2|2|2|…..|2|2|2|2|1
538 |**Value**|iBeacon MAJOR|iBeacon MINOR|iBeacon RSSI|…..|iBeacon MAJOR|iBeacon MINOR|iBeacon RSSI|[[Alarm & BAT>>path:#HAlarm26BAT:]]|[[FLAG>>path:#HFLAG:]]
539
540 (% class="wikigeneratedid" id="H" %)
541 [[image:image-20231023103116-1.png||height="448" width="901"]]
542
543 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
544 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
545 * (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
546 * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
547
548 (% class="wikigeneratedid" %)
549 **Note: This mode does not have a fixed decoder. Its decoder depends on the number of beacons and can be parsed according to the order of the payload.**
550 payload format: (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State
551
552
553 === 2.4.9  Add Payload format in TTN V3 ===
554
555
556 In TTN V3, user can add a custom payload so it shows friendly.
557
558 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
559
560 [[image:1664502649601-895.png||_mstalt="296985"]]
561
562
563 Add the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
564
565 Save the change the uplink message will be parsed. As below:
566
567 [[image:1664502676891-606.png||_mstalt="296673"]]
568
569
570 == 2.5 Integrate with Datacake ==
571
572
573 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.
574
575 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]]
576
577 [[image:1664502695771-538.png||_mstalt="297349"]]
578
579
580 == 2.6 Integrate with Tago ==
581
582
583 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.
584
585 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]]
586
587 [[image:1664502715371-321.png||_mstalt="292162"]]
588
589
590 == 2.7  Integrate with Node-red ==
591
592
593 ~1. Install node-red, please refer to the installation method in the link:
594
595 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
596
597
598 2. Import the created flow template, please refer to the import method in the link:
599
600 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
601
602
603 The address of the flow template: [[dragino-end-node-decoder/TrackerD.json at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/TrackerD.json]]
604
605 (% style="color:red" %)**Note: If you are using NODE-RED for the first time, please search and install the two plug-ins in the figure below in node-red to fully use the flow template.**
606
607 [[image:image-20230307135914-1.png||height="527" width="1045"]]
608
609
610 [[image:image-20230307135932-2.png||height="527" width="1044"]]
611
612
613 3. Display the map
614 Enter the link to the map:
615
616 Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
617
618 **~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
619
620
621 Hit all input in input stream
622
623 [[image:image-20230308115616-2.png||height="563" width="1070"]]
624
625
626 View map again
627
628 [[image:image-20230308115701-3.png||height="571" width="1085"]]
629
630
631 == 2.8  Datalog Feature ==
632
633
634 total 273 entries,by default,
635
636 User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
637
638 Example use case.
639
640 [[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
641
642
643 [[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
644
645
646 == 2.9  Alarm Mode ==
647
648
649 (((
650 User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. Alarm Mode is used to send SOS info to IoT platform.
651 )))
652
653
654 (((
655 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.
656 )))
657
658
659 (((
660 **Two ways to exit alarm mode:**
661 )))
662
663 * Server sends a downlink command to exit.
664 * User fast press the RED button 10 times.
665
666 (((
667 When exit alarm mode, (% style="color:red" %)**RED LED**(%%) will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false.
668 )))
669
670
671 == 2.10  Transport Mode ==
672
673
674 In Transport Mode, TrackerD will check if there is motion (threldhold defined by **[[PT)>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** . If there is no motion, device will send uplinks every 20 minutes (Defined by **[[TDC)>>||anchor="H3.2.1SetTransmitInterval"]]** . If there is motion, device will send uplink every 5 minutes(defined by **[[MTDC)>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]**.
675
676 When device is set in Transport Mode, it will uplink more frequenctly during moving.
677
678 * **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
679 * **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
680 * **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
681
682 (% style="display:none" %) (%%)
683
684
685 == 2.11  LED Status ==
686
687
688 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:500px" %)
689 |=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**Event**|=(% style="width: 200px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**AT+LON to control on/off**
690 |(% 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
691 |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
692 |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
693 |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
694 |(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
695 |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
696 |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
697 |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
698 |(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes
699 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
700 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
701
702 (% style="display:none" %) (%%)
703
704
705 == 2.12  Button Function ==
706
707
708 (% style="color:blue" %)**RESET button:**
709
710 [[image:1664502835802-546.png||_mstalt="295061"]]
711
712 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
713
714
715 (% style="color:red" %)**RED button:**
716
717 [[image:image-20230213110506-3.png]](% style="display:none" %)
718
719 (% style="display:none" %) (%%)
720
721 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
722 |=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Description**
723 |(% 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"]]
724 |(% 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
725 |(% 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.
726
727 (% style="display:none" %) (%%)
728
729
730 == 2.13  USB Port Function ==
731
732
733 The USB interface of TrackerD has below functions:
734
735 * Power on the device
736 * Recharge the battery
737 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
738 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
739
740 (% style="display:none" %) (%%)
741
742
743 == 2.14  Sleep Mode ==
744
745
746 (% style="color:blue" %)**Sleep Mode:**(%%) To prevent accidental touch of the red button during transportation or assembly, so the peripherals of the device are turned off and enter deep sleep.
747
748 In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
749
750 Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
751
752
753 = 3. Configure TrackerD via AT command or LoRaWAN downlink =
754
755
756 User can configure TrackerD via AT Command or LoRaWAN Downlink.
757
758 LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
759
760
761 == 3.1 Access AT Command ==
762
763
764 TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below.
765
766 [[image:1664502999401-486.png||_mstalt="296985"]]
767
768
769 In PC, User needs to set serial tool baud rate to (% style="color:green" %)**115200**(%%) to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
770
771
772 [[image:1664503022490-662.png||_mstalt="293332"]]
773
774
775 [[image:1664503035713-500.png||_mstalt="291096"]]
776
777
778 [[image:1664503047675-651.png||_mstalt="295386"]]
779
780 (% style="display:none" %) (%%)
781
782 == 3.2 Command Set ==
783
784 === 3.2.1 Set Transmit Interval ===
785
786
787 Set device uplink interval.
788
789 * (% style="color:blue" %)**AT Command:**
790
791 (% style="color:#037691" %)**AT+TDC=xxx **
792
793 Example:  AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
794
795
796 * (% style="color:blue" %)**Downlink Payload (prefix 0x01):**
797
798 (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
799
800
801 === 3.2.2 Set Alarm Packet transmission interval ===
802
803
804 Set alarm packet transmit interval
805
806 * (% style="color:blue" %)**AT Command:**
807
808 (% style="color:#037691" %)**AT+ATDC=xx. **
809
810 Example:  AT+ATDC=60000  **~-~->    ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
811
812
813 * (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**
814
815 (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
816
817
818 === 3.2.3 Set Transport Mode Packet transmission interval ===
819
820
821 Set Transport Mode packet transmit interval
822
823 * (% style="color:blue" %)**AT Command:**
824
825 (% style="color:#037691" %)**AT+MTDC=xx. **
826
827 Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
828
829
830 * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
831
832 (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
833
834
835 === 3.2.4 Exit Alarm ===
836
837
838 Server send downlink command to exit Alarm mode
839
840 * (% style="color:blue" %)**AT Command: No AT Command**
841
842 * (% style="color:blue" %)**Downlink Payload (prefix 0x02):**
843
844 (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
845
846
847 === 3.2.5 Disable/Enable LED flash and buzzer ===
848
849
850 Disable/Enable LED for position, downlink and uplink
851
852 * (% style="color:blue" %)**AT Command:**
853
854 (% style="color:#037691" %)**AT+LON=xx.  (Disable (0), Enable (1), default:1)**
855
856 Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
857
858
859 * (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**
860
861 (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
862
863
864 === 3.2.6 Disable/Enable Transport Mode ===
865
866
867 Users can use this feature to enable/disable Transport Mode.
868
869 * (% style="color:blue" %)**AT Command:**
870
871 (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
872
873 Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
874
875
876 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
877
878 (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
879
880
881 === 3.2.7 Set Positioning Mode ===
882
883
884 SMOD define how TrackerD scan and uplink data:
885
886 * (% style="color:blue" %)**AT Command:**
887
888 (% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
889
890 (% style="color:#037691" %)** aa:**
891
892 * (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
893
894 * (% 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.
895
896 * (% 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.
897
898 (% style="color:#037691" %)**bb:**
899
900 * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
901
902 * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
903
904 (% style="color:#037691" %)**cc:   **
905
906 * (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
907
908 * (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
909
910 (% style="color:blue" %)**Example:**
911
912 AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
913
914 AT+SMOD=1,1,0 ~-~->  GPS +BAT State
915
916 AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
917
918 AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
919
920 AT+SMOD=2,0,3  ~-~->  (iBeacon) (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State
921
922 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
923
924 (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
925
926
927 === 3.2.8 Set MAX GPS position time ===
928
929
930 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.
931
932 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.
933
934 * (% style="color:blue" %)**AT Command:**
935
936 (% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
937
938 **Example:**  AT+FTIME=150
939
940
941 * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
942
943 (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
944
945
946 === 3.2.9 Set PDOP value for GPS fix accuracy ===
947
948
949 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.
950
951 A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
952
953 * (% style="color:blue" %)**AT Command:**
954
955 (% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
956
957
958 * (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**
959
960 (% style="color:#037691" %)**0xAD 00 0A**   (%%) ~/~/  Set AT+PDOP=1  (0x0A / 10 =1)
961
962 (% style="color:#037691" %)**0xAD 00 19**   (%%) ~/~/  Set AT+PDOP=2.5    (0x19 / 10 =2.5)
963
964 (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
965
966
967 === 3.2.10 Disable/Enable the confirmation mode ===
968
969
970 * (% style="color:blue" %)**AT Command:**
971
972 (% style="color:#037691" %)**AT+CFM=xx**
973
974
975 **Example:**
976
977 AT+CFM=0    **~-~->   ** Disable confirmation
978
979 AT+CFM=1    **~-~->  ** Enable confirmation
980
981
982 * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
983
984 (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
985
986
987 === 3.2.11  Auto Send None-ACK messages ===
988
989
990 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.
991
992
993 * (% style="color:blue" %)**AT Command: AT+PNACKMD**
994
995 The default factory setting is 0.
996
997
998 **Command Example Function Response:**
999
1000 (% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
1001
1002
1003 * (% style="color:blue" %)**Downlink Command: 0x34**
1004
1005 Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
1006
1007
1008 === 3.2.12  Set BLEMASK to filter BLE iBeacon ===
1009
1010
1011 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.
1012
1013 (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
1014
1015 (% style="color:blue" %)**AT Command:**
1016
1017 (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
1018
1019 (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
1020
1021 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
1022
1023 Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
1024
1025
1026 === 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
1027
1028
1029 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.
1030
1031 (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
1032
1033 (% style="color:blue" %)**AT Command:**
1034
1035 (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1036
1037 (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1038
1039 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
1040
1041 Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
1042
1043
1044 === 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
1045
1046
1047 Users can use this feature to enable/disable Information printing.
1048
1049 (% style="color:blue" %)**AT Command:**
1050
1051 (% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
1052 \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1053
1054
1055 === 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1056
1057
1058 The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
1059
1060 (% style="color:blue" %)**AT Command:**
1061
1062 (% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
1063
1064
1065 (% style="color:blue" %)**Downlink Payload:0X24**
1066
1067 Example: 0x24 01  ~/~/ Same as AT+CHE=1
1068
1069
1070 === 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1071
1072
1073 User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1074
1075 (% style="color:blue" %)**AT Command:**
1076
1077 (% style="color:#037691" %)**AT+PT=xx**
1078
1079 Example:
1080
1081 AT+PT=14    ~-~->    Set to detect car motion.
1082
1083 AT+PT=41  ~-~->    set to detect walk motion.
1084
1085
1086 (% style="color:blue" %)**Downlink Payload:0xB4**
1087
1088 0xB4 14          ~/~/  Same as AT+PT=14
1089
1090
1091 === 3.2.17  Set AT command window time（Since firmware 1.4.5） ===
1092
1093
1094 AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
1095
1096 (% style="color:blue" %)**AT Command:**
1097
1098 (% style="color:#037691" %)**AT+ATST=XX**
1099
1100 Example:
1101
1102 AT+ATST=15    ~-~-> Set the time to 15 seconds
1103
1104 (% style="color:blue" %)**Downlink Payload:0XB5**
1105
1106 0xB5 0F          ~/~/  Same as AT+ATST=15
1107
1108
1109 === 3.2.18  Set the stepmeter mode（Since firmware 1.4.5） ===
1110
1111
1112 After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
1113
1114 (% style="color:blue" %)**AT Command:**
1115
1116 (% style="color:#037691" %)**AT+PM=xx**
1117
1118 Example:
1119
1120 AT+PM=1    ~-~->  Turn on step counting mode
1121
1122 AT+PM=0    ~-~->  Turn OFF step counting mode
1123
1124 (% style="color:blue" %)**Downlink Payload:0XB6**
1125
1126 0xB6 01          ~/~/  Same as AT+PM=1
1127
1128
1129 === 3.2.19  Set down the decline detection mode（Since firmware 1.4.5） ===
1130
1131
1132 This mode is used in conjunction with AT+PT(The recommended threshold is between 50 and 70, you need to set it according to the environment yourself). This function is used in hospitals, nursing homes, nursing homes and other places to prevent the elderly and patients from falling. No one knows.
1133
1134 (% style="color:blue" %)**AT Command:**
1135
1136 (% style="color:#037691" %)**AT+FD=xx**
1137
1138 **Example:**
1139
1140 AT+FD=1    ~-~->  Turn on the Fall detection
1141
1142 AT+FD=0    ~-~->  Turn OFF the Fall detection
1143
1144 (% style="color:blue" %)**Downlink Payload:0XB7**
1145
1146 0xB7 01          ~/~/  Same as AT+FD=1
1147
1148
1149 === 3.2.20 Disable/Enable buzzer（Since firmware 1.4.6） ===
1150
1151
1152 Disable/Enable buzzer for Alarm, downlink and uplink
1153
1154 (% style="color:blue" %)**AT Command:**
1155
1156 (% style="color:#037691" %)**AT+BEEP=XX**
1157
1158 Example:
1159
1160 AT+BEEP=1 ~-~-> Turn on the buzzer
1161
1162 AT+BEEP=0 ~-~-> Turn OFF the buzzer
1163
1164 (% style="color:blue" %)**Downlink Payload:0XB9**
1165
1166 0xB9 01 ~/~/ Same as AT+BEEP=1
1167
1168
1169 === 3.2.21 Set long press time（Since firmware 1.4.6） ===
1170
1171
1172 When using the red button Changan to alarm, press and hold the time to set 0~~10 seconds, which is convenient for use scenarios.
1173
1174 (% style="color:blue" %)**AT Command:**
1175
1176 (% style="color:#037691" %)**AT+EAT=XX**
1177
1178 Example:
1179
1180 AT+EAT=2 ~-~-> Set the long press time to 2s
1181
1182 (% style="color:blue" %)**Downlink Payload:0XBA**
1183
1184 0xBA 02 ~/~/ Same as AT+EAT=2
1185
1186
1187 = 4. Setting for Different Scenarios =
1188
1189
1190
1191 = 5. Upload Firmware =
1192
1193 == 5.1 Firmware Change Log ==
1194
1195
1196 **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1197
1198
1199 == 5.2 How to upgrade firmware ==
1200
1201
1202 User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
1203
1204
1205 (% style="color:blue" %)**Step1:  **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
1206
1207
1208 (% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC.
1209
1210 After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
1211
1212
1213 (% style="color:blue" %)**Step3:  **(%%)Download and Install Flash Tool:  [[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]]
1214
1215
1216 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1217
1218
1219 [[image:1664503563660-578.png||_mstalt="296777"]]
1220
1221
1222 [[image:1664503574618-659.png||_mstalt="297986"]]
1223
1224
1225
1226 (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
1227
1228 [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1229
1230
1231 **Users need to use below files:**
1232
1233 boot_app0.bin @0e000
1234
1235 US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1236
1237
1238 [[image:image-20221207120501-1.png]]
1239
1240
1241
1242 After upgrade finish, it will show finish as below:
1243
1244 [[image:image-20221207133911-7.png]]
1245
1246
1247 = 6. Developer Guide =
1248
1249 == 6.1 Compile Source Code ==
1250
1251 === 6.1.1 Set up ARDUINO compile environment ===
1252
1253
1254 * **Download the latest Arduino software (IDE) from the Arduino official website:  [[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]**
1255
1256 Install IDE on PC, open and click (% style="color:#037691" %)**File ~-~-> Preference**,(%%) add the following URL:  [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]]
1257
1258
1259 [[image:1664503635019-941.png||_mstalt="294658"]]
1260
1261
1262
1263 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1264
1265 [[image:1664503715811-892.png||_mstalt="295698"]]
1266
1267
1268 === 6.1.2  Build the development environment ===
1269
1270
1271 **~1. Download and install arduino IDE**
1272
1273 [[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]]
1274
1275
1276 **2. Download the ESP32 development package in the arduino IDE**
1277
1278 [[image:image-20221213100007-1.png]]
1279
1280
1281 Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1282
1283 [[image:image-20221213100626-2.png]]
1284
1285
1286 Restart the IDE after the addition is complete, then:
1287
1288 [[image:image-20221213100808-3.png||height="679" width="649"]]
1289
1290
1291 [[image:image-20221213101040-4.png]]
1292
1293
1294 (% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1295 Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)**
1296
1297
1298 Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import:
1299
1300 (% style="color:blue" %)**Methods as below:**
1301
1302 ~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1303
1304 2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1305
1306 (% 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.
1307
1308 [[image:image-20221213102311-5.png||height="582" width="711"]]
1309
1310
1311 **3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1312
1313 [[image:image-20221213102334-6.png]]
1314
1315 (% style="color:red" %)**Note: This step requires a python environment**
1316
1317
1318 Either way, in the end:
1319
1320 The final effect is to open the arduino and you can see the esp32
1321
1322 [[image:image-20221213110952-8.png||height="866" width="711"]]
1323
1324
1325
1326 [[image:image-20221024105643-1.png||_mstalt="428129"]]
1327
1328 **~ Figure1**
1329
1330
1331
1332 [[image:image-20221024105643-2.png||_mstalt="428493"]]
1333
1334 **Figure2**
1335
1336
1337 * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1338
1339 Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1340
1341
1342 [[image:1664503752288-974.png||_mstalt="298194"]]
1343
1344
1345 == 6.2 Source Code ==
1346
1347
1348 * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1349
1350 [[image:1664503794261-827.png||_mstalt="296387"]]
1351
1352
1353
1354 * (% style="color:blue" %)**Click to upload**
1355
1356 [[image:1664503808294-336.png||_mstalt="295711"]]
1357
1358
1359
1360 * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1361
1362 [[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1363
1364
1365 = 7.  FAQ =
1366
1367 == 7.1 How to change the LoRa Frequency Bands/Region? ==
1368
1369
1370 User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1371
1372
1373 == 7.2 What is the pin mapping for the USB program cable? ==
1374
1375
1376 [[image:1664499635206-262.png||_mstalt="295360"]]
1377
1378
1379 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:314px" %)
1380 |=(% style="width: 120px;background-color:#D9E2F3;color:#0070C0" %)**Pin**|=(% style="width: 69px;background-color:#D9E2F3;color:#0070C0" %)**Color**|=(% style="width: 125px;background-color:#D9E2F3;color:#0070C0" %)**USB Pin**
1381 |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1382 |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1383 |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
1384 |(% style="width:118px" %)A1,B1,A12,B12|(% style="width:67px" %)Black|(% style="width:123px" %)GND
1385 |(% style="width:118px" %)A5|(% style="width:67px" %)Purple|(% style="width:123px" %)MTDC/GOIO13
1386 |(% style="width:118px" %)B5|(% style="width:67px" %)Blue|(% style="width:123px" %)MTDC/GPIO12
1387 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1388 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1389
1390 (% style="display:none" %) (%%)
1391
1392
1393 == 7.3 Notes on using different serial port tools for TrackerD ==
1394
1395 === 7.3.1  Serial port utility ===
1396
1397
1398 Serial port utility requires you to automatically add data streams.
1399
1400 Need to adjust the data stream to RTS/CTS on physical restart.
1401
1402 (% class="wikigeneratedid" %)
1403 [[image:image-20221102140621-1.png||_mstalt="425672"]]
1404
1405
1406 When using AT commands, the data flow needs to be adjusted to XON/XOFF
1407
1408 [[image:image-20221102140638-2.png||_mstalt="428727"]]
1409
1410
1411 === 7.3.2  SecureCRT ===
1412
1413
1414 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.
1415
1416
1417 [[image:image-20221102140704-3.png||_mstalt="427076"]]
1418
1419
1420 [[image:image-20221102140712-4.png||_mstalt="427089"]]
1421
1422
1423 === 7.3.3  PUTTY ===
1424
1425
1426 [[image:image-20221102140748-5.png||_mstalt="430456"]]
1427
1428
1429 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.
1430
1431
1432 [[image:image-20221102140801-6.png||_mstalt="427466"]]
1433
1434
1435 == 7.4 How to modify source code to compile different frequency band bin file? ==
1436
1437
1438 (% class="box infomessage" %)
1439 (((
1440 (% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1441 See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1442 )))
1443
1444 **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1445
1446
1447 [[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1448
1449
1450
1451 **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1452
1453
1454 [[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1455
1456
1457
1458 **3. Compile the AS923_JP band, please refer to the intention shown**
1459
1460
1461 [[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1462
1463
1464
1465 **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.**
1466
1467
1468 [[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1469
1470
1471 [[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1472
1473
1474 == 7.5 Are there example python example for BLE Indoor Positioning? ==
1475
1476
1477 [[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1478
1479
1480 == 7.6 Can alert mode and transport mode be used together? ==
1481
1482
1483 Yes, you can also press the panic button to sound the alarm if set to transport mode
1484
1485
1486 = 8  Trouble Shooting =
1487
1488 == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1489
1490
1491 (((
1492 Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**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
1493 )))
1494
1495
1496 == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1497
1498
1499 (((
1500 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.
1501 )))
1502
1503
1504 == 8.3  Problem after Upgrading Firmware ==
1505
1506 === 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1507
1508
1509 **Error Output**
1510
1511
1512 [[image:image-20221122100004-4.png||_mstalt="424606"]]
1513
1514
1515 (((
1516 Some partition is missed during upgrade, please upgrade below four files as example:
1517
1518 [[image:image-20221207120524-2.png]]
1519 )))
1520
1521
1522 === 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1523
1524
1525 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
1526
1527
1528 === 8.3.3 "flash read err" after upgrade firmware ===
1529
1530
1531 Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1532
1533 [[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1534
1535
1536 User need to upgrade again with below four files to solve this issue.
1537
1538 [[image:image-20221207120530-3.png]]
1539
1540 **Figure 2**
1541
1542
1543 === 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1544
1545
1546 User might erase the entire flash include keys and default settings which cause this issue.
1547
1548 After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below.
1549
1550
1551 [[image:image-20221122100004-3.png||_mstalt="424242"]]
1552
1553
1554 Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1555
1556 After AT+FDR. please set
1557
1558 * (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1559
1560 * (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1561
1562 **Example:**
1563
1564 AT+PDOP=7.00
1565
1566 AT+FTIME=180
1567
1568 AT+DEUI=70B3D57ED0053981  
1569
1570 AT+APPEUI=D23345667BCBCCAF
1571
1572 AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1573
1574 AT+DADDR=260b4dce    ( no need for OTAA)
1575
1576 AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1577
1578 AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1579
1580
1581 == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1582
1583
1584 Please download version 1.4.2 again
1585
1586
1587 == 8.5  How to deal with unsuccessful GPS positioning? ==
1588
1589
1590 1） Make Sure the device is in Open Area where can see the sky.
1591
1592 2)  Set PDOP to a higher value.
1593
1594 * (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1595
1596 * (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1597
1598 * (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1599
1600 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
1601
1602
1603 == 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1604
1605
1606 When upgrading, use the erase button to upgrade
1607
1608 [[image:image-20221207120536-4.png]]
1609
1610
1611 The parameters are displayed abnormally and cannot be fixed using AT+FDR
1612
1613 [[image:image-20221128103040-2.png||height="431" width="525"]]
1614
1615
1616 Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1617
1618 [[image:image-20221207134028-8.png]]
1619
1620
1621 Reboot information after upgrade
1622
1623 [[image:image-20221128111443-4.png||height="432" width="546"]]
1624
1625
1626 Use (% style="color:blue" %)**AT+FDR**(%%) command to reset and then use (% style="color:blue" %)**AT+CFG**(%%) to check whether the configuration is back to normal
1627
1628 [[image:image-20221128111850-5.png]]
1629
1630
1631 After the parameters return to normal, upgrade to the version you need again
1632
1633 [[image:image-20221207120601-5.png]]
1634
1635
1636 At this point, the parameters return to normal after running AT+FDR again
1637
1638 [[image:image-20221128112035-7.png]]
1639
1640
1641 == 8.7  If you encounter the following problems, please upgrade to the latest version ==
1642
1643
1644 ~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1645
1646 2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1647
1648
1649 == 8.8  Why when using some serial consoles, only inputting the first string port console will return "error"? ==
1650
1651
1652 Need to enter the entire command at once, not a single character.
1653 User can open a command window or copy the entire command to the serial console.
1654
1655
1656 = 9.  Order Info =
1657
1658
1659 Part Number: (% style="color:blue" %)**TrackerD-XXX**
1660
1661 (% style="color:blue" %)**XXX**(%%): The default frequency band
1662
1663 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1664
1665 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1666
1667 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1668
1669 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1670
1671 * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1672
1673 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1674
1675 * (% style="color:red" %)**US915**(%%): Default frequency band US915
1676
1677 (% style="display:none" %) (%%)
1678
1679
1680 = 10.  Packing Info =
1681
1682
1683 (% style="color:#037691" %)**Package Includes**:
1684
1685 * TrackerD LoRaWAN GPS/BLE Tracker x 1
1686
1687 * USB recharge & program cable x 1
1688
1689 (% style="color:#037691" %)**Dimensions and Weight**:
1690
1691 * Device Size: 85 x 48 x 15 mm
1692
1693 * Weight: 50g
1694
1695 (% style="display:none" %) (%%)
1696
1697
1698 = 11. Support =
1699
1700
1701 * 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.
1702
1703 * 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]].
1704
1705 (% style="display:none" %)
1706
1707
1708
1709 = 12.  Reference =
1710
1711
1712 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1713
1714 * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1715
1716 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1717
1718
1719 )))