Skip to Content
Version 241.1 by Xiaoling on 2025/02/07 14:55
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: -15℃ ~~ 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 (% style="display:none" %)
97
98
99
100 == 1.3  Features ==
101
102
103 * LoRaWAN 1.0.3 Class A
104 * ESP32 PICO D4
105 * SX1276/78 Wireless Chip
106 * Arduino IDE Compatible
107 * Open source hardware / software
108 * Regular/ Real-time GPS,BLE,WIFI tracking
109 * Built-in3 axis accelerometer (LIS3DH)
110 * Humidity / temperature sensor : GXCAS Technology GXHT3X
111 * Motion sensing capability
112 * Power Monitoring
113 * Charging circuit via USB port
114 * 1000mA Li-on Battery power
115 * Tri-color LED, Alarm button
116 * Datalog
117
118 (% style="display:none" %)
119
120
121
122 == 1.4  Applications ==
123
124
125 * Logistics and Supply Chain Management
126 * Human tracking
127
128 (% style="display:none" %)
129
130
131
132 = 2.  Use TrackerD =
133
134 == 2.1 How it works? ==
135
136
137 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.
138
139
140 == 2.2 Quick guide to connect to LoRaWAN server ==
141
142
143 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. 
144
145
146 [[image:image-20230213110214-2.png||height="388" width="847"]]
147
148
149 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:
150
151
152 (% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
153
154 Each TrackerD is shipped with a sticker with the default device EUI as below:
155
156
157 [[image:image-20230426085815-1.png||height="259" width="558"]]
158
159
160 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
161
162
163 **__Add APP EUI in the application:__**
164
165 [[image:1664501711466-918.png||_mstalt="295828"]]
166
167
168 [[image:1664501721248-725.png||_mstalt="294450"]]
169
170
171 [[image:1664501734705-405.png||_mstalt="293306"]]
172
173
174 **__Add APP KEY and DEV EUI:__**
175
176
177 [[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"]]
178
179
180 (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
181
182 (% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
183
184 [[image:1664502835802-546.png||_mstalt="295061"]]
185
186
187 (% 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.
188
189
190 == 2.3  Positioning Mode(SMOD) ==
191
192
193 Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
194
195 * (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
196 * (% 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.
197 * (% 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.
198
199 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
200
201
202 == 2.4  Uplink Payload ==
203
204 === 2.4.1 Uplink FPORT~=5, Device Status ===
205
206
207 Uplink the device configures with (% style="color:blue" %)**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.
208
209 Use can also get the Device Status uplink through the downlink command: (% style="color:#037691" %)**Downlink:  0x2301**
210
211 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:440px" %)
212 |(% style="background-color:#4f81bd; color:white; width:63px" %)**Size(bytes)**|=(% style="width: 72px;background-color:#4F81BD;color:white" %)1|=(% style="width: 72px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 70px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 50px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 31px;background-color:#4F81BD;color:white" %)2|=(% style="width: 41px;background-color:#4F81BD;color:white" %)1|=(% style="width: 41px;background-color:#4F81BD;color:white" %)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 (% style="color:#037691" %)**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 (% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
251
252 Use can also get the Device Status uplink through the downlink command:
253
254
255 (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
256
257 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:270px" %)
258 |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bit)**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1 bit**|(% style="background-color:#4f81bd; color:white; width:80px" %)**2 bits**|(% style="background-color:#4f81bd; color:white; width:80px" %)**4 bits**
259 |(% style="width:75px" %)Value|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
260
261 (% style="color:blue" %)**SMOD：**
262
263 (% style="color:red" %)**1 :** (%%) GPS ONLY
264
265 (% style="color:red" %)**2 :** (%%) BLE ONLY
266
267 (% style="color:red" %)**3 :**  (%%) GPS/BLE Hybrid
268
269
270 (% style="color:blue" %)**GPS_MOD: Define how to send GPS payload**
271
272 (% style="color:red" %)**0 : ** (%%) Enable uploading on-board Temperature and humidity values
273
274 (% style="color:red" %)**1 :** (%%) Disable uploading on-board Temperature and humidity values
275
276
277 (% style="color:blue" %)**BLE_Settings:**
278
279 (% style="color:red" %)**1: ** (%%) BLE Positioning with Strongest iBeacon
280
281 (% _mstmutation="1" style="color:red" %)**2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
282
283
284 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
285
286 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:413px" %)
287 |(% style="background-color:#4f81bd; color:white; width:77px" %)**Size(bit)**|(% style="background-color:#4f81bd; color:white; width:70px" %)**5 Bits**|(% style="background-color:#4f81bd; color:white; width:88px" %)**1 Bit**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1 Bit**|(% style="background-color:#4f81bd; color:white; width:128px" %)**1 Bit**
288 |(% 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"]]
289
290 (% style="display:none" %)
291
292
293 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
294
295
296 Users can use (% style="color:blue" %)**AT+SMOD=1,0,0**(%%) to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
297
298 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
299 |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:50px" %)**4**|(% style="background-color:#4f81bd; color:white; width:50px" %)**4**|(% style="background-color:#4f81bd; color:white; width:70px" %)**2**|(% style="background-color:#4f81bd; color:white; width:30px" %)**1**|(% style="background-color:#4f81bd; color:white; width:30px" %)**2**|(% style="background-color:#4f81bd; color:white; width:30px" %)**2**
300 |(% style="width:69px" %)Value|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
301 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
302 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
303
304 [[image:1665301636888-168.png||_mstalt="298012"]]
305
306
307 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
308
309 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:329px" %)
310 |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bit)**|(% style="background-color:#4f81bd; color:white; width:60px" %)**1 bit**|(% style="background-color:#4f81bd; color:white; width:134px" %)**1 bit**|(% style="background-color:#4f81bd; color:white; width:75px" %)**14 bits**
311 |(% style="width:72px" %)Value|(% style="width:67px" %)reserve|(% style="width:114px" %)Alarm Indicate|(% style="width:62px" %)[[BAT>>||anchor="HBAT:"]] 
312
313 (% style="display:none" %)
314
315
316 ==== (% style="color:blue" %)**FLAG:**(%%) ====
317
318 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:184px" %)
319 |(% style="background-color:#4f81bd; color:white; width:68px" %)**Size(bit)**|(% style="background-color:#4f81bd; color:white; width:61px" %)**2 bits**|(% style="background-color:#4f81bd; color:white; width:55px" %)**1 bit**
320 |(% style="width:79px" %)Value|(% style="width:56px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:50px" %)[[LON>>||anchor="HLON:"]]
321
322 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
323
324
325 ==== (% style="color:blue" %)**Location info:**(%%) ====
326
327 * Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
328 * Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
329
330 (% style="color:red" %)**Important note:**
331
332 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.
333
334 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:
335
336
337 [[image:1664502116362-706.png||_mstalt="293306"]]
338
339
340 3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
341
342 [[image:1664502166010-515.png||_mstalt="291395"]]
343
344
345 ==== (% style="color:blue" %)**Alarm:**(%%) ====
346
347 **Example: ** 0x4B & 0x40 >> 6 = 0x01
348
349
350 ==== (% style="color:blue" %)**BAT:**(%%) ====
351
352 **Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
353
354 (((
355 The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
356 )))
357
358 * > 4.0v :  80% ~~ 100%
359 * 3.85v ~~3.99v:  60% ~~ 80%
360 * 3.70v ~~ 3.84v:  40% ~~ 60%
361 * 3.40v ~~ 3.69v:  20% ~~ 40%
362 * < 3.39v:  0~~20%
363
364 (% style="display:none" %) (%%)
365
366 ==== (% style="color:blue" %)**MOD:**(%%) ====
367
368 **Example: ** (0x60>>6) & 0x3f =1
369
370 **Set the format of GPS data uplink link:**
371
372 (% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
373 (% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
374
375
376 **Set the format of BLE data uplink link：**
377
378 (% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
379
380
381 ==== (% style="color:blue" %)**LON:**(%%) ====
382
383 **Example:** (0x60>>5) & 0x01=1.
384
385 Enable/Disable LED activity for uplink
386
387 (((
388 (% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
389 )))
390
391 (((
392 (% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
393 )))
394
395
396 ==== (% style="color:blue" %)**Hum:**(%%) ====
397
398 0230   value = 0x0230  / 10 = 560 ⇒ 56%
399
400
401 ==== (% style="color:blue" %)**Tem:**(%%) ====
402
403 0202 = if (0x0202 & 0x8000 = 0 ):  value = 0x0202 / 100 = +514 ⇒ 5.14 degree
404
405 011A =if (0xF11A & 0x8000 = 1 ):  value =( 0xF11A - 0x10000)/100(dec) ⇒ -38.14 degree
406
407
408 === 2.4.3  Uplink FPORT~=3, Realti me GNSS Positioning (Default Mode) ===
409
410
411 The default uplink payload includes total 11 bytes ((% style="color:blue" %)**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)
412
413 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
414 |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:60px" %)**4**|(% style="background-color:#4f81bd; color:white; width:60px" %)**4**|(% style="background-color:#4f81bd; color:white; width:70px" %)**2**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1**
415 |(% style="width:69px" %)Value|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
416 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
417 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
418
419 (% class="wikigeneratedid" %)
420 [[image:1665301687277-443.png||_mstalt="296140"]]
421
422
423 === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
424
425
426 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.
427
428
429 (% style="color:red" %)**Note for this mode:**
430
431 * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
432 * 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.
433 * 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
434
435 The payload is 15 bytes, as below.
436
437 (% border="1" style="background-color:#f2f2f2; width:500px" %)
438 |(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**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 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
452 |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:30px" %)**16**|(% style="background-color:#4f81bd; color:white; width:50px" %)**2**|(% style="background-color:#4f81bd; color:white; width:50px" %)**2**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1**|(% style="background-color:#4f81bd; color:white; width:80px" %)**1**|(% style="background-color:#4f81bd; color:white; width:80px" %)**2**|(% style="background-color:#4f81bd; color:white; width:40px" %)**1**|(% style="background-color:#4f81bd; color:white; width:30px" %)**1**|(% style="background-color:#4f81bd; color:white; width:30px" %)**1**
453 |(% style="width:50px" %)Value|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
454 iBeacon MAJOR
455 )))|(% style="width:63px" %)(((
456 iBeacon MINOR
457 )))|(% style="width:71px" %)(((
458 senseless
459 )))|(% style="width:50px" %)RSSI of the device within 1m|(% style="width:50px" %)(((
460 iBeacon Measured Power
461 )))|(% style="width:50px" %)(((
462 iBeacon RSSI
463 )))|(% style="width:47px" %)(((
464 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
465 )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
466
467 [[image:1664502425687-834.png||_mstalt="296738"]]
468
469
470 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
471 * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
472 * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
473 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
474 * (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
475 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
476 * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
477 * (% style="color:#037691" %)**RSSI_1M:** (%%) RSSI of the device within 1m.
478
479 (% style="display:none" %) (%%)
480
481 === 2.4.6  Uplink FPORT~=7, Alarm information status (Since firmware 1.4.4) ===
482
483
484 The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
485
486 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:284px" %)
487 |(% style="background-color:#4f81bd; color:white; width:98px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:104px" %)**2**|(% style="background-color:#4f81bd; color:white; width:82px" %)**1**
488 |(% style="width:97px" %)Value|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon
489
490 [[image:image-20230302145315-1.png]]
491
492 **alarm**=(bytes[0] & 0x40)  ~/~/ Alarm status
493
494 **batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
495
496 **mod** = bytes[2] & 0xC0;
497
498 **Lon**=(bytes[2] & 0x20)
499
500
501 === 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID (Since firmware 1.4.1) ===
502
503
504 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.
505
506 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:348px" %)
507 |(% style="background-color:#4f81bd; color:white; width:65px" %)(((
508 **Size(bytes)**
509 )))|(% style="background-color:#4f81bd; color:white; width:50px" %)**6**|(% style="background-color:#4f81bd; color:white; width:50px" %)**4**|(% style="background-color:#4f81bd; color:white; width:133px" %)**2**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1**
510 |(% style="width:69px" %)Value|(% style="width:48px" %)SSID|(% style="width:48px" %)RSSI|(% style="width:103px" %)(((
511 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
512 )))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]
513
514 (% class="wikigeneratedid" %)
515 [[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
516
517 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
518 * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
519 * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
520
521 (% style="display:none" %) (%%)
522
523 === 2.4.8  Uplink FPORT~=9, BLE Positioning with Multiple iBeacon(Since firmware 1.4.7) ===
524
525
526 TrackerD supports BLE scanning for indoor positioning. Users can set SMOD to BLE pure or GPS/BLE Hybrid, so TrackerD will scan up to 40 BLE iBeacons and send uplinks.
527
528 User can set [[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**BLEMASK**>>path:#H3.2.11A0SetBLEMASKtofilterBLEiBeacon]](%%) so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
529
530 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:348px" %)
531 |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**...**
532 |Value|[[Alarm & BAT>>path:#HAlarm26BAT:]]|[[FLAG>>path:#HFLAG:]]|iBeacon MAJOR|iBeacon MINOR|iBeacon RSSI|iBeacon MAJOR|iBeacon MINOR|iBeacon RSSI|...
533
534 (% class="wikigeneratedid" id="H" %)
535 [[image:image-20240606162359-1.png||height="361" width="716"]]
536
537 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
538 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
539 * (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
540 * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
541 * (% style="color:#037691" %)**MOD:      **(%%)Bluetooth mode: 1: Search the beacon with the strongest signal. 2: Search the three beacons with the strongest signal. 3: Search all Bluetooth beacons (up to 40 Bluetooth beacons are displayed).
542
543 (% class="wikigeneratedid" %)
544 (% style="color:red" %)**Note: This mode does not have a fixed decoder. Its decoder depends on the number of beacons and can be parsed according to the order of the payload.**
545
546 payload format: BAT+State+(Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...
547
548
549 === 2.4.9  Add Payload format in TTN V3 ===
550
551
552 In TTN V3, user can add a custom payload so it shows friendly.
553
554 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
555
556 [[image:1664502649601-895.png||_mstalt="296985"]]
557
558
559 Add the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
560
561 Save the change the uplink message will be parsed. As below:
562
563 [[image:1664502676891-606.png||_mstalt="296673"]]
564
565
566 == 2.5 Integrate with Datacake ==
567
568
569 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.
570
571 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]]
572
573 [[image:1664502695771-538.png||_mstalt="297349"]]
574
575
576 == 2.6 Integrate with Tago ==
577
578
579 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.
580
581 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]]
582
583 [[image:1664502715371-321.png||_mstalt="292162"]]
584
585
586 == 2.7  Integrate with Node-red ==
587
588
589 ~1. Install node-red, please refer to the installation method in the link:
590
591 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
592
593
594 2. Import the created flow template, please refer to the import method in the link:
595
596 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
597
598
599 The address of the flow template: [[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]]
600
601 (% 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.**
602
603 [[image:image-20230307135914-1.png||height="527" width="1045"]]
604
605
606 [[image:image-20230307135932-2.png||height="527" width="1044"]]
607
608
609 3. Display the map
610 Enter the link to the map:
611
612 Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
613
614 **~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
615
616
617 Hit all input in input stream
618
619 [[image:image-20230308115616-2.png||height="563" width="1070"]]
620
621
622 View map again
623
624 [[image:image-20230308115701-3.png||height="571" width="1085"]]
625
626
627 == 2.8  Datalog Feature ==
628
629
630 total 273 entries,by default,
631
632 User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
633
634 Example use case.
635
636 [[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
637
638
639 [[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
640
641
642 == 2.9  Alarm Mode ==
643
644
645 (((
646 User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. Alarm Mode is used to send SOS info to IoT platform.
647 )))
648
649 (((
650 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.
651 )))
652
653
654 (((
655 **Two ways to exit alarm mode:**
656 )))
657
658 * Server sends a downlink command to exit.
659 * User fast press the RED button 10 times.
660
661 (((
662 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.
663 )))
664
665
666 == 2.10  Transport Mode ==
667
668
669 In Transport Mode, TrackerD will check if there is motion (threldhold defined by **[[PT)>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** . If there is no motion, device will send uplinks every 20 minutes (Defined by **[[TDC)>>||anchor="H3.2.1SetTransmitInterval"]]** . If there is motion, device will send uplink every 5 minutes(defined by **[[MTDC)>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]**.
670
671 When device is set in Transport Mode, it will uplink more frequenctly during moving.
672
673 * **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
674 * **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
675 * **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
676
677 (% style="display:none" %) (%%)
678
679 == 2.11  LED Status ==
680
681
682 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %)
683 |=(% style="width: 150px;background-color:#4F81BD;color:white" %)**Event**|=(% style="width: 200px;background-color:#4F81BD;color:white" %)**Action**|=(% style="width: 150px;background-color:#4F81BD;color:white" %)**AT+LON to control on/off**
684 |(% 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
685 |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
686 |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
687 |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
688 |(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
689 |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
690 |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
691 |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
692 |(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes
693 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
694 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
695
696 (% style="display:none" %) (%%)
697
698 == 2.12  Button Function ==
699
700
701 (% style="color:blue" %)**RESET button:**
702
703 [[image:1664502835802-546.png||_mstalt="295061"]]
704
705 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
706
707
708 (% style="color:red" %)**RED button:**
709
710 [[image:image-20230213110506-3.png]](% style="display:none" %)
711
712 (% style="display:none" %) (%%)
713
714 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
715 |=(% style="width: 100px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 205px;background-color:#4F81BD;color:white" %)**Action**|=(% style="width: 205px;background-color:#4F81BD;color:white" %)**Description**
716 |(% 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"]]
717 |(% 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
718 |(% 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.
719
720 (% style="display:none" %) (%%)
721
722 == 2.13  USB Port Function ==
723
724
725 The USB interface of TrackerD has below functions:
726
727 * Power on the device
728 * Recharge the battery
729 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
730 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
731
732 (% style="display:none" %) (%%)
733
734 == 2.14  Sleep Mode ==
735
736
737 (% style="color:blue" %)**Sleep Mode:**(%%) To prevent accidental touch of the red button during transportation or assembly, so the peripherals of the device are turned off and enter deep sleep.
738
739 In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
740
741 Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
742
743
744 = 3. Configure TrackerD via AT command or LoRaWAN downlink =
745
746
747 User can configure TrackerD via AT Command or LoRaWAN Downlink.
748
749 LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
750
751
752 == 3.1 Access AT Command ==
753
754
755 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.
756
757 [[image:1664502999401-486.png||_mstalt="296985"]]
758
759
760 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:
761
762
763 [[image:1664503022490-662.png||_mstalt="293332"]]
764
765
766 [[image:1664503035713-500.png||_mstalt="291096"]]
767
768
769 [[image:1664503047675-651.png||_mstalt="295386"]]
770
771 (% style="display:none" %) (%%)
772
773 == 3.2 Command Set ==
774
775 === 3.2.1 Set Transmit Interval ===
776
777
778 Set device uplink interval.
779
780 * (% style="color:blue" %)**AT Command:**
781
782 (% style="color:#037691" %)**AT+TDC=xxx **
783
784 Example:  AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
785
786
787 * (% style="color:blue" %)**Downlink Payload (prefix 0x01):**
788
789 (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
790
791
792 === 3.2.2 Set Alarm Packet transmission interval ===
793
794
795 Set alarm packet transmit interval
796
797 * (% style="color:blue" %)**AT Command:**
798
799 (% style="color:#037691" %)**AT+ATDC=xx. **
800
801 Example:  AT+ATDC=60000  **~-~->    ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
802
803
804 * (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**
805
806 (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
807
808
809 === 3.2.3 Set Transport Mode Packet transmission interval ===
810
811
812 Set Transport Mode packet transmit interval
813
814 * (% style="color:blue" %)**AT Command:**
815
816 (% style="color:#037691" %)**AT+MTDC=xx. **
817
818 Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
819
820
821 * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
822
823 (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=300000
824
825
826 === 3.2.4 Exit Alarm ===
827
828
829 Server send downlink command to exit Alarm mode
830
831 * (% style="color:blue" %)**AT Command: No AT Command**
832
833 * (% style="color:blue" %)**Downlink Payload (prefix 0x02):**
834
835 (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
836
837
838 === 3.2.5 Disable/Enable LED flash and buzzer ===
839
840
841 Disable/Enable LED for position, downlink and uplink
842
843 * (% style="color:blue" %)**AT Command:**
844
845 (% style="color:#037691" %)**AT+LON=xx.  (Disable (0), Enable (1), default:1)**
846
847 Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
848
849
850 * (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**
851
852 (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
853
854
855 === 3.2.6 Disable/Enable Transport Mode ===
856
857
858 Users can use this feature to enable/disable Transport Mode.
859
860 * (% style="color:blue" %)**AT Command:**
861
862 (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
863
864 Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
865
866
867 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
868
869 (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
870
871
872 === 3.2.7 Set Positioning Mode ===
873
874
875 SMOD define how TrackerD scan and uplink data:
876
877 * (% style="color:blue" %)**AT Command:**
878
879 (% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
880
881 (% style="color:#037691" %)** aa:**
882
883 * (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
884
885 * (% 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.
886
887 * (% 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.
888
889 (% style="color:#037691" %)**bb:**
890
891 * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
892
893 * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
894
895 (% style="color:#037691" %)**cc:   **
896
897 * (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
898
899 * (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
900
901 (% style="color:blue" %)**Example:**
902
903 AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
904
905 AT+SMOD=1,1,0 ~-~->  GPS +BAT State
906
907 AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
908
909 AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
910
911 AT+SMOD=2,0,3  ~-~->  (iBeacon) (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State
912
913 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
914
915 (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
916
917
918 === 3.2.8 Set MAX GPS position time ===
919
920
921 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.
922
923 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.
924
925 * (% style="color:blue" %)**AT Command:**
926
927 (% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
928
929 **Example:**  AT+FTIME=150
930
931
932 * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
933
934 (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
935
936
937 === 3.2.9 Set PDOP value for GPS fix accuracy ===
938
939
940 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.
941
942 A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
943
944 * (% style="color:blue" %)**AT Command:**
945
946 (% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
947
948
949 * (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**
950
951 (% style="color:#037691" %)**0xAD 00 0A**   (%%) ~/~/  Set AT+PDOP=1  (0x0A / 10 =1)
952
953 (% style="color:#037691" %)**0xAD 00 19**   (%%) ~/~/  Set AT+PDOP=2.5    (0x19 / 10 =2.5)
954
955 (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
956
957
958 === 3.2.10 Disable/Enable the confirmation mode ===
959
960
961 * (% style="color:blue" %)**AT Command:**
962
963 (% style="color:#037691" %)**AT+CFM=xx**
964
965
966 **Example:**
967
968 AT+CFM=0    **~-~->   ** Disable confirmation
969
970 AT+CFM=1    **~-~->  ** Enable confirmation
971
972
973 * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
974
975 (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
976
977
978 === 3.2.11  Auto Send None-ACK messages ===
979
980
981 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.
982
983
984 * (% style="color:blue" %)**AT Command: AT+PNACKMD**
985
986 The default factory setting is 0.
987
988
989 **Command Example Function Response:**
990
991 (% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
992
993
994 * (% style="color:blue" %)**Downlink Command: 0x34**
995
996 Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
997
998
999 === 3.2.12  Set BLEMASK to filter BLE iBeacon ===
1000
1001
1002 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.
1003
1004 (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
1005
1006 (% style="color:blue" %)**AT Command:**
1007
1008 (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
1009
1010 (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
1011
1012 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)**
1013
1014 Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
1015
1016
1017 === 3.2.13  Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===
1018
1019
1020 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.
1021
1022 (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
1023
1024 (% style="color:blue" %)**AT Command:**
1025
1026 (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1027
1028 (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1029
1030 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)**
1031
1032 Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
1033
1034
1035 === 3.2.14  Disable/Enable Information printing(Since firmware 1.4.1) ===
1036
1037
1038 Users can use this feature to enable/disable Information printing.
1039
1040 (% style="color:blue" %)**AT Command:**
1041
1042 (% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
1043 \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1044
1045
1046 === 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===
1047
1048
1049 The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
1050
1051 (% style="color:blue" %)**AT Command:**
1052
1053 (% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
1054
1055
1056 (% style="color:blue" %)**Downlink Payload:0X24**
1057
1058 Example: 0x24 01  ~/~/ Same as AT+CHE=1
1059
1060
1061 === 3.2.16  Get or Set Threshold for motion detect(Since firmware 1.4.3) ===
1062
1063
1064 User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1065
1066 (% style="color:blue" %)**AT Command:**
1067
1068 (% style="color:#037691" %)**AT+PT=xx**
1069
1070 Example:
1071
1072 AT+PT=14    ~-~->    Set to detect car motion.
1073
1074 AT+PT=41  ~-~->    set to detect walk motion.
1075
1076
1077 (% style="color:blue" %)**Downlink Payload:0xB4**
1078
1079 0xB4 14          ~/~/  Same as AT+PT=14
1080
1081
1082 === 3.2.17  Set AT command window time(Since firmware 1.4.5) ===
1083
1084
1085 AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
1086
1087 (% style="color:blue" %)**AT Command:**
1088
1089 (% style="color:#037691" %)**AT+ATST=XX**
1090
1091 Example:
1092
1093 AT+ATST=15    ~-~-> Set the time to 15 seconds
1094
1095 (% style="color:blue" %)**Downlink Payload:0XB5**
1096
1097 0xB5 0F          ~/~/  Same as AT+ATST=15
1098
1099
1100 === 3.2.18  Set the stepmeter mode(Since firmware 1.4.5) ===
1101
1102
1103 After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
1104
1105 (% style="color:blue" %)**AT Command:**
1106
1107 (% style="color:#037691" %)**AT+PM=xx**
1108
1109 Example:
1110
1111 AT+PM=1    ~-~->  Turn on step counting mode
1112
1113 AT+PM=0    ~-~->  Turn OFF step counting mode
1114
1115 (% style="color:blue" %)**Downlink Payload:0XB6**
1116
1117 0xB6 01          ~/~/  Same as AT+PM=1
1118
1119
1120 === 3.2.19  Set down the decline detection mode(Since firmware 1.4.5) ===
1121
1122
1123 This mode is used in conjunction with AT+PT(The recommended threshold is between 50 and 70, you need to set it according to the environment yourself). This function is used in hospitals, nursing homes, nursing homes and other places to prevent the elderly and patients from falling. No one knows.
1124
1125 (% style="color:blue" %)**AT Command:**
1126
1127 (% style="color:#037691" %)**AT+FD=xx**
1128
1129 **Example:**
1130
1131 AT+FD=1    ~-~->  Turn on the Fall detection
1132
1133 AT+FD=0    ~-~->  Turn OFF the Fall detection
1134
1135 (% style="color:blue" %)**Downlink Payload:0XB7**
1136
1137 0xB7 01          ~/~/  Same as AT+FD=1
1138
1139
1140 === 3.2.20 Disable/Enable buzzer(Since firmware 1.4.6) ===
1141
1142
1143 Disable/Enable buzzer for Alarm, downlink and uplink
1144
1145 (% style="color:blue" %)**AT Command:**
1146
1147 (% style="color:#037691" %)**AT+BEEP=XX**
1148
1149 Example:
1150
1151 AT+BEEP=1 ~-~-> Turn on the buzzer
1152
1153 AT+BEEP=0 ~-~-> Turn OFF the buzzer
1154
1155 (% style="color:blue" %)**Downlink Payload:0XB9**
1156
1157 0xB9 01 ~/~/ Same as AT+BEEP=1
1158
1159
1160 === (% data-sider-select-id="358d0797-d8c7-4a5d-b51f-fd0c537f26e4" %)3.2.21 Set long press time(Since firmware 1.4.6)(%%) ===
1161
1162
1163 When using the red button Changan to alarm, press and hold the time to set 0~~10 seconds(The default value is 5 seconds), which is convenient for use scenarios.
1164
1165 (% data-sider-select-id="5e6cc597-e839-4a16-9d6b-776f523bcb8c" style="color:blue" %)**AT Command:**
1166
1167 (% style="color:#037691" %)**AT+EAT=XX**
1168
1169 Example:
1170
1171 AT+EAT=2 ~-~-> Set the long press time to 2s
1172
1173 (% style="color:blue" %)**Downlink Payload: 0XBA**
1174
1175 0xBA 02 ~/~/ Same as AT+EAT=2
1176
1177
1178
1179 === 3.2.22 Set the Bluetooth scan time(Since firmware 1.5.1) ===
1180
1181
1182 Use this command to set the Bluetooth scan time. Default is 5s, value range: 1~~255.
1183
1184 (% data-sider-select-id="5e6cc597-e839-4a16-9d6b-776f523bcb8c" style="color:blue" %)**AT Command:**
1185
1186 (% style="color:#037691" %)**AT+BTDC=XX**
1187
1188 Example:
1189
1190 AT+BTDC=5 ~-~-> Set the Bluetooth scan time to 5s
1191
1192 (% style="color:blue" %)**Downlink Payload:**
1193
1194 No downlink
1195
1196
1197 (% data-sider-select-id="8e1bc417-f7f8-49f0-b796-8460ff412d7c" %)
1198 === 3.2.23 Conversion of TrackerD and TrackerD-LS(Since firmware 1.4.9) ===
1199
1200
1201 They use the same source code and can be converted using the AT command below
1202
1203 (% data-sider-select-id="5e6cc597-e839-4a16-9d6b-776f523bcb8c" style="color:blue" %)**AT Command:**
1204
1205 (% data-sider-select-id="d1642275-40f9-4a61-876f-c50aa2a2c492" style="color:#037691" %)**AT+DEVICE=22**
1206
1207 Example:
1208
1209 (% data-sider-select-id="80b524e6-34b5-469c-b05f-c144bee41d20" %)
1210 AT+DEVICE=22  ~-~-> Set  to TrackerD-LS
1211
1212 (% data-sider-select-id="d7427d7e-0c50-4af5-a666-fd59d105d39f" %)
1213 AT+DEVICE=13  ~-~-> Set  to TrackerD
1214
1215
1216 = (% data-sider-select-id="45c47ab9-03ef-4224-9771-e53c0d98eb40" %)4. Setting for Different Scenarios(%%) =
1217
1218
1219
1220 = 5. Upload Firmware =
1221
1222 == 5.1 Firmware Change Log ==
1223
1224
1225 **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1226
1227
1228 == 5.2 How to upgrade firmware ==
1229
1230
1231 User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
1232
1233
1234 (% style="color:blue" %)**Step1:  **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
1235
1236
1237 (% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC.
1238
1239 After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
1240
1241
1242 (% style="color:blue" %)**Step3:  **(%%)Download and Install Flash Tool:  [[Tools ~| Espressif Systems>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=]]
1243
1244
1245 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1246
1247
1248 [[image:1664503563660-578.png||_mstalt="296777"]]
1249
1250
1251 [[image:1664503574618-659.png||_mstalt="297986"]]
1252
1253
1254
1255 (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
1256
1257 [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1258
1259
1260 **Users need to use below files:**
1261
1262 boot_app0.bin @0e000
1263
1264 US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1265
1266
1267 [[image:image-20221207120501-1.png]]
1268
1269
1270
1271 After upgrade finish, it will show finish as below:
1272
1273 [[image:image-20221207133911-7.png]]
1274
1275
1276 = 6. Developer Guide =
1277
1278 == 6.1 Compile Source Code ==
1279
1280 === 6.1.1 Set up ARDUINO compile environment ===
1281
1282
1283 * **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]]**
1284
1285 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]]
1286
1287
1288 [[image:1664503635019-941.png||_mstalt="294658"]]
1289
1290
1291
1292 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1293
1294 [[image:1664503715811-892.png||_mstalt="295698"]]
1295
1296
1297 === 6.1.2  Build the development environment ===
1298
1299
1300 **~1. Download and install arduino IDE**
1301
1302 [[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]]
1303
1304
1305 **2. Download the ESP32 development package in the arduino IDE**
1306
1307 [[image:image-20221213100007-1.png]]
1308
1309
1310 Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1311
1312 [[image:image-20221213100626-2.png]]
1313
1314
1315 Restart the IDE after the addition is complete, then:
1316
1317 [[image:image-20221213100808-3.png||height="679" width="649"]]
1318
1319
1320 [[image:image-20221213101040-4.png]]
1321
1322
1323 (% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1324 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)**
1325
1326
1327 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:
1328
1329 (% style="color:blue" %)**Methods as below:**
1330
1331 ~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1332
1333 2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1334
1335 (% 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.
1336
1337 [[image:image-20221213102311-5.png||height="582" width="711"]]
1338
1339
1340 **3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1341
1342 [[image:image-20221213102334-6.png]]
1343
1344 (% style="color:red" %)**Note: This step requires a python environment**
1345
1346
1347 Either way, in the end:
1348
1349 The final effect is to open the arduino and you can see the esp32
1350
1351 [[image:image-20221213110952-8.png||height="866" width="711"]]
1352
1353
1354
1355 [[image:image-20221024105643-1.png||_mstalt="428129"]]
1356
1357 **~ Figure1**
1358
1359
1360
1361 [[image:image-20221024105643-2.png||_mstalt="428493"]]
1362
1363 **Figure2**
1364
1365
1366 * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1367
1368 Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1369
1370
1371 [[image:1664503752288-974.png||_mstalt="298194"]]
1372
1373
1374 == 6.2 Source Code ==
1375
1376
1377 * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1378
1379 [[image:1664503794261-827.png||_mstalt="296387"]]
1380
1381
1382
1383 * (% style="color:blue" %)**Click to upload**
1384
1385 [[image:1664503808294-336.png||_mstalt="295711"]]
1386
1387
1388
1389 * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1390
1391 [[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1392
1393
1394 = 7.  FAQ =
1395
1396 == 7.1 How to change the LoRa Frequency Bands/Region? ==
1397
1398
1399 User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1400
1401
1402 == 7.2 What is the pin mapping for the USB program cable? ==
1403
1404
1405 [[image:1664499635206-262.png||_mstalt="295360"]]
1406
1407
1408 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:314px" %)
1409 |=(% style="width: 120px;background-color:#4F81BD;color:white" %)**Pin**|=(% style="width: 69px;background-color:#4F81BD;color:white" %)**Color**|=(% style="width: 125px;background-color:#4F81BD;color:white" %)**USB Pin**
1410 |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1411 |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1412 |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
1413 |(% style="width:118px" %)A1,B1,A12,B12|(% style="width:67px" %)Black|(% style="width:123px" %)GND
1414 |(% style="width:118px" %)A5|(% style="width:67px" %)Purple|(% style="width:123px" %)MTDC/GOIO13
1415 |(% style="width:118px" %)B5|(% style="width:67px" %)Blue|(% style="width:123px" %)MTDC/GPIO12
1416 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1417 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1418
1419 (% style="display:none" %) (%%)
1420
1421
1422 == 7.3 Notes on using different serial port tools for TrackerD ==
1423
1424 === 7.3.1  Serial port utility ===
1425
1426
1427 Serial port utility requires you to automatically add data streams.
1428
1429 Need to adjust the data stream to RTS/CTS on physical restart.
1430
1431 (% class="wikigeneratedid" %)
1432 [[image:image-20221102140621-1.png||_mstalt="425672"]]
1433
1434
1435 When using AT commands, the data flow needs to be adjusted to XON/XOFF
1436
1437 [[image:image-20221102140638-2.png||_mstalt="428727"]]
1438
1439
1440 === 7.3.2  SecureCRT ===
1441
1442
1443 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.
1444
1445
1446 [[image:image-20221102140704-3.png||_mstalt="427076"]]
1447
1448
1449 [[image:image-20221102140712-4.png||_mstalt="427089"]]
1450
1451
1452 === 7.3.3  PUTTY ===
1453
1454
1455 [[image:image-20221102140748-5.png||_mstalt="430456"]]
1456
1457
1458 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.
1459
1460
1461 [[image:image-20221102140801-6.png||_mstalt="427466"]]
1462
1463
1464 == 7.4 How to modify source code to compile different frequency band bin file? ==
1465
1466
1467 (% class="box infomessage" %)
1468 (((
1469 (% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1470 See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1471 )))
1472
1473 **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1474
1475
1476 [[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1477
1478
1479
1480 **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1481
1482
1483 [[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1484
1485
1486
1487 **3. Compile the AS923_JP band, please refer to the intention shown**
1488
1489
1490 [[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1491
1492
1493
1494 **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.**
1495
1496
1497 [[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1498
1499
1500 [[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1501
1502
1503 == 7.5 Are there example python example for BLE Indoor Positioning? ==
1504
1505
1506 [[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1507
1508
1509 == 7.6 Can alert mode and transport mode be used together? ==
1510
1511
1512 Yes, you can also press the panic button to sound the alarm if set to transport mode
1513
1514
1515 == 7.7 Can i get the datalog record from console? ==
1516
1517 Since firmware TrackerD-v1.4.9, User is able to get the datalog record from console as well.
1518
1519 [[image:image-20240329120308-1.png||height="537" width="525"]]
1520
1521
1522 == 7.8 FAQs for upgrading to version 1.4.9 or later ==
1523
1524 1.The device does not display version information or indicates low battery
1525
1526 Please set the device type
1527
1528 (% style="color:red" %)**AT+DEVICE=13~-~->TrackerD
1529 AT+DEVICE=22->TrackerD-LS**
1530
1531
1532 2.Unable to control the red button on trackerD
1533
1534 Please set any 8-digit DADDR less than** 01880788**.
1535
1536 (% style="color:red" %)**Example:**
1537
1538 (% style="color:red" %)**AT+DADDR=01880688**
1539
1540
1541 = 8  Trouble Shooting =
1542
1543 == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1544
1545
1546 (((
1547 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
1548 )))
1549
1550
1551 == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1552
1553
1554 (((
1555 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.
1556 )))
1557
1558
1559 == 8.3  Problem after Upgrading Firmware ==
1560
1561 === 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1562
1563
1564 **Error Output**
1565
1566
1567 [[image:image-20221122100004-4.png||_mstalt="424606"]]
1568
1569
1570 (((
1571 Some partition is missed during upgrade, please upgrade below four files as example:
1572
1573 [[image:image-20221207120524-2.png]]
1574 )))
1575
1576
1577 === 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1578
1579
1580 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
1581
1582
1583 === 8.3.3 "flash read err" after upgrade firmware ===
1584
1585
1586 Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1587
1588 [[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1589
1590
1591 User need to upgrade again with below four files to solve this issue.
1592
1593 [[image:image-20221207120530-3.png]]
1594
1595 **Figure 2**
1596
1597
1598 === 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1599
1600
1601 User might erase the entire flash include keys and default settings which cause this issue.
1602
1603 After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below.
1604
1605
1606 [[image:image-20221122100004-3.png||_mstalt="424242"]]
1607
1608
1609 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.
1610
1611 After AT+FDR. please set
1612
1613 * (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1614
1615 * (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1616
1617 **Example:**
1618
1619 AT+PDOP=7.00
1620
1621 AT+FTIME=180
1622
1623 AT+DEUI=70B3D57ED0053981  
1624
1625 AT+APPEUI=D23345667BCBCCAF
1626
1627 AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1628
1629 AT+DADDR=260b4dce    ( no need for OTAA)
1630
1631 AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1632
1633 AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1634
1635
1636 == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1637
1638
1639 Please download version 1.4.2 again
1640
1641
1642 == 8.5  How to deal with unsuccessful GPS positioning? ==
1643
1644
1645 1） Make Sure the device is in Open Area where can see the sky.
1646
1647 2)  Set PDOP to a higher value.
1648
1649 * (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1650
1651 * (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1652
1653 * (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1654
1655 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
1656
1657
1658 == 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1659
1660
1661 When upgrading, use the erase button to upgrade
1662
1663 [[image:image-20221207120536-4.png]]
1664
1665
1666 The parameters are displayed abnormally and cannot be fixed using AT+FDR
1667
1668 [[image:image-20221128103040-2.png||height="431" width="525"]]
1669
1670
1671 Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1672
1673 [[image:image-20221207134028-8.png]]
1674
1675
1676 Reboot information after upgrade
1677
1678 [[image:image-20221128111443-4.png||height="432" width="546"]]
1679
1680
1681 Use (% style="color:blue" %)**AT+FDR**(%%) command to reset and then use (% style="color:blue" %)**AT+CFG**(%%) to check whether the configuration is back to normal
1682
1683 [[image:image-20221128111850-5.png]]
1684
1685
1686 After the parameters return to normal, upgrade to the version you need again
1687
1688 [[image:image-20221207120601-5.png]]
1689
1690
1691 At this point, the parameters return to normal after running AT+FDR again
1692
1693 [[image:image-20221128112035-7.png]]
1694
1695
1696 == 8.7  If you encounter the following problems, please upgrade to the latest version ==
1697
1698
1699 ~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1700
1701 2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1702
1703
1704 == 8.8  Why when using some serial consoles, only inputting the first string port console will return "error"? ==
1705
1706
1707 Need to enter the entire command at once, not a single character.
1708 User can open a command window or copy the entire command to the serial console.
1709
1710
1711 == 8.9  When the device is connected to the serial port, it cannot send Uplink, the light color is abnormal, and it does not respond to commands. ==
1712
1713 ESP32 hardware is affected by the flow control of the serial port control program, which causes abnormal phenomena.
1714 Please do not select flow control when using the serial port tool.
1715 Please refer to this link to use the serial port tool
1716
1717 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H7.3NotesonusingdifferentserialporttoolsforTrackerD>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H7.3NotesonusingdifferentserialporttoolsforTrackerD]]
1718
1719
1720
1721 = 9.  Order Info =
1722
1723
1724 Part Number: (% style="color:blue" %)**TrackerD-XXX**
1725
1726 (% style="color:blue" %)**XXX**(%%): The default frequency band
1727
1728 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1729
1730 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1731
1732 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1733
1734 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1735
1736 * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1737
1738 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1739
1740 * (% style="color:red" %)**US915**(%%): Default frequency band US915
1741
1742 (% style="display:none" %) (%%)
1743
1744
1745 = 10.  Packing Info =
1746
1747
1748 (% style="color:#037691" %)**Package Includes**:
1749
1750 * TrackerD LoRaWAN GPS/BLE Tracker x 1
1751
1752 * USB recharge & program cable x 1
1753
1754 (% style="color:#037691" %)**Dimensions and Weight**:
1755
1756 * Device Size: 85 x 48 x 15 mm
1757
1758 * Weight: 50g
1759
1760 (% style="display:none" %) (%%)
1761
1762
1763 = 11. Support =
1764
1765 * 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.
1766
1767 * 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]].
1768
1769 (% style="display:none" %)
1770
1771 = 12.  Reference =
1772
1773 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1774 * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1775 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1776 )))