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

Summary

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

Author

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

Content

...	...	@@ -14,6 +14,7 @@
14	14
15	15	= 1.  Introduction =
16	16
	17	+
17	17	== 1.1  What is TrackerD ==
18	18
19	19
...	...	@@ -45,6 +45,7 @@
45	45	(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
46	46
47	47
	49	+
48	48	== 1.2 Specifications ==
49	49
50	50
...	...	@@ -96,6 +96,7 @@
96	96	* Tracking: max: 38mA
97	97
98	98
	101	+
99	99	== 1.3  Features ==
100	100
101	101
...	...	@@ -115,6 +115,7 @@
115	115	* Datalog
116	116
117	117
	121	+
118	118	== 1.4  Applications ==
119	119
120	120
...	...	@@ -122,8 +122,10 @@
122	122	* Human tracking
123	123
124	124
125		-= 2.  Use TrackerD =
126	126
	130	+= 2.1 Use TrackerD =
	131	+
	132	+
127	127	== 2.1 How it works? ==
128	128
129	129
...	...	@@ -130,6 +130,7 @@
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
	139	+
133	133	== 2.2 Quick guide to connect to LoRaWAN server ==
134	134
135	135
...	...	@@ -171,34 +171,34 @@
171	171	**__Add APP KEY and DEV EUI:__**
172	172
173	173
174		-[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
	181	+[[image:1664501784668-703.png]]
175	175
176	176
177	177
178		-(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
179	179
180		-(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
	186	+(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
181	181
182		-[[image:1664502835802-546.png]]
183	183
184		-
185	185	(% 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.
186	186
187	187
	192	+
188	188	== 2.3  Positioning Mode(SMOD) ==
189	189
190	190
191	191	Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
192	192
193		-* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
194		-* (% 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.
195		-* (% 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.
	198	+* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
	199	+* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
	200	+* (% 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.
196	196
197	197	Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
198	198
199	199
	205	+
200	200	== 2.4  Uplink Payload ==
201	201
	208	+
202	202	=== 2.4.1 Uplink FPORT~=5, Device Status ===
203	203
204	204
...	...	@@ -207,8 +207,8 @@
207	207	Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
208	208
209	209
210		-(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
211		-|=(% 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
	217	+(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
	218	+|=(% 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
212	212	|=(% 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
213	213
214	214	[[image:1665301570342-765.png]]
...	...	@@ -252,11 +252,12 @@
252	252	Use can also get the Device Status uplink through the downlink command:
253	253
254	254
	262	+
255	255	(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
256	256
257		-(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
258		-|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
259		-|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
	265	+(% border="1.5" style="background-color:#ffffcc; color:green; width:420px" %)
	266	+|(% style="width:75px" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:137px" %)2bit|(% style="width:142px" %)4bit
	267	+|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:137px" %)GPS_Settings|(% style="width:142px" %)BLE_Settings
260	260
261	261	(% style="color:blue" %)** SMOD：**
262	262
...	...	@@ -278,14 +278,13 @@
278	278
279	279	(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
280	280
281		-(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)
282	282
283	283
284	284	(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
285	285
286		-(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
287		-|=(% 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
288		-|=(% 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"]]
	293	+(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %)
	294	+|(% style="width:77px" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:92px" %)1 Bit|(% style="width:48px" %)1 Bit|(% style="width:126px" %)1 Bit
	295	+|(% 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"]]
289	289
290	290
291	291	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
...	...	@@ -294,12 +294,12 @@
294	294	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,
295	295
296	296
297		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
298		-|=(% scope="row" style="width: 60px;" %)(((
	304	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
	305	+|=(% scope="row" style="width: 50px;" %)(((
299	299	**Size(bytes)**
300		-)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
	307	+)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
301	301	2
302		-)))|(% style="width:30px" %)(((
	309	+)))|(% style="width:87px" %)(((
303	303	2
304	304	)))
305	305	|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
...	...	@@ -318,8 +318,8 @@
318	318
319	319	==== (% style="color:blue" %)**FLAG:**(%%) ====
320	320
321		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
322		-|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
	328	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
	329	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
323	323	|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
324	324
325	325	**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
...	...	@@ -330,6 +330,7 @@
330	330	* Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
331	331	* Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
332	332
	340	+
333	333	(% style="color:red" %)**Important note:**
334	334
335	335	1.  When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF.
...	...	@@ -366,9 +366,10 @@
366	366	* < 3.39v:  0~~20%
367	367
368	368
	377	+
369	369	==== (% style="color:blue" %)**MOD:**(%%) ====
370	370
371		-**Example: ** (0x60>>6) & 0x3f =1
	380	+**Example: ** (0x60>>6)& 0x3f =1.
372	372
373	373	**Set the format of GPS data uplink link：**
374	374
...	...	@@ -396,6 +396,7 @@
396	396	)))
397	397
398	398
	408	+
399	399	==== (% style="color:blue" %)**Hum:**(%%) ====
400	400
401	401	0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
...	...	@@ -406,6 +406,7 @@
406	406	011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
407	407
408	408
	419	+
409	409	=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
410	410
411	411
...	...	@@ -412,10 +412,10 @@
412	412	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)
413	413
414	414
415		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
416		-|=(% scope="row" style="width: 60px;" %)(((
	426	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
	427	+|=(% scope="row" style="width: 50px;" %)(((
417	417	**Size(bytes)**
418		-)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
	429	+)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
419	419	|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
420	420	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
421	421	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
...	...	@@ -424,6 +424,7 @@
424	424	[[image:1665301687277-443.png]]
425	425
426	426
	438	+
427	427	=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
428	428
429	429
...	...	@@ -433,12 +433,12 @@
433	433	(% style="color:red" %)**Note for this mode:**
434	434
435	435	* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
436		-* 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.
	448	+* 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.
437	437	* 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
438	438
439	439	The payload is 15 bytes, as below.
440	440
441		-(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
	453	+(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
442	442	|=(% scope="row" %)(((
443	443	**Size(bytes)**
444	444	)))|4|4|2|1|1|1|1|1
...	...	@@ -447,14 +447,10 @@
447	447	[[image:image-20221009160309-2.png]]
448	448
449	449
	462	+
450	450	=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
451	451
452	452
453		-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.
454		-
455		-User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
456		-
457		-
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)**
...	...	@@ -474,43 +474,21 @@
474	474	[[image:1664502425687-834.png]]
475	475
476	476
477		-* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
	485	+* (% 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 MINOR from the strongest iBeacon.
	489	+* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR 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	485
486		-=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
487	487
	495	+=== 2.4.6  Add Payload format in TTN V3 ===
488	488
489		-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.
490	490
	498	+In TTN V3, use can add a custom payload so it shows friendly.
491	491
492		-(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
493		-|=(% scope="row" style="width: 60px;" %)(((
494		-**Size(bytes)**
495		-)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
496		-|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
497		-[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
498		-)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
499		-
500		-(% class="wikigeneratedid" %)
501		-[[image:1667288597595-714.png||height="212" width="1151"]]
502		-
503		-
504		-* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
505		-* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
506		-* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
507		-
508		-
509		-=== 2.4.7  Add Payload format in TTN V3 ===
510		-
511		-
512		-In TTN V3, user can add a custom payload so it shows friendly.
513		-
514	514	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
515	515
516	516
...	...	@@ -517,38 +517,47 @@
517	517	[[image:1664502649601-895.png]]
518	518
519	519
	506	+Add the decoder from this link:
520	520
521		-Add the decoder from this link:
522	522
523		-[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
524		-
525	525	Save the change the uplink message will be parsed. As below:
526	526
527	527	[[image:1664502676891-606.png]]
528	528
529	529
	514	+
530	530	== 2.5 Integrate with Datacake ==
531	531
532	532
	518	+(((
533	533	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.
	520	+)))
534	534
	522	+(((
535	535	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]]
	524	+)))
536	536
537	537
538	538	[[image:1664502695771-538.png]]
539	539
540	540
	530	+
541	541	== 2.6 Integrate with Tago ==
542	542
543	543
544		-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.
	534	+(((
	535	+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.
	536	+)))
545	545
	538	+(((
546	546	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]]
	540	+)))
547	547
548	548
549	549	[[image:1664502715371-321.png]]
550	550
551	551
	546	+
552	552	== 2.7  Datalog Feature ==
553	553
554	554
...	...	@@ -564,6 +564,7 @@
564	564	[[image:image-20221009234629-1.png||height="390" width="577"]]
565	565
566	566
	562	+
567	567	== 2.8 Alarm Mode ==
568	568
569	569
...	...	@@ -573,15 +573,15 @@
573	573
574	574
575	575	(((
576		-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.
	572	+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.
577	577	)))
578	578
579	579
580	580	(((
581		-**Two ways to exit alarm mode:**
	577	+Two ways to exit alarm mode:
582	582	)))
583	583
584		-* Server sends a downlink command to exit.
	580	+* Server send a downlink command to exit.
585	585	* User fast press the RED button 10 times.
586	586
587	587	(((
...	...	@@ -589,6 +589,7 @@
589	589	)))
590	590
591	591
	588	+
592	592	== 2.9 Transport Mode ==
593	593
594	594
...	...	@@ -595,16 +595,17 @@
595	595	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.
596	596
597	597
	595	+
598	598	== 2.10 LED Status ==
599	599
600	600
601		-(% border="1.5" style="background-color:#ffffcc; width:500px" %)
	599	+(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
602	602	|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
603	603	|(% 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
604	604	|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
605	605	|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
606	606	|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
607		-|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
	605	+|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
608	608	|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
609	609	|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
610	610	|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
...	...	@@ -628,9 +628,9 @@
628	628	[[image:1664502854406-763.png]]
629	629
630	630
631		-(% border="1" style="background-color:#ffffcc; width:510px" %)
632		-|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
633		-|(% 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"]]
	629	+(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
	630	+|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
	631	+|(% 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"]]
634	634	|(% 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
635	635	|(% 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.
636	636
...	...	@@ -654,6 +654,7 @@
654	654	LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
655	655
656	656
	655	+
657	657	== 3.1 Access AT Command ==
658	658
659	659
...	...	@@ -669,9 +669,11 @@
669	669	[[image:1664503022490-662.png]]
670	670
671	671
	671	+
672	672	[[image:1664503035713-500.png]]
673	673
674	674
	675	+
675	675	[[image:1664503047675-651.png]]
676	676
677	677
...	...	@@ -678,6 +678,7 @@
678	678
679	679	== 3.2 Command Set ==
680	680
	682	+
681	681	=== 3.2.1 Set Transmit Interval ===
682	682
683	683
...	...	@@ -695,6 +695,7 @@
695	695	(% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
696	696
697	697
	700	+
698	698	=== 3.2.2 Set Alarm Packet transmission interval ===
699	699
700	700
...	...	@@ -712,6 +712,7 @@
712	712	(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
713	713
714	714
	718	+
715	715	=== 3.2.3 Set Transport Mode Packet transmission interval ===
716	716
717	717
...	...	@@ -726,9 +726,10 @@
726	726
727	727	* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
728	728
729		-(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
	733	+(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
730	730
731	731
	736	+
732	732	=== 3.2.4 Exit Alarm ===
733	733
734	734
...	...	@@ -741,6 +741,7 @@
741	741	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
742	742
743	743
	749	+
744	744	=== 3.2.5 Disable/Enable LED flash ===
745	745
746	746
...	...	@@ -758,6 +758,7 @@
758	758	(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
759	759
760	760
	767	+
761	761	=== 3.2.6 Disable/Enable Transport Mode ===
762	762
763	763
...	...	@@ -767,18 +767,19 @@
767	767
768	768	(% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
769	769
770		-Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
	777	+Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
771	771
772	772
773	773	* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
774	774
775		-(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
	782	+(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
776	776
777	777
	785	+
778	778	=== 3.2.7 Set Positioning Mode ===
779	779
780	780
781		-SMOD define how TrackerD scan and uplink data:
	789	+SMOD define the how TrackerD scan and uplink data:
782	782
783	783
784	784	* (% style="color:blue" %)**AT Command:**
...	...	@@ -787,40 +787,32 @@
787	787
788	788	(% style="color:#037691" %)** aa:**
789	789
790		-* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
	798	+* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
	799	+* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
	800	+* (% 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.
791	791
792		-* (% 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.
793		-
794		-* (% 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.
795		-
796	796	(% style="color:#037691" %)**bb:**
797	797
798	798	* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
799		-
800	800	* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
801	801
802	802	(% style="color:#037691" %)**cc:   **
803	803
804		-* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
805		-
806		-* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))
	809	+* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
807	807
808	808	(% style="color:blue" %)**Example:**
809	809
810		- AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
	813	+ AT+ SMOD =1,0 ,0 ~-~->  GPS+ BAT+ State+Tem&Hum
	814	+ AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
	815	+ AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
811	811
812		- AT+SMOD=1,1,0 ~-~->  GPS +BAT State
813	813
814		- AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
815		-
816		- AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
817		-
818		-
819	819	* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
820	820
821		-(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
	820	+(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
822	822
823	823
	823	+
824	824	=== 3.2.8 Set MAX GPS position time ===
825	825
826	826
...	...	@@ -827,7 +827,7 @@
827	827	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.
828	828
829	829
830		-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.
	830	+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.
831	831
832	832
833	833	* (% style="color:blue" %)**AT Command:**
...	...	@@ -842,6 +842,7 @@
842	842	(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
843	843
844	844
	845	+
845	845	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
846	846
847	847
...	...	@@ -866,7 +866,7 @@
866	866
867	867
868	868
869		-**Disable/Enable the confirmation mode**
	870	+Disable/Enable the confirmation mode
870	870
871	871	* (% style="color:blue" %)**AT Command:**
872	872
...	...	@@ -875,16 +875,17 @@
875	875
876	876	**~ Example:**
877	877
878		- AT+CFM=0    **~-~->   ** Disable confirmation
	879	+ AT+ CFM=0    **~-~->   ** Disable confirmation
879	879
880		- AT+CFM=1    **~-~->  ** Enable confirmation
	881	+ AT+ CFM=1    **~-~->  ** Enable confirmation
881	881
882	882
883	883	* (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
884	884
885		-(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
	886	+(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
886	886
887	887
	889	+
888	888	=== 3.2.10  Auto Send None-ACK messages ===
889	889
890	890
...	...	@@ -906,68 +906,6 @@
906	906	Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
907	907
908	908
909		-=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
910		-
911		-
912		-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.
913		-
914		-(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
915		-
916		-(% style="color:blue" %)**AT Command:**
917		-
918		- (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
919		-
920		- (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
921		-
922		-(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
923		-
924		-Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
925		-
926		-
927		-=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
928		-
929		-
930		-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.
931		-
932		-(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
933		-
934		-(% style="color:blue" %)**AT Command:**
935		-
936		- (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
937		-
938		- (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
939		-
940		-(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
941		-
942		-Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
943		-
944		-
945		-=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
946		-
947		-
948		-Users can use this feature to enable/disable Information printing.
949		-
950		-(% style="color:blue" %)**AT Command:**
951		-
952		-(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
953		-\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
954		-
955		-
956		-=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
957		-
958		-
959		-The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
960		-
961		-(% style="color:blue" %)**AT Command:**
962		-
963		-(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
964		-
965		-
966		-(% style="color:blue" %)**Downlink Payload:0X24**
967		-
968		-Example: 0x24 01 ~/~/ Same as AT+CHE=1
969		-
970		-
971	971	= 4. Setting for Different Scenarios =
972	972
973	973
...	...	@@ -974,6 +974,7 @@
974	974
975	975	= 5. Upload Firmware =
976	976
	917	+
977	977	== 5.1 Firmware Change Log ==
978	978
979	979
...	...	@@ -980,6 +980,7 @@
980	980	**[[See this link>>url:https://github.com/dragino/TrackerD]]**
981	981
982	982
	924	+
983	983	== 5.2 How to upgrade firmware ==
984	984
985	985
...	...	@@ -1006,33 +1006,34 @@
1006	1006	[[image:1664503574618-659.png]]
1007	1007
1008	1008
1009		-
1010	1010	(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
1011	1011
1012	1012	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1013	1013
1014	1014
1015		-**Users need to use below files:**
	956	+Users need to use below files:
1016	1016
1017	1017	boot_app0.bin @0e000
1018	1018
1019		-US915.bin @ 0x10000(Select the bin file of the frequency band you need)
	960	+ESP_LORA-eeprom-class.bin @ 0x10000
1020	1020
1021	1021
1022		-[[image:image-20221118105220-2.png]]
	963	+[[image:1664503593459-435.png]]
1023	1023
1024	1024
1025	1025
1026	1026	After upgrade finish, it will show finish as below:
1027	1027
1028		-[[image:image-20221118105402-4.png]]
	969	+[[image:1664503611848-385.png]]
1029	1029
1030	1030
1031	1031
1032	1032	= 6. Developer Guide =
1033	1033
	975	+
1034	1034	== 6.1 Compile Source Code ==
1035	1035
	978	+
1036	1036	=== 6.1.1 Set up ARDUINO compile environment ===
1037	1037
1038	1038
...	...	@@ -1050,18 +1050,7 @@
1050	1050	[[image:1664503715811-892.png]]
1051	1051
1052	1052
1053		-(% 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.
1054	1054
1055		-[[image:image-20221024105643-1.png]]
1056		-
1057		-**~ Figure1**
1058		-
1059		-
1060		-[[image:image-20221024105643-2.png]]
1061		-
1062		- **Figure2**
1063		-
1064		-
1065	1065	* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1066	1066
1067	1067	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
...	...	@@ -1070,6 +1070,7 @@
1070	1070	[[image:1664503752288-974.png]]
1071	1071
1072	1072
	1005	+
1073	1073	== 6.2 Source Code ==
1074	1074
1075	1075
...	...	@@ -1090,8 +1090,10 @@
1090	1090	[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1091	1091
1092	1092
	1026	+
1093	1093	= 7.  FAQ =
1094	1094
	1029	+
1095	1095	== 7.1 How to change the LoRa Frequency Bands/Region? ==
1096	1096
1097	1097
...	...	@@ -1098,6 +1098,7 @@
1098	1098	User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1099	1099
1100	1100
	1036	+
1101	1101	== 7.2 What is the pin mapping for the USB program cable? ==
1102	1102
1103	1103
...	...	@@ -1117,245 +1117,52 @@
1117	1117	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1118	1118
1119	1119
1120		-== 7.3 Notes on using different serial port tools for TrackerD ==
1121	1121
1122		-=== 7.3.1  Serial port utility ===
	1057	+= 8.  Order Info =
1123	1123
1124	1124
1125		-Serial port utility requires you to automatically add data streams.
1126		-
1127		-Need to adjust the data stream to RTS/CTS on physical restart.
1128		-
1129		-(% class="wikigeneratedid" %)
1130		-[[image:image-20221102140621-1.png]]
1131		-
1132		-
1133		-
1134		-When using AT commands, the data flow needs to be adjusted to XON/XOFF
1135		-
1136		-[[image:image-20221102140638-2.png]]
1137		-
1138		-
1139		-=== 7.3.2  SecureCRT ===
1140		-
1141		-
1142		-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.
1143		-
1144		-
1145		-[[image:image-20221102140704-3.png]]
1146		-
1147		-
1148		-[[image:image-20221102140712-4.png]]
1149		-
1150		-
1151		-=== 7.3.3  PUTTY ===
1152		-
1153		-
1154		-[[image:image-20221102140748-5.png]]
1155		-
1156		-
1157		-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.
1158		-
1159		-
1160		-[[image:image-20221102140801-6.png]]
1161		-
1162		-
1163		-== 7.4 How to modify source code to compile different frequency band bin file? ==
1164		-
1165		-
1166		-(% class="box infomessage" %)
1167		-(((
1168		-(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1169		-See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1170		-)))
1171		-
1172		-**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1173		-
1174		-
1175		-[[image:image-20221116111844-1.png||height="227" width="782"]]
1176		-
1177		-
1178		-
1179		-**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1180		-
1181		-
1182		-[[image:image-20221116111844-2.png||height="262" width="781"]]
1183		-
1184		-
1185		-
1186		-**3. Compile the AS923_JP band, please refer to the intention shown**
1187		-
1188		-
1189		-[[image:image-20221116111844-3.png||height="338" width="746"]]
1190		-
1191		-
1192		-
1193		-**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.**
1194		-
1195		-
1196		-[[image:image-20221116111844-4.png||height="641" width="739"]]
1197		-
1198		-
1199		-[[image:image-20221116111844-5.png||height="551" width="708"]]
1200		-
1201		-
1202		-= 8  Trouble Shooting =
1203		-
1204		-== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1205		-
1206		-
1207		-(((
1208		-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
1209		-)))
1210		-
1211		-
1212		-== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1213		-
1214		-
1215		-(((
1216		-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.
1217		-)))
1218		-
1219		-
1220		-== 8.3  Problem after Upgrading Firmware ==
1221		-
1222		-=== 8.3.1 Continue Restart after upgrading ===
1223		-
1224		-
1225		-(((
1226		-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
1227		-)))
1228		-
1229		-
1230		-[[image:image-20221118105249-3.png]]
1231		-
1232		-
1233		-=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1234		-
1235		-
1236		-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
1237		-
1238		-
1239		-=== 8.3.3 "flash read err" after upgrade firmware ===
1240		-
1241		-Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1242		-
1243		-[[image:image-20221122100004-1.png||height="497" width="534"]]
1244		-
1245		-
1246		-User need to upgrade again with below four files to solve this issue.
1247		-
1248		- [[image:image-20221122100004-2.png||height="619" width="389"]]
1249		-
1250		- **Figure 2**
1251		-
1252		-
1253		-=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1254		-
1255		-User might erase the entire flash include keys and default settings which cause this issue.
1256		-
1257		-After the upgrade is completed, enter AT+CFG as shown in the figure below.
1258		-
1259		-[[image:image-20221122100004-3.png]]
1260		-
1261		-Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1262		-
1263		-
1264		-Example:
1265		-
1266		-AT+DEUI=70B3D57ED0053981
1267		-
1268		-AT+APPEUI=D23345667BCBCCAF
1269		-
1270		-AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1271		-
1272		-AT+DADDR=260b4dce    ( no need for OTAA)
1273		-
1274		-AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1275		-
1276		-AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1277		-
1278		-
1279		-
1280		-==== 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 ====
1281		-
1282		-
1283		-[[image:image-20221122100004-4.png]]
1284		-
1285		-
1286		-== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1287		-
1288		-
1289		-Please download version 1.4.2 again
1290		-
1291		-
1292		-== 8.5  How to deal with unsuccessful GPS positioning? ==
1293		-
1294		-
1295		-1） Make Sure the device is in Open Area where can see the sky.
1296		-
1297		-2)  Set PDOP to a higher value.
1298		-
1299		-* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1300		-
1301		-* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1302		-
1303		-* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1304		-
1305		-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
1306		-
1307		-
1308		-= 9.  Order Info =
1309		-
1310		-
1311	1311	Part Number: (% style="color:blue" %)**TrackerD-XXX**
1312	1312
1313	1313	(% style="color:blue" %)**XXX**(%%): The default frequency band
1314	1314
1315	1315	* (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1316		-
1317	1317	* (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1318		-
1319	1319	* (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1320		-
1321	1321	* (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1322		-
1323	1323	* (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1324		-
1325	1325	* (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1326		-
1327	1327	* (% style="color:red" %)**US915**(%%): Default frequency band US915
1328	1328
1329	1329
1330		-= 10.  Packing Info =
1331	1331
	1074	+= 9.  Packing Info =
1332	1332
	1076	+
1333	1333	(% style="color:#037691" %)**Package Includes**:
1334	1334
1335	1335	* TrackerD LoRaWAN GPS/BLE Tracker x 1
1336		-
1337	1337	* USB recharge & program cable x 1
1338	1338
1339	1339	(% style="color:#037691" %)**Dimensions and Weight**:
1340	1340
1341		-* Device Size: 85 x 48 x 15 mm
1342		-
	1084	+* Device Size: 85 x 48 x 15 cm
1343	1343	* Weight: 50g
1344	1344
1345	1345
1346		-= 11. Support =
1347	1347
	1089	+= 10. Support =
1348	1348
1349		-* 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.
1350	1350
	1092	+* 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.
1351	1351	* 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]].
1352	1352
1353	1353
1354		-= 12.  Reference =
1355	1355
	1097	+= 11.  Reference =
1356	1356
1357		-* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1358	1358
	1100	+* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1359	1359	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
1360		-
1361	1361	* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
	1103	+
	1104	+

1667288597595-714.png

Author

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

Size

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

Content

image-20221024105643-1.png

Author

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

Size

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

Content

image-20221024105643-2.png

Author

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

Size

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

Content

image-20221102140621-1.png

Author

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

Size

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

Content

image-20221102140638-2.png

Author

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

Size

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

Content

image-20221102140704-3.png

Author

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

Size

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

Content

image-20221102140712-4.png

Author

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

Size

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

Content

image-20221102140748-5.png

Author

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

Size

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

Content

image-20221102140801-6.png

Author

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

Size

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

Content

image-20221107145243-1.png

Author

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

Size

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

Content

image-20221116111844-1.png

Author

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

Size

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

Content

image-20221116111844-2.png

Author

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

Size

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

Content

image-20221116111844-3.png

Author

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

Size

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

Content

image-20221116111844-4.png

Author

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

Size

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

Content

image-20221116111844-5.png

Author

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

Size

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

Content

image-20221118104359-1.png

Author

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

Size

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

Content

image-20221118105220-2.png

Author

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

Size

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

Content

image-20221118105249-3.png

Author

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

Size

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

Content

image-20221118105402-4.png

Author

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

Size

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

Content

image-20221122100004-1.png

Author

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

Size

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

Content

image-20221122100004-2.png

Author

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

Size

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

Content

image-20221122100004-3.png

Author

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

Size

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

Content

image-20221122100004-4.png

Author

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

Size

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

Content