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

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 26 removed)
  • 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
  • image-20221207120501-1.png
  • image-20221207120524-2.png
  • image-20221207120530-3.png
  • image-20221207120536-4.png
  • image-20221207120601-5.png
  • image-20221207133836-6.png
  • image-20221207133911-7.png
  • image-20221207134028-8.png
  • image-20221213100007-1.png
  • image-20221213100626-2.png
  • image-20221213100808-3.png
  • image-20221213101040-4.png
  • image-20221213102311-5.png
  • image-20221213102334-6.png
  • image-20221213102718-7.png
  • image-20221213110952-8.png
  • image-20230213110119-1.png
  • image-20230213110214-2.png
  • image-20230213110506-3.png

Details

Page properties

Author

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

Content

...	...	@@ -1,5 +1,5 @@
1	1	(% style="text-align:center" %)
2		-[[image:1664505654417-133.png||_mstalt="293696"]]
	2	+[[image:1664505654417-133.png]]
3	3
4	4
5	5
...	...	@@ -12,9 +12,9 @@
12	12
13	13
14	14
15		-
16	16	= 1.  Introduction =
17	17
	17	+
18	18	== 1.1  What is TrackerD ==
19	19
20	20
...	...	@@ -32,17 +32,21 @@
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	+)))
35	35
36	36	(((
37	37	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	+
38	38	)))
39	39
40		-[[image:image-20230213110119-1.png||height="382" width="834"]]
	43	+[[image:1664499921684-770.png]]
41	41
42	42
43	43	(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
44	44
45	45
	49	+
46	46	== 1.2 Specifications ==
47	47
48	48
...	...	@@ -93,8 +93,6 @@
93	93	* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94	94	* Tracking: max: 38mA
95	95
96		-
97		-
98	98	== 1.3  Features ==
99	99
100	100
...	...	@@ -113,8 +113,6 @@
113	113	* Tri-color LED, Alarm button
114	114	* Datalog
115	115
116		-
117		-
118	118	== 1.4  Applications ==
119	119
120	120
...	...	@@ -121,10 +121,9 @@
121	121	* Logistics and Supply Chain Management
122	122	* Human tracking
123	123
124		-
125		-
126	126	= 2.  Use TrackerD =
127	127
	126	+
128	128	== 2.1 How it works? ==
129	129
130	130
...	...	@@ -131,6 +131,7 @@
131	131	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.
132	132
133	133
	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:image-20230213110214-2.png||height="388" width="847"]]
	140	+[[image:1664501652064-326.png]]
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||_mstalt="296569"]]
	152	+[[image:1664501677253-891.png]]
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||_mstalt="295828"]]
	161	+[[image:1664501711466-918.png]]
162	162
163	163
164	164
165		-[[image:1664501721248-725.png||_mstalt="294450"]]
	165	+[[image:1664501721248-725.png]]
166	166
167	167
168		-[[image:1664501734705-405.png||_mstalt="293306"]]
	168	+[[image:1664501734705-405.png]]
169	169
170	170
171	171
...	...	@@ -172,20 +172,21 @@
172	172	**__Add APP KEY and DEV EUI:__**
173	173
174	174
175		-[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
	175	+[[image: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||alt="1654671889112-678.png"]]
176	176
177	177
178	178
179	179	(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
180	180
181		-(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
	181	+(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
182	182
183		-[[image:1664502835802-546.png||_mstalt="295061"]]
	183	+[[image:1664502835802-546.png]]
184	184
185	185
186	186	(% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
187	187
188	188
	189	+
189	189	== 2.3  Positioning Mode(SMOD) ==
190	190
191	191
...	...	@@ -198,8 +198,10 @@
198	198	Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
199	199
200	200
	202	+
201	201	== 2.4  Uplink Payload ==
202	202
	205	+
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||_mstalt="294580"]]
	218	+[[image:1665301570342-765.png]]
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		-(% _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)(%%)
	285	+(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% 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,8 +288,6 @@
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
291		-
292		-
293	293	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
294	294
295	295
...	...	@@ -308,7 +308,7 @@
308	308	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
309	309	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
310	310
311		-[[image:1665301636888-168.png||_mstalt="298012"]]
	312	+[[image:1665301636888-168.png]]
312	312
313	313
314	314	==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
...	...	@@ -338,12 +338,12 @@
338	338	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:
339	339
340	340
341		-[[image:1664502116362-706.png||_mstalt="293306"]]
	342	+[[image:1664502116362-706.png]]
342	342
343	343
344	344	3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
345	345
346		-[[image:1664502166010-515.png||_mstalt="291395"]]
	347	+[[image:1664502166010-515.png]]
347	347
348	348
349	349
...	...	@@ -366,9 +366,6 @@
366	366	* 3.40v ~~ 3.69v:  20% ~~ 40%
367	367	* < 3.39v:  0~~20%
368	368
369		-(% style="display:none" %) (%%)
370		-
371		-
372	372	==== (% style="color:blue" %)**MOD:**(%%) ====
373	373
374	374	**Example: ** (0x60>>6) & 0x3f =1
...	...	@@ -409,6 +409,7 @@
409	409	011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
410	410
411	411
	410	+
412	412	=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
413	413
414	414
...	...	@@ -424,13 +424,14 @@
424	424	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
425	425
426	426	(% class="wikigeneratedid" %)
427		-[[image:1665301687277-443.png||_mstalt="296140"]]
	426	+[[image:1665301687277-443.png]]
428	428
429	429
	429	+
430	430	=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
431	431
432	432
433		-Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-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.
	433	+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.
434	434
435	435
436	436	(% style="color:red" %)**Note for this mode:**
...	...	@@ -447,9 +447,10 @@
447	447	)))|4|4|2|1|1|1|1|1
448	448	|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
449	449
450		-[[image:image-20221009160309-2.png||_mstalt="429312"]]
	450	+[[image:image-20221009160309-2.png]]
451	451
452	452
	453	+
453	453	=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
454	454
455	455
...	...	@@ -474,7 +474,7 @@
474	474	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
475	475	)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
476	476
477		-[[image:1664502425687-834.png||_mstalt="296738"]]
	478	+[[image:1664502425687-834.png]]
478	478
479	479
480	480	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
...	...	@@ -485,9 +485,6 @@
485	485	* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
486	486	* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
487	487
488		-(% style="display:none" %) (%%)
489		-
490		-
491	491	=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
492	492
493	493
...	...	@@ -503,7 +503,7 @@
503	503	)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
504	504
505	505	(% class="wikigeneratedid" %)
506		-[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
	504	+[[image:1667288597595-714.png||height="212" width="1151"]]
507	507
508	508
509	509	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
...	...	@@ -510,9 +510,6 @@
510	510	* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
511	511	* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
512	512
513		-(% style="display:none" %) (%%)
514		-
515		-
516	516	=== 2.4.7  Add Payload format in TTN V3 ===
517	517
518	518
...	...	@@ -521,10 +521,9 @@
521	521	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
522	522
523	523
524		-[[image:1664502649601-895.png||_mstalt="296985"]]
	519	+[[image:1664502649601-895.png]]
525	525
526	526
527		-
528	528	Add the decoder from this link:
529	529
530	530	[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
...	...	@@ -531,9 +531,10 @@
531	531
532	532	Save the change the uplink message will be parsed. As below:
533	533
534		-[[image:1664502676891-606.png||_mstalt="296673"]]
	528	+[[image:1664502676891-606.png]]
535	535
536	536
	531	+
537	537	== 2.5 Integrate with Datacake ==
538	538
539	539
...	...	@@ -542,9 +542,10 @@
542	542	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]]
543	543
544	544
545		-[[image:1664502695771-538.png||_mstalt="297349"]]
	540	+[[image:1664502695771-538.png]]
546	546
547	547
	543	+
548	548	== 2.6 Integrate with Tago ==
549	549
550	550
...	...	@@ -553,24 +553,26 @@
553	553	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]]
554	554
555	555
556		-[[image:1664502715371-321.png||_mstalt="292162"]]
	552	+[[image:1664502715371-321.png]]
557	557
558	558
	555	+
559	559	== 2.7  Datalog Feature ==
560	560
561	561
562	562	total 273 entries,by default,
563	563
564		-User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
	561	+User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
565	565
566	566	Example use case.
567	567
568		-[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
	565	+[[image:image-20221009234703-2.png||height="328" width="899"]]
569	569
570	570
571		-[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
	568	+[[image:image-20221009234629-1.png||height="390" width="577"]]
572	572
573	573
	571	+
574	574	== 2.8 Alarm Mode ==
575	575
576	576
...	...	@@ -585,7 +585,7 @@
585	585
586	586
587	587	(((
588		-**Two ways to exit alarm mode:**
	586	+Two ways to exit alarm mode:
589	589	)))
590	590
591	591	* Server sends a downlink command to exit.
...	...	@@ -596,18 +596,14 @@
596	596	)))
597	597
598	598
	597	+
599	599	== 2.9 Transport Mode ==
600	600
601	601
602	602	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.
603	603
604		-* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
605		-* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
606		-* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
607	607
608		-(% style="display:none" %) (%%)
609	609
610		-
611	611	== 2.10 LED Status ==
612	612
613	613
...	...	@@ -625,15 +625,12 @@
625	625	|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
626	626	|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
627	627
628		-(% style="display:none" %) (%%)
629		-
630		-
631	631	== 2.11 Button Function ==
632	632
633	633
634	634	(% style="color:blue" %)**RESET button:**
635	635
636		-[[image:1664502835802-546.png||_mstalt="295061"]]
	627	+[[image:1664502835802-546.png]]
637	637
638	638	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
639	639
...	...	@@ -640,9 +640,8 @@
640	640
641	641	(% style="color:red" %)**RED button:**
642	642
643		-[[image:image-20230213110506-3.png]](% style="display:none" %)
	634	+[[image:1664502854406-763.png]]
644	644
645		-(% style="display:none" %) (%%)
646	646
647	647	(% border="1" style="background-color:#ffffcc; width:510px" %)
648	648	|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
...	...	@@ -650,9 +650,6 @@
650	650	|(% 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
651	651	|(% 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.
652	652
653		-(% style="display:none" %) (%%)
654		-
655		-
656	656	== 2.12 USB Port Function ==
657	657
658	658
...	...	@@ -663,9 +663,6 @@
663	663	* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
664	664	* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
665	665
666		-(% style="display:none" %) (%%)
667		-
668		-
669	669	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
670	670
671	671
...	...	@@ -674,6 +674,7 @@
674	674	LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
675	675
676	676
	661	+
677	677	== 3.1 Access AT Command ==
678	678
679	679
...	...	@@ -680,24 +680,25 @@
680	680	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.
681	681
682	682
683		-[[image:1664502999401-486.png||_mstalt="296985"]]
	668	+[[image:1664502999401-486.png]]
684	684
685	685
686	686	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:
687	687
688	688
689		-[[image:1664503022490-662.png||_mstalt="293332"]]
	674	+[[image:1664503022490-662.png]]
690	690
691	691
692		-[[image:1664503035713-500.png||_mstalt="291096"]]
	677	+[[image:1664503035713-500.png]]
693	693
694	694
695		-[[image:1664503047675-651.png||_mstalt="295386"]]
	680	+[[image:1664503047675-651.png]]
696	696
697		-(% style="display:none" %) (%%)
698	698
	683	+
699	699	== 3.2 Command Set ==
700	700
	686	+
701	701	=== 3.2.1 Set Transmit Interval ===
702	702
703	703
...	...	@@ -715,6 +715,7 @@
715	715	(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
716	716
717	717
	704	+
718	718	=== 3.2.2 Set Alarm Packet transmission interval ===
719	719
720	720
...	...	@@ -732,6 +732,7 @@
732	732	(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
733	733
734	734
	722	+
735	735	=== 3.2.3 Set Transport Mode Packet transmission interval ===
736	736
737	737
...	...	@@ -749,6 +749,7 @@
749	749	(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
750	750
751	751
	740	+
752	752	=== 3.2.4 Exit Alarm ===
753	753
754	754
...	...	@@ -761,9 +761,10 @@
761	761	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
762	762
763	763
764		-=== 3.2.5 Disable/Enable LED flash and buzzer ===
765	765
	754	+=== 3.2.5 Disable/Enable LED flash ===
766	766
	756	+
767	767	Disable/Enable LED for position, downlink and uplink
768	768
769	769	* (% style="color:blue" %)**AT Command:**
...	...	@@ -778,6 +778,7 @@
778	778	(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
779	779
780	780
	771	+
781	781	=== 3.2.6 Disable/Enable Transport Mode ===
782	782
783	783
...	...	@@ -795,6 +795,7 @@
795	795	(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
796	796
797	797
	789	+
798	798	=== 3.2.7 Set Positioning Mode ===
799	799
800	800
...	...	@@ -821,9 +821,9 @@
821	821
822	822	(% style="color:#037691" %)**cc:   **
823	823
824		-* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
	816	+* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
825	825
826		-* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))
	818	+* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))
827	827
828	828	(% style="color:blue" %)**Example:**
829	829
...	...	@@ -841,6 +841,7 @@
841	841	(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
842	842
843	843
	836	+
844	844	=== 3.2.8 Set MAX GPS position time ===
845	845
846	846
...	...	@@ -847,7 +847,7 @@
847	847	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.
848	848
849	849
850		-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.
	843	+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.
851	851
852	852
853	853	* (% style="color:blue" %)**AT Command:**
...	...	@@ -862,6 +862,7 @@
862	862	(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
863	863
864	864
	858	+
865	865	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
866	866
867	867
...	...	@@ -885,8 +885,8 @@
885	885	(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
886	886
887	887
888		-=== 3.2.10 Disable/Enable the confirmation mode ===
889	889
	883	+Disable/Enable the confirmation mode
890	890
891	891	* (% style="color:blue" %)**AT Command:**
892	892
...	...	@@ -905,9 +905,10 @@
905	905	(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
906	906
907	907
908		-=== 3.2.11  Auto Send None-ACK messages ===
909	909
	903	+=== 3.2.10  Auto Send None-ACK messages ===
910	910
	905	+
911	911	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.
912	912
913	913
...	...	@@ -923,12 +923,13 @@
923	923
924	924	* (% style="color:blue" %)**Downlink Command: 0x34**
925	925
926		-Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
	921	+Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
927	927
928	928
929		-=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
930	930
	925	+=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
931	931
	927	+
932	932	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.
933	933
934	934	(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
...	...	@@ -935,18 +935,19 @@
935	935
936	936	(% style="color:blue" %)**AT Command:**
937	937
938		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
	934	+ (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
939	939
940		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
	936	+ (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
941	941
942	942	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
943	943
944		-Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
	940	+Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
945	945
946	946
947		-=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
948	948
	944	+=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
949	949
	946	+
950	950	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.
951	951
952	952	(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
...	...	@@ -953,61 +953,44 @@
953	953
954	954	(% style="color:blue" %)**AT Command:**
955	955
956		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
	953	+ (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
957	957
958		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
	955	+ (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
959	959
960	960	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
961	961
962		-Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
	959	+Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
963	963
964	964
965		-=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
966	966
	963	+=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
967	967
	965	+
968	968	Users can use this feature to enable/disable Information printing.
969	969
970	970	(% style="color:blue" %)**AT Command:**
971	971
972		-(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
	970	+(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
973	973	\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
974	974
975	975
976		-=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
977	977
	975	+=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
978	978
	977	+
979	979	The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
980	980
981	981	(% style="color:blue" %)**AT Command:**
982	982
983		-(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
	982	+(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
984	984
985	985
986	986	(% style="color:blue" %)**Downlink Payload:0X24**
987	987
988		-Example: 0x24 01  ~/~/ Same as AT+CHE=1
	987	+Example: 0x24 01 ~/~/ Same as AT+CHE=1
989	989
990	990
991		-=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
992	992
993		-
994		-User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
995		-
996		-(% style="color:blue" %)**AT Command:**
997		-
998		-(% style="color:#037691" %)**AT+PT=xx**
999		-
1000		- Example:
1001		-
1002		- AT+PT=14    ~-~->    Set to detect car motion.
1003		-
1004		- AT+PT=41  ~-~->    set to detect walk motion.
1005		-
1006		-
1007		-(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
1008		-0xB4 14          ~/~/  Same as AT+PT=14
1009		-
1010		-
1011	1011	= 4. Setting for Different Scenarios =
1012	1012
1013	1013
...	...	@@ -1014,6 +1014,7 @@
1014	1014
1015	1015	= 5. Upload Firmware =
1016	1016
	997	+
1017	1017	== 5.1 Firmware Change Log ==
1018	1018
1019	1019
...	...	@@ -1020,6 +1020,7 @@
1020	1020	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
1021	1021
1022	1022
	1004	+
1023	1023	== 5.2 How to upgrade firmware ==
1024	1024
1025	1025
...	...	@@ -1040,10 +1040,10 @@
1040	1040	(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1041	1041
1042	1042
1043		-[[image:1664503563660-578.png||_mstalt="296777"]]
	1025	+[[image:1664503563660-578.png]]
1044	1044
1045	1045
1046		-[[image:1664503574618-659.png||_mstalt="297986"]]
	1028	+[[image:1664503574618-659.png]]
1047	1047
1048	1048
1049	1049
...	...	@@ -1052,7 +1052,7 @@
1052	1052	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1053	1053
1054	1054
1055		-**Users need to use below files:**
	1037	+Users need to use below files:
1056	1056
1057	1057	boot_app0.bin @0e000
1058	1058
...	...	@@ -1059,19 +1059,22 @@
1059	1059	US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1060	1060
1061	1061
1062		-[[image:image-20221207120501-1.png]]
	1044	+[[image:image-20221118105220-2.png]]
1063	1063
1064	1064
1065	1065
1066	1066	After upgrade finish, it will show finish as below:
1067	1067
1068		-[[image:image-20221207133911-7.png]]
	1050	+[[image:image-20221118105402-4.png]]
1069	1069
1070	1070
	1053	+
1071	1071	= 6. Developer Guide =
1072	1072
	1056	+
1073	1073	== 6.1 Compile Source Code ==
1074	1074
	1059	+
1075	1075	=== 6.1.1 Set up ARDUINO compile environment ===
1076	1076
1077	1077
...	...	@@ -1080,80 +1080,24 @@
1080	1080	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]]
1081	1081
1082	1082
1083		-[[image:1664503635019-941.png||_mstalt="294658"]]
	1068	+[[image:1664503635019-941.png]]
1084	1084
1085	1085
1086	1086
1087	1087	* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1088	1088
1089		-[[image:1664503715811-892.png||_mstalt="295698"]]
	1074	+[[image:1664503715811-892.png]]
1090	1090
1091	1091
1092		-=== 6.1.2  Build the development environment ===
1093		-
1094		-
1095		-**~1. Download and install arduino IDE**
1096		-
1097		-[[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]]
1098		-
1099		-
1100		-**2. Download the ESP32 development package in the arduino IDE**
1101		-
1102		-[[image:image-20221213100007-1.png]]
1103		-
1104		-
1105		-Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1106		-
1107		-[[image:image-20221213100626-2.png]]
1108		-
1109		-
1110		-Restart the IDE after the addition is complete, then:
1111		-
1112		-[[image:image-20221213100808-3.png||height="679" width="649"]]
1113		-
1114		-
1115		-[[image:image-20221213101040-4.png]]
1116		-
1117		-
1118		-(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1119		-Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)**
1120		-
1121		-Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import:
1122		-
1123		-(% style="color:blue" %)**Methods as below:**
1124		-
1125		-~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1126		-
1127		-2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1128		-
1129	1129	(% 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.
1130	1130
1131		-[[image:image-20221213102311-5.png||height="582" width="711"]]
	1079	+[[image:image-20221024105643-1.png]]
1132	1132
1133		-
1134		-**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1135		-
1136		-[[image:image-20221213102334-6.png]]
1137		-
1138		-(% style="color:red" %)**Note: This step requires a python environment**
1139		-
1140		-
1141		-Either way, in the end:
1142		-
1143		-The final effect is to open the arduino and you can see the esp32
1144		-
1145		-[[image:image-20221213110952-8.png||height="866" width="711"]]
1146		-
1147		-
1148		-
1149		-[[image:image-20221024105643-1.png||_mstalt="428129"]]
1150		-
1151	1151	**~ Figure1**
1152	1152
1153	1153
	1084	+[[image:image-20221024105643-2.png]]
1154	1154
1155		-[[image:image-20221024105643-2.png||_mstalt="428493"]]
1156		-
1157	1157	**Figure2**
1158	1158
1159	1159
...	...	@@ -1162,31 +1162,34 @@
1162	1162	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1163	1163
1164	1164
1165		-[[image:1664503752288-974.png||_mstalt="298194"]]
	1094	+[[image:1664503752288-974.png]]
1166	1166
1167	1167
	1097	+
1168	1168	== 6.2 Source Code ==
1169	1169
1170	1170
1171	1171	* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1172	1172
1173		-[[image:1664503794261-827.png||_mstalt="296387"]]
	1103	+[[image:1664503794261-827.png]]
1174	1174
1175	1175
1176	1176
1177	1177	* (% style="color:blue" %)**Click to upload**
1178	1178
1179		-[[image:1664503808294-336.png||_mstalt="295711"]]
	1109	+[[image:1664503808294-336.png]]
1180	1180
1181	1181
1182	1182
1183	1183	* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1184	1184
1185		-[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
	1115	+[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1186	1186
1187	1187
	1118	+
1188	1188	= 7.  FAQ =
1189	1189
	1121	+
1190	1190	== 7.1 How to change the LoRa Frequency Bands/Region? ==
1191	1191
1192	1192
...	...	@@ -1193,10 +1193,11 @@
1193	1193	User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1194	1194
1195	1195
	1128	+
1196	1196	== 7.2 What is the pin mapping for the USB program cable? ==
1197	1197
1198	1198
1199		-[[image:1664499635206-262.png||_mstalt="295360"]]
	1132	+[[image:1664499635206-262.png]]
1200	1200
1201	1201
1202	1202
...	...	@@ -1211,11 +1211,9 @@
1211	1211	|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1212	1212	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1213	1213
1214		-(% style="display:none" %) (%%)
1215		-
1216		-
1217	1217	== 7.3 Notes on using different serial port tools for TrackerD ==
1218	1218
	1149	+
1219	1219	=== 7.3.1  Serial port utility ===
1220	1220
1221	1221
...	...	@@ -1223,16 +1223,18 @@
1223	1223
1224	1224	Need to adjust the data stream to RTS/CTS on physical restart.
1225	1225
	1157	+
1226	1226	(% class="wikigeneratedid" %)
1227		-[[image:image-20221102140621-1.png||_mstalt="425672"]]
	1159	+[[image:image-20221102140621-1.png]]
1228	1228
1229	1229
1230		-
1231	1231	When using AT commands, the data flow needs to be adjusted to XON/XOFF
1232	1232
1233		-[[image:image-20221102140638-2.png||_mstalt="428727"]]
1234	1234
	1165	+[[image:image-20221102140638-2.png]]
1235	1235
	1167	+
	1168	+
1236	1236	=== 7.3.2  SecureCRT ===
1237	1237
1238	1238
...	...	@@ -1239,22 +1239,23 @@
1239	1239	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.
1240	1240
1241	1241
1242		-[[image:image-20221102140704-3.png||_mstalt="427076"]]
	1175	+[[image:image-20221102140704-3.png]]
1243	1243
1244	1244
1245		-[[image:image-20221102140712-4.png||_mstalt="427089"]]
	1178	+[[image:image-20221102140712-4.png]]
1246	1246
1247	1247
	1181	+
1248	1248	=== 7.3.3  PUTTY ===
1249	1249
1250	1250
1251		-[[image:image-20221102140748-5.png||_mstalt="430456"]]
	1185	+[[image:image-20221102140748-5.png]]
1252	1252
1253	1253
1254	1254	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.
1255	1255
1256	1256
1257		-[[image:image-20221102140801-6.png||_mstalt="427466"]]
	1191	+[[image:image-20221102140801-6.png]]
1258	1258
1259	1259
1260	1260	== 7.4 How to modify source code to compile different frequency band bin file? ==
...	...	@@ -1266,52 +1266,38 @@
1266	1266	See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1267	1267	)))
1268	1268
1269		-**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
	1203	+1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
1270	1270
	1205	+[[image:image-20221116111844-1.png||height="227" width="782"]]
1271	1271
1272		-[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
	1207	+2.Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
1273	1273
	1209	+[[image:image-20221116111844-2.png||height="262" width="781"]]
1274	1274
	1211	+3.Compile the AS923_JP band, please refer to the intention shown
1275	1275
1276		-**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
	1213	+[[image:image-20221116111844-3.png||height="338" width="746"]]
1277	1277
	1215	+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.
1278	1278
1279		-[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
	1217	+[[image:image-20221116111844-4.png||height="641" width="739"]]
1280	1280
	1219	+[[image:image-20221116111844-5.png||height="551" width="708"]]
1281	1281
1282	1282
1283		-**3. Compile the AS923_JP band, please refer to the intention shown**
1284	1284
1285		-
1286		-[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1287		-
1288		-
1289		-
1290		-**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.**
1291		-
1292		-
1293		-[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1294		-
1295		-
1296		-[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1297		-
1298		-
1299		-== 7.5 Are there example python example for BLE Indoor Positioning? ==
1300		-
1301		-
1302		-[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1303		-
1304		-
1305	1305	= 8  Trouble Shooting =
1306	1306
	1225	+
1307	1307	== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1308	1308
1309	1309
1310	1310	(((
1311		-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
	1230	+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
1312	1312	)))
1313	1313
1314	1314
	1234	+
1315	1315	== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1316	1316
1317	1317
...	...	@@ -1320,152 +1320,85 @@
1320	1320	)))
1321	1321
1322	1322
	1243	+
1323	1323	== 8.3  Problem after Upgrading Firmware ==
1324	1324
1325		-=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
	1246	+=== 8.3.1 Continue Restart after upgrading ===
1326	1326
1327	1327
1328		-**Error Output**
1329		-
1330		-
1331		-[[image:image-20221122100004-4.png||_mstalt="424606"]]
1332		-
1333		-
1334	1334	(((
1335		-Some partition is missed during upgrade, please upgrade below four files as example:
1336		-
1337		-[[image:image-20221207120524-2.png]]
	1250	+If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1338	1338	)))
1339	1339
1340	1340
1341		-=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1254	+[[image:image-20221118105249-3.png]]
1342	1342
1343	1343
	1257	+=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1258	+
1344	1344	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
1345	1345
1346	1346
1347		-=== 8.3.3 "flash read err" after upgrade firmware ===
	1262	+==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ====
1348	1348
	1264	+[[image:image-20221122100004-1.png||height="497" width="534"]]
1349	1349
1350		-Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
	1266	+ Figure 1
1351	1351
	1268	+ [[image:image-20221122100004-2.png||height="619" width="389"]]
1352	1352
1353		-[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
	1270	+ Figure 2
1354	1354
	1272	+After the upgrade is completed, enter AT+CFG as shown in the figure below.
1355	1355
1356		-User need to upgrade again with below four files to solve this issue.
	1274	+[[image:image-20221122100004-3.png]]
1357	1357
1358		- [[image:image-20221207120530-3.png]]
	1276	+Please AT+FDR, and then enter the following instructions by the information on the label
1359	1359
1360		- **Figure 2**
	1278	+AT+DEUI=70B3D57ED0053981
1361	1361
1362		-
1363		-=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1364		-
1365		-
1366		-User might erase the entire flash include keys and default settings which cause this issue.
1367		-
1368		-After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1369		-
1370		-
1371		-[[image:image-20221122100004-3.png||_mstalt="424242"]]
1372		-
1373		-
1374		-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.
1375		-
1376		-After AT+FDR. please set
1377		-
1378		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1379		-
1380		-* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1381		-
1382		-**Example:**
1383		-
1384		-AT+PDOP=7.00
1385		-
1386		-AT+FTIME=180
1387		-
1388		-AT+DEUI=70B3D57ED0053981
1389		-
1390	1390	AT+APPEUI=D23345667BCBCCAF
1391	1391
1392	1392	AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1393	1393
1394		-AT+DADDR=260b4dce    ( no need for OTAA)
	1284	+AT+DADDR=260b4dce
1395	1395
1396		-AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
	1286	+AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1397	1397
1398		-AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
	1288	+AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1399	1399
1400	1400
1401		-== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1402	1402
	1292	+==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ====
1403	1403
1404		-Please download version 1.4.2 again
	1294	+[[image:image-20221122100004-4.png]]
1405	1405
	1296	+== ==
1406	1406
1407		-== 8.5  How to deal with unsuccessful GPS positioning? ==
	1298	+== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
1408	1408
	1300	+Please download version 1.4.2 again
1409	1409
1410		-1） Make Sure the device is in Open Area where can see the sky.
1411	1411
	1303	+(((
	1304	+== 8.5 How to deal with unsuccessful GPS positioning? ==
	1305	+
	1306	+1） Make Sure the device is in Open Area where can see the sky.
1412	1412	2)  Set PDOP to a higher value.
1413	1413
1414		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
	1309	+ AT+PDOP=2(can be positioned precisely.）
1415	1415
1416		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
	1311	+ AT+PDOP=7(Quickly locate in open spaces）
1417	1417
1418		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
	1313	+ AT+PDOP=14.7(Positioning can be acquired in complex environments）
1419	1419
1420	1420	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
	1316	+)))
1421	1421
1422	1422
1423		-== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
	1319	+== ==
1424	1424
1425	1425
1426		-When upgrading, use the erase button to upgrade
1427		-
1428		-[[image:image-20221207120536-4.png]]
1429		-
1430		-
1431		-The parameters are displayed abnormally and cannot be fixed using AT+FDR
1432		-
1433		-[[image:image-20221128103040-2.png||height="431" width="525"]]
1434		-
1435		-
1436		-Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1437		-
1438		-[[image:image-20221207134028-8.png]]
1439		-
1440		-
1441		-Reboot information after upgrade
1442		-
1443		-[[image:image-20221128111443-4.png||height="432" width="546"]]
1444		-
1445		-
1446		-Use **AT+FDR** command to reset and then use **AT+CFG** to check whether the configuration is back to normal
1447		-
1448		-[[image:image-20221128111850-5.png]]
1449		-
1450		-
1451		-After the parameters return to normal, upgrade to the version you need again
1452		-
1453		-[[image:image-20221207120601-5.png]]
1454		-
1455		-
1456		-At this point, the parameters return to normal after running AT+FDR again
1457		-
1458		-[[image:image-20221128112035-7.png]]
1459		-
1460		-
1461		-== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1462		-
1463		-
1464		-~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1465		-
1466		-2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1467		-
1468		-
1469	1469	= 9.  Order Info =
1470	1470
1471	1471
...	...	@@ -1474,22 +1474,13 @@
1474	1474	(% style="color:blue" %)**XXX**(%%): The default frequency band
1475	1475
1476	1476	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1477		-
1478	1478	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1479		-
1480	1480	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1481		-
1482	1482	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1483		-
1484	1484	* (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1485		-
1486	1486	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1487		-
1488	1488	* (% style="color:red" %)**US915**(%%): Default frequency band US915
1489	1489
1490		-(% style="display:none" %) (%%)
1491		-
1492		-
1493	1493	= 10.  Packing Info =
1494	1494
1495	1495
...	...	@@ -1496,38 +1496,22 @@
1496	1496	(% style="color:#037691" %)**Package Includes**:
1497	1497
1498	1498	* TrackerD LoRaWAN GPS/BLE Tracker x 1
1499		-
1500	1500	* USB recharge & program cable x 1
1501	1501
1502	1502	(% style="color:#037691" %)**Dimensions and Weight**:
1503	1503
1504	1504	* Device Size: 85 x 48 x 15 mm
1505		-
1506	1506	* Weight: 50g
1507	1507
1508		-(% style="display:none" %) (%%)
1509		-
1510		-
1511	1511	= 11. Support =
1512	1512
1513	1513
1514	1514	* 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.
1515		-
1516	1516	* 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]].
1517	1517
1518		-(% style="display:none" %) (%%)
1519		-
1520		-
1521	1521	= 12.  Reference =
1522	1522
1523	1523
1524	1524	* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1525		-
1526	1526	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
1527		-
1528	1528	* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1529		-
1530		-
1531		-
1532		-
1533		-)))

image-20221128102938-1.png

Author

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

Size

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

Content

image-20221128103040-2.png

Author

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

Size

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

Content

image-20221128110503-3.png

Author

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

Size

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

Content

image-20221128111443-4.png

Author

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

Size

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

Content

image-20221128111850-5.png

Author

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

Size

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

Content

image-20221128111951-6.png

Author

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

Size

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

Content

image-20221128112035-7.png

Author

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

Size

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

Content

image-20221207120501-1.png

Author

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

Size

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

Content

image-20221207120524-2.png

Author

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

Size

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

Content

image-20221207120530-3.png

Author

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

Size

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

Content

image-20221207120536-4.png

Author

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

Size

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

Content

image-20221207120601-5.png

Author

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

Size

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

Content

image-20221207133836-6.png

Author

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

Size

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

Content

image-20221207133911-7.png

Author

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

Size

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

Content

image-20221207134028-8.png

Author

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

Size

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

Content

image-20221213100007-1.png

Author

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

Size

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

Content

image-20221213100626-2.png

Author

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

Size

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

Content

image-20221213100808-3.png

Author

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

Size

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

Content

image-20221213101040-4.png

Author

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

Size

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

Content

image-20221213102311-5.png

Author

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

Size

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

Content

image-20221213102334-6.png

Author

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

Size

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

Content

image-20221213102718-7.png

Author

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

Size

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

Content

image-20221213110952-8.png

Author

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

Size

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

Content

image-20230213110119-1.png

Author

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

Size

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

Content

image-20230213110214-2.png

Author

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

Size

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

Content

image-20230213110506-3.png

Author

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

Size

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

Content