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

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 33 removed)
  • image-20221128102938-1.png
  • image-20221128103040-2.png
  • image-20221128110503-3.png
  • image-20221128111443-4.png
  • image-20221128111850-5.png
  • image-20221128111951-6.png
  • image-20221128112035-7.png
  • image-20221207120501-1.png
  • image-20221207120524-2.png
  • image-20221207120530-3.png
  • image-20221207120536-4.png
  • image-20221207120601-5.png
  • image-20221207133836-6.png
  • image-20221207133911-7.png
  • image-20221207134028-8.png
  • image-20221213100007-1.png
  • image-20221213100626-2.png
  • image-20221213100808-3.png
  • image-20221213101040-4.png
  • image-20221213102311-5.png
  • image-20221213102334-6.png
  • image-20221213102718-7.png
  • image-20221213110952-8.png
  • image-20230213110119-1.png
  • image-20230213110214-2.png
  • image-20230213110506-3.png
  • image-20230302145315-1.png
  • image-20230307135914-1.png
  • image-20230307135932-2.png
  • image-20230308115430-1.png
  • image-20230308115616-2.png
  • image-20230308115701-3.png
  • image-20230426085815-1.png

Details

Page properties

Content

...	...	@@ -1,5 +1,5 @@
1	1	(% style="text-align:center" %)
2		-[[image:1664505654417-133.png||_mstalt="293696"]]
	2	+[[image:1664505654417-133.png]]
3	3
4	4
5	5
...	...	@@ -12,7 +12,6 @@
12	12
13	13
14	14
15		-
16	16	= 1.  Introduction =
17	17
18	18	== 1.1  What is TrackerD ==
...	...	@@ -32,12 +32,15 @@
32	32	(((
33	33	The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
34	34	)))
	34	+)))
35	35
36	36	(((
37	37	TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
	38	+
	39	+
38	38	)))
39	39
40		-[[image:image-20230213110119-1.png||height="382" width="834"]]
	42	+[[image:1664499921684-770.png]]
41	41
42	42
43	43	(% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
...	...	@@ -93,8 +93,8 @@
93	93	* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94	94	* Tracking: max: 38mA
95	95
96		-(% style="display:none" %)
97	97
	99	+
98	98	== 1.3  Features ==
99	99
100	100
...	...	@@ -113,7 +113,6 @@
113	113	* Tri-color LED, Alarm button
114	114	* Datalog
115	115
116		-(% style="display:none" %)
117	117
118	118
119	119	== 1.4  Applications ==
...	...	@@ -122,7 +122,6 @@
122	122	* Logistics and Supply Chain Management
123	123	* Human tracking
124	124
125		-(% style="display:none" %)
126	126
127	127
128	128	= 2.  Use TrackerD =
...	...	@@ -139,7 +139,7 @@
139	139	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.
140	140
141	141
142		-[[image:image-20230213110214-2.png||height="388" width="847"]]
	142	+[[image:1664501652064-326.png]]
143	143
144	144
145	145
...	...	@@ -151,7 +151,7 @@
151	151	Each TrackerD is shipped with a sticker with the default device EUI as below:
152	152
153	153
154		-[[image:image-20230426085815-1.png||height="259" width="558"]]
	154	+[[image:1664501677253-891.png]]
155	155
156	156
157	157	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
...	...	@@ -160,14 +160,14 @@
160	160	**__Add APP EUI in the application:__**
161	161
162	162
163		-[[image:1664501711466-918.png||_mstalt="295828"]]
	163	+[[image:1664501711466-918.png]]
164	164
165	165
166	166
167		-[[image:1664501721248-725.png||_mstalt="294450"]]
	167	+[[image:1664501721248-725.png]]
168	168
169	169
170		-[[image:1664501734705-405.png||_mstalt="293306"]]
	170	+[[image:1664501734705-405.png]]
171	171
172	172
173	173
...	...	@@ -174,15 +174,15 @@
174	174	**__Add APP KEY and DEV EUI:__**
175	175
176	176
177		-[[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"]]
	177	+[[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"]]
178	178
179	179
180	180
181	181	(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
182	182
183		-(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
	183	+(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
184	184
185		-[[image:1664502835802-546.png||_mstalt="295061"]]
	185	+[[image:1664502835802-546.png]]
186	186
187	187
188	188	(% 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.
...	...	@@ -205,16 +205,16 @@
205	205	=== 2.4.1 Uplink FPORT~=5, Device Status ===
206	206
207	207
208		-Uplink the device configures with (% style="color:blue" %)**FPORT=5**(%%). Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.
	208	+Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.
209	209
210		-Use can also get the Device Status uplink through the downlink command: (% style="color:#037691" %)**Downlink:  0x2301**
	210	+Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
211	211
212	212
213		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:440px" %)
214		-|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**Size(bytes)**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 30px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1
215		-|(% 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	+(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
	214	+|=(% 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
	215	+|=(% 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
216	216
217		-[[image:1665301570342-765.png||_mstalt="294580"]]
	217	+[[image:1665301570342-765.png]]
218	218
219	219
220	220	(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
...	...	@@ -257,9 +257,9 @@
257	257
258	258	(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
259	259
260		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:270px" %)
261		-|(% style="width:60px" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)2 bits|(% style="width:80px" %)4 bits
262		-|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
	260	+(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
	261	+|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
	262	+|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
263	263
264	264	(% style="color:blue" %)** SMOD：**
265	265
...	...	@@ -281,26 +281,25 @@
281	281
282	282	(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
283	283
284		-(% _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)(%%)
	284	+(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)
285	285
286	286
287	287	(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
288	288
289		-(% border="1" style="background-color:#f2f2f2; width:413px" %)
290		-|(% style="width:77px" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:88px" %)1 Bit|(% style="width:50px" %)1 Bit|(% style="width:128px" %)1 Bit
291		-|(% style="width:75px" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
	289	+(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
	290	+|=(% 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
	291	+|=(% 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"]]
292	292
293		-(% style="display:none" %)
294	294
295	295
296	296	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
297	297
298	298
299		-Users can use (% style="color:blue" %)**AT+SMOD=1,0,0**(%%) to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
	298	+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,
300	300
301	301
302		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:320px" %)
303		-|(% style="width:60px" %)(((
	301	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
	302	+|=(% scope="row" style="width: 60px;" %)(((
304	304	**Size(bytes)**
305	305	)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
306	306	2
...	...	@@ -307,27 +307,26 @@
307	307	)))|(% style="width:30px" %)(((
308	308	2
309	309	)))
310		-|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
	309	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
311	311	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
312	312	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
313	313
314		-[[image:1665301636888-168.png||_mstalt="298012"]]
	313	+[[image:1665301636888-168.png]]
315	315
316	316
317	317	==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
318	318
319		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:321px" %)
320		-|(% style="width:60px" %)**Size(bit)**|(% style="width:60px" %)1 bit|(% style="width:134px" %)1 bit|(% style="width:67px" %)14 bits
321		-|(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:114px" %)Alarm Indicate|(% style="width:62px" %)[[BAT>>||anchor="HBAT:"]]
	318	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
	319	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
	320	+|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]
322	322
323		-(% style="display:none" %)
324	324
325	325
326	326	==== (% style="color:blue" %)**FLAG:**(%%) ====
327	327
328		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:184px" %)
329		-|(% style="width:68px" %)**Size(bit)**|(% style="width:61px" %)2 bits|(% style="width:55px" %)1 bit
330		-|(% style="width:79px" %)**Value**|(% style="width:56px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:50px" %)[[LON>>||anchor="HLON:"]]
	326	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
	327	+|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
	328	+|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
331	331
332	332	**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
333	333
...	...	@@ -344,12 +344,12 @@
344	344	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:
345	345
346	346
347		-[[image:1664502116362-706.png||_mstalt="293306"]]
	345	+[[image:1664502116362-706.png]]
348	348
349	349
350	350	3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
351	351
352		-[[image:1664502166010-515.png||_mstalt="291395"]]
	350	+[[image:1664502166010-515.png]]
353	353
354	354
355	355
...	...	@@ -372,7 +372,6 @@
372	372	* 3.40v ~~ 3.69v:  20% ~~ 40%
373	373	* < 3.39v:  0~~20%
374	374
375		-(% style="display:none" %) (%%)
376	376
377	377
378	378	==== (% style="color:blue" %)**MOD:**(%%) ====
...	...	@@ -418,25 +418,25 @@
418	418	=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
419	419
420	420
421		-The default uplink payload includes total 11 bytes ((% style="color:blue" %)**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)
	418	+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)
422	422
423	423
424		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:300px" %)
425		-|(% style="width:60px" %)(((
	421	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
	422	+|=(% scope="row" style="width: 60px;" %)(((
426	426	**Size(bytes)**
427		-)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:70px" %)2|(% style="width:50px" %)1
428		-|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
	424	+)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
	425	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
429	429	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
430	430	)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
431	431
432	432	(% class="wikigeneratedid" %)
433		-[[image:1665301687277-443.png||_mstalt="296140"]]
	430	+[[image:1665301687277-443.png]]
434	434
435	435
436	436	=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
437	437
438	438
439		-Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
	436	+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.
440	440
441	441
442	442	(% style="color:red" %)**Note for this mode:**
...	...	@@ -447,13 +447,13 @@
447	447
448	448	The payload is 15 bytes, as below.
449	449
450		-(% border="1" style="background-color:#f2f2f2; width:500px" %)
451		-|(((
	447	+(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
	448	+|=(% scope="row" %)(((
452	452	**Size(bytes)**
453	453	)))|4|4|2|1|1|1|1|1
454		-|**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
	451	+|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
455	455
456		-[[image:image-20221009160309-2.png||_mstalt="429312"]]
	453	+[[image:image-20221009160309-2.png]]
457	457
458	458
459	459	=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
...	...	@@ -464,11 +464,11 @@
464	464	User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
465	465
466	466
467		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
468		-|(% style="width:60px" %)(((
	464	+(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
	465	+|=(% scope="row" style="width: 60px;" %)(((
469	469	**Size(bytes)**
470	470	)))|(% style="width:30px" %)16|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:120px" %)2|(% style="width:50px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1
471		-|(% style="width:50px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
	468	+|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)(((
472	472	iBeacon MAJOR
473	473	)))|(% style="width:63px" %)(((
474	474	iBeacon MINOR
...	...	@@ -480,7 +480,7 @@
480	480	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
481	481	)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
482	482
483		-[[image:1664502425687-834.png||_mstalt="296738"]]
	480	+[[image:1664502425687-834.png]]
484	484
485	485
486	486	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
...	...	@@ -491,45 +491,24 @@
491	491	* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
492	492	* (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
493	493
494		-(% style="display:none" %) (%%)
495	495
496	496
497		-=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
	493	+=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
498	498
499	499
500		-The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
501		-
502		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:284.818px" %)
503		-|(% style="width:97px" %)**Size(bytes)**|(% style="width:103px" %)2|(% style="width:81px" %)1
504		-|(% style="width:97px" %)**Value**|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon
505		-
506		- [[image:image-20230302145315-1.png]]
507		-
508		-**alarm**=(bytes[0] & 0x40)  ~/~/ Alarm status
509		-
510		-**batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
511		-
512		-**mod** = bytes[2] & 0xC0;
513		-
514		-**Lon**=(bytes[2] & 0x20)
515		-
516		-
517		-=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
518		-
519		-
520	520	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.
521	521
522	522
523		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %)
524		-|(% style="width:65px" %)(((
	499	+(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
	500	+|=(% scope="row" style="width: 60px;" %)(((
525	525	**Size(bytes)**
526		-)))|(% style="width:50px" %)6|(% style="width:50px" %)4|(% style="width:133px" %)2|(% style="width:50px" %)1
527		-|(% style="width:69px" %)**Value**|(% style="width:48px" %)SSID|(% style="width:48px" %)RSSI|(% style="width:103px" %)(((
	502	+)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
	503	+|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
528	528	[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
529		-)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]
	505	+)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
530	530
531	531	(% class="wikigeneratedid" %)
532		-[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
	508	+[[image:1667288597595-714.png||height="212" width="1151"]]
533	533
534	534
535	535	* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
...	...	@@ -536,10 +536,9 @@
536	536	* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
537	537	* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
538	538
539		-(% style="display:none" %) (%%)
540	540
541	541
542		-=== 2.4.8  Add Payload format in TTN V3 ===
	517	+=== 2.4.7  Add Payload format in TTN V3 ===
543	543
544	544
545	545	In TTN V3, user can add a custom payload so it shows friendly.
...	...	@@ -547,15 +547,17 @@
547	547	In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
548	548
549	549
550		-[[image:1664502649601-895.png||_mstalt="296985"]]
	525	+[[image:1664502649601-895.png]]
551	551
552	552
553	553
554		-Add the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
	529	+Add the decoder from this link:
555	555
	531	+[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
	532	+
556	556	Save the change the uplink message will be parsed. As below:
557	557
558		-[[image:1664502676891-606.png||_mstalt="296673"]]
	535	+[[image:1664502676891-606.png]]
559	559
560	560
561	561	== 2.5 Integrate with Datacake ==
...	...	@@ -566,7 +566,7 @@
566	566	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]]
567	567
568	568
569		-[[image:1664502695771-538.png||_mstalt="297349"]]
	546	+[[image:1664502695771-538.png]]
570	570
571	571
572	572	== 2.6 Integrate with Tago ==
...	...	@@ -577,70 +577,29 @@
577	577	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]]
578	578
579	579
580		-[[image:1664502715371-321.png||_mstalt="292162"]]
	557	+[[image:1664502715371-321.png]]
581	581
582	582
583		-== 2.7  Integrate with Node-red ==
	560	+== 2.7  Datalog Feature ==
584	584
585	585
586		-~1. Install node-red, please refer to the installation method in the link:
587		-
588		-[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
589		-
590		-
591		-2. Import the created flow template, please refer to the import method in the link:
592		-
593		-[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
594		-
595		-
596		-The address of the flow template: [[dragino-end-node-decoder/TrackerD.json at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/TrackerD.json]]
597		-
598		-(% style="color:red" %)**Note: If you are using NODE-RED for the first time, please search and install the two plug-ins in the figure below in node-red to fully use the flow template.**
599		-
600		-[[image:image-20230307135914-1.png||height="527" width="1045"]]
601		-
602		-
603		-[[image:image-20230307135932-2.png||height="527" width="1044"]]
604		-
605		-
606		-3. Display the map
607		- Enter the link to the map:
608		-
609		- Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
610		-
611		-**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
612		-
613		-
614		- Hit all input in input stream
615		-
616		- [[image:image-20230308115616-2.png||height="563" width="1070"]]
617		-
618		-
619		- View map again
620		-
621		-[[image:image-20230308115701-3.png||height="571" width="1085"]]
622		-
623		-
624		-== 2.8  Datalog Feature ==
625		-
626		-
627	627	total 273 entries,by default,
628	628
629		-User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
	565	+User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
630	630
631	631	Example use case.
632	632
633		-[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
	569	+[[image:image-20221009234703-2.png||height="328" width="899"]]
634	634
635	635
636		-[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
	572	+[[image:image-20221009234629-1.png||height="390" width="577"]]
637	637
638	638
639		-== 2.9  Alarm Mode ==
	575	+== 2.8 Alarm Mode ==
640	640
641	641
642	642	(((
643		-User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. Alarm Mode is used to send SOS info to IoT platform.
	579	+User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
644	644	)))
645	645
646	646
...	...	@@ -661,24 +661,17 @@
661	661	)))
662	662
663	663
664		-== 2.10  Transport Mode ==
	600	+== 2.9 Transport Mode ==
665	665
666	666
667		-In Transport Mode, TrackerD will check if there is motion (threldhold defined by **[[PT)>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** . If there is no motion, device will send uplinks every 20 minutes (Defined by **[[TDC)>>||anchor="H3.2.1SetTransmitInterval"]]** . If there is motion, device will send uplink every 5 minutes(defined by **[[MTDC)>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]**.
	603	+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.
668	668
669		-When device is set in Transport Mode, it will uplink more frequenctly during moving.
670	670
671		-* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
672		-* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
673		-* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
	606	+== 2.10 LED Status ==
674	674
675		-(% style="display:none" %) (%%)
676	676
677		-== 2.11  LED Status ==
678		-
679		-
680		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:500px" %)
681		-|=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**Event**|=(% style="width: 200px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**AT+LON to control on/off**
	609	+(% border="1.5" style="background-color:#ffffcc; width:500px" %)
	610	+|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
682	682	|(% 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
683	683	|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
684	684	|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
...	...	@@ -691,14 +691,14 @@
691	691	|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
692	692	|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
693	693
694		-(% style="display:none" %) (%%)
695	695
696		-== 2.12  Button Function ==
697	697
	625	+== 2.11 Button Function ==
698	698
	627	+
699	699	(% style="color:blue" %)**RESET button:**
700	700
701		-[[image:1664502835802-546.png||_mstalt="295061"]]
	630	+[[image:1664502835802-546.png]]
702	702
703	703	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
704	704
...	...	@@ -705,21 +705,20 @@
705	705
706	706	(% style="color:red" %)**RED button:**
707	707
708		-[[image:image-20230213110506-3.png]](% style="display:none" %)
	637	+[[image:1664502854406-763.png]]
709	709
710		-(% style="display:none" %) (%%)
711	711
712		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
713		-|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Description**
	640	+(% border="1" style="background-color:#ffffcc; width:510px" %)
	641	+|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
714	714	|(% 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"]]
715	715	|(% 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
716	716	|(% 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.
717	717
718		-(% style="display:none" %) (%%)
719	719
720		-== 2.13  USB Port Function ==
721	721
	648	+== 2.12 USB Port Function ==
722	722
	650	+
723	723	The USB interface of TrackerD has below functions:
724	724
725	725	* Power on the device
...	...	@@ -727,18 +727,8 @@
727	727	* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
728	728	* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
729	729
730		-(% style="display:none" %) (%%)
731	731
732		-== 2.14  Sleep Mode ==
733	733
734		-
735		-(% style="color:blue" %)**Sleep Mode:**(%%) To prevent accidental touch of the red button during transportation or assembly, so the peripherals of the device are turned off and enter deep sleep.
736		-
737		-In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
738		-
739		-Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
740		-
741		-
742	742	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
743	743
744	744
...	...	@@ -753,22 +753,22 @@
753	753	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.
754	754
755	755
756		-[[image:1664502999401-486.png||_mstalt="296985"]]
	674	+[[image:1664502999401-486.png]]
757	757
758	758
759	759	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:
760	760
761	761
762		-[[image:1664503022490-662.png||_mstalt="293332"]]
	680	+[[image:1664503022490-662.png]]
763	763
764	764
765		-[[image:1664503035713-500.png||_mstalt="291096"]]
	683	+[[image:1664503035713-500.png]]
766	766
767	767
768		-[[image:1664503047675-651.png||_mstalt="295386"]]
	686	+[[image:1664503047675-651.png]]
769	769
770		-(% style="display:none" %) (%%)
771	771
	689	+
772	772	== 3.2 Command Set ==
773	773
774	774	=== 3.2.1 Set Transmit Interval ===
...	...	@@ -834,7 +834,7 @@
834	834	(% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
835	835
836	836
837		-=== 3.2.5 Disable/Enable LED flash and buzzer ===
	755	+=== 3.2.5 Disable/Enable LED flash ===
838	838
839	839
840	840	Disable/Enable LED for position, downlink and uplink
...	...	@@ -894,9 +894,9 @@
894	894
895	895	(% style="color:#037691" %)**cc:   **
896	896
897		-* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
	815	+* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
898	898
899		-* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))
	817	+* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))
900	900
901	901	(% style="color:blue" %)**Example:**
902	902
...	...	@@ -958,8 +958,8 @@
958	958	(% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
959	959
960	960
961		-=== 3.2.10 Disable/Enable the confirmation mode ===
962	962
	880	+**Disable/Enable the confirmation mode**
963	963
964	964	* (% style="color:blue" %)**AT Command:**
965	965
...	...	@@ -978,7 +978,7 @@
978	978	(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
979	979
980	980
981		-=== 3.2.11  Auto Send None-ACK messages ===
	899	+=== 3.2.10  Auto Send None-ACK messages ===
982	982
983	983
984	984	TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
...	...	@@ -996,10 +996,10 @@
996	996
997	997	* (% style="color:blue" %)**Downlink Command: 0x34**
998	998
999		-Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
	917	+Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
1000	1000
1001	1001
1002		-=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
	920	+=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
1003	1003
1004	1004
1005	1005	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.
...	...	@@ -1008,16 +1008,16 @@
1008	1008
1009	1009	(% style="color:blue" %)**AT Command:**
1010	1010
1011		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
	929	+ (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
1012	1012
1013		- (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
	931	+ (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
1014	1014
1015	1015	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
1016	1016
1017		-Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
	935	+Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
1018	1018
1019	1019
1020		-=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
	938	+=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
1021	1021
1022	1022
1023	1023	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.
...	...	@@ -1026,16 +1026,16 @@
1026	1026
1027	1027	(% style="color:blue" %)**AT Command:**
1028	1028
1029		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
	947	+ (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1030	1030
1031		- (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
	949	+ (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1032	1032
1033	1033	(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
1034	1034
1035		-Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
	953	+Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
1036	1036
1037	1037
1038		-=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
	956	+=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
1039	1039
1040	1040
1041	1041	Users can use this feature to enable/disable Information printing.
...	...	@@ -1042,11 +1042,11 @@
1042	1042
1043	1043	(% style="color:blue" %)**AT Command:**
1044	1044
1045		-(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
	963	+(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
1046	1046	\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1047	1047
1048	1048
1049		-=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
	967	+=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1050	1050
1051	1051
1052	1052	The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
...	...	@@ -1053,93 +1053,14 @@
1053	1053
1054	1054	(% style="color:blue" %)**AT Command:**
1055	1055
1056		-(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
	974	+(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1057	1057
1058	1058
1059	1059	(% style="color:blue" %)**Downlink Payload:0X24**
1060	1060
1061		-Example: 0x24 01  ~/~/ Same as AT+CHE=1
	979	+Example: 0x24 01 ~/~/ Same as AT+CHE=1
1062	1062
1063	1063
1064		-=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1065		-
1066		-
1067		-User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1068		-
1069		-(% style="color:blue" %)**AT Command:**
1070		-
1071		-(% style="color:#037691" %)**AT+PT=xx**
1072		-
1073		- Example:
1074		-
1075		- AT+PT=14    ~-~->    Set to detect car motion.
1076		-
1077		- AT+PT=41  ~-~->    set to detect walk motion.
1078		-
1079		-
1080		-(% style="color:blue" %)**Downlink Payload:0xB4**
1081		-
1082		-0xB4 14          ~/~/  Same as AT+PT=14
1083		-
1084		-
1085		-=== 3.2.17  Set AT command window time（Since firmware 1.4.5） ===
1086		-
1087		-
1088		-AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
1089		-
1090		-(% style="color:blue" %)**AT Command:**
1091		-
1092		-(% style="color:#037691" %)**AT+ATST=XX**
1093		-
1094		- Example:
1095		-
1096		- AT+ATST=15    ~-~-> Set the time to 15 seconds
1097		-
1098		-(% style="color:blue" %)**Downlink Payload:0XB5**
1099		-
1100		-0xB5 0F          ~/~/  Same as AT+ATST=15
1101		-
1102		-
1103		-=== 3.2.18  Set the stepmeter mode（Since firmware 1.4.5） ===
1104		-
1105		-
1106		-After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
1107		-
1108		-(% style="color:blue" %)**AT Command:**
1109		-
1110		-(% style="color:#037691" %)**AT+PM=xx**
1111		-
1112		- Example:
1113		-
1114		- AT+PM=1    ~-~->  Turn on step counting mode
1115		-
1116		-AT+PM=0    ~-~->  Turn OFF step counting mode
1117		-
1118		-(% style="color:blue" %)**Downlink Payload:0XB6**
1119		-
1120		-0xB6 01          ~/~/  Same as AT+PM=1
1121		-
1122		-
1123		-=== 3.2.19  Set down the decline detection mode（Since firmware 1.4.5） ===
1124		-
1125		-
1126		-This mode is used in conjunction with AT+PT(The recommended threshold is between 50 and 70, you need to set it according to the environment yourself). This function is used in hospitals, nursing homes, nursing homes and other places to prevent the elderly and patients from falling. No one knows.
1127		-
1128		-(% style="color:blue" %)**AT Command:**
1129		-
1130		-(% style="color:#037691" %)**AT+FD=xx**
1131		-
1132		- Example:
1133		-
1134		- AT+FD=1    ~-~->  Turn on the Fall detection
1135		-
1136		-AT+FD=0    ~-~->  Turn OFF the Fall detection
1137		-
1138		-(% style="color:blue" %)**Downlink Payload:0XB7**
1139		-
1140		-0xB7 01          ~/~/  Same as AT+FD=1
1141		-
1142		-
1143	1143	= 4. Setting for Different Scenarios =
1144	1144
1145	1145
...	...	@@ -1172,10 +1172,10 @@
1172	1172	(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1173	1173
1174	1174
1175		-[[image:1664503563660-578.png||_mstalt="296777"]]
	1014	+[[image:1664503563660-578.png]]
1176	1176
1177	1177
1178		-[[image:1664503574618-659.png||_mstalt="297986"]]
	1017	+[[image:1664503574618-659.png]]
1179	1179
1180	1180
1181	1181
...	...	@@ -1191,15 +1191,16 @@
1191	1191	US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1192	1192
1193	1193
1194		-[[image:image-20221207120501-1.png]]
	1033	+[[image:image-20221118105220-2.png]]
1195	1195
1196	1196
1197	1197
1198	1198	After upgrade finish, it will show finish as below:
1199	1199
1200		-[[image:image-20221207133911-7.png]]
	1039	+[[image:image-20221118105402-4.png]]
1201	1201
1202	1202
	1042	+
1203	1203	= 6. Developer Guide =
1204	1204
1205	1205	== 6.1 Compile Source Code ==
...	...	@@ -1212,81 +1212,24 @@
1212	1212	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]]
1213	1213
1214	1214
1215		-[[image:1664503635019-941.png||_mstalt="294658"]]
	1055	+[[image:1664503635019-941.png]]
1216	1216
1217	1217
1218	1218
1219	1219	* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1220	1220
1221		-[[image:1664503715811-892.png||_mstalt="295698"]]
	1061	+[[image:1664503715811-892.png]]
1222	1222
1223	1223
1224		-=== 6.1.2  Build the development environment ===
1225		-
1226		-
1227		-**~1. Download and install arduino IDE**
1228		-
1229		-[[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]]
1230		-
1231		-
1232		-**2. Download the ESP32 development package in the arduino IDE**
1233		-
1234		-[[image:image-20221213100007-1.png]]
1235		-
1236		-
1237		-Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1238		-
1239		-[[image:image-20221213100626-2.png]]
1240		-
1241		-
1242		-Restart the IDE after the addition is complete, then:
1243		-
1244		-[[image:image-20221213100808-3.png||height="679" width="649"]]
1245		-
1246		-
1247		-[[image:image-20221213101040-4.png]]
1248		-
1249		-
1250		-(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1251		-Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)**
1252		-
1253		-
1254		-Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import:
1255		-
1256		-(% style="color:blue" %)**Methods as below:**
1257		-
1258		-~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1259		-
1260		-2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1261		-
1262	1262	(% 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.
1263	1263
1264		-[[image:image-20221213102311-5.png||height="582" width="711"]]
	1066	+[[image:image-20221024105643-1.png]]
1265	1265
1266		-
1267		-**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1268		-
1269		-[[image:image-20221213102334-6.png]]
1270		-
1271		-(% style="color:red" %)**Note: This step requires a python environment**
1272		-
1273		-
1274		-Either way, in the end:
1275		-
1276		-The final effect is to open the arduino and you can see the esp32
1277		-
1278		-[[image:image-20221213110952-8.png||height="866" width="711"]]
1279		-
1280		-
1281		-
1282		-[[image:image-20221024105643-1.png||_mstalt="428129"]]
1283		-
1284	1284	**~ Figure1**
1285	1285
1286	1286
	1071	+[[image:image-20221024105643-2.png]]
1287	1287
1288		-[[image:image-20221024105643-2.png||_mstalt="428493"]]
1289		-
1290	1290	**Figure2**
1291	1291
1292	1292
...	...	@@ -1295,7 +1295,7 @@
1295	1295	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1296	1296
1297	1297
1298		-[[image:1664503752288-974.png||_mstalt="298194"]]
	1081	+[[image:1664503752288-974.png]]
1299	1299
1300	1300
1301	1301	== 6.2 Source Code ==
...	...	@@ -1303,19 +1303,19 @@
1303	1303
1304	1304	* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1305	1305
1306		-[[image:1664503794261-827.png||_mstalt="296387"]]
	1089	+[[image:1664503794261-827.png]]
1307	1307
1308	1308
1309	1309
1310	1310	* (% style="color:blue" %)**Click to upload**
1311	1311
1312		-[[image:1664503808294-336.png||_mstalt="295711"]]
	1095	+[[image:1664503808294-336.png]]
1313	1313
1314	1314
1315	1315
1316	1316	* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1317	1317
1318		-[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
	1101	+[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1319	1319
1320	1320
1321	1321	= 7.  FAQ =
...	...	@@ -1329,12 +1329,12 @@
1329	1329	== 7.2 What is the pin mapping for the USB program cable? ==
1330	1330
1331	1331
1332		-[[image:1664499635206-262.png||_mstalt="295360"]]
	1115	+[[image:1664499635206-262.png]]
1333	1333
1334	1334
1335	1335
1336		-(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:314px" %)
1337		-|=(% style="width: 120px;background-color:#D9E2F3;color:#0070C0" %)**Pin**|=(% style="width: 69px;background-color:#D9E2F3;color:#0070C0" %)**Color**|=(% style="width: 125px;background-color:#D9E2F3;color:#0070C0" %)**USB Pin**
	1119	+(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
	1120	+|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin**
1338	1338	|(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC
1339	1339	|(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A)
1340	1340	|(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A)
...	...	@@ -1344,7 +1344,6 @@
1344	1344	|(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1345	1345	|(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1346	1346
1347		-(% style="display:none" %) (%%)
1348	1348
1349	1349
1350	1350	== 7.3 Notes on using different serial port tools for TrackerD ==
...	...	@@ -1357,13 +1357,13 @@
1357	1357	Need to adjust the data stream to RTS/CTS on physical restart.
1358	1358
1359	1359	(% class="wikigeneratedid" %)
1360		-[[image:image-20221102140621-1.png||_mstalt="425672"]]
	1142	+[[image:image-20221102140621-1.png]]
1361	1361
1362	1362
1363	1363
1364	1364	When using AT commands, the data flow needs to be adjusted to XON/XOFF
1365	1365
1366		-[[image:image-20221102140638-2.png||_mstalt="428727"]]
	1148	+[[image:image-20221102140638-2.png]]
1367	1367
1368	1368
1369	1369	=== 7.3.2  SecureCRT ===
...	...	@@ -1372,22 +1372,22 @@
1372	1372	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.
1373	1373
1374	1374
1375		-[[image:image-20221102140704-3.png||_mstalt="427076"]]
	1157	+[[image:image-20221102140704-3.png]]
1376	1376
1377	1377
1378		-[[image:image-20221102140712-4.png||_mstalt="427089"]]
	1160	+[[image:image-20221102140712-4.png]]
1379	1379
1380	1380
1381	1381	=== 7.3.3  PUTTY ===
1382	1382
1383	1383
1384		-[[image:image-20221102140748-5.png||_mstalt="430456"]]
	1166	+[[image:image-20221102140748-5.png]]
1385	1385
1386	1386
1387	1387	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.
1388	1388
1389	1389
1390		-[[image:image-20221102140801-6.png||_mstalt="427466"]]
	1172	+[[image:image-20221102140801-6.png]]
1391	1391
1392	1392
1393	1393	== 7.4 How to modify source code to compile different frequency band bin file? ==
...	...	@@ -1402,7 +1402,7 @@
1402	1402	**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1403	1403
1404	1404
1405		-[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
	1187	+[[image:image-20221116111844-1.png||height="227" width="782"]]
1406	1406
1407	1407
1408	1408
...	...	@@ -1409,7 +1409,7 @@
1409	1409	**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1410	1410
1411	1411
1412		-[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
	1194	+[[image:image-20221116111844-2.png||height="262" width="781"]]
1413	1413
1414	1414
1415	1415
...	...	@@ -1416,7 +1416,7 @@
1416	1416	**3. Compile the AS923_JP band, please refer to the intention shown**
1417	1417
1418	1418
1419		-[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
	1201	+[[image:image-20221116111844-3.png||height="338" width="746"]]
1420	1420
1421	1421
1422	1422
...	...	@@ -1423,24 +1423,12 @@
1423	1423	**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.**
1424	1424
1425	1425
1426		-[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
	1208	+[[image:image-20221116111844-4.png||height="641" width="739"]]
1427	1427
1428	1428
1429		-[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
	1211	+[[image:image-20221116111844-5.png||height="551" width="708"]]
1430	1430
1431	1431
1432		-== 7.5 Are there example python example for BLE Indoor Positioning? ==
1433		-
1434		-
1435		-[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1436		-
1437		-
1438		-== 7.6 Can alert mode and transport mode be used together? ==
1439		-
1440		-
1441		-Yes, you can also press the panic button to sound the alarm if set to transport mode
1442		-
1443		-
1444	1444	= 8  Trouble Shooting =
1445	1445
1446	1446	== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
...	...	@@ -1447,7 +1447,7 @@
1447	1447
1448	1448
1449	1449	(((
1450		-Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**AT+INTWK=1**(%%)), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
	1220	+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
1451	1451	)))
1452	1452
1453	1453
...	...	@@ -1461,82 +1461,65 @@
1461	1461
1462	1462	== 8.3  Problem after Upgrading Firmware ==
1463	1463
1464		-=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
	1234	+=== 8.3.1 Continue Restart after upgrading ===
1465	1465
1466	1466
1467		-**Error Output**
1468		-
1469		-
1470		-[[image:image-20221122100004-4.png||_mstalt="424606"]]
1471		-
1472		-
1473	1473	(((
1474		-Some partition is missed during upgrade, please upgrade below four files as example:
1475		-
1476		-[[image:image-20221207120524-2.png]]
	1238	+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
1477	1477	)))
1478	1478
1479	1479
1480		-=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
	1242	+[[image:image-20221118105249-3.png]]
1481	1481
1482	1482
1483		-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
	1245	+=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1484	1484
1485	1485
1486		-=== 8.3.3 "flash read err" after upgrade firmware ===
	1248	+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
1487	1487
1488	1488
1489		-Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1490	1490
	1252	+==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ====
1491	1491
1492		-[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1493	1493
	1255	+[[image:image-20221122100004-1.png||height="497" width="534"]]
1494	1494
1495		-User need to upgrade again with below four files to solve this issue.
	1257	+ ** Figure 1  **
1496	1496
1497		- [[image:image-20221207120530-3.png]]
1498	1498
	1260	+ [[image:image-20221122100004-2.png||height="619" width="389"]]
	1261	+
1499	1499	**Figure 2**
1500	1500
1501	1501
1502		-=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1503	1503
	1266	+After the upgrade is completed, enter AT+CFG as shown in the figure below.
1504	1504
1505		-User might erase the entire flash include keys and default settings which cause this issue.
1506	1506
1507		-After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below.
	1269	+[[image:image-20221122100004-3.png]]
1508	1508
	1271	+Please AT+FDR, and then enter the following instructions by the information on the label
1509	1509
1510		-[[image:image-20221122100004-3.png||_mstalt="424242"]]
	1273	+AT+DEUI=70B3D57ED0053981
1511	1511
	1275	+AT+APPEUI=D23345667BCBCCAF
1512	1512
1513		-Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
	1277	+AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1514	1514
1515		-After AT+FDR. please set
	1279	+AT+DADDR=260b4dce
1516	1516
1517		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
	1281	+AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1518	1518
1519		-* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
	1283	+AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1520	1520
1521		-**Example:**
1522	1522
1523		-AT+PDOP=7.00
1524	1524
1525		-AT+FTIME=180
	1287	+==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ====
1526	1526
1527		-AT+DEUI=70B3D57ED0053981
1528	1528
1529		-AT+APPEUI=D23345667BCBCCAF
	1290	+[[image:image-20221122100004-4.png]]
1530	1530
1531		-AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1532	1532
1533		-AT+DADDR=260b4dce    ( no need for OTAA)
1534		-
1535		-AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1536		-
1537		-AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1538		-
1539		-
1540	1540	== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1541	1541
1542	1542
...	...	@@ -1550,61 +1550,15 @@
1550	1550
1551	1551	2)  Set PDOP to a higher value.
1552	1552
1553		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
	1306	+* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1554	1554
1555		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
	1308	+* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1556	1556
1557		-* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
	1310	+* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1558	1558
1559	1559	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
1560	1560
1561	1561
1562		-== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1563		-
1564		-
1565		-When upgrading, use the erase button to upgrade
1566		-
1567		-[[image:image-20221207120536-4.png]]
1568		-
1569		-
1570		-The parameters are displayed abnormally and cannot be fixed using AT+FDR
1571		-
1572		-[[image:image-20221128103040-2.png||height="431" width="525"]]
1573		-
1574		-
1575		-Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1576		-
1577		-[[image:image-20221207134028-8.png]]
1578		-
1579		-
1580		-Reboot information after upgrade
1581		-
1582		-[[image:image-20221128111443-4.png||height="432" width="546"]]
1583		-
1584		-
1585		-Use (% style="color:blue" %)**AT+FDR**(%%) command to reset and then use (% style="color:blue" %)**AT+CFG**(%%) to check whether the configuration is back to normal
1586		-
1587		-[[image:image-20221128111850-5.png]]
1588		-
1589		-
1590		-After the parameters return to normal, upgrade to the version you need again
1591		-
1592		-[[image:image-20221207120601-5.png]]
1593		-
1594		-
1595		-At this point, the parameters return to normal after running AT+FDR again
1596		-
1597		-[[image:image-20221128112035-7.png]]
1598		-
1599		-
1600		-== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1601		-
1602		-
1603		-~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1604		-
1605		-2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1606		-
1607		-
1608	1608	= 9.  Order Info =
1609	1609
1610	1610
...	...	@@ -1626,8 +1626,8 @@
1626	1626
1627	1627	* (% style="color:red" %)**US915**(%%): Default frequency band US915
1628	1628
1629		-(% style="display:none" %) (%%)
1630	1630
	1337	+
1631	1631	= 10.  Packing Info =
1632	1632
1633	1633
...	...	@@ -1643,8 +1643,8 @@
1643	1643
1644	1644	* Weight: 50g
1645	1645
1646		-(% style="display:none" %) (%%)
1647	1647
	1354	+
1648	1648	= 11. Support =
1649	1649
1650	1650
...	...	@@ -1652,7 +1652,6 @@
1652	1652
1653	1653	* 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]].
1654	1654
1655		-(% style="display:none" %) (%%)
1656	1656
1657	1657
1658	1658	= 12.  Reference =
...	...	@@ -1663,6 +1663,3 @@
1663	1663	* **[[Source Code>>https://github.com/dragino/TrackerD]] **
1664	1664
1665	1665	* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1666		-
1667		-
1668		-)))

image-20221128102938-1.png

Author

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

Size

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

Content

image-20221128103040-2.png

Author

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

Size

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

Content

image-20221128110503-3.png

Author

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

Size

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

Content

image-20221128111443-4.png

Author

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

Size

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

Content

image-20221128111850-5.png

Author

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

Size

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

Content

image-20221128111951-6.png

Author

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

Size

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

Content

image-20221128112035-7.png

Author

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

Size

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

Content

image-20221207120501-1.png

Author

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

Size

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

Content

image-20221207120524-2.png

Author

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

Size

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

Content

image-20221207120530-3.png

Author

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

Size

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

Content

image-20221207120536-4.png

Author

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

Size

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

Content

image-20221207120601-5.png

Author

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

Size

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

Content

image-20221207133836-6.png

Author

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

Size

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

Content

image-20221207133911-7.png

Author

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

Size

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

Content

image-20221207134028-8.png

Author

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

Size

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

Content

image-20221213100007-1.png

Author

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

Size

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

Content

image-20221213100626-2.png

Author

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

Size

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

Content

image-20221213100808-3.png

Author

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

Size

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

Content

image-20221213101040-4.png

Author

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

Size

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

Content

image-20221213102311-5.png

Author

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

Size

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

Content

image-20221213102334-6.png

Author

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

Size

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

Content

image-20221213102718-7.png

Author

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

Size

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

Content

image-20221213110952-8.png

Author

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

Size

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

Content

image-20230213110119-1.png

Author

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

Size

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

Content

image-20230213110214-2.png

Author

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

Size

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

Content

image-20230213110506-3.png

Author

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

Size

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

Content

image-20230302145315-1.png

Author

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

Size

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

Content

image-20230307135914-1.png

Author

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

Size

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

Content

image-20230307135932-2.png

Author

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

Size

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

Content

image-20230308115430-1.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-2.4 MB

Content

image-20230308115616-2.png

Author

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

Size

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

Content

image-20230308115701-3.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-2.4 MB

Content

image-20230426085815-1.png

Author

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

Size

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

Content