Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 155.2 by Xiaoling on 2022/11/24 17:00

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications