Skip to Content
Last modified by Bei Jinggeng on 2025/07/23 10:57
Show last authors
1
2
3 [[image:image-20250321133921-1.png||data-xwiki-image-style-alignment="center" height="417" width="322"]]
4
5
6
7
8
9
10
11
12
13
14 (% class="wikigeneratedid" %)
15 **Table of Contents:**
16
17 {{toc/}}
18
19
20
21
22
23 = 1.  Introduction =
24
25 == 1.1  What is LoRaWAN Asset Tracker ==
26
27
28 (((
29 TrackerD-LS is an (% style="color:blue" %)**Open Source LoRaWAN Asset Tracker**(%%) based on (% style="color:blue" %)**ESP32 MCU**(%%) and (% style="color:blue" %)**Semtech LoRa Wireless Chip**(%%). It can get the location data via GPS and set it to IoT server via LoRaWAN network.
30
31 TrackerD-LS supports Motion Detection, when there is motion, TrackerD-LS can send data more frequently and it will save power when no motion is detected.
32
33 The LoRa wireless technology used in TrackerD-LS 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 When there is no LoRaWAN network, TrackerD-LS can save the location data. It will send these data to IoT server when there is LoRaWAN network coverage.
36
37 TrackerD-LS is equipped with a (% style="color:blue" %)**3000mAh Li-ion rechargeable battery + Solar Panel**(%%) which let the device can be used for many years. Each TrackerD-LS has a worldwide unique OTAA keys to join the LoRaWAN network.
38
39 TrackerD-LS is program friendly. Developers can use Arduino IDE to customize the software of TrackerD-LS to fit their IoT solution.
40 )))
41
42 (((
43 [[image:image-20250321141555-3.png]]
44
45 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
46
47
48 == 1.2 Specifications ==
49
50
51 (% style="color:blue" %)**Micro Controller:**
52
53 * Espressif ESP32 PICO D4
54 * MCU: ESP32 PICO D4
55 * 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: 2.5v ~~ 3.6v
63 * Operating Temperature: -15℃ ~~ 60°C
64
65 (% style="color:blue" %)**LoRa Spec:**
66
67 * Frequency Range, 168 dB maximum link budget.
68 ** Band 1 (HF): 862 ~~ 1020 Mhz
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 * 3000mA Li-ion Battery power
88 * Built-in Solar Panel
89
90 (% style="color:blue" %)**Power Consumption**
91
92 * Sleeping Mode: 60uA
93 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 * Tracking: max: 38mA
95
96 (% style="display:none" %)
97
98
99 == 1.3  Features ==
100
101
102 * LoRaWAN 1.0.3 Class A
103 * ESP32 PICO D4
104 * SX1276/78 Wireless Chip
105 * Arduino IDE Compatible
106 * Open source hardware / software
107 * Regular/ Real-time GPS tracking
108 * Built-in3 axis accelerometer.
109 * Motion sensing capability
110 * Power Monitoring
111 * Charging circuit via USB port
112 * 3000mA Rechargeable Li-ion Battery + Solar Panel
113 * Datalog
114
115 (% style="display:none" %)
116
117
118 == 1.4  Applications ==
119
120
121 * Logistics and Supply Chain Management
122
123 == 1.5 Hardware version update ==
124
125
126 (% style="display:none" %) (%%)In order to facilitate the use of our customers, we have upgraded the hardware of TrackerD-LS.
127
128 The new version of the hardware adds** an external charging and programming port**, and users do not need to remove the shell for charging and programming in the future.
129
130 Please check the photos below:
131
132
133 [[image:image-20250327112845-1.jpeg||height="423" width="755"]]
134
135 [[image:image-20250327114330-2.png||height="220" width="451"]]
136
137 [[image:image-20250327114537-3.png||height="220" width="447"]]
138
139 (% style="color:red" %)**Note: In order to avoid an external interface failure that would leave the customer unable to access the device, the original typeC interface was not canceled.**
140
141
142 * Charging with the new external interface:
143
144 [[image:image-20250326173255-2.png||height="376" width="382"]]
145
146 (% style="color:red" %)**Note: Do not use the external PIN4 interface and the original built-in TypeC interface at the same time, which will cause the mother board to burn out.**
147
148
149 = 2.  Use TrackerD-LS =
150
151 == 2.1 How it works? ==
152
153
154 TrackerD-LS 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-LS (next to USB port). TrackerD-LS will wake up and auto join the network via OTAA.
155
156
157 == 2.2 Quick guide to connect to LoRaWAN server ==
158
159
160 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. 
161
162 [[image:image-20250321141547-2.png]]
163
164
165 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:
166
167
168 (% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD-LS.
169
170 Each TrackerD-LS is shipped with a sticker with the default device EUI as below:
171
172 [[image:image-20230426085815-1.png||height="206" width="444"]]
173
174
175 You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
176
177 **Create the application.**
178
179 [[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"]]
180
181 [[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"]]
182
183
184 **Add devices to the created Application.**
185
186 [[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"]]
187
188 [[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"]]
189
190
191 **Enter end device specifics manually.**
192
193 [[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"]]
194
195
196 **Add DevEUI and AppKey. Customize a platform ID for the device.**
197
198 [[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"]]
199
200
201 (% style="color:blue" %)**Step 2**:(%%) Add decoder.
202
203 In TTN, user can add a custom payload so it shows friendly reading.
204
205 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/]]
206
207 Below is TTN screen shot:
208
209 [[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"]]
210
211 [[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"]]
212
213
214 (% style="color:blue" %)**Step 3**:(%%) Long press for 5 seconds to start.
215
216 [[image:image-20250321140759-1.png||height="284" width="222"]] (% style="display:none" %)
217
218 TrackerD-LS will auto join to the LoRaWAN network. After join success, TrackerD-LS will start to upload message to IoT server.
219
220
221 == 2.3  Positioning Mode(SMOD) ==
222
223
224 Users can set TrackerD-LS to different Positioning Mode for different applications. Below mod are supported.
225
226 * GPS ONLY(Factory Settings):    Only get and uplink GPS location info.
227
228 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
229
230
231 == 2.4  Uplink Payload ==
232
233 === 2.4.1 Uplink FPORT~=5, Device Status ===
234
235
236 Uplink the device configures with FPORT=5. Once TrackerD-LS Joined the network, it will uplink this message to the server. After the first uplink, TrackerD-LS will uplink Device Status every 12 hours.
237
238 Use can also get the Device Status uplink through the downlink command: Downlink:  0x2301
239
240 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:440px" %)
241 |(% style="background-color:#4f81bd; color:white; width:62px" %)Size(bytes)|=(% style="width: 72px;background-color:#4F81BD;color:white" %)1|=(% style="width: 72px;background-color:#4F81BD;color:white" %)2|=(% style="width: 72px;background-color:#4F81BD;color:white" %)1|=(% style="width: 52px;background-color:#4F81BD;color:white" %)1|=(% style="width: 30px;background-color:#4F81BD;color:white" %)2|=(% style="width: 40px;background-color:#4F81BD;color:white" %)1|=(% style="width: 40px;background-color:#4F81BD;color:white" %)1
242 |(% 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
243
244 [[image:image-20240826095740-1.png||height="191" width="882"]]
245
246
247 Example of Device Status: 22014001FF0FA24002
248
249 Sensor Model:  For TrackerD-LS,this value is 0x22
250
251 Firmware Version:  0x0140,Means:v1.4.0 version
252
253 Frequency Band:
254
255 0x01: EU868
256
257 0x02: US915
258
259 0x03: IN865
260
261 0x04: AU915
262
263 0x05: KZ865
264
265 0x06: RU864
266
267 0x07: AS923
268
269 0x08: AS923-1
270
271 0x09: AS923-2
272
273 0x0a: AS923-3
274
275 Sub-Band: value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
276
277 BAT: shows the battery voltage for TrackerD-LS.
278
279 Ex1: 0x0FA2 = 4002mV
280
281 Use can also get the Device Status uplink through the downlink command:
282
283
284 SMOD Field (total 1 byte)：0x40
285
286 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:270px" %)
287 |(% 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
288 |(% style="width:75px" %)Value|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
289
290 SMOD:
291
292 1 : GPS ONLY
293
294 2 : BLE ONLY
295
296 3 : GPS/BLE Hybrid
297
298
299 GPS_MOD: Define how to send GPS payload
300
301 0 : Enable uploading on-board Temperature and humidity values
302
303 1 : Disable uploading on-board Temperature and humidity values
304
305
306 BLE_Settings:
307
308 1: BLE Positioning with Strongest iBeacon
309
310 2: WiFi Positioning with Strongest WiFi SSID
311
312
313 Status Field (total 1 byte):  0x02
314
315 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:413px" %)
316 |(% 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
317 |(% style="width:75px" %)Value|(% style="width:68px" %)Reserve|(% style="width:87px" %)PNACKMD|(% style="width:49px" %)LON|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9A0TransportMode"]]
318
319 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
320
321
322 Users can use AT+SMOD=1,0,0 to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
323
324 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
325 |(% 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
326 |(% style="width:69px" %)Value|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
327 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
328 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
329
330 [[image:1665301636888-168.png||_mstalt="298012"]]
331
332
333 ==== Alarm & BAT: ====
334
335 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:330px" %)
336 |(% style="background-color:#4f81bd; color:white; width:70px" %)Size(bit)|(% style="background-color:#4f81bd; color:white; width:70px" %)1 bit|(% style="background-color:#4f81bd; color:white; width:120px" %)1 bit|(% style="background-color:#4f81bd; color:white; width:70px" %)14 bits
337 |(% style="width:72px" %)Value|(% style="width:67px" %)reserve|(% style="width:115px" %)Alarm Indicate|(% style="width:65px" %)[[BAT>>||anchor="HBAT:"]] 
338
339 ==== FLAG: ====
340
341 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:184px" %)
342 |(% 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
343 |(% style="width:79px" %)Value|(% style="width:56px" %)[[MOD>>||anchor="HMOD:"]]|(% style="width:50px" %)[[LON>>||anchor="HLON:"]]
344
345 Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
346
347
348 ==== Location info: ====
349
350 * Latitude: 02863D68  ⇒  if (0x02863D68& 0x80000000 = 0 ):  value = 02863D68 /1000000 = 42.351976
351 * Longitude: FAC29BAF  ⇒ if (0xFAC29BAF & 0x80000000 = 1 ):  value = (0xFAC29BAF – 0x 100000000)/1000000 =-87.909457
352
353 Important note:
354
355 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.
356
357 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:
358
359
360 [[image:1664502116362-706.png||_mstalt="293306"]]
361
362
363 3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
364
365 [[image:1664502166010-515.png||_mstalt="291395"]]
366
367
368 ==== Alarm: ====
369
370 Example:  0x4B & 0x40 >> 6 = 0x01
371
372
373 ==== BAT: ====
374
375 Example:  0x4B45 & 0x3FFF ⇒ 2885 (mV).
376
377
378 The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
379
380 * > 4.0v :  80% ~~ 100%
381 * 3.85v ~~3.99v:  60% ~~ 80%
382 * 3.70v ~~ 3.84v:  40% ~~ 60%
383 * 3.40v ~~ 3.69v:  20% ~~ 40%
384 * < 3.39v:  0~~20%
385
386 ==== MOD: ====
387
388 Example:  (0x60>>6) & 0x3f =1
389
390 Set the format of GPS data uplink link：
391
392 0x00:  Enable uploading on-board Temperature and humidity values
393 0x01:   Disable uploading on-board Temperature and humidity values
394
395
396 Set the format of BLE data uplink link：
397
398 0x01:  BLE Positioning with Strongest iBeacon
399
400
401 ==== LON: ====
402
403 Example: (0x60>>5) & 0x01=1.
404
405 Enable/Disable LED activity for uplink
406
407
408 0x00:   Disable LED indicator.
409
410
411 0x01:   Enable LED indicator (Default Value)
412
413
414 ==== Hum: ====
415
416 0202 = if (0x0202 & 0x8000 = 0 ):  value = 0x0202 / 100 = +514 ⇒ 51.4 degree
417
418 Note：The temperature will be higher when charging. Due to the sealing of the device, it will be 1~~2℃ higher than the room temperature. This parameter is for reference only
419
420
421 ==== Tem: ====
422
423 011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -28.2 degree
424
425 Note：Due to the sealing of the equipment, the accuracy of humidity will be 5~~20% lower than the normal value. This parameter is for reference only
426
427 === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
428
429
430 The default uplink payload includes total 11 bytes (AT+SMOD=1,1,0). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
431
432 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:300px" %)
433 |(% 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
434 |(% style="width:69px" %)Value|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
435 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
436 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
437
438 [[image:1665301687277-443.png||_mstalt="296140"]]
439
440
441 === 2.4.4  Uplink FPORT~=7, Alarm information status ===
442
443
444 The upward link device is configured to FPORT = 7. Once TrackerD-LS alarm, it will upload the news to the server.
445
446 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:285px" %)
447 |(% style="background-color:#4f81bd; color:white; width:97px" %)Size(bytes)|(% style="background-color:#4f81bd; color:white; width:105px" %)2|(% style="background-color:#4f81bd; color:white; width:83px" %)1
448 |(% style="width:97px" %)Value|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon
449
450 [[image:image-20230302145315-1.png]]
451
452 alarm=(bytes[0] & 0x40)  ~/~/ Alarm status
453
454 batV=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
455
456 mod = bytes[2] & 0xC0;
457
458 Lon=(bytes[2] & 0x20)
459
460
461 === 2.4.5  Add Payload format in TTN V3 ===
462
463
464 In TTN V3, user can add a custom payload so it shows friendly.
465
466 In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
467
468 [[image:1664502649601-895.png||_mstalt="296985"]]
469
470
471 Add the decoder from this link:  [[dragino-end-node-decoder/TrackerD at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
472
473 Save the change the uplink message will be parsed. As below:
474
475 [[image:1664502676891-606.png||_mstalt="296673"]]
476
477
478 == 2.5 Integrate with Datacake ==
479
480
481 After TrackerD-LS sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
482
483 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]]
484
485 [[image:1664502695771-538.png||_mstalt="297349"]]
486
487
488 == 2.6 Integrate with Tago ==
489
490
491 After TrackerD-LS sends data to LoRaWAN server such as TTN, user can pass the data to Datacake and plot out, currently only support GPS plot.
492
493 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]]
494
495 [[image:1664502715371-321.png||_mstalt="292162"]]
496
497
498 == 2.7  Integrate with Node-red ==
499
500
501 ~1. Install node-red, please refer to the installation method in the link:
502
503 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
504
505
506 2. Import the created flow template, please refer to the import method in the link:
507
508 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
509
510
511 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]]
512
513 **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.**
514
515 [[image:image-20230307135914-1.png||height="527" width="1045"]]
516
517
518 [[image:image-20230307135932-2.png||height="527" width="1044"]]
519
520
521 3. Display the map
522 Enter the link to the map:
523
524 Change its suffix to ditu: http:~/~/119.91.62.30:1880/ditu/
525
526 [[image:image-20230308115430-1.png||height="548" width="1041"]]
527
528
529 Hit all input in input stream
530
531 [[image:image-20230308115616-2.png||height="563" width="1070"]]
532
533
534 View map again
535
536 [[image:image-20230308115701-3.png||height="571" width="1085"]]
537
538
539 == 2.8  Datalog Feature ==
540
541
542 total 273 entries,by default,
543
544 User can set PNACKMD=1, to enable Datalog feature.
545
546 Example use case.
547
548 [[image:image-20231026134207-6.png||height="326" width="899"]]
549
550
551 [[image:image-20231026134244-7.png||height="441" width="660"]]
552
553
554 == 2.9  Transport Mode ==
555
556
557 In Transport Mode, TrackerD-LS will check if there is motion (threldhold defined by [[PT)>>||anchor="H3.2.14A0GetorSetThresholdformotiondetect"]] . 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"]].
558
559 When device is set in Transport Mode, it will uplink more frequenctly during moving.
560
561 * [[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]] defines the Uplink Interval during transportation.
562 * [[TDC>>||anchor="H3.2.1SetTransmitInterval"]] defines the uplink interval when TrackerD-LS is stactic.
563 * [[PT>>||anchor="H3.2.14A0GetorSetThresholdformotiondetect"]] defines the threldhold to detect a motion.
564
565 == 2.10  LED Status ==
566
567
568 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:500px" %)
569 |=(% 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
570 |(% style="width:157px" %)Power On|(% style="width:271px" %)BLUE, RED , Green flash once|(% style="width:202px" %)N/A
571 |(% style="width:157px" %)Join request|(% style="width:271px" %)Green led fast blink once (200ms)|(% style="width:202px" %)Yes
572 |(% style="width:157px" %)Join Success|(% style="width:271px" %)Green led on 5 second|(% style="width:202px" %)N/A
573 |(% style="width:157px" %)Fixing Location|(% style="width:271px" %)BLUE blinks 200ms per second|(% style="width:202px" %)Yes
574 |(% style="width:157px" %)Fixed and uplink|(% style="width:271px" %)GREEN blinks twice (200ms per blink)|(% style="width:202px" %)Yes
575 |(% style="width:157px" %)Fail Fix and uplink|(% style="width:271px" %)RED blinks twice (200ms per blink)|(% style="width:202px" %)Yes
576 |(% style="width:157px" %)Get Downlink|(% style="width:271px" %)GREEN led on 1 second|(% style="width:202px" %)Yes
577 |(% style="width:157px" %)Movement Detect|(% style="width:271px" %)RED led on 500ms|(% style="width:202px" %)N/A
578
579 == 2.11  Button Function ==
580
581
582 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD-LS_LoRaWAN_Asset_Tracker_User_Manual/WebHome/image-20250321140759-1.png?width=264&height=337&rev=1.1||alt="image-20250321140759-1.png"]]
583
584
585 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
586 |=(% 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
587 |(% style="width:135px" %)Factory settings wake up|(% style="width:220px" %)Keep Pressing button for more than 5 seconds|(% style="width:265px" %)Device restart
588 |(% style="width:135px" %)Enter Deep Sleep Mode|(% style="width:220px" %)quickly press the device 5 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.
589
590 == 2.12  USB Port Function ==
591
592
593 The USB interface of TrackerD-LS has below functions:
594
595 * [[Configure Device>>||anchor="H3.ConfigureTrackerD-LSviaATcommandorLoRaWANdownlink"]]
596 * [[Upgrade Firmware>>||anchor="H4.UploadFirmware"]]
597 * Charging TrackerD-LS
598
599 == 2.13  Sleep Mode ==
600
601
602 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.
603
604 There are two ways to put the device into sleep mode:
605
606 ~1. Quickly press the device 5 times to enter deep sleep.
607
608 2. Use the AT+SLEEP command to put the device into sleep.
609
610 In SLEEP mode, you need to reset by reset button.
611
612
613 == 2.14  External charging function(Since hardware version 1.4) ==
614
615
616 Starting from hardware version 1.4, TrackerD-LS adds external charging and serial ports, while the internal TYPE-C port remains as follows:
617
618 **Mode 1: connected via a dedicated 4Pin cable**
619
620 [[image:image-20250414165011-3.png||height="353" width="843"]]
621
622
623 **Mode 2: connected via TYPE-C**
624
625 [[image:image-20250326102016-1.jpeg||height="434" width="386"]]
626
627 (% style="color:red" %)**Note: Because the serial port also comes with a charging function, when using the newly added external charging, you can't use the serial port for connection at the same time, otherwise the mother board will not be able to withstand the voltage and burn the base board.**
628
629
630 = 3. Configure TrackerD-LS via AT command or LoRaWAN downlink =
631
632
633 User can configure TrackerD-LS via AT Command or LoRaWAN Downlink.
634
635 LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
636
637
638 == 3.1 Access AT Command ==
639
640
641 The TrackerD-LS supports the AT command set in the stock firmware. Users can use AT commands by connecting to the TrackerD-LS via a TYPE-C cable or a dedicated 4Pin cable as shown below:
642
643 **Mode 1: connected via TYPE-C**
644
645 [[image:image-20250326102016-1.jpeg||height="434" width="386"]]
646
647
648 **Mode 2: connected via a dedicated 4Pin cable**
649
650 [[image:image-20250326173255-2.png||height="376" width="382"]]
651
652
653 In PC, User needs to set serial tool baud rate to 115200 to access serial console for TrackerD-LS. TrackerD-LS will output system info once power on and user will be able to send AT commands:
654
655 [[image:1664503022490-662.png||_mstalt="293332"]]
656
657
658 [[image:1664503035713-500.png||_mstalt="291096"]]
659
660
661 [[image:1664503047675-651.png||_mstalt="295386"]]
662
663
664 == 3.2 Command Set ==
665
666 === 3.2.1 Set Transmit Interval ===
667
668
669 Set device uplink interval.
670
671 * AT Command:
672
673 AT+TDC=xxx
674
675 Example:  AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
676
677
678 * Downlink Payload (prefix 0x01):
679
680 0x01 00 01 2C   ~/~/  Same as AT+TDC=300000
681
682
683 === 3.2.2 Set Alarm Packet transmission interval ===
684
685
686 Set alarm packet transmit interval
687
688 * AT Command:
689
690 AT+ATDC=xx.
691
692 Example:  AT+ATDC=60000  ~-~->     Set Alarm Packet Interval to 60 seconds. TrackerD-LS will send every 60 seconds in Alarm mode, Default Value: 60000
693
694
695 * Downlink Payload (prefix 0xB1):
696
697 0xB1 00 00 3C     ~/~/  Same as AT+ATDC=60000
698
699
700 === 3.2.3 Set Transport Mode Packet transmission interval ===
701
702
703 Set Transport Mode packet transmit interval
704
705 * AT Command:
706
707 AT+MTDC=xx.
708
709 Example:  AT+MTDC=300000  ~-~->     Set Transport Mode Packet Interval to 300 seconds. TrackerD-LS will send every 300 seconds in Transport mode, Default Value: 300000
710
711
712 * Downlink Payload (prefix 0x03):
713
714 0x03 00 01 2C   ~/~/  Same as AT+MTDC=3000000
715
716
717 === 3.2.4 Exit Alarm ===
718
719
720 Server send downlink command to exit Alarm mode
721
722 * AT Command: No AT Command
723
724 * Downlink Payload (prefix 0x02):
725
726 0x02 01     ~/~/  Exit Alarm Mode
727
728
729 === 3.2.5 Disable/Enable LED flash and buzzer ===
730
731
732 Disable/Enable LED for position, downlink and uplink
733
734 * AT Command:
735
736 AT+LON=xx.  (Disable (0), Enable (1), default:1)
737
738 Example: AT+LON=0  ~-~->  Disable LED for position, downlink and uplink.
739
740
741 * Downlink Payload (prefix 0xAE):
742
743 0xAE 00     ~/~/  Same as AT+LON=0
744
745
746 === 3.2.6 Disable/Enable Transport Mode ===
747
748
749 Users can use this feature to enable/disable Transport Mode.
750
751 * AT Command:
752
753 AT+INTWK=xx.  (Disable (0), Enable (1), default:0)
754
755 Example:  AT+INTWK=1  ~-~->    Enable Transport Mode.
756
757
758 * Downlink Payload (prefix 0xAF):
759
760 0xAF 01   ~/~/  Same as AT+INTWK=1
761
762
763 === 3.2.7 Set Positioning Mode ===
764
765
766 SMOD define how TrackerD-LS scan and uplink data:
767
768 * AT Command:
769
770 AT+SMOD=aa,bb,cc
771
772 aa:
773
774 * 1: GPS ONLY(Factory Settings):    Only get and uplink GPS location info.
775
776 bb:
777
778 * 0 :  GPS+ BAT+ State+Tem&Hum
779
780 * 1 :  GPS +BAT State
781
782 Example:
783
784 AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
785
786 AT+SMOD=1,1,0 ~-~->  GPS +BAT State
787
788
789 * Downlink Payload (prefix 0xA5):
790
791 0xA5 01 00 00     ~/~/  Same as AT+SMOD=1,0,0
792
793
794 === 3.2.8 Set MAX GPS position time ===
795
796
797 Set max positioning time, default is 150 seconds. TrackerD-LS will try to get location info within this period. If fail to get position data within this time, TrackerD-LS will use 000000 for latitude and longitude.
798
799 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.
800
801 * AT Command:
802
803 AT+FTIME=xx   ~-~->  Set to use xx as max fix time.
804
805 Example:  AT+FTIME=150
806
807
808 * Downlink Payload (prefix 0xAA):
809
810 0xAA 00 96   ~/~/  Set AT+FTIME=150
811
812
813 === 3.2.9 Set PDOP value for GPS fix accuracy ===
814
815
816 PDOP(Position Dilution of Precision) filter, TrackerD-LS 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.
817
818 A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
819
820 * AT Command:
821
822 AT+PDOP=2.5    ~-~->   Set PDOP to 2.5
823
824
825 * Downlink Payload (prefix 0xAD):
826
827 0xAD 00 0A    ~/~/  Set AT+PDOP=1  (0x0A / 10 =1)
828
829 0xAD 00 19    ~/~/  Set AT+PDOP=2.5    (0x19 / 10 =2.5)
830
831 0xAD 00 46     ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
832
833
834 === 3.2.10 Disable/Enable the confirmation mode ===
835
836
837 * AT Command:
838
839 AT+CFM=xx
840
841
842 Example:
843
844 AT+CFM=0    ~-~->    Disable confirmation
845
846 AT+CFM=1    ~-~->   Enable confirmation
847
848
849 * Downlink Payload (prefix 0x05):
850
851 0x05 01  ~/~/  Same as AT+CFM=1
852
853
854 === 3.2.11  Auto Send None-ACK messages ===
855
856
857 TrackerD-LS will wait for ACK for each uplink, If TrackerD-LS doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD-LS keeps sending messages in normal periodically. Once TrackerD-LS gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
858
859
860 * AT Command: AT+PNACKMD
861
862 The default factory setting is 0.
863
864
865 Command Example Function Response:
866
867 AT+PNACKMD=1   ~/~/  Poll None-ACK message OK
868
869
870 * Downlink Command: 0x34
871
872 Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
873
874
875 === 3.2.12  Disable/Enable Information printing ===
876
877
878 Users can use this feature to enable/disable Information printing.
879
880 AT Command:
881
882 AT+SHOWID=XX          ~/~/  (Disable (0), Enable (1), default:0)
883 \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
884
885
886 === 3.2.13  Get or Set Eight Channels Mode, only for us915, AU915 ===
887
888
889 The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
890
891 AT Command:
892
893 AT+CHE=1       ~/~/ set one channels mode
894
895
896 Downlink Payload:0X24
897
898 Example: 0x24 01  ~/~/ Same as AT+CHE=1
899
900
901 === 3.2.14  Get or Set Threshold for motion detect ===
902
903
904 User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
905
906 AT Command:
907
908 AT+PT=xx
909
910 Example:
911
912 AT+PT=14    ~-~->    Set to detect car motion.
913
914 AT+PT=41  ~-~->    set to detect walk motion.
915
916
917 Downlink Payload:0xB4
918
919 0xB4 14          ~/~/  Same as AT+PT=14
920
921
922 === 3.2.15  Set AT command window time ===
923
924
925 AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
926
927 AT Command:
928
929 AT+ATST=XX
930
931 Example:
932
933 AT+ATST=15    ~-~-> Set the time to 15 seconds
934
935 Downlink Payload:0XB5
936
937 0xB5 0F          ~/~/  Same as AT+ATST=15
938
939
940 === 3.2.16  Set the stepmeter mode ===
941
942
943 After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
944
945 AT Command:
946
947 AT+PM=xx
948
949 Example:
950
951 AT+PM=1    ~-~->  Turn on step counting mode
952
953 AT+PM=0    ~-~->  Turn OFF step counting mode
954
955 Downlink Payload:0XB6
956
957 0xB6 01          ~/~/  Same as AT+PM=1
958
959
960 = 4. Upload Firmware =
961
962 == 4.1 Firmware Change Log ==
963
964
965 [[See this link>>https://github.com/dragino/TrackerD/releases]]
966
967
968 == 4.2 How to upgrade firmware ==
969
970
971 User can use the TrackerD-LS's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
972
973
974 **Step 1:** Connect the TrackerD-LS to the PC via the USB cable that came with the TrackerD-LS or the dedicated 4Pin cable.
975
976 Mode 1: connected via TYPE-C
977
978 [[image:image-20250326102040-2.jpeg||height="516" width="458"]]
979
980
981 Mode 2: connected via a dedicated 4Pin cable
982
983 [[image:image-20250326173255-2.png]]
984
985
986 **Step2:**  Install CH9102 driver in the PC.
987
988 After installation of the driver and plug in TrackerD-LS, user should be able to see com port in PC's device manager.
989
990 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD-LS_LoRaWAN_Asset_Tracker_User_Manual/WebHome/image-20231107105146-1.png?width=754&height=519&rev=1.1||alt="image-20231107105146-1.png"]]
991
992
993 **Step3:**  Click this **[[link>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/AMBNyRAnzPS7eJJ1ibfl6WM/LoRaWAN%20End%20Node/TrackerD/Flash%20Tool?rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1&dl=0]]** to download and install the Flash tool.
994
995
996 **Step4:**  Run Flash Download Tool and configure chip type to ESP32
997
998
999 [[image:1664503563660-578.png||_mstalt="296777"]]
1000
1001
1002 [[image:1664503574618-659.png||_mstalt="297986"]]
1003
1004
1005
1006 **Step5:**  Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
1007
1008 [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1009
1010
1011 Users need to use below files:
1012
1013 boot_app0.bin @0e000
1014
1015 US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1016
1017
1018 [[image:image-20221207120501-1.png]]
1019
1020
1021 After upgrade finish, it will show finish as below:
1022
1023 [[image:image-20221207133911-7.png]]
1024
1025
1026 = 5. Developer Guide =
1027
1028 == 5.1 Compile Source Code ==
1029
1030 === 5.1.1 Set up ARDUINO compile environment ===
1031
1032
1033 * 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]]
1034
1035 Install IDE on PC, open and click 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]]
1036
1037
1038 [[image:1664503635019-941.png||_mstalt="294658"]]
1039
1040
1041
1042 * Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it.
1043
1044 [[image:1664503715811-892.png||_mstalt="295698"]]
1045
1046
1047 === 5.1.2  Build the development environment ===
1048
1049
1050 ~1. Download and install arduino IDE
1051
1052 [[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]]
1053
1054
1055 2. Download the ESP32 development package in the arduino IDE
1056
1057 [[image:image-20221213100007-1.png]]
1058
1059
1060 Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1061
1062 [[image:image-20221213100626-2.png]]
1063
1064
1065 Restart the IDE after the addition is complete, then:
1066
1067 [[image:image-20221213100808-3.png||height="679" width="649"]]
1068
1069
1070 [[image:image-20221213101040-4.png]]
1071
1072
1073 Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1074 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)
1075
1076
1077 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:
1078
1079 Methods as below:
1080
1081 ~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1082
1083 2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1084
1085 (% id="cke_bm_4554S" %) (%%)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.
1086
1087 [[image:image-20221213102311-5.png||height="582" width="711"]]
1088
1089
1090 3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)
1091
1092 [[image:image-20221213102334-6.png]]
1093
1094 **Note: This step requires a python environment**
1095
1096
1097 Either way, in the end:
1098
1099 The final effect is to open the arduino and you can see the esp32
1100
1101 [[image:image-20221213110952-8.png||height="866" width="711"]]
1102
1103
1104
1105 [[image:image-20221024105643-1.png||_mstalt="428129"]]
1106
1107 Figure1
1108
1109
1110
1111 [[image:image-20221024105643-2.png||_mstalt="428493"]]
1112
1113 Figure2
1114
1115
1116 * Download the latest TrackerD-LS from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD-LS>>url:https://github.com/dragino/TrackerD]]
1117
1118 Note:As of version 1.4.9, the source code of TrackerD and TrackerD-LS has been merged.Switching mod via AT commands.
1119
1120 [[image:image-20240618111924-1.png]]
1121
1122
1123 Put the Library in the TrackerD-LS directory into the libraries file in the Arduino directory:
1124
1125
1126 [[image:1664503752288-974.png||_mstalt="298194"]]
1127
1128
1129 == 5.2 Source Code ==
1130
1131
1132 * Open the example in the TrackerD-LS file, please select the correct port in the IDE, as shown below:
1133
1134 [[image:1664503794261-827.png||_mstalt="296387"]]
1135
1136
1137
1138 * Click to upload
1139
1140 [[image:1664503808294-336.png||_mstalt="295711"]]
1141
1142
1143
1144 * Check the result, if the upload is successful, as shown below, open the serial port to view the data
1145
1146 [[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1147
1148
1149 = 6.  FAQ =
1150
1151 == 6.1 How to change the LoRa Frequency Bands/Region? ==
1152
1153
1154 User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1155
1156
1157 == 6.2 What is the pin mapping for the USB program cable? ==
1158
1159
1160 [[image:1664499635206-262.png||_mstalt="295360"]]
1161
1162
1163 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:314px" %)
1164 |=(% 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
1165 |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1166 |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1167 |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
1168 |(% style="width:118px" %)A1,B1,A12,B12|(% style="width:67px" %)Black|(% style="width:123px" %)GND
1169 |(% style="width:118px" %)A5|(% style="width:67px" %)Purple|(% style="width:123px" %)MTDC/GOIO13
1170 |(% style="width:118px" %)B5|(% style="width:67px" %)Blue|(% style="width:123px" %)MTDC/GPIO12
1171 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1172 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1173
1174 == 6.3 Notes on using different serial port tools for TrackerD-LS ==
1175
1176 === 6.3.1  Serial port utility ===
1177
1178
1179 [[image:1698284199922-935.png]]
1180
1181
1182 === 6.3.2  SecureCRT ===
1183
1184
1185 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.
1186
1187
1188 [[image:image-20221102140704-3.png||_mstalt="427076"]]
1189
1190
1191 [[image:image-20221102140712-4.png||_mstalt="427089"]]
1192
1193
1194 === 6.3.3  PUTTY ===
1195
1196
1197 [[image:image-20221102140748-5.png||_mstalt="430456"]]
1198
1199
1200 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.
1201
1202
1203 [[image:image-20221102140801-6.png||_mstalt="427466"]]
1204
1205
1206 == 6.4 How to modify source code to compile different frequency band bin file? ==
1207
1208
1209 Important: Developer MUST follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1210 See : [[Set Up Arduino Compile Environment for TrackerD-LS. >>||anchor="H5.1.1SetupARDUINOcompileenvironment"]]
1211
1212 ~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
1213
1214
1215 [[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1216
1217
1218 2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
1219
1220
1221 [[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1222
1223
1224 3. Compile the AS923_JP band, please refer to the intention shown
1225
1226
1227 [[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1228
1229
1230 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.
1231
1232
1233 [[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1234
1235
1236 [[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1237
1238
1239 == 6.5 Are there example python example for BLE Indoor Positioning? ==
1240
1241
1242 [[Operating instructions for BLE indoor positioning>>doc:Main.User Manual for LoRaWAN End Nodes.TrackerD.Example of BLE indoor positioning python.WebHome]]
1243
1244
1245 == 6.6 Can alert mode and transport mode be used together? ==
1246
1247
1248 Yes, you can also press the panic button to sound the alarm if set to transport mode
1249
1250
1251 == 6.7 Can i get the datalog record from console? ==
1252
1253
1254 Since firmware v1.0.3, User is able to get the datalog record from console as well.
1255
1256 [[image:image-20240329120023-1.png||height="556" width="543"]]
1257
1258
1259 = 7  Trouble Shooting =
1260
1261 == 7.1  TDC is changed to 4294947296 and cause no uplink. ==
1262
1263
1264 Before firmware v1.4.0: When the Transport Mode is enabled (AT+INTWK=1), the TDC needs to be greater than MTDC, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1265
1266
1267 == 7.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1268
1269
1270 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-LS will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.
1271
1272
1273 == 7.3  Problem after Upgrading Firmware ==
1274
1275 === 7.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1276
1277
1278 Error Output
1279
1280 [[image:image-20221122100004-4.png||_mstalt="424606"]]
1281
1282
1283 Some partition is missed during upgrade, please upgrade below four files as example:
1284
1285 [[image:image-20221207120524-2.png]]
1286
1287
1288 === 7.3.2 TrackerD-LS's led light is always GREEN on after upgrading ===
1289
1290
1291 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 7.3.1
1292
1293
1294 === 7.3.3 "flash read err" after upgrade firmware ===
1295
1296
1297 Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1298
1299 [[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1300
1301
1302 User need to upgrade again with below four files to solve this issue.
1303
1304 [[image:image-20221207120530-3.png]]
1305
1306 Figure 2
1307
1308
1309 === 7.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1310
1311
1312 User might erase the entire flash include keys and default settings which cause this issue.
1313
1314 After the upgrade is completed, enter AT+CFG as shown in the figure below.
1315
1316
1317 [[image:image-20221122100004-3.png||_mstalt="424242"]]
1318
1319
1320 Please AT+FDR which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1321
1322 After AT+FDR. please set
1323
1324 * AT+PDOP=7
1325
1326 * AT+FTIME=180
1327
1328 Example:
1329
1330 AT+PDOP=7.00
1331
1332 AT+FTIME=180
1333
1334 AT+DEUI=70B3D57ED0053981  
1335
1336 AT+APPEUI=D23345667BCBCCAF
1337
1338 AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1339
1340 AT+DADDR=260b4dce  (no need for OTAA)
1341
1342 AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1343
1344 AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1345
1346
1347 == 7.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1348
1349
1350 Please download version 1.4.2 again
1351
1352
1353 == 7.5  How to deal with unsuccessful GPS positioning? ==
1354
1355
1356 1） Make Sure the device is in Open Area where can see the sky.
1357
1358 2)  Set PDOP to a higher value.
1359
1360 * AT+PDOP=2 (can be positioned precisely.）
1361
1362 * AT+PDOP=7 (Quickly locate in open spaces）
1363
1364 * AT+PDOP=14.7 (Positioning can be acquired in complex environments）
1365
1366 Please refer to this [[link>>||anchor="H3.2.9SetPDOPvalueforGPSfixaccuracy"]] on how to set up PDOP
1367
1368
1369 == 7.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1370
1371
1372 When upgrading, use the erase button to upgrade
1373
1374 [[image:image-20221207120536-4.png]]
1375
1376
1377 The parameters are displayed abnormally and cannot be fixed using AT+FDR
1378
1379 [[image:image-20221128103040-2.png||height="431" width="525"]]
1380
1381
1382 Please upgrade these four files,link (The boot_app0 file is in the version folder you need)
1383
1384 [[image:image-20221207134028-8.png]]
1385
1386
1387 Reboot information after upgrade
1388
1389 [[image:image-20221128111443-4.png||height="432" width="546"]]
1390
1391
1392 Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
1393
1394 [[image:image-20221128111850-5.png]]
1395
1396
1397 After the parameters return to normal, upgrade to the version you need again
1398
1399 [[image:image-20221207120601-5.png]]
1400
1401
1402 At this point, the parameters return to normal after running AT+FDR again
1403
1404 [[image:image-20221128112035-7.png]]
1405
1406
1407 == 7.7  If you encounter the following problems, please upgrade to the latest version ==
1408
1409
1410 ~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1411
1412 2. Send some commands through the serial port to prompt an error (Example: AT+SMOD=1,0,1)
1413
1414
1415 == 7.8  Why when using some serial consoles, only inputting the first string port console will return "error"? ==
1416
1417
1418 Need to enter the entire command at once, not a single character.
1419 User can open a command window or copy the entire command to the serial console.
1420
1421
1422 = 8.  Order Info =
1423
1424
1425 Part Number: TrackerD-LS-XXX
1426
1427 XXX: The default frequency band
1428
1429 * EU433: Default frequency band EU433
1430
1431 * EU868: Default frequency band EU868
1432
1433 * IN865: Default frequency band IN865
1434
1435 * KR920: Default frequency band KR920
1436
1437 * AS923: Default frequency band AS923
1438
1439 * AU915: Default frequency band AU915
1440
1441 * US915: Default frequency band US915
1442
1443 = 9.  Packing Info =
1444
1445
1446 Package Includes:
1447
1448 * TrackerD-LS LoRaWAN Asset Tracker x 1
1449
1450 * Solar charging & program cable x 1
1451
1452 Dimensions and Weight:
1453
1454 * Device Size: mm
1455
1456 * Weight: g
1457
1458 = 10. Support =
1459
1460
1461 * 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.
1462
1463 * 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]].
1464
1465 = 11.  Reference =
1466
1467
1468 * [[Firmware in Bin format>>https://www.dropbox.com/sh/9oi0fvpfs7z25qb/AACqAy9Y_x_JLkmEWJ28CdTxa?dl=0]]
1469
1470 * [[Hardware Source>>https://www.dropbox.com/sh/8cunfpcrxumxb6i/AABs-Wlm670VtZDViZXx7V0pa?dl=0]]
1471 )))