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