Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 123.1 by Edwin Chen on 2022/11/16 15:30

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications