Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 21 removed)
  • 1667288597595-714.png
  • image-20221102140621-1.png
  • image-20221102140638-2.png
  • image-20221102140704-3.png
  • image-20221102140712-4.png
  • image-20221102140748-5.png
  • image-20221102140801-6.png
  • image-20221107145243-1.png
  • image-20221116111844-1.png
  • image-20221116111844-2.png
  • image-20221116111844-3.png
  • image-20221116111844-4.png
  • image-20221116111844-5.png
  • image-20221118104359-1.png
  • image-20221118105220-2.png
  • image-20221118105249-3.png
  • image-20221118105402-4.png
  • image-20221122100004-1.png
  • image-20221122100004-2.png
  • image-20221122100004-3.png
  • image-20221122100004-4.png

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Edwin
	1	+XWiki.Xiaoling

Content

...	...	@@ -1,5 +1,5 @@
1	1	(% style="text-align:center" %)
2		-[[image:1664505654417-133.png||_mstalt="293696"]]
	2	+[[image:1664505654417-133.png]]
3	3
4	4
5	5
...	...	@@ -14,6 +14,7 @@
14	14
15	15	= 1.  Introduction =
16	16
	17	+
17	17	== 1.1  What is TrackerD ==
18	18
19	19
...	...	@@ -39,12 +39,13 @@
39	39
40	40	)))
41	41
42		-[[image:1664499921684-770.png||_mstalt="298194"]]
	43	+[[image:1664499921684-770.png]]
43	43
44	44
45	45	(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
46	46
47	47
	49	+
48	48	== 1.2 Specifications ==
49	49
50	50
...	...	@@ -119,8 +119,9 @@
119	119	* Logistics and Supply Chain Management
120	120	* Human tracking
121	121
122		-= 2.  Use TrackerD =
	124	+= 2.1 Use TrackerD =
123	123
	126	+
124	124	== 2.1 How it works? ==
125	125
126	126
...	...	@@ -127,6 +127,7 @@
127	127	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.
128	128
129	129
	133	+
130	130	== 2.2 Quick guide to connect to LoRaWAN server ==
131	131
132	132
...	...	@@ -133,7 +133,7 @@
133	133	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.
134	134
135	135
136		-[[image:1664501652064-326.png||_mstalt="293306"]]
	140	+[[image:1664501652064-326.png]]
137	137
138	138
139	139
...	...	@@ -145,7 +145,7 @@
145	145	Each TrackerD is shipped with a sticker with the default device EUI as below:
146	146
147	147
148		-[[image:1664501677253-891.png||_mstalt="296569"]]
	152	+[[image:1664501677253-891.png]]
149	149
150	150
151	151	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
...	...	@@ -154,14 +154,14 @@
154	154	**__Add APP EUI in the application:__**
155	155
156	156
157		-[[image:1664501711466-918.png||_mstalt="295828"]]
	161	+[[image:1664501711466-918.png]]
158	158
159	159
160	160
161		-[[image:1664501721248-725.png||_mstalt="294450"]]
	165	+[[image:1664501721248-725.png]]
162	162
163	163
164		-[[image:1664501734705-405.png||_mstalt="293306"]]
	168	+[[image:1664501734705-405.png]]
165	165
166	166
167	167
...	...	@@ -168,34 +168,34 @@
168	168	**__Add APP KEY and DEV EUI:__**
169	169
170	170
171		-[[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"]]
	175	+[[image:1664501784668-703.png]]
172	172
173	173
174	174
175		-(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
176	176
177		-(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
	180	+(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
178	178
179		-[[image:1664502835802-546.png||_mstalt="295061"]]
180	180
181		-
182	182	(% 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.
183	183
184	184
	186	+
185	185	== 2.3  Positioning Mode(SMOD) ==
186	186
187	187
188	188	Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
189	189
190		-* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
191		-* (% style="color:#037691" %)**BLE or WiFi ONLY:            **(%%)** **Only obtain iBeacon info via BLE and uplink  or obtain wifi ssid info via WiFi 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.
	192	+* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
	193	+* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
	194	+* (% 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	193
194	194	Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
195	195
196	196
	199	+
197	197	== 2.4  Uplink Payload ==
198	198
	202	+
199	199	=== 2.4.1 Uplink FPORT~=5, Device Status ===
200	200
201	201
...	...	@@ -208,7 +208,7 @@
208	208	|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
209	209	|=(% 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
210	210
211		-[[image:1665301570342-765.png||_mstalt="294580"]]
	215	+[[image:1665301570342-765.png]]
212	212
213	213
214	214	(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
...	...	@@ -251,7 +251,7 @@
251	251
252	252	(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
253	253
254		-(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
	258	+(% border="1.5" style="background-color:#ffffcc; color:green; width:280px" %)
255	255	|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
256	256	|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
257	257
...	...	@@ -275,13 +275,11 @@
275	275
276	276	(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
277	277
278		-(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)
279	279
280		-
281	281	(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
282	282
283		-(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
284		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
	285	+(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %)
	286	+|=(% scope="row" style="width: 77px;" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:92px" %)1 Bit|(% style="width:48px" %)1 Bit|(% style="width:126px" %)1 Bit
285	285	|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
286	286
287	287	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
...	...	@@ -290,12 +290,12 @@
290	290	Users can use **AT+SMOD=1,0,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
291	291
292	292
293		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
294		-|=(% scope="row" style="width: 60px;" %)(((
	295	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
	296	+|=(% scope="row" style="width: 50px;" %)(((
295	295	**Size(bytes)**
296		-)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
	298	+)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
297	297	2
298		-)))|(% style="width:30px" %)(((
	300	+)))|(% style="width:87px" %)(((
299	299	2
300	300	)))
301	301	|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
...	...	@@ -302,7 +302,7 @@
302	302	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
303	303	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
304	304
305		-[[image:1665301636888-168.png||_mstalt="298012"]]
	307	+[[image:1665301636888-168.png]]
306	306
307	307
308	308	==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
...	...	@@ -313,8 +313,8 @@
313	313
314	314	==== (% style="color:blue" %)**FLAG:**(%%) ====
315	315
316		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
317		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
	318	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
	319	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
318	318	|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
319	319
320	320	**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
...	...	@@ -332,12 +332,12 @@
332	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	333
334	334
335		-[[image:1664502116362-706.png||_mstalt="293306"]]
	337	+[[image:1664502116362-706.png]]
336	336
337	337
338	338	3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
339	339
340		-[[image:1664502166010-515.png||_mstalt="291395"]]
	342	+[[image:1664502166010-515.png]]
341	341
342	342
343	343
...	...	@@ -390,6 +390,7 @@
390	390	)))
391	391
392	392
	395	+
393	393	==== (% style="color:blue" %)**Hum:**(%%) ====
394	394
395	395	0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
...	...	@@ -400,6 +400,7 @@
400	400	011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
401	401
402	402
	406	+
403	403	=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
404	404
405	405
...	...	@@ -406,18 +406,19 @@
406	406	The default uplink payload includes total 11 bytes (**AT+SMOD=1,1,0**). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
407	407
408	408
409		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
410		-|=(% scope="row" style="width: 60px;" %)(((
	413	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
	414	+|=(% scope="row" style="width: 50px;" %)(((
411	411	**Size(bytes)**
412		-)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
	416	+)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
413	413	|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
414	414	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
415	415	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
416	416
417	417	(% class="wikigeneratedid" %)
418		-[[image:1665301687277-443.png||_mstalt="296140"]]
	422	+[[image:1665301687277-443.png]]
419	419
420	420
	425	+
421	421	=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
422	422
423	423
...	...	@@ -427,20 +427,21 @@
427	427	(% style="color:red" %)**Note for this mode:**
428	428
429	429	* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
430		-* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=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.
	435	+* b) TrackerD will send data in (% style="color:blue" %)**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.
431	431	* c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL
432	432
433	433	The payload is 15 bytes, as below.
434	434
435		-(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
	440	+(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
436	436	|=(% scope="row" %)(((
437	437	**Size(bytes)**
438	438	)))|4|4|2|1|1|1|1|1
439	439	|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
440	440
441		-[[image:image-20221009160309-2.png||_mstalt="429312"]]
	446	+[[image:image-20221009160309-2.png]]
442	442
443	443
	449	+
444	444	=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
445	445
446	446
...	...	@@ -465,7 +465,7 @@
465	465	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
466	466	)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
467	467
468		-[[image:1664502425687-834.png||_mstalt="296738"]]
	474	+[[image:1664502425687-834.png]]
469	469
470	470
471	471	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
...	...	@@ -472,44 +472,21 @@
472	472	* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
473	473	* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
474	474	* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
475		-* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
	481	+* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
476	476	* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
477	477	* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
478	478
479		-=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
	485	+=== 2.4.6  Add Payload format in TTN V3 ===
480	480
481	481
482		-TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
	488	+In TTN V3, use can add a custom payload so it shows friendly.
483	483
484		-
485		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
486		-|=(% scope="row" style="width: 60px;" %)(((
487		-**Size(bytes)**
488		-)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
489		-|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
490		-[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
491		-)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
492		-
493		-(% class="wikigeneratedid" %)
494		-[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
495		-
496		-
497		-* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
498		-* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
499		-* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
500		-
501		-=== 2.4.7  Add Payload format in TTN V3 ===
502		-
503		-
504		-In TTN V3, user can add a custom payload so it shows friendly.
505		-
506	506	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
507	507
508	508
509		-[[image:1664502649601-895.png||_mstalt="296985"]]
	493	+[[image:1664502649601-895.png]]
510	510
511	511
512		-
513	513	Add the decoder from this link:
514	514
515	515	[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
...	...	@@ -516,9 +516,10 @@
516	516
517	517	Save the change the uplink message will be parsed. As below:
518	518
519		-[[image:1664502676891-606.png||_mstalt="296673"]]
	502	+[[image:1664502676891-606.png]]
520	520
521	521
	505	+
522	522	== 2.5 Integrate with Datacake ==
523	523
524	524
...	...	@@ -526,8 +526,8 @@
526	526
527	527	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]]
528	528
	513	+[[image:1664502695771-538.png]]
529	529
530		-[[image:1664502695771-538.png||_mstalt="297349"]]
531	531
532	532
533	533	== 2.6 Integrate with Tago ==
...	...	@@ -538,9 +538,11 @@
538	538	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]]
539	539
540	540
541		-[[image:1664502715371-321.png||_mstalt="292162"]]
542	542
	526	+[[image:1664502715371-321.png]]
543	543
	528	+
	529	+
544	544	== 2.7  Datalog Feature ==
545	545
546	546
...	...	@@ -550,12 +550,13 @@
550	550
551	551	Example use case.
552	552
553		-[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
	539	+[[image:image-20221009234703-2.png||height="328" width="899"]]
554	554
555	555
556		-[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
	542	+[[image:image-20221009234629-1.png||height="390" width="577"]]
557	557
558	558
	545	+
559	559	== 2.8 Alarm Mode ==
560	560
561	561
...	...	@@ -570,7 +570,7 @@
570	570
571	571
572	572	(((
573		-**Two ways to exit alarm mode:**
	560	+Two ways to exit alarm mode:
574	574	)))
575	575
576	576	* Server sends a downlink command to exit.
...	...	@@ -581,25 +581,24 @@
581	581	)))
582	582
583	583
	571	+
584	584	== 2.9 Transport Mode ==
585	585
586	586
587	587	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.
588	588
589		-* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
590		-* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
591		-* **[[PT>>||anchor="H3.2.1SetTransmitInterval"]]** defines the threldhold to detect a motion.
592	592
	578	+
593	593	== 2.10 LED Status ==
594	594
595	595
596		-(% border="1.5" style="background-color:#ffffcc; width:500px" %)
	582	+(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
597	597	|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
598	598	|(% 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
599	599	|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
600	600	|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
601	601	|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
602		-|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
	588	+|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
603	603	|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
604	604	|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
605	605	|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
...	...	@@ -612,7 +612,7 @@
612	612
613	613	(% style="color:blue" %)**RESET button:**
614	614
615		-[[image:1664502835802-546.png||_mstalt="295061"]]
	601	+[[image:1664502835802-546.png]]
616	616
617	617	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
618	618
...	...	@@ -619,12 +619,12 @@
619	619
620	620	(% style="color:red" %)**RED button:**
621	621
622		-[[image:1664502854406-763.png||_mstalt="295568"]]
	608	+[[image:1664502854406-763.png]]
623	623
624	624
625		-(% border="1" style="background-color:#ffffcc; width:510px" %)
626		-|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
627		-|(% 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.8AlarmMode"]]
	611	+(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
	612	+|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
	613	+|(% 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"]]
628	628	|(% 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
629	629	|(% 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.
630	630
...	...	@@ -646,6 +646,7 @@
646	646	LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
647	647
648	648
	635	+
649	649	== 3.1 Access AT Command ==
650	650
651	651
...	...	@@ -652,24 +652,25 @@
652	652	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.
653	653
654	654
655		-[[image:1664502999401-486.png||_mstalt="296985"]]
	642	+[[image:1664502999401-486.png]]
656	656
657	657
658	658	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:
659	659
660	660
661		-[[image:1664503022490-662.png||_mstalt="293332"]]
	648	+[[image:1664503022490-662.png]]
662	662
663	663
664		-[[image:1664503035713-500.png||_mstalt="291096"]]
	651	+[[image:1664503035713-500.png]]
665	665
666	666
667		-[[image:1664503047675-651.png||_mstalt="295386"]]
	654	+[[image:1664503047675-651.png]]
668	668
669	669
670	670
671	671	== 3.2 Command Set ==
672	672
	660	+
673	673	=== 3.2.1 Set Transmit Interval ===
674	674
675	675
...	...	@@ -687,6 +687,7 @@
687	687	(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
688	688
689	689
	678	+
690	690	=== 3.2.2 Set Alarm Packet transmission interval ===
691	691
692	692
...	...	@@ -704,6 +704,7 @@
704	704	(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
705	705
706	706
	696	+
707	707	=== 3.2.3 Set Transport Mode Packet transmission interval ===
708	708
709	709
...	...	@@ -718,9 +718,10 @@
718	718
719	719	* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
720	720
721		-(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
	711	+(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
722	722
723	723
	714	+
724	724	=== 3.2.4 Exit Alarm ===
725	725
726	726
...	...	@@ -733,6 +733,7 @@
733	733	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
734	734
735	735
	727	+
736	736	=== 3.2.5 Disable/Enable LED flash ===
737	737
738	738
...	...	@@ -750,6 +750,7 @@
750	750	(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
751	751
752	752
	745	+
753	753	=== 3.2.6 Disable/Enable Transport Mode ===
754	754
755	755
...	...	@@ -759,14 +759,15 @@
759	759
760	760	(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
761	761
762		-Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
	755	+Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
763	763
764	764
765	765	* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
766	766
767		-(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
	760	+(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
768	768
769	769
	763	+
770	770	=== 3.2.7 Set Positioning Mode ===
771	771
772	772
...	...	@@ -779,40 +779,32 @@
779	779
780	780	(% style="color:#037691" %)** aa:**
781	781
782		-* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
	776	+* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
	777	+* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
	778	+* (% style="color:red" %)**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.
783	783
784		-* (% style="color:red" %)**2: BLE or WiFi ONLY:                     **(%%)Only obtain iBeacon info via BLE and uplink  or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking.
785		-
786		-* (% style="color:red" %)**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.
787		-
788	788	(% style="color:#037691" %)**bb:**
789	789
790	790	* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
791		-
792	792	* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
793	793
794	794	(% style="color:#037691" %)**cc:   **
795	795
796		-* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
797		-
798		-* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))
	787	+* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
799	799
800	800	(% style="color:blue" %)**Example:**
801	801
802		- AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
	791	+ AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
	792	+ AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
	793	+ AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
803	803
804		- AT+SMOD=1,1,0 ~-~->  GPS +BAT State
805	805
806		- AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
807		-
808		- AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
809		-
810		-
811	811	* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
812	812
813		-(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
	798	+(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
814	814
815	815
	801	+
816	816	=== 3.2.8 Set MAX GPS position time ===
817	817
818	818
...	...	@@ -819,7 +819,7 @@
819	819	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.
820	820
821	821
822		-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.
	808	+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.
823	823
824	824
825	825	* (% style="color:blue" %)**AT Command:**
...	...	@@ -834,6 +834,7 @@
834	834	(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
835	835
836	836
	823	+
837	837	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
838	838
839	839
...	...	@@ -858,7 +858,7 @@
858	858
859	859
860	860
861		-=== 3.2.10 Disable/Enable the confirmation mode ===
	848	+Disable/Enable the confirmation mode
862	862
863	863	* (% style="color:blue" %)**AT Command:**
864	864
...	...	@@ -867,19 +867,20 @@
867	867
868	868	**~ Example:**
869	869
870		- AT+CFM=0    **~-~->   ** Disable confirmation
	857	+ AT+ CFM=0    **~-~->   ** Disable confirmation
871	871
872		- AT+CFM=1    **~-~->  ** Enable confirmation
	859	+ AT+ CFM=1    **~-~->  ** Enable confirmation
873	873
874	874
875	875	* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
876	876
877		-(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
	864	+(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
878	878
879	879
880		-=== 3.2.11  Auto Send None-ACK messages ===
881	881
	868	+=== 3.2.10  Auto Send None-ACK messages ===
882	882
	870	+
883	883	TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
884	884
885	885
...	...	@@ -895,91 +895,30 @@
895	895
896	896	* (% style="color:blue" %)**Downlink Command: 0x34**
897	897
898		-Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
	886	+Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
899	899
900	900
901		-=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
902	902
	890	+=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
903	903
904		-BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
905	905
	893	+BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. LBT1 will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
	894	+
906	906	(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
907	907
908	908	(% style="color:blue" %)**AT Command:**
909	909
910		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
	899	+ (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
911	911
912		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
	901	+ (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
913	913
914		-(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
915	915
916		-Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
	904	+(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**
917	917
	906	+Example: 0xA5010203040506    ~/~/ Set BLEMASK to 123456
918	918
919		-=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
920	920
921	921
922		-WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
923		-
924		-(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
925		-
926		-(% style="color:blue" %)**AT Command:**
927		-
928		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
929		-
930		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
931		-
932		-(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
933		-
934		-Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
935		-
936		-
937		-=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
938		-
939		-
940		-Users can use this feature to enable/disable Information printing.
941		-
942		-(% style="color:blue" %)**AT Command:**
943		-
944		-(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
945		-\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
946		-
947		-
948		-=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
949		-
950		-
951		-The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
952		-
953		-(% style="color:blue" %)**AT Command:**
954		-
955		-(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
956		-
957		-
958		-(% style="color:blue" %)**Downlink Payload:0X24**
959		-
960		-Example: 0x24 01 ~/~/ Same as AT+CHE=1
961		-
962		-
963		-=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
964		-
965		-User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
966		-
967		-(% style="color:blue" %)**AT Command:**
968		-
969		-(% style="color:#037691" %)**AT+PT=xx**
970		-
971		- Example:
972		-
973		- AT+PT=14    ~-~->    Set to detect car motion.
974		-
975		- AT+PT=41   ~-~->    set to detect walk motion.
976		-
977		-
978		-(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
979		-0xB4 14          ~/~/  Same as AT+PT=14
980		-
981		-
982		-
983	983	= 4. Setting for Different Scenarios =
984	984
985	985
...	...	@@ -986,6 +986,7 @@
986	986
987	987	= 5. Upload Firmware =
988	988
	916	+
989	989	== 5.1 Firmware Change Log ==
990	990
991	991
...	...	@@ -992,6 +992,7 @@
992	992	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
993	993
994	994
	923	+
995	995	== 5.2 How to upgrade firmware ==
996	996
997	997
...	...	@@ -1012,10 +1012,10 @@
1012	1012	(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1013	1013
1014	1014
1015		-[[image:1664503563660-578.png||_mstalt="296777"]]
	944	+[[image:1664503563660-578.png]]
1016	1016
1017	1017
1018		-[[image:1664503574618-659.png||_mstalt="297986"]]
	947	+[[image:1664503574618-659.png]]
1019	1019
1020	1020
1021	1021
...	...	@@ -1024,27 +1024,29 @@
1024	1024	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1025	1025
1026	1026
1027		-**Users need to use below files:**
	956	+Users need to use below files:
1028	1028
1029	1029	boot_app0.bin @0e000
1030	1030
1031		-US915.bin @ 0x10000(Select the bin file of the frequency band you need)
	960	+ESP_LORA-eeprom-class.bin @ 0x10000
1032	1032
1033	1033
1034		-[[image:image-20221118105220-2.png||_mstalt="426608"]]
	963	+[[image:1664503593459-435.png]]
1035	1035
1036	1036
1037	1037
1038	1038	After upgrade finish, it will show finish as below:
1039	1039
1040		-[[image:image-20221118105402-4.png||_mstalt="427986"]]
	969	+[[image:1664503611848-385.png]]
1041	1041
1042	1042
1043	1043
1044	1044	= 6. Developer Guide =
1045	1045
	975	+
1046	1046	== 6.1 Compile Source Code ==
1047	1047
	978	+
1048	1048	=== 6.1.1 Set up ARDUINO compile environment ===
1049	1049
1050	1050
...	...	@@ -1053,23 +1053,23 @@
1053	1053	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]]
1054	1054
1055	1055
1056		-[[image:1664503635019-941.png||_mstalt="294658"]]
	987	+[[image:1664503635019-941.png]]
1057	1057
1058	1058
1059	1059
1060	1060	* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1061	1061
1062		-[[image:1664503715811-892.png||_mstalt="295698"]]
	993	+[[image:1664503715811-892.png]]
1063	1063
1064	1064
1065	1065	(% 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.
1066	1066
1067		-[[image:image-20221024105643-1.png||_mstalt="428129"]]
	998	+[[image:image-20221024105643-1.png]]
1068	1068
1069	1069	**~ Figure1**
1070	1070
1071	1071
1072		-[[image:image-20221024105643-2.png||_mstalt="428493"]]
	1003	+[[image:image-20221024105643-2.png]]
1073	1073
1074	1074	**Figure2**
1075	1075
...	...	@@ -1079,31 +1079,34 @@
1079	1079	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1080	1080
1081	1081
1082		-[[image:1664503752288-974.png||_mstalt="298194"]]
	1013	+[[image:1664503752288-974.png]]
1083	1083
1084	1084
	1016	+
1085	1085	== 6.2 Source Code ==
1086	1086
1087	1087
1088	1088	* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1089	1089
1090		-[[image:1664503794261-827.png||_mstalt="296387"]]
	1022	+[[image:1664503794261-827.png]]
1091	1091
1092	1092
1093	1093
1094	1094	* (% style="color:blue" %)**Click to upload**
1095	1095
1096		-[[image:1664503808294-336.png||_mstalt="295711"]]
	1028	+[[image:1664503808294-336.png]]
1097	1097
1098	1098
1099	1099
1100	1100	* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1101	1101
1102		-[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
	1034	+[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1103	1103
1104	1104
	1037	+
1105	1105	= 7.  FAQ =
1106	1106
	1040	+
1107	1107	== 7.1 How to change the LoRa Frequency Bands/Region? ==
1108	1108
1109	1109
...	...	@@ -1110,10 +1110,11 @@
1110	1110	User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1111	1111
1112	1112
	1047	+
1113	1113	== 7.2 What is the pin mapping for the USB program cable? ==
1114	1114
1115	1115
1116		-[[image:1664499635206-262.png||_mstalt="295360"]]
	1051	+[[image:1664499635206-262.png]]
1117	1117
1118	1118
1119	1119
...	...	@@ -1128,250 +1128,45 @@
1128	1128	|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1129	1129	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1130	1130
1131		-== 7.3 Notes on using different serial port tools for TrackerD ==
	1066	+= 8.  Order Info =
1132	1132
1133		-=== 7.3.1  Serial port utility ===
1134	1134
1135		-
1136		-Serial port utility requires you to automatically add data streams.
1137		-
1138		-Need to adjust the data stream to RTS/CTS on physical restart.
1139		-
1140		-(% class="wikigeneratedid" %)
1141		-[[image:image-20221102140621-1.png||_mstalt="425672"]]
1142		-
1143		-
1144		-
1145		-When using AT commands, the data flow needs to be adjusted to XON/XOFF
1146		-
1147		-[[image:image-20221102140638-2.png||_mstalt="428727"]]
1148		-
1149		-
1150		-=== 7.3.2  SecureCRT ===
1151		-
1152		-
1153		-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.
1154		-
1155		-
1156		-[[image:image-20221102140704-3.png||_mstalt="427076"]]
1157		-
1158		-
1159		-[[image:image-20221102140712-4.png||_mstalt="427089"]]
1160		-
1161		-
1162		-=== 7.3.3  PUTTY ===
1163		-
1164		-
1165		-[[image:image-20221102140748-5.png||_mstalt="430456"]]
1166		-
1167		-
1168		-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.
1169		-
1170		-
1171		-[[image:image-20221102140801-6.png||_mstalt="427466"]]
1172		-
1173		-
1174		-== 7.4 How to modify source code to compile different frequency band bin file? ==
1175		-
1176		-
1177		-(% class="box infomessage" %)
1178		-(((
1179		-(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1180		-See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1181		-)))
1182		-
1183		-**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1184		-
1185		-
1186		-[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1187		-
1188		-
1189		-
1190		-**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1191		-
1192		-
1193		-[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1194		-
1195		-
1196		-
1197		-**3. Compile the AS923_JP band, please refer to the intention shown**
1198		-
1199		-
1200		-[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1201		-
1202		-
1203		-
1204		-**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.**
1205		-
1206		-
1207		-[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1208		-
1209		-
1210		-[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1211		-
1212		-
1213		-= 8  Trouble Shooting =
1214		-
1215		-== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1216		-
1217		-
1218		-(((
1219		-Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1220		-)))
1221		-
1222		-
1223		-== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1224		-
1225		-
1226		-(((
1227		-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 will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.
1228		-)))
1229		-
1230		-
1231		-== 8.3  Problem after Upgrading Firmware ==
1232		-
1233		-=== 8.3.1 Continue Restart after upgrading ===
1234		-
1235		-
1236		-(((
1237		-If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1238		-)))
1239		-
1240		-
1241		-[[image:image-20221118105249-3.png||_mstalt="430664"]]
1242		-
1243		-
1244		-=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1245		-
1246		-
1247		-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 8.3.1
1248		-
1249		-
1250		-=== 8.3.3 "flash read err" after upgrade firmware ===
1251		-
1252		-Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1253		-
1254		-[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1255		-
1256		-
1257		-User need to upgrade again with below four files to solve this issue.
1258		-
1259		- [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1260		-
1261		- **Figure 2**
1262		-
1263		-
1264		-=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1265		-
1266		-User might erase the entire flash include keys and default settings which cause this issue.
1267		-
1268		-After the upgrade is completed, enter AT+CFG as shown in the figure below.
1269		-
1270		-[[image:image-20221122100004-3.png||_mstalt="424242"]]
1271		-
1272		-Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1273		-
1274		-After AT+FDR. please set
1275		-
1276		-* AT+PDOP=7
1277		-* AT+FTIME=180000
1278		-
1279		-Example:
1280		-
1281		-AT+PDOP=7.00
1282		-
1283		-AT+FTIME=180
1284		-
1285		-AT+DEUI=70B3D57ED0053981
1286		-
1287		-AT+APPEUI=D23345667BCBCCAF
1288		-
1289		-AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1290		-
1291		-AT+DADDR=260b4dce    ( no need for OTAA)
1292		-
1293		-AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1294		-
1295		-AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1296		-
1297		-
1298		-
1299		-=== 8.3.4  If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ===
1300		-
1301		-
1302		-[[image:image-20221122100004-4.png||_mstalt="424606"]]
1303		-
1304		-
1305		-== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1306		-
1307		-
1308		-Please download version 1.4.2 again
1309		-
1310		-
1311		-== 8.5  How to deal with unsuccessful GPS positioning? ==
1312		-
1313		-
1314		-1） Make Sure the device is in Open Area where can see the sky.
1315		-
1316		-2)  Set PDOP to a higher value.
1317		-
1318		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1319		-
1320		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1321		-
1322		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1323		-
1324		-Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP
1325		-
1326		-
1327		-= 9.  Order Info =
1328		-
1329		-
1330	1330	Part Number: (% style="color:blue" %)**TrackerD-XXX**
1331	1331
1332	1332	(% style="color:blue" %)**XXX**(%%): The default frequency band
1333	1333
1334	1334	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1335		-
1336	1336	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1337		-
1338	1338	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1339		-
1340	1340	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1341		-
1342	1342	* (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1343		-
1344	1344	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1345		-
1346	1346	* (% style="color:red" %)**US915**(%%): Default frequency band US915
1347	1347
1348		-= 10.  Packing Info =
	1081	+= 9.  Packing Info =
1349	1349
1350	1350
1351	1351	(% style="color:#037691" %)**Package Includes**:
1352	1352
1353	1353	* TrackerD LoRaWAN GPS/BLE Tracker x 1
1354		-
1355	1355	* USB recharge & program cable x 1
1356	1356
1357	1357	(% style="color:#037691" %)**Dimensions and Weight**:
1358	1358
1359		-* Device Size: 85 x 48 x 15 mm
1360		-
	1091	+* Device Size: 85 x 48 x 15 cm
1361	1361	* Weight: 50g
1362	1362
1363		-= 11. Support =
	1094	+= 10. Support =
1364	1364
1365	1365
1366	1366	* 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.
1367		-
1368	1368	* 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]].
1369	1369
1370		-= 12.  Reference =
	1100	+= 11.  Reference =
1371	1371
1372	1372
1373	1373	* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1374		-
1375	1375	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
1376		-
1377	1377	* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
	1106	+
	1107	+

1667288597595-714.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-27.9 KB

Content

image-20221102140621-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-46.1 KB

Content

image-20221102140638-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-40.8 KB

Content

image-20221102140704-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-15.5 KB

Content

image-20221102140712-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-73.2 KB

Content

image-20221102140748-5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-56.0 KB

Content

image-20221102140801-6.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-21.0 KB

Content

image-20221107145243-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-107.3 KB

Content

image-20221116111844-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-15.8 KB

Content

image-20221116111844-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-32.6 KB

Content

image-20221116111844-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-37.0 KB

Content

image-20221116111844-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-96.8 KB

Content

image-20221116111844-5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-78.0 KB

Content

image-20221118104359-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-38.0 KB

Content

image-20221118105220-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-40.2 KB

Content

image-20221118105249-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-40.2 KB

Content

image-20221118105402-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-43.7 KB

Content

image-20221122100004-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-18.0 KB

Content

image-20221122100004-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-127.2 KB

Content

image-20221122100004-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-12.5 KB

Content

image-20221122100004-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Bei

Size

...	...	@@ -1,1 +1,0 @@
1		-22.3 KB

Content