Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 110.1 by Edwin Chen on 2022/11/07 11:58

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications