Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 186.2 by Xiaoling on 2022/12/16 10:34

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications