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

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 19 added, 0 removed)
  • 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

Details

Page properties

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

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