Skip to Content
Last modified by Xiaoling on 2025/04/27 16:48
From version 18.1
edited by Xiaoling
on 2022/09/30 09:00
Change comment: Uploaded new attachment "1664499635206-262.png", version {1}
To version 66.2
edited by Xiaoling
on 2022/10/09 15:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,3 +1,9 @@
1 +(% style="text-align:center" %)
2 +[[image:1664505654417-133.png]]
3 +
4 +
5 +
6 +
1 1  (% class="wikigeneratedid" %)
2 2  **Table of Contents:**
3 3  
... ... @@ -6,19 +6,18 @@
6 6  
7 7  
8 8  
9 -
10 10  = 1.  Introduction =
11 11  
12 -== 1.1  OverView ==
13 13  
18 +== 1.1  What is TrackerD ==
14 14  
20 +
15 15  (((
16 16  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**.
17 17  )))
18 18  
19 19  (((
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 -)))
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.
22 22  
23 23  (((
24 24  TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.
... ... @@ -25,8 +25,9 @@
25 25  )))
26 26  
27 27  (((
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.
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.
29 29  )))
35 +)))
30 30  
31 31  (((
32 32  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.
... ... @@ -34,109 +34,921 @@
34 34  
35 35  )))
36 36  
37 -[[image:image-20220906111043-1.png]]
43 +[[image:1664499921684-770.png]]
38 38  
39 39  
40 -== 1.2  Features ==
46 +(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
41 41  
42 42  
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
56 56  
50 +== 1.2 Specifications ==
57 57  
58 58  
59 -== 1.3  Applications ==
53 +(% style="color:blue" %)**Micro Controller:**
60 60  
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
61 61  
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 +== 1.3  Features ==
101 +
102 +
103 +* LoRaWAN 1.0.3 Class A
104 +* ESP32 PICO D4
105 +* SX1276/78 Wireless Chip
106 +* Arduino IDE Compatible
107 +* Open source hardware / software
108 +* Regular/ Real-time GPS,BLE,WIFI tracking
109 +* Built-in3 axis accelerometer (LIS3DH)
110 +* Humidity / temperature sensor : GXCAS Technology GXHT3X
111 +* Motion sensing capability
112 +* Power Monitoring
113 +* Charging circuit via USB port
114 +* 1000mA Li-on Battery power
115 +* Tri-color LED, Alarm button
116 +* Datalog
117 +
118 +== 1.4  Applications ==
119 +
120 +
62 62  * Logistics and Supply Chain Management
63 63  * Human tracking
64 64  
124 += 2.1 Use TrackerD =
65 65  
66 66  
67 -= 2.  Use TrackerD in LoRaWAN network =
127 +== 2.1 How it works? ==
68 68  
69 69  
70 -== 2.1  LED ==
130 +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.
71 71  
72 72  
73 -== 2.2  Button ==
74 74  
134 +== 2.2 Quick guide to connect to LoRaWAN server ==
75 75  
76 -= 3.  Update Firmware =
77 77  
137 +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. 
78 78  
79 -== 3.1  Method 1: Update BIN file ==
80 80  
140 +[[image:1664501652064-326.png]]
81 81  
82 -(% style="color:blue" %)**Step1:  **(%%)Connect TrackerD and PC via TypeC cable directly.
83 83  
84 84  
85 -(% style="color:blue" %)**Step2:**(%%)  Install CH9102 driver in the PC.
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:
86 86  
87 -After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
88 88  
147 +(% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
89 89  
90 -(% style="color:blue" %)**Step3：**(%%) Download and Install Flash Tool from :
149 +Each TrackerD is shipped with a sticker with the default device EUI as below:
91 91  
92 -[[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]]
93 93  
152 +[[image:1664501677253-891.png]]
94 94  
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]]
162 +
163 +
164 +
165 +[[image:1664501721248-725.png]]
166 +
167 +
168 +[[image:1664501734705-405.png]]
169 +
170 +
171 +
172 +**__Add APP KEY and DEV EUI:__**
173 +
174 +
175 +[[image:1664501784668-703.png]]
176 +
177 +
178 +
179 +
180 +(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
181 +
182 +
183 +(% 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.
184 +
185 +
186 +== 2.3 Positioning Mode(SMOD) ==
187 +
188 +Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
189 +
190 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
191 +* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
192 +* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
193 +
194 +Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
195 +
196 +
197 +== 2.3 Uplink Payload ==
198 +
199 +
200 +=== 2.3.1 Uplink FPORT~=5, Device Status ===
201 +
202 +
203 +Uplink the device configures with FPORT=5. Once LGT92 Joined the network, it will uplink this message to the server. After first uplink, LHT52 will uplink Device Status every 12 hours.
204 +
205 +
206 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
207 +|=(% scope="row" style="width: 108px;" %)**Size(bytes)**|=(% style="width: 82px;" %)**1**|=(% style="width: 83px;" %)**2**|=(% style="width: 94px;" %)**1**|=(% style="width: 84px;" %)**1**|=(% style="width: 44px;" %)2|=(% style="width: 63px;" %)**2**|=(% style="width: 60px;" %)1
208 +|=(% 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
209 +
210 +[[image:1665301570342-765.png]]
211 +
212 +
213 +Example Payload (FPort=5):  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT52%20-%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/image-20220621105116-11.png?rev=1.1||alt="image-20220621105116-11.png"]]
214 +
215 +**Sensor Model**: For TrackerD, this value is 0x13.
216 +
217 +**Firmware Version**: 0x0100, Means: v1.0.0 version.
218 +
219 +**Frequency Band**:
220 +
221 +*0x01: EU868
222 +
223 +*0x02: US915
224 +
225 +*0x03: IN865
226 +
227 +*0x04: AU915
228 +
229 +*0x05: KZ865
230 +
231 +*0x06: RU864
232 +
233 +*0x07: AS923
234 +
235 +*0x08: AS923-1
236 +
237 +*0x09: AS923-2
238 +
239 +*0x0a: AS923-3
240 +
241 +**Sub-Band**: value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
242 +
243 +**BAT**: shows the battery voltage for TrackerD.
244 +
245 +Ex1: 0x0B3A = 2874mV
246 +
247 +Use can also get the Device Status uplink through the downlink command:
248 +
249 +
250 +
251 +=== 2.3.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
252 +
253 +
254 +User can use **AT+SMOD=1,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, please note that 15 bytes won't work on DR0 on US915/AU915 frequency band.
255 +
256 +
257 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
258 +|=(% scope="row" style="width: 50px;" %)(((
259 +**Size(bytes)**
260 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
261 +2
262 +)))|(% style="width:87px" %)(((
263 +2
264 +)))
265 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
266 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
267 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
268 +
269 +[[image:1665301636888-168.png]]
270 +
271 +
272 +==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
273 +
274 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
275 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
276 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
277 +
278 +==== (% style="color:blue" %)**FLAG:**(%%) ====
279 +
280 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
281 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
282 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
283 +
284 +**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
285 +
286 +
287 +==== (% style="color:blue" %)**Location info:**(%%) ====
288 +
289 +* Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
290 +* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
291 +
292 +(% style="color:red" %)**Important note:**
293 +
294 +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.
295 +
296 +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:
297 +
298 +
299 +[[image:1664502116362-706.png]]
300 +
301 +
302 +3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
303 +
304 +[[image:1664502166010-515.png]]
305 +
306 +
307 +
308 +==== (% style="color:blue" %)**Alarm:**(%%) ====
309 +
310 +Example:  0x4B & 0x40 >> 6 = 0x01
311 +
312 +
313 +==== (% style="color:blue" %)**BAT:**(%%) ====
314 +
315 +Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
316 +
317 +(((
318 +The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
319 +)))
320 +
321 +* > 4.0v :  80% ~~ 100%
322 +* 3.85v ~~3.99v:  60% ~~ 80%
323 +* 3.70v ~~ 3.84v:  40% ~~ 60%
324 +* 3.40v ~~ 3.69v:  20% ~~ 40%
325 +* < 3.39v:  0~~20%
326 +
327 +==== (% style="color:blue" %)**LON:**(%%) ====
328 +
329 +Enable/Disable LED activity for uplink
330 +
331 +(((
332 +0x00:  Disable LED indicator.
333 +)))
334 +
335 +(((
336 +0x01:  Enable LED indicator (Default Value)
337 +)))
338 +
339 +
340 +==== (% style="color:blue" %)**Hum:**(%%) ====
341 +
342 +0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
343 +
344 +
345 +==== (% style="color:blue" %)**Tem:**(%%) ====
346 +
347 +011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
348 +
349 +
350 +
351 +=== 2.3.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
352 +
353 +
354 +The default uplink payload includes totally 11 bytes. The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
355 +
356 +
357 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
358 +|=(% scope="row" style="width: 50px;" %)(((
359 +**Size(bytes)**
360 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
361 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
362 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
363 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
364 +
365 +
366 +(% class="wikigeneratedid" %)
367 +[[image:1665301687277-443.png]]
368 +
369 +
370 +
371 +=== 2.3.4  Uplink FPORT~=4, History GNSS Positioning ===
372 +
373 +
374 +Set [[PNACKMD=1>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H4.13AutoSendNone-ACKmessages]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
375 +
376 +
377 +**Note for this mode:**
378 +
379 +* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
380 +* b) TrackerD will send data in **CONFIRMED Mode** when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
381 +
382 +The payload is 15 bytes, as below.
383 +
384 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
385 +|=(% scope="row" %)(((
386 +**Size(bytes)**
387 +)))|4|4|2|1|1|1|1|1
388 +|=**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|[[Year>>path:#Alarm]]|Month|Day|Hous|Min|[[Sen>>path:#Pitch]]
389 +
390 +[[image:1665301786397-168.png]]
391 +
392 +
393 +
394 +=== 2.3.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
395 +
396 +
397 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
398 +|=(% scope="row" style="width: 60px;" %)(((
399 +**Size(bytes)**
400 +)))|(% style="width:30px" %)16|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:120px" %)2|(% style="width:50px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1
401 +|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
402 +iBeacon MAJOR
403 +)))|(% style="width:63px" %)(((
404 +iBeacon MINOR
405 +)))|(% style="width:71px" %)(((
406 +iBeacon Measured Power
407 +)))|(% style="width:50px" %)(((
408 +iBeacon RSSI
409 +)))|(% style="width:47px" %)(((
410 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
411 +)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
412 +
413 +[[image:1664502425687-834.png]]
414 +
415 +
416 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
417 +* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
418 +* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
419 +* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
420 +* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
421 +* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
422 +* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
423 +
424 +=== 2.3.5 Add Payload format in TTN V3 ===
425 +
426 +
427 +In TTN V3, use can add a custom payload so it shows friendly.
428 +
429 +In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
430 +
431 +
432 +[[image:1664502649601-895.png]]
433 +
434 +
435 +Add the decoder from this link:
436 +
437 +
438 +Save the change the uplink message will be parsed. As below:
439 +
440 +[[image:1664502676891-606.png]]
441 +
442 +
443 +
444 +== 2.4 Integrate with Datacake ==
445 +
446 +
447 +(((
448 +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.
449 +)))
450 +
451 +(((
452 +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]]
453 +)))
454 +
455 +
456 +[[image:1664502695771-538.png]]
457 +
458 +
459 +
460 +== 2.5 Integrate with Tago ==
461 +
462 +
463 +(((
464 +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.
465 +)))
466 +
467 +(((
468 +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]]
469 +)))
470 +
471 +
472 +[[image:1664502715371-321.png]]
473 +
474 +
475 +
476 +== 2.6 Datalog Feature ==
477 +
478 +total 273 entries,by default disable
479 +
480 +== 2.6 Alarm Mode ==
481 +
482 +
483 +(((
484 +User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
485 +)))
486 +
487 +
488 +(((
489 +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.
490 +)))
491 +
492 +
493 +(((
494 +Two ways to exit alarm mode:
495 +)))
496 +
497 +* Server send a downlink command to exit.
498 +* User fast press the RED button 10 times.
499 +
500 +(((
501 +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.
502 +)))
503 +
504 +
505 +
506 +== 2.7 Transport Mode ==
507 +
508 +
509 +In Transport Mode, TrackerD will check if there is motion. If there is no motion, device will send uplinks every 20 minutes. If there is motion, device will send uplink every 5 minutes.
510 +
511 +
512 +== 2.8 LED Status ==
513 +
514 +
515 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
516 +|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
517 +|(% 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
518 +|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
519 +|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
520 +|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
521 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
522 +|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
523 +|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
524 +|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
525 +|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes
526 +|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
527 +|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
528 +
529 +== 2.9 Button Function ==
530 +
531 +
532 +(% style="color:blue" %)**RESET button:**
533 +
534 +[[image:1664502835802-546.png]]
535 +
536 +Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
537 +
538 +
539 +(% style="color:red" %)**RED button:**
540 +
541 +[[image:1664502854406-763.png]]
542 +
543 +
544 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
545 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
546 +|(% 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"]]
547 +|(% 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
548 +|(% 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.
549 +
550 +== 2.10 USB Port Function ==
551 +
552 +
553 +The USB interface of TrackerD has below functions:
554 +
555 +* Power on the device
556 +* Recharge the battery
557 +* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
558 +* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
559 +
560 += 3. Configure TrackerD via AT command or LoRaWAN downlink =
561 +
562 +
563 +User can configure TrackerD via AT Command or LoRaWAN Downlink.
564 +
565 +LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
566 +
567 +
568 +
569 +== 3.1 Access AT Command ==
570 +
571 +
572 +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.
573 +
574 +
575 +[[image:1664502999401-486.png]]
576 +
577 +
578 +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:
579 +
580 +
581 +[[image:1664503022490-662.png]]
582 +
583 +
584 +
585 +[[image:1664503035713-500.png]]
586 +
587 +
588 +
589 +[[image:1664503047675-651.png]]
590 +
591 +
592 +
593 +== 3.2 Command Set ==
594 +
595 +
596 +=== 3.2.1 Set Transmit Interval ===
597 +
598 +
599 +Set device uplink interval.
600 +
601 +* (% style="color:blue" %)**AT Command:**
602 +
603 +(% style="color:#037691" %)**AT+TDC=xxx **
604 +
605 +Example:  AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
606 +
607 +
608 +* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**
609 +
610 +(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
611 +
612 +
613 +
614 +=== 3.2.2 Set Alarm Packet transmission interval ===
615 +
616 +
617 +Set alarm packet transmit interval
618 +
619 +* (% style="color:blue" %)**AT Command:**
620 +
621 +(% style="color:#037691" %)**AT+ATDC=xx. **
622 +
623 +Example:  AT+ATDC=60000  **~-~->    ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
624 +
625 +
626 +* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**
627 +
628 +(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
629 +
630 +
631 +
632 +=== 3.2.3 Set Transport Mode Packet transmission interval ===
633 +
634 +
635 +Set Transport Mode packet transmit interval
636 +
637 +* (% style="color:blue" %)**AT Command:**
638 +
639 +(% style="color:#037691" %)**AT+MTDC=xx. **
640 +
641 +Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
642 +
643 +
644 +* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
645 +
646 +(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
647 +
648 +
649 +
650 +=== 3.2.4 Exit Alarm ===
651 +
652 +
653 +Server send downlink command to exit Alarm mode
654 +
655 +* (% style="color:blue" %)**AT Command: No AT Command**
656 +
657 +* (% style="color:blue" %)**Downlink Payload (prefix 0x02):**
658 +
659 +(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
660 +
661 +
662 +
663 +=== 3.2.5 Disable/Enable LED flash ===
664 +
665 +
666 +Disable/Enable LED for position, downlink and uplink
667 +
668 +* (% style="color:blue" %)**AT Command:**
669 +
670 +(% style="color:#037691" %)**AT+LON=xx.  (Disable (0), Enable (1), default:1)**
671 +
672 +Example: AT+LON=0  **~-~-> ** Disable LED for position, downlink and uplink.
673 +
674 +
675 +* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**
676 +
677 +(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
678 +
679 +
680 +
681 +=== 3.2.6 Disable/Enable Transport Mode ===
682 +
683 +
684 +Users can use this feature to enable/disable Transport Mode.
685 +
686 +* (% style="color:blue" %)**AT Command:**
687 +
688 +(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
689 +
690 +Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
691 +
692 +
693 +* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
694 +
695 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
696 +
697 +
698 +
699 +=== 3.2.7 Set Positioning Mode ===
700 +
701 +
702 +SMOD define the how TrackerD scan and uplink data:
703 +
704 +
705 +* (% style="color:blue" %)**AT Command:**
706 +
707 +(% style="color:#037691" %)**AT+SMOD=aa,bb**
708 +
709 +(% style="color:#037691" %)** aa:**
710 +
711 +* (% style="color:#037691" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
712 +* (% style="color:#037691" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
713 +* (% style="color:#037691" %)**3: GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning
714 +
715 +(% style="color:#037691" %)**bb:**
716 +
717 +(% style="color:#037691" %)** if aa = 1: **
718 +
719 +* (% style="color:#037691" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
720 +* (% style="color:#037691" %)**1 :**(%%)  GPS +BAT State
721 +
722 +(% style="color:#037691" %)** if aa = 2: **
723 +
724 +* (% style="color:#037691" %)**3 :  **(%%)(iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
725 +
726 + **Example:**
727 +
728 + AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
729 +
730 + AT+ SMOD =1,1    **~-~->**  GPS +BAT State
731 +
732 + AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
733 +
734 +
735 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
736 +
737 +(% style="color:#037691" %)**0xA5 01 00**    (%%) ~/~/  Same as AT+ SMOD =1,0
738 +
739 +
740 +
741 +=== 3.2.8 Set MAX GPS position time ===
742 +
743 +
744 +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.
745 +
746 +
747 +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.
748 +
749 +
750 +* (% style="color:blue" %)**AT Command:**
751 +
752 +(% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
753 +
754 +Example:  AT+FTIME=150
755 +
756 +
757 +* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
758 +
759 +(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
760 +
761 +
762 +
763 +=== 3.3.9 Set PDOP value for GPS fix accuracy ===
764 +
765 +
766 +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.
767 +
768 +
769 +A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
770 +
771 +
772 +* (% style="color:blue" %)**AT Command:**
773 +
774 +(% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~->  ** Set PDOP to 2.5
775 +
776 +
777 +* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**
778 +
779 +(% style="color:#037691" %)**0xAD 00 0A**   (%%) ~/~/  Set AT+PDOP=1  (0x0A / 10 =1)
780 +
781 +(% style="color:#037691" %)**0xAD 00 19**   (%%) ~/~/  Set AT+PDOP=2.5    (0x19 / 10 =2.5)
782 +
783 +(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
784 +
785 +
786 +
787 +Disable/Enable the confirmation mode
788 +
789 +* (% style="color:blue" %)**AT Command:**
790 +
791 +(% style="color:#037691" %)**AT+CFM=xx. **
792 +
793 +
794 +**~ Example:**
795 +
796 + AT+ CFM=0    **~-~->   ** Disable confirmation
797 +
798 + AT+ CFM=1    **~-~->  ** Enable confirmation
799 +
800 +
801 +* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
802 +
803 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
804 +
805 +
806 +
807 += 4. Setting for Different Scenarios =
808 +
809 +
810 +
811 += 5. Upload Firmware =
812 +
813 +
814 +== 5.1 Firmware Change Log ==
815 +
816 +
817 +**[[See this link>>url:https://github.com/dragino/TrackerD]]**
818 +
819 +
820 +
821 +== 5.2 How to upgrade firmware ==
822 +
823 +
824 +User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
825 +
826 +
827 +(% style="color:blue" %)**Step1:  **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
828 +
829 +
830 +(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC.
831 +
832 +After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
833 +
834 +
835 +(% 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]]
836 +
837 +
95 95  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
96 96  
97 -[[image:image-20220712083115-1.png||height="238" width="1071"]]
98 98  
841 +[[image:1664503563660-578.png]]
99 99  
100 -[[image:image-20220712083115-2.png]]
101 101  
844 +[[image:1664503574618-659.png]]
102 102  
103 -(% style="color:blue" %)**Step5:** (%%) Select the bin file , com port and proper SPI configure. and click Start.
104 104  
105 -Bin file can be downloaded from:  [[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
847 +(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
106 106  
849 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
107 107  
108 -**Users need to use below files:**
109 109  
110 -* boot_app0.bin @0e000
111 -* ESP_LORA-eeprom-class.bin @ 0x10000
852 +Users need to use below files:
112 112  
113 -[[image:image-20220712083115-3.png]]
854 +boot_app0.bin @0e000
114 114  
856 +ESP_LORA-eeprom-class.bin @ 0x10000
115 115  
116 -After upgrade finish, it will shows below:
117 117  
118 -[[image:image-20220712083115-4.png]]
859 +[[image:1664503593459-435.png]]
119 119  
120 120  
121 121  
122 -= 4.  FAQ =
863 +After upgrade finish, it will show finish as below:
123 123  
124 -== 4.1  Where can i find the source files for TrackerD? ==
865 +[[image:1664503611848-385.png]]
125 125  
126 126  
127 -Software & Hardware Source: [[https:~~/~~/github.com/dragino/TrackerD >>https://github.com/dragino/TrackerD]]
128 128  
869 += 6. Developer Guide =
129 129  
130 130  
131 -= 5.  Order Info =
872 +== 6.1 Compile Source Code ==
132 132  
133 133  
875 +=== 6.1.1 Set up ARDUINO compile environment ===
876 +
877 +
878 +* **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]]**
879 +
880 +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]]
881 +
882 +
883 +[[image:1664503635019-941.png]]
884 +
885 +
886 +* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
887 +
888 +[[image:1664503715811-892.png]]
889 +
890 +
891 +
892 +* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
893 +
894 +Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
895 +
896 +
897 +[[image:1664503752288-974.png]]
898 +
899 +
900 +
901 +== 6.2 Source Code ==
902 +
903 +
904 +* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
905 +
906 +[[image:1664503794261-827.png]]
907 +
908 +
909 +
910 +* (% style="color:blue" %)**Click to upload**
911 +
912 +[[image:1664503808294-336.png]]
913 +
914 +
915 +
916 +* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
917 +
918 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
919 +
920 +
921 +
922 += 7.  FAQ =
923 +
924 +
925 +== 7.1 How to change the LoRa Frequency Bands/Region? ==
926 +
927 +
928 +User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
929 +
930 +
931 +
932 +== 7.2 What is the pin mapping for the USB program cable? ==
933 +
934 +
935 +[[image:1664499635206-262.png]]
936 +
937 +
938 +
939 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
940 +|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
941 +|(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
942 +|(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
943 +|(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
944 +|(% style="width:118px" %)A1,B1,A12,B12|(% style="width:67px" %)Black|(% style="width:123px" %)GND
945 +|(% style="width:118px" %)A5|(% style="width:67px" %)Purple|(% style="width:123px" %)MTDC/GOIO13
946 +|(% style="width:118px" %)B5|(% style="width:67px" %)Blue|(% style="width:123px" %)MTDC/GPIO12
947 +|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
948 +|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
949 +
950 += 8.  Order Info =
951 +
952 +
134 134  Part Number: (% style="color:blue" %)**TrackerD-XXX**
135 135  
136 136  (% style="color:blue" %)**XXX**(%%): The default frequency band
137 137  
138 138  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
139 -* (% style="color:red" %)**CN470**(%%): Default frequency band CN470
140 140  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
141 141  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
142 142  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
... ... @@ -144,24 +144,26 @@
144 144  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
145 145  * (% style="color:red" %)**US915**(%%): Default frequency band US915
146 146  
965 += 9.  Packing Info =
147 147  
148 -= 6.  Packing Info =
149 149  
968 +(% style="color:#037691" %)**Package Includes**:
150 150  
151 -**Package Includes**:
970 +* TrackerD LoRaWAN GPS/BLE Tracker x 1
971 +* USB recharge & program cable x 1
152 152  
153 -* TrackerD x 1
154 -* Rechargeable cable x 1
155 -* Program Cable x 1
973 +(% style="color:#037691" %)**Dimensions and Weight**:
156 156  
157 -**Dimensions and Weight**:
975 +* Device Size: 85 x 48 x 15 cm
976 +* Weight: 50g
158 158  
159 -* Device Size: 85 x 48 x 15 mm/pcs
160 -* Weight: 55g/pcs
978 += 10. Support =
161 161  
162 162  
981 +* 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.
982 +* 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]].
163 163  
164 -= 7.  Reference =
984 += 11.  Reference =
165 165  
166 166  
167 167  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
... ... @@ -168,3 +168,4 @@
168 168  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
169 169  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
170 170  
991 +
1664499921684-770.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.9 KB
Content
1664501652064-326.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.9 KB
Content
1664501677253-891.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +202.7 KB
Content
1664501711466-918.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +62.0 KB
Content
1664501721248-725.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +55.6 KB
Content
1664501734705-405.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +64.1 KB
Content
1664501784668-703.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +62.0 KB
Content
1664501958445-288.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +74.1 KB
Content
1664502116362-706.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +56.0 KB
Content
1664502166010-515.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +41.3 KB
Content
1664502425687-834.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +38.2 KB
Content
1664502649601-895.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +59.2 KB
Content
1664502676891-606.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +64.3 KB
Content
1664502695771-538.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +54.7 KB
Content
1664502715371-321.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +79.9 KB
Content
1664502835802-546.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +37.8 KB
Content
1664502854406-763.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +14.3 KB
Content
1664502999401-486.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +916.7 KB
Content
1664503022490-662.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +133.6 KB
Content
1664503035713-500.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +354.0 KB
Content
1664503047675-651.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +199.1 KB
Content
1664503563660-578.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +38.1 KB
Content
1664503574618-659.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +139.8 KB
Content
1664503593459-435.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.3 KB
Content
1664503611848-385.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +175.9 KB
Content
1664503635019-941.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +161.8 KB
Content
1664503715811-892.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +36.6 KB
Content
1664503752288-974.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +112.6 KB
Content
1664503794261-827.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +119.5 KB
Content
1664503808294-336.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +161.6 KB
Content
1664503824081-592.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.4 KB
Content
1664503831430-500.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +147.8 KB
Content
1664505654417-133.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.5 KB
Content
1665301570342-765.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.6 KB
Content
1665301636888-168.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +36.6 KB
Content
1665301687277-443.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.6 KB
Content
1665301786397-168.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.6 KB
Content
image-20221006181316-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +17.7 KB
Content
image-20221006181357-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +88.0 KB
Content