Skip to Content
Last modified by Xiaoling on 2025/04/27 16:48
From version 51.25
edited by Xiaoling
on 2022/09/30 15:07
Change comment: There is no comment for this version
To version 19.1
edited by Xiaoling
on 2022/09/30 09:05
Change comment: Uploaded new attachment "1664499921684-770.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,9 +7,3 @@
1 -(% style="text-align:center" %)
2 -[[image:1664505654417-133.png]]
3 -
4 -
5 -
6 -
7 7  (% class="wikigeneratedid" %)
8 8  **Table of Contents:**
9 9  
... ... @@ -12,18 +12,19 @@
12 12  
13 13  
14 14  
9 +
15 15  = 1.  Introduction =
16 16  
12 +== 1.1  OverView ==
17 17  
18 -== 1.1  What is TrackerD ==
19 19  
20 -
21 21  (((
22 22  TrackerD is an (% style="color:blue" %)**Open Source LoRaWAN Tracker**(%%) based on (% style="color:blue" %)**ESP32 MCU**(%%) and (% style="color:blue" %)**Semtech LoRa Wireless Chip**.
23 23  )))
24 24  
25 25  (((
26 -In TrackerD, there are various sensors such as GPS, WiFi, BLE, Temperature, Humidity, Motion Detection, and Buzzer. User can use TrackerD for different tracking scenario.
20 +There are various sensors such as GPS, WiFi, BLE, Temperature, Humidity, Motion Detection, and Buzzer in TrackerD. Make it useful for different kinds of applications.
21 +)))
27 27  
28 28  (((
29 29  TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.
... ... @@ -30,9 +30,8 @@
30 30  )))
31 31  
32 32  (((
33 -The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
28 +The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates.It provides ultra-long range spread spectrum communication and high interference immunity whilst minimising current consumption. It targets professional tracking services.
34 34  )))
35 -)))
36 36  
37 37  (((
38 38  TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
... ... @@ -40,788 +40,42 @@
40 40  
41 41  )))
42 42  
43 -[[image:1664499921684-770.png]]
37 +[[image:image-20220906111043-1.png]]
44 44  
45 45  
46 -(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
40 +== 1.2  Features ==
47 47  
48 48  
43 +* LoRaWAN v1.0.3 Class A protocol.
44 +* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
45 +* Track position via GPS / BLE or WiFi
46 +* Temperature & Humidity
47 +* Motion detection
48 +* Built-in Buzzer
49 +* AT Commands to change parameters
50 +* Remote configure parameters via LoRa Downlink
51 +* Uplink on periodically
52 +* Datalog feature
53 +* Firmware upgradable via program port
54 +* Programable via Arduino IDE
55 +* 1000mAh li-on rechargeable battery
49 49  
50 -== 1.2 Specifications ==
57 +== 1.3  Applications ==
51 51  
52 52  
53 -(% style="color:blue" %)**Micro Controller:**
54 -
55 -* Espressif ESP32 PICO D4
56 -* MCU: ESP32 PICO D4
57 -* Bluetooth: Bluetooth V4.2 BR/EDR and Bluetooth LE
58 -* WiFi : 802.11 b/g/n (802.11n up to 150 Mbps)
59 -* Integrated SPI flash : 4 MB
60 -* RAM: 448 KB
61 -* EEPROM: 520 KB
62 -* Clock Speed: 32Mhz
63 -
64 -(% style="color:blue" %)**Common DC Characteristics:**
65 -
66 -* Supply Voltage: 5V via USB port or Internal li-on battery
67 -* Operating Temperature: -40 ~~ 60°C
68 -
69 -(% style="color:blue" %)**LoRa Spec:**
70 -
71 -* Frequency Range,
72 -** Band 1 (HF): 862 ~~ 1020 Mhz
73 -* 168 dB maximum link budget.
74 -* +20 dBm - 100 mW constant RF output vs.
75 -* +14 dBm high efficiency PA.
76 -* Programmable bit rate up to 300 kbps.
77 -* High sensitivity: down to -148 dBm.
78 -* Bullet-proof front end: IIP3 = -12.5 dBm.
79 -* Excellent blocking immunity.
80 -* Low RX current of 10.3 mA, 200 nA register retention.
81 -* Fully integrated synthesizer with a resolution of 61 Hz.
82 -* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
83 -* Built-in bit synchronizer for clock recovery.
84 -* Preamble detection.
85 -* 127 dB Dynamic Range RSSI.
86 -* Automatic RF Sense and CAD with ultra-fast AFC.
87 -* Packet engine up to 256 bytes with CRC.
88 -* LoRaWAN 1.0.3 Specification
89 -
90 -(% style="color:blue" %)**Battery:**
91 -
92 -* 1000mA Li-on Battery power (for model TrackerD)
93 -
94 -(% style="color:blue" %)**Power Consumption**
95 -
96 -* Sleeping Mode: 200uA
97 -* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
98 -* Tracking: max: 38mA
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,BLE,WIFI tracking
110 -* Built-in3 axis accelerometer (LIS3DH)
111 -* Humidity / temperature sensor : GXCAS Technology GXHT3X
112 -* Motion sensing capability
113 -* Power Monitoring
114 -* Charging circuit via USB port
115 -* 1000mA Li-on Battery power
116 -* Tri-color LED, Alarm button
117 -* Datalog
118 -
119 -
120 -== 1.4  Applications ==
121 -
122 -
123 123  * Logistics and Supply Chain Management
124 124  * Human tracking
125 125  
126 126  
127 -= 2.1 Use TrackerD =
128 128  
129 -
130 -== 2.1 How it works? ==
131 -
132 -
133 -TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
134 -
135 -
136 -
137 -== 2.2 Quick guide to connect to LoRaWAN server ==
138 -
139 -
140 -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. 
141 -
142 -
143 -[[image:1664501652064-326.png]]
144 -
145 -
146 -
147 -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:
148 -
149 -
150 -(% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
151 -
152 -Each TrackerD is shipped with a sticker with the default device EUI as below:
153 -
154 -
155 -[[image:1664501677253-891.png]]
156 -
157 -
158 -Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
159 -
160 -
161 -**__Add APP EUI in the application:__**
162 -
163 -
164 -[[image:1664501711466-918.png]]
165 -
166 -
167 -
168 -[[image:1664501721248-725.png]]
169 -
170 -
171 -[[image:1664501734705-405.png]]
172 -
173 -
174 -
175 -**__Add APP KEY and DEV EUI:__**
176 -
177 -
178 -[[image:1664501784668-703.png]]
179 -
180 -
181 -
182 -
183 -(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
184 -
185 -
186 -(% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
187 -
188 -
189 -(% style="color:blue" %)**Positioning Mode(SMOD):**
190 -
191 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get GPS location info.
192 -* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking.
193 -* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.
194 -
195 -User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
196 -
197 -
198 -
199 -== 2.3 Uplink Payload ==
200 -
201 -
202 -=== 2.3.1 Uplink FPORT~=5, Device Status ===
203 -
204 -
205 -
206 -=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
207 -
208 -
209 -The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won't work on DR0 on US915/AU915 frequency band. )
210 -
211 -
212 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
213 -|=(% scope="row" style="width: 50px;" %)(((
214 -**Size(bytes)**
215 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
216 -2(optional)
217 -)))|(% style="width:87px" %)(((
218 -2(optional)
219 -)))
220 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
221 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
222 -)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
223 -
224 -[[image:1664501958445-288.png]]
225 -
226 -
227 -==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
228 -
229 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
230 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
231 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
232 -
233 -
234 -==== (% style="color:blue" %)**FLAG:**(%%) ====
235 -
236 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
237 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits
238 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H2.3.4BLEpositioningPayload28Fport229"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 
239 -
240 -**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
241 -
242 -
243 -==== (% style="color:blue" %)**Location info:**(%%) ====
244 -
245 -* Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
246 -* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
247 -
248 -
249 -
250 -(% style="color:red" %)**Important note:**
251 -
252 -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.
253 -
254 -2.  In firmware version v1.5, Roll & Pitch is disabled by default.
255 -
256 -3.  When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
257 -
258 -
259 -[[image:1664502116362-706.png]]
260 -
261 -
262 -
263 -4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
264 -
265 -[[image:1664502166010-515.png]]
266 -
267 -
268 -
269 -==== (% style="color:blue" %)**Alarm:**(%%) ====
270 -
271 -Example:  0x4B & 0x40 >> 6 = 0x01
272 -
273 -
274 -==== (% style="color:blue" %)**BAT:**(%%) ====
275 -
276 -Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
277 -
278 -The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \
279 -
280 -
281 -* > 4.0v :  80% ~~ 100%
282 -* 3.85v ~~3.99v:  60% ~~ 80%
283 -* 3.70v ~~ 3.84v:  40% ~~ 60%
284 -* 3.40v ~~ 3.69v:  20% ~~ 40%
285 -* < 3.39v:  0~~20%
286 -
287 -
288 -
289 -
290 -==== (% style="color:blue" %)**LON:**(%%) ====
291 -
292 -
293 -Enable/Disable LED activity for uplink
294 -
295 -0x00:  Disable LED indicator.
296 -
297 -0x01:  Enable LED indicator (Default Value)
298 -
299 -
300 -==== (% style="color:blue" %)**Hum:**(%%) ====
301 -
302 -0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
303 -
304 -
305 -==== (% style="color:blue" %)**Tem:**(%%) ====
306 -
307 -011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
308 -
309 -
310 -
311 -=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
312 -
313 -
314 -
315 -=== 2.3.4 BLE positioning Payload(Fport2) ===
316 -
317 -
318 -Different MODE has different payload:
319 -
320 -**MODE=2**
321 -
322 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
323 -|=(% scope="row" style="width: 50px;" %)(((
324 -**Size(bytes)**
325 -)))|(% style="width:30px" %)16|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1
326 -|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
327 -iBeacon MAJOR
328 -)))|(% style="width:63px" %)(((
329 -iBeacon MINOR
330 -)))|(% style="width:71px" %)(((
331 -iBeacon Measured Power
332 -)))|(% style="width:50px" %)(((
333 -iBeacon RSSI
334 -)))|(% style="width:47px" %)(((
335 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
336 -)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
337 -
338 -[[image:1664502425687-834.png]]
339 -
340 -
341 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
342 -* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
343 -* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
344 -* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
345 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
346 -* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
347 -* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
348 -
349 -=== 2.3.5 Add Payload format in TTN V3 ===
350 -
351 -
352 -In TTN V3, use can add a custom payload so it shows friendly.
353 -
354 -In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
355 -
356 -
357 -[[image:1664502649601-895.png]]
358 -
359 -
360 -Add the decoder from this link:
361 -
362 -
363 -Save the change the uplink message will be parsed. As below:
364 -
365 -[[image:1664502676891-606.png]]
366 -
367 -
368 -
369 -== 2.4 Integrate with Datacake ==
370 -
371 -
372 -After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
373 -
374 -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]]
375 -
376 -
377 -[[image:1664502695771-538.png]]
378 -
379 -
380 -
381 -== 2.5 Integrate with Tago ==
382 -
383 -
384 -After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
385 -
386 -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]]
387 -
388 -
389 -[[image:1664502715371-321.png]]
390 -
391 -
392 -
393 -== 2.6 Alarm Mode ==
394 -
395 -
396 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
397 -
398 -
399 -Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode.
400 -
401 -
402 -Two ways to exit alarm mode:
403 -
404 -* Server send a downlink command to exit.
405 -* User fast press the RED button 10 times.
406 -
407 -When exit alarm mode, (% style="color:red" %)**RED LED**(%%) will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false.
408 -
409 -
410 -
411 -== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- ==
412 -
413 -
414 -
415 -== 2.8 LED Status ==
416 -
417 -
418 -(% border="2" style="background-color:#ffffcc; color:green; width:636px" %)
419 -|(% style="width:157px" %)**Event**|(% style="width:271px" %)**Action**|(% style="width:202px" %)**AT+LON to control on/off**
420 -|(% 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
421 -|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
422 -|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
423 -|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
424 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
425 -|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
426 -|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
427 -|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
428 -|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes
429 -|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
430 -|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
431 -
432 -== 2.9 Button Function ==
433 -
434 -
435 -(% style="color:green" %)**RESET button:**
436 -
437 -[[image:1664502835802-546.png]]
438 -
439 -Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
440 -
441 -
442 -(% style="color:red" %)**RED button:**
443 -
444 -[[image:1664502854406-763.png]]
445 -
446 -
447 -(% border="2" style="background-color:#ffffcc; color:green; width:627px" %)
448 -|(% style="width:135px" %)**Function**|(% style="width:220px" %)**Action**|(% style="width:265px" %)**Description**
449 -|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.6AlarmMode"]]
450 -|(% style="width:135px" %)Exit Alarm Mode|(% style="width:220px" %)Fast press the (% style="color:red" %)**RED** (%%)button 10 times|(% style="width:265px" %)Exit Alarm Mode
451 -|(% style="width:135px" %)Enter Deep Sleep Mode|(% style="width:220px" %)Press and hold the button for 10 seconds, then quickly press the device 3 times to enter deep sleep|(% style="width:265px" %)This is the mode ship out from factory. CPU will be complete in sleep mode and no LoRa activity, only use before deploy.
452 -
453 -== 2.10 USB Port Function ==
454 -
455 -
456 -The USB interface of TrackerD has below functions:
457 -
458 -* Power on the device
459 -* Recharge the battery
460 -* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
461 -* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
462 -
463 -= 3. Configure TrackerD via AT command or LoRaWAN downlink =
464 -
465 -
466 -User can configure TrackerD via AT Command or LoRaWAN Downlink.
467 -
468 -LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
469 -
470 -
471 -
472 -== 3.1 Access AT Command ==
473 -
474 -
475 -TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below.
476 -
477 -
478 -[[image:1664502999401-486.png]]
479 -
480 -
481 -In PC, User needs to set serial tool baud rate to (% style="color:green" %)**115200**(%%) to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
482 -
483 -
484 -[[image:1664503022490-662.png]]
485 -
486 -
487 -
488 -[[image:1664503035713-500.png]]
489 -
490 -
491 -
492 -[[image:1664503047675-651.png]]
493 -
494 -
495 -
496 -== 3.2 Command Set ==
497 -
498 -
499 -=== 3.2.1 Set Transmit Interval ===
500 -
501 -
502 -Set device uplink interval.
503 -
504 -* (% style="color:blue" %)**AT Command:**
505 -
506 -(% style="color:#037691" %)**AT+TDC=xxx **
507 -
508 -Example:  AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
509 -
510 -
511 -* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**
512 -
513 -(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
514 -
515 -
516 -
517 -=== 3.2.2 Set Alarm Packet transmission interval ===
518 -
519 -
520 -Set alarm packet transmit interval
521 -
522 -* (% style="color:blue" %)**AT Command:**
523 -
524 -(% style="color:#037691" %)**AT+ATDC=xx. **
525 -
526 -Example:  AT+ATDC=60000  **~-~->    ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
527 -
528 -
529 -* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**
530 -
531 -(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
532 -
533 -
534 -
535 -=== 3.2.3 Set Sports Mode Packet transmission interval ===
536 -
537 -
538 -Set sports packet transmit interval
539 -
540 -* (% style="color:blue" %)**AT Command:**
541 -
542 -(% style="color:#037691" %)**AT+MTDC=xx. **
543 -
544 - Example:  AT+MTDC=300000  **~-~->    ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
545 -
546 -
547 -* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
548 -
549 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
550 -
551 -
552 -
553 -=== 3.2.4 Exit Alarm ===
554 -
555 -
556 -Server send downlink command to exit Alarm mode
557 -
558 -* (% style="color:blue" %)**AT Command: No AT Command**
559 -
560 -* (% style="color:blue" %)**Downlink Payload (prefix 0x02):**
561 -
562 -(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
563 -
564 -
565 -
566 -=== 3.2.5 Disable/Enable LED flash ===
567 -
568 -
569 -Disable/Enable LED for position, downlink and uplink
570 -
571 -* (% style="color:blue" %)**AT Command:**
572 -
573 -(% style="color:#037691" %)**AT+LON=xx.  (Disable (0), Enable (1), default:1)**
574 -
575 - Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
576 -
577 -
578 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**
579 -
580 -(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
581 -
582 -
583 -
584 -=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
585 -
586 -
587 -User can use this feature to check and set thread hole of movement detect
588 -
589 -* (% style="color:blue" %)**AT Command:**
590 -
591 -(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
592 -
593 - Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
594 -
595 -
596 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
597 -
598 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
599 -
600 -
601 -
602 -=== 3.2.7 Set Positioning Mode ===
603 -
604 -
605 -SMOD define the how TrackerD scan and uplink date.
606 -
607 -GPS室外定位模式：  设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
608 -
609 -BLE室内定位模式：  设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
610 -
611 -GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
612 -
613 -运动模式：  设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
614 -
615 -
616 -
617 -* (% style="color:blue" %)**AT Command:**
618 -
619 -(% style="color:#037691" %)**AT+SMOD=xx. **
620 -
621 -
622 - **Example:**
623 -
624 - AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
625 -
626 - AT+ SMOD =1,1    **~-~->**  GPS +BAT State
627 -
628 - AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
629 -
630 -
631 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
632 -
633 -(% style="color:#037691" %)**0xA5 01 00**    (%%) ~/~/  Same as AT+ SMOD =1,0
634 -
635 -
636 -
637 -=== 3.2.8 Set MAX GPS position time ===
638 -
639 -
640 -Set max positioning time, default is 150 seconds. TrackerD will try to get location info within this period. If fail to get position data within this time, TrackerD will use 000000 for latitude and longitude.
641 -
642 -
643 -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.
644 -
645 -
646 -* (% style="color:blue" %)**AT Command:**
647 -
648 -(% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
649 -
650 -Example:  AT+FTIME=150
651 -
652 -
653 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
654 -
655 -(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
656 -
657 -
658 -
659 -=== 3.3.9 Set PDOP value for GPS fix accuracy ===
660 -
661 -
662 -PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can't get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.
663 -
664 -
665 -A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
666 -
667 -
668 -* (% style="color:blue" %)**AT Command:**
669 -
670 -(% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
671 -
672 -
673 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**
674 -
675 -(% style="color:#037691" %)**0xAD 00 0A**   (%%) ~/~/  Set AT+PDOP=1  (0x0A / 10 =1)
676 -
677 -(% style="color:#037691" %)**0xAD 00 19**   (%%) ~/~/  Set AT+PDOP=2.5    (0x19 / 10 =2.5)
678 -
679 -(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
680 -
681 -
682 -
683 -Disable/Enable the confirmation mode
684 -
685 -* (% style="color:blue" %)**AT Command:**
686 -
687 -(% style="color:#037691" %)**AT+CFM=xx. **
688 -
689 -
690 -**~ Example:**
691 -
692 - AT+ CFM=0    **~-~->   ** Disable confirmation
693 -
694 - AT+ CFM=1    **~-~->  ** Enable confirmation
695 -
696 -
697 -* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
698 -
699 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
700 -
701 -
702 -
703 -= 4. Setting for Different Scenarios =
704 -
705 -
706 -
707 -= 5. Upload Firmware =
708 -
709 -
710 -== 5.1 Firmware Change Log ==
711 -
712 -
713 -**[[See this link>>url:https://github.com/dragino/TrackerD]]**
714 -
715 -
716 -
717 -== 5.2 How to upgrade firmware ==
718 -
719 -
720 -User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
721 -
722 -
723 -(% style="color:blue" %)**Step1:  **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
724 -
725 -
726 -(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC.
727 -
728 -After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
729 -
730 -
731 -(% 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]]
732 -
733 -
734 -(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
735 -
736 -
737 -[[image:1664503563660-578.png]]
738 -
739 -
740 -[[image:1664503574618-659.png]]
741 -
742 -
743 -(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
744 -
745 -[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
746 -
747 -
748 -Users need to use below files:
749 -
750 -boot_app0.bin @0e000
751 -
752 -ESP_LORA-eeprom-class.bin @ 0x10000
753 -
754 -
755 -[[image:1664503593459-435.png]]
756 -
757 -
758 -
759 -After upgrade finish, it will show finish as below:
760 -
761 -[[image:1664503611848-385.png]]
762 -
763 -
764 -
765 -= 6. Developer Guide =
766 -
767 -
768 -== 6.1 Compile Source Code ==
769 -
770 -
771 -=== 6.1.1 Set up ARDUINO compile environment ===
772 -
773 -
774 -* 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]]
775 -
776 -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]]
777 -
778 -
779 -[[image:1664503635019-941.png]]
780 -
781 -
782 -* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) find the esp32 information and install it.
783 -
784 -[[image:1664503715811-892.png]]
785 -
786 -
787 -
788 -* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
789 -
790 -Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
791 -
792 -
793 -[[image:1664503752288-974.png]]
794 -
795 -
796 -
797 -== 6.2 Source Code ==
798 -
799 -
800 -* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
801 -
802 -[[image:1664503794261-827.png]]
803 -
804 -
805 -
806 -* (% style="color:blue" %)**Click to upload**
807 -
808 -[[image:1664503808294-336.png]]
809 -
810 -
811 -
812 -* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
813 -
814 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
815 -
816 -
817 -
818 818  = 7.  FAQ =
819 819  
820 820  
68 +
821 821  == 7.1 How to change the LoRa Frequency Bands/Region? ==
822 822  
823 823  
824 -User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
72 +User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
825 825  
826 826  
827 827  
... ... @@ -843,6 +843,8 @@
843 843  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
844 844  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
845 845  
94 +
95 +
846 846  = 8.  Order Info =
847 847  
848 848  
... ... @@ -851,6 +851,7 @@
851 851  (% style="color:blue" %)**XXX**(%%): The default frequency band
852 852  
853 853  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
104 +* (% style="color:red" %)**CN470**(%%): Default frequency band CN470
854 854  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
855 855  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
856 856  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
... ... @@ -858,25 +858,37 @@
858 858  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
859 859  * (% style="color:red" %)**US915**(%%): Default frequency band US915
860 860  
112 +
113 +
114 +
861 861  = 9.  Packing Info =
862 862  
863 863  
864 864  **Package Includes**:
865 865  
866 -* TrackerD LoRaWAN GPS/BLE Tracker x 1
867 -* USB recharge & program cable x 1
120 +* TrackerD x 1
121 +* Rechargeable cable x 1
122 +* Program Cable x 1
868 868  
869 869  **Dimensions and Weight**:
870 870  
871 -* Device Size: 85 x 48 x 15 cm
872 -* Weight: 50g
126 +* Device Size: 85 x 48 x 15 mm/pcs
127 +* Weight: 55g/pcs
873 873  
874 -= 10. Support =
875 875  
876 876  
131 +
132 +
133 += 10. Support =
134 +
877 877  * 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.
878 -* 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]]
136 +* 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
879 879  
138 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
139 +
140 +
141 +
142 +
880 880  = 11.  Reference =
881 881  
882 882  
1664501652064-326.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -143.9 KB
Content
1664501677253-891.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -202.7 KB
Content
1664501711466-918.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -62.0 KB
Content
1664501721248-725.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -55.6 KB
Content
1664501734705-405.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -64.1 KB
Content
1664501784668-703.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -62.0 KB
Content
1664501958445-288.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.1 KB
Content
1664502116362-706.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -56.0 KB
Content
1664502166010-515.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -41.3 KB
Content
1664502425687-834.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -38.2 KB
Content
1664502649601-895.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -59.2 KB
Content
1664502676891-606.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -64.3 KB
Content
1664502695771-538.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -54.7 KB
Content
1664502715371-321.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.9 KB
Content
1664502835802-546.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -37.8 KB
Content
1664502854406-763.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -14.3 KB
Content
1664502999401-486.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -916.7 KB
Content
1664503022490-662.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -133.6 KB
Content
1664503035713-500.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -354.0 KB
Content
1664503047675-651.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -199.1 KB
Content
1664503563660-578.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -38.1 KB
Content
1664503574618-659.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -139.8 KB
Content
1664503593459-435.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.3 KB
Content
1664503611848-385.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -175.9 KB
Content
1664503635019-941.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -161.8 KB
Content
1664503715811-892.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.6 KB
Content
1664503752288-974.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -112.6 KB
Content
1664503794261-827.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -119.5 KB
Content
1664503808294-336.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -161.6 KB
Content
1664503824081-592.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.4 KB
Content
1664503831430-500.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
1664505654417-133.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.5 KB
Content