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

Applications

Navigation

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