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

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0