Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 209.53 by Xiaoling on 2023/05/23 10:12

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications