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