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

Applications

Navigation

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