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