Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 195.1 by Bei Jinggeng on 2023/03/07 13:59

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
194.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
194.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
194.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" %)
192.1	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;" %)1\|=(% 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" %)
192.1	259	\|=(% scope="row" style="width: 60px;" %)Size(bit)\|(% style="width:50px" %)1bits\|(% 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
192.2	287	(% border="1.5" style="background-color:#ffffcc; color:green; width:412.222px" %)
	288	\|=(% scope="row" style="width: 75px;" %)Size(bit)\|(% style="width:68px" %)5 Bits\|(% style="width:87px" %)1 Bit\|(% style="width:49px" %)1 Bit\|(% style="width:126px" %)1 Bit
	289	\|=(% 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"]]
74.2	290
186.3	291
194.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
192.2	316	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:279.222px" %)
	317	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:50px" %)1 bit\|(% style="width:69px" %)1 bit\|(% style="width:63px" %)14 bits
	318	\|=(% style="width: 72px;" %)Value\|(% style="width:67px" %)reserve\|(% style="width:69px" %)Alarm Indicate\|(% style="width:63px" %)[[BAT>>\|\|anchor="HBAT:"]]
19.2	319
51.24	320	==== (% style="color:blue" %)FLAG:(%%) ====
	321
192.2	322	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:183.222px" %)
	323	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:30px" %)2 bits\|(% style="width:52px" %)1 bit
	324	\|=(% style="width: 79px;" %)Value\|(% style="width:55px" %)[[MOD>>\|\|anchor="H3.2.7SetPositioningMode"]]\|(% style="width:52px" %)[[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
194.2	490
194.1	491	=== 2.4.6 Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
188.2	492
194.2	493
194.1	494	The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
105.2	495
194.1	496	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
	497	\|Size(bytes)\|2\|1
	498	\|Value\|[[Alarm & BAT>>path:#HAlarm26BAT:]]\|Mod+lon
84.19	499
194.2	500	[[image:image-20230302145315-1.png]]
194.1	501
194.2	502	alarm=(bytes[0] & 0x40) ~/~/ Alarm status
194.1	503
194.2	504	batV=~(~(~(bytes[0] & 0x3f) <<8) \| bytes[1])/1000; ~/~/ Battery,units:V
194.1	505
	506	mod = bytes[2] & 0xC0;
	507
	508	Lon=(bytes[2] & 0x20)
	509
	510
	511	=== 2.4.7 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
	512
	513
109.1	514	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	515
50.2	516
86.1	517	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
	518	\|=(% scope="row" style="width: 60px;" %)(((
	519	Size(bytes)
	520	)))\|(% style="width:60px" %)6\|(% style="width:60px" %)4\|(% style="width:79px" %)2\|(% style="width:66px" %)1
	521	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)SSID\|(% style="width:87px" %)RSSI\|(% style="width:79px" %)(((
	522	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
	523	)))\|(% style="width:66px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	524
86.1	525	(% class="wikigeneratedid" %)
146.1	526	[[image:1667288597595-714.png\|\|_mstalt="299598" height="212" width="1151"]]
86.1	527
	528
	529	* (% style="color:#037691" %)BAT: (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
	530	* (% style="color:#037691" %)SSID: (%%)WiFi name.
	531	* (% style="color:#037691" %)RSSI: (%%)The RSSI from the strongest WiFi.
	532
191.2	533	(% style="display:none" %) (%%)
186.3	534
188.2	535
194.1	536	=== 2.4.8 Add Payload format in TTN V3 ===
86.1	537
	538
	539	In TTN V3, user can add a custom payload so it shows friendly.
	540
51.9	541	In the page (% style="color:#037691" %)Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
19.2	542
	543
146.1	544	[[image:1664502649601-895.png\|\|_mstalt="296985"]]
50.2	545
51.9	546
143.2	547
78.7	548	Add the decoder from this link:
19.2	549
78.7	550	[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
19.2	551
	552	Save the change the uplink message will be parsed. As below:
	553
146.1	554	[[image:1664502676891-606.png\|\|_mstalt="296673"]]
19.2	555
	556
66.3	557	== 2.5 Integrate with Datacake ==
19.2	558
84.5	559
19.2	560	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.
	561
50.2	562	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	563
113.4	564
146.1	565	[[image:1664502695771-538.png\|\|_mstalt="297349"]]
19.2	566
50.2	567
66.3	568	== 2.6 Integrate with Tago ==
19.2	569
	570
81.1	571	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.
	572
19.2	573	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]]
	574
	575
146.1	576	[[image:1664502715371-321.png\|\|_mstalt="292162"]]
19.2	577
	578
68.4	579	== 2.7 Datalog Feature ==
56.1	580
68.4	581
78.1	582	total 273 entries,by default,
56.1	583
164.2	584	User can set [[PNACKMD=1>>\|\|anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
68.4	585
71.1	586	Example use case.
68.4	587
146.1	588	[[image:image-20221009234703-2.png\|\|_mstalt="429143" height="328" width="899"]]
71.1	589
	590
146.1	591	[[image:image-20221009234629-1.png\|\|_mstalt="431145" height="390" width="577"]]
71.1	592
	593
66.3	594	== 2.8 Alarm Mode ==
19.2	595
	596
51.27	597	(((
51.11	598	User can push the (% style="color:red" %)RED button(%%) by more than 5 seconds to enter Alarm Mode.
51.27	599	)))
19.2	600
	601
51.27	602	(((
81.1	603	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	604	)))
19.2	605
	606
51.27	607	(((
143.2	608	Two ways to exit alarm mode:
51.27	609	)))
19.2	610
81.1	611	* Server sends a downlink command to exit.
19.2	612	* User fast press the RED button 10 times.
	613
51.27	614	(((
51.11	615	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	616	)))
19.2	617
	618
66.3	619	== 2.9 Transport Mode ==
19.2	620
	621
57.1	622	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	623
151.1	624	* [[MTDC>>\|\|anchor="H3.2.3SetTransportModePackettransmissioninterval"]] defines the Uplink Interval during transportation.
	625	* [[TDC>>\|\|anchor="H3.2.1SetTransmitInterval"]] defines the uplink interval when TrackerD is stactic.
153.1	626	* [[PT>>\|\|anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]] defines the threldhold to detect a motion.
55.1	627
191.2	628	(% style="display:none" %) (%%)
186.3	629
188.2	630
66.3	631	== 2.10 LED Status ==
19.2	632
	633
113.7	634	(% border="1.5" style="background-color:#ffffcc; width:500px" %)
51.27	635	\|=(% style="width: 150px;" %)Event\|=(% style="width: 200px;" %)Action\|=(% style="width: 150px;" %)AT+LON to control on/off
51.11	636	\|(% 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
	637	\|(% style="width:157px" %)Join request\|(% style="width:271px" %)(% style="color:green" %)Green (%%)led fast blink once (200ms)\|(% style="width:202px" %)Yes
	638	\|(% style="width:157px" %)Join Success\|(% style="width:271px" %)(% style="color:green" %)Green(%%) led on 5 second\|(% style="width:202px" %)N/A
	639	\|(% style="width:157px" %)Fixing Location\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)blinks 200ms per second\|(% style="width:202px" %)Yes
113.7	640	\|(% style="width:157px" %)Fixed and uplink\|(% style="width:271px" %)(% style="color:green" %)GREEN (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
51.11	641	\|(% style="width:157px" %)Fail Fix and uplink\|(% style="width:271px" %)(% style="color:red" %)RED (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	642	\|(% style="width:157px" %)Enter Alarm mode\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 3 seconds\|(% style="width:202px" %)Yes
	643	\|(% style="width:157px" %)Uplink under Alarm\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 1 second\|(% style="width:202px" %)Yes
	644	\|(% style="width:157px" %)Exit Alarm\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)led on 5 second\|(% style="width:202px" %)Yes
	645	\|(% style="width:157px" %)Get Downlink\|(% style="width:271px" %)(% style="color:green" %)GREEN(%%) led on 1 second\|(% style="width:202px" %)Yes
	646	\|(% style="width:157px" %)Movement Detect\|(% style="width:271px" %)(% style="color:red" %)RED (%%)led on 500ms\|(% style="width:202px" %)N/A
19.2	647
191.2	648	(% style="display:none" %) (%%)
186.3	649
188.2	650
66.3	651	== 2.11 Button Function ==
19.2	652
50.2	653
51.27	654	(% style="color:blue" %)RESET button:
19.2	655
146.1	656	[[image:1664502835802-546.png\|\|_mstalt="295061"]]
19.2	657
	658	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
	659
	660
51.11	661	(% style="color:red" %)RED button:
19.2	662
191.2	663	[[image:image-20230213110506-3.png]](% style="display:none" %)
19.2	664
191.2	665	(% style="display:none" %) (%%)
19.2	666
113.7	667	(% border="1" style="background-color:#ffffcc; width:510px" %)
84.18	668	\|=(% style="width: 100px;" %)Function\|=(% style="width: 205px;" %)Action\|=(% style="width: 205px;" %)Description
113.6	669	\|(% 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	670	\|(% 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	671	\|(% 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	672
191.2	673	(% style="display:none" %) (%%)
186.3	674
188.2	675
66.3	676	== 2.12 USB Port Function ==
19.2	677
50.2	678
19.2	679	The USB interface of TrackerD has below functions:
	680
	681	* Power on the device
	682	* Recharge the battery
51.11	683	* [[Configure Device>>\|\|anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
	684	* [[Upgrade Firmware>>\|\|anchor="H5.UploadFirmware"]]
19.2	685
191.2	686	(% style="display:none" %) (%%)
186.3	687
188.2	688
19.3	689	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
19.2	690
	691
	692	User can configure TrackerD via AT Command or LoRaWAN Downlink.
	693
51.13	694	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
19.2	695
	696
19.3	697	== 3.1 Access AT Command ==
19.2	698
	699
50.2	700	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	701
	702
146.1	703	[[image:1664502999401-486.png\|\|_mstalt="296985"]]
50.2	704
	705
51.11	706	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	707
	708
146.1	709	[[image:1664503022490-662.png\|\|_mstalt="293332"]]
19.2	710
	711
146.1	712	[[image:1664503035713-500.png\|\|_mstalt="291096"]]
19.2	713
	714
146.1	715	[[image:1664503047675-651.png\|\|_mstalt="295386"]]
50.2	716
191.2	717	(% style="display:none" %) (%%)
50.2	718
19.3	719	== 3.2 Command Set ==
19.2	720
19.3	721	=== 3.2.1 Set Transmit Interval ===
19.2	722
50.2	723
19.2	724	Set device uplink interval.
	725
51.13	726	* (% style="color:blue" %)AT Command:
19.2	727
51.13	728	(% style="color:#037691" %)AT+TDC=xxx
19.2	729
50.2	730	Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
19.2	731
	732
51.13	733	* (% style="color:blue" %)Downlink Payload (prefix 0x01):
19.2	734
51.13	735	(% style="color:#037691" %)0x01 00 01 2C (%%) ~/~/ Same as AT+TDC=300000
19.2	736
	737
19.3	738	=== 3.2.2 Set Alarm Packet transmission interval ===
19.2	739
50.2	740
19.2	741	Set alarm packet transmit interval
	742
51.13	743	* (% style="color:blue" %)AT Command:
19.2	744
51.13	745	(% style="color:#037691" %)AT+ATDC=xx.
19.2	746
51.2	747	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	748
	749
51.13	750	* (% style="color:blue" %)Downlink Payload (prefix 0xB1):
19.2	751
51.13	752	(% style="color:#037691" %)0xB1 00 00 3C (%%) ~/~/ Same as AT+ATDC=60000
19.2	753
	754
57.1	755	=== 3.2.3 Set Transport Mode Packet transmission interval ===
50.2	756
	757
57.1	758	Set Transport Mode packet transmit interval
19.2	759
51.13	760	* (% style="color:blue" %)AT Command:
19.2	761
51.13	762	(% style="color:#037691" %)AT+MTDC=xx.
19.2	763
57.1	764	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	765
	766
51.13	767	* (% style="color:blue" %)Downlink Payload (prefix 0x03):
19.2	768
111.1	769	(% style="color:#037691" %)0x03 00 01 2C (%%) ~/~/ Same as AT+MTDC=3000000
19.2	770
	771
50.2	772	=== 3.2.4 Exit Alarm ===
19.2	773
50.2	774
19.2	775	Server send downlink command to exit Alarm mode
	776
51.13	777	* (% style="color:blue" %)AT Command: No AT Command
19.2	778
51.13	779	* (% style="color:blue" %)Downlink Payload (prefix 0x02):
19.2	780
51.13	781	(% style="color:#037691" %)0x02 01 (%%) ~/~/ Exit Alarm Mode
19.2	782
51.13	783
188.1	784	=== 3.2.5 Disable/Enable LED flash and buzzer ===
50.2	785
	786
19.2	787	Disable/Enable LED for position, downlink and uplink
	788
51.13	789	* (% style="color:blue" %)AT Command:
19.2	790
51.13	791	(% style="color:#037691" %)AT+LON=xx. (Disable (0), Enable (1), default:1)
19.2	792
51.28	793	Example: AT+LON=0 ~-~-> Disable LED for position, downlink and uplink.
19.2	794
	795
51.13	796	* (% style="color:blue" %)Downlink Payload (prefix 0xAE):
19.2	797
51.13	798	(% style="color:#037691" %)0xAE 00 (%%) ~/~/ Same as AT+LON=0
19.2	799
	800
59.1	801	=== 3.2.6 Disable/Enable Transport Mode ===
19.2	802
	803
59.1	804	Users can use this feature to enable/disable Transport Mode.
19.2	805
51.13	806	* (% style="color:blue" %)AT Command:
19.2	807
51.13	808	(% style="color:#037691" %)AT+INTWK=xx. (Disable (0), Enable (1), default:0)
19.2	809
111.1	810	Example: AT+INTWK=1 ~-~-> Enable Transport Mode.
19.2	811
	812
51.13	813	* (% style="color:blue" %)Downlink Payload (prefix 0xAF):
19.2	814
111.1	815	(% style="color:#037691" %)0xAF 01 (%%) ~/~/ Same as AT+INTWK=1
19.2	816
	817
50.2	818	=== 3.2.7 Set Positioning Mode ===
19.2	819
50.2	820
79.1	821	SMOD define how TrackerD scan and uplink data:
19.2	822
	823
51.13	824	* (% style="color:blue" %)AT Command:
19.2	825
74.5	826	(% style="color:#037691" %)AT+SMOD=aa,bb,cc
19.2	827
60.2	828	(% style="color:#037691" %) aa:
19.2	829
87.1	830	* (% style="color:red" %)1: GPS ONLY(Factory Settings): (%%)Only get and uplink GPS location info.
113.3	831
88.1	832	* (% 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	833
113.4	834	* (% 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	835
	836	(% style="color:#037691" %)bb:
	837
74.5	838	* (% style="color:red" %)0 : (%%)GPS+ BAT+ State+Tem&Hum
113.2	839
74.5	840	* (% style="color:red" %)1 :(%%) GPS +BAT State
60.2	841
74.5	842	(% style="color:#037691" %)cc:
60.2	843
147.1	844	* (% _mstmutation="1" style="color:red" %)1 : (%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
113.2	845
146.1	846	* (% _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	847
74.5	848	(% style="color:blue" %)Example:
19.2	849
111.1	850	AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum
113.2	851
111.1	852	AT+SMOD=1,1,0 ~-~-> GPS +BAT State
113.2	853
111.1	854	AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
113.2	855
111.1	856	AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State
19.2	857
	858
51.13	859	* (% style="color:blue" %)Downlink Payload (prefix 0xA5):
19.2	860
111.1	861	(% style="color:#037691" %)0xA5 01 00 00 (%%) ~/~/ Same as AT+SMOD=1,0,0
19.2	862
	863
50.2	864	=== 3.2.8 Set MAX GPS position time ===
	865
	866
19.2	867	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.
	868
	869
143.2	870	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	871
	872
51.13	873	* (% style="color:blue" %)AT Command:
19.2	874
51.13	875	(% style="color:#037691" %)AT+FTIME=xx (%%) ~-~-> Set to use xx as max fix time.
19.2	876
74.5	877	Example: AT+FTIME=150
19.2	878
	879
51.13	880	* (% style="color:blue" %)Downlink Payload (prefix 0xAA):
19.2	881
51.13	882	(% style="color:#037691" %)0xAA 00 96 (%%) ~/~/ Set AT+FTIME=150
19.2	883
	884
68.4	885	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
19.2	886
	887
50.2	888	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	889
50.2	890
19.2	891	A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
	892
	893
51.13	894	* (% style="color:blue" %)AT Command:
19.2	895
51.13	896	(% style="color:#037691" %)AT+PDOP=2.5 (%%) ~-~-> Set PDOP to 2.5
19.2	897
	898
51.13	899	* (% style="color:blue" %)Downlink Payload (prefix 0xAD):
19.2	900
51.13	901	(% style="color:#037691" %)0xAD 00 0A (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1)
19.2	902
51.13	903	(% style="color:#037691" %)0xAD 00 19 (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5)
19.2	904
51.13	905	(% style="color:#037691" %)0xAD 00 46 (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7)
19.2	906
50.2	907
155.3	908	=== 3.2.10 Disable/Enable the confirmation mode ===
19.2	909
155.4	910
51.13	911	* (% style="color:blue" %)AT Command:
19.2	912
74.6	913	(% style="color:#037691" %)AT+CFM=xx
19.2	914
	915
50.2	916	~ Example:
19.2	917
107.1	918	AT+CFM=0 ~-~-> Disable confirmation
19.2	919
107.1	920	AT+CFM=1 ~-~-> Enable confirmation
19.2	921
50.2	922
51.13	923	* (% style="color:blue" %)Downlink Payload (prefix 0x05):
19.2	924
111.1	925	(% style="color:#037691" %)0x05 01 (%%) ~/~/ Same as AT+CFM=1
19.2	926
	927
148.1	928	=== 3.2.11 Auto Send None-ACK messages ===
74.6	929
	930
	931	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.
	932
	933
	934	* (% style="color:blue" %)AT Command: AT+PNACKMD
	935
	936	The default factory setting is 0.
	937
	938
	939	Command Example Function Response:
	940
	941	(% style="color:#037691" %)AT+PNACKMD=1 (%%) ~/~/ Poll None-ACK message OK
	942
	943
	944	* (% style="color:blue" %)Downlink Command: 0x34
	945
148.1	946	Example: 0x34 01 ~/~/ Same as AT+PNACKMD=1
74.6	947
	948
148.1	949	=== 3.2.12 Set BLEMASK to filter BLE iBeacon ===
80.1	950
84.2	951
86.1	952	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	953
84.5	954	(% style="color:red" %)Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.
80.1	955
84.5	956	(% style="color:blue" %)AT Command:
80.1	957
146.1	958	(% _mstmutation="1" style="color:#037691" %)AT+BLEMASK=123456 (%%) ~/~/ Set BLEMASK = 123456
80.1	959
146.1	960	(% _mstmutation="1" style="color:#037691" %)AT+BLEMASK=0 (%%) ~/~/ disable BLEMASK
80.1	961
100.1	962	(% style="color:blue" %)Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）
84.5	963
148.1	964	Example: 0xB2 01 02 03 04 05 06 ~/~/ Set BLEMASK to 123456
100.1	965
105.2	966
148.1	967	=== 3.2.13 Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
84.5	968
86.1	969
108.1	970	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	971
	972	(% style="color:red" %)Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.
	973
	974	(% style="color:blue" %)AT Command:
	975
146.1	976	(% _mstmutation="1" style="color:#037691" %)AT+WiFiMASK=123456 (%%) ~/~/ Set WiFiMASK = 123456
86.1	977
146.1	978	(% _mstmutation="1" style="color:#037691" %)AT+WiFiMASK=0 (%%) ~/~/ disable WiFiMASK
86.1	979
100.1	980	(% style="color:blue" %)Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）
86.1	981
148.1	982	Example: 0xB3 01 02 03 04 05 06 ~/~/ Set WiFiMASK to 123456
100.1	983
105.2	984
148.1	985	=== 3.2.14 Disable/Enable Information printing（Since firmware 1.4.1） ===
98.1	986
	987
	988	Users can use this feature to enable/disable Information printing.
	989
	990	(% style="color:blue" %)AT Command:
	991
164.3	992	(% style="color:#037691" %)AT+SHOWID=XX (%%) ~/~/ (Disable (0), Enable (1), default:0)
111.1	993	\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
98.1	994
	995
164.3	996	=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
104.1	997
105.2	998
104.1	999	The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
	1000
	1001	(% style="color:blue" %)AT Command:
	1002
173.1	1003	(% style="color:#037691" %)AT+CHE=1 (%%) ~/~/ set one channels mode
104.1	1004
113.2	1005
113.4	1006	(% style="color:blue" %)Downlink Payload:0X24
113.2	1007
164.3	1008	Example: 0x24 01 ~/~/ Same as AT+CHE=1
104.1	1009
	1010
164.3	1011	=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
152.1	1012
164.3	1013
152.1	1014	User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
	1015
	1016	(% style="color:blue" %)AT Command:
	1017
	1018	(% style="color:#037691" %)AT+PT=xx
	1019
	1020	Example:
	1021
	1022	AT+PT=14 ~-~-> Set to detect car motion.
	1023
164.3	1024	AT+PT=41 ~-~-> set to detect walk motion.
152.1	1025
	1026
	1027	(% style="color:blue" %)Downlink Payload:0xB4(%%)
	1028	0xB4 14 ~/~/ Same as AT+PT=14
	1029
	1030
19.4	1031	= 4. Setting for Different Scenarios =
19.2	1032
	1033
	1034
19.4	1035	= 5. Upload Firmware =
19.2	1036
19.4	1037	== 5.1 Firmware Change Log ==
	1038
50.2	1039
19.2	1040	[[See this link>>url:https://github.com/dragino/TrackerD]]
	1041
	1042
19.4	1043	== 5.2 How to upgrade firmware ==
19.2	1044
	1045
50.2	1046	User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
19.2	1047
	1048
50.2	1049	(% style="color:blue" %)Step1: (%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
19.2	1050
50.2	1051
	1052	(% style="color:blue" %)Step2: (%%) Install CH9102 driver in the PC.
	1053
19.2	1054	After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
	1055
	1056
51.28	1057	(% 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	1058
	1059
50.2	1060	(% style="color:blue" %)Step4: (%%) Run Flash Download Tool and configure chip type to ESP32
19.2	1061
	1062
146.1	1063	[[image:1664503563660-578.png\|\|_mstalt="296777"]]
19.2	1064
	1065
146.1	1066	[[image:1664503574618-659.png\|\|_mstalt="297986"]]
19.2	1067
50.2	1068
84.2	1069
50.2	1070	(% style="color:blue" %)Step5: (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
	1071
73.1	1072	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
19.2	1073
	1074
143.2	1075	Users need to use below files:
19.2	1076
	1077	boot_app0.bin @0e000
	1078
131.1	1079	US915.bin @ 0x10000(Select the bin file of the frequency band you need)
19.2	1080
	1081
173.1	1082	[[image:image-20221207120501-1.png]]
19.2	1083
	1084
	1085
50.2	1086	After upgrade finish, it will show finish as below:
19.2	1087
173.1	1088	[[image:image-20221207133911-7.png]]
19.2	1089
	1090
19.4	1091	= 6. Developer Guide =
19.2	1092
19.4	1093	== 6.1 Compile Source Code ==
	1094
	1095	=== 6.1.1 Set up ARDUINO compile environment ===
	1096
	1097
51.28	1098	* 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	1099
51.15	1100	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	1101
	1102
146.1	1103	[[image:1664503635019-941.png\|\|_mstalt="294658"]]
19.2	1104
50.2	1105
68.4	1106
51.28	1107	* (% style="color:#037691" %)Go to tools ~-~-> Boards ~-~-> Boards Manager,(%%) find the esp32 information and install it.
19.2	1108
146.1	1109	[[image:1664503715811-892.png\|\|_mstalt="295698"]]
19.2	1110
	1111
186.3	1112	=== 6.1.2 Build the development environment ===
181.1	1113
	1114
186.2	1115	~1. Download and install arduino IDE
	1116
181.1	1117	[[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]]
	1118
	1119
186.2	1120	2. Download the ESP32 development package in the arduino IDE
181.1	1121
	1122	[[image:image-20221213100007-1.png]]
	1123
186.2	1124
181.1	1125	Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
	1126
	1127	[[image:image-20221213100626-2.png]]
	1128
186.2	1129
181.1	1130	Restart the IDE after the addition is complete, then:
	1131
	1132	[[image:image-20221213100808-3.png\|\|height="679" width="649"]]
	1133
186.2	1134
181.1	1135	[[image:image-20221213101040-4.png]]
	1136
186.2	1137
	1138	(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
181.1	1139	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)**
	1140
192.2	1141
181.1	1142	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:
	1143
186.2	1144	(% style="color:blue" %)Methods as below:
	1145
182.1	1146	~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
181.1	1147
	1148	2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
	1149
84.3	1150	(% 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	1151
181.1	1152	[[image:image-20221213102311-5.png\|\|height="582" width="711"]]
	1153
186.2	1154
186.3	1155	3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)
181.1	1156
	1157	[[image:image-20221213102334-6.png]]
	1158
186.2	1159	(% style="color:red" %)Note: This step requires a python environment
181.1	1160
186.2	1161
181.1	1162	Either way, in the end:
186.2	1163
181.1	1164	The final effect is to open the arduino and you can see the esp32
	1165
184.1	1166	[[image:image-20221213110952-8.png\|\|height="866" width="711"]]
181.1	1167
	1168
	1169
146.1	1170	[[image:image-20221024105643-1.png\|\|_mstalt="428129"]]
84.3	1171
84.4	1172	~ Figure1
84.3	1173
	1174
181.1	1175
146.1	1176	[[image:image-20221024105643-2.png\|\|_mstalt="428493"]]
84.3	1177
84.4	1178	Figure2
84.3	1179
	1180
51.28	1181	* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
19.2	1182
50.2	1183	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
19.2	1184
	1185
146.1	1186	[[image:1664503752288-974.png\|\|_mstalt="298194"]]
19.2	1187
50.2	1188
19.4	1189	== 6.2 Source Code ==
	1190
	1191
51.16	1192	* (% style="color:blue" %)Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
19.2	1193
146.1	1194	[[image:1664503794261-827.png\|\|_mstalt="296387"]]
19.2	1195
	1196
	1197
51.16	1198	* (% style="color:blue" %)Click to upload
19.2	1199
146.1	1200	[[image:1664503808294-336.png\|\|_mstalt="295711"]]
19.2	1201
	1202
	1203
51.16	1204	* (% style="color:blue" %)Check the result, if the upload is successful, as shown below, open the serial port to view the data
19.2	1205
146.1	1206	[[image:1664503824081-592.png\|\|_mstalt="294918"]] [[image:1664503831430-500.png\|\|_mstalt="290784"]]
19.2	1207
	1208
18.2	1209	= 7. FAQ =
15.2	1210
18.2	1211	== 7.1 How to change the LoRa Frequency Bands/Region? ==
14.1	1212
	1213
51.14	1214	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	1215
12.1	1216
18.2	1217	== 7.2 What is the pin mapping for the USB program cable? ==
2.1	1218
7.1	1219
146.1	1220	[[image:1664499635206-262.png\|\|_mstalt="295360"]]
7.1	1221
	1222
	1223
51.28	1224	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
51.27	1225	\|=(% style="width: 118px;" %)Pin\|=(% style="width: 67px;" %)Color\|=(% style="width: 123px;" %)USB Pin
18.2	1226	\|(% style="width:118px" %)A4,B4,A9,B9\|(% style="width:67px" %)Red\|(% style="width:123px" %)VCC
	1227	\|(% style="width:118px" %)A7,B7\|(% style="width:67px" %)White\|(% style="width:123px" %)D- (N/A)
	1228	\|(% style="width:118px" %)A6,B6\|(% style="width:67px" %)Green\|(% style="width:123px" %)D+(N/A)
	1229	\|(% style="width:118px" %)A1,B1,A12,B12\|(% style="width:67px" %)Black\|(% style="width:123px" %)GND
	1230	\|(% style="width:118px" %)A5\|(% style="width:67px" %)Purple\|(% style="width:123px" %)MTDC/GOIO13
	1231	\|(% style="width:118px" %)B5\|(% style="width:67px" %)Blue\|(% style="width:123px" %)MTDC/GPIO12
	1232	\|(% style="width:118px" %)A8\|(% style="width:67px" %)Yellow\|(% style="width:123px" %)MTMS/GPIO14
	1233	\|(% style="width:118px" %)B8\|(% style="width:67px" %)Grey\|(% style="width:123px" %)MTDO/GPIO15
7.1	1234
191.2	1235	(% style="display:none" %) (%%)
186.2	1236
188.2	1237
97.1	1238	== 7.3 Notes on using different serial port tools for TrackerD ==
	1239
113.4	1240	=== 7.3.1 Serial port utility ===
97.1	1241
	1242
	1243	Serial port utility requires you to automatically add data streams.
	1244
	1245	Need to adjust the data stream to RTS/CTS on physical restart.
	1246
	1247	(% class="wikigeneratedid" %)
146.1	1248	[[image:image-20221102140621-1.png\|\|_mstalt="425672"]]
97.1	1249
	1250
143.2	1251
97.1	1252	When using AT commands, the data flow needs to be adjusted to XON/XOFF
	1253
146.1	1254	[[image:image-20221102140638-2.png\|\|_mstalt="428727"]]
97.1	1255
	1256
113.4	1257	=== 7.3.2 SecureCRT ===
97.1	1258
	1259
	1260	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.
	1261
	1262
146.1	1263	[[image:image-20221102140704-3.png\|\|_mstalt="427076"]]
97.1	1264
	1265
146.1	1266	[[image:image-20221102140712-4.png\|\|_mstalt="427089"]]
97.1	1267
	1268
113.4	1269	=== 7.3.3 PUTTY ===
97.1	1270
	1271
146.1	1272	[[image:image-20221102140748-5.png\|\|_mstalt="430456"]]
97.1	1273
	1274
	1275	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.
	1276
	1277
146.1	1278	[[image:image-20221102140801-6.png\|\|_mstalt="427466"]]
97.1	1279
98.2	1280
123.1	1281	== 7.4 How to modify source code to compile different frequency band bin file? ==
113.4	1282
133.1	1283
	1284	(% class="box infomessage" %)
	1285	(((
135.1	1286	(% style="color:red" %)Important(%%): Developer MUST follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
134.1	1287	See : [[Set Up Arduino Compile Environment for TrackerD. >>\|\|anchor="H6.1.1SetupARDUINOcompileenvironment"]]
133.1	1288	)))
	1289
143.2	1290	~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
122.1	1291
143.2	1292
146.1	1293	[[image:image-20221116111844-1.png\|\|_mstalt="428688" height="227" width="782"]]
122.1	1294
	1295
143.2	1296
	1297	2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
	1298
	1299
146.1	1300	[[image:image-20221116111844-2.png\|\|_mstalt="429052" height="262" width="781"]]
122.1	1301
	1302
143.2	1303
	1304	3. Compile the AS923_JP band, please refer to the intention shown
	1305
	1306
146.1	1307	[[image:image-20221116111844-3.png\|\|_mstalt="429416" height="338" width="746"]]
122.1	1308
	1309
143.2	1310
	1311	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.
	1312
	1313
146.1	1314	[[image:image-20221116111844-4.png\|\|_mstalt="429780" height="641" width="739"]]
122.1	1315
143.2	1316
146.1	1317	[[image:image-20221116111844-5.png\|\|_mstalt="430144" height="551" width="708"]]
122.1	1318
	1319
187.1	1320	== 7.5 Are there example python example for BLE Indoor Positioning? ==
	1321
	1322
187.3	1323	[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
187.1	1324
187.2	1325
110.1	1326	= 8 Trouble Shooting =
98.2	1327
113.4	1328	== 8.1 TDC is changed to 4294947296 and cause no uplink. ==
	1329
	1330
	1331	(((
155.4	1332	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	1333	)))
105.1	1334
105.2	1335
113.4	1336	== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode ==
	1337
	1338
	1339	(((
110.1	1340	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	1341	)))
7.1	1342
	1343
136.1	1344	== 8.3 Problem after Upgrading Firmware ==
113.4	1345
155.3	1346	=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
113.4	1347
136.1	1348
155.4	1349	Error Output
	1350
	1351
154.1	1352	[[image:image-20221122100004-4.png\|\|_mstalt="424606"]]
	1353
155.4	1354
113.4	1355	(((
154.1	1356	Some partition is missed during upgrade, please upgrade below four files as example:
	1357
173.1	1358	[[image:image-20221207120524-2.png]]
113.4	1359	)))
113.1	1360
113.4	1361
155.3	1362	=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
113.1	1363
	1364
136.1	1365	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	1366
	1367
155.3	1368	=== 8.3.3 "flash read err" after upgrade firmware ===
143.2	1369
155.4	1370
144.1	1371	Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
142.1	1372
155.4	1373
146.1	1374	[[image:image-20221122100004-1.png\|\|_mstalt="423514" height="497" width="534"]]
142.1	1375
	1376
144.1	1377	User need to upgrade again with below four files to solve this issue.
143.2	1378
173.1	1379	[[image:image-20221207120530-3.png]]
142.1	1380
143.2	1381	Figure 2
142.1	1382
143.2	1383
155.4	1384	=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
143.2	1385
155.4	1386
144.1	1387	User might erase the entire flash include keys and default settings which cause this issue.
	1388
155.4	1389	After the upgrade is completed, enter AT+CFG as shown in the figure below.
142.1	1390
155.4	1391
146.1	1392	[[image:image-20221122100004-3.png\|\|_mstalt="424242"]]
142.1	1393
	1394
155.4	1395	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.
	1396
147.1	1397	After AT+FDR. please set
142.1	1398
155.4	1399	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=7
155.3	1400
155.4	1401	* (% _mstmutation="1" style="color:blue" %)AT+FTIME=180000
147.1	1402
155.4	1403	Example:
144.1	1404
146.1	1405	AT+PDOP=7.00
	1406
	1407	AT+FTIME=180
	1408
144.1	1409	AT+DEUI=70B3D57ED0053981
	1410
142.1	1411	AT+APPEUI=D23345667BCBCCAF
	1412
	1413	AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
	1414
144.1	1415	AT+DADDR=260b4dce ( no need for OTAA)
142.1	1416
144.1	1417	AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d ( no need for OTAA)
142.1	1418
144.1	1419	AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)
142.1	1420
	1421
143.2	1422	== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
142.1	1423
143.2	1424
142.1	1425	Please download version 1.4.2 again
	1426
	1427
143.2	1428	== 8.5 How to deal with unsuccessful GPS positioning? ==
116.1	1429
143.2	1430
	1431	1） Make Sure the device is in Open Area where can see the sky.
	1432
116.1	1433	2) Set PDOP to a higher value.
	1434
148.1	1435	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=2 (%%)(can be positioned precisely.）
132.1	1436
148.1	1437	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=7 (%%)(Quickly locate in open spaces）
132.1	1438
148.1	1439	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=14.7 (%%)(Positioning can be acquired in complex environments）
132.1	1440
116.1	1441	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
	1442
	1443
163.1	1444	== 8.6 When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
	1445
164.3	1446
163.1	1447	When upgrading, use the erase button to upgrade
	1448
173.1	1449	[[image:image-20221207120536-4.png]]
163.1	1450
	1451
	1452	The parameters are displayed abnormally and cannot be fixed using AT+FDR
	1453
	1454	[[image:image-20221128103040-2.png\|\|height="431" width="525"]]
	1455
164.3	1456
163.1	1457	Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
	1458
173.1	1459	[[image:image-20221207134028-8.png]]
163.1	1460
164.3	1461
163.1	1462	Reboot information after upgrade
	1463
	1464	[[image:image-20221128111443-4.png\|\|height="432" width="546"]]
	1465
164.3	1466
188.2	1467	Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
163.1	1468
	1469	[[image:image-20221128111850-5.png]]
	1470
164.3	1471
163.1	1472	After the parameters return to normal, upgrade to the version you need again
	1473
173.1	1474	[[image:image-20221207120601-5.png]]
163.1	1475
164.3	1476
164.1	1477	At this point, the parameters return to normal after running AT+FDR again
163.1	1478
	1479	[[image:image-20221128112035-7.png]]
	1480
	1481
186.2	1482	== 8.7 If you encounter the following problems, please upgrade to the latest version ==
185.1	1483
186.2	1484
186.1	1485	~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
185.1	1486
186.2	1487	2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
185.1	1488
	1489
110.1	1490	= 9. Order Info =
	1491
	1492
15.6	1493	Part Number: (% style="color:blue" %)TrackerD-XXX
8.1	1494
15.6	1495	(% style="color:blue" %)XXX(%%): The default frequency band
8.1	1496
15.6	1497	* (% style="color:red" %)EU433(%%): Default frequency band EU433
143.2	1498
15.6	1499	* (% style="color:red" %)EU868(%%): Default frequency band EU868
143.2	1500
15.6	1501	* (% style="color:red" %)IN865(%%): Default frequency band IN865
143.2	1502
15.6	1503	* (% style="color:red" %)KR920(%%): Default frequency band KR920
143.2	1504
15.6	1505	* (% style="color:red" %)AS923(%%): Default frequency band AS923
143.2	1506
15.6	1507	* (% style="color:red" %)AU915(%%): Default frequency band AU915
143.2	1508
15.6	1509	* (% style="color:red" %)US915(%%): Default frequency band US915
15.2	1510
191.2	1511	(% style="display:none" %) (%%)
186.2	1512
188.2	1513
110.1	1514	= 10. Packing Info =
18.2	1515
	1516
51.30	1517	(% style="color:#037691" %)Package Includes:
8.1	1518
50.3	1519	* TrackerD LoRaWAN GPS/BLE Tracker x 1
143.2	1520
50.3	1521	* USB recharge & program cable x 1
12.1	1522
51.30	1523	(% style="color:#037691" %)Dimensions and Weight:
12.1	1524
98.2	1525	* Device Size: 85 x 48 x 15 mm
143.2	1526
50.3	1527	* Weight: 50g
15.6	1528
191.2	1529	(% style="display:none" %) (%%)
186.2	1530
188.2	1531
110.1	1532	= 11. Support =
18.2	1533
50.3	1534
18.2	1535	* 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	1536
51.28	1537	* 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	1538
191.2	1539	(% style="display:none" %) (%%)
186.2	1540
188.2	1541
110.1	1542	= 12. Reference =
18.2	1543
	1544
12.1	1545	* [[Firmware in Bin format>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
143.2	1546
12.1	1547	* [[Source Code>>https://github.com/dragino/TrackerD]]
143.2	1548
12.1	1549	* [[Hardware Source>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
188.2	1550
	1551
155.4	1552	)))

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications