Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Version 163.1 by Bei Jinggeng on 2022/11/28 11:20

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

Wiki source code of TrackerD -LoRaWAN Tracker User Manual

Applications