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

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 27 added, 0 removed)
  • 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
  • image-20221128102938-1.png
  • image-20221128103040-2.png
  • image-20221128110503-3.png
  • image-20221128111443-4.png
  • image-20221128111850-5.png
  • image-20221128111951-6.png
  • image-20221128112035-7.png

Details

Page properties

Author

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

Content

...	...	@@ -1,5 +1,5 @@
1	1	(% style="text-align:center" %)
2		-[[image:1664505654417-133.png]]
	2	+[[image:1664505654417-133.png||_mstalt="293696"]]
3	3
4	4
5	5
...	...	@@ -14,7 +14,6 @@
14	14
15	15	= 1.  Introduction =
16	16
17		-
18	18	== 1.1  What is TrackerD ==
19	19
20	20
...	...	@@ -32,21 +32,17 @@
32	32	(((
33	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.
34	34	)))
35		-)))
36	36
37	37	(((
38	38	TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
39		-
40		-
41	41	)))
42	42
43		-[[image:1664499921684-770.png]]
	39	+[[image:1664499921684-770.png||_mstalt="298194"]]
44	44
45	45
46	46	(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
47	47
48	48
49		-
50	50	== 1.2 Specifications ==
51	51
52	52
...	...	@@ -97,6 +97,7 @@
97	97	* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
98	98	* Tracking: max: 38mA
99	99
	95	+
100	100	== 1.3  Features ==
101	101
102	102
...	...	@@ -115,6 +115,7 @@
115	115	* Tri-color LED, Alarm button
116	116	* Datalog
117	117
	114	+
118	118	== 1.4  Applications ==
119	119
120	120
...	...	@@ -121,8 +121,8 @@
121	121	* Logistics and Supply Chain Management
122	122	* Human tracking
123	123
124		-= 2.1 Use TrackerD =
125	125
	122	+= 2.  Use TrackerD =
126	126
127	127	== 2.1 How it works? ==
128	128
...	...	@@ -130,7 +130,6 @@
130	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.
131	131
132	132
133		-
134	134	== 2.2 Quick guide to connect to LoRaWAN server ==
135	135
136	136
...	...	@@ -137,7 +137,7 @@
137	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.
138	138
139	139
140		-[[image:1664501652064-326.png]]
	136	+[[image:1664501652064-326.png||_mstalt="293306"]]
141	141
142	142
143	143
...	...	@@ -149,7 +149,7 @@
149	149	Each TrackerD is shipped with a sticker with the default device EUI as below:
150	150
151	151
152		-[[image:1664501677253-891.png]]
	148	+[[image:1664501677253-891.png||_mstalt="296569"]]
153	153
154	154
155	155	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
...	...	@@ -158,14 +158,14 @@
158	158	**__Add APP EUI in the application:__**
159	159
160	160
161		-[[image:1664501711466-918.png]]
	157	+[[image:1664501711466-918.png||_mstalt="295828"]]
162	162
163	163
164	164
165		-[[image:1664501721248-725.png]]
	161	+[[image:1664501721248-725.png||_mstalt="294450"]]
166	166
167	167
168		-[[image:1664501734705-405.png]]
	164	+[[image:1664501734705-405.png||_mstalt="293306"]]
169	169
170	170
171	171
...	...	@@ -172,34 +172,34 @@
172	172	**__Add APP KEY and DEV EUI:__**
173	173
174	174
175		-[[image:1664501784668-703.png]]
	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"]]
176	176
177	177
178	178
	175	+(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
179	179
180		-(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
	177	+(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
181	181
	179	+[[image:1664502835802-546.png||_mstalt="295061"]]
182	182
	181	+
183	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	184
185	185
186		-
187	187	== 2.3  Positioning Mode(SMOD) ==
188	188
189	189
190	190	Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
191	191
192		-* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
193		-* (% 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.
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.
	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.
195	195
196	196	Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
197	197
198	198
199		-
200	200	== 2.4  Uplink Payload ==
201	201
202		-
203	203	=== 2.4.1 Uplink FPORT~=5, Device Status ===
204	204
205	205
...	...	@@ -212,7 +212,7 @@
212	212	|=(% 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
213	213	|=(% 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
214	214
215		-[[image:1665301570342-765.png]]
	211	+[[image:1665301570342-765.png||_mstalt="294580"]]
216	216
217	217
218	218	(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
...	...	@@ -279,7 +279,9 @@
279	279
280	280	(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
281	281
	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)(%%)
282	282
	280	+
283	283	(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
284	284
285	285	(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
...	...	@@ -286,6 +286,7 @@
286	286	|=(% 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
287	287	|=(% 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"]]
288	288
	287	+
289	289	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
290	290
291	291
...	...	@@ -304,7 +304,7 @@
304	304	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
305	305	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
306	306
307		-[[image:1665301636888-168.png]]
	306	+[[image:1665301636888-168.png||_mstalt="298012"]]
308	308
309	309
310	310	==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
...	...	@@ -334,12 +334,12 @@
334	334	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:
335	335
336	336
337		-[[image:1664502116362-706.png]]
	336	+[[image:1664502116362-706.png||_mstalt="293306"]]
338	338
339	339
340	340	3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
341	341
342		-[[image:1664502166010-515.png]]
	341	+[[image:1664502166010-515.png||_mstalt="291395"]]
343	343
344	344
345	345
...	...	@@ -362,6 +362,7 @@
362	362	* 3.40v ~~ 3.69v:  20% ~~ 40%
363	363	* < 3.39v:  0~~20%
364	364
	364	+
365	365	==== (% style="color:blue" %)**MOD:**(%%) ====
366	366
367	367	**Example: ** (0x60>>6) & 0x3f =1
...	...	@@ -402,7 +402,6 @@
402	402	011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
403	403
404	404
405		-
406	406	=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
407	407
408	408
...	...	@@ -418,20 +418,19 @@
418	418	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
419	419
420	420	(% class="wikigeneratedid" %)
421		-[[image:1665301687277-443.png]]
	420	+[[image:1665301687277-443.png||_mstalt="296140"]]
422	422
423	423
424		-
425	425	=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
426	426
427	427
428		-Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-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.
	426	+Set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-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.
429	429
430	430
431	431	(% style="color:red" %)**Note for this mode:**
432	432
433	433	* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
434		-* 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.
	432	+* 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	435	* 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
436	436
437	437	The payload is 15 bytes, as below.
...	...	@@ -442,10 +442,9 @@
442	442	)))|4|4|2|1|1|1|1|1
443	443	|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
444	444
445		-[[image:image-20221009160309-2.png]]
	443	+[[image:image-20221009160309-2.png||_mstalt="429312"]]
446	446
447	447
448		-
449	449	=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
450	450
451	451
...	...	@@ -470,7 +470,7 @@
470	470	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
471	471	)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
472	472
473		-[[image:1664502425687-834.png]]
	470	+[[image:1664502425687-834.png||_mstalt="296738"]]
474	474
475	475
476	476	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
...	...	@@ -477,16 +477,17 @@
477	477	* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
478	478	* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
479	479	* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
480		-* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
	477	+* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
481	481	* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
482	482	* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
483	483
484		-=== 2.4.6  Uplink FPORT~=6, WiFi Positioning with Strongest WiFi SSID ===
485	485
	482	+=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
486	486
487		-TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
488	488
	485	+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.
489	489
	487	+
490	490	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
491	491	|=(% scope="row" style="width: 60px;" %)(((
492	492	**Size(bytes)**
...	...	@@ -496,7 +496,7 @@
496	496	)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
497	497
498	498	(% class="wikigeneratedid" %)
499		-[[image:1667288597595-714.png||height="212" width="1151"]]
	497	+[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
500	500
501	501
502	502	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
...	...	@@ -503,6 +503,7 @@
503	503	* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
504	504	* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
505	505
	504	+
506	506	=== 2.4.7  Add Payload format in TTN V3 ===
507	507
508	508
...	...	@@ -511,9 +511,10 @@
511	511	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
512	512
513	513
514		-[[image:1664502649601-895.png]]
	513	+[[image:1664502649601-895.png||_mstalt="296985"]]
515	515
516	516
	516	+
517	517	Add the decoder from this link:
518	518
519	519	[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
...	...	@@ -520,10 +520,9 @@
520	520
521	521	Save the change the uplink message will be parsed. As below:
522	522
523		-[[image:1664502676891-606.png]]
	523	+[[image:1664502676891-606.png||_mstalt="296673"]]
524	524
525	525
526		-
527	527	== 2.5 Integrate with Datacake ==
528	528
529	529
...	...	@@ -531,8 +531,8 @@
531	531
532	532	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]]
533	533
534		-[[image:1664502695771-538.png]]
535	535
	534	+[[image:1664502695771-538.png||_mstalt="297349"]]
536	536
537	537
538	538	== 2.6 Integrate with Tago ==
...	...	@@ -543,27 +543,24 @@
543	543	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]]
544	544
545	545
	545	+[[image:1664502715371-321.png||_mstalt="292162"]]
546	546
547		-[[image:1664502715371-321.png]]
548	548
549		-
550		-
551	551	== 2.7  Datalog Feature ==
552	552
553	553
554	554	total 273 entries,by default,
555	555
556		-User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
	553	+User can set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
557	557
558	558	Example use case.
559	559
560		-[[image:image-20221009234703-2.png||height="328" width="899"]]
	557	+[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
561	561
562	562
563		-[[image:image-20221009234629-1.png||height="390" width="577"]]
	560	+[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
564	564
565	565
566		-
567	567	== 2.8 Alarm Mode ==
568	568
569	569
...	...	@@ -578,7 +578,7 @@
578	578
579	579
580	580	(((
581		-Two ways to exit alarm mode:
	577	+**Two ways to exit alarm mode:**
582	582	)))
583	583
584	584	* Server sends a downlink command to exit.
...	...	@@ -589,24 +589,26 @@
589	589	)))
590	590
591	591
592		-
593	593	== 2.9 Transport Mode ==
594	594
595	595
596	596	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.
597	597
	593	+* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
	594	+* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
	595	+* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
598	598
599	599
600	600	== 2.10 LED Status ==
601	601
602	602
603		-(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
	601	+(% border="1.5" style="background-color:#ffffcc; width:500px" %)
604	604	|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
605	605	|(% 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
606	606	|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
607	607	|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
608	608	|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
609		-|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
	607	+|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
610	610	|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
611	611	|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
612	612	|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
...	...	@@ -614,12 +614,13 @@
614	614	|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
615	615	|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
616	616
	615	+
617	617	== 2.11 Button Function ==
618	618
619	619
620	620	(% style="color:blue" %)**RESET button:**
621	621
622		-[[image:1664502835802-546.png]]
	621	+[[image:1664502835802-546.png||_mstalt="295061"]]
623	623
624	624	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
625	625
...	...	@@ -626,15 +626,16 @@
626	626
627	627	(% style="color:red" %)**RED button:**
628	628
629		-[[image:1664502854406-763.png]]
	628	+[[image:1664502854406-763.png||_mstalt="295568"]]
630	630
631	631
632		-(% border="1" style="background-color:#ffffcc; color:green; width:510px" %)
	631	+(% border="1" style="background-color:#ffffcc; width:510px" %)
633	633	|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
634		-|(% 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"]]
	633	+|(% 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"]]
635	635	|(% 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
636	636	|(% 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.
637	637
	637	+
638	638	== 2.12 USB Port Function ==
639	639
640	640
...	...	@@ -645,6 +645,7 @@
645	645	* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
646	646	* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
647	647
	648	+
648	648	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
649	649
650	650
...	...	@@ -653,7 +653,6 @@
653	653	LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
654	654
655	655
656		-
657	657	== 3.1 Access AT Command ==
658	658
659	659
...	...	@@ -660,25 +660,23 @@
660	660	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.
661	661
662	662
663		-[[image:1664502999401-486.png]]
	663	+[[image:1664502999401-486.png||_mstalt="296985"]]
664	664
665	665
666	666	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:
667	667
668	668
669		-[[image:1664503022490-662.png]]
	669	+[[image:1664503022490-662.png||_mstalt="293332"]]
670	670
671	671
672		-[[image:1664503035713-500.png]]
	672	+[[image:1664503035713-500.png||_mstalt="291096"]]
673	673
674	674
675		-[[image:1664503047675-651.png]]
	675	+[[image:1664503047675-651.png||_mstalt="295386"]]
676	676
677	677
678		-
679	679	== 3.2 Command Set ==
680	680
681		-
682	682	=== 3.2.1 Set Transmit Interval ===
683	683
684	684
...	...	@@ -696,7 +696,6 @@
696	696	(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
697	697
698	698
699		-
700	700	=== 3.2.2 Set Alarm Packet transmission interval ===
701	701
702	702
...	...	@@ -714,7 +714,6 @@
714	714	(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
715	715
716	716
717		-
718	718	=== 3.2.3 Set Transport Mode Packet transmission interval ===
719	719
720	720
...	...	@@ -729,10 +729,9 @@
729	729
730	730	* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
731	731
732		-(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
	728	+(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
733	733
734	734
735		-
736	736	=== 3.2.4 Exit Alarm ===
737	737
738	738
...	...	@@ -745,7 +745,6 @@
745	745	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
746	746
747	747
748		-
749	749	=== 3.2.5 Disable/Enable LED flash ===
750	750
751	751
...	...	@@ -763,7 +763,6 @@
763	763	(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
764	764
765	765
766		-
767	767	=== 3.2.6 Disable/Enable Transport Mode ===
768	768
769	769
...	...	@@ -773,15 +773,14 @@
773	773
774	774	(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
775	775
776		-Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
	769	+Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
777	777
778	778
779	779	* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
780	780
781		-(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
	774	+(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
782	782
783	783
784		-
785	785	=== 3.2.7 Set Positioning Mode ===
786	786
787	787
...	...	@@ -794,34 +794,40 @@
794	794
795	795	(% style="color:#037691" %)** aa:**
796	796
797		-* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
798		-* (% 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.
799		-* (% 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.
	789	+* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
800	800
	791	+* (% 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.
	792	+
	793	+* (% 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.
	794	+
801	801	(% style="color:#037691" %)**bb:**
802	802
803	803	* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
	798	+
804	804	* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
805	805
806	806	(% style="color:#037691" %)**cc:   **
807	807
808		-* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
809		-* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))
	803	+* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
	804	+
	805	+* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))
810	810
811	811	(% style="color:blue" %)**Example:**
812	812
813		- AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
814		- AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
815		- AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
816		- AT+ SMOD =2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
	809	+ AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
817	817
	811	+ AT+SMOD=1,1,0 ~-~->  GPS +BAT State
818	818
819		-* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
	813	+ AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
820	820
821		-(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
	815	+ AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
822	822
823	823
	818	+* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
824	824
	820	+(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
	821	+
	822	+
825	825	=== 3.2.8 Set MAX GPS position time ===
826	826
827	827
...	...	@@ -828,7 +828,7 @@
828	828	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.
829	829
830	830
831		-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.
	829	+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.
832	832
833	833
834	834	* (% style="color:blue" %)**AT Command:**
...	...	@@ -843,7 +843,6 @@
843	843	(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
844	844
845	845
846		-
847	847	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
848	848
849	849
...	...	@@ -868,8 +868,9 @@
868	868
869	869
870	870
871		-Disable/Enable the confirmation mode
	868	+=== 3.2.10 Disable/Enable the confirmation mode ===
872	872
	870	+
873	873	* (% style="color:blue" %)**AT Command:**
874	874
875	875	(% style="color:#037691" %)**AT+CFM=xx**
...	...	@@ -877,20 +877,19 @@
877	877
878	878	**~ Example:**
879	879
880		- AT+ CFM=0    **~-~->   ** Disable confirmation
	878	+ AT+CFM=0    **~-~->   ** Disable confirmation
881	881
882		- AT+ CFM=1    **~-~->  ** Enable confirmation
	880	+ AT+CFM=1    **~-~->  ** Enable confirmation
883	883
884	884
885	885	* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
886	886
887		-(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
	885	+(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
888	888
889	889
	888	+=== 3.2.11  Auto Send None-ACK messages ===
890	890
891		-=== 3.2.10  Auto Send None-ACK messages ===
892	892
893		-
894	894	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.
895	895
896	896
...	...	@@ -906,13 +906,12 @@
906	906
907	907	* (% style="color:blue" %)**Downlink Command: 0x34**
908	908
909		-Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
	906	+Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
910	910
911	911
	909	+=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
912	912
913		-=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
914	914
915		-
916	916	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.
917	917
918	918	(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
...	...	@@ -919,35 +919,79 @@
919	919
920	920	(% style="color:blue" %)**AT Command:**
921	921
922		- (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
	918	+ (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
923	923
924		- (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
	920	+ (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
925	925
	922	+(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
926	926
927		-(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**
	924	+Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
928	928
929		-Example: 0xA5010203040506    ~/~/ Set BLEMASK to 123456
930	930
	927	+=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
931	931
932		-=== 3.2.12  Set WiFIMASK to filter WiFi SSID ===
933	933
	930	+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.
934	934
935		-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. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
936		-
937	937	(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
938	938
939	939	(% style="color:blue" %)**AT Command:**
940	940
941		- (% style="color:#037691" %)**AT+ WiFiMASK =123456**    (%%) ~/~/ Set WiFiMASK = 123456
	936	+ (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
942	942
943		- (% style="color:#037691" %)**AT+ WiFiMASK =0**       (%%) ~/~/ disable WiFiMASK
	938	+ (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
944	944
	940	+(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
945	945
946		-(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**
	942	+Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
947	947
948		-Example: 0xA5010203040506    ~/~/ Set WiFiMASK to 123456
949	949
	945	+=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
950	950
	947	+
	948	+Users can use this feature to enable/disable Information printing.
	949	+
	950	+(% style="color:blue" %)**AT Command:**
	951	+
	952	+(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
	953	+\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
	954	+
	955	+
	956	+=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
	957	+
	958	+
	959	+The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
	960	+
	961	+(% style="color:blue" %)**AT Command:**
	962	+
	963	+(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
	964	+
	965	+
	966	+(% style="color:blue" %)**Downlink Payload:0X24**
	967	+
	968	+Example: 0x24 01 ~/~/ Same as AT+CHE=1
	969	+
	970	+
	971	+=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
	972	+
	973	+User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
	974	+
	975	+(% style="color:blue" %)**AT Command:**
	976	+
	977	+(% style="color:#037691" %)**AT+PT=xx**
	978	+
	979	+ Example:
	980	+
	981	+ AT+PT=14    ~-~->    Set to detect car motion.
	982	+
	983	+ AT+PT=41   ~-~->    set to detect walk motion.
	984	+
	985	+
	986	+(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
	987	+0xB4 14          ~/~/  Same as AT+PT=14
	988	+
	989	+
	990	+
951	951	= 4. Setting for Different Scenarios =
952	952
953	953
...	...	@@ -954,7 +954,6 @@
954	954
955	955	= 5. Upload Firmware =
956	956
957		-
958	958	== 5.1 Firmware Change Log ==
959	959
960	960
...	...	@@ -961,7 +961,6 @@
961	961	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
962	962
963	963
964		-
965	965	== 5.2 How to upgrade firmware ==
966	966
967	967
...	...	@@ -982,10 +982,10 @@
982	982	(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
983	983
984	984
985		-[[image:1664503563660-578.png]]
	1023	+[[image:1664503563660-578.png||_mstalt="296777"]]
986	986
987	987
988		-[[image:1664503574618-659.png]]
	1026	+[[image:1664503574618-659.png||_mstalt="297986"]]
989	989
990	990
991	991
...	...	@@ -994,29 +994,27 @@
994	994	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
995	995
996	996
997		-Users need to use below files:
	1035	+**Users need to use below files:**
998	998
999	999	boot_app0.bin @0e000
1000	1000
1001		-ESP_LORA-eeprom-class.bin @ 0x10000
	1039	+US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1002	1002
1003	1003
1004		-[[image:1664503593459-435.png]]
	1042	+[[image:image-20221118105220-2.png||_mstalt="426608"]]
1005	1005
1006	1006
1007	1007
1008	1008	After upgrade finish, it will show finish as below:
1009	1009
1010		-[[image:1664503611848-385.png]]
	1048	+[[image:image-20221118105402-4.png||_mstalt="427986"]]
1011	1011
1012	1012
1013	1013
1014	1014	= 6. Developer Guide =
1015	1015
1016		-
1017	1017	== 6.1 Compile Source Code ==
1018	1018
1019		-
1020	1020	=== 6.1.1 Set up ARDUINO compile environment ===
1021	1021
1022	1022
...	...	@@ -1025,23 +1025,23 @@
1025	1025	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]]
1026	1026
1027	1027
1028		-[[image:1664503635019-941.png]]
	1064	+[[image:1664503635019-941.png||_mstalt="294658"]]
1029	1029
1030	1030
1031	1031
1032	1032	* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1033	1033
1034		-[[image:1664503715811-892.png]]
	1070	+[[image:1664503715811-892.png||_mstalt="295698"]]
1035	1035
1036	1036
1037	1037	(% 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.
1038	1038
1039		-[[image:image-20221024105643-1.png]]
	1075	+[[image:image-20221024105643-1.png||_mstalt="428129"]]
1040	1040
1041	1041	**~ Figure1**
1042	1042
1043	1043
1044		-[[image:image-20221024105643-2.png]]
	1080	+[[image:image-20221024105643-2.png||_mstalt="428493"]]
1045	1045
1046	1046	**Figure2**
1047	1047
...	...	@@ -1051,34 +1051,31 @@
1051	1051	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1052	1052
1053	1053
1054		-[[image:1664503752288-974.png]]
	1090	+[[image:1664503752288-974.png||_mstalt="298194"]]
1055	1055
1056	1056
1057		-
1058	1058	== 6.2 Source Code ==
1059	1059
1060	1060
1061	1061	* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1062	1062
1063		-[[image:1664503794261-827.png]]
	1098	+[[image:1664503794261-827.png||_mstalt="296387"]]
1064	1064
1065	1065
1066	1066
1067	1067	* (% style="color:blue" %)**Click to upload**
1068	1068
1069		-[[image:1664503808294-336.png]]
	1104	+[[image:1664503808294-336.png||_mstalt="295711"]]
1070	1070
1071	1071
1072	1072
1073	1073	* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1074	1074
1075		-[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
	1110	+[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1076	1076
1077	1077
1078		-
1079	1079	= 7.  FAQ =
1080	1080
1081		-
1082	1082	== 7.1 How to change the LoRa Frequency Bands/Region? ==
1083	1083
1084	1084
...	...	@@ -1085,11 +1085,10 @@
1085	1085	User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1086	1086
1087	1087
1088		-
1089	1089	== 7.2 What is the pin mapping for the USB program cable? ==
1090	1090
1091	1091
1092		-[[image:1664499635206-262.png]]
	1124	+[[image:1664499635206-262.png||_mstalt="295360"]]
1093	1093
1094	1094
1095	1095
...	...	@@ -1104,45 +1104,291 @@
1104	1104	|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1105	1105	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1106	1106
1107		-= 8.  Order Info =
1108	1108
	1140	+== 7.3 Notes on using different serial port tools for TrackerD ==
1109	1109
	1142	+=== 7.3.1  Serial port utility ===
	1143	+
	1144	+
	1145	+Serial port utility requires you to automatically add data streams.
	1146	+
	1147	+Need to adjust the data stream to RTS/CTS on physical restart.
	1148	+
	1149	+(% class="wikigeneratedid" %)
	1150	+[[image:image-20221102140621-1.png||_mstalt="425672"]]
	1151	+
	1152	+
	1153	+
	1154	+When using AT commands, the data flow needs to be adjusted to XON/XOFF
	1155	+
	1156	+[[image:image-20221102140638-2.png||_mstalt="428727"]]
	1157	+
	1158	+
	1159	+=== 7.3.2  SecureCRT ===
	1160	+
	1161	+
	1162	+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.
	1163	+
	1164	+
	1165	+[[image:image-20221102140704-3.png||_mstalt="427076"]]
	1166	+
	1167	+
	1168	+[[image:image-20221102140712-4.png||_mstalt="427089"]]
	1169	+
	1170	+
	1171	+=== 7.3.3  PUTTY ===
	1172	+
	1173	+
	1174	+[[image:image-20221102140748-5.png||_mstalt="430456"]]
	1175	+
	1176	+
	1177	+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.
	1178	+
	1179	+
	1180	+[[image:image-20221102140801-6.png||_mstalt="427466"]]
	1181	+
	1182	+
	1183	+== 7.4 How to modify source code to compile different frequency band bin file? ==
	1184	+
	1185	+
	1186	+(% class="box infomessage" %)
	1187	+(((
	1188	+(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
	1189	+See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
	1190	+)))
	1191	+
	1192	+**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
	1193	+
	1194	+
	1195	+[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
	1196	+
	1197	+
	1198	+
	1199	+**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
	1200	+
	1201	+
	1202	+[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
	1203	+
	1204	+
	1205	+
	1206	+**3. Compile the AS923_JP band, please refer to the intention shown**
	1207	+
	1208	+
	1209	+[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
	1210	+
	1211	+
	1212	+
	1213	+**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.**
	1214	+
	1215	+
	1216	+[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
	1217	+
	1218	+
	1219	+[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
	1220	+
	1221	+
	1222	+= 8  Trouble Shooting =
	1223	+
	1224	+== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
	1225	+
	1226	+
	1227	+(((
	1228	+Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**AT+INTWK=1**(%%)), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
	1229	+)))
	1230	+
	1231	+
	1232	+== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
	1233	+
	1234	+
	1235	+(((
	1236	+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.
	1237	+)))
	1238	+
	1239	+
	1240	+== 8.3  Problem after Upgrading Firmware ==
	1241	+
	1242	+=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
	1243	+
	1244	+
	1245	+**Error Output**
	1246	+
	1247	+
	1248	+[[image:image-20221122100004-4.png||_mstalt="424606"]]
	1249	+
	1250	+
	1251	+(((
	1252	+Some partition is missed during upgrade, please upgrade below four files as example:
	1253	+
	1254	+[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
	1255	+)))
	1256	+
	1257	+
	1258	+=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1259	+
	1260	+
	1261	+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
	1262	+
	1263	+
	1264	+=== 8.3.3 "flash read err" after upgrade firmware ===
	1265	+
	1266	+
	1267	+Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
	1268	+
	1269	+
	1270	+[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
	1271	+
	1272	+
	1273	+User need to upgrade again with below four files to solve this issue.
	1274	+
	1275	+ [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
	1276	+
	1277	+ **Figure 2**
	1278	+
	1279	+
	1280	+=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
	1281	+
	1282	+
	1283	+User might erase the entire flash include keys and default settings which cause this issue.
	1284	+
	1285	+After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
	1286	+
	1287	+
	1288	+[[image:image-20221122100004-3.png||_mstalt="424242"]]
	1289	+
	1290	+
	1291	+Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
	1292	+
	1293	+After AT+FDR. please set
	1294	+
	1295	+* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
	1296	+
	1297	+* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
	1298	+
	1299	+**Example:**
	1300	+
	1301	+AT+PDOP=7.00
	1302	+
	1303	+AT+FTIME=180
	1304	+
	1305	+AT+DEUI=70B3D57ED0053981
	1306	+
	1307	+AT+APPEUI=D23345667BCBCCAF
	1308	+
	1309	+AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
	1310	+
	1311	+AT+DADDR=260b4dce    ( no need for OTAA)
	1312	+
	1313	+AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
	1314	+
	1315	+AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
	1316	+
	1317	+
	1318	+== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
	1319	+
	1320	+
	1321	+Please download version 1.4.2 again
	1322	+
	1323	+
	1324	+== 8.5  How to deal with unsuccessful GPS positioning? ==
	1325	+
	1326	+
	1327	+1） Make Sure the device is in Open Area where can see the sky.
	1328	+
	1329	+2)  Set PDOP to a higher value.
	1330	+
	1331	+* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
	1332	+
	1333	+* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
	1334	+
	1335	+* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
	1336	+
	1337	+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
	1338	+
	1339	+
	1340	+== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
	1341	+
	1342	+When upgrading, use the erase button to upgrade
	1343	+
	1344	+[[image:image-20221128102938-1.png||height="537" width="335"]]
	1345	+
	1346	+
	1347	+The parameters are displayed abnormally and cannot be fixed using AT+FDR
	1348	+
	1349	+[[image:image-20221128103040-2.png||height="431" width="525"]]
	1350	+
	1351	+Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
	1352	+
	1353	+[[image:image-20221128110503-3.png||height="647" width="410"]]
	1354	+
	1355	+Reboot information after upgrade
	1356	+
	1357	+[[image:image-20221128111443-4.png||height="432" width="546"]]
	1358	+
	1359	+Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
	1360	+
	1361	+[[image:image-20221128111850-5.png]]
	1362	+
	1363	+After the parameters return to normal, upgrade to the version you need again
	1364	+
	1365	+[[image:image-20221128111951-6.png||height="620" width="389"]]
	1366	+
	1367	+At this point the parameters return to normal
	1368	+
	1369	+[[image:image-20221128112035-7.png]]
	1370	+
	1371	+
	1372	+= 9.  Order Info =
	1373	+
	1374	+
1110	1110	Part Number: (% style="color:blue" %)**TrackerD-XXX**
1111	1111
1112	1112	(% style="color:blue" %)**XXX**(%%): The default frequency band
1113	1113
1114	1114	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
	1380	+
1115	1115	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
	1382	+
1116	1116	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
	1384	+
1117	1117	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
	1386	+
1118	1118	* (% style="color:red" %)**AS923**(%%): Default frequency band AS923
	1388	+
1119	1119	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
	1390	+
1120	1120	* (% style="color:red" %)**US915**(%%): Default frequency band US915
1121	1121
1122		-= 9.  Packing Info =
1123	1123
	1394	+= 10.  Packing Info =
1124	1124
	1396	+
1125	1125	(% style="color:#037691" %)**Package Includes**:
1126	1126
1127	1127	* TrackerD LoRaWAN GPS/BLE Tracker x 1
	1400	+
1128	1128	* USB recharge & program cable x 1
1129	1129
1130	1130	(% style="color:#037691" %)**Dimensions and Weight**:
1131	1131
1132		-* Device Size: 85 x 48 x 15 cm
	1405	+* Device Size: 85 x 48 x 15 mm
	1406	+
1133	1133	* Weight: 50g
1134	1134
1135		-= 10. Support =
1136	1136
	1410	+= 11. Support =
1137	1137
	1412	+
1138	1138	* 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.
	1414	+
1139	1139	* 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]].
1140	1140
1141		-= 11.  Reference =
1142	1142
	1418	+= 12.  Reference =
1143	1143
	1420	+
1144	1144	* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	1422	+
1145	1145	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
1146		-* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1147	1147
1148		-
	1425	+* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
	1426	+)))

image-20221102140621-1.png

Author

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

Size

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

Content

image-20221102140638-2.png

Author

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

Size

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

Content

image-20221102140704-3.png

Author

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

Size

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

Content

image-20221102140712-4.png

Author

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

Size

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

Content

image-20221102140748-5.png

Author

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

Size

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

Content

image-20221102140801-6.png

Author

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

Size

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

Content

image-20221107145243-1.png

Author

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

Size

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

Content

image-20221116111844-1.png

Author

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

Size

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

Content

image-20221116111844-2.png

Author

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

Size

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

Content

image-20221116111844-3.png

Author

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

Size

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

Content

image-20221116111844-4.png

Author

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

Size

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

Content

image-20221116111844-5.png

Author

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

Size

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

Content

image-20221118104359-1.png

Author

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

Size

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

Content

image-20221118105220-2.png

Author

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

Size

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

Content

image-20221118105249-3.png

Author

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

Size

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

Content

image-20221118105402-4.png

Author

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

Size

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

Content

image-20221122100004-1.png

Author

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

Size

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

Content

image-20221122100004-2.png

Author

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

Size

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

Content

image-20221122100004-3.png

Author

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

Size

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

Content

image-20221122100004-4.png

Author

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

Size

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

Content

image-20221128102938-1.png

Author

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

Size

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

Content

image-20221128103040-2.png

Author

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

Size

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

Content

image-20221128110503-3.png

Author

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

Size

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

Content

image-20221128111443-4.png

Author

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

Size

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

Content

image-20221128111850-5.png

Author

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

Size

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

Content

image-20221128111951-6.png

Author

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

Size

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

Content

image-20221128112035-7.png

Author

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

Size

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

Content