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

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 27 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
  • image-20230302145315-1.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,16 +276,15 @@
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
283	283
284		-(% border="1.5" style="background-color:#ffffcc; color:green; width:412.222px" %)
285		-|=(% scope="row" style="width: 75px;" %)**Size(bit)**|(% style="width:68px" %)5 Bits|(% style="width:87px" %)1 Bit|(% style="width:49px" %)1 Bit|(% style="width:126px" %)1 Bit
286		-|=(% style="width: 75px;" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
	290	+(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
	291	+|=(% 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
	292	+|=(% 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,20 +304,20 @@
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:**(%%) ====
311	311
312		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:279.222px" %)
313		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:69px" %)1 bit|(% style="width:63px" %)14 bits
314		-|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:69px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]
	317	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
	318	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
	319	+|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]
315	315
316	316	==== (% style="color:blue" %)**FLAG:**(%%) ====
317	317
318		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:183.222px" %)
319		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2 bits|(% style="width:52px" %)1 bit
320		-|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:52px" %)[[LON>>||anchor="HLON:"]]
	323	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
	324	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
	325	+|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
321	321
322	322	**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
323	323
...	...	@@ -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,30 +481,9 @@
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" %) (%%)
	489	+=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
485	485
486		-=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
487	487
488		-The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
489		-
490		-(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
491		-|**Size(bytes)**|2|1
492		-|**Value**|[[Alarm & BAT>>path:#HAlarm26BAT:]]|Mod+lon
493		-
494		- [[image:image-20230302145315-1.png]]
495		-
496		-alarm=(bytes[0] & 0x40) ~/~/Alarm status
497		-
498		-batV=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;~/~/Battery,units:V
499		-
500		-mod = bytes[2] & 0xC0;
501		-
502		-Lon=(bytes[2] & 0x20)
503		-
504		-
505		-=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
506		-
507		-
508	508	TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
509	509
510	510
...	...	@@ -517,7 +517,7 @@
517	517	)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
518	518
519	519	(% class="wikigeneratedid" %)
520		-[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
	504	+[[image:1667288597595-714.png||height="212" width="1151"]]
521	521
522	522
523	523	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
...	...	@@ -524,21 +524,17 @@
524	524	* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
525	525	* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
526	526
527		-(% style="display:none" %) (%%)
	511	+=== 2.4.7  Add Payload format in TTN V3 ===
528	528
529	529
530		-=== 2.4.8  Add Payload format in TTN V3 ===
531		-
532		-
533	533	In TTN V3, user can add a custom payload so it shows friendly.
534	534
535	535	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
536	536
537	537
538		-[[image:1664502649601-895.png||_mstalt="296985"]]
	519	+[[image:1664502649601-895.png]]
539	539
540	540
541		-
542	542	Add the decoder from this link:
543	543
544	544	[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
...	...	@@ -545,9 +545,10 @@
545	545
546	546	Save the change the uplink message will be parsed. As below:
547	547
548		-[[image:1664502676891-606.png||_mstalt="296673"]]
	528	+[[image:1664502676891-606.png]]
549	549
550	550
	531	+
551	551	== 2.5 Integrate with Datacake ==
552	552
553	553
...	...	@@ -556,9 +556,10 @@
556	556	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]]
557	557
558	558
559		-[[image:1664502695771-538.png||_mstalt="297349"]]
	540	+[[image:1664502695771-538.png]]
560	560
561	561
	543	+
562	562	== 2.6 Integrate with Tago ==
563	563
564	564
...	...	@@ -567,24 +567,26 @@
567	567	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]]
568	568
569	569
570		-[[image:1664502715371-321.png||_mstalt="292162"]]
	552	+[[image:1664502715371-321.png]]
571	571
572	572
	555	+
573	573	== 2.7  Datalog Feature ==
574	574
575	575
576	576	total 273 entries,by default,
577	577
578		-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.
579	579
580	580	Example use case.
581	581
582		-[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
	565	+[[image:image-20221009234703-2.png||height="328" width="899"]]
583	583
584	584
585		-[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
	568	+[[image:image-20221009234629-1.png||height="390" width="577"]]
586	586
587	587
	571	+
588	588	== 2.8 Alarm Mode ==
589	589
590	590
...	...	@@ -599,7 +599,7 @@
599	599
600	600
601	601	(((
602		-**Two ways to exit alarm mode:**
	586	+Two ways to exit alarm mode:
603	603	)))
604	604
605	605	* Server sends a downlink command to exit.
...	...	@@ -610,18 +610,14 @@
610	610	)))
611	611
612	612
	597	+
613	613	== 2.9 Transport Mode ==
614	614
615	615
616	616	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.
617	617
618		-* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
619		-* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
620		-* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
621	621
622		-(% style="display:none" %) (%%)
623	623
624		-
625	625	== 2.10 LED Status ==
626	626
627	627
...	...	@@ -639,15 +639,12 @@
639	639	|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
640	640	|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
641	641
642		-(% style="display:none" %) (%%)
643		-
644		-
645	645	== 2.11 Button Function ==
646	646
647	647
648	648	(% style="color:blue" %)**RESET button:**
649	649
650		-[[image:1664502835802-546.png||_mstalt="295061"]]
	627	+[[image:1664502835802-546.png]]
651	651
652	652	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
653	653
...	...	@@ -654,9 +654,8 @@
654	654
655	655	(% style="color:red" %)**RED button:**
656	656
657		-[[image:image-20230213110506-3.png]](% style="display:none" %)
	634	+[[image:1664502854406-763.png]]
658	658
659		-(% style="display:none" %) (%%)
660	660
661	661	(% border="1" style="background-color:#ffffcc; width:510px" %)
662	662	|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
...	...	@@ -664,9 +664,6 @@
664	664	|(% 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
665	665	|(% 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.
666	666
667		-(% style="display:none" %) (%%)
668		-
669		-
670	670	== 2.12 USB Port Function ==
671	671
672	672
...	...	@@ -677,9 +677,6 @@
677	677	* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
678	678	* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
679	679
680		-(% style="display:none" %) (%%)
681		-
682		-
683	683	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
684	684
685	685
...	...	@@ -688,6 +688,7 @@
688	688	LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
689	689
690	690
	661	+
691	691	== 3.1 Access AT Command ==
692	692
693	693
...	...	@@ -694,24 +694,25 @@
694	694	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.
695	695
696	696
697		-[[image:1664502999401-486.png||_mstalt="296985"]]
	668	+[[image:1664502999401-486.png]]
698	698
699	699
700	700	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:
701	701
702	702
703		-[[image:1664503022490-662.png||_mstalt="293332"]]
	674	+[[image:1664503022490-662.png]]
704	704
705	705
706		-[[image:1664503035713-500.png||_mstalt="291096"]]
	677	+[[image:1664503035713-500.png]]
707	707
708	708
709		-[[image:1664503047675-651.png||_mstalt="295386"]]
	680	+[[image:1664503047675-651.png]]
710	710
711		-(% style="display:none" %) (%%)
712	712
	683	+
713	713	== 3.2 Command Set ==
714	714
	686	+
715	715	=== 3.2.1 Set Transmit Interval ===
716	716
717	717
...	...	@@ -729,6 +729,7 @@
729	729	(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
730	730
731	731
	704	+
732	732	=== 3.2.2 Set Alarm Packet transmission interval ===
733	733
734	734
...	...	@@ -746,6 +746,7 @@
746	746	(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
747	747
748	748
	722	+
749	749	=== 3.2.3 Set Transport Mode Packet transmission interval ===
750	750
751	751
...	...	@@ -763,6 +763,7 @@
763	763	(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
764	764
765	765
	740	+
766	766	=== 3.2.4 Exit Alarm ===
767	767
768	768
...	...	@@ -775,9 +775,10 @@
775	775	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
776	776
777	777
778		-=== 3.2.5 Disable/Enable LED flash and buzzer ===
779	779
	754	+=== 3.2.5 Disable/Enable LED flash ===
780	780
	756	+
781	781	Disable/Enable LED for position, downlink and uplink
782	782
783	783	* (% style="color:blue" %)**AT Command:**
...	...	@@ -792,6 +792,7 @@
792	792	(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
793	793
794	794
	771	+
795	795	=== 3.2.6 Disable/Enable Transport Mode ===
796	796
797	797
...	...	@@ -809,6 +809,7 @@
809	809	(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
810	810
811	811
	789	+
812	812	=== 3.2.7 Set Positioning Mode ===
813	813
814	814
...	...	@@ -835,9 +835,9 @@
835	835
836	836	(% style="color:#037691" %)**cc:   **
837	837
838		-* (% _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
839	839
840		-* (% _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(%%))
841	841
842	842	(% style="color:blue" %)**Example:**
843	843
...	...	@@ -855,6 +855,7 @@
855	855	(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
856	856
857	857
	836	+
858	858	=== 3.2.8 Set MAX GPS position time ===
859	859
860	860
...	...	@@ -861,7 +861,7 @@
861	861	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.
862	862
863	863
864		-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.
865	865
866	866
867	867	* (% style="color:blue" %)**AT Command:**
...	...	@@ -876,6 +876,7 @@
876	876	(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
877	877
878	878
	858	+
879	879	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
880	880
881	881
...	...	@@ -899,8 +899,8 @@
899	899	(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
900	900
901	901
902		-=== 3.2.10 Disable/Enable the confirmation mode ===
903	903
	883	+Disable/Enable the confirmation mode
904	904
905	905	* (% style="color:blue" %)**AT Command:**
906	906
...	...	@@ -919,9 +919,10 @@
919	919	(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
920	920
921	921
922		-=== 3.2.11  Auto Send None-ACK messages ===
923	923
	903	+=== 3.2.10  Auto Send None-ACK messages ===
924	924
	905	+
925	925	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.
926	926
927	927
...	...	@@ -937,12 +937,13 @@
937	937
938	938	* (% style="color:blue" %)**Downlink Command: 0x34**
939	939
940		-Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
	921	+Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
941	941
942	942
943		-=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
944	944
	925	+=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
945	945
	927	+
946	946	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.
947	947
948	948	(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
...	...	@@ -949,18 +949,19 @@
949	949
950	950	(% style="color:blue" %)**AT Command:**
951	951
952		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
	934	+ (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
953	953
954		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
	936	+ (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
955	955
956	956	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
957	957
958		-Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
	940	+Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
959	959
960	960
961		-=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
962	962
	944	+=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
963	963
	946	+
964	964	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.
965	965
966	966	(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
...	...	@@ -967,61 +967,44 @@
967	967
968	968	(% style="color:blue" %)**AT Command:**
969	969
970		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
	953	+ (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
971	971
972		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
	955	+ (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
973	973
974	974	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
975	975
976		-Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
	959	+Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
977	977
978	978
979		-=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
980	980
	963	+=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
981	981
	965	+
982	982	Users can use this feature to enable/disable Information printing.
983	983
984	984	(% style="color:blue" %)**AT Command:**
985	985
986		-(% 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)
987	987	\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
988	988
989	989
990		-=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
991	991
	975	+=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
992	992
	977	+
993	993	The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
994	994
995	995	(% style="color:blue" %)**AT Command:**
996	996
997		-(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
	982	+(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
998	998
999	999
1000	1000	(% style="color:blue" %)**Downlink Payload:0X24**
1001	1001
1002		-Example: 0x24 01  ~/~/ Same as AT+CHE=1
	987	+Example: 0x24 01 ~/~/ Same as AT+CHE=1
1003	1003
1004	1004
1005		-=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1006	1006
1007		-
1008		-User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1009		-
1010		-(% style="color:blue" %)**AT Command:**
1011		-
1012		-(% style="color:#037691" %)**AT+PT=xx**
1013		-
1014		- Example:
1015		-
1016		- AT+PT=14    ~-~->    Set to detect car motion.
1017		-
1018		- AT+PT=41  ~-~->    set to detect walk motion.
1019		-
1020		-
1021		-(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
1022		-0xB4 14          ~/~/  Same as AT+PT=14
1023		-
1024		-
1025	1025	= 4. Setting for Different Scenarios =
1026	1026
1027	1027
...	...	@@ -1028,6 +1028,7 @@
1028	1028
1029	1029	= 5. Upload Firmware =
1030	1030
	997	+
1031	1031	== 5.1 Firmware Change Log ==
1032	1032
1033	1033
...	...	@@ -1034,6 +1034,7 @@
1034	1034	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
1035	1035
1036	1036
	1004	+
1037	1037	== 5.2 How to upgrade firmware ==
1038	1038
1039	1039
...	...	@@ -1054,10 +1054,10 @@
1054	1054	(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1055	1055
1056	1056
1057		-[[image:1664503563660-578.png||_mstalt="296777"]]
	1025	+[[image:1664503563660-578.png]]
1058	1058
1059	1059
1060		-[[image:1664503574618-659.png||_mstalt="297986"]]
	1028	+[[image:1664503574618-659.png]]
1061	1061
1062	1062
1063	1063
...	...	@@ -1066,7 +1066,7 @@
1066	1066	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1067	1067
1068	1068
1069		-**Users need to use below files:**
	1037	+Users need to use below files:
1070	1070
1071	1071	boot_app0.bin @0e000
1072	1072
...	...	@@ -1073,19 +1073,22 @@
1073	1073	US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1074	1074
1075	1075
1076		-[[image:image-20221207120501-1.png]]
	1044	+[[image:image-20221118105220-2.png]]
1077	1077
1078	1078
1079	1079
1080	1080	After upgrade finish, it will show finish as below:
1081	1081
1082		-[[image:image-20221207133911-7.png]]
	1050	+[[image:image-20221118105402-4.png]]
1083	1083
1084	1084
	1053	+
1085	1085	= 6. Developer Guide =
1086	1086
	1056	+
1087	1087	== 6.1 Compile Source Code ==
1088	1088
	1059	+
1089	1089	=== 6.1.1 Set up ARDUINO compile environment ===
1090	1090
1091	1091
...	...	@@ -1094,81 +1094,24 @@
1094	1094	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]]
1095	1095
1096	1096
1097		-[[image:1664503635019-941.png||_mstalt="294658"]]
	1068	+[[image:1664503635019-941.png]]
1098	1098
1099	1099
1100	1100
1101	1101	* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1102	1102
1103		-[[image:1664503715811-892.png||_mstalt="295698"]]
	1074	+[[image:1664503715811-892.png]]
1104	1104
1105	1105
1106		-=== 6.1.2  Build the development environment ===
1107		-
1108		-
1109		-**~1. Download and install arduino IDE**
1110		-
1111		-[[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]]
1112		-
1113		-
1114		-**2. Download the ESP32 development package in the arduino IDE**
1115		-
1116		-[[image:image-20221213100007-1.png]]
1117		-
1118		-
1119		-Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1120		-
1121		-[[image:image-20221213100626-2.png]]
1122		-
1123		-
1124		-Restart the IDE after the addition is complete, then:
1125		-
1126		-[[image:image-20221213100808-3.png||height="679" width="649"]]
1127		-
1128		-
1129		-[[image:image-20221213101040-4.png]]
1130		-
1131		-
1132		-(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1133		-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)**
1134		-
1135		-
1136		-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:
1137		-
1138		-(% style="color:blue" %)**Methods as below:**
1139		-
1140		-~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1141		-
1142		-2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1143		-
1144	1144	(% 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.
1145	1145
1146		-[[image:image-20221213102311-5.png||height="582" width="711"]]
	1079	+[[image:image-20221024105643-1.png]]
1147	1147
1148		-
1149		-**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1150		-
1151		-[[image:image-20221213102334-6.png]]
1152		-
1153		-(% style="color:red" %)**Note: This step requires a python environment**
1154		-
1155		-
1156		-Either way, in the end:
1157		-
1158		-The final effect is to open the arduino and you can see the esp32
1159		-
1160		-[[image:image-20221213110952-8.png||height="866" width="711"]]
1161		-
1162		-
1163		-
1164		-[[image:image-20221024105643-1.png||_mstalt="428129"]]
1165		-
1166	1166	**~ Figure1**
1167	1167
1168	1168
	1084	+[[image:image-20221024105643-2.png]]
1169	1169
1170		-[[image:image-20221024105643-2.png||_mstalt="428493"]]
1171		-
1172	1172	**Figure2**
1173	1173
1174	1174
...	...	@@ -1177,31 +1177,34 @@
1177	1177	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1178	1178
1179	1179
1180		-[[image:1664503752288-974.png||_mstalt="298194"]]
	1094	+[[image:1664503752288-974.png]]
1181	1181
1182	1182
	1097	+
1183	1183	== 6.2 Source Code ==
1184	1184
1185	1185
1186	1186	* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1187	1187
1188		-[[image:1664503794261-827.png||_mstalt="296387"]]
	1103	+[[image:1664503794261-827.png]]
1189	1189
1190	1190
1191	1191
1192	1192	* (% style="color:blue" %)**Click to upload**
1193	1193
1194		-[[image:1664503808294-336.png||_mstalt="295711"]]
	1109	+[[image:1664503808294-336.png]]
1195	1195
1196	1196
1197	1197
1198	1198	* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1199	1199
1200		-[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
	1115	+[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1201	1201
1202	1202
	1118	+
1203	1203	= 7.  FAQ =
1204	1204
	1121	+
1205	1205	== 7.1 How to change the LoRa Frequency Bands/Region? ==
1206	1206
1207	1207
...	...	@@ -1208,10 +1208,11 @@
1208	1208	User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1209	1209
1210	1210
	1128	+
1211	1211	== 7.2 What is the pin mapping for the USB program cable? ==
1212	1212
1213	1213
1214		-[[image:1664499635206-262.png||_mstalt="295360"]]
	1132	+[[image:1664499635206-262.png]]
1215	1215
1216	1216
1217	1217
...	...	@@ -1226,11 +1226,9 @@
1226	1226	|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1227	1227	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1228	1228
1229		-(% style="display:none" %) (%%)
1230		-
1231		-
1232	1232	== 7.3 Notes on using different serial port tools for TrackerD ==
1233	1233
	1149	+
1234	1234	=== 7.3.1  Serial port utility ===
1235	1235
1236	1236
...	...	@@ -1238,16 +1238,18 @@
1238	1238
1239	1239	Need to adjust the data stream to RTS/CTS on physical restart.
1240	1240
	1157	+
1241	1241	(% class="wikigeneratedid" %)
1242		-[[image:image-20221102140621-1.png||_mstalt="425672"]]
	1159	+[[image:image-20221102140621-1.png]]
1243	1243
1244	1244
1245		-
1246	1246	When using AT commands, the data flow needs to be adjusted to XON/XOFF
1247	1247
1248		-[[image:image-20221102140638-2.png||_mstalt="428727"]]
1249	1249
	1165	+[[image:image-20221102140638-2.png]]
1250	1250
	1167	+
	1168	+
1251	1251	=== 7.3.2  SecureCRT ===
1252	1252
1253	1253
...	...	@@ -1254,22 +1254,23 @@
1254	1254	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.
1255	1255
1256	1256
1257		-[[image:image-20221102140704-3.png||_mstalt="427076"]]
	1175	+[[image:image-20221102140704-3.png]]
1258	1258
1259	1259
1260		-[[image:image-20221102140712-4.png||_mstalt="427089"]]
	1178	+[[image:image-20221102140712-4.png]]
1261	1261
1262	1262
	1181	+
1263	1263	=== 7.3.3  PUTTY ===
1264	1264
1265	1265
1266		-[[image:image-20221102140748-5.png||_mstalt="430456"]]
	1185	+[[image:image-20221102140748-5.png]]
1267	1267
1268	1268
1269	1269	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.
1270	1270
1271	1271
1272		-[[image:image-20221102140801-6.png||_mstalt="427466"]]
	1191	+[[image:image-20221102140801-6.png]]
1273	1273
1274	1274
1275	1275	== 7.4 How to modify source code to compile different frequency band bin file? ==
...	...	@@ -1281,52 +1281,38 @@
1281	1281	See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1282	1282	)))
1283	1283
1284		-**~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.
1285	1285
	1205	+[[image:image-20221116111844-1.png||height="227" width="782"]]
1286	1286
1287		-[[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).
1288	1288
	1209	+[[image:image-20221116111844-2.png||height="262" width="781"]]
1289	1289
	1211	+3.Compile the AS923_JP band, please refer to the intention shown
1290	1290
1291		-**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"]]
1292	1292
	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.
1293	1293
1294		-[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
	1217	+[[image:image-20221116111844-4.png||height="641" width="739"]]
1295	1295
	1219	+[[image:image-20221116111844-5.png||height="551" width="708"]]
1296	1296
1297	1297
1298		-**3. Compile the AS923_JP band, please refer to the intention shown**
1299	1299
1300		-
1301		-[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1302		-
1303		-
1304		-
1305		-**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.**
1306		-
1307		-
1308		-[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1309		-
1310		-
1311		-[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1312		-
1313		-
1314		-== 7.5 Are there example python example for BLE Indoor Positioning? ==
1315		-
1316		-
1317		-[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1318		-
1319		-
1320	1320	= 8  Trouble Shooting =
1321	1321
	1225	+
1322	1322	== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1323	1323
1324	1324
1325	1325	(((
1326		-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
1327	1327	)))
1328	1328
1329	1329
	1234	+
1330	1330	== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1331	1331
1332	1332
...	...	@@ -1335,152 +1335,85 @@
1335	1335	)))
1336	1336
1337	1337
	1243	+
1338	1338	== 8.3  Problem after Upgrading Firmware ==
1339	1339
1340		-=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
	1246	+=== 8.3.1 Continue Restart after upgrading ===
1341	1341
1342	1342
1343		-**Error Output**
1344		-
1345		-
1346		-[[image:image-20221122100004-4.png||_mstalt="424606"]]
1347		-
1348		-
1349	1349	(((
1350		-Some partition is missed during upgrade, please upgrade below four files as example:
1351		-
1352		-[[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
1353	1353	)))
1354	1354
1355	1355
1356		-=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1254	+[[image:image-20221118105249-3.png]]
1357	1357
1358	1358
	1257	+=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1258	+
1359	1359	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
1360	1360
1361	1361
1362		-=== 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 ====
1363	1363
	1264	+[[image:image-20221122100004-1.png||height="497" width="534"]]
1364	1364
1365		-Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
	1266	+ Figure 1
1366	1366
	1268	+ [[image:image-20221122100004-2.png||height="619" width="389"]]
1367	1367
1368		-[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
	1270	+ Figure 2
1369	1369
	1272	+After the upgrade is completed, enter AT+CFG as shown in the figure below.
1370	1370
1371		-User need to upgrade again with below four files to solve this issue.
	1274	+[[image:image-20221122100004-3.png]]
1372	1372
1373		- [[image:image-20221207120530-3.png]]
	1276	+Please AT+FDR, and then enter the following instructions by the information on the label
1374	1374
1375		- **Figure 2**
	1278	+AT+DEUI=70B3D57ED0053981
1376	1376
1377		-
1378		-=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1379		-
1380		-
1381		-User might erase the entire flash include keys and default settings which cause this issue.
1382		-
1383		-After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1384		-
1385		-
1386		-[[image:image-20221122100004-3.png||_mstalt="424242"]]
1387		-
1388		-
1389		-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.
1390		-
1391		-After AT+FDR. please set
1392		-
1393		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1394		-
1395		-* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1396		-
1397		-**Example:**
1398		-
1399		-AT+PDOP=7.00
1400		-
1401		-AT+FTIME=180
1402		-
1403		-AT+DEUI=70B3D57ED0053981
1404		-
1405	1405	AT+APPEUI=D23345667BCBCCAF
1406	1406
1407	1407	AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1408	1408
1409		-AT+DADDR=260b4dce    ( no need for OTAA)
	1284	+AT+DADDR=260b4dce
1410	1410
1411		-AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
	1286	+AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1412	1412
1413		-AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
	1288	+AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1414	1414
1415	1415
1416		-== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1417	1417
	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 ====
1418	1418
1419		-Please download version 1.4.2 again
	1294	+[[image:image-20221122100004-4.png]]
1420	1420
	1296	+== ==
1421	1421
1422		-== 8.5  How to deal with unsuccessful GPS positioning? ==
	1298	+== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
1423	1423
	1300	+Please download version 1.4.2 again
1424	1424
1425		-1） Make Sure the device is in Open Area where can see the sky.
1426	1426
	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.
1427	1427	2)  Set PDOP to a higher value.
1428	1428
1429		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
	1309	+ AT+PDOP=2(can be positioned precisely.）
1430	1430
1431		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
	1311	+ AT+PDOP=7(Quickly locate in open spaces）
1432	1432
1433		-* (% _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）
1434	1434
1435	1435	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	+)))
1436	1436
1437	1437
1438		-== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
	1319	+== ==
1439	1439
1440	1440
1441		-When upgrading, use the erase button to upgrade
1442		-
1443		-[[image:image-20221207120536-4.png]]
1444		-
1445		-
1446		-The parameters are displayed abnormally and cannot be fixed using AT+FDR
1447		-
1448		-[[image:image-20221128103040-2.png||height="431" width="525"]]
1449		-
1450		-
1451		-Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1452		-
1453		-[[image:image-20221207134028-8.png]]
1454		-
1455		-
1456		-Reboot information after upgrade
1457		-
1458		-[[image:image-20221128111443-4.png||height="432" width="546"]]
1459		-
1460		-
1461		-Use **AT+FDR** command to reset and then use **AT+CFG** to check whether the configuration is back to normal
1462		-
1463		-[[image:image-20221128111850-5.png]]
1464		-
1465		-
1466		-After the parameters return to normal, upgrade to the version you need again
1467		-
1468		-[[image:image-20221207120601-5.png]]
1469		-
1470		-
1471		-At this point, the parameters return to normal after running AT+FDR again
1472		-
1473		-[[image:image-20221128112035-7.png]]
1474		-
1475		-
1476		-== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1477		-
1478		-
1479		-~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1480		-
1481		-2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1482		-
1483		-
1484	1484	= 9.  Order Info =
1485	1485
1486	1486
...	...	@@ -1489,22 +1489,13 @@
1489	1489	(% style="color:blue" %)**XXX**(%%): The default frequency band
1490	1490
1491	1491	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1492		-
1493	1493	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1494		-
1495	1495	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1496		-
1497	1497	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1498		-
1499	1499	* (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1500		-
1501	1501	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1502		-
1503	1503	* (% style="color:red" %)**US915**(%%): Default frequency band US915
1504	1504
1505		-(% style="display:none" %) (%%)
1506		-
1507		-
1508	1508	= 10.  Packing Info =
1509	1509
1510	1510
...	...	@@ -1511,36 +1511,22 @@
1511	1511	(% style="color:#037691" %)**Package Includes**:
1512	1512
1513	1513	* TrackerD LoRaWAN GPS/BLE Tracker x 1
1514		-
1515	1515	* USB recharge & program cable x 1
1516	1516
1517	1517	(% style="color:#037691" %)**Dimensions and Weight**:
1518	1518
1519	1519	* Device Size: 85 x 48 x 15 mm
1520		-
1521	1521	* Weight: 50g
1522	1522
1523		-(% style="display:none" %) (%%)
1524		-
1525		-
1526	1526	= 11. Support =
1527	1527
1528	1528
1529	1529	* 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.
1530		-
1531	1531	* 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]].
1532	1532
1533		-(% style="display:none" %) (%%)
1534		-
1535		-
1536	1536	= 12.  Reference =
1537	1537
1538	1538
1539	1539	* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1540		-
1541	1541	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
1542		-
1543	1543	* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1544		-
1545		-
1546		-)))

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

image-20230302145315-1.png

Author

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

Size

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

Content