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

Applications

Navigation

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