Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 198.1 by Bei Jinggeng on 2023/03/07 14:31

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications