Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 209.42 by Xiaoling on 2023/05/23 09:45

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications