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

Summary

• Page properties (1 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

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

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