Wiki source code of TrackerD -- LoRaWAN Tracker User Manual

Version 227.1 by Bei Jinggeng on 2024/07/11 14:38

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
205.6	96	(% style="display:none" %)
198.2	97
209.53	98
210.2	99
19.2	100	== 1.3 Features ==
	101
	102
	103	* LoRaWAN 1.0.3 Class A
	104	* ESP32 PICO D4
	105	* SX1276/78 Wireless Chip
51.31	106	* Arduino IDE Compatible
19.2	107	* Open source hardware / software
	108	* Regular/ Real-time GPS,BLE,WIFI tracking
	109	* Built-in3 axis accelerometer (LIS3DH)
	110	* Humidity / temperature sensor : GXCAS Technology GXHT3X
	111	* Motion sensing capability
	112	* Power Monitoring
	113	* Charging circuit via USB port
	114	* 1000mA Li-on Battery power
	115	* Tri-color LED, Alarm button
	116	* Datalog
	117
205.6	118	(% style="display:none" %)
198.2	119
205.3	120
210.2	121
19.2	122	== 1.4 Applications ==
	123
	124
12.1	125	* Logistics and Supply Chain Management
	126	* Human tracking
	127
205.6	128	(% style="display:none" %)
198.2	129
205.3	130
210.2	131
105.2	132	= 2. Use TrackerD =
	133
19.3	134	== 2.1 How it works? ==
19.2	135
19.3	136
19.2	137	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.
	138
	139
19.3	140	== 2.2 Quick guide to connect to LoRaWAN server ==
19.2	141
	142
50.2	143	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	144
	145
191.2	146	[[image:image-20230213110214-2.png\|\|height="388" width="847"]]
19.2	147
50.2	148
19.2	149	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:
	150
	151
50.2	152	(% style="color:blue" %)Step 1:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
	153
19.2	154	Each TrackerD is shipped with a sticker with the default device EUI as below:
	155
51.3	156
209.2	157	[[image:image-20230426085815-1.png\|\|height="259" width="558"]]
19.2	158
	159
	160	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
	161
	162
50.2	163	__Add APP EUI in the application:__
19.2	164
146.1	165	[[image:1664501711466-918.png\|\|_mstalt="295828"]]
19.2	166
	167
146.1	168	[[image:1664501721248-725.png\|\|_mstalt="294450"]]
19.2	169
	170
146.1	171	[[image:1664501734705-405.png\|\|_mstalt="293306"]]
19.2	172
	173
50.2	174	__Add APP KEY and DEV EUI:__
19.2	175
	176
146.1	177	[[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	178
	179
125.1	180	(% style="color:blue" %)Step 2:(%%) Push this button will activate this device.
19.2	181
146.1	182	(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png\|\|_mstalt="295061"]]
50.2	183
146.1	184	[[image:1664502835802-546.png\|\|_mstalt="295061"]]
124.1	185
	186
50.2	187	(% 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.
	188
	189
66.3	190	== 2.3 Positioning Mode(SMOD) ==
50.2	191
66.3	192
55.1	193	Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
19.2	194
87.1	195	* (% style="color:#037691" %)GPS ONLY(Factory Settings): (%%)Only get and uplink GPS location info.
	196	* (% 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	197	* (% 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	198
55.1	199	Users can switch modes by [[changing SMOD>>\|\|anchor="H3.2.7SetPositioningMode"]].
19.2	200
50.2	201
66.3	202	== 2.4 Uplink Payload ==
19.2	203
66.3	204	=== 2.4.1 Uplink FPORT~=5, Device Status ===
66.2	205
66.3	206
209.4	207	Uplink the device configures with (% style="color:blue" %)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	208
209.5	209	Use can also get the Device Status uplink through the downlink command: (% style="color:#037691" %)Downlink: 0x2301
19.2	210
216.6	211	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:440px" %)
216.15	212	\|(% style="background-color:#4f81bd; color:white; width:63px" %)Size(bytes)\|=(% style="width: 72px;background-color:#4F81BD;color:white" %)1\|=(% style="width: 72px;background-color:#4F81BD;color:white" %)2\|=(% style="width: 70px;background-color:#4F81BD;color:white" %)1\|=(% style="width: 50px;background-color:#4F81BD;color:white" %)1\|=(% style="width: 31px;background-color:#4F81BD;color:white" %)2\|=(% style="width: 41px;background-color:#4F81BD;color:white" %)1\|=(% style="width: 41px;background-color:#4F81BD;color:white" %)1
216.8	213	\|(% style="width:108px" %)Value\|(% style="width:82px" %)Sensor Model\|(% style="width:83px" %)Firmware Version\|(% style="width:94px" %)Frequency Band\|(% style="width:84px" %)Sub-band\|(% style="width:44px" %)BAT\|(% style="width:63px" %)SMOD\|(% style="width:60px" %)Status
19.2	214
146.1	215	[[image:1665301570342-765.png\|\|_mstalt="294580"]]
66.2	216
	217
74.2	218	(% style="color:#037691" %)Example of Device Status:(%%) 13014001FF0FA24002
19.2	219
74.2	220	(% style="color:#037691" %)Sensor Model: (%%) For TrackerD,this value is 0x13
19.2	221
74.2	222	(% style="color:#037691" %)Firmware Version: (%%) 0x0140,Means:v1.4.0 version
50.2	223
74.2	224	(% style="color:#037691" %)Frequency Band:
55.1	225
210.2	226	0x01: EU868
55.1	227
210.2	228	0x02: US915
55.1	229
210.2	230	0x03: IN865
55.1	231
210.2	232	0x04: AU915
55.1	233
210.2	234	0x05: KZ865
55.1	235
210.2	236	0x06: RU864
55.1	237
210.2	238	0x07: AS923
55.1	239
210.2	240	0x08: AS923-1
55.1	241
210.2	242	0x09: AS923-2
55.1	243
210.2	244	0x0a: AS923-3
55.1	245
210.2	246	(% style="color:#037691" %)Sub-Band:(%%) value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
55.1	247
74.2	248	(% style="color:#037691" %)BAT:(%%) shows the battery voltage for TrackerD.
55.1	249
74.2	250	(% style="color:#037691" %)Ex1:(%%) 0x0FA2 = 4002mV
	251
55.1	252	Use can also get the Device Status uplink through the downlink command:
	253
	254
75.1	255	(% style="color:#037691" %)SMOD Field (total 1 byte)(%%)：0x40
74.2	256
209.8	257	(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:270px" %)
216.11	258	\|(% style="background-color:#4f81bd; color:white; width:60px" %)Size(bit)\|(% style="background-color:#4f81bd; color:white; width:50px" %)1 bit\|(% style="background-color:#4f81bd; color:white; width:80px" %)2 bits\|(% style="background-color:#4f81bd; color:white; width:80px" %)4 bits
216.6	259	\|(% style="width:75px" %)Value\|(% style="width:64px" %)SMOD\|(% style="width:104px" %)GPS_Settings\|(% style="width:103px" %)BLE_Settings
74.2	260
212.2	261	(% style="color:blue" %)SMOD：
74.2	262
212.2	263	(% style="color:red" %)1 : (%%) GPS ONLY
74.2	264
212.2	265	(% style="color:red" %)2 : (%%) BLE ONLY
74.2	266
212.2	267	(% style="color:red" %)3 : (%%) GPS/BLE Hybrid
74.2	268
	269
212.2	270	(% style="color:blue" %)GPS_MOD: Define how to send GPS payload
74.2	271
212.2	272	(% style="color:red" %)0 : (%%) Enable uploading on-board Temperature and humidity values
74.2	273
212.2	274	(% style="color:red" %)1 : (%%) Disable uploading on-board Temperature and humidity values
74.2	275
	276
212.2	277	(% style="color:blue" %)BLE_Settings:
74.2	278
212.2	279	(% style="color:red" %)1: (%%) BLE Positioning with Strongest iBeacon
74.2	280
212.2	281	(% _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	282
88.1	283
75.1	284	(% style="color:#037691" %)Status Field (total 1 byte)(%%): 0x02
74.2	285
210.2	286	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:413px" %)
216.14	287	\|(% style="background-color:#4f81bd; color:white; width:77px" %)Size(bit)\|(% style="background-color:#4f81bd; color:white; width:70px" %)5 Bits\|(% style="background-color:#4f81bd; color:white; width:88px" %)1 Bit\|(% style="background-color:#4f81bd; color:white; width:50px" %)1 Bit\|(% style="background-color:#4f81bd; color:white; width:128px" %)1 Bit
216.9	288	\|(% 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	289
205.6	290	(% style="display:none" %)
198.2	291
205.4	292
66.3	293	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
55.1	294
	295
209.20	296	Users can use (% style="color:blue" %)AT+SMOD=1,0,0(%%) to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
55.1	297
216.10	298	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
216.14	299	\|(% style="background-color:#4f81bd; color:white; width:60px" %)Size(bytes)\|(% style="background-color:#4f81bd; color:white; width:50px" %)4\|(% style="background-color:#4f81bd; color:white; width:50px" %)4\|(% style="background-color:#4f81bd; color:white; width:70px" %)2\|(% style="background-color:#4f81bd; color:white; width:30px" %)1\|(% style="background-color:#4f81bd; color:white; width:30px" %)2\|(% style="background-color:#4f81bd; color:white; width:30px" %)2
216.10	300	\|(% style="width:69px" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
51.5	301	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
59.2	302	)))\|(% style="width:73px" %)[[FLAG>>\|\|anchor="HFLAG:"]]\|(% style="width:40px" %)[[Hum>>\|\|anchor="HHum:"]]\|(% style="width:87px" %)[[Tem>>\|\|anchor="HTem:"]]
19.2	303
146.1	304	[[image:1665301636888-168.png\|\|_mstalt="298012"]]
19.2	305
50.2	306
51.24	307	==== (% style="color:blue" %)Alarm & BAT:(%%) ====
19.2	308
216.14	309	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:329px" %)
	310	\|(% style="background-color:#4f81bd; color:white; width:60px" %)Size(bit)\|(% style="background-color:#4f81bd; color:white; width:60px" %)1 bit\|(% style="background-color:#4f81bd; color:white; width:134px" %)1 bit\|(% style="background-color:#4f81bd; color:white; width:75px" %)14 bits
216.10	311	\|(% style="width:72px" %)Value\|(% style="width:67px" %)reserve\|(% style="width:114px" %)Alarm Indicate\|(% style="width:62px" %)[[BAT>>\|\|anchor="HBAT:"]]
19.2	312
205.6	313	(% style="display:none" %)
205.4	314
205.5	315
51.24	316	==== (% style="color:blue" %)FLAG:(%%) ====
	317
216.10	318	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:184px" %)
216.14	319	\|(% style="background-color:#4f81bd; color:white; width:68px" %)Size(bit)\|(% style="background-color:#4f81bd; color:white; width:61px" %)2 bits\|(% style="background-color:#4f81bd; color:white; width:55px" %)1 bit
216.10	320	\|(% style="width:79px" %)Value\|(% style="width:56px" %)[[MOD>>\|\|anchor="H3.2.7SetPositioningMode"]]\|(% style="width:50px" %)[[LON>>\|\|anchor="HLON:"]]
19.2	321
51.11	322	Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A
19.2	323
	324
51.24	325	==== (% style="color:blue" %)Location info:(%%) ====
19.2	326
51.11	327	* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976//
	328	* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
19.2	329
51.9	330	(% style="color:red" %)Important note:
19.2	331
50.2	332	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	333
59.3	334	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	335
	336
146.1	337	[[image:1664502116362-706.png\|\|_mstalt="293306"]]
19.2	338
	339
59.3	340	3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
50.2	341
146.1	342	[[image:1664502166010-515.png\|\|_mstalt="291395"]]
50.2	343
	344
51.24	345	==== (% style="color:blue" %)Alarm:(%%) ====
50.2	346
74.9	347	Example: 0x4B & 0x40 >> 6 = 0x01
19.2	348
	349
51.24	350	==== (% style="color:blue" %)BAT:(%%) ====
51.6	351
74.9	352	Example: 0x4B45 & 0x3FFF ⇒ 2885 (mV).
51.6	353
51.27	354	(((
59.3	355	The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
51.27	356	)))
51.6	357
50.4	358	* > 4.0v : 80% ~~ 100%
	359	* 3.85v ~~3.99v: 60% ~~ 80%
	360	* 3.70v ~~ 3.84v: 40% ~~ 60%
	361	* 3.40v ~~ 3.69v: 20% ~~ 40%
	362	* < 3.39v: 0~~20%
19.2	363
191.2	364	(% style="display:none" %) (%%)
188.2	365
74.3	366	==== (% style="color:blue" %)MOD:(%%) ====
	367
79.1	368	Example: (0x60>>6) & 0x3f =1
74.10	369
216.16	370	Set the format of GPS data uplink link:
74.3	371
74.7	372	(% style="color:#037691" %)0x00: (%%) Enable uploading on-board Temperature and humidity values
74.9	373	(% style="color:#037691" %)0x01: (%%) Disable uploading on-board Temperature and humidity values
74.3	374
	375
74.7	376	Set the format of BLE data uplink link：
74.3	377
74.7	378	(% style="color:#037691" %)0x01: (%%) BLE Positioning with Strongest iBeacon
	379
	380
74.10	381	==== (% style="color:blue" %)LON:(%%) ====
74.9	382
74.10	383	Example: (0x60>>5) & 0x01=1.
74.9	384
51.4	385	Enable/Disable LED activity for uplink
19.2	386
51.27	387	(((
74.7	388	(% style="color:#037691" %)0x00: (%%) Disable LED indicator.
51.27	389	)))
19.2	390
51.27	391	(((
74.7	392	(% style="color:#037691" %)0x01: (%%) Enable LED indicator (Default Value)
51.27	393	)))
19.2	394
	395
51.24	396	==== (% style="color:blue" %)Hum:(%%) ====
19.2	397
51.4	398	0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
19.2	399
	400
51.24	401	==== (% style="color:blue" %)Tem:(%%) ====
19.2	402
51.9	403	011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
51.4	404
	405
66.3	406	=== 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
51.4	407
66.2	408
209.23	409	The default uplink payload includes total 11 bytes ((% style="color:blue" %)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	410
	411
216.10	412	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
216.12	413	\|(% style="background-color:#4f81bd; color:white; width:60px" %)Size(bytes)\|(% style="background-color:#4f81bd; color:white; width:60px" %)4\|(% style="background-color:#4f81bd; color:white; width:60px" %)4\|(% style="background-color:#4f81bd; color:white; width:70px" %)2\|(% style="background-color:#4f81bd; color:white; width:50px" %)1
216.10	414	\|(% style="width:69px" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
59.2	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
209.27	436	(% border="1" style="background-color:#f2f2f2; width:500px" %)
216.13	437	\|(% style="background-color:#4f81bd; color:white" %)Size(bytes)\|(% style="background-color:#4f81bd; color:white" %)4\|(% style="background-color:#4f81bd; color:white" %)4\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)1
216.12	438	\|Value\|Latitude\|Longitude\|Year\|Month\|Day\|Hous\|Min\|Sen
59.3	439
146.1	440	[[image:image-20221009160309-2.png\|\|_mstalt="429312"]]
59.3	441
66.2	442
66.3	443	=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
59.3	444
84.2	445
81.1	446	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	447
82.1	448	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	449
81.1	450
216.10	451	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:450px" %)
220.1	452	\|(% style="background-color:#4f81bd; color:white; width:60px" %)Size(bytes)\|(% style="background-color:#4f81bd; color:white; width:30px" %)16\|(% style="background-color:#4f81bd; color:white; width:50px" %)2\|(% style="background-color:#4f81bd; color:white; width:50px" %)2\|(% style="background-color:#4f81bd; color:white; width:120px" %)1\|(% style="background-color:#4f81bd; color:white; width:50px" %)1\|(% style="background-color:#4f81bd; color:white; width:50px" %)2\|(% style="background-color:#4f81bd; color:white; width:30px" %)1
216.10	453	\|(% style="width:50px" %)Value\|(% style="width:44px" %)[[UUID>>\|\|anchor="HLocationinfo:"]]\|(% style="width:61px" %)(((
51.8	454	iBeacon MAJOR
51.11	455	)))\|(% style="width:63px" %)(((
	456	iBeacon MINOR
50.2	457	)))\|(% style="width:71px" %)(((
51.8	458	iBeacon Measured Power
51.11	459	)))\|(% style="width:50px" %)(((
51.8	460	iBeacon RSSI
51.11	461	)))\|(% style="width:47px" %)(((
51.8	462	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
51.11	463	)))\|(% style="width:15px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	464
146.1	465	[[image:1664502425687-834.png\|\|_mstalt="296738"]]
19.2	466
	467
79.1	468	* (% style="color:#037691" %)BAT: (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
51.9	469	* (% style="color:#037691" %)MODE: (%%)Define the payload format.
	470	* (% style="color:#037691" %)UUID: (%%)The uuid from the strongest iBeacon.
	471	* (% style="color:#037691" %)MAJOR: (%%) The MAJOR from the strongest iBeacon.
114.1	472	* (% style="color:#037691" %)MINOR: (%%)The MINOR from the strongest iBeacon.
51.9	473	* (% style="color:#037691" %)Measured Power: (%%) The Measured Power from the strongest iBeacon.
	474	* (% style="color:#037691" %)RSSI: (%%) The RSSI from the strongest iBeacon.
19.2	475
191.2	476	(% style="display:none" %) (%%)
186.3	477
194.1	478	=== 2.4.6 Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
188.2	479
194.2	480
194.1	481	The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
105.2	482
216.17	483	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:284px" %)
	484	\|(% style="background-color:#4f81bd; color:white; width:98px" %)Size(bytes)\|(% style="background-color:#4f81bd; color:white; width:104px" %)2\|(% style="background-color:#4f81bd; color:white; width:82px" %)1
216.10	485	\|(% style="width:97px" %)Value\|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]\|(% style="width:81px" %)Mod+lon
84.19	486
194.2	487	[[image:image-20230302145315-1.png]]
194.1	488
205.2	489	alarm=(bytes[0] & 0x40) ~/~/ Alarm status
194.1	490
205.2	491	batV=~(~(~(bytes[0] & 0x3f) <<8) \| bytes[1])/1000; ~/~/ Battery,units:V
194.1	492
205.2	493	mod = bytes[2] & 0xC0;
194.1	494
205.2	495	Lon=(bytes[2] & 0x20)
194.1	496
	497
	498	=== 2.4.7 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
	499
	500
109.1	501	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	502
216.11	503	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:348px" %)
216.12	504	\|(% style="background-color:#4f81bd; color:white; width:65px" %)(((
86.1	505	Size(bytes)
216.12	506	)))\|(% style="background-color:#4f81bd; color:white; width:50px" %)6\|(% style="background-color:#4f81bd; color:white; width:50px" %)4\|(% style="background-color:#4f81bd; color:white; width:133px" %)2\|(% style="background-color:#4f81bd; color:white; width:50px" %)1
216.11	507	\|(% style="width:69px" %)Value\|(% style="width:48px" %)SSID\|(% style="width:48px" %)RSSI\|(% style="width:103px" %)(((
86.1	508	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
209.33	509	)))\|(% style="width:52px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	510
86.1	511	(% class="wikigeneratedid" %)
146.1	512	[[image:1667288597595-714.png\|\|_mstalt="299598" height="212" width="1151"]]
86.1	513
	514	* (% style="color:#037691" %)BAT: (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
	515	* (% style="color:#037691" %)SSID: (%%)WiFi name.
	516	* (% style="color:#037691" %)RSSI: (%%)The RSSI from the strongest WiFi.
	517
191.2	518	(% style="display:none" %) (%%)
186.3	519
219.2	520	=== 2.4.8 Uplink FPORT~=9, BLE Positioning with Multiple iBeacon(Since firmware 1.4.7) ===
210.6	521
219.2	522
214.1	523	TrackerD supports BLE scanning for indoor positioning. Users can set SMOD to BLE pure or GPS/BLE Hybrid, so TrackerD will scan up to 40 BLE iBeacons and send uplinks.
86.1	524
227.1	525	User can set [[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)BLEMASK>>path:#H3.2.11A0SetBLEMASKtofilterBLEiBeacon]](%%) so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
86.1	526
216.11	527	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:348px" %)
224.1	528	\|(% style="background-color:#4f81bd; color:white" %)Size(bytes)\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)2\|(% style="background-color:#4f81bd; color:white" %)1\|(% style="background-color:#4f81bd; color:white" %)...
	529	\|Value\|[[Alarm & BAT>>path:#HAlarm26BAT:]]\|[[FLAG>>path:#HFLAG:]]\|iBeacon MAJOR\|iBeacon MINOR\|iBeacon RSSI\|iBeacon MAJOR\|iBeacon MINOR\|iBeacon RSSI\|...
214.1	530
215.2	531	(% class="wikigeneratedid" id="H" %)
224.1	532	[[image:image-20240606162359-1.png\|\|height="361" width="716"]]
214.1	533
	534	* (% style="color:#037691" %)BAT: (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
	535	* (% style="color:#037691" %)MAJOR: (%%) The MAJOR from the strongest iBeacon.
	536	* (% style="color:#037691" %)MINOR: (%%)The MINOR from the strongest iBeacon.
	537	* (% style="color:#037691" %)RSSI: (%%) The RSSI from the strongest iBeacon.
225.1	538	* (% style="color:#037691" %)MOD: (%%)Bluetooth mode: 1: Search the beacon with the strongest signal. 2: Search the three beacons with the strongest signal. 3: Search all Bluetooth beacons (up to 40 Bluetooth beacons are displayed).
214.1	539
	540	(% class="wikigeneratedid" %)
219.2	541	(% style="color:red" %)Note: This mode does not have a fixed decoder. Its decoder depends on the number of beacons and can be parsed according to the order of the payload.
	542
224.1	543	payload format: BAT+State+(Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...
214.1	544
	545
	546	=== 2.4.9 Add Payload format in TTN V3 ===
	547
	548
86.1	549	In TTN V3, user can add a custom payload so it shows friendly.
	550
51.9	551	In the page (% style="color:#037691" %)Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
19.2	552
146.1	553	[[image:1664502649601-895.png\|\|_mstalt="296985"]]
50.2	554
51.9	555
209.32	556	Add the decoder from this link: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
19.2	557
	558	Save the change the uplink message will be parsed. As below:
	559
146.1	560	[[image:1664502676891-606.png\|\|_mstalt="296673"]]
19.2	561
	562
66.3	563	== 2.5 Integrate with Datacake ==
19.2	564
84.5	565
19.2	566	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.
	567
50.2	568	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	569
146.1	570	[[image:1664502695771-538.png\|\|_mstalt="297349"]]
19.2	571
50.2	572
66.3	573	== 2.6 Integrate with Tago ==
19.2	574
	575
81.1	576	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.
	577
19.2	578	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]]
	579
146.1	580	[[image:1664502715371-321.png\|\|_mstalt="292162"]]
19.2	581
	582
197.1	583	== 2.7 Integrate with Node-red ==
56.1	584
198.2	585
197.1	586	~1. Install node-red, please refer to the installation method in the link:
68.4	587
209.31	588	[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
202.2	589
	590
197.1	591	2. Import the created flow template, please refer to the import method in the link:
	592
209.31	593	[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
	594
197.1	595
209.31	596	The address of the flow template: [[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]]
197.1	597
198.2	598	(% style="color:red" %)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.
197.1	599
	600	[[image:image-20230307135914-1.png\|\|height="527" width="1045"]]
	601
198.2	602
197.1	603	[[image:image-20230307135932-2.png\|\|height="527" width="1044"]]
	604
202.2	605
202.1	606	3. Display the map
	607	Enter the link to the map:
198.2	608
202.1	609	Change its suffix to ditu：http:~/~/119.91.62.30:1880/ditu/
	610
	611	~ [[image:image-20230308115430-1.png\|\|height="548" width="1041"]]
202.2	612
	613
202.1	614	Hit all input in input stream
	615
	616	[[image:image-20230308115616-2.png\|\|height="563" width="1070"]]
202.2	617
	618
202.1	619	View map again
	620
	621	[[image:image-20230308115701-3.png\|\|height="571" width="1085"]]
	622
	623
197.1	624	== 2.8 Datalog Feature ==
	625
	626
78.1	627	total 273 entries,by default,
56.1	628
164.2	629	User can set [[PNACKMD=1>>\|\|anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
68.4	630
71.1	631	Example use case.
68.4	632
146.1	633	[[image:image-20221009234703-2.png\|\|_mstalt="429143" height="328" width="899"]]
71.1	634
	635
146.1	636	[[image:image-20221009234629-1.png\|\|_mstalt="431145" height="390" width="577"]]
71.1	637
	638
197.1	639	== 2.9 Alarm Mode ==
19.2	640
	641
51.27	642	(((
205.1	643	User can push the (% style="color:red" %)RED button(%%) by more than 5 seconds to enter Alarm Mode. Alarm Mode is used to send SOS info to IoT platform.
51.27	644	)))
19.2	645
51.27	646	(((
81.1	647	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	648	)))
19.2	649
	650
51.27	651	(((
143.2	652	Two ways to exit alarm mode:
51.27	653	)))
19.2	654
81.1	655	* Server sends a downlink command to exit.
19.2	656	* User fast press the RED button 10 times.
	657
51.27	658	(((
51.11	659	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	660	)))
19.2	661
	662
197.1	663	== 2.10 Transport Mode ==
19.2	664
	665
204.1	666	In Transport Mode, TrackerD will check if there is motion (threldhold defined by [[PT)>>\|\|anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]] . If there is no motion, device will send uplinks every 20 minutes (Defined by [[TDC)>>\|\|anchor="H3.2.1SetTransmitInterval"]] . If there is motion, device will send uplink every 5 minutes(defined by [[MTDC)>>\|\|anchor="H3.2.3SetTransportModePackettransmissioninterval"]].
19.2	667
205.1	668	When device is set in Transport Mode, it will uplink more frequenctly during moving.
	669
151.1	670	* [[MTDC>>\|\|anchor="H3.2.3SetTransportModePackettransmissioninterval"]] defines the Uplink Interval during transportation.
	671	* [[TDC>>\|\|anchor="H3.2.1SetTransmitInterval"]] defines the uplink interval when TrackerD is stactic.
153.1	672	* [[PT>>\|\|anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]] defines the threldhold to detect a motion.
55.1	673
191.2	674	(% style="display:none" %) (%%)
186.3	675
197.1	676	== 2.11 LED Status ==
19.2	677
	678
216.6	679	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %)
	680	\|=(% style="width: 150px;background-color:#4F81BD;color:white" %)Event\|=(% style="width: 200px;background-color:#4F81BD;color:white" %)Action\|=(% style="width: 150px;background-color:#4F81BD;color:white" %)AT+LON to control on/off
51.11	681	\|(% 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
	682	\|(% style="width:157px" %)Join request\|(% style="width:271px" %)(% style="color:green" %)Green (%%)led fast blink once (200ms)\|(% style="width:202px" %)Yes
	683	\|(% style="width:157px" %)Join Success\|(% style="width:271px" %)(% style="color:green" %)Green(%%) led on 5 second\|(% style="width:202px" %)N/A
	684	\|(% style="width:157px" %)Fixing Location\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)blinks 200ms per second\|(% style="width:202px" %)Yes
113.7	685	\|(% style="width:157px" %)Fixed and uplink\|(% style="width:271px" %)(% style="color:green" %)GREEN (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
51.11	686	\|(% style="width:157px" %)Fail Fix and uplink\|(% style="width:271px" %)(% style="color:red" %)RED (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	687	\|(% style="width:157px" %)Enter Alarm mode\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 3 seconds\|(% style="width:202px" %)Yes
	688	\|(% style="width:157px" %)Uplink under Alarm\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 1 second\|(% style="width:202px" %)Yes
	689	\|(% style="width:157px" %)Exit Alarm\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)led on 5 second\|(% style="width:202px" %)Yes
	690	\|(% style="width:157px" %)Get Downlink\|(% style="width:271px" %)(% style="color:green" %)GREEN(%%) led on 1 second\|(% style="width:202px" %)Yes
	691	\|(% style="width:157px" %)Movement Detect\|(% style="width:271px" %)(% style="color:red" %)RED (%%)led on 500ms\|(% style="width:202px" %)N/A
19.2	692
191.2	693	(% style="display:none" %) (%%)
186.3	694
197.1	695	== 2.12 Button Function ==
19.2	696
50.2	697
51.27	698	(% style="color:blue" %)RESET button:
19.2	699
146.1	700	[[image:1664502835802-546.png\|\|_mstalt="295061"]]
19.2	701
	702	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
	703
	704
51.11	705	(% style="color:red" %)RED button:
19.2	706
191.2	707	[[image:image-20230213110506-3.png]](% style="display:none" %)
19.2	708
191.2	709	(% style="display:none" %) (%%)
19.2	710
216.6	711	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
	712	\|=(% style="width: 100px;background-color:#4F81BD;color:white" %)Function\|=(% style="width: 205px;background-color:#4F81BD;color:white" %)Action\|=(% style="width: 205px;background-color:#4F81BD;color:white" %)Description
113.6	713	\|(% 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	714	\|(% 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	715	\|(% 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	716
191.2	717	(% style="display:none" %) (%%)
186.3	718
197.1	719	== 2.13 USB Port Function ==
19.2	720
50.2	721
19.2	722	The USB interface of TrackerD has below functions:
	723
	724	* Power on the device
	725	* Recharge the battery
51.11	726	* [[Configure Device>>\|\|anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
	727	* [[Upgrade Firmware>>\|\|anchor="H5.UploadFirmware"]]
19.2	728
191.2	729	(% style="display:none" %) (%%)
186.3	730
202.3	731	== 2.14 Sleep Mode ==
	732
	733
	734	(% style="color:blue" %)Sleep Mode:(%%) To prevent accidental touch of the red button during transportation or assembly, so the peripherals of the device are turned off and enter deep sleep.
	735
	736	In SLEEP mode, you need to reset by (% style="color:#037691" %)reset button.
	737
	738	Use the (% style="color:#4472c4" %)AT+SLEEP(%%) command to put the device into sleep.
	739
	740
19.3	741	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
19.2	742
	743
	744	User can configure TrackerD via AT Command or LoRaWAN Downlink.
	745
51.13	746	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
19.2	747
	748
19.3	749	== 3.1 Access AT Command ==
19.2	750
	751
50.2	752	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	753
146.1	754	[[image:1664502999401-486.png\|\|_mstalt="296985"]]
50.2	755
	756
51.11	757	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	758
	759
146.1	760	[[image:1664503022490-662.png\|\|_mstalt="293332"]]
19.2	761
	762
146.1	763	[[image:1664503035713-500.png\|\|_mstalt="291096"]]
19.2	764
	765
146.1	766	[[image:1664503047675-651.png\|\|_mstalt="295386"]]
50.2	767
191.2	768	(% style="display:none" %) (%%)
50.2	769
19.3	770	== 3.2 Command Set ==
19.2	771
19.3	772	=== 3.2.1 Set Transmit Interval ===
19.2	773
50.2	774
19.2	775	Set device uplink interval.
	776
51.13	777	* (% style="color:blue" %)AT Command:
19.2	778
51.13	779	(% style="color:#037691" %)AT+TDC=xxx
19.2	780
50.2	781	Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
19.2	782
	783
51.13	784	* (% style="color:blue" %)Downlink Payload (prefix 0x01):
19.2	785
51.13	786	(% style="color:#037691" %)0x01 00 01 2C (%%) ~/~/ Same as AT+TDC=300000
19.2	787
	788
19.3	789	=== 3.2.2 Set Alarm Packet transmission interval ===
19.2	790
50.2	791
19.2	792	Set alarm packet transmit interval
	793
51.13	794	* (% style="color:blue" %)AT Command:
19.2	795
51.13	796	(% style="color:#037691" %)AT+ATDC=xx.
19.2	797
51.2	798	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	799
	800
51.13	801	* (% style="color:blue" %)Downlink Payload (prefix 0xB1):
19.2	802
51.13	803	(% style="color:#037691" %)0xB1 00 00 3C (%%) ~/~/ Same as AT+ATDC=60000
19.2	804
	805
57.1	806	=== 3.2.3 Set Transport Mode Packet transmission interval ===
50.2	807
	808
57.1	809	Set Transport Mode packet transmit interval
19.2	810
51.13	811	* (% style="color:blue" %)AT Command:
19.2	812
51.13	813	(% style="color:#037691" %)AT+MTDC=xx.
19.2	814
57.1	815	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	816
	817
51.13	818	* (% style="color:blue" %)Downlink Payload (prefix 0x03):
19.2	819
111.1	820	(% style="color:#037691" %)0x03 00 01 2C (%%) ~/~/ Same as AT+MTDC=3000000
19.2	821
	822
50.2	823	=== 3.2.4 Exit Alarm ===
19.2	824
50.2	825
19.2	826	Server send downlink command to exit Alarm mode
	827
51.13	828	* (% style="color:blue" %)AT Command: No AT Command
19.2	829
51.13	830	* (% style="color:blue" %)Downlink Payload (prefix 0x02):
19.2	831
51.13	832	(% style="color:#037691" %)0x02 01 (%%) ~/~/ Exit Alarm Mode
19.2	833
51.13	834
188.1	835	=== 3.2.5 Disable/Enable LED flash and buzzer ===
50.2	836
	837
19.2	838	Disable/Enable LED for position, downlink and uplink
	839
51.13	840	* (% style="color:blue" %)AT Command:
19.2	841
51.13	842	(% style="color:#037691" %)AT+LON=xx. (Disable (0), Enable (1), default:1)
19.2	843
51.28	844	Example: AT+LON=0 ~-~-> Disable LED for position, downlink and uplink.
19.2	845
	846
51.13	847	* (% style="color:blue" %)Downlink Payload (prefix 0xAE):
19.2	848
51.13	849	(% style="color:#037691" %)0xAE 00 (%%) ~/~/ Same as AT+LON=0
19.2	850
	851
59.1	852	=== 3.2.6 Disable/Enable Transport Mode ===
19.2	853
	854
59.1	855	Users can use this feature to enable/disable Transport Mode.
19.2	856
51.13	857	* (% style="color:blue" %)AT Command:
19.2	858
51.13	859	(% style="color:#037691" %)AT+INTWK=xx. (Disable (0), Enable (1), default:0)
19.2	860
111.1	861	Example: AT+INTWK=1 ~-~-> Enable Transport Mode.
19.2	862
	863
51.13	864	* (% style="color:blue" %)Downlink Payload (prefix 0xAF):
19.2	865
111.1	866	(% style="color:#037691" %)0xAF 01 (%%) ~/~/ Same as AT+INTWK=1
19.2	867
	868
50.2	869	=== 3.2.7 Set Positioning Mode ===
19.2	870
50.2	871
79.1	872	SMOD define how TrackerD scan and uplink data:
19.2	873
51.13	874	* (% style="color:blue" %)AT Command:
19.2	875
74.5	876	(% style="color:#037691" %)AT+SMOD=aa,bb,cc
19.2	877
60.2	878	(% style="color:#037691" %) aa:
19.2	879
87.1	880	* (% style="color:red" %)1: GPS ONLY(Factory Settings): (%%)Only get and uplink GPS location info.
113.3	881
88.1	882	* (% 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	883
113.4	884	* (% 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	885
	886	(% style="color:#037691" %)bb:
	887
74.5	888	* (% style="color:red" %)0 : (%%)GPS+ BAT+ State+Tem&Hum
113.2	889
74.5	890	* (% style="color:red" %)1 :(%%) GPS +BAT State
60.2	891
74.5	892	(% style="color:#037691" %)cc:
60.2	893
147.1	894	* (% _mstmutation="1" style="color:red" %)1 : (%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
113.2	895
146.1	896	* (% _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	897
74.5	898	(% style="color:blue" %)Example:
19.2	899
111.1	900	AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum
113.2	901
111.1	902	AT+SMOD=1,1,0 ~-~-> GPS +BAT State
113.2	903
111.1	904	AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
113.2	905
111.1	906	AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State
19.2	907
214.1	908	AT+SMOD=2,0,3 ~-~-> (iBeacon) (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State
19.2	909
51.13	910	* (% style="color:blue" %)Downlink Payload (prefix 0xA5):
19.2	911
111.1	912	(% style="color:#037691" %)0xA5 01 00 00 (%%) ~/~/ Same as AT+SMOD=1,0,0
19.2	913
	914
50.2	915	=== 3.2.8 Set MAX GPS position time ===
	916
	917
19.2	918	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.
	919
143.2	920	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	921
51.13	922	* (% style="color:blue" %)AT Command:
19.2	923
51.13	924	(% style="color:#037691" %)AT+FTIME=xx (%%) ~-~-> Set to use xx as max fix time.
19.2	925
74.5	926	Example: AT+FTIME=150
19.2	927
	928
51.13	929	* (% style="color:blue" %)Downlink Payload (prefix 0xAA):
19.2	930
51.13	931	(% style="color:#037691" %)0xAA 00 96 (%%) ~/~/ Set AT+FTIME=150
19.2	932
	933
68.4	934	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
19.2	935
	936
50.2	937	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	938
	939	A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
	940
51.13	941	* (% style="color:blue" %)AT Command:
19.2	942
51.13	943	(% style="color:#037691" %)AT+PDOP=2.5 (%%) ~-~-> Set PDOP to 2.5
19.2	944
	945
51.13	946	* (% style="color:blue" %)Downlink Payload (prefix 0xAD):
19.2	947
51.13	948	(% style="color:#037691" %)0xAD 00 0A (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1)
19.2	949
51.13	950	(% style="color:#037691" %)0xAD 00 19 (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5)
19.2	951
51.13	952	(% style="color:#037691" %)0xAD 00 46 (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7)
19.2	953
50.2	954
155.3	955	=== 3.2.10 Disable/Enable the confirmation mode ===
19.2	956
155.4	957
51.13	958	* (% style="color:blue" %)AT Command:
19.2	959
74.6	960	(% style="color:#037691" %)AT+CFM=xx
19.2	961
	962
212.2	963	Example:
19.2	964
212.2	965	AT+CFM=0 ~-~-> Disable confirmation
19.2	966
212.2	967	AT+CFM=1 ~-~-> Enable confirmation
19.2	968
50.2	969
51.13	970	* (% style="color:blue" %)Downlink Payload (prefix 0x05):
19.2	971
111.1	972	(% style="color:#037691" %)0x05 01 (%%) ~/~/ Same as AT+CFM=1
19.2	973
	974
148.1	975	=== 3.2.11 Auto Send None-ACK messages ===
74.6	976
	977
	978	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.
	979
	980
	981	* (% style="color:blue" %)AT Command: AT+PNACKMD
	982
	983	The default factory setting is 0.
	984
	985
	986	Command Example Function Response:
	987
	988	(% style="color:#037691" %)AT+PNACKMD=1 (%%) ~/~/ Poll None-ACK message OK
	989
	990
	991	* (% style="color:blue" %)Downlink Command: 0x34
	992
148.1	993	Example: 0x34 01 ~/~/ Same as AT+PNACKMD=1
74.6	994
	995
148.1	996	=== 3.2.12 Set BLEMASK to filter BLE iBeacon ===
80.1	997
84.2	998
86.1	999	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	1000
84.5	1001	(% style="color:red" %)Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.
80.1	1002
84.5	1003	(% style="color:blue" %)AT Command:
80.1	1004
212.2	1005	(% _mstmutation="1" style="color:#037691" %)AT+BLEMASK=123456 (%%) ~/~/ Set BLEMASK = 123456
80.1	1006
212.2	1007	(% _mstmutation="1" style="color:#037691" %)AT+BLEMASK=0 (%%) ~/~/ disable BLEMASK
80.1	1008
216.4	1009	(% style="color:blue" %)Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)
84.5	1010
148.1	1011	Example: 0xB2 01 02 03 04 05 06 ~/~/ Set BLEMASK to 123456
100.1	1012
105.2	1013
216.3	1014	=== 3.2.13 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===
84.5	1015
86.1	1016
108.1	1017	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	1018
	1019	(% style="color:red" %)Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.
	1020
	1021	(% style="color:blue" %)AT Command:
	1022
212.2	1023	(% _mstmutation="1" style="color:#037691" %)AT+WiFiMASK=123456 (%%) ~/~/ Set WiFiMASK = 123456
86.1	1024
212.2	1025	(% _mstmutation="1" style="color:#037691" %)AT+WiFiMASK=0 (%%) ~/~/ disable WiFiMASK
86.1	1026
216.4	1027	(% style="color:blue" %)Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)
86.1	1028
148.1	1029	Example: 0xB3 01 02 03 04 05 06 ~/~/ Set WiFiMASK to 123456
100.1	1030
105.2	1031
216.3	1032	=== 3.2.14 Disable/Enable Information printing(Since firmware 1.4.1) ===
98.1	1033
	1034
	1035	Users can use this feature to enable/disable Information printing.
	1036
	1037	(% style="color:blue" %)AT Command:
	1038
164.3	1039	(% style="color:#037691" %)AT+SHOWID=XX (%%) ~/~/ (Disable (0), Enable (1), default:0)
111.1	1040	\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
98.1	1041
	1042
216.3	1043	=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===
104.1	1044
105.2	1045
104.1	1046	The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
	1047
	1048	(% style="color:blue" %)AT Command:
	1049
173.1	1050	(% style="color:#037691" %)AT+CHE=1 (%%) ~/~/ set one channels mode
104.1	1051
113.2	1052
113.4	1053	(% style="color:blue" %)Downlink Payload:0X24
113.2	1054
164.3	1055	Example: 0x24 01 ~/~/ Same as AT+CHE=1
104.1	1056
	1057
216.3	1058	=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) ===
152.1	1059
164.3	1060
152.1	1061	User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
	1062
	1063	(% style="color:blue" %)AT Command:
	1064
	1065	(% style="color:#037691" %)AT+PT=xx
	1066
212.2	1067	Example:
152.1	1068
212.2	1069	AT+PT=14 ~-~-> Set to detect car motion.
152.1	1070
212.2	1071	AT+PT=41 ~-~-> set to detect walk motion.
152.1	1072
	1073
209.48	1074	(% style="color:blue" %)Downlink Payload:0xB4
209.44	1075
152.1	1076	0xB4 14 ~/~/ Same as AT+PT=14
	1077
	1078
216.3	1079	=== 3.2.17 Set AT command window time(Since firmware 1.4.5) ===
206.1	1080
209.43	1081
206.1	1082	AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
	1083
	1084	(% style="color:blue" %)AT Command:
	1085
	1086	(% style="color:#037691" %)AT+ATST=XX
	1087
212.2	1088	Example:
206.1	1089
212.2	1090	AT+ATST=15 ~-~-> Set the time to 15 seconds
206.1	1091
209.48	1092	(% style="color:blue" %)Downlink Payload:0XB5
209.43	1093
206.1	1094	0xB5 0F ~/~/ Same as AT+ATST=15
	1095
209.45	1096
216.3	1097	=== 3.2.18 Set the stepmeter mode(Since firmware 1.4.5) ===
206.1	1098
209.43	1099
206.1	1100	After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
	1101
	1102	(% style="color:blue" %)AT Command:
	1103
	1104	(% style="color:#037691" %)AT+PM=xx
	1105
212.2	1106	Example:
206.1	1107
212.2	1108	AT+PM=1 ~-~-> Turn on step counting mode
206.1	1109
	1110	AT+PM=0 ~-~-> Turn OFF step counting mode
	1111
209.48	1112	(% style="color:blue" %)Downlink Payload:0XB6
209.43	1113
207.1	1114	0xB6 01 ~/~/ Same as AT+PM=1
206.1	1115
	1116
216.3	1117	=== 3.2.19 Set down the decline detection mode(Since firmware 1.4.5) ===
206.1	1118
209.43	1119
206.1	1120	This mode is used in conjunction with AT+PT(The recommended threshold is between 50 and 70, you need to set it according to the environment yourself). This function is used in hospitals, nursing homes, nursing homes and other places to prevent the elderly and patients from falling. No one knows.
	1121
	1122	(% style="color:blue" %)AT Command:
	1123
	1124	(% style="color:#037691" %)AT+FD=xx
	1125
210.6	1126	Example:
206.1	1127
210.6	1128	AT+FD=1 ~-~-> Turn on the Fall detection
206.1	1129
	1130	AT+FD=0 ~-~-> Turn OFF the Fall detection
	1131
209.48	1132	(% style="color:blue" %)Downlink Payload:0XB7
209.43	1133
209.1	1134	0xB7 01 ~/~/ Same as AT+FD=1
206.1	1135
	1136
216.3	1137	=== 3.2.20 Disable/Enable buzzer(Since firmware 1.4.6) ===
210.1	1138
	1139
	1140	Disable/Enable buzzer for Alarm, downlink and uplink
	1141
	1142	(% style="color:blue" %)AT Command:
	1143
	1144	(% style="color:#037691" %)AT+BEEP=XX
	1145
212.2	1146	Example:
210.1	1147
	1148	AT+BEEP=1 ~-~-> Turn on the buzzer
	1149
	1150	AT+BEEP=0 ~-~-> Turn OFF the buzzer
	1151
	1152	(% style="color:blue" %)Downlink Payload:0XB9
	1153
	1154	0xB9 01 ~/~/ Same as AT+BEEP=1
	1155
	1156
219.1	1157	=== (% data-sider-select-id="358d0797-d8c7-4a5d-b51f-fd0c537f26e4" %)3.2.21 Set long press time(Since firmware 1.4.6)(%%) ===
210.1	1158
	1159
	1160	When using the red button Changan to alarm, press and hold the time to set 0~~10 seconds, which is convenient for use scenarios.
	1161
219.1	1162	(% data-sider-select-id="5e6cc597-e839-4a16-9d6b-776f523bcb8c" style="color:blue" %)AT Command:
210.1	1163
	1164	(% style="color:#037691" %)AT+EAT=XX
	1165
212.2	1166	Example:
210.1	1167
	1168	AT+EAT=2 ~-~-> Set the long press time to 2s
	1169
	1170	(% style="color:blue" %)Downlink Payload:0XBA
	1171
	1172	0xBA 02 ~/~/ Same as AT+EAT=2
	1173
	1174
219.1	1175	(% data-sider-select-id="8e1bc417-f7f8-49f0-b796-8460ff412d7c" %)
	1176	=== 3.2.22 Conversion of TrackerD and TrackerD-LS ===
19.2	1177
219.3	1178
219.1	1179	They use the same source code and can be converted using the AT command below
19.2	1180
219.1	1181	(% data-sider-select-id="5e6cc597-e839-4a16-9d6b-776f523bcb8c" style="color:blue" %)AT Command:
19.2	1182
219.1	1183	(% data-sider-select-id="d1642275-40f9-4a61-876f-c50aa2a2c492" style="color:#037691" %)AT+DEVICE=22
	1184
	1185	Example:
	1186
	1187	(% data-sider-select-id="80b524e6-34b5-469c-b05f-c144bee41d20" %)
	1188	AT+DEVICE=22 ~-~-> Set to TrackerD-LS
	1189
	1190	(% data-sider-select-id="d7427d7e-0c50-4af5-a666-fd59d105d39f" %)
	1191	AT+DEVICE=13 ~-~-> Set to TrackerD
	1192
	1193
	1194	= (% data-sider-select-id="45c47ab9-03ef-4224-9771-e53c0d98eb40" %)4. Setting for Different Scenarios(%%) =
	1195
	1196
	1197
19.4	1198	= 5. Upload Firmware =
19.2	1199
19.4	1200	== 5.1 Firmware Change Log ==
	1201
50.2	1202
19.2	1203	[[See this link>>url:https://github.com/dragino/TrackerD]]
	1204
	1205
19.4	1206	== 5.2 How to upgrade firmware ==
19.2	1207
	1208
50.2	1209	User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
19.2	1210
	1211
50.2	1212	(% style="color:blue" %)Step1: (%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
19.2	1213
50.2	1214
	1215	(% style="color:blue" %)Step2: (%%) Install CH9102 driver in the PC.
	1216
19.2	1217	After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
	1218
	1219
221.1	1220	(% style="color:blue" %)Step3: (%%)Download and Install Flash Tool: [[Tools ~\| Espressif Systems>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=]]
19.2	1221
	1222
50.2	1223	(% style="color:blue" %)Step4: (%%) Run Flash Download Tool and configure chip type to ESP32
19.2	1224
	1225
146.1	1226	[[image:1664503563660-578.png\|\|_mstalt="296777"]]
19.2	1227
	1228
146.1	1229	[[image:1664503574618-659.png\|\|_mstalt="297986"]]
19.2	1230
50.2	1231
84.2	1232
50.2	1233	(% style="color:blue" %)Step5: (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
	1234
73.1	1235	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
19.2	1236
	1237
143.2	1238	Users need to use below files:
19.2	1239
	1240	boot_app0.bin @0e000
	1241
131.1	1242	US915.bin @ 0x10000(Select the bin file of the frequency band you need)
19.2	1243
	1244
173.1	1245	[[image:image-20221207120501-1.png]]
19.2	1246
	1247
	1248
50.2	1249	After upgrade finish, it will show finish as below:
19.2	1250
173.1	1251	[[image:image-20221207133911-7.png]]
19.2	1252
	1253
19.4	1254	= 6. Developer Guide =
19.2	1255
19.4	1256	== 6.1 Compile Source Code ==
	1257
	1258	=== 6.1.1 Set up ARDUINO compile environment ===
	1259
	1260
51.28	1261	* 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	1262
51.15	1263	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	1264
	1265
146.1	1266	[[image:1664503635019-941.png\|\|_mstalt="294658"]]
19.2	1267
50.2	1268
68.4	1269
51.28	1270	* (% style="color:#037691" %)Go to tools ~-~-> Boards ~-~-> Boards Manager,(%%) find the esp32 information and install it.
19.2	1271
146.1	1272	[[image:1664503715811-892.png\|\|_mstalt="295698"]]
19.2	1273
	1274
186.3	1275	=== 6.1.2 Build the development environment ===
181.1	1276
	1277
186.2	1278	~1. Download and install arduino IDE
	1279
181.1	1280	[[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]]
	1281
	1282
186.2	1283	2. Download the ESP32 development package in the arduino IDE
181.1	1284
	1285	[[image:image-20221213100007-1.png]]
	1286
186.2	1287
181.1	1288	Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
	1289
	1290	[[image:image-20221213100626-2.png]]
	1291
186.2	1292
181.1	1293	Restart the IDE after the addition is complete, then:
	1294
	1295	[[image:image-20221213100808-3.png\|\|height="679" width="649"]]
	1296
186.2	1297
181.1	1298	[[image:image-20221213101040-4.png]]
	1299
186.2	1300
	1301	(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
181.1	1302	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)**
	1303
192.2	1304
181.1	1305	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:
	1306
186.2	1307	(% style="color:blue" %)Methods as below:
	1308
182.1	1309	~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
181.1	1310
	1311	2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
	1312
84.3	1313	(% 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	1314
181.1	1315	[[image:image-20221213102311-5.png\|\|height="582" width="711"]]
	1316
186.2	1317
186.3	1318	3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)
181.1	1319
	1320	[[image:image-20221213102334-6.png]]
	1321
186.2	1322	(% style="color:red" %)Note: This step requires a python environment
181.1	1323
186.2	1324
181.1	1325	Either way, in the end:
186.2	1326
181.1	1327	The final effect is to open the arduino and you can see the esp32
	1328
184.1	1329	[[image:image-20221213110952-8.png\|\|height="866" width="711"]]
181.1	1330
	1331
	1332
146.1	1333	[[image:image-20221024105643-1.png\|\|_mstalt="428129"]]
84.3	1334
84.4	1335	~ Figure1
84.3	1336
	1337
181.1	1338
146.1	1339	[[image:image-20221024105643-2.png\|\|_mstalt="428493"]]
84.3	1340
84.4	1341	Figure2
84.3	1342
	1343
51.28	1344	* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
19.2	1345
50.2	1346	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
19.2	1347
	1348
146.1	1349	[[image:1664503752288-974.png\|\|_mstalt="298194"]]
19.2	1350
50.2	1351
19.4	1352	== 6.2 Source Code ==
	1353
	1354
51.16	1355	* (% style="color:blue" %)Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
19.2	1356
146.1	1357	[[image:1664503794261-827.png\|\|_mstalt="296387"]]
19.2	1358
	1359
	1360
51.16	1361	* (% style="color:blue" %)Click to upload
19.2	1362
146.1	1363	[[image:1664503808294-336.png\|\|_mstalt="295711"]]
19.2	1364
	1365
	1366
51.16	1367	* (% style="color:blue" %)Check the result, if the upload is successful, as shown below, open the serial port to view the data
19.2	1368
146.1	1369	[[image:1664503824081-592.png\|\|_mstalt="294918"]] [[image:1664503831430-500.png\|\|_mstalt="290784"]]
19.2	1370
	1371
18.2	1372	= 7. FAQ =
15.2	1373
18.2	1374	== 7.1 How to change the LoRa Frequency Bands/Region? ==
14.1	1375
	1376
51.14	1377	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	1378
12.1	1379
18.2	1380	== 7.2 What is the pin mapping for the USB program cable? ==
2.1	1381
7.1	1382
146.1	1383	[[image:1664499635206-262.png\|\|_mstalt="295360"]]
7.1	1384
	1385
216.7	1386	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:314px" %)
	1387	\|=(% style="width: 120px;background-color:#4F81BD;color:white" %)Pin\|=(% style="width: 69px;background-color:#4F81BD;color:white" %)Color\|=(% style="width: 125px;background-color:#4F81BD;color:white" %)USB Pin
18.2	1388	\|(% style="width:118px" %)A4,B4,A9,B9\|(% style="width:67px" %)Red\|(% style="width:123px" %)VCC
	1389	\|(% style="width:118px" %)A7,B7\|(% style="width:67px" %)White\|(% style="width:123px" %)D- (N/A)
	1390	\|(% style="width:118px" %)A6,B6\|(% style="width:67px" %)Green\|(% style="width:123px" %)D+(N/A)
	1391	\|(% style="width:118px" %)A1,B1,A12,B12\|(% style="width:67px" %)Black\|(% style="width:123px" %)GND
	1392	\|(% style="width:118px" %)A5\|(% style="width:67px" %)Purple\|(% style="width:123px" %)MTDC/GOIO13
	1393	\|(% style="width:118px" %)B5\|(% style="width:67px" %)Blue\|(% style="width:123px" %)MTDC/GPIO12
	1394	\|(% style="width:118px" %)A8\|(% style="width:67px" %)Yellow\|(% style="width:123px" %)MTMS/GPIO14
	1395	\|(% style="width:118px" %)B8\|(% style="width:67px" %)Grey\|(% style="width:123px" %)MTDO/GPIO15
7.1	1396
191.2	1397	(% style="display:none" %) (%%)
186.2	1398
188.2	1399
97.1	1400	== 7.3 Notes on using different serial port tools for TrackerD ==
	1401
113.4	1402	=== 7.3.1 Serial port utility ===
97.1	1403
	1404
	1405	Serial port utility requires you to automatically add data streams.
	1406
	1407	Need to adjust the data stream to RTS/CTS on physical restart.
	1408
	1409	(% class="wikigeneratedid" %)
146.1	1410	[[image:image-20221102140621-1.png\|\|_mstalt="425672"]]
97.1	1411
	1412
	1413	When using AT commands, the data flow needs to be adjusted to XON/XOFF
	1414
146.1	1415	[[image:image-20221102140638-2.png\|\|_mstalt="428727"]]
97.1	1416
	1417
113.4	1418	=== 7.3.2 SecureCRT ===
97.1	1419
	1420
	1421	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.
	1422
	1423
146.1	1424	[[image:image-20221102140704-3.png\|\|_mstalt="427076"]]
97.1	1425
	1426
146.1	1427	[[image:image-20221102140712-4.png\|\|_mstalt="427089"]]
97.1	1428
	1429
113.4	1430	=== 7.3.3 PUTTY ===
97.1	1431
	1432
146.1	1433	[[image:image-20221102140748-5.png\|\|_mstalt="430456"]]
97.1	1434
	1435
	1436	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.
	1437
	1438
146.1	1439	[[image:image-20221102140801-6.png\|\|_mstalt="427466"]]
97.1	1440
98.2	1441
123.1	1442	== 7.4 How to modify source code to compile different frequency band bin file? ==
113.4	1443
133.1	1444
	1445	(% class="box infomessage" %)
	1446	(((
135.1	1447	(% style="color:red" %)Important(%%): Developer MUST follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
134.1	1448	See : [[Set Up Arduino Compile Environment for TrackerD. >>\|\|anchor="H6.1.1SetupARDUINOcompileenvironment"]]
133.1	1449	)))
	1450
143.2	1451	~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
122.1	1452
143.2	1453
146.1	1454	[[image:image-20221116111844-1.png\|\|_mstalt="428688" height="227" width="782"]]
122.1	1455
	1456
143.2	1457
	1458	2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
	1459
	1460
146.1	1461	[[image:image-20221116111844-2.png\|\|_mstalt="429052" height="262" width="781"]]
122.1	1462
	1463
143.2	1464
	1465	3. Compile the AS923_JP band, please refer to the intention shown
	1466
	1467
146.1	1468	[[image:image-20221116111844-3.png\|\|_mstalt="429416" height="338" width="746"]]
122.1	1469
	1470
143.2	1471
	1472	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.
	1473
	1474
146.1	1475	[[image:image-20221116111844-4.png\|\|_mstalt="429780" height="641" width="739"]]
122.1	1476
143.2	1477
146.1	1478	[[image:image-20221116111844-5.png\|\|_mstalt="430144" height="551" width="708"]]
122.1	1479
	1480
187.1	1481	== 7.5 Are there example python example for BLE Indoor Positioning? ==
	1482
	1483
187.3	1484	[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
187.1	1485
187.2	1486
203.1	1487	== 7.6 Can alert mode and transport mode be used together? ==
	1488
	1489
	1490	Yes, you can also press the panic button to sound the alarm if set to transport mode
	1491
	1492
218.1	1493	== 7.7 Can i get the datalog record from console? ==
	1494
	1495	Since firmware TrackerD-v1.4.9, User is able to get the datalog record from console as well.
	1496
	1497	[[image:image-20240329120308-1.png\|\|height="537" width="525"]]
	1498
	1499
226.1	1500	== 7.8 FAQs for upgrading to version 1.4.9 or later ==
225.1	1501
	1502	1.The device does not display version information or indicates low battery
	1503
	1504	Please set the device type
	1505
	1506	(% style="color:red" %)**AT+DEVICE=13~-~->TrackerD
	1507	AT+DEVICE=22->TrackerD-LS**
	1508
	1509
	1510	2.Unable to control the red button on trackerD
	1511
227.1	1512	Please set any 8-digit DADDR less than 01880788.
225.1	1513
227.1	1514	(% style="color:red" %)Example:
225.1	1515
227.1	1516	(% style="color:red" %)AT+DADDR=01880688
225.1	1517
	1518
110.1	1519	= 8 Trouble Shooting =
98.2	1520
113.4	1521	== 8.1 TDC is changed to 4294947296 and cause no uplink. ==
	1522
	1523
	1524	(((
155.4	1525	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	1526	)))
105.1	1527
105.2	1528
113.4	1529	== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode ==
	1530
	1531
	1532	(((
110.1	1533	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	1534	)))
7.1	1535
	1536
136.1	1537	== 8.3 Problem after Upgrading Firmware ==
113.4	1538
155.3	1539	=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
113.4	1540
136.1	1541
155.4	1542	Error Output
	1543
	1544
154.1	1545	[[image:image-20221122100004-4.png\|\|_mstalt="424606"]]
	1546
155.4	1547
113.4	1548	(((
154.1	1549	Some partition is missed during upgrade, please upgrade below four files as example:
	1550
173.1	1551	[[image:image-20221207120524-2.png]]
113.4	1552	)))
113.1	1553
113.4	1554
155.3	1555	=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
113.1	1556
	1557
136.1	1558	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	1559
	1560
155.3	1561	=== 8.3.3 "flash read err" after upgrade firmware ===
143.2	1562
155.4	1563
144.1	1564	Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
142.1	1565
146.1	1566	[[image:image-20221122100004-1.png\|\|_mstalt="423514" height="497" width="534"]]
142.1	1567
	1568
144.1	1569	User need to upgrade again with below four files to solve this issue.
143.2	1570
173.1	1571	[[image:image-20221207120530-3.png]]
142.1	1572
143.2	1573	Figure 2
142.1	1574
143.2	1575
155.4	1576	=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
143.2	1577
155.4	1578
144.1	1579	User might erase the entire flash include keys and default settings which cause this issue.
	1580
209.40	1581	After the upgrade is completed, enter (% style="color:blue" %)AT+CFG(%%) as shown in the figure below.
142.1	1582
155.4	1583
146.1	1584	[[image:image-20221122100004-3.png\|\|_mstalt="424242"]]
142.1	1585
	1586
155.4	1587	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.
	1588
147.1	1589	After AT+FDR. please set
142.1	1590
155.4	1591	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=7
155.3	1592
155.4	1593	* (% _mstmutation="1" style="color:blue" %)AT+FTIME=180000
147.1	1594
155.4	1595	Example:
144.1	1596
146.1	1597	AT+PDOP=7.00
	1598
	1599	AT+FTIME=180
	1600
144.1	1601	AT+DEUI=70B3D57ED0053981
	1602
142.1	1603	AT+APPEUI=D23345667BCBCCAF
	1604
	1605	AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
	1606
144.1	1607	AT+DADDR=260b4dce ( no need for OTAA)
142.1	1608
144.1	1609	AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d ( no need for OTAA)
142.1	1610
144.1	1611	AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)
142.1	1612
	1613
143.2	1614	== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
142.1	1615
143.2	1616
142.1	1617	Please download version 1.4.2 again
	1618
	1619
143.2	1620	== 8.5 How to deal with unsuccessful GPS positioning? ==
116.1	1621
143.2	1622
	1623	1） Make Sure the device is in Open Area where can see the sky.
	1624
116.1	1625	2) Set PDOP to a higher value.
	1626
148.1	1627	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=2 (%%)(can be positioned precisely.）
132.1	1628
148.1	1629	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=7 (%%)(Quickly locate in open spaces）
132.1	1630
148.1	1631	* (% _mstmutation="1" style="color:blue" %)AT+PDOP=14.7 (%%)(Positioning can be acquired in complex environments）
132.1	1632
116.1	1633	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
	1634
	1635
163.1	1636	== 8.6 When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
	1637
164.3	1638
163.1	1639	When upgrading, use the erase button to upgrade
	1640
173.1	1641	[[image:image-20221207120536-4.png]]
163.1	1642
	1643
	1644	The parameters are displayed abnormally and cannot be fixed using AT+FDR
	1645
	1646	[[image:image-20221128103040-2.png\|\|height="431" width="525"]]
	1647
164.3	1648
163.1	1649	Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
	1650
173.1	1651	[[image:image-20221207134028-8.png]]
163.1	1652
164.3	1653
163.1	1654	Reboot information after upgrade
	1655
	1656	[[image:image-20221128111443-4.png\|\|height="432" width="546"]]
	1657
164.3	1658
209.39	1659	Use (% style="color:blue" %)AT+FDR(%%) command to reset and then use (% style="color:blue" %)AT+CFG(%%) to check whether the configuration is back to normal
163.1	1660
	1661	[[image:image-20221128111850-5.png]]
	1662
164.3	1663
163.1	1664	After the parameters return to normal, upgrade to the version you need again
	1665
173.1	1666	[[image:image-20221207120601-5.png]]
163.1	1667
164.3	1668
164.1	1669	At this point, the parameters return to normal after running AT+FDR again
163.1	1670
	1671	[[image:image-20221128112035-7.png]]
	1672
	1673
186.2	1674	== 8.7 If you encounter the following problems, please upgrade to the latest version ==
185.1	1675
186.2	1676
186.1	1677	~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
185.1	1678
186.2	1679	2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
185.1	1680
	1681
211.1	1682	== 8.8 Why when using some serial consoles, only inputting the first string port console will return "error"? ==
	1683
	1684
212.2	1685	Need to enter the entire command at once, not a single character.
	1686	User can open a command window or copy the entire command to the serial console.
	1687
	1688
222.1	1689	== 8.9 When the device is connected to the serial port, it cannot send Uplink, the light color is abnormal, and it does not respond to commands. ==
	1690
	1691	ESP32 hardware is affected by the flow control of the serial port control program, which causes abnormal phenomena.
	1692	Please do not select flow control when using the serial port tool.
	1693	Please refer to this link to use the serial port tool
	1694
	1695	[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H7.3NotesonusingdifferentserialporttoolsforTrackerD>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H7.3NotesonusingdifferentserialporttoolsforTrackerD]]
	1696
	1697
	1698
110.1	1699	= 9. Order Info =
	1700
	1701
15.6	1702	Part Number: (% style="color:blue" %)TrackerD-XXX
8.1	1703
15.6	1704	(% style="color:blue" %)XXX(%%): The default frequency band
8.1	1705
15.6	1706	* (% style="color:red" %)EU433(%%): Default frequency band EU433
143.2	1707
15.6	1708	* (% style="color:red" %)EU868(%%): Default frequency band EU868
143.2	1709
15.6	1710	* (% style="color:red" %)IN865(%%): Default frequency band IN865
143.2	1711
15.6	1712	* (% style="color:red" %)KR920(%%): Default frequency band KR920
143.2	1713
15.6	1714	* (% style="color:red" %)AS923(%%): Default frequency band AS923
143.2	1715
15.6	1716	* (% style="color:red" %)AU915(%%): Default frequency band AU915
143.2	1717
15.6	1718	* (% style="color:red" %)US915(%%): Default frequency band US915
15.2	1719
191.2	1720	(% style="display:none" %) (%%)
186.2	1721
210.6	1722
110.1	1723	= 10. Packing Info =
18.2	1724
	1725
51.30	1726	(% style="color:#037691" %)Package Includes:
8.1	1727
50.3	1728	* TrackerD LoRaWAN GPS/BLE Tracker x 1
143.2	1729
50.3	1730	* USB recharge & program cable x 1
12.1	1731
51.30	1732	(% style="color:#037691" %)Dimensions and Weight:
12.1	1733
98.2	1734	* Device Size: 85 x 48 x 15 mm
143.2	1735
50.3	1736	* Weight: 50g
15.6	1737
191.2	1738	(% style="display:none" %) (%%)
186.2	1739
210.6	1740
110.1	1741	= 11. Support =
18.2	1742
50.3	1743
18.2	1744	* 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	1745
51.28	1746	* 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	1747
209.56	1748	(% style="display:none" %)
209.50	1749
209.51	1750
210.6	1751
110.1	1752	= 12. Reference =
18.2	1753
	1754
12.1	1755	* [[Firmware in Bin format>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
143.2	1756
12.1	1757	* [[Source Code>>https://github.com/dragino/TrackerD]]
143.2	1758
12.1	1759	* [[Hardware Source>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
188.2	1760
	1761
155.4	1762	)))

Wiki source code of TrackerD -- LoRaWAN Tracker User Manual

Applications

Navigation