Version 210.3 by Xiaoling on 2023/08/07 16:16

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