Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 113.8 by Xiaoling on 2022/11/09 17:05

version	line-number	content
51.2	1	(% style="text-align:center" %)
	2	[[image:1664505654417-133.png]]
	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
15.2	15	= 1. Introduction =
	16
	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	)))
51.18	35	)))
8.1	36
15.3	37	(((
	38	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.
16.4	39
	40
15.3	41	)))
8.1	42
19.2	43	[[image:1664499921684-770.png]]
8.1	44
15.4	45
19.2	46	(% style="color:red" %)Note: LoRaWAN server can be a general LoRaWAN server other than TTN.
8.1	47
15.2	48
50.2	49
19.2	50	== 1.2 Specifications ==
12.1	51
15.2	52
19.2	53	(% style="color:blue" %)Micro Controller:
15.2	54
19.2	55	* Espressif ESP32 PICO D4
	56	* MCU: ESP32 PICO D4
	57	* Bluetooth: Bluetooth V4.2 BR/EDR and Bluetooth LE
	58	* WiFi : 802.11 b/g/n (802.11n up to 150 Mbps)
	59	* Integrated SPI flash : 4 MB
	60	* RAM: 448 KB
	61	* EEPROM: 520 KB
	62	* Clock Speed: 32Mhz
	63
	64	(% style="color:blue" %)Common DC Characteristics:
	65
	66	* Supply Voltage: 5V via USB port or Internal li-on battery
	67	* Operating Temperature: -40 ~~ 60°C
	68
	69	(% style="color:blue" %)LoRa Spec:
	70
	71	* Frequency Range,
	72	** Band 1 (HF): 862 ~~ 1020 Mhz
	73	* 168 dB maximum link budget.
	74	* +20 dBm - 100 mW constant RF output vs.
	75	* +14 dBm high efficiency PA.
	76	* Programmable bit rate up to 300 kbps.
	77	* High sensitivity: down to -148 dBm.
	78	* Bullet-proof front end: IIP3 = -12.5 dBm.
	79	* Excellent blocking immunity.
	80	* Low RX current of 10.3 mA, 200 nA register retention.
	81	* Fully integrated synthesizer with a resolution of 61 Hz.
	82	* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
	83	* Built-in bit synchronizer for clock recovery.
	84	* Preamble detection.
	85	* 127 dB Dynamic Range RSSI.
	86	* Automatic RF Sense and CAD with ultra-fast AFC.
	87	* Packet engine up to 256 bytes with CRC.
	88	* LoRaWAN 1.0.3 Specification
	89
	90	(% style="color:blue" %)Battery:
	91
	92	* 1000mA Li-on Battery power (for model TrackerD)
	93
	94	(% style="color:blue" %)Power Consumption
	95
	96	* Sleeping Mode: 200uA
	97	* LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
	98	* Tracking: max: 38mA
	99
113.8	100
	101
19.2	102	== 1.3 Features ==
	103
	104
	105	* LoRaWAN 1.0.3 Class A
	106	* ESP32 PICO D4
	107	* SX1276/78 Wireless Chip
51.31	108	* Arduino IDE Compatible
19.2	109	* Open source hardware / software
	110	* Regular/ Real-time GPS,BLE,WIFI tracking
	111	* Built-in3 axis accelerometer (LIS3DH)
	112	* Humidity / temperature sensor : GXCAS Technology GXHT3X
	113	* Motion sensing capability
	114	* Power Monitoring
	115	* Charging circuit via USB port
	116	* 1000mA Li-on Battery power
	117	* Tri-color LED, Alarm button
	118	* Datalog
	119
113.8	120
	121
19.2	122	== 1.4 Applications ==
	123
	124
12.1	125	* Logistics and Supply Chain Management
	126	* Human tracking
	127
113.8	128
	129
105.2	130	= 2. Use TrackerD =
	131
	132
19.3	133	== 2.1 How it works? ==
19.2	134
19.3	135
19.2	136	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.
	137
	138
50.2	139
19.3	140	== 2.2 Quick guide to connect to LoRaWAN server ==
19.2	141
	142
50.2	143	Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example.
19.2	144
	145
50.2	146	[[image:1664501652064-326.png]]
19.2	147
50.2	148
	149
19.2	150	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:
	151
	152
50.2	153	(% style="color:blue" %)Step 1:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD.
	154
19.2	155	Each TrackerD is shipped with a sticker with the default device EUI as below:
	156
51.3	157
50.2	158	[[image:1664501677253-891.png]]
19.2	159
	160
	161	Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
	162
	163
50.2	164	__Add APP EUI in the application:__
19.2	165
	166
50.2	167	[[image:1664501711466-918.png]]
19.2	168
	169
	170
50.2	171	[[image:1664501721248-725.png]]
19.2	172
	173
50.2	174	[[image:1664501734705-405.png]]
19.2	175
	176
	177
50.2	178	__Add APP KEY and DEV EUI:__
19.2	179
	180
113.5	181	[[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\|\|alt="1654671889112-678.png"]]
19.2	182
	183
	184
50.2	185	(% style="color:blue" %)Step 2:(%%) Power on TrackerD by using the on board switch.
19.2	186
50.2	187
	188	(% 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.
	189
	190
68.4	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
19.2	204
66.3	205	== 2.4 Uplink Payload ==
19.2	206
	207
66.3	208	=== 2.4.1 Uplink FPORT~=5, Device Status ===
66.2	209
66.3	210
74.1	211	Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.
19.2	212
76.1	213	Use can also get the Device Status uplink through the downlink command: Downlink: 0x2301
19.2	214
76.1	215
84.8	216	(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
84.9	217	\|=(% style="width: 60px;" %)Size(bytes)\|=(% style="width: 70px;" %)1\|=(% style="width: 70px;" %)2\|=(% style="width: 70px;" %)1\|=(% style="width: 50px;" %)1\|=(% style="width: 30px;" %)2\|=(% style="width: 40px;" %)2\|=(% style="width: 40px;" %)1
66.2	218	\|=(% 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	219
66.2	220	[[image:1665301570342-765.png]]
	221
	222
74.2	223	(% style="color:#037691" %)Example of Device Status:(%%) 13014001FF0FA24002
19.2	224
74.2	225	(% style="color:#037691" %)Sensor Model: (%%) For TrackerD,this value is 0x13
19.2	226
74.2	227	(% style="color:#037691" %)Firmware Version: (%%) 0x0140,Means:v1.4.0 version
50.2	228
74.2	229	(% style="color:#037691" %)Frequency Band:
55.1	230
	231	*0x01: EU868
	232
	233	*0x02: US915
	234
	235	*0x03: IN865
	236
	237	*0x04: AU915
	238
	239	*0x05: KZ865
	240
	241	*0x06: RU864
	242
	243	*0x07: AS923
	244
	245	*0x08: AS923-1
	246
	247	*0x09: AS923-2
	248
	249	*0x0a: AS923-3
	250
74.2	251	Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
55.1	252
74.2	253	(% style="color:#037691" %)BAT:(%%) shows the battery voltage for TrackerD.
55.1	254
	255
74.2	256	(% style="color:#037691" %)Ex1:(%%) 0x0FA2 = 4002mV
	257
55.1	258	Use can also get the Device Status uplink through the downlink command:
	259
	260
75.1	261	(% style="color:#037691" %)SMOD Field (total 1 byte)(%%)：0x40
74.2	262
84.11	263	(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
84.10	264	\|=(% scope="row" style="width: 60px;" %)Size(bit)\|(% style="width:50px" %)2bits\|(% style="width:80px" %)2bit\|(% style="width:80px" %)4bit
84.9	265	\|=(% style="width: 75px;" %)Value\|(% style="width:64px" %)SMOD\|(% style="width:104px" %)GPS_Settings\|(% style="width:103px" %)BLE_Settings
74.2	266
75.1	267	(% style="color:blue" %) SMOD：
74.2	268
75.1	269	(% style="color:red" %) 1 : (%%) GPS ONLY
74.2	270
75.1	271	(% style="color:red" %) 2 : (%%) BLE ONLY
74.2	272
75.1	273	(% style="color:red" %) 3 : (%%) GPS/BLE Hybrid
74.2	274
	275
75.1	276	(% style="color:blue" %) GPS_MOD: Define how to send GPS payload
74.2	277
75.1	278	(% style="color:red" %) 0 : (%%) Enable uploading on-board Temperature and humidity values
74.2	279
75.1	280	(% style="color:red" %) 1 : (%%) Disable uploading on-board Temperature and humidity values
74.2	281
	282
75.1	283	(% style="color:blue" %) BLE_Settings:
74.2	284
75.1	285	(% style="color:red" %) 1: (%%) BLE Positioning with Strongest iBeacon
74.2	286
90.1	287	(% style="color:red" %) 2： (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)
74.2	288
88.1	289
75.1	290	(% style="color:#037691" %)Status Field (total 1 byte)(%%): 0x02
74.2	291
84.11	292	(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
	293	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:50px" %)5 Bits\|(% style="width:60px" %)1 Bit\|(% style="width:20px" %)1 Bit\|(% style="width:80px" %)1 Bit
84.9	294	\|=(% style="width: 77px;" %)Value\|(% style="width:70px" %)Reserve\|(% style="width:92px" %)[[PNACKMD>>\|\|anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]\|(% style="width:48px" %)[[LON>>\|\|anchor="H3.2.5Disable2FEnableLEDflash"]]\|(% style="width:126px" %)[[Transport Mode>>\|\|anchor="H2.9TransportMode"]]
74.2	295
113.8	296
	297
66.3	298	=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
55.1	299
	300
77.1	301	Users can use AT+SMOD=1,0,0 to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
55.1	302
	303
84.13	304	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
	305	\|=(% scope="row" style="width: 60px;" %)(((
84.19	306	Size(bytes)
	307	)))\|(% style="width:50px" %)4\|(% style="width:50px" %)4\|(% style="width:70px" %)2\|(% style="width:30px" %)1\|(% style="width:30px" %)(((
	308	2
	309	)))\|(% style="width:30px" %)(((
	310	2
	311	)))
51.18	312	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
51.5	313	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
59.2	314	)))\|(% style="width:73px" %)[[FLAG>>\|\|anchor="HFLAG:"]]\|(% style="width:40px" %)[[Hum>>\|\|anchor="HHum:"]]\|(% style="width:87px" %)[[Tem>>\|\|anchor="HTem:"]]
19.2	315
66.2	316	[[image:1665301636888-168.png]]
19.2	317
50.2	318
51.24	319	==== (% style="color:blue" %)Alarm & BAT:(%%) ====
19.2	320
51.24	321	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
	322	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:50px" %)1 bit\|(% style="width:80px" %)1bit\|(% style="width:50px" %)14bits
51.22	323	\|=(% style="width: 72px;" %)Value\|(% style="width:67px" %)reserve\|(% style="width:118px" %)Alarm Indicate\|(% style="width:63px" %)[[BAT>>\|\|anchor="HBAT:"]]
19.2	324
113.8	325
	326
51.24	327	==== (% style="color:blue" %)FLAG:(%%) ====
	328
84.12	329	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
	330	\|=(% scope="row" style="width: 50px;" %)Size(bit)\|(% style="width:30px" %)2bits\|(% style="width:30px" %)1bit
59.3	331	\|=(% style="width: 79px;" %)Value\|(% style="width:55px" %)[[MOD>>\|\|anchor="H3.2.7SetPositioningMode"]]\|(% style="width:47px" %)[[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
50.2	348	[[image:1664502116362-706.png]]
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
	353	[[image:1664502166010-515.png]]
	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
113.8	376
	377
74.3	378	==== (% style="color:blue" %)MOD:(%%) ====
	379
79.1	380	Example: (0x60>>6) & 0x3f =1
74.10	381
74.7	382	Set the format of GPS data uplink link：
74.3	383
74.7	384	(% style="color:#037691" %)0x00: (%%) Enable uploading on-board Temperature and humidity values
74.9	385	(% style="color:#037691" %)0x01: (%%) Disable uploading on-board Temperature and humidity values
74.3	386
	387
74.7	388	Set the format of BLE data uplink link：
74.3	389
74.7	390	(% style="color:#037691" %)0x01: (%%) BLE Positioning with Strongest iBeacon
	391
	392
74.10	393	==== (% style="color:blue" %)LON:(%%) ====
74.9	394
74.10	395	Example: (0x60>>5) & 0x01=1.
74.9	396
51.4	397	Enable/Disable LED activity for uplink
19.2	398
51.27	399	(((
74.7	400	(% style="color:#037691" %)0x00: (%%) Disable LED indicator.
51.27	401	)))
19.2	402
51.27	403	(((
74.7	404	(% style="color:#037691" %)0x01: (%%) Enable LED indicator (Default Value)
51.27	405	)))
19.2	406
	407
51.24	408	==== (% style="color:blue" %)Hum:(%%) ====
19.2	409
51.4	410	0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
19.2	411
	412
51.24	413	==== (% style="color:blue" %)Tem:(%%) ====
19.2	414
51.9	415	011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
51.4	416
	417
66.2	418
66.3	419	=== 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
51.4	420
66.2	421
78.1	422	The default uplink payload includes total 11 bytes (AT+SMOD=1,1,0). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
19.2	423
	424
84.14	425	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
84.19	426	\|=(% scope="row" style="width: 60px;" %)(((
	427	Size(bytes)
	428	)))\|(% style="width:60px" %)4\|(% style="width:60px" %)4\|(% style="width:60px" %)2\|(% style="width:50px" %)1
59.2	429	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)[[Latitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:87px" %)[[Longitude>>\|\|anchor="HLocationinfo:"]]\|(% style="width:76px" %)(((
	430	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
	431	)))\|(% style="width:73px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
50.2	432
66.2	433	(% class="wikigeneratedid" %)
	434	[[image:1665301687277-443.png]]
	435
	436
	437
66.3	438	=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning ===
59.2	439
66.2	440
78.2	441	Set [[PNACKMD=1>>\|\|anchor="H3.2.10A0A0AutoSendNone-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	442
66.2	443
66.3	444	(% style="color:red" %)Note for this mode:
59.2	445
59.3	446	* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
103.1	447	* 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	448	* 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	449
59.3	450	The payload is 15 bytes, as below.
50.2	451
84.15	452	(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
66.2	453	\|=(% scope="row" %)(((
	454	Size(bytes)
	455	)))\|4\|4\|2\|1\|1\|1\|1\|1
66.3	456	\|=Value\|Latitude\|Longitude\|Year\|Month\|Day\|Hous\|Min\|Sen
59.3	457
68.2	458	[[image:image-20221009160309-2.png]]
59.3	459
66.2	460
	461
66.3	462	=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
59.3	463
84.2	464
81.1	465	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	466
82.1	467	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	468
81.1	469
51.25	470	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
51.26	471	\|=(% scope="row" style="width: 60px;" %)(((
51.24	472	Size(bytes)
51.26	473	)))\|(% style="width:30px" %)16\|(% style="width:50px" %)4\|(% style="width:50px" %)4\|(% style="width:120px" %)2\|(% style="width:50px" %)4\|(% style="width:50px" %)2\|(% style="width:30px" %)1
51.24	474	\|=(% style="width: 50px;" %)Value\|(% style="width:44px" %)[[UUID>>\|\|anchor="HLocationinfo:"]]\|(% style="width:61px" %)(((
51.8	475	iBeacon MAJOR
51.11	476	)))\|(% style="width:63px" %)(((
	477	iBeacon MINOR
50.2	478	)))\|(% style="width:71px" %)(((
51.8	479	iBeacon Measured Power
51.11	480	)))\|(% style="width:50px" %)(((
51.8	481	iBeacon RSSI
51.11	482	)))\|(% style="width:47px" %)(((
51.8	483	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
51.11	484	)))\|(% style="width:15px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	485
50.2	486	[[image:1664502425687-834.png]]
19.2	487
	488
79.1	489	* (% style="color:#037691" %)BAT: (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
51.9	490	* (% style="color:#037691" %)MODE: (%%)Define the payload format.
	491	* (% style="color:#037691" %)UUID: (%%)The uuid from the strongest iBeacon.
	492	* (% style="color:#037691" %)MAJOR: (%%) The MAJOR from the strongest iBeacon.
	493	* (% style="color:#037691" %)MINOR: (%%)The MAJOR from the strongest iBeacon.
	494	* (% style="color:#037691" %)Measured Power: (%%) The Measured Power from the strongest iBeacon.
	495	* (% style="color:#037691" %)RSSI: (%%) The RSSI from the strongest iBeacon.
19.2	496
113.8	497
	498
106.1	499	=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
105.2	500
84.19	501
109.1	502	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	503
50.2	504
86.1	505	(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
	506	\|=(% scope="row" style="width: 60px;" %)(((
	507	Size(bytes)
	508	)))\|(% style="width:60px" %)6\|(% style="width:60px" %)4\|(% style="width:79px" %)2\|(% style="width:66px" %)1
	509	\|=(% style="width: 69px;" %)Value\|(% style="width:76px" %)SSID\|(% style="width:87px" %)RSSI\|(% style="width:79px" %)(((
	510	[[Alarm & BAT>>\|\|anchor="HAlarm26BAT:"]]
	511	)))\|(% style="width:66px" %)[[FLAG>>\|\|anchor="HFLAG:"]]
19.2	512
86.1	513	(% class="wikigeneratedid" %)
	514	[[image:1667288597595-714.png\|\|height="212" width="1151"]]
	515
	516
	517	* (% style="color:#037691" %)BAT: (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
	518	* (% style="color:#037691" %)SSID: (%%)WiFi name.
	519	* (% style="color:#037691" %)RSSI: (%%)The RSSI from the strongest WiFi.
	520
113.8	521
	522
86.1	523	=== 2.4.7 Add Payload format in TTN V3 ===
	524
	525
	526	In TTN V3, user can add a custom payload so it shows friendly.
	527
51.9	528	In the page (% style="color:#037691" %)Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder
19.2	529
	530
50.2	531	[[image:1664502649601-895.png]]
	532
51.9	533
78.7	534	Add the decoder from this link:
19.2	535
78.7	536	[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
19.2	537
	538	Save the change the uplink message will be parsed. As below:
	539
50.2	540	[[image:1664502676891-606.png]]
19.2	541
	542
	543
66.3	544	== 2.5 Integrate with Datacake ==
19.2	545
84.5	546
19.2	547	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.
	548
50.2	549	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	550
113.4	551
50.2	552	[[image:1664502695771-538.png]]
19.2	553
50.2	554
	555
66.3	556	== 2.6 Integrate with Tago ==
19.2	557
	558
81.1	559	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.
	560
19.2	561	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]]
	562
	563
50.2	564	[[image:1664502715371-321.png]]
19.2	565
	566
	567
68.4	568	== 2.7 Datalog Feature ==
56.1	569
68.4	570
78.1	571	total 273 entries,by default,
56.1	572
78.4	573	User can set [[PNACKMD=1>>\|\|anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
68.4	574
71.1	575	Example use case.
68.4	576
72.1	577	[[image:image-20221009234703-2.png\|\|height="328" width="899"]]
71.1	578
	579
72.1	580	[[image:image-20221009234629-1.png\|\|height="390" width="577"]]
71.1	581
	582
	583
66.3	584	== 2.8 Alarm Mode ==
19.2	585
	586
51.27	587	(((
51.11	588	User can push the (% style="color:red" %)RED button(%%) by more than 5 seconds to enter Alarm Mode.
51.27	589	)))
19.2	590
	591
51.27	592	(((
81.1	593	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	594	)))
19.2	595
	596
51.27	597	(((
19.2	598	Two ways to exit alarm mode:
51.27	599	)))
19.2	600
81.1	601	* Server sends a downlink command to exit.
19.2	602	* User fast press the RED button 10 times.
	603
51.27	604	(((
51.11	605	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	606	)))
19.2	607
	608
50.2	609
66.3	610	== 2.9 Transport Mode ==
19.2	611
	612
57.1	613	In Transport Mode, TrackerD will check if there is motion. If there is no motion, device will send uplinks every 20 minutes. If there is motion, device will send uplink every 5 minutes.
19.2	614
55.1	615
68.4	616
66.3	617	== 2.10 LED Status ==
19.2	618
	619
113.7	620	(% border="1.5" style="background-color:#ffffcc; width:500px" %)
51.27	621	\|=(% style="width: 150px;" %)Event\|=(% style="width: 200px;" %)Action\|=(% style="width: 150px;" %)AT+LON to control on/off
51.11	622	\|(% 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
	623	\|(% style="width:157px" %)Join request\|(% style="width:271px" %)(% style="color:green" %)Green (%%)led fast blink once (200ms)\|(% style="width:202px" %)Yes
	624	\|(% style="width:157px" %)Join Success\|(% style="width:271px" %)(% style="color:green" %)Green(%%) led on 5 second\|(% style="width:202px" %)N/A
	625	\|(% style="width:157px" %)Fixing Location\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)blinks 200ms per second\|(% style="width:202px" %)Yes
113.7	626	\|(% style="width:157px" %)Fixed and uplink\|(% style="width:271px" %)(% style="color:green" %)GREEN (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
51.11	627	\|(% style="width:157px" %)Fail Fix and uplink\|(% style="width:271px" %)(% style="color:red" %)RED (%%)blinks twice (200ms per blink)\|(% style="width:202px" %)Yes
	628	\|(% style="width:157px" %)Enter Alarm mode\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 3 seconds\|(% style="width:202px" %)Yes
	629	\|(% style="width:157px" %)Uplink under Alarm\|(% style="width:271px" %)(% style="color:red" %)RED (%%)on for 1 second\|(% style="width:202px" %)Yes
	630	\|(% style="width:157px" %)Exit Alarm\|(% style="width:271px" %)(% style="color:blue" %)BLUE (%%)led on 5 second\|(% style="width:202px" %)Yes
	631	\|(% style="width:157px" %)Get Downlink\|(% style="width:271px" %)(% style="color:green" %)GREEN(%%) led on 1 second\|(% style="width:202px" %)Yes
	632	\|(% style="width:157px" %)Movement Detect\|(% style="width:271px" %)(% style="color:red" %)RED (%%)led on 500ms\|(% style="width:202px" %)N/A
19.2	633
113.8	634
	635
66.3	636	== 2.11 Button Function ==
19.2	637
50.2	638
51.27	639	(% style="color:blue" %)RESET button:
19.2	640
50.2	641	[[image:1664502835802-546.png]]
19.2	642
	643	Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
	644
	645
51.11	646	(% style="color:red" %)RED button:
19.2	647
50.2	648	[[image:1664502854406-763.png]]
19.2	649
	650
113.7	651	(% border="1" style="background-color:#ffffcc; width:510px" %)
84.18	652	\|=(% style="width: 100px;" %)Function\|=(% style="width: 205px;" %)Action\|=(% style="width: 205px;" %)Description
113.6	653	\|(% 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	654	\|(% 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	655	\|(% 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	656
113.2	657
113.7	658
66.3	659	== 2.12 USB Port Function ==
19.2	660
50.2	661
19.2	662	The USB interface of TrackerD has below functions:
	663
	664	* Power on the device
	665	* Recharge the battery
51.11	666	* [[Configure Device>>\|\|anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
	667	* [[Upgrade Firmware>>\|\|anchor="H5.UploadFirmware"]]
19.2	668
113.8	669
	670
19.3	671	= 3. Configure TrackerD via AT command or LoRaWAN downlink =
19.2	672
	673
	674	User can configure TrackerD via AT Command or LoRaWAN Downlink.
	675
51.13	676	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
19.2	677
	678
50.2	679
19.3	680	== 3.1 Access AT Command ==
19.2	681
	682
50.2	683	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	684
	685
50.2	686	[[image:1664502999401-486.png]]
	687
	688
51.11	689	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	690
	691
50.2	692	[[image:1664503022490-662.png]]
19.2	693
	694
50.2	695	[[image:1664503035713-500.png]]
19.2	696
	697
50.2	698	[[image:1664503047675-651.png]]
	699
	700
	701
19.3	702	== 3.2 Command Set ==
19.2	703
	704
19.3	705	=== 3.2.1 Set Transmit Interval ===
19.2	706
50.2	707
19.2	708	Set device uplink interval.
	709
51.13	710	* (% style="color:blue" %)AT Command:
19.2	711
51.13	712	(% style="color:#037691" %)AT+TDC=xxx
19.2	713
50.2	714	Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds)
19.2	715
	716
51.13	717	* (% style="color:blue" %)Downlink Payload (prefix 0x01):
19.2	718
51.13	719	(% style="color:#037691" %)0x01 00 01 2C (%%) ~/~/ Same as AT+TDC=300000
19.2	720
	721
50.2	722
19.3	723	=== 3.2.2 Set Alarm Packet transmission interval ===
19.2	724
50.2	725
19.2	726	Set alarm packet transmit interval
	727
51.13	728	* (% style="color:blue" %)AT Command:
19.2	729
51.13	730	(% style="color:#037691" %)AT+ATDC=xx.
19.2	731
51.2	732	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	733
	734
51.13	735	* (% style="color:blue" %)Downlink Payload (prefix 0xB1):
19.2	736
51.13	737	(% style="color:#037691" %)0xB1 00 00 3C (%%) ~/~/ Same as AT+ATDC=60000
19.2	738
	739
	740
57.1	741	=== 3.2.3 Set Transport Mode Packet transmission interval ===
50.2	742
	743
57.1	744	Set Transport Mode packet transmit interval
19.2	745
51.13	746	* (% style="color:blue" %)AT Command:
19.2	747
51.13	748	(% style="color:#037691" %)AT+MTDC=xx.
19.2	749
57.1	750	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	751
	752
51.13	753	* (% style="color:blue" %)Downlink Payload (prefix 0x03):
19.2	754
111.1	755	(% style="color:#037691" %)0x03 00 01 2C (%%) ~/~/ Same as AT+MTDC=3000000
19.2	756
	757
	758
50.2	759	=== 3.2.4 Exit Alarm ===
19.2	760
50.2	761
19.2	762	Server send downlink command to exit Alarm mode
	763
51.13	764	* (% style="color:blue" %)AT Command: No AT Command
19.2	765
51.13	766	* (% style="color:blue" %)Downlink Payload (prefix 0x02):
19.2	767
51.13	768	(% style="color:#037691" %)0x02 01 (%%) ~/~/ Exit Alarm Mode
19.2	769
51.13	770
	771
50.2	772	=== 3.2.5 Disable/Enable LED flash ===
	773
	774
19.2	775	Disable/Enable LED for position, downlink and uplink
	776
51.13	777	* (% style="color:blue" %)AT Command:
19.2	778
51.13	779	(% style="color:#037691" %)AT+LON=xx. (Disable (0), Enable (1), default:1)
19.2	780
51.28	781	Example: AT+LON=0 ~-~-> Disable LED for position, downlink and uplink.
19.2	782
	783
51.13	784	* (% style="color:blue" %)Downlink Payload (prefix 0xAE):
19.2	785
51.13	786	(% style="color:#037691" %)0xAE 00 (%%) ~/~/ Same as AT+LON=0
19.2	787
	788
	789
59.1	790	=== 3.2.6 Disable/Enable Transport Mode ===
19.2	791
	792
59.1	793	Users can use this feature to enable/disable Transport Mode.
19.2	794
51.13	795	* (% style="color:blue" %)AT Command:
19.2	796
51.13	797	(% style="color:#037691" %)AT+INTWK=xx. (Disable (0), Enable (1), default:0)
19.2	798
111.1	799	Example: AT+INTWK=1 ~-~-> Enable Transport Mode.
19.2	800
	801
51.13	802	* (% style="color:blue" %)Downlink Payload (prefix 0xAF):
19.2	803
111.1	804	(% style="color:#037691" %)0xAF 01 (%%) ~/~/ Same as AT+INTWK=1
19.2	805
	806
	807
50.2	808	=== 3.2.7 Set Positioning Mode ===
19.2	809
50.2	810
79.1	811	SMOD define how TrackerD scan and uplink data:
19.2	812
	813
51.13	814	* (% style="color:blue" %)AT Command:
19.2	815
74.5	816	(% style="color:#037691" %)AT+SMOD=aa,bb,cc
19.2	817
60.2	818	(% style="color:#037691" %) aa:
19.2	819
87.1	820	* (% style="color:red" %)1: GPS ONLY(Factory Settings): (%%)Only get and uplink GPS location info.
113.3	821
88.1	822	* (% 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	823
113.4	824	* (% 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	825
	826	(% style="color:#037691" %)bb:
	827
74.5	828	* (% style="color:red" %)0 : (%%)GPS+ BAT+ State+Tem&Hum
113.2	829
74.5	830	* (% style="color:red" %)1 :(%%) GPS +BAT State
60.2	831
74.5	832	(% style="color:#037691" %)cc:
60.2	833
113.2	834	* (% style="color:red" %)1 : (%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
	835
86.1	836	* (% style="color:red" %)2 : (%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))
60.2	837
74.5	838	(% style="color:blue" %)Example:
19.2	839
111.1	840	AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum
113.2	841
111.1	842	AT+SMOD=1,1,0 ~-~-> GPS +BAT State
113.2	843
111.1	844	AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
113.2	845
111.1	846	AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State
19.2	847
	848
51.13	849	* (% style="color:blue" %)Downlink Payload (prefix 0xA5):
19.2	850
111.1	851	(% style="color:#037691" %)0xA5 01 00 00 (%%) ~/~/ Same as AT+SMOD=1,0,0
19.2	852
	853
	854
50.2	855	=== 3.2.8 Set MAX GPS position time ===
	856
	857
19.2	858	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.
	859
	860
	861	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.
	862
	863
51.13	864	* (% style="color:blue" %)AT Command:
19.2	865
51.13	866	(% style="color:#037691" %)AT+FTIME=xx (%%) ~-~-> Set to use xx as max fix time.
19.2	867
74.5	868	Example: AT+FTIME=150
19.2	869
	870
51.13	871	* (% style="color:blue" %)Downlink Payload (prefix 0xAA):
19.2	872
51.13	873	(% style="color:#037691" %)0xAA 00 96 (%%) ~/~/ Set AT+FTIME=150
19.2	874
	875
	876
68.4	877	=== 3.2.9 Set PDOP value for GPS fix accuracy ===
19.2	878
	879
50.2	880	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	881
50.2	882
19.2	883	A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0
	884
	885
51.13	886	* (% style="color:blue" %)AT Command:
19.2	887
51.13	888	(% style="color:#037691" %)AT+PDOP=2.5 (%%) ~-~-> Set PDOP to 2.5
19.2	889
	890
51.13	891	* (% style="color:blue" %)Downlink Payload (prefix 0xAD):
19.2	892
51.13	893	(% style="color:#037691" %)0xAD 00 0A (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1)
19.2	894
51.13	895	(% style="color:#037691" %)0xAD 00 19 (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5)
19.2	896
51.13	897	(% style="color:#037691" %)0xAD 00 46 (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7)
19.2	898
50.2	899
51.12	900
19.2	901	Disable/Enable the confirmation mode
	902
51.13	903	* (% style="color:blue" %)AT Command:
19.2	904
74.6	905	(% style="color:#037691" %)AT+CFM=xx
19.2	906
	907
50.2	908	~ Example:
19.2	909
107.1	910	AT+CFM=0 ~-~-> Disable confirmation
19.2	911
107.1	912	AT+CFM=1 ~-~-> Enable confirmation
19.2	913
50.2	914
51.13	915	* (% style="color:blue" %)Downlink Payload (prefix 0x05):
19.2	916
111.1	917	(% style="color:#037691" %)0x05 01 (%%) ~/~/ Same as AT+CFM=1
19.2	918
	919
	920
74.6	921	=== 3.2.10 Auto Send None-ACK messages ===
	922
	923
	924	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.
	925
	926
	927	* (% style="color:blue" %)AT Command: AT+PNACKMD
	928
	929	The default factory setting is 0.
	930
	931
	932	Command Example Function Response:
	933
	934	(% style="color:#037691" %)AT+PNACKMD=1 (%%) ~/~/ Poll None-ACK message OK
	935
	936
	937	* (% style="color:blue" %)Downlink Command: 0x34
	938
	939	Example: 0x3401 ~/~/ Same as AT+PNACKMD=1
	940
	941
84.2	942
80.1	943	=== 3.2.11 Set BLEMASK to filter BLE iBeacon ===
	944
84.2	945
86.1	946	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	947
84.5	948	(% style="color:red" %)Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.
80.1	949
84.5	950	(% style="color:blue" %)AT Command:
80.1	951
84.5	952	(% style="color:#037691" %)AT+BLEMASK=123456 (%%) ~/~/ Set BLEMASK = 123456
80.1	953
84.5	954	(% style="color:#037691" %)AT+BLEMASK=0 (%%) ~/~/ disable BLEMASK
80.1	955
100.1	956	(% style="color:blue" %)Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）
84.5	957
100.1	958	Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456
	959
105.2	960
	961
106.1	962	=== 3.2.12 Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
84.5	963
86.1	964
108.1	965	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	966
	967	(% style="color:red" %)Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.
	968
	969	(% style="color:blue" %)AT Command:
	970
111.1	971	(% style="color:#037691" %)AT+WiFiMASK=123456 (%%) ~/~/ Set WiFiMASK = 123456
86.1	972
111.1	973	(% style="color:#037691" %)AT+WiFiMASK=0 (%%) ~/~/ disable WiFiMASK
86.1	974
100.1	975	(% style="color:blue" %)Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）
86.1	976
100.1	977	Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456
	978
105.2	979
	980
99.1	981	=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
98.1	982
	983
	984	Users can use this feature to enable/disable Information printing.
	985
	986	(% style="color:blue" %)AT Command:
	987
106.1	988	(% style="color:#037691" %)AT+SHOWID=XX (%%) ~/~/(Disable (0), Enable (1), default:0)
111.1	989	\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
98.1	990
	991
105.2	992
104.1	993	=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
	994
105.2	995
104.1	996	The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
	997
	998	(% style="color:blue" %)AT Command:
	999
113.2	1000	(% style="color:#037691" %)AT+CHE=1(%%) ~/~/ set one channels mode
104.1	1001
113.2	1002
113.4	1003	(% style="color:blue" %)Downlink Payload:0X24
113.2	1004
111.1	1005	Example: 0x24 01 ~/~/ Same as AT+CHE=1
104.1	1006
	1007
105.2	1008
19.4	1009	= 4. Setting for Different Scenarios =
19.2	1010
	1011
	1012
19.4	1013	= 5. Upload Firmware =
19.2	1014
19.4	1015
	1016	== 5.1 Firmware Change Log ==
	1017
50.2	1018
19.2	1019	[[See this link>>url:https://github.com/dragino/TrackerD]]
	1020
	1021
50.2	1022
19.4	1023	== 5.2 How to upgrade firmware ==
19.2	1024
	1025
50.2	1026	User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below:
19.2	1027
	1028
50.2	1029	(% style="color:blue" %)Step1: (%%)Connect TrackerD and PC via USB cable shipped with TrackerD.
19.2	1030
50.2	1031
	1032	(% style="color:blue" %)Step2: (%%) Install CH9102 driver in the PC.
	1033
19.2	1034	After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager.
	1035
	1036
51.28	1037	(% 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	1038
	1039
50.2	1040	(% style="color:blue" %)Step4: (%%) Run Flash Download Tool and configure chip type to ESP32
19.2	1041
	1042
50.2	1043	[[image:1664503563660-578.png]]
19.2	1044
	1045
50.2	1046	[[image:1664503574618-659.png]]
19.2	1047
50.2	1048
84.2	1049
50.2	1050	(% style="color:blue" %)Step5: (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
	1051
73.1	1052	[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
19.2	1053
	1054
	1055	Users need to use below files:
	1056
	1057	boot_app0.bin @0e000
	1058
	1059	ESP_LORA-eeprom-class.bin @ 0x10000
	1060
	1061
50.2	1062	[[image:1664503593459-435.png]]
19.2	1063
	1064
	1065
50.2	1066	After upgrade finish, it will show finish as below:
19.2	1067
50.2	1068	[[image:1664503611848-385.png]]
19.2	1069
	1070
50.2	1071
19.4	1072	= 6. Developer Guide =
19.2	1073
	1074
19.4	1075	== 6.1 Compile Source Code ==
	1076
	1077
	1078	=== 6.1.1 Set up ARDUINO compile environment ===
	1079
	1080
51.28	1081	* 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	1082
51.15	1083	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	1084
	1085
50.2	1086	[[image:1664503635019-941.png]]
19.2	1087
50.2	1088
68.4	1089
51.28	1090	* (% style="color:#037691" %)Go to tools ~-~-> Boards ~-~-> Boards Manager,(%%) find the esp32 information and install it.
19.2	1091
50.2	1092	[[image:1664503715811-892.png]]
19.2	1093
	1094
84.3	1095	(% 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	1096
84.3	1097	[[image:image-20221024105643-1.png]]
	1098
84.4	1099	~ Figure1
84.3	1100
	1101
	1102	[[image:image-20221024105643-2.png]]
	1103
84.4	1104	Figure2
84.3	1105
	1106
51.28	1107	* Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]
19.2	1108
50.2	1109	Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
19.2	1110
	1111
50.2	1112	[[image:1664503752288-974.png]]
19.2	1113
50.2	1114
	1115
19.4	1116	== 6.2 Source Code ==
	1117
	1118
51.16	1119	* (% style="color:blue" %)Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:
19.2	1120
50.2	1121	[[image:1664503794261-827.png]]
19.2	1122
	1123
	1124
51.16	1125	* (% style="color:blue" %)Click to upload
19.2	1126
50.2	1127	[[image:1664503808294-336.png]]
19.2	1128
	1129
	1130
51.16	1131	* (% style="color:blue" %)Check the result, if the upload is successful, as shown below, open the serial port to view the data
19.2	1132
50.2	1133	[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
19.2	1134
	1135
	1136
18.2	1137	= 7. FAQ =
15.2	1138
	1139
18.2	1140	== 7.1 How to change the LoRa Frequency Bands/Region? ==
14.1	1141
	1142
51.14	1143	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	1144
12.1	1145
2.1	1146
18.2	1147	== 7.2 What is the pin mapping for the USB program cable? ==
2.1	1148
7.1	1149
18.2	1150	[[image:1664499635206-262.png]]
7.1	1151
	1152
	1153
51.28	1154	(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)
51.27	1155	\|=(% style="width: 118px;" %)Pin\|=(% style="width: 67px;" %)Color\|=(% style="width: 123px;" %)USB Pin
18.2	1156	\|(% style="width:118px" %)A4,B4,A9,B9\|(% style="width:67px" %)Red\|(% style="width:123px" %)VCC
	1157	\|(% style="width:118px" %)A7,B7\|(% style="width:67px" %)White\|(% style="width:123px" %)D- (N/A)
	1158	\|(% style="width:118px" %)A6,B6\|(% style="width:67px" %)Green\|(% style="width:123px" %)D+(N/A)
	1159	\|(% style="width:118px" %)A1,B1,A12,B12\|(% style="width:67px" %)Black\|(% style="width:123px" %)GND
	1160	\|(% style="width:118px" %)A5\|(% style="width:67px" %)Purple\|(% style="width:123px" %)MTDC/GOIO13
	1161	\|(% style="width:118px" %)B5\|(% style="width:67px" %)Blue\|(% style="width:123px" %)MTDC/GPIO12
	1162	\|(% style="width:118px" %)A8\|(% style="width:67px" %)Yellow\|(% style="width:123px" %)MTMS/GPIO14
	1163	\|(% style="width:118px" %)B8\|(% style="width:67px" %)Grey\|(% style="width:123px" %)MTDO/GPIO15
7.1	1164
113.8	1165
	1166
97.1	1167	== 7.3 Notes on using different serial port tools for TrackerD ==
	1168
	1169
113.4	1170	=== 7.3.1 Serial port utility ===
97.1	1171
	1172
	1173	Serial port utility requires you to automatically add data streams.
	1174
	1175	Need to adjust the data stream to RTS/CTS on physical restart.
	1176
	1177
	1178	(% class="wikigeneratedid" %)
	1179	[[image:image-20221102140621-1.png]]
	1180
	1181
	1182	When using AT commands, the data flow needs to be adjusted to XON/XOFF
	1183
	1184
	1185	[[image:image-20221102140638-2.png]]
	1186
	1187
98.2	1188
113.4	1189	=== 7.3.2 SecureCRT ===
97.1	1190
	1191
	1192	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.
	1193
	1194
	1195	[[image:image-20221102140704-3.png]]
	1196
	1197
	1198	[[image:image-20221102140712-4.png]]
	1199
	1200
98.2	1201
113.4	1202	=== 7.3.3 PUTTY ===
97.1	1203
	1204
	1205	[[image:image-20221102140748-5.png]]
	1206
	1207
	1208	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.
	1209
	1210
	1211	[[image:image-20221102140801-6.png]]
	1212
98.2	1213
113.4	1214
110.1	1215	= 8 Trouble Shooting =
98.2	1216
105.1	1217
113.4	1218	== 8.1 TDC is changed to 4294947296 and cause no uplink. ==
	1219
	1220
	1221	(((
110.1	1222	Before firmware v1.4.0: When the Transport Mode is enabled (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	1223	)))
105.1	1224
105.2	1225
	1226
113.4	1227	== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode ==
	1228
	1229
	1230	(((
110.1	1231	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	1232	)))
7.1	1233
	1234
110.1	1235
113.4	1236	== 8.3 The reason why it has been restarted after upgrading（V.1.4.1） ==
	1237
	1238
	1239	(((
113.1	1240	If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
113.4	1241	)))
113.1	1242
113.4	1243
113.1	1244	[[image:image-20221107145243-1.png\|\|height="695" width="443"]]
	1245
	1246
113.4	1247
110.1	1248	= 9. Order Info =
	1249
	1250
15.6	1251	Part Number: (% style="color:blue" %)TrackerD-XXX
8.1	1252
15.6	1253	(% style="color:blue" %)XXX(%%): The default frequency band
8.1	1254
15.6	1255	* (% style="color:red" %)EU433(%%): Default frequency band EU433
	1256	* (% style="color:red" %)EU868(%%): Default frequency band EU868
	1257	* (% style="color:red" %)IN865(%%): Default frequency band IN865
	1258	* (% style="color:red" %)KR920(%%): Default frequency band KR920
	1259	* (% style="color:red" %)AS923(%%): Default frequency band AS923
	1260	* (% style="color:red" %)AU915(%%): Default frequency band AU915
	1261	* (% style="color:red" %)US915(%%): Default frequency band US915
15.2	1262
113.8	1263
	1264
110.1	1265	= 10. Packing Info =
18.2	1266
	1267
51.30	1268	(% style="color:#037691" %)Package Includes:
8.1	1269
50.3	1270	* TrackerD LoRaWAN GPS/BLE Tracker x 1
	1271	* USB recharge & program cable x 1
12.1	1272
51.30	1273	(% style="color:#037691" %)Dimensions and Weight:
12.1	1274
98.2	1275	* Device Size: 85 x 48 x 15 mm
50.3	1276	* Weight: 50g
15.6	1277
113.8	1278
	1279
110.1	1280	= 11. Support =
18.2	1281
50.3	1282
18.2	1283	* 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.
51.28	1284	* 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	1285
113.8	1286
	1287
110.1	1288	= 12. Reference =
18.2	1289
	1290
12.1	1291	* [[Firmware in Bin format>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
	1292	* [[Source Code>>https://github.com/dragino/TrackerD]]
	1293	* [[Hardware Source>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
105.2	1294
	1295

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications