Changes for page TrackerD -- LoRaWAN Tracker User Manual

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 23 added, 0 removed)
  • 1667288597595-714.png
  • image-20221024105643-1.png
  • image-20221024105643-2.png
  • image-20221102140621-1.png
  • image-20221102140638-2.png
  • image-20221102140704-3.png
  • image-20221102140712-4.png
  • image-20221102140748-5.png
  • image-20221102140801-6.png
  • image-20221107145243-1.png
  • image-20221116111844-1.png
  • image-20221116111844-2.png
  • image-20221116111844-3.png
  • image-20221116111844-4.png
  • image-20221116111844-5.png
  • image-20221118104359-1.png
  • image-20221118105220-2.png
  • image-20221118105249-3.png
  • image-20221118105402-4.png
  • image-20221122100004-1.png
  • image-20221122100004-2.png
  • image-20221122100004-3.png
  • image-20221122100004-4.png

Details

Page properties

Content

...	...	@@ -1,5 +1,5 @@
1	1	(% style="text-align:center" %)
2		-[[image:1664505654417-133.png]]
	2	+[[image:1664505654417-133.png||_mstalt="293696"]]
3	3
4	4
5	5
...	...	@@ -14,7 +14,6 @@
14	14
15	15	= 1.  Introduction =
16	16
17		-
18	18	== 1.1  What is TrackerD ==
19	19
20	20
...	...	@@ -40,13 +40,12 @@
40	40
41	41	)))
42	42
43		-[[image:1664499921684-770.png]]
	42	+[[image:1664499921684-770.png||_mstalt="298194"]]
44	44
45	45
46	46	(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
47	47
48	48
49		-
50	50	== 1.2 Specifications ==
51	51
52	52
...	...	@@ -121,9 +121,8 @@
121	121	* Logistics and Supply Chain Management
122	122	* Human tracking
123	123
124		-= 2.1 Use TrackerD =
	122	+= 2.  Use TrackerD =
125	125
126		-
127	127	== 2.1 How it works? ==
128	128
129	129
...	...	@@ -130,7 +130,6 @@
130	130	TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
131	131
132	132
133		-
134	134	== 2.2 Quick guide to connect to LoRaWAN server ==
135	135
136	136
...	...	@@ -137,7 +137,7 @@
137	137	Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example.
138	138
139	139
140		-[[image:1664501652064-326.png]]
	136	+[[image:1664501652064-326.png||_mstalt="293306"]]
141	141
142	142
143	143
...	...	@@ -149,7 +149,7 @@
149	149	Each TrackerD is shipped with a sticker with the default device EUI as below:
150	150
151	151
152		-[[image:1664501677253-891.png]]
	148	+[[image:1664501677253-891.png||_mstalt="296569"]]
153	153
154	154
155	155	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
...	...	@@ -158,14 +158,14 @@
158	158	**__Add APP EUI in the application:__**
159	159
160	160
161		-[[image:1664501711466-918.png]]
	157	+[[image:1664501711466-918.png||_mstalt="295828"]]
162	162
163	163
164	164
165		-[[image:1664501721248-725.png]]
	161	+[[image:1664501721248-725.png||_mstalt="294450"]]
166	166
167	167
168		-[[image:1664501734705-405.png]]
	164	+[[image:1664501734705-405.png||_mstalt="293306"]]
169	169
170	170
171	171
...	...	@@ -172,34 +172,34 @@
172	172	**__Add APP KEY and DEV EUI:__**
173	173
174	174
175		-[[image:1664501784668-703.png]]
	171	+[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
176	176
177	177
178	178
	175	+(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
179	179
180		-(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
	177	+(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
181	181
	179	+[[image:1664502835802-546.png||_mstalt="295061"]]
182	182
	181	+
183	183	(% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
184	184
185	185
186		-
187	187	== 2.3  Positioning Mode(SMOD) ==
188	188
189	189
190	190	Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
191	191
192		-* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
193		-* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
194		-* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
	190	+* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
	191	+* (% style="color:#037691" %)**BLE or WiFi ONLY:            **(%%)** **Only obtain iBeacon info via BLE and uplink  or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking.
	192	+* (% style="color:#037691" %)**GPS/BLE Hybrid:                        **(%%)Combination for Indoor and Outdoor tracking. Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
195	195
196	196	Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
197	197
198	198
199		-
200	200	== 2.4  Uplink Payload ==
201	201
202		-
203	203	=== 2.4.1 Uplink FPORT~=5, Device Status ===
204	204
205	205
...	...	@@ -208,11 +208,11 @@
208	208	Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
209	209
210	210
211		-(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
212		-|=(% scope="row" style="width: 108px;" %)**Size(bytes)**|=(% style="width: 82px;" %)**1**|=(% style="width: 83px;" %)**2**|=(% style="width: 94px;" %)**1**|=(% style="width: 84px;" %)**1**|=(% style="width: 44px;" %)2|=(% style="width: 63px;" %)**2**|=(% style="width: 60px;" %)1
	207	+(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
	208	+|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
213	213	|=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
214	214
215		-[[image:1665301570342-765.png]]
	211	+[[image:1665301570342-765.png||_mstalt="294580"]]
216	216
217	217
218	218	(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
...	...	@@ -253,12 +253,11 @@
253	253	Use can also get the Device Status uplink through the downlink command:
254	254
255	255
256		-
257	257	(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
258	258
259		-(% border="1.5" style="background-color:#ffffcc; color:green; width:420px" %)
260		-|(% style="width:75px" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:137px" %)2bit|(% style="width:142px" %)4bit
261		-|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:137px" %)GPS_Settings|(% style="width:142px" %)BLE_Settings
	254	+(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
	255	+|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
	256	+|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
262	262
263	263	(% style="color:blue" %)** SMOD：**
264	264
...	...	@@ -280,30 +280,27 @@
280	280
281	281	(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
282	282
	278	+(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)
283	283
284	284
285	285	(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
286	286
287		-(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
288		-|(% style="width:77px" %)**Size(bit)**|(% style="width:82px" %)5 Bits|(% style="width:106px" %)1 Bit|(% style="width:67px" %)1 Bit|(% style="width:121px" %)1 Bit
289		-|(% style="width:77px" %)**Value**|(% style="width:82px" %)Reserve|(% style="width:106px" %)PNACKMD|(% style="width:67px" %)LON|(% style="width:121px" %)Transport** **Mode
	283	+(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
	284	+|=(% 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
	285	+|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
290	290
291		-
292		-
293	293	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
294	294
295	295
296	296	Users can use **AT+SMOD=1,0,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
297	297
298		-(% style="color:red" %)Please note that 15 bytes won't work on DR0 on US915/AU915 frequency band. IoT server will see NULL payload in this case.(%%)
299	299
300		-
301		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
302		-|=(% scope="row" style="width: 50px;" %)(((
	293	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
	294	+|=(% scope="row" style="width: 60px;" %)(((
303	303	**Size(bytes)**
304		-)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
	296	+)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
305	305	2
306		-)))|(% style="width:87px" %)(((
	298	+)))|(% style="width:30px" %)(((
307	307	2
308	308	)))
309	309	|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
...	...	@@ -310,7 +310,7 @@
310	310	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
311	311	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
312	312
313		-[[image:1665301636888-168.png]]
	305	+[[image:1665301636888-168.png||_mstalt="298012"]]
314	314
315	315
316	316	==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
...	...	@@ -321,8 +321,8 @@
321	321
322	322	==== (% style="color:blue" %)**FLAG:**(%%) ====
323	323
324		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
325		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
	316	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
	317	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
326	326	|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
327	327
328	328	**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
...	...	@@ -340,12 +340,12 @@
340	340	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:
341	341
342	342
343		-[[image:1664502116362-706.png]]
	335	+[[image:1664502116362-706.png||_mstalt="293306"]]
344	344
345	345
346	346	3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
347	347
348		-[[image:1664502166010-515.png]]
	340	+[[image:1664502166010-515.png||_mstalt="291395"]]
349	349
350	350
351	351
...	...	@@ -370,7 +370,7 @@
370	370
371	371	==== (% style="color:blue" %)**MOD:**(%%) ====
372	372
373		-**Example: ** (0x60>>6)& 0x3f =1.
	365	+**Example: ** (0x60>>6) & 0x3f =1
374	374
375	375	**Set the format of GPS data uplink link：**
376	376
...	...	@@ -398,7 +398,6 @@
398	398	)))
399	399
400	400
401		-
402	402	==== (% style="color:blue" %)**Hum:**(%%) ====
403	403
404	404	0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
...	...	@@ -409,52 +409,55 @@
409	409	011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
410	410
411	411
412		-
413	413	=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
414	414
415	415
416		-The default uplink payload includes totally 11 bytes. The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
	406	+The default uplink payload includes total 11 bytes (**AT+SMOD=1,1,0**). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
417	417
418	418
419		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
420		-|=(% scope="row" style="width: 50px;" %)(((
	409	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
	410	+|=(% scope="row" style="width: 60px;" %)(((
421	421	**Size(bytes)**
422		-)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
	412	+)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
423	423	|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
424	424	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
425	425	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
426	426
427	427	(% class="wikigeneratedid" %)
428		-[[image:1665301687277-443.png]]
	418	+[[image:1665301687277-443.png||_mstalt="296140"]]
429	429
430	430
431		-
432	432	=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
433	433
434	434
435		-Set [[PNACKMD=1>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H4.13AutoSendNone-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.
	424	+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.
436	436
437	437
438	438	(% style="color:red" %)**Note for this mode:**
439	439
440	440	* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
441		-* b) TrackerD will send data in (% style="color:blue" %)**CONFIRMED Mode**(%%) when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
	430	+* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
	431	+* c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL
442	442
443	443	The payload is 15 bytes, as below.
444	444
445		-(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
	435	+(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
446	446	|=(% scope="row" %)(((
447	447	**Size(bytes)**
448	448	)))|4|4|2|1|1|1|1|1
449	449	|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
450	450
451		-[[image:image-20221009160309-2.png]]
	441	+[[image:image-20221009160309-2.png||_mstalt="429312"]]
452	452
453	453
454		-
455	455	=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
456	456
457	457
	447	+TrackerD supports BLE scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan BLE iBeacon and find the strongest iBeacon info and uplink.
	448	+
	449	+User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
	450	+
	451	+
458	458	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
459	459	|=(% scope="row" style="width: 60px;" %)(((
460	460	**Size(bytes)**
...	...	@@ -471,84 +471,97 @@
471	471	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
472	472	)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
473	473
474		-[[image:1664502425687-834.png]]
	468	+[[image:1664502425687-834.png||_mstalt="296738"]]
475	475
476	476
477		-* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
	471	+* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
478	478	* (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
479	479	* (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
480	480	* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
481		-* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
	475	+* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
482	482	* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
483	483	* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
484	484
485		-=== 2.4.6  Add Payload format in TTN V3 ===
	479	+=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
486	486
487	487
488		-In TTN V3, use can add a custom payload so it shows friendly.
	482	+TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
489	489
	484	+
	485	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
	486	+|=(% scope="row" style="width: 60px;" %)(((
	487	+**Size(bytes)**
	488	+)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
	489	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
	490	+[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
	491	+)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
	492	+
	493	+(% class="wikigeneratedid" %)
	494	+[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
	495	+
	496	+
	497	+* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
	498	+* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
	499	+* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
	500	+
	501	+=== 2.4.7  Add Payload format in TTN V3 ===
	502	+
	503	+
	504	+In TTN V3, user can add a custom payload so it shows friendly.
	505	+
490	490	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
491	491
492	492
493		-[[image:1664502649601-895.png]]
	509	+[[image:1664502649601-895.png||_mstalt="296985"]]
494	494
495	495
496		-Add the decoder from this link:
497	497
	513	+Add the decoder from this link:
498	498
	515	+[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
	516	+
499	499	Save the change the uplink message will be parsed. As below:
500	500
501		-[[image:1664502676891-606.png]]
	519	+[[image:1664502676891-606.png||_mstalt="296673"]]
502	502
503	503
504		-
505	505	== 2.5 Integrate with Datacake ==
506	506
507	507
508		-(((
509	509	After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
510		-)))
511	511
512		-(((
513	513	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]]
514		-)))
515	515
516	516
517		-[[image:1664502695771-538.png]]
	530	+[[image:1664502695771-538.png||_mstalt="297349"]]
518	518
519	519
520		-
521	521	== 2.6 Integrate with Tago ==
522	522
523	523
524		-(((
525		-After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
526		-)))
	536	+After TrackerD sends data to LoRaWAN server such as TTN, user can pass the data to Datacake and plot out, currently only support GPS plot.
527	527
528		-(((
529	529	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]]
530		-)))
531	531
532	532
533		-[[image:1664502715371-321.png]]
	541	+[[image:1664502715371-321.png||_mstalt="292162"]]
534	534
535	535
536		-
537	537	== 2.7  Datalog Feature ==
538	538
539	539
540		-total 273 entries,by default disable
	547	+total 273 entries,by default,
541	541
	549	+User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
542	542
543	543	Example use case.
544	544
545		-[[image:image-20221009234703-2.png||height="328" width="899"]]
	553	+[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
546	546
547	547
548		-[[image:image-20221009234629-1.png||height="390" width="577"]]
	556	+[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
549	549
550	550
551		-
552	552	== 2.8 Alarm Mode ==
553	553
554	554
...	...	@@ -558,15 +558,15 @@
558	558
559	559
560	560	(((
561		-Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode.
	568	+Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exits alert mode.
562	562	)))
563	563
564	564
565	565	(((
566		-Two ways to exit alarm mode:
	573	+**Two ways to exit alarm mode:**
567	567	)))
568	568
569		-* Server send a downlink command to exit.
	576	+* Server sends a downlink command to exit.
570	570	* User fast press the RED button 10 times.
571	571
572	572	(((
...	...	@@ -574,7 +574,6 @@
574	574	)))
575	575
576	576
577		-
578	578	== 2.9 Transport Mode ==
579	579
580	580
...	...	@@ -581,17 +581,16 @@
581	581	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.
582	582
583	583
584		-
585	585	== 2.10 LED Status ==
586	586
587	587
588		-(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
	593	+(% border="1.5" style="background-color:#ffffcc; width:500px" %)
589	589	|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
590	590	|(% style="width:157px" %)**Power On**|(% style="width:271px" %)(% style="color:blue" %)**BLUE, **(% style="color:red" %)**RED , **(% style="color:green" %)**Green** flash once|(% style="width:202px" %)N/A
591	591	|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
592	592	|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
593	593	|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
594		-|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
	599	+|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
595	595	|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
596	596	|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
597	597	|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
...	...	@@ -604,7 +604,7 @@
604	604
605	605	(% style="color:blue" %)**RESET button:**
606	606
607		-[[image:1664502835802-546.png]]
	612	+[[image:1664502835802-546.png||_mstalt="295061"]]
608	608
609	609	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
610	610
...	...	@@ -611,12 +611,12 @@
611	611
612	612	(% style="color:red" %)**RED button:**
613	613
614		-[[image:1664502854406-763.png]]
	619	+[[image:1664502854406-763.png||_mstalt="295568"]]
615	615
616	616
617		-(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
618		-|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
619		-|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.6AlarmMode"]]
	622	+(% border="1" style="background-color:#ffffcc; width:510px" %)
	623	+|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
	624	+|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.8AlarmMode"]]
620	620	|(% 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
621	621	|(% 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.
622	622
...	...	@@ -638,7 +638,6 @@
638	638	LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
639	639
640	640
641		-
642	642	== 3.1 Access AT Command ==
643	643
644	644
...	...	@@ -645,27 +645,24 @@
645	645	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.
646	646
647	647
648		-[[image:1664502999401-486.png]]
	652	+[[image:1664502999401-486.png||_mstalt="296985"]]
649	649
650	650
651	651	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:
652	652
653	653
654		-[[image:1664503022490-662.png]]
	658	+[[image:1664503022490-662.png||_mstalt="293332"]]
655	655
656	656
	661	+[[image:1664503035713-500.png||_mstalt="291096"]]
657	657
658		-[[image:1664503035713-500.png]]
659	659
	664	+[[image:1664503047675-651.png||_mstalt="295386"]]
660	660
661	661
662		-[[image:1664503047675-651.png]]
663	663
664		-
665		-
666	666	== 3.2 Command Set ==
667	667
668		-
669	669	=== 3.2.1 Set Transmit Interval ===
670	670
671	671
...	...	@@ -683,7 +683,6 @@
683	683	(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
684	684
685	685
686		-
687	687	=== 3.2.2 Set Alarm Packet transmission interval ===
688	688
689	689
...	...	@@ -701,7 +701,6 @@
701	701	(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
702	702
703	703
704		-
705	705	=== 3.2.3 Set Transport Mode Packet transmission interval ===
706	706
707	707
...	...	@@ -716,10 +716,9 @@
716	716
717	717	* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
718	718
719		-(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
	718	+(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
720	720
721	721
722		-
723	723	=== 3.2.4 Exit Alarm ===
724	724
725	725
...	...	@@ -732,7 +732,6 @@
732	732	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
733	733
734	734
735		-
736	736	=== 3.2.5 Disable/Enable LED flash ===
737	737
738	738
...	...	@@ -750,7 +750,6 @@
750	750	(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
751	751
752	752
753		-
754	754	=== 3.2.6 Disable/Enable Transport Mode ===
755	755
756	756
...	...	@@ -760,19 +760,18 @@
760	760
761	761	(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
762	762
763		-Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
	759	+Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
764	764
765	765
766	766	* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
767	767
768		-(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
	764	+(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
769	769
770	770
771		-
772	772	=== 3.2.7 Set Positioning Mode ===
773	773
774	774
775		-SMOD define the how TrackerD scan and uplink data:
	770	+SMOD define how TrackerD scan and uplink data:
776	776
777	777
778	778	* (% style="color:blue" %)**AT Command:**
...	...	@@ -781,32 +781,40 @@
781	781
782	782	(% style="color:#037691" %)** aa:**
783	783
784		-* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
785		-* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
786		-* (% style="color:red" %)**3: GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
	779	+* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
787	787
	781	+* (% style="color:red" %)**2: BLE or WiFi ONLY:                     **(%%)Only obtain iBeacon info via BLE and uplink  or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking.
	782	+
	783	+* (% style="color:red" %)**3: GPS/BLE Hybrid:                       **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
	784	+
788	788	(% style="color:#037691" %)**bb:**
789	789
790	790	* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
	788	+
791	791	* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
792	792
793	793	(% style="color:#037691" %)**cc:   **
794	794
795		-* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
	793	+* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
	794	+
	795	+* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))
796	796
797	797	(% style="color:blue" %)**Example:**
798	798
799		- AT+ SMOD =1,0 ,0 ~-~->  GPS+ BAT+ State+Tem&Hum
800		- AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
801		- AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
	799	+ AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
802	802
	801	+ AT+SMOD=1,1,0 ~-~->  GPS +BAT State
803	803
804		-* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
	803	+ AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
805	805
806		-(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
	805	+ AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
807	807
808	808
	808	+* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
809	809
	810	+(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
	811	+
	812	+
810	810	=== 3.2.8 Set MAX GPS position time ===
811	811
812	812
...	...	@@ -813,7 +813,7 @@
813	813	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.
814	814
815	815
816		-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.
	819	+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.
817	817
818	818
819	819	* (% style="color:blue" %)**AT Command:**
...	...	@@ -828,7 +828,6 @@
828	828	(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
829	829
830	830
831		-
832	832	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
833	833
834	834
...	...	@@ -853,7 +853,7 @@
853	853
854	854
855	855
856		-Disable/Enable the confirmation mode
	858	+**Disable/Enable the confirmation mode**
857	857
858	858	* (% style="color:blue" %)**AT Command:**
859	859
...	...	@@ -862,17 +862,16 @@
862	862
863	863	**~ Example:**
864	864
865		- AT+ CFM=0    **~-~->   ** Disable confirmation
	867	+ AT+CFM=0    **~-~->   ** Disable confirmation
866	866
867		- AT+ CFM=1    **~-~->  ** Enable confirmation
	869	+ AT+CFM=1    **~-~->  ** Enable confirmation
868	868
869	869
870	870	* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
871	871
872		-(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
	874	+(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
873	873
874	874
875		-
876	876	=== 3.2.10  Auto Send None-ACK messages ===
877	877
878	878
...	...	@@ -894,6 +894,68 @@
894	894	Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
895	895
896	896
	898	+=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
	899	+
	900	+
	901	+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.
	902	+
	903	+(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
	904	+
	905	+(% style="color:blue" %)**AT Command:**
	906	+
	907	+ (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
	908	+
	909	+ (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
	910	+
	911	+(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
	912	+
	913	+Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
	914	+
	915	+
	916	+=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
	917	+
	918	+
	919	+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.
	920	+
	921	+(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
	922	+
	923	+(% style="color:blue" %)**AT Command:**
	924	+
	925	+ (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
	926	+
	927	+ (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
	928	+
	929	+(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
	930	+
	931	+Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
	932	+
	933	+
	934	+=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
	935	+
	936	+
	937	+Users can use this feature to enable/disable Information printing.
	938	+
	939	+(% style="color:blue" %)**AT Command:**
	940	+
	941	+(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
	942	+\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
	943	+
	944	+
	945	+=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
	946	+
	947	+
	948	+The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
	949	+
	950	+(% style="color:blue" %)**AT Command:**
	951	+
	952	+(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
	953	+
	954	+
	955	+(% style="color:blue" %)**Downlink Payload:0X24**
	956	+
	957	+Example: 0x24 01 ~/~/ Same as AT+CHE=1
	958	+
	959	+
897	897	= 4. Setting for Different Scenarios =
898	898
899	899
...	...	@@ -900,7 +900,6 @@
900	900
901	901	= 5. Upload Firmware =
902	902
903		-
904	904	== 5.1 Firmware Change Log ==
905	905
906	906
...	...	@@ -907,7 +907,6 @@
907	907	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
908	908
909	909
910		-
911	911	== 5.2 How to upgrade firmware ==
912	912
913	913
...	...	@@ -928,40 +928,39 @@
928	928	(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
929	929
930	930
931		-[[image:1664503563660-578.png]]
	992	+[[image:1664503563660-578.png||_mstalt="296777"]]
932	932
933	933
934		-[[image:1664503574618-659.png]]
	995	+[[image:1664503574618-659.png||_mstalt="297986"]]
935	935
936	936
	998	+
937	937	(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
938	938
939	939	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
940	940
941	941
942		-Users need to use below files:
	1004	+**Users need to use below files:**
943	943
944	944	boot_app0.bin @0e000
945	945
946		-ESP_LORA-eeprom-class.bin @ 0x10000
	1008	+US915.bin @ 0x10000(Select the bin file of the frequency band you need)
947	947
948	948
949		-[[image:1664503593459-435.png]]
	1011	+[[image:image-20221118105220-2.png||_mstalt="426608"]]
950	950
951	951
952	952
953	953	After upgrade finish, it will show finish as below:
954	954
955		-[[image:1664503611848-385.png]]
	1017	+[[image:image-20221118105402-4.png||_mstalt="427986"]]
956	956
957	957
958	958
959	959	= 6. Developer Guide =
960	960
961		-
962	962	== 6.1 Compile Source Code ==
963	963
964		-
965	965	=== 6.1.1 Set up ARDUINO compile environment ===
966	966
967	967
...	...	@@ -970,49 +970,57 @@
970	970	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]]
971	971
972	972
973		-[[image:1664503635019-941.png]]
	1033	+[[image:1664503635019-941.png||_mstalt="294658"]]
974	974
975	975
976	976
977	977	* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
978	978
979		-[[image:1664503715811-892.png]]
	1039	+[[image:1664503715811-892.png||_mstalt="295698"]]
980	980
981	981
	1042	+(% 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.
982	982
	1044	+[[image:image-20221024105643-1.png||_mstalt="428129"]]
	1045	+
	1046	+**~ Figure1**
	1047	+
	1048	+
	1049	+[[image:image-20221024105643-2.png||_mstalt="428493"]]
	1050	+
	1051	+ **Figure2**
	1052	+
	1053	+
983	983	* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
984	984
985	985	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
986	986
987	987
988		-[[image:1664503752288-974.png]]
	1059	+[[image:1664503752288-974.png||_mstalt="298194"]]
989	989
990	990
991		-
992	992	== 6.2 Source Code ==
993	993
994	994
995	995	* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
996	996
997		-[[image:1664503794261-827.png]]
	1067	+[[image:1664503794261-827.png||_mstalt="296387"]]
998	998
999	999
1000	1000
1001	1001	* (% style="color:blue" %)**Click to upload**
1002	1002
1003		-[[image:1664503808294-336.png]]
	1073	+[[image:1664503808294-336.png||_mstalt="295711"]]
1004	1004
1005	1005
1006	1006
1007	1007	* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1008	1008
1009		-[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
	1079	+[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1010	1010
1011	1011
1012		-
1013	1013	= 7.  FAQ =
1014	1014
1015		-
1016	1016	== 7.1 How to change the LoRa Frequency Bands/Region? ==
1017	1017
1018	1018
...	...	@@ -1019,11 +1019,10 @@
1019	1019	User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1020	1020
1021	1021
1022		-
1023	1023	== 7.2 What is the pin mapping for the USB program cable? ==
1024	1024
1025	1025
1026		-[[image:1664499635206-262.png]]
	1093	+[[image:1664499635206-262.png||_mstalt="295360"]]
1027	1027
1028	1028
1029	1029
...	...	@@ -1038,45 +1038,251 @@
1038	1038	|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1039	1039	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1040	1040
1041		-= 8.  Order Info =
	1108	+== 7.3 Notes on using different serial port tools for TrackerD ==
1042	1042
	1110	+=== 7.3.1  Serial port utility ===
1043	1043
	1112	+
	1113	+Serial port utility requires you to automatically add data streams.
	1114	+
	1115	+Need to adjust the data stream to RTS/CTS on physical restart.
	1116	+
	1117	+(% class="wikigeneratedid" %)
	1118	+[[image:image-20221102140621-1.png||_mstalt="425672"]]
	1119	+
	1120	+
	1121	+
	1122	+When using AT commands, the data flow needs to be adjusted to XON/XOFF
	1123	+
	1124	+[[image:image-20221102140638-2.png||_mstalt="428727"]]
	1125	+
	1126	+
	1127	+=== 7.3.2  SecureCRT ===
	1128	+
	1129	+
	1130	+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.
	1131	+
	1132	+
	1133	+[[image:image-20221102140704-3.png||_mstalt="427076"]]
	1134	+
	1135	+
	1136	+[[image:image-20221102140712-4.png||_mstalt="427089"]]
	1137	+
	1138	+
	1139	+=== 7.3.3  PUTTY ===
	1140	+
	1141	+
	1142	+[[image:image-20221102140748-5.png||_mstalt="430456"]]
	1143	+
	1144	+
	1145	+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.
	1146	+
	1147	+
	1148	+[[image:image-20221102140801-6.png||_mstalt="427466"]]
	1149	+
	1150	+
	1151	+== 7.4 How to modify source code to compile different frequency band bin file? ==
	1152	+
	1153	+
	1154	+(% class="box infomessage" %)
	1155	+(((
	1156	+(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
	1157	+See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
	1158	+)))
	1159	+
	1160	+**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
	1161	+
	1162	+
	1163	+[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
	1164	+
	1165	+
	1166	+
	1167	+**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
	1168	+
	1169	+
	1170	+[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
	1171	+
	1172	+
	1173	+
	1174	+**3. Compile the AS923_JP band, please refer to the intention shown**
	1175	+
	1176	+
	1177	+[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
	1178	+
	1179	+
	1180	+
	1181	+**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.**
	1182	+
	1183	+
	1184	+[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
	1185	+
	1186	+
	1187	+[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
	1188	+
	1189	+
	1190	+= 8  Trouble Shooting =
	1191	+
	1192	+== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
	1193	+
	1194	+
	1195	+(((
	1196	+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
	1197	+)))
	1198	+
	1199	+
	1200	+== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
	1201	+
	1202	+
	1203	+(((
	1204	+ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.
	1205	+)))
	1206	+
	1207	+
	1208	+== 8.3  Problem after Upgrading Firmware ==
	1209	+
	1210	+=== 8.3.1 Continue Restart after upgrading ===
	1211	+
	1212	+
	1213	+(((
	1214	+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
	1215	+)))
	1216	+
	1217	+
	1218	+[[image:image-20221118105249-3.png||_mstalt="430664"]]
	1219	+
	1220	+
	1221	+=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1222	+
	1223	+
	1224	+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
	1225	+
	1226	+
	1227	+=== 8.3.3 "flash read err" after upgrade firmware ===
	1228	+
	1229	+Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
	1230	+
	1231	+[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
	1232	+
	1233	+
	1234	+User need to upgrade again with below four files to solve this issue.
	1235	+
	1236	+ [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
	1237	+
	1238	+ **Figure 2**
	1239	+
	1240	+
	1241	+=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
	1242	+
	1243	+User might erase the entire flash include keys and default settings which cause this issue.
	1244	+
	1245	+After the upgrade is completed, enter AT+CFG as shown in the figure below.
	1246	+
	1247	+[[image:image-20221122100004-3.png||_mstalt="424242"]]
	1248	+
	1249	+Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
	1250	+
	1251	+After AT+FDR. please set
	1252	+
	1253	+* AT+PDOP=7
	1254	+* AT+FTIME=180000
	1255	+
	1256	+
	1257	+Example:
	1258	+
	1259	+AT+PDOP=7.00
	1260	+
	1261	+AT+FTIME=180
	1262	+
	1263	+AT+DEUI=70B3D57ED0053981
	1264	+
	1265	+AT+APPEUI=D23345667BCBCCAF
	1266	+
	1267	+AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
	1268	+
	1269	+AT+DADDR=260b4dce    ( no need for OTAA)
	1270	+
	1271	+AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
	1272	+
	1273	+AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
	1274	+
	1275	+
	1276	+
	1277	+=== 8.3.4  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 ===
	1278	+
	1279	+
	1280	+[[image:image-20221122100004-4.png||_mstalt="424606"]]
	1281	+
	1282	+
	1283	+== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
	1284	+
	1285	+
	1286	+Please download version 1.4.2 again
	1287	+
	1288	+
	1289	+== 8.5  How to deal with unsuccessful GPS positioning? ==
	1290	+
	1291	+
	1292	+1） Make Sure the device is in Open Area where can see the sky.
	1293	+
	1294	+2)  Set PDOP to a higher value.
	1295	+
	1296	+* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
	1297	+
	1298	+* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
	1299	+
	1300	+* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
	1301	+
	1302	+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
	1303	+
	1304	+
	1305	+= 9.  Order Info =
	1306	+
	1307	+
1044	1044	Part Number: (% style="color:blue" %)**TrackerD-XXX**
1045	1045
1046	1046	(% style="color:blue" %)**XXX**(%%): The default frequency band
1047	1047
1048	1048	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
	1313	+
1049	1049	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
	1315	+
1050	1050	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
	1317	+
1051	1051	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
	1319	+
1052	1052	* (% style="color:red" %)**AS923**(%%): Default frequency band AS923
	1321	+
1053	1053	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
	1323	+
1054	1054	* (% style="color:red" %)**US915**(%%): Default frequency band US915
1055	1055
1056		-= 9.  Packing Info =
	1326	+= 10.  Packing Info =
1057	1057
1058	1058
1059	1059	(% style="color:#037691" %)**Package Includes**:
1060	1060
1061	1061	* TrackerD LoRaWAN GPS/BLE Tracker x 1
	1332	+
1062	1062	* USB recharge & program cable x 1
1063	1063
1064	1064	(% style="color:#037691" %)**Dimensions and Weight**:
1065	1065
1066		-* Device Size: 85 x 48 x 15 cm
	1337	+* Device Size: 85 x 48 x 15 mm
	1338	+
1067	1067	* Weight: 50g
1068	1068
1069		-= 10. Support =
	1341	+= 11. Support =
1070	1070
1071	1071
1072	1072	* 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.
	1345	+
1073	1073	* 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]].
1074	1074
1075		-= 11.  Reference =
	1348	+= 12.  Reference =
1076	1076
1077	1077
1078	1078	* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	1352	+
1079	1079	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
1080		-* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1081	1081
1082		-
	1355	+* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]

1667288597595-714.png

Author

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

Size

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

Content

image-20221024105643-1.png

Author

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

Size

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

Content

image-20221024105643-2.png

Author

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

Size

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

Content

image-20221102140621-1.png

Author

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

Size

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

Content

image-20221102140638-2.png

Author

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

Size

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

Content

image-20221102140704-3.png

Author

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

Size

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

Content

image-20221102140712-4.png

Author

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

Size

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

Content

image-20221102140748-5.png

Author

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

Size

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

Content

image-20221102140801-6.png

Author

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

Size

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

Content

image-20221107145243-1.png

Author

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

Size

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

Content

image-20221116111844-1.png

Author

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

Size

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

Content

image-20221116111844-2.png

Author

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

Size

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

Content

image-20221116111844-3.png

Author

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

Size

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

Content

image-20221116111844-4.png

Author

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

Size

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

Content

image-20221116111844-5.png

Author

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

Size

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

Content

image-20221118104359-1.png

Author

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

Size

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

Content

image-20221118105220-2.png

Author

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

Size

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

Content

image-20221118105249-3.png

Author

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

Size

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

Content

image-20221118105402-4.png

Author

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

Size

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

Content

image-20221122100004-1.png

Author

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

Size

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

Content

image-20221122100004-2.png

Author

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

Size

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

Content

image-20221122100004-3.png

Author

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

Size

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

Content

image-20221122100004-4.png

Author

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

Size

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

Content