Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 124.1 by Bei Jinggeng on 2022/11/16 17:45

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications