Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 188.2 by Xiaoling on 2023/01/06 15:30

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications