Version 155.3 by Xiaoling on 2022/11/24 17:07

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 = 1.  Introduction =
16
17 == 1.1  What is TrackerD ==
18
19
20 (((
21 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**.
22 )))
23
24 (((
25 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.
26
27 (((
28 TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.
29 )))
30
31 (((
32 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.
33 )))
34
35 (((
36 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.
37 )))
38
39 [[image:1664499921684-770.png||_mstalt="298194"]]
40
41
42 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
43
44
45 == 1.2 Specifications ==
46
47
48 (% style="color:blue" %)**Micro Controller:**
49
50 * Espressif ESP32 PICO D4
51 * MCU: ESP32 PICO D4
52 * Bluetooth: Bluetooth V4.2 BR/EDR and Bluetooth LE
53 * WiFi : 802.11 b/g/n (802.11n up to 150 Mbps)
54 * Integrated SPI flash : 4 MB
55 * RAM: 448 KB
56 * EEPROM: 520 KB
57 * Clock Speed: 32Mhz
58
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
66 (% style="color:blue" %)**LoRa Spec:**
67
68 * Frequency Range,
69 ** Band 1 (HF): 862 ~~ 1020 Mhz
70 * 168 dB maximum link budget.
71 * +20 dBm - 100 mW constant RF output vs.
72 * +14 dBm high efficiency PA.
73 * Programmable bit rate up to 300 kbps.
74 * High sensitivity: down to -148 dBm.
75 * Bullet-proof front end: IIP3 = -12.5 dBm.
76 * Excellent blocking immunity.
77 * Low RX current of 10.3 mA, 200 nA register retention.
78 * Fully integrated synthesizer with a resolution of 61 Hz.
79 * FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
80 * Built-in bit synchronizer for clock recovery.
81 * Preamble detection.
82 * 127 dB Dynamic Range RSSI.
83 * Automatic RF Sense and CAD with ultra-fast AFC.
84 * Packet engine up to 256 bytes with CRC.
85 * LoRaWAN 1.0.3 Specification
86
87
88 (% style="color:blue" %)**Battery:**
89
90 * 1000mA Li-on Battery power (for model TrackerD)
91
92
93 (% style="color:blue" %)**Power Consumption**
94
95 * Sleeping Mode: 200uA
96 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
97 * Tracking: max: 38mA
98
99
100
101
102 == 1.3  Features ==
103
104
105 * LoRaWAN 1.0.3 Class A
106 * ESP32 PICO D4
107 * SX1276/78 Wireless Chip
108 * Arduino IDE Compatible
109 * Open source hardware / software
110 * Regular/ Real-time GPS,BLE,WIFI tracking
111 * Built-in3 axis accelerometer (LIS3DH)
112 * Humidity / temperature sensor : GXCAS Technology GXHT3X
113 * Motion sensing capability
114 * Power Monitoring
115 * Charging circuit via USB port
116 * 1000mA Li-on Battery power
117 * Tri-color LED, Alarm button
118 * Datalog
119
120
121
122
123
124 == 1.4  Applications ==
125
126
127 * Logistics and Supply Chain Management
128 * Human tracking
129
130
131
132
133 = 2.  Use TrackerD =
134
135 == 2.1 How it works? ==
136
137
138 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.
139
140
141 == 2.2 Quick guide to connect to LoRaWAN server ==
142
143
144 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. 
145
146
147 [[image:1664501652064-326.png||_mstalt="293306"]]
148
149
150
151 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:
152
153
154 (% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
155
156 Each TrackerD is shipped with a sticker with the default device EUI as below:
157
158
159 [[image:1664501677253-891.png||_mstalt="296569"]]
160
161
162 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
163
164
165 **__Add APP EUI in the application:__**
166
167
168 [[image:1664501711466-918.png||_mstalt="295828"]]
169
170
171
172 [[image:1664501721248-725.png||_mstalt="294450"]]
173
174
175 [[image:1664501734705-405.png||_mstalt="293306"]]
176
177
178
179 **__Add APP KEY and DEV EUI:__**
180
181
182 [[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"]]
183
184
185
186 (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
187
188 (% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
189
190 [[image:1664502835802-546.png||_mstalt="295061"]]
191
192
193 (% 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.
194
195
196 == 2.3  Positioning Mode(SMOD) ==
197
198
199 Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
200
201 * (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
202 * (% 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.
203 * (% 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.
204
205 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
206
207
208 == 2.4  Uplink Payload ==
209
210 === 2.4.1 Uplink FPORT~=5, Device Status ===
211
212
213 Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.
214
215 Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
216
217
218 (% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
219 |=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
220 |=(% 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
221
222 [[image:1665301570342-765.png||_mstalt="294580"]]
223
224
225 (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
226
227 (% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
228
229 (% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
230
231 (% style="color:#037691" %)**Frequency Band**:
232
233 *0x01: EU868
234
235 *0x02: US915
236
237 *0x03: IN865
238
239 *0x04: AU915
240
241 *0x05: KZ865
242
243 *0x06: RU864
244
245 *0x07: AS923
246
247 *0x08: AS923-1
248
249 *0x09: AS923-2
250
251 *0x0a: AS923-3
252
253 Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
254
255 (% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
256
257
258 (% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
259
260 Use can also get the Device Status uplink through the downlink command:
261
262
263 (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40
264
265 (% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
266 |=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
267 |=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
268
269 (% style="color:blue" %)** SMOD:**
270
271 (% style="color:red" %)** 1 :** (%%) GPS ONLY
272
273 (% style="color:red" %)** 2 :** (%%) BLE ONLY
274
275 (% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
276
277
278 (% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
279
280 (% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
281
282 (% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
283
284
285 (% style="color:blue" %)** BLE_Settings:**
286
287 (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
288
289 (% _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)(%%)  
290
291
292 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
293
294 (% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
295 |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
296 |=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
297
298
299 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
300
301
302 Users can use **AT+SMOD=1,0,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
303
304
305 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
306 |=(% scope="row" style="width: 60px;" %)(((
307 **Size(bytes)**
308 )))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
309 2
310 )))|(% style="width:30px" %)(((
311 2
312 )))
313 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
314 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
315 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
316
317 [[image:1665301636888-168.png||_mstalt="298012"]]
318
319
320 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
321
322 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
323 |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
324 |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
325
326 ==== (% style="color:blue" %)**FLAG:**(%%) ====
327
328 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
329 |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
330 |=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
331
332 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
333
334
335 ==== (% style="color:blue" %)**Location info:**(%%) ====
336
337 * Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
338 * Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
339
340 (% style="color:red" %)**Important note:**
341
342 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.
343
344 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:
345
346
347 [[image:1664502116362-706.png||_mstalt="293306"]]
348
349
350 3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
351
352 [[image:1664502166010-515.png||_mstalt="291395"]]
353
354
355
356 ==== (% style="color:blue" %)**Alarm:**(%%) ====
357
358 **Example: ** 0x4B & 0x40 >> 6 = 0x01
359
360
361 ==== (% style="color:blue" %)**BAT:**(%%) ====
362
363 **Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
364
365 (((
366 The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
367 )))
368
369 * > 4.0v :  80% ~~ 100%
370 * 3.85v ~~3.99v:  60% ~~ 80%
371 * 3.70v ~~ 3.84v:  40% ~~ 60%
372 * 3.40v ~~ 3.69v:  20% ~~ 40%
373 * < 3.39v:  0~~20%
374
375
376
377
378 ==== (% style="color:blue" %)**MOD:**(%%) ====
379
380 **Example: ** (0x60>>6) & 0x3f =1
381
382 **Set the format of GPS data uplink link:**
383
384 (% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
385 (% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
386
387
388 **Set the format of BLE data uplink link:**
389
390 (% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
391
392
393 ==== (% style="color:blue" %)**LON:**(%%) ====
394
395 **Example:** (0x60>>5) & 0x01=1.
396
397 Enable/Disable LED activity for uplink
398
399 (((
400 (% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
401 )))
402
403 (((
404 (% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
405 )))
406
407
408 ==== (% style="color:blue" %)**Hum:**(%%) ====
409
410 0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
411
412
413 ==== (% style="color:blue" %)**Tem:**(%%) ====
414
415 011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
416
417
418 === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
419
420
421 The default uplink payload includes total 11 bytes (**AT+SMOD=1,1,0**). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
422
423
424 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
425 |=(% scope="row" style="width: 60px;" %)(((
426 **Size(bytes)**
427 )))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
428 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
429 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
430 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
431
432 (% class="wikigeneratedid" %)
433 [[image:1665301687277-443.png||_mstalt="296140"]]
434
435
436 === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
437
438
439 Set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-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.
440
441
442 (% style="color:red" %)**Note for this mode:**
443
444 * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
445 * 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.
446 * 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
447
448 The payload is 15 bytes, as below.
449
450 (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
451 |=(% scope="row" %)(((
452 **Size(bytes)**
453 )))|4|4|2|1|1|1|1|1
454 |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
455
456 [[image:image-20221009160309-2.png||_mstalt="429312"]]
457
458
459 === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
460
461
462 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.
463
464 User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
465
466
467 (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
468 |=(% scope="row" style="width: 60px;" %)(((
469 **Size(bytes)**
470 )))|(% 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
471 |=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
472 iBeacon MAJOR
473 )))|(% style="width:63px" %)(((
474 iBeacon MINOR
475 )))|(% style="width:71px" %)(((
476 iBeacon Measured Power
477 )))|(% style="width:50px" %)(((
478 iBeacon RSSI
479 )))|(% style="width:47px" %)(((
480 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
481 )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
482
483 [[image:1664502425687-834.png||_mstalt="296738"]]
484
485
486 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
487 * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
488 * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
489 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
490 * (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
491 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
492 * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
493
494
495
496
497 === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) ===
498
499
500 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.
501
502
503 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
504 |=(% scope="row" style="width: 60px;" %)(((
505 **Size(bytes)**
506 )))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
507 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
508 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
509 )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
510
511 (% class="wikigeneratedid" %)
512 [[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
513
514
515 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
516 * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
517 * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
518
519
520
521
522 === 2.4.7  Add Payload format in TTN V3 ===
523
524
525 In TTN V3, user can add a custom payload so it shows friendly.
526
527 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
528
529
530 [[image:1664502649601-895.png||_mstalt="296985"]]
531
532
533
534 Add the decoder from this link: 
535
536 [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
537
538 Save the change the uplink message will be parsed. As below:
539
540 [[image:1664502676891-606.png||_mstalt="296673"]]
541
542
543 == 2.5 Integrate with Datacake ==
544
545
546 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.
547
548 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]]
549
550
551 [[image:1664502695771-538.png||_mstalt="297349"]]
552
553
554 == 2.6 Integrate with Tago ==
555
556
557 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.
558
559 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]]
560
561
562 [[image:1664502715371-321.png||_mstalt="292162"]]
563
564
565 == 2.7  Datalog Feature ==
566
567
568 total 273 entries,by default,
569
570 User can set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
571
572 Example use case.
573
574 [[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
575
576
577 [[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
578
579
580 == 2.8 Alarm Mode ==
581
582
583 (((
584 User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
585 )))
586
587
588 (((
589 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.
590 )))
591
592
593 (((
594 **Two ways to exit alarm mode:**
595 )))
596
597 * Server sends a downlink command to exit.
598 * User fast press the RED button 10 times.
599
600 (((
601 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.
602 )))
603
604
605 == 2.9 Transport Mode ==
606
607
608 In Transport Mode, TrackerD will check if there is motion. If there is no motion, device will send uplinks every 20 minutes. If there is motion, device will send uplink every 5 minutes.
609
610 * **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
611 * **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
612 * **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
613
614
615
616
617 == 2.10 LED Status ==
618
619
620 (% border="1.5" style="background-color:#ffffcc; width:500px" %)
621 |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
622 |(% 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
623 |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
624 |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
625 |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
626 |(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
627 |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
628 |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
629 |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
630 |(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes
631 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
632 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
633
634
635 == 2.11 Button Function ==
636
637
638 (% style="color:blue" %)**RESET button:**
639
640 [[image:1664502835802-546.png||_mstalt="295061"]]
641
642 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
643
644
645 (% style="color:red" %)**RED button:**
646
647 [[image:1664502854406-763.png||_mstalt="295568"]]
648
649
650 (% border="1" style="background-color:#ffffcc; width:510px" %)
651 |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
652 |(% 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"]]
653 |(% 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
654 |(% 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.
655
656
657 == 2.12 USB Port Function ==
658
659
660 The USB interface of TrackerD has below functions:
661
662 * Power on the device
663 * Recharge the battery
664 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
665 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
666
667
668
669
670 = 3. Configure TrackerD via AT command or LoRaWAN downlink =
671
672
673 User can configure TrackerD via AT Command or LoRaWAN Downlink.
674
675 LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
676
677
678 == 3.1 Access AT Command ==
679
680
681 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.
682
683
684 [[image:1664502999401-486.png||_mstalt="296985"]]
685
686
687 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:
688
689
690 [[image:1664503022490-662.png||_mstalt="293332"]]
691
692
693 [[image:1664503035713-500.png||_mstalt="291096"]]
694
695
696 [[image:1664503047675-651.png||_mstalt="295386"]]
697
698
699
700 == 3.2 Command Set ==
701
702 === 3.2.1 Set Transmit Interval ===
703
704
705 Set device uplink interval.
706
707 * (% style="color:blue" %)**AT Command:**
708
709 (% style="color:#037691" %)**AT+TDC=xxx **
710
711 Example:  AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
712
713
714 * (% style="color:blue" %)**Downlink Payload (prefix 0x01):**
715
716 (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
717
718
719 === 3.2.2 Set Alarm Packet transmission interval ===
720
721
722 Set alarm packet transmit interval
723
724 * (% style="color:blue" %)**AT Command:**
725
726 (% style="color:#037691" %)**AT+ATDC=xx. **
727
728 Example:  AT+ATDC=60000  **~-~->    ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
729
730
731 * (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**
732
733 (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
734
735
736 === 3.2.3 Set Transport Mode Packet transmission interval ===
737
738
739 Set Transport Mode packet transmit interval
740
741 * (% style="color:blue" %)**AT Command:**
742
743 (% style="color:#037691" %)**AT+MTDC=xx. **
744
745 Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
746
747
748 * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
749
750 (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
751
752
753 === 3.2.4 Exit Alarm ===
754
755
756 Server send downlink command to exit Alarm mode
757
758 * (% style="color:blue" %)**AT Command: No AT Command**
759
760 * (% style="color:blue" %)**Downlink Payload (prefix 0x02):**
761
762 (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
763
764
765 === 3.2.5 Disable/Enable LED flash ===
766
767
768 Disable/Enable LED for position, downlink and uplink
769
770 * (% style="color:blue" %)**AT Command:**
771
772 (% style="color:#037691" %)**AT+LON=xx.  (Disable (0), Enable (1), default:1)**
773
774 Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
775
776
777 * (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**
778
779 (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
780
781
782 === 3.2.6 Disable/Enable Transport Mode ===
783
784
785 Users can use this feature to enable/disable Transport Mode.
786
787 * (% style="color:blue" %)**AT Command:**
788
789 (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
790
791 Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
792
793
794 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
795
796 (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
797
798
799 === 3.2.7 Set Positioning Mode ===
800
801
802 SMOD define how TrackerD scan and uplink data:
803
804
805 * (% style="color:blue" %)**AT Command:**
806
807 (% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
808
809 (% style="color:#037691" %)** aa:**
810
811 * (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
812
813 * (% 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.
814
815 * (% 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.
816
817 (% style="color:#037691" %)**bb:**
818
819 * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
820
821 * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
822
823 (% style="color:#037691" %)**cc:   **
824
825 * (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
826
827 * (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
828
829 (% style="color:blue" %)**Example:**
830
831 AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
832
833 AT+SMOD=1,1,0 ~-~->  GPS +BAT State
834
835 AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
836
837 AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
838
839
840 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
841
842 (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
843
844
845 === 3.2.8 Set MAX GPS position time ===
846
847
848 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.
849
850
851 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.
852
853
854 * (% style="color:blue" %)**AT Command:**
855
856 (% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
857
858 **Example:**  AT+FTIME=150
859
860
861 * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
862
863 (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
864
865
866 === 3.2.9 Set PDOP value for GPS fix accuracy ===
867
868
869 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.
870
871
872 A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
873
874
875 * (% style="color:blue" %)**AT Command:**
876
877 (% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
878
879
880 * (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**
881
882 (% style="color:#037691" %)**0xAD 00 0A**   (%%) ~/~/  Set AT+PDOP=1  (0x0A / 10 =1)
883
884 (% style="color:#037691" %)**0xAD 00 19**   (%%) ~/~/  Set AT+PDOP=2.5    (0x19 / 10 =2.5)
885
886 (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
887
888
889
890 === 3.2.10 Disable/Enable the confirmation mode ===
891
892 * (% style="color:blue" %)**AT Command:**
893
894 (% style="color:#037691" %)**AT+CFM=xx**
895
896
897 **~ Example:**
898
899 AT+CFM=0    **~-~->   ** Disable confirmation
900
901 AT+CFM=1    **~-~->  ** Enable confirmation
902
903
904 * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
905
906 (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
907
908
909 === 3.2.11  Auto Send None-ACK messages ===
910
911
912 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.
913
914
915 * (% style="color:blue" %)**AT Command: AT+PNACKMD**
916
917 The default factory setting is 0.
918
919
920 **Command Example Function Response:**
921
922 (% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
923
924
925 * (% style="color:blue" %)**Downlink Command: 0x34**
926
927 Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
928
929
930 === 3.2.12  Set BLEMASK to filter BLE iBeacon ===
931
932
933 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.
934
935 (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
936
937 (% style="color:blue" %)**AT Command:**
938
939 (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
940
941 (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
942
943 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)**
944
945 Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
946
947
948 === 3.2.13  Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===
949
950
951 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.
952
953 (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
954
955 (% style="color:blue" %)**AT Command:**
956
957 (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
958
959 (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
960
961 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)**
962
963 Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
964
965
966 === 3.2.14  Disable/Enable Information printing(Since firmware 1.4.1) ===
967
968
969 Users can use this feature to enable/disable Information printing.
970
971 (% style="color:blue" %)**AT Command:**
972
973 (% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
974 \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
975
976
977 === 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===
978
979
980 The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
981
982 (% style="color:blue" %)**AT Command:**
983
984 (% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
985
986
987 (% style="color:blue" %)**Downlink Payload:0X24**
988
989 Example: 0x24 01 ~/~/ Same as AT+CHE=1
990
991
992 === 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) ===
993
994 User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
995
996 (% style="color:blue" %)**AT Command:**
997
998 (% style="color:#037691" %)**AT+PT=xx**
999
1000 Example:
1001
1002 AT+PT=14    ~-~->    Set to detect car motion.
1003
1004 AT+PT=41   ~-~->    set to detect walk motion.
1005
1006
1007 (% style="color:blue" %)**Downlink Payload:0xB4**(%%)
1008 0xB4 14          ~/~/  Same as AT+PT=14
1009
1010
1011
1012 = 4. Setting for Different Scenarios =
1013
1014
1015
1016 = 5. Upload Firmware =
1017
1018 == 5.1 Firmware Change Log ==
1019
1020
1021 **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1022
1023
1024 == 5.2 How to upgrade firmware ==
1025
1026
1027 User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
1028
1029
1030 (% style="color:blue" %)**Step1:  **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
1031
1032
1033 (% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC.
1034
1035 After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
1036
1037
1038 (% 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]]
1039
1040
1041 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1042
1043
1044 [[image:1664503563660-578.png||_mstalt="296777"]]
1045
1046
1047 [[image:1664503574618-659.png||_mstalt="297986"]]
1048
1049
1050
1051 (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
1052
1053 [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1054
1055
1056 **Users need to use below files:**
1057
1058 boot_app0.bin @0e000
1059
1060 US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1061
1062
1063 [[image:image-20221118105220-2.png||_mstalt="426608"]]
1064
1065
1066
1067 After upgrade finish, it will show finish as below:
1068
1069 [[image:image-20221118105402-4.png||_mstalt="427986"]]
1070
1071
1072
1073 = 6. Developer Guide =
1074
1075 == 6.1 Compile Source Code ==
1076
1077 === 6.1.1 Set up ARDUINO compile environment ===
1078
1079
1080 * **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]]**
1081
1082 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]]
1083
1084
1085 [[image:1664503635019-941.png||_mstalt="294658"]]
1086
1087
1088
1089 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1090
1091 [[image:1664503715811-892.png||_mstalt="295698"]]
1092
1093
1094 (% 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.
1095
1096 [[image:image-20221024105643-1.png||_mstalt="428129"]]
1097
1098 **~ Figure1**
1099
1100
1101 [[image:image-20221024105643-2.png||_mstalt="428493"]]
1102
1103 **Figure2**
1104
1105
1106 * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1107
1108 Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1109
1110
1111 [[image:1664503752288-974.png||_mstalt="298194"]]
1112
1113
1114 == 6.2 Source Code ==
1115
1116
1117 * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1118
1119 [[image:1664503794261-827.png||_mstalt="296387"]]
1120
1121
1122
1123 * (% style="color:blue" %)**Click to upload**
1124
1125 [[image:1664503808294-336.png||_mstalt="295711"]]
1126
1127
1128
1129 * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1130
1131 [[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1132
1133
1134 = 7.  FAQ =
1135
1136 == 7.1 How to change the LoRa Frequency Bands/Region? ==
1137
1138
1139 User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1140
1141
1142 == 7.2 What is the pin mapping for the USB program cable? ==
1143
1144
1145 [[image:1664499635206-262.png||_mstalt="295360"]]
1146
1147
1148
1149 (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
1150 |=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
1151 |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1152 |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1153 |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
1154 |(% style="width:118px" %)A1,B1,A12,B12|(% style="width:67px" %)Black|(% style="width:123px" %)GND
1155 |(% style="width:118px" %)A5|(% style="width:67px" %)Purple|(% style="width:123px" %)MTDC/GOIO13
1156 |(% style="width:118px" %)B5|(% style="width:67px" %)Blue|(% style="width:123px" %)MTDC/GPIO12
1157 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1158 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1159
1160
1161 == 7.3 Notes on using different serial port tools for TrackerD ==
1162
1163 === 7.3.1  Serial port utility ===
1164
1165
1166 Serial port utility requires you to automatically add data streams.
1167
1168 Need to adjust the data stream to RTS/CTS on physical restart.
1169
1170 (% class="wikigeneratedid" %)
1171 [[image:image-20221102140621-1.png||_mstalt="425672"]]
1172
1173
1174
1175 When using AT commands, the data flow needs to be adjusted to XON/XOFF
1176
1177 [[image:image-20221102140638-2.png||_mstalt="428727"]]
1178
1179
1180 === 7.3.2  SecureCRT ===
1181
1182
1183 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.
1184
1185
1186 [[image:image-20221102140704-3.png||_mstalt="427076"]]
1187
1188
1189 [[image:image-20221102140712-4.png||_mstalt="427089"]]
1190
1191
1192 === 7.3.3  PUTTY ===
1193
1194
1195 [[image:image-20221102140748-5.png||_mstalt="430456"]]
1196
1197
1198 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.
1199
1200
1201 [[image:image-20221102140801-6.png||_mstalt="427466"]]
1202
1203
1204 == 7.4 How to modify source code to compile different frequency band bin file? ==
1205
1206
1207 (% class="box infomessage" %)
1208 (((
1209 (% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1210 See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1211 )))
1212
1213 **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1214
1215
1216 [[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1217
1218
1219
1220 **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1221
1222
1223 [[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1224
1225
1226
1227 **3. Compile the AS923_JP band, please refer to the intention shown**
1228
1229
1230 [[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1231
1232
1233
1234 **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.**
1235
1236
1237 [[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1238
1239
1240 [[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1241
1242
1243 = 8  Trouble Shooting =
1244
1245 == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1246
1247
1248 (((
1249 Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1250 )))
1251
1252
1253 == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1254
1255
1256 (((
1257 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.
1258 )))
1259
1260
1261 == 8.3  Problem after Upgrading Firmware ==
1262
1263 === 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1264
1265 Error Output
1266
1267 [[image:image-20221122100004-4.png||_mstalt="424606"]]
1268
1269 (((
1270 Some partition is missed during upgrade, please upgrade below four files as example:
1271
1272 [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1273 )))
1274
1275
1276 === 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1277
1278
1279 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
1280
1281
1282 === 8.3.3 "flash read err" after upgrade firmware ===
1283
1284 Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1285
1286 [[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1287
1288
1289 User need to upgrade again with below four files to solve this issue.
1290
1291 [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1292
1293 **Figure 2**
1294
1295
1296 === 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1297
1298 User might erase the entire flash include keys and default settings which cause this issue.
1299
1300 After the upgrade is completed, enter AT+CFG as shown in the figure below.
1301
1302 [[image:image-20221122100004-3.png||_mstalt="424242"]]
1303
1304 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.
1305
1306 After AT+FDR. please set
1307
1308 * AT+PDOP=7
1309
1310 * AT+FTIME=180000
1311
1312 Example:
1313
1314 AT+PDOP=7.00
1315
1316 AT+FTIME=180
1317
1318 AT+DEUI=70B3D57ED0053981  
1319
1320 AT+APPEUI=D23345667BCBCCAF
1321
1322 AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1323
1324 AT+DADDR=260b4dce    ( no need for OTAA)
1325
1326 AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1327
1328 AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1329
1330
1331 == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1332
1333
1334 Please download version 1.4.2 again
1335
1336
1337 == 8.5  How to deal with unsuccessful GPS positioning? ==
1338
1339
1340 1) Make Sure the device is in Open Area where can see the sky.
1341
1342 2)  Set PDOP to a higher value.
1343
1344 * (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.)
1345
1346 * (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces)
1347
1348 * (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments)
1349
1350 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
1351
1352
1353 = 9.  Order Info =
1354
1355
1356 Part Number: (% style="color:blue" %)**TrackerD-XXX**
1357
1358 (% style="color:blue" %)**XXX**(%%): The default frequency band
1359
1360 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1361
1362 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1363
1364 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1365
1366 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1367
1368 * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1369
1370 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1371
1372 * (% style="color:red" %)**US915**(%%): Default frequency band US915
1373
1374
1375
1376
1377 = 10.  Packing Info =
1378
1379
1380 (% style="color:#037691" %)**Package Includes**:
1381
1382 * TrackerD LoRaWAN GPS/BLE Tracker x 1
1383
1384 * USB recharge & program cable x 1
1385
1386 (% style="color:#037691" %)**Dimensions and Weight**:
1387
1388 * Device Size: 85 x 48 x 15 mm
1389
1390 * Weight: 50g
1391
1392
1393
1394
1395 = 11. Support =
1396
1397
1398 * 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.
1399
1400 * 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]].
1401
1402
1403
1404
1405 = 12.  Reference =
1406
1407
1408 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1409
1410 * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1411
1412 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]