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