Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 133.1 by Edwin Chen on 2022/11/21 10:00

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications