Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 98.2 by Xiaoling on 2022/11/02 15:52

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications

Navigation