Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 191.2 by Xiaoling on 2023/02/13 11:07

version	line-number	content
51.2	1	(% style="text-align:center" %)
146.1	2	[[image:1664505654417-133.png\|\|_mstalt="293696"]]
51.2	3
	4
	5
	6
7.1	7	(% class="wikigeneratedid" %)
	8	Table of Contents:
1.1	9
51.2	10	{{toc/}}
1.1	11
2.1	12
	13
12.1	14
173.2	15
15.2	16	= 1. Introduction =
	17
50.2	18	== 1.1 What is TrackerD ==
15.2	19
50.2	20
15.3	21	(((
	22	TrackerD is an (% style="color:blue" %)Open Source LoRaWAN Tracker(%%) based on (% style="color:blue" %)ESP32 MCU(%%) and (% style="color:blue" %)Semtech LoRa Wireless Chip.
	23	)))
7.2	24
15.3	25	(((
19.2	26	In TrackerD, there are various sensors such as GPS, WiFi, BLE, Temperature, Humidity, Motion Detection, and Buzzer. User can use TrackerD for different tracking scenario.
7.2	27
51.18	28	(((
8.1	29	TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution.
51.18	30	)))
8.1	31
51.18	32	(((
19.2	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.
15.3	34	)))
8.1	35
15.3	36	(((
	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	)))
8.1	39
191.2	40	[[image:image-20230213110119-1.png\|\|height="382" width="834"]]
8.1	41
15.4	42
19.2	43	(% style="color:red" %)Note: LoRaWAN server can be a general LoRaWAN server other than TTN.
8.1	44
15.2	45
19.2	46	== 1.2 Specifications ==
12.1	47
15.2	48
19.2	49	(% style="color:blue" %)Micro Controller:
15.2	50
19.2	51	* Espressif ESP32 PICO D4
	52	* MCU: ESP32 PICO D4
	53	* Bluetooth: Bluetooth V4.2 BR/EDR and Bluetooth LE
	54	* WiFi : 802.11 b/g/n (802.11n up to 150 Mbps)
	55	* Integrated SPI flash : 4 MB
	56	* RAM: 448 KB
	57	* EEPROM: 520 KB
	58	* Clock Speed: 32Mhz
	59
	60	(% style="color:blue" %)Common DC Characteristics:
	61
	62	* Supply Voltage: 5V via USB port or Internal li-on battery
	63	* Operating Temperature: -40 ~~ 60°C
	64
	65	(% style="color:blue" %)LoRa Spec:
	66
	67	* Frequency Range,
	68	** Band 1 (HF): 862 ~~ 1020 Mhz
	69	* 168 dB maximum link budget.
	70	* +20 dBm - 100 mW constant RF output vs.
	71	* +14 dBm high efficiency PA.
	72	* Programmable bit rate up to 300 kbps.
	73	* High sensitivity: down to -148 dBm.
	74	* Bullet-proof front end: IIP3 = -12.5 dBm.
	75	* Excellent blocking immunity.
	76	* Low RX current of 10.3 mA, 200 nA register retention.
	77	* Fully integrated synthesizer with a resolution of 61 Hz.
	78	* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
	79	* Built-in bit synchronizer for clock recovery.
	80	* Preamble detection.
	81	* 127 dB Dynamic Range RSSI.
	82	* Automatic RF Sense and CAD with ultra-fast AFC.
	83	* Packet engine up to 256 bytes with CRC.
	84	* LoRaWAN 1.0.3 Specification
	85
	86	(% style="color:blue" %)Battery:
	87
	88	* 1000mA Li-on Battery power (for model TrackerD)
	89
	90	(% style="color:blue" %)Power Consumption
	91
	92	* Sleeping Mode: 200uA
	93	* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
	94	* Tracking: max: 38mA
	95
186.3	96
188.2	97
19.2	98	== 1.3 Features ==
	99
	100
	101	* LoRaWAN 1.0.3 Class A
	102	* ESP32 PICO D4
	103	* SX1276/78 Wireless Chip
51.31	104	* Arduino IDE Compatible
19.2	105	* Open source hardware / software
	106	* Regular/ Real-time GPS,BLE,WIFI tracking
	107	* Built-in3 axis accelerometer (LIS3DH)
	108	* Humidity / temperature sensor : GXCAS Technology GXHT3X
	109	* Motion sensing capability
	110	* Power Monitoring
	111	* Charging circuit via USB port
	112	* 1000mA Li-on Battery power
	113	* Tri-color LED, Alarm button
	114	* Datalog
	115
186.3	116
188.2	117
19.2	118	== 1.4 Applications ==
	119
	120
12.1	121	* Logistics and Supply Chain Management
	122	* Human tracking
	123
186.3	124
188.2	125
105.2	126	= 2. Use TrackerD =
	127
19.3	128	== 2.1 How it works? ==
19.2	129
19.3	130
19.2	131	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.
	132
	133
19.3	134	== 2.2 Quick guide to connect to LoRaWAN server ==
19.2	135
	136
50.2	137	Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example.
19.2	138
	139
191.2	140	[[image:image-20230213110214-2.png\|\|height="388" width="847"]]
19.2	141
50.2	142
	143
19.2	144	The LPS8N is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. What the rest need to is register this device in TTN V3:
	145
	146
50.2	147	(% style="color:blue" %)Step 1:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
	148
19.2	149	Each TrackerD is shipped with a sticker with the default device EUI as below:
	150
51.3	151
146.1	152	[[image:1664501677253-891.png\|\|_mstalt="296569"]]
19.2	153
	154
	155	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
	156
	157
50.2	158	__Add APP EUI in the application:__
19.2	159
	160
146.1	161	[[image:1664501711466-918.png\|\|_mstalt="295828"]]
19.2	162
	163
	164
146.1	165	[[image:1664501721248-725.png\|\|_mstalt="294450"]]
19.2	166
	167
146.1	168	[[image:1664501734705-405.png\|\|_mstalt="293306"]]
19.2	169
	170
	171
50.2	172	__Add APP KEY and DEV EUI:__
19.2	173
	174
146.1	175	[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1\|\|_mstalt="298233" alt="1654671889112-678.png"]]
19.2	176
	177
	178
125.1	179	(% style="color:blue" %)Step 2:(%%) Push this button will activate this device.
19.2	180
146.1	181	(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png\|\|_mstalt="295061"]]
50.2	182
146.1	183	[[image:1664502835802-546.png\|\|_mstalt="295061"]]
124.1	184
	185
50.2	186	(% 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.
	187
	188
66.3	189	== 2.3 Positioning Mode(SMOD) ==
50.2	190
66.3	191
55.1	192	Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
19.2	193
87.1	194	* (% style="color:#037691" %)GPS ONLY(Factory Settings): (%%)Only get and uplink GPS location info.
	195	* (% 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.
88.1	196	* (% 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.
19.2	197
55.1	198	Users can switch modes by [[changing SMOD>>\|\|anchor="H3.2.7SetPositioningMode"]].
19.2	199
50.2	200
66.3	201	== 2.4 Uplink Payload ==
19.2	202
66.3	203	=== 2.4.1 Uplink FPORT~=5, Device Status ===
66.2	204
66.3	205
74.1	206	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.
19.2	207
76.1	208	Use can also get the Device Status uplink through the downlink command: Downlink: 0x2301
19.2	209
76.1	210
84.8	211	(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
84.9	212	\|=(% 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
66.2	213	\|=(% style="width: 108px;" %)Value\|(% style="width:82px" %)Sensor Model\|(% style="width:83px" %)Firmware Version\|(% style="width:94px" %)Frequency Band\|(% style="width:84px" %)Sub-band\|(% style="width:44px" %)BAT\|(% style="width:63px" %)SMOD\|(% style="width:60px" %)Status
19.2	214
146.1	215	[[image:1665301570342-765.png\|\|_mstalt="294580"]]
66.2	216
	217
74.2	218	(% style="color:#037691" %)Example of Device Status:(%%) 13014001FF0FA24002
19.2	219
74.2	220	(% style="color:#037691" %)Sensor Model: (%%) For TrackerD,this value is 0x13
19.2	221
74.2	222	(% style="color:#037691" %)Firmware Version: (%%) 0x0140,Means:v1.4.0 version
50.2	223
74.2	224	(% style="color:#037691" %)Frequency Band:
55.1	225
	226	*0x01: EU868
	227
	228	*0x02: US915
	229
	230	*0x03: IN865
	231
	232	*0x04: AU915
	233
	234	*0x05: KZ865
	235
	236	*0x06: RU864
	237
	238	*0x07: AS923
	239
	240	*0x08: AS923-1
	241
	242	*0x09: AS923-2
	243
	244	*0x0a: AS923-3
	245
74.2	246	Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
55.1	247
74.2	248	(% style="color:#037691" %)BAT:(%%) shows the battery voltage for TrackerD.
55.1	249
	250
74.2	251	(% style="color:#037691" %)Ex1:(%%) 0x0FA2 = 4002mV
	252
55.1	253	Use can also get the Device Status uplink through the downlink command:
	254
	255
75.1	256	(% style="color:#037691" %)SMOD Field (total 1 byte)(%%)：0x40
74.2	257
84.11	258	(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
84.10	259	\|=(% scope="row" style="width: 60px;" %)Size(bit)\|(% style="width:50px" %)2bits\|(% style="width:80px" %)2bit\|(% style="width:80px" %)4bit
84.9	260	\|=(% style="width: 75px;" %)Value\|(% style="width:64px" %)SMOD\|(% style="width:104px" %)GPS_Settings\|(% style="width:103px" %)BLE_Settings
74.2	261
75.1	262	(% style="color:blue" %) SMOD：
74.2	263
75.1	264	(% style="color:red" %) 1 : (%%) GPS ONLY
74.2	265
75.1	266	(% style="color:red" %) 2 : (%%) BLE ONLY
74.2	267
75.1	268	(% style="color:red" %) 3 : (%%) GPS/BLE Hybrid
74.2	269
	270
75.1	271	(% style="color:blue" %) GPS_MOD: Define how to send GPS payload
74.2	272
75.1	273	(% style="color:red" %) 0 : (%%) Enable uploading on-board Temperature and humidity values
74.2	274
75.1	275	(% style="color:red" %) 1 : (%%) Disable uploading on-board Temperature and humidity values
74.2	276
	277
75.1	278	(% style="color:blue" %) BLE_Settings:
74.2	279
75.1	280	(% style="color:red" %) 1: (%%) BLE Positioning with Strongest iBeacon
74.2	281
146.1	282	(% _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)(%%)
74.2	283
88.1	284
75.1	285	(% style="color:#037691" %)Status Field (total 1 byte)(%%): 0x02
74.2	286
84.11	287	(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
	288	\|=(% 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
84.9	289	\|=(% 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"]]
74.2	290
186.3	291
188.2	292
66.3	293	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
55.1	294
	295
77.1	296	Users can use AT+SMOD=1,0,0 to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
55.1	297
	298
84.13	299	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
	300	\|=(% scope="row" style="width: 60px;" %)(((
84.19	301	Size(bytes)
	302	)))\|(% style="width:50px" %)4\|(% style="width:50px" %)4\|(% style="width:70px" %)2\|(% style="width:30px" %)1\|(% style="width:30px" %)(((
	303	2
	304	)))\|(% style="width:30px" %)(((
	305	2
	306	)))
51.18	307	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
51.5	308	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
59.2	309	)))\|(% style="width:73px" %)[[FLAG>>\|\|anchor="HFLAG:"]]\|(% style="width:40px" %)[[Hum>>\|\|anchor="HHum:"]]\|(% style="width:87px" %)[[Tem>>\|\|anchor="HTem:"]]
19.2	310
146.1	311	[[image:1665301636888-168.png\|\|_mstalt="298012"]]
19.2	312
50.2	313
51.24	314	==== (% style="color:blue" %)Alarm & BAT:(%%) ====
19.2	315
51.24	316	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
	317	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:50px" %)1 bit\|(% style="width:80px" %)1bit\|(% style="width:50px" %)14bits
51.22	318	\|=(% style="width: 72px;" %)Value\|(% style="width:67px" %)reserve\|(% style="width:118px" %)Alarm Indicate\|(% style="width:63px" %)[[BAT>>\|\|anchor="HBAT:"]]
19.2	319
51.24	320	==== (% style="color:blue" %)FLAG:(%%) ====
	321
84.12	322	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
	323	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:30px" %)2bits\|(% style="width:30px" %)1bit
59.3	324	\|=(% style="width: 79px;" %)Value\|(% style="width:55px" %)[[MOD>>\|\|anchor="H3.2.7SetPositioningMode"]]\|(% style="width:47px" %)[[LON>>\|\|anchor="HLON:"]]
19.2	325
51.11	326	Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
19.2	327
	328
51.24	329	==== (% style="color:blue" %)Location info:(%%) ====
19.2	330
51.11	331	* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976//
	332	* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
19.2	333
51.9	334	(% style="color:red" %)Important note:
19.2	335
50.2	336	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.
19.2	337
59.3	338	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:
19.2	339
	340
146.1	341	[[image:1664502116362-706.png\|\|_mstalt="293306"]]
19.2	342
	343
59.3	344	3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
50.2	345
146.1	346	[[image:1664502166010-515.png\|\|_mstalt="291395"]]
50.2	347
	348
	349
51.24	350	==== (% style="color:blue" %)Alarm:(%%) ====
50.2	351
74.9	352	Example: 0x4B & 0x40 >> 6 = 0x01
19.2	353
	354
51.24	355	==== (% style="color:blue" %)BAT:(%%) ====
51.6	356
74.9	357	Example: 0x4B45 & 0x3FFF ⇒ 2885 (mV).
51.6	358
51.27	359	(((
59.3	360	The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
51.27	361	)))
51.6	362
50.4	363	* > 4.0v : 80% ~~ 100%
	364	* 3.85v ~~3.99v: 60% ~~ 80%
	365	* 3.70v ~~ 3.84v: 40% ~~ 60%
	366	* 3.40v ~~ 3.69v: 20% ~~ 40%
	367	* < 3.39v: 0~~20%
19.2	368
191.2	369	(% style="display:none" %) (%%)
188.2	370
	371
74.3	372	==== (% style="color:blue" %)MOD:(%%) ====
	373
79.1	374	Example: (0x60>>6) & 0x3f =1
74.10	375
74.7	376	Set the format of GPS data uplink link：
74.3	377
74.7	378	(% style="color:#037691" %)0x00: (%%) Enable uploading on-board Temperature and humidity values
74.9	379	(% style="color:#037691" %)0x01: (%%) Disable uploading on-board Temperature and humidity values
74.3	380
	381
74.7	382	Set the format of BLE data uplink link：
74.3	383
74.7	384	(% style="color:#037691" %)0x01: (%%) BLE Positioning with Strongest iBeacon
	385
	386
74.10	387	==== (% style="color:blue" %)LON:(%%) ====
74.9	388
74.10	389	Example: (0x60>>5) & 0x01=1.
74.9	390
51.4	391	Enable/Disable LED activity for uplink
19.2	392
51.27	393	(((
74.7	394	(% style="color:#037691" %)0x00: (%%) Disable LED indicator.
51.27	395	)))
19.2	396
51.27	397	(((
74.7	398	(% style="color:#037691" %)0x01: (%%) Enable LED indicator (Default Value)
51.27	399	)))
19.2	400
	401
51.24	402	==== (% style="color:blue" %)Hum:(%%) ====
19.2	403
51.4	404	0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
19.2	405
	406
51.24	407	==== (% style="color:blue" %)Tem:(%%) ====
19.2	408
51.9	409	011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
51.4	410
	411
66.3	412	=== 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
51.4	413
66.2	414
78.1	415	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)
19.2	416
	417
84.14	418	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
84.19	419	\|=(% scope="row" style="width: 60px;" %)(((
	420	Size(bytes)
	421	)))\|(% style="width:60px" %)4\|(% style="width:60px" %)4\|(% style="width:60px" %)2\|(% style="width:50px" %)1
59.2	422	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
	423	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
	424	)))\|(% style="width:73px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
50.2	425
66.2	426	(% class="wikigeneratedid" %)
146.1	427	[[image:1665301687277-443.png\|\|_mstalt="296140"]]
66.2	428
	429
66.3	430	=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning ===
59.2	431
66.2	432
164.2	433	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.
59.2	434
66.2	435
66.3	436	(% style="color:red" %)Note for this mode:
59.2	437
59.3	438	* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
103.1	439	* 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.
78.1	440	* 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
50.2	441
59.3	442	The payload is 15 bytes, as below.
50.2	443
84.15	444	(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
66.2	445	\|=(% scope="row" %)(((
	446	Size(bytes)
	447	)))\|4\|4\|2\|1\|1\|1\|1\|1
66.3	448	\|=Value\|Latitude\|Longitude\|Year\|Month\|Day\|Hous\|Min\|Sen
59.3	449
146.1	450	[[image:image-20221009160309-2.png\|\|_mstalt="429312"]]
59.3	451
66.2	452
66.3	453	=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
59.3	454
84.2	455
81.1	456	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.
59.3	457
82.1	458	User can set [[BLEMASK>>\|\|anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]] so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
79.1	459
81.1	460
51.25	461	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
51.26	462	\|=(% scope="row" style="width: 60px;" %)(((
51.24	463	Size(bytes)
51.26	464	)))\|(% 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
51.24	465	\|=(% style="width: 50px;" %)Value\|(% style="width:44px" %)[[UUID>>\|\|anchor="HLocationinfo:"]]\|(% style="width:61px" %)(((
51.8	466	iBeacon MAJOR
51.11	467	)))\|(% style="width:63px" %)(((
	468	iBeacon MINOR
50.2	469	)))\|(% style="width:71px" %)(((
51.8	470	iBeacon Measured Power
51.11	471	)))\|(% style="width:50px" %)(((
51.8	472	iBeacon RSSI
51.11	473	)))\|(% style="width:47px" %)(((
51.8	474	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
51.11	475	)))\|(% style="width:15px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	476
146.1	477	[[image:1664502425687-834.png\|\|_mstalt="296738"]]
19.2	478
	479
79.1	480	* (% style="color:#037691" %)BAT: (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
51.9	481	* (% style="color:#037691" %)MODE: (%%)Define the payload format.
	482	* (% style="color:#037691" %)UUID: (%%)The uuid from the strongest iBeacon.
	483	* (% style="color:#037691" %)MAJOR: (%%) The MAJOR from the strongest iBeacon.
114.1	484	* (% style="color:#037691" %)MINOR: (%%)The MINOR from the strongest iBeacon.
51.9	485	* (% style="color:#037691" %)Measured Power: (%%) The Measured Power from the strongest iBeacon.
	486	* (% style="color:#037691" %)RSSI: (%%) The RSSI from the strongest iBeacon.
19.2	487
191.2	488	(% style="display:none" %) (%%)
186.3	489
188.2	490
106.1	491	=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
105.2	492
84.19	493
109.1	494	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.
19.3	495
50.2	496
86.1	497	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
	498	\|=(% scope="row" style="width: 60px;" %)(((
	499	Size(bytes)
	500	)))\|(% style="width:60px" %)6\|(% style="width:60px" %)4\|(% style="width:79px" %)2\|(% style="width:66px" %)1
	501	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)SSID\|(% style="width:87px" %)RSSI\|(% style="width:79px" %)(((
	502	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
	503	)))\|(% style="width:66px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	504
86.1	505	(% class="wikigeneratedid" %)
146.1	506	[[image:1667288597595-714.png\|\|_mstalt="299598" height="212" width="1151"]]
86.1	507
	508
	509	* (% style="color:#037691" %)BAT: (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
	510	* (% style="color:#037691" %)SSID: (%%)WiFi name.
	511	* (% style="color:#037691" %)RSSI: (%%)The RSSI from the strongest WiFi.
	512
191.2	513	(% style="display:none" %) (%%)
186.3	514
188.2	515
86.1	516	=== 2.4.7 Add Payload format in TTN V3 ===
	517
	518
	519	In TTN V3, user can add a custom payload so it shows friendly.
	520
51.9	521	In the page (% style="color:#037691" %)Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
19.2	522
	523
146.1	524	[[image:1664502649601-895.png\|\|_mstalt="296985"]]
50.2	525
51.9	526
143.2	527
78.7	528	Add the decoder from this link:
19.2	529
78.7	530	[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
19.2	531
	532	Save the change the uplink message will be parsed. As below:
	533
146.1	534	[[image:1664502676891-606.png\|\|_mstalt="296673"]]
19.2	535
	536
66.3	537	== 2.5 Integrate with Datacake ==
19.2	538
84.5	539
19.2	540	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.
	541
50.2	542	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]]
19.2	543
113.4	544
146.1	545	[[image:1664502695771-538.png\|\|_mstalt="297349"]]
19.2	546
50.2	547
66.3	548	== 2.6 Integrate with Tago ==
19.2	549
	550
81.1	551	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.
	552
19.2	553	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]]
	554
	555
146.1	556	[[image:1664502715371-321.png\|\|_mstalt="292162"]]
19.2	557
	558
68.4	559	== 2.7 Datalog Feature ==
56.1	560
68.4	561
78.1	562	total 273 entries,by default,
56.1	563
164.2	564	User can set [[PNACKMD=1>>\|\|anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
68.4	565
71.1	566	Example use case.
68.4	567
146.1	568	[[image:image-20221009234703-2.png\|\|_mstalt="429143" height="328" width="899"]]
71.1	569
	570
146.1	571	[[image:image-20221009234629-1.png\|\|_mstalt="431145" height="390" width="577"]]
71.1	572
	573
66.3	574	== 2.8 Alarm Mode ==
19.2	575
	576
51.27	577	(((
51.11	578	User can push the (% style="color:red" %)RED button(%%) by more than 5 seconds to enter Alarm Mode.
51.27	579	)))
19.2	580
	581
51.27	582	(((
81.1	583	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.
51.27	584	)))
19.2	585
	586
51.27	587	(((
143.2	588	Two ways to exit alarm mode:
51.27	589	)))
19.2	590
81.1	591	* Server sends a downlink command to exit.
19.2	592	* User fast press the RED button 10 times.
	593
51.27	594	(((
51.11	595	When exit alarm mode, (% style="color:red" %)RED LED(%%) will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false.
51.27	596	)))
19.2	597
	598
66.3	599	== 2.9 Transport Mode ==
19.2	600
	601
57.1	602	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.
19.2	603
151.1	604	* [[MTDC>>\|\|anchor="H3.2.3SetTransportModePackettransmissioninterval"]] defines the Uplink Interval during transportation.
	605	* [[TDC>>\|\|anchor="H3.2.1SetTransmitInterval"]] defines the uplink interval when TrackerD is stactic.
153.1	606	* [[PT>>\|\|anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]] defines the threldhold to detect a motion.
55.1	607
191.2	608	(% style="display:none" %) (%%)
186.3	609
188.2	610
66.3	611	== 2.10 LED Status ==
19.2	612
	613
113.7	614	(% border="1.5" style="background-color:#ffffcc; width:500px" %)
51.27	615	\|=(% style="width: 150px;" %)Event\|=(% style="width: 200px;" %)Action\|=(% style="width: 150px;" %)AT+LON to control on/off
51.11	616	\|(% 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
	617	\|(% style="width:157px" %)Join request\|(% style="width:271px" %)(% style="color:green" %)Green (%%)led fast blink once (200ms)\|(% style="width:202px" %)Yes
	618	\|(% style="width:157px" %)Join Success\|(% style="width:271px" %)(% style="color:green" %)Green(%%) led on 5 second\|(% style="width:202px" %)N/A
	619	\|(% style="width:157px" %)Fixing Location\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)blinks 200ms per second\|(% style="width:202px" %)Yes
113.7	620	\|(% style="width:157px" %)Fixed and uplink\|(% style="width:271px" %)(% style="color:green" %)GREEN (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
51.11	621	\|(% style="width:157px" %)Fail Fix and uplink\|(% style="width:271px" %)(% style="color:red" %)RED (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	622	\|(% style="width:157px" %)Enter Alarm mode\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 3 seconds\|(% style="width:202px" %)Yes
	623	\|(% style="width:157px" %)Uplink under Alarm\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 1 second\|(% style="width:202px" %)Yes
	624	\|(% style="width:157px" %)Exit Alarm\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)led on 5 second\|(% style="width:202px" %)Yes
	625	\|(% style="width:157px" %)Get Downlink\|(% style="width:271px" %)(% style="color:green" %)GREEN(%%) led on 1 second\|(% style="width:202px" %)Yes
	626	\|(% style="width:157px" %)Movement Detect\|(% style="width:271px" %)(% style="color:red" %)RED (%%)led on 500ms\|(% style="width:202px" %)N/A
19.2	627
191.2	628	(% style="display:none" %) (%%)
186.3	629
188.2	630
66.3	631	== 2.11 Button Function ==
19.2	632
50.2	633
51.27	634	(% style="color:blue" %)RESET button:
19.2	635
146.1	636	[[image:1664502835802-546.png\|\|_mstalt="295061"]]
19.2	637
	638	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
	639
	640
51.11	641	(% style="color:red" %)RED button:
19.2	642
191.2	643	[[image:image-20230213110506-3.png]](% style="display:none" %)
19.2	644
191.2	645	(% style="display:none" %) (%%)
19.2	646
113.7	647	(% border="1" style="background-color:#ffffcc; width:510px" %)
84.18	648	\|=(% style="width: 100px;" %)Function\|=(% style="width: 205px;" %)Action\|=(% style="width: 205px;" %)Description
113.6	649	\|(% 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"]]
51.11	650	\|(% 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
50.2	651	\|(% 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.
19.2	652
191.2	653	(% style="display:none" %) (%%)
186.3	654
188.2	655
66.3	656	== 2.12 USB Port Function ==
19.2	657
50.2	658
19.2	659	The USB interface of TrackerD has below functions:
	660
	661	* Power on the device
	662	* Recharge the battery
51.11	663	* [[Configure Device>>\|\|anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
	664	* [[Upgrade Firmware>>\|\|anchor="H5.UploadFirmware"]]
19.2	665
191.2	666	(% style="display:none" %) (%%)
186.3	667
188.2	668
19.3	669	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
19.2	670
	671
	672	User can configure TrackerD via AT Command or LoRaWAN Downlink.
	673
51.13	674	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
19.2	675
	676
19.3	677	== 3.1 Access AT Command ==
19.2	678
	679
50.2	680	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.
19.2	681
	682
146.1	683	[[image:1664502999401-486.png\|\|_mstalt="296985"]]
50.2	684
	685
51.11	686	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:
19.2	687
	688
146.1	689	[[image:1664503022490-662.png\|\|_mstalt="293332"]]
19.2	690
	691
146.1	692	[[image:1664503035713-500.png\|\|_mstalt="291096"]]
19.2	693
	694
146.1	695	[[image:1664503047675-651.png\|\|_mstalt="295386"]]
50.2	696
191.2	697	(% style="display:none" %) (%%)
50.2	698
19.3	699	== 3.2 Command Set ==
19.2	700
19.3	701	=== 3.2.1 Set Transmit Interval ===
19.2	702
50.2	703
19.2	704	Set device uplink interval.
	705
51.13	706	* (% style="color:blue" %)AT Command:
19.2	707
51.13	708	(% style="color:#037691" %)AT+TDC=xxx
19.2	709
50.2	710	Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
19.2	711
	712
51.13	713	* (% style="color:blue" %)Downlink Payload (prefix 0x01):
19.2	714
51.13	715	(% style="color:#037691" %)0x01 00 01 2C (%%) ~/~/ Same as AT+TDC=300000
19.2	716
	717
19.3	718	=== 3.2.2 Set Alarm Packet transmission interval ===
19.2	719
50.2	720
19.2	721	Set alarm packet transmit interval
	722
51.13	723	* (% style="color:blue" %)AT Command:
19.2	724
51.13	725	(% style="color:#037691" %)AT+ATDC=xx.
19.2	726
51.2	727	Example: AT+ATDC=60000 ~-~-> Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000
19.2	728
	729
51.13	730	* (% style="color:blue" %)Downlink Payload (prefix 0xB1):
19.2	731
51.13	732	(% style="color:#037691" %)0xB1 00 00 3C (%%) ~/~/ Same as AT+ATDC=60000
19.2	733
	734
57.1	735	=== 3.2.3 Set Transport Mode Packet transmission interval ===
50.2	736
	737
57.1	738	Set Transport Mode packet transmit interval
19.2	739
51.13	740	* (% style="color:blue" %)AT Command:
19.2	741
51.13	742	(% style="color:#037691" %)AT+MTDC=xx.
19.2	743
57.1	744	Example: AT+MTDC=300000 ~-~-> Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
19.2	745
	746
51.13	747	* (% style="color:blue" %)Downlink Payload (prefix 0x03):
19.2	748
111.1	749	(% style="color:#037691" %)0x03 00 01 2C (%%) ~/~/ Same as AT+MTDC=3000000
19.2	750
	751
50.2	752	=== 3.2.4 Exit Alarm ===
19.2	753
50.2	754
19.2	755	Server send downlink command to exit Alarm mode
	756
51.13	757	* (% style="color:blue" %)AT Command: No AT Command
19.2	758
51.13	759	* (% style="color:blue" %)Downlink Payload (prefix 0x02):
19.2	760
51.13	761	(% style="color:#037691" %)0x02 01 (%%) ~/~/ Exit Alarm Mode
19.2	762
51.13	763
188.1	764	=== 3.2.5 Disable/Enable LED flash and buzzer ===
50.2	765
	766
19.2	767	Disable/Enable LED for position, downlink and uplink
	768
51.13	769	* (% style="color:blue" %)AT Command:
19.2	770
51.13	771	(% style="color:#037691" %)AT+LON=xx. (Disable (0), Enable (1), default:1)
19.2	772
51.28	773	Example: AT+LON=0 ~-~-> Disable LED for position, downlink and uplink.
19.2	774
	775
51.13	776	* (% style="color:blue" %)Downlink Payload (prefix 0xAE):
19.2	777
51.13	778	(% style="color:#037691" %)0xAE 00 (%%) ~/~/ Same as AT+LON=0
19.2	779
	780
59.1	781	=== 3.2.6 Disable/Enable Transport Mode ===
19.2	782
	783
59.1	784	Users can use this feature to enable/disable Transport Mode.
19.2	785
51.13	786	* (% style="color:blue" %)AT Command:
19.2	787
51.13	788	(% style="color:#037691" %)AT+INTWK=xx. (Disable (0), Enable (1), default:0)
19.2	789
111.1	790	Example: AT+INTWK=1 ~-~-> Enable Transport Mode.
19.2	791
	792
51.13	793	* (% style="color:blue" %)Downlink Payload (prefix 0xAF):
19.2	794
111.1	795	(% style="color:#037691" %)0xAF 01 (%%) ~/~/ Same as AT+INTWK=1
19.2	796
	797
50.2	798	=== 3.2.7 Set Positioning Mode ===
19.2	799
50.2	800
79.1	801	SMOD define how TrackerD scan and uplink data:
19.2	802
	803
51.13	804	* (% style="color:blue" %)AT Command:
19.2	805
74.5	806	(% style="color:#037691" %)AT+SMOD=aa,bb,cc
19.2	807
60.2	808	(% style="color:#037691" %) aa:
19.2	809
87.1	810	* (% style="color:red" %)1: GPS ONLY(Factory Settings): (%%)Only get and uplink GPS location info.
113.3	811
88.1	812	* (% 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.
113.3	813
113.4	814	* (% 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.
60.2	815
	816	(% style="color:#037691" %)bb:
	817
74.5	818	* (% style="color:red" %)0 : (%%)GPS+ BAT+ State+Tem&Hum
113.2	819
74.5	820	* (% style="color:red" %)1 :(%%) GPS +BAT State
60.2	821
74.5	822	(% style="color:#037691" %)cc:
60.2	823
147.1	824	* (% _mstmutation="1" style="color:red" %)1 : (%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
113.2	825
146.1	826	* (% _mstmutation="1" style="color:red" %)2 : (%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))
60.2	827
74.5	828	(% style="color:blue" %)Example:
19.2	829
111.1	830	AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum
113.2	831
111.1	832	AT+SMOD=1,1,0 ~-~-> GPS +BAT State
113.2	833
111.1	834	AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
113.2	835
111.1	836	AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State
19.2	837
	838
51.13	839	* (% style="color:blue" %)Downlink Payload (prefix 0xA5):
19.2	840
111.1	841	(% style="color:#037691" %)0xA5 01 00 00 (%%) ~/~/ Same as AT+SMOD=1,0,0
19.2	842
	843
50.2	844	=== 3.2.8 Set MAX GPS position time ===
	845
	846
19.2	847	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.
	848
	849
143.2	850	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.
19.2	851
	852
51.13	853	* (% style="color:blue" %)AT Command:
19.2	854
51.13	855	(% style="color:#037691" %)AT+FTIME=xx (%%) ~-~-> Set to use xx as max fix time.
19.2	856
74.5	857	Example: AT+FTIME=150
19.2	858
	859
51.13	860	* (% style="color:blue" %)Downlink Payload (prefix 0xAA):
19.2	861
51.13	862	(% style="color:#037691" %)0xAA 00 96 (%%) ~/~/ Set AT+FTIME=150
19.2	863
	864
68.4	865	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
19.2	866
	867
50.2	868	PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can't get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.
19.2	869
50.2	870
19.2	871	A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
	872
	873
51.13	874	* (% style="color:blue" %)AT Command:
19.2	875
51.13	876	(% style="color:#037691" %)AT+PDOP=2.5 (%%) ~-~-> Set PDOP to 2.5
19.2	877
	878
51.13	879	* (% style="color:blue" %)Downlink Payload (prefix 0xAD):
19.2	880
51.13	881	(% style="color:#037691" %)0xAD 00 0A (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1)
19.2	882
51.13	883	(% style="color:#037691" %)0xAD 00 19 (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5)
19.2	884
51.13	885	(% style="color:#037691" %)0xAD 00 46 (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7)
19.2	886
50.2	887
155.3	888	=== 3.2.10 Disable/Enable the confirmation mode ===
19.2	889
155.4	890
51.13	891	* (% style="color:blue" %)AT Command:
19.2	892
74.6	893	(% style="color:#037691" %)AT+CFM=xx
19.2	894
	895
50.2	896	~ Example:
19.2	897
107.1	898	AT+CFM=0 ~-~-> Disable confirmation
19.2	899
107.1	900	AT+CFM=1 ~-~-> Enable confirmation
19.2	901
50.2	902
51.13	903	* (% style="color:blue" %)Downlink Payload (prefix 0x05):
19.2	904
111.1	905	(% style="color:#037691" %)0x05 01 (%%) ~/~/ Same as AT+CFM=1
19.2	906
	907
148.1	908	=== 3.2.11 Auto Send None-ACK messages ===
74.6	909
	910
	911	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.
	912
	913
	914	* (% style="color:blue" %)AT Command: AT+PNACKMD
	915
	916	The default factory setting is 0.
	917
	918
	919	Command Example Function Response:
	920
	921	(% style="color:#037691" %)AT+PNACKMD=1 (%%) ~/~/ Poll None-ACK message OK
	922
	923
	924	* (% style="color:blue" %)Downlink Command: 0x34
	925
148.1	926	Example: 0x34 01 ~/~/ Same as AT+PNACKMD=1
74.6	927
	928
148.1	929	=== 3.2.12 Set BLEMASK to filter BLE iBeacon ===
80.1	930
84.2	931
86.1	932	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.
80.1	933
84.5	934	(% style="color:red" %)Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.
80.1	935
84.5	936	(% style="color:blue" %)AT Command:
80.1	937
146.1	938	(% _mstmutation="1" style="color:#037691" %)AT+BLEMASK=123456 (%%) ~/~/ Set BLEMASK = 123456
80.1	939
146.1	940	(% _mstmutation="1" style="color:#037691" %)AT+BLEMASK=0 (%%) ~/~/ disable BLEMASK
80.1	941
100.1	942	(% style="color:blue" %)Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）
84.5	943
148.1	944	Example: 0xB2 01 02 03 04 05 06 ~/~/ Set BLEMASK to 123456
100.1	945
105.2	946
148.1	947	=== 3.2.13 Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
84.5	948
86.1	949
108.1	950	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.
86.1	951
	952	(% style="color:red" %)Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.
	953
	954	(% style="color:blue" %)AT Command:
	955
146.1	956	(% _mstmutation="1" style="color:#037691" %)AT+WiFiMASK=123456 (%%) ~/~/ Set WiFiMASK = 123456
86.1	957
146.1	958	(% _mstmutation="1" style="color:#037691" %)AT+WiFiMASK=0 (%%) ~/~/ disable WiFiMASK
86.1	959
100.1	960	(% style="color:blue" %)Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）
86.1	961
148.1	962	Example: 0xB3 01 02 03 04 05 06 ~/~/ Set WiFiMASK to 123456
100.1	963
105.2	964
148.1	965	=== 3.2.14 Disable/Enable Information printing（Since firmware 1.4.1） ===
98.1	966
	967
	968	Users can use this feature to enable/disable Information printing.
	969
	970	(% style="color:blue" %)AT Command:
	971
164.3	972	(% style="color:#037691" %)AT+SHOWID=XX (%%) ~/~/ (Disable (0), Enable (1), default:0)
111.1	973	\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
98.1	974
	975
164.3	976	=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
104.1	977
105.2	978
104.1	979	The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
	980
	981	(% style="color:blue" %)AT Command:
	982
173.1	983	(% style="color:#037691" %)AT+CHE=1 (%%) ~/~/ set one channels mode
104.1	984
113.2	985
113.4	986	(% style="color:blue" %)Downlink Payload:0X24
113.2	987
164.3	988	Example: 0x24 01 ~/~/ Same as AT+CHE=1
104.1	989
	990
164.3	991	=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
152.1	992
164.3	993
152.1	994	User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
	995
	996	(% style="color:blue" %)AT Command:
	997
	998	(% style="color:#037691" %)AT+PT=xx
	999
	1000	Example:
	1001
	1002	AT+PT=14 ~-~-> Set to detect car motion.
	1003
164.3	1004	AT+PT=41 ~-~-> set to detect walk motion.
152.1	1005
	1006
	1007	(% style="color:blue" %)Downlink Payload:0xB4(%%)
	1008	0xB4 14 ~/~/ Same as AT+PT=14
	1009
	1010
19.4	1011	= 4. Setting for Different Scenarios =
19.2	1012
	1013
	1014
19.4	1015	= 5. Upload Firmware =
19.2	1016
19.4	1017	== 5.1 Firmware Change Log ==
	1018
50.2	1019
19.2	1020	[[See this link>>url:https://github.com/dragino/TrackerD]]
	1021
	1022
19.4	1023	== 5.2 How to upgrade firmware ==
19.2	1024
	1025
50.2	1026	User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
19.2	1027
	1028
50.2	1029	(% style="color:blue" %)Step1: (%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
19.2	1030
50.2	1031
	1032	(% style="color:blue" %)Step2: (%%) Install CH9102 driver in the PC.
	1033
19.2	1034	After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
	1035
	1036
51.28	1037	(% style="color:blue" %)Step3: (%%)Download and Install Flash Tool: [[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]]
19.2	1038
	1039
50.2	1040	(% style="color:blue" %)Step4: (%%) Run Flash Download Tool and configure chip type to ESP32
19.2	1041
	1042
146.1	1043	[[image:1664503563660-578.png\|\|_mstalt="296777"]]
19.2	1044
	1045
146.1	1046	[[image:1664503574618-659.png\|\|_mstalt="297986"]]
19.2	1047
50.2	1048
84.2	1049
50.2	1050	(% style="color:blue" %)Step5: (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
	1051
73.1	1052	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
19.2	1053
	1054
143.2	1055	Users need to use below files:
19.2	1056
	1057	boot_app0.bin @0e000
	1058
131.1	1059	US915.bin @ 0x10000(Select the bin file of the frequency band you need)
19.2	1060
	1061
173.1	1062	[[image:image-20221207120501-1.png]]
19.2	1063
	1064
	1065
50.2	1066	After upgrade finish, it will show finish as below:
19.2	1067
173.1	1068	[[image:image-20221207133911-7.png]]
19.2	1069
	1070
19.4	1071	= 6. Developer Guide =
19.2	1072
19.4	1073	== 6.1 Compile Source Code ==
	1074
	1075	=== 6.1.1 Set up ARDUINO compile environment ===
	1076
	1077
51.28	1078	* Download the latest Arduino software (IDE) from the Arduino official website: [[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]
19.2	1079
51.15	1080	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]]
19.2	1081
	1082
146.1	1083	[[image:1664503635019-941.png\|\|_mstalt="294658"]]
19.2	1084
50.2	1085
68.4	1086
51.28	1087	* (% style="color:#037691" %)Go to tools ~-~-> Boards ~-~-> Boards Manager,(%%) find the esp32 information and install it.
19.2	1088
146.1	1089	[[image:1664503715811-892.png\|\|_mstalt="295698"]]
19.2	1090
	1091
186.3	1092	=== 6.1.2 Build the development environment ===
181.1	1093
	1094
186.2	1095	~1. Download and install arduino IDE
	1096
181.1	1097	[[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]]
	1098
	1099
186.2	1100	2. Download the ESP32 development package in the arduino IDE
181.1	1101
	1102	[[image:image-20221213100007-1.png]]
	1103
186.2	1104
181.1	1105	Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
	1106
	1107	[[image:image-20221213100626-2.png]]
	1108
186.2	1109
181.1	1110	Restart the IDE after the addition is complete, then:
	1111
	1112	[[image:image-20221213100808-3.png\|\|height="679" width="649"]]
	1113
186.2	1114
181.1	1115	[[image:image-20221213101040-4.png]]
	1116
186.2	1117
	1118	(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
181.1	1119	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)**
	1120
	1121	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:
	1122
186.2	1123	(% style="color:blue" %)Methods as below:
	1124
182.1	1125	~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
181.1	1126
	1127	2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
	1128
84.3	1129	(% 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.
19.2	1130
181.1	1131	[[image:image-20221213102311-5.png\|\|height="582" width="711"]]
	1132
186.2	1133
186.3	1134	3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)
181.1	1135
	1136	[[image:image-20221213102334-6.png]]
	1137
186.2	1138	(% style="color:red" %)Note: This step requires a python environment
181.1	1139
186.2	1140
181.1	1141	Either way, in the end:
186.2	1142
181.1	1143	The final effect is to open the arduino and you can see the esp32
	1144
184.1	1145	[[image:image-20221213110952-8.png\|\|height="866" width="711"]]
181.1	1146
	1147
	1148
146.1	1149	[[image:image-20221024105643-1.png\|\|_mstalt="428129"]]
84.3	1150
84.4	1151	~ Figure1
84.3	1152
	1153
181.1	1154
146.1	1155	[[image:image-20221024105643-2.png\|\|_mstalt="428493"]]
84.3	1156
84.4	1157	Figure2
84.3	1158
	1159
51.28	1160	* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
19.2	1161
50.2	1162	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
19.2	1163
	1164
146.1	1165	[[image:1664503752288-974.png\|\|_mstalt="298194"]]
19.2	1166
50.2	1167
19.4	1168	== 6.2 Source Code ==
	1169
	1170
51.16	1171	* (% style="color:blue" %)Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
19.2	1172
146.1	1173	[[image:1664503794261-827.png\|\|_mstalt="296387"]]
19.2	1174
	1175
	1176
51.16	1177	* (% style="color:blue" %)Click to upload
19.2	1178
146.1	1179	[[image:1664503808294-336.png\|\|_mstalt="295711"]]
19.2	1180
	1181
	1182
51.16	1183	* (% style="color:blue" %)Check the result, if the upload is successful, as shown below, open the serial port to view the data
19.2	1184
146.1	1185	[[image:1664503824081-592.png\|\|_mstalt="294918"]] [[image:1664503831430-500.png\|\|_mstalt="290784"]]
19.2	1186
	1187
18.2	1188	= 7. FAQ =
15.2	1189
18.2	1190	== 7.1 How to change the LoRa Frequency Bands/Region? ==
14.1	1191
	1192
51.14	1193	User can follow the introduction for [[how to upgrade image>>\|\|anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
14.1	1194
12.1	1195
18.2	1196	== 7.2 What is the pin mapping for the USB program cable? ==
2.1	1197
7.1	1198
146.1	1199	[[image:1664499635206-262.png\|\|_mstalt="295360"]]
7.1	1200
	1201
	1202
51.28	1203	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
51.27	1204	\|=(% style="width: 118px;" %)Pin\|=(% style="width: 67px;" %)Color\|=(% style="width: 123px;" %)USB Pin
18.2	1205	\|(% style="width:118px" %)A4,B4,A9,B9\|(% style="width:67px" %)Red\|(% style="width:123px" %)VCC
	1206	\|(% style="width:118px" %)A7,B7\|(% style="width:67px" %)White\|(% style="width:123px" %)D- (N/A)
	1207	\|(% style="width:118px" %)A6,B6\|(% style="width:67px" %)Green\|(% style="width:123px" %)D+(N/A)
	1208	\|(% style="width:118px" %)A1,B1,A12,B12\|(% style="width:67px" %)Black\|(% style="width:123px" %)GND
	1209	\|(% style="width:118px" %)A5\|(% style="width:67px" %)Purple\|(% style="width:123px" %)MTDC/GOIO13
	1210	\|(% style="width:118px" %)B5\|(% style="width:67px" %)Blue\|(% style="width:123px" %)MTDC/GPIO12
	1211	\|(% style="width:118px" %)A8\|(% style="width:67px" %)Yellow\|(% style="width:123px" %)MTMS/GPIO14
	1212	\|(% style="width:118px" %)B8\|(% style="width:67px" %)Grey\|(% style="width:123px" %)MTDO/GPIO15
7.1	1213
191.2	1214	(% style="display:none" %) (%%)
186.2	1215
188.2	1216
97.1	1217	== 7.3 Notes on using different serial port tools for TrackerD ==
	1218
113.4	1219	=== 7.3.1 Serial port utility ===
97.1	1220
	1221
	1222	Serial port utility requires you to automatically add data streams.
	1223
	1224	Need to adjust the data stream to RTS/CTS on physical restart.
	1225
	1226	(% class="wikigeneratedid" %)
146.1	1227	[[image:image-20221102140621-1.png\|\|_mstalt="425672"]]
97.1	1228
	1229
143.2	1230
97.1	1231	When using AT commands, the data flow needs to be adjusted to XON/XOFF
	1232
146.1	1233	[[image:image-20221102140638-2.png\|\|_mstalt="428727"]]
97.1	1234
	1235
113.4	1236	=== 7.3.2 SecureCRT ===
97.1	1237
	1238
	1239	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.
	1240
	1241
146.1	1242	[[image:image-20221102140704-3.png\|\|_mstalt="427076"]]
97.1	1243
	1244
146.1	1245	[[image:image-20221102140712-4.png\|\|_mstalt="427089"]]
97.1	1246
	1247
113.4	1248	=== 7.3.3 PUTTY ===
97.1	1249
	1250
146.1	1251	[[image:image-20221102140748-5.png\|\|_mstalt="430456"]]
97.1	1252
	1253
	1254	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.
	1255
	1256
146.1	1257	[[image:image-20221102140801-6.png\|\|_mstalt="427466"]]
97.1	1258
98.2	1259
123.1	1260	== 7.4 How to modify source code to compile different frequency band bin file? ==
113.4	1261
133.1	1262
	1263	(% class="box infomessage" %)
	1264	(((
135.1	1265	(% style="color:red" %)Important(%%): Developer MUST follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
134.1	1266	See : [[Set Up Arduino Compile Environment for TrackerD. >>\|\|anchor="H6.1.1SetupARDUINOcompileenvironment"]]
133.1	1267	)))
	1268
143.2	1269	~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
122.1	1270
143.2	1271
146.1	1272	[[image:image-20221116111844-1.png\|\|_mstalt="428688" height="227" width="782"]]
122.1	1273
	1274
143.2	1275
	1276	2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
	1277
	1278
146.1	1279	[[image:image-20221116111844-2.png\|\|_mstalt="429052" height="262" width="781"]]
122.1	1280
	1281
143.2	1282
	1283	3. Compile the AS923_JP band, please refer to the intention shown
	1284
	1285
146.1	1286	[[image:image-20221116111844-3.png\|\|_mstalt="429416" height="338" width="746"]]
122.1	1287
	1288
143.2	1289
	1290	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.
	1291
	1292
146.1	1293	[[image:image-20221116111844-4.png\|\|_mstalt="429780" height="641" width="739"]]
122.1	1294
143.2	1295
146.1	1296	[[image:image-20221116111844-5.png\|\|_mstalt="430144" height="551" width="708"]]
122.1	1297
	1298
187.1	1299	== 7.5 Are there example python example for BLE Indoor Positioning? ==
	1300
	1301
187.3	1302	[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
187.1	1303
187.2	1304
110.1	1305	= 8 Trouble Shooting =
98.2	1306
113.4	1307	== 8.1 TDC is changed to 4294947296 and cause no uplink. ==
	1308
	1309
	1310	(((
155.4	1311	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
113.4	1312	)))
105.1	1313
105.2	1314
113.4	1315	== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode ==
	1316
	1317
	1318	(((
110.1	1319	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.
113.4	1320	)))
7.1	1321
	1322
136.1	1323	== 8.3 Problem after Upgrading Firmware ==
113.4	1324
155.3	1325	=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
113.4	1326
136.1	1327
155.4	1328	Error Output
	1329
	1330
154.1	1331	[[image:image-20221122100004-4.png\|\|_mstalt="424606"]]
	1332
155.4	1333
113.4	1334	(((
154.1	1335	Some partition is missed during upgrade, please upgrade below four files as example:
	1336
173.1	1337	[[image:image-20221207120524-2.png]]
113.4	1338	)))
113.1	1339
113.4	1340
155.3	1341	=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
113.1	1342
	1343
136.1	1344	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
114.1	1345
	1346
155.3	1347	=== 8.3.3 "flash read err" after upgrade firmware ===
143.2	1348
155.4	1349
144.1	1350	Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
142.1	1351
155.4	1352
146.1	1353	[[image:image-20221122100004-1.png\|\|_mstalt="423514" height="497" width="534"]]
142.1	1354
	1355
144.1	1356	User need to upgrade again with below four files to solve this issue.
143.2	1357
173.1	1358	[[image:image-20221207120530-3.png]]
142.1	1359
143.2	1360	Figure 2
142.1	1361
143.2	1362
155.4	1363	=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
143.2	1364
155.4	1365
144.1	1366	User might erase the entire flash include keys and default settings which cause this issue.
	1367
155.4	1368	After the upgrade is completed, enter AT+CFG as shown in the figure below.
142.1	1369
155.4	1370
146.1	1371	[[image:image-20221122100004-3.png\|\|_mstalt="424242"]]
142.1	1372
	1373
155.4	1374	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.
	1375
147.1	1376	After AT+FDR. please set
142.1	1377
155.4	1378	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=7
155.3	1379
155.4	1380	* (% _mstmutation="1" style="color:blue" %)AT+FTIME=180000
147.1	1381
155.4	1382	Example:
144.1	1383
146.1	1384	AT+PDOP=7.00
	1385
	1386	AT+FTIME=180
	1387
144.1	1388	AT+DEUI=70B3D57ED0053981
	1389
142.1	1390	AT+APPEUI=D23345667BCBCCAF
	1391
	1392	AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
	1393
144.1	1394	AT+DADDR=260b4dce ( no need for OTAA)
142.1	1395
144.1	1396	AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d ( no need for OTAA)
142.1	1397
144.1	1398	AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)
142.1	1399
	1400
143.2	1401	== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
142.1	1402
143.2	1403
142.1	1404	Please download version 1.4.2 again
	1405
	1406
143.2	1407	== 8.5 How to deal with unsuccessful GPS positioning? ==
116.1	1408
143.2	1409
	1410	1） Make Sure the device is in Open Area where can see the sky.
	1411
116.1	1412	2) Set PDOP to a higher value.
	1413
148.1	1414	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=2 (%%)(can be positioned precisely.）
132.1	1415
148.1	1416	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=7 (%%)(Quickly locate in open spaces）
132.1	1417
148.1	1418	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=14.7 (%%)(Positioning can be acquired in complex environments）
132.1	1419
116.1	1420	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
	1421
	1422
163.1	1423	== 8.6 When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
	1424
164.3	1425
163.1	1426	When upgrading, use the erase button to upgrade
	1427
173.1	1428	[[image:image-20221207120536-4.png]]
163.1	1429
	1430
	1431	The parameters are displayed abnormally and cannot be fixed using AT+FDR
	1432
	1433	[[image:image-20221128103040-2.png\|\|height="431" width="525"]]
	1434
164.3	1435
163.1	1436	Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
	1437
173.1	1438	[[image:image-20221207134028-8.png]]
163.1	1439
164.3	1440
163.1	1441	Reboot information after upgrade
	1442
	1443	[[image:image-20221128111443-4.png\|\|height="432" width="546"]]
	1444
164.3	1445
188.2	1446	Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
163.1	1447
	1448	[[image:image-20221128111850-5.png]]
	1449
164.3	1450
163.1	1451	After the parameters return to normal, upgrade to the version you need again
	1452
173.1	1453	[[image:image-20221207120601-5.png]]
163.1	1454
164.3	1455
164.1	1456	At this point, the parameters return to normal after running AT+FDR again
163.1	1457
	1458	[[image:image-20221128112035-7.png]]
	1459
	1460
186.2	1461	== 8.7 If you encounter the following problems, please upgrade to the latest version ==
185.1	1462
186.2	1463
186.1	1464	~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
185.1	1465
186.2	1466	2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
185.1	1467
	1468
110.1	1469	= 9. Order Info =
	1470
	1471
15.6	1472	Part Number: (% style="color:blue" %)TrackerD-XXX
8.1	1473
15.6	1474	(% style="color:blue" %)XXX(%%): The default frequency band
8.1	1475
15.6	1476	* (% style="color:red" %)EU433(%%): Default frequency band EU433
143.2	1477
15.6	1478	* (% style="color:red" %)EU868(%%): Default frequency band EU868
143.2	1479
15.6	1480	* (% style="color:red" %)IN865(%%): Default frequency band IN865
143.2	1481
15.6	1482	* (% style="color:red" %)KR920(%%): Default frequency band KR920
143.2	1483
15.6	1484	* (% style="color:red" %)AS923(%%): Default frequency band AS923
143.2	1485
15.6	1486	* (% style="color:red" %)AU915(%%): Default frequency band AU915
143.2	1487
15.6	1488	* (% style="color:red" %)US915(%%): Default frequency band US915
15.2	1489
191.2	1490	(% style="display:none" %) (%%)
186.2	1491
188.2	1492
110.1	1493	= 10. Packing Info =
18.2	1494
	1495
51.30	1496	(% style="color:#037691" %)Package Includes:
8.1	1497
50.3	1498	* TrackerD LoRaWAN GPS/BLE Tracker x 1
143.2	1499
50.3	1500	* USB recharge & program cable x 1
12.1	1501
51.30	1502	(% style="color:#037691" %)Dimensions and Weight:
12.1	1503
98.2	1504	* Device Size: 85 x 48 x 15 mm
143.2	1505
50.3	1506	* Weight: 50g
15.6	1507
191.2	1508	(% style="display:none" %) (%%)
186.2	1509
188.2	1510
110.1	1511	= 11. Support =
18.2	1512
50.3	1513
18.2	1514	* 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.
143.2	1515
51.28	1516	* 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]].
18.2	1517
191.2	1518	(% style="display:none" %) (%%)
186.2	1519
188.2	1520
110.1	1521	= 12. Reference =
18.2	1522
	1523
12.1	1524	* [[Firmware in Bin format>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
143.2	1525
12.1	1526	* [[Source Code>>https://github.com/dragino/TrackerD]]
143.2	1527
12.1	1528	* [[Hardware Source>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
188.2	1529
	1530
	1531
	1532
155.4	1533	)))

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications